Backward Compatibility

Topics | Support | Related Topics


Overview

1-Touch for Windows

Auxiliary Copy

ContinuousDataReplicator

Data Encryption

Data Encryption and Deduplication

Deduplication

Inline Copies With Encrypted Data

EMC Celerra NAS NDMP iDataAgent DAR Restores

DataArchiver Outlook Add-In

NetWare Server iDataAgents

Novell GroupWise iDataAgent

SQL Server iDataAgent

Network TCP Port Numbers


Overview

The CommCell can function with two versions of the software. For example, when the CommServe is upgraded to the current version, the clients can remain in the previous versions. See Backward Compatibility - Support for more information and supported versions.

The new features in the current release will not be functional for the MediaAgents or Clients until they are upgraded to the same version as the CommServe. Additionally, some existing features may not function as expected when the CommServe is upgraded. The following sections identify such issues.


1-Touch for Windows

A 6.1 Windows client using the current version of the 1-Touch server does not support the Format system disk option while you are preparing 1-Touch configuration and answer files for the 1-Touch recovery. To enable this support, either upgrade your client to the current release of the software or use the dissimilar disk map option to recreate the system disk.

Auxiliary Copy

Auxiliary copies are not supported if the source and destination MediaAgents are not at the same software release level. Upgrade all MediaAgents associated with the storage policy for auxiliary copies to work properly.


ContinuousDataReplicator

If the CommServe is version 8.0 and the Client is version 7.0, QSnap cannot be used as a snap engine for CDR on Unix. LVM will always be used as a snap engine.

When the CommServe is upgraded to the current version, both source and destination client can remain in the previous version. Also, when the CommServe and destination client are upgraded to the current version, the source client can remain in the previous version. However, if CommServe and source client are upgraded, the destination client also need to be upgraded to the current version.

Data Encryption

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.


Data Encryption and Deduplication

If the CommServe and MediaAgent are upgraded to the current release, for Clients that are not upgraded, de-duplication will not be supported if data encryption is enabled. Data protection and data recovery jobs from such clients may fail. To overcome this problem, you can:

  1. Upgrade the client to the same version as the CommServe and MediaAgent, or
  2. Change the Storage Policy associated with the subclients, or
  3. Disable deduplication in the storage policy used by the subclients. 

Deduplication

If the CommServe is upgraded, but the MediaAgent and the clients are not upgraded, then deduplication will be available only at the Object Level.


Inline Copies With Encrypted Data

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.


EMC Celerra NAS NDMP iDataAgent DAR Restores

If the CommServe is in version 7.0 and the MediaAgent is in version 6.1, DAR restores on Celerra clients running OS 5.5.X and beyond will all run as non-recursive restores. Non-recursive restores do not restore the contents of the selected directories. To overcome this problem, you can:

  1. Run the restores as non-DAR restores, or
  2. Individually select the files that you want restored (do not select the containing directory).

DataArchiver Outlook Add-In

The backward compatibility support for DataArchiver Outlook Add-In functionality in mixed mode scenarios is provided below.

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 DataArchiver WebProxy Agent for Exchange and the DataArchiver 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.

NetWare Server iDataAgents

If you have a version 8.0 CommServe and a client with the version 6.1 NetWare Server iDataAgents, the View Items Restored dialog box will display the same contents regardless of whether successful, failed, skipped, or all is selected.

If the 6.1 client is upgraded to the same release as the CommServe, the View Items Restored dialog box will display Items Not Found if successful, failed, or skipped are selected. However, selecting All will display the list of restored items.


Novell GroupWise iDataAgent

If you have a version 8.0 CommServe and a client with the version 6.1 Novell GroupWise iDataAgent, the options to perform incremental and differential backups will appear in the CommCell Console. However, because incremental and differential backups are not supported with the version 6.1 Novell GroupWise iDataAgent, any backups performed on the version 6.1 client with either incremental or differential backup selected will be automatically converted to a full backup. Therefore, it is recommended the 6.1 client be upgraded to the same release version as the CommServe.


SQL Server iDataAgent

If you have a version 8.0 CommServe and a client machine with 6.1 SQL Server iDataAgent, the advanced backup option Partial (excludes read-only Filegroups) will be visible but will not work as expected until the client is upgraded to a later release.


Network TCP Port Numbers

When specifying a Network TCP Port Number other than 8400 for a MediaAgent's Communications Service (GxCVD), which may be necessary when more than one instance of the MediaAgent is installed on a computer, bear in mind that clients with an earlier release may not be able to communicate through that port. Thus, when specifying a non-default port number in such cases, you should ensure that all clients using the MediaAgent are at a release version (7.0.0 or higher) that supports the Multi Instancing feature, and non-default Network TCP Port Numbers.


Back To Top