Upgrade Considerations - Version 9 to Version 10

Table of Contents

Server

CommServe

Pre-Upgrade

Free Space Requirements for CommServe Upgrade

Before upgrading the CommServe, make sure that the free space available in the CommServe is at least 3 times the size of the current database for performing the upgrade.

Note that the size of the database itself may shrink slightly or remain the same after the upgrade.

Deprecated Versions for CommServe

The CommServe software is no longer supported on computers running Windows 32-bit versions and Windows Server 2003 editions.

Refer to Deprecated Platforms for a comprehensive list.

You can migrate existing CommServe to a Windows x64-bit Server using CommServe Hardware Refresh.

Refer to System Requirements for a list of supported versions.

Database Engine

  • In a Non-Cluster Environment

    During the CommServe upgrade, the Microsoft SQL Server is upgraded as follows:

    • If you have SQL Server 2005, the SQL Server is automatically upgraded to SQL Server 2012 SP2.
    • If you have SQL Server 2008, no SQL Server upgrade takes place. SQL Server 2008 continues to be used.
  • In a Cluster Environment

    The Microsoft SQL Server must be manually upgraded before initiating the CommServe upgrade. Some SQL Server versions do not require to be upgraded.

    • If you have SQL Server 2005 (or an earlier version), you must upgrade to SQL Server 2012 SP2 before starting the CommServe upgrade.
    • If you have SQL Server 2008, the SQL Server upgrade is not required as the 2008 version is still supported.

    For more information and instructions on upgrading the SQL Server, see SQL Server Upgrade.

CommServe and SQL Server on Different Computers Not Supported

Installing the CommServe and the SQL Server on different computers is no longer supported.

If you have this setup configured on a previous release, it is recommended that you move the CommServe database back to the CommServe computer before the upgrade. See Upgrade the CommServe and Database Engine on Separate Computers for more information.

CommServe Express Version License Change

If you have a CommServe installed with Express Version, token-based licenses are converted to traditional licenses. For more information, see What Happens to CommServe Express Version During Upgrade?

.NET Framework and Microsoft Visual C++

Some Simpana components, such as the CommServe and the File System Agent, use .Net Framework and Microsoft Visual C++. When you upgrade a Simpana component, the .Net Framework and Microsoft Visual C++ are also upgraded to meet the new Simpana version requirements. During the upgrade, the services for these third-party application are temporarily stopped.

If you have critical applications using .Net Framework and Microsoft Visual C++, we recommend that you plan the Simpana upgrade accordingly. You can also upgrade these third-party applications manually before you start the Simpana upgrade.

Uninstall CommNet Server

Uninstall CommNet Server before upgrading the CommServe software. CommNet Server is deprecated and we recommend that you transition to Metrics Reporting Server, as described in Transition from CommNet to Metrics Reporting Server.

Uninstall SRM Server and Components

We recommend that you uninstall the SRM Server and any standalone SRM agents. For more information on SRM, see Upgrade - SRM Components.

Post-Upgrade

Log Off from the Command Prompt

After the CommServe database is upgraded, make sure to log off from the CommServe in the command prompt as follows:

qlogout -cs CommserveName

We recommend you to perform the log off operation before you start to run new command line operations.

Verify SQL Server Settings

From Microsoft SQL Server Management Studio, open Server Properties, and from the Memory page verify that the dynamically configured Maximum memory is set to 50% of the physical memory available in the CommServe computer.

Verify Email and IIS Configuration

The user defined senders e-mail 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 under the E-Mail Server tab.

Mobile Applications

CommVault Access has been replaced by the new application "CommVault Edge". Review the following upgrade considerations for the CommVault Edge application:

  • The application will not work if the Web Server is from the previous version. When upgrading the CommServe from Version 9 to Version 10, the Web Server must be also upgraded.
  • After the CommServe and the Web Server are upgraded to Version 10, you must download the new application as the CommVault Access application will not work after the upgrade.

Verify Network Ports

If you have upgraded the CommServe using the Database Upgrade tool, and later if you restore the upgraded database to the newly installed (fresh) database, then the port numbers used by the Web Console and CommCell Console in the earlier version will be changed to the new default port numbers that are used in the current release.
  • By default, Web Console uses port number 80 in the current release.
  • By default, CommCell Console uses port number 81 in the current release.

Make sure that these port numbers are not used by any other application.

Verify CommServe Cache

  • During the upgrade process, the latest updates and service packs for the current software release are downloaded to the CommServe Software Cache folder. Updates from previous releases are cleared from the software cache.

    If the software provider has new updates for the software after the upgrade, you can repopulate the CommServe Software Cache to download the latest updates. See Managing Software Cache - Populating the Cache for more information.

  • If the bCHECK_AUTOUPDATES additional setting was defined in the previous release, its settings (enabled or disabled) will carry over to the current release. If enabled, the CommServe will contact the configured Automatic Updates FTP site every 24-hours check if the CommServe Software Cache is up-to-date. If there are missing updates, they will be downloaded as per the Automatic Update Configuration.
  • Upon upgrade, if you had configured a UNIX share for the CommServe Software Cache in the previous release, the software will automatically point all clients associated with the configured share to the CommServe Software Cache as the source for updates.  A UNIX share can no longer be configured for the CommServe Software Cache. Instead, UNIX Clients can be designated as software caches as part of Automatic Updates Multicache Configuration. Once designated as an software cache, a UNIX client can be configured to push out the latest software packages it receives from the CommServe Software Cache to the clients within the CommCell that are selected to receive their updates from this UNIX software cache. For more information, see Software Cache.
  • Upon upgrade, if you had enabled the Get Updates From Share option in the previous release, the software will automatically point all clients associated with the configured share to the CommServe Software Cache as the source for updates.

Disable Client Certificate Authentication

In a locked down CommCell, authentication of client certificates is enforced during install and upgrades.

Hence when upgrading clients to the current software version in a locked down CommCell, it is recommended that you disable the lock-down mode for the upgrade to complete successfully.

Use the following steps to the disable certificate authentication during CommCell upgrade:

  1. Disable the certificate authentication for the CommServe. To disable:
    • From the CommCell Console, right-click the CommServe computer and click Properties.
    • Click the Firewall Configuration tab.
    • Click the Options tab
    • Clear Lock down CommCell if selected.
    • Click OK to save the changes.
  2. Upgrade the clients.
  3. Enable certificate authentication from the CommServe.

    For step-by-step instructions on enabling certificate authentication, see Enable Client Certificate Authentication on the CommServe.

Upgrade MediaAgent to Enable Browse and Restore Operations Using Web Console

After upgrading the CommServe, if you want to browse and restore from MediaAgent using Web Console, make sure that the associated MediaAgent is also upgraded to the current version.

MediaAgents

Pre-Upgrade

Follow an Upgrade Sequence

New features in this release will not be available until both the MediaAgent and its associated Clients are upgraded. Use the following steps to upgrade MediaAgents:

  • Upgrade the MediaAgent first, before upgrading the clients attached to the MediaAgent.
  • Make sure to upgrade all the clients associated with the MediaAgent as soon as the MediaAgent is upgraded.

Additionally, some existing features may not function as expected when the CommServe is upgraded to the current release.

