Install Considerations

Pre-Install

Post-Install

Network

If your CommServe^® computer has multiple Network Interface Cards and IP addresses, make certain that all network communication paths are working. Also, make sure that the network interface to be used in the CommServe installation is set as the first one to be bound to the network. For more information on Network Interface Cards, see the Network Requirements.

Terminal Services

When installing CommCell^® components using Terminal Services, you must specify a UNC path to the installer. When using a UNC path to install the CommServe software, SQL must already be installed and the database instance must already be configured.

General

• If you have a permanent license, open the CommCell Console and apply the license. See Update License for step-by-step instructions.

• After installing the CommServe^® or MediaAgent software, it will be listed as a client computer in the host computer's CommCell Browser. The alert icon preceding the CommServe or MediaAgent client computer in the CommCell Console indicates that agent software must be installed on that computer for it to be utilized as a client.

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

Database Engine

• Microsoft SQL Server 2008 Enterprise Edition (with Service Pack 1) will be automatically installed while installing the software. Later versions of the Service Pack, if available, are also supported.

  If necessary, download and install the latest version of the Microsoft SQL Server service pack and/or post-release updates after an install or upgrade.

• After installing the CommServe^® software, the database instance requires specific SQL server settings:

  From the SQL Server Management Studio, right-click the database instance to access the instance properties. In the Memory options, the value for Maximum server memory (in MB) should be 50% of the physical memory available in the CommServe machine.

Cluster/Firewall

• <software installation path>/<software installation folder>/Base/FwHosts.txt
• <software installation path>/<software installation folder>/Base/FwPeers.txt
• <software installation path>/<software installation folder>/Base/FwPorts.txt

If for some reason the passive node is currently active, make sure to stop and restart Services after copying the files.

Pre-Install

Post-Install

gENERAL

• For devices using the iSCSI and Storport drivers make sure that the medium changer for the library is enabled in the Windows Computer Management window. For all other drivers we recommend that the media changer is disabled in the Windows Computer Management window.

  For more information on how to enable or disable the media changer, see Driver Configurations.

• The following loopback address must be present in the /etc/hosts file for all Unix clients:

  127.0.0.1     localhost

NetApp NAS File Servers

• For information on connecting the storage devices, refer to your vendor's documentation.
• After attaching the NetApp NAS file server and MediaAgent machine to the library and before you begin your installation, verify that the NDMP service is enabled in the NetApp file server.

Installing On Microsoft Virtual Server

For information on installing the MediaAgent software on the Microsoft Virtual Server, see Considerations for backing up the Microsoft Virtual Server.

General

• You must configure the libraries and drives before using the MediaAgent for data protection operations. (For more information, see Library and Drive Configuration.)

  The MediaAgent software supports various types of libraries and library configurations. See the following sections for more information:

  • Blind Libraries
  • Centera Clusters
  • Cloud Storage
  • Direct-Attached Libraries
  • Direct-Attached Shared Libraries
  • HDS Data Retention Utility (DRU)
  • IP Libraries (Like libraries attached to ACSLS Server)
  • Disk Libraries
  • NAS Libraries
  • Optical Libraries
  • PnP (Plug and Play) Disk Libraries
  • Removable Magnetic Disk Drives
  • SAN-Attached Libraries
  • Stand-Alone Drives
  • Virtual Tape Libraries

• After installing the CommServe^® or MediaAgent software, it will be listed as a client computer in the host computer's CommCell Browser. The alert icon preceding the CommServe or MediaAgent client computer in the CommCell Console indicates that agent software must be installed on that computer for it to be utilized as a client.

Pre-Install

General

• If your install requires the software to be installed on a domain controller, the install program checks your operating system for domain controller status. If your computer is not a domain controller, a message informs you of the need to abort this installation.
• The ADLDAPTool.exe must be installed on a domain controller with Flexible Single Master Operations (FSMO) roles.

User Privileges

Review the table below to identify the privileges you will require for installing the Active Directory iDataAgent.

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

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

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

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

Pre-Install

Post-Install

General

• Be sure to obtain the necessary number of DB2 iDataAgent licenses. Each DB2 iDataAgent that you install requires one license. Licenses are used as the DB2 iDataAgent is configured as described in Create an Instance. The license type can be used on any supported Windows platform.
• A reboot will be required after install/upgrade to initialize the QSnap driver, before you can use this Agent.

General

Several configuration tasks are required before you can begin using the DB2 iDataAgent for data protection operations:

• Create an Instance
• Create Backup Sets
• Enable Database Configuration Parameters for DB2 Backups

Pre-Install

Post-Install

General

Configuration

1. Configure a supported Snapshot Environment for this agent.
2. Create a New Subclient.

Cluster

