Uninstalling Components

Topics | How To | Troubleshoot | Related Topics

Overview

Uninstalling Windows Components

Uninstalling NetWare Components

Uninstalling Unix and Macintosh Components

Uninstalling Components from a Cluster

Component-Specific Considerations

• Uninstalling the CommServe
• Uninstalling the MediaAgent
• Uninstalling Media Explorer
• Uninstalling Backup and Recovery Agents
• Uninstalling NAS Components
• Uninstalling SAN Agents
• Uninstalling Archive Management Agents
• Uninstalling ContinuousDataReplicator
• Uninstalling SRM Components

Uninstalling the Data Classification Enabler

Uninstalling the Content Indexing Engine

Uninstalling the MSI Package Using SMS - Lotus Notes Client Add-In

Overview

Once you have uninstalled a component, you will no longer be able to perform data protection operations. The protected data, however, is still available on the media for the length of time expressed in the Retention Time defined in the associated Storage Policy Copy. If desired, you can browse the backup data from another active client within the same CommCell or perform data recovery operations from the component to another active client within the same CommCell.

You cannot, however, restore the data to the component's original host computer because the necessary software is no longer present. You will have to reinstall the component software to the original computer in order to perform data recovery operations on such data. See Reinstalling Uninstalled Agents for more information.

If you want to browse backup data from a client computer whose component software has been removed, simply follow the standard browse procedures. (See Browse Data for more information.)

Once you have uninstalled the component software, the corresponding icon in the CommCell Browser will appear dimmed as depicted in the CommCell Browser image on the right. While this icon exists, most components can still perform data recovery operations. If you delete this icon, all of the component's data is irretrievably lost.

General Uninstall Considerations

Removing a component is a two-phase process:

• First, you need to uninstall the component software from the client computer hosting the software.
  • If you are unable to uninstall the component from a computer using the recommended procedures, you can use the Deconfigure Agents feature to release the license and clean up entries from the CommServe database. However, files and registry entries relating to the component will not be removed from its host computer.
• Next, you must delete the component icon from the CommCell Browser.
  • Once you decide that you wont need to browse and/or restore the data after an uninstall or deconfigure, you can manually delete the component from the CommCell Browser. Doing so invalidates the corresponding backup data which may also release backup media to the system. See Delete the Agent for step-by-step instructions.

Consider the following prior to uninstalling any component:

• Verify that the CommServe is running (except when uninstalling the CommServe software).

• Verify that no jobs are in progress or scheduled to occur while the software is being uninstalled. If jobs are scheduled, either perform the uninstall at another time or disable the jobs on the client computer using the CommCell Console.

• Verify that the CommCell Console and Service Control Manager window are closed.

• If components were not installed in the default location, you will have to manually delete the directory/folders once the uninstall is complete.

• When uninstalling software, you may need to remove additional components and drivers if any had been installed.
• If the Authentication for Agent Installs feature has been enabled on the CommCell, users must have Agent Management capabilities to uninstall agents. During the uninstall, users will be prompted for their account information to continue with the uninstall. If the user is not authorized, the uninstall process will abort. For more information, see Authentication for Agent Installs.
• If uninstalling a component from the command line using an uninstall shortcut in the <software_installation_directory>\Uninstall folder, the command should not be run with the <software_installation_directory>\Uninstall folder open in the command. Instead, the command should be run with the uninstall package included in the command.

  For example, the correct command would appear as follows:

  <software_installation_directory>\Uninstall\<uninstall_package>

Uninstalling Windows Components

You can uninstall Windows components as you would any other applications by using the Add/Remove Programs utility in the Windows Control Panel. (To uninstall an application in Windows Vista, click Uninstall a Program under Programs in the Control Panel.)

Uninstall Sequence

The following sequence is recommended when uninstalling components from a Windows computer:

1. Uninstall all application components
2. Uninstall the File System iDataAgent (if installed)/SRM Windows File System Agent (see Uninstalling the Windows File System iDataAgent for more information)
3. Uninstall the MediaAgent (if one exists)
4. Uninstall the CommCell Console (if one exists)
5. Uninstall the CommServe
6. Uninstall the Base software

Components on Windows

The following table lists all the Windows components and their corresponding title within the Control Panel's Add/Remove Programs utility.

