Upgrade Considerations

Common Technology Engine

CommCell

CommServe

MediaAgent

CommCell Console

Backup & Recovery

Active Directory

DB2

Image Level iDataAgent

Informix

Lotus Notes/Domino Server

Macintosh File System

Microsoft Data Protection Manager

Microsoft SharePoint Server

Microsoft SQL Server

Microsoft Exchange Mailbox iDataAgents

Microsoft Windows File System

MySQL

Backup & Recovery

NAS

Archiving

Domino Mailbox Archiver

Exchange Compliance Archiver

Exchange Mailbox Archiver

File Archiver for NetWare

File Archiver for Unix

File Archiver for Windows

SharePoint Archiver

Content Indexing and Search

Web Search Server

Data Classification Enabler

Replication

ContinuousDataReplicator

Storage Resource Management (SRM)

SRM Server

CommNet

CommNet Server

General

Deprecated Products And Platforms

Before upgrading agents software, make sure to see the Extended Support and Deprecated Products and Platforms for comprehensive information on products and platforms that have been deprecated or placed on Extended Support.

Client Version

Clients with software version 7.0.0 and 8.0.0 are supported once the CommServe is upgraded. Note the following in such cases:

• Make sure all clients are in version 7.0.0 or above before performing the upgrade.
• New features will not be available until the client is upgraded. Additionally, some existing features may not function as expected when the CommServe is upgraded to the current release. See Backward Compatibility Issues for more information on mixed version issues.

Base Client

A Base Client module will be installed on computer when the software component is upgraded. Note that when you uninstall the software the Base Client must be the last component to be uninstalled.

Pre-Upgrade

Post-Upgrade

Deconfigured Clients

During the CommServe upgrade, clients that were deconfigured will be automatically upgraded to the current version in the database. This is applicable for the clients with version 7.0 or 8.0. If you wish to reinstall these clients, you must use current software version during the installation.

Operating Systems / Application Versions

Before performing an upgrade, make sure to check the System Requirements to see if the operating system/application version is supported in the current release. If the operating system/application version is not supported ensure that the operating system/application is upgraded to a supported version.

Registry Keys

• Information from user created registry keys is stored in the operating systems temp directory during the upgrade. The name of the file is GalaxyReg_OLD_But_Not_New.txt. Re-create these registry keys, if necessary.
• The values in all the system created registry keys are set to default after the upgrade. If any of these values were modified prior to the upgrade, the modified values are stored in the operating systems temp directory within GalaxyReg_MIX_OLD_New_Diff.txt.

General

Pre-Upgrade

Upgrading 32-bit CommServe on a Microsoft Windows x64 Platform

Enterprise Version

The CommServe is now supported on Windows x64 platforms. See System Requirements - CommServe for more information.

The CommServe must be upgraded with the Windows x64 binaries - See Upgrade the 32-bit Components installed on Microsoft Windows x64 Platform for step by step instruction. (Upgrade to a 32-bit CommServe is not supported.)

Express Version

The CommServe on a x64 platform can be upgraded and will continue to use the 32-bit version of the software. Use Disc 1 from the Software Installation Disc for Express version to perform this upgrade.

General

• After upgrading the CommServe, make sure that the MediaAgent associated with the Disaster Recovery policy is also upgraded to the same version in order to perform the Disaster Recovery backups successfully.

• If a CommNet Agent was installed on a CommServe that was registered with a CommNet Server, the CommNet Agent is automatically upgraded to current version during the CommServe upgrade.

Database Engine

The CommServe Database Engine will be upgraded to Microsoft SQL Server 2008 database with the service pack during the CommServe upgrade.

If SQL Server has a later Service Pack, make sure to download and install the service pack and/or critical updates after the CommServe upgrade.

Note that SQL Server 2008 is not supported on Windows 2000. Hence if your CommServe resides in Windows 2000, make sure to upgrade operating system prior to CommServe Upgrade

Note that SQL Server 2008 is applicable for CommServe, CommNet Server, SRM Server and Content Indexing Engine.

Post-Upgrade

General

• Verify the following settings by viewing the Server Properties using the Microsoft SQL Server Management Studio:

  In the Memory page, the dynamically configured Maximum memory should be 50% of the physical memory available in the CommServe computer.