Upgrade Related MediaAgents at the Same Time

Some features require multiple MediaAgents. If you have implemented such features ensure that the related MediaAgents are upgraded together.

MediaAgents are considered as 'related' for the following features:

  • Deduplication - All MediaAgents associated with a storage policy copy in the deduplication configuration.
  • GridStor - MediaAgents associated with the data paths in any storage policy.
  • Index Cache Server - All MediaAgents associated with an Index Cache Server.
  • Subclients in a BackupSet or Instance - All MediaAgents associated with the subclients in a backupset or instance must be upgraded together, especially if the wildcards are used to define the contents of any of the subclients.
  • Auxiliary Copy - Auxiliary Copy operations are not supported if the source and destination MediaAgents are not at the same release.

MediaAgents Using a Shared Index Cache

If you plan to upgrade the MediaAgent where the shared index cache is configured, then you should also upgrade all the other MediaAgents using the shared index cache.

Upgrade MediaAgents for Accurate Information During Browse and Find Operations from Web Console

Browse and Find operations will not show deleted items across cycles, if MediaAgent is at an earlier version of the software than the CommServe.

It is recommended to upgrade all MediaAgents to the same version as the CommServe.

Media in Libraries

Ensure that no tapes are mounted in the drives of libraries attached to the MediaAgent you wish to upgrade.

Move the Mount Path Location If It is Located in the Install Directory

Before upgrading MediaAgent, if you have created Disk Library under <Software_Installation_Directory> location, make sure to change the Mount Path location to different location and then copy all the content (files and folders) under existing Mount Path to new Mount path.

Use the following steps to change the mount path location:

  1. From the CommCell Console, click the Control Panel icon.
  2. From the Control Panel, click the Library and Drive Configuration icon.
  3. Select the MediaAgent whose devices you want to detect or display and then click OK.
  4. Click OK to continue.
  5. Locate the disk library for which you wish to move the mount path.
  6. Right-click the mount path that you wish to move and then select Properties.
  7. From the Mount Path Properties dialog box, enter the new path:
    • If you select Local Path, click Browse to select a mount path, or type a mount path.
    • If you select Network Path, type the user name and password to access the network share. Click Browse to select a mount path, or type a mount path.
  8. Click OK to save the information.

    The mount path is moved to the specified location.

  9. Copy all files and folder available under old mount path location to new mount path location.
  10. Perform the upgrade of the MediaAgent.

Optical Library is Deprecated

Optical Library is deprecated in the current release. When you upgrade a MediaAgent with an Optical Library attached, the upgrade will fail.

In such situations, the MediaAgent with the Optical Library can remain in the previous version or you can deconfigure the Optical Library and then perform the upgrade.

NetWare and Tru64 MediaAgents are on Extended Support

NetWare MediaAgent is on Extended Support and cannot be upgraded.

Refer Product on Extended Support for more information.

Tru64 MediaAgent is on Extended Support and cannot be upgraded.

Refer Product on Extended Support for more information.

Data Aging

Pruning might fail when:

  • The MediaAgent that is associated with the library (Data Mover MediaAgent) is upgraded to same version and the MediaAgent that hosts the DDB (DDB MediaAgent) is in the previous version.
  • The DDB MediaAgent is upgraded to current version and Data Mover MediaAgent is in the previous version.

We recommend you to have both the MediaAgents in the same version to reclaim the disk space.

Post-Upgrade

Additional Space Requirements for Index Cache

Index Cache now requires 5% more storage space. Verify and ensure that you have sufficient disk space for the index cache in the current release.

Also note that the default value of Index Retention Criteria is now changed to 15 days. (Previously this was 35 days.)

However, if you have changed the default value, the changed value will be carried forward after the upgrade.

As Index Retention Criteria affects the number of days for which the index cache is retained and as additional space is now required for the index cache, ensure that the value of Index Retention Criteria specified in MediaAgent Properties (Catalog) tab is set appropriately after the upgrade.

Media in Libraries with I/E Port

If you had used nUseImpExpBitForImport additional setting to prevent exported media in I/E port to be re-imported back to the library after reset 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 Import of Exported Media after Resetting a Library for step-by-step instructions.

First Incremental Backup Requires More Time Due to Indexing Changes

After upgrading the MediaAgent to version 10, the first incremental backups will require additional time to complete. The additional time is required to convert the index of that subclient to version 10 format.

CommCell Console

Java Runtime Environment (JRE) Upgrade

The software supports Java 7, JRE version 1.7.0_17 or higher.

For Macintosh the software supports Java 7, JRE version 1.7.0_xx.

If version 1.7.0_17 or higher is available on the computer, the software uses the existing JRE software.

If the JRE version is lower than 1.7.0_17, or no JRE is available at all, you will be prompted to install JRE version 1.7.0_17.

To run the CommCell Console as a remote web-based application without installing the software, the computer must have IIS and JRE installed.

Reconfigure Web Administration

If the CommServe was configured for Web administration manually after the install in the previous version, then after upgrading the CommServe, you should re-configure the CommServe for Web administration manually.

Re-Create Shortcuts for CommCell Console

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.

Web Server and Web Console

Pre-Upgrade

Web Server and Web Console are Not Backward Compatible

Web Server and Web Console are not backward compatible and must be upgraded to the current version as soon as the CommServe is upgraded.

Tomcat Configuration Files

If you configured the Web Console for secured connections (to use HTTPS instead of HTTP), ensure that the Tomcat custom configuration files and certificates are saved before the upgrade.

Cannot Be Remotely Upgraded from the CommCell Console

The Web Server and Web Console cannot be remotely upgraded  from the CommCell Console.

You must upgrade them using the Interactive upgrade method.

Web Client Renamed

The Web Console was referred as ‘Web Client’ in the previous releases. When the Web Client is upgraded to the current version, both the Compliance Search and the Web Console components are installed as part of the upgrade.

Upgrading a Web Client Installed on the CommServe Computer

You cannot directly upgrade the Web Client component when it is installed on the CommServe computer. Use the following steps to upgrade the Web Client:

  1. Uninstall the Web Client component. See Uninstalling Components - Topics for more information.
  2. Install the Web Client (using Version 9 software) on a different client computer. Make sure the client you choose does not have the Content Indexing Engine installed as it cannot be upgraded. See Install the Web Client for more information.
  3. Upgrade the Web Server. See Upgrade - Web Server for more information.
  4. Upgrade the client computer where you installed the Web Client. See Upgrade - Web Client for more information.

Deprecated Versions for Web Server

  • The Web Server software is no longer supported on computers running Windows 32-bit versions and Windows Server 2003 editions.
  • You must decommission existing Web Server on 32-bit and install a new Web Server on Windows x64-bit Server.

    Refer to System Requirements for a list of supported versions.

Deprecated Versions for Web Console

  • The Web Server software is no longer supported on computers running Windows 32-bit versions and Windows Server 2003 editions.

    Refer to System Requirements - Web Server for a list of supported versions.

  • The Web Console software is no longer supported on computers running Windows 32-bit versions.

    Refer to System Requirement - Web Console for a list of supported versions.

Post-Upgrade

Change the Web Console URL Link Provided in the CommCell Console

