Work with RNs in Windows Cluster Services Environment

Before performing these procedures, make sure to complete the Configure Quorum onQ Service procedure.

To configure the onQ Appliance:

1.	Turn onQ Protection OFF.

2.	Upgrade onQ to 3.6 HF1, if not already at that release level.

3.	Putty or Terminal into the hypervisor

4.	Download the SAN template and store it locally on the hypervisor (preferably under /var/run/sr-mount/xxxxxxxxx-xxxx-xxxx-xxxx folder).

5.	In the console command prompt, do the following:

a.	Extract the SAN template to its original size. When extracted the template should end with .xva extension.

# gunzip SAN-TEMP.cluster.xva.gz

b.	Run the following command, then record the uuid for the item with name-label set to VHD_SR:

# xe sr-list

c.	Using the uuid that you just identified, run the following command:

The import can take a long time. Nonetheless, the command returns immediately, and so you can monitor the import using XenCenter’s log screen; also, when the import disappears from the ps -ef command output, the import completed.

# xe vm-import filename=SAN-TEMP.cluster.xva sr-uuid=<UUID>

To import a template and create the VHD on the hypervisor can take 10-15 minutes.

To enroll the cluster on onQ:

1.	Do the following:

a.	Stop protection.

b.	Go to the Protection Config tab.

c.	Click + to enroll the cluster.

d.	In the Hostname field, enter the cluster name.

If the cluster name is not known, run the following command on the active cluster node:

> cluster /PROPERTIES

e.	Set other parameters as needed.

f.	Configure the cluster node and SAN disks that are associated with the cluster. Verify that the Disk Letter and corresponding Size for each disk is appropriate.

g.	Click SAVE.

2.	Click on the Modify button, then in the protection list, add all volumes and applications that the cluster requires.

If you are enrolling the PN for the first time using the Protect Me button on the onQ Portal, then all volumes (local and iSCSI) on the PN are auto discovered.

3.	Click on the Advanced button, then in the window, set the radio button for Enable Cluster Support to Yes to display additional fields for the configuration.

4.	From the expanded display for cluster configuration, do the following:

a.	Select the volumes pertaining to cluster services and also any application or other services desired from the list for ‘Cluster Volumes’.

b.	In the Virtual SAN IP Address field, type a valid and unique IP address that you want to be used with the virtual SAN. The IP used should be in the same subnet as that of onQ. Also, this IP should not be the same as that of physical SAN currently used with the PN.

c.	Type a gateway address that is associated with the virtual SAN IP address.

d.	Type a subnet mask for the virtual SAN.

5.	SAVE the protected node configuration.

6.	Do the following:

a.	Go to APPLIANCE CONFIG tab > ADVANCED… button > HOSTS tab.

b.	In the IP Address field, type the cluster (shared) IP address.

c.	In the Host(s)/comments field, type the cluster name.

d.	Click + to add the host.

e.	Click APPLY.

To back up the PN:

1.	Start protection.

2.	Trigger (scheduled or manual) backups as needed for the configured node.

3.	Allow the backup to complete and the RN to be built.

4.	If new volumes were added to protection, re-initialize the RN to trigger a complete RN build.

If the PN is added for the first time, this is not required.

To start the RN in test mode (Windows 2003):

Start the Recovery Node for the Domain Controller first in test mode, if the cluster is configured to work with a domain account.

1.	Create and start the RN and iSCSI SAN clones. To do so, select the Recovery Node for the cluster node and start it in Test Mode

2.	In the RN console for the cluster node, do the following:

a.	Log on with same administrative account that you used on the PN.

If necessary, to log on to the virtual SAN use the default password for the root user account. If you do not know this password, contact Quorum Support.

b.	From a command prompt on the RN, run the following:

> cd /d c:\Program Files\Quorum\usr\ONQSUP > CLUSSERVICEFQ.BAT

3.	Start the Microsoft iSCSI initiator.

4.	Select the Targets tab, then log off from any existing or reconnecting targets.

5.	Select Discovery tab, then do the following:

a.	In the Target Portals section, remove any residual entries.

b.	Select Discover Portal > ADD, then type the virtual SAN IP that was provided earlier when you configured the PN in the onQ Portal. Leave the default port set to 3260.

c.

Click OK.

6.	Select Targets tab, then do the following:

a.	Select the default Target name or the appropriate one, if more than one exists, then Logon button.

b.	In the Log on to Target pop-up window, select the Automatically restore this connection check box, then OK.

c.	Select Persistent Targets tab, then ensure that the same target that you selected previously on the Targets tab appears in the list.

Note:  Click Finish to ignore any error while loading a driver for new hardware (IET Controller).

7.	Select OK on the main window to exit the iSCSI initiator setup.

8.	From a command prompt, do the following:

a.	Execute the following commands:

> cd C:\Program Files\Quorum\usr\ONQSUP > FIX_CLUSTER.BAT

b.	Ignore errors at the end of the output and ascertain that the cluster service started.

c.	Rejoin the domain, if cluster service fails to start because the RN does not have a domain trust relationship established.

d.	Restart the cluster service.

9.	Launch Cluster Administrator interface, then do the following:

a.	If the Open Connection to Cluster dialog doesn’t appear, use the FileOpen Connection dialog.

b.	In the Open Connection to Cluster dialog, choose Open Connection to Cluster value in the drop‑down menu.

c.	In the Cluster or server name field, type a value ‘.’ (dot), then OK.

d.	Under Groups, ensure that Cluster Group and any other Application Cluster (SQL Cluster for example) are all on-line, indicating that the cluster is in a usable state.

To start the RN in test mode (Windows 2008):

Start the Recovery Node for the Domain Controller in test mode, if the cluster is configured to work with a domain account.