• Install post-release updates or Service Packs that may have been released after the release of the software. When you are installing a Service Pack, ensure that it is the same version as the one installed in the CommServe Server. Alternatively, you can enable Automatic Updates for quick and easy installation of updates in the CommCell component.

• If Activity Control was disabled on the client prior to the upgrade, enable it after the upgrade using the Activity Control tab from the Client Computer Properties dialog box in the CommCell Console.

• Some existing features may not function as expected when the CommServe is upgraded and the Clients/MediaAgents remain in a older version of the software. See Backwards Compatibility Issues for more information on such features.

Email and IIS Settings

• The user defined senders email address is not retained after the upgrade. From the Control Panel, open the E-Mail and IIS Configuration dialog box and specify the e-mail address in the Senders Address box on the E-Mail Server tab.

• After the upgrade, in order to view reports, from the Control Panel, open the E-Mail and IIS Configuration dialog box and remove the port number from IIS Server Name and add it in HTTP box.

Command Line Interface

If, in previous releases, you scheduled operations to occur using the Save As Script feature, the script files were saved as .ini formatted files. With this release, if you schedule operations to occur using the Save as Script feature, the script files are now saved as .xml formatted files, which can be executed from the command line interface using the qoperation execute command. Note that .ini formatted script files can still be utilized to manually execute an operation, but not in conjunction with the Save as Script feature. For more information, see Save As Script.

Storage Policy Copy

After the upgrade, the storage policy copies with the options Copy most recent full backups when Auxiliary Copy starts and Manually select Full Backups will be converted to the option Do not Automatically select jobs. Any previous auxiliary copy schedules related to the copies with the option Copy most recent full backups when Auxiliary Copy starts should be deleted, and re-created with the option Select most Recent Full backup when Auxiliary Copy starts.

After the upgrade, the storage policy copy's Year Starts option is converted to the Custom Calendar feature. If previously configured, the values will carry over to the Custom Calendar feature.

Find and Retrieve operation schedules created in the previous release will carry over to this release. However, since this type of content indexing is now considered a legacy feature, new data will not be indexed once the CommServe has been upgraded. Therefore, when these scheduled jobs run, no new data will be found. It is recommended that you delete those schedules and create new Search and Retrieve schedules in the current release. 

VaultTracker Policy

After upgrading the CommServe, note that the Time delay in minutes before starting the VaultTracker policy option, which was located in the Media Management Configuration (Service Configuration) dialog box, is now available as Start exporting media x minute(s) from the execution time of policy option in the Tracking Policy Details dialog box for each VaultTracker policy. Also, note that this option will be enabled by default for each VaultTracker policy. If you do not wish to use this option, you will have to manually disable it for the specific VaultTracker policy.

Registry Keys

• Following an upgrade of the CommServe to the current release, manually add the OracleDeleteAgedBackupPiece registry key on the CommServe. Even if this registry key was previously added as a matter of course and was on the CommServe, it must be added again following an upgrade of the specified CommServe.

• The following registry keys are now available in the Media Management Configuration (Data Aging) dialog box. (See Data Aging of Job History Data for step-by-step instructions on how to access this dialog box.)

  • archiverRestoreHistoryLifeSpan is now the Days to keep the archiver restore job histories option.
  • jobHistoryLifeSpan is now the Days to keep successful backup job histories option.

General

Version

MediaAgent with software version 7.0.0 and 8.0.0 are supported once the CommServe is upgraded. Note the following in such cases:

• Make sure all clients attached to the MediaAgent are in same version or lower version before performing the upgrade.
• Upgrade the MediaAgent first, before upgrading the clients attached to the MediaAgent.
• New features will not be available until the MediaAgent is upgraded. Additionally, some existing features may not function as expected when the CommServe is upgraded to the current release. See Backward Compatibility Issues for more information on mixed version issues.

Pre-Upgrade

Deduplication

All MediaAgents associated with a Storage Policy Copy in deduplication configuration must operate in the same version. When one MediaAgent in a deduplication configuration is upgraded to the current version, then all MediaAgents associated with the storage policy copy (MediaAgents associated with data paths as well as the Deduplication Store) must be upgraded.

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.

