TestArchitect Repository
A TestArchitect repository is the central storage location for all your work on test modules, actions, interfaces, data, and test results. It is essential that you back up repositories in case of data loss or corruption. Here are some best practices you can follow to ensure you have a good backup in place.
Manual Backup
The simplest means of backing up a repository is by exporting it to a file manually, which can later be imported when the repository needs to be restored. This manual backup is needed when you have an immediate need such as you want to move the Repository Server to another machine.
Refer to TA Help > Administration Guide > Repository Server Management > Exporting/ Importing Repositories for how to do manual backup, or click Here
Automatic Backup
A more elegant and convenient alternative to manual backup is to allow TestArchitect to back up your repositories automatically, on a periodic schedule.
Automatic backup can be set up or reconfigured at any time, with the repository server running or stopped. Similarly, backups themselves can take place while the server is running.
To ensure that your backup repositories are always up-to-date, it is suggested that you select a daily backup, i.e. every day from Mon to Sun. It is recommended that you specify a time when your team does not work with the repositories, for example, 1:00 AM.
When specifying the backup folder where the backup repositories reside, make sure the backup folder has sufficient disk space to store the backups.
Refer to TA Help > Administration Guide > Repository Server Management > Backing up Repositories for how to do automatic backup, or click Here
Replication Repositories
In a large or medium-scale test setup, or an outsourcing arrangement, tests may be developed by different teams in different regions. A primary/replication-repository configuration improves reliability, fault-tolerance, and latency issues. Particularly, the replication server monitors the health and availability of the primary repository, and takes over if the primary repository fails or goes offline.
Additionally, each team has the option to have a local repository server that is a replication of the primary repository. Data can be synchronized between the primary and replication repositories, so all team members can work off of their local repositories as if they are working from the same repository.
Refer to TA Help > Administration Guide -> Repository Server Management -> Replication Repositories for how to setup replication repositories , or click Here
The backup procedures on primary and replication repositories are identical. Refer to the discussions under Manual and Automatic Backups above.
Notes: The backup of a primary repository and its replication repository are separate and independent of each other. You are free to set a backup schedule on a primary that is different from the backup schedule on any of its replications.