在veritas中更改 client 的名字

在veritas中，更改 client 的名字

 

Modification
The following general guidelines can be used to determine if a restart of NetBackup is required after making changes to the /usr/openv/netbackup/bp.conf file on a system.

• Client daemons such as bpcd, bpbkar, tar and database agents are not persistent and are called only to complete an individual backup or restore.  As a result, there are no client daemons to restart.  Changes to the bp.conf on a client will take effect when new job streams start, they will not affect jobs that are already started.
• Media Server daemons such as bpbrm, bptm, bpdm are not persistent and are called only to complete a backup, restore, duplication, or other operation.  Changes to the bp.conf on a media server should take effect once a new backup or restore is run, they will not affect existing backups.  The exception to this is any configuration value that is passed to bpbrm by a master server process such as bpsched.  Note: Other Media Manager daemons such as ltid, vmd, avrd and robotic daemons on the media server read from the /usr/openv/volmgr/vm.conf file.  These daemons are persistent and typically require a restart of NetBackup.  
• Master server daemons bprd, bpdbm and bpjobd are persistent.  As a result, these need to be restarted to recognize changes to the NetBackup configuration.  The bpsched daemon is called by bprd and is continuously active until all queued jobs have completed.  The bpsched daemon must be restarted if jobs are continuously active and the configuration change needs to be picked up before the queued jobs execute.

After changing the NetBackup master's bp.conf file, the bprdreq command can be run.  This command rereads the bp.conf, but only entries that affect the main bprd process will be updated.  It will not change the environments of existing processes.  For example, adding or changing SERVER entries will not be reread using this command.

Use the following command to tell bprd to reread it's configuration:
# /usr/openv/netbackup/bin/admincmd/bprdreq -rereadconfig

Note: This command will only detect and incorporate some bp.conf configuration changes. Many NetBackup configuration changes, such as adding or changing a SERVER entry, require a complete stop and start of the NetBackup daemons. If the bp.conf configuration change does not take effect, then the NetBackup daemons must be restarted.  To do so, when no backups or restores are running, execute the commands:

# /usr/openv/netbackup/bin/goodies/netbackup stop
# /usr/openv/netbackup/bin/goodies/netbackup start