The link to the Web Console from the CommCell Console may need to be updated in the following cases:

  • The Web Console is installed on multiple computers and the link should not be the computer where the Web Console was installed first.
  • Multiple Web Console computers are upgraded to the current release and the link should not be the Web Console computer upgraded first.

Update the URL for the link to the Web Console using the following command:

qoperation execscript -sn SetKeyIntoGlobalParamTbl.sql -si WebConsoleURL -si y -si "http://hostname:port/webconsole/clientDetails/fsDetails.do?clientName=CLIENTNAME"

where:

  • hostname is the hostname of the computer where the Web Console is installed
  • port is the port number used by the Web Console

Upgrade Associated MediaAgents to Browse Client Data

When the CommServe and Web Server are upgraded browsing the client data from the Web Console may fail if the MediaAgent is not upgraded.

Hence, it is recommended to upgrade all MediaAgents to the same version as the CommServe and Web Server.

Clusters

Pre-Upgrade

Upgrading Clients in a Microsoft Cluster Environment

It is required that each node maintains its status (Active or Passive) throughout the upgrade session. If the Active node needs a reboot during the upgrade process, upon reboot, it should be made Active node again before resuming the upgrade operation.

If the status of the nodes (Active or Passive) is not maintained throughout the upgrade session, then the cluster plug-in resource may get removed after the upgrade operation is complete. In such a case, do the following to recreate your cluster plug-in resource:

  1. From the CommCell Console, right-click the <Cluster Group Client>, and click Properties.
  2. Click Advanced on the Client Computer Properties dialog box, and then click the Cluster Group Configuration tab.
  3. Click the Force Sync configuration on remote nodes checkbox to force the cluster configuration on the remote clients.

Upgrading Clients in a Veritas Cluster (VCS) Environment

During the upgrade of Veritas cluster nodes, make sure to upgrade the passive nodes first, and then continue with the active nodes.

Upgrade Clients with Products That are Not Backward Compatible

The following products must be upgraded as soon as the CommServe is upgraded:

  • 1 Touch
  • Web Serve and Web Console

Post-Upgrade

Cluster Group Configuration after Upgrade

The following consideration is applicable if you have created a new cluster group after upgrading the clients residing in a cluster environment to the current release:

  • Before configuring the newly created cluster group from the CommCell Console, install the required components on all the physical computers using interactive install procedure, and then configure the newly created cluster group from the CommCell Console.
  • If you want to configure the newly created cluster group for the components that were already installed on the Virtual node, first interactively install these components on all the physical computers, and then configure the cluster group for these components from the CommCell Console.

Reinstalling Simpana on a Decommissioned Version 9 Cluster Client

If you uninstalled Simpana version 9 from a cluster client before or after the CommServe software was upgraded from version 9 to version 10, you can again reinstall the software using the cluster client definitions stored in the CommServe database (unless the client was permanently removed).

In Simpana version 10, cluster clients are referred to as "cluster group clients". Use the following steps to reinstall the software on the cluster group client:

  1. Install the required Simpana components on each of the physical nodes.

    During the installation, you will be asked to provide the names of both the physical nodes and cluster servers.

  2. After the installation, open the CommCell Console, navigate to Client Computers from the CommCell Browser, right click the <Cluster Group Client> and then click Properties.
  3. On the Client Computer Properties dialog box, click Advanced.
  4. On the Advanced Client Properties dialog box, click the Cluster Group Configuration tab and then select the Force Sync configuration on remote nodes check box.
  5. Click OK.
  6. Click OK to close the Client Computer Properties dialog box.

Backup

1-Touch

1-Touch Server is Not Backward Compatible

1-Touch agents are not backward compatible and must be upgraded to the current version as soon as the CommServe is upgraded.

Solaris 9 clients can be recovered using Simpana version 9 on Solaris 9 boot servers.

Restoring after Upgrade

After the upgrade, we recommend to perform a new backup of the client. Once the data is backed up, you can proceed to perform an 1-Touch offline restore.

For more information on restoring data post-upgrade, refer to the following sections:

Active Directory

Verify User Privileges before You Upgrade

To upgrade Active Directory iDataAgent, you require specific user privileges. Before upgrading, review the User Privileges table to identify the privileges.

Data Classification for UNIX

Applicable for Upgrades with Service Pack 5 or Higher

Upon upgrade, for each subclient, the mount points that make up the subclient content are checked for in the Data Classification monitored volumes list on clients in the previous version. If there is at least one such match then Optimized Scan is enabled on that subclient and the mount points that are not monitored are filtered out; if there is no match then Optimized Scan is not enabled for that subclient.

Restart Services after the Upgrade

After upgrading the client, restart the Data Classification Enabler services.

Post-Upgrade Considerations

  • Any new mount points that are created post upgrade will be automatically monitored if they are part of the subclients for which Optimized Scan feature is enabled.
  • To explicitly add the volumes that are filtered out during the upgrade to the monitored volumes list, use the following command.

    DcClient -monitor <mount_path>

    This might be necessary when creating new subclients or when altering the content of the existing subclients.

Applicable for Upgrades with Service Pack 4 or Earlier

Disable/Enable Data Classification during Upgrade

  1. Before upgrading the client computer, disable Data Classification from the backup set as follows:
    1. From the CommCell Browser, navigate to Client Computers | <Client>.
    2. Right-click the <Backup Set> and then click Properties.
    3. In the Backup Set Properties dialog box, select a different data scan option other than Use Data Classification.
    4. Click OK.
  2. After the upgrade, enable Optimized Scan (new term to refer to Data Classification in Version 10) for each subclient that requires an improved scan performance.
    1. From the CommCell Browser, navigate to Client Computers | <Client> | <Backup Set>.
    2. Right-click the <Subclient> and then click Properties.
    3. In the Subclient Properties dialog box, click the Advanced Options tab and then select Optimized Scan.
    4. Click OK.

If you have already upgraded the client with Data Classification enabled, then the Optimized Scan feature is automatically enabled for all subclients, both default and user-defined. The Optimized Scan feature will start to monitor mount points that were not monitored before the upgrade, causing performance issues on clients with large number of mount points.

Use the following steps to disable the Optimized Scan feature for those mount points that do not need to be monitored.

  1. On the client computer, open the command prompt and navigate to the /<Software Installation Directory>/Base directory.
  2. Run the following command to obtain the list of mount points being monitored:

    ./DcClient –getinfo

  3. Identify the mount points that do not require to be monitored.
  4. Run the following command to stop monitoring a specific mount point:

    ./DcClient –donot-monitor /<mount_path>

    Repeat this step for each mount point that does not require to be monitored.

Restart Services after the Upgrade

After upgrading the client, restart the Data Classification Enabler services.

Post-Upgrade Considerations

  • The Data Classification meta database will be recreated after the upgrade.
  • You cannot use the Data Classification scan for the first incremental backup after the upgrade.

DB2

Stop DB2 Services on UNIX Clients before the Upgrade

Make sure to stop the DB2 services before upgrading Simpana on a DB2 UNIX client.

The DB2 Services need to be restarted to reload the new Simpana VENDOR library used by the db2logmgr process. 

This will prevent the following error from occurring during an online full backup job.

SQL2428N The BACKUP did not complete because one or more of the requested log files could not be retrieved

