From: Les M. <les...@gm...> - 2013-02-28 19:03:17
|
On Thu, Feb 28, 2013 at 9:53 AM, upen <upe...@gm...> wrote: Not sure I can help much with specifics here, but I think those 'Unknown parameter' errors are harmless and from a samba4 based winexe seeing your samba3 configs. > CheckHostAlive: returning 0.353 > Executing DumpPreUserCmd: /tmp/backuppc/preusercmd.sh a.b.c.d > cmdSystemOrEval: about to system /tmp/backuppc/preusercmd.sh a.b.c.d > Unknown parameter encountered: "valid users" > Ignoring unknown parameter "valid users" > Unknown parameter encountered: "valid users" > Ignoring unknown parameter "valid users" > Unknown parameter encountered: "public" > Ignoring unknown parameter "public" > Unknown parameter encountered: "writable" > Ignoring unknown parameter "writable" > Unknown parameter encountered: "valid users" > Ignoring unknown parameter "valid users" > Unknown parameter encountered: "public" > Ignoring unknown parameter "public" > Unknown parameter encountered: "writable" > Ignoring unknown parameter "writable" > Unknown parameter encountered: "valid users" > Ignoring unknown parameter "valid users" > Unknown parameter encountered: "public" > Ignoring unknown parameter "public" > Unknown parameter encountered: "writable" > Ignoring unknown parameter "writable" > Microsoft (R) Windows Script Host Version 5.7 > Copyright (C) Microsoft Corporation. All rights reserved. > > > /tmp/backuppc/preusercmd.sh: line 13: at: command not found That seems odd. I don't see an 'at' command in the version of the script I found. And most systems should have an 'at' in the path anyway. > full backup started for directory C (baseline backup #3) > started full dump, share=C > Connected to a.b.c.d:873, remote version 30 > Negotiated protocol version 28 > Error connecting to module C at a.b.c.d:873: auth failed on module C And this may be your real problem. Does your authentication work if you just back up the normal C$ share without the VSS stuff? -- Les Mikesell les...@gm... |