02-05-2009 08:54 AM
I'm having an issue with Netbackup Vault including images in a vault profile that shouldn't be there, and I can't figure out why it's doing it.
02/05/2009 Monthly Offsite Page: 1
Robot: TLD(2) Vault: Offsite Profile: Monthly
Vendor: Iron Mountain Session ID: 1806
Detailed Distribution List for Vault
SLOTID MEDIA EXPIRATION IMAGES MBYTES CATEGORY EJECTED
CLIENT KBYTES
POLICY SCHEDULE
WRITTEN BACKUP ID PARTIAL
182 T00156 03/07/2009 15 383643 NBU YES
CLIENT-A 7281963
CLIENT-A.VM.Std CLIENT-A.Full.VM
02/04/2009 CLIENT-A_1233749589 **EXTRA*
CLIENT-B 1256330
CLIENT-B.NT CLIENT-B.Incr
02/04/2009 CLIENT-B_1233731195 **EXTRA*
CLIENT-C 1276180
CLIENT-C.NT.BMR CLIENT-C.Incr
02/04/2009 CLIENT-C_1233731220 **EXTRA*
CLIENT-E 80754160
TEST TEST.Full
01/31/2009 CLIENT-E_1233414900 COMPLETE
CLIENT-E 60689571
TEST TEST.Full.2
01/31/2009 CLIENT-E_1233398745 PARTIAL
In this email, only CLIENT-E in the TEST policy should have been vaulted. It's been working that way for months. Somehow, the clients named A B C all got added in, with that weird **EXTRA* type.
The only change I have made recently is to put clients A B C in their own vault profile. Since creating this new vault profile, I'm seeing them added into two separate vault profiles they are NOT members of. Both times, the backup images are listed with the weird **EXTRA* modifier.
I can't find any documentation on that **EXTRA* text, nor are my internet/STN searches proving fruitful.
Anyone seen this type of issue before?
Solved! Go to Solution.
02-05-2009 10:07 AM
Found the issue.
There is an issue with the library not ejecting tapes due to a full CAP, and since the vault profile has the option set to suspend the media at the time of eject, some tapes aren't getting ejected so they're not being suspended, and are being picked up for other vault profiles that share the same volume pool.
bingo!
Now, time to find out why all of the tapes aren't being ejected.
02-05-2009 10:07 AM
Found the issue.
There is an issue with the library not ejecting tapes due to a full CAP, and since the vault profile has the option set to suspend the media at the time of eject, some tapes aren't getting ejected so they're not being suspended, and are being picked up for other vault profiles that share the same volume pool.
bingo!
Now, time to find out why all of the tapes aren't being ejected.