The connection backup, also known as data backup contains the audit files and connection metadata of a connection. It can be configured as a scheduled policy and is saved to a backup server.
For more information on how to perform a connection backup of a connection, see: Creating data backups. It is a three-step process:
-
Configure a system backup. Restoring a data backup works only if a matching system configuration and metadata is available, that is, if a system backup is restored first.
-
Create a backup policy at Policies > Backup & Archive > Backup policies.
-
Navigate to <Protocol name> Control > Connections. Select the connection you want to back up. Select the previously created backup policy in the Backup policy field.
For more information on how to restore the configuration and data of One Identity Safeguard for Privileged Sessions (SPS) from a complete backup, for example, after a hardware replacement, see: Restoring SPS configuration and data.
The connection backup is used for
-
Saving the created audit trail files and indexing metadata of a connection to a remote share. This is a copy operation in terms of data files.
-
Recovery: In case of a hardware replacement, creating configuration export, system backup and connection backups is essential.
-
Migration: Creating a machine identical to another SPS machine.
The connection backup contains the following
-
The audit trails of the connection, that is, the .zat files storing the recorded activities of the administrators. For more information on audit trails, see Audit Policies.
-
The index of the audit trail that makes the content of the audit trail searchable. For more information on indexing audit trails, see Indexing audit trails.
NOTE: Audit trails and index files are large. This means that backing up a connection requires a significant amount of free hardware space. Make sure you have enough free hardware space for those connections that you want to back up.