Jump to content
robvil

Windows 2008 backup error

Recommended Posts

Recently I added 3 windows 2008 servers to my network. 2 running windows 2008 64bit domaincontrollers and 1 32bit running terminal services.

I am using Retrospect version 7.6.123, Driver hotfix 7.6.2.101 and client 7.6.107.

 

When retrospect is doing backup is get these errors in my windows logs on my terminal server:

 

Volume Shadow Copy Service error: Unexpected error querying for the IVssWriterCallback interface. hr = 0x80070005.

 

This is often caused by incorrect security settings in either the writer or requestor process.

 

Operation:

Gathering Writer Data

 

Context:

Writer Class Id: {e8132975-6f93-4464-a53e-1050253ae220}

Writer Name: System Writer

Writer Instance ID: {5a2ce352-0ffd-4fb8-b7d7-9f5ceeb74619}

 

 

 

And on my Windows 2008 64bit domain controllers I see this in windows event logs:

 

lsass (568) Unable to write to logfile \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy14\Windows\NTDS\edb.log. Error

 

-1032 (0xfffffbf8).

 

Volume Shadow Copy Service error: Unexpected error querying for the IVssWriterCallback interface. hr = 0x80070005.

 

This is often caused by incorrect security settings in either the writer or requestor process.

 

Operation:

Gathering Writer Data

 

Context:

Writer Class Id: {5382579c-98df-47a7-ac6c-98a6d7106e09}

Writer Name: TermServLicensing

Writer Instance ID: {87c349a9-af3e-47cf-981b-54395ec39c20}

 

lsass (568) Unable to write to logfile \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy14\Windows\NTDS\edb.log. Error

 

-1032 (0xfffffbf8).

 

lsass (568) An attempt to write to the file "\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy15\Windows\NTDS\edb.log"

 

at offset 2981888 (0x00000000002d8000) for 512 (0x00000200) bytes failed after 0 seconds with system error 19

 

(0x00000013): "The media is write protected. ". The write operation will fail with error -1032 (0xfffffbf8). If

 

this error persists then the file may be damaged and may need to be restored from a previous backup.

 

 

Using Windows 2008 native backup I do not get these errors. What is the issue here?

 

Regards

Robert

 

Share this post


Link to post
Share on other sites

Doing a vssadmin list writers I get:

 

Writer name: 'System Writer'

Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}

Writer Instance Id: {6327631f-859b-4f0d-b1ab-3a4b011f54c7}

State: [1] Stable

Last error: Non-retryable error

 

Writer name: 'ASR Writer'

Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}

Writer Instance Id: {c1abec47-c644-4027-bfea-9eca009d1244}

State: [1] Stable

Last error: No error

 

Writer name: 'TermServLicensing'

Writer Id: {5382579c-98df-47a7-ac6c-98a6d7106e09}

Writer Instance Id: {f546fd0f-7f89-49ce-8f13-7f8a36b5d766}

State: [1] Stable

Last error: Non-retryable error

 

Writer name: 'NTDS'

Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757}

Writer Instance Id: {c77f78a4-202c-455d-9708-fd59ff1448d4}

State: [11] Failed

Last error: Non-retryable error

 

Writer name: 'Registry Writer'

Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}

Writer Instance Id: {15ced918-fa3a-44e0-8c42-779897cf2292}

State: [1] Stable

Last error: No error

 

Writer name: 'FRS Writer'

Writer Id: {d76f5a28-3092-4589-ba48-2958fb88ce29}

Writer Instance Id: {87515078-93f1-4e79-9012-10a2609241aa}

State: [1] Stable

Last error: No error

 

Writer name: 'COM+ REGDB Writer'

Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}

Writer Instance Id: {921d0e7b-e4b9-4ca4-8b89-f4543893c9a7}

State: [1] Stable

Last error: No error

 

Writer name: 'BITS Writer'

Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}

Writer Instance Id: {b246f8d3-79ac-4786-8837-8b3837dab62f}

State: [1] Stable

Last error: No error

 

Writer name: 'Shadow Copy Optimization Writer'

Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}

Writer Instance Id: {3a6a802e-5514-4bc8-8653-32a9ea00c45d}

State: [1] Stable

Last error: No error

 

Writer name: 'WMI Writer'

Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}

Writer Instance Id: {2e1bd6da-bc5d-48ca-8018-7cc5573144a7}

State: [1] Stable

Last error: No error

 

This is with retrospect.

Share this post


Link to post
Share on other sites

