#dominoforever | Product Ideas Portal
Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.
For more information and upcoming events around #dominoforever, please visit our Destination Domino Page
Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.
For more information and upcoming events around #dominoforever, please visit our Destination Domino Page
This feature is shipping as part of Domino V12
This feature is now available as part of the Domino Early Access Program https://blog.hcltechsw.com/domino/new-october-release-domino-early-access-program/
Replication of database quota / warning settings within a cluster would in fact be of great help - we implemented own small utilities to achieve this.
You are able to activate DAOS, encryption and compression in the mailtemplate. So you don't have to touch these settings after a new user is set up.
Yes please.
How about controlling them via policy if you need them all to match? Currently I am manually having to set DAOS, encryption, quota, and compression separately on 4 different servers each time a user is setup. It would be nice to have those settings enforced across all replicas.
What are the circumstances, not to replicate the quota and the warnings for a mailfile in a cluster? Perhaps, with a special notes.ini entry for the cluster servers?
DAOS, encryption and compression is different question....
Thomas is right, there are circumstances why this should not be a default or a general change of the behavior. And from my point of view i would prefer a granular config setting ,what database properties should replicate. (with a wise chosen default in beginning :-)) Btw.: Some database properties replicate already. In first it can help, especially for newbies, to make this visible in the database properties window?
There are circumstances where servers need to have different settings, so replicating those flags needs to be configurable.
Also replicate database properties, like DAOS, encryption and compression