SBS 2011 standard move data wizard has stopped working

Hello,

Have a look at the MoveData log file located here:
C:\Program Files\Windows Small Business Server\Logs

It may give you a better idea to why it has failed.

make sure you have a good backup before attempting again.

Greetings,

First of all clear some more space on c: drive... update windows to latest... they try again...

for moving database
check this solution

https://www.experts-exchange.com/questions/27602544/SBS-2011-Move-Exchange-DB-to-another-drive-failed.html

by/
Glen Knight2012-02-24 at 13:31:17ID: 37639455
Comment Utility
The path shouldn't need to exist, it will create this when you move it.

How are you moving the database?  You should be using the SBS Console under Backup and Server Storage select the Server Storage tab.

Do both drives appear here?

Then on the tasks bar on the right hand side select move exchange server data.

You might want to check the following link?

http://www.planitcomputing.ie/blog/?p=248

Hi,

I followed David Atkin and cpmcomputers' suggestion. I connected a new USB HDD to do a full backup. It was failed (see the attached screen shot) with following error:
"A Shadow Copy Service operation failed. Detailed error: The Volume Shadow Copy Service operation failed with error 0x800423F3. View the event log for more information."
Shaik, I was trying moving exchange data using SBS console and I am not too sure what can I do to safely clear more space on C drive?

Thanks.
backup-fail.jpg

Can you open an elevated cmd and type the below please:
vssadmin list writers

Paste the results into here.

The wizard is possibly failing due to it not being able to check the backup at the start of the wizard.  Either way its strongly recommended that you have a successful backup prior to moving any actual data.

If you're in dyer need of more disk space then there are other things you can do in the interim.  Read this article:

http://blogs.technet.com/b/sbs/archive/2010/03/02/recovering-disk-space-on-the-c-drive-in-small-business-server-2008.aspx

David is correct here and I think has a good handle on what is happening
So to save duplicating/confusing the issue I will step back and keep a watching brief only

one observation
When was the server last rebooted - this would likely restart the Failed Vsswriters and allow the move

Thank you David. I've done the "vssadmin list writers" in cmd but I don't know how to copy from the cmd mode. It appears that the "Last error: No error" is for all writer name.
I'll check your link to see if I can get some more space on C drive. Thank you.

cpmcomputers is correct by saying a reboot will more than likely resolve the writer issues.  Can you reply to his question regarding the uptime.

FYI, if you right click within the cmd windows and select 'mark'.  Highlight the text and press enter.  This will copy it for you.

Do you have anything in the 'state' section on any of the writers that isn't at a 'Stable' state?

Thank you David. Following are the output.

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Windows\system32>vssadmin list writers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.

Waiting for responses.
These may be delayed if a shadow copy is being prepared.

Writer name: 'Task Scheduler Writer'
   Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
   Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}
   State: [1] Stable
   Last error: No error

Writer name: 'VSS Metadata Store Writer'
   Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
   Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
   State: [1] Stable
   Last error: No error

Writer name: 'Performance Counters Writer'
   Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}
   Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}
   State: [1] Stable
   Last error: No error

Writer name: 'SharePoint Services Writer'
   Writer Id: {da452614-4858-5e53-a512-38aab25c61ad}
   Writer Instance Id: {aa0f13fa-cfb7-4522-939e-0f9165bea784}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'System Writer'
   Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
   Writer Instance Id: {092dc2a1-5f67-42e2-a37b-370b7b90a8e9}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'FSRM Writer'
   Writer Id: {12ce4370-5bb7-4c58-a76a-e5d5097e3674}
   Writer Instance Id: {7d438fcd-21e1-445f-9af8-c0a115ed1a65}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'FRS Writer'
   Writer Id: {d76f5a28-3092-4589-ba48-2958fb88ce29}
   Writer Instance Id: {68ebeb4b-ae7d-4ea7-91b8-81d3ad54c73f}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'ASR Writer'
   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Writer Instance Id: {ffb0bcd7-b459-4e9a-a442-e76de0098355}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'Certificate Authority'
   Writer Id: {6f5b15b5-da24-4d88-b737-63063e3a1f86}
   Writer Instance Id: {e9315468-9e90-467a-a9dd-eef71359016f}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'Shadow Copy Optimization Writer'
   Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Writer Instance Id: {552114e9-0adb-4e24-9e89-08ccc38b717a}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'TS Gateway Writer'
   Writer Id: {368753ec-572e-4fc7-b4b9-ccd9bdc624cb}
   Writer Instance Id: {a4f9ad37-4249-4759-88be-a941ca8eb94f}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'Microsoft Exchange Writer'
   Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
   Writer Instance Id: {b2bf1f0d-4878-4d1d-a92a-af6f29b8a127}
   State: [8] Failed
   Last error: Retryable error

Writer name: 'SPSearch4 VSS Writer'
   Writer Id: {35500004-0201-0000-0000-000000000000}
   Writer Instance Id: {f452a51d-fb40-4998-a854-29abf467bdb4}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'NPS VSS Writer'
   Writer Id: {35e81631-13e1-48db-97fc-d5bc721bb18a}
   Writer Instance Id: {eb27979a-4ac8-466d-b570-860799f2ea2b}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'IIS Config Writer'
   Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
   Writer Instance Id: {9cb69dfa-e7a7-4d0e-9557-5ba0c8b3d2a8}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'IIS Metabase Writer'
   Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
   Writer Instance Id: {01e97ea4-f17a-4687-90c3-b7bd9aa879a3}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {52ec3518-9ff2-4aa0-96b3-d9b4ef3d2e66}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'Dhcp Jet Writer'
   Writer Id: {be9ac81e-3619-421f-920f-4c6fea9e93ad}
   Writer Instance Id: {82d4cf64-34b3-488f-a27f-551ba6515475}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'MSSearch Service Writer'
   Writer Id: {cd3f2362-8bef-46c7-9181-d62844cdc0b2}
   Writer Instance Id: {2c4debe3-e275-4a10-8a03-c5384d9edbc2}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {65a5164a-da0a-4692-8447-4d56d894a89b}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {55f3b45e-4566-4b34-818d-81d0b495e720}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'NTDS'
   Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757}
   Writer Instance Id: {1837314c-5eef-4e71-96e4-b1f93d6a45a1}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'BITS Writer'
   Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
   Writer Instance Id: {1017b792-2bd2-4ce6-8eac-458da24a9641}
   State: [1] Stable
   Last error: No error

C:\Windows\system32>

cpmcomputers--I will reboot the server and try back up again. Thank you.

suggest

(perhaps) follow article to free up space

a reboot

then run vssadmin list writers and repost first

All writers should show stable and no error before trying a move

before trying any move what are you using to backup? (essential in my view) !!

Thank you guys. I've rebooted the server. The Windows Backup is in the process. I'll let you know the result and try the Data Move again.

Thank you David. It is great. I've backed up the SBS server and moved the exchange data successfully.

Thanks to cpmcomputers as well. Your suggestion of reboot the server was really helpful. It solved the back up problem.