Summary

This Knowledgebase article provides information about attempting to perform a Data Rollback when protecting Microsoft Exchange 2013 on Windows Server 2008 R2 SP1 or Windows Server 2012 failing.

More Information

Symptoms

Attempting to perform a Data Rollback when Microsoft Exchange 2013 is protected and running on Windows Server 2008 R2 SP1 or Windows Server 2012 fails and results in an Out-of-Sync state.

Cause

When a shadow is created before a Data Rollback and then a Data Rollback is performed afterwards, Neverfail Heartbeat blocks some of the Exchange 2013 .dll files.

Resolution

If a shadow copy is not desired before performing a Data Rollback:

• Restart Neverfail Heartbeat on all servers opting to leave protected applications running.

If a shadow copy is desired before performing a Data Rollback:

1. Create a shadow copy.
2. Restart Neverfail Heartbeat on all servers opting to leave protected applications running.

If a Data Rollback was attempted before restarting Neverfail Heartbeat:

Note: Attempting Data Rollback without restarting Neverfail Heartbeat will cause the rollback to fail and leave the file system in an Out-of-Sync state.

1. Restart Neverfail Heartbeat on all servers opting to leave protected applications running.
2. Initiate the Data Rollback procedure.

Note: It is not necessary to wait for the servers to synchronize, when Neverfail Heartbeat is restarted, a Full System Check will start automatically.

Applies To

Neverfail Heartbeat v6.7 protecting Microsoft Exchange 2013 up to SP1 on:
Windows Server 2008 R2 SP1
Windows Server 2012 and 2012 R2

Related Information

None

KBID-2600