Data backup

System backups are an important part of a disaster recovery plan. Software backups should be done at an interval that matches the dynamic nature of a system.

For example, if a system has just a few database changes a month and history file retention is not critical, monthly backups may be sufficient. In a very dynamic system, where database retention is critical, backups may need to be done on a daily basis.

Three backup operations are available:

  • A system backup combines a Supervisor station and one or more subordinate stations in a single backup job. System backups create *.zip files. To restore a system backup you must first un-zip the file using a third-party data compression utility.
  • A local backup creates a single compressed distribution file (*.dist) of a Supervisor or controller station. The restore job requires only the .dist file.
  • You can use a station copy to back up all files and subdirectories.

After creating the backup, you should download it, copy it to a thumb drive or other storage medium, and store it off site in a secure location.

Software backups need to be stored at a secure location that is isolated from the system. When choosing how and where to store a backup, remember that system backups contain information that could be used to compromise the security of a system or network. You may send the backup to the local server drive or a mapped network drive. For disaster recovery purposes, it is recommended that the backup either be sent to a network drive at another physical location, or that auto archiving of the server be setup to archive to a remote server.