Event Management Overview › Event Management Architecture › Event Management Components › Event Store › Archiving Event Store XML Files › How the Archiving Process Works

How the Archiving Process Works

The archiving process includes the following steps:

1. Old XML files that are stored in the EventStore folder are added to a zip file.
2. The zip files move to the archive folder.
3. The old files are deleted from the EventStore folder.
4. The archived zip files are purged from the system after a specific amount of time.

Archiving removes the old data from the EventStore folder that is based on the archive retention interval. The archive retention interval represents the number of days the Event Store data is retained until it is archived. You can change the archive retention interval that is based on your organization requirements to decide how you want to archive your files.

For example, consider a scenario where the organization policy mandates that you must keep the files in the EventStore folder for seven days. You can archive an XML file only after it completes the prescribed period of seven days. In this case, you can set an archive retention policy that validates the XML files. The policy also archives the XML files only when the seven-day period expires.

The default archive and purge settings are as follows:

• Event Store XML files are moved to zip files in the archive folder after one day.
• Archived zip files in the archive folder are purged from the system after 30 days in the archive folder.
• If the disk volume on the system moves below 20 percent, the Event Store automatically archives all files to preserve the disk space.

Note: By default, archiving starts at midnight, and you cannot change this time. Additionally, you cannot archive any file on the day it is created. The policy requires a minimum of a one day's (24 hours) difference to be able to archive the file.

More information:

Archiving Event Store XML Files