database error Netbackup
This issue has been solved. See solution.
Claudio Veronezi
November 5th, 2009
Hello
I have migrate my master server,
now netbackup 6.5.4 over solaris 10
I'm getting some database errors...
I'll try to restart services. but Why does it hapened is the question? mistery :)
here is the SS
Thaks..
see ya
:wq!
I've restarted
I've restarted and error still there
All jobs are queued
Claudio Veronezi Mendes
EMC / Veritas / Solaris
Londrina - Pr - Brazil
Please tell us more about
Please tell us more about your 'migrate' procedure?
What did you migrate from?
Please list the steps that you followed.
Wow.. Marianne cool
Wow.. thanks Marianne.. I really like your posts... almost a fan
soo.. We have migrated from a V240 to a V490 solaris 10
- Installed a new server
- update from 6.5.3 to 6.5.4 in both servers (v240 and v490)
- bpbackupdb in the v240
- bprecover in the v490
- reconfigured the devices
the backup have started well
at night a lot of file polices have been started and finished status = 0
that 3 o'clock everything have stopped..
I have restarted the netbackup and the error still there
Claudio Veronezi Mendes
EMC / Veritas / Solaris
Londrina - Pr - Brazil
now I'm rebooting the server
I know that is windows thing.. but I have to try..
solaris 10 rebooting
Claudio Veronezi Mendes
EMC / Veritas / Solaris
Londrina - Pr - Brazil
hummm
Marianne.. I think that I don't have disk space for catalog..
Actually my catalog have 35GB
I'll try to compact it up..
hold on
Claudio Veronezi Mendes
EMC / Veritas / Solaris
Londrina - Pr - Brazil
YES IT IS
Yes,,
the problem was the catalog had no space to disk
very crazy because none even the database was up just because of the calalog space.
THANKS for help
By the way,,, I really don't know why.. but I had to reboot the server
Claudio Veronezi Mendes
EMC / Veritas / Solaris
Londrina - Pr - Brazil
d/b shutdown was probably "intentional"
From T/N http://seer.entsupport.symantec.com/docs/286020.htm
"...
As of NetBackup 6.0 Maintenance Pack 3 (MP3) the Enterprise Media Manager (EMM) database will shut itself down if the file system approaches 100% capacity. This will protect the integrity of the EMM database in the event of a full file system. However, this behavior does not result in any log messages being generated in the NetBackup Administration console or error logs. It is necessary to search the admin legacy log files or unified log files for the nbemm originator id to determine if the database was shut down due to a full file system.
..."
If you do have space issues there are a lot of TechNotes in the Knowledgebase covering moving catalog to another location, clearing unified/legacy logs etc etc.
Regards Andy
"It's not too late to panic ..."
I wanted to ask if you
I wanted to ask if you provided sufficient space on the new server for catalogs.
A lot of SUN engineers install O/S with default partitions, which normally means too small /opt partition (NetBackup default install).
As Andy pointed out, shutdown of EMM database is protection against database corruption.
Rather fix your partitions than having to compress databases.
If your installation is not on a filesystem that can be expanded, rather do a NBU catalog backup, reinstall O/S with large enough partitions, put NBU back.
Would you like to reply?
Login or Register to post your comment.