V11 SP8
Loading...

Installing the SQL Server Agent on High Availability Standby CommServe Host

  1. Create a non-deduplicated Storage Policy using the MediaAgent installed in the standby CommServe location. For instructions, see Storage Policy - Getting Started.

    This Storage Policy must be used by the SQL Server Agent (see step 5 below) to backup and restore the CommServe database, to keep it synchronized between the production and standby CommServe host.

    Optional but Recommended: Use this Storage Policy exclusively for backing up and restoring the CommServe database using the SQL Server Agent

  2. Stop the CommCell Services on the standby CommServe host.
  3. Enable multi-instancing on both the production and standby CommServe hosts. For instructions, see Enabling Multi-Instance Installations.
  4. Install the SQL Server agent on the production and standby CommServe hosts, For instructions on installing the SQL Server Agent, see Preinstallation Checklist for the SQL Server Agent.
    • Install the SQL Server Agent using the interactive custom install method.
    • Make sure to install the SQL Server Agent on a second instance by choosing the Create a new instance option during the installation.
  5. Provide the following during the installation:
  6. After installing the agent:
    • Configure a local user account for the SQL Agent. For instructions, see Setting up Password at the Agent Level for the SQL Agent.

      Note: Make sure that the local user account overrides the user account settings configured at the CommCell and Client Computer Group levels

    • Using SQL Management Studio, ensure that the NT Authority\System account has sysadmin permissions enabled in the Server Roles. This role is required to successfully perform SQL backups and restores.

Firewall Configuration

If you have a firewall configured between the production and the standby CommServe hosts, configure a firewall route between the second instances of the CommServe hosts.