Forum Discussion
As you assumed, the migration will work most of the time. To really say if there will be any befinits can you share what type of data/servers you are backing up and what device(s) you are backing up to?
Also, if you have the hardware, you can alway keep the 2008 server up while you are working on the migration to make sure that everything goes smoothly.
- DSAI7 years agoLevel 4
In terms of data/servers that we backup and devices that we are backing up to. We have physical DCs running 2K8 R2 using the AD agent, Hyper-v 2008 R2 VMs comprising of file servers, application servers (flat files), exchange 2010 running on 2K8 R2 using the exchange agent, MS SQL servers (flat files), Sharepoint Servers (flat files). We have a few Server 2012 VMs, We have also have a server 2012 physical server.
We have a dual drive LTO6 tape library and SAN storage. We dont have enough disk space to really perform Dedup. We typicaly are doing fulls and diffs and we are also doing disk-to-disk-tape backups.
If there are no benefits to BackupExec (performance, features etc). I would probably stay on the same platform.
- Stephen_Kent7 years agoLevel 4
Sorry for the delay.
So I wouldn't say it's really a necessity that you upgrade the OS. There are a few restirctions with Backup Exec server OS that you can find in the Software Compatibility List, but I don't think any affect you in your current environment. A couple things to note. Again not that it should matter for you now, but to keep in mind going forward....
- To back up Microsoft Exchange Server 2016, you must install Backup Exec on a Microsoft Windows 2012 64-bit server or newer
- To perform a GRT-enabled backup of an Active Directory Application Server on Windows 2012 R2 or later, the Backup Exec server must be the same version or a later version of Microsoft Windows.
- DSAI7 years agoLevel 4
Hi Stephen,
What would you suggest I do?
Related Content
- 5 months ago