Turning on Retrospect logging shows this:

 

ifacOptValue: 'WODy' undefined, using default value 2

soctSetThread: socket thread now 0xba4

soccOpen: socket send buffer size is 65.536

soccOpen: socket recv buffer size is 65.536

soccCallback: connected

necoOpen: connection established with "DC4-DMZ1"

 

19-03-2009 23:45:16: Connected to DC4-DMZ1

necoSetReserve: reserved for "testbackupW2K8"

necoCmd: transaction 1: '_gl_' on "RfsDownload"

necoTranGone: transaction 1 disappeared

necoDispatch: transaction 1: result 0 ignored

necoDispatch: transaction 1: result 0 ignored

necoCmd: transaction 2: 'VAcc' on "pcpds"

necoDispatch: transaction 2: result 0

necoCmd: transaction 3: 'VAcc' on "pcpds"

necoDispatch: transaction 3: result 0

necoCmd: transaction 4: 'VAcc' on "pcpds"

necoDispatch: transaction 4: result 0

necoCmd: transaction 5: 'VAcc' on "pcpds"

necoDispatch: transaction 5: result 0

necoCmd: transaction 6: 'VAcc' on "pcpds"

necoDispatch: transaction 6: result 0

* Resolved container DC4-DMZ1 to 1 volumes:

Local Disk (C:) on DC4-DMZ1

soccRecv: connection closed cleanly

soctPreDispose: maximum queue depth was 1

ifacOptValue: 'WODy' undefined, using default value 2

soctSetThread: socket thread now 0xba4

soccOpen: socket send buffer size is 65.536

soccOpen: socket recv buffer size is 65.536

soccCallback: connected

necoOpen: connection established with "DC4-DMZ1"

necoSetReserve: reserved for "Preparing..."

necoCmd: transaction 1: '_gl_' on "RfsDownload"

necoTranGone: transaction 1 disappeared

necoDispatch: transaction 1: result 0 ignored

necoDispatch: transaction 1: result 0 ignored

necoCmd: transaction 2: 'VAcc' on "pcpds"

necoDispatch: transaction 2: result 0

necoSetRelease: unreserved

necoSetReserve: reserved for "Preparing..."

necoCmd: transaction 3: 'VAcc' on "pcpds"

necoDispatch: transaction 3: result 0

necoSetRelease: unreserved

necoSetReserve: reserved for "Preparing..."

necoCmd: transaction 4: 'VAcc' on "pcpds"

necoDispatch: transaction 4: result 0

necoSetRelease: unreserved

necoSetReserve: reserved for "Preparing..."

necoCmd: transaction 5: 'XPMI' on "pcpds"

T-5: VssWEnumWriterMetadata: Excluding writer "ASR Writer" from the backup.

T-5: VssWEnumWriterMetadata: Excluding writer "Shadow Copy Optimization Writer" from the backup.

T-5: VssWEnumWriterMetadata: Excluding writer "FRS Writer" from the backup.

necoDispatch: transaction 5: result 0

necoSetRelease: unreserved

necoSetReserve: reserved for "Preparing..."

necoCmd: transaction 6: 'VAcc' on "pcpds"

necoDispatch: transaction 6: result 0

necoSetRelease: unreserved

necoSetReserve: reserved for "Preparing..."

necoCmd: transaction 7: 'XATM' on "pcpds"

T-7: Windows XP VSS Writer found: BITS Writer

T-7: Windows XP VSS Writer found: WMI Writer

T-7: Windows XP VSS Writer found: NTDS

T-7: Windows XP VSS Writer found: COM+ REGDB Writer

T-7: Windows XP VSS Writer found: Registry Writer

necoDispatch: transaction 7: result 0

necoSetRelease: unreserved

necoSetReserve: reserved for "Preparing..."

necoCmd: transaction 8: 'XDMV' on "pcpds"

T-8: VssWMapAndLogError: mapped Windows error -2.147.212.300 to -1.017

T-8: VssWSnapVolume: Writer "NTDS" indicated failure of DoSnapshotSet, winerr -2147212300, error -1017

necoDispatch: transaction 8: result 0

necoSetRelease: unreserved

necoSetReserve: reserved for "Preparing..."

necoCmd: transaction 9: 'VAcc' on "pcpds"

necoDispatch: transaction 9: result 0

necoSetRelease: unreserved

necoSetReserve: reserved for "Preparing..."

necoCmd: transaction 10: 'VAcc' on "pcpds"

