cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted

Using catalog backup and recovery to transfer NetBackup catalogs between Windows master servers as part of a hardware refresh

Hi All,

When running the catalog import wizard on the “new” server, I got the following message:

Please see the Screen Shot attached:

catalog restore error on new server.jpg

This is the Error that i get when I run the complete Catalogue Recovery

Previouse Environment is Shut Down all Storage is connected and accessible plus the backup for catalogue image is also accessible to the new environment.

Please suggest solution to this issue, or any other best way to do it.

 

1 Solution

Accepted Solutions
Highlighted
Accepted Solution!

Escalated to Veritas

Escalated to Veritas Enterprise Support as the Issue was Critical

 

Thanks All for your Feeds

View solution in original post

8 Replies
Highlighted

Re: Using catalog backup and recovery to transfer NetBackup catalogs between Windows master servers as part of a hardware refresh

Please share all the steps that you have performed.

Where is the DR file located?

What is the media that is listed in the DR-file?
Disk STU or tape?
Is this media listed in the DR-file available?
If tape - have you added it to the robot and ensure it is in CatalogBackup pool?

Highlighted

Re: Using catalog backup and recovery to transfer NetBackup catalogs between Windows master servers as part of a hardware refresh

Status 83 is "media open error".

On what media is the catalog located on (disk, tape, MSDP )?

A catalog restore can't be done from the bare metal - you need at least a empty EMM database for the recovery to work. Please see this tech note:

How to create a blank NetBackup NBDB database for the recovery of the NetBackup NBDB database from an online catalog backup in case of corruption or failure.

http://www.veritas.com/docs/000031908

Highlighted

Re: Using catalog backup and recovery to transfer NetBackup catalogs between Windows master servers as part of a hardware refresh

BPDM is used for disk based backup and restore jobs. If catalog is running this command, it might not be able to get the disk storage where catalog backup was taken. Please make sure that backup is kept in the same location on disk as in old server.

Highlighted

Re: Using catalog backup and recovery to transfer NetBackup catalogs between Windows master servers as part of a hardware refresh

Don't know about disk based catalog backup, but with tape based catalog backups you can need to change the media server in DR file to the new media server.

Unfortunately you can't see the activity monitor while catalog recovery is running, this would show if the wrong media server was used.

The standard questions: Have you checked: 1) What has changed. 2) The manual 3) If there are any tech notes or VOX posts regarding the issue
Highlighted
Accepted Solution!

Escalated to Veritas

Escalated to Veritas Enterprise Support as the Issue was Critical

 

Thanks All for your Feeds

View solution in original post

Highlighted

Re: Using catalog backup and recovery to transfer NetBackup catalogs between Windows master servers as part of a hardware refresh

You did not tell us HOW the issue was solved. A Solution only makes sense when you share what exactly the problem was and how it was solved.
Highlighted

Hi Marianne, The DR was

Hi Marianne,

The DR was located on Disk STU.

You know when you have Disk STU, it change and ID when attach to new system.

Followed the Procedure by Veritas Enterprise Engineer and created Temp directory and restored it.

Things now fine.

 

Sorry for the late response.

 

 

Highlighted

Re: Using catalog backup and recovery to transfer NetBackup catalogs between Windows master servers as part of a hardware refresh

That is why we asked about DR-file and storage location. Glad it is fixed now.