1.	Create and start the RN and ISCSI SAN clones. To do so, select the Recovery Node for the cluster node, then start it in Test Mode.

2.	In the RN console for the cluster node, do the following:

a.	Log on with same administrative account that you use on the PN.

If necessary, to log on to the virtual SAN use the password password for the root user account.

b.	From a command prompt on the RN, run the following:

> cd /d c:\Program Files\Quorum\usr\ONQSUP > CLUSSERVICEFQ.BAT

3.	Start the Microsoft iSCSI initiator.

4.	Select the Targets tab, then log off from any existing or reconnecting targets.

5.	Select Discovery tab, then do the following:

a.	In the Target Portals section, remove any residual entries.

b.	Select Discover Portal > Add Portal, then type the virtual SAN IP that was provided earlier when you configured the PN in the portal. Leave the default port set to 3260.

c.

Click OK.

6.	Select Targets tab, then do the following:

a.	Select the default Target name or the appropriate one, if more than one exists, then click on the Logon button.

b.	In the Log on to Target pop-up window, select the Automatically restore this connection check box, then OK.

7.	Select Volumes and Devices tab to list the volumes that reflect the cluster disks. If none appear, choose Autoconfigure to force the iSCSI properties to display all cluster volumes configured, then OK.

8.	From a command prompt, do the following:

a.	Execute the following commands:

> cd C:\Program Files\Quorum\usr\ONQSUP > FIX_CLUSTER.BAT

b.	Verify that all disks are marked as Reserved using the diskpart command. If all volumes expected are not listed and/or are not marked as Reserved after few minutes from RN starting, reboot the RN.

9.	Rejoin the domain. If the cluster service fails to start because RN does not have a domain trust relationship established, then restart the cluster service.

10.	Launch the Failover Cluster Manager interface to perform additional administration, if necessary: Start > Administrative Tools > Failover Cluster Manager.

•	When the interface comes up, the left hand pane lists the clusters available along with the Services and applications, Nodes, Storage, and Networks associated with them.

•	Select the items under Services and applications, to list the status of the cluster (server name, disk drives and other resources) as it relates to the specific application. The Status of all of these items listed display on-line to indicate that the cluster is in a usable state.

To start the RN in test mode (Windows 2008 R2 & 2012):

Start the Recovery Node for the Domain Controller in test mode, if the cluster is configured to work with a domain account.

1.	Create and start the RN and ISCSI SAN clones. To do so, select the Recovery Node for the cluster node, then start it in Test Mode.

2.	In the RN console for the cluster node, do the following:

a.	Log on with the administrative account (local or domain if configured for domain) for the PN.

If necessary, to log on to the virtual SAN, use the password password for the root user account.

b.	From a command prompt on the RN, run the following:

> cd /d c:\Program Files\Quorum\usr\ONQSUP > CLUSSERVICEFQ.BAT

3.	Start the Microsoft iSCSI initiator.

4.	Select the Targets tab, then disconnect from any existing targets.

5.	Select Discovery tab, then do the following:

a.	Remove any residual entries under Target Portals and iSNS servers sections.

b.	Select Discover Portal. Type the virtual SAN IP that you used to configure the PN in the onQ Portal. Leave the default port set to 3260. Click OK.

6.	Select Targets tab, then do the following:

a.	Select the Target name from under Discovered Targets. If the Status for the same is Inactive, then click on the Connect button, bringing the Status to Connected.

b.	If the Target name doesn’t display, type the target IP (same as the virtual SAN IP in the Discovery tab), then Quick Connect to connect to the virtual SAN, bringing the Status to Connected.

7.	Select Volumes and Devices tab to list the volumes that reflect the cluster disks. If none appear, choose Auto Configure to force the iSCSI properties to display all cluster volumes configured, then OK.

8.	From a command prompt, do the following:

a.	Execute the following commands:

> cd C:\Program Files\Quorum\usr\ONQSUP > FIX_CLUSTER.BAT

b.	Verify that all disks are marked as Reserved using the diskpart command. It might take a long time for the volumes to reflect Reserved or to appear in the list from list vol command. If still not correctly listed after 30 minutes, reboot the RN.

9.	If the cluster service fails to start (for example, you cannot see the cluster in the Failover Cluster Manager) or there are issues seeing the domain controller, rejoin the domain.

10.	Launch the Failover Cluster Manager interface to perform additional administration, if necessary: Start > Administrative Tools > Failover Cluster Manager.

•	When the interface comes up, the left hand pane lists the clusters available along with Services and applications, Nodes, Storage, and Networks associated with them.

•	Select the items under Services and applications, to list the status of the cluster (server name, disk drives and other resources) as it relates to the specific application. The Status of all of these items listed display on-line to indicate that the cluster is in a usable state.

To start the RN in production mode:

1.	Before your start the RN, do the following:

a.	Ensure that physical iSCSI target SAN is turned off and/or the drives configured to work with cluster node are not accessible.

This is a precautionary step. The Recovery Node registry is updated with the information provided in the onQ Portal for the virtual SAN.

b.	Ensure that all failover nodes in the cluster are turned off.

The RN you choose must have the latest backup in order for the data to be correct. Only one RN at a time can run in the cluster. When the RN is running in the production cluster, failover is not available.

2.	Start the Recovery Node in production mode. Go to Start recovery nodes on HA Appliance or Start recovery nodes on DR Appliance or DR Mirror.

3.	Perform the procedure for your respective platform. The remaining steps are identical to those for test mode.

•	To start the RN in test mode (Windows 2003):

•	To start the RN in test mode (Windows 2008):

•	To start the RN in test mode (Windows 2008 R2 & 2012):

 

v3.6 HF1