EMC Documentum Content Server Relocation Using the NetWorker Module for Documentum as a Data Mover Applied Technology

Abstract

EMC® NetWorker® Module for EMC Documentum® (NMD) delivers integrated, synchronized Documentum server “hot” backups with no shutdown or disruption of applications. NMD can be used for relocating Documentum repositories to a remote site. This white paper highlights how users can utilize NMD to relocate the EMC Documentum Content Server from one location to another. August 2010

Copyright © 2010 EMC Corporation. All rights reserved. EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice. THE INFORMATION IN THIS PUBLICATION IS PROVIDED “AS IS.” EMC CORPORATION MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Use, copying, and distribution of any EMC software described in this publication requires an applicable software license. For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com All other trademarks used herein are the property of their respective owners. Part Number h8044 EMC Documentum Content Server Relocation Using the NetWorker Module for Documentum as a Data Mover Applied Technology

2

Table of Contents Executive summary ............................................................................................ 4 Introduction ......................................................................................................... 4 Audience ...................................................................................................................................... 4 Terminology ................................................................................................................................. 4

Installation and configuration of EMC Documentum Content Server components ........................................................................................................ 5 Setup of the source host, target host, and NetWorker server ........................ 7 Setup of the source host .............................................................................................................. 8 Setup of the target host ................................................................................................................ 9 Setup of the NetWorker server .................................................................................................... 9

Prerequisites for relocating the Content Server .............................................. 9 Backup of the EMC Documentum Content Server with NetWorker, NMD, and NMO ............................................................................................................ 12 Configure the NetWorker resources .......................................................................................... 12 Configure the Schedule resource ........................................................................................... 12 Configure the Group resource ................................................................................................ 13 Configure the Client resource................................................................................................. 13 Set parameters in the NMD configuration file ............................................................................ 14 Configure the SA backups ......................................................................................................... 15 Configure the FTI backup .......................................................................................................... 15 Configure settings for an Oracle backup ................................................................................... 15 Link the NetWorker library with Oracle (Linux only) ............................................................... 15 Configure the Oracle parameters ........................................................................................... 15 Set Oracle parameters in the NMD configuration file ............................................................. 16 Perform a manual backup with the scope ALL .......................................................................... 17 Perform a scheduled backup with the scope ALL ..................................................................... 18

Relocated restore of the EMC Documentum Content Server with NetWorker, NMD, and NMO .................................................................................................. 18 Prepare the NetWorker server for restore ................................................................................. 18 Set parameters in the NMD configuration file ............................................................................ 19 Obtain the backup tag number from the backup index .............................................................. 19 Recover the Documentum components .................................................................................... 20 Restore the SA ....................................................................................................................... 20 Restore the FTI ...................................................................................................................... 20 Restore and recover the Oracle database ............................................................................. 21 Copy the Documentum security files ......................................................................................... 22

Validation of a successful relocation .............................................................. 22 Troubleshooting................................................................................................ 22 Conclusion ........................................................................................................ 23 References ........................................................................................................ 23

EMC Documentum Content Server Relocation Using the NetWorker Module for Documentum as a Data Mover Applied Technology

3

Executive summary The EMC® NetWorker® Module for Documentum® (NMD) is the NetWorker module that facilitates the backup and recovery of various objects of the EMC Documentum Content Server. The solution ensures the consistent backup of the EMC Documentum Content Server by backing up the data in a manner that ensures all the objects belong to the same point in time. NMD software provides a unique solution to relocate the EMC Documentum Content Server from one site to another by acting as a data mover to facilitate the movement. This white paper illustrates the procedure you should follow to relocate an existing Documentum setup from site A to site B by using NMD. NMD is used as a data mover to relocate the storage areas (SAs), fulltext indexes (FTIs), and Oracle® databases along with NetWorker and the NetWorker Module for Oracle.

Introduction This white paper provides information on how to perform a relocated recovery of an EMC Documentum Content Server repository from a source site to a target site by using NMD. It provides the detailed steps to restore the repository to a remote host.

Audience This white paper is meant for anyone who uses the NMD solution to back up an EMC Documentum Content Server. All users should have a basic understanding of the EMC Documentum Content Server and its components, such as repositories, FTIs, SAs, distributed storage areas (DSAs), databases, and NMD implementation.

