cbw71
asked on
SBS 2011 Server Backup Fails at the same point
Out of the blue my SBS 2011 server backup quit working. I have it set to back up to an attached USB hard drive. A couple weeks ago, it failed one evening and I have not been able to figure out how to get it working again.
I have reformatted/renamed the USB drive and set up a new backup job.
When run as scheduled, I get this error:
Description: Backup
Backup Location: NORDIC0 2013_09_05 15:43 DISK_01
VSS Settings: VSS Copy Backup
Status: Failed
The system cannot find the file specified
and the backup did not even start.
When I select backup once from the menu, this is the result of that:
Description: Backup
Backup Location: NORDIC0 2013_09_05 15:43 DISK_01
VSS Settings: VSS Copy Backup
Status: Failed
The device is not ready
The backup ran for the System Reserved, C: drive and appears to stop at the same point for the D: drive 29.32 GB of 203.35 GB
I tried running the backup from an elevated command prompt and it appears to run with the same results as when I selected "Backup Once"...makes significant progress and then errors out during the D: drive backup.
This led me to believe there must be some file on the D: drive that is causing problems. I tried to view the backup logs and the only one I could find really didn't show me anything else.
Thanks, Chad
I have reformatted/renamed the USB drive and set up a new backup job.
When run as scheduled, I get this error:
Description: Backup
Backup Location: NORDIC0 2013_09_05 15:43 DISK_01
VSS Settings: VSS Copy Backup
Status: Failed
The system cannot find the file specified
and the backup did not even start.
When I select backup once from the menu, this is the result of that:
Description: Backup
Backup Location: NORDIC0 2013_09_05 15:43 DISK_01
VSS Settings: VSS Copy Backup
Status: Failed
The device is not ready
The backup ran for the System Reserved, C: drive and appears to stop at the same point for the D: drive 29.32 GB of 203.35 GB
I tried running the backup from an elevated command prompt and it appears to run with the same results as when I selected "Backup Once"...makes significant progress and then errors out during the D: drive backup.
This led me to believe there must be some file on the D: drive that is causing problems. I tried to view the backup logs and the only one I could find really didn't show me anything else.
Thanks, Chad
ASKER
I ran vssadmin list writers and it just sits there saying...
"Waiting for responses.
These may be delayed if a shadow copy is being prepared"
I'm guessing something must be going on with the VSS writers then?
But I did notice the System log has a number of this error listed but it hasn't appeared since yesterday morning... An error was detected on device \Device\Harddisk2\DR2 during a paging operation.
I checked my raid drives and all the hard drives appear to be functioning properly.
I have attached 2 log files filtered for backup and vss respectively. Please let me know if you need anything else.
There is a vss error that shows in the event log often...Volume Shadow Copy Service error: Failed resolving account spsearch with status 1376. Check connection to domain controller and VssAccessControl registry key --- Event ID 8230
The other day I tried a fix I found on the internet...doesn't appear to have done anything but here is a link to it. http://support.microsoft.com/kb/2537096
vss-Events.csv
Backup.csv
"Waiting for responses.
These may be delayed if a shadow copy is being prepared"
I'm guessing something must be going on with the VSS writers then?
But I did notice the System log has a number of this error listed but it hasn't appeared since yesterday morning... An error was detected on device \Device\Harddisk2\DR2 during a paging operation.
I checked my raid drives and all the hard drives appear to be functioning properly.
I have attached 2 log files filtered for backup and vss respectively. Please let me know if you need anything else.
There is a vss error that shows in the event log often...Volume Shadow Copy Service error: Failed resolving account spsearch with status 1376. Check connection to domain controller and VssAccessControl registry key --- Event ID 8230
The other day I tried a fix I found on the internet...doesn't appear to have done anything but here is a link to it. http://support.microsoft.com/kb/2537096
vss-Events.csv
Backup.csv
After analysis backup logs i suspect there is multiple backup jobs configure
event id : 518 which is causing Vss writers are going in waiting for completion state
http://technet.microsoft.com/en-us/library/cc734329%28WS.10%29.aspx
also request you to run check disk on the volumes and see if any file system errors are there..
event 8230 can be ignored as they are just warning
http://support.microsoft.com/default.aspx?scid=kb;en-US;2483007
event id : 518 which is causing Vss writers are going in waiting for completion state
http://technet.microsoft.com/en-us/library/cc734329%28WS.10%29.aspx
also request you to run check disk on the volumes and see if any file system errors are there..
event 8230 can be ignored as they are just warning
http://support.microsoft.com/default.aspx?scid=kb;en-US;2483007
ASKER
There were no other backup jobs running. After doing some of the trouble shooting I went back and tried to run vssadmin list writers and it worked.
All the writers listed showed Stable & No Error.
I ran chkdsk on the local drives and...neither of them showed any error or problems.
I will try running the backup again right now and report back what occurs. It will be a couple hours...
All the writers listed showed Stable & No Error.
I ran chkdsk on the local drives and...neither of them showed any error or problems.
I will try running the backup again right now and report back what occurs. It will be a couple hours...
ASKER
Checked the backup this morning and it still failed with the same error. I saved out the specific Backup event log and have attached.
It backed up the system reserved, C: drive fully and then backed up 29.7 GB of 204 GB on the D: drive. It stops at about the same point on the D: drive each time.
Is there a log somewhere that shows the file back up detail and maybe then I could figure out what file might be causing this problem?
Any other ideas of what I can try?
Backup-Operational.csv
It backed up the system reserved, C: drive fully and then backed up 29.7 GB of 204 GB on the D: drive. It stops at about the same point on the D: drive each time.
Is there a log somewhere that shows the file back up detail and maybe then I could figure out what file might be causing this problem?
Any other ideas of what I can try?
Backup-Operational.csv
Every message in attached file show that you need to look an event log for more information.
Can you do follow:
1) clean up and save old event logs: system and application
2) run 'vssadmin list writers' and be sure that no errors shown in output. If any errors shown, reboot server to clean any writers and vss errors
3) start command prompt with option 'Run as administrator'
4) run backup manually from command prompt
5) save and attach event files here after backup fails
Can you do follow:
1) clean up and save old event logs: system and application
2) run 'vssadmin list writers' and be sure that no errors shown in output. If any errors shown, reboot server to clean any writers and vss errors
3) start command prompt with option 'Run as administrator'
4) run backup manually from command prompt
5) save and attach event files here after backup fails
ASKER
I will do that tonight after normal work hours...and upload the event logs
ASKER
I have attached the System and Application Logs after failure. The backup started at 7:46 p.m. and quit around 9:42 p.m. The schedule backup time also attempted to run at 2:00 a.m. That one wasn't successful either.
Looks like it might be something with our exchange vss writer?
SysLog.csv
AppLog.csv
Looks like it might be something with our exchange vss writer?
SysLog.csv
AppLog.csv
check shadow copies are enable on the Exchange server.. if yes then disable that.. reboot server and then take backup.
note: all writers should be in stable state.
note: all writers should be in stable state.
ASKER
The vss writers were all in a stable state prior to the last backup I tried. Are you saying that the backup will still run if shadow copies aren't enabled for exchange?
yes, and i suspect shadow copies are conflicting with your backup agent.
So just disable shadow copies and then run backup.. ( if all writers are in stable state)
So just disable shadow copies and then run backup.. ( if all writers are in stable state)
ASKER
Pardon my ignorance, but where do I go to disable shadow copies for Exchange?
I. Application event log:
Event 8230 has to be resolved, apparently it was not. This is a root cause why backup fail: after writer for spserach failed, the backup was market as failure, shadow copy deleted
VSS 8230 Volume Shadow Copy Service error: Failed resolving account spsearch with status 1376. Check connection to domain controller and VssAccessControl registry key.
Context:
Current State: GatherWriterStatus
Error-specific details:
Error: NetLocalGroupGetMemebers(s psearch), 0x80070560, The specified local group does not exist
Also check resolution of EventID 18264
MSSQL$MICROSOFT##SSEE 18264 -6 "The description for Event ID 18264 from source MSSQL$MICROSOFT##SSEE cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
You have some issue in system log
II. System log:
Event 51 "An error was detected on device \Device\Harddisk2\DR2 during a paging operation." The error message you are viewing has occurred due to paging operation. This event might have generated during swapping operation of page file. If this is an external disk, move paging file form this device to local, so memory manager stops doing swapping a page out of memory to an external disk or retrieved a page from external disk back. If this is a local disk, you may want to run a check disk against the drive to see if any errors or problems occur.
Event 8230 has to be resolved, apparently it was not. This is a root cause why backup fail: after writer for spserach failed, the backup was market as failure, shadow copy deleted
VSS 8230 Volume Shadow Copy Service error: Failed resolving account spsearch with status 1376. Check connection to domain controller and VssAccessControl registry key.
Context:
Current State: GatherWriterStatus
Error-specific details:
Error: NetLocalGroupGetMemebers(s
Also check resolution of EventID 18264
MSSQL$MICROSOFT##SSEE 18264 -6 "The description for Event ID 18264 from source MSSQL$MICROSOFT##SSEE cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
You have some issue in system log
II. System log:
Event 51 "An error was detected on device \Device\Harddisk2\DR2 during a paging operation." The error message you are viewing has occurred due to paging operation. This event might have generated during swapping operation of page file. If this is an external disk, move paging file form this device to local, so memory manager stops doing swapping a page out of memory to an external disk or retrieved a page from external disk back. If this is a local disk, you may want to run a check disk against the drive to see if any errors or problems occur.
Just note: exchange writer was is good shape during backup and behaved normal and did not report any errors during VSS snapshot, so this is not a root cause of failure of backup.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
The other suggestions did not include trying different backup media.
also post VSS writer status for the server
to check vss writer run following command prompt
vssadmin list writers