projects / irc.git / blame
| Commit | Line | Data |
|---|---|---|
| 3bd189cb JR |
1 | <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> |
| 2 | <HTML> | |
| 3 | <HEAD> | |
| 4 | <TITLE> [IRCServices Coding] Backup Idea...? | |
| 5 | </TITLE> | |
| 6 | <LINK REL="Index" HREF="index.html" > | |
| 7 | <LINK REL="made" HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20Backup%20Idea...%3F&In-Reply-To=000901c2b5ce%24d49ffb60%24316419ac%40caphealth.org"> | |
| 8 | <META NAME="robots" CONTENT="index,nofollow"> | |
| 9 | <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> | |
| 10 | <LINK REL="Previous" HREF="001856.html"> | |
| 11 | <LINK REL="Next" HREF="001857.html"> | |
| 12 | </HEAD> | |
| 13 | <BODY BGCOLOR="#ffffff"> | |
| 14 | <H1>[IRCServices Coding] Backup Idea...?</H1> | |
| 15 | <B>Aragon Gouveia</B> | |
| 16 | <A HREF="mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20Backup%20Idea...%3F&In-Reply-To=000901c2b5ce%24d49ffb60%24316419ac%40caphealth.org" | |
| 17 | TITLE="[IRCServices Coding] Backup Idea...?">aragon at phat.za.net | |
| 18 | </A><BR> | |
| 19 | <I>Tue Jan 7 00:16:54 PST 2003</I> | |
| 20 | <P><UL> | |
| 21 | <LI>Previous message: <A HREF="001856.html">[IRCServices Coding] Backup Idea...? | |
| 22 | </A></li> | |
| 23 | <LI>Next message: <A HREF="001857.html">[IRCServices Coding] Backup Idea...? | |
| 24 | </A></li> | |
| 25 | <LI> <B>Messages sorted by:</B> | |
| 26 | <a href="date.html#1859">[ date ]</a> | |
| 27 | <a href="thread.html#1859">[ thread ]</a> | |
| 28 | <a href="subject.html#1859">[ subject ]</a> | |
| 29 | <a href="author.html#1859">[ author ]</a> | |
| 30 | </LI> | |
| 31 | </UL> | |
| 32 | <HR> | |
| 33 | <!--beginarticle--> | |
| 34 | <PRE>This kind of thing is best left upto shell scripts. I'd highly recommend | |
| 35 | using rsync over FTP for two reasons: | |
| 36 | ||
| 37 | 1. It's secure. All file transfers are performed over ssh by default. | |
| 38 | ||
| 39 | 2. It uses a differential algorithm so as to only transfer the incremental | |
| 40 | differences between files across the network, hence saving *alot* of | |
| 41 | bandwidth and making the backup procedure very quick. | |
| 42 | ||
| 43 | ||
| 44 | Regards, | |
| 45 | Aragon | |
| 46 | ||
| 47 | ||
| 48 | |<i> By Saturn <<A HREF="http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">saturn at jetirc.net</A>> | |
| 49 | </I>|<i> [ 2003-01-07 00:00 +0200 ] | |
| 50 | </I>><i> An Idea... any chance of some sort of built in log/database backup | |
| 51 | </I>><i> function -- something that makes a daily automatic backup copy of the | |
| 52 | </I>><i> databases and that day's log (dated), and stuffs it into a designated | |
| 53 | </I>><i> location (like some other backup dir) or even better, can auto-FTP send it | |
| 54 | </I>><i> to another machine? I know this is something above and beyond the call of | |
| 55 | </I>><i> duty for Services, but it would sure make catastrophic failures of the | |
| 56 | </I>><i> primary machine more bearable... | |
| 57 | </I>><i> | |
| 58 | </I>><i> Just a thought... meanwhile, anyone know of a linux utility that can be bent | |
| 59 | </I>><i> into an automatic FTP send of files to a remote FTP server? Maybe via a | |
| 60 | </I>><i> script? Thanks | |
| 61 | </I>><i> | |
| 62 | </I>><i> Saturn | |
| 63 | </I> | |
| 64 | </PRE> | |
| 65 | ||
| 66 | <!--endarticle--> | |
| 67 | <HR> | |
| 68 | <P><UL> | |
| 69 | <!--threads--> | |
| 70 | <LI>Previous message: <A HREF="001856.html">[IRCServices Coding] Backup Idea...? | |
| 71 | </A></li> | |
| 72 | <LI>Next message: <A HREF="001857.html">[IRCServices Coding] Backup Idea...? | |
| 73 | </A></li> | |
| 74 | <LI> <B>Messages sorted by:</B> | |
| 75 | <a href="date.html#1859">[ date ]</a> | |
| 76 | <a href="thread.html#1859">[ thread ]</a> | |
| 77 | <a href="subject.html#1859">[ subject ]</a> | |
| 78 | <a href="author.html#1859">[ author ]</a> | |
| 79 | </LI> | |
| 80 | </UL> | |
| 81 | ||
| 82 | </body></html> |