Netbackup 7.7 and Windows 2003 Compatibility
Moved to new post fromhttps://vox.veritas.com/t5/NetBackup/Netbackup-7-7-and-Windows-2003-Support/m-p/754626 It seems from your responses that nobody really knows the answer (to Relboy's question either). It's better just to say those three little words that are so hard for some to utter: "I don't know." Better still, don't post at all, and leave the preaching about Win2003 being a risk to an audience who wouldn't already know this. I suspect no-one in this forum is in a position to kill off business critical legacy systems as they wouldn't have the authority or budget control. Let's look at the question of operating a newer NetBackup server with older clients for legacy platforms another way. Is anyone out there already doing this ? E.g., have you tried running NetBackup Server 7.7.3 or 8.0 and, on the legacy Win2003 client, NB Client 7.6.1.2 ? How did this work out for you ? Did you experiment with different NB versions ? Which was the optimal combination ?
Netbackup Catalog Merging
Hi everybody, Can we merge a catalog with other, using same NetBackup version (8.0)? Our previous enviroment was a clustered Microsoft Windows 2012 R2 running as Master Servers and a couple of physical servers running as Media Servers... On our previous enviroment we lost our access to the GUI and some command line weren't work as well, so we had to rise another enviroment with a new Master Server (Windows 2012 R2, not clustered), connecting to the our Media Servers, but we were not abble to restore the catalog... So we're willing to know if there is a way to merge our old catalog with our new one.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,
Backups on appliance hangs post upgrade to 3.0
Post EOS for NBU appliance version 2.6, our appliances was upgraded to 3.0. However, post upgrade the backups are getting hung and is progressing at a very slow speed and we have to restart the appliances for backups to resume. But the issue re-occurs again after of couple of days.Please help.
Netbackup licenses - capacity
we're trying to confirm the amount in TB we should be licensed for under capacity model , we ran the nbdeployutil but there are several amounts there , which one should be the number to be licensed then Flagged Capacity Figures (TB) Master Server Confirmed (TB) or Capacity by Policy Type Policy Type Total (TB) Or Capacity Totals (TB) Platform Base (TB) Master Server Calculated ChargedExchange server Error 26
Hello, I have NBU 8.0. One of my policies which is a Exchange server policy is returning an error. the error is: ----------- ul 29, 2018 1:06:12 PM - end Parent Job; elapsed time 2:00:11 Jul 29, 2018 1:27:26 PM - Error bpbrm (pid=6420) from client server.com: ERR - Send bpfis state toMasterserver.com failed. status = -3 Jul 29, 2018 1:27:26 PM - Info bpfis (pid=8072) done. status: 0 Jul 29, 2018 1:27:26 PM - Error bpbrm (pid=6420) could not write filelist start to OUTSOCK Jul 29, 2018 1:27:26 PM - Error bpbrm (pid=6420) could not write EXIT STATUS to OUTSOCK Jul 29, 2018 1:27:26 PM - Info bpfis (pid=8072) done. status: 24: socket write failed client/server handshaking failed (26) ---------- The work I have done to solve it are: restarting the exchange server restarting the exchange replication service deleteing the shadow list on exchange Ihave done all the searches on the net and did everything need but unsuccessful. Before this i get 130 error but after restarting teh replication service anddeleting the shadows it became the mentioend error 26. Thanks in advance, Ashkan