AW: [rdiff-backup-users] [PATCH] Sparse file support

2011-01-08 Thread D. Kriesel
Hi Dominic,

this is certainly a cool idea, only I have no Python developer experience und 
therefore you for sure don't want me as a project member :-). Currently, I just 
try to help out people on the mailinglist from my experience as a computer 
scientist and rdiff-backup user. Anyway, there is hope. I am currently 
preparing my PhD project, and plan to use python for some scripting. Once I 
feel my understanding of python and the internals of rdiff-backup is good 
enough, I will file a request as you said.

David

 AFAIK Andrew's last posting on this newsgroup was March 2009, and his
 last entry in CVS was January 2010, which is indeed the last entry by
 anyone. Josh (who also created the excellent rdiffWeb GUI front-end) was
 last seen here April 2010. You could try requesting to become a project
 member
 http://savannah.nongnu.org/my/groups.php?words=rdiff-
 backup#searchgroup?
 
 Dominic
 



___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki


Re: AW: [rdiff-backup-users] [PATCH] Sparse file support

2011-01-08 Thread Dominic Raferd

On 08/01/11 10:31, D. Kriesel wrote:

Hi Dominic,

this is certainly a cool idea, only I have no Python developer experience und 
therefore you for sure don't want me as a project member :-). Currently, I just 
try to help out people on the mailinglist from my experience as a computer 
scientist and rdiff-backup user.

ditto (except the scientist bit)

  Anyway, there is hope. I am currently preparing my PhD project, and plan to 
use python for some scripting. Once I feel my understanding of python and the 
internals of rdiff-backup is good enough, I will file a request as you said.
Thanks. In the meantime, if there are any python programmers who use and 
value rdiff-backup and could offer their services to the project, the 
rest of us would be very grateful I'm sure.


Dominic

AFAIK Andrew's last posting on this newsgroup was March 2009, and his
last entry in CVS was January 2010, which is indeed the last entry by
anyone. Josh (who also created the excellent rdiffWeb GUI front-end) was
last seen here April 2010. You could try requesting to become a project
member
http://savannah.nongnu.org/my/groups.php?words=rdiff-
backup#searchgroup?

Dominic






___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki


Re: [rdiff-backup-users] Re: What happens if you add a --exclude to an existing rdiff-backup?

2011-01-08 Thread Dominic Raferd

Thanks David, that is helpful.

It would be good if there was a way of removing a subset of data from 
the entire repository. So let's say I put a 500GB folder in /home by 
accident and it has gone into the repository and is bloating it. I can 
exclude it from my future rdiff-backup runs but the folder will still be 
held as snapshot[s]. If I run --remove-older-than it will remove all 
data older than whenever, but I want to keep all the other stuff and 
just remove this folder (and its contents).


Quite a common scenario but rdiff-backup can't handle it (AFAIK) and I 
don't know of a reliable workaround (apart from: get a bigger disk for 
the repository).


Dominic

On 08/01/11 10:15, D. Kriesel wrote:

Hi, according to rdiff-backups doc, excluded files are just treated as if they 
would not exist. This means that a snapshot of such a file will be created in 
the metadata once a backup run with the exclusion is performed, and the file 
will be deleted from the mirror data.llyu

Cheers, david



Dominic Raferddomi...@timedicer.co.uk  schrieb:


I agree that makes sense in terms of the question in the body of your
posting. But the subject of your posting was a slightly different
question: 'What happens if you add a --exclude to an existing
rdiff-backup?'

If a week ago you added  --exclude /home/fred to your rdiff-backup line

backing up /home, will /home/fred now be removed from the destination
by
a --remove-older-than 5D run?

In other words, if you add exclusion criteria to an existing
rdiff-backup run, are the copies of the newly-excluded files removed

