Table of contents |
Related Topics |
|
Data Encryption and Deduplication |
Provides comprehensive information on Backward Compatibility support. |
When the CommServe is upgraded to the current version, the Commcell components can remain in the previous supported version. This Backward compatibility is provided in order to phase out the upgrade process in the CommCell.
The new features in the current release will not function for the CommCell components until they are upgraded to the same version as the CommServe. In addition, some existing features may not function as expected when the CommServe is upgraded. The following sections describes these issues.
See Backward Compatibility - Support for supported version and agents that are not backward compatible.
If the CommServe is current version and the Client is previous version, QSnap cannot be used as a snap engine for CDR on Unix. LVM will always be used as a snap engine.
If you upgrade the CommServe and MediaAgent, but not the Client, restores from a secondary copy containing encrypted backups enabled using a storage policy copy operation would not be supported until the Client is upgraded.
If the CommServe and MediaAgent are upgraded to the current release, for clients that are still at version 7.0, deduplication is not supported if data encryption is enabled. Data protection and data recovery jobs for version 7.0 clients may fail. However, for version 8.0 clients backing up to version 8.0 or version 9.0 MediaAgents, deduplication will work as expected when encryption is enabled.
There are three possible resolutions, workarounds and considerations for Upgrade Planning to support encrypted deduplicated backups:
|
1: Upgrade the Version 7 client to the same version as the CommServe and MediaAgent. 2: Change the Storage Policy associated with the subclients and disable encryption. 3: Disable deduplication in the storage policy used by the subclients. |
When upgrading from 7.0 to 9.0, if the CommServe is upgraded but the MediaAgent and the clients are not upgraded, then deduplication will be available at the Object Level only.
If the CommServe and MediaAgent are upgraded to the current release, but the Client is not upgraded, the restored data from a secondary copy containing encrypted backups enabled using the auxiliary copy operation will not be supported until the Client is upgraded to the current release.
The backward compatibility support for Outlook Add-In functionality in mixed mode scenarios is provided below.
Upgrade the v7 client to the same version as the CommServe and MediaAgent, or Change the Storage Policy associated with the subclients and disable encryption, or Disable deduplication in the storage policy used by the subclients.Therefore, we recommend upgrading both the agent and the DataArchiver Outlook Add-In to the same release version as the CommServe. When of all these components are at the current release version, all functionality is supported.
| The Exchange WebProxy Archiver Agent and the Outlook Add-In must be at the same release level in order for secure stub recalls to be successful in an RPC over HTTP configuration. |
When the CommServe is upgraded to the current version and the clients remain in the previous version, the new subclients created will not have block filter driver enabled. See The Block Filter Driver and Bitmaps to manually activate block filter on these new subclients.
For SnapProtect feature, if the CommServe is upgraded to the current version, the Client and/or the MediaAgent should also be upgraded to the current version.
During 8.0 Unix client installation on 9.0 CommServe, the client group name starting with the special character '[' is not supported. Before installing any 8.0 Unix client, the client group name must be modified. To modify the client group name, see Change the Name of a Client Computer Group for step-by-step instruction.