HCL Domino 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
when you compact -a -daos on the target archive database will be DAOS enabled.
This is not exactly what you are asking for but would enable all databases on the target archive server to be DAOS enabled.
Would this be OK or do you really want to have only the DAOS enabled databases on also DAOS enabled?
What if you disable DAOS on a source database? would you expect DAOS to be disabled on the archive too?
You see that this feature request raises a couple of related questions which is why it is probably not implemented this way.
IMHO the DAOS enable flag in combination with archive is a good way.
This lack caused a disk full error on customer because we decide to implement an archive policy at once to all users.
In order to circumvent the problem I had to create a fake policy (eg. archive docs older than 20 years), apply it, run compact an all archives, set the proprer archive.
As already written the archive DB should inherit ALL main database properties (DAOS, Compress Data and Design, etc.)