Terminology CS: Content Server DSA: Distributed storage area, which enables the Content Server contents to be distributed across participating sites. FTI: Full-text index, which is an optional component that facilitates the creation and maintenance of indexes used for searching for specific values in a repository. ICF: EMC Documentum Content Server installation and configuration files. NMD: NetWorker Module for Documentum; the plug-in for NetWorker software that provides support for backup and recovery of different Documentum objects. RDBMS: Relational database management systems. Repository: Overall content management system, which is a grouping of different Content Server objects. SA: Storage area, which is a logical entity of the Content Server where the user contents can be stored.

EMC Documentum Content Server Relocation Using the NetWorker Module for Documentum as a Data Mover Applied Technology

4

Installation and configuration of EMC Documentum Content Server components EMC Documentum Content Server is an enterprise content management system that provides a systematic solution for organizing, storing, and delivering unstructured content within an enterprise. In the Content Server, the unstructured content is managed according to predefined business rules, policies, and procedures. The Content Server has a comprehensive, extensible, open, scalable, and secure architecture that meets the needs of global and distributed enterprises. EMC Documentum Content Server enables a user to: Create or import files of different formats Manage and track the different versions of a content file Create and manage virtual documents Add and remove renditions for a content file Index the content file contents for rapid searching The Content Server repository stores content in a unified environment. The repository is responsive to the business needs of an organization. This adaptive feature of the repository is useful for the enterprise that operates in multiple locations and requires a distributed repository or multiple repositories. The Content Server repository stores contents and its associated metadata using an object-oriented model. The documents within the repository are composed of content files and document attributes. The content can be of any form including: Text documents Spreadsheets Pictures XML files Web pages Full-motion video Streaming audio Instant messages E-mail messages Fixed content, such as reports, images, and scanned images The repository uses the attributes or metadata, such as the document owner, version, and creation date, to organize and search the content. The contents are stored in file systems, and the metadata is stored in tables underlying the relational databases. The Content Server can have more than one repository. A user accesses the contents of a repository through connection brokers. A connection broker is a process that enables clients to connect to the Content Server and, in turn, to a specific repository. A repository must have at least one connection broker so that users can access and manage the contents stored in the repository. A connection broker can project to n number of repositories, and vice versa. A repository consists of three main components: SA containing the contents, FTIs, and the RDBMS containing the metadata in the attribute tables. All components behave as a single entity from an application point of view. Additionally Content Server consists of installation and configuration files (ICF) that are installed on the file system during the Documentum server installation.

EMC Documentum Content Server Relocation Using the NetWorker Module for Documentum as a Data Mover Applied Technology

5

Figure 1. Three main components of an EMC Documentum repository SA: An SA contains the content files of all formats. Content Server supports different options of an SA. Users can choose any option, depending on the contents stored in the repository. Each SA points to a location where the contents are stored. The location can be a file system residing on the same host as the Content Server or on a remote host, any external storage device, or databases. RDBMS (attribute tables): Content attributes are stored in the tables of a relational database. Storing metadata in attribute tables enables rapid query and retrieval. For operational, performance, and security reasons, users can store all the content in the RDBMS. In addition, content assets can be stored as binary large objects (BLOBs) adjacent to attribute tables. EMC Documentum Content Server supports both local and remote RDBMS, such as Microsoft SQL Server, Oracle, Sybase, and DB2 databases. FTI (optional): EMC Documentum Content Server maintains an FTI for all the content stored in the repository. The FTI enables rapid search through a large collection of unstructured information. In addition to searching the text within the content, the FTI also searches content attributes. The indexed content can include documents, text files, XML components, HTML files, and closed-caption tracks of video files. The FAST index server is embedded in the EMC Documentum Content Server. When a document is added to the repository, the associated content files are added to the SA’s index the next time the index is updated. The FTI that is automatically created when the content is added to the repository contains all the words, keywords, and content attributes of the content stored in the repository.

EMC Documentum Content Server Relocation Using the NetWorker Module for Documentum as a Data Mover Applied Technology

6

Figure 2. EMC Documentum Content Server overview

Setup of the source host, target host, and NetWorker server The following sections describe the setup of the source host, target host, and NetWorker server for relocating the EMC Documentum Content Server from one site to another. These sections include details regarding a test setup that EMC used to validate the relocation procedure. The following figure provides an overview of the backup and recovery workflow that involves the source host, target host, and NetWorker server.

