On 2019-06-04 07:33, Philip Parsons (Velindre - Medical Physics) wrote:
> Thanks for the reply Michael.
>
> I've tried to restore to another share on another server and am getting
> NT_STATUS_BAD_NETWORK_NAME
>
> I don't want to overwrite the existing data, I just want to be able to
> download data to another share so that I can QA our backups.
>
> Running: /usr/bin/smbclient \\\\destinationserver\\share -U domainaccount -E
> -d 1 -c tarmode\ full -mSMB3 -Tx -
>
> Running: /usr/local/BackupPC/bin/BackupPC_tarCreate -h sourceserver -n 510 -s
> sourceshare -t /sourcefolder
>
> Xfer PIDs are now 104823,104824
>
> WARNING: The "syslog" option is deprecated
>
> [ skipped 1 lines ]
>
> This backup will fail because: tree connect failed:
> NT_STATUS_BAD_NETWORK_NAME
>
> tree connect failed: NT_STATUS_BAD_NETWORK_NAME
>
> [ skipped 1 lines ]
>
> tree connect failed: NT_STATUS_BAD_NETWORK_NAME
>
> readOutput: sysread returns 0 and got EOF (exit ok = , )
>
> XferErr Non-zero exit status from smbclient
>
> restore failed: tree connect failed: NT_STATUS_BAD_NETWORK_NAME
>
> thanks again for any advice!
>
> Phil
Samba errors are maddeningly unspecific. In this case, the error
translates to "something about that share ain't working for me." It
could be anything from the share name being misspelled, or the wrong
part of the tree, or permission errors.
At any rate, the simplest way to diagnose this is to start with what the
share names are:
smbclient -L //destinationserver
This should give you a list of valid shares -- if the sharename you
tried doesn't exactly match one of the shares in that list, viola, that
is the trouble. (N.B. I do mean *exactly.* There's no support for
joining the tree at a different point in the hierarchy.)
_______________________________________________
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