For Non-Microsoft cluster, create the file <JobResults Directory>\CVClusterVolumes.txt with a list of drives in it. For example, the file can contain "D: E: F:".

Use of QSnap

Upon installation of QSnap, the QSnap block-filter is activated by default for all volumes. This means that the QSnap block filter driver automatically monitors all volumes on the server. For more information, see The Block-Filter Driver and Bitmaps on the QSnap Overview page.

Pre-Install

Post-Install

General

• While the Lotus Notes Database iDataAgent supports all logging styles (disabled, archive, circular, linear) it is strongly recommended that Archive Logging be used. For information on how to set the transaction logging style see Configuring the Lotus Domino Server for Transaction Logging.

  Logging methods should not be changed once the software has been installed. Changing logging methods after the software has been installed may result in unexpected results when data aging operations are performed.

  For overview information on transaction logging, refer to Domino Server Transaction Logs.

• The public name and address book (names.nsf) must be using the R5 or R6 template, in order for the required transaction logging settings to appear on the Server document.
• Installing the iDataAgent using Microsoft Windows Terminal Service Client is not supported. For remote access, use of a remote control software such as NetMeeting is supported.
• If you have edited the Domino servers local host file to resolve Notes port mapping issues, make sure that the network interface names that you enter during File System iDataAgent installation are recognized by the DNS server and are not just local host file entries. Check the default values before accepting them. Otherwise, the CommServe and MediaAgent may not be able to access the client using the interface names that you have entered.
• Ensure that the Domino Server ID does not have an associated password. If the Domino Server ID has a password associated with it, you must enable the option on the ID called Dont prompt for password from other Notes based programs. For more information on the subject, see Domino Server ID.

General

• Before you back up data with the Notes Document iDataAgent, create a Restore View Name for each partition configured as described in Add a Restore View Name.
• If you did not install all the partitions with your initial install, remember to add the needed partitions to the iDataAgent afterward. To add a new partition to the iDataAgent, see either Add a Lotus Domino Server Partition on Windows or Add a Lotus Notes Database Partition on Unix for more detail.
• Schedule appropriate backups for the default and transaction log subclients based upon server activity and business requirements:
  • For default and user-defined subclients schedule incrementals based upon how often new databases are added to the Domino server.
  • For the transaction log subclient, create schedules based upon the volume of data that is changed or added. For more information on transaction logging, see Domino Server Transaction Logs.

Pre-Install

Post-Install

General

• If the SharePoint Server iDataAgent is installed on the same machine as Microsoft Office SharePoint Portal Server 2003, all servers in the server farm will be upgraded to Microsoft .NET Framework version 2.0.
• The SharePoint Server iDataAgent should be installed only on a Front End Web Server. If the farm contains more than one Front End Web Server, then the SharePoint Server iDataAgent must be installed on all of them.
• The configuration and topology of any server farm must be one that is supported by SharePoint Server.
• In a SharePoint server farm (i.e., where SQL Server runs on a remote machine), the SQL Server iDataAgent must be installed on the SQL Server machine.
• If the Single Sign-on Service is configured in the SharePoint server farm then the SharePoint Server iDataAgent can be installed on the job server.

General

• In a SharePoint environment with more than 500 site collections, it is recommended to increase the size and number of log files with the <logfile>_MaxLogFileSize  and <logfile>_MaxLogFileBackups registry keys. Replace <logfile> with any desired name (e.g., SPDBBackup, SPDocBackup, SPDocArchive, etc.).

• For SharePoint Server iDataAgent backups using database backup sets in an all-in-one configuration, install the software with either 32 or 64-bit Microsoft SQL Server 2005 Management Objects Collection or SQL Server 2008 Shared Management Objects.

  If you have installed the 32-bit SQL Server 2008 Shared Management Objects on a 64-bit client, then you may see this error: Could not load file or assembly "Microsoft.SqlServer.BatchParser, Version=10.0.0.0".

Silent/ Decoupled Installation

After completing a silent or decoupled installation of a SharePoint Agent, you must manually enter a SharePoint Server Name and SharePoint Administrator Account in the Agent's Properties dialog box. For step-by-step instructions on accounts, see Change Account for Accessing Application Servers/Filers.

SharePoint Server

• If the SharePoint Server is configured to use the Single Sign-on Service, then the administrator account for this service must be entered in the SharePoint Server iDataAgent properties before any backups are run. Perform the following steps:
  1. From the CommCell Console, right-click the SharePoint Server iDataAgent, and select Properties.
  2. In the iDataAgent Properties, click the Change Account button for the SSO Account, and enter the Single Sign-on Account name and password.
• The following information is not backed up by the system, and must be recorded for use in the event a Full System Restore is required:
  • E-Mail Server Settings
  • Anti-virus Settings
  • Blocked File Types
  • Logging Settings
  • HTML Viewer
  • Usage Analysis Processing
  • Shared Services (SharePoint 2003)

  Record this information and store it in a safe place, as part of your disaster recovery planning. For more information about Full System Restore, refer to Restore Data - SharePoint Server iDataAgents - Full System Restore.

