Frequently Asked Questions - CommCell Management

Table of Contents

How do we identify the third-party application files installed with the CommServe?

The following third-party application files are installed along with the CommServe.

























































These files are not signed and will not have complete file version information in the file's Properties dialog box.

For example:

<software install path>\Base\AutoMapper.dll does not have a valid Company name and Product Name properties.

However, note that having incomplete file version information on these files does not affect the performance of the software.

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

Yes. During the installation of the SnapProtect software, you can configure the Administrator account to have no password. This configuration will skip the password check to access the CommCell Console, which disables the login window that prompts for credentials.

Having this account without a password is useful when the Administrator is the only user configured in the CommCell 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 with multiple users, it is recommended that the Administrator account is configured with a password for security reasons. To change the password of your Administrator account, see Changing the User Information.

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 following Microsoft article Collecting User-Mode Dumps for more information.

You can set up a Process Crash Dump using the registry editor.

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

    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 1

    Name: DumpFolder

    Type: Multi-String Value

    Data: <path to the crash dump folder> (for example, C:\CrashDumps)

    Registry 2

    Name: DumpCount

    Type: DWORD (32-bit) Value

    Data: <number of .DMP files kept in the crash dump folder before overwrite; value is in decimal>

    Registry 3

    Name: DumpType

    Type: DWORD (32-bit) Value

    Data: 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 Enterprise 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, click the Home tab and then click Control Panel.
  2. Under the System section, 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.

Additionally, the ScrubLogFiles utility in the Resource Pack can be used for log scrubbing. For more information, see Customizing Log File Contents.