Creating a GeoCluster Replicated Disk resource

1. From the Failover Cluster Manager, right-click the group that you want to add a replicated disk to and select New, Resource.
2. Specify the following fields on the New Resource dialog box.
• Name—Specify a name that identifies which application, file set, disk, and so on that you are protecting. This name must be unique within the cluster.
• Description—You can optionally add a more detailed description for this resource.
• Resource type—Specify GeoCluster Replicated Disk.
• Group—The group that you originated the new resource from will be selected. Verify that this is the correct group. If it is not, select the correct group name.
3. Click Next to continue.
4. The GeoCluster Replicated Disk resource ensures that an up-to-the-minute copy of the data resides on all nodes identified in the Possible owners list. All nodes are included in the default, which should not be changed. Click Next to continue.
5. The GeoCluster Replicated Disk resource is not dependent on any other resources. Click Next to continue.
6. Specify the GeoCluster Replicated Disk parameters using the settings below.
• Disk to replicate—Select a disk to replicate from the available volumes. The only volumes that will be displayed are those that meet the following criteria.
• NTFS volumes
• Volumes which are not already being replicated by another GeoCluster Replicated Disk resource
• Volumes that are not physical disk resources
• Volumes that do not contain system files (The volume that you booted Windows from will not be displayed.)
• Volumes that exist on all nodes of the cluster
• Network—Select the network that you want to use for Double-Take mirroring and replication traffic. If you do not have multiple networks established, you will only be able to select the one network that does exist. If you do not select a network, Double-Take will use DNS to determine a network route to use. Ideally, the networks used for various traffic should be separated. This is dependent on the number of networks that you established when you created the cluster and the priority assigned to each network. For example, if you have two network routes, separate Double-Take and your public traffic. If you have three routes, separate the public traffic and then separate Double-Take from the cluster heartbeat.
• Interval to check unresponsive nodes—Specify how much time, in seconds, between checks of nodes to see if a Double-Take connection can be made.
• Delay connection until resources dependent on this one are online—This option allows you to delay a Double-Take connection until any resources that have the GeoCluster Replicated Disk resource as a dependency are online. By ensuring that all resources that are dependent on the GeoCluster Replicated disk resource are online before starting the connection, the chance of a conflict occurring because application resources are attempting to open files exclusively while Double-Take is mirroring those files is removed.
7. Click Next to continue.
8. An orphan is a file that exists in the target location but is not in the source location. You can select to delete orphans during a mirror.
9. Click Next to continue.
10. If you want to configure compression, verify that Enable Compression is selected. Depending on the compression algorithms available for your operating system, you may see a slider bar indicating different compression levels. Set the level from minimum to maximum compression to suit your needs.
11. Click Next to continue.
12. Specify your Double-Take mirroring settings.
• Full Mirror—All files will be sent from the source to the target.
• File differences—Only those files that are different based size or date and time will be sent from the source to the target.

• Send data only if Source is newer than Target—Only those files that are newer on the source are sent to the target.

  If you are using a database application, do not use the newer option unless you know for certain you need it. With database applications, it is critical that all files, not just some of them that might be newer, get mirrored.

   

• Use block checksum—For those files flagged as different, the mirror performs a checksum comparison and only sends those blocks that are different.
• Calculate Replication Set size prior to mirror—Determines the size of the protected data set prior to starting the mirror. The mirroring status will update the percentage complete if the data set size is calculated.
13. Click Finish to complete the creation of the GeoCluster Replicated Disk resource.
14. To control the resource, you can bring it online and take it offline. Neither of these actions trigger failover. They just control the activity of the resource.

