Scheduled FULL Backup fails

Hi Liam

I'm sort of assuming you have checked this but we all have to start somewhere to resolve issues:

From the error you have posted it is suggesting a couple of things

1. Network connection between client and server is lost - probably unlikely as you say the incrementals all work OK as a group

2. The disk holding the client status log is full; just to full to allow a FULL backup but with sufficient space to allow an incremental

Windows:

SystemDrive\Program Files\Legato\nsr\logs

As I say just a first port of call

Mike

Thanks Mike.

No there are no network issues and there is plenty of disk space in the log directory.

On each client I see this entry in the daemon.log

39078 12/14/2009 1:03:23 PM  0 0 2 3956 3308 0 brh1cimbweb1 nsrexecd SYSTEM error: There is already a machine using the name: "vcpbubrh101.vcp.amer.dell.com". Either choose a different name for your machine, or delete the "NSR peer information" entry for "vcpbubrh101.vcp.amer.dell.com" on host: "brh1cimbweb1.vcp.amer.dell.com

I ran, from nsradmin, "delete type: NSR peer information; name: vcpbubrh101.vcp.amer.dell.com"

but rerunning the job again, I still got failures.

Hi Liam

So your 2nd posting was your original error and the orinal posting was the error you received since:

You have VSS entries in the error log so run

vssadmin list writers

to see current state of writer in question

Also have you run mminfo to determine job status, basically just to see if something did in fact run and no entry has been placed...

Mike

I just selected the VSS savesets as an example. I'm getting the same error from the C:\ & D:\ saveset.

But here are the VSS writer details

C:\Documents and Settings\admliam_guinane>vssadmin list writers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001 Microsoft Corp.

Writer name: 'System Writer'
   Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
   Writer Instance Id: {4a1a6e6d-3e14-4346-ad57-5ee3fe706e75}
   State: [1] Stable
   Last error: No error

Writer name: 'MSDEWriter'
   Writer Id: {f8544ac1-0611-4fa5-b04b-f7ee00b03277}
   Writer Instance Id: {d48cf38d-6539-4956-9a35-1b6d79b74e24}
   State: [1] Stable
   Last error: No error

Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {0949c055-32d9-4903-bcb1-2d3a9b69c230}
   State: [1] Stable
   Last error: No error

Writer name: 'Event Log Writer'
   Writer Id: {eee8c692-67ed-4250-8d86-390603070d00}
   Writer Instance Id: {a5d1db86-1aef-4e6e-ba93-270c68444824}
   State: [1] Stable
   Last error: No error

Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {ecab33b0-d1f3-4ff5-93bd-126b3591a736}
   State: [1] Stable
   Last error: No error

Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {fd2524af-bb36-4466-a819-a7af62b5392b}
   State: [1] Stable
   Last error: No error

Writer name: 'IIS Metabase Writer'
   Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
   Writer Instance Id: {2d21ebb0-82bc-4aaf-886a-8443e068e899}
   State: [1] Stable
   Last error: No error

and after my latest attempt I ran mminfo

C:\Documents and Settings\admliam_guinane>mminfo -c brh1cimbweb1 -t "1 hour ago"

volume        client       date      size   level  name
VCA308L3       brh1cimbweb1 12/15/2009 526 MB full  VSS SYSTEM FILESET:\
VCA335L3       brh1cimbweb1 12/15/2009 424  B full  VSS USER DATA:\
VCA335L3       brh1cimbweb1 12/15/2009 424  B full  VSS OTHER:\
VCA335L3       brh1cimbweb1 12/15/2009 2625 KB full VSS ASR DISK:\
VCA335L3       brh1cimbweb1 12/15/2009 23 MB  full  VSS SYSTEM BOOT:\
VCA335L3       brh1cimbweb1 12/15/2009 105 MB full  VSS SYSTEM SERVICES:\

C:\Documents and Settings\admliam_guinane>

I did do some further investigation and tried to delete the certificates under "Local Hosts" in NMC. But when I tried to select any of the affect client I got the error:

"Unable to connect to server. Authentication failed or no valid authentication methods supported by both client and server"

I was able to select non-affected clients under "Local Hosts" without issue.

I'm thinking its client corruption at this stage.

Just disable nsrauth on server & storage nodes (requires restart) and you should be fine.