Note that the Netware MediaAgent is deprecated in 9.0.0. Hence if your source or destination MediaAgents are on Netware operating system, make sure to upgrade operating system to Linux or point to Windows MediaAgent from Auxiliary Copy.

Index Cache

MediaAgents participating in index cache sharing must operate in the same version. When the Index Cache of a MediaAgent is shared, then all MediaAgents participating in the share must be upgraded together.

General

Java Runtime Environment (JRE)

Consideration for Java Runtime Environment (JRE):

• The software can function with JRE version 1.6.x or higher.

  If a JRE version 1.6.0_06 or higher is available, the software will use the existing JRE software.

  If JRE version 1.6.0_05 or lower is available, or no JRE version is available at all, you will be prompted to install JRE version 1.6.0_16

  You can run CommCell Console as a Remote Web-Based Application without installing the software provided IIS is installed and running on the CommServe computer (or CommCell Console and IIS are running on an alternate computer). However, you must manually install JRE in this case. When running the applet Java™ Runtime Environment (JRE) SE v1.6.0_06 is recommended - can be installed from the software installation disc.

• If you have created or copied shortcuts for the CommCell Console on your desktop or Start menu, you should delete them and re-copy the new shortcut which is created during the upgrade.

Pre-Upgrade

User Privileges

To upgrade Active Directory iDataAgent you now require specific user privileges. Before upgrading, review the table below to identify the privileges:

Domain Admin – A user that belongs to Domain Administrator group for that domain

ADAM Admin – A user that belongs to Roles\Administrator group (container) of configuration partition for that ADAM instance.

LDS Admin – A user that belongs to Roles\Administrator group (container) of configuration partition for that LDS instance.

Local Admin – A user that belongs to Local Administrators group.

Pre-Upgrade

• It is strongly recommended that you run a Full Backup after the upgrade. Upgrading the agent will NOT automatically convert the next incremental update to a Full Backup.
• Image agents will no longer support differential backup, and the differential backups scheduled before the upgrade will run as full backups. Change your existing schedules with differential backups appropriately.

• If you had manually changed any of these settings in the previous release, they will not be preserved in the upgrade:
  • COW Cache size (Minimum and Maximum)
  • COW Cache location

• If you are using the QSnap snapshot enabler with this Agent, see The Block Filter Driver and Bitmaps on the Overview - QSnap page for important information about how the QSnap block filter operates.

• The required CVD resource dependencies set on the virtual node of the cluster will not be preserved in the upgrade.Only the disk resource that contains the partition on which the agent was installed will be set as a dependency for the CVD resource. Add any other disk resources that contain partitions you intend to protect as dependencies for the CVD resource on the cluster group server. For example, the agent was install on the R: drive of the cluster group server. You use the agent to protect the R: and S: drives. You must add the S: drive as a dependency to the CVD resource. This required for the disk resources to fail over properly.

Post-Upgrade

After upgrading the Lotus Notes Database and Document iDataAgents, the Domino version number will not be displayed in the CommCell Console. You will now see Notes Database and Notes Document instead of Notes 6 Database and Notes 6 Document. See Tree Levels in the Lotus Domino Server iDataAgents for an example.

General

Post-Upgrade

SharePoint Database/Document iDataAgents merge with SharePoint Server

The SharePoint Database iDataAgent and SharePoint Document iDataAgent have merged into one SharePoint Server iDataAgent.

Default Backup Sets

In 7.0, only one default backup set was created. It was named defaultBackupSet. In 9.0, two default backup sets are created. One is Documents, the other is Databases.

• The Databases backup set has the same functionality as the SharePoint Database iDataAgent did in the 7.0.
• The defaultBackupSet of the 7.0 SharePoint Document iDataAgent will be renamed to Documents in 9.0 and it remains as the default backup set. If defaultBackupSet was renamed before upgrading, then that name will remain the same and it becomes the default backup set after upgrading.

See Backup Sets - Microsoft SharePoint Server iDataAgent for more information.

Run a Full Backup