1. From the Failover Cluster Manager, right-click the application group or role where you want to add a replicated disk to and select Add a resource, More resources, Add GeoCluster Replicated Disk (for Windows 2008) or GeoCluster Replicated Disk (for Windows 2012).
2. Right-click on the new resource and select Properties.
3. On the General tab, specify a name that identifies which application, file set, disk, and so on that you are protecting. This name must be unique within the cluster.
4. On the Connection Parameters tab, specify the GeoCluster Replicated Disk connection parameters using the settings below.
• Disk to replicate—Select a disk to replicate from the available volumes. The only volumes that will be displayed are those that meet the following criteria.
• NTFS volumes
• Volumes which are not already being replicated by another GeoCluster Replicated Disk resource
• Volumes that are not physical disk resources
• Volumes that do not contain system files (The volume that you booted Windows from will not be displayed.)
• Volumes that exist on all nodes of the cluster
• Network to route Double-Take mirroring and replication traffic over—Select the network that you want to use for Double-Take mirroring and replication traffic. If you do not have multiple networks established, you will only be able to select the one network that does exist. If you do not select a network, Double-Take will use DNS to determine a network route to use. Ideally, the networks used for various traffic should be separated. This is dependent on the number of networks that you established when you created the cluster and the priority assigned to each network. For example, if you have two network routes, separate Double-Take and your public traffic. If you have three routes, separate the public traffic and then separate Double-Take from the cluster heartbeat.
• Interval to check unresponsive nodes—Specify how much time, in seconds, between checks of nodes to see if a Double-Take connection can be made.
• Delay connection until resources dependent on this one are online—This option allows you to delay a Double-Take connection until any resources that have the GeoCluster Replicated Disk resource as a dependency are online. By ensuring that all resources that are dependent on the GeoCluster Replicated disk resource are online before starting the connection, the chance of a conflict occurring because application resources are attempting to open files exclusively while Double-Take is mirroring those files is removed.
5. On the Orphans tab, you will see the option to delete orphan files. An orphan is a file that exists in the target location but is not in the source location. You can select to delete orphans during a mirror.
6. On the Compression tab, you will see your compression configuration. If you want to configure compression, verify that Enable Compression is selected. Depending on the compression algorithms available for your operating system, you may see a slider bar indicating different compression levels. Set the level from minimum to maximum compression to suit your needs.
7. On the Mirror Properties tab, specify your Double-Take mirroring settings.
• Full Mirror—All files will be sent from the source to the target.
• File differences—Only those files that are different based size or date and time will be sent from the source to the target.

• Send data only if Source is newer than Target—Only those files that are newer on the source are sent to the target.

  If you are using a database application, do not use the newer option unless you know for certain you need it. With database applications, it is critical that all files, not just some of them that might be newer, get mirrored.

   

• Use block checksum—For those files flagged as different, the mirror performs a checksum comparison and only sends those blocks that are different.
• Calculate Replication Set size prior to mirror—Determines the size of the protected data set prior to starting the mirror. The mirroring status will update the percentage complete if the data set size is calculated.
8. No other settings are required for the GeoCluster Replicated Disk resource, although there are optional settings available. See GeoCluster Replicated Disk resource properties for details. Click OK to save the GeoCluster Replicated Disk configuration changes that you made.
9. To control the resource, you can bring it online and take it offline. Neither of these actions trigger failover. They just control the activity of the resource.