EMC Documentum Content Server Relocation Using the NetWorker Module for Documentum as a Data Mover Applied Technology

7

Figure 3. Overview of the backup and recovery workflow

Setup of the source host Follow these steps to set up the source host: 1.

Install and configure the Oracle database on the source host. Ensure that the supported Oracle patches are also installed. The test setup of the source host included the following details: Oracle instance: oracle Oracle username: sys Oracle password: oracle

2.

Install and configure the EMC Documentum Content Server. The test setup included the following details: Docbroker name: Docbroker Repository name: Docbase Repository ID: 111 Username: test Password: emclegato

3.

Install the NetWorker client software. The test setup included the NetWorker client release 7.5.2.

4.

Install NMD release 1.2 on the host where the EMC Documentum Content Server is installed.

5.

Install NetWorker Module for Oracle (NMO) release 5.0 on the host where Oracle is installed.

Note: To simplify the test setup, we installed Oracle on the same host where the EMC Documentum Content Server.

EMC Documentum Content Server Relocation Using the NetWorker Module for Documentum as a Data Mover Applied Technology

8

Setup of the target host Follow these steps to set up the target host: 1.

Install and configure the Oracle database on the target/destination host. Ensure that the target host has the same database version and patches installed as the source host. Create an Oracle instance with the same username, password, and instance name that you used on the source host. For example: Oracle instance: oracle Oracle username: sys Oracle password: oracle

2.

Install the EMC Documentum Content Server on the target host. For the Content Server configuration, create the repository copy. Ensure that you use the same repository name, repository ID, and repository owner name and password that you used in the production repository. For example: Docbroker name: Docbroker Repository name: Docbase Repository ID: 111 Username: test Password: emclegato

3.

Install the NetWorker client software. The test setup included the NetWorker client release 7.5.2.

4.

Install NMD release 1.2 on the host where you need to relocate the EMC Documentum Content Server

5.

Install NMO release 5.0 on the host where you need to relocate the RDBMS.

Setup of the NetWorker server Install the NetWorker server on the host from which you will perform backups and recovery of the data from the source host to the target host.

Prerequisites for relocating the Content Server Ensure that you meet these prerequisites for relocating the Content Server: The hostnames of the source host and target host are the same. The NetWorker client for the source host is configured in the NetWorker server by using the hostname, not the IP address. Note: You must create the indexes of the source NetWorker client with the hostname, not the IP address. The Oracle instance on the target host is the same as the instance on the source host. When you create the repository copy, use the same repository name, repository ID, repository owner name and password that you used in the production repository. Keep a copy of dbpasswd.txt and aek.key from the source Documentum setup: o

dbpasswd.txt is located in C:\Documentum\dba\config\Docbase.

o

aek.key is located in C:\Documentum\dba\secure.

Note: You will use these files to start the Content Server on the target host.

EMC Documentum Content Server Relocation Using the NetWorker Module for Documentum as a Data Mover Applied Technology

9

You can validate the successful backups and get the required information by following the steps below. After the backup is completed, run the list backup command from the RMAN prompt on the source host, and store the latest SCN number for the control files, database, and archive logs you will use during the recovery. The following shows a sample output from the list backup command:

Keep a copy of the DBID of the source Oracle database. You can obtain the DBID by running this command from the SQL prompt: SQL> SELECT DBID FROM V$DATABASE; The following shows sample output from the command:

EMC Documentum Content Server Relocation Using the NetWorker Module for Documentum as a Data Mover Applied Technology

10

On the source host, after the backup is completed, keep a copy of the piece handle of the database backup. You can find this in the NMD logs of the backup. The following samples show details from the NMD backup logs: 06/09/10 12:26:36 nsrnmdsv: input datafile fno=00004 name=C:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\USERS01.DBF 06/09/10 12:26:36 nsrnmdsv: channel t2: starting piece 1 at 09-JUN10 06/09/10 12:26:36 nsrnmdsv: channel t2: finished piece 1 at 09-JUN10 06/09/10 12:26:36 nsrnmdsv: piece handle=47lfq1pk_1_1 tag=TAG20100609T122524 comment=API Version 2.0,MMS Version 4.5.0.0 06/09/10 12:26:36 nsrnmdsv: piece handle=48lfq1qn_1_1 tag=TAG20100609T122524 comment=API Version 2.0,MMS Version 4.5.0.0 06/09/10 12:26:36 nsrnmdsv: Starting Control File and SPFILE Autobackup at 09-JUN-10 06/09/10 12:26:36 nsrnmdsv: piece handle=NMO_c-1237709418-2010060900/ comment=API Version 2.0,MMS Version 4.5.0.0

