I'd suggest using the bpcat* commands:
/usr/openv/netbackup/bin/admincmd/bpcatarc
/usr/openv/netbackup/bin/admincmd/bpcatlist
/usr/openv/netbackup/bin/admincmd/bpcatres
/usr/openv/netbackup/bin/admincmd/bpcatrm
We were able to cut our catalog from ~450GB to ~250GB.
Ken Zufall
Operating
Hello,
we have also to move our Netbackup master server ( 6.5.4) in Solaris 10 (
cluster config) to linux 2.6 Netbackup ( 7.1 ) .
Our plan is very close to your Option 2 .
keep existing Master and catalog to archiving .
Start with a new catalog on linux cluster config with Netbackup 7.1
Christophe,
You can upgrade the solaris installation and copy the class directory. Doing
that you will move all policies easily.
Also there is a technote at Symantec site that describe the recovery without
import method. You can use this method to move the images and the tapes from
the
We are leaning towards option 2
@ken_zufall Thanks!
What to do with our growing Catalog on the Master server??
I'd suggest using the bpcat* commands:
/usr/openv/netbackup/bin/admincmd/bpcatarc
/usr/openv/netbackup/bin/admincmd/bpcatlist
/usr/openv/netbackup/bin/admincmd/bpcatres
We have a midsize NBU environment consist of 1 master and 6 media servers.
Windows 32bit NBU7.0.1 backing up around 60-70 TB per week. Good portion of the
data coming from ndmp. Front-end connected to a VTL and backend to a
SpectraThe master catalog has grown to about 450 GB.
We are
1B: instead of keeping the catalog on a local disk - possibly we can
direct connect to one of our filers and dump the catalog there.
I always considered it a really bad idea to put my catalog, or even
catalog backup, on the same storage systems as the data that I'm
backing up (I'm not
