About Resilient jobs
The Resilient jobs feature lets the media server's job processes continue to run during a service disruption with the primary server. Backup metadata is cached to a user-defined location while the primary server processes are disrupted. Once the primary server re-establishes connections to the active media server processes, the cached data is transferred, and the backup proceeds.
To determine if a job is resilient, search the job details for the text, "job is resilient". If this text is present, the job is resilient.
The Resilient jobs feature is enabled by default. This feature is only available for some policy types. Please review the current requirements and limitations:
The resiliency feature is either enabled or disabled. Backup jobs run as resilient jobs only when resiliency is enabled.
Resilient jobs are only supported for Windows and Standard policy types.
Backups cannot be multiplexed.
Backups cannot have parent and child hierarchy. Use the Activity monitor to show parent and child relationship.
Resilient jobs support the failure of the primary server. If the media server fails for any reason, the resilient jobs feature is not supported.
Note:
If the primary server is also either the media server or the client, and it fails, the job is not resilient.
If the client fails for any reason, the resilient job feature is not supported.
The media server must be at NetBackup version 10.1.1 or later.
Multistreamed backup jobs are not supported.
Fiber Transport Media Server (FTMS) environments are not supported.