Deployment - Non-Microsoft Cluster - SQL Server iDataAgent

Deployment Deployment - Microsoft Cluster Deployment - Non-Microsoft Cluster Configuration Backup Restore

Skip this page if you are not installing this agent on a non-Microsoft cluster, and continue to the next page.

Steps involved in installing the SQL Server iDataAgent in a Clustered environment:

  1. Install the Software on Physical Nodes

  2. Configure the Cluster Group Client

  3. Configure Cluster Resources

  4. Configure Failovers

Before You Begin

System Requirements

Verify that the computer in which you wish to install the software satisfies the minimum requirements specified in System Requirements.

Network TCP Port Requirements

Review the Network TCP Port requirements specified in Network TCP Port Requirements.

License Requirements

Review the license requirements specified in License Requirements.

Download Software Packages

Download the latest SnapProtect® software using the Download Manager application. The Download Manager bundles an installation package from the SnapProtect components that you chose to download. Use the installation package to launch the software installer on a client computer.

See Download Manager - Getting Started for instructions on creating an installation package.

Several additional options are available for remotely installing the software from CommCell Console, refer to Install Software from the CommCell Console (Remote Install) for more information.

Network Protocol Requirement

If the option to install SQL Server is disabled, verify that there is at least one network protocol enabled. For SQL Server 2005, go to SQL Server Configuration Manager and enable protocols for each instance.

SQL Server Management Objects

Microsoft SQL Server Management Objects (SMO) is required on the client machine. By default, SMO is automatically installed with SQL Server 2005 or later versions.

Install the Software on Physical Nodes

If you do not wish to protect physical nodes with a specific agent, you can install that agent in 'restore only' mode, doing so will prevent the consumption of additional license per node. See Installing Restore Only Agents for more information. Alternatively, you can release license from the CommCell Console for a specific agent after installing it on the physical nodes. Refer to Releasing a License section to see the procedure for releasing a license.

The software can be installed on the Physical nodes using one of the following methods:

Method 1 : Remote Installation Using CommCell Console

Use this procedure to install remotely on the physical nodes.

Method 2 : Interactive Installation

Use this procedure to Install the software on the physical nodes from the active node of a cluster group.

