Backup Central

Hello-

I would like some assistance ruminating on some best practices for
designing a backup solution...

here is what one of our clients have:

Two locations - an office and a COLO with servers at both.

Right now we have them running rSnapshot (3 times a day, daily, weekly)
from a single server at the office with a different script for each
server, to have bwlimit control over the different boxes.

There are two reasons for the bandwidth limiting, performance and the COLO
is on a metered line.

With that in mind I am wondering if it would make sense to do the daily
rsnapshot to a local server and then ship them over to the office from the
COLO on a weekly basis. I am thinking that if I am only doing one big
exchange a week I could both up the bwlimit and not worry about the
perfomance on servers that are being backed up because I am rsyncing an
offline backup.

That being said, what would you recommend I backup on the COLO's rSnapshot
server, the contents of ./snapshot or something more like the contents of
./snapshot/daily.6?

This is a great bit of work and has already saved my bacon a couple of
times.

Thanks in advance,

Timur Snoke
Intalgent
107 First Street South, Suite 202
Charlottesville, VA 22902
T: (434) 977-5152 ext. 104
F: (866) 812-5291
timur.snoke < at > intalgent.com


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
rsnapshot-discuss mailing list
rsnapshot-discuss < at > lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rsnapshot-discuss

timur.snoke < at > intalgent.com wrote:

here is what one of our clients have:

Two locations - an office and a COLO with servers at both.

Right now we have them running rSnapshot (3 times a day, daily, weekly)
from a single server at the office with a different script for each
server, to have bwlimit control over the different boxes.

There are two reasons for the bandwidth limiting, performance and the COLO
is on a metered line.

With that in mind I am wondering if it would make sense to do the daily
rsnapshot to a local server and then ship them over to the office from the
COLO on a weekly basis. I am thinking that if I am only doing one big
exchange a week I could both up the bwlimit and not worry about the
perfomance on servers that are being backed up because I am rsyncing an
offline backup.

That being said, what would you recommend I backup on the COLO's rSnapshot
server, the contents of ./snapshot or something more like the contents of
./snapshot/daily.6?


I thought I knew the answer, but upon reflection, it is not so clear to
me. If there is little churn in the files, then I would not bother
with the local snapshots. If the COLO is very busy, then local backups
that use full bandwidth would minimize error 24 when a file has changed
out from underneath rsync/rsnapshot. If you have tons of CPU to spare,
you could go for local snapshotting and post-process the collection in a
way that would save on bandwidth (hard link identical files,
compression) before rsyncing across the network. If you opt for the
local backups, when you rsync them across, I would do each hourly.x,
daily.x, weekly.x chunk separately do reduce rsync's memory and
processing needs.

--Carl Boe


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
rsnapshot-discuss mailing list
rsnapshot-discuss < at > lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rsnapshot-discuss