Frequently Asked Questions - CommCell Management

Table of Contents

Can I configure the CommCell Administrator account to have no password?

During the installation of the SnapProtect software, the CommCell Administrator account is automatically created and does not have a password. This configuration skips the password check to access the CommCell Console, which disables the login window that prompts for credentials.

Not having a password is useful when the Administrator is the only user configured in the CommCell environment as you can automatically log on to the CommCell Console. However, when more CommCell users are created, the CommCell Console will start asking again for user credentials to allow access.

In a CommCell environment with multiple users, add a password to the CommCell Administrator account for security reasons. To change the password of the CommCell Administrator account, see Editing a User.

Can I change the path of the CommServe database files?

Yes. You can easily change the drive or directory location of the CommServe database using the SQL Server Management Studio.

See Change the Location of the CommServe Database Files for more information.

Can I configure a new client with the same name and hostname of an existing client?

No. When you configure a new client in the CommCell, the client must not have the same name or hostname of any existing client in the CommCell. Although the CommCell Console does not prevent you from doing it, this configuration is not supported. For example, backup operations on the client will fail.

If a CommServe installed in a Microsoft Cluster Environment fails over, what happens to all backup operations?

After a CommServe in a Microsoft Cluster Environment undergoes a failover, restartable jobs are restarted, but non-restartable jobs fail to complete. There might be scenarios when the failover process is quick enough to beat the network timeout, allowing backup jobs that cannot be interrupted to continue.

We recommend that all "non-interruptible" backups are restarted after the failover.

How to create a Process Dump on Windows Server and Desktop computers?

Doctor Watson (Drwtsn32.exe), a troubleshooting utility in previous Windows versions, was removed with the introduction of Windows Vista and Windows Server 2008. Microsoft introduced a more reliable solution for un-handled exceptions. See the Microsoft article, Collecting User-Mode Dumps, for more information. You can set up a Process Crash Dump using the registry editor.

You can also create an on-demand dump file of a SnapProtect process from the SnapProtect Process Manager. For information, see Creating a Process Dump in the Process Manager.


  1. Open the Registry Editor on your Windows computer.
  2. Navigate to the registry key location HKLM\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps.

    Notes: You may need to create the following subkeys if they do not exist:

    • Windows Error Reporting
    • LocalDumps
  3. Under the LocalDumps subkey, create another subkey for the process name. For example, if you create a subkey for the process IFind.exe, then the complete registry location will be:

    HKLM\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps\IFind.exe

  4. Under the subkey for the process (using the example above, IFind.exe), create the following registry entries:
    Registry Name Type Data
    1 DumpFolder Multi-String Value Path to the crash dump folder

    For example: C:\CrashDumps

    2 DumpCount DWORD (32-bit) Value Number of .DMP files kept in the crash dump folder before overwrite; value is in decimal
    3 DumpType DWORD (32-bit) Value 2 (the 2 value means Full Dump)

How does SnapProtect handle the SQL Enterprise License during the CommServe installation?

Commvault Systems, Inc. has an ISV-R royalty contract with Microsoft, allowing the SnapProtect software to be bundled with a full copy of the SQL Server Standard Edition. Commvault Systems, Inc. reports the license usage (per country) every month to Microsoft.

Sending CommServe database and CommCell activity logs to Customer Support through Static IPs

When the security requirements in your environment demand the use of static IP address connections for third-party connections, SnapProtect provides the following IP addresses (of secured sites) to upload logs associated with CommCell activities:

  • For FTP

  • For HTTP

The IP addresses shown above are configured by default for the CommCell. You can view these settings from the CommCell Console:

  1. From the CommCell Console ribbon, on the Home tab, click Control Panel.
  2. Under Maintenance, click Troubleshooting Settings.
  3. Check the FTP Log Settings and HTTP Log Settings.

    The sites specified for FTP and HTTP represent the IP addresses listed above.

A Full Disaster Recovery backup must be run manually before sending the CommCell activity and the CommServe DB logs. If a disaster recovery is not performed, the collected SQL database log files will not be in sync with the current errors occurring in the CommCell.