diff options
| author | Nicolas Vigier <boklm@mageia.org> | 2013-04-14 13:46:12 +0000 |
|---|---|---|
| committer | Nicolas Vigier <boklm@mageia.org> | 2013-04-14 13:46:12 +0000 |
| commit | 1be510f9529cb082f802408b472a77d074b394c0 (patch) | |
| tree | b175f9d5fcb107576dabc768e7bd04d4a3e491a0 /zarb-ml/mageia-sysadm/2010-November/000535.html | |
| parent | fa5098cf210b23ab4f419913e28af7b1b07dafb2 (diff) | |
| download | archives-master.tar archives-master.tar.gz archives-master.tar.bz2 archives-master.tar.xz archives-master.zip | |
Diffstat (limited to 'zarb-ml/mageia-sysadm/2010-November/000535.html')
| -rw-r--r-- | zarb-ml/mageia-sysadm/2010-November/000535.html | 133 |
1 files changed, 133 insertions, 0 deletions
diff --git a/zarb-ml/mageia-sysadm/2010-November/000535.html b/zarb-ml/mageia-sysadm/2010-November/000535.html new file mode 100644 index 000000000..4df500b79 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2010-November/000535.html @@ -0,0 +1,133 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-sysadm] Backups + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-sysadm%40mageia.org?Subject=Re%3A%20%5BMageia-sysadm%5D%20Backups&In-Reply-To=%3C1289842520.722.169.camel%40akroma.ephaone.org%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="000534.html"> + <LINK REL="Next" HREF="000547.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-sysadm] Backups</H1> + <B>Michael Scherer</B> + <A HREF="mailto:mageia-sysadm%40mageia.org?Subject=Re%3A%20%5BMageia-sysadm%5D%20Backups&In-Reply-To=%3C1289842520.722.169.camel%40akroma.ephaone.org%3E" + TITLE="[Mageia-sysadm] Backups">misc at zarb.org + </A><BR> + <I>Mon Nov 15 18:35:20 CET 2010</I> + <P><UL> + <LI>Previous message: <A HREF="000534.html">[Mageia-sysadm] Keep puppet module generic without hardcoding domain name +</A></li> + <LI>Next message: <A HREF="000547.html">[Mageia-sysadm] Backups +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#535">[ date ]</a> + <a href="thread.html#535">[ thread ]</a> + <a href="subject.html#535">[ subject ]</a> + <a href="author.html#535">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Hi ( again ), + +While doing some unrelated work, I have see that we do not have a backup +strategy at the moment. + +While a server is planned to be setup for this ( fiona ), we do not have +it at the moment ( as this requires money, that requires a bank account, +that requires feedback from french administration ). + +So, in order to decide, we need to know : +- what do we backup ? + - ldap + - sql dump of the database + - svn dump ( which will lead to my next mail ) + - /etc/ /usr/local/, in case someone forget to add something to puppet + - CA certificate, once we will have them + - gpg keys, once we have them + - logs, as required by french laws ( 1 year of logs, no precision +about the amount of data in it ). My own experience with law enforcement +agency showed me that it doesn't change much usually + - mail archives + - irc logs + +See also with others teams if something was forbidden ( but since we +should be the only one to have access to servers, this should not be a +issue ). + + +This requires some work, first to estimate the required ressources and +the projected growth, then to decide the required strategy +( incremential, full, etc ). + +I would also highlight the need to have encrypted backups for the more +sensible set of data, to be sure that passwords keys and others do not +leave valstar in cleartext, and are not stored in form that someone +could decipher. + +Of course, the usual free/packaged/maintained/no-ressource-hog stanza +apply for the software we will use. + +Any volunteer for the tasks : + +- evaluate the needs + - discuss with all teams to check we do not forget anything +- propose and document a backup strategy, based on what we have and what +we need + - off site backup is nice, but we may not have the choice + - take in account that a new server is planned, so check with dams +( who was taked of taking care of this ) for the requirement + +- setup the backups +- setup some kind of monitoring of the backup ( disc space ) + +- check the backups are secure ( I can help on this part ) + +- write a clear documentation about backup restauration +- do regular testing of the previous procedure + +ideally, a test of a emergency restoration would be nice ( ie, let's +assume that alamut exploded and is unusable and need to be restored ), +but this would requires a spare computer, lots of disk, bandwidth and +time. + +-- +Michael Scherer + +</PRE> + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="000534.html">[Mageia-sysadm] Keep puppet module generic without hardcoding domain name +</A></li> + <LI>Next message: <A HREF="000547.html">[Mageia-sysadm] Backups +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#535">[ date ]</a> + <a href="thread.html#535">[ thread ]</a> + <a href="subject.html#535">[ subject ]</a> + <a href="author.html#535">[ author ]</a> + </LI> + </UL> + +<hr> +<a href="https://www.mageia.org/mailman/listinfo/mageia-sysadm">More information about the Mageia-sysadm +mailing list</a><br> +</body></html> |