Table of Contents

Control has the ability to run a SQL backup. By default, this action is in some of the default close-out configurations so that a backup is periodically run.There is an old tech support saying that in the long run there are only two types of people in the world, “Those who back up and those who wish they did.” Unfortunately, while users can continue to use Control while the backup is being done SQL becomes far less responsive and the entire system can slow down.

Concept

This how-to guide will help you set up Control to automatically run a backup at night. The basic approach is as follows:

Cautions

In this process, Control instructs SQL to start the backup. However, Control does not get confirmation back from SQL whether it was successful or not.

Since this process is run off-hours and without user interaction, it is important that you check the results periodically to make sure that you are getting new backups. Many things (most commonly a bad network path or a full drive) can prevent the backup from succeeding. The only way you will know with this configuration is if you check it.

Cyrious strongly recommends you store the backup on a different computer. The backup path in the setup options can be a UNC path.

As noted above, you will need to be sure that the temporary path, storage space and final destination is properly set in the System Setup/Backup Options setup page in Control.

Steps

  1. Create a Macro to run run a backup.
  1. Schedule the Macro to automatically run on the server every evening.
  1. Check that the backup is successful! Important Step

Source

Contributor: Cyrious

Date: 9/21/090

Version: Control 4.0+