Document Actions
7.
Backup and Restore
Up one level
With Hosted Solutions, restore operations will be performed by OpenEngagement. Users should simply notify OpenEngagement of database problems, and we will address these if we have not already begun to do so.
With Local Solutions, users should perform regular, complete backups on a scheduled basis. Because the firm's content is kept in one location, backups are simpler for firms when using the OpenEngagement DMS than when not using it, but backups are still necessary. These firms should backup the entire Data/var directory of the DMS, as to cover the database (the Data.fs file) and the External Storage (all files uploaded to Engagement and File objects). The backup should copy the var directory to another computer, to protect the backup against hard-drive failures, viruses and so on. Ideally, the backup should be to another building, so firms are also protected from fire and other such issues.
The OpenEngagement for Local Solutions ships with a database backup. This provides a minimal degree of security for firms, but it includes only the Data.fs file and not the External Storage. Firms should not rely on this backup. The data.fs file includes the metadata, user accounts, local roles and similar information. It includes all data other than the uploaded files themselves.
If firms do their own full backup and there is a database failure, they should do a restore using this backup. If this is not available, or there is no recent backup, firms may use the backup of the Data.fs file. However, this may be out-of-synch with the External storage, so not all of the DMS will be accessible. In this case, portions of the DMS may need to be re-created.
The script to provide the backup of the data.fs file is called BackupWithRepozo.bat. A readme file is associated with this file. The readme file explains how the script may be modified to backup to another destination. Most firms can use the default backup directory.
Firms using Local Solutions are also advised to also use replication, or to at least have backup hardware available in the event of a hardware failure.