- to be informed when it happens, when it's restored - to get a planned date for restoration of service
- be told whether there's data loss or not (and what I should have done to avoid data loss) Possible implementations are : - full redondancy on several sites (well quite expensive), quite compulsory for DNS (at least for the secundary) - no redundancy : means of information are indirect (currently linuxfr is quite good), if you still could have sent a mail to subscribers of gna project ML it would have been better - partial redundancy : alternate hosts are available and can provide minimal service (see below) For example, you could have a www.gna.org hosted on another server : - if www is unavailable, people go directly to gna.org - if gna.org (projects) is unavailable, people go to www.gna.org and see what happened => it's interesting as it does not require any DNS change (which can be long to propagate...) For hosting, you may ask several LUGs, maybe one can provide you with limited hosting : - a homepage for information (users have to find something interesting there, or they will forget this URL...) - maybe a wiki (as was done with tuxfamily.org...) - perhaps a ML for emergency situations (that project admins are advised to subscribe to) Last : for backups, they should be externalized if possible - either on user side : for cvs that's easy (but not for support/bugs...) - or by server side : maybe a regular rsync (but once gna grows it becomes more and more heavy...) Maybe there's descriptions of procedures / implementations of this already on the web ? other than what I've already done... http://wiki.eagle-usb.org/wakka.php?wiki=BesoinsUtilisateursHebergement in other situations /**************************************************************************/ [task #744] Full Item Snapshot: URL: <http://gna.org/task/?func=detailitem&item_id=744> Project: Gna! Administration Submitted by: Mathieu Roy On: dim 12.09.2004 à 08:41 Should Start On: sam 11.09.2004 à 22:00 Should be Finished on: lun 11.10.2004 à 22:00 Category: Services Functionalities Priority: 9 - Immediate Resolution: None Privacy: Public Assigned to: None Percent Complete: 0% Status: Open Effort: 0.00 Summary: emergency homepage Original Submission: We definitely need an emergency homepage, as suggested by Baud123, to be able to inform user easily in case all system go offline. This page must be on another location that gna machines (otherwise it would probably not help much). An account on this machine should be accessible through ssh to gna admins + virtual domain. We could set emergency.gna.org -- if we use a gna address, it means that the secondary DNS must be a working thing. Commentaires ------------------ ------------------------------------------------------- Date: dim 12.09.2004 à 13:14 By: Benoît Audouard <baud123> I was not far for my previous request, as it was support #218 : reread the (full) discussion...
