Install the CommServe and Database Engine on Separate Computers


Click on a link below to go to a specific section of the software installation:

Overview

The CommServe and the Microsoft SQL Server Database Engine can be installed on separate computers.

The following procedure describes the steps involved in building such a topology. Note that these procedures require familiarity and understanding of both the Microsoft SQL Server Database Engine and the Windows operating system.

This procedure can be used when you initially install the software, or when you split an existing CommServe.

The following are not supported in this configuration:

Install Requirements

Review the following requirements before setting up the CommServe and the Microsoft SQL Server Database Engine on separate computers:
  • Two computers that can host the CommServe and the database engine.
  • A reliable and fast network connection between these two computers.
  • The CreateCSSQLAccount utility, which is available in the Resource Pack. (See Tools and Utilities for more information.)

Install Procedure

Installing the Necessary Software

1. If you are installing a new CommServe, install the CommServe software on the computer that will host the CommServe. (Referred to as the CommServe computer in the subsequent steps.)

This step is not necessary if you already have a CommServe running on this computer.

See Install the CommServe for step-by-step instructions.
2. Install Microsoft SQL Server with the appropriate Service Pack on the computer that will host the Database Engine. (Referred to as the SQL Server computer in the subsequent steps.)

See System Requirements - CommServe for more information on the SQL Server version.

See Pre-Installing SQL Database for CommServe for step-by-step instructions.

Moving the Database

3. Verify that no jobs are in progress or scheduled to occur while setting up this configuration. If jobs are in progress or other tasks (such as reports or updates) are scheduled, either perform this task at another time or disable all activity or disable all scheduled tasks from the CommCell Console. For step-by-step instructions, see Enable or Disable Operations.
4. Stop all services on the CommServe computer. See Stop Services on Windows for step-by-step instructions.
5. In the CommServe computer, using the SQL Server Management Studio, backup the CommServ database and create a .dmp file. See the SQL Server Management Studio help for information on backing up a database.

Alternatively you can use the following command line in a batch file:

<sql install path>\osql -S <SQL ServerName> -U sa -P <sapwd> -Q "BACKUP DATABASE [CommServ] TO DISK = 'C:\cs.dmp'"

This should create a dump file c:\cs.dmp.

You can choose the folder in which the .dmp file is created.

6. Perform this step if you wish to free-up the memory associated with SQL Services.

Remove the dependencies from SQL Services and then stop and disable SQL Services for HDPS instance on the CommServe computer.

Reboot the computer.

To remove the dependencies:
  1. Start Regedit.exe
  2. Navigate to the following key:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\GxCVD(Instance001)

  3. Remove MSSQL$HDPS entry from the DependOnService multi string value.

 

To stop and disable the services:

  1. Open the Services window from Administrative Tools in Windows Control Panel.
  2. Right click the SQL Server(HDPS)service and then click Properties.
  3. Select the Disabled option from the Startup Type list.
  4. Click the Stop button.
7. In the SQL Server computer, using the SQL Server Management Studio, restore the CommServ database.

See the SQL Server Management Studio help for information on restoring a database.

8. In the CommServe computer, open the Registry Editor and  navigate to the following key:

HKEY_LOCAL_MACHINE\SOFTWARE\CommVault Systems\Galaxy\Instance<xxx>\Database

Edit the following values:

sCONNECTION set it to <SQL Server computer>_commserv

sDOMAIN set it to <SQL Server computer>

sINSTANCE set it to <SQL Server computer>\HDPS

See Windows help for information on opening and editing registry keys.

Setting up the SQL Server Account

9. From the Resource Pack copy the CreateCSSQLAccount utility to the CommServe computer. The utility is available in the following location in the Resource Pack:

Windows\CreateCSSQLAccount\CreateCSSQLAccount.htm

The utility must be copied to the following location in the CommServe computer:

<software_install_folder>\base 

10. In the CommServe computer, run the CreateCSSQLAccount utility and create the SQL Server System Administrator account and password that will be used to access the SQL database. For information on how to run this utility, see Readme_CreateCSSQLAccount.txt available in the following location in the Resource Pack:

Windows\CreateCSSQLAccount

Changing DSN Settings

11. In the CommServe computer, modify the DSN Settings for the CommServe database to point to the database in the SQL Server computer.
  1. Open Control Panel | Administrative Tools | Data Sources (ODBC).
  2. Click the System DSN tab.
  3. Click <CommServe computer>_commserv and then click Configure.
  4. Edit the following values:

    Name -  set it to <SQL Server computer>_commserv

    Server - set it to <SQL Server computer>\HDPS

  5. Click Next.
  6. Choose the With SQL Server authentication using a login ID and password entered by the user option.
  7. Select the Connect to SQL Server to obtain default settings for the additional configuration options check box and enter the login and password that you created using the CreateCSSQLAccount utility.
  8. Click Next twice and then click Finish. (Nothing needs to be changed on these dialog boxes.)
  9. Click Test Data Source.

    The result should be TEST COMPLETED SUCCESSFULLY.

    If not make sure SQL server on the SQL Server computer is accessible and the login information given are correct.

12. Restart the services on the CommServe computer and re-enable jobs that were disabled. See Start Services on Windows for step-by-step instructions.

See  Enable or Disable Operations for step-by-step instructions.

Protecting the Database - Setting up the Disaster Recovery Backup

13. Disaster Recovery Backup will not work in this setup. Disable the Disaster Recovery Backup schedule. (Use the following steps instead.) See Disable a Schedule for more information.
14. Install the File System iDataAgent on the SQL Server computer. See Deployment - Windows File System iDataAgent for more information.
15. Using the File System iDataAgent, create a subclient which includes a script in the pre-scan phase to create a .dmp file of the CommServ database. Schedule regular backups of this subclient database from file system iDataAgent.

Recommended schedule is a daily full backup.

Use the following command line in a batch file and attach the batch file as a PreBackup Process:

<sql install path>\Isql.exe -S <SQL ServerName> -U sa -P <sapwd> -q "BACKUP DATABASE [CommServ] TO DISK = 'C:\cs.dmp'"

This should create a dump file c:\cs.dmp.

You can choose the folder in which the .dmp file is created.

16. If you want a copy of the dump in a magnetic library (similar to Disaster Recovery Backup) copy the dump file to another location. This can be included in the post-backup phase.

Restoring the Database

17. If you wish to recover the database, restore the dump file using the File System iDataAgent on the SQL Server computer and then recover the database using the SQL Server Management Studio.