software/!RELEASES/ircservices/achurch.org/services/lists/ircservices/1999/000293.html

   1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
   2 <HTML>
   3  <HEAD>
   4    <TITLE> [IRCServices] Re: backups
   5    </TITLE>
   6    <LINK REL="Index" HREF="index.html" >
   7    <LINK REL="made" HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Re%3A%20backups&In-Reply-To=">
   8    <META NAME="robots" CONTENT="index,nofollow">
   9    <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
  10    <LINK REL="Previous"  HREF="000292.html">
  11    <LINK REL="Next"  HREF="000294.html">
  12  </HEAD>
  13  <BODY BGCOLOR="#ffffff">
  14    <H1>[IRCServices] Re: backups</H1>
  15     <B>quension at softhome.net</B>
  16     <A HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Re%3A%20backups&In-Reply-To="
  17        TITLE="[IRCServices] Re: backups">quension at softhome.net
  18        </A><BR>
  19     <I>Sat Nov  6 13:05:22 PST 1999</I>
  20     <P><UL>
  21         <LI>Previous message: <A HREF="000292.html">[IRCServices] backups
  22 </A></li>
  23         <LI>Next message: <A HREF="000294.html">[IRCServices] IRC Daemon core dumpes after 1000 users
  24 </A></li>
  25          <LI> <B>Messages sorted by:</B>
  26               <a href="date.html#293">[ date ]</a>
  27               <a href="thread.html#293">[ thread ]</a>
  28               <a href="subject.html#293">[ subject ]</a>
  29               <a href="author.html#293">[ author ]</a>
  30          </LI>
  31        </UL>
  32     <HR>
  33 <!--beginarticle-->
  34 <PRE>zshack wrote:
  35
  36 &gt;<i> It says something in the readme that it can be done. I have 2 sets of
  37 </I>&gt;<i> services linked, but when the primary fails the secondary set stays in
  38 </I>&gt;<i> read only. I was under the impression that the second set would &quot;take
  39 </I>&gt;<i> over&quot; unless there is a certain command i can give it to start when the
  40 </I>&gt;<i> primary fails.
  41 </I>
  42 The secondary set would have to stay in read-only unless you are able to
  43 easily sync the dbs in the opposite direction (from backup to primary) as
  44 well.  And if the backup and primary services are on separate sections of
  45 the network, a network split would cause a nice mess of confusion as users
  46 change things on the backup services that are not echoed to the primary.
  47
  48 I've done some thinking recently as to what a really good backup system
  49 would look like, and have come to the conclusion that it's going to take a
  50 rather large amount of work.
  51
  52 If you still want to run the backups as full services, OperServ's SET
  53 READONLY OFF  may work.
  54
  55 I would like to know how you've set up the backups... are they using
  56 different nicks?
  57
  58 -- Quension
  59
  60 ---------------------------------------------------------------
  61 To unsubscribe, send email to <A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices">majordomo at ender.shadowfire.org</A>
  62 with &quot;unsubscribe ircservices&quot; in the body, without the quotes.
  63
  64 </PRE>
  65
  66 <!--endarticle-->
  67     <HR>
  68     <P><UL>
  69         <!--threads-->
  70         <LI>Previous message: <A HREF="000292.html">[IRCServices] backups
  71 </A></li>
  72         <LI>Next message: <A HREF="000294.html">[IRCServices] IRC Daemon core dumpes after 1000 users
  73 </A></li>
  74          <LI> <B>Messages sorted by:</B>
  75               <a href="date.html#293">[ date ]</a>
  76               <a href="thread.html#293">[ thread ]</a>
  77               <a href="subject.html#293">[ subject ]</a>
  78               <a href="author.html#293">[ author ]</a>
  79          </LI>
  80        </UL>
  81
  82 </body></html>