Loading...

Release Notes - Known Issues in Service Pack 4

Whether you are installing this software for the first time, or upgrading from a previous version, please note these important considerations.

The following issues are in addition to the Known Issues in Version 11.

Expand All

Deployment

32-bit Installations on 64-bit Windows Computers Fail When Performed From the CommCell Console

When you run an installation job from the CommCell Console to install 32-bit agents on 64-bit Windows computers, the installation job fails.

While this issue is being resolved, you can use the Alternative Method described in Enabling 32-Bit Installations on 64-Bit Windows Computers.

Mongo DB fails to Install on Windows Server 2008 (or Earlier Versions)

During the installation of the CommServe software on Windows Server 2008 computers (or earlier versions), the Mongo DB installation fails with the following error:

mongod.exe - Entry Point Not Found: The procedure entry point TryAcquireSRWLockExclusive could not be located in the dynamic link library KERNEL32.dll.

Mongo DB is not supported on computers running Windows Server 2008 or earlier versions. Without the Mongo DB, you cannot add comments and replies on files and folders from the Web Console.

There is no action required for this issue. You can ignore the error message and continue with the CommServe installation.

Remote Installations of Updates Are Not Supported for Stand-Alone CommCell Console Clients

The CommCell Console does not support the installation of updates and service packs on client computers that only have the CommCell Console software installed. To update these CommCell Console clients, you must install the updates locally on the clients by using the installation package or the Download Manager.

This issue will be addressed in a future service pack.

Upgrade to V11 Removes Subclient Content

After upgrading a Virtual Server Agent from Version 10 to Version 11, the list of virtual machines in the subclient Content tab are replaced in V11 with the list that had been configured in V9. As a result, virtual machines might not be backed up.

This issue can occur when a VSA client was earlier upgraded from V9 to V10, and now has been upgraded to V11. This issue affects VSA clients for VMware and Microsoft Hyper-V.

To address this issue for clients that have not yet been upgraded, immediately download SP4-HotFix 180 and install it on the CommServe system.

For clients that have already been upgraded, you must add the content back to subclients to match the V10 configuration.

For more information about installing HotFixes, see Installing a Hotfix.

Backup Agents

1-Touch Recovery for Linux Systems with GPT Boot Disk and BIOS

For Linux systems with GPT boot disk that are booted in BIOS mode (not UEFI), in-place interactive and non-interactive 1-Touch recovery is supported. Out-of-place 1-Touch recovery and Virtualize Me might fail.

SnapProtect Plug-in Does Not Support Backup and Restore of SQL Availability Databases

You cannot back up or restore SQL databases protected by an Availability Group client using the SnapProtect Plug-in for SQL Management Studio.

File System Agent on the CommServe Computer is Deconfigured After Upgrade

After the CommServe upgrade, the File System Agent on the CommServe computer goes into a deconfigured state.

To continue running backup operations using the File System Agent, you must perform the following operations on the agent:

  1. Release the license.

    From the CommCell Browser, expand Client Computers > CommServe_computer, right-click File System, click All Tasks > Release License, and then follow the prompts.

  2. Reconfigure the client.

    From the CommCell Browser, expand Client Computers > CommServe_computer, right-click File System, click All Tasks > Reconfigure, and then follow the prompts.

SAP HANA Pseudo-Clients are Not Upgraded in a Multi-Node Environment

In a SAP multi-node environment, when you upgrade a SAP HANA client from Version 10 to Version 11 Service Pack 4, the SAP HANA pseudo client is not upgraded to o Version 11 Service Pack 4.

To resolve this issue, make sure that you have installed Hot Fix 192 on the CommServe before you begin the upgrade.

SQL Server 2012 and 2014 Log Restores to a Database in a Stand-By State May Fail

SQL Server log restores to a database in the stand-by state are affected by a Microsoft issue. Refer to Microsoft Support article Restore Log with Standby Mode on an Advanced Format disk may cause a 9004 error in SQL Server 2008 R2 or SQL Server 2012. As a workaround, perform restores of database and transaction logs using the NORECOVERY option.

SAP HANA Pseudo-Clients are Not Upgraded in a Multi-Node Environment

In a SAP multi-node environment, when you upgrade a SAP HANA client from Version 10 to Version 11 Service Pack 4, the SAP HANA pseudo client is not upgraded to o Version 11 Service Pack 4.

To resolve this issue, make sure that you have installed Hot Fix 192 on the CommServe before you begin the upgrade.

Snapshot Management

Inconsistent Volume Backup Occurs Because of Manually Deleted IntelliSnap and Backup Copy Jobs

Applies to: UNIX File System, Windows File System, Oracle, MySQL, and PostGreSQL with block-level backup enabled

If block-level backups are enabled and unmaterialized IntelliSnap or backup copy jobs are manually deleted, the subsequent backup copy job does not include the changes that happened during the deleted IntelliSnap or backup copy job. This could result in inconsistent volume backups. You might not be able to recover the file system or database from the backed-up data.

To resolve this issue, if an unmaterialized IntelliSnap or backup copy is manually deleted, run an immediate full, block-level backup job.

Edge Endpoint Solutions

Data To Process Value Mismatch for Edge Backups During Auxiliary Copy Jobs

If Edge backup data is being processed during the auxiliary copy operation, the values in the Total Data Processed field in the Auxiliary Copy Job Details dialog box might exceed the Total Data to Process field and the auxiliary copy job may keep running at 100%. This issue will be addressed in a future service pack.