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

Add a new idea Subscribe
Status Under Consideration
Workspace Domino
Categories Administration
Created by Guest
Created on Dec 21, 2021

RELATED IDEAS

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.

  • Attach files
  • Guest
    Reply
    |     Oct 10, 2022

    The number of backup for the database repository is limited! You can't store more than around 150-200 backups (depending on the path len of the databases). The prune of the backup is designed to be in-line with the backup data.

    If you are below 150 backups in total, you can configure the prune operations to not prune the backups from dominobackup.nsf today.

    It is designed for flexibility. But you still need a restore logic, which takes into account the other data store. where you store the backups for a longer time.

    This is still a logic you can implement today leveraging the existing functionality in backup. In case you need a higher number of backups than 150, you can keep the backup log files with the backup and import them from the log to the dominobackup.nsf for a restore when needed.

    This option is actually included for disaster recovery where you dominobackup.nsf is not available. Also Domino backup/restore configuration is dumped to a DXL, and can be imported by the way.

    There is a HCL GitHub open source project to discuss those type of integrations.
    https://github.com/HCL-TECH-SOFTWARE/domino-backup


    I am happy to help with some additional information in the community project.

    [ Daniel Nashed / HCL Lifetime Ambassador ]


Copyright © 2023 HCL Technologies Limited