Hi Maarten and Ty,
On Fri, 4 Aug 2006, Maarten Bezemer wrote:
It's not always known beforehand what the source contains. Since
rdiff-backup is already checking for other filesystem capabilities, it
would make some sense to check for and escape directories (or
files!!) named rdiff-backup-data
Hi J,
I think I did a bone-headed thing. I excluded the rdiff-backup-data
path in the backup. I probably want that path in order to do
incremental restores... is that correct?
I'm sorry, I don't understand. What command did you use, and why are you
worried about the results?
Cheers,
I think I did a bone-headed thing. I excluded the rdiff-backup-data
path in the backup. I probably want that path in order to do
incremental restores... is that correct?
Thanks for answering what possibly is the dumbest question posed to this
group,
--J.
On Fri, 4 Aug 2006, J. Norment wrote:
I think I did a bone-headed thing. I excluded the rdiff-backup-data
path in the backup. I probably want that path in order to do
incremental restores... is that correct?
Hmm.. never tried that. You mean you have an --exclude rdiff-backup-data
on your
Maarten Bezemer wrote:
On Fri, 4 Aug 2006, J. Norment wrote:
I think I did a bone-headed thing. I excluded the rdiff-backup-data
path in the backup. I probably want that path in order to do
incremental restores... is that correct?
Hmm.. never tried that. You mean you have an
On Fri, 4 Aug 2006, Maarten Bezemer wrote:
This made me think about something related: what happens if the tree
you're backup up contains an rdiff-backup-data directory? Will it be
escaped? Will it be ignored? Will it be used and screw up the whole thing?
danger danger. you'll be unhappy if