• Immediately after upgrading to the current release, run a Full Backup for all subclients of the Databases backup set. This is because a single restore operation cannot restore both the previous release's data and new data of the current release.

Restore Operations

• Restoring data from the current release to a SharePoint Server client of the 7.0 is not supported.
• If you want to restore data of a 7.0, while browsing the data you need to specify a point in time before you upgrade to the current release. See Browse Data Before a Specified Time for details.

Site Collections

In 7.0, the number of site collections that were shown as being backed up in the Backup Job Details, Job History, etc. were erroneously doubled. After upgrading, this has been resolved and the correct number is displayed.

Scripts

After upgrading, it is recommended to regenerate your Save as scripts due to backup set and agent name changes. See Command Line Interface - Save a Job as a Script for more information.

General

Outlook Add-In

We strongly recommend upgrading the Outlook Add-In, and any agents that support it, to the same release version as the CommServe. Otherwise, the Outlook Add-In functionality will be limited or unavailable. For more information, see Backward Compatibility - Outlook Add-In.

Post-Upgrade

Outlook Add-In

• After the upgrade, for Vista clients, the system state will automatically be included in the default subclient and will be backed if a backup is initiated for the default subclient. If you wish to include the system state for user-defined subclients you must manually enable the Backup System State option from the Subclient Properties (Content) dialog box.

• It is strongly recommended that you review the advanced options for the schedules or schedule policies. Some default options may have changed.

• Upgrade on a virtual machine preserves the system state subclient from previous versions, even though system state subclients are no longer created on virtual machines. If a previous system state subclient of the virtual machine is preserved after the upgrade, delete it.

General

NAS Subclients

Every MediaAgent within a storage policy used by NAS subclients must be on the same version of the software, which must be a MediaAgent Version supported with this release of the CommServe software.

Post-Upgrade

• After upgrade, we recommend that you manually run a CROSSCHECK and, if necessary, DELETE EXPIRED BACKUP from RMAN prior to running a data aging operation, in cases where a backup piece has been manually deleted (or marked expired) in the Recovery Catalog. Otherwise, the CommServe database is not made aware of the change and it would become out of sync with the Recovery Catalog. This manual task ensures that the CommServe database is properly synchronized with the Recovery Catalog before data aging is run.

• If you upgraded the Oracle iDataAgent for Oracle on any supported version of  Solaris, AND if you have previously set (or are planning to set) SQLNET_EXPIRETIME in sqlnet.ora (which restricts the iDataAgent access through sqlnet), then follow these post-upgrade steps to prevent potential backup failures:
  1. Shut down the Oracle database and the listener.
  2. Edit the sysliblist file under the $ORACLE_HOME/lib directory.
  3. Add -lthread and -lpthread at the beginning of the sysliblist file. For example:

     -lthread -lpthread -lnsl -lsocket -lgen -ldl -lsched

  4. After performing the above steps, start up the Oracle database and the listener, then run a backup.

• After you upgrade from a 7.0.0 client where you used registry key SID_ExcludeArchPaths to exclude some Oracle log destinations, these log destinations will not be excluded unless you recreate your schedules to exclude these log destinations. You can recreate these schedules from either the subclient or advanced log options.

Post-Upgrade

• After installing or upgrading the Oracle iDataAgent on a Red Hat Linux AS 3.0 32-bit platform, if you want to include the Oracle iDataAgent instance in an Oracle RAC node, follow the procedure to Create a RAC Client.

  Note that any previous backups taken by the upgraded Oracle iDataAgent cannot be restored through the RAC node but can only be restored from the original client. Therefore, we recommend that you perform a full backup of all RAC nodes after creating the RAC client.

• After upgrading the Oracle or Oracle RAC iDataAgent, update the RMAN command line scripts created before the upgrade, with the new command parameters listed under Third-Party Command Line Operations. 

Post-Upgrade

• It is strongly recommended that you run a Full QR Volume Creation job after the upgrade. The QR Agent software will NOT automatically convert the next incremental update to a Full QR Volume creation job.

• If you had manually changed any of these settings in the previous release, they will not be preserved in the upgrade:
  • COW Cache size (Minimum and Maximum)
  • COW Cache location

