NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

NetBackup status code: 2003

NetBackup status code : 2003
HOWTO104831 | 2014-11-20
How To | CMS-XML

How to disable circular logging in Microsoft Exchange 2003/2007/2010 to avoid a differential or incremental backup failure with error "snapshot preparation failed, status 130".

Microsoft Exchange 2003 . Microsoft Exchange 2007. Microsoft Exchange 2010.
TECH192178 | 2014-07-22
Technical Solutions | CMS-XML

BUG REPORT: Exchange clusters: 2003, 2007 (CCR or SCC) or 2010 DAG Backups fail Status 69, Status 1512 or Status 2

A recent issue has been discovered with NetBackup 7.5 when hosts files are used to resolve the Exchange clusters ( 2003 , 2007 (CCR or SCC) or 2010 DAG).
TECH187937 | 2013-11-11
Technical Solutions | CMS-XML

GENERAL ERROR: After disabling Removable Storage Management (RSM) services on Windows 2000 and 2003, the system event viewer log reports EVT ID: 10005. NtmsSvc DCOM errors.

: After disabling removable storage management (RSM) services on Windows 2000 and 2003 , the system event viewer log reports Et ID: 10005. NtmsSvc DCOM errors.
TECH16248 | 2013-10-24
Technical Solutions | CMS-XML

Backup of Microsoft Exchange 2000 /2003 file system fails with exit status 13. Job Detailed Status shows "Error bpbrm(pid=<processid>) socket read failed".

M drive is the Exchange Installable File System (IFS) drive, (which is drive M by default on Exchange 2000/ 2003 servers). Microsoft warns not to include the M drive in regular file level backup (see related articles).
TECH30887 | 2013-10-24
Technical Solutions | CMS-XML

Full backups of Microsoft Exchange 2003 Public Folders fail with status 71 - ERR - bedsExchangePubInit() Failed! 0xe0008488:Access is denied

We double-click on the Exchange 2003 client to bring up the Client Properties dialog. We expand the Windows Client settings and click on Exchange. Under Mailbox for message level backup and restore, we will enter the name of the service account mailbox.
TECH181024 | 2013-10-26
Technical Solutions | CMS-XML

Non Snapshot backups of Exchange 2003 fail with a "status 69" after upgrading to 7.1 from 7.0.1, unless the NetBackup Client and NetBackup Legacy services are running as "Administrator"

Windows 2003 Exchange 2003 NetBackup 7.1 GA
TECH170069 | 2013-10-09
Technical Solutions | CMS-XML

Exchange 2003 GRT backup to MSDP fails with Status 20 invalid command parameter (NetBackup storage unit NOT compatible for Granular enabled backup)

Microsoft Exchange 2003 GRT Backups sent to Media Server Deduplication Pool (MSDP) fails with invalid command parameter (20)
TECH197772 | 2013-08-20
Technical Solutions | CMS-XML

Exchange 2003 database restore to an alternate exchange server is failing with error "BEDS 0xe000fe16: An operation was attempted on an item of the wrong type"

Exchange 2003 database restore to an alternate exchange server is failing with error "BEDS 0xe000fe16: An operation was attempted on an item of the wrong type"
TECH145744 | 2012-02-07
Technical Solutions | CMS-XML

WIN 2003 R2 Server failing backup with status 24/54/58

WIN 2003 R2 Server failing backup with status 24/54/58
TECH169380 | 2011-09-12
Technical Solutions | CMS-XML

BUG REPORT: Windows 2000, 2003 and Windows XP clients complete with Status 1 because it is failing to backup Event Logs.

BUG REPORT: Windows 2000, 2003 and Windows XP clients complete with Status 1 because it is failing to backup Event Logs.
TECH71103 | 2010-01-13
Technical Solutions | CMS-XML

When circular logging is enabled for Exchange 2000/2003, VERITAS NetBackup (tm) incremental backups report Status 0 (successful); however, the transaction logs are not backed up.

An Exchange 2000/ 2003 incremental or differential backup is not available for restore when circular logging is enabled on the Exchange server. TechNotes that explain this issue already exist in the Knowledge Base. This issue is being released as a Software Alert to address areas of potential confusion regarding the exit status being returned for incremental backup jobs.
TECH45002 | 2005-01-22
Technical Solutions | CMS-XML

VSphere 5.0 backup of Windows 2003 client fails with STATUS 130 and "ERROR :1735:scan operation failed:" using NetBackup 52xx appliance as VMware backup host

Master, NetBackup 7.5.0.4 Media server acting as VMware backup host, running NetBackup 7.5.0.4 or NetBackup 52xx appliance 2.5.1 Client , Windows 2003 or 2003 R2, vSphere 5.0
TECH205606 | 2013-09-12
Technical Solutions | CMS-XML

BMR error on 2003 Cluster | Symantec Connect

The document linked is for Linux. The clients I see this on are either Windows 2003 or 2008
Connect Forums | HTML

NetBackUp 7.0 on Server 2003 156 error | Symantec Connect

NetBackUp 7.0 on Server 2003 156 error Operating Systems: Discussion Filed Under: Backup and Recovery , NetBackup , Windows Server ( 2003 /2008)
Connect Forums | HTML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?