#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

Keep backup logs in dominobackup instead of pruning them

We use dominobackup to make backups while the backup provider adapts to Domino 12. So we backup a week of databases, and the copies are picked up by the file backup of our backup software and stored much longer. The problem is that if we need to restore something older than a week, we have to do several restore activities: first restore the dominobackup.nsf so we can pickup the old log documents, so dominobackup knows about this backup having occurred again, then the database itself, then go to dominobackup and restore the actual database or documents. I fully get why the backup itself is pruned, because of storage needs. But I strongly disagree with pruning the backup logs, this is causing a lot of extra work and complicates things, so I have to spend expensive senior admin time doing a restore instead of letting a normal admin do a restore.

  • Guest
  • Dec 21 2021
  • Under Consideration
  • Attach files