Veritas NetBackup™ Administrator's Guide, Volume II
- NetBackup licensing models and the nbdeployutil utility
- About NetBackup licensing models
- About the capacity licensing model
- nbdeployutil utility options
- Creating and viewing the licensing report
- After creating a traditional licensing report
- After creating a capacity licensing report
- Reconciling the capacity licensing report results
- Additional configuration
- About dynamic host name and IP addressing
- About busy file processing on UNIX clients
- About the Shared Storage Option
- About configuring the Shared Storage Option in NetBackup
- Viewing SSO summary reports
- About the vm.conf configuration file
- Holds Management
- Menu user interfaces on UNIX
- About the tpconfig device configuration utility
- About the NetBackup Disk Configuration Utility
- Reference topics
- Host name rules
- About reading backup images with nbtar or tar32.exe
- Factors that affect backup time
- NetBackup notify scripts
- Media and device management best practices
- About TapeAlert
- About tape drive cleaning
- How NetBackup reserves drives
- About SCSI persistent reserve
- About the SPC-2 SCSI reserve process
- About checking for data loss
- About checking for tape and driver configuration errors
- How NetBackup selects media
- About selecting media in robots
- About selecting media in standalone drives
- About Tape I/O commands on UNIX
Configuring dynamic NetBackup clients
To configure a dynamic Windows client
- If it's not already installed, install NetBackup on the Windows client.
- In the NetBackup Administration Console, in the left pane, click NetBackup Management. On the menu bar, expand File > Backup, Archive, and Restore.
- On the menu bar of the Backup, Archive, and Restore dialog box, expand File > NetBackup Client Properties.
- In the NetBackup Client Properties dialog box, select the General tab. Change the Client Name to specify the NetBackup client name for the Windows client. Click OK.
- In the NetBackup Administration Console, set 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 the Announce DHCP Interval, return to the NetBackup Administration Console. In the left pane, expand NetBackup Management > Host Properties > Clients. Double-click on the Windows client(s) in the right pane to open the Client Properties window. In the Client Properties window, in the left pane, expand Windows Client > Network. In the right pane, check the Announce DHCP Interval check box.
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.
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:
The format of the bpdynamicclient command is as follows:
bpdynamicclient -last_successful_hostname file_name
When bpdynamicclient starts up, it checks for 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 master server. If the host names do not match, bpdynamicclient connects to the master 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/S99nbdynamicclient
Ensure 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.