Due to recent events in South La. with the hurricanes, I had to remove all quotas for a certain agency on 2 clustered servers. Now, I am having to reset these quotas and it’s been a BEAST! All that I’ve read,I will have to reset the quotas on the other server manually??? What a waste of IT time. Does anyone have any OTHER ideas???
Desperate in BR
Subject: Why won’t quotas replicate when settings are in place???
I did a little test with our clustered server and it looks like your research is correct. The quota setting change doesn’t replicate to the clustered server via cluster replication or regular replication. So, it would have to be changed manually on each server where a replica exists.
To save time, did you know that in the Admin client you can select multiple databases at a time and change the quota on all of them at once? (As long as they all get the same quota.) Depending on how many different quota levels you have, that could turn this into a 1-click operation.
HTH
Subject: RE: Why won’t quotas replicate when settings are in place???
Yes indeed I do know about selecting multiple db’s for quotas. However, Notes has a nasty way of sorting and because we have different quotas assigned due to title/rank…that too is cumbersome.
Does the router have something to do with this not working?
Thanks for your response.
Subject: RE: Why won’t quotas replicate when settings are in place???
The router would not have anything to do with this not working. Routing and replication are separate. I suspect the quota wouldn’t replicate for any database, not just mail. This is probably intentional, as database size and drivespace are tied when you consider application databases, not just mail databases.
RE: “Notes has a nasty way of sorting”
Click on any column header in the Admin clients, Files view to sort by that value. For instance, click on the “Quota” column header,select all set at a certain quota, and change those to a different quota. I realize there is not a sorting for people’s title/rank unless you were to put that into the db title or something. I guess it would depend on how you broke these up as to what would be easier. If you have a few at the highest level, then a few at a lower level, then everyone else at the lowest…what you could do is select the highest and set them first, then select the next level and set them, then sort by quota and select all who are left and set them.