Backing up a Teamcenter environment

Caution Failure to back up all environment components runs the risk of data loss in the event of the need to restore the environment. Backup software requirements Third-party software is used to back up and restore files in volumes. Ensure the user running the third-party backup software is the same user as the volume owner. When to back up In addition to the normal backup of information for purposes of disaster recovery, back up the Teamcenter environment before performing any of the following actions: Installing or updating Teamcenter software Changing the machine environment, such as updating operating system software or 3rd party software Changing the data model, especially by deploying a new or modified template Other tasks that modify a particular directory in the installation Example The addition of another FSC modifies the TC_ROOT\fsc directory. In such cases, that directory and any other related dependencies (database, volumes, and so on) should also be backed up. Components of a Teamcenter environment backup For each configured database: Oracle, Microsoft SQL Server, or Aurora database TC_DATA directory and its contents Teamcenter volume directories On each workstation where Teamcenter is installed: TC_ROOT\install directory TC_ROOT\bmide directory and any custom Business Modeler IDE project folders stored in a location other than TC_ROOT\bmide TC_ROOT\fossrepo directory TC_ROOT\tc_vault directory TC_ROOT\vault_tls directory Deployment Center installation directory Back up and restore Teamcenter vault data. Depending on the environment, additional components should be backed up. For example: Dispatcher root directory (if updating the dispatcher configuration) TC_ROOT\fsc (if updating the FSC configuration) Tip In the case of Teamcenter environment components installed in virtual machines, taking a snapshot of the affected virtual machines is also a viable means of backup.