=Seneca CDOT ARM Project: Management Server Backup Strategy and Recovery Planplan=Contact info: 

The backup system has been broken into two custom scripts. First one is to create a local copy of the configurations and to back up the repository to removable drives, it is called blaze. The second script is called wildfire and it is to synchronize those local copies to different locations over the network. The servers get the copies of those scripts from the central backup management and storage server (iraq) via scp and runs blaze first and then wildfire. ===Backup Script Source===The scripts are located at(any server with backup enabled):

===Backup Directory Structure===The backups (both local copies and networked synced copies) are stored inside /archive/blaze-backup (/archive/repo-backup for the repository sync) in each servers respective directory. Example:

│ │ ├── chile-etc-Feb-2627-2012.tar.bz2

│ ├── ireland-etc-Feb-2627-2012.tar.bz2

 ===Space consideration Consideration and allocationAllocation===

This applies to any new server that will be backed up (this process could be scriptable become a script eventually)

* Create the following directoriesand give "backup" write permission to those directories /archive/blaze-backup /archive/repo-backup /var/log/blaze-backup* Create the following file and give "backup" write permission to that file and also add the hostname for the admin server (iraq) in that file (please see offered services section for other options) /etc/sysconfig/blaze* In the admin host, add the hostname in the buddyhost section in blaze and wildfire with a random syncpeer. (optional, please see offered services section for more options) * Add the following entry to /etc/aliases (use proper email format): blaze-wildfire: fedora-arm at senecacollege dot ca* Schedule backupas root (crontab entry). It will look something similar to this: 20 2 * * * ADMHOST=$(cat /aretc/sysconfig/blaze); BKU=backup; export ADMHOST BKU; scp $BKU@$ADMHOST:/usr/local/bin/blaze \ /usr/local/bin/; chown -R $BKU:$BKU /usr/local/bin/blaze; chmod 755 /usr/local/bin/blaze; /usr/local/bin/blaze* If the server is going to be a reposync host then follow the first three steps to create a user account called apache and give it access to and from the repohost

==Backup script explanation/source=Scheduling===* In Chile blaze runs at 01:35 AM UTC* In Hongkong blaze runs at 02:05 AM UTC* In Australia blaze runs at 02:20 AM UTC* In Ireland blaze runs at 03:35 AM UTC* In Scotland blaze runs at 12:50 AM EDT* In Romania blaze runs at 01:50 AM EDT* In Iraq blaze runs at 08:30 AM EDT

maybe source here?===Offered/Backedup Servers/Services===possible description * Please add the service type in the appropriate row in the "Define the names of it?the remote machines and services" section in each script** PostgreSQL Database Server (DBHOST)(Possibly one - Ireland)** Repository (REPOHOST) (Possibly one - Chile)** Server that has backup to removable drive capabilities (RBDHOST) (Chile or Ireland or Scotland)** Central Sync Server (SYNCHOST) (Iraq, Scotland and Romania)** Repository Backup (COPYREPOHOST) (Scotland Romania)** Sync Peer (BUDDYHOST) (All)** Custom Log and Mail Server (AGGREGHOST) (Iraq)** Administrator Host (ADMHOST) (Iraq, for now)** All related servers under blaze wildfire system (ALLSYS) (Australia Chile Hongkong Iraq Ireland Scotland Romania)

===Repo Sync===* Repo sync process is done via rsync* Repo sync via LVM snapshot is under consideration===Backup layout exampleto Removable Drives===* Removable drives (2x1T or 1x2T) can be attached to the repo server or any server that has a copy of the repo* Those servers have the capability to auto backup overnight as long as the drives are labeled as cdot-backup-nnn (where nnn could be 001..999) * Multiple removable drives should be used and one set of drives containing the full repo copy should be always offsite (daily rotation schedule)===Offsite Backup===* Offsite backup over the network is still under consideration===Restore from Backups===This process is not automated yet. If an older copy is required for the postgresql dump or any scripts or configuration files, please copy the necessary zip file from /archive/blaze-backup/[hostname]/ location and unzip it to a new location and copy the desired file. Please follow the [[#Backup_Layout|backup layout]] table provided in the Appendix.PostgreSQL Restore is done via the following command (after unzipping): pg_restore

== Conclusion==ARM is still a developing technology and expectations are that The Fedora ARM Project at Seneca CDOT will be highly active for the next few years. Depending on the level of activity the backup strategy in place may become out of date in a matter of months or it may need to be supplemented with other solutions.==Appendix=====Admin Configuration===This file specifies which server is the admin host. It is available in each host at /etc/sysconfig/blaze===Backup Layout==={| class="wikitablemediawiki" border="1"cellspacing="2" width="100%"|:'''Source Server'''|:'''Backup Source'''|:'''Type of Data'''|:'''LAN Targets'''|:'''Backup Location'''|-|:Hongkong|+ :/etc/:/var/spool/cron/:/usr/local/bin/:/var/lib/bcfg2/|:Configurations:Cronjobs:Scripts:BCFG2 DB|:Iraq and Scotland|:/archive/blaze-backup layout example/hongkong/! source !! files or folder !! type of data !! destination !! location|-|:Ireland|:/etc/:/var/spool/cron/:pg_dump:/usr/local/bin/|:Configurations:Cronjobs:PostgreSQL DB:Scripts|:Iraq and Chile|:/archive/blaze-backup/ireland/|-|:Australia|:/etc/:/var/spool/cron/:/usr/local/bin/|:Configurations:Cronjobs:Scripts|:Iraq and Hongkong|:/archive/blaze-backup/australia/|-|:Chile|:/etc/:/var/spool/cron/:/mnt/koji/:/usr/local/bin/|:Configurations:Cronjobs:Repo:Scripts|:Iraq and Australia:(Repo Sync in Scotland and Romania only)|:/archive/blaze-backup/chile/:/archive/repo-backup/|-|:Iraq|:/etc/:/var/spool/cron/:/usr/local/bin/|:Configurations:Cronjobs:Scripts|:Chile|:/archive/blaze-backup/iraq/

| hongkong |:Scotland| :/etc /:/var/spool/cron/:/usr/local/bin/:/var/lib/etherpad-lite|:Configurations:Cronjobs:Scripts:Etherpad Lite DB| configurations || backup_server |:Iraq and Ireland| :/vararchive/blaze-backup/scotland/

| chile |:Romania| :/etc/:/var/libspool/db || database |cron/:/usr/local/bin/| backup_server :Configurations:Cronjobs:Scripts|:Australia, Iraq and Scotland| :/vararchive/blaze-backup/romania/

configs, database, repo commands etc.. chile Filesystem Type Size Mounted on /dev/mapper/chile-archive ext4 9.9G /archive

scotland Filesystem Type Size Mounted on /dev/mapper/scotland-archive ext4 2.2T /archive  romania Filesystem Type Size Mounted on /dev/mapper/yoda-archive ext4 2.0T /archive ===Data RetentionLog Files===* Removable drives will keep data up to 3 days oldAvailable on all servers running blaze* Network synced drives /servers will keep data up to 30 days oldvar/log/blaze-backup.log /var/log/wildfire-sync.logAvailable on central/aggregator/admin server /var/log/blaze-wildfire.log .