Use the following steps if you are upgrading SQL Compliance Manager 4.0 or older in a clustered environment. The steps support upgrading in either a windows Server 2003 or Windows Server 2008 clustered environment.

Be sure to back up your Repository and all databases and archives before upgrading SQL CM.

Install the SQL CM Collection Service on Cluster Nodes

You must upgrade the SQL Compliance Manager Collection Service on each cluster node for the service to work correctly when a failure occurs on the primary cluster node hosting the Collection Service.

Before upgrading, changing, or uninstalling SQL CM on the passive node, you must delete the following registry entry: HKEY_LOCAL_MACHINE\Software\Idera\SQLcompliance\CollectionService\TraceDirectory. This step in unnecessary for new installations.

 

To install the SQL Compliance Manager Collection Service on cluster nodes:

  1. In the Microsoft Cluster Administrator tool (Windows Server 2003) or Microsoft Failover Cluster Management Console (Windows Server 2008), select the SQLComplianceCollectionService resource and take the service offline.
  2. Log on with an administrator account to the computer on which you want to upgrade SQL CM.
  3. Run Setup.exe in the root of the SQL CM installation kit on the first cluster node.
  4. Under Install, click SQL Compliance Manager.
  5. Read the Welcome window, and then click Next.
  6. Review and accept the license agreement by clicking I accept the terms in the license agreement, and then click Next.
  7. Verify that the installation folder is the same location where you initially installed SQL CM, and then click Next.
  8. Select the Clustered Collection Server setup type, and then click Next.
  9. Check the Install the Collection Server in a Windows Cluster check box.
  10. Select whether you are upgrading the Collection Service on the Currently Active Node or A Passive Node, and then click Next.
  11. If you upgrade the currently active node, verify that the SQL CM Collection Service trace directory is the same location where you current directory resides, and then click Next. If you install on a passive node, continue with the next step.
  12. Type the service account information, and then click Next.
  13. Verify that the Repository path is the same SQL Server instance name hosting the Repository.
  14. Select the authentication method used to upgrade the Repository database and include credentials, if required, and then click Next.
  15. In the Repository Warning dialog box, click Preserve to retain your current Repository. If you click Delete, the upgrade tool DELETES all of your current Repository databases.
  16. Click Install.
  17. In Windows Services, stop the SQL CM Collection Service and set the Startup type to Manual.
  18. Repeat the previous steps on each cluster node. Point to the SQL CM Repository installed on the first node.
  19. In the Microsoft Cluster Administrator tool (Windows Server 2003) or Microsoft Failover Cluster Management Console (Windows Server 2008), select the SQLComplianceCollectionService resource and bring the service online.

 

SQL Compliance Manager audits all activity on your server. Learn more > >
Idera WebsiteProductsPurchaseSupportResourcesCommunityAbout UsLegal 
  • No labels