• In an environment where two different versions of SharePoint Server (e.g., 2003 and 2007) co-exist on the same client with the SharePoint Server iDataAgent, an additional Database type backup set should be created to backup SharePoint Database components for other version.

SharePoint Server Farms

• For SharePoint server farms only (i.e., where SQL Server runs on a remote machine), perform the following steps.
  1. From the CommCell Console, right-click the SharePoint Server iDataAgent, and select Properties.
  2. In the General tab of the iDataAgent Properties, select SQL Databases hosted on a remote SQL Server.

  You must install the Windows and SQL iDataAgents on the remote SQL Server to protect its data; the SharePoint iDataAgent will not do so. Ensure that backups of the SharePoint Server and the remote SQL Server are scheduled to run at about the same time.

• For medium to large SharePoint Server 2003 farms, create a folder on a machine with enough disk space to temporarily store the Portal Site Index for the farm during backup and restore operations, as well as job results information, and share this folder on the network. (The Services account used by the software, the Front End Web Server, and the Portal Site Index server must all be able to access this folder.) Perform the following steps:
  1. From the CommCell Console, right-click the SharePoint Server iDataAgent, and select Properties.
  2. In the General tab of the iDataAgent Properties, in the Index Backup/Restore field, type the path to the folder you just created.

Post-Install

General

Microsoft Windows Server 2008 and Microsoft Windows Server 2008 R2 requires "csvde.exe" feature to be installed on the server to query Active Directory for mailbox information

• To install "csvde.exe" feature on Windows Server 2008 follow these steps:
  1. Open Server Manager
  2. Go to Features->Add Feature
  3. Remote Server Administration Tools
  4. Role Administration Tools
  5. Select "Active Directory Lightweight Directory Service Tools"

Outlook Add-In

• The Outlook Add-In's language default is for the Outlook Language Setting. If applicable, modify the language setting (i.e., set to OS Language Setting) through the UseOSLocale registry key.

• Before using the Outlook Add-In, ensure that the port number used by the Client Event Manager Service is properly configured. Typically, the install program configures this automatically; however, when using custom port numbers you will need to make sure that the port number configured on the Exchange Server under the nEVMGRCPORT registry key matches the port number configured on the Outlook client under registry key nEvMgrCPortNumber. This requirement also applies to multi-instance installs, in which case, you will need to locate the nEVMGRCPORT registry key under the appropriate instance on the Exchange Server. For general information on port number requirements, see Network TCP Port Requirements.

• You can configure the software to download Java updates periodically from the CommCell Console. See Configuring Java Updates for more information.
• To customize registry settings and override the installation default settings for Outlook Add-In, follow the README file instructions for the CVOutlookAddin.adm Template available in the Resource Pack.
• If the Outlook Add-In is installed from the CommCell Console, it installs base software package will be installed which allows for the CommNet Server computer to support automatic update and licensing updates through the CommCell Licensing Administration Utility.
• For Outlook Add-In, if this component is installed from the CommCell Console or from the Software Installation Disc along with any agent software, the base client will be installed along with the Outlook Add-In which allows to install automatic updates on the client computer in your CommCell.
• If Outlook Add-In is installed from the CommCell Console or from the Software Installation Disc along with any agent install, the base client gets installed along with the Outlook Add-In, which registers the client computer with the CommServe, that allows you to install the automatic updates on the client computer in your CommCell.

  If the installation is made using MSI package, the automatic updates will not be installed on the client computer.

Pre-Install

Post-Install

• For Exchange 2003

  Set Permissions for the Mail-Enabled User:

  Method One:

  Assigning permissions by using the Exchange Administration Delegation Wizard.

  1. Using the Exchange System Manager snap-in, right-click the organization object and delegate control.
  2. Using the Wizard, assign the MailboxAdmin user Exchange Full Administrator privileges.

  Now the MailboxAdmin user will be allowed full access to all mailboxes on servers in the domain.

  Method Two:

  To be used if the MailboxAdmin account is NOT the Administrator, OR a member of the Domain Admins OR Enterprise Admins groups.

  1. Using the Active Directory Users and Computers snap-in, right-click on the MailboxAdmin user and select Properties.
  2. From the Properties window, select the Member of tab.
  3. Click Add, then select Exchange Services or Exchange Domain Servers group. Click Add.
  4. Verify that the group selected is added to the list box.
  5. Click Apply and OK to close the window.

  Now the MailboxAdmin user will be allowed full access to all mailboxes on servers in the domain.

