You are here

Backup Tab

Subscribe to Syndicate

Local Backup

The schedule of backups can be set along with retention. A TM server on a designated machine will coordinate the backups. See the setup below for the TM server

Backups Occur at Enter the times of the day that you want backups to run. Generally, at least two is recommended like 2:00 am and 2 pm (2:00,14:00) unless you have streaming replication enabled, in which case you likely only want one.
Hourly The number of hourly backups that you want the system to retain. This number can be greater that the number you want to run in any one day. if so, then more are kept across multiple days. 4 to 6 is recommended.

example: if you want to keep 9 hourly backups and do 3 backups daily, then you will have 3 backups per day (the hourlies) for each of the past 3 days.

Daily The number of days of daily backups that will be kept. 15 days (half a month) or more is recommended.

note: if backups are not run for 5 out of the past 15 days, then 15 days of daily backups means that 15 distinct days are kept, which will be across 20 days in total.

Weekly The number of weeks of weekly backups that will be kept. Between 4 and 8 is recommended.

Like the above, this is the number of distinct weeks of backups that are kept. If you keep 4 weeks of backups, but one week got missed for some reason, then TM will keep the 5th week as well.

Monthly The number of months of monthly backups that will be kept. 12 or more is recommended
Yearly The number of years that an annual backups should kept. About 5 is recommended and/or you may want to set this to coincide with the government (IRS/CCRA) requirements for electronic storage.

Backup and Notification

The daily backup script is designed to send a message to the server to update the date of last backup. If it does not, then you can deceide how long you can run without a backup before the message is displayed on startup.

Last Backup The date and time that the backup script was last known to have run. If this field does not change, then backups are probably not running.
Last Size The size of the file in the last backup. This file will increase in size.
Prior Size The size of the file in the second to last backup. This file will increase in size.
Remind in The number of days to wait until a reminder is created at a startup that the backup script did not run. Can be set between 1 and 7 days.
Threshold Enter a threshold for the differences between the current and the prior backup sizes. If the difference is over the this threshold, you will receive a warning. We recommend it is small - like 0.5%

Remote Backup

This allows you to send the backups off to another machine in the office or offsite if you want to push backups to a second safe place. Its something that we recommend.

Backup Type You can indicate what kind of offsite you want - the options are:
  • None - no offsite back will be attempted
  • FTP - this is used to send your backup to an FTP site. TM Server will attempt secure connections and fall back if necessary. You can use tools like Filezilla to set up your own PC based storage.
  • HTTP - will sent your backup data over HTTPS to a server.
  • AMS Cloud - if you have this feature, this will back up your data to the AMS cloud. No other credentials are required. It cannot be enabled in a training database.
Backup URL The URL that the backup will be sent to. Only applicable to the FTP and HTTP methods. For AMS cloud, this will be specified for you
User Name The user name to log into the remote backup location.
Password The password used to log into the remote backup location


Enabling a TM server to do backups

At least one of your TM servers should be enabled for backups.

  • This is preferably the one that is NOT running on the database server so that you have off machine backups.
  • You can enable this on multiple machines if you wish.. However it is better to enable remote push of the database instead.
Normally, a backup path (shown below) is local to the machine, but you can make it a network share if you know how to to that. Example
Platform Local Path Network Path
Windows C:\BoxOffice\Backups Log TM Server in as user that has access to network file share (i.e. set the service to login as a person with access to the share as per he sample to the right)
  • Type share name as //Share + path
  • Share: //pt-bkp01\Backups
  • Path: \TheatreManager
  • Share + Path: //pt-bkp01\Backups\TheatreManager
Windows \BoxOffice\Backups You'll have to mount a remote volume that will appear in the volumes directory that you allow read/write access to
  • Type backup path name as \volumes + path
  • Share: \Volumes\DiskMount
  • Path: \TheatreManager\Backups
  • Share + Path: \Volumes\DiskMount\TheatreManager\Backups