How to create a DK Replicated Volume that has Multiple Targets via CLI

The environment in this example looks like this:

*The Goals:

• To create a synchronous mirror from PRIMARY to SECONDARY and an asynchronous mirror from PRIMARY to DR.


• To verify the DataKeeper Job knows how to create a mirror from SECONDARY to DR in case the SECONDARY or DR server ever become the source of the mirror.

EMCMD will be used to create this multiple target mirror. The DataKeeper documentation describes this as a Mirror with Multiple Targets.

1. Run cd %extmirrbase% to get to the DK folder to run the following emcmd commands.

2. Create the Job that contains all this possible endpoints and define whether the mirror will be Sync (S) or Async (A) between those endpoints.

• emcmd . createjob ddrive sqldata

*Note: This single “createjob” command creates the Job.

3. Create the mirrors.

• emcmd 10.0.2.100 createmirror D 10.0.1.10 A
• emcmd 10.0.2.100 createmirror D 10.0.3.100 S

Our DataKeeper Job should now look like this in the DataKeeper UI

One-to-Many DataKeeper Replicated Volume

Now, we can register the DataKeeper Volume Resource in the cluster Available Storage with this command.

• emcmd . registerclustervolume D

The DataKeeper Volume Resource will now appear in Available Storage as shown below.

DataKeeper Volume in Available Storage

We are now ready to install SQL Server, SAP, File Server or any other clustered resource you normally protect with Windows Server Failover Clustering.

*This information was extracted from the Clustering for Mere Mortals article.