Enable the Restart Oracle/DB2 Services Option for the Windows Client

To restart DB2 services on Windows client computers, enable the Restart Oracle/DB2 services (if applicable. Oracle/DB2 Instances need to be restarted to load Simpana Media Library for Data protection.) check box located on the General tab of the Upgrade Software Options dialog box. The  Simpana software detects and stops the DB2 services if they are running during an upgrade and restarts the services after the upgrade.

Assign the User Group to the Simpana Install

Assign the user group to a group with Deployment permissions.

Consider Memory Requirements

Insufficient memory may cause 32-bit client upgrades to fail on AIX computers as memory requirement has increased due to added functionality.

In such cases, it is recommended to grant read permissions for others (chmod o+r) on shared libraries and executables during upgrade so that the services start without issues. This can be done by setting the sAIXGrantReadPermForOthers additional setting on the CommServe.

See AIX Client Upgrade Failed for more information.

Grant 'Read' Permissions for Other Users on AIX Computers

Before performing a remote upgrade on an AIX client computer, installed binaries should have read permissions for other users.

Use the following steps to add read permissions to other users:

  1. Ensure that no jobs are running on any Simpana instance. You have to restart Simpana services for all instances to change the permissions.
  2. From the Command Prompt, run the following command:

    cvpkgchg

  3. Type 2 and press Enter.
  4. Select the type of permission that you want to assign to other users and press Enter.
  5. Type Yes to change the permissions.
  6. Restart Simpana services for all instances for the changes to take effect.

Documentum

Consider Memory Requirements

Insufficient memory may cause 32-bit client upgrades to fail on AIX computers as memory requirement has increased due to added functionality.

In such cases, it is recommended to grant read permissions for others (chmod o+r) on shared libraries and executables during upgrade so that the services start without issues. This can be done by setting the sAIXGrantReadPermForOthers additional setting on the CommServe.

See AIX Client Upgrade Failed for more information.

Grant 'Read' Permissions for Other Users on AIX Computers

Before performing a remote upgrade on an AIX client computer, installed binaries should have read permissions for other users.

Use the following steps to add read permissions to other users:

  1. Ensure that no jobs are running on any Simpana instance. You have to restart Simpana services for all instances to change the permissions.
  2. From the Command Prompt, run the following command:

    cvpkgchg

  3. Type 2 and press Enter.
  4. Select the type of permission that you want to assign to other users and press Enter.
  5. Type Yes to change the permissions.
  6. Restart Simpana services for all instances for the changes to take effect.

Restart Services after the Upgrade

After upgrading the Windows client, restart the Oracle services. If services are not restarted, backup jobs will remain in the pending state.

Exchange Server

Browse from Backup Set Level is Not Supported on Clients from Previous Version

If the CommServe is upgraded and client is still at an older version and the content of the defaultBackupSet is modified, then browse operations will not work from the Backup Set level.

In such cases,

  • Browse and Restore at the Subclient level.
  • Upgrade the Client computer and related MediaAgent to the same version as the CommServe and then run a Browse and Restore operation at the Backup Set level.

CAL (Client Access License) Replaces the Traditional License for Exchange Mailbox

Client Access License (CAL) is now required for protected and archived mailboxes. License consumption is based on the number of mailboxes in your system, rather than the number of clients, agents, and storage policies. This allows you to purchase licenses based on your data size.

Previously, a license was consumed for each client.

For more information, see Client Access License - FAQ - How Do I Use This License if I Have Upgraded from a Previous Version?

Simpana OnePass Restore

Once you upgrade the CommServe to the current release, Simpana OnePass Restore of Exchange Database backups is no longer supported.

Automatic Conversion to Full Backup

For the Exchange Mailbox agent, the first backup after upgrading the agent is automatically converted into a full backup.

Image Level

Settings Not Preserved during the Upgrade

  • If you have manually changed any of these settings in the previous release, they will not be preserved during the upgrade:
    • COW Cache size (Minimum and Maximum)
    • COW Cache location
  • The required CVD resource dependencies set on the virtual node of the cluster will not be preserved during the upgrade.

Make sure to re-establish these setting after the upgrade:

QSnap and Block Filters

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.

Perform a Full Backup after the 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.

Reboot the Client after the Upgrade

If the client has CXBF devices configured, you must reboot the client after upgrading the Image Level agent to allow CXBF devices to load properly.

Image Level ProxyHost

Upgrade is Not Supported - Product is Merged

The functionality in this product is now available in IntelliSnap Backup. We recommend that you transition to IntelliSnap Backup.

Contact your software provider if you need assistance in transitioning to IntelliSnap Backup.

New installations and upgrades are not supported.

Lotus Notes/Domino Server

CAL (Client Access License) Replaces the Traditional License

Client Access License (CAL) is now required for protected and archived mailboxes. License consumption is based on the number of mailboxes in your system, rather than the number of clients, agents, and storage policies. This allows you to purchase licenses based on your data size.

Previously, a license was consumed for each client.

For more information, see Client Access License - FAQ - How Do I Use This License if I Have Upgraded from a Previous Version?

After Upgrading the Lotus Notes iDataAgent the First Few Backups May Display Low Deduplication Ratio

After upgrading Lotus Notes iDataAgent, the first few backups may display lower deduplication ratio. The deduplication ratio will increase after few backup jobs.

Microsoft Data Protection Manager

Upgrade is Not Supported - Product is Merged

The functionality in this product is now available in Microsoft Windows File System and Microsoft SQL Server iDataAgents.

New installations and upgrades are not supported.

Microsoft SharePoint Server

Post-Upgrade

Ensure to reconfigure the content for Database subclient.

To browse data backed up in v 9.0, the End Time should be a date before the completion of upgrade.

See FAQ for more information.

After Upgrading the SharePoint Server iDataAgent the First Few Backups May Display Low Deduplication Ratio

After upgrading SharePoint Server iDataAgent, the first few backups may display lower deduplication ratio. The deduplication ratio will increase after few backup jobs.

Recreate the Save as Script for SharePoint Document Restore after Upgrading the SharePoint Server iDataAgent to Version 10 Service Pack 5

The Save as Script for restoring SharePoint Document should be recreated after upgrading the SharePoint Server iDataAgent from V9.0 to V 10.0 Service Pack 5.

Reconfigure the SharePoint Database Subclient after Upgrading to Version 10

Introduction of a new backup set called Site Collection has changed the format for Database subclient content. Therefore after upgrading to V 10.0 reconfigure the Database subclient content.

Also, if before upgrading, you were backing up sites using the Farm backup set Export Method, then after upgrading to V 10.0 configure to back up these sites using the SharePoint Document backup set.

First Backup Post-Upgrade Should be a Full Backup

After upgrading to V 10.0,  the first Database and Document backup should be a Full backup.

NAS

Automatically Upgraded with CommServe

NAS iDataAgent is automatically upgraded with the CommServe.

NAS Components Do Not Require Separate Installation

In the current version, the NDMP Remote Server (NRS) and File System Restore Enabler (NRE) components are integrated as follows:

  • The NDMP Remote Server is part of the MediaAgent software.
  • The File System Restore Enabler is part of the File System iDataAgent software.

In Version 9, these add-on components had to be installed separately for the NAS iDataAgent.

