This article can also be found in the Premium Editorial Download "Storage magazine: Upgrade path bumpy for major backup app."
Download it now to read this article plus other related content.
After hearing similar stories, Hackland decided to perform his upgrade to MP2 in two steps. "We felt that was safer," he says. He upgraded the master server (which includes the catalog) in the first part of the week. "That's the one thing that worried me because I'd heard about issues with the catalog," he says. However, he notes, the firm's catalog isn't particularly big (approximately 100MB). "If there were going to be major problems, I thought it was going to be at that stage."
Not so, but there were other surprises. During the upgrade process, users must disable all their policies, perform the upgrade and then re-enable the policies. The Renault F1 Team discovered a problem when it came to reactivating its policies. A script that should have reactivated all the policies didn't work, so an admin had to reactivate all the policies manually. It ended up taking almost a day to upgrade the master server, considerably longer than the company had expected.
Engineers then performed three test backups and three test restores, which all worked fine. "Off they went home, happy as Larry," says Hackland. But when they returned to work the following day, they discovered that none of the scheduled backups had run. "I am still not entirely clear what the issue was," says Hackland. Symantec told him it was due to a "storage unit problem," which is a part of Veritas NetBackup. He says Symantec engineers corrected the issue that day by stopping and
"That was a little nerve-wracking, coming in the next morning and getting the report that none of the backups had run," he says. "The rest of the upgrade that week was fine ... It took an age to import the media database, but there were no other issues on that day."
This was first published in September 2006