• For Exchange 2007/2010

  To Set Permissions for the Mail-Enabled User:

  1. Using the Active Directory Users and Computers snap-in, right-click on the MailboxAdmin user and select Properties.
  2. From the Properties window, select the Member of tab.
  3. Click Add, then select Exchange Organization Administrators group for Exchange Server 2007.

     For Exchange Server 2010, the group name is Organization Management.

  4. Verify that the group selected is added to the list box.
  5. Click Apply and OK to close the window.

  Now the MailboxAdmin user will be allowed full access to all mailboxes on servers in the domain.

• For Exchange 2003

  If you installed the agent in an off-host proxy configuration, OWAProxyEnabler is required to be installed on the Exchange Server in order to support Outlook Add-In functionality. To install OWAProxyEnabler, see Install the OWA Proxy Enabler.

• After install, in order to support stub recalls from OWA for Exchange 2003 Agents, run the RegisterWSSForm tool located on the Resource Pack
• For Exchange 2007

  If you installed the agent in an off-host proxy configuration, OWAProxyEnabler is required to be installed on the Client Access Role in order to support OWA Recalls. It should also be installed on Mailbox Role to support both OWA Recalls and Outlook Add-In functionality. To install OWAProxyEnabler, see Install the OWA Proxy Enabler.

• For Exchange 2010

  If you installed the agent in an off-host proxy configuration, OWAProxyEnabler is required to be installed on the Client Access Role in order to support Outlook Add-In functionality. It should also be installed on Mailbox Role to support OWA Recalls.  To install OWAProxyEnabler, see Install the OWA Proxy Enabler.

• Use sCASServerName key to identify the CAS servers during profile creation for Exchange 2010 DAG configuration and also when Exchange 2010 server does not have Client Access Role.

Post-Install

Pre-Install

Post-Install

General

If you want to use the QSnap^® service to back up locked files with the Windows File System iDataAgent, see Install QSnap - Windows for combined installation procedures instead of using the procedures below.

Cluster

• By default, a failure of MediaAgent or Agent software on the active node in a Windows, Veritas, or HP Scalable NAS/PolyServe Cluster will not cause a failover to be initiated. For information on how to change this default behavior, see Clustering Support - Failovers.
• To uninstall, start, and stop windows services on a local computer, use the instsvc utility. For more information, see List of Tools and Utilities.
• For Non-Microsoft cluster, backups of local physical node volumes from virtual nodes are not recommended. Set the virtual node default subclient content to the shared disk resource(s) instead of using auto detection (/), or create a subclient to use for backups with the shared disk resource(s).

Pre-Install

Post-Install

Shut Down Instances

• For a database Agent, you may be required or be given the option to shut down the instances/databases for the agent before or during the following procedure. See Shut Down Instances for more information.

Reboot

• A reboot will be required after install/upgrade to initialize the QSnap driver, before you can use this Agent.