NetWare File System

Upgrade is Not Supported - Product is Deprecated

NetWare File System is deprecated.

If you have clients with these components, make sure to uninstall them before upgrading the client to the current version.

See End-of-Life, Deprecated and Extended Support for more information.

Novell GroupWise

Upgrade is Not Supported - Product is Deprecated

New installations and upgrades are not supported for this product.
  • If you wish to use Groupwise 2012 and earlier versions on a Version 10 CommServe, use Simpana® Version 9 package.
  • For versions greater than Groupwise 2012, we recommend that you transition to OES File System.

Oracle

Data Aging Requirements after 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.

Enable the Restart Oracle/DB2 Services Option

To restart Oracle services on Windows client computers, select the Restart Oracle/DB2 services (if applicable) check box located on the General tab of the Upgrade Software Options dialog box. Oracle Instances must be restarted to load the Simpana Media Library for Data protection. The Simpana software detects and stops the Oracle services if they are running during an upgrade and restarts the services after the upgrade.

Restart Services after Upgrading on Windows

After upgrading the Windows client, restart the Oracle services. If services are not restarted, backup jobs will remain in the pending state.

Table Restore after the Upgrade

After upgrading the client and the MediaAgent to the current version, the table restore from Version 8 client backup fails. Use the following post-upgrade steps to prevent table restore failures:

  1. From the CommCell Browser, navigate to Client Computers.
  2. Right-click the <Client> to be configured and then click Properties.
  3. Click Advanced.
  4. Click the Advanced Settings tab and then click Add.
  5. In the Name field, type sDISABLE_ORA_USE_NEWBROWSE.
  6. In the Value field, type Y.
  7. Click OK to save the key.
  8. Click OK.

Windows:

On Windows, the Oracle service restart is required for an upgrade. So please plan the upgrade accordingly.

Enable the Restart Oracle/DB2 Services Option

To restart Oracle services on Windows client computers, select the Restart Oracle/DB2 services (if applicable) check box located on the General tab of the Upgrade Software Options dialog box. Oracle Instances must be restarted to load the Simpana Media Library for Data protection. The Simpana software detects and stops the Oracle services if they are running during an upgrade and restarts the services after the upgrade.

Oracle RAC

The upgrade considerations are the same as Oracle.  Make sure to upgrade all clients that are part of the RAC client to access the new features.

Windows:

On Windows, the Oracle service restart is required for an upgrade. So please plan the upgrade accordingly.

Enable the Restart Oracle/DB2 Services Option

To restart Oracle services on Windows client computers, select the Restart Oracle/DB2 services (if applicable) check box located on the General tab of the Upgrade Software Options dialog box. Oracle Instances must be restarted to load the Simpana Media Library for Data protection. The Simpana software detects and stops the Oracle services if they are running during an upgrade and restarts the services after the upgrade.

You might see the push upgrade job successful but get the following error:

Upgrade software successful but installer failed to start Oracle services. Manually start Oracle services on client.

If you get that error, manually restart the Oracle service after a successful upgrade.

OSSV Plug-In

Upgrade Not Supported

New installations and upgrades are not supported in this release.

A new solution using NetApp Logical replication will be available in a future service pack.

ProxyHost

Upgrade is Not Supported - Product is Merged

The functionality in this product is now available in IntelliSnap Backup. We recommend that you transition to IntelliSnap Backup.

Contact your software provider if you need assistance in transitioning to IntelliSnap Backup.

New installations and upgrades are not supported.

Quick Recovery Agent

Upgrade is Not Supported - Product is Merged

The functionality in this product is now available in IntelliSnap Backup. We recommend that you transition to IntelliSnap Backup.

Contact your software provider if you need assistance in transitioning to IntelliSnap Backup.

New installations and upgrades are not supported.

Recovery Director

Upgrade is Not Supported - Product is Deprecated

Recovery Director is deprecated.

If you have clients with these components, make sure to uninstall them before upgrading the client to the current version.

See End-of-Life, Deprecated and Extended Support for more information.

SAP

Consider Memory Requirements

Insufficient memory may cause 32-bit client upgrades to fail on AIX computers as memory requirement has increased due to added functionality.

In such cases, it is recommended to grant read permissions for others (chmod o+r) on shared libraries and executables during upgrade so that the services start without issues. This can be done by setting the sAIXGrantReadPermForOthers additional setting on the CommServe.

See AIX Client Upgrade Failed for more information.

Grant 'Read' Permissions for Other Users on AIX Computers

Before performing a remote upgrade on an AIX client computer, installed binaries should have read permissions for other users.

Use the following steps to add read permissions to other users:

  1. Ensure that no jobs are running on any Simpana instance. You have to restart Simpana services for all instances to change the permissions.
  2. From the Command Prompt, run the following command:

    cvpkgchg

  3. Type 2 and press Enter.
  4. Select the type of permission that you want to assign to other users and press Enter.
  5. Type Yes to change the permissions.
  6. Restart Simpana services for all instances for the changes to take effect.

Restart Services after Upgrading on Windows

After upgrading the Windows client, restart the Oracle services. If services are not restarted, backup jobs will remain in the pending state.

UNIX File System

Consider Memory Requirements

Insufficient memory may cause 32-bit client upgrades to fail on AIX computers as memory requirement has increased due to added functionality.

In such cases, it is recommended to grant read permissions for others (chmod o+r) on shared libraries and executables during upgrade so that the services start without issues. This can be done by setting the sAIXGrantReadPermForOthers additional setting on the CommServe.

See AIX Client Upgrade Failed for more information.

Grant 'Read' Permissions for Other Users on AIX Computers

Before performing a remote upgrade on an AIX client computer, installed binaries should have read permissions for other users.

Use the following steps to add read permissions to other users:

  1. Ensure that no jobs are running on any Simpana instance. You have to restart Simpana services for all instances to change the permissions.
  2. From the Command Prompt, run the following command:

    cvpkgchg

  3. Type 2 and press Enter.
  4. Select the type of permission that you want to assign to other users and press Enter.
  5. Type Yes to change the permissions.
  6. Restart Simpana services for all instances for the changes to take effect.

Tru64 File System is on Extended Support

Tru64 File System is on Extended Support and cannot be upgraded.

Refer Product on Extended Support for more information.

Browse from Backup Set Level is Not Supported on Clients from Previous Version

If the CommServe is upgraded and client is still at an older version and the content of the defaultBackupSet is modified, then browse operations will not work from the Backup Set level.

In such cases,

  • Browse and Restore at the Subclient level.
  • Upgrade the Client computer and related MediaAgent to the same version as the CommServe and then run a Browse and Restore operation at the Backup Set level.

Client Group Name

During Version 8 UNIX client installation on Version 9 CommServe, the client group name starting with the special character '[' is not supported. Before installing any Version 8 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 instructions.

If the CommServe is in the current version and the client is in the previous version, wildcard support for defining subclient content is limited to what is supported in the previous version. For more information, refer documentation for the corresponding version.

Upgrade Not Supported for Solaris 10 (Sparc) Operating System GA Version with Patch Level Less than 119963-14

Upgrade is not supported for Solaris clients running Solaris 10.x SunoS (Sparc) with patch level less than 119963-14.

