Configuring dynamic NetBackup clients
The instructions for configuring a dynamic NetBackup client depend on the operating system, as follows.
See Configuring a dynamic Windows client.
See Configuring a dynamic UNIX NetBackup client.
Use the following procedure to configure a dynamic Windows client.
To configure a dynamic Windows client
- If it's not already installed, install NetBackup on the Windows client.
- Open the Backup, Archive, and Restore interface.
- Click File > NetBackup Client Properties.
- Click the General tab. Change the Client Name to specify the NetBackup client name for the Windows client. Click OK.
- In the host properties for the client, set the value for Announce DHCP interval. This value specifies how many minutes the client waits before it announces that it will use a different IP address.
To set this value, in the NetBackup web UI, on the left click NetBackup Hosts > Host properties. Select the client. If necessary, click Connect. Then click Edit client. Expand Windows client > Network. Select the option Announce DHCP interval.
Additional information is available for Announce DHCP Interval in the NetBackup Administrator's Guide, Volume I.
The server is not notified if the default value of 0 is used. For a DHCP client, a good value to use is one-half of the lease period.
- On the client, stop and restart the NetBackup Client service to have the changes take effect.
Use the following procedure to configure a dynamic UNIX NetBackup client.
To configure a dynamic UNIX NetBackup client
- If not already installed, install the NetBackup client software.
- Edit the /usr/openv/netbackup/bp.conf file. Use the CLIENT_NAME entry to specify the NetBackup client name for the computer, as follows:
CLIENT_NAME = nbclient00
- Run the bpdynamicclient command once when the system first starts up. bpdynamicclient notifies the NetBackup server of the computer's NetBackup client name and current network host name. The bpdynamicclient command is in the directory:
/usr/openv/netbackup/bin
The format of the bpdynamicclient command is as follows:
bpdynamicclient -last_successful_hostname file_name
When bpdynamicclient starts up, it verifies the existence of file_name. If file_name exists, bpdynamicclient determines if the host name that is written in the file is the same as the current network host name. If the host names match, bpdynamicclient exits and does not connect to the primary server. If the host names do not match, bpdynamicclient connects to the primary server and informs the server of its NetBackup client name and host name. If bpdynamicclient successfully informs the server, bpdynamicclient writes the current network host name into file_name. If bpdynamicclient cannot inform the server, bpdynamicclient deletes file_name.
Most UNIX systems provide a facility to define startup scripts.
For example, create the following script in the /etc/rc2.d directory on a Solaris system:
# cat > /etc/rc2.d/S99nbdynamicclient <<EOF #! /bin/sh rm /usr/openv/netbackup/last_successful_hostname /usr/openv/netbackup/bin/bpdynamicclient -last_successful_hostname \ /usr/openv/netbackup/last_successful_hostname EOF # chmod 544 /etc/rc2.d/S99nbdynamicclientEnsure that the dynamic client startup script is called after the computer obtains its IP address.
- You must also create a root crontab entry to call the bpdynamicclient command periodically.
For example, the following entry (one line) calls bpdynamicclient at seven minutes after each hour:
7 * * * * /usr/openv/netbackup/bin/bpdynamicclient -last_successful_hostname /usr/openv/netbackup/last_successful_hostname
For DHCP, an acceptable interval to use between calls to bpdynamicclient is one-half of the lease period.