DOCUMENTATION: How to troubleshoot an Exchange Mailbox Backup

Article:TECH38737  |  Created: 2008-01-10  |  Updated: 2011-08-15  |  Article URL http://www.symantec.com/docs/TECH38737
Article Type
Technical Solution

Product(s)

Environment

Issue



DOCUMENTATION: How to troubleshoot an Exchange Mailbox Backup


Solution



Manual:
NetBackup 4.5 for Microsoft Exchange Server System Administrator's Guide on Windows NT/2000, Page: 74
Veritas NetBackup 5.0 for Microsoft Exchange Server System Administrator's Guide for Windows, Page: 91
Veritas NetBackup 5.1 for Microsoft Exchange Server System Administrator's Guide for Windows, Page: 99
Veritas NetBackup 6.0 for Microsoft Exchange Server System Administrator's Guide for Windows, Page: 68

Modification Type: Supplement

Modification:
Once correctly configured per the Symantec manual and TechNotes (links shown below in the Related Documents section), mailbox backups generally work well.  Several status codes can occur, however, and this TechNote covers the most common ones.

The first concern expressed by most people with regard to mailbox backups is performance. It is important to note with mailbox backups, throughput is expected to perform at speeds that are 10% of the exchange information store throughput. Some things which can be done to improve performance include:
 
  • Confirm the there are no errors in the indexes  -- run ESEUTIL to verify. Consult Microsoft Support for assistance on running the utility.  
  • Disable all NetBackup logging
  • Verify network configuration. If the network is poorly configured, or there is poor network throughput, mailbox backups will show extremely slow response. To test if the network is an issue, test a backup to a null device on the Exchange server. (See TechNote in the Related Documents section.)
  • If network configuration is poor, verify performance with third-party Network Sniffer
It is also important to check the Windows account which starts the NetBackup Client Service. The account must have Exchange Full Administrator rights and Local Administrative rights to the Exchange server. Running the NetBackup Client Service as the Local System account will not allow Exchange Mailbox backups to be successful.

Status Code 1:
If Single Instance Store (SIS) is enabled, it is possible for problems with the attachments to cause the backup to finish with a status code 1. The activity monitor shows the following message:

WRN - unable to successfully enumerate folder: Microsoft Exchange Mailboxes:\_Attachments_\

The bpbkar log displays:

1:40:52 AM - Warning bpbrm(pid=2836) from client Exchange: WRN - unable to successfully enumerate folder: Microsoft Exchange Mailboxes:/_Attachments_/

This means not everything was captured. To work around this issue, disable Single Instance Store. A formal resolution to this issue is expected in a later version of NetBackup.  

Otherwise, as a general rule, Status Code 1 on a mailbox backup is quite normal, and there is no reason to be concerned.  

Due to the nature of Exchange mailbox backups, and the use of the MAPI interface, a number of things can be missed, and result in a Status Code 1. Among the causes of a Status Code 1 on mailbox backups, are:
  • An attachment with a URL which either no longer exists, or one which NetBackup cannot open
  • A quarantined attachment
  • Any mail moved/deleted by a user during the backup
  • Any disabled user accounts
To determine what is not being captured by the backup, enable the bpbkar log file, and review it for errors.  

Status Code 14 or Status Code 41:
In most instances, if a backup fails with either of these messages, the client read timeout value on the Exchange server was exceeded. Increase the client read timeout value on the Exchange server to 1200 to 1800.  

Status Code 69 or Status Code 71:
Mailbox backups fail with a status code 69 or 71 because of a limited number of reasons:
  • If the Netbackup Exchange Server 2003 or onwards is configured with in the Clustered Environment, the client list should point to the Virtual Name of the Exchange Cluster .
  • The user has incorrectly specified the files list. The files list Microsoft Exchange Mailboxes:\ allows the backup to capture all mailboxes. Wildcard options such as Microsoft Exchange Mailboxes:\[a-m]* and Microsoft Exchange Mailboxes:\[n-z]* allow the backup of different subsets of the mailboxes. Please refer to the NetBackup Exchange System Administrator's Guide for more information on the use of wildcards.  
  • If the backups have never worked, it is possible the mailbox created for mailbox backups was not properly initialized. To initialize the mailbox, please send the mailbox an email, and retry the backup.
  • If the mailbox backups had previously worked, but recently stopped, confirm the mailbox used by NetBackup is not hidden. If the mailbox used by NetBackup is hidden, backups fail with a status 69 or 71.
  • The mailbox needs to be defined on the Exchange server as the mailbox being used for backups. Confirm this in the registry. Go to HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\NetBackup\CurrentVersion\Config, and find the EXCHANGE_MAILBOX value. Confirm that is the display name of the mailbox being used for backups.  
Finally, if multiple servers are in the environment, and are using the mailbox backup feature, be careful in selecting the names for the mailboxes on the various servers. If the first server uses "Veritas" and the second server attempts to use "Veritas2," backups on the first server fail, because the name is no longer unique. The names would need to be "Veritas1" and "Veritas2".
 



Legacy ID



276763


Article URL http://www.symantec.com/docs/TECH38737


Terms of use for this information are found in Legal Notices