Back up projects in existing installation

Back up all your projects in the existing installation. Projects should be backed up before running the verify and repair tools.

When you run the repair or upgrade process, OpenText Application Quality Management performs changes on your projects to align them with the specifications for the current version. You must back up your projects before you start to repair or upgrade them.

We strongly recommend that you deactivate projects before backing them up. If you must back up while your project is still active, you must back up the database before the file system. We also recommend backing up the file system as soon as possible after backing up the database. To back up and restore data from active projects, see this KB article.

Note:

  • The repair process makes changes to the project database schema only. Before running the repair process, you should back up the project database schema on the database server, and you should back up the project data in the file system.

  • Before you run the upgrade process, perform a full backup of your projects that includes the project database schema and the project repository.

  • Version Control: Version control enabled projects cannot be backed up while there are checked out entities. All entities must be checked in to the corresponding version of OpenText Application Quality Management. To determine if there are checked out entities, see this KB article.

To back up the project database schema on the database server:

  • Microsoft SQL database. To back up the project database schema on the database server, see this KB article.

  • Oracle database. To back up the project database schema on the database server, see this KB article.