EMC Documentum Content Server Relocation Using the NetWorker Module for Documentum as a Data Mover Applied Technology

11

Backup of the EMC Documentum Content Server with NetWorker, NMD, and NMO The following sections describe the sequence of steps to configure and perform a backup of the EMC Documentum Content Server with the NetWorker, NMD, and NMO software.

Configure the NetWorker resources The following sections describe the configuration of the required NetWorker resources. For more information on how to use the NMC program to configure the NetWorker resources, refer to the EMC NetWorker Administration Guide and NetWorker Management Console (NMC) online help.

Configure the Schedule resource Configure the required NetWorker Schedule resource in NMC to automate scheduled backups. The backup levels specified in the Schedule resource determine the levels of the scheduled NMD backups, for example, level full, incremental, and so on.

Figure 4. Creating a Schedule resource in NMC

EMC Documentum Content Server Relocation Using the NetWorker Module for Documentum as a Data Mover Applied Technology

12

Configure the Group resource Configure the required NetWorker Group resource in NMC so that the scheduled backup of the NetWorker clients start to back up data at a specified time.

Figure 5. Creating a Group resource in NMC

Configure the Client resource Create the required NetWorker Client resource in NMC for the Documentum backup by setting the following attributes: Backup Command: nsrnmdsv –f configuration_file_path Save Set: DCB_repository_name

EMC Documentum Content Server Relocation Using the NetWorker Module for Documentum as a Data Mover Applied Technology

13

Figure 6. Creating a Client resource for NMD backup in NMC

Set parameters in the NMD configuration file During a backup or restore session, the NMD software uses the parameter settings in the configuration file, or the default values of parameters that are not set in the file. Set the required parameter values in the configuration file for an NMD backup or restore. Specify the configuration file pathname with the mandatory -f option of the nsrnmdsv (backup) or nsrnmdrs (restore) command. The EMC NetWorker Module for Documentum Multiplatform Version Administration Guide provides details on the parameters supported in the NMD configuration file. You must set up these mandatory parameters before performing a backup: DOCUMENTUM DOCUMENTUM_SHARED DM_HOME CLASSPATH JAVA_PATH LD_LIBRARY_PATH or LIBPATH or SHLIB_PATH PATH NMDDE_DM_DOCBASE NMDDE_DM_USER NMDDE_DM_PASSWD NMD_SCOPE EMC Documentum Content Server Relocation Using the NetWorker Module for Documentum as a Data Mover Applied Technology

14

NMD_OBJECT_NAME NSR_BACKUP_LEVEL NSR_CLIENT NSR_DATA_VOLUME_POOL NSR_GROUP NSR_SERVER

Configure the SA backups To configure the NMD configuration file for all SA backups, including FTI and database backups, set the required parameters in the file: NMDDE_DM_DOCBASE=Docbase NMD_SCOPE=ALL

Configure the FTI backup To configure the NMD configuration file for an FTI backup, set the required parameters in the file: NMD_FTI_INCLUDED=yes NMD_FTI_HOST=caper NMD_FTI_USER=ftiadmin NMD_FTI_NAME=rep_name_ftindex_01

Configure settings for an Oracle backup Once you have installed the NMO software, you must perform additional configurations for a successful Oracle backup, as described in the following sections.

Link the NetWorker library with Oracle (Linux only) On Linux only, link the NetWorker library with Oracle by using the following command: ln -s /usr/lib/libnwora.so $ORACLE_HOME/lib/libobk.so

