Getting Started - Windows File System iDataAgent Deployment On A Non-Microsoft Cluster

1. Start the Registry Editor (Regedit.exe or Redegt32.exe)
2. Locate the directory under which you want to create a key, e.g., HKEY_LOCAL_MACHINE\SOFTWARE\.
3. Right click the SOFTWARE and click New -> Key.
4. Name the key as GalaxyInstallerFlags.
5. Right click the GalaxyInstallerFlags and select New -> DWORD value, name it as bIgnoreClusterVMCheck and by double clicking the bIgnoreClusterVMCheck key modify the Value data to 1.

Click Next.

Click Next.

Click Next.

• In the disk groups box, specify the host name of the Virtual Host created for backup, e.g., VirtualVeritasServe.
• In the Communication Interface Name box, specify the fully qualified domain name of the Virtual Host, e.g., VirtualVeritasServe.acme.com.
• Click Next.

Specify the name of active node in Current Owner Node box.

Click Next.

NOTES

• If you click No the program will perform the passive install. Follow the steps described in Manually Installing the Software on a Passive Node.
• This screen may look different from the example shown.

Click Next.

For firewall options and configuration instructions, see Firewall Configuration and continue with the installation.

If firewall configuration is not required, click Next.

Click Next.

Click Next.

Click Browse to change the default location.

Click Next.

This screen will be displayed if Client Groups are configured in the CommCell Console.

Click Next.

Also, you may want to designate the services as "critical" if you want to cause the virtual machine to fail over if the associated service stops.

• In Windows Services, locate the services for each installed cluster (e.g., Bull Calypso Cluster Plugin (penodevn1_netwo) (instance001)) right-click and select Properties, and locate the service name in the General tab (e.g., GxClusPlugin (penodevn1_netwo) (Instance001))

  The service name is case- and space-sensitive, so record it exactly as it appears.

• In Cluster Administrator, navigate to the appropriate Cluster group. Create a generic service resource for the cluster plugin service.
• If you want an automatic failover to occur, mark the resource as Critical and Enabled.
• Repeat this procedure for each client installed on the cluster.

• In Cluster Administrator, click Resources.
• Click Link and make the Cluster plugin resource dependent upon the Mount resource and the Lanman service.

• In Cluster Administrator, navigate to the appropriate GenericService group.
• Right-click the cluster plugin resource.
• From the short-cut menu, click Online and the name of the current active node.

1. Start the Registry Editor (Regedit.exe or Redegt32.exe)
2. Locate the directory under which you want to create a key, e.g., HKEY_LOCAL_MACHINE\SOFTWARE\.
3. Right click the SOFTWARE and click New -> Key.
4. Name the key as GalaxyInstallerFlags.
5. Right click the GalaxyInstallerFlags and select New -> DWORD value, name it as bIgnoreClusterVMCheck and by double clicking the bIgnoreClusterVMCheck key modify the Value data to 1.

• In the PolyServe Matrix Server, create a virtual host resource name that has an assigned TCP/IP address in the network.
• Provide a virtual host name (e.g., VirtualPolyServe.acme.com) and an Application name (e.g., VirtualPolyServe).
• Select all network Interfaces that will be available as hosts for the backup software services and click OK.

Click Next.

Click Next.

Click Next.

• In the disk groups box, specify the host name of the Virtual Host created for backup, e.g., VirtualVeritasServe.
• In the Communication Interface Name box, specify the fully qualified domain name of the Virtual Host, e.g., VirtualVeritasServe.acme.com.
• Click Next.

Specify the name of active node in Current Owner Node box.

Click Next.

Click Next.

For firewall options and configuration instructions, see Firewall Configuration and continue with the installation.

If firewall configuration is not required, click Next.

Click Next.

NOTES

• The client name should be equivalent to the vhost name and the interface name equals the vhosts fully qualified domain name.

Click Next.

Click Browse to change the default location.

Click Next.

This screen will be displayed if Client Groups are configured in the CommCell Console.

Click Next.

• Probe script is used to reveal the state of the specified services. This is done using the GxSCMCmd.exe utility.
• Start script is used to start services.
• Stop script is used to stop services.

Create a probe script to have the status of both the Bull Calypso Communications Service (GxCVD) and the Bull Calypso Event Manager Service (GxEvMgrC) checked. In the probe script, include the GxSCMCmd.exe utility by name in the appropriate command. (This utility is available from the Resource Pack. See Tools and Utilities for more information.) Create a folder (e.g., m:\GxSCMCmd) on a shared disk that the virtual host you created has access to. Copy the GxSCMCmd.exe utility and the script files you created (probe.bat, start.bat, stop.bat) to this folder. The utility will return the state of the specified services: '0' if the services are running or '1' if services are stopped. For an error condition, '-1' is returned. Note that the service name includes the name of the client and the name of the instance. To avoid error in providing the vhost name and instance name in the path of scripts, copy the key name from here: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\GXClusPlugIn (vhostname) (Instance00x)

The command syntax is:

GxSCMCmd.exe -IsRunning <list of service name>

For example, your probe script (e.g., m:\GxSCMCmd\gxprobe.bat) may appear as follows:

@echo off

if'%MX_ACTIVE_STATE%'='INACTIVE' exit 0

m:\GxSCMCmd\GxSCMCmd.exe -IsRunning "GxClusPlugIn (virtualpolyserve) (Instance001)"

if ERRORLEVEL 0 exit 0

exit 1

Be sure to copy the GxSCMCmd.exe utility to the shared disk resource. Also, be sure to include the probe script on the shared disk.

The stop and start scripts must also contain the registry entry for the virtual machine service names. Your start script (e.g., m:\GxSCMCmd\gxstart.bat) may appear as follows:

@echo off

C:\WINDOWS\system32\net.exe start "GxClusPlugIn (virtualpolyserve) (Instance001)"

exit 0

Your stop script (e.g., m:\GxSCMCmd\gxstart.bat) may appear as follows:

@echo off

C:\WINDOWS\system32\net.exe stop GxClusPlugIn (virtualpolyserve) (Instance001)

exit 0

Add the custom service monitor to the virtual host configuration in the PolyServe Matrix Server console.

1. Ensure that the virtual host name <virtualpolyserve> is online.
2. From the Services MMC snap-in, verify or manually start the cluster plugin service, "Bull Calypso Cluster Plugin (virtualpolyserve) (Instance00x)", on the active primary node for the Vhost virtualpolyserve
3. From the PolyServe Matrix Server, click the Virtual Hosts tab.
4. Right click Virtual Host <virtualpolyserve> and then Add Service Monitor.
5. For the Monitor Type field in the Add Service Monitor dialog box, click CUSTOM.
6. Assign a name to the service monitor by typing the name in the Name field.
7. In the User probe script field, type the path to the probe script that calls the GxSCMCmd.exe command (on the share disk)
8. Click Advanced.
9. From the Advanced Service Configuration dialog box, click the Scripts tab.
10. In the Script pathname: Start field, type the path to the start script (shared disk). In the corresponding Timeout (seconds) field, type a timeout value greater than 60 seconds.
11. In the Script pathname: Stop field, type the path to the stop script (shared disk). In the corresponding Timeout (seconds) field, type a timeout value greater than 60 seconds.
12. Click OK once, then again.

The monitor should now start, and the primary node should now be active. Failover will occur if services are disabled on the primary node, and services in such a case will move to a secondary node.