• EMC SnapView snapshots created with previous releases of the QR Agent and SnapView Enabler cannot be deleted after upgrading to the current release. After deleting the snapshot from the previous version in the QR Browse window (which removes the snapshot from the database) the snapshot must be deleted manually using the EMC Navisphere software. This does not affect any snapshots created after the upgrade.

• If you are using the QSnap snapshot enabler with this Agent, see The Block Filter Driver and Bitmaps on the Overview - QSnap page for important information about how the QSnap block filter operates.

• The required CVD resource dependencies set on the virtual node of the cluster will not be preserved in the upgrade.Only the disk resource that contains the partition on which the agent was installed will be set as a dependency for the CVD resource. Add any other disk resources that contain partitions you intend to protect as dependencies for the CVD resource on the cluster group server. For example, the agent was install on the R: drive of the cluster group server. You use the agent to protect the R: and S: drives. You must add the S: drive as a dependency to the CVD resource. This required for the disk resources to fail over properly.

• After upgrading the clients, all the file servers configured in the earlier releases must be detected again in the upgraded setup, to activate the SnapMirror license on the upgraded clients. See Getting Started - NAS idataAgent Configuration, for step-by-step instructions on detecting a file server.

Post-Upgrade

• After upgrade, the service commands of the previous release software are no longer valid. For more information on the current release service commands, see Service Control for Unix.

• After upgrade, the Follow Mount Point option is automatically selected at the Advanced Backup options dialog box, for a scheduled backup job. See Follow Mount Points for more information.

General

Once the 1-Touch Server is upgraded to 9.0, the clients with software version 7.0 and 8.0 cannot be recovered using Offline recovery. Use Online recovery to restore the 7.0 and 8.0 clients. See Online Recovery for more information.

Pre Upgrade

• Ensure that the 1-Touch Server version always matches the CommServe version.

• This agent must be upgraded to the current version as soon as the CommServe is upgraded.

Post Upgrade

• Online Restore –You must exclude the Calypso folder while performing the Online Restore. This will prevent any older versions of the binaries from being restored.
• Interactive Restore – You must perform the backup on the client computer after the upgrade and then perform the Interactive Restore.

General

Pre-Upgrade

File Share Archiver Agent Merge with File Archiver Windows

The File Archiver for Windows Agent and File Share Archiver Agent have merged into one File Archiver for Windows Agent with enhanced capabilities of archiving and recovering files from both Windows file systems and NAS file servers. Details regarding the changes are provided below.

Licensing

There have been no license naming changes for any of the previously supported DataArchiver configurations. The difference is that the license is consumed at the point of Instance creation, instead of being consumed during installation.

Recovery Operations

• Data archived by the agent in a previous release can be recovered by the File Archiver for Windows Agent in the current release. However, data archived by the File Archiver for Windows Agent in the current release cannot be recovered to an agent from the previous release.
• If you want to recover data from a previous release, while browsing the data you need to specify a point in time before you upgraded to the current release. See Browse Data Before a Specified Time for details.

Post-Upgrade

Agent Name

After upgrading the File Share Archiver Agent, the corresponding icon name in the CommCell Browser will change from File Share Archiver to File Archiver. There is no icon name change when upgrading the File Archiver for Windows Agent, therefore the name in the CommCell Browser will remain as File Archiver.

Instances

The agent has been restructured in the CommCell Browser to include an Instance icon below the agent, and above the archive set, corresponding to the type of data or configuration that was used in the prior release. The new instance types that are created automatically during upgrade are briefly described below.