Method 1: Remote Installation Using CommCell Console

  1. Open CommCell Console:

    • Click Start and point to All Programs.
    • Click NetApp .
    • Click SnapProtect  Administrative Console.
  2. From the CommCell Browser, click Tools | Add/Remove Software | Install Software.

  3. Click Next.

  4. Click Next.

  5. Click Manually Select Computers.

    Click Next.

  6. Enter the fully qualified domain name of each of the physical computers (nodes) on which you want to install the software.

    Fully qualified domain name of each physical computer must be specified in a separate line.

    For example, if your cluster group is hosted on two nodes (physicalcomputer1 and physicalcomputer2), then specify as following:

    physicalcomputer1.mydomain.mycompany.com

    physicalcomputer2.mydomain.mycompany.com

    Click Next.

    • Make sure that the physical computers (active node and passive node) that you specify here are reachable from the CommServe computer.
    • Do not use space and the following characters when specifying the Host Name:

      \|`~!_@#$%^&*()+=<>/?,[]{}:;'"

  7. Choose one of  the following:

    • Click Next if you want to use the default cache location
    • Click Override Software Cache and specify a new location in the Software Cache box and then click Next

    • The software cache is the location from where the remote install program installs the software.
    • This screen will not appear if the remote cache is not configured. For more information, see Managing Cache - Remote Cache.

  8. Specify the User Name and Password of the Domain Administrator account to perform remote installs on the physical computers that you selected in step 6.

    Click Next.

    • The Domain Administrator account must have Administrator rights on all the physical computers that you selected in step 6.
    • Account information is required while performing remote installs for the first time on the physical computers. For subsequent remote installs on those physical computers, click Next without specifying the account information.

  9. Click MSSQL Server under Databases.

    Click Next.

  10. Select the following:

    • Select a client group from the available Client Groups, and then click Add.
    • From the Global Filters list, select one of the following:
      • Use Cell level Policy to inherit the global filter policy configuration set for the CommCell.
      • Always use Global Filters to apply the global filters policy to the default subclient regardless of the policy set for the CommCell.
      • Do not use Global Filters if you plan to define specific filters for the Agent.
    • From the Storage Policy To Use list, select a storage policy.
    • Click Next.

    This screen will not be displayed if Client Groups are not configured in the CommCell Console. For more information, see Client Computer Groups.

    If you do not have a Storage Policy, the list will not be displayed. You can create a Storage Policy later using the steps described in the Configuring storage Policy section.

  11. Click Next.

  12. Click Next.

    If necessary you can select additional options. Click the Help button to get more information on the available options.

  13. Click Next.

    If necessary you can select optional settings. Click the Help button to get more information on the available options.

  14. Select one of the following:

    • If firewall configuration is not required, click Next.
    • If this computer and the CommServe is separated by a firewall, click Configure firewall services.

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

  15. Select Immediate.

    Click Next.

  16. Click Finish.

    This screen will reflect the components you selected for install, and may look different from the example shown.

  17. You can track the progress of the job from the Job Controller window of the CommCell console.
    • From the Home menu, click Job Controller.

    • Once the job is complete, view the job details from the Admin Job History.

      • Right-click the <CommServe>, point to View and then click Admin Job History.
      • Click Select Install/Upgrade/Remove/Repair Software.
      • Click OK.

    • You can view the following by right-clicking the job:
      • Details of the job
      • Option to Resubmit the job
      • Events associated with the job
      • Logs associated with the job
      • Option to send the Logs associated with the job

After installing the software successfully on all the physical computers that host the cluster group, you must configure the Cluster Group Client from the CommCell Console. Use the steps described in the Configure the Cluster Group Client  section for configuring the Cluster Group Client.

Method 2: Interactive Installation

  1. From the active node of the cluster group, log on to the physical computer as an Administrator or as a member of the Administrator group on that computer.
  2. Run SetupAll.exe from the installation package that was created using the Download Manager.
  3. Click I accept the terms in the license agreement.

    Click Next.

  4. Click Custom.

    Click Next.

  5. Click Select components to install on this computer and click Next.

  6. Expand Database, and then click MSSQL Server.

    Click Next.

  7. Verify the default location for software installation.

    Click Next.

    If necessary, click Browse... to change the default location.

    • Do not install the software to a mapped network drive
    • Do not use the following characters when specifying the destination path: / : * ? " < > | #
    • It is recommended that you use alphanumeric characters only

  8. Click Install.

    The Summary on your screen should reflect the components you selected for install, and may look different from the example shown.

  9. Click Yes.

  10. Click Next.

  11. Select one of the following:

    • If firewall configuration is not required, click Next.
    • If this computer and the CommServe is separated by a firewall, click Configure firewall services.

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

  12. Enter the fully qualified domain name of the CommServe in the CommServe Host Name box.
    • Do not use space and the following characters when specifying the CommServe Host Name:

      \|`~!@#$%^&*()+=<>/?,[]{}:;'"

    Click Next.

  13. Enter the following:
    • The local (NetBIOS) name of the client computer is displayed in the Select a Client name list.

      If necessary you can also type a new (friendly) name for the client in this box. This name will be used in the CommCell and will also be displayed in the CommCell Console.

      Do not use spaces when specifying a new name for the client.

    • The default network interface name of the client computer is displayed if the computer has only one network interface (NIC card).

      If the computer has multiple network interfaces, select the interface name that is preferred for communication with the CommServe.

    Click Next.

    If a component is already installed on this computer, this screen will not be displayed; instead, the install program will use the same name as previously specified.

  14. The default port numbers used for CommCell communication is displayed. If necessary, you can modify the port numbers.

    Click Next.

    This screen will not appear if the default port numbers are not used for CommCell communication.

  15. Select one of the following options:

    • If you do not want to disable Windows Firewall, click Next.
    • If you want to disable Windows Firewall for all profiles, click Yes, disable Windows Firewall for all profiles and then click Next.

    You will get this screen if you do not configure the firewall settings in step 10.

  16. Select Add programs to the Windows Firewall Exclusion List, to add CommCell programs and services to the Windows Firewall Exclusion List.

    Click Next.

    This option enables CommCell operations across Windows firewall by adding CommCell programs and services to Windows firewall exclusion list.

    It is recommended to select this option even if Windows firewall is disabled. This will allow the CommCell programs and services to function if the Windows firewall is enabled at a later time.

  17. Select one of the following:
    • Click Use Cell level Policy to inherit the global filter policy configuration set for the CommCell.
    • Click Always use Global Filters to apply the global filters policy to the default subclient regardless of the policy set for the CommCell.
    • Select Do not use Global Filters if you plan to define specific filters for the Agent.

    Click Next.

  18. Select a Client Group.
    Click Next.

    This screen will not be displayed if Client Groups are not configured in the CommCell Console. For more information, see Client Computer Groups.

  19. Select a storage policy from the Storage Policy list.

    Click Next.

    If you do not have a Storage Policy, the list will not be displayed. You can create a Storage Policy later using the steps described in the Configuring Storage Policy section.

  20. Click Next.

  21. Click Finish.

    This screen will reflect the components you selected for install, and may look different from the example shown.

  22. Click Yes.

    When you click Yes, the software automatically retrieves the list of nodes to which the current active node can failover.

  23. Select cluster nodes from the Preferred Nodes list and click the arrow button to move them to the Selected Nodes list.

    Once you complete your selections, click Next.

    The list of Preferred Nodes displays all the nodes found in the cluster; from this list, you are required to select the cluster nodes configured to host this cluster group server.

  24. Specify User Name and Password of the Domain Administrator account to perform the remote install on the cluster nodes you selected in the previous step.

    Click Next.

    The Domain Administrator user account that you specify here must have Administrator rights on all the cluster nodes that you selected in the previous step.

    The Installer tries to install the software on all the nodes (physical computers) that you selected in step 23.

    The progress of the remote install for the cluster nodes is displayed on the Remote Install Progress screen.

  25. Click Finish.

    If the software is not installed successfully on any of the passive nodes selected in step 23, or if any passive node is not available during the installation, a separate installation from the CommCell Console needs to be performed on that node in order to prepare it for a failover protection.

    For remote install instructions, see Remote Install.

  26. Click Finish.

