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 lot1.5KViews0likes6Comments5230 hangs on POST after 3.1.2/8.1.2 upgrade
Hello, I am in the final stages of upgraded our NetBackup environment from version 7.7.3 to 8.1.2. I have successfully upgraded the master servers, and 4 out of 6 NetBackup appliances. However, I have a major issue with my last 2 appliances. They are both model 5230's, were both running the exact same 7.7.3 version with all patches, upgraded disk firmware, and upgraded to 8.1.2 today. I even got email notifications from the appliances that "Appliance is successfully upgraded to 3.1.2" message. Both rebooted 2-3 times (I wasn't watching the whole time), and now both of them hang after the Symantec splash screen with a blinking cursor. I have let them sit untouched for several hours, and nothing. I checked the BIOS and everything seems correct, but I have attached 2 pics for you to look at. I have scoured the Internet and Knowledgebase, but to no avail. I have not called Support yet because I thought I could find an answer or fix it myself, and also it is now after 10pm EST. Does anyone have any ideas on what's going on? It just seems like it might be the same fix because the issue is only happening on my 5230's. The upgrade was successful on our 5240's and 5330's. Only my 5230's are having this issue. Thank you!1.7KViews0likes3CommentsUPGRADE 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.4.4KViews1like12CommentsImports are failing on target domain post Appliance upgrade to 3.1
We have two sites Site A and Site B and are using Netbackup appliance 5230. The appliance at Site A replicates to B and vice versa. Post upgrade to 3.1, Site B is replicating the data to A - the replication job is getting successfully completed however the import job is failing at site A. I have tried reconfiguring the AIR between the two sites but the still persists. Please help.Solved1.5KViews0likes3CommentsAppliance 5230 alarm trap MSDP
Hello, At now, we Appears the next alarm in our monitoring system. Trap Appliance: Fallo Hardware en el Appliance. Descripcion: {"appliance_1_partition_1_errorstatus":"2","appliance_1_partition_1_status":"Optimal","appliance_1_partition_1_ackid":"ack:raidhead:partition:MSDP","appliance_1_partition_1_total":"13.1 TB","appliance_1_partition_1_state":"Warning","appliance_1_partition_1_used":"82 % *","appliance_1_partition_1_ack":"No","appliance_1_partition_1_partition":"MSDP"} I don't know if this alarm is about used space in the MSDP pool or if about the percentage of deduplication.Solved1.5KViews0likes2Comments