PageRenderTime 36ms CodeModel.GetById 14ms RepoModel.GetById 0ms app.codeStats 0ms

/old-site/archive/2007-April/001226.html

http://github.com/bjdean/cambridge-pm-website
HTML | 98 lines | 83 code | 12 blank | 3 comment | 0 complexity | ddfbeec8bcf7a49db26bd692eaaa8c61 MD5 | raw file
  1. <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
  2. <HTML>
  3. <HEAD>
  4. <TITLE> [cam.pm] Backups + next pubmeet, Re: Hangover over?
  5. </TITLE>
  6. <LINK REL="Index" HREF="index.html" >
  7. <LINK REL="made" HREF="mailto:cam.pm%40cam.pm.org?Subject=%5Bcam.pm%5D%20Backups%20%2B%20next%20pubmeet%2C%20Re%3A%20Hangover%20over%3F&In-Reply-To=20070421132115.GK18070%40t8o.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="001225.html">
  11. <LINK REL="Next" HREF="001227.html">
  12. </HEAD>
  13. <BODY BGCOLOR="#ffffff">
  14. <H1>[cam.pm] Backups + next pubmeet, Re: Hangover over?</H1>
  15. <B>David Cantrell</B>
  16. <A HREF="mailto:cam.pm%40cam.pm.org?Subject=%5Bcam.pm%5D%20Backups%20%2B%20next%20pubmeet%2C%20Re%3A%20Hangover%20over%3F&In-Reply-To=20070421132115.GK18070%40t8o.org"
  17. TITLE="[cam.pm] Backups + next pubmeet, Re: Hangover over?">david at cantrell.org.uk
  18. </A><BR>
  19. <I>Sun Apr 22 00:14:32 BST 2007</I>
  20. <P><UL>
  21. <LI>Previous message: <A HREF="001225.html">[cam.pm] Backups + next pubmeet, Re: Hangover over?
  22. </A></li>
  23. <LI>Next message: <A HREF="001227.html">[cam.pm] Backups + next pubmeet, Re: Hangover over?
  24. </A></li>
  25. <LI> <B>Messages sorted by:</B>
  26. <a href="date.html#1226">[ date ]</a>
  27. <a href="thread.html#1226">[ thread ]</a>
  28. <a href="subject.html#1226">[ subject ]</a>
  29. <a href="author.html#1226">[ author ]</a>
  30. </LI>
  31. </UL>
  32. <HR>
  33. <!--beginarticle-->
  34. <PRE>Matthew Astley wrote:
  35. &gt;<i> I've just set Dad's Linux box up with dirvish. It's Perl &lt;/obperl&gt;
  36. </I>&gt;<i> and rsync. It keeps multiple copies of the source filesystems and
  37. </I>&gt;<i> uses hardlinks to economise on unchanged files.
  38. </I>
  39. rsnapshot is better, if only because I'll bribe you to use it with beer :-)
  40. &gt;<i> He's only dumping to another disk in the machine, but with the magic
  41. </I>&gt;<i> of ssh authorisation key pairs you can send it... somewhere else, if
  42. </I>&gt;<i> there is anywhere.
  43. </I>&gt;<i>
  44. </I>&gt;<i> But not if rsync can't cope with the UFS+ filesystem?
  45. </I>
  46. You mean HFS+ (as does the author of the message whose URL I deleted).
  47. Plain ol' rsync works just fine provided that you don't care about those
  48. stupid fork things. Thankfully, OS X avoids using them to a great
  49. extent - even Apple finally realised that they were a really dumb idea.
  50. Certainly ignoring them has never done me any harm in my backups
  51. (admittedly I mostly use UFS, which eschews such stupidity).
  52. There are hacked-up versions of rsync which add support for them. And
  53. another reason to use rsnapshot - I have an email in my mailbox from one
  54. of the lovely users who has written up in detail how to use it to back
  55. up Macs, which I'll be adding to the docs soon.
  56. &gt;<i> Not that Dirvish looks particularly easy to fit with encrypted storage
  57. </I>&gt;<i> that can't be peeked on the archiving side. Sigh.
  58. </I>
  59. Consider Box Backup or duplicity if you need encryption:
  60. <A HREF="http://www.fluffy.co.uk/boxbackup/">http://www.fluffy.co.uk/boxbackup/</A>
  61. <A HREF="http://duplicity.nongnu.org/">http://duplicity.nongnu.org/</A>
  62. Both have more features than dirvish or rsnapshot, but at the expense of
  63. making it a little more complicated to restore data.
  64. --
  65. David Cantrell | top google result for &quot;topless karaoke murders&quot;
  66. Anyone willing to give up a little fun for tolerance deserves neither
  67. </PRE>
  68. <!--endarticle-->
  69. <HR>
  70. <P><UL>
  71. <!--threads-->
  72. <LI>Previous message: <A HREF="001225.html">[cam.pm] Backups + next pubmeet, Re: Hangover over?
  73. </A></li>
  74. <LI>Next message: <A HREF="001227.html">[cam.pm] Backups + next pubmeet, Re: Hangover over?
  75. </A></li>
  76. <LI> <B>Messages sorted by:</B>
  77. <a href="date.html#1226">[ date ]</a>
  78. <a href="thread.html#1226">[ thread ]</a>
  79. <a href="subject.html#1226">[ subject ]</a>
  80. <a href="author.html#1226">[ author ]</a>
  81. </LI>
  82. </UL>
  83. <hr>
  84. <a href="http://cam.pm.org/list/listinfo/cam.pm">More information about the Cam.pm
  85. mailing list</a><br>
  86. </body></html>