After installing the software successfully on all the physical computers that host the Cluster Group, you must configure the Cluster Group Client from the CommCell Console. Use the steps described in the Configure the Cluster Group Client section fro configuring the Cluster Group Client.

Configure the Cluster Group Client

  1. From the CommCell Browser, right-click the Client Computers node, point to New Client | Clustered Server and then click Windows Cluster.

  2. In the Client Name box, type a name for the cluster group. The Client name can be any unique name.

    In the Host Name box, type the fully qualified domain name of the SQL cluster instance.

    The Host name of the cluster group client should not be used by any existing client in your CommCell.

  3. Review the cluster group information and click Finish.

    Advanced Client Properties window is displayed now.

  4. On the Advanced Client Properties dialog box, click the Cluster Group Configuration tab. All the Windows clients that are available in the CommCell will be listed in the Available list. Select the physical computers (nodes) where you installed the necessary Agents from the Available list, and then click Add > to move the client to the Selected list.

    If the client computer properties dialog box is not displayed automatically, then you need to open it manually: Right-click the  <Cluster Group Client>, and then click Properties. Click Advanced on the Client Computer Properties dialog box. Click the Cluster Group Configuration tab on the Advanced Client Properties dialog box.

  5. Click the Agents tab.

    Select the Agents you want to use in the cluster group client from the Available list and click Add > to move the Agent to the Selected list.

    In order to configure a Cluster Group Client, the agents should be installed on all the clustered nodes for proper failover. If an Agent is not installed on all the nodes, then the Agents selection tab on the Advanced Client Properties window will display the Agent name in plain text (not in bold). However, you can still configure the Cluster Group Client even when the Agents are not installed on a particular node; installation can be done later using Remote install procedure.

  6. Click the Job Configuration tab.

    Type or click Browse to specify the path for the Job Results Directory in the cluster group client.

    • Ensure that the Job Results Directory resides on a shared clustered drive.
    • In the case of MediaAgent and ContinuousDataReplicator, the Job Result directory path will be used for the Index Cache and CDR Log directories respectively if no directory location is provided.

    Click OK.

