Creating a backup for the Content Store

Depending on the third-party backup solution you selected, you may need to designate a backup folder to receive the backup files and create a script to trigger the backups regularly.

Using snapshots

If you are using a snapshot volume solution, all the files that compose the Content Store (data files and log facility) must be installed on the same volume. Once the snapshot is created, all the Content Store files must be copied together. You cannot perform an incremental backup on the archive bit or use the modification date to just copy the files that were changed since the last backup.

Note: The TEXTML Server hosting the docbase supports taking a snapshot at any point in time, even in the middle of a write operation; therefore, you do not need to “request a quiesce” moment to create the snapshot.

Using a file backup agent

If you are using a file backup agent, you need to generate a offline copy or "hot copy" of the Content Store since you cannot perform a back up on it while it is in use by TEXTML Server. The TEXTML Server contains scripts that you can use to produce a full “hot” backup of the live Content Store in the designated backup folder. The script produces a consistent backup containing all the write transactions done by users while the back up was performed. The script must be run before the file backup agent starts its sweep of the files. The script can be run by the Windows Task Scheduler or the Linux Cron service. The file backup agent’s pre-execution script, if available, can also be used.

Note: The entire backup folder must be backed up. You cannot perform an incremental backup on the archive bit or use the modification date to just copy the files that were changed since the last backup. All the files in the folder must be backed up as one unit otherwise the backup will not be valid.