Forum Discussion

BKPEXEAdmin's avatar
11 days ago
Solved

Extended retention for FULLs and Cycles

Hi Folks,

 

Wanted to get some clarification regarding retention in NBU10:

  1. In NetBackup 10 through the WebUI, does it support extended retention for Full backups? For example, if I have a weekly Full backup schedule with a standard retention of 4 weeks, is there a way to configure NetBackup to keep the last successful Full backup for a longer period—say, 3 months—even after the regular 4-week retention expires? I'm looking for a way to automatically retain a longer-term Full without creating a separate backup schedule or policy manually. Is this possible in the WebUI or via another mechanism?
  2. Does NetBackup have a concept similar to Commvault's "Cycles" or IBM Spectrum Protect's "Versions" where the system ensures that at least one backup cycle is retained, even if backups fail to run for a certain period? This would help ensure that a backup cycle is always available and not expired due to missed jobs. Does NetBackup have such a feature or a similar mechanism to ensure this level of protection?


Regards,

  • 1)
    NetBackup has never had the ability to change the retention of a backup image after the backup via the WebUI or JavaUI.
    To do this, you must use the bpexpdate CLI command. If you need to automate the process, you will have to create a script.  

    2)
    NetBackup does not use a versioning or aging concept—only retention.
    You must ensure that the configured retention is sufficient to survive a failure.

3 Replies

  • 1)
    NetBackup has never had the ability to change the retention of a backup image after the backup via the WebUI or JavaUI.
    To do this, you must use the bpexpdate CLI command. If you need to automate the process, you will have to create a script.  

    2)
    NetBackup does not use a versioning or aging concept—only retention.
    You must ensure that the configured retention is sufficient to survive a failure.

  • Hi BKPEXEAdmin​ 

    Further to StefanosM's reply for point 1 - you could consider using SLP's to achieve what you want (only successful backups will be controlled by an SLP. The primary backup retention could be your 4 weeks, then a secondary copy (duplication) could be retained for the 3 months (and potentially to another backup target). 

    Cheers