Consider the following software configuration requirements before configuring an application for DR:

• Make sure that the latest Adobe Flash Player plugin is available for the browser that you use to access the Console UI.

• Adobe Flash Player must be enabled for use on systems that run Windows Server 2012.

• The authentication (AT) service requires that an endpoint with the port number 14153 is configured on the Console host and the Client hosts.

• The application that you want to configure for DR must be configured for monitoring on the on-premises application host and the cloud application host. If application monitoring is not configured on any of these systems, the Disaster Recovery Orchestrator Configuration Wizard prompts you to do so. You can launch the Application Monitoring Configuration Wizard from within the DR configuration wizard. After the application monitoring configurations are in place on both the systems, you can proceed to configure the application for recovery.

• Ensure that User Access Control (UAC) is disabled on all the systems that participate in the DR solution.

• Ensure that the appropriate users are configured on the Privilege Settings view of the Console UI.

• The following SQL Server configuration items on the cloud application hosts must match those on the corresponding on-premises application hosts exactly:

  • Installation directory, name, and ID of each instance

  • Drive letters of the data volumes

  • Installation directory and name of each user-defined database

  • Users

• Ensure that the following patches are installed on the on-premises application host and the cloud application host for SQL Server. These patches are required for the sqlcmd utility commands to work, and they must be installed in the following order:

  • http://www.microsoft.com/en-us/download/confirmation.aspx?id=36434

  • http://www.microsoft.com/en-us/download/confirmation.aspx?id=36433

Consider the following storage and replication requirements before configuring an application for DR:

• During the time that Disaster Recovery Orchestrator Console is hosted on the virtual machine, a disk must not be manually attached or detached. Disaster Recovery Orchestrator must manage the addition or removal of any storage on this virtual machine.

• The disks must not be part of a storage pool. If you use a volume created in a storage pool, the takeover and failback operations will eventually fail.

• The Windows automount feature must be enabled on the Console host. The replication service driver needs the volumes to be mounted so that it can access the file replication configurations.

  For more information, see the Microsoft article:

  http://technet.microsoft.com/en-us/library/cc753703.aspx

• Sufficient space must be available on the volumes that are used to store the application data.

  If required, the volumes can be resized even after replication is configured.

• The application data must be stored at identical locations on the on-premises application host and the corresponding cloud application host. This is required for configuring replication between the two sites, which ensures that application data is synchronized.

  The following criteria must be satisfied:

  • The folders to be mapped for replication must exist at both locations.

  • The drive letters of the volumes on which the folders are located must match exactly.

• The journal file size must be defined appropriately. Although the minimum requirement is 1 GB, Symantec recommends that you set the journal file size to 10 GB for better performance.

  Specify a size that fits within the space that is currently available on the volume. You can change the journal file size for each application later from the corresponding Settings page.

• The disk on which the journal file is located (replication log volume) must not be detached while the replication is in progress.