Create an Application Consistency Protection Plan

By adding a consistency policy to an existing data protection plan, you can specify which data to protect and create bookmarks in the data as roll back targets.

Prerequisites

Before you create an application consistency protection plan, you must first create either a synchronous or asynchronous data protection plan.
  1. Navigate to Protect > Manage Protection Plan and locate your previously created data protection plan.
  2. Click Manage Consistency Policy.
  3. Click Add Consistency.
  4. In the Consistency Options table, select the name of the application server from the Select Host drop-down list.
  5. Select the type of application consistency policy to set up.
    Application Agent
    To protect data for a specific operating system, select one of the following applications:
    • Microsoft Exchange Server 2003, 2007, or 2010

    • Microsoft SQL Server 2000, 2005, or 2008

    • Oracle (Unix/Linux), RAC, CFS

    Other Volumes

    To create consistency bookmarks for a particular volume rather than for a specific application, specify the actual volumes on the host in the field.

  6. Click Save.
    Result:
    Your consistency policy appears in the Consistency Policies list with a command line in the Consistency Option column that corresponds to the information you entered in the Consistency Options table.
  7. Click Activate in the Action column of the Consistency Policies list to activate your consistency policy.
  8. Verify that the consistency policy has been activated.
    • Navigate to Monitor > File Replication.

    • In the File Protection Status table, expand the consistency policy job that you created.

    • Verify that the job Status is Completed and that the Start Time and End Time correspond with the creation of your consistency policy.

  9. In the host application event log, verify that an event that reports the tag was sent successfully.
    Display the properties for the InMageVssProvider event, and verify that the bookmark tags were successfully sent to the remote server.