From: Ryan J. <rje...@gm...> - 2006-05-22 15:31:17
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> <title></title> </head> <body bgcolor="#ffffff" text="#000000"> Hi Les,<br> <br> Thank you for your feedback. I have a few questions that may help me understand the reasons for your options.<br> <br> I thought one option might be to use an offsite instance of backuppc to rsync copy the file pool or a tar archive. It sounds like you're talking about rsyncing to the original files on the various clients... Is this the recommended technique because an rsync, like I'm suggesting, wouldn't get any speed benefits? I'm thinking the compression in the tar will change the file with each archive and maybe the file pool changes a lot too (rendering speed improvements in rsync useless).<br> <br> Thanks again for the response.<br> Ryan<br> <blockquote cite="mid...@le..." type="cite"> <pre wrap="">On Fri, 2006-05-19 at 17:25, Ryan Jewell wrote: </pre> <blockquote type="cite"> <pre wrap="">I've read different options and searched past posts. Could someone help me find/determine a fitting offsite backup strategy. </pre> </blockquote> <pre wrap=""><!----> The simple way is to run a completely independent instance of backuppc from the offsite location using a VPN if necessary to reach all the hosts. You might need to do the initial full runs with the machine on site, then move it to the offsite location - or you might be able to get the fulls over a weekend. If that isn't practical, look at one of the ways to do image copies of your local archive to an external drive that can be rotated offsite. </pre> </blockquote> <br> </body> </html> |