On 27/06/12 00:02, shorvath wrote:
> Hi Timothy,
>
> Thanks for your comments, unfortunately however I think you're missing my
> point.
> I very much like the way Backuppc handles backup, dedupe etc. and to use this
> on the local site to handle the backups of each individual client would be
> preferred, plus it gives the client an interface to browse backups and do
> restores. (One of the main reasons I want to use it)
> However for remote backups (eg offsite) I want to be able to have and rsync
> style "snapshot" of the most recent backup.
> I do not want to have to pull backups from my remote site to each individual
> server for this purpose because
> A) I'm already backing them up from the local site backup server and I don't
> want to back them up twice (more io/cpu and it'll take longer) These servers
> are production and heavily used with a lot of daily changes.
> Keep in mind that the backup server is used just for backups so it can spend
> the whole day getting thrashed for all I care.
> and to be honest that just seems silly and more than a solution.
> B) I don't like having multiple entry points ..... actually no other points
> are needed. Point A is enough reason not to do it.
> I already achieve my needs currently by simply using rsync for both local and
> remote but as mentioned earlier I want a more elegant solution and I like
> backuppc and how it handles the local backups.
> If there is no way of exposing the latest backup of each host from the
> backuppc server either via a fuse module (that works) or other means then my
> solution to either stick to my current solution. eg rsync but spend some time
> refining it.
> or
> use something like rdiff-backup or rsnapshot.
> rdiff-backup will allow me to see the most recent "snapshot" but has it's
> caveats/pitfalls/complexities.
> Rsnapshot will do everything I need but maybe not the most efficient on space.
> Of course there are other...
> Bandwidth, not a problem, I can limit/shape that several ways.
You options that I can see are:
1. Script up a recover of each server to the backup server and then
rsync that to the remote host. This means you lose a chunk of space on
the backup server but is bandwidth efficient.
Something like:
BackupPC_tarCreate -h <host> -n -1 -s "<share name>" / |\
tar -C /path/to/localbackups/host -x -f -
and then:
rsync -avz /path/to/localbackups/ remotehost:/path/to/remotebackups/
This will cost you disk space on the backup server and some disk
bandwidth during the recover.
2. If bandwidth truely isn't an issue then you can simply recover the
latest backup into an ssh pipe something like this:
BackupPC_tarCreate -h <host> -n -1 -s "<share name>" / |\
ssh -c arcfour -C remotehost tar -C /path/to/remotebackups/host -x -f -
This will transfer the most recent backup via tar and ssh to the remote
host but this will transfer a full backup everytime.
This will hammer the cpu on the backup server to compress and encrypt
the transfer and also hammer your bandwidth both remote disk and network.
--
Tim Fletcher <tim AT night-shade.org DOT uk>
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
BackupPC-users mailing list
BackupPC-users AT lists.sourceforge DOT net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
|