Configure the Oracle parameters Use the nsrnmoadmin command to set the NSR_ORACLECAT_MODE, NSR_REMOVE_ON_FAILURE, NSR_ORACLE_SID, NSR_ORACLE_HOME, and NSR_ORACLE_CONNECT_FILE parameters. The EMC NetWorker Module for Oracle Administration Guide provides more details regarding these parameters and gives users information about how to use the nsrnmoadmin command. For example, run the following nsrnmoadmin commands to set the parameters: nsrnmoadmin -r list nsrnmoadmin -r update NSR_ORACLECAT_MODE=enabled nsrnmoadmin -r update NSR_REMOVE_ON_FAILURE=TRUE nsrnmoadmin -r add sid=orcl home=c:\Oracle_home connect=c:\connect.txt

EMC Documentum Content Server Relocation Using the NetWorker Module for Documentum as a Data Mover Applied Technology

15

The following shows the content of a sample connect.txt file: connect target sys/oracle@oracle The following shows a sample output from the nsrnmoadmin –r list command:

Figure 7. Sample nsrnmoadmin –r list command

Set Oracle parameters in the NMD configuration file Set the following parameters in the NMD configuration file for an Oracle database backup: NMD_DB_FULL_BACKUP_CMD=nsrnmddbf.sh (script to perform full backups of database) NMD_DB_LOG_BACKUP_CMD=nsrnmddbl.sh (script to perform database log backups) NMD_DB_INCR_BACKUP_CMD=nsrnmddbi.sh (script to perform incremental backups of database)