Uninstalling NetWare Components

You can uninstall NetWare components by inserting the component software installation disc for the Windows platform into the Novell client computer disc drive, or by mapping the disc drive running the component software on another computer.

The following NetWare components may be removed using the uninstall procedure:

• NetWare File System iDataAgent software
• NetWare MediaAgent software
• NDS iDataAgent software
• Novell GroupWise iDataAgent software
• File Archiver for NetWare Agent software

Uninstalling the OES File System iDataAgent

You can uninstall the OES File System iDataAgent as you would any other Unix component. See Uninstalling Unix and Macintosh Components below for more information.

Uninstalling Unix and Macintosh Components

You can uninstall Unix components by using the cvpkgrm utility.

Uninstall Sequence

When uninstalling a component on a Unix or Macintosh computer, the following sequence must be used:

1. Uninstall all application components and updates.
2. Uninstall the File System iDataAgent/SRM Unix File System Agent (Unix and Macintosh)
3. Uninstall the MediaAgent (if one exists)
4. Uninstall the Base software

Since the component software depends upon the Base software, you must uninstall the component software first.

Components on Unix

The following table lists all the Unix components and their corresponding titles within the uninstall program's selection menu:

Uninstalling Components from a Cluster

The following sections provide general guidelines for uninstalling components from a Windows, NetWare, or Unix cluster.

All Clusters

• Verify that the cluster is set to its original state (i.e., the active and passive nodes are in the same state of ownership for their disk groups as they were during installation).

• If the computer from which the component has been uninstalled is rebooted, services will not be restarted following the reboot. However, any cluster plug-ins available will continue to run.

Windows Clusters

• The software for a virtual server must be uninstalled from each computer in the cluster configured to host that virtual server, on which the software had been installed.
• For uninstalling a MediaAgent or Client from a cluster virtual server, it is recommended that users uninstall the active node first and then continue and uninstall all passive nodes. This will ensure that GxClusterPlugIn resources are removed properly.

• For a CommServe in a clustered environment, it is possible to remove the CommServe software from just one node of the cluster, while allowing it to continue to function on the remaining node(s). To do so, you must ensure the computer from which you are uninstalling the CommServe is a passive node. If you uninstall the CommServe from an active node, this will cause it to stop functioning because this will also remove the database.
• When you have more than one CommServe installed in a cluster and if you uninstall one of the CommServes from any of the nodes, leaving behind other installations, you need to re-register the DM2FastWebquery.dll using the following command line utility on the node where the CommServe was uninstalled:

  <software installation path>\Base\CVGACUtil.exe /i /s DM2FastWebquery.dll

NetWare Clusters

• All virtual servers in a cluster must be uninstalled before any physical server in the cluster can be uninstalled.
• Verify that at least four network drives are available in the Novell Client computer from which the MediaAgent is installed.
• Deconfigure the libraries and drives before uninstalling the NetWare MediaAgent. For information on deconfiguring libraries and drives, see Deconfiguring Libraries and Drives.
• If uninstalling the OES File System iDataAgent , all components on the virtual servers must be uninstalled prior to uninstalling any components from the physical server.

Unix Clusters

• Clustered environments pertain only to HP-UX, Linux, and Solaris clients.
• You will need to deconfigure the Unix File System iDataAgent from each virtual machine first before uninstalling it from the physical nodes.
• You will then need to uninstall the Unix File System iDataAgent and Base software (cvpkgrm) from the client computer hosting the software. You can uninstall the Base software from your client computer by entering the cvpkgrm command from a command line and then completing the directives in the resulting script. This script deletes the appropriate files and executables, and it removes the registry entries from the system.
• The component software allows you to Deconfigure virtual machines completely. It also allows you to Deconfigure individual modules for the virtual machines.

  To Deconfigure a virtual machine, the virtual machine must be Deconfigured from all of the physical machines (hosts) on which it has been configured. This means that, within a clustered environment, each virtual machine must be Deconfigured from at least two hosts. To do this, follow the sequence outlined in Components on Unix.

Component-Specific Considerations

The following sections provide additional steps and considerations for uninstalling specific components from the computer.

If you are uninstalling a component in a clustered environment, see Uninstalling Components from a Cluster for additional cluster-specific considerations.

Uninstalling the CommServe