1. Create a virtual machine using the Hyper-V Manager. For details, see your Hyper-V documentation.
2. From the Failover Cluster Manager, cluster the virtual machine using the High Availability Wizard.
3. Take the virtual machine cluster group offline by right-clicking on it and selecting Take this resource offline (for Windows 2008) or Take Offline (for Windows 2012).
4. Right-click on the virtual machine cluster group and select select Add a resource, More resources, Add GeoCluster Replicated Disk (for Windows 2008) or GeoCluster Replicated Disk (for Windows 2012).
5. Right-click on the resource and select Properties.
6. On the General tab, specify a name that identifies which application, file set, disk, and so on that you are protecting. This name must be unique within the cluster.
7. On the Connection Parameters tab, specify the GeoCluster Replicated Disk connection parameters using the settings below.
• Disk to replicate—Select the volume where the virtual machine .vhd or .vhdx file is stored.
• Network to route Double-Take mirroring and replication traffic over—Select the network that you want to use for Double-Take mirroring and replication traffic. If you do not have multiple networks established, you will only be able to select the one network that does exist. If you do not select a network, Double-Take will use DNS to determine a network route to use. Ideally, the networks used for various traffic should be separated. This is dependent on the number of networks that you established when you created the cluster and the priority assigned to each network. For example, if you have two network routes, separate Double-Take and your public traffic. If you have three routes, separate the public traffic and then separate Double-Take from the cluster heartbeat.
• Interval to check unresponsive nodes—Specify how much time, in seconds, between checks of nodes to see if a Double-Take connection can be made.
• Delay connection until resources dependent on this one are online—This option allows you to delay a Double-Take connection until any resources that have the GeoCluster Replicated Disk resource as a dependency are online. By ensuring that all resources that are dependent on the GeoCluster Replicated disk resource are online before starting the connection, the chance of a conflict occurring because application resources are attempting to open files exclusively while Double-Take is mirroring those files is removed.
8. On the Orphans tab, you will see the option to delete orphan files. An orphan is a file that exists in the target location but is not in the source location. You can select to delete orphans during a mirror.
9. On the Compression tab, you will see your compression configuration. If you want to configure compression, verify that Enable Compression is selected. Depending on the compression algorithms available for your operating system, you may see a slider bar indicating different compression levels. Set the level from minimum to maximum compression to suit your needs.
10. On the Mirror Properties tab, specify your Double-Take mirroring settings.
• Full Mirror—All files will be sent from the source to the target.
• File differences—Only those files that are different based size or date and time will be sent from the source to the target.

• Send data only if Source is newer than Target—Only those files that are newer on the source are sent to the target.

  If you are using a database application, do not use the newer option unless you know for certain you need it. With database applications, it is critical that all files, not just some of them that might be newer, get mirrored.

   

• Use block checksum—For those files flagged as different, the mirror performs a checksum comparison and only sends those blocks that are different.
• Calculate Replication Set size prior to mirror—Determines the size of the protected data set prior to starting the mirror. The mirroring status will update the percentage complete if the data set size is calculated.
11. No other settings are required for the GeoCluster Replicated Disk resource, although there are optional settings available. See GeoCluster Replicated Disk resource properties for details. Click OK to save the GeoCluster Replicated Disk configuration changes that you made.
12. Modify the virtual machine and virtual machine configuration resources and add the GeoCluster Replicated Disk resource (not the GeoCluster Replicated Disk Status resource) as a dependency.

The GeoCluster Replicated Disk resource will appear offline after it is created. When you bring it online, the following actions occur.

1. A Double-Take job is created.
2. The job is connected to all of the possible owners specified in the resource (except the active node which is the source).
3. A mirror is initiated to create the baseline copy of data from the active node to all of the possible owners.
4. The drive where the mirrored data is located on each of the possible owners is made read-only to all other applications except Double-Take.
5. Real-time replication from the active node to all of the possible owners begins.

If you are using Windows 2003, right-click the resource and select Bring online.

If you are using Windows 2008, right-click the resource and select Bring this resource online.

If you are using Windows 2012, right-click the resource and select Bring Online.

When you take the GeoCluster Replicated Disk resource offline, the following actions occur.

1. Real-time replication from the active node to the possible owners stops.
2. The read-only limitation is removed from the corresponding drive letters on the possible owners.
3. The job is disconnected from all of the possible owners.
4. The job is deleted.

If you are using Windows 2003, right-click the resource and select Take offline.

If you are using Windows 2008, right-click the resource and select Take this resource offline.

If you are using Windows 2012, right-click the resource and select Take Offline.

If the GeoCluster Replicated Disk Resource is offline, it will impact any application depending on it. Data integrity cannot be guaranteed on the other nodes in the cluster.