154
NetBackup System Administrator’s Guide - Windows NT Server
4
# 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 machine obtains
its IP address.
You must also create a root
crontab
entry to periodically call the
bpdynamicclient
command. 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
If you are using DHCP, a good interval to use between calls to
bpdynamicclient
is one-half of the lease period.
Bandwidth Limiting
The bandwidth limiting feature lets you restrict the amount of network
bandwidth consumed by one or more NetBackup clients on a network. The
actual limiting occurs on the client side of the backup connection.
This feature only restricts bandwidth during backups. Restores are unaffected.
Read This First
• NetBackup does not currently support bandwidth limiting on NetBackup
for Microsoft SQL-Server clients
• Bandwidth limiting has no effect on a local backup (where the server is also
a client and data does not go over the network).
• Bandwidth limiting restricts maximum network usage and does not imply
required bandwidth. For example, If you set the bandwidth limit for a client
to 500 kilobyes per second, the client can use up to that limit. It does not
mean, however, that the client requires 500 kilobyes per second.
NetBackup 3.2 System Administrator's Guide for Windows NT
NetBackup 3.2 System Administrator's Guide for Windows NT
