Requirements for Content Store backups

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

Snapshots

If you are using a snapshot volume solution, all the files that compose the Content Store docbase, such as data files and log facility, must be installed on the same volume.

Important: Once you create the snapshot, you must backup the entire backup folder. 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 is not valid.

The IXIA TEXTML Server that hosts the docbase also supports taking a snapshot at any point in time, even in the middle of a write operation. You do not need to request a quiesce moment to create the snapshot.

File backup agents

If you use a file backup agent, you need to generate a offline or "hot" copy of the Content Store docbase since you cannot perform a backup while it is in use by TEXTML Server.

Important: Once you create the snapshot, you must backup the entire backup folder. 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 is not valid.

The TEXTML Server contains scripts that you can use to produce a full hot backup of the live docbase in the designated backup folder. The script produces a consistent backup that contains all the write transactions completed by users during the time of the backup. The script must be run before the file backup agent starts its sweep of the files. You can run the script using the Windows Task Scheduler or the Linux cron service. You can also use the file backup agent’s pre-run script, if available.