= DBackups =

<<TableOfContents>>

= Introduction =

This section describes how SoftXS internal and customer data is backed up.

= Basic Strategy and Organization of Backup =

 * Backups of critical data are made locally on the servers where the data is managed.
 * Backups are made on a nightly basis, typically using cronjobs.
 * Local backups are stored in the local file system in staging areas. See ''File System Structure'' below.
 * Backup servers make copies of staging areas of the servers on a nightly basis.
 * There are multiple servers acting as backup servers.
 * On one of the backup servers offsite backups are made to USB drives, which are stored in a bank vault

= Backup Cycles and Offline/Offsite Backups =

 1. Online backups are made of all production systems, every night, to at least two online backup servers
    * The backups are made between 0300 and 0430 every night
 2. Offline backups are made once per week, every Saturday
    * A set of two offline backup disks is maintained
 3. Offsite backups are made once per week, every Wednesday, 
    * A set of three offsite backup disks is maintained, 
    * Two disk sets are always stored offsite in a bank vault

== Site Backups ==

Data is divided into ''sites'', where a site represents a system that manages a collection of data. Typically sites are customer DrawMGT systems. Sites are also used to represent the set of wiki systems and the SoftXS development cvs root.

Site are responsible for their own backups, and are typically implemented using a cronjob, making use of the following scripts:

 * '''backupClient.pl''' - A script that makes backups. It is located in the venture-lib CVS tree at etc/backupClient.pl
 * '''mailcron''' - A script that report cronjob errors via email. Stored in venture-lib CVS tree at etc/mailcron

These scripts are described in detail below.

== Local and Remote Backups ==

= Data that is Backed Up =

== Internal Data ==

 || '''Data''' || '''Description''' || '''Host''' || '''Site''' ||
 || Tracking System || Issue tracking system and internal & customer supplied documents || zg.softxs.ch || intern.softxs.ch ||
 || Sales System || Sales and PR documents || lu.softxs.ch || softxs.softxs.ch ||
 || Wiki || Internal and customer wiki sites || lu.softxs.ch || wiki.softxs.ch ||
 || CVS Root || Development cvsroot || lu.softxs.ch || honir.softxs.ch ||


== Customer Data ==

 * See CustomerSystemsSummary

= Backups =


== Backup Servers ==

 * zg.softxs.ch
 * bp.softxs.ch
 * thor.spftxs.ch
 * modi.softxs.ch

== Offsite Backups ==

 * Wednesday cycle
 * Saturday cycle

= File System Structure =

On backup servers the backup for locally managed data is stored in the following path:

  {{{
    /e/{volume}/backup/business/local/(intern|obsolete|sites)/{site}
  }}}

 * '''volume''' - typically 'vol001' or 'vol002'
 * '''intern|obsolete|sites'''
   * '''intern''' - internal SoftXS data, including data from internal DrawMGT system
   * '''obsolete''' - backup data that is no longer actively changed, including DrawMGT data from project that are completed (and not running as live arcive systems.
   * '''sites''' - backups of customer DrawMGT systems
 * '''site''' - the name of the customer site

For remote backups the following paths are used:

  {{{
    /e/{volume}/backup/business/remote/{system}/(intern|obsolete|sites)/{site}
  }}}
 
 * '''volume''' - as described above
 * '''system' - the hostname of the system when the original backup data is stored
 * '''intern|obsolete|sites''' - as described above
 * '''site''' - as described above