vCenter 7.0 and NetBackup 8.1(Appliance version 3.1) incompatibility Issue. Backup Fails!
Hello, First of all, I'm not familiar with NetBackup. I just noticed that all VMware VM backups fail after I upgraded vCenter from 6.7 to 7.0. NetBackup 8.1 console> Media and Device Management> Credentials> Virtual Machine Server, the login to new vCenter fails, which I think why all VM backup fails. NetBackup Core Support confirmed that this is incompatiblity issue and I have to upgrade my Appliance and the other media server and Netbackup to upper version. Can anyone layout the steps and links how I can perform this upgrade? I searched knowledge bases but Appliance white papers talk about only appliance, Netbackup talks about only netbackup upgreade. Much Appreciated in advance.
NetBackup 5230 Appliance Upgrade
Hello all I have a NetBackup Appliance 5230 3.0 with NBU 8.0 and I will do the upgrade to 3.1; but is my first time working with this appliance, so I need a manual or the step by step for this activity. I now reading the links: https://www.veritas.com/support/en_US/article.100041985 [How to upgrade to NetBackup Appliance Release 3.1.1] https://www.veritas.com/content/support/en_US/doc/113205077-137337289-0/v116048700-137337289 [Veritas NetBackup Appliance Upgrade Guide] But yet is confussing for me the process. Anyone that can help me, please? Thanks a lotUPGRADE NOTE: 3.0 -> 3.1 5230 media server
Just an FYI - I upgraded my non-prod media server this morning, and upon the final reboot, the system came up but *none* of the media mgmt services started: NB Processes ------------ root 98265 1 0 12:58 ? 00:00:00 /usr/openv/netbackup/bin/private/nbatd -c /usr/openv/var/global/vxss/eab/data root 98433 1 0 12:58 ? 00:00:00 /usr/openv/netbackup/bin/vnetd -proxy inbound_proxy -number 0 root 98434 1 0 12:58 ? 00:00:00 /usr/openv/netbackup/bin/vnetd -proxy outbound_proxy -number 0 root 98435 1 0 12:58 ? 00:00:00 /usr/openv/netbackup/bin/vnetd -proxy http_tunnel -number 0 root 98552 1 0 12:58 ? 00:00:00 /usr/openv/netbackup/bin/vnetd -standalone root 98578 1 0 12:58 ? 00:00:00 /usr/openv/netbackup/bin/bpcd -standalone root 98683 1 0 12:58 ? 00:00:00 /usr/openv/netbackup/bin/nbdisco root 98979 1 0 12:58 ? 00:00:00 /usr/openv/pdde/pdcr/bin/spad root 99237 1 14 12:58 ? 00:04:50 /usr/openv/pdde/pdcr/bin/spoold MM Processes ------------ Shared Veritas Processes ------------------------- root 64397 1 0 12:56 ? 00:00:00 /opt/VRTSpbx/bin/pbx_exchange I ran "netbackup start" from the init dir and everything came up then... but not on reboot. Just an FYI.
Netbackup Appliance 5240 upgrade 3.0 to 3.1
Goodmorning 2 ya all I updated to version 3.1 and works fine.. but we encounter some problem regarding the update. I would like to tell about my experience about this here. Short version: Error: "Wont reboot" Solution: manual reboot OK so I've uploaded the 3.1 one binary (md5 checked it before). This through the shell (ssh) with the sysadmin account. We have two boxes.. I did this on both at same time (should take one at the time). I bpstop the master server but should do that then the script didnt find my master and stopped. So manually stopped the SLP exclude the date for the actual time in the schedule, wont have any interference on our 5240:s. (here Vertias should develeoped some script to stop enough items on master so that upgrade of deduplication nodes could be done.) Started the update install <file> enter and prechecked went good, the guidehttps://www.veritas.com/support/en_US/article.000116014 tells that there will be severeal reboots but (actually three). OK so after waiting for 2.5 hours.. we waited for 1 hour more.. Now something was wrong. No ping to the boxes. We could access them through the mgm, Mangement(so check this before the update) We had recived the mail from the appliance that the update went successfull We contact the Veritas support and concluded that reboot manually. OK now we had checked that the box was in some idle status. And this what we did to get it to work: Go to mgm (mangement) and chose reset on the power so they rebooted Let it boot and let it hang, wait 15minutes then Go to mgm and chose reset on the power reboot Done, verify it on NBU master and see that you have the boxes there ? Other that have same problem, did it requier 2 reboots ? Only 5240 have seen simliar to the 5230. ? Some technical info regarding this. Regards Pontus Ankarbåge