Proc and Alert logs show "Database backup sets" being locked
error message is "Unexpected exception while removing C:\Quest\Repos\DatabaseBackupSet\000765fe0000021a-0001-2.5.916.1184-tpam.log.zip:
The process cannot access the file ' C:\Quest\Repos\DatabaseBackupSet\000765fe0000021a-0001-2.5.916.1184-tpam.log.zip' because it is being used by another process."
If the TPAM appliance is changed from "Appliance Active: Active" to "Appliance Active: Not Active" on the slow-link Replica the alert logs stop sending the Moderate warning that 'primary server name (ip address of primary) caught and unexpected exception while performing task Removing 1 files from Database BackupSet://(ip address of slow link replica): Repository is write protected.
Considering the value of the information stored in TPAM the backup engine is an integral part of TPAM. Backups can be configured to run automatically and moved securely to offline storage. If PSM sessions are being recorded on the appliance and they are not sent to an archive server the TPAM backups can get extremely large. It is recommended to send session logs to an archive server to avoid this.
In the /admin console navigate to Backup Management | Settings | Schedule
------------------------------------------------------------------------------------------------------------------------------------------------------------------------
© 2024 One Identity LLC. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center