NetBackup 7.6.1 / 2.6.1 - MSDP Conversion
After going through the 'pain' of MSDP conversion when moving appliances from 2.5.x to 2.6.0.x, whereby I saw conversion taking anywhere from 4hrs to 27hrs, I was surprised to see the conversion is required AGAIN when moving from NBU 7.6.0.3 to 7.6.1. I have only performed this upgrade in my test lab which has very little data in the MSDP pool, and is WIndows based NOT an appliance - but I am assuming this will also be the case when moving the appliances from 2.6.0.x to 2.6.1. Has anyone moved an appliance to 2.6.1 yet, and if so is the MSDP conversion a similar duration to that when moving from 2.5.x to 2.6.0.x ? As I mentioned my MSDP pool is tiny in the lab and conversion only took a minute or so. Thanks, AJ
NetBackup Appliances 2.6.1.2 is now available!
(crossposted from the Netting Out NetBackup blog) I’m extremely happy to announce that NetBackup Appliances 2.6.1.2 is now Generally Available! NetBackup Appliances 2.6.1.2 is the latest update for NetBackup 52xx and 5330 Applainces and the equivalent Appliance patch release to NetBackup 7.6.1.2. It can be applied in an upgrade to Appliances running ANY 2.5.x or 2.6.x.x version. This release includes all fixes included in the NetBackup 7.6.1.2 release, including resolutions for most commonly downloaded EEBs, customer escalations, and critical internally found defects. To download 2.6.1.2, please visit the following page: NetBackup Appliance 2.6.1.2 Release http://symantec.com/docs/TECH228624 More information on 2.6.1.2 can be found at the following locations: NetBackup Appliances 2.6.1.2 Release Notes http://symantec.com/docs/DOC8185 Complete Symantec NetBackup Appliance Documentation Set - 2.6.1.2 versions http://symantec.com/docs/DOC8194 The NetBackup Appliances Late Breaking News can be found here: NetBackup 5xxx appliance series Late Breaking News http://symantec.com/docs/TECH145136 Short link: http://bit.ly/APPLBN Bookmark the NetBackup Appliances Common Topics page to have these and many more useful links handy: http://go.symantec.com/nba bit.ly/761LBN | APPLBN | 76LBN
Deduplication Appliances 1.4.5 is now available!
(Crossposted from the Netting out NetBackup blog) I'm very pleased to announce that the next Release Updates for Deduplication Appliances is now available! NetBackup 5000/5020/5030 Deduplication Appliances 1.4.5 is the latest patch release and can be applied on top of 1.4.3.1 or 1.4.4. This cumulative release contains almost 900 fixes! It also includes the following new features: Optimized Deduplication from PDDO to MSDP Configurable Fibre Channel buffer size for replication Agent Proliferations 3rd Party Component Upgrades Unique Message ID Support More information on this release can be found at the following links: NetBackup Deduplication Appliance 1.4.5 Patch (for NetBackup 5000, 5020, and 5030) http://symantec.com/docs/TECH224577 NetBackup Deduplication Appliance version 1.4.5 Release Notes (for NetBackup 5000, 5020 and 5030) http://symantec.com/docs/DOC7661 Documentation for NetBackup 5000/5020/5030 Deduplication Appliance version 1.4.5 http://symantec.com/docs/DOC7662 The latest information on all NetBackup Appliances can be found in the Late Breaking News document and on our Appliances landing page - have you bookmarked them yet? NetBackup 5xxx appliance series Late Breaking News http://symantec.com/docs/TECH145136 Short link: http://bit.ly/APPLBN NetBackup Appliance Technical Support http://go.symantec.com/nba/ bit.ly/761LBN | APPLBN | 76LBNNetBackup Appliances 2.6.0.3 is now available!
(crossposted from the Netting out NetBackup blog) I’m extremely happy to announce that NetBackup Appliances 2.6.0.3 is now Generally Available! NetBackup 2.6.0.3 is the latest update for NetBackup 52xx Appliances and the equivalent Appliance patch release to NetBackup 7.6.0.3. It can be applied in an upgrade to Appliances running ANY 2.5.x or 2.6.0.x version. This release includes all 336 fixes included in the NetBackup 7.6.0.3 release, including resolutions for most commonly downloaded EEBs, customer escalations, and critical internally found defects. The 2.6.0.3 release also contains: Built-in VLAN support Active Directory CLISH configuration Web console usability enhancements To download 2.6.0.3, please visit the following page: NetBackup Appliance 2.6.0.3 Release http://symantec.com/docs/TECH217250 To check to see if your particular Etrack is resolved in NetBackup Appliances 2.6.0.3, please refer to these Release Notes: Symantec NetBackup 52xx Appliance Release Notes - Release 2.6.0.3 http://symantec.com/docs/DOC7458 The documentation pack for this release can be found here: Complete Symantec NetBackup 52xx Appliance Documentation Set - Release 2.6.0.2 http://symantec.com/docs/DOC7465 The NetBackup Appliances Late Breaking News can be found here: NetBackup 5xxx appliance series Late Breaking News http://symantec.com/docs/TECH145136 Bookmark the NetBackup Appliances Common Topics page to have these and many more useful links handy: http://go.symantec.com/nba Finally, more information on this release can be found by accessing the NetBackup 7.6.0.3 release announcement, which is also available here on Connect: http://www.symantec.com/connect/blogs/netbackup-7603-netbackup-76-maintenance-release-3-now-availableNetBackup 5200/5220 Appliances 2.5.1 is now available!
I'm very pleased to announce that the next Maintenance Release for NetBackup 7.5 and Release Update for NetBackup 52x0 Appliances is now available! NetBackup 7.5.0.4 is the fourth maintenance release for NetBackup 7.5. It is a cumulative release containing fixes and content from 7.5.0.1 through 7.5.0.3. In addition, this release contains an additional 315 fixes (bringing the total fixes in 7.5.0.4 to over 700!) including the most commonly downloaded EEBs, several customer escalations, and internal engineering defects. The simultaneously released NetBackup 5200/5220 Appliances 2.5.1 Release Update is the equivalent Appliance patch release to NetBackup 7.5.0.4. The significant content of NetBackup 7.5.0.4 is: No new features in 7.5.0.4. However, some features that were delivered in previous maintenance releases are included: Solaris 11 master server, Bare Metal Restore server and OpsCenter Managed Server support – delivered in 7.5.0.3 NetBackup for VMware on SLES – delivered in 7.5.0.2 PureDisk seeding utility – delivered in 7.5.0.2 Client Direct Whole Image Mode – delivered in 7.1.0.4 Multi-process nbostpxy for Client Dedupe – delivered in 7.1.0.4 Fixes included in EVERY publicly available 7.5.0.3 hotfix are included in 7.5.0.4 Other miscellaneous fixes across NetBackup which were not publicly released Additional content applicable to Appliances 2.5.1 is: Improved agent for proactive support Support for OST 3rd party plug-ins Information about 2.5.1 is available here: NetBackup 5200/5220 2.5.1 Update http://symantec.com/docs/TECH197011 The 2.5.1 Update can only be applied to an Appliance already running at version 2.5. To check to see if your particular Etrack is resolved in 2.5.1 (NetBackup 7.5.0.4), please refer to both sets of Release Notes: NetBackup 7.5.0.4 Release Notes http://symantec.com/docs/DOC5514 NetBackup Appliance 2.5.1 Release Notes for NetBackup 52xx http://symantec.com/docs/DOC5797Netbackup 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ågeUPGRADE 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.Spurious Alerts following Appliance Upgrade to 2.7.2
I have recently upgraded a number of 5230 Appliances to 2.7.2, and whilst all appear to be functioning as expected we are getting numerous alerts relating to disk failures which are 'false'. I am wondering whether there is a BIOS issue here (mismatch) ? Two questions: 1. How can I display the current BIOS level without rebooting the appliance ? 2. Is there a required BIOS update to be applied 'outside' of the regular software/firmware package used for 2.7.2 ? Thanks, AJ.