• A 1-Touch Recovery is not used to recover a 1-Touch Server. Thus it is important to configure the File System iDataAgent for data protection and recovery on the 1-Touch server.
• Be sure to ensure security access for 1-Touch Server shares created on Windows XP.

  1-Touch Server shares require that the logged-on user running OneTouch.exe have read, write, execute, create, modify, and delete rights to C:\<software installation path>\SystemRecovery\ClientFiles folders.

  Confirm that the 1-Touch Server Shares created during installation have security access by using either the classic file sharing and security interface or the Simple Sharing User Interface (UI).

  Windows XP Professional uses the Simple Sharing UI. The Simple Sharing UI appears if ForceGuest is turned on; the traditional sharing and security tabs are shown if ForceGuest is turned off. By default, Simple File Sharing is turned on in Windows XP Professional computers that are joined to a workgroup.

  Windows XP Professional computers that are joined to a domain use only the classic file sharing and security interface. When you use the Simple File Sharing UI (that is located in the folder's properties), both share and file permissions are configured.

  When simple sharing is in effect, permissions are automatically set on shared files and folders. The following permissions are added when using the Simple Sharing UI:

  • Share permissions
  • File permissions
  • Allow others to change my files
  • Don't allow others to change my files

  When the Guest-only security model is used, the Sharing tab has only three options:

  • Share this folder on the network (this grants the Everyone group Read permissions on the folder and its contents)
  • Share name (i.e., the name of the share on the network)
  • Allow other users to change my files (this grants the Everyone group Full Control permissions on folders and Change permissions on files)

  To turn Simple File Sharing on or off, perform the following steps:

  • Double-click My Computer on the desktop
  • Select Tools from the menu bar
  • Select Folder Options and select the View tab
  • Select or clear the Use Simple File Sharing (Recommended) check box.

Post-Install

General

• Several configuration tasks are required before you schedule or run content indexing operations on the data. See Configuration - Content Indexing and Search page for more information.
• Once you have installed the Content Indexing Engine, you must set the user authentication to access the staging location, if the staging path is on a network path. See Configure Content Indexing Engine Options for step-step instructions.
• Once you have installed the Content Indexing Engine, you can set the following options in the CI Engine Properties dialog box from the CommCell Console to improve the performance of the content indexing operation: (In the case of multi-node installation, you can set these options for the Content Indexing Engine in the Admin node.)
• Maximum Number of Batch Slots - You can set this option to determine the maximum number of batch slots to be sent at a time to the Content Indexing Server for content indexing. By default, the value is set to 40. It is recommended to set this value to 40 times the number of nodes created (including the Admin node). For example, if you have 4 nodes created, including the Admin node, set the value to 160.

  Maximum Number of Documents Per Batch - You can set this option to determine the maximum number of documents to be included in a batch for content indexing. By default, the value is set to 1000. It is always recommended to include 100 documents in a batch.

  For step-by-step instructions on setting these options, see Configure Content Indexing Engine Options.

Pre-Install

Post-Install

Configure the Client for Java Updates During Installation

The client computer can be configured to automatically download Java updates from the CommCell Console during the software installation. To do so, create the sGUIUpdateURL registry key on each client computer prior to installing the software. This key should include the IIS web alias for the CommCell Console from which you wish to download updates. Once this key is created and the software is installed, the latest Java updates from the CommCell Console will be available on the client computer.

Note that if you choose to select a CommCell Console installed on a computer other than the CommServe computer, you must configure the CommServe computer's CommCell Console to use the alternate computer for Java updates. See Configure an Alternate Computer for Add-In Java Updates for step-by-step instructions.

Lotus Notes Client Add-In

• Once the Lotus Notes Client Add-In is installed, the Windows user accessing the Lotus Notes application must be given Full Control permission in the LotusNotesDMClient registry key.
• You can configure the software to download Java updates periodically from the CommCell Console. See Configuring Java Updates for more information.

Pre-Install

Post-Install

General

• The Oracle Database application has been installed on the client.

• For a database Agent, you may be required or be given the option to shut down the instances/databases for the agent before or during the following procedure. See Shut Down Instances for more information.
• Although the File System iDataAgent is a prerequisite, you do not have to install it separately. The Oracle iDataAgent installation program checks for the File System iDataAgent and installs it automatically if it is not installed.
• A reboot will be required after install/upgrade to initialize the QSnap driver, before you can use this Agent.

Reboot Required

A reboot will be required after installation, before you can use this Agent.

Cluster

• Prior to installing the Oracle iDataAgent in a cluster group that does not have the required cluster resource type (i.e., Oracle Failsafe) in Windows Cluster Administrator, you must use the bAllowOracleOnVmWithoutFailsafe registry key to bypass this requirement and enable the Oracle iDataAgent option on the platform selection screen for this configuration.

General

• Before you can begin using the Oracle iDataAgent for data protection operations, you must Create an Instance.
• To plan for a full system restore of the Oracle database in the event of a destroyed or damaged client, we recommend that you configure the client for disaster recovery by including the Oracle database files in your file system backups. Refer to Disaster Recovery Considerations for more information and procedures.

Pre-Install

post-install

General

For a hardware Snapshots system verify the Snapshot environment has been configured and tested.

General

• In addition to the software installation you have just completed, the Backup Host computer must have the appropriate Windows File System iDataAgent installed; for more information, refer to Deployment - Windows File System iDataAgent.
• The following configuration tasks are required before you can begin using the software for data protection operations:
  1. Configure a supported Snapshot Environment for this agent.
  2. Create a New Subclient.

Pre-Install

Post-Install

General

• For a database Agent, you may be required or be given the option to shut down the instances/databases for the agent before or during the following procedure. See Shut Down Instances for more information.
• Although the File System iDataAgent is a prerequisite, you do not have to install it separately. The SAP for Oracle iDataAgent installation program checks for the File System iDataAgent and installs it automatically if it is not installed.
• A reboot will be required after install/upgrade to initialize the QSnap driver, before you can use this Agent.

General

• Include the Directory Path for backint into the SAP for Oracle User Path.

• Before you run backups or restores, create a symbolic link file for the “backint” file
  under the install directory. For example:

  ln -s <software installation path>/iDataAgent/backint /usr/sap/CER/SYS/exe/run/backint

  Then include the /usr/sap/CER/SYS/exe/run directory path into the SAP user path.

Pre-Install

General

• For a database Agent, you may be required or be given the option to shut down the instances/databases for the agent before or during the following procedure. See Shut Down Instances for more information.
• A reboot will be required after install/upgrade to initialize the QSnap driver, before you can use this Agent.
• The MAXDB database application has been installed on the client.
• Although the File System iDataAgent is a prerequisite, you do not have to install it separately. The SAP for MAXDB iDataAgent installation program checks for the File System iDataAgent and installs it automatically if it is not installed.

PRE-Install

Post-Install

Pre-Install

Post-Install

VMware

The following utilities must be installed prior to performing any backup operations using the Virtual Server iDataAgent (these packages can be obtained from the VMware web site):

VMware Consolidated Backup (refer to the VMware customer support web site for support information for the VMware Consolidated Backup utility.)

• The Virtual Server iDataAgent supports all modes supported by the VMware Consolidated Backup utility.
• Refer to the VMware customer support web site for support information for the VMware Consolidated Backup utility.

VMware Converter (refer to the VMware customer support web site for support information for the VMware Converter utility.)

• Ensure that the guest operating systems are using the supported version of the VMware Converter.
• The vCenter Converter Standalone 4.0.1 package must be installed for Windows Vista and Windows Server 2008 environments.

In addition to the above-mentioned utilities, VDDK version 1.2.1 or higher is required. The Virtual Server iDataAgent will install this component automatically. However, if you are already running a VDDK version prior to 1.2.1, you must uninstall the VDDK package prior to installing the Virtual Server iDataAgent.

Cluster

Post-Install

General

After workstation backup agent install on Windows Vista or higher, workstation backup agent console does not start automatically because of the User Account Control (UAC). You can manually start workstation backup agent console or it will be started automatically after reboot.

Post-Install

General

• A 1-Touch Recovery is not used to recover a 1-Touch Server. Thus it is important to configure the File System iDataAgent for data protection and recovery on the 1-Touch server.
• Be sure to ensure security access for 1-Touch Server shares created on Windows XP.

  1-Touch Server shares require that the logged-on user running OneTouch.exe have read, write, execute, create, modify, and delete rights to C:\<software installation path>\SystemRecovery\ClientFiles folders.

  Confirm that the 1-Touch Server Shares created during installation have security access by using either the classic file sharing and security interface or the Simple Sharing User Interface (UI).

  Windows XP Professional uses the Simple Sharing UI. The Simple Sharing UI appears if ForceGuest is turned on; the traditional sharing and security tabs are shown if ForceGuest is turned off. By default, Simple File Sharing is turned on in Windows XP Professional computers that are joined to a workgroup.

  Windows XP Professional computers that are joined to a domain use only the classic file sharing and security interface. When you use the Simple File Sharing UI (that is located in the folder's properties), both share and file permissions are configured.

  When simple sharing is in effect, permissions are automatically set on shared files and folders. The following permissions are added when using the Simple Sharing UI:

  • Share permissions
  • File permissions
  • Allow others to change my files
  • Dont allow others to change my files

  When the Guest-only security model is used, the Sharing tab has only three options:

  • Share this folder on the network (this grants the Everyone group Read permissions on the folder and its contents)
  • Share name (i.e., the name of the share on the network)
  • Allow other users to change my files (this grants the Everyone group Full Control permissions on folders and Change permissions on files)

  To turn Simple File Sharing on or off, perform the following steps:

  • Double-click My Computer on the desktop
  • Select Tools from the menu bar
  • Select Folder Options and select the View tab
  • Select or clear the Use Simple File Sharing (Recommended) check box.

Pre-Install

Post-Install

General

• If you have edited the Domino servers local host file to resolve Notes port mapping issues, make sure that the network interface names are recognized by the DNS server and are not just local host file entries. Check the default values before accepting them. Otherwise, the CommServe and MediaAgent may not be able to access the client using the interface names that you have entered.
• Ensure that the Domino Server ID does not have an associated password. If the Domino Server ID has a password associated with it, you must enable the option on the ID called don't prompt for password from other Notes based programs. For more information on the subject, see Domino Server ID.

General

• After installing the Domino Mailbox Archiver Agent, restart the Domino Server by typing the command restart server from the Domino Server Console.

• After installing the Domino Mailbox Archiver Agent, the Lotus Notes Mailbox master template should be configured to display a stub icon for each message archived. When this configuration is performed, the Lotus Notes client mailbox will automatically display archived messages with a stub icon. Users can then recall the archived message by opening the message in the Lotus Notes client mailbox.

  See Configure Stub Icons for Lotus Notes Mailboxes for step-by-step instructions.

• Create a Subclient - see Subclients - Domino Mailbox Archiver for more information.
• The Domino Server should be up and running while performing discoveries of mail databases.
• Archiving Rules are initially disabled by default. You must clear the Disable All Rules option in the Subclient Properties (Archiving Rules) or (Rules) tab and configure the archiving rules before conducting rules-based Archive Operations.

• The Domino Mailbox Archiver Agents provides three modes which further direct how archive and recovery operations behave for each subclient. These modes can be selected using the General tab of the Subclient Properties dialog box and should be configured prior to running the first archive operation.

  See Operation Modes for more information.

Lotus Notes Client Add-In

If Lotus Notes Client Add-In is installed from the CommCell Console or from the Software Installation Disc along with any agent install, the base client gets installed along with the Lotus Notes Client Add-In, which registers the client computer with the CommServe, that allows you to install the automatic updates on the client computer in your CommCell.

If the installation is made using MSI package, the automatic updates will not be installed on the client computer.

Post-Install

General

The following configuration tasks are required before performing an Archive Operation using the Archiver Agents:

• Archiving Rules are initially disabled by default. You must clear the Disable All Rules option in the Subclient Properties (Archiving Rules) or (Rules) tab and configure the archiving rules before conducting rules-based Archive Operations.

For Exchange 2003

• If you installed the Mailbox Archiver agent in an off-host proxy configuration, OWAProxyEnabler is required to be installed on the Exchange Server in order to support Outlook Add-In functionality. To install OWAProxyEnabler, see Install the OWA Proxy Enabler.

For Exchange 2007

• If you installed the Mailbox Archiver agent in an off-host proxy configuration, OWAProxyEnabler is required to be installed on the Client Access Role in order to support OWA Recalls. It should also be installed on Mailbox Role to support both OWA Recalls and Outlook Add-In functionality. To install OWAProxyEnabler, see Install the OWA Proxy Enabler.

For Exchange 2010

• If you installed the Mailbox Archiver agent in an off-host proxy configuration, OWAProxyEnabler is required to be installed on the Client Access Role in order to support Outlook Add-In functionality. It should also be installed on Mailbox Role to support OWA Recalls.  To install OWAProxyEnabler, see Install the OWA Proxy Enabler.

• Use sCASServerName key to identify the CAS servers during profile creation for Exchange 2010 DAG configuration and also when Exchange 2010 server does not have Client Access Role.

Pre-Install

Post-Install

General

• The File Archiver client driver and File System Data Migrator agent driver cannot be installed on the same machine for the feature to work properly.

• .NET Framework 2.0 or above needs to be installed on the computer where you wish to install the File Share Archiver Client.

General

• The following configuration tasks are required before performing an Archive Operation using this Archiver Agent:

  • Create an Instance - see Agents - File Archiver - How To for more information.

  • Create a Subclient - see Subclients - File Archiver for Windows for more information.
  • Archiving Rules are initially disabled by default. You must clear the Disable All Rules option in the Subclient Properties (Archiving Rules) or (Rules) tab and configure the archiving rules before conducting rules-based Archive Operations.
  • After installing the File Archiver for Windows Agent and File Share Archiver Client (if applicable) before performing a migration archiving operation of data residing on a NAS file server,  you must configure the authentication credentials with administrator privileges to access the file server. To get more information, see Configure File Server/Proxy Authentication Credentials.
  • Before archiving data for an EMC Celerra File Server, you must configure the IIS Server if it is not installed on the same machine as the File Archiver agent. See Configure the IIS Server for Celerra Proxy Stub Subclient Support for more information.
• You can override the stub file port number by using the EVMGRC_REMOTE_PORT_OVERRIDE registry key.  Use this key when the port number changes. Keep in mind that using this key defeats the benefit of being able to recall data using different port numbers for multiple Agents.

Cluster

• If the passive node was not available while installing the software, you must manually install the software on the passive node now. (See Manually Installing the Software on a Passive Node for step-by-step instructions.)
• By default, a failure of MediaAgent or Agent software on the active node in a Windows, Veritas, or HP Scalable NAS/PolyServe Cluster will not cause a failover to be initiated. For information on how to change this default behavior, see Clustering Support - Failovers.
• After the installation of software is complete for all the physical nodes and for the cluster server, stop and restart Services on all the physical nodes before you begin using the File Archiver for Windows Agent in the cluster group for migration archiving. For more information about how to do this, see Services - How To.
• For FPolicy Instance configuration for File Archiver for Windows Agent in clustered environment the driver for the File Archiver for Windows Agent must be installed only on the physical nodes of the cluster and then the File Archiver for Windows Agent should be installed on all the nodes (physical and virtual).

  See Managing NetApp Data for more details.

File Share Archiver Client

If File Share Archiver Client is installed from the CommCell Console or from the Software Installation Disc along with any agent install, the base client gets installed along with the File Share Archiver Client, which registers the client computer with the CommServe, that allows you to install the automatic updates on the client computer in your CommCell.

If the installation is made using MSI package, the automatic updates will not be installed on the client computer.

Pre-Install

Post-Install

General

• If the SharePoint Archiver is installed on the same machine as Microsoft Office SharePoint Portal Server 2003, all servers in the server farm will be upgraded to Microsoft .NET Framework version 2.0.
• When the SharePoint Archiver is installed on multiple Web Front End Servers, see Migration Archiving Considerations for configuration details and how to replicate SPDAStubDatabase.db across all Web Front End servers using Distributed File System (DFS) Replication.
• After installation, you will need to restart Internet Information Services (IIS). Typically, the iisreset command is used to restart IIS.

General

• The following configuration tasks are required before performing an Archive Operation using the SharePoint Archiver Agent:
  • Create a Subclient - See Subclients - SharePoint Archiver for more details.
  • Archiving Rules are initially disabled by default. You must clear the Disable All Rules option and deliberately enable the archiving rules before Archive Operations are possible.
• When both SharePoint 2003 and 2007 servers co-exist on the same client with the SharePoint Archiver Agent:
  1. Run the following command on the command line from the <Software Installation Path>\Base installation directory:
     
     CVAddSharePointMenu -c
  2. Restart Internet Information Services (IIS).*

  *Typically, the iisreset command is used to restart IIS.

• After the SharePoint Archiver Agent has been installed, the user may encounter the following error when attempting to access a SharePoint site from a web browser:

  This Windows SharePoint Services virtual server has not been configured for use with ASP.NET 2.0.50727.42. For more information, please refer to Knowledge Base article 894903 at http://go.microsoft.com/fwlink/?LinkId=42660.

  In this scenario, the following command should be executed to resolve this error:

  stsadm o upgrade forceupgrade url http://<URL_of_the_virtual_server>

• In a SharePoint environment with more than 500 site collections, it is recommended to increase the size and number of log files with the <logfile>_MaxLogFileSize  and <logfile>_MaxLogFileBackups registry keys. Replace <logfile> with any desired name (e.g., SPDBBackup, SPDocBackup, SPDocArchive, etc.).

Silent/ Decoupled Installation

After completing a silent or decoupled installation of a SharePoint Agent, you must manually enter a SharePoint Server Name and SharePoint Administrator Account in the Agent's Properties dialog box. For step-by-step instructions on accounts, see Change Account for Accessing Application Servers/Filers.

Post-Install

General

• In order to view or restore the content indexed NAS data from the Search Console, install the Deployment - File System NDMP Restore Enabler on the web search server.
• Several configuration tasks are required before you perform search and discovery operations on the data. See Configuration - Content Indexing and Search page for more information.

• In order to enable Domino Directory Service login or to restore Lotus Notes emails, you need to install the Lotus Notes Client on the Web Search Server on a 32-bit platform.

Enable Network Protocol to access SQL Server Express Edition Remotely

If you have Web Search Server installed pointing to Express Version of CommServe, you need to enable the TCP/IP network protocol, in order to access the SQLite database remotely using SQL Server management studio. Use the following steps to enable the network protocol on the CommServe computer:

1. On the Start menu, choose All Programs, point to Microsoft SQL Server and then click SQL Server Configuration Manager.
2. Expand SQL Server Network Configuration, and then click Protocols for <Instance>.
3. In the list of protocols, right-click the TCP/IP protocol, and then click Enable.

Post-Install

General

Install the latest version of Java with all the updates and configure SSL (Secure Socket Layer) on the tomcat server to enable secured access for the Web Search Client. For more information, see Enabling Secured Access for Web Search Client.

Pre-Install

Post-Install

General

In addition to a license for ContinuousDataReplicator, you must have an available license on the CommServe for any snapshot engines and copy managers you plan to use.

General

1. Ensure that ContinuousDataReplicator is installed on both the source and destination computers.
2. Create a Replication Set on the source computer.
3. Add a Replication Pair to the Replication Set you created on the source computer.

Cluster

• If the passive node was not available while installing the software, you must manually install the software on the passive node now. (See Manually Installing the Software on a Passive Node for step-by-step instructions.)

• After the installation of software is complete for all the physical nodes, and CDR software has been installed on the cluster server, stop and restart CDR Services on all of the physical nodes before you begin using CDR on the virtual server for data replication. For more information about how to do this, see Services - How To.

Post-Install

General

• After installing the SRM NAS Agent, you need to add a SRM NAS Filer that has the required data. For step-by-step instructions, see Add NAS Filer.

Post-Install

general

Add/Edit an Oracle Database for instructions on how to configure the SRM Agent for Oracle.

Post-Install

General

After installing the CommNet Server software, it will be listed as a client computer in its associated CommServe's CommCell Console. This does not register the CommCell with the CommNet Server, nor does it merge the user interfaces; however, this enables the CommNet Server to act as a client computer in the CommCell Console, which allows for the CommNet Server computer to support automatic update and licensing updates through the CommCell Licensing Administration Utility.

SNMP Enabler

Once the CommNet SNMP Enabler software is installed, verify that each computer defined during the installation to receive SNMP Traps is properly set up through their trap receiver software.