1
edit
Changes
no edit summary
As for the management servers, there are five major ones that are critical to this operation. For a complete list of servers and the services those offer please consult the necessary documents. These four servers are Australia (Koji builders temporary work storage), Chile (The complete ARM repository), Hongkong (Koji hub and web interface), Iraq (Central backup management and storage) and Ireland (Koji database).
==Description==
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. The scripts are located at:
/usr/local/bin/
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.
[root@australia ~]# tree /archive /archive ├── blaze-backup │ ├── australia │ │ ├── australia-cron-Feb-27-2012.tar.bz2 │ │ ├── australia-etc-Feb-27-2012.tar.bz2 │ │ └── australia-userlocalbin-Feb-27-2012.tar.bz2 │ └── chile │ ├── chile-cron-Feb-27-2012.tar.bz2 │ ├── chile-etc-Feb-26-2012.tar.bz2 │ └── chile-userlocalbin-Feb-27-2012.tar.bz2 └── lost+found ===Space consideration and allocation===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 requires at least , minimum space requirements is 10GB space. To accommodate for the synced copy of the repository that size could go up to 1.7T2TB
===Initial Setup===
