01-03-2016 12:08 AM
Solved! Go to Solution.
01-03-2016 04:07 AM
01-04-2016 01:08 AM
You are better of throwing a bunch of tape at Netbackup and let it manage the backups.
The approach on knowing "Monday is on this tape" is a thing from the past in my view. The strategy may work for small shop, but once yore backup exceed more than one tape (or even using multiple retention) its become a heavy task to manage.
My advice is to keep your backup server and robot in a alternate another location from source data, and leave as many tapes in the robot as possible.
Br Nicolai
01-05-2016 12:37 AM
Only tapes that started in scratch, will be returned to scratch when they expire.
Eg.
Scratch > Some other pool > Scratch
If the tape starts in a pool other than scratch (EG. you manually move it, when it is empty to NetBackup pool) it will always stay in NetBackup pool
01-05-2016 12:43 AM
... so you mean to say even if a tape is already expired, unless i move them manually to scratch pool NBU will not touch them?
No. That is not what I meant.
If a tape is in Daily pool it will stay in Daily pool - with or without unexpired backups on them.
(This is true if the tape was not previously in Scratch pool.)
My advice is to add a Scratch Pool.
This is where you will add all new tapes and move expired (unassigned) tapes to.
(You will have to do this once for existing tapes as soon they expire.)
A Scratch pool has the advantage that you do not have to battle to ensure that each pool have sufficient media.
Any pool without blank (unassigned) tapes will draw from Scratch when a new tape is needed.
If a tape started out in Scratch pool, it will return to Scratch pool once all images have expired.
See http://www.veritas.com/docs/000063473
01-03-2016 04:07 AM
01-04-2016 01:08 AM
You are better of throwing a bunch of tape at Netbackup and let it manage the backups.
The approach on knowing "Monday is on this tape" is a thing from the past in my view. The strategy may work for small shop, but once yore backup exceed more than one tape (or even using multiple retention) its become a heavy task to manage.
My advice is to keep your backup server and robot in a alternate another location from source data, and leave as many tapes in the robot as possible.
Br Nicolai
01-05-2016 12:01 AM
hi all,
ok so far, as a carry over from the 20th century of managing tapes, i have implemented a Daily, Weekly, and Monthly pool.
oh there's also a Yearly pool which benefited me a lot this 2015 year end backup.
and today, i have returned two tapes which belonged to the Daily pool as they are due or expired already.
i see that the "Tape Summary" is a much, much better way to find tapes that are due to expire. thanks for pointing that out.
yes we have a need to send tapes offsite hence the need to know which tapes where used. fortunately, our requirement only need the Monthly and Yearly tapes so that lessens the number of tapes to eject.
i only have a 30-slot (2 are used by the cleaning cartridges) so probably until end of this month i will have to eject some tapes whose status is full and not expired. as i still have remnants of tapes that don't belong to the new pools i created.
Vault? i will need to look into this.
@Marianne, so you mean to say even if a tape is already expired, unless i move them manually to scratch pool NBU will not touch them?
EDIT: i have a media that is as of today is expired but when i load it back to the library, it went back to the Daily pool. won't NBU reuse this where it is since it's already expired? or must i have to manually move it to Scratch pool first to be reused?
01-05-2016 12:37 AM
Only tapes that started in scratch, will be returned to scratch when they expire.
Eg.
Scratch > Some other pool > Scratch
If the tape starts in a pool other than scratch (EG. you manually move it, when it is empty to NetBackup pool) it will always stay in NetBackup pool
01-05-2016 12:43 AM
... so you mean to say even if a tape is already expired, unless i move them manually to scratch pool NBU will not touch them?
No. That is not what I meant.
If a tape is in Daily pool it will stay in Daily pool - with or without unexpired backups on them.
(This is true if the tape was not previously in Scratch pool.)
My advice is to add a Scratch Pool.
This is where you will add all new tapes and move expired (unassigned) tapes to.
(You will have to do this once for existing tapes as soon they expire.)
A Scratch pool has the advantage that you do not have to battle to ensure that each pool have sufficient media.
Any pool without blank (unassigned) tapes will draw from Scratch when a new tape is needed.
If a tape started out in Scratch pool, it will return to Scratch pool once all images have expired.
See http://www.veritas.com/docs/000063473
01-05-2016 03:37 AM
i load all new tapes to Scratch pool (not my default) manually to replace tapes that have status "Full".
based on above suggestions, even though the expired tape loaded in Daily pool, because it started from scratch pool it will eventually be returned there once ALL images on the tape expired.
for those catching up and as a summary, i'm rotating my tapes based on an old tape rotation scheme of Grandfather-Father-Son where Grandfather is the Monthly, Father is the Weekly, and Son is the Daily.
i have created this three pool Monthly, Weekly, and Daily (Daily tapes will be left inside library as well as Weekly; for a total of 11 tapes) and am only sending to remote site the Monthly tapes.
btw, i have also the Yearly pool for year end backups which was also sent offsite.
01-05-2016 03:53 AM
Expired tapes in Daily pool will only be returned to Scratch if the 'Previous Pool Name:' field shows Scratch.
If that column does not show by default in Media GUI, you can see this field with nbemmcmd command:
nbemmcmd -listmedia -mediaid <media-id>
or as per Martin's command to list all media ( how to expire tapes in catalog?) : nbemmcmd -listmedia -allrecords
If this column is blank or something else, you will need to move Unassigned (expired/new) tapes manually to Scratch as a once-off exercise.