Small Business Susan

Houston … we have no backup….


11/29/2006 6:21 PM
——————————-
Date: 11/29/2006
Time: 6:21 PM
User: Administrator
——————————-


Backup Runner started.
Launching NTBackup: ntbackup.exe backup “@C:\Program Files\Microsoft Windows Small Business Server\Backup\Small Business Backup Script.bks” /d “SBS Backup created on 11/29/2006 at 6:21 PM” /v:yes /r:no /rs:no /hc:off /m normal /j “Small Business Server Backup Job” /l:s /f “G:\Backup Files\Small Business Server Backup (02).bkf” /UM
NTBACKUP LOG FILE: C:\Documents and Settings\SBS Backup User\Local Settings\Application Data\Microsoft\Windows NT\NTBackup\data\backup07.log
=====================<BEGIN NTBACKUP LOG FILE>=====================
Backup Status
Operation: Backup
Active backup destination: File
Media name: “Small Business Server Backup (02).bkf created 11/29/2006 at 6:21 PM”


Volume shadow copy creation: Attempt 1.
Timeout before function completed


Error returned while creating the volume shadow copy:0xffffffff.


Error returned while creating the volume shadow copy:ffffffff
Aborting Backup.


———————-


The operation did not successfully complete.


———————-


=======================<END NTBACKUP LOG FILE>=====================
NTBackup finished the backup with errors.


For more information about failed backups, see the article on troubleshooting your backup at the following Web page: http://go.microsoft.com/fwlink/?LinkId=18414


Backup ended at Wednesday, November 29, 2006 6:26 PM
Backup Runner finished.


So off we go to check the VSS writers…. 


Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.


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



C:\Documents and Settings\Administrator>


Okay… hmmm…That’s supposed to be a bit more filled up than that…so off we go to Stephanie’s blog to reregister the dll’s
http://blogs.technet.com/sdoakes/archive/2006/02/03/418722.aspx 


And now after registering all that.. we have:


Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.


C:\Documents and Settings\Administrator>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: {852d07a9-bbae-40b8-8214-10b78a8fedf9}
   State: [1] Stable
   Last error: No error


Writer name: ‘MSDEWriter’
   Writer Id: {f8544ac1-0611-4fa5-b04b-f7ee00b03277}
   Writer Instance Id: {069cc33d-ea51-4b1a-8185-697fc5743edb}
   State: [1] Stable
   Last error: No error


Writer name: ‘Dhcp Jet Writer’
   Writer Id: {be9ac81e-3619-421f-920f-4c6fea9e93ad}
   Writer Instance Id: {e8633ced-b964-4533-b3ed-ae4f99aa0ff2}
   State: [1] Stable
   Last error: No error


Writer name: ‘TermServLicensing’
   Writer Id: {5382579c-98df-47a7-ac6c-98a6d7106e09}
   Writer Instance Id: {04b74023-de0c-424f-ab44-fe0a0eb4f2c1}
   State: [1] Stable
   Last error: No error


Writer name: ‘FRS Writer’
   Writer Id: {d76f5a28-3092-4589-ba48-2958fb88ce29}
   Writer Instance Id: {f3fcefb4-ee91-4107-8646-d7f62652ce4c}
   State: [1] Stable
   Last error: No error


Writer name: ‘Registry Writer’
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {f98048ac-04ff-4c05-a597-1250e4fde12e}
   State: [1] Stable
   Last error: No error


Writer name: ‘COM+ REGDB Writer’
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {6a5f42ee-eea8-4de8-a03f-8c2126a5ab13}
   State: [1] Stable
   Last error: No error


Writer name: ‘WINS Jet Writer’
   Writer Id: {f08c1483-8407-4a26-8c26-6c267a629741}
   Writer Instance Id: {d36d82d5-0a2c-4207-9831-a5b483f7790d}
   State: [1] Stable
   Last error: No error


Writer name: ‘Event Log Writer’
   Writer Id: {eee8c692-67ed-4250-8d86-390603070d00}
   Writer Instance Id: {39d64be1-14f7-4ed9-8af1-38a9ca4a1281}
   State: [1] Stable
   Last error: No error


Writer name: ‘NTDS’
   Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757}
   Writer Instance Id: {59afdde9-5e4e-44c2-a205-4b58e437e9fa}
   State: [1] Stable
   Last error: No error


Writer name: ‘WMI Writer’
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {3f164a79-8196-4381-827f-4c0d2042a0ff}
   State: [1] Stable
   Last error: No error


Writer name: ‘BITS Writer’
   Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
   Writer Instance Id: {ddfe61e1-7484-4a3d-b5de-ceb432f20f6a}
   State: [1] Stable
   Last error: No error


Writer name: ‘IIS Metabase Writer’
   Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
   Writer Instance Id: {fbb8ea58-4325-4f29-9eb8-bce127b2cb8c}
   State: [1] Stable
   Last error: No error



C:\Documents and Settings\Administrator>


…and we now have a functioning backup…. I know what did it… I installed an updated version of Policy Patrol last night and it mooshed my VSS writers…



1 comment so far ↓

  • #   RandyS on 11.30.06 at 6:33 pm     

    Huh???

    Susan, I don’t know how you come up with this stuff, but I have a server doing the exact same thing, so I’m going to see if this fixes it.

    Thanks!