Consider the following prior to uninstalling the CommServe:

• Removing the CommServe stops the entire CommCell from functioning. Do not remove the CommServe software unless you wish to remove the entire data management system. Once you remove the CommServe software, the system can no longer provide services for data protection operations.
• In order to completely remove the CommServe software from the computer, the Base package must be uninstalled after the CommServe software has been uninstalled.

  Note that the Base package cannot be uninstalled if the CommServe software remains installed on the computer.

• The CommServe software can only be removed by a user that is a member of the local Administrators group.
• If you have configured your CommServe and MediaAgent for firewall support, make sure you deconfigure ports you have designated for firewall use.
• Make sure that you have uninstalled any remotely installed MediaAgents, agents, or client computers prior to removing the CommServe.
• Close any open user connection to the CommServe database through either SQL Analyzer, Enterprise Manager, isql, osql, or any other. The CommServe Uninstaller may not be able to delete the CommServe database.

Uninstalling the MediaAgent

The MediaAgent uninstall software performs the following tasks:

• Cleans up all the information about the MediaAgent in the CommServe database.
• Deconfigure the libraries and drives.
• Releases the license associated with the following: MediaAgent Libraries or stand-alone drives attached to the MediaAgent
• Remove the files and registry entries from the computer hosting the MediaAgent.

Consider the following prior to uninstalling the MediaAgent software:

• Verify that the CommServe computer is accessible and all services on the CommServe and the MediaAgent in which you wish to perform the uninstall are running.
• Ensure that you remove the NDMP Remote Server software, if the software has been installed along with the MediaAgent.
• If you have a QR Policy configured using the specific MediaAgent, deconfigure the QR Policy before uninstalling the MediaAgent.
• If you are unable to uninstall a MediaAgent using the recommended procedure, you can use the Deconfigure feature to release the license and clean up entries from the CommServe database. However, the files and registry entries relating to the MediaAgent will not be removed from its host computer.
• If you are uninstalling a Solaris MediaAgent from a Unix machine, you must first remove the WA SCSI Driver. To do this, remove the CVGxWA package first before you uninstall the MediaAgent.

Uninstalling Media Explorer

Consider the following when uninstalling Media Explorer:

• For uninstalls from a NetWare or Unix computer, ensure that you run the correct command from the appropriate resource pack.
• Have Media Information reports at hand to help you identify media archive files.
• Ensure that no other applications or services are attempting to access the library.
• Stop services if they are running.
  • For Media Explorer on Unix, use command ps -ef|grep ga to check services.

Uninstalling Backup and Recovery Agents

Consider the following prior to uninstalling a Backup and Recovery Agent:

Uninstalling the Windows File System iDataAgent

Most Windows components are dependent on the Windows File System iDataAgent and must be uninstalled prior to uninstalling the File System iDataAgent.

The following components are not dependent of the File System iDataAgent and can be uninstalled independent of it:

• CommServe
• CommCell Console
• MediaAgent
• File Archiver for Windows Agent
• File Archiver for Unix Agent
• Exchange Compliance Archiver Agent
• Exchange Mailbox Archiver Agent
• Exchange Public Folder Archiver Agent
• Domino Mailbox Archiver Agent
• SharePoint Archiver Agent
• Data Classification Enabler
• QuickRecovery Agent
• ContinuousDataReplicator
• 1-Touch for Windows
• Workstation Backup Agent
• SRM Components

Uninstalling the Virtual Server iDataAgent

If uninstalling the Virtual Server iDataAgent from a Windows Server 2008 Core Edition cluster, perform the following steps:

1. Using the command prompt, navigate to the Base folder.
2. Execute the following command:

   "<base_folder_location>\QUnInstaller.exe" VirtualServerAgent /CalledFromARPChange

3. Select the cluster group to be removed.

The Virtual Server iDataAgent is uninstalled from the selected cluster.

Uninstalling the Workstation Backup Agent

Consider the following prior to uninstalling the Workstation Backup Agent:

• Delete the replication set before uninstalling the agent.

Uninstalling NAS Components

NAS components are installed automatically with the MediaAgent software. Individual NAS clients must be deconfigured from the MediaAgent computer prior to uninstalling the File System iDataAgent or MediaAgent software.

