Error Cannot start Shadow Copy

Discuss any Exchange Database backup and restore issues here.

Error Cannot start Shadow Copy

Postby techsupport@mika.com » Tue Oct 07, 2014 10:17 pm

cloudbacko cannot start shadow copy, reason listmailboxdatabase you must provide a vaule for this property property name hostserver - Last three days
User avatar
techsupport@mika.com
 
Posts: 4
Joined: Tue Oct 07, 2014 10:13 pm

Re: Error Cannot start Shadow Copy

Postby CB.Support.Manager » Wed Oct 08, 2014 9:51 am

Hello

To resolve your Microsoft Volume Shadow Copy (VSS) error:

1. Register the Volume Shadow Copy by running the C:\Program Files\CloudBacko Pro\bin\RegisterVSS.bat file

2. Reboot the machine for the settings to take effect.

3. After rebooting our Exchange server, please run a "vssadmin list writers" command to verify the VSS writers are Stable and there are no errors
Support Manager of CloudBacko
The Most Secure Cloud & Local Backup Software
User avatar
CB.Support.Manager
Site Admin
 
Posts: 443
Joined: Wed Aug 21, 2013 5:53 pm

Re: Error Cannot start Shadow Copy

Postby techsupport@mika.com » Wed Oct 08, 2014 8:50 pm

i ran the command and rebooted then verified all services were running

i still get [2014/10/08 08:34:43] [erro] Cannot start shadow copy, reason =[listMailboxDatabases] You must provide a value for this property. Property Name: HostServer

The backup fails with 0 files updated/new

running the vssadmin list writers i get no errors

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: 'System Writer'
Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
Writer Instance Id: {7dd9fb7d-0a15-4605-bec7-368d526feb35}
State: [1] Stable
Last error: No error

Writer name: 'ASR Writer'
Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
Writer Instance Id: {36b7b25d-8edb-44c5-860b-957d050b0e7b}
State: [1] Stable
Last error: No error

Writer name: 'Shadow Copy Optimization Writer'
Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
Writer Instance Id: {5c4114b5-c889-48be-b26b-921555b27a88}
State: [1] Stable
Last error: No error

Writer name: 'Registry Writer'
Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
Writer Instance Id: {81694bc1-d949-4b4c-b7f5-b8a695fe9260}
State: [1] Stable
Last error: No error

Writer name: 'COM+ REGDB Writer'
Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
Writer Instance Id: {5ad23edd-0cac-4fd8-a835-858181390623}
State: [1] Stable
Last error: No error

Writer name: 'IIS Config Writer'
Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
Writer Instance Id: {2414ca8b-a265-4f6b-a766-6494bed5c31d}
State: [1] Stable
Last error: No error

Writer name: 'WMI Writer'
Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Writer Instance Id: {302741c7-b6e4-453c-b5b6-5a2bb95d1b22}
State: [1] Stable
Last error: No error

Writer name: 'BITS Writer'
Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
Writer Instance Id: {28b9c4c2-ecbf-420f-925e-5643a2f8c7fc}
State: [1] Stable
Last error: No error

Writer name: 'Microsoft Exchange Writer'
Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
Writer Instance Id: {a8e0e055-4929-4e4b-beda-4e9b2385c369}
State: [5] Waiting for completion
Last error: No error

Writer name: 'IIS Metabase Writer'
Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
Writer Instance Id: {cbf6aded-38a0-4d60-95ce-862970479e48}
State: [1] Stable
Last error: No error


C:\Users\backup>
User avatar
techsupport@mika.com
 
Posts: 4
Joined: Tue Oct 07, 2014 10:13 pm

Re: Error Cannot start Shadow Copy

Postby CB.Support.Manager » Thu Oct 09, 2014 9:35 am

Hello,

From the output of your vssadmin list writers, it looks like there is an issue with your "Microsoft Exchange Writer". The status is "Waiting for completion" it should be "Stable". This is causing your backup error "Cannot start shadow copy, reason =[listMailboxDatabases]". As CloudBacko Pro uses Microsoft Exchange Writer to create a consistent snapshot of your Exchange database in order to perform a backup job.

Writer name: 'Microsoft Exchange Writer'
Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
Writer Instance Id: {a8e0e055-4929-4e4b-beda-4e9b2385c369}
State: [5] Waiting for completion
Last error: No error

-Can you check your Windows Event logs at the time of the backup job to see if there are any errors recorded?
-Do you mind providing us with some information about your Exchange server setup, i.e. Exchange version & service pack/CU version, Windows version & service pack, is this a Domain controller?
-Are using an administrator account to install and operate CloudBacko Pro?
-Is there any other backup software installed on your Exchange server?
-Do you mind post the full backup log for our reference?
Support Manager of CloudBacko
The Most Secure Cloud & Local Backup Software
User avatar
CB.Support.Manager
Site Admin
 
Posts: 443
Joined: Wed Aug 21, 2013 5:53 pm

Re: Error Cannot start Shadow Copy

Postby techsupport@mika.com » Fri Oct 17, 2014 3:09 am

