This is but a single data point, but if others can provide some
additional data, it might help you triangulate what you want.
I'd also recommend 3ware over Areca - I've had 2 bad experiences with
Areca involving data loss - only one of which I could really blame on
the controller, but 3ware
You didn't say if it appeared as though data was coming across the wire
or not.
This is possibly the culprit:
$Conf{ClientTimeout} = 72000;
Timeout in seconds when listening for the transport program's
(smbclient, tar etc) stdout. If no output is received during this time,
then it is assumed
Peter,
For testing purposes, you may reduce the alarm period, but under
practical circumstances, it must be large enough that it doesn't cut off
backups that would finish, had they been given the time to collect
enough file information. The behavior also depends on the transport
mechanism
Peter Nearing wrote:
Aaron,
When I ran the command line that it's trying, the data isn't coming,
rsync is running on the client, but it stops there. The backuppc logs
state that it's saving the data as a partial, tho.
^^
If backuppc saves
Unfortunatly right now, I am rechecking backuppc's data partition, so I
can't check the setup, and the client is in windows (it's in kingston, on...
and I am in Prince George, BC, so I can't just walk over and kick them off,
grr...) But the backups are split up, one fs is the '/', excluding