Patch Required to Upgrade Red Hat Enterprise Linux/CentOS 4.7 Clients

Download and install the patch from the following location on Red Hat Enterprise Linux/CentOS 4.7 clients prior to the upgrade.

https://rhn.redhat.com/errata/RHBA-2008-0650.html

Windows File System

Browse from Backup Set Level is Not Supported on Clients from Previous Version

If the CommServe is upgraded and client is still at an older version and the content of the defaultBackupSet is modified, then browse operations will not work from the Backup Set level.

In such cases,

  • Browse and Restore at the Subclient level.
  • Upgrade the Client computer and related MediaAgent to the same version as the CommServe and then run a Browse and Restore operation at the Backup Set level.

Out of Place Restores to Older Clients are not Supported

Backed up data from clients running the current Simpana version cannot be restored to clients running older versions.

Changes in the Phases Associated with a Backup Job

To speed up backups, in the current version, the backup job will complete after the scan phase if no files in a subclient were changed or added. Backup and archive index phases will not be performed.

When you upgrade a client from the previous version to the current version, this option is not available by default. To enable this option make sure that SkipEmptyBackup key is created in the gxGlobalParam table and its value is set to 1.To disable this option later, you can set the value of this key to 0.

Use the following steps to enable/disable this key:

  1. From the CommCell Browser, right-click <CommServe> and point to Properties.
  2. Click the Additional Settings tab.
  3. Click Add.
  4. In the Name box, type SkipEmptyBackup.
  5. Select CommServDB.GXGlobalParam from the Category list.
  6. Select INTEGER from the Type list.
  7. In the Value box, type:
    • 1, if you want to enable this key.
    • 0, if you want to disable this key later.
  8. Click OK twice.

Number of Objects Backed Up Appears Higher on a Client with Older Version of the Software

If the MediaAgent and CommServe are in the current version and client is in the previous version, then the number of objects displayed in the Job Details dialog box is higher as the parent/root folders of files that are not changed are also taken into account in this release.

Workstation Backup

Upgrade is Not Supported - Product is Merged

The functionality in this product is now available in Laptop Backup.

Contact your Software Provider if you need assistance in transitioning to Laptop Backup.

New installations and upgrades are not supported.

File Archive

File Archiver for BlueArc

Transition to Simpana OnePass Agent

This product is now available as Simpana OnePass Agent for BlueArc.

Upgrade Not Available for File Share Archiver Client for BlueArc

If you have File Share Archiver Client installed in your computer, we recommend you to uninstall it and install the latest version of the software.

Version 9 OnePass Subclients Count towards Capacity License Calculation

Starting Service Pack 6, existing OnePass subclients from version 9 will display the Enable OnePass check box in the Subclient Properties dialog box. This option is automatically selected and grayed out. To configure new subclients, see Enable Simpana OnePass for Your Subclient.

File Archiver for Celerra

Transition to Simpana OnePass Agent

This product is now available as Simpana OnePass Agent for Celerra.

Version 9 OnePass Subclients Count towards Capacity License Calculation

Starting Service Pack 6, existing OnePass subclients from version 9 will display the Enable OnePass check box in the Subclient Properties dialog box. This option is automatically selected and grayed out. To configure new subclients, see Enable Simpana OnePass for Your Subclient.

File Archiver for NetApp

Transition to Simpana OnePass Agent

This product is now available as Simpana OnePass Agent for NetApp.

Version 9 OnePass Subclients Count towards Capacity License Calculation

Starting Service Pack 6, existing OnePass subclients from version 9 will display the Enable OnePass check box in the Subclient Properties dialog box. This option is automatically selected and grayed out. To configure new subclients, see Enable Simpana OnePass for Your Subclient.

Generic File Archiver for NAS

Transition to Simpana OnePass Agent

This product is now deprecated.

File Archiver for UNIX

Transition to Simpana OnePass Agent

This product is now available as Simpana OnePass for UNIX.

Version 9 OnePass Subclients Count towards Capacity License Calculation

Starting Service Pack 6, existing OnePass subclients from version 9 will display the Enable OnePass check box in the Subclient Properties dialog box. This option is automatically selected and grayed out. To configure new subclients, see Enable Simpana OnePass for Your Subclient.

Upgrading on Solaris

While upgrading on a Solaris platform, ensure that the cxfs mount points are not busy during upgrade. If the cxfs mount points are busy, it is recommended to reboot the client computer.

If you do not wish to reboot the client computer, then follow the steps given below:

On the client computer, open the command prompt and type the following:

  1. simpana stop
  2. rem_drv cvfsf
  3. unmounts <fs>
  4. rem_drv cxhsm
  5. simpana start

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

CXFS Upgrade Tool to Convert Old Stubs

Run cxfs_upgrade tool located in the Base directory. This will upgrade the old cxfs stubs to the new stub format. Use the following command:

cxfs_upgrade -c <cache_root> -l <log_file> <fs_dir>

where:

<cache_root>  is the location of the stub cache.

<log_file> is the location of the Simpana logfile.

<fs_dir>  is name of the volume for which you want to upgrade the stubs.

When you run the archive job, the cxfs_upgrade tool will run automatically.

Stubs created by the previous version of the software will be recalled correctly even before cxfs_upgrade is run for the mountpoint. The cxfs_upgrade tool corrects the size of the stubs.

Upgrade Not Supported for Red Hat Enterprise Linux AS 4.x

Upgrade is not supported for Red Hat Enterprise Linux AS 4.x version with 2.6.x kernel

File Archiver for Windows

Transition to Simpana OnePass Agent

This product is now available as Simpana OnePass Agent for Windows.

Scan Method

After upgrading the Windows File System and Windows File Archiver agents, if you configure your subclient to use Optimized scan, the scan method automatically switches to Recursive scan.

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.

Version 9 OnePass Subclients Count towards Capacity License Calculation

Starting Service Pack 6, existing OnePass subclients from version 9 will display the Enable OnePass check box in the Subclient Properties dialog box. This option is automatically selected and grayed out. To configure new subclients, see Enable Simpana OnePass for Your Subclient.

SharePoint Archiver Agent

This product is now deprecated.

  • If you already have a client with this product installed, you can continue to use the client on an 'as is' basis.
  • New installations and upgrades for this agent are not supported in this release.

The SharePoint Archiver Agent has been deprecated in favor of a converged data management approach. All SharePoint data management, including data protection and recovery, Storage Manager, BLOB storage, and archiving solutions are now available using the SharePoint Server Agent. For more information, see Getting Started - SharePoint Server iDataAgent - Overview and SharePoint Storage Manager.

Email Archive

Exchange Mailbox Archiver

Transition to Simpana OnePass

This product is now available as Simpana OnePass for Exchange Mailbox.

  • Exchange Mailbox Archiver Agent reaches end-of-life October 2015.
  • After this agent has reached end-of-life:
    • No more changes or fixes for this agent will be supported in Simpana version 10 and earlier.
    • Only recovery jobs will be supported in future releases of Simpana, and no archive jobs will be allowed.
  • If you have Exchange Mailbox Archiver Agent installed on an existing client, we recommend that you transition to OnePass for Exchange Mailbox as described in Transitioning from Traditional Archiver to Simpana OnePass.
  • New installations of Exchange Mailbox Archiver Agent are no longer supported.

    If you plan to upgrade to the current version, see Upgrading - Exchange Mailbox Archiver Agent.

