On 29.01.2018 12:32, Zielke, Julian, NLI wrote:
Talking about the point on not saving the rest of the archives: There is afaik
no current way to tell BackuPC to stop the backup on this share, execute
post-share using xferOK = 0 and continue
with the rest of the backups. So we'll keep it that way. Maybe this could be a
nice feature implementation to skip a share on xfer errors and return xferOK=0.
This would be a perfect way to have
a solution of partitial backups AND notification in both ways.
On the second thought, skipping certain shares is an overkill. Probably in case
if we want treat shares differently we should just create different hosts for
them.
I suggest to create an option in the configuration of the tar xfer method (bool
/ checkbox) so the user can decide whether
to abort on Xfer errors or not.
I agree with you. It would be nice to add a configuration option for that, but
for any xfer type, not only for tar xfer.
The options could be something like:
$Conf{xferErrsAreFatal} If any share had xfer errors then consider the dump bad
and mark it as partial
0 - no (default)
1 - yes
n - yes if $stat{xferErrCnt} >= n
$Conf{abortOnXferErrs} abort the dump instead of marking it partial if
$Conf{xferErrsAreFatal} condition is met.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
BackupPC-users mailing list
[email protected]
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
