We Have MSSQL 2005 - Should We Upgrade to NetBackup 8.0 or 7.7.3 ?
We Have MSSQL 2005 - Should We Upgrade to NetBackup 8.0 or 7.7.3 ? I'm preparing to upgrade our NetBackup servers as our current version (v7.6.1.2) is EOSL. However, I have a problem. We are still gradually migrating our databases from an MSSQL Server 2005 cluster to a new MSSQL 2014 cluster. This process will take months and the NetBackup upgrade cannot wait. I'm aware that MSSQLServer 2005 is not supported in NetBackup beyond v7.6.1.2. Worse still is it's running on Win2003SP2, which is, of course, also not supported. I am proposing to go ahead and upgrade our NetBackup servers to v8.0 in the meantime, and keep the NetBackup Client on our SQL Server 2005 cluster at v7.6.1.2. Alternatively, I could upgrade the NetBackup servers to v7.7.3 and keep the NetBackup Client on our SQL Server 2005 cluster at 7.6.1.2. So my questions are: 1. Would this work ? Would our existing database and transaction log backup policies still work? 2. If it would work, which NetBackup version would you recommend, v7.7.3 or v8.0 ? I'm leaning towards v8.0 myself and a Symantec / Veritas support engineer told me yesterday it is the generally more stable of the two. Please note that the fact that we still use Win2003 and MSSQL2005 is a matter which is largely beyond my control, so please don't post replies telling me about the risks this poses to our organisation - I already know and we're working on it. Tags:Windows 2003 End of Support, SQL Server, NetBackup 7.6, NetBackup 8.0,
Windows - Netback 7.0 Reboot issues
Currently have a server which is Windows Server 2003 running Netbackup 7.0. I have a robot with two drives - Dell PowerVault 132T. I have been having a problem readding the Robot to Netbackup, when i am running the scan it is only picking up the two drives. I have had the robot on the netbackup before but i had to readd the drives which i had accidently removed the robot as well. It is on a NDMP set up but i dont have the full info to manually add it in. The medium changer can be seen in Device Manger. and the device can be accessed through its webGUI. I know this is out of support officially but any help would be much appreciated?