http://blog.shwango.com/2005/01/07/rsync-rocks/ life, love and some other stuff... Sun, 03 May 2009 17:48:34 -0400 http://wordpress.org/?v=2.8.4 hourly 1 http://blog.shwango.com/2005/01/07/rsync-rocks/comment-page-1/#comment-142 osterday Mon, 10 Jan 2005 15:05:21 +0000 http://blog.shwango.com/2005/01/07/rsync-rocks/#comment-142 For retension I was just thinking of tarring and gzipping the current backup once a week. You could then burn it off to CD or DVD or even tape if you wanted and then delete the tgz file. And for code, developers _should_ be using CVS or Subversion, which would have some of that built in. (We are planning to use Subversion soon, but aren't there just yet.) For retension I was just thinking of tarring and gzipping the current backup once a week. You could then burn it off to CD or DVD or even tape if you wanted and then delete the tgz file. And for code, developers _should_ be using CVS or Subversion, which would have some of that built in. (We are planning to use Subversion soon, but aren’t there just yet.)

]]> http://blog.shwango.com/2005/01/07/rsync-rocks/comment-page-1/#comment-141 Henry Fri, 07 Jan 2005 20:21:03 +0000 http://blog.shwango.com/2005/01/07/rsync-rocks/#comment-141 Thats what I have been telling ya. Rsync does indeed rock. The only issue with using it for backups is retention... If you sync every day, then you only have a retention of one day by definition. One possible solution would be to just have 2 backup sets, one that runs every day and the other that goes once a month or byweekly. Thats still not the best solution because you have to at least double your backup size, and retention varies depending on when in the backup cycle it is when you want to do a restore. Rsync has --backup and --suffix flags that can be set to rename files to be overwritten on teh remote size. By programmatically setting these flags with a perl or bash script when rsync is called, you could achieve unlimited retention and version control all at the same time... I'd like to see a tape system do that! Thats what I have been telling ya. Rsync does indeed rock. The only issue with using it for backups is retention… If you sync every day, then you only have a retention of one day by definition. One possible solution would be to just have 2 backup sets, one that runs every day and the other that goes once a month or byweekly. Thats still not the best solution because you have to at least double your backup size, and retention varies depending on when in the backup cycle it is when you want to do a restore. Rsync has –backup and –suffix flags that can be set to rename files to be overwritten on teh remote size. By programmatically setting these flags with a perl or bash script when rsync is called, you could achieve unlimited retention and version control all at the same time… I’d like to see a tape system do that!

]]>