Re: [Duplicity-talk] Rsync Backend

[Richard Scott]

Hi Will,

The "remove-all-but-n-full" options removes all but leaves the following:

previous full backup and associated incremental chain.

current full backup and associated incremental chain.

This means you always have 1 full backup chain plus your current backup chain available.

However, the MySQL thing throws a spanner in the works...

I'm guessing that your running mysqldump each night to dump to a flat file? If so, duplicity will see this "flat file" as a brand new file (each night) and take a full backup of it (each night) :-( I think its something to do with the file having a different inode or something?

If anyone else on this list as a different view, please shout :-)

Rich

 

On Wed, 30 Dec 2009 10:45:18 +0000, william pink <address@hidden> wrote:

Hi Richard,

Thanks for the reply,

I thought that maybe the case in my situation I have Mysql backups which are full backups every evening and once these have completed I use duplicity to copy these to remote storage,
 if I use the full backup option with Duplicity it's going to duplicate data isn't? I did a full backup when I first run Duplicity now I am using incremental backups each evening but maybe this is the wrong thing to do?

If I use the "remove-all-but-n-full 1" it will remove all my incremental backups wouldn't it?

Many Thanks,
Will

On Wed, Dec 30, 2009 at 10:29 AM, Richard Scott <address@hidden> wrote:

Hi Will,

As far as I know, both scp:// and rsync:// transfer methods work in the same way. I don't believe that any of the special features of rsync are used during upload/download to the remote site so the "--delete" option won't help.

Also, you can only safely delete files on the remote system that are nothing to do with the current backup chain i.e. a backup chain is any file uploaded since you last did a full backup. All these files are linked and to restore a single file could need any one of these files for a partial bit of data as any incremental backups you run since the last full backup will only store the changed parts in a file since the last backup run and not the whole file.

If you want to save space on your remote site, you can the "remove-all-but-n-full 1" option to duplicity to remove anything but one previous full backup and your current backup chain.

It is safer to get duplicity to delete stuff, rather than doing it yourself.

Hope that helps,

Rich

On Wed, 30 Dec 2009 10:09:08 +0000, william pink <address@hidden> wrote:

Hi,

I am currently using Duplicity with the scp backend to copy over the files to my remote storage, I noticed that it also offers the Rsync backend which is great but I was wondering if there was anyway to incorporate the Rsync --delete feature or getting duplicity to compare both the local and remote directorys and mirror this somehow?

Many Thanks,
Will

 

_______________________________________________
Duplicity-talk mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/duplicity-talk