from the main repository and placed in the increments folder [in which

case they *would* be removed by a subsequent --remove-older-than
command], or are they just left where they were [in which case they
*wouldn't* be]?

I don't know the answer, but if someone does I would be interested.

Dominic

On 07/01/11 21:31, Chris G wrote:

On Fri, Jan 07, 2011 at 02:38:45PM -0500, cov...@ccs.covici.com

wrote:

When the files are deleted, they are copied to the increments folder

and

kept till they are removed by --remove-older-than.


That makes sense, thank you.


Chris Gc...@isbd.net   wrote:


If you delete files/directories from the 'source' of an

rdiff-backup

will they get removed from the destination with an appropriate
--remove-older-than run?

For example if rdiff-backup has been backing up a hierarchy with a
directory called 'tmp' for a while and then the 'tmp' directory is
removed can one get rdiff-backup to remove the 'tmp' backups 7 days
later by --remove-older-than 7D.

  From the man page it sounds as if deleted files *will* be

removed:-

Note that snapshots of deleted files are covered by

this  opera-

tion.  Thus if you deleted a file two weeks ago,

backed up imme-

diately afterwards, and then  ran  rdiff-backup

with  --remove-

older-than  10D  today,  no  trace  of  that  file

would remain.

Finally, file selection options such as --include

and  --exclude

don't affect --remove-older-than.

But this bit from the examples section of the documentation worries

me

slightly:-

  Note that an existing file which hasn't changed for a year

will still be

  preserved. But a file which was deleted 15 days ago cannot be

restored

  after this command is run.

--
Chris Green





___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki


[rdiff-backup-users] Re: Re: What happens if you add a --exclude to an existing rdiff-backup?

2011-01-08 Thread Chris G
On Sat, Jan 08, 2011 at 08:39:15AM +, Dominic Raferd wrote:
 I agree that makes sense in terms of the question in the body of
 your posting. But the subject of your posting was a slightly
 different question: 'What happens if you add a --exclude to an
 existing rdiff-backup?'
 
Oops, I meant to change that, I haven't added an exclude to the
rdiff-backup command.  What I have is an rsync across to the backup
machine and then the rdiff-backup runs there.  I though I had a --exclude
in the rdiff-backup run but it's actually in the rsync.  I only noticed
this when I started composing the E-Mail and, as I said, forgot to
change the subject.


 If a week ago you added  --exclude /home/fred to your rdiff-backup
 line backing up /home, will /home/fred now be removed from the
 destination by a --remove-older-than 5D run?
 
 In other words, if you add exclusion criteria to an existing
 rdiff-backup run, are the copies of the newly-excluded files removed
 from the main repository and placed in the increments folder [in
 which case they *would* be removed by a subsequent
 --remove-older-than command], or are they just left where they were
 [in which case they *wouldn't* be]?
 
 I don't know the answer, but if someone does I would be interested.
 
Yes, it's the question I originally *thought* I needed to ask.

-- 
Chris Green

___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki


AW: [rdiff-backup-users] Re: Re: What happens if you add a --exclude to an existing rdiff-backup?

2011-01-08 Thread D. Kriesel
 Oops, I meant to change that, I haven't added an exclude to the
 rdiff-backup command.  What I have is an rsync across to the backup
 machine and then the rdiff-backup runs there.  I though I had a --exclude
 in the rdiff-backup run but it's actually in the rsync.  I only noticed
 this when I started composing the E-Mail and, as I said, forgot to
 change the subject.

If you use rsync with exclusions AFTER rdiff-backup, what you get are
inconsistencies in the final rdiff repository and therefore pain in the ass
when verifying it.
If you first rsync and then rdiff-backup, you should be fine whatsoever.

Long story short: Let only rdiff-backup perform operations whithin the
rdiff-backup repository. If you rsync the repository to some place excluding
parts of it, it will be like you deleted files out of it.


___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki


AW: [rdiff-backup-users] Re: What happens if you add a --exclude to an existing rdiff-backup?

2011-01-08 Thread D. Kriesel
 It would be good if there was a way of removing a subset of data from
 the entire repository. So let's say I put a 500GB folder in /home by
 accident and it has gone into the repository and is bloating it. I can
 exclude it from my future rdiff-backup runs but the folder will still be
 held as snapshot[s]. If I run --remove-older-than it will remove all
 data older than whenever, but I want to keep all the other stuff and
 just remove this folder (and its contents).

RIGHT! This is the ONE feature I miss about rdiff-backup and which is my 
largest concern about it. I'll try to put it in a formalized way: 
I want to be able to remove an entire subtree of an rdiff-backup repository 
_and every single trace of it in the metadata_.

This is not possible right now, as far as I know. If this was possible, it 
would just be great.

In my opinion, one would just have to remove 
   * any diffs, snapshots, increment, dir and missing markers and similar files 
of the subtree (easy because you just would have to delete a subtree within the 
metadata plus some few additional files)
   * any trace of any file within the subtree to delete in the zipped backup 
table of content files.

Please correct me if I'm wrong. If anyone wants to implement this feature, It 
will gladly be my shout for a sixpack :-)

David



___
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki