Mimosa NearPoint for Microsoft Exchange Server

Transcription

1 Information Immediacy, Discovery, & Continuity 3.5 Mimosa NearPoint for Microsoft Exchange Server Upgrade Guide 3.5

2 Copyright , Mimosa Systems, Inc. All Rights Reserved. Mimosa Systems, Inc Coronado Drive Santa Clara, CA The software and each of its components, including the source code, documentation, appearance, structure, and organization are owned by Mimosa and others and are protected under copyright and other laws. Title to the Software and any components or to any copy, modification, or merged portion shall remain with the respective copyright holders, subject to the licenses described within the Mimosa End User License Agreement ( EULA ). The Mimosa Software cannot be distributed without the prior written permission of Mimosa and cannot be copied, except as necessary for back-up purposes. The information contained in this manual is governed by the Limited Warranty expressed in the EULA. For additional third party copyright attributions refer the Additional_Copyrights.pdf document present in the <drive>:\program Files\Mimosa directory. The following are trademarks, or registered trademarks of Mimosa Systems, Inc: Mimosa Mimosa NearPoint Mimosa Systems NearPoint One Pass Protection NearPoint Deployment Advantage Microsoft, Windows, Outlook, and Entourage, are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. All other trademarks are the property of their respective owners. Mimosa NearPoint for Microsoft Exchange Server - Upgrade Guide October 9, 2008

3 CONTENTS 1. Upgrading NearPoint Overview Understanding the Upgrade Procedure Supported Hardware and Software Computing Storage Requirements Upgrade Prerequisites Performing Upgrade Post Upgrade Steps Post-Upgrade Points to Remember Configuring NPBackup after Upgrade Upgrading the Disaster Recovery Option Upgrading the ediscovery Option Reverting back to NearPoint Troubleshooting Upgrade A. Upgrade Checklist 43 iii

4 1 UPGRADING NEARPOINT This document covers the details about upgrading NearPoint 2.1 to 3.1 and higher. The details include: Overview Understanding the Upgrade Procedure Supported Hardware and Software Computing Storage Requirements Upgrade Prerequisites Performing Upgrade Post Upgrade Steps Post-Upgrade Points to Remember Configuring NPBackup after Upgrade Upgrading the Disaster Recovery Option Upgrading the ediscovery Option Troubleshooting Upgrade 1

5 1 UPGRADING NEARPOINT 1.1 OVERVIEW.. This guide provides planning and deployment for the NearPoint administrators who want to upgrade from NearPoint version 2.1 Build 2566 plus Hotfixes (HF7 is a minimum requirement), to 3.1 and higher versions Audience The NearPoint solution is intended to be deployed by an Exchange system administrator whose primary responsibilities include installing, configuring, and administrating Windows Servers, Microsoft Exchange Servers, and Outlook. Readers should be familiar with the principles and tasks of managing an Exchange Server, and perform these tasks as part of their typical responsibilities. While the NearPoint Server leverages Microsoft SQL Server and Active Directory, and is a consumer of storage, no special skills are needed to deploy NearPoint, beyond the ability to set up, connect or use these technologies. This guide provides guidance on the best practices for deployment and storage configurations Product Documentation Mimosa Systems strongly recommends reviewing the additional documentation prior to performing upgrade. The latest NearPoint documentation set includes the following guides: Mimosa NearPoint for Microsoft Exchange Server Compatibility Document Mimosa NearPoint for Microsoft Exchange Server Installation Guide Mimosa NearPoint for Microsoft Exchange Server Upgrade Guide Mimosa NearPoint for Microsoft Exchange Server Administrator's Guide Mimosa NearPoint for Microsoft Exchange Server Dashboard Guide Mimosa NearPoint Archive Client User s Guide Mimosa NearPoint Archive Client Quick Start User s Guide Mimosa NearPoint Cross Platform Archive Client User s Guide Mimosa NearPoint Cross Platform Archive Client Quick Start User s Guide 2 Mimosa NearPoint 3.5

6 UPGRADING NEARPOINT The NearPoint Options documentation set includes the following guides: Mimosa NearPoint Options Installation Guide Mimosa NearPoint File System Archiving Option Administrator's Guide Mimosa NearPoint PST Management Option Administrator's Guide Mimosa NearPoint Disaster Recovery Option Administrator's Guide Mimosa NearPoint ediscovery User s Guide Mimosa NearPoint Content Monitoring User s Guide Mimosa NearPoint Software Development Kit Typographical Conventions This guide uses the following conventions and symbols to highlight key information: Convention Note Warning Best Practice Bold Italic Glossary term Code Text Text in red Indicates Information provided as a note, tip, or advice Information provided as warning to avoid error conditions Recommendations and suggestions for best results Names of commands and fields in the user interface. Cross references or names of Websites and books. Terms appearing in the Glossary. Command line instructions and names of registry keys Error conditions (explained in Troubleshooting Section) Getting Additional Help To learn more about Mimosa products, visit our Web site, Upgrade Guide 3

7 1 UPGRADING NEARPOINT Understanding the Upgrade Procedure For help on using Mimosa products, you can us at You can also call the hotline numbers listed here: Country Hotline Number North America For customers with 24x7 Support: (408) For all other customers: (408) France Germany United Kingdom UNDERSTANDING THE UPGRADE PROCEDURE.. This section provides an overview of the additional features that the current NearPoint version comprises of and the performance change that administrators may experience after upgrade NearPoint Features and Above NearPoint 3.1 and above versions include many new features for increased scalability and enhanced performance. These features require additional storage for implementation and usage, which is discussed in the further sections. The key features include: GRID: With 3.1 and above, the advantage of Grid computing is brought to Microsoft Exchange archiving environments. You can now economically scale from hundreds to tens of thousands of mailboxes with a single NearPoint system consisting of one or many Servers. Cross-Forest NearPoint Support: Enterprises segregate Exchange Servers into one forest and User Accounts in to a different forest. The Exchange Resource forest trusts the Active Directory tree with Users, User Groups, and so on. This forest is the Account Forest. NearPoint 3.1 and above supports this Resource-User cross-forest configuration. 4 Mimosa NearPoint 3.5

8 UPGRADING NEARPOINT Understanding the Upgrade Procedure NearPoint Database Partitioning: NearPoint 3.1 and above supports multiple SQL Databases and multiple Storage Volumes. NearPoint stores the archive metainformation in SQL Databases and message information across Storage Volumes. By supporting multiple SQL Databases and Volumes, the NearPoint Archive can grow significantly without compensating on search performance. Scalable IOR: NearPoint 3.1 and above now supports multiple IOR volumes to enhance resiliency and availability for the NearPoint Grid. Public Folder Archiving for Auditor Access: NearPoint 3.1 and above can now perform continuous data protection for public folders, and support message-level restores and disaster recovery. PST Management Option: The NearPoint PST Archiving Option now consists of an automated PST Crawler, that searches Servers, desktops, and laptops for PST files based on administrator-defined policies. Disaster Recovery Option: The NearPoint Disaster Recovery Option can now enable the recovery of Exchange Server without requiring a Secondary NearPoint Server. Internationalization: The NearPoint functions such as Application Shadowing, Smart Extraction, Indexing, Self-Service Access, Mailbox Extension, and Offline Cache are now supported in German, French, and Japanese languages. For more information about additional features, refer to the current NearPoint Release Notes Upgrade Assumptions Before performing Upgrade, consider the following points: The Upgrade procedure assumes that NearPoint version 2.1 Build 2566 is installed. If ediscovery audits are being held, refrain from performing an upgrade as NearPoint upgrade uninstalls ediscovery Server. Ensure that all the audit work is complete before commencing upgrade related activities. Ensure that all handlers such as QueryPrep, Indexing, and so on have completed execution before commencing upgrade related activities. Upgrade Guide 5

9 1 UPGRADING NEARPOINT Understanding the Upgrade Procedure Depending upon the size of your organization, Upgrade may take few hours to few days. During this time, client side functions (Self Service Retrieve, Backup, ediscovery, Disaster Recovery) would not be available. Ensure that the users are aware that such a process is taking place. During Upgrade, NearPoint would not be backing up your Exchange related data. Ensure that a third party software is backing up the data so there is no information loss. If you have a multiple SQL Server environment, configure dedicated physical servers for each database instance. You must not configure multiple database instances running on a single physical server Understanding NearPoint SQL Database Changes With NearPoint 3.1 and above versions, the SQL Server and the NearPoint Server must be on separate machines within the same domain. NearPoint now creates five different databases to store information: MimosaContext This database contains configuration information, locations of all the storage volumes, information about the Exchange Servers and Active Directories that the NearPoint Server manages, and so on. MimosaExchangeItem This database contains information about all the items from the Exchange Servers that the NearPoint Server has archived. The database also contains the metadata information for retrieving the information from the file system. You can have multiple instances of this database. MimosaApplication This database contains the configuration details of the NearPoint client applications such as Self Service Retrieve Client and ediscovery. It also contains the application related data such as saved results, reports, and so on. MimosaActivity This database keeps track of all the activities performed by the NearPoint administrator and/or end user on the NearPoint Server or its applications such as SSR Client, ediscovery, PST Management, etc. MimosaBlobInfo This database contains information about retrieving data from the file system, for the exchange items that are stored in the MimosaExchangeItem database. You can have multiple instances of this database. 6 Mimosa NearPoint 3.5

10 UPGRADING NEARPOINT Understanding the Upgrade Procedure These databases can be on separate machines within the same domain. You need to set permissions for the NearPoint Service Account to access these databases Phasing out the VSS Shadow Volume NearPoint 3.1 and above versions do not use the VSS storage for storing Shadow Repository snapshot. Refer to the Mimosa 2.1 documentation for information about the MsiDelSnaps utility that you can use to clean this volume for re-use. In case you plan to revert back to NearPoint 2.1 in case of failure, leave this VSS diff association as is Understanding the NearPoint Repositories With this version, NearPoint uses the following repositories to store NearPoint related data. You can have multiple instances of all the repositories, except for Scratch Volume: Indexed Object Repository (IOR) The IOR volumes store single-instanced machine-readable archived message and item data that is extracted from Exchange Mailboxes and Archived PST files. Index Volume This volume stores indexes of all the objects in the Indexed Object Repository. Scratch Volume This volume stores temporary files for PSTs, Message Restore, Offline Cache, and such operations. Shadow Repository These shared volumes are used to store databases from Exchange Storage Group managed by Mimosa NearPoint. This volume stores the Exchange Database files (EDBs and STMs). All the Exchange data that is shipped to NearPoint is stored in this location. These repositories can be on separate machines within the same domain. You need to set permissions for the NearPoint Service Account to access these repositories. While keeping the existing IOR, Index, and Shadow Repository volumes, you can add more of these volumes, and use all the volumes to store data. You can add more volumes Upgrade Guide 7

11 1 UPGRADING NEARPOINT Supported Hardware and Software after you perform an upgrade. Refer to the current Mimosa NearPoint Administrator s Guide for adding these volumes using the NearPoint Configuration Tool. Note: For each NP repository, disable content indexing for the volume in which the repository exists for improved performance: 1. Right-click the volume and select Properties from the shortcut menu. For example, if a repository is on the E:\ drive, then right-click E:\. 2. Clear Allow Indexing Service to index this disk for fast file searching. 3. Click Apply and then OK Understanding Additional Storage Requirements For upgrade, it is important to plan storage requirements for the SQL Server databases. In NearPoint 2.1, only one SQL database was present. With NearPoint 3.1 and above, five databases are required. For details about computing these requirements, refer Computing Storage Requirements on page SUPPORTED HARDWARE AND SOFTWARE.. Based on the features described in the NearPoint Features and Above section, you need to make changes in the hardware and software provisions for NearPoint. This section covers the Hardware and Software recommendations that you can use to plan the upgrade prerequisite requirements. The section includes: Hardware Recommendations Supported Operating Systems Supported Microsoft Outlook Versions Supported SQL Server Versions Additional Microsoft Components 8 Mimosa NearPoint 3.5

12 UPGRADING NEARPOINT Supported Hardware and Software Supported Exchange Servers Supported Exchange Server 2007 Configurations Hardware Recommendations Depending on the size of your environment and the NearPoint Servers' capacity (storage and performance), you may configure up to four Exchange Servers to be shadowed. The CPU, memory, and storage requirements will depend on the size and number of Exchange Servers you plan to manage. Note: NearPoint requires RAW disks. Virtual Hard Disks (VHDs) are not supported. NearPoint supports a wide variety of storage devices including Parallel or Serial ATA. Mimosa Systems strongly recommends these be configured using some form of RAID, either hardware RAID, or minimally, Windows Software RAID. Though the NearPoint Server will support almost any type of direct-access storage that Microsoft supports, a key value proposition for the NearPoint solution is to optimize NearPoint capabilities for data protection, recovery, and archiving, leveraging the lowest cost reliable storage. In today's market, this translates into lower cost solutions often built around SATA drives. NearPoint can also support Network Access Storage (NAS) as a target; however at the time of writing, this feature has not been extensively tested, and in many cases will not be as fast as other types of Direct Access Storage (DAS), and is therefore not recommended. Note: NAS is not supported for NearPoint Shadow as these volumes require block storage. The following table provides general, recommended, hardware configurations: Scaling Factor Large Medium Small Number of Mailboxes 1, ,000 up to 50 NearPoint Microsoft SQL server Location Dedicated - Remote Dedicated - Remote Shared - Local SQL (under 50 mailboxes) Upgrade Guide 9

13 1 UPGRADING NEARPOINT Supported Hardware and Software Scaling Factor Large Medium Small Memory 4-6GB 4GB 4GB Storage Interconnect Storage Classification [Includes any suitable Array certified in Microsoft Windows Server System Storage, RAID Storage, RAID System Catalog] Disk Type Windows Volume Expansion iscsi SATA RAID Controller Medium Enterprise class RAID Array with Hot Spare SATA I & II SCSI 320 SAS Fibre Channel 1-2GB/sec Fibre Channel SCSI 320/160 SATA RAID Controller iscsi Server internal hardware RAID with cold spare Workgroup class RAID Array with Spare SATA I & II PATA SCSI 320/160 Fibre Channel SCSI SATA RAID Controller iscsi PATA RAID Controller IDE Server internal JBOD (with Windows OS RAID) Server Internal Hardware RAID SATA I & II PATA Yes Yes Yes Networking 1000 MB/sec 1000 MB/sec 100 MB/sec SCSI 320/ MB/sec 100 MB/sec 10 Mimosa NearPoint 3.5

14 UPGRADING NEARPOINT Supported Hardware and Software Supported Operating Systems NearPoint 3.1 and above versions are supported on the following operating systems. Mimosa Systems recommends upgrading the Service Packs, if required, prior to performing Upgrade: Operating System Microsoft Windows Server 2003 Standard Edition (32 and 64 bit) Microsoft Windows Server 2003 Enterprise Edition (32 and 64 bit) Microsoft Windows Server 2003 R2 Standard Edition (32 and 64 bit) Microsoft Windows Server 2003 R2 Enterprise Edition (32 and 64 bit) Service Packs SP1, SP2 SP1, SP2 SP1, SP2 SP1, SP Supported Microsoft Outlook Versions The current NearPoint version SSR client works with following Outlook versions. Mimosa Systems recommends upgrading the Outlook version, if required, prior to performing Upgrade: Microsoft Outlook Microsoft Outlook 2003 (all editions) Microsoft Outlook 2007 (Professional and Enterprise editions) Versions SP1 (build ) or SP2 SP3 RTM, SP Supported SQL Server Versions For this NearPoint version, Mimosa Systems requires Microsoft SQL Server bit SP1 or SP2. Upgrade Guide 11

15 1 UPGRADING NEARPOINT Supported Hardware and Software Depending on the size of your environment you will need to decide whether you will run SQL Server on a separate machine or on the NearPoint Server. This is a performance consideration that Mimosa recommends for the environments listed in the "Large and Very Large" categories defined in the Sample Configurations and Recommended Components for NearPoint Server table. For those in the Medium category above, although optional, a separate Microsoft SQL Server will offer better performance. From a sizing perspective, a rule of thumb is for the size of the Microsoft SQL Server database records as a portion of the total archived data is approximately 20% of the total messages, where the average message size is 50kb. Alternatively, for each archived message, approximately 7KB should be reserved for SQL Data and Log data Additional Microsoft Components For NearPoint, you must install the following Microsoft components: Exchange System Manager tools (for Exchange Server 2003) Exchange Management Console (for Exchange Server 2007) SQLXML MSXML.NET FrameWork 12 Mimosa NearPoint 3.5

16 UPGRADING NEARPOINT Supported Hardware and Software Microsoft Exchange System Manager Tools (for Exchange Server 2003 only) You must install ESM tools for a native Exchange Server 2003 environment or in a mixed mode environment. Microsoft Exchange System Manager a Microsoft Exchange 2003 System Manager (ESM) Tools Service Pack (Match Service pack to highest level of Production Exchange Servers) RTM (No Service Pack) SP1 SP1 and Hot Fix Microsoft Exchange 2000 System Manager (ESM) Tools SP2 (Match Service pack to highest level of Production Exchange Servers) Microsoft Exchange 2000 SP3 and Rollup Patch KBKB v2 b a. Microsoft does not support ESM 2003 installation on x64 Operating Systems. b. You might not be able to install Rollup Patch KBKB v2 on a x64 Operating System. If patch does not update ese.dll or esebcli2.dll they need not be applied on the ESM tools on NP Server. Note: ESM 2003 can be installed on x64 Operating Systems that are not patched with SP2 in spite of warnings. To install ESM 2003 on x64 OS with SP2: 1. Uninstall SP2. 2. Re-install IIS and.net components. 3. Install ESM Re-apply SP2. Upgrade Guide 13

17 1 UPGRADING NEARPOINT Supported Hardware and Software Microsoft Exchange Management Console (for Exchange Server 2007) If you have a native Exchange Server 2007 environment, you do not need to install ESM tools. For a native Exchange Server 2007 environment or a mixed mode environment, you must install Exchange Management Console version Microsoft SQLXML You must install Microsoft SQLXML version 3.0 SP3. Refer Microsoft MSXML You must install Microsoft MSXML version 4.0 SP2. Refer C5D7485F2B42&displaylang=en. Microsoft.NET Framework Install one of the following versions: Microsoft.NET FrameWork Microsoft.NET FrameWork Version 3.5 (32 and 64 bit) Service Pack - 14 Mimosa NearPoint 3.5

18 UPGRADING NEARPOINT Supported Hardware and Software Supported Exchange Servers NearPoint 3.1 and above versions support the following Microsoft Exchange Server versions. Mimosa Systems recommends upgrading the Exchange version, if required, prior to performing Upgrade: Version Microsoft Exchange 2003 Standard Edition Microsoft Exchange 2003 Enterprise Edition Microsoft Exchange 2000 Standard Edition Microsoft Exchange 2000 Enterprise Edition Microsoft Exchange 2007 Enterprise and Standard Editions Service Pack RTM (No service pack) SP1 SP1 and Hot Fix SP2 RTM (No service pack) SP1 SP1 and Hot Fix SP2 SP3 and Rollup Patch KBKB v21 SP3 and Rollup Patch KBKB v221 RTM (No service pack) SP1 For details about supported configuration, refer to Supported Exchange Server 2007 Configurations on page -16. Upgrade Guide 15

19 1 UPGRADING NEARPOINT Computing Storage Requirements Supported Exchange Server 2007 Configurations Since NearPoint 3.1 and above support both Exchange Server 2003 and 2007, you can configure the Exchange Server environment as described below. Mimosa Systems recommends configuring the Exchange Server environment before performing Upgrade: Exchange Organization Configuration Details Public Folder Store Available Supported NearPoint Clients Mixed Mode The organization has both Exchange Server versions, 2003 and 2007, where the Exchange Server 2003 is the first Exchange Server in the organization. Available Both Outlook and Outlook Web Access are supported. Native E2K7 The organization has a native Exchange Server 2007 environment, with Microsoft Outlook version Available Both Outlook and Outlook Web Access are supported. Native E2K7 The organization has a native Exchange Server 2007 environment, with Microsoft Outlook version Is Explicitly Created Both Outlook and Outlook Web Access are supported. Not Available Only Outlook Web Access is supported. a a. Mimosa Systems strongly recommends contacting the Mimosa Support for further assistance. 1.4 COMPUTING STORAGE REQUIREMENTS.. To compute storage requirements, download and install the Pre-Migration Tool. Perform the following steps to install and use the Tool: 1. Access the NearPoint Installation directory and copy the Pre-Migration Tool zip file on the machine where NearPoint is installed. 16 Mimosa NearPoint 3.5

20 UPGRADING NEARPOINT Computing Storage Requirements 2. Unzip the file and double-click setup.exe. 3. Follow on screen instructions to install the Tool. To use this tool, click Start > Programs > Mimosa Systems > Mimosa Pre- Migration Tool. The Tools computes sizing requirements and plans the capacity required by the NearPoint system to upgrade from 2.1 to 3.1 or above. View the Summary and Report tabs for details. To understand the storage requirements that NearPoint 3.1 and above versions would require, consider the following example: Details Specific to 2.1 Specific to 3.1 and above No. of Active Mailboxes Space allocation for Mimosa Databases 180GB 495GB (about 2.7 times the original space) Shadow IOR 1.2TB 1.2TB Space allocation for MimosaLog Temporary space allocation for tempdb Temporary Extra Space for Scratch Volume 150GB approx. This space is more or less equal to the space allocated for the Mimosa Databases. 35GB This space is temporarily allocated to assist migration-related activities. While specifying the scratch volume, ensure that: the free space available for the scratch volume must be 20% more than the size of the largest table in the 2.1 Mimosa database the target volume on which you configure this Scratch Volume must not host any other NearPoint repositories or databases Upgrade Guide 17

21 1 UPGRADING NEARPOINT Upgrade Prerequisites 1.5 UPGRADE PREREQUISITES.. Before commencing Upgrade, perform the following steps: 1. Before you begin upgrade planning, you MUST contact the Mimosa Support for critical information. 2. Based on the capacity planning details specified in Understanding the Upgrade Procedure section, upgrade the hardware and software that the upgraded version of NearPoint would be using. 3. If you are upgrading to NearPoint version 3.5 and above, migrate all databases to SQL Server(s) versions If you have upgraded from NearPoint version 1.3 to 2.1, and now plan to upgrade to 3.1 or above, ensure that you have moved the Index directories to a separate location than the SmartExtract directory. If you have not moved the Index directories to a separate location, use the NearPoint Re-Config Tool to modify the location. Refer to the NearPoint 2.1 documentation for details. 5. Ensure that SQL Management Tools are present on the NearPoint Server that you want to upgrade. 6. Ensure that the BCP.exe file is present on the NearPoint Server in the <drive>:\program Files\Microsoft SQL Server\90\Tools\Binn directory. 7. Cancel and disable all running NearPoint jobs. 8. Delete all scheduled NearPoint tasks from the C:\WINDOWS\Tasks directory. 9. Stop all NearPoint services. 10.Ensure that a third party software is backing up the Exchange Server data. 11.Since the TempDB database temporarily expands during upgrade, Mimosa Systems strongly recommends moving the database to a non-system drive (any local drive other than C:\). 12.Back up the Mimosa and MimosaActivity SQL databases using a third party software. 18 Mimosa NearPoint 3.5

22 UPGRADING NEARPOINT Performing Upgrade 13.Backup CIM and registry using waterfall.exe. Refer to the Mimosa NearPoint for Microsoft Exchange Server Administrator's Guide for details. Note: In event that you want to revert back to NearPoint 2.1, you would need these databases, CIM, and registry details during the reverting procedure. 14.Save a snapshot of the current NearPoint installation, in case you need it later. 15.Ensure that the ediscovery and SSR users are aware that NearPoint is under maintenance, and would not be available for a stipulated period. 1.6 PERFORMING UPGRADE.. This section covers details about performing upgrade. Before performing an Upgrade, ensure that you have performed the prerequisite steps specified in the Upgrade Prerequisites section. The actual Upgrade procedure performs the following activities: 1. The NearPoint installer converts the existing Shadow, Smart Extract, and Index Repositories into NearPoint 3.1 (or above) specific format, and stores them in the newly created repositories. It also adds the Scratch Volume. 2. The Database installer checks that the current databases are on SQL Server(s) version It then modifies the SQL databases for migration to the format that NearPoint 3.1 and above supports. 3. Since NearPoint 3.1 and above use MimosaContext database instead of CIMOM, the installer performs steps to migrate the information from existing CIMOM to NearPoint 3.x specific format. 4. Previous registry settings are migrated to the SQL Databases. Mimosa Systems recommends using the Upgrade Checklist attached to this guide before beginning to upgrade your NearPoint system. For the checklist, refer Upgrade Checklist on page -43. The Upgrade procedure consists of the following steps: Upgrade Guide 19

23 1 UPGRADING NEARPOINT Performing Upgrade 1. Beginning Upgrade 2. Installing the NearPoint Database 3. Adding Scratch Volume 4. Upgrading to NearPoint 3.1 and Above Beginning Upgrade To begin Upgrade: 1. Log in with the Mimosa Service Account. 2. Unzip the NearPoint Installer to a location that does not have a deep folder hierarchy. Typically, unzip it directly to C: or D: drives. 3. Double-click setup.exe. 4. In the NearPoint wizard, click Next. 5. In the End User License Agreement dialog box, read through the terms of the license agreement. After reading the terms, select I accept the terms in license agreement. Click Next. 20 Mimosa NearPoint 3.5

24 UPGRADING NEARPOINT Performing Upgrade 6. Under NearPoint Maintenance Mode Options, select Upgrade. 7. Click Next. 8. Select the NearPoint component(s) that you want to upgrade: NearPoint Server NearPoint Administrative Console 9. NearPoint performs a pre-requisite check. If you have not migrated the NearPoint databases to SQL Server(s) version 2005, an error is displayed. You must exit the upgrade procedure, migrate the databases, and then restart the upgrade procedure. If all prerequisites are present, a summary is displayed. 10.Click Next. 11.If you had installed NearPoint version 1.3, then upgraded to NearPoint version 2.1, and now are upgrading to 3.1 or above, ensure that the Index directories are moved to Upgrade Guide 21

25 1 UPGRADING NEARPOINT Performing Upgrade a separate location than the SmartExtract directory. To ensure that you have performed this prerequisite, the following warning is displayed: 12.If you have moved the Index directories as directed, click OK. A warning is displayed to ensure that you have backed up the Mimosa databases. If you have, click OK, else click Cancel to quit the Upgrade process and back up the Mimosa databases. The NearPoint Installer now launches the Cimom Data Export Tool. This tool exports important job related information to a specified location in XML format. You can later use this XML file to schedule NearPoint operations once upgrade is complete. 22 Mimosa NearPoint 3.5

26 UPGRADING NEARPOINT Performing Upgrade 13.Click Click here to continue with upgrade, once the tool completes execution Installing the NearPoint Database To install the current NearPoint version databases, perform the following steps: 1. Specify the size of the NearPoint databases in the NearPoint Database Installation screen. 2. Click Next. In the Database Server Settings dialog box, for each database: a. Select the SQL Server in the Server Name field. Click... to browse to the server if required. Upgrade Guide 23

27 1 UPGRADING NEARPOINT Performing Upgrade b. In the SQL User and Password fields, specify the user name and password for connecting to the SQL server. Note: If you want to use the same username and password for all NearPoint databases, select Apply settings to all databases. c. Specify the locations where you want the database data files and database log files in the Default Data File Path and Default Log File Path fields. d. Click Apply to establish the SQL connection. e. For each database, you can click Customize and specify different locations for storing the data of specific database files. 24 Mimosa NearPoint 3.5

28 UPGRADING NEARPOINT Performing Upgrade 3. For example, for MimosaContext, you can specify different locations for MimosaContext.mdf, MimosaContext_Data.ndf, and so on. Select the database file and click... to browse to a different location for storing that database file. f. Click Next. The database installation summary is displayed. Upgrade Guide 25

29 1 UPGRADING NEARPOINT Performing Upgrade 4. Click Next to begin the installation. Note: If any of the MimosaExchangeItem databases are hosted on servers with SQL version 2000, the NearPoint installer creates the <drive>:\program Files\Microsoft SQL Server\MSSQL\Binn\NearPoint directory, and copies the MsiHashBytes.dll file into this directory. This file is used to install an extended stored procedure to support generation of md5 hashes on SQL Server For more information, refer the relevant SQL Server documentation. 5. After installation is complete, click Finish. The Volume Information dialog box opens. 26 Mimosa NearPoint 3.5

30 UPGRADING NEARPOINT Performing Upgrade Adding Scratch Volume This dialog box displays information about the locations where the IOR, Index, and Shadow volumes are stored along with their share paths. To add the scratch volume: 1. Click Add Scratch Volume. 2. Enter a name for the scratch volume in the Description field. Note: While specifying the scratch volume, ensure that: the free space available for the scratch volume must be 20% more than the size of the largest table in the 2.1 Mimosa database the target volume on which you configure this Scratch Volume must not host any other NearPoint repositories or databases Upgrade Guide 27

31 1 UPGRADING NEARPOINT Performing Upgrade 3. Enter or click Browse to specify the shared path where you want to store the scratch volume. 4. Click OK. 5. Click Next to begin Upgrade Upgrading to NearPoint 3.1 and Above The NearPoint Installer now upgrades to the latest NearPoint version. After Upgrade is successfully complete: 1. A summary of the upgraded NearPoint components is displayed. Click Next. 2. Upgrade performs the following activities: 28 Mimosa NearPoint 3.5

32 UPGRADING NEARPOINT Performing Upgrade Import 2.1-related information about policies, roles, configuration-related data, and so on Upgrade Guide 29

33 1 UPGRADING NEARPOINT Performing Upgrade Generate blob handles for extended messages If the TempDB database is still on C:\ drive, a warning is displayed to indicate that since this database would temporarily expand during upgrade, Mimosa Systems strongly recommends moving TempDB data and log files to a non-system drive. Click Yes to continue. 30 Mimosa NearPoint 3.5

34 UPGRADING NEARPOINT Performing Upgrade Migrate MimosaContext database information Upgrade Guide 31

35 1 UPGRADING NEARPOINT Performing Upgrade Migrate from the 2.1 Mimosa database to 3.1 (or above) MimosaExchangeItem database 32 Mimosa NearPoint 3.5

36 UPGRADING NEARPOINT Performing Upgrade Migrate information from the Mimosa databases - MimosaBlobInfo, MimosaApplication, and MimosaActivity as shown below 3. After the migration is complete, a message is displayed: 4. Click OK. The NearPoint Installer validates the migrated data. 5. After the validation is complete, click Finish twice. After Upgrade is complete, you must perform Post Upgrade steps specified here, Post Upgrade Steps on page -34. Upgrade Guide 33

37 1 UPGRADING NEARPOINT Post Upgrade Steps 1.7 POST UPGRADE STEPS.. After Upgrade is complete, perform the following steps before using NearPoint: 1. Re-publish the Mimosa stub forms. For details, refer the Mimosa NearPoint for Microsoft Exchange Server Administrator's Guide. 2. Run a Full Copy schedule on all Exchange Servers that NearPoint manages. 3. Re-create and schedule all the NearPoint jobs. 4. After Upgrade, only the Mimosa Service Account has full access permissions on the NearPoint Repositories. For information about other permissions that you need to set, refer to the Permissions Assigned by the Installer appendix on the Mimosa NearPoint for Microsoft Exchange Server Installation Guide. Ensure that all the permissions mentioned in this section are set for the freshly upgraded NearPoint Server. 5. The Shadow Repository contains old data from the 2.1 Shadow Repository. After Full Copy is successfully complete, you can either delete this data or move it to another location. 6. You can now start archiving Exchange data as before. Ensure that SSR and ediscovery clients are made aware that the maintenance is complete, and that the NearPoint archive clients would now be available. 7. If your organization has a multiple-dc, multiple-domain environment, set the order of preference for the DCs that would scan the domains using the Advanced Node Settings of the NearPoint Configuration Tool. Refer to the Mimosa NearPoint for Microsoft Exchange Server Administrator s Guide for details. 1.8 POST-UPGRADE POINTS TO REMEMBER.. After Upgrade is successfully done, please remember the following points while using NearPoint-archived data: 34 Mimosa NearPoint 3.5

38 UPGRADING NEARPOINT Configuring NPBackup after Upgrade Do not delete old data from the Shadow Repository till the Full Copy operation is successfully complete. The current NearPoint version now archives distribution list related information. Data archived with prior NearPoint versions may not include this information. This may affect ediscovery searches. In this NearPoint version, if you login as a non-archived user, and access the Outlook profile of an archived user, the cross-platform links on the extended messages would not function. NearPoint requires you to login as an archived user, to use this functionality. Access the Add/Remove Programs wizard: a. Click Start > Control Panel > Add or Remove Programs. b. If you see more than one entry for Offline Cache installation, remove the older entry and keep the latest Offline Cache installation only. 1.9 CONFIGURING NPBACKUP AFTER UPGRADE.. After Upgrade is successfully complete, perform the following steps for configuring NPBackup: The third party backup softwares supported by this NearPoint version are Windows NTBackup, Symantec s Backup Exec, and Tivoli Storage Manager. Depending upon the software that you use, perform the following steps to replace the relevant *BackupIOR.ini file: a. Access the NearPoint installation directory, setup\mimosa\nearpointbackup\<3rd_party_sw_dir>. b. Copy the *BackupIOR.ini file. c. Access <drive>:\program Files\Mimosa\NearPointBackup\<3rd_party_sw_dir>, and replace the existing file with the file you copied in previous step. Upgrade Guide 35

39 1 UPGRADING NEARPOINT Upgrading the Disaster Recovery Option For example, if you use NTBackup as the third party backup software, access the...\nearpointbackup\nt directory within the setup, and copy the NTBackupIOR.ini file. Replace the file of the same name in the <drive>:\program Files\Mimosa\NearPointBackup\NT directory. After replacing the *BackupIOR.ini files, modify them to configure backup for the IOR repositories. For details, refer to the current version s Mimosa NearPoint for Microsoft Exchange Server Administrator's Guide. If you want to take advantage of the catalog list based backup option, modify the *BackupIOR.ini file accordingly by referring the Mimosa NearPoint for Microsoft Exchange Server Administrator's Guide. Then perform a full backup operation on the IOR volume(s), before scheduling incremental backups. Since the structure of the NearPoint databases has changed with the current NearPoint version, you must reconfigure all DBBackup tasks to take backup of the new databases. For details, refer to the current version s Mimosa NearPoint for Microsoft Exchange Server Administrator's Guide. Ensure that you perform a full backup operation on all NearPoint databases before configuring incremental backups. Mimosa Systems strongly recommends full backup of the NearPoint repositories. Then, you can configure incremental backups for the repositories as well UPGRADING THE DISASTER RECOVERY OPTION.. Before upgrading the 2.1 Disaster Recovery Option to 3.1 or above, ensure that you have performed the following prerequisites: Backup the 2.1 Mimosa databases. Delete the existing Exchange and Site Disaster Recovery policies. This step deletes the replication sets for all the Repositories and Databases. 36 Mimosa NearPoint 3.5

40 UPGRADING NEARPOINT Upgrading the ediscovery Option Upgrading and Configuring the Disaster Recovery Option Perform the following steps to upgrade and configure the DR Option: 1. Perform NearPoint Upgrade by following the steps described in the Performing Upgrade section. 2. Perform the post Upgrade steps described in the Post Upgrade Steps section. 3. Re-configure the Exchange and Site Disaster Recovery policies. For details about configuring the policies, refer to the current version of Mimosa NearPoint Disaster Recovery Option Administrator's Guide. Configuring the NearPoint Standby Site You cannot directly upgrade the Standby Site. You can: 1. Uninstall NearPoint 2.1. Refer to the NearPoint 2.1 documentation for details. 2. Install the current NearPoint version. Refer to respective documentation for details. 3. Configure the Site to work as the Standby Site UPGRADING THE EDISCOVERY OPTION.. After you have installed the NearPoint Server and performed the post-upgrade steps, you can upgrade the ediscovery Server: 1. Unzip the installation directory of the same version of ediscovery Server. 2. Double-click setup.exe. 3. On the Installation Wizard, enter the Alias name of the NearPoint Server. 4. Click OK to begin ediscovery data migration. 5. After migration is successful, click Finish. 6. Enter the Mimosa Service Account password. 7. Click OK to complete the installation. Upgrade Guide 37

41 1 UPGRADING NEARPOINT Reverting back to NearPoint 2.1 After installation is successfully complete, ediscovery notifies the ediscovery clients about the upgrade. Next time a user invokes the ediscovery Client, they would be requested to upgrade to the current ediscovery version REVERTING BACK TO NEARPOINT In case of a failure to upgrade and you want to revert back to NearPoint 2.1, follow the steps described in this section. Note: Mimosa Systems assumes that you have taken a backup of the databases, CIM, and registry as directed in the Upgrade Prerequisites on page -18 section Prerequisites before Reverting back Before you revert back to NearPoint 2.1, ensure that: 1. Ensure that a third party software is backing up the Exchange Server data. 2. A snapshot of the old NearPoint installation is available. 3. Ensure that the VSS diff association is left as is. 4. Ensure that the ediscovery and SSR users are aware that NearPoint is under maintenance, and would not be available for a stipulated period Reverting back to NearPoint 2.1 Perform the following steps: 1. Click Start > Control Panel > Add/Remove Programs and uninstall all NearPoint applications. 2. Rename NearPoint directories (Shadow, SmartExtract, and Index) to oldshadow, oldsmartextract, and oldindex. 3. Excluding the repositories, clean all residual directories from the filesystem. 38 Mimosa NearPoint 3.5

42 UPGRADING NEARPOINT Reverting back to NearPoint Install NearPoint 2.1 using the instructions present in the Mimosa NearPoint 2.1 Installation Guide. While configuring the databases, use the existing 2.1 Mimosa and MimosaActivity databases. Also, ensure that you configure the repositories to point to the same location as they were before. 5. After the installation is complete, stop and disable all NearPoint services: a. Click Start > Run. b. Enter services.msc and click OK. c. Right-click all the NearPoint services and select Stop from the shortcut menu. 6. Delete MimosaCtx and Mimosa namespaces: a. Click Start > Run. b. Enter wbemtest and click OK. c. Enter root in the Namespace field and click Connect. d. Click Open Instance. e. Enter NAMESPACE and click OK. f. Click Instances. g. Delete the MimosaCtx namespace. h. Delete the Mimosa namespace. 7. From backup, restore the MsiInstrumentation.mof file, and compile the file. 8. Delete the newly created Shadow, SmartExtract, and Index directories. Rename the old directories to their original names. 9. Restart all NP services. You can now start archiving Exchange data as before. Ensure that SSR and ediscovery clients are made aware that the maintenance is complete, and that the NearPoint archive clients would now be available. Upgrade Guide 39

