Customer Facing Information.
What is it?
We maintain offsite backups of your Kiln On Demand account. If you wish, you can also maintain your own offsite backups of your repositories.
Who will use it?
Any System Administrator or Kiln User might have the need to backup the Kiln data.
How is it used?
NOTE: We have not tested any of the scripts mentioned below with kbfiles or largefiles. Using these extension causes certain versions of files to only be retrieved from the server when you update to a given revision. If you are using a script to hg pull your repos from a local or an On Demand site, please see the command here which updates to all revisions to make sure every version of a kbfile/largefile is present. Some versions of Mercurial will also grab every version of the kbfile/largefile when you run “hg verify”.
There are a few of options to create off-site backups of your repositories. Essentially the core concept is to run a script on a remote server, use the Kiln API to enumerate the repositories on the kiln server and then use simple hg clone / pull commands to get current copies of the repositories on the remote server.
There are a couple of user-written scripts that do just that. The first was written by Stefan Rusek and is available here. The second was originally written by Nate Silva and is now maintained by Ken Morse, and can be found here.
These scripts are both pretty generic and might work perfectly for your needs without modification. Alternatively, you could use them as a starting point and expand the scripts to suit your own environment.