09-05-2012 03:35 PM
FIRST QUESTION:
My company is running SP2 of Backup Exec. Has anyone had any problems upgrading to SP3? It's been out long enough now that I figured the bugs should have been found/worked out by now.
I called Symantec tech support, got transferred 5 times asking the same question - and nobody knew anything...
Due to some "ancient" servers we are still running - we can't upgrade to 2012 at this time - otherwise we would.
SECOND QUESTION
My current version of 2010 sp2 keeps saying that I have 36 servers needing an upgrade - and the directions to do so (Tools -> Install agents and Media servers -> etc). When I try from my BackupExec server however - it cannot find any servers except one - and when it tries to do the 9 updates on THAT server, it just fails. What am I missing?
- My backups to disk work just fine - and the duplicate to tape works just fine.... weird.
THANKS for any help anyone can throw my way.
Cory
Solved! Go to Solution.
09-09-2012 01:09 PM
Hi,
While there might be no known issues, there have been issues during upgrades. Check the forums where these are detailed.
From my side, I've had the BEDB being wiped out during the SQL Express upgrade as McAfee decided to block the installation. During the rollback of the upgrade, the contents of the BEDB were lost.
ISO images get corrupted; AVs causes issues etc, so it does happen.
Thanks!
09-05-2012 04:27 PM
09-05-2012 05:22 PM
Oops... stupid me - I DID mean BE2010 R3
Any problems with it? My boss is more paranoid than I am - are there any known conflicts?
2nd Question
When you say to do a silent install on a remote server - I assume it doesn't matter that it has the agent installed already, right? It will just update it? and STILL no reboot required?
THANKS
09-05-2012 05:29 PM
Hi
I DID mean BE2010 R3,
Fine if it is BE 2010 R3 then no service pack 3 released yet ,we have service pack 2 for it.
When you say to do a silent install on a remote server - I assume it doesn't matter that it has the agent installed already, right? It will just update it? and STILL no reboot required?
NO ,It won't matter even if remote agent is not installed ,if it is not installed it will install remote agent & yes reboot is not required. Also ensure you install only remote agent and not AOFO option as installing that option install the driver called vsp.sys and which requires a reboot & but it is not recommended to install AOFO on win2003 and above OS as we would be using VSS to perform open file backup
Hope that helps
Thanks
09-05-2012 06:09 PM
As the name BE 2012 R3 implies, this is a refresh of BE 2010 which is almost like a new release. You would need to reboot the servers after installing it. Doing a silent install does not remove this requirement. If you do not have the time to re-boot alll your server, you can do it in stages. BE 2012 R3 will work with older BE 2010 agents, but you should upgrade your remote agents as soon as possible.
After you have installed R3, run LU a couple of times to upgrade to SP2 and the hotfixes after that. After all the updates are done, you can then push out the remote agents.
09-05-2012 09:43 PM
pkh means 2010 R3 (not 2012 R3)
09-05-2012 10:15 PM
Thanks for the correction.
09-07-2012 10:29 AM
My last standing question is this:
Has anyone had ANY issues upgrading BE 2010 r2 to BE2010 R3? Our oldest server is running Windows 2000 server - which is why we can't upgrade to BE 2012. The rest of my servers are a mix of Server 2003 and 2008.
I am truthfully terrified of having to re-create my backup schedule - it's a nightmare.
Thanks for any advice
09-07-2012 10:37 AM
There are no known issues of upgrading R2 to R3, to be on a safer side before upgrading stop SQL
service and make a copy of DATA and CATALOGS folder.
09-09-2012 01:09 PM
Hi,
While there might be no known issues, there have been issues during upgrades. Check the forums where these are detailed.
From my side, I've had the BEDB being wiped out during the SQL Express upgrade as McAfee decided to block the installation. During the rollback of the upgrade, the contents of the BEDB were lost.
ISO images get corrupted; AVs causes issues etc, so it does happen.
Thanks!