Assuming 'this' is the Access Denied issue...
I will check the server event log in the morning. The backup concerned is multi-gigabyte and takes nearly five hours. Needless to say it runs overnight.
I will run it tomorrow with debug level 3 assuming my aged memory cells remember after work tomorrow. I don't know from memory how many thousand files are involved, and the problem is on the W folders at the back end of the alphabet. If you have any suggestion about how big the level 3 log is per 1000 files it might help me to make sure there is enough disk space on the client. I might need to relocate the log file away from the crowded 20Gb system drive onto the large backup drive. But I'll try anyway if you can't get back.
Chris
PS If it is the smbclient -L bug, I now have a number for it, viz 437944.
Assuming 'this' is the Access Denied issue...
I will check the server event log in the morning. The backup concerned is multi-gigabyte and takes nearly five hours. Needless to say it runs overnight.
I will run it tomorrow with debug level 3 assuming my aged memory cells remember after work tomorrow. I don't know from memory how many thousand files are involved, and the problem is on the W folders at the back end of the alphabet. If you have any suggestion about how big the level 3 log is per 1000 files it might help me to make sure there is enough disk space on the client. I might need to relocate the log file away from the crowded 20Gb system drive onto the large backup drive. But I'll try anyway if you can't get back.
Chris
PS If it is the smbclient -L bug, I now have a number for it, viz 437944.
C