Skip to main content

1E 23.11 (SaaS)

Peer Backup Assistant: Finalize Nomad PBA Data Store

Closes the connection to the PBA data store after user state is saved with USMT Capture User State.

Note

This step replaces the Peer Backup Assistant: Close Nomad PBA Data Store (deprecated) and the Peer Backup Assistant: High Availability (deprecated) steps. You can continue using the deprecated steps if you have already deployed them, but you cannot modify them. Going forward, we recommend you migrate to this new task sequence step.

This custom action is available in the 1E Nomad PBA task sequence actions .

Actions

When run, this task:

  1. Closes the connection to the PBA data store after the user state is saved with USMT Capture User State.

  2. Optionally, stores user state data locally if there is enough disk space.

Context

This task sequence action:

  • Must be run after the Provision Nomad PBA Data Store and USMT Capture User State actions.

Associated variables

n/a

Configurable parameters

Parameter

Default value

Description

Name

Peer Backup Assistant: Finalize Nomad PBA Data Store

Name for the custom task sequence action.

Description

Action to close the connection to the Nomad PBA data store after saving the user state.

Description for the custom task sequence action.

Enable HA

False

Enable high availability.

Note

If the task sequence variable 1EDisablePBA_HA = True, then High Availability is disabled. This variable is automatically set for Remote WSA deployments.

Minimum

1

The minimum number of PBA data store backups. The number of data stores must be available when PBA-HA starts the backup, else if fails.

  • Must be between 1 and 6

  • Must be equal to or greater than the Synchronous value.

Maximum

1

The maximum number of PBA data store backups.

  • Must be between 1 and 6.

Synchronous

1

The number of successful backups to create before moving on to the next task sequence action.

  • Must be between 1 and the value in Maximum. You can set the value to 0, but we do not recommend it as it causes the next task sequence to execute immediately with no guarantee of a successful backup.

In this section: