1
edit
Changes
no edit summary
[[Category:Fedora]][[Category:SOP]][[Category:Fedora ARM Secondary Architecture]]{{Draft}}
=Seneca CDOT ARM Project: Management Server Backup and Recoveryplan=Contact info:
* Phone: X33463
* Email: fedora-arm at senecacollege dot ca
For backing up the configurations and keeping copies of those for the previous 30 days and also allocating room for possible synced copies from other servers, minimum space requirements is 10GB. To accommodate for the synced copy of the repository that could go up to 2TB
===Data Retention===
* Removable drives will keep data up to 3 days old* Network synced drives/servers will keep data up to 30 days old
===Initial Setup===
This applies to any new server that will be backed up (this process could be scriptable become a script eventually)
* Create a user named "backup"
* Give that user certificate access through ssh (to and from) the other servers (in the backup group). Tutorials available [http://zenit.senecac.on.ca/wiki/index.php/OPS235_Lab_7 here]
* Also give cert access to the root of each server so that those can remote access to the "backup" user of other servers.
* Add a new lvm called archive that will be mounted as /archive on startup (add an entry to /etc/fstab). LVM tutorial available [http://zenit.senecac.on.ca/wiki/index.php/OPS235_Lab_4 here]
* Create the following directories and give "backup" write permission to those directories
/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 backup as root (crontab entry). It will look something similar to this:
20 2 * * * ADMHOST=$(cat /etc/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
===Scheduling===
* In Chile it blaze runs at 01:35 AM UTC* In Hongkong it blaze runs at 02:05 AM UTC* In Australia it blaze runs at 02:20 AM UTC* In Ireland it 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 it blaze runs at 0108:30 AM EDT ===Offered/Backedup Servers/Services===* Please add the service type in the appropriate row in the "Define the names of 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===
* Add Content (to do for max)Repo sync process is done via rsync* Repo sync via LVM snapshot is under consideration===Backing up in Backup to Removable Drives===* Add Content Removable drives (2x1T or 1x2T) can be attached to do 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 maxthe 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="mediawiki" border="1" cellspacing="2" width="100%"
|-
| Hongkong |:Ireland| :/etc/ :/usrvar/localspool/bincron/ :pg_dump:/varusr/spoollocal/cronbin/ || :Configurations, :Cronjobs and :PostgreSQL DB:Scripts || :Iraq and Ireland |Chile| :/archive/blaze-backup/hongkongireland/
|-
| Ireland |:Australia| :/etc/ :/usrvar/localspool/bincron/ :/varusr/spoollocal/cronbin/ pg_dump || :Configurations, :Cronjobs, PostgreSQL and :Scripts || :Iraq and Chile |Hongkong| :/archive/blaze-backup/irelandaustralia/
|-
| Australia |:Chile| :/etc/ :/var/spool/cron/usr:/localmnt/binkoji/ :/varusr/spoollocal/cronbin/ || :Configurations, :Cronjobs and :Repo:Scripts || :Iraq and Hongkong |Australia:(Repo Sync in Scotland and Romania only)| :/archive/blaze-backup/australiachile/:/archive/repo-backup/
|-
| Chile |:Iraq| :/etc/ /usr/local/bin/ :/var/spool/cron/ :/mntusr/kojilocal/ bin/|| :Configurations, :Cronjobs, Repo and :Scripts |:Chile| Iraq and Australia || :/archive/blaze-backup/chile/ /archive/repo-backupiraq/
|-
| Iraq |:Scotland| :/etc/ :/var/spool/cron/:/usr/local/bin/ :/var/lib/etherpad-lite|:Configurations:Cronjobs:Scripts:Etherpad Lite DB|:Iraq and Ireland|:/archive/blaze-backup/scotland/|-|:Romania|:/etc/:/var/spool/cron/ :/usr/local/bin/|| :Configurations, :Cronjobs and :Scripts |:Australia, Iraq and Scotland| Chile || :/archive/blaze-backup/iraqromania/
|}
===Backup Location Capacity===
hongkong
Filesystem Type Size Mounted on
/dev/mapper/hk-archive ext4 5.0G /archive
iraq
Filesystem Type Size Mounted on
/dev/mapper/iraq-archive ext4 50.0G /archive
ireland
Filesystem Type Size Mounted on
/dev/mapper/ireland-archive ext4 1.2T /archive
australia
Filesystem Type Size Mounted on
/dev/mapper/australia-archive ext4 9.9G /archive
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
===Log Files===
Available on all servers running blaze
/var/log/blaze-backup.log
/var/log/wildfire-sync.log
Available on central/aggregator/admin server
/var/log/blaze-wildfire.log
.