necoDispatch: transaction 10: result 0

necoSetRelease: unreserved

necoSetReserve: reserved for "Preparing..."

necoCmd: transaction 11: 'VAcc' on "pcpds"

necoDispatch: transaction 11: result 0

necoSetRelease: unreserved

necoSetReserve: reserved for "Preparing..."

necoCmd: transaction 12: 'VAcc' on "pcpds"

necoDispatch: transaction 12: result 0

necoSetRelease: unreserved

necoSetReserve: reserved for "Preparing..."

necoCmd: transaction 13: 'ScTg' on "pcpds"

necoDispatch: transaction 13: result 0

necoSetRelease: unreserved

 

Any idea what this means?

 

T-8: VssWMapAndLogError: mapped Windows error -2.147.212.300 to -1.017

T-8: VssWSnapVolume: Writer "NTDS" indicated failure of DoSnapshotSet, winerr -2147212300, error -1017

 

Share this post


Link to post
Share on other sites

What does the Windows Event Log say for the backup attempt? This error is coming directly from VSS

Share this post


Link to post
Share on other sites

The first post was from windows event log. All below is windows complaining.

 

Volume Shadow Copy Service error: Unexpected error querying for the IVssWriterCallback interface. hr = 0x80070005.

 

This is often caused by incorrect security settings in either the writer or requestor process.

 

Operation:

Gathering Writer Data

 

Context:

Writer Class Id: {e8132975-6f93-4464-a53e-1050253ae220}

Writer Name: System Writer

Writer Instance ID: {5a2ce352-0ffd-4fb8-b7d7-9f5ceeb74619}

 

 

 

And on my Windows 2008 64bit domain controllers I see this in windows event logs:

 

lsass (568) Unable to write to logfile \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy14\Windows\NTDS\edb.log. Error

 

-1032 (0xfffffbf8).

 

Volume Shadow Copy Service error: Unexpected error querying for the IVssWriterCallback interface. hr = 0x80070005.

 

This is often caused by incorrect security settings in either the writer or requestor process.

 

Operation:

Gathering Writer Data

 

Context:

Writer Class Id: {5382579c-98df-47a7-ac6c-98a6d7106e09}

Writer Name: TermServLicensing

Writer Instance ID: {87c349a9-af3e-47cf-981b-54395ec39c20}

 

lsass (568) Unable to write to logfile \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy14\Windows\NTDS\edb.log. Error

 

-1032 (0xfffffbf8).

 

lsass (568) An attempt to write to the file "\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy15\Windows\NTDS\edb.log"

 

at offset 2981888 (0x00000000002d8000) for 512 (0x00000200) bytes failed after 0 seconds with system error 19

 

(0x00000013): "The media is write protected. ". The write operation will fail with error -1032 (0xfffffbf8). If

 

this error persists then the file may be damaged and may need to be restored from a previous backup.

 

If I do a backup with windows backup there is no problems, so it's related to retrospect.

 

 

Share this post


Link to post
Share on other sites

I contacted support last week regarding this issue via email as I have a support contract.

 

I got a reply saying they would see into this and get back to me. I have not heard anything since then even though I have send several emails. How do I get support to reply to my emails?

 

Regards

Robert

 

Share this post


Link to post
Share on other sites

That is the email address for our Asia Pacific support. I will follow-up with our APJ tech support team.

 

Share this post


Link to post
Share on other sites

Hi,

 

Have any of you in this forum dobbelt checked your Retrospect is doing a complete backup of windows 2008?

 

I have setup a test windows 2008 server without any 3. party software except the retrospect client and if terminal server license server is installed it does not get backup up. Futher if the server is running AD, then the active directory database is not backup up.

 

Checking with "vssadmin list writers" there is no errors and no errors in the windows event log or Retrospect backup log. But what I can see is there is no VSS backup done on AD because this is not logged in the event log which it´s normally is.

 

So despite Retrospect is showing the backup job as completed successfully it´s not.

 

Regards

Robert

 

Share this post


Link to post
Share on other sites

I simply cannot figure this out.

 

Retrospect support says there are no issues with Windows 2008 NTDS backup despite I still do not get NTDS backup of W2K8 servers. Currently waiting for support as I have escalated my case. They are not too fast over there. How long a responstime is to be expected?

 

Here is a test setup that´s not working:

 

a. Standalone retrospect backupserver on windows 2008. Not member of any domain.

 