The following are sample scripts to perform a full database backup: nsrnmddbf.sh -----------------------------------------------------------------------------------------------------call "C:\Program Files\Legato\nsr\bin\nsrnmo.bat" -s manis -g NMD -m caper RMAN:C:\scripts\rmanfull.txt set rc=%errorlevel% if "%rc%" == "0" ( echo ##completed ) exit %rc%

EMC Documentum Content Server Relocation Using the NetWorker Module for Documentum as a Data Mover Applied Technology

16

nsrnmddbl.sh -----------------------------------------------------------------------------------------------------call "C:\Program Files\Legato\nsr\bin\nsrnmo.bat" -s manis -g NMD -m caper RMAN:C:\scripts\rmanlog.txt set rc=%errorlevel% if "%rc%" == "0" ( echo ##completed ) exit %rc%

rmanfull.txt -----------------------------------------------------------------------------------------------------connect target sys/orcl@orcl run { allocate channel t2 type SBT_TAPE; BACKUP FULL DATABASE INCLUDE CURRENT CONTROLFILE; release channel t2; }

rmanlog.txt -----------------------------------------------------------------------------------------------------connect target sys/orcl@orcl run { allocate channel t2 type SBT; send 'ENV=(NSR_SERVER=manis,NSR_CLIENT=caper)'; BACKUP ARCHIVELOG ALL; release channel t2; } Note: You should enable the autobackup option on the source database. Ensure that the control files that were backed up have the latest information about the archive logs. Alternatively, you can use the Recovery Catalog.

Perform a manual backup with the scope ALL Both manual and scheduled backups invoke the nsrnmdsv process, which uses the mandatory -f option of the nsrnmdsv command to locate the NMD configuration file.

EMC Documentum Content Server Relocation Using the NetWorker Module for Documentum as a Data Mover Applied Technology

17

For example, an NMD backup of scope ALL performs all the SA, FTI, and database backups in turn. You must set the parameters for all these component backups as they were described in the preceding sections. The scope ALL must be set with the NMD_SCOPE parameter in the configuration file: NMD_SCOPE=ALL After all the required parameters are set, run the following command to perform the manual backup: nsrnmdsv –f NMD_configuration_file_path

Perform a scheduled backup with the scope ALL To perform a scheduled backup, start the backup group (configured with the NMD client) in NMC, or run the following command: savegrp –G group_name Note: The NMD client must be configured in NMC according to the instructions in the “Backup of the EMC Documentum Content Server with NetWorker, NMD, and NMO” section.

Relocated restore of the EMC Documentum Content Server with NetWorker, NMD, and NMO The following sections describe the sequence of steps to configure and perform a relocated restore of the EMC Documentum Content Server with the NetWorker, NMD, and NMO software.

Prepare the NetWorker server for restore To perform a relocated recovery of the Documentum components, you must perform a backup from the source host and then recover the data to the target host by using NMD. You must configure the NetWorker Client resource by using the required hostname. To recover the data to the target host, you can use either the same NetWorker server that was used for backup or a new NetWorker server. To use the existing NetWorker server, use the workflow described as follows. Once the backup is completed, perform the following steps so that the NetWorker server properly resolves the target host for recovery: 1.

Stop the services on the NetWorker server.

2.

Change the etc/hosts entry from the source host IP to the target host IP, assuming that the hosts are in the workgroup.

3.

Run the ipconfig /flushdns command on Windows only.

4.

Restart the NetWorker server services.

Note: If you are also performing a disaster recovery of the NetWorker server, you do not need to perform the steps that recognize the target host because the server will recognize the IP address of the target host as soon as it comes up. After you follow the normal disaster recovery steps for the NetWorker server and ship the backup devices from the source to the targe, run the scanner command. All the subsequent steps remain the same.

Example: The sample hosts have the following hostnames and IP addresses: Source: caper: 10.31.192.96 NetWorker server: manis: 10.31.192.97 EMC Documentum Content Server Relocation Using the NetWorker Module for Documentum as a Data Mover Applied Technology

18

Target: caper: 10.31.192.98 Note: Since the source and target hosts have the same hostname, both hosts cannot be up and running at the same time on the same network.

Once the backup on the source (caper 10.31.192.96) is completed, you must perform the following: 1.

Stop the services on the NetWorker server (manis 10.31.192.97).

2.

Change this entry in etc/hosts: 10.31.192.96 caper Change the entry to the following: 10.31.192.98 caper

3.

Run the ipconfig /flushdns command.

4.

Restart the NetWorker server services.

Set parameters in the NMD configuration file You must set the required parameter values in the NMD configuration file for the restore. The EMC NetWorker Module for Documentum Multiplatform Version Administration Guide provides more details on the parameters supported in the NMD configuration file. You can use the same NMD configuration file that you used for the backup. Before starting the restore with the nsrnmdrs command, set the following parameters in the NMD configuration file: NSR_CLIENT=target_Documentum_Content_Server_hostname NSR_CONFLICT_PROMPT=R NSR_DEBUG_FILE=C:\restore\nmd_restore_D9.log NSR_DEBUG_LEVEL=9 NSR_PARALLELISM=16 NSR_RELOCATION=c:\relocate NSR_SERVER=NetWorker_server_hostname NSR_FTI_RELOCATION=c:\relocate\fti

Obtain the backup tag number from the backup index Run the nsrnmdnx command on the EMC Documentum Content Server to browse the backup index. Select the correct Documentum repository backup that includes all the SAs, all the FTIs, and the database. Run the following command to obtain the tag number of an SA that was backed up: # nsrnmdnx –B repository_name -c client_name -s NetWorker_server_name where: repository_name is the name of the repository to be recovered. client_name is the hostname of the Documentum client that was originally backed up. NetWorker_server_name is the hostname of the backup server where the recovery is performed.

EMC Documentum Content Server Relocation Using the NetWorker Module for Documentum as a Data Mover Applied Technology

19

The following shows a sample output from the nsrnmdnx command:

Figure 8. Sample nsrnmdnx command

Recover the Documentum components Perform the recovery of the Documentum components in the order described in the following sections.

Restore the SA Run the following command to recover the Documentum SA on the Documentum server: # nsrnmdrs –B repository_name –f configuration_file_path –C SA –T 1240329719 –c client_name –s NetWorker_server_name Read the information about the components selected for restore, and type y to proceed with the Documentum system restore. After you have successfully completed the restore, verify that the SA was restored properly.

Restore the FTI Run the following command to recover the Documentum FTI on the Documentum server: # nsrnmdrs –B repository_name –f configuration_file_path –C FTI –T 1240329719 –c client_name –s NetWorker_server_name Read the information about the components selected for restore, and type y to proceed with the Documentum system restore. After you have successfully completed the restore, verify that the FTI was restored properly.

EMC Documentum Content Server Relocation Using the NetWorker Module for Documentum as a Data Mover Applied Technology

20

Restore and recover the Oracle database Restore and recover the Oracle database by using the appropriate RMAN commands: 1.

Shut down the Oracle instance on the target host.

2.

Rename or move all the original files in the oradata directory of the Oracle instance. For example, rename or relocate files under C:\oracle\product\10.2.0\oradata\instance_name.

3.

Start the Oracle database instance with the nomount option.

4.

Use the following script to recover the SP files and control files: connect target sys/orcl; run { set DBID 12341232 Note: This should be run in the shell where you start the Oracle RMAN prompt. allocate channel t1 type 'SBT_TAPE' parms 'ENV=(NSR_SERVER=manis,NSR_CLIENT=caper)'; restore controlfile from 'NMO_c-1237709418-20100414-01/'; release channel t1; } Note: You can obtain the tag NMO_c-1237709418-20100414-01 from the applogs log file (for example, nmd_db9.log) that was created during the backup. Select the tag from the latest control file backup. The section “Prerequisites for relocating the Content Server” provides more details. After the recovery of the control files, you should be able to see the backups by issuing the command list backup at the RMAN prompt. The following shows a sample output from the list backup command:

Figure 9. Sample list backup command 5.

Use the following script to restore and recover the Oracle database: connect target sys/orcl@orcl; run {

EMC Documentum Content Server Relocation Using the NetWorker Module for Documentum as a Data Mover Applied Technology

21

allocate channel t1 type 'SBT_TAPE' parms 'ENV=(NSR_SERVER=manis, NSR_CLIENT=caper)'; restore database; set until scn 6661087; recover database; release channel t1; } Note: See the “Prerequisites for relocating the Content Server” section for details on how to obtain the SCN number. 6.

Use the following script to restore the archive logs: connect target sys/oracle run { allocate channel t1 type 'SBT_TAPE'; send 'ENV=(NSR_SERVER=manis,NSR_CLIENT=caper)'; restore archivelog from scn=1457080 until scn=1462335; release channel t1; }

Copy the Documentum security files Replace the aek.key and the dbpasswd.txt on the target host with the corresponding files that you copied from the source host.

Validation of a successful relocation Perform the following actions to validate the relocated restore of the EMC Documentum Content Server: 1.

Start the Oracle instance, docbroker, and docbase. Ensure that there are no errors in starting all these components.

2.

Launch DA for the target Documentum setup, and ensure that the SAs that were created in the source repository are visible in the target Documentum repository,

3.

Access the files and folders that were uploaded in the source repository. Ensure that the same files and folders are accessible in the target repository.

4.

Perform a backup of the EMC Documentum Content Server on the target host.

Troubleshooting The following are sample error messages, including the solutions for the errors: Error: The NW authentication for client 'client_name' was refused by server 'source_server_name' because 'client target_client_name' is not properly configured on the NetWorker Server' . (lnm_index_cfx_pconn|2|12|0) Solution: EMC Documentum Content Server Relocation Using the NetWorker Module for Documentum as a Data Mover Applied Technology

22

Stop the nsrd services on the NetWorker server, and run ipconfig /flushdns. Start the NetWorker services, and run the command again. Error: [DM_SESSION_I_INIT_BEGIN]info: "Initialize Crypto Objects." [DM_SESSION_E_INIT_FAILURE1]error: "Failure to complete Crypto Objects initialization." [DM_SERVER_I_START_ID]info: "Docbase repos01 was not successfully opened. Docbase id: (111)" Solution: Shut down the target Documentum Content Server, and copy the files aek.key and dbpasswd.txt from the source setup to the target setup. If you refer to the “Prerequisites for relocating the Content Server” section, you should have a copy of these files from the source setup in order to bring up a copy of the same setup.

Conclusion The NMD software is the perfect solution to move data in order to relocate the EMC Documentum Content Server from one host to another. When you follow the required rules to back up different components in a specific manner, this solution ensures the consistency of the backup images and restores all the components to a remote site as an exact replica of the source Documentum setup.

References The following documents provide more information: EMC Documentum Content Server 6.5 Administration Guide EMC Documentum Content Server 6.5 SP2 Installation Guide EMC NetWorker Module for Documentum Release 1.2 Multiplatform Version Administration Guide EMC NetWorker Module for Documentum Release 1.2 Multiplatform Version Installation Guide EMC NetWorker Module for Documentum Release 1.2 Multiplatform Version Best Practices Guide Backup and Recovery of EMC Documentum Content Server Using the NetWorker Module for Documentum

EMC Documentum Content Server Relocation Using the NetWorker Module for Documentum as a Data Mover Applied Technology

23