Well, at this point, given the near zero "community" support for the "community" edition of ZWC, I'm going to move away from it for my M$ systems and utilize Windows 10's backup utility to push client backups to my file server and let Amanda pick them up from there. I'm really not concerned about bare metal capabilities with the M$ clients. Since ZWC and the OS backup utility both rely on VSS, I'm pretty much getting the same thing AFAICT.
On Tue, Mar 27, 2018 at 3:43 PM, Chris Nighswonger < [email protected]> wrote: > Yes. Here is a DLE from my dislist: > > admin-asst-1.foo.bar "C:/Documents and Settings" { > zwc-compress > estimate server > exclude "C:\\Documents and Settings\\*\\Local Settings\\Temp" > > } > > > On Tue, Mar 27, 2018 at 1:20 PM, Paddy Sreenivasan < > [email protected]> wrote: > >> Have you configured the DLE the same way i.e, using scriptor.foo.bar as >> hostname in both cases? >> >> On Tue, Mar 27, 2018 at 3:05 AM, Chris Nighswonger < >> [email protected]> wrote: >> >>> Has Zamanda abandoned ZWC? >>> >>> On Thu, Mar 22, 2018, 9:09 AM Chris Nighswonger < >>> [email protected]> wrote: >>> >>>> Ping. >>>> >>>> >>>> On Sun, Mar 18, 2018 at 1:34 PM, Chris Nighswonger < >>>> [email protected]> wrote: >>>> >>>>> No takers? To be sure someone who works on the ZWC can comment on what >>>>> sorts of issues might cause this change in behavior. >>>>> >>>>> Kind regards, >>>>> >>>>> Chris >>>>> >>>>> On Mar 14, 2018 3:24 PM, "Chris Nighswonger" < >>>>> [email protected]> wrote: >>>>> >>>>>> Thanks Paddy. I also had to restart the ZWC service to make the log >>>>>> level change effective. >>>>>> >>>>>> So maybe someone who works on the ZWC code can explain what operation >>>>>> might account for the following differences in log entries. Both are from >>>>>> the same machine. The backup began failing with the 18/1/2018 run. I >>>>>> wonder >>>>>> if ZWC is doing some sort of name resolution here which suddenly began to >>>>>> fail? On the client, nslookup results are correct both ways (see below). >>>>>> This same failure occurs on all of my ZWC installs. >>>>>> >>>>>> ZWC working fine: >>>>>> >>>>>> 4424:384:17/1/2018:12:59:36:548::CZWCJobHandler : Entering >>>>>> ExecuteValidateServerJob >>>>>> 4424:384:17/1/2018:12:59:36:548::CZWCJobHandler : Server address to >>>>>> be validated from the list of authentic server = 192.168.x.x >>>>>> 4424:384:17/1/2018:12:59:36:548::CZWCJobHandler : Server name = >>>>>> scriptor.foo.bar >>>>>> 4424:384:17/1/2018:12:59:36:548::CZWCJobHandler : Authentic Server >>>>>> name = scriptor.foo.bar >>>>>> 4424:384:17/1/2018:12:59:36:548::CZWCJobHandler : Leaving >>>>>> ExecuteValidateServerJob >>>>>> >>>>>> ZWC borking: >>>>>> >>>>>> 5692:12004:14/3/2018:14:54:9:706::CZWCJobHandler : Entering >>>>>> ExecuteValidateServerJob >>>>>> 5692:12004:14/3/2018:14:54:9:706::CZWCJobHandler : Server address to >>>>>> be validated from the list of authentic server = 192.168.x.x >>>>>> 5692:12004:14/3/2018:14:54:9:706::CZWCJobHandler : Server name = >>>>>> 192.168.x.x >>>>>> 5692:12004:14/3/2018:14:54:9:706::CZWCJobHandler : Authentic Server >>>>>> name = scriptor.foo.bar >>>>>> 5692:12004:14/3/2018:14:54:9:706::CZWCJobHandler : Server Validation >>>>>> Failed - Server 192.168.x.x With IP 192.168.x.x is not registered >>>>>> 5692:12004:14/3/2018:14:54:9:706::CZWCJobHandler : Leaving >>>>>> ExecuteValidateServerJob >>>>>> 5692:12004:14/3/2018:14:54:9:706::CZWCJobHandler:: Exiting >>>>>> ExecuteJob with status = 65535 >>>>>> >>>>>> Client-side nslookup: >>>>>> >>>>>> PS C:\Program Files\Zmanda\Zmanda Client for Windows Community >>>>>> Edition(x64)\bin> nslookup 192.168.x.x >>>>>> Server: UnKnown >>>>>> Address: 192.168.y.y >>>>>> >>>>>> Name: scriptor.foo.bar >>>>>> Address: 192.168.x.x >>>>>> >>>>>> PS C:\Program Files\Zmanda\Zmanda Client for Windows Community >>>>>> Edition(x64)\bin> nslookup scriptor.foo.bar >>>>>> Server: UnKnown >>>>>> Address: 192.168.x.x >>>>>> >>>>>> Name: scriptor.foo.bar >>>>>> Address: 192.168.x.x >>>>>> >>>>>> PS C:\Program Files\Zmanda\Zmanda Client for Windows Community >>>>>> Edition(x64)\bin> >>>>>> >>>>>> Kind regards, >>>>>> Chris >>>>>> >>>>>> >>>>>> On Fri, Mar 9, 2018 at 10:46 AM, Paddy Sreenivasan < >>>>>> [email protected]> wrote: >>>>>> >>>>>>> >>>>>>> 1. Open the ZWC Config Utility: Start Menu → All Programs → >>>>>>> Zmanda → Zmanda Client for Windows → ZWC Config Utility >>>>>>> 2. Select the Logging tab >>>>>>> 3. Set Log Level to 5 >>>>>>> 4. Click Save >>>>>>> 5. Click Exit >>>>>>> >>>>>>> >>>>>>> >>>>>>> On Fri, Mar 9, 2018 at 5:59 AM, Chris Nighswonger < >>>>>>> [email protected]> wrote: >>>>>>> >>>>>>>> Jean-Louis can you help with this? Is there a way to up the >>>>>>>> verbosity level of the ZWC log? >>>>>>>> >>>>>>>> >>>>>>>> On Tue, Feb 27, 2018 at 10:43 AM, Chris Nighswonger < >>>>>>>> [email protected]> wrote: >>>>>>>> >>>>>>>>> No takers? >>>>>>>>> >>>>>>>>> The ZWC is always a hard one to gin up help for. >>>>>>>>> >>>>>>>>> An additional piece of information: DNS resolution seems to be >>>>>>>>> working fine both server and client side. >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> On Fri, Feb 23, 2018 at 8:34 AM, Chris Nighswonger < >>>>>>>>> [email protected]> wrote: >>>>>>>>> >>>>>>>>>> Any thoughts on what might be going on here? >>>>>>>>>> >>>>>>>>>> Last week I began to have numerous Win10 clients failing in this >>>>>>>>>> fashion: >>>>>>>>>> >>>>>>>>>> backup@scriptor:/home/manager amcheck -c campus shipping.foo.bar >>>>>>>>>> >>>>>>>>>> Amanda Backup Client Hosts Check >>>>>>>>>> -------------------------------- >>>>>>>>>> ERROR: shipping.foo.bar: Server validation Failed. Please >>>>>>>>>> register server with client. >>>>>>>>>> Client check: 1 host checked in 0.072 seconds. 1 problem found. >>>>>>>>>> >>>>>>>>>> Taking a look at the ZWC debug log on that client, I see the >>>>>>>>>> following: >>>>>>>>>> >>>>>>>>>> 11020:9144:23/2/2018:08:16:7:22::CZWCJobHandler : Entering >>>>>>>>>> ExecuteValidateServerJob >>>>>>>>>> 11020:9144:23/2/2018:08:16:7:22::CZWCJobHandler : Server address >>>>>>>>>> to be validated from the list of authentic server = 192.168.x.x >>>>>>>>>> 11020:9144:23/2/2018:08:16:7:22::CZWCJobHandler : Server name = >>>>>>>>>> 192.168.x.x >>>>>>>>>> 11020:9144:23/2/2018:08:16:7:22::CZWCJobHandler : Authentic >>>>>>>>>> Server name = scriptor.foo.bar >>>>>>>>>> 11020:9144:23/2/2018:08:16:7:22::CZWCJobHandler : Server >>>>>>>>>> Validation Failed - Server 192.168.x.x With IP 192.168.x.x is not >>>>>>>>>> registered >>>>>>>>>> 11020:9144:23/2/2018:08:16:7:22::CZWCJobHandler : Leaving >>>>>>>>>> ExecuteValidateServerJob >>>>>>>>>> >>>>>>>>>> However, the server is registered with the client: >>>>>>>>>> >>>>>>>>>> Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Zmanda\ZWC\1.0\Install\Servers >>>>>>>>>> value is 'scriptor.foo.bar' >>>>>>>>>> >>>>>>>>>> If I add the server IP (192.168.x.x) to the list of registered >>>>>>>>>> Servers, everything checks out fine: >>>>>>>>>> >>>>>>>>>> backup@scriptor:/home/manager amcheck -c campus shipping.foo.bar >>>>>>>>>> >>>>>>>>>> Amanda Backup Client Hosts Check >>>>>>>>>> -------------------------------- >>>>>>>>>> Client check: 1 host checked in 0.071 seconds. 0 problems found. >>>>>>>>>> >>>>>>>>>> (brought to you by Amanda 3.3.6) >>>>>>>>>> >>>>>>>>>> And the ZWC debug log says: >>>>>>>>>> >>>>>>>>>> 11020:8956:23/2/2018:08:21:17:29::CZWCJobHandler : Entering >>>>>>>>>> ExecuteValidateServerJob >>>>>>>>>> 11020:8956:23/2/2018:08:21:17:29::CZWCJobHandler : Server >>>>>>>>>> address to be validated from the list of authentic server = >>>>>>>>>> 192.168.2.203 >>>>>>>>>> 11020:8956:23/2/2018:08:21:17:29::CZWCJobHandler : Server name = >>>>>>>>>> 192.168.x.x >>>>>>>>>> 11020:8956:23/2/2018:08:21:17:29::CZWCJobHandler : Authentic >>>>>>>>>> Server name = scriptor.foo.bar >>>>>>>>>> 11020:8956:23/2/2018:08:21:17:29::CZWCJobHandler : Authentic >>>>>>>>>> Server name = 192.168.x.x >>>>>>>>>> 11020:8956:23/2/2018:08:21:17:29::CZWCJobHandler : Leaving >>>>>>>>>> ExecuteValidateServerJob >>>>>>>>>> >>>>>>>>>> Thanks, >>>>>>>>>> Chris >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>> >> >
