Summary

This Knowledgebase article provides information about how to setup Data Rollback and Volume Shadow Copy in Neverfail Continuity Engine.

More Information

The Data Rollback Screen 

Neverfail Continuity Engine’s Data Rollback Module helps avoid problems associated with corrupt data, by enabling data rollback to an earlier point-in-time should data corruption occur.

To configure this feature, navigate to the Engine Management Service Shadows page. Before configuring or using any of the Data Rollback Module features, it is recommended that you first read through and follow the best practices for Using Volume Shadow Copy Service (VSS) and the Data Rollback Module, described below.

Procedure 

Best Practices for Using Volume Shadow Copy Service & Data Rollback Module

The storage of Shadow Copies is performed by the Shadow Copies component of Windows 2008 and 2012. See 

https://help.neverfail.com/portal/kb/articles/how-to-configure-windows-server-2008-and-2012-to-store-shadow-copies-20-11-2019-1

 - 'How to Configure Windows Server 2008 or 2012 to Store Shadow Copies'.

The recommended steps are:

• Decide which volume to use for storing shadow copies before using the Data Rollback Module. This is because before you can change the storage volume, you must delete the existing shadow copies.
• It is recommended that a separate volume be allocated for storing shadow copies.  Do not use a volume for storing both, data that is protected by Neverfail Continuity Engine together with data that is not protected, yet updated regularly. For example, do not write backups of data (even temporary) to a volume that contains Neverfail Continuity Engine protected files, as that would increase the space used for snapshots.

In accordance with Microsoft guidelines: 

"Select a separate volume on another disk as the storage area for shadow copies. Select a storage area on a volume that is not being shadow copied. Using a separate volume on another disk provides two advantages. First, it eliminates the possibility that high I/O load will cause shadow copies to be deleted. Second, this configuration provides better performance.”  

• Ensure that you allocate enough space for the shadow copies you wish to retain. This will be dependent on the typical load for your application, such as the number and size of emails received per day, or the number and size of transactions per day. The default is only 10% of the shadowed volume size, so this should be increased. Ideally, dedicate an entire volume on a separate disk to Shadow Storage.
• Configure the schedule to match your clients' working patterns, considering both the required granularity of data-restoration, and the available storage.

The Data Rollback Module provides a means of flexibly scheduling the creation of new shadow copies, and the deletion of older shadow copies. This should be adjusted to the working-patterns of your clients and applications. For example, do clients tend to work 9am-5pm, Monday-Friday in a single time zone, or throughout the day across multiple time zones?  You should avoid taking shadow copies during an application's maintenance period, such as Exchange defragmentation, or a nightly backup. In selecting how frequently to create new shadow copies, and how to purge older ones, you must balance the needs for fine-granularity of restorable points-in-time versus the available disk space and the upper limit of 512 Shadow Copies across all shadowed volumes on the server.
 
Note: The schedule referred to in the Volume Properties > Shadow Copies > Settings dialog is for Shadow Copies for Shared Folders. This is not used for Data Rollback Module - the Data Rollback Module schedule is configured on the Shadows > Configure panel of the Engine Management Client.

Perform a Trial Rollback

Once you have configured the Data Rollback Module, it is recommended that you perform a trial rollback, to ensure that you understand how the process functions, and that it operates correctly.

IMPORTANT: all protected applications MUST be stopped during rollback (this is done automatically by Neverfail Continuity Engine), which means they will not be available to users. 

Note:  All client application files must be closed prior to conducting a rollback to ensure all data is rolled back to the previous state.

PERFORMING A DATA ROLLBACK WITHOUT FULLY UNDERSTANDING HOW DATA ROLLBACK FUNCTIONS AND THE CONSEQUENCES ON A SERVER PAIR, CAN LEAD TO UNDESIRED RESULTS.

If you do not select the option ‘Restart applications and replication automatically after rollback’, then you will be able to rollback to Shadow Copies on the passive Server without losing the most recent data.

You will be able to start the application(s) manually, in order to check that it starts successfully using the restored data.  Once the test has completed to restart using the application data, as it was immediately before the rollback, you should:

1. Shutdown Neverfail Continuity Engine on both servers. 
2. Use the 'Server Configuration' wizard to swap the active and passive roles. 
3. Restart Neverfail Continuity Engine. This will resynchronize the two servers.

Monitor Neverfail Continuity Engine in Order to Identify any Shadow Copies Being Discarded by VSS

If the Data Rollback Module finds that any shadow copies it expects to be present have been deleted, it will note this in the Neverfail Continuity Engine Event Log. The log can be inspected by opening the Engine Management Service and clicking on the Events tab and reviewing the Event Log. This is an indication that VSS has reached its limit of available space or number of shadow copies. If many shadow copies are automatically discarded, then you should consider adding more storage, or reconfiguring your schedule to create and maintain fewer shadow copies.

Applies To

Neverfail Continuity Engine

Related Information

None