Images Duplication from Tape to Data Domain expire very fast

[Bryan_Sousa]

Hi all,

We has been duplicate images from tape to disk (data domain), because the backup retention in tape are differents from the data domain backup.

So, we can see that the image duplicated to data domain expire after a few minutes.

System Informations:

Netbackup version: 7.6.0.4

Master and Media Server: Windows Server 2008

Data Domain: EMC

someone already had a similar problem?

Thanks all.

[sdo]

Are your SLPs configured such that they immediately expire the source copy after succcessful duplication from DD to tape?

[Marianne]

How are you duplicating the images? SLP? Using the Duplicate option in Catalog section of the GUI? Using bpduplicate from cmd? Whatever method you are using, we need to know the parameters specified /selected.

[Nicolai]

if you are using the bpduplicate command be sure to specify the -rl retention_level[,rl-copy2,...]

http://www.symantec.com/docs/HOWTO103809

It's best to use SLP for processing backup images. Primary destination Data Domain with retention X then duplicate with retention Y

[Bryan_Sousa]

Dears,

I'm not using SLP.

I'm Using the Duplicate option in Catalog section of the GUI for duplicate the images to data domain.

I selected the Storage Unit (data domain), in Retention I selected "No changes" and in copies I select the copy as pimary.

The process run normally, but the image expire after few minutes.

[sdo · Accepted solution]

Ok - two possible causes:

Scenario 1:  Your source backups have not previously had their expiration date manually adjusted, and so you've discovered a bug in duplication.

Scenario 2:  You previously manipulated the expiration dates of the source images - AND - the previous "original-backup-date PLUS original-retention-level" has since passed, and so... because you are not choosing a new retention level for the new copy... such that the "original-backup-date PLUS retention-level-of-new-copy" exceeds the current date and time, then... when the duplication runs, it "recalculates" the expiration date of the new copy as "original-backup-datetime PLUS original-retention-level", and so because the sum of that calculation is in the past... this leads to the backup images being expired shortly after duplication completes.   If this is true, then I guess it's a shame that the admin GUI doesn't warn you.

Sceanrio 3:  Similar to scenario 2, but you are duplicating image image that was imported from another backup environment where the retention level "period" of the original retention level "number" of the original backup environment is longer than the "period" of the same retention level "number" in the new/current environment within which the duplication is occuring.  Remember:  Backup images carry a 'retention level number' and not a 'retention level period' - so if, for example, backup environment "A" has a retention "period" of "2 years" for retention "level" number "20", AND backup environment  "B" has a retention period of "2 days" for retention level number "20" - then when the retention of the new copy in environment is "recalculated" it will use "2 days" within environment "B", and not the "2 years" from environment "A".

.

The solutions:

Scenario 1:  Review the very latest EEB listing (version 8) for NetBackup v7.6 and see if your bug has previously been picked up / described.  If not, open a support case.

Scenario 2/3:  Choose a retention level for the target duplication such the sum of "original-backup-date PLUS new-retention-level" exceeds the current date and time.

[Nicolai]

Please consider to use SLP's. Netbackup can do the duplication for you automatic.

There some background infromation about in the documetn below.

Best practices for using Storage Lifecycle Policies and Auto Image Replication in NetBackup 7.6

http://www.symantec.com/docs/TECH208536

[Bryan_Sousa]

Dears, thanks for all.

Now i understand this process: "it "recalculates" the expiration date of the new copy as "original-backup-datetime PLUS original-retention-level", and so because the sum of that calculation is in the past... this leads to teh backup images being expired shortly after duplication completes"

I choosed retention level 1 year and the image not was expired