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 | 76LBNDeduplication 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-available
2.6.0.1 upgrade breaks CLISH if you have altered ssh port
If your company is like ours and has as a security model adopted using ssh on a different port than the default 22 then when you upgrade the CLISH is broken for various commands. I have not investigated all the commands but a couple of prominent ones are Monitor > Hardware ShowStatus and Hardware ShowComponents along with Support > KillRemoteCall. The resolution is to edit the /etc/ssh/ssh_config to change the port there to the port that sshd is listening on. If you have in the /etc/ssh/sshd_config Port 8222 then in the /etc/ssh/ssh_config you need to put in Port 8222. You need to make sure that the default Port 22 is commented out. No services need to be restarted. This is a change from 2.5.x where the CLISH just made internal calls. Now for certain calls it appears to issue an ssh remote command to the appliance itself and expects sshd to be listening. It is a good thing that the command did not hard code the script with port 22 but allowed the system to use the ssh_config values. There is an ETrack that has been created to address this issue and the issue that the ssh_config and sshd_config were overwritten on this upgrade and may be on subsequent upgrades.
