NetBackup 7.6.0.2 (NetBackup 7.6 Maintenance Release 2) is now available!
(Crossposted from the Netting Out NetBackup blog) I’m extremely happy to announce that NetBackup 7.6.0.2 is now Generally Available! NetBackup 7.6.0.2 is our first maintenance release for the NetBackup 7.6 line ("7.6.0.1" was our "7.6 GA" release). This release contains fixes to 568 issues including resolutions for most commonly downloaded EEBs, customer escalations, and critical internally found defects. 7.6.0.2 also provides several critical security fixes and many high-demand proliferations to our customers. The significant content of this release is: Almost 200 customer-related defect fixes, including 12 issues highlighted in the 7.6 Late Breaking News Security fixes - most notably, removal/update of all components making use of an OpenSSL version potentially affected by "Heartbleed" Parity with 7.5.0.7 - if you were still waiting for a 7.5.0.7 fix to make it into the 7.6 line, here's your update! Proliferations: Oracle 12c Hyper-V 2012 R2 w/File level GRT VDDK 5.5 (I understand that some of you are interested in this one!) FT Media Server SLES 11 SP3 BMR Proliferations (Solaris 11.1, Suse 11 SP2/SP3, Windows 2012/8, RHEL6 XEN) Features Amazon Cloud Non-US Regions Support (7.5 line parity) To download 7.6.0.2, please visit the following page: NetBackup 7.6.0.2 Download Links http://symantec.com/docs/TECH214999 This is a MAINTENANCE Release for NetBackup (as opposed to a Release Update) - it can ONLY be applied on top of NetBackup 7.6 GA. (If you are currently running 7.0, 7.0.1, 7.1, 7.1.0.x, 7.5 OR 7.5.0.x, you will need to upgrade to 7.6 GA before you can apply 7.6.0.2.) To check to see if your particular Etrack is resolved in NetBackup 7.6.0.2, please refer to these Release Notes and our updated EEB guide: NetBackup 7.6.0.2 Release Notes http://symantec.com/docs/DOC6840 Symantec NetBackup 7.6 Emergency Engineering Binary Guide http://symantec.com/docs/DOC6085 The NetBackup 7.6 Late Breaking News has also been updated to reflect newly released fixes in 7.6.0.2 for some of our highest visibility issues: NetBackup 7.6 Late Breaking News http://symantec.com/docs/TECH199999 Bookmark the NetBackup Product Landing Page to have these links and many more useful links handy: http://go.symantec.com/nb --
Media host override for SAP restores on Data Domain storage server
Hi, We are required to run a very large restore (~12TB) of a SAP database. The backup image is stored on a Data Doamin storage server. We would like to force the restore to use a specific media server that is not the server used for the oirignal backup. The storage server has 6 DD Boost enabled media servers accessing it for both backups and duplications between data centers. Each time we initiate the restore a different media server is used. We have used the "media host override" settings but these do not seem to be honored for OST storgae servers according to this artilce - http://www.symantec.com/connect/forums/how-use-media-host-override Has anyone else experinced this problem?
NetBackup 7.6.0.4 (NetBackup 7.6 Maintenance Release 4) is now available!
(crossposted from the Netting Out NetBackup blog) I’m extremely happy to announce that NetBackup 7.6.0.4 is now Generally Available! NetBackup 7.6.0.4 is our latest maintenance release for the NetBackup 7.6 line. This release contains fixes to 262 issues (bringing our total to over 1100!) including resolutions for most commonly downloaded EEBs, customer escalations, and critical internally found defects. 7.6.0.4 also provides several critical security fixes and many high-demand proliferations to our customers. The significant content of this release is: Over 120 customer-related defect fixes, including nine 7.6.0.3 issues highlighted in the 7.6 Late Breaking News Proliferations: MSC - W2012 MSCS EV 11 BMR AF Disk Support Features: Increasing FT Pipes for FT Media Server Java UI password encryption JRE update (7u55) Tomcat update (7.0.54) Tomcat vCenter Plugin 6.0.41 changed due to display issues in OpsCenter addresses vulnerabilities discovered in 7.0.33 fileupload 1.3.1 To download 7.6.0.4, please visit the following page: NetBackup 7.6.0.4 Download Links http://symantec.com/docs/TECH223695 This is a MAINTENANCE Release for NetBackup (as opposed to a Release Update) - it can be applied on top of NetBackup 7.6 GA or any 7.6.0.x. (If you are currently running 7.0, 7.0.1, 7.1, 7.1.0.x, 7.5 OR 7.5.0.x, you will need to upgrade to 7.6 GA before you can apply 7.6.0.4.) To check to see if your particular Etrack is resolved in NetBackup 7.6.0.4, please refer to these Release Notes and our updated EEB guide: NetBackup 7.6.0.4 Release Notes http://symantec.com/docs/DOC7450 Symantec NetBackup 7.6 Emergency Engineering Binary Guide http://symantec.com/docs/DOC6085 The NetBackup 7.6 Late Breaking News has also been updated to reflect newly released fixes in 7.6.0.4 for some of our highest visibility issues: NetBackup 7.6 Late Breaking News http://symantec.com/docs/TECH199999 Bookmark the NetBackup Product Landing Page to have these links and many more useful links handy: http://go.symantec.com/nb bit.ly/76LBN | APPLBN | 75LBNFailed to backup in query mode when one of your Vcenter is down
Hi everyone, First, i'm sorry for my English :) With my team, we found a problem with the query mode when one of your Vcenter is not accessible in 7.6.0.3 The QUERY request will try to connect to all vcenter by default to check his request. At this time, if one of Vcenter added in credential is not accessible, the query will fail with status 4234 (VMware server login failure) even if the Vcenter whereby the QUERY must go is UP. Of course you can delete in credential the Vcenter who are down. But a option is more effective i think in Vmware policy. In this policy, go to Vmware Tab --> Advanced --> Vmware server list Then add the Vcenter who must be used by the QUERY. With this action, the QUERY request will inspect only this vcenter and not all Vcenter added in credential. More information about Netabckup infra : NBU Verison :7.6.0.3 Master/MDSP : Windows 2008 R2 SP1 Standard. I'm not sure if this action is a bug or not but i think is dangerous to check all vcenter when just one is needed. Previously, in 7.5.x, the job parent was in partially successful and not in failed. Regards, Johan
