Re: Recursion limits

[Colin Percival <cperciva@tarsnap.com>]

On 05/24/15 15:23, Bob wrote:
> I'll try and let  you know. What I found when I attempted the restore was that
> /usr/local/www  didn't drill all the way down into
> /usr/local/www/wordpress/wp-content/uploads/.../..../.../.../... The backup
> was missing some of the deepest directories. It similarly seemed to choke on
> /usr/local . Admittedly, that is not a useful backup path, but I did try it.
> Again, it didn't get all the directories. In this case it missed
> /usr/local/www/wordpress entirely. I will run the dry run and check the results.

Just to rule out the obvious: You know that tarsnap won't (by default) follow
symlinks, right?

Colin Percival

> 
> Thanks,
> Bob
> 
> On 5/24/2015 3:18 PM, Colin Percival wrote:
>> On 05/24/15 11:18, Bob wrote:
>>> I recently attempted a restore and discovered that my backup didn't go down
>>> the full directory tree for a couple of items. Is there a limit to the depth
>>> tarsnap will recurse?
>> Not one you should run into.  The only limits I'm aware of are the inevitable
>> ones (e.g., "paths must fit into RAM").
>>
>> Can you reproduce the scenario with `tarsnap -c -v --dry-run` (which should
>> list the objects which would be archived but not actually create an archive)?
>>
> 
> 
> 

-- 
Colin Percival
Security Officer Emeritus, FreeBSD | The power to serve
Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid