On This Page
Backing up TOS Classic
The backup command creates a backup of the Tufin Orchestration Suite Classic current configuration and databases for restore and disaster recovery purposes. The backup includes all files necessary to restore a TOS Classic server, but does not include files that are part of the operating system, such as postgresql.conf
.
When the database takes up most of the hard drive's disk space, this command may fail if the backup is made to a local (non-NFS) file.
For SecureTrack, you can backup only the SecureTrack configuration (conf-only) or backup the configuration with all of the reports and collected policy revisions.
Use the screen command to ensure that the backup command runs to completion.
To backup Tufin Orchestration Suite (TOS) Classic, run:
tos
backup [--st] [--conf-only] [--stop-all] [--scw ] [--sa] <backup file>
If you do not include --st
or --scw
, the backup includes both SecureChange and SecureTrack.
--st
- Makes a backup of the SecureTrack database and configuration only
--conf-only
- Makes a backup that includes only SecureTrack configuration information. When you use --conf-only
, you must also use --st
.
--stop-all
- Stops all SecureTrack and SecureChange processes before performing the backup. Use this option only if you need to make sure that revisions from after the time the backup is run are not included in the backup.
When --stop-all
is used, some traffic usage information may be lost.
--scw
- Makes a backup the SecureChange and SecureApp database and configuration only
--sa
- Include Suite Administration backup data
<backup_file>
- the name of the backup file. The file is compressed in TGZ format.
We recommend that you always verify the integrity of a backup file after you copy it to another location. See Verifying TOS Backups.
- Before backing up your database, check that the topology synchronization is not also running.
- Schedule the Backup and Topology Synchronization to run at different times in which there will be no overlap between the two processes.