• If the agent was previously configured for archiving and recovery of Windows file system data, then the upgrade process will automatically create the Local File System Instance type below the agent. The previous property settings in the default archive set and subclients below the Instance will be preserved.
• If the agent was previously configured for Proxy Stub Subclient support to archive and recover data residing on a Celerra file server, then the upgrade process will automatically create the Celerra Instance type below the agent. The previous property settings in the default archive set and subclients below the Instance will be preserved.
• If the agent was previously configured for FPolicy Subclient support to archive and recover data residing on a NetApp filer, then the upgrade process will automatically create the FPolicy Instance type below the agent. The previous property settings in the default archive set and subclients below the Instance will be preserved.
• If the agent was previously configured for archiving and recovery of NAS data residing on any supported file server, which was not configured for Proxy Stub Subclient or FPolicy Subclient support, then the upgrade process will automatically create the Network File Share Instance type below the agent. The previous property settings in the default archive set and subclients below the instance will be preserved.
• The Celerra proxy subclients deleted prior to upgrade would be visible as active instances after the upgrade. 
• After upgrading the File Archiver for Windows Agent to this release, previous Celerra restore operations are now associated with the Local File System instance. This is because 7.0 File Archiver subclient content was assigned to either a Local Migration or a Celerra subclient.
• The FPolicy subclients deleted prior to upgrade would be visible as active instances after the upgrade.
• After upgrading the File Share Archiver Agent to this release, previous FPolicy restore operations are now associated with the Network File Share instance. This is because 7.0 File Share Archiver subclient content was assigned to either a NAS or an FPolicy subclient.
• After upgrading the File Share Archiver from 7.0 to 9.0, the filer name of the first content path in the File Share Archiver subclient will be used as the filer name of the corresponding 9.0 Network File Share instance. If the 7.0 subclient has more than one folder path in the content, they will all be preserved after upgrade. The 9.0 GUI does not allow the user to add data to the subclient content that does not reside on the filer indicated by the filer name of the Network File Share instance. If the user would like to add data residing on a different filer, a new Network File Share instance must be created with that filer name.

Configuration Settings

All previously configured property settings in the CommCell Browser will be preserved after the upgrade, therefore there is no need to re-configure or re-apply these settings after upgrading the agent. For example, the archiving rules, authentication credentials, pre/post processes, filters, security, etc. will be seamlessly ported forward to the new agent design.

Functionality

General CommCell functionality will remain the same for the agent after the upgrade. For example, archive and recovery operations, job management features such as Job History, Reports, Alerts, Schedules, etc. will seamlessly support the new agent design without the need to re-establish any configuration settings.

Run a New Index

Immediately after upgrading to the current release, we strongly recommend that you Start a Migration Archiving Operation that Creates a New Index for all subclients. This is because a single recovery operation cannot recover both the previous release's data and new data of the current release.

Backward Compatibility

Scripts

After upgrading, it is recommended to create new scripts for Network File Share and FPolicy subclients. See Command Line Interface - Save a Job as a Script for more information.

General

• Many of the new features require the latest version of the Content Indexing Engine profile, Contact Professional Service for replacing the old index profile.
• Replace to the latest version of the Content Indexing profile, involves re-content index the data (see Select/Prevent Content Indexing for a Job on a Storage Policy for more information), including data that was secured before the upgrade. This will allow you to seamlessly perform searches on all your data.
• When you upgrade Content Index Engine the existing index profile will not be replaced. As a result the new features like tagging and preview will not be available after the upgrade. Contact Professional Service for replacing the old index profile.
• For tagging and delegate search, ensure that to have a latest version of Content Indexing Engine profile.

Exchange Compliance Archiver

Find and Retrieve operation schedules created in the previous release will carry over to this release. However, since this type of content indexing is now considered a legacy feature, new data will not be indexed once the CommServe has been upgraded. Therefore, when these scheduled jobs run, no new data will be found. It is recommended that you delete those schedules and create new Search and Retrieve schedules in the current release. 

General

pre-upgrade

When upgrading the Web Search Server and Web Search Client, ensure that all the MediaAgents are also upgraded to the current version in order to perform retrieval operations

General

For the Data Classification Enabler, installed using the installer software, stop the Data Classification Enabler service before upgrading any other installed agents. If necessary, delete the old Data Classification databases on the root of each volume.

For Data Classification Enablers, installed using an MSI package (Remote Installs - MSI Packages Using Active Directory Group Policies), uninstall the previous version before upgrading any other installed agents.

General

• This agent must be upgraded to the current version as soon as the CommServe is upgraded.
• 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 will also need to be upgraded to the current version.

Pre-Upgrade

Post-Upgrade

If you are using CDR in Disk Library Replication solution setup (previously known as Remote Office solution), then create the nSuspendSDR registry key and set the value to 1, to stop the replication activities before upgrade.