Reusing Tapes - Expiration

Just looking to confirm some logic here...

If some (not all) savesets and dependencies have expired on a tape that doesn't mean that space can be reused for some backup job looking for media? Correct?

I assume all savesets and dependencies need to expire before the tape can be recycled and reused? Correct?

I have ran out of usable tapes and it seems the savesets are oddly spread across multiple tapes so nothing can be reused. I'm trying to understand whats going on here so I can move forward with troubleshooting.


Tags (1)
0 Kudos
2 Replies
4 Germanium

Re: Reusing Tapes - Expiration

There is nothing to troubleshoot. This is the ehavior of each "sequential storage media".

And it is nothing specific with respect to NetWorker.

What you can do is that you consolidate the backups as follows:

  1. Determine the tapes you can recycle (you need at least 1 (re-)usable tape) und re-label it/them

  2. Set all other tapes ro read-only:   nsrmm -y -o readonly <volume>

  3. Start migrating the save sets one-by-one:  nsrclone -m -b <same_pool> -S <ssid>

  4. Once the tape does not contain any valid save sets any more, re-label it

Of course you must have at least 2 tape drives to run a migration from one drive/media to another.

The most obvious reason for this effect is that you have media which contains save sets with different retention policies.

To avoid that you better use a separate pool for each retention period.

0 Kudos
2 Iron

Re: Reusing Tapes - Expiration

For step 3,  it is better to use nsrstage than nsrclone.

The nsrclone command with -b will require a clone pool.

With nsrstage, you can specify any pool. including the same pool the source tape was labeled with.

0 Kudos