Peer Backup Assistant: High Availability (deprecated)
Note
This step is deprecated, and you should use the Peer Backup Assistant: Finalize Nomad PBA Data Store instead. Existing deployments will still work, but you cannot modify them. Going forward, we recommend using its replacement.
This step stores additional backup copies of the PBA data store, after the primary data store has been created with Peer Backup Assistant: Provision Nomad PBA Data Store and after the USMT data has been saved andc losed with Peer Backup Assistant: Close Nomad PBA Data Store (deprecated).
The following actions must have been run successfully:
Peer Backup Assistant: Provision Nomad PBA Data Store
USMT Save User State
Peer Backup Assistant: Close Nomad PBA Data Store (deprecated).
This custom action is available in the 1E Nomad PBA task sequence actions .
Actions | Notes |
---|---|
When run, this task:
| This task sequence:
|
Configurable parameters
Parameter | Default value | Description |
---|---|---|
Name | Peer Backup Assistant: High Availability. | Name for the custom task sequence step. |
Description | Action to find additional PBA data stores for saving user state. | Description for the custom task sequence action. |
Minimum | 1 | The minimum number of PBA data store backups. Must be at least 1 and not greater than 6. The specified number (minimum) of data stores must be available when PBA-HA starts backing up the data. If the minimum number of data stores will not respond, then the PBA-HA task sequence step will fail. NoteThe minimum should be greater than or equal to the Synchronous value. If the minimum number is less than the Synchronous value, the task sequence may fail even though the minimum number of backups have been done. |
Maximum | 1 | The maximum number of PBA data store backups. Must be at least equal to the minimum and not greater than 6. |
Synchronous | 1 | The number of backups that must be performed successfully before moving onto the next action in the task sequence. Must be 0 or more and not greater than the value set for the maximum. NoteIt is possible, but not recommended, to set this value to 0. If this is done, the next action in the task sequence will start immediately, but there will be no guarantee that any backups have been successful. |