There is currently no way, without programming something, to verify that the quota settings of cluster replicas are the same. If we can identify where cluster replicas have differant quota's, either with cluster analysis or an Admin view, then we could correct inconsistancies. Alternatively, if there was a way to ...
When using quota/warnings once this is set it should replicate so that the change does not need to be modified on each replica. Also, the ability to generate a report of replicas where the quota/warning setting are not in sync would be very helpful.
Currently, we use quotas/warning on our ...
we have enforced strict mail quota rules for everybody (with the possibility to archive old mails and a 'archive attachments). Unfortunatelly some users don't get the mail quota warning message, so every few days we have to use our cluebat and tell them what to do after such messages and ...
Rather than having to compact mail files to get them under quota, it would be great if the calculation that determines quota could ignore any whitespace in the mail file.
It would be very useful to know who changed a database quota, when it was changed & the before & after values. Otherwise, lazy administrators ignore the quota that should be enforced & increase quotas endlessly to placate complaining users.