Build a policy
Open Policies and click New Policy, and the builder takes you through it.
Plan details: name it after what it protects.
Backup content: tick the machines, then list the folders. Exclusions, databases and scripts are under More options.
Backup destination: choose the repository, if your account has more than one.
Schedule and retention: daily, weekly, chosen days, or a custom cron pattern, in India time. Then how many copies to keep at each tier: latest, hourly, daily, weekly, monthly and yearly.
Summary: check every setting on one page, and create it. Machines receive it at their next check-in, within a minute.
Schedules, retention and missed backups
- On a PC used by several people, one line covers everyone: the Desktop, Documents, Downloads and Pictures buttons back up that folder for every user who signs in
- After the first backup a run moves only what changed, so backups stay short and less of your line is taken up during the working day
- When a copy passes its retention date it leaves the list, and a regular clean-up then releases the space it used, so storage does not grow for ever. The clean-up runs by itself on a machine that uses the repository, and each repository shows when the last one finished and when the next is due
- 'Run backup now' takes exactly the same path as a scheduled run, so testing it actually proves something
- On Windows, files that are open or in use are captured properly rather than skipped, so a busy server does not leave holes in its own backup
- If a machine is off at its scheduled time, it can catch up when it comes back, after a delay you set so it does not slow someone starting work
- A scheduled slot that can never now be covered is recorded as missed rather than quietly vanishing
- You can cap how much of your internet line backups and restores may use
- To keep a local and an off-site copy of the same machines, create two policies with the same folders, one for each repository
Scripts before and after a backup
A policy can run a script just before each backup and another just after it. Use it for software Satkosh does not back up directly: dump Microsoft SQL Server or MongoDB into a folder the policy backs up, or pause an application so its files are consistent, then start it again.
- The script lives on the server and the console only chooses it by name. Nobody can type a command into the console and have it run on your servers
- The agent refuses to run a script that anyone other than an administrator could change, because whoever can edit it would be running commands as root or SYSTEM
- If the before-script fails, nothing is backed up and the backup fails, so an old dump never passes as a good backup. A policy can choose to back up anyway, with a warning
- The after-script runs whether the backup worked or not
- Each script's result appears in the backup's details, and a script is stopped after 60 minutes