|
|
The following are the limitations of the nbdecommission command:
Does not decommission media servers at release levels earlier than 6.0.
Does not decommission clustered media servers. Those include NetBackup failover media servers or application clusters.
Does not update the vm.conf files on the NetBackup servers in your
environment. Therefore, the old server may remain in the
vm.conf files on the NetBackup
servers.
Does not update the configuration files on the clients. Therefore, the old server may remain in the server lists on the clients. If you replace an old server with a new server, the new server is not added to the client server lists.
Does not process the NetBackup Vault profiles. If NetBackup Vault profiles exist that refer to the storage units on the old server, update the Vault profiles manually.
Does not restart the daemons and services on other servers that the decommissioning affects.
Requires that you shut down all daemons and services on the old server after it is decommissioned.
Requires that you reconfigure devices on the new server manually (if required).
Requires that you know which jobs are running on the old server. You must kill them or let them run to completion before you run the decommission process.
The -list_ref option only reports on the references that it removes explicitly. The command removes some items implicitly and it does not report them. For example, host aliases and host credentials are removed but not reported.
Requires that you move any media ID generation rules that exist on the old server. You must move them manually to the media server that performs robot inventory.
Moves the old server to an Administrative Pause state so that no new jobs are started. However, NetBackup still can start backup and restore jobs for basic disk; they obtain resources differently than do jobs for other storage destinations. Also, the nbdecommission command may clear the Administrative Pause to expire images (depending on your responses to the wizard). Jobs may start during this period.