The Surround SCM database stores branches, repositories, source files, users, security groups, and server options. We strongly recommend backing up the database frequently.

The following steps are for performing a backup of the PostgreSQL database installed on the Surround SCM Server computer using the pgAdmin tool. Ask your DBA for help with backups if you use a different RDBMS or moved the PostgreSQL database to a different computer.

Note: pgAdmin is automatically installed with PostgreSQL on Windows. If you use Mac OS X or Linux, download pgAdmin.

1. Stop the Surround SCM Server.
   
   Note: If you want to ensure your backup is an exact copy of the database at the specific time of backup, you can lock the database to prevent users from performing actions that write to the database, such as adding files. Refer to the Surround SCM User Guide for information about locking databases for backups.
2. Start pgAdmin.
   
   • Windows—Choose Start > Programs > PostgreSQL (version) > pgAdmin III.
   • Mac OS X—Double-click pgAdmin III in the /Applications/PostgreSQL (version) folder.
   • Linux—Enter /usr/bin/pgadmin3.
3. Double-click the local PostgreSQL server in the Object Browser to connect to it. You may be prompted to enter your PostgreSQL password.
4. Expand the Databases node and select the Surround SCM Server database.
5. Choose Tools > Backup. The Backup Database dialog box opens.
6. Enter the Filename for the backup. You must enter the full directory path for the .backup file or browse to the directory to save the backup in.
7. Click OK. The backup starts.
8. Click Done when the backup is complete.
9. Restart the Surround SCM Server and PostgreSQL server after the backup is complete.

To restore the data, select a database in pgAdmin and choose Tools > Restore. Browse to the backup file and click OK. After the data is restored, click Cancel to close the Restore Database dialog box.

Note: PostgreSQL also supports continuous archiving, which is a more advanced backup strategy that logs every database change. See Using Continuous Archiving for Surround SCM PostgreSQL Databases for information.