09-25-2013 02:57 PM
Everything I've read says that Backup Exec 12.5 is not compatible with Windows Server 2008 R2 64-bit as a media server. However, I've run into an installation where 12.5 is installed and working fine on a 2008 R2 media server. It was previously backing up to tape but is now backing up to disk. It's even backing up a couple of other servers through the remote agent. It's running Backup Exec 12.5 with SP4 plus various hotfixes/updates.
I believe this may have been initially installed back when 2008 R2 was very new if that matters.
So, what is the issue with 12.5 running on 2008 R2 media server exactly? Will it just not install? Are there functional issues? If this is installed and seems to be working, should I leave it?
Thanks
Solved! Go to Solution.
09-25-2013 06:41 PM
BE 12.5 does not support Windows 2008 R2 as a media server. This means that this configuration has not been tested. If it works, you are lucky. However, you can never be sure when this configuration will fail. In the worse case scenario, you might find that you would be unable to recover your server from backups taken with this untested configuration. Furthermore, you cannot log a support case with Symantec when you use an unsupported configuration.
09-25-2013 03:10 PM
Hello, Actually on further review you are correct! installed on the media server it is not supported. http://www.symantec.com/docs/TECH62301
EDIT based on the release of Hotfix 331998 see this document for more information on support http://www.symantec.com/docs/TECH75697
09-25-2013 03:23 PM
I recommend upgrading to 2010 R3. From Backup exec 12.5 you can do a Direct upgrade to 2010R3 http://www.symantec.com/docs/TECH159557
09-25-2013 06:41 PM
BE 12.5 does not support Windows 2008 R2 as a media server. This means that this configuration has not been tested. If it works, you are lucky. However, you can never be sure when this configuration will fail. In the worse case scenario, you might find that you would be unable to recover your server from backups taken with this untested configuration. Furthermore, you cannot log a support case with Symantec when you use an unsupported configuration.