Reliable backups are critical to the stability of your Micro Focus TeamWorks site.
IMPORTANT:Do not use VMware snapshots as a backup method for TeamWorks. Doing so creates problems when managing the system disk and inhibits your ability to update TeamWorks in the future.
In order to keep adequate backups of your Micro Focus TeamWorks data, you must back up the following types of data:
Back up the following location on the TeamWorks appliance. In a multiple-appliance deployment, back up this location on each TeamWorks appliance in the cluster.
/vastorage/esn/filerepository
Back up the following location on the TeamWorks appliance (in an all-in-one deployment) or on the PostgreSQL database appliance (in a multiple-appliance deployment):
/vastorage/postgres
Specifically, you should back up the following databases: TeamWorks, information_schema, PostgreSQL
Refer to the Backup and Restore in the PostgreSQL documentation.
You can back up the following location on the TeamWorks appliance (in an all-in-one deployment) or the Search index appliance (in a multiple-appliance deployment):
/vastorage/conf
The Search index does not need to be backed up because it can be rebuilt at any time.
Back up the following location on the TeamWorks appliance. In a multiple-appliance deployment, back up this location on each TeamWorks appliance.
/vastorage/conf/certs
You do not need to bring your Micro Focus TeamWorks site down in order to perform backups. You might want to back up the TeamWorks file repository and the TeamWorks database every night, perhaps doing a full backup once a week and incremental backups on other days. You can back up the Elasticsearch index whenever it is convenient. You can always reindex the TeamWorks site in order to re-create the Elasticsearch index, but being able to restore content from a backup can save time in case of an outage.
If you need to restore your Micro Focus TeamWorks site from a backup, restoring the same backup version for both the file repository and the database creates a TeamWorks site that is consistent within itself but might be missing information that was added after the backups were created. If you lose the file repository but not the database, you can restore the backed-up file repository and keep the more current database, but some files are likely to be missing from the file repository.