NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

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

3rd PARTY: When attempting to restore an Exchange 2003 public folder on a server with the Recovery Storage Group enabled, the restore fails with a NetBackup Status Code 1, partially successful.

OS: Exchange 2003 Hardware:
TECH39133 | 2013-10-23
Technical Solutions | CMS-XML

3rd PARTY: Attempts to back up Exchange 2003 servers using the NetBackup Exchange Database Extension fail with error message "ERR - beds_ese_access::v_read() fs_readobj() Failed! (0xfffffe7a:0xa000fe7a (2684419706)".

OS: Windows servers running Exchange 2003 Hardware:
TECH42994 | 2013-10-23
Technical Solutions | 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 | 2013-10-26
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

GENERAL ERROR: NetBackup Exchange backups of Exchange 2000/2003 exit with Status Code 12. The <install_path>\netbackup\logs\bpbkar log shows errors that would indicate the Exchange services are not running.

Further review of the bpbkar log shows the Exchange 5.5 directives, and not the correct Exchange 2000/ 2003 directives were specified in the policy. Once the directives were correctly specified in the Backup Selection
TECH16593 | 2013-10-23
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

Unable to restore Exchange 2003 mailbox store to Recovery Storage Group - getting error "BEDS 0xe000fe30: A communications failure has occurred."

Unable to restore Exchange 2003 mailbox store to Recovery Storage Group - getting error "BEDS 0xe000fe30: A communications failure has occurred."
TECH66256 | 2013-10-24
Technical Solutions | CMS-XML

After upgrading to NetBackup 7.0.1 Exchange 2003 server backup fails with Status 24.

After upgrading to NetBackup 7.0.1 Exchange 2003 server backup fails with Status 24.
TECH146715 | 2013-10-24
Technical Solutions | CMS-XML

When using VERITAS NetBackup (tm) for Lotus Notes on Windows to backup Lotus Domino Servers, the backup may complete with an erroneous status 0 (successful) message, but the backup does not actually capture all the database information on Windows 2000/2003 platforms.

When using VERITAS NetBackup (tm) for Lotus Notes on Windows to backup Lotus Domino Servers, the backup may complete with an erroneous status 0 (successful) message, but the backup does not actually capture all the database information on Windows 2000/ 2003 platforms.
TECH30907 | 2013-10-23
Technical Solutions | CMS-XML

STATUS CODE: 131 "ERROR: Client is not validated to use this server" occurs when attempting to restore an Exchange 2000 / 2003 database (involves cluster).

STATUS CODE : 131 ERROR : Client is not validated to use this server occurs when attempting to restore an Exchange 2000 / 2003 database (involves cluster).
TECH33334 | 2013-10-23
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

NetBackup status code: 2003

NetBackup status code : 2003
HOWTO91346 | 2013-10-02
How To | 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
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?