Re: [BackupPC-users] Redundant calls to DumpPostUserCmd

[Craig B. <cba...@us...>]

Chris Stone writes:

> I needed to include the "if (! -e "$archpath")" block in the script  
> since I found that if the backup and archive writing go on for more  
> than a couple hours, DumpPostUserCmd gets called again for some  
> reason, and the script would start writing to the same directory and  
> screw up the archive. With the if block, though, I at least get a  
> complete archive written.
> 
> Still, however, an issue remains since that second invocation of  
> DumpPostUserCmd exits with a non-zero even though the actual backup  
> was successful, and so the entire backup is rendered "partial". That  
> client then gets hit for another full at the next window (and the  
> cycle repeats).
> 
> My questions then are:
> 
> Why might I be getting multiple calls to DumpPostUserCmd, and how can  
> I prevent that?

I can't see how DumpPostUserCmd can get run twice, since only
a single BackupPC_dump can be run per client.  That said, it
could be caused by $Conf{ClientTimeout} aborting the first run
during the archive phase.  I'd try increasing $Conf{ClientTimeout}
by a significant factor.

Craig