NetBackup 7.5.0.6 (NetBackup 7.5 Maintenance Release 6) is now available!
(This is a crosspost from the Netting Out NetBackup blog) I'm very pleased to announce that the next Maintenance Release for NetBackup 7.5 is now available! NetBackup 7.5.0.6 is the sixth maintenance release for NetBackup 7.5. It is a cumulative release containing fixes and content from 7.5.0.1 through 7.5.0.5. In addition, this release contains almost 600 additional fixes (bringing the total fixes in 7.5.0.6 to over 1700!) including the most commonly downloaded EEBs, several customer escalations, and internal engineering defects. NetBackup 7.5.0.6 includes the following proliferations and enhancements: YES, Windows Server 2012/8 is now supported! db2 10.1 (snapshot support; streaming support was added in 7.5.0.5) Exchange 2013 Hyper-V 2012 SharePoint 2013 SAP HANA client support - see this blog post for more information To download 7.5.0.5, please visit the following page: NetBackup 7.5.0.6 Download Links http://symantec.com/docs/TECH204644 (link is fixed - sorry about that!) This is a MAINTENANCE Release for NetBackup (as opposed to a Release Update) - it can ONLY be applied on top of NetBackup 7.5. (If you are currently running 7.0, 7.0.1, 7.1, or 7.1.0.x, you will need to upgrade to 7.5 before you can apply 7.5.0.6.) Please note that maintenance releases are CUMULATIVE - that means that 7.5.0.6 contains all product fixes included in 7.5.0.1, 7.5.0.2, 7.5.0.3, 7.5.0.4 AND 7.5.0.5. If you are currently running NetBackup 7.5, you may apply the 7.5.0.6 maintenanace release without installing 7.5.0.1, 7.5.0.3, 7.5.0.4 or 7.5.0.5. In fact, if you are still running NetBackup 7.5, we would HIGHLY encourage applying 7.5.0.6! To check to see if your particular Etrack is resolved in NetBackup 7.5.0.6, please refer to these Release Notes: NetBackup 7.5.0.6 Release Notes http://symantec.com/docs/DOC6396 The NetBackup 7.5 Late Breaking News has also been updated to reflect newly released fixes in 7.5.0.6 for some of our highest visibility issues: NetBackup 7.5 Late Breaking News http://symantec.com/docs/TECH178334 --3.9KViews5likes27CommentsExchange Backup Failing 'file read failed(13)'
Our Netbackup 7.5.0.5Exchange backups have started failing with 'file read failed(13)' errors. Both servers (Exchange and Netbackup) are running on Server 2008 R2. The mailstores (database & logs)are residing ona Netapp FAS2040 with SnapDrive managing snapshots which are created frequently without error. The Netbackup policy itself is set to perform snapshot backups using VSS Provider Type 1 (System), without a DAG database source, has been backing up without any problems until some Windows updates including SP3 for Exchange 2010 were installed. The job fails as follows: 28/11/2014 10:32:33 - Info nbjm(pid=5940) starting backup job (jobid=186119) for client exchange, policy EXCHANGE, schedule Full_Disc 28/11/2014 10:32:33 - estimated 0 Kbytes needed 28/11/2014 10:32:33 - Info nbjm(pid=5940) started backup (backupid=exchange_1417170753) job for client exchange, policy EXCHANGE, schedule Full_Disc on storage unit NexsanDSU 28/11/2014 10:32:34 - started process bpbrm (484288) 28/11/2014 10:32:40 - Info bpbrm(pid=484288) exchange is the host to backup data from 28/11/2014 10:32:40 - Info bpbrm(pid=484288) reading file list from client 28/11/2014 10:32:40 - connecting 28/11/2014 10:32:43 - Info bpbrm(pid=484288) starting bpbkar32 on client 28/11/2014 10:32:43 - connected; connect time: 00:00:03 28/11/2014 10:33:27 - Info bpbkar32(pid=11548) Backup started 28/11/2014 10:33:27 - Info bptm(pid=484816) start 28/11/2014 10:33:28 - Info bptm(pid=484816) using 262144 data buffer size 28/11/2014 10:33:28 - Info bptm(pid=484816) setting receive network buffer to 1049600 bytes 28/11/2014 10:33:28 - Info bptm(pid=484816) using 30 data buffers 28/11/2014 10:33:29 - Info bptm(pid=484816) start backup 28/11/2014 10:33:30 - Info bptm(pid=484816) backup child process is pid 482596.479660 28/11/2014 10:33:30 - Info bptm(pid=482596) start 28/11/2014 10:33:30 - begin writing 28/11/2014 11:07:53 - Error bpbrm(pid=484288) from client exchange: ERR - Terminating backup. 28/11/2014 11:07:53 - Error bpbrm(pid=484288) from client exchange: ERR - failure reading file: Microsoft Information Store:\1GB Limit Mailbox Database\Logs_1417170539 (BEDS 0x0: ) 28/11/2014 11:08:03 - Error bpbrm(pid=484288) could not send server status message 28/11/2014 11:08:04 - Error bpbrm(pid=484288) cannot send mail to... 28/11/2014 11:08:05 - Info bpbkar32(pid=11548) done. status: 13: file read failed 28/11/2014 11:08:05 - end writing; write time: 00:34:35 file read failed(13) I have checked the VSS Writers on Exchange and all are showing as stable with no errors. The Event Viewer on Exchange shows the following events just before the Netbackupjob fails: Log Name: Application Source: MSExchangeIS Date: 28/11/2014 11:06:35 Event ID: 9606 Task Category: Exchange VSS Writer Level: Information Keywords: Classic User: N/A Computer: exchange Description: Exchange VSS Writer (instance 8315289c-83fc-4e18-95c6-2f9e76f0f821) has prepared for backup successfully. Log Name: Application Source: SnapManager for Exchange Date: 28/11/2014 11:06:36 Event ID: 200 Task Category: Backup Level: Information Keywords: Classic User: N/A Computer: exchange Description: SnapManager VSS asynchronous DoSnapshotSet operation started. Log Name: Application Source: ESE Date: 28/11/2014 11:06:39 Event ID: 2007 Task Category: ShadowCopy Level: Error Keywords: Classic User: N/A Computer: exchange Description: Information Store (6236) Shadow copy instance 3 aborted. Log Name: Application Source: MSExchangeIS Date: 28/11/2014 11:06:39 Event ID: 9609 Task Category: Exchange VSS Writer Level: Error Keywords: Classic User: N/A Computer: exchange Description: Exchange VSS Writer (instance 8315289c-83fc-4e18-95c6-2f9e76f0f821:3) failed with error code -2403 when preparing for Snapshot. I appreciate this is probably an Exchange issue rather than a Netbackup one, but if anyone has an ideas as to why it is failing I'd be grateful for some help. I have attached some log files, let me know if there is any other information that may help. Thanks1.6KViews0likes3CommentsAdamm Mover Error After Upgrading to SP4 on Backup Exec 2012
Since upgrading to sp4 on Backup Exec 2012 I am seeing this error on a couple servers pretty frequently. Before sp4 I was not seeing this error. [6484] 05/13/14 15:45:01 Adamm Mover Error: DeviceIo: ndmpSendRequest->connection error to 192.168.3.70:10000, 100542.4KViews0likes8CommentsNetbackup 7.7.3 Java patch
Hi; I am looking for any information about the Java Version packaged within version 7.7.3 Our security team has identified a Java Vulnerability during our PCI audits. The issue with the packaged version of Java with in Netbackup 7.7.3 on our Linux servers. Bad versions are : Oracle Java SE 1.7.0_221 / 1.8.0_211 / 1.11.0_3 / 1.12.0_1 Multiple Vulnerabilities (Apr 2019 CPU) (Unix) The Fixed version I am looking for is one : 1.7.0_221 / 1.8.0_211 / 1.11.0_3 / 1.12.0_1 Can you tell me if Version 8.0 or any of the newer ones has the fixed versions? If there is no EEB or way to update Java I will have to Upgrage from 7.7.3 ASAP. Or Is there a Hot Fix or EEB to update the Java Version in Netbackup 7.7.31.2KViews0likes1Comment0x80004005 - Unspecified error
good afternoon Installed Backup Exec 2012 revision 1798 Service Pack 4 (Windows 2008R2 + Update / SQL Server 2005 SP4 -9.0.5000) Through LiveUpdate patches installed 217,347. Randomly error 0x80004005 - Unspecified error, which results in the failure of backup. After reading the forum and the recommendations it all comes down to the article that I TECH53004 requirements fulfilled And installation of patches 201596, 203574, 205111. Service Pack 4 (Article: TECH215122) already includes all the necessary patches. Please help how to conquer this problem?Solved7.3KViews1like14Comments- 4.4KViews1like5Comments
when i login to symantec BE 2014 it will through error message
Hello guys, Am new in backup I got below error message and when i login to the Backup Exec it will through connection refused error message. in my customer 60 days once change the domain Administrator password and Administrator password. i have check with both the password.am unable to login Backup Exec 2014. and services are not running it's running in Windows 2012 r2... Error Message: could not connect to net.tcp://backup-server:/BEMService/Serverdata.the connection attempt lasted for a time span of 00:00:05:0056762.Tcp error code 10061:no connection could be made because the target machine actively refused it thanks......Solved4.2KViews0likes11CommentsUpgrading Multiple 5220 Appliances
I have the following upgrade scenario with NBU and 5220 appliances, and am wondering how much of this I can perform concurrently. Windows 2008R2 Master Server - recently upgraded to NBU 7611 - all OK 5220 Media Server 1 (72TB) - 2.5.3 5220 Media Server 2 (36TB) - 2.5.3 I am moving the appliances to 2611 and am wondering do I have to stop all activity on Master and both appliances and upgrade them consecutively or can I stop all activity and upgrade the two appliances at the same time ? They are both Media ONLY, and the Master is already at 7611 so there should be no version issues. Thanks, AJ.Solved1.9KViews1like8CommentsError while updating BE 2014 SP1 to SP2 BEDB version 0.00000
Hi I get this error in the log while i try to update our BE 2014 SP1 to SP2. After the error the rollback starts. Any fixes for this? Or what to do? V-225-266: ERROR: BEDB version 0.000000 does not qualify for schema upgrade and data migration. ***To search for information about this error, click hereSolved1.3KViews0likes3Comments