On the Windows Event Logs, the errors are:
Source: ESE - Information Store (4060) Shadow copy instance 7 aborted.
Source: MSExchangeIS - Exchange VSS Writer (instance 5fd95e16-7353-4956-9ef3-4028730cd764:7) failed with error code -2403 when preparing for Snapshot.
Exchange VSS Writer (instance 5fd95e16-7353-4956-9ef3-4028730cd764:7) failed with error code 1295 when processing the post-snapshot event.
Exchange VSS Writer (instance 5fd95e16-7353-4956-9ef3-4028730cd764:7) failed with error code -2403 when preparing the database engine for backup of database 'Public Folder'.
An attempt to prepare the database 'Public Folder' for backup failed because the database is already in the process of being backed up. The error code is -2403. (Note that if a backup was recently aborted, then it may take several minutes for the system to detect the aborted backup and initiate backup cleanup procedures, so this message may be generated if an attempt was made to backup a database before a previous backup attempt had fully terminated.)

Running Windows Server 2208 SP1, Exchange 2010 SP 3 version 14.3. Not a domain controller.
To run Cloudbacko, we're using a dedicated backup account and the only backup software besides Cloubacko is the Windows Server Backup, which we do not use.

I'm now noticing a different error in the logs. Here is the most current one.
[2014/10/15 02:00:18] [info] Start [ Windows Server 2008 R2 (ender-temp), CloudBacko Pro 1.5.0.0 ]
[2014/10/15 02:00:23] [info] Start Backup ... Database [In-File Delta: Incremental]
[2014/10/15 02:00:23] [info] Using Temporary Directory E:\Temp\CloudBacko Pro\1405224788421\Local@1405224938144
[2014/10/15 02:00:23] [info] Microsoft Exchange Server 2010 (14.3.123.4)
[2014/10/15 02:00:23] [info] Start running pre-commands
[2014/10/15 02:00:23] [info] Finished running pre-commands
[2014/10/15 02:00:23] [info] Downloading server file list ...
[2014/10/15 02:00:43] [info] Downloading server file list ... Completed
[2014/10/15 02:00:43] [info] Start Microsoft Exchange backup
[2014/10/15 02:00:43] [info] Start creating Shadow Copy Set ...
[2014/10/15 02:01:20] [erro] Cannot start shadow copy, reason =The writer failed due to an error that would likely not occur if the entire backup, restore, or shadow copy creation process was restarted. (VSS_E_WRITERERROR_RETRYABLE)
[2014/10/15 02:01:21] [info] Saving encrypted backup file index to 1405224788421/files at destination MIKA - Exchange Daily …
[2014/10/15 02:01:23] [info] Saving encrypted backup settings to settings/ender-temp-2014-10-15.xml at destination MIKA - Exchange Daily …
[2014/10/15 02:01:24] [info] Saving encrypted backup log files to 1405224788421/logs at destination MIKA - Exchange Daily …
[2014/10/15 02:01:31] [info] Start running post-commands
[2014/10/15 02:01:31] [info] Finished running post-commands
[2014/10/15 02:01:31] [info] Deleting temporary file E:\Temp\CloudBacko Pro\1405224788421\Local@1405224938144
[2014/10/15 02:01:31] [erro] The writer failed due to an error that would likely not occur if the entire backup, restore, or shadow copy creation process was restarted. (VSS_E_WRITERERROR_RETRYABLE)
[2014/10/15 02:01:31] [erro] Backup completed with error(s)
User avatar
techsupport@mika.com
 
Posts: 4
Joined: Tue Oct 07, 2014 10:13 pm

Re: Error Cannot start Shadow Copy

Postby CB.Support.Manager » Fri Oct 17, 2014 10:06 am

Hello,

Thank you for the update and the clarification of your Exchange setup.

The "VSS_E_WRITERERROR_RETRYABLE" error indicates there is still an issue with your Microsoft Exchange Writer. If you run a "vssadmin list writers" you will see the following status.

Writer name: 'Microsoft Exchange Writer'
Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
Writer Instance Id: {a8e0e055-4929-4e4b-beda-4e9b2385c369}
State: [14] Failed
Last error: Retryable error


We recommend you try the following steps:

1. The backup logs shows the MS Exchange version as 2010 SP3, we recommend you patch you Exchange to the latest Update Rollup 7 for SP3 to rule out any issues with Exchange which could be causing this problem http://social.technet.microsoft.com/wik ... mbers.aspx

Also, you may need to consider patching Windows 2008 to make sure that there are no outstanding patches for Windows that might fix issue relating to the VSS.

2. If enabled, please disable the circular logging option for information store(s) and public folder.
3. Reboot the Exchange server
Support Manager of CloudBacko
The Most Secure Cloud & Local Backup Software
User avatar
CB.Support.Manager
Site Admin
 
Posts: 443
Joined: Wed Aug 21, 2013 5:53 pm


Return to Microsoft Exchange Server Database

Who is online

Users browsing this forum: No registered users