tbielawa / glorious-backups Goto Github PK
View Code? Open in Web Editor NEWA glorious system for backups
A glorious system for backups
lcsee-glorious-backups for LOUD --------------------------------- INTRODUCTION ------------ If you want to better understand the methodology used by Glorious Backups we need to explain what sparked it's inception. Raison d'être - Reason for Existence ==================================== * Story about an svn server failing in the last few weeks of a course and there being no backups because the backup report tool was retelling lies. There was no logs of anything happening. All services had their own backup routines. Each being heavilty dependent upon the current geometry of the rapidly changing infrastructure. * Attributes Describing the new System Requirements ================================================= - Ignorant - Uniform - Test-driven - Chatty This package is used to GLORIOUSLY backup services via a centralized system which isolates outside information from the utilities which actually prep backup data to be moved. Essentially, you have a series of scripts in /etc/gbackups.d/ which are run to create the backup data and place it neatly in /srv/lcsee-backups/. After this is done, gloriously-backup rsyncs all the data in that directory to the backups file server (designated in LDAP via: cn=backups). Information is isolated such that the backup generation scripts in /etc/gbackups.d/ don't know where data is being placed or sent to, and gloriously-backup doesn't know what utilities will run. This prevents a problem of generality and makes it easy to keep all backup utilities uniform. SCRIPTS: /etc/gbackups.d/ ------------------------- Scripts placed in /etc/gbackups.d/ that end in .lgb (see the glorious acronym?) are executed by gloriously-backup each time it executes. The purpose of these scripts is to actually do the backup process (ie. mysqldump, slapcat, etc.) and place their final backup data in /srv/lcsee-backups/ ready for gloriously-backup to rsync to the backup file server. These scripts need not do anything more than this, and do not need to know where they're actually placing the data nor what file server they're being placed on. This is all provided by the native glory library functions that must be sourced in each script. A good idea is to have the following header in each script (where "SERVICE NAME" is replaced with the actual service, ie. rt, svn, ldap, etc.): --- START CODE --- #!/bin/bash SERVICE="SERVICE NAME" # Include glorious backups library if [ -e /usr/lib/glory ]; then . /usr/lib/glory else echo "Glorious backups library not found." echo "Are you sure that lcsee-glorious-backups is installed?" apt-cache policy lcsee-glorious-backups | egrep "(Installed|Candidate|Unable)" exit 1; fi --- END CODE --- From here, native functions are provided which provide the local directory to data in, as well as providing file names for current day-of-week tagged dump files, bzip and gzip files. Those functions are described in the next section. NATIVE GLORY FUNCTIONS ---------------------- TODO: Write these... NAME: PARAMETERS: RETURNS: DESCRIPTION: GLORY HOLES ----------- This section outlines potential bugs or holes in the glorious backup system. * Currently, most systems utilize a standard "backup stuff, toss it in /srv/lcsee-backups/" method. However, some other systems (ie. minid) use an alternative approach (ie. placing a symlink to /srv/bronze/). Because of this, the rsync flags in gloriously-backup include --follow-symlinks, thus if symlinks are not carefully checked for loops, this could break the backup system. * Most systems toss a single file into /srv/lcsee-backups/ for each day, however some others (ie. wv3c) include multiple files. These are tossed into an additional directory named data/. This is accomplished by performing a sed on functions which return a full path. Because of this, concurrency must be maintained in maintenance of this package. -- Timothy Bielawa (Shaggy) <[email protected]>, Wed, 28 Apr 2010 17:07:16 -0400
/etc/gbackups.conf
Preferably configurable items:
"transport routine" -> decouple the rsync script from the main gloriously-backup program
???
./install works.... but it's not really a good solution.
Yo dawg, heard you like writing documentation.
Deb/RPM packages please.
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.