The following sequence must be used when uninstalling NAS components:

1. Deconfigure all NAS clients
2. Uninstall any application components that may be installed
3. Uninstall any application Agents or iDataAgents that may be installed
4. Uninstall the File System iDataAgent (if installed)
5. Uninstall the MediaAgent

Consider the following prior to uninstalling NAS components:

• Ensure that all NAS clients have been deconfigured, or, for NAS NDMP iDataAgents, that they are using storage policies for either NAS attached libraries or for NRS attached libraries on another MediaAgent than this one. For more information on deconfiguring a NAS client, see Deconfiguring Agents.
• You cannot uninstall a Windows File System iDataAgent from a MediaAgent if the MediaAgent is in the Data Path of a Storage Policy associated with NAS NDMP subclients.

Uninstalling SAN Components

SAN components consist of the Image Level iDataAgent, Image Level ProxyHost iDataAgent, ProxyHost iDataAgent, Quick Recovery Agent, Recovery Director, and QSnap.

When SAN components are installed, additional drivers and enablers may be automatically installed as well. When uninstalling, the following sequence must be used for any components that had been installed:

1. Uninstall Recovery Director (if installed)
2. Uninstall Enablers (SnapView, VSS, etc.)
3. Uninstall the Agent or iDataAgent
4. Uninstall QSnap
5. Uninstall File System iDataAgent

Uninstalling the Quick Recovery Agent

Consider the following prior to uninstalling the Quick Recovery Agent:

• Once you uninstall the Quick Recovery Agent software, the system can no longer recover the Quick Recovery volumes you have created for that client. Re-install the Agent if you want to recover these previously created volumes.

• Recovery Points are not automatically deleted from the database or the Registry when you uninstall the Quick Recovery Agent software.

  If you have created Recovery Points and they still exist when you uninstall the Quick Recovery Agent, the Quick Recovery Agent software uninstall will succeed, but you will need to manually remove the Recovery Points from the database by deleting the Quick Recovery Agent icon (and its associated data) from the Browser window. However, the accompanying Snapshots will still remain in the Registry.

  To work around this issue, you can:

  • Manually delete the Recovery Points from the Browser window prior to uninstalling the Quick Recovery Agent, and then delete the Quick Recovery Agent icon from the Browser window after the Quick Recovery Agent has been uninstalled.

    OR

  • Uninstall QSnap after uninstalling the Quick Recovery Agent.

Removing QSnap Drivers Manually from Windows Computers

If manually removing a SAN component instead of using the Add/Remove Programs utility in the Windows Control Panel or the cvpkgrm utility in Unix, the QSnap driver must be manually removed as well. Failure to do so will result in a system crash when the computer is rebooted.

Note that for Image Level ProxyHost to function, QSnap, the Image Level iDataAgent, and File System iDataAgent are needed.

See Remove QSnap Drivers Manually from Windows Computers for step-by-step instructions.

Removing QSnap Drivers Manually from Unix Computers

If manually removing a SAN component instead of using the the cvpkgrm utility in Unix, the QSnap driver must be manually removed as well. Failure to do so will result in a system crash when the computer is rebooted.

Note that for Image Level ProxyHost to function, QSnap, the Image Level iDataAgent, and File System iDataAgent are needed.

See Remove QSnap Drivers Manually from Unix Computers for step-by-step instructions.

Uninstalling Archive Management Agents

Consider the following prior to uninstalling an Archive Management Agent:

Exchange Archiver Agents

• Before uninstalling the Exchange Migration Archiver Agents or Outlook Add-In, verify that the Microsoft Outlook application window is closed. In the event that an Outlook Add-In session is still active during uninstall of the Exchange Migration Archiver Agent, the Outlook Add-In's search capability will continue to function however no data will be recovered.
• Once you uninstall the Exchange Migration Archiver Agent software, the system can no longer provide archive and recovery operations for the client from which the Agent has been removed.
• Unlike other components, Exchange Compliance Archiver does not give a destination client to retrieve data. If this component is uninstalled, cross-machine retrieval cannot be run.

File Archiver Agents