b. Freshly installed W2K8 AD server 64bit. Only Retrospect 3. part app. installed.

 

If I do a backup from retrospect I do not get NTDS or terminal service licensing backup. No errors of interrest I think.

 

If I do a backup with windows wbadmin I get backup of everything incl. NTDS. Eventlog currectly show NTDS being backup up.

 

I have enabled Microsoft VSS debug logging, but from all the log text I cannot see if anything should be wrong. I actually do not know what to look for.

 

Retrospect is showing this (only some):

 

Normal backup using testbackupW2K8 at 22-04-2009 17:42 (Execution unit 1)

MemPack: total heaps = 22

Wow64 file redirection enabled

Wow64EnableWow64FsRedirection failed, 1

Wow64 file redirection disabled

Wow64EnableWow64FsRedirection failed, 1

To Backup Set Test2...

tyceGCCheck: periodic GC, error 0 (unknown)

tyceGCCheck: periodic GC, error 0 (unknown)

tyceGCCheck: periodic GC, error 0 (unknown)

MapError: mapped Windows error 2 to error -1101 (file/directory not found)

TFileLoc::Delete: UDeleteFile failed, C:\ProgramData\Retrospect\intv5443.reh, winerr 2, error -1101

MapError: mapped Windows error 2 to error -1101 (file/directory not found)

TFolderLoc::StartFind: UFindFirstFile failed, C:\Program Files\Retrospect\Retrospect 7.6, winerr 2, error -1101

 

T-11: MapError: mapped Windows error 2 to

T-11: TPCFileLoc::SetAttributes: USetFileAttributes failed, C:\Program Files (x86)\Retrospect\Retrospect Client\intv5444.reh, winerr 2, error -1101

T-11: MapError: mapped Windows error 2 to

T-11: TFileLoc::Delete: UDeleteFile failed, C:\Program Files (x86)\Retrospect\Retrospect Client\intv5444.reh, winerr 2, error -1101

 

T-31: MapError: mapped Windows error 2 to

T-31: TReg::Open(SYSTEM\CurrentControlSet\Services\CertSvc\Configuration): failed, winerr 2, error -1101

MapError: mapped Windows error 2 to error -1101 (file/directory not found)

TFileLoc::SetAttributes: USetFileAttributes failed, C:\ProgramData\Retrospect\RtrExec.dir\Exec\State\RtrRSM\RtrRSM.dat, winerr 2, error -1101

MapError: mapped Windows error 2 to error -1101 (file/directory not found)

TFileLoc::Delete: UDeleteFile failed, C:\ProgramData\Retrospect\RtrExec.dir\Exec\State\RtrRSM\RtrRSM.dat, winerr 2, error -1101

T-33: MapError: mapped Windows error 2 to

T-33: TPCFolderLoc::GetAttributes: UGetFileAttributes failed, C:\Windows\system32\ntmsdata, winerr 2, error -1101

tyceGCCheck: periodic GC, error 0 (unknown)

MapError: mapped Windows error 2 to error -1101 (file/directory not found)

TFileLoc::SetAttributes: USetFileAttributes failed, C:\ProgramData\Retrospect\RtrExec.dir\Exec\State\RtrComRg\RtrComRg.dat, winerr 2, error -1101

MapError: mapped Windows error 2 to error -1101 (file/directory not found)

TFileLoc::Delete: UDeleteFile failed, C:\ProgramData\Retrospect\RtrExec.dir\Exec\State\RtrComRg\RtrComRg.dat, winerr 2, error -1101

T-36: MapError: mapped Windows error 19 to

T-36: TPCFileLoc::SetAttributes: USetFileAttributes failed, \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy9\Windows\registration\R000000000001.clb, winerr 19, error -1103

T-36: MapError: mapped Windows error 19 to

T-36: TFileLoc::Delete: UDeleteFile failed, \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy9\Windows\registration\R000000000001.clb, winerr 19, error -1103

T-36: MapError: mapped Windows error 18 to

T-36: MapError: mapped Windows error 18 to

MapError: mapped Windows error 2 to error -1101 (file/directory not found)

TFileLoc::SetAttributes: USetFileAttributes failed, C:\ProgramData\Retrospect\RtrExec.dir\Exec\State\RtrWMI\RtrWMI.dat, winerr 2, error -1101

MapError: mapped Windows error 2 to error -1101 (file/directory not found)

TFileLoc::Delete: UDeleteFile failed, C:\ProgramData\Retrospect\RtrExec.dir\Exec\State\RtrWMI\RtrWMI.dat, winerr 2, error -1101

