WG: [BackupPC-users] Rsyncing

[Patrick N. - F. S. J. <ne...@fu...>]

hello,

see inline.

> -----Urspr=FCngliche Nachricht-----
> Von: cba...@us...
> [mailto:cba...@us...]=20
> Gesendet: Montag, 3. November 2003 07:23
> An: Patrick Neuner - Futureweb St. Johann
> Cc: bac...@li...
> Betreff: Re: [BackupPC-users] Rsyncing=20
>=20
>=20
> "Patrick Neuner - Futureweb St. Johann" writes:
>=20
> > I tried to figure that out, but I am not sure if it is possible:
> >
> > I want to backup one machine that has about 50-100 gb data. It is a
> > Redhat machine, so I can use rsync.
> >
> > Now, due this machine is at another location, I only have about
> > 2.5mbit as connection speed.
> >
> > Usually I would use rsync to sync data to the backup
> machine, causes
> > me only changes to be moved over. (but not the incremental restore
> > functions).
> >
> > Now, I can do full backups and incremental backups at backuppc. The
> > incemental would do it aswell, but if I want to do another full=20
> > backup, I guess it will have to backup all data again to the backup=20
> > machine, correct?
>=20
> No.  A full backup with rsync is still "efficient".  Only
> checksums and file deltas are exchanged.  The difference is=20
> that rsync incrementals skip files that have identical=20
> attributes (mtime, size, owner, permissions). Rsync fulls use=20
> the --ignore-times
> option: the block checksums for every file are sent (even if=20
> the attributes are the same), and the client's rsync checks=20
> the contents of every file.  Any deltas are sent back.
>=20
> So the advantage of a full is that the file contents are
> fully checked, unlike an incremental.

So do I understand that correct, that if a Full-Backup exists,=20
some incremental ones,=20
and I do another full backup, that it does "not" copy all files over =
again, but only changed once ?

because that would solve the issue and no manual intervention would be =
necessary.=20

thanks
patrick



>=20
> > Is there a way (also if I do it manually) to first have like copied
> > over the full backup from backuppc, probably rsync it and have it=20
> > named as full backup within backuppc? Due to mangled files=20
> that won't
> > be that easy, but suggestions are welcome.
>=20
> You could create a local image of the remote client machine.
> Then use a local rsync to pick up the files with a full dump.=20
>  You'll need the share name to be the same as the client=20
> machine.  Otherwise the real backup of the remote machine=20
> will think every file is new.
>=20
> Craig
>=20