Using tapes after Server crash and reinstall

[360Highlander]

Using NetBackup 4.5 on a Windows 2000 Server box.

Our server crashed last week due to hardware failure (don't trust RAID 5). Not only did one disk fail, but the machine then blue screened while writing the catalog tape. Needless to say restoring the from catalog did not restore all the necessary data.

I have spent the past couple of days doing Phase I imports on all of our tapes that contain Windows backups. I have decided I will not do a Phase II import on anything unless someone needs something restored. However now that I can see what is on each tape I can also determine when the images on the tapes would have expired had everything there not been a crash.

My problem is I am unable to change the Volume Pool of the tapes that I know would have already expired. I would like to place them in the Scratchpool, but Netbackup says "Cannot change Volume pool for assigned volume (91)"

What do I need to do so that NetBackup will allow me to put these tapes in the ScratchPool so I can start using the tapes again?

Thanks

 

[comtec17]

You will need to run the following command;

bpexpdate -m <barcodeid> -d 0 -force

Why do you not restore the Catalog from the backup prior the bad backup?

 

[Stumpr]

How to manually remove a tape completely from NetBackup/Media Manager.

http://seer.support.veritas.com/docs/208420.htm

Details:
First, if there are images on the tape, they need to be expired. This can be done by:
bpexpdate -ev <mediaid> -d 0

This will not completely free up the tape if the tape is frozen or suspended, so the command(s):
bpmedia -unfreeze -ev <mediaid>
or
bpmedia -unsuspend -ev <mediaid>
may be needed.

At this point there will be no image database entries for that tape and the media database should show the tape as not assigned therefore allowing the tape to be reused. However sometimes the image database and the media manager database can be out of sync, and the tape may show as still assigned, or if the tape has a NetBackup database backup on it, there would be no image entry to begin with. When a tape shows an assigned date, but no images are related to that tape, it will show up in the available_media report as dbbackup. To tell if a tape actually has a dbbackup on it, the command:
vmquery -m mediaid
will show a status, where 0x0 means normal backups, 0x1 means NetBackup database backup and 0x2 means Storage Migrator.
If it is 0x1, be certain this is not a database backup which will ever be needed.
If it is 0x2, it is in use by Storage Migrator and understanding of the use of the tape by Storage Migrator (not covered here) is required.

To free up the tape, when it has an assigned date but no images in the database, the command:
vmquery -deassignbyid <mediaid> <poolnumber> <status>
must be run, but the status will be displayed as 0x0, 0x1 or 0x2 and needs to be just 0, 1 or 2 in the vmquery -deassignbyid.

At this point the tape is available to be used for backups.

If the tape was bad or destroyed and that is why it is being removed, the command:
vmdelete -m <mediaid>
will remove the last remnants of information about it from media manager.

There are other options which may be specified for the above commands. Some are to specify server names, volume database host names, etc. If the NetBackup/Media Manager setup is complex, those options may be needed. The full paths to the commands mentioned are:

/usr/openv/netbackup/bin/admincmd/bpexpdate
/usr/openv/netbackup/bin/admincmd/bpmedia
/usr/openv/netbackup/bin/goodies/available_media
/usr/openv/volmgr/bin/vmquery
usr/openv/volmgr/bin/vmdelete
All but available_media have man pages.


Bob Stump
Just because the VERITAS documentation states a certain thing does not make it a fact and thats the truth