KBI 311827 Options For Archiving Argent for Compliance Data

Version

Argent Advanced Technology – All Versions

Date

Wednesday, 29 April 2020

Summary

This article describes options for archiving Argent for Compliance data

Technical Background

Database maintenance is inevitable due to storage contention and the need for healthy disk performance

Option One – Database Backup Followed With Argent CLI Compliance Data Cleanup

Scheduled database backup followed by data purging using the Argent for Compliance cleanup CLI tool

Please see this article for details: https://help.argent.com/knowledge-base/kbi-311254-argent-for-compliance-cleanup-cli-tool/kbi-311254-argent-for-compliance-cleanup-cli-tool/

Note: Compliance data should be in a separate database according to compliance best practices

Pros

  • Does not require a database change over and has low administration overhead
  • Most customers already have an existing process covering database backups
  • No scripting is required for data purging
  • Data size is relatively stable
  • Set and forget
  • Works for customer record compliance data in the same database as Argent AT database, AND customer record compliance data in different database(s) than Argent AT database (however, see the note above about best practices for database separation)

Cons

  • Data restore requires careful planning and requires assistance of the database administrator
  • Data restore, if ever needed, can take a long time
  • Periodic data purging increases disk usage

Option Two – Database Change Over With Name Change

Change over to a new database, determined by time or database size, using a different database name from the old one

Note: Compliance data must be in separate database to use this option

Pros

  • Allows more time for the customer to archive the old database
  • Avoids periodic data purging so disk usage is reduced
  • Process for mounting and dismounting database is easy; only basic database skills are needed
  • Data restore, if ever needed, does not interfere with the current database
  • For customer record compliance data in different database(s) from the Argent AT database

Cons

  • This is a manual process since database creation involves space provisioning and planning
  • Requires configuration updates in Argent monitoring and reporting
  • Lack of maintenance can lead to oversized database

Option Three – Database Change Over Without Name Change

Change over to new database, determined by time or database size, using the SAME database name as the old one

The old database is renamed

Note: Compliance data must be in separate database to use this option

Pros

  • Argent configuration remains unchanged
  • Allows more time for the customer to archive old database
  • Avoids periodic data purging so disk usage is reduced
  • Simple archiving process; only basic database skills required to create and rename database
  • For customer record compliance data in different database(s) from Argent AT database

Cons

  • Typically a manual process since database creation involves space provisioning and planning
  • Restore requires careful planning and usually requires assistance of a database administrator
  • Lack of maintenance can lead to oversized database

Resolution

Contact Argent Free 24/7 support via https://InstantHelp.Argent.com