NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

Receive error when restoring MSSQL 2000 database "Error in GetConfiguration: 0x80770003"

Uninstalling and reinstalling Netbackup client binaries (up to 6.5.5) did not make any difference. Uninstalling the MSSQL 2000 Security Update kb960083 resolved the issue, thus enabling both MSSQL backups and restores to work again.
TECH146444 | 2013-11-07
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: While running an Exchange 2000 backup, the Exchange Information Store dismounts and the backup fails

Overview: While running an Exchange 2000 backup, the Exchange Information Store dismounts, and the backup fails. Troubleshooting:
TECH43899 | 2013-10-23
Technical Solutions | CMS-XML

GENERAL ERROR: Exchange 2000 directives do not appear in the file list when creating a new ms_exchange policy with Veritas NetBackup (tm).

Exchange 2000 directives do not appear in the file list when creating a new ms_exchange policy.
TECH28150 | 2013-10-23
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

GENERAL ERROR: When attempting to restore an Exchange 2000 database, the TAR log file indicates the Information Store cannot be found

GENERAL ERROR : When attempting to restore an Exchange 2000 database, the TAR log file indicates the Information Store cannot be found
TECH39359 | 2013-10-23
Technical Solutions | CMS-XML

STATUS CODE 71: Backups using NetBackup for Microsoft Exchange on an Exchange 2000 client fail with a NetBackup Status Code 71 (none of the files in the file list exist) and the bpbkar log file contains the error "fs_no_more_dle" when backing up a particular storage group.

STATUS CODE 71: Backups using NetBackup for Microsoft Exchange on an Exchange 2000 client fail with a NetBackup Status Code 71 (none of the files in the file list exist) and the bpbkar log file contains the error "fs_no_more_dle" when backing up a particular storage group.
TECH19226 | 2013-10-23
Technical Solutions | CMS-XML

When trying to restore a Microsoft SQL 2000 database to a Microsoft SQL 7 server, the VERITAS NetBackup (tm) Microsoft SQL Client restores fail with the error: "The backed-up database has on-disk structure version 539. The server supports version 515 and cannot restore or upgrade this database."

When trying to restore a Microsoft SQL 2000 database to a Microsoft SQL 7 server, the VERITAS NetBackup (tm) Microsoft SQL Client restores fail with the error : "The backed-up database has on-disk structure version 539. The server supports version 515 and cannot restore or upgrade this database."
TECH36427 | 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

NetBackup status code: 2000

NetBackup status code : 2000
HOWTO91343 | 2013-10-02
How To | CMS-XML

NetBackup status code: 2000

NetBackup status code : 2000
HOWTO51652 | 2012-11-19
How To | CMS-XML

STATUS CODE 69: Exchange 2000 backups fail with a NetBackup Status Code 69 (invalid filelist specification) when snapshot backups are enabled.

STATUS CODE 69: Exchange 2000 backups fail with a NetBackup Status Code 69 (invalid filelist specification) when snapshot backups are enabled.
TECH52640 | 2012-02-20
Technical Solutions | CMS-XML

NetBackup status code: 2000

NetBackup status code : 2000
HOWTO35762 | 2010-10-29
How To | CMS-XML

STATUS CODE 1: Exchange 2000 and 2003 backups fail with a NetBackup Status Code 1 (the requested operation was partially successful).

STATUS CODE 1: Exchange 2000 and 2003 backups fail with a NetBackup Status Code 1 (the requested operation was partially successful).
TECH51752 | 2008-01-26
Technical Solutions | CMS-XML

STATUS CODE 1 or 13: NetBackup Exchange 2003 mailbox backups fail with a NetBackup Status Code 1 (the requested operation was partially successful) or 13 (file read failed) when the Inbox has 2000 or more subfolders.

Overview Attempts to perform NetBackup Exchange 2003 mailbox backups fail with a NetBackup Status Code 1: the requested operation was partially successful; or status code 13: file read failed, when the Inbox has 2000 or more subfolders. Troubleshooting
TECH48720 | 2007-01-25
Technical Solutions | CMS-XML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?