commvault.com commvault.com
Solved

StoragePolicy tiering or moving backups older than 6 months to different storage

  • 31 May 2023
  • 2 replies
  • 60 views
M
Rank
Badge +2

Hello community,

We have Storage Policy which keeps all backups for 30 days and monthly backups for 18 months all on the same storage.

To free up some space, we could create another copy pointing to the cloud to keep our monthly backups for 18 months. Then we would have 30 days on prem and all monthly backups in the cloud.

Now, a new idea has come up to keep 30 days on prem as well as 6 months for monthly backups.
And when the monthly backups are 6 month old, the should be copied to the cloud until they are 18 months old and removed on prem.

Is there a way to delay the copy of the monthly backups for 6 months?
 

 

icon

Best answer by Brian Bruno 1 June 2023, 15:39

View original

2 replies

B
Rank
Userlevel 5
Badge +12

Hi @Marc St.,

 

Yes, this can be achieved using the ‘Defer Aux Copy for n Days’ option on your Secondary copy to cloud : 

 

https://documentation.commvault.com/2022e/expert/11496_delay_creation_of_additional_backup_copies.html

 

This will defer the aux copy of jobs until they have existed on the source copy (primary in this case) for the set number of days.  With that in mind, we should be able to do the following : 

Primary Copy :

Basic Retention : 30 days

Extended Retention : Monthly backups for 180 days

 

Secondary Copy (Selective Copy - Monthly Fulls Only)
Basic Retention : 540 days

Defer Aux Copy for 180 days

 

This configuration should give you the outcome you’re looking for.  The Monthly full backups will be maintained on-prem for 6 months.  After the job has existed on that copy for 6 months, it will then simultaneously will become eligible to be copied to the Cloud copy, as well as now be allowed to age.

 

Just to clarify, the software will automatically ensure that the job will not be pruned off of the on-prem copy until it has successfully been written to your cloud copy.  Only after the copy is successful will the job be allowed to age, as it will have now met all basic and extended retention requirements.

 

-Brian Bruno

M
Rank
Badge +2

Hi @Marc St.,

 

Yes, this can be achieved using the ‘Defer Aux Copy for n Days’ option on your Secondary copy to cloud : 

 

https://documentation.commvault.com/2022e/expert/11496_delay_creation_of_additional_backup_copies.html

 

This will defer the aux copy of jobs until they have existed on the source copy (primary in this case) for the set number of days.  With that in mind, we should be able to do the following : 

Primary Copy :

Basic Retention : 30 days

Extended Retention : Monthly backups for 180 days

 

Secondary Copy (Selective Copy - Monthly Fulls Only)
Basic Retention : 540 days

Defer Aux Copy for 180 days

 

This configuration should give you the outcome you’re looking for.  The Monthly full backups will be maintained on-prem for 6 months.  After the job has existed on that copy for 6 months, it will then simultaneously will become eligible to be copied to the Cloud copy, as well as now be allowed to age.

 

Just to clarify, the software will automatically ensure that the job will not be pruned off of the on-prem copy until it has successfully been written to your cloud copy.  Only after the copy is successful will the job be allowed to age, as it will have now met all basic and extended retention requirements.

 

-Brian Bruno

Hi Brian,

I know Commvault since of many years but to my shame I have not seen this option in the copy properties...
Thanks a ton for your quick and detailed answer.

Kind Regards
Marc

Reply


Terms & ConditionsCookie settings