Offline option usage considerations and restrictions
The ability to take clients offline is useful in a number of situations. For example, in the event of planned outages or maintenance, client systems can be taken offline to avoid the unnecessary errors that administrators would then need to investigate. This option can also be used to anticipate new clients in the system; listing them in policies but configuring them as offline until they are in place and ready to be used
The following actions can be performed if a client is offline.
Table: Offline option actions
Type of job or operation | Action or restriction |
|---|
A client is offline and the job is already in progress | Offline clients continue to be included in any job. |
A client is offline and job retries were started before the client was taken offline | Job retries continue as normal. |
Any duplication job that is associated with a storage lifecycle policy and an offline client | Continues to run until complete. |
LiveUpdate jobs for offline clients | Continues to run until complete. |
Restore jobs | Can be run for offline clients. |
The user attempts a manual backup for an offline client | The backup fails with a status code 1000 (Client is offline). The user can either wait until the client is brought online again or bring the client online manually. Use either the NetBackup Administration Console or the bpclient command to do so before resubmitting the manual job. |
Archive backups | Not allowed for offline clients. |
Administrators restarting or resuming jobs | Not allowed for offline clients. |
If the master server is offline, hot catalog backups cannot run.
