I left precise instructions, but they still managed to blow up the Netbackup catalog.
They were importing catalog images into a remote DR environment. It didn't go as planned, and it corrupted the NBDB instance of the ASA database. The image of someone slamming a square peg into a round hole with a hammer until it went through came into my head but I confidently went about my business and tried my best it get the system back online.
First of all, this is EXACTLY why I take a catalog backup of every Netbackup server in the environment. Second of all, I'm still surprised about the lack of documentation and lack of internal knowledge of Symantec support folks on how the new Netbackup Catalog introduced in 6.0 works.
I'm also surprised that they still haven't figured out Disaster Recovery. No, I don't mean how to recover the catalog in the event of a catastrophic loss like we suffered, but the fact of how we were using a home grown, and dangerous, script to import catalog images at our DR site instead of an official application extension. In this day and age, you would think that Netbackup would be able to syncronize certain clients or policies across multiple master servers for seamless recovery.
One can only hope.
Subscribe to:
Post Comments (Atom)
1 comment:
Hi, I work in the product management group at Symantec and I totally agree. I think there are a number of things in our future plans that might match up with your requirements. Drop me an email and we can chat more about it.
Post a Comment