DOCUMENTATION: How to back up and restore Exchange 5.5/2000/2003 with NetBackup using a private backup LAN with a private IP Address and host name

Article:TECH38703  |  Created: 2008-01-10  |  Updated: 2013-10-23  |  Article URL http://www.symantec.com/docs/TECH38703
Article Type
Technical Solution


Environment

Issue



DOCUMENTATION: How to back up and restore Exchange 5.5/2000/2003 with NetBackup using a private backup LAN with a private IP Address and host name

Solution



Manuals:
Veritas NetBackup (tm) 6.0 for Microsoft Exchange Server System Administrator's Guide
Veritas NetBackup (tm) 5.1 for Microsoft Exchange Server System Administrator's Guide for Windows
Veritas NetBackup (tm) 5.0 for Microsoft Exchange Server System Administrator's Guide for Windows
NetBackup 4.5 for Microsoft Exchange Server System Administrator's Guide on Windows NT/2000

Modification Type:  Supplement

Modification:
When using Veritas NetBackup (tm) and backing up any version of Exchange through a backup local area network (LAN), there are certain configurations that must be done in order to get this to work properly. In order to back up Exchange and for the Exchange specific directives to work, the Exchange server name must be used in the NetBackup policy as the client name (the Exchange server name that is shown in Exchange System Manager and the name that the email clients are using). If a different host name is used the backups and restores will fail.

The reason is that when Exchange is backed up, directives such as Microsoft Information Store:\ are used, and it will use the name configured as the client name in the policy and add the directive to back up the Exchange data.

For example:
Exchange server name: Test
Public interface name: Test
Public IP Address:10.0.0.1
Private interface name: Test-backup
Private IP Address:192.168.0.1

From the example above, the only name that can be used in the NetBackup policy to back up the Exchange server is Test. This is regardless if the Exchange server is backed up through the public interface or the private interface (fully qualified names can also be used, i.e. if the Exchange server name would have been Test.veritas.com, this could have been used in the policy but not Test-backup.veritas.com).

If the private interface name is used in the policy, NetBackup will try to back up Test-backup\Microsoft Information Store, this will fail with "EXIT STATUS 69: invalid file list specification." This is because there is no Exchange server with the name Test-backup. The client name in the policy should be Test.

In NetBackup environments where the backup goes through the backup LAN, this is a problem since the master\media servers might not be able to reach the Exchange server under the name of Test (public name) but only under the name Test-Backup (private name), in which case modifications have to be done either in NetBackup or in the name resolution in order to be able to back up Exchange.

Two workarounds exist in order to enable NetBackup to back up the Exchange server using the private LAN.

Workaround 1: Using the Dynamic Host Configuration Protocol (DHCP) function of NetBackup
In this case, the DHCP function within NetBackup can be used to tell NetBackup that it has a client of the name Test, that can be found under a different host name and IP address. This will then allow NetBackup to use the public Exchange server name in the policy but access the Exchange server through its private name and IP Address i.e. in this case Test-Backup.

To set this up configure the policy using the Exchange public name as the client name (Test). Then, to enable the DHCP function within NetBackup, run the following command on the NetBackup master server (using the host names and internet protocol (IP) Address examples above):

% <install_dir>\Veritas\NetBackup\bin\admincmd\bpclient -client Test -M <Master_Server> -add -dynamic_address 1 -current_hostname Test-Backup -current_ip_addr 192.168.0.1

The above command will tell NetBackup that the client Test can be found under the name of Test-Backup and the IP Address of 192.168.0.1 but still using the Exchange server name of Test when adding the Exchange backup specific directives.

The information the above command is updating will be stored in <install_path>\veritas\netbackup\db\client\<client name>\HOST_INFO on the master. For full syntax of the command, run:
% bpclient -?

Note: When it comes to restores from the client, the name Test-Backup is not a valid client (if it is not configured as a client name for other backup policies), nor is it by default allowed to browse and restore images from the client Test, and since the name that the client will contact the master server with is Test-Backup, it might not be allowed to browse images or run restores.

To fix this, add the following entries on the master server:
Create the necessary entries in the altnames directory on the master server:
install_path\NetBackup\db\altnames\Test
In the file, add the private host name Test-Backup on one line in the file. This will allow the client Test-Backup to browse images and run restores that have been done under the client name Test.

Workaround 2:
Change the name resolution on the NetBackup master and media servers to allow the client name Test to resolve to the private IP address of 192.168.0.1.
This can be done in two ways, the simplest way is to add an entry in the local host files on the master and media server that points the host name Test to the IP Address 192.168.0.1 so the entry in the host file would look like this:
192.168.0.1   Test
In the policy, the client name should be Test. The entry above allows NetBackup to find the client Test under the IP Address of 192.168.0.1 and the Exchange backups will work.

If preferable, this can also be done through the Domain Name Service (DNS) by adding another A record in the DNS server that is used by the NetBackup master and media server that points the client Test to the IP Address of 192.168.0.1. This will also allow the client to be reached from the backup LAN under the name of Test.

Supplemental Materials

SourceError Code
Value69
DescriptionNetBackup Error 69: invalid file list specification


Legacy ID



276732


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


Terms of use for this information are found in Legal Notices