Hello,

I am having problems backing up one of my mail mail databases which is on Exchange 2010.

I have a replica is inconsistant error that I cannot solve. I have tried performing a consistancy check and have modified the disc usage but nothing has helped. I have also removed it from the Protection Group and then re-added it again but this hasn't helped either.

Any advice would be much appreciated, the error message received is below.

Many thanks

Rowan

==================================================

Description:        Recovery point creation jobs for Exchange Mailbox Database HRSFC Student Database on HR-MAIL.hrsfc.ac.uk have been failing. The number of failed recovery point creation jobs = 1.

 If the data source protected has some dependent data sources (like a SharePoint Farm), then click on the Error Details to view the list of dependent data sources for which recovery point creation failed. (ID 3114)

                DPM failed to synchronize changes for Exchange Mailbox Database HRSFC Student Database on HR-MAIL.hrsfc.ac.uk because the snapshot volume did not have sufficient storage space to hold the churn on the protected computer (ID 30115 Details: VssError:Insufficient storage available to create either the shadow copy storage file or other shadow copy data.

 (0x8004231F))

                More information

Recommended action:  Retry the operation at a later point when the churn is expected to be lower.

                Create a recovery point...

Can you please make sure that the volume on the protected server where the
databases reside have free sufficient disk space available for
snapshots

I have checked the pysical disk and indeed it does say it is full. However the accounts and the actual mailboxes where deleted yesterday so I do not understand why it is still showing as full. Any ideas on how I can create the necessary space needed for the snapshots?

Many thanks

Rowan

What kind of configuration of volumes do you have on your exchange server? 

What operating system is your Exchange server?

It is possible to use a different volume to store VSS Snapshots. As an example, set c:\ to store its shadow copies on a completely different volume. Its rather simple in 2008 R2 to modify the shadow copy storage location to another volume, and you could do that as a work around to get a backup until you resolve your exchange issues.

I do believe that exchange doesn't delete the mailboxes for 30 days after 'deletion'. Though, there are cmdlets to remove the deleted mailboxes permanently.  Check out http://technet.microsoft.com/en-us/library/ff829913(v=exchg.141).aspx  for the Remove-StoreMailbox cmdlet.

Regards,

Kyle

• Marked as answer by rowan68 Thursday, July 11, 2013 8:30 AM

What kind of configuration of volumes do you have on your exchange server? 

What operating system is your Exchange server?

It is possible to use a different volume to store VSS Snapshots. As an example, set c:\ to store its shadow copies on a completely different volume. Its rather simple in 2008 R2 to modify the shadow copy storage location to another volume, and you could do that as a work around to get a backup until you resolve your exchange issues.

I do believe that exchange doesn't delete the mailboxes for 30 days after 'deletion'. Though, there are cmdlets to remove the deleted mailboxes permanently.  Check out http://technet.microsoft.com/en-us/library/ff829913(v=exchg.141).aspx  for the Remove-StoreMailbox cmdlet.

Regards,

Kyle

• Marked as answer by rowan68 Thursday, July 11, 2013 8:30 AM

What kind of configuration of volumes do you have on your exchange server? 

What operating system is your Exchange server?

It is possible to use a different volume to store VSS Snapshots. As an example, set c:\ to store its shadow copies on a completely different volume. Its rather simple in 2008 R2 to modify the shadow copy storage location to another volume, and you could do that as a work around to get a backup until you resolve your exchange issues.

I do believe that exchange doesn't delete the mailboxes for 30 days after 'deletion'. Though, there are cmdlets to remove the deleted mailboxes permanently.  Check out http://technet.microsoft.com/en-us/library/ff829913(v=exchg.141).aspx  for the Remove-StoreMailbox cmdlet.

Regards,

Kyle

• Marked as answer by rowan68 Thursday, July 11, 2013 8:30 AM

What kind of configuration of volumes do you have on your exchange server? 

What operating system is your Exchange server?

It is possible to use a different volume to store VSS Snapshots. As an example, set c:\ to store its shadow copies on a completely different volume. Its rather simple in 2008 R2 to modify the shadow copy storage location to another volume, and you could do that as a work around to get a backup until you resolve your exchange issues.

I do believe that exchange doesn't delete the mailboxes for 30 days after 'deletion'. Though, there are cmdlets to remove the deleted mailboxes permanently.  Check out http://technet.microsoft.com/en-us/library/ff829913(v=exchg.141).aspx  for the Remove-StoreMailbox cmdlet.

Regards,

Kyle

• Marked as answer by rowan68 Thursday, July 11, 2013 8:30 AM

What kind of configuration of volumes do you have on your exchange server? 

What operating system is your Exchange server?

It is possible to use a different volume to store VSS Snapshots. As an example, set c:\ to store its shadow copies on a completely different volume. Its rather simple in 2008 R2 to modify the shadow copy storage location to another volume, and you could do that as a work around to get a backup until you resolve your exchange issues.

I do believe that exchange doesn't delete the mailboxes for 30 days after 'deletion'. Though, there are cmdlets to remove the deleted mailboxes permanently.  Check out http://technet.microsoft.com/en-us/library/ff829913(v=exchg.141).aspx  for the Remove-StoreMailbox cmdlet.

Regards,

Kyle

• Marked as answer by rowan68 Thursday, July 11, 2013 8:30 AM

Hi all,

I had a similar issue at a client of us and I resold it :-)

You can try this command.

>vssadmin add shadowstorage /for=D: /on=D: /maxsize=UNBOUNDED

Regards