Test Asset Backup Configuration involves keeping the test assets synchronized between the master and backup machines. When a user commits any test asset to a version control system to CVS, it ensures that both the master and backup machines are updated in sync. There are two backup methods available to prevent any loss of these assets.

One is to use GIT configuration, which ensures that you won't lose the assets. By performing a GIT commit, you securely save them on the GIT server. In case the machine goes down for some reason, you can retrieve your assets by performing a GIT checkout on the backup machine. You can configure GIT from Configuration > GIT Configuration.

If you are not using GIT, you can use the alternative mechanism. This involves configuring your backup server details so that every time you execute a CVS commit, your data is automatically backed up.

To handle such cases where the possibility of data loss exists, we have also implemented a nightly procedure. This procedure is scheduled to run every night at 9 PM by using the daily sync process. By using the daily synchronization feature, all of your test assets will be synchronized, and a corresponding log file will be generated.

- Make this Machine Master: Check this if you want to configure backup server and treat this machine as a master machine. Keep this unchecked if you want to treat this machine as backup machine and want to configure master machine for synchronization.
- Enable Daily Synchronization (At 9:00 pm of server time every day): By enabling this checkbox, all of your test assets will be synchronized everyday at 9:00 pm of the server time , and a corresponding log file will be generated.
- Master/Backup Server IP: Provide the IP address of a master/backup server. Provided server will be used for storing backups of Test Assets.
- SSH Port: Specify the SSH port number for establishing secure, encrypted communication between master and backup server over a network.
- Master/Backup Controller Name: Specify the name of the master/backup controller where test assets need to be backed up.
- Size of Log File : Specify the size of the log file generated during the master/backup process of test assets. These log files contain records of activities, events, and details related to the master/backup process. After reaching the maximum size of log file, the data will be truncated.
  Note: You can see the log file from the Manage Load >Logs > Log Viewer > Test Asset Backup Logs.

## Backend Steps for Creating a Connection

Below are the one time mandatory steps that need to be performed in the backend on the master and backup servers:

- Step 1: Run "ssh-keygen -t rsa -b $TR_NUM" command.
  Output:
  Generating public/private rsa key pair.
  Enter file in which to save the key (/home/cavisson/.ssh/id_rsa):
- Step 2: Press Enter
  Output:
  Enter passphrase (empty for no passphrase):
- Step 3: Press Enter
  Output:
  Enter same passphrase again:
- Step 4: Press Enter
  Output:
  Your identification has been saved in /home/cavisson/.ssh/id_rsa.
  Your public key has been saved in /home/cavisson/.ssh/id_rsa.pub.