Perform an on-demand backup of your Content Store

To manually trigger a backup of your Content Store docbase, you can launch the backup from the IXIA TEXTML Server interface.

Note: Content Store data is stored in a IXIA TEXTML Server docbase. To back up your Content Store, you must back up the docbase.

There are two very different approaches to a system backup for your docbase. For more information, read the following: Computer Weekly Backup and Replication Article.

Synchronous backup is a linear process that runs the entire script continuously and in real-time to create a complete copy or clone of the specified files and then waits for confirmation of success before it returns to the command prompt. While it provides a high level of data protection, it involves higher latency and can slow the other applications on the system.
Asynchronous backup is a multi-thread process used in a distributed environment that runs the script while it is performing other tasks and can manage the data transfer to optimize performance and availability, but with greater risk to the dataset.

On the computer where the IXIA TEXTML Server is installed, create a directory for the backups.
In the TEXTML Administration perspective, connect to your Content Store.
Right-click the Content Store and select Backup.
The Start backup window opens.
Figure: Backing up a Content Store

CAUTION: If the destination folder is not empty,IXIA TEXTML Server deletes the contents of the folder before starting the backup.
In the Directory Path box, type the full path to the folder you created for the Content Store backups.
In Windows, for example, replace [version] by the release version:
```
C:\docbase_backups\[version]\docbaseA
```
In Linux, for example, replace [version] by the release version:
```
/docbase_backups/[version]/docbaseA
```
Note: The IXIA TEXTML Server service or daemon must have write privileges to the top-level folder storing the backups; for example, the docbase_backups directory.
Click OK.
The backup is initiated. To verify, look in the Properties view under General > Status. When you initiate the backup, the value for Status changes from Ready to Ready Backing-up.
Figure: Example of Properties view:
Wait while the backup occurs. Depending on the size of the docbase and your server activity, this could take considerable time.

Note: While the backup is running, the backup creates the temporary file backuperror.tmp within the backup folder. If no errors occur during backup and the backup successfully completes, the backup deletes the temporary file and creates a new file called backup.info.
To confirm successful completion of the backup, refresh your Properties view by clicking a different docbase and then click back again on the backup you want to refresh.
When complete, the Status changes to Ready.
To confirm that the backup was successful, look in your target directory.
- If the backup.info file is present, then the backup successfully completed.
- It the backup completed, but the backuperror.tmp is present, then an error occurred and the backup is corrupt.