• Before uninstalling the File Archiver for Windows Agent, keep in mind that any unrecovered stub files cannot be deleted after uninstalling the agent unless the Microsoft command-line tool to Delete File and Reparse Points (i.e., DELRP.exe) is used to delete them. Refer to www.microsoft.com for more information on the use of this tool.
• If the File Archiver for Unix software is uninstalled from a Linux computer, you must subsequently unmount and remount the affected XFS file system(s) without the DMAPI option specified.

SharePoint Archiver Agent

• After uninstalling SharePoint Archiver, two columns (i.e., Archived and CommVault Stub) are not automatically removed.  These columns are created in Document and Picture Libraries during archive operations using SharePoint Archiver. To remove these columns, use the CleanSPDA tool.

Uninstalling ContinuousDataReplicator

ContinuousDataReplicator is uninstalled from at least two computers; the server from which you replicated data (source machine) and the computer to which you replicated data (destination machine.) You may choose to perform additional uninstalls based on the Replication Scenario used in your particular environment.

Prior to uninstalling the software, it is recommended that you delete all replication sets used in your Replication Scenario before deleting the source machine and destination machine. Consider the following before deleting these components.

• Replication sets can be deleted if the replication pairs are in any of the following states:
  • Stopped
  • New Pair
• Deleting the source machine will remove job history from that machine.

See Delete the Agent for step-by-step instructions on deleting components.

Uninstalling SRM Components

The following sequence must be used when uninstalling SRM components:

1. Uninstall any SRM Updates applied to the component(s) to be uninstalled
2. Uninstall all SRM Agents
3. Uninstall the SRM Server

Uninstall the SRM Agent

If the SRM Server is not communicating with a client when the SRM Agent software is uninstalled, the uninstall will work, but the SRM server will still think that the client exists. As a result, subsequent installs of the same SRM Agent software to this client may fail. In some cases, even if the agent install succeeds, the server would experience trouble in communicating to the client causing job failures.

This failure can be avoided by uninstalling the Client manually in the CommCell Console after the SRM Agent software has been uninstalled. For step-by-step instructions, see Delete a Client Computer.

Uninstalling the Data Classification Enabler

• If your computer has both the Data Classification Enabler and Online Content Indexing installed, you will not be able to uninstall the Data Classification Enabler until you first uninstall Online Content Indexing. Therefore, in such cases, be sure to uninstall Online Content Indexing before you uninstall the Data Classification Enabler.
• After you uninstall the Data Classification Enabler on Windows, the items for the enabler (e.g., DataClassSet) are not automatically displayed as uninstalled in the CommCell Browser. To display these items as uninstalled in the CommCell Browser, you must restart the Bull Calypso Communication Services (GxCVD).
• For the Unix File System iDataAgents, uninstalling the Data Classification Enabler from a Unix client does not disable the Use Data Classification option within the Backup Set Properties dialog box. Similarly, for the File Archiver for Unix agents, uninstalling the enabler does not disable the DataClassSet archive set.
• When you are uninstalling Data Classification on Windows, the following message will be displayed:

  Setup failed to uninstall Windows .NET Service ‘DM2Server.exe’.

  Ignore this message and click OK to continue the uninstall.

Uninstalling the Content Indexing Engine

After uninstalling the Content Indexing Engine software, delete the specific Content indexing Engine from the CommCell Console from Storage Resources | Content Indexing Engines | <uninstalled content indexing engine name>.

Uninstalling the MSI Package Using SMS - Lotus Notes Client Add-In

To uninstall the Lotus Notes Client Add-In set up a batch file that contains the following uninstall command and then run it as a scheduled task on remote Lotus Notes clients:

msiexec.exe /x {ProductCode_GUID} /qn /L*v "%TEMP%\LotusNotes_DM_Client_Uninstall.log"

To locate the ProductCode GUID, navigate to the following location:

[SOFTWARE\Calypso\Galaxy\Instance001\InstalledPackages\LotusNotesDMCleint]

Note that the /L*v "%TEMP%\LotusNotes_DM_Client_Uninstall.log" portion of the above command line is optional and is only used for generating a detailed log file of the uninstallation process.

In the event that the uninstallation process does not complete successfully, add the following to the end of the above command, to bypass QUninstaller.exe, which may leave unused registry entries under "HKEY_LOCAL_MACHINE\SOFTWARE\CommVault Systems\...":

EXECUTEGALAXYUNINSTALLER="FALSE"

Back to Top