Upgrade Considerations

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.

Pre-Upgrade

Post-Upgrade

general

If the CommServe that you want to upgrade is registered with a CommNet server which is on a different computer, first upgrade the CommNet server to the same version that you are planning to upgrade the CommServe to.

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.

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.

• 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.

• 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.

• 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.

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.

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.

Firewall

If you have a direct connection setup where the client computer connects to the CommServe (one-way firewall), you will have to configure the firewall settings of the CommServe and client computer using the CommCell Console. Following the firewall configuration, you will be able to install new components on the upgraded client computer.

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

Post-Upgrade

General

• If you have NAS iDataAgents installed on your MediaAgent, review Upgrade the NAS iDataAgents before upgrading the MediaAgent software.

• Ensure that no tapes are mounted in the drives of libraries attached to the MediaAgent you wish to 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.

For more information, see Upgrade the Deduplication Database.

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.

Disk Libraries

If you had used RevokeDeletePermissions registry key to prevent accidently deleting the disk mount path contents in previous release, then you will have to manually enable the corresponding option at the library level from CommCell Console in the current release. See Prevent Accidentally Deleting Mount Path Contents for step-by-step instructions.

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.

Post-Upgrade

After upgrading the CommServe, perform the following:

1. Enter the active directory user account information on the Active Directory Properties dialog box.

   While entering the user account information, ensure that the username is specified in the following format:

   <Domain Name>\<user name>

   For more information, refer to Modifying User Accounts for Active Directory.

2. Perform the full backup.

Post-Upgrade

• If you performed backups of DAG setups in 8.0, it is recommended you create a new Master Client configuration to resume backups after upgrading to 9.0. Note, however, that the backup data from release 8.0 will remain on the physical server, while all subsequent backups in release 9.0 will remain on the Master Client.

Post-Upgrade

• If you performed backups with release 8.0 32-bit Agents and wish to upgrade to release 9.0 64-bit Agents, you must uninstall the release 32-bit 8.0 software and install the 9.0 64-bit software to use the 9.0 64-bit Agents.

Post-Upgrade

• when you upgrade client from 8.0 to 9.0, ensure that the Log Data Directory path in Instance Properties dialog box is properly directed to the directory where the log files are stored.
• In 8.0, you need to activate sAdvancedBackupOptions registry key to perform a single transaction on mysql dump based backup job. In 9.0, a single transaction is performed by default with the backup of mysql dump. Hence, you need to remove this registry key option after an upgrade.
• In 8.0, you need to activate sLogStagingPath registry key to stage logs to a staging location while performing a restore. Staging location is a default feature in 9.0.  Hence, you need to remove this registry key option after an upgrade.

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 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.

General

If the CommServe is upgraded to 9.0 and 1-Touch server is not upgraded, you can perform only the online recovery of the 8.0 and 7.0 clients.

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.

Post-Upgrade

• The Data Classification metadatabase will be recreated after the upgrade.
• You cannot use the Data Classification Scan for the first incremental backup after the upgrade.

Pre-Upgrade

Post Upgrade

• The Data Classification enabler is integrated with Windows File System agent. The Data Classification Console and Service Control Manager are no longer required to control the data classification scan. For more information about Data Classification, go to FAQs - Windows File System iDataAgent.

General

• 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.

• To avoid possible intermittent message recall failures when using the Outlook Add-In in RPC over HTTP mode, worker process recycling and Web Garden options under IIS 6.0 should be disabled for the DMProxy Service. The installation or upgrade process will do this for you automatically. However, in the event that you need to perform this task manually, see Configure an Application Pool for the Exchange WebProxy Archiver Agent for step-by-step instructions.

Pre-Upgrade

Post-Upgrade

Solaris

Ensure that the cxfs mount points are not busy. If the cxfs mount points are busy during upgrade it is recommended to reboot the client computer.

In case you do not wish to reboot the client computer follow the steps given below:

1. On the client computer, open the command prompt and type the following:
   • simpana stop
   • rem_drv cvfsf
   • unmounts <fs>
   • rem_drv cxhsm
   • simpana start

On completing the above mentioned procedure you will notice that the newer driver is loaded.

Pre-Upgrade

Data Classification

If you are using Data Classification Enabler with the File Archiver and you have created any DataClassSets, you cannot use them after the upgrade.

General

Content Indexing Engine

• For Content Indexing Multi Node environment, all the nodes must be upgraded. Ensure that the Admin Node is upgraded prior to upgrading the other nodes.
• Many of the new features require the latest version of the Content Indexing Engine profile, Contact Professional Service for replacing the old index profile.
• Ensure that to have a license for the new features on the CommServe. See License Requirements for more information on these licenses.
• 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.
• 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. 

Pre-Upgrade

• To take advantage of the new features, it is recommended to upgrade the Web Server along with the CommServe upgrade.

• 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.

• 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.

Pre-Upgrade

Post-Upgrade

Disk Library Replication

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.

Pre-Upgrade

Post-Upgrade

General

The QSM Server now requires a MediaAgent. Hence during the upgrade, if a MediaAgent is not available, the system will automatically install the MediaAgent in the computer.

Before upgrading a CommServe with the SRM Server, ensure that you have permanent license for an additional MediaAgent.

Contact your Software Provider to obtain a copy of MediaAgent license.

Reporting  Services

After the SRM Server upgrade, the SRM reporting services will not available. Therefore, before the upgrade, export the existing reports to a PDF or HTML file.

You can generate the SRM report as long as the existing data on a media is not aged.

General

The following components are not supported after SRM Server upgrade:

• SRM Report schedules
• SRM Thresholds

After upgrading SRM Server, schedules for SRM Reports, SRM Report Schedule Policies and SRM Thresholds will not be carried over to 9.0. You have to re-create the schedules for SRM Reports, SRM Report Schedule Policies and SRM Thresholds. This is because 9.0 SRM Reports Architecture has changed, see SRM Reports - Overview for more information.

Pre-Upgrade

Space Requirement

The following space is required for the CommNet Server during upgrade:

• 3 to 5 times the size of CommNet Server database on local disk space.
• Make sure for tempdb and QNet log files space, the log file properties are modified to Unrestricted File Growth. Use the following steps to modify the log file properties:

  For tempdb file space:

  1. Log on to CommNet Server computer.
  2. Open Microsoft SQL Server Management Studio.
  3. Navigate to <Server Instance> | Database | System Databases | tempdb
  4. Right-click the tempdb, click Properties. The Database Properties - tempdb dialog box appears.
  5. Click Files in the left pane.
  6. From Logical Name column, select templog, click the ... button in the Autogrowth column. The Change Autogrowth for templog dialog box appears.
  7. Make sure Enable Autogrowth check box is selected and under Maximum File Growth, Unrestricted File Growth option is selected.
  8. Click OK.
  For QNet log files:
  1. Log on to CommNet Server computer.
  2. Open Microsoft SQL Server Management Studio.
  3. Navigate to <Server Instance> | Database | QNet
  4. Right-click the QNet, click Properties. The Database Properties - QNet dialog box appears.
  5. Click Files in the left pane.
  6. From Logical Name column, select QNet_Log, click the ... button in the Autogrowth column. The Change Autogrowth for QNet_Log dialog box appears.
  7. Make sure Enable Autogrowth check box is selected and under Maximum File Growth, Unrestricted File Growth option is selected.
  8. Click OK.