T-39: MapError: mapped Windows error 19 to

T-39: TPCFileLoc::SetAttributes: USetFileAttributes failed, \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy9\Windows\system32\wbem\repository\INDEX.BTR, winerr 19, error -1103

 

This is veryfied on 3 different W2K8 servers. Tried playing with the DCOM+ security settings and changing properties on the retrospect services without look.

 

I´m out of good ideas. Any suggestions whats wrong here?

 

Regards

Robert

:confused2:

 

 

 

 

Share this post


Link to post
Share on other sites

I tried to restore the DC from retrospect backup (even though I know it will not work) and got this error:

 

- 23-04-2009 15:40:11: Restoring from Test2, Snapshot W2K8TEST, 23-04-2009 14:50:53

T-26: TReg::Replace(C:\Users\ADMINI~1\AppData\Local\Temp\REG00000): failed, winerr 17, error -1011

Can't restore registry, error -1011 (API request impossible)

vtopRestoreState: Registry restored unsuccessfully.

System configuration restored, please reboot the computer.

23-04-2009 15:50:16: 1 execution errors

Completed: 102 files, 1,6 GB

Performance: 168,0 MB/minute

Duration: 00:10:05 (00:00:23 idle/loading/preparing)

 

And Retrospect ends the backup job saying "completed successfully" of cause!

 

Rebooting the server in AD restore mode ends up with "no rpc servers avaible to request login information". Rebooting again in normal mode causes one automatic reboot and then I´m able to login.

 

What´s the right way to restore AD on W2K8? (if the backup was done correctly of cause).

 

 

Share this post


Link to post
Share on other sites

Retrospect currently has a bug that prevents the backup/Restore of Windows 2008 Active Directory. The other registry items are copied. Until that bug is fixed, you can use the built in Microsoft "Windows Server backup" to backup/restore System State in 2008. You can then use Retrospect to backup that backup.

 

We are working to fix this problem.

Share this post


Link to post
Share on other sites

Thank you!

 

What wonders me is why support/engineering keep saying to me there's no issues and it is a Microsoft problem.

 

Btw. Terminal server license server does NOT get backup either.

 

Robert

 

Edited by Guest

Share this post


Link to post
Share on other sites

This is not a small bug fix. Retrospect is a 32 bit program and fixing this will either require the release of a 64 bit version or we need to write 64 to 32 bit translations. We are working on it, but it won't happen in the short term. It could be a month or more before we have a pre-release version to offer customers.

 

Until that bug is fixed, you can use the built in Microsoft "Windows Server backup" to backup/restore System State in 2008. You can then use Retrospect to backup that backup.
Edited by Guest

Share this post


Link to post
Share on other sites

I have only tested NTDS backup on 64-bit. Are you saying 32-bit NTDS backup on W2K8 is working with retrospect?

 

 

Share this post


Link to post
Share on other sites

I don't know, my knowledge is limited in this area. I have only heard of Windows 2008 being a 64 bit OS in production environments and I didn't know that NTDS came in 32/64 bit versions.

 

If NTDS is captured as part of the AD backup, under 2008 server, then that may be a factor.

 

EMC has never tested 32 bit versions of Windows 2008 since it typically isn't found in production environments.

Share this post


Link to post
Share on other sites

There is no thing as 32-bit or 64-bit Active directory (ntds), but there is 32-bit W2K8 and 64-bit W2K8, so that´s what I ment.

 

But both 32-bit and 64-bit versions of W2K8 must be supported as we see a lot of 32-bit W2K8 terminal servers due to bad or missing 64-bit drivers.

 

Btw. what about 64-bit SQL. There must be bugs there too?

 

Anyway I would expect the bug not to be related to only 64-bit W2K8 but also 32-bit OS and again I see missing backup of terminal server license database and BITS also. General I see a overall issue with the retrospect client on W2K8.

 

Others on this forum should probobly dobbelcheck there W2K8 backup and verify it actually is backup up right because Retrospect will say "succesfully backup" even if it´s not.

 

And yes you are correct - the only way to backup a complete valid system is to use Windows Server backup feature.

 

 

Share this post


Link to post
Share on other sites

Was this patch ever finalized? Having the same ASR Writeback errors as above user, and AD is not showing up in the properties of the server's snapshot. Additional note, this is happening to me in Retrospect 7.7, backing up 2008 Server R2.

Edited by Guest

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×