Archiving Best Practices

Aptify supports three archiving operations:

• Archive: This operation copies the selected data to the specified destination and then deletes it from the Aptify server.
• Copy: This option copies the selected data to the specified destination.
• Delete: This option removes the selected data from the Aptify server without copying it to another server. Aptify strongly recommends that you archive data rather than delete it.

When archiving data, Aptify recommends that you adhere to the following best practices:

• Establish a dedicated archive server that will store all of the data you remove from the Aptify server.
• Keep in mind that you cannot copy the same data to the same location more than once. For example, if you copy a set of data to a server and then attempt to archive the same data to the same location, the archive operation will fail. However, you can copy the same data to multiple, different locations as needed.
• When archiving information, the Culture and SQL Server Regional Settings for the users on both servers (that is, the Aptify production server and the server to which data is being archived) must match.
• An administrator should never archive Record History for Framework entities, since Aptify's Upgrade Tools may reference Record History to assist with the identification of client configurations.
• Note that the default Working Set Selection Criteria automatically excludes all Framework entities from Archive Runs, but an administrator can override the default criteria.
• In the event that you decide to override the default criteria, you should retain the "where entityid in (select id from APTIFY.dbo.entity where isframeworkentity = 0)" phrase in the SQL statement to ensure that Record History for Framework entities is not archived.
• To identify the set of entities that are flagged as Framework entities, create a view of the Entities service that filters on the IsFrameworkEntity field.