Known Issues for Backup Agents in 11.20

Archiving SQL Server Database Tables

Note the following caveats when you archive SQL Server database tables:

  • Database names containing characters {, }, and ; are not supported for archiving.

  • Table names containing characters [, ], and . are not supported for archiving.

  • Read-only databases are not supported for archiving.

  • You can archive only one target table for each subclient.

Backups May Fail on SQL Server 2017 Linux Clients with Cumulative Update 19 or Later

A Microsoft issue has caused backup jobs to fail on SQL Server 2017 Linux clients after installing the Cumulative Update 19 or later.

As a workaround, downgrade the SQL Server application to Cumulative Update 18 on the Linux client.

Client Computer Name Is Not Displayed for NAS and Network Share Client Computers

If a client computer does not consume a Server File System license, then the client computer name is not displayed in the Backup Nodes tab or in the Proxy Client list of the Subclient Properties dialog box.

Deduplication Database (DDB) Backups May Complete with One or More Errors After Upgrading to Feature Release 20

Deduplication Database (DDB) backups may complete with one or more errors after upgrading to Feature Release 20.

As a workaround, install Maintenance Release 11.20.3 or higher. Download the release from the Commvault Store.

File-Level Live Browse Operations of Solaris ZFS Mount Point Block-Level Backups

On Solaris MediaAgents, file-level live browse operations of ZFS mount point block-level backups might leave behind uncleaned zpools (that were created by the live browse operation) in certain cases. The uncleaned zpools cannot be removed by using the export or delete commands. This issue will be addressed in a future feature release.

As a workaround, Commvault recommends using non-production clients for file-level browse operations of ZFS mount point block-level backups.

GlusterFind API for GlusterFS

The following GlusterFind known issues might result in inconsistent backup operations in certain cases.

  • "Glusterfind : wrong results while retrieving incremental list of files modified after last run"

    For more information, see, bug #1535526.

  • "Glusterfind : Move Operations performed in the Filesystem are not reported correctly"

    For more information, see, bug #1471963.

These issues will be automatically resolved when you synchronize the data on the GlusterFS volume and the backup index periodically. For more information, see Synchronizing Data on the Disk and the Index.

Network Share Backups May Fail with "Access Denied" Error

Network share backups may fail during the scan phase with an "Access Denied" error.

To resolve this issue, download and install Commvault hotfix 2417 on all access nodes used for network share clients in the CommCell environment.

Office 365 with Exchange Support Ended for the Exchange Mailbox (Classic) Agent

On October 31, 2017, Microsoft ended support for RPC over HTTP for Office 365. For more information, see the Microsoft support article: "RPC over HTTP reaches end of support in Office 365 on October 31, 2017",

After December 15, 2018, Commvault will not support backup nor archiving operations using Office 365 (Exchange Online) for the Exchange Mailbox (Classic) Agent or OnePass for Exchange Mailbox (Classic).

If you use Exchange Mailbox (Classic) Agent, we recommend that you transition to the Exchange Mailbox Agent. The Exchange Mailbox Agent uses EWS for backup and archiving instead of MAPI.

For more information, see Transitioning to the Exchange Mailbox Agent.

Oracle Live Sync Replication with Disk Caching of Oracle Archive Log Backups

Don't enable disk caching of archive log backups for Oracle source instances that have Live Sync configured, because Live Sync will be disabled as a result. If disk caching is enabled at the plan level or in a schedule policy, you must use a different plan, that doesn’t have disk caching enabled, for the source Oracle instance. Support for Oracle Live Sync with instances that have disk caching of log backups enabled will be added in a later release.

Oracle Live Sync Replication with Redirect Paths

When you configure Oracle Live Sync Replication with a redirect path, if a new datafile is added to the source database, the subsequent live sync replication operation might fail. For example, the source datafiles are located in /u01/app/oracle/oradata/database_file.dbf path, and the live sync replication is configured to redirect the datafiles to /home/oracle/datafiles/database_file.dbf path. When you add a new datafile datafile1.dbf to the source database, the next live sync replication operation fails.

This issue will be fixed in a future feature release. As a workaround, to allow replication operations to complete successfully, create the same path as the source datafile on the destination database.

Upgrading to SP8 or later for SAP Archive Link clients is now supported. To upgrade, contact Commvault Support for upgrade assistance.

SQL Server 2012, 2014, 2016 and 2017 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. For more information, refer to Microsoft Support article FIX: Intermittent 9004 error when a backup is restored via Standby Mode in SQL Server 2014, 2016, and 2017. As a workaround, perform restores of database and transaction logs using the NORECOVERY option.