Video Screencast Help

Expiration of tape storage

Created: 15 Feb 2013 | 3 comments

scenario:

Full backup B2D on friday at 8pm (Keep for 4 days option) than duplicate Full to Tape

In BackupSets page I see Expiration Date for Storage Disk correctly after 4 days, BUT Expiration Date for Storage Tape after 11 days.

Diff backup B2D from mon-thur at 8pm (Keep for 4 days option) than duplicate Diff to Tape...

In BackupSets page I see Expiration Date for Storage Disk correctly after 4 days, BUT Expiration Date for Storage Tape after 11 days.

How is "Expiration Date for Storage Tape" calculated???

DLM can't remove correctly Storage to disk and delivery free space on volume disk use for backup, until this Expiration Date for Storage Tape is ...

Comments 3 CommentsJump to latest comment

pkh's picture

Tapes are not managed by DLM.  Tapes are managed using media sets as in previous versions of BE.   The OPP set in the media set that contains the tape determines the expiration of the tape.

adler.ravaioli's picture

All Tape used for Duplication Jobs are set with option "Keep for 1 day" and they are managed correctly in Storage Media Set... (scratched and available after 1 day)

But problem is this...

DLM correctly delete all Storage Disk when expired, but in Backup Set are remaining the Storage Tape using for Duplication and with the "strange" Expiration Date for Storage Tape, so

DLM can't remove Storage Disk and delivery free space on volume disk use for backup, until this Expiration Date for Storage Tape is still valid.

 

Colin Weaver's picture

Tape overwrite protection expiry should not be locking DLM

Are you sure your problem is not

a) DLM locks the full backup retention to the last differential backup retention. So if you run a Full on a Friday with Keep 4 days set and Differentail Mon-Thursday with Keep 4 days set then the full will not be removed form disk until 4 days (+ up to 4 hours) after the Thursday Differentials (some time on Monday)

b) DLM will not let you overwrite the very last complete backup of a resource until after another complete backup of the same resource - although this one should only affect things if one of your Friday full's fails to run, otherwise the timing form point a) would take precedence.

 

We do have a some defects in this area but I am, not aware of one that specifically matches your symptoms as such for us to investigate further please log a formal support case fro Syamnetc to confirm exactly what your problem (and configuration) is.