Configure Cluster Resources

After installing the software component (s) on the physical nodes and the cluster group client is configured, you must configure the Cluster resources.

Configure VERITAS Cluster Resources.

Configure HP Scalable NAS or PolyServe Cluster Resources.

Configure VERITAS Cluster Resources

Use the following steps to configure Veritas Cluster resources:

  1. Create the Cluster Resources for Services

    After configuring the Cluster group client, the services should be added as generic services. However, you must designate the <Cluster Plug-in  (Cluster Group) (Instance)> service as "critical" if you want to cause the cluster group to failover if the associated service stops.

    • Click the Windows Start button, click Run, type services.msc and press Enter. Services window will be displayed\
    • Locate the services for each installed cluster group. For example,  NetApp Cluster Plugin (penodevn1_netwo) (instance001))
    •  Right-click this service, 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.
      • If you have created multiple cluster groups, you can designate each of the associated services as critical.

    • 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.

      If you have created multiple cluster groups, you can designate each of the services associated with the corresponding cluster group as "critical".

    • Repeat this procedure on each physical computer hosting the cluster.
  2. Create Service Dependencies.
    • In the Cluster Administrator, click Resources.
    • Click Link and make the Cluster plugin resource dependent upon the Mount resource and the Lanman service.
  3. Associate Services with the Current Active Node.
    • 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.

Configuring HP Scalable NAS or PolyServe Cluster Resources

Use the following steps to configure HP Scalable NAS/PolyServe Cluster resources:

  1. Create and Use Scripts to Administer Virtual Machine Services.
  2. Add the Customer Service Monitor.

Create and Use Scripts to Administer Virtual Machine Services

You should create and use three scripts to administer virtual machine services:

  • Probe script is used to reveal the state of the specified services - This is done by 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 NetApp Communications Service (GxCVD) and the NetApp 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

'1' if services are stopped

'-1' is returned for an error condition.

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)

These examples provide sample script names, locations and virtual host name as suggested names not requirements.

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 Customer Service Monitor

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

  • Ensure that the virtual host name <virtualpolyserve> is online.
  • From the Services MMC snap-in, verify or manually start the cluster plugin service, "NetApp Cluster Plugin (virtualpolyserve) (Instance00x)", on the active primary node for the Vhost virtualpolyserve
  • From the PolyServe Matrix Server, click the Virtual Hosts tab.
  • Right click Virtual Host <virtualpolyserve> and then Add Service Monitor.
  • For the Monitor Type field in the Add Service Monitor dialog box, click CUSTOM.
  • Assign a name to the service monitor by typing the name in the Name field.
  • In the User probe script field, type the path to the probe script that calls the GxSCMCmd.exe command (on the share disk)
  • Click Advanced.
  • From the Advanced Service Configuration dialog box, click the Scripts tab.
  • 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.
  • 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.
  • Click OK..

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.

Configure Failovers

Skip this step if you do not want to configure failovers for the agent software failures, and continue to the next page.

