Skip to Main Content
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

Status Needs Clarification
Workspace Domino
Categories Administration
Created by Guest
Created on Jan 17, 2023

Make it possible to create multiple backup jobs with different retention periods

By today you can only set one retention period after that old backups are removed. This is working fine !!

But maybe you want to backup a different set of applications where you want to hold the backups longer. Therefore you have to configure a different retention time.

  • Attach files
  • Guest
    Jan 29, 2023

    Due to the very configurable implementation of Domino Backup, this request isn't simple to implement.

    Domino backup isn't intended as a full enterprise long term backup application.
    There are many different ways to configure backup and there are a couple of backup types storing databases in a way that they can be restored without Domino.

    - For example file operations merge changes by default into the database
    - The new Windows VSS Writer integration with auto recovery support, also writes database merged with deltas and closed

    This allows to restore them without Domino and keep them for a longer time outside the Domino backup application.

    The backup repository contains information about all backups.
    And adding more backup jobs logging to the same database at some point will overflow the backup lists.

    Changing the retention time per database would be an idea.
    But it would not work for all backup targets. For example this would not work for snapshot backups.

    In most cases snapshot backups always backup the whole data directory.

    The goal here is to not over complicate the backup functionality to keep it supportable for all type of backup implementations.

    But depending on how to keep some databases for longer term, there could be ways to implement it with custom configurations.

    If you have a cluster, you could also backup one server with a shorter retention time and the other server with excludes and a longer retention time.

    It would be interesting to understand your exact business case and what type of backup target you are planning to use.

    There is a GitHub project for integrations:

    You might want to raise an issue there and discuss with the team.
    We can try to help to find a way for your specifc use case.

    And this would be also visible to others having similar questions.

    -- Daniel Nashed

  • Admin
    Thomas Hampel
    Jan 21, 2023
    How about configuring long term preservation of those backups on file level by offshoring the instances you‘d like to keep to an other type of storage, e.g. offline?