43 1 UPGRADING NEARPOINT Troubleshooting Upgrade 1.13 TROUBLESHOOTING UPGRADE.. The Upgrade procedure fails with a critical error. Explanation: The upgrade procedure could not find a critical component or could not perform a critical operation, and fails to proceed further. Resolution: Mimosa Systems recommends reverting back to 2.1 and then restarting the Upgrade procedure. For reverting back to 2.1, refer to Upgrading the ediscovery Option on page -37. While performing Upgrade, the message Installer was un-able to rename MimosaActivity to MimosaActivity21. Please rename MimosaActivity to MimosaActivity21 and press OK to continue. Explanation: While upgrading from 2.1 to 3.1 or above, the Database Installer detects the existing MimosaActivity database, and renames it to MimosaActivity21. If the installer is unable to rename the database, this error occurs. Resolution: Perform the following steps: 1. Leave the Upgrade Installer running. 2. Access the SQL Enterprise Manager. 3. Manually kill all the connections to the MimosaActivity Database. 4. Quit the SQL Enterprise Manager. 5. Return to the Upgrade wizard, and click OK to continue. While performing Upgrade, the process exits before the current NearPoint version gets installed. Explanation: The system is left in an unstable state due to a failure during the upgrade or migration process. Resolution: During upgrade, SSR and ediscovery is not available for clients. Mimosa Systems strongly recommends reverting back to NearPoint 2.1, so that the NearPoint archive client functions become available. 40 Mimosa NearPoint 3.5

44 UPGRADING NEARPOINT Troubleshooting Upgrade Before reverting back to NearPoint 2.1, perform the following steps to clean the machine on which you were installing NearPoint: 1. Log in with the Mimosa Service Account. 2. In the current NearPoint setup directory, double-click setup.exe. 3. In the NearPoint wizard, click Next twice. 4. In the End User License Agreement dialog box, read through the terms of the license agreement. After reading the terms, select I accept the terms in license agreement. Click Next. 5. Under NearPoint Maintenance Mode Options, select Uninstall Components: Click Next. 6. Select all NearPoint components to uninstall. 7. If a warning is displayed to ensure that the messages are retracted, click Yes and continue the uninstall procedure. Upgrade Guide 41

45 1 UPGRADING NEARPOINT Troubleshooting Upgrade 8. After the uninstall procedure is complete, access the <drive>:\program Files directory and delete the Mimosa directory. Note: Do not delete any other NearPoint related files or directories. 9. Access the scheduled Windows Tasks, and delete all tasks scheduled for NearPoint. 10.Access the SQL Server Management wizard, and delete all Mimosa databases. Now perform the steps mentioned in the Upgrading the ediscovery Option section to revert back to NearPoint 2.1. After upgrading the ediscovery Option, searched messages do not open on double-clicking them. Explanation: After upgrading to NearPoint version 3.1.1, if you attempt to open searched items through the ediscovery Client, a mapi issue may occur. Resolution: On the machine that has the ediscovery Server installed, perform the following steps: 1. Click Start > Run > cmd > OK. 2. Type fixmapi and press Enter. 3. After the program executes successfully, exit the command prompt. 4. Click Start > Run > services.msc > OK. 5. Right-click Mimosa Restore Service and select Restart from the shortcut menu. On the ediscovery Client machine, you can now attempt to open the searched messages. 42 Mimosa NearPoint 3.5

46 A UPGRADE CHECKLIST This appendix provides a checklist that you can use while upgrading NearPoint from version 2.1 to 3.1 or above. Mimosa Systems recommends printing this checklist and mark the action items as you perform them. Action Item The current NearPoint version is 2.1 Build 2566 plus HF7. Sizing and Capacity Planning: The Pre-Migration Tool is installed and executed to get a list of pre-migration capacity planning and sizing requirements. Depending upon the Pre-Migration Tool file sizing recommendations, physical provision is made. All NearPoint databases are migrated to SQL Server(s) version SQL 2005 tools are installed on the machine where you are upgrading NearPoint. Storage Health-check using IOMeter is done. If SQL databases are hosted on NAS/CIFS, network requirements are taken care of. Additional Scratch volume on SQL server is temporarily provisioned for faster migration. Bring down the 2.1 NearPoint Server: Done? 43

47 UPGRADE CHECKLIST Action Item From the command prompt, the Waterfall.exe is executed to backup Registry and CIMOM. This backup that is stored under <Installation Path>\Mimosa\common\backup directory, is then copied to a safe location. Allow the dehydrate and differed dehydrate jobs finish. Then delete all scheduled jobs. The Log Shipping and Full copy cycles are stopped. Let Indexer and QueryPrep jobs finish, such that no items remain in Messagequeryprep Table. Quit the NearPoint Administrative Console. If the NearPoint Server is acting as primary backup software, ensure that a third party software is backing up the Exchange Server. Disable SSR and ediscovery access. Notify the users accordingly. If an Audit is either expected or is in progress, do not migrate till the Audit is done. Backup Mimosa and MimosaActivity SQL databases using third party backup software. Any software that is backing up the SQL server is stopped. Getting ready for upgrade: All 3.1 pre-requisites are installed. For customers who had upgraded from 1.3 to 2.1 and are now upgrading to higher versions, Indexes are moved to separate location. TCP/IP is enabled in the SQL configuration tools. Storage allotment and health check using IOMeter is done. The DMConfig.txt is updated and copied to the NearPoint directory, as instructed. Done? Upgrade Guide 44