By default, a failure of any Agent software (e.g., Windows FileSystem ) on the active node will not cause a failover to be initiated. To configure a cluster server to failover when the Agent software fails, you are required to perform the following steps on each of the physical computers configured to host the cluster group:

  1. Add the list of Services that GxClusPlugin must monitor for failures :

    Configure the sServiceMonitorList additional setting with a list of services that GxClusPlugin will monitor for failure. For information about the services used by an Agent or MediaAgent, which can be listed in this additional setting, see Services.

    • From the CommCell Browser, navigate to Client Computers | <Cluster Group Client>. Right-click the <Cluster Group Client> and then select Properties.
    • On the Client Computer Properties dialog box, click Advanced.
    • On the Advanced Client Properties dialog box, click the Additional Settings tab, and then click Add.
    • In the Name box, type sServiceMonitorList.Once entered, the Category and Type details will be automatically populated. Alternatively, you can click Lookup and search for the additional setting by typing the additional setting name in the Find box or scrolling through the list. Once found, double-click the additional setting from the lookup window.
    • In the Value box, type the services that need to be monitored by the cluster plug-in.

      Example:  GxCVD(Instance001);GxEvMgrC(Instance001)

    • Click OK.Click OK.

  2. Configure the Monitoring Frequency :

    Configure the sServiceMonitorFrequency additional setting for the frequency (in seconds) at which those services should be polled for failure. This value should be less than the service restart interval being monitored, if any.

    • From the CommCell Browser, navigate to Client Computers | <Cluster Group Client>.Right-click the <Cluster Group Client> and select Properties.
    • On the Client Computer Properties dialog box, click Advanced.
    • On the Advanced Client Properties dialog box, click the Additional Settings tab, and then click Add.
    • In the Name box, type sServiceMonitorFrequency. Once entered, the Category and Type details will be automatically populated. Alternatively, you can click Lookup and search for the additional setting by typing the additional setting name in the Find box or scrolling through the list. Once found, double-click the additional setting from the lookup window.
    • In the Value box, type the time interval in seconds. This time interval will be the frequency at which the services will be pooled for status on the active node of a cluster.

      Default Value: 30

    • Click OK.Click OK.
  3. Configure GxClusPlugin Properties :

    Configure the properties of GxClusPlugin so that a failover will be triggered by a failure of any of the services listed in the sServiceMonitorList additional setting.

    For Windows 2008 Server:

    • From the Failover Cluster Manager console, right-click GxClusPlugin listed under Cluster Core Resources | Other Resources, and then select Properties.
    • Click the Policies tab and select the If restart is unsuccessful, fail over all resources in this service or application check box.
    • Click OK.

    For Windows 2003 Server:

    • From the Cluster Administrator, right-click GxClusPlugin listed under Other Resources, and then select Properties.
    • Click the Advanced tab and select Restart and Affect the Group, and click OK.

Configuring Storage Policy

If you do not have a Storage Policy created, use the following steps to create a storage policy:

To create a storage policy, you must have configured a library in the CommCell.

Disk Library Creation

  1. From the CommCell Browser, navigate to Storage Resources, right-click the Libraries, point to Add and then click Disk Library...

    Alternatively, you can also navigate to MediaAgents, right-click <MediaAgent>, point to All Tasks | Create Library and then click Disk Library...

  2. From the Add Disk Library dialog box, specify the following:
    • In the Name box, specify name of the disk library.
    • From the MediaAgent list, select the MediaAgent.

    Perform one of the following:

    • Select Local Path if you wish to specify a local path in the MediaAgent computer.

      In the Disk Device box, type the name of the folder in which the disk library must located or click button to select the folder.

    • Select Network Path, if you wish to specify a network path as the target share.

      In the Connect As box, type the user name.

      In the Password and Verify Password box, type the password to access the network share.

      In the Folder box, type the mount path or click button to select a mount path.

    • Click OK.
  3. The newly created disk library will be displayed under Libraries node.

This will create a library and Storage Policy. Proceed to the next page.

Storage Policy Creation

  1. From the CommCell Browser, navigate to Policies.
  2. Right-click the Storage Policies and then click New Storage Policy.
  3. Follow the prompts displayed in the Storage Policy Wizard. The required options are mentioned below:
    • Select the Storage Policy type as Data Protection and Archiving and click Next.
    • Enter the name in the Storage Policy Name box and click Next.
    • From the Library list, click the name of a disk library to which the primary copy should be associated and then click Next.

      Ensure that you select a library attached to a MediaAgent operating in the current release.

    • From the MediaAgent list, click the name of a MediaAgent that will be used to create the primary copy and then click Next.
    • For the device streams and the retention criteria information, click Next to accept default values.
    • Review the details and click Finish to create the Storage Policy.

This will create a storage policy. Proceed to the next page.

Additional Installation Methods

Remote Install

Deploy the software from CommCell Console on multiple clients.