Version etc -
NetBackup Version
HARDWARE SOLARIS
VERSION NetBackup 4.5GA
RELEASEDATE Thu Mar 21 04:50:03 CST 2002
NetBackup Binary Version
NetBackup-Solaris2.6 4.5MP5
SunOS 5.8 Generic_117350-02
System Configuration: Enterprise 450 (3 X UltraSPARC-II 400MHz)
Memory size: 3072 Megabytes
Ok, this server is old, it has been running for a long time and simply needs to keep doing so until migration off is finished. So, no upgrades of any kind are an option.
I have a catalog problem, every backup fails with an 84, it is running accros an old atm link and I want to move it to the gig link but seem to be missing the simple answer?
ServerA Approx 40GB catalog has a cron to kick off the catalog backup to MediaServerB:
00 12 * * * /usr/bin/rsh MediaServerB_atm0 /usr/openv/netbackup/bin/admincmd/bpbackupdb -v 2>&1
Fine, it kicks off, it runs around 2 hours, then dies..
No matter what I seem to change, it always seems to use the same link to that media server, and I want to somehow force it to go over the gig link. How can this be done?
Yes, this is a new problem. It is new because the catalog was not being backed up properly before and I am trying to make sure we do have a catalog just in case.. The person here before was only backing up approx 1gb of the catalog so it worked fine every day.
That said, I will also let you give me a sanity check- previous catalog being backed up was:
ServerA_atm0:/usr/openv/netbackup/db/images/servera_atm
ServerA_atm0:/usr/openv/volmgr/database
ServerA_atm0:/usr/openv/var
I have changed this to include the whole db tree..
ServerA_atm0:/usr/openv/netbackup/db/*
So now the 84's fly.. and I need to switch links.. =)
Ideas?
NetBackup Version
HARDWARE SOLARIS
VERSION NetBackup 4.5GA
RELEASEDATE Thu Mar 21 04:50:03 CST 2002
NetBackup Binary Version
NetBackup-Solaris2.6 4.5MP5
SunOS 5.8 Generic_117350-02
System Configuration: Enterprise 450 (3 X UltraSPARC-II 400MHz)
Memory size: 3072 Megabytes
Ok, this server is old, it has been running for a long time and simply needs to keep doing so until migration off is finished. So, no upgrades of any kind are an option.
I have a catalog problem, every backup fails with an 84, it is running accros an old atm link and I want to move it to the gig link but seem to be missing the simple answer?
ServerA Approx 40GB catalog has a cron to kick off the catalog backup to MediaServerB:
00 12 * * * /usr/bin/rsh MediaServerB_atm0 /usr/openv/netbackup/bin/admincmd/bpbackupdb -v 2>&1
Fine, it kicks off, it runs around 2 hours, then dies..
No matter what I seem to change, it always seems to use the same link to that media server, and I want to somehow force it to go over the gig link. How can this be done?
Yes, this is a new problem. It is new because the catalog was not being backed up properly before and I am trying to make sure we do have a catalog just in case.. The person here before was only backing up approx 1gb of the catalog so it worked fine every day.
That said, I will also let you give me a sanity check- previous catalog being backed up was:
ServerA_atm0:/usr/openv/netbackup/db/images/servera_atm
ServerA_atm0:/usr/openv/volmgr/database
ServerA_atm0:/usr/openv/var
I have changed this to include the whole db tree..
ServerA_atm0:/usr/openv/netbackup/db/*
So now the 84's fly.. and I need to switch links.. =)
Ideas?