Advice for an upgrade from BEWS 12.5 to 2010 2003 R2 x64 to 2008 R2
Updated: 27 May 2010 | 7 comments
This issue has been solved. See solution.
Hi:
I'm looking for a little advice on my upgrade. I have a 2003 R2 x64 Backup Exec 12.5 Media server (all the latest BEWS patches). I'd like to upgrade it to 2008 R2 and also Backup Exec 2010. In which order should I do this? the OS first or BEWS or is it more complicated than that?
Thanks for any help you can provide.
John
Discussion Filed Under:
Comments
Hello, We need to upgrade BE
Hello,
We need to upgrade BE 12.5 to BE2010 1st and then the OS from 2003 to 2008 64-bit.
Hope this helps...
Its a best practice to have a "Support Contract" with Symantec...
Just to be clear, the upgrade
Just to be clear, the upgrade OS is going from 2003 R2 x64 to 2008 R2 not 2008 x64. Is this still the correct upgrade procedure (BEWS then OS).
Thank you for the help
...whatever you do, make sure
...whatever you do, make sure you have a copy of your Data and Catalogs folders. I have had 3 servers completely corrupt the DB during the 12 servers I have done so far.
It is going to save you a lot of time if you have to revert back.
If you find this is a solution, please mark it as such.
Hi, Has any of this helped
Hi,
Has any of this helped you at all?
Laters!
If you find this is a solution, please mark it as such.
Yes. I backed up my data and
Yes. I backed up my data and catalogs. I then stopped all the services and did the upgrade in 2 environments. It worked fine. Nothing lost. All selection lists in tact and the jobs were fine too. So the 1st phase is finished, the Backup Exec environments are now at 2010. The OS upgrade is next.
Thanks for your help
OK...can you then close this
OK...can you then close this off?
If you find this is a solution, please mark it as such.
What I would suggest (just in
What I would suggest (just in case) is shutdown teh BackuP Exec services (including the SQL instance holding the BEDB) and then copy the catalogs and data folders to a safe place before upgrading the Operating System. If there are likely to be any issues it is going to be because we install a slighly different binary somewhere on Windows 2008 R2 which is not installed currently - which would need an uninstall and re-install of Backup Exec to correct - but your catalogs and database are now converted for BE 2010 so should be easy to put back on if you do have to do this.
Would you like to reply?
Login or Register to post your comment.