Backing up Team Studio

To protect against data loss and to plan for disaster recovery, add a regular backup procedure for your installation of Team Studio to your other disaster recovery plans.

Perform this task on the server where Team Studio is installed. During the backup process, the following backup file is dumped into your backup directory.

chorus_backup_YYYYMMDD_HHMMSS.tar

We recommend running a cron job to backup Team Studio at least daily.

Important: Team Studio logs and indexes are not stored in the backup file. After you restore the database, trigger index building.

Prerequisites

  • Be sure that Team Studio is shut down before your run the backup process.
  • Do not run this task as root.

Procedure

  1. Change to the directory where Team Studio is installed. 
    $ cd <Team Studio install path>
  2. Run the following code. 
    $ source chorus_path.sh
$ chorus_control.sh backup [-d dir] [-r days]
    Option Description
    -d Specifies the directory where the backup files are written. If you do not specify a backup directory, the backup utility creates the default backup directory /data/chorus/bak
    -r Specifies the number of days of backup files should be kept in the backup directory. Files more than -r days old are removed. If -r is not specified, no files are removed.
    For example, the following command backs up the Team Studio files to /data/tsds/daily_bu and deletes backup files that are more than 10 days old. 
    chorus_control.sh backup -d /data/tsds/daily_bu -r 10
Related concepts
Related tasks