Jean-Michel Beuken writes:
> I have a common config for all PC and particularly, for ShareName
>
> $Conf{SmbShareName} = ['SYSTEM$','DATA$','USERS$','E$'];
>
> when the share doesn't exist on a client, the remainder of backup fails :
>
> 2006-11-29 21:53:44 full backup started for share SYSTEM$
> 2006-11-29 22:15:31 full backup started for share DATA$
> 2006-11-29 22:15:33 Got fatal error during xfer (tree connect failed:
> NT_STATUS_BAD_NETWORK_NAME)
> 2006-11-29 22:15:38 Backup aborted (tree connect failed:
> NT_STATUS_BAD_NETWORK_NAME)
> 2006-11-29 22:15:39 Saved partial dump 0
>
> nevertheless I put this :
>
> $Conf{BackupZeroFilesIsFatal} = '0';
>
> the backup fails...
>
> is there a parameter or a method to carry on the backup nevertheless a
> 'NT_STATUS_BAD_NETWORK_NAME'
> error ?
No. If you ask for a share to be backed up, it is considered
a fatal error if you can't connect to that share.
$Conf{BackupZeroFilesIsFatal} only determines what happens with
an otherwise successful backup that has no files. That defaults
to on, since it usually means there is some underlying problem
(permissions, failed mount etc).
Craig
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
BackupPC-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/
