What to look out for when upgrading to Backup Exec 2010...my experiences!
I am busy going through the process of upgrading our Backup Exec 12.5 servers (with 2 CASOs) to Backup Exec 2010, in order to take advantage of the new features introduced in the new software.
However, I have come across a number of issues and problems, and the article below will tell you what to look out for, and what to do prior to upgrading your environment.
1. Backups of your data
Having run through a number of upgrades from Backup Exec 12.5 to Backup Exec 2010, was caught out initially on the first failure...I hadn't made a backup of my Data and Catalogs olders. This was stupidly based on the first 3 successful upgrades I had done. When the upgrade failed, it had also erased all my data.
Before running through the actualy upgrade process, stop all your Backup Exec services, and copy your Data and Catalogs folders to a separate location. This is going to ensure that if you have any issues during the upgrade, you will be able to revert back to your original information.
2. Stop all antivirus activity
I suspected that McAfee Antivirus was causing issues on some of my failed upgrades. I hadn’t factored this into the equAtion, as it hadn’t caused issues before with the upgrades from Backup Exec 11D to Backup Exec 12.5. The only change between the 2 upgrade cycles, was that we had moved from EPO 3.5 to EPO 4.0.
My suggestion is to stop your antivirus services, and then set them to disabled during the upgrade process. Once this process has completed, you are then able to set your services to their original settings, and start up the services. Doing this will make sure that the AV is not blocking any sort of activity deemed virus-like (such as installing new *.dlls, accessing folders etc.).
3. Make sure your installation media works
There seems to be a couple of issues doing the rounds now with Backup Exec 2010 downloadable installation files. There are 2: a single 3GB ISO, and multiple 780MB ISOs which are combined using a batch file. Before proceeding with your installation, try a test installation on another server/VM, and make sure you are able to run right through the installation. This is going to save time (for those of you not having access to slow Internet links) if you have a corrupt file for some reason.
4. Make sure the applications you want to back up are on the SCL
There are a number of software products that are no longer on the Backup Exec 2010 SCL. Exchange 2000 comes to mind. Download the Backup Exec 2010 SCL, and make sure that your applications are supported. If not, it is going to mean either staying with your current version of Backup Exec, or upgrading your softwae.
You can get the Backup Exec 2010 SCL here...
5. Schedule proper downtime
There is nothing worse than starting an upgrade, and on completing it, finding out you cannot restart the server due to workload by users. Schedule proper downtime for the upgrade for Backup Exec 2010, as you will need to restart your media server.
As for upgrading the RAWS agents, I have yet to restart a remote server. However, considering this is from RAWS 12.5 to RAWS 2010, anything earlier will most likely need a restart, so factor that in too.
6. Get all the patches
With the new software out, you would want to have all the update patches currently available. This will allow you to patch what needs to be patched, and have a baseline from which to work going forward.
7. Remove your server from a CASO prior to the upgrade
I have seen some issues with the CASO in use. In my situation, I created a new VM with Backup Exec 2010 CASO installed, and then upgraded a client. However, moving from the old CASO (running 12.5) to this caused issues, and ended up with me hacking the old CASO’s entries out of the newly upgraded server, and then adding the server to the new CASO. Lots of wasted time!
My suggestion is to remove the server from the old CASO first before the upgrade. This will make sure all entries are removed from the registry, returning the server to a stand-alone solution again. Adding it to the new CASO server is easy enough.
The above is by no means an exhaustive list of what you should be doing, and looking at. You can use the same process when upgrading between Backup Exec versions, excluding the multi-step upgrade from Backup Exec 10d to Backup Exec 12.5 for example.
If you have any other ideas, post them at the bottom of this...it all helps!