This article is not applicable to Cloud versions.
The application stores data in one or two databases: Collaboration and Database. These databases should be backed up periodically. For backup and recovery procedures, refer to the appropriate database application documentation:
When backing up databases, you can create full database backups, differential backups, or transactional log backups. Full database backups provide the most complete backup and easiest restore procedure at a cost of the largest disk or storage space. Differential backups offer a smaller storage requirement but only store the latest changes since the last full backup. Finally, transactional log backups keep a list of recent transactions but must be incrementally restored along with differential backups and the full backup.
The amount of space and time required to generate the backup depends largely on the number of documents and revisions saved within the system. One or a combination of database backup methods may be the appropriate approach for your project given available hardware resources and expectations from your end user community. Establishing a backup and recovery plan will help determine the appropriate method and schedule for the backup.
When backing up the databases it is imperative to include the login information for each database. The database login accounts are created during the installation. While Oracle and IBM include database login information within the backups, Microsoft SQL Server does not.