cancel
Showing results for 
Search instead for 
Did you mean: 

Netbackup Catalog Recovery - Linux Redhat -EASY?

tomb_IAS
Level 2
Partner Accredited Certified

All,

An easy question I hope. I have successfully recovered the Netbackup Catalog to a new server but due to other issues we weren't able to start using the new Master. So my question is will recovering the catalog (Full) again to the same server overwrite the existing Catalog or will I have to uninstall Netbackup and reinstall/recover again. We need the catalog to be up to date.

thanks,

tom

4 REPLIES 4

Marianne
Level 6
Partner    VIP    Accredited Certified

@tomb_IAS

I have moved your post to NetBackup forum for better visibility.

nbutech
Level 6
Accredited Certified

Hello,

If the NBU version hasn't change and nothing has been added as hotfix then I don't think uninstall is required. You can recover from the new catalog backup and see if everything looks working to you.

But many times it is recommended though to strat clean. 

Any choice you make if your NBU Ctalog is recovered and running then you are good to use it

Marianne
Level 6
Partner    VIP    Accredited Certified

I have never restored from an older version of Catalog backup - only latest.
I am also not aware of any documentation with this kind of information, nor can you log a Support call with Veritas because of your EOSL NBU version.
So, the following advice is just my humble opinion.

You can recreate the nbdb catalog before recovering from the latest catalog backup:

How to create a blank NetBackup NBDB database for the recovery of the NetBackup NBDB database
https://www.veritas.com/support/en_US/article.100017664.html

HTH

tunix2k
Level 5
Partner Accredited

Hi tomb_IAS !

 

I think you can restore a newer catalog backup as long as no changes in NBU version took place.

Due to ducumentation netbackup have to be up and running. No need for fresh install or delete of old catalog. My experience is that settings to access catalogbackup tape are overwritten. (drives, robots, stus etc)

If you have a look at the catalogimage you will find a TIR file. Ctalog backup is special and not the same as "normal" backups. But I think a kinf of catalog TIR restore will take place.

 

ciao

tunix2k

 

[root@nbumaster ~]# bpimagelist -l -hoursago 165
IMAGE nbumaster.hoon 0 0 13 nbumaster.hoon_1515071839 Catalog1 35 *NULL* root full 0 5 1515071839 3 1523107039 0 0 3245 327 1 2 0 Catalog1_1515071839_FULL.f *NULL* *NULL* 0 1 0 2 1515158239 *NULL* 0 0 0 0 0 0 0 *NULL* 0 0 0 *NULL* 149 1 0 44376 0 0 *NULL* *NULL* 0 0 0 0 *NULL* *NULL* 0 1 0 0
HISTO 0 0 0 0 0 0 0 0 0 0
FRAG 1 -1 45 235 0 0 0 /DSSU/nbumaster.hoon_1515071839_C1_TIR nbumedia1.hoon 262144 0 0 -1 0 nbumedia1.hoon 1523107039 0 65541 0 0 0 1 0 1515071842 3 1 *NULL* *NULL* 0 0
FRAG 1 1 3200 0 0 0 0 /DSSU/nbumaster.hoon_1515071839_C1_F1 nbumedia1.hoon 262144 0 0 -1 0 nbumedia1.hoon 1523107039 0 65541 0 0 0 1 0 1515071842 3 1 *NULL* *NULL* 0 0
IMAGE nbumaster.hoon 0 0 13 nbumaster.hoon_1515071828 Catalog1 7 *NULL* root full 0 5 1515071828 6 1523107028 0 0 236992 18 1 1 0 Catalog1_1515071828_FULL.f *NULL* *NULL* 0 1 0 0 0 NBDB:146:1515071826:F 0 0 0 0 0 0 0 *NULL* 0 0 0 *NULL* 148 1 0 5341 0 0 *NULL* *NULL* 0 0 0 0 *NULL* *NULL* 0 1 0 0
HISTO 0 0 0 0 0 0 0 0 0 0
FRAG 1 1 236992 0 0 0 0 /DSSU/nbumaster.hoon_1515071828_C1_F1 nbumedia1.hoon 262144 0 0 -1 0 nbumedia1.hoon 1523107028 0 65541 0 0 0 1 0 1515071834 3 1 *NULL* *NULL* 0 0
[root@nbumaster ~]#