CAL (Client Access License) Replaces the Traditional License

Client Access License (CAL) is now required for protected and archived mailboxes. License consumption is based on the number of mailboxes in your system, rather than the number of clients, agents, and storage policies. This allows you to purchase licenses based on your data size.

Previously, a license was consumed for each client.

For more information, see Client Access License - FAQ - How Do I Use This License if I Have Upgraded from a Previous Version?

Stub Recalls from Exchange WebProxy

The Exchange WebProxy Archiver agent and 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.

Domino Mailbox Archiver

Pre-Upgrade

Shut down the Domino server before starting the upgrade of Domino Mailbox Archiver agent.

Post-Upgrade

If .NET Framework is upgraded then reboot the Domino server after upgrading the Domino Mailbox Archiver agent.

Deduplication

Disk

Upgrade Related MediaAgents Simultaneously

All MediaAgents associated with a Storage Policy Copy in the 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 Database) must be upgraded.

Deduplication Database Upgrade

When you upgrade the DDB MediaAgent from version 9 to version 10, you do not need to seal the DDB. The version 10 MediaAgent uses the version 9 DDB.

Upgrade Deduplication Database MediaAgent that Has an Object Level Deduplication

The object level deduplication will be supported only for MediaAgent with Software Version 8 installed to Version 10 CommServe. If object level deduplication is configured on a deduplication storage policy, then the upgrade of the deduplication MediaAgent to Version 10 is not supported.

To upgrade DDB and MediaAgent from version 8 or 9 to version 10, which has object level deduplication configured, see DDB and MediaAgent Upgrade from Previous Version.

Location or MediaAgent of the Deduplication Database

The location or MediaAgent of the DDB cannot be changed when MediaAgent hosting the deduplication database is in previous software version and CommServe is upgraded to version 10.

To change the MediaAgent or location of the DDB, upgrade the MediaAgent.

Deduplication Ratio on UNIX Clients May Be Higher after the Upgrade

If you had disabled the Optimize Concurrent LAN Backups option for UNIX Client, the first backup after the upgrade may display lower deduplication ratio and a large data transfer rate.

This is because ALL the data will be backed up in first backup after upgrade due to deduplication enhancements for UNIX clients.

Managed Disk Space Option is Disabled after the Upgrade

Enable Managed Disk Space for Disk Library checkbox is not selected for new deduplicated storage policies. If an existing deduplication copy (for CommServe updated with service pack 8B) has this option enabled, then while updating and saving the deduplication copy, you will be asked to manually disable this option. This option will not be changed automatically for any existing deduplication copy. Disabling this option helps in faster pruning of the aged data in order to reclaim space on the disk.

For step-by-step instructions to select Enable Managed Disk Space for Disk Library checkbox, click here.

Source

Source Side Deduplication Cannot be Associate with Partitioned DDB Storage Policy

When CommServe is in Version 10, the previous version clients with Client Side Deduplication on Client Computer Properties cannot be re-associated to Partitioned DDB storage policy for backups.

Upgrade your clients to current software version to associate to Partitioned DDB storage policy for backups.

or,

Disable the Client Side Deduplication from Client Computer Properties or use Storage Policy without Partitioned DDB for backups.

Virtualization

VMware

Pre-Upgrade

ESX Server Instance Cannot Be Upgraded

You cannot upgrade the Virtual Server iDataAgent if you have configured an instance for an ESX server using Version 9 Virtual Server iDataAgent. Before upgrading the Virtual Server iDataAgent, change the instance type.  For each ESX server, change the instance type from an ESX server to a vCenter instance, identifying the ESX server or the vCenter that manages ESX servers for the instance:

  1. From the CommCell Browser, go to Client Computers | <ClientName> | Virtual Server.
  2. Right-click the instance under Virtual Server and select Properties
  3. Under Vendor Type, VMware is selected. Select vCenter and provide the vCenter host name.
  4. Click Change to enter the user credentials.
  5. Click OK on each of the dialogs to save the changed settings.

After changing the instance type, you can upgrade the Virtual Server iDataAgent.

Proxies in Master Configuration Must Be Upgraded Simultaneously

All the proxies in the Master configuration and the master proxy must be upgraded simultaneously. If any proxy is not upgraded, the scheduled backup jobs may fail.

Upgrade the Proxy Used for Movement to Media Operation

During the IntelliSnap operation, you can use a separate proxy for movement to media operation. When you upgrade any such proxy, ensure that the proxy which is used for the IntelliSnap backup is upgraded.

For more information refer to Using Separate Proxy for Backup Copy and IntelliSnap Configuration.

Backward Compatibility Issues

  • You can view detailed status of each virtual machine included in the backup in the Backup Job Summary report. If the CommServe is in the current version and client is in the previous version, for File Level and Volume Level regular backups, the Backup Job Summary report displays N/A in the VM Size and CBT Status columns.
  • If the CommServe is in the current version and client is in the previous version, if you perform the Inline backup copy operation, the backup copy operation will be performed after the completion of IntelliSnap backup job.
  • If client is in the previous version, and you want to use a separate proxy for the backup copy during IntelliSnap operation, it is recommended to use the MediaAgent with the previous version. If you are using a MediaAgent with current version and the Dell Equallogic storage array, you may not be able to browse and restore the files from the backup copy.
  • If the CommServe is in the current version and client is in the previous version, you must configure the automatic discovery of virtual machines at the backup set level and not at the subclient level.

Reboot Required before Upgrading the Client if You Have Uninstalled and Re-Installed the Virtual Server iDataAgent

If  you have uninstalled the Version 9 Virtual Server iDataAgent and re-installed it on a client, you must reboot the client before upgrading it to Version 10. If you do not reboot the client, vStorage services do not start automatically and the upgrade job fails.

Accurate Calculation of Capacity License Usage Requires Version 9 Clients to Be Upgraded

Service Pack 5 introduced capacity licensing based on guest VM size. To ensure that the capacity licensing details are accurate, you must upgrade Simpana® Version 9 virtualization clients to Version 10. After the upgrade, make sure to run full backup jobs (not synthetic full).

Post-Upgrade

File Level and Volume Level Backups are Converted to Disk Level Backups

If you have configured file level and volume level backups using the Version 9 Virtual Server iDataAgent, those backups are converted to disk level backups for all subclients after the upgrade.

After the upgrade, consider the following:

  • You cannot restore VMDK files from the old volume level backups. Restore any needed VMDK files before the upgrade, and perform a new backup after the upgrade.
  • You can restore guest files and folders from the old volume level and file level backups by browsing to the older backup and restoring the data. For more information, refer to Restoring Files and Folders and Browse and Restore Data before a Specified Backup Time.
  • If you have scheduled any restores, the restore jobs fail after the upgrade. Remove the schedule, then recreate it as part of a new restore job. To remove a schedule:
    1. From the CommCell Browser, go to Client Computers | <ClientName> | Virtual Server.
    2. Right-click an instance under Virtual Server and select View | Schedules.
    3. Right-click the schedule and select Delete.
    4. Confirm the deletion. The schedule is removed.

Re-Register the VM File Recovery Plugin after Upgrading Web Server and Web Console

You must re-register the Plugin when you upgrade the Web Server and Web Console. When you upgrade web server and web console, port 80 will be set for Tomcat services and port 81 will be used for web console. The web console URL will set to port 82.

When you un-register and re-register the VM File Recovery Plugin using CommCell console, the vCenter will automatically register with new URL for web console. Before re-registering the plugin, ensure that the client has latest version of Virtual Server iDataAgent.

For more information, refer to Unregistering and Re-registering the Plug-In

Move from BIOS UUIDs to Instance UUIDs to Eliminate Duplicate ID Issues

If you experience duplicate client issues after an upgrade, you can create and configure a virtualization client and run a full backup to begin a new backup cycle.

For more information, see Virtual machine client names are created with '_1' appended to the original client name.

Continuing Incremental Backups after an Upgrade

To ensure that incremental backups are maintained after an upgrade, run an incremental job on the primary proxy before adding additional proxies for teaming. This ensures that any CRC or CHGID files are uploaded to the index cache and available for other proxies. Otherwise some virtual machines may be converted to full backups if the first backup is handled by another proxy. For more information see Incremental Backups.

Add New vCenter User Permissions

After upgrading a Virtual Server Agent to Simpana® V10, ensure that the following permissions are added:

Function Category Permissions
Backup Virtual machine – Configuration Set annotation
Restore Virtual machine - Guest Operations Guest Operation Modifications

Guest Operation Program Execution

Guest Operation Queries

VM Lifecycle Management Virtual machine – Configuration Display connection settings

Set annotation

For more information, see Permissions for Custom User Accounts (VMware) or Permissions for Custom User Accounts (IntelliSnap for VMware).

Microsoft Hyper-V

Upgrade for Hyper-V hosts Configured for Failover Clusters

If Hyper-V hosts are configured for failover clusters, after upgrading a client you can continue to use individual nodes to back up virtual machines. If you want to use multiple nodes to back up virtual machines, you can add the nodes to the upgraded client. Configure a new virtualization client with exactly the same content as that of the upgraded client.

On the newly created virtualization client, job history is lost and you cannot view the backup history and backed up content from the previous version; but you can still view backup history on older client nodes.

How Upgrade Handles the “Do Not Backup” Client

The Version 9 “Do Not Backup” client is not supported in Version 10; subclients do not act as filters against other subclients. The only exception is the “unprotected VMs” option for the default subclient. In Version 10, any content that was listed in the “Do Not Backup” subclient is applied as a filter to each upgraded subclient.

Moving a Standalone Host to a Hyper-V Cluster

For Hyper-V, a Version 9 standalone host is still a standalone host in Version 10. To create a Hyper-V cluster, you can add a virtualization client with two or more host nodes.

Accurate Calculation of Capacity License Usage Requires Version 9 Clients to be Upgraded

Service Pack 5 introduced capacity licensing based on guest VM size. To ensure that the capacity licensing details are accurate, you must upgrade Simpana® Version 9 virtualization clients to Version 10. After the upgrade, make sure to run full backup jobs (not synthetic full).

Xen

Upgrading the Virtual Server Agent for Xen from Simpana® Version 9 to Version 10, or uninstalling a Version 9 VSA and installing Version 10, is not supported.

To use Version 10, you must install the VSA on a new VM to create a new proxy, and configure new subclients to provide protection for VMs.  

If you already have a client with the Version 9 Xen Virtual Server Agent installed, you can continue to use the client on an "as is" basis with a Version 10 CommServe system.

Snapshots

VMware and Exchange Mailbox

Upgrade Virtual Server iDataAgent before Performing a Snap Mining Job

Before performing a Snap Mining job, consider the following:

  • If you are upgrading the Exchange Mailbox iDataAgent on a virtual machine, you must upgrade the Virtual Server iDataAgent on the Proxy computer, which is used to perform the IntelliSnap backup of the virtual machine.
  • When you upgrade the Exchange Mailbox iDataAgent and Virtual Server iDataAgent, the next Exchange Mining backup will automatically convert to Full backup.

Search

Content Indexing and Search

Pre-Upgrade Considerations

  • Content Indexing and Search Engine in the current release is powered by SOLR. This engine is not compatible with the content indexing engines used in the previous releases.

  • Search engine licensing is now usage based. Hence, when you upgrade from the previous version of the content indexing engine to current version of search engine, the existing licenses will be automatically converted to usage based license. The license issued as part of upgrade will have an available document count based on your current licenses.

Refer to Upgrading from a Previous Version to plan your upgrade.

CAL (Client Access License) Replaces the Traditional License

The Client Access License (CAL) is now required for content indexing. License consumption is based on the number of documents that are content indexed, rather than the number of clients that are enabled for content indexing. This allows you to purchase licenses based on your data size.

Previously, a license was consumed on each client on which content indexing was enabled.

For more information, see Client Access License - FAQ - How Do I Use This License if I Have Upgraded from a Previous Version?

Online Content Indexing

Upgrade - Merged Product

The functionality of this product is now available in Offline Content Indexing. We recommend that you transition to Offline Content Indexing by backing up all your data with minimum retention.

New installations and upgrades are not supported in this release.

Reports

Scheduled Primary Storage (SRM) Reports Generate Incorrectly

Primary Storage (SRM) Reports that were scheduled in the previous version generate the wrong report once the CommServe is upgraded to the current release.

SRM Components are Deprecated

If SRM Components are installed, review the Upgrade - SRM Components page before you upgrade.

Custom Reports Must Be Modified after Upgrade

Custom Reports that were created in the previous version generate without charts. You must reset your chart selections on the reports that upgraded. For instructions, see Custom Reporting.

Laptops

Scheduling Backups

For Laptop clients (Windows, Macintosh and Linux), Administrator can schedule a backup job based on the modifications in the subclient content.

If you have clients with mixed version, consider the following when you schedule backup based on content modification:

  • For Version 10 clients, the backup will trigger automatically based on the content modification.
  • For Version 9 clients, the backup will trigger automatically based on the specified minimum interval between the two backup jobs.

Replication

ContinuousDataReplicator

QSnap Support

If the CommServe is in the current version and the client is in the previous version, QSnap cannot be used as a snap engine for CDR on UNIX. LVM will always be used as a snap engine.

Adding a Replication Pair

Optimized Sync is not enabled by default after upgrade. To include the new/modified files which do not match the destination files, select Include files that do not match with destination copy option. For step-by-step instructions, see Add a Replication Pair.

Miscellaneous

CommNet Server

CommNet Server and CommNet Browser are deprecated. This product is now available as Enterprise Metrics Reporting Server and Cloud Metrics Reporting Server.

If you have an existing version of CommNet Server and/or CommNet Browser installed, we recommend that you transition to Metrics Reporting Server, as explained in Transition from CommNet to Metrics Reporting Server.

EDC

EDC for NetApp Snap Manager is Deprecated - Upgrade is Not Supported

EDC for NetApp Snap Manager is deprecated.

If you have clients with these components, make sure to uninstall them before upgrading the client to the current version.

See End-of-Life, Deprecated and Extended Support for more information.