star-rm-300-010-267

EMC® Replication ManagerVersion 5.2.3

Release NotesP/N 300-010-267

Rev A01

February 3, 2010

These release notes contain supplemental information about EMC Replication Manager version 5.2.3. Topics include:

◆ Revision history .................................................................................... 2◆ Product description.............................................................................. 2◆ New features and changes .................................................................. 3◆ Fixed problems ..................................................................................... 4◆ Environment and system requirements .......................................... 17◆ Known problems and limitations .................................................... 17◆ Technical notes .................................................................................... 18◆ Documentation ................................................................................... 20◆ Software media, organization, and files.......................................... 20◆ Installation........................................................................................... 21◆ Troubleshooting and getting help .................................................... 28

1

2

Revision history

Revision historyThe following table presents the revision history of this document.

A01 February 3, 2010 Release notes for Replication Manager Version 5.2.3.

Product descriptionThe EMC® Replication Manager product creates point-in-time replicas of databases or file systems residing on supported storage arrays. Replicas can be stored on Symmetrix® arrays using TimeFinder®/ Mirror, TimeFinder/Clone, or TimeFinder/Snap (VDEVs); CLARiiON® arrays using SnapView clones, snapshots, or SAN Copy™; iSCSI Celerra arrays Celerra® SnapSure™ local snapshots, Celerra Replicator™ remote snapshots, Celerra NFS, Invista® clones, and the RecoverPoint family in Symmetrix or CLARiiON environments.

Replication Manager allows you to perform local and remote replications using TimeFinder, Symmetrix Remote Data Facility (SRDF®)/Synchronous, SRDF/Asynchronous, SAN Copy, Navisphere® , Celerra iSCSI, Celerra NFS, and/or replicas of MirrorView™/S and MirrorView/A secondaries using SnapView™/Snap and SnapView/Clone replication technologies where they are appropriate.

Replication Manager provides application integration with Oracle, UDB, Microsoft SQL Server, Microsoft Exchange, and Microsoft SharePoint to create replicas simply, quickly, and automatically. In fact, it automates all the important procedures related to data replication.

Revision Date Description

EMC Replication Manager Version 5.2.3 Release Notes

New features and changes

New features and changesReplication Manager 5.2.3 includes the following new features and changes. The Replication Manager documentation and the EMC Replication Manager Support Matrix describe the features and supported configurations in detail:

◆ Support for Exchange 2010 databases in standalone as well as Database Availability Group (DAG) configurations

◆ SharePoint 2007 full farm restore

◆ RecoverPoint failover tolerance for Replication Manager application sets and jobs

◆ Support for RecoverPoint consistency groups managed by RecoverPoint/CE or Site Recovery Manager

◆ Enhanced array and host level versioning information in the Replication Manager Console

◆ For Oracle installations on Celerra NFS in a Linux environment, support for RMAN integration including the ability to catalog replicas with RMAN

◆ Ability to perform Celerra NFS filesystem mount and Celerra NFS datastore mount on alternate network interface

◆ Support for AIX VIO environments

◆ Symmetrix long duration locks (LDL) no longer enabled by default

◆ Support for restoring a replica made on a Solaris host using VERITAS Quick I/O to a Solaris host where Quick I/O is not installed

◆ Fixed problems

End of support With the release of Replication Manager 5.2 SP2 (the previous release), EMC announced termination of support for the following:

◆ Windows Server 2000 as a host OS for Replication Manager Server

◆ Any IA64 platform as a host for Replication Manager Server

Migration of an existing Replication Manager Server to a new host should be performed by EMC customer service only. Customer

3EMC Replication Manager Version 5.2.3 Release Notes

4

Fixed problems

service should refer to EMC Knowledgebase solution emc218841 for the migration procedure.

Fixed problemsThis section lists problems fixed in releases after Version 5.2.0. Refer to the EMC Replication Manager 5.2.0 Release Notes for a list of problems fixed in that release.

Problems fixed in 5.2.3This section lists the problems that were fixed in Replication Manager 5.2.3.

Storage discovery of CLARiiON array stopped responding (068268)This release fixes the problem that in some circumstances caused storage discovery for a CLARiiON array to stop responding.

Mount error 100748 ERROR:Attempt to mount file system filesystem has failed (067624)This release fixes AIX mount problems that returned the error “100748 ERROR:Attempt to mount file system filesystem has failed” by adding support for CIO-enabled JFS/JFS2 file systems on AIX.

Upgrade to 5.2 SP2 failed with "SOLID System Fatal Error 11019: License is not valid for this server version” (067359)

This release fixes the problem that caused an upgrade to fail with the error "SOLID System Fatal Error 11019: License is not valid for this server version”.

Static snapshot mounts left stray CLARiiON snapshots (067302)This release fixes the problem that caused static snapshot mounts to leave stray CLARiiON snapshots with a name ending in "_Expired" on the array after a mount.

Job failed with 000033 ERROR: Function SwecheckMVA_or_MVS (067243)This release fixes the issue with MirrorView replications when the application resided on LUN 0.


Fixed problems

Job properties’ Storage tab values were not preserved (066991)This release fixes the problem that prevented values in the Storage tab of job properties from being retained when the user moved to a different tab.

Oracle mount failed with error that the ASM init file already exists on the target RAC node (066563)

This release fixes the problem related to the system language setting that led to a false detection of the ASM init file on the target RAC node and resulted in Oracle mount failure.

Failed to recover Oracle on mount in RMAN environment where SBT_TAPE was set (066305)This release fixes the problem that prevented Oracle recovery on mount in an RMAN environment in which the SBT_TAPE parameter was set. In addition to installing this release of Replication Manager, you need to follow the procedures described in EMC Knowledgebase article emc226300.

Snapshots not cleaned up after failed Celerra replication (066295)This fix addresses a problem in which a failed Celerra replication could leave snapshots on the Celerra that were not cleaned up by Replication Manager.

Unable to create an application set for SQL Server (066265)This release fixes the problem that prevented creation of a SQL Server application set when the Server was at Version 5.2.2 and the client at Version 5.2.1.

Mount of snap LUNs on Windows 2008 VM failed with error "000382 ERROR:No storage group could be located for host host on CLARiiON" (066215)

This release fixes the problem that caused mount of SnapView snaps on a Windows 2008 VM mount host to fail.

Celerra Replicator iSCSI loopback replication failed with SNAPAPI_NOT_CONNECTED error (066164)

This release fixes the problem that caused a Celerra Replicator iSCSI loopback replication to fail with a SNAPAPI_NOT_CONNECTED error.


6

Fixed problems

MirrorView replication failed with 000708 ERROR:This is a REMOTE replication, but no remote node exists in the source node for source (066007, 066840, 067031)

This release fixes the problem that caused MirrorView replication to fail with 000708 ERROR:This is a REMOTE replication, but no remote node exists in the source node for source.

MirrorView job failed and update CLARiiON array properties failed (065942)This release fixes a problem related to Replication Manager’s detection of MirrorView enablers that caused MirrorView jobs to fail, and CLARiiON array properties to be displayed incorrectly.

Celerra incremental job failed (065814)This release fixes the problem that caused the act of deleting a Celerra Replicator replica to incorrectly delete the Replicator session, and forcing the next replica to be a full copy instead of an incremental copy.

Restore of SFRAC Oracle database failed intermittently with cluster reservation failed for volume error (065803)

This release fixes the problem that caused restore of SFRAC Oracle database to fail intermittently because remote nodes could not be unmounted. It adds customer service-only environment variables to add a series of waits and retries to the remote unmount commands used in SFRAC environments, allowing remotely mounted systems ample time to fill the unmount request from the parent node. Customer service should refer to EMC Knowledgebase solution emc225969.

Jobs stopped responding during storage selection phase when multiple jobs ran at same time (065779)

This release fixes the problem that caused jobs to stop responding during the storage selection phase when multiple jobs ran at the same time.

Oracle job failed with "000221 ERROR:Required file not found on the system: /opt/oracle/db/10.2.0/dbs/orapw" (065177)

This release fixes the problem related to the host locale setting that caused Oracle jobs to fail with the error "000221 ERROR:Required file not found on the system: /opt/oracle/db/10.2.0/dbs/orapw".

Oracle mount recovery failure: ORA-00205: error in identifying control file (065100)This release fixes a problem that Oracle recovery mounts to fail. The problem occurred with Linux ASM on ASMLib replicas. The actual


Fixed problems

cause of the failure was ASM devices managed by ASMLib being owned by an OS user different from the mounted instance.

Support for SRDF/Star configurations (064875)This release enables Symmetrix replications in an SRDF/Star configuration. In addition to installing this version of Replication Manager, contact EMC customer service and refer to EMC Knowledgebase article emc229416.

Replication on a non-English Windows host failed with error “No iSCSI initiator found on the local host” (064320)

This release fixes the problem that caused replication on a German Windows host to fail with the error “No iSCSI initiator found on the local host”. The fix may also apply to non-English Windows versions other than German.

Every other linked job failed in CCR clustered environment (063640)This release fixes the problem that caused every other linked job to fail in a CCR clustered environment.

Console did not update job’s Latest Status and Last Run Time values (063580)This release fixes the problem that prevented the Replication Manager Console from updating a job’s Latest Status and Last Run Time values when viewed by a user running with the Operator role.


Replication failed intermittently with “000209 ERROR:The discovery phase could not build the browse tree” (064120)

This release fixes the problem that caused replications to fail intermittently with the message “000209 ERROR:The discovery phase could not build the browse tree.”

Replication Manager was unable to release the IBM UDB database after replication (063682)

This release fixes the problem that caused sporadic errors at the end of UDB replications.


8

Fixed problems

Celerra Replicator snap jobs failed (063236, 064344)This release fixes the problem that caused Celerra Replicator snap jobs to fail in a configuration with a poor quality network.

Replication Manager Client service terminated unexpectedly, faulting module ntdll.dll (063192)

This release fixes the problem related to Replication Manager hotfix URM00057359 that caused the Replication Manager Client service to fail with the error “faulting module ntdll.dll” .

Replication Manager failed to purge storage on Celerra when it deleted snaps (063013)This release fixes the problem specific to VMFS LUNs that prevented Replication Manager from purging storage on Celerra when it deleted Replication Manager snaps.

Replication Manager Console did not display Navisphere Secure CLI version (062741)This release fixes the problem that prevented the Replication Manager Console from displaying the Navisphere Secure CLI version in host properties.

Job failed with “IRD Size Mismatch in meta member” error (062737)This release fixes the problem that caused the failure of a job using a metadevice that contained a very large number of members.

Repeated mount of same CLARiiON snap failed (062687)This release fixes the problem that caused the failure of a second mount of a CLARiiON snap replica, including failures to activate the snapshot and add it to a storage group.

Remote Celerra replication failed (062661, 062573)This release fixes the problem that caused remote Celerra replication to fail unless the remote datamover could be accessed from the Replication Manager production host.

Unmounting replicas on AIX 6.1 host left hdiskpower devices in a Defined state (062371)This release fixes the problem that caused AIX 6.1 hosts to leave hdiskpower devices in a Defined state after an unmount.

Replication Manager Server service took a long time to start with very large number of replicas (062279)

This release fixes the problem that caused Replication Manager Server service to take a long time to start when there was a very large number of replicas in the internal database.


Fixed problems

Resolved issues with Oracle mounts in recover mode (062172)This defect resolves an issue that prevented Replication Manager from creating temporary tablespaces for Oracle during a mount with recovery. The version of Oracle in use requires a size that ends with K or M (Kilobytes or Megabytes) in the ALTER TABLESPACE command issued. If the temporary size is represented in gigabytes (G) the command fails to create the tablespace. This fix performs the conversion.

Celerra replicas were being removed from the array incorrectly but were still showing as existing in Replication Manager (062063)

This release fixes the problem for sites using time-based rotation instead of replica count-based rotation, in which a failed CelerraReplicator job could allow the clone replica to be expired. The next time a CelerraReplicator job ran, it would recreate the clone replica, but it would have an incorrect internal counter, which could cause the session to be deleted.

Exchange CCR node-based jobs required two licenses (061260)This release fixes the problem that caused Exchange CCR node-based jobs to require two licenses, when only one license should have been required.

Oracle replication failed due to timeout issue (061778)This release fixes a problem that caused Oracle replications to fail due to a timeout issue, with “Error reading response from pipe - 026554 ERROR:The log switch operation failed (Pipe error in HPUX)”.

Hostname issue on HP-UX client crashed Replication Manager client daemon (061749)This release fixes a problem on HP-UX clients relating to the length of the hostname that caused Replication Manager client daemon (irccd) to crash.

Exchange backup failed with "100722 ERROR:waiting 1200 seconds for BackupComplete to complete. BackupComplete was cancelled" (061737)

This release adds a customer service-only environment variable for Exchange 2003 that overrides the default backup completion wait time of 20 minutes to prevent backups from failing due to timeout.

RM CLI mount script failed with 026433 ERROR: The IRDB fetch failed for hostname with the following error: Host not found in DB (061460)

This release fixes the problem that caused RM CLI mount scripts to failed with the error “026433 ERROR: The IRDB fetch failed for


10

Fixed problems

hostname with the following error: Host not found in DB” when a domain name was specified during host registration.

Mount failed when clone device became invisible after originally being visible (061287)This release fixes the problem that caused a clone to be visible to Replication Manager, then become invisible and causing a mount to fail.

Replication Manager Console stopped responding when accessing mount options for an Exchange job (061266)

This release fixes the problem that caused the Replication Manager Console to stop responding when accessing mount options for an Exchange job where both Windows 2000 and non-Windows 2000 hosts were involved.

Replication failed with VSS_UNKNOWN ERROR (060983)This release fixes the problem that caused replications to fail with the error “027275 ERROR:A VSS_UNKNOWN_ERROR error occurred while setting the context for the VSS shadow copy.”

"Function purgeSnapshot failed with an error as follows: NBS Err:NBS_EBUSY" error after successful Celerra Replicator job(060936)

This release fixes the problem that caused the incorrect display of the error “Function purgeSnapshot failed with an error as follows: NBS Err:NBS_EBUSY” after a successful Celerra Replicator job.

Oracle ASM RAC job failed with error “Storage device undefined replication object could not be located on supported arrays” (060916)

This release fixes the problem that caused an Oracle ASM RAC job to fail with the error “000600 ERROR:Storage device undefined replication object could not be located on supported arrays.”

Replication Manager client security vulnerability resolved (060704)This release fixes a security vulnerability in the Replication Manager client. Refer to the EMC Security Advisory (ESA-09-010) for more information.

MirrorView Oracle snap job failed with "Validate failed" error (060668)This release fixes a problem that caused a MirrorView Oracle snap job to fail with a “Cannot determine user's temporary tablespace” error.


Fixed problems

Fibre-attached tape device failed on Solaris host (060601)This release fixes a problem that caused Replication Manager to configure a controller that did not have a disk on it, causing problems with fibre-attached tape devices.

Loopback replication using Celerra Replicator failed (060470)This release fixes the problem that caused loopback replications using Celerra Replicator to fail.

CLARiiON copy job failed with “000399 ERROR:Failed to make all LUNs visible to the host after 120 seconds” (060435)

This release fixes the problem that caused the error "000399 ERROR:Failed to make all LUNs visible to the host after 120 seconds" when multiple copy jobs started at same time and from the same source.

Oracle job failed with 026565 ERROR:Oracle query or command returns error: SESSIONID failed (060291)

This release fixes the problem that caused Oracle replications to fail with the error “Error reading response from pipe”.

Replication Manager Client daemon (irccd) memory leak on HP-UX (060193)This release contains fixes for Replication Manager Client daemon (irccd) memory leaks on HP-UX clients.

Host name containing dashes caused snapshot-based replications to fail (060163)This release fixes the problem that caused snapshot-based replications to fail when the host name had dashes (-).

CLARiiON: Second copy job failed with “ERROR:Unable to complete the replication because application set is active in some other operation” (060044)

This release fixes the problem that caused the second copy job to fail with “000111 ERROR:Unable to complete the replication because application set app_set is active in some other operation” when two copy jobs were started at the same time.

Could not discover CLARiiON when SnapView Enabler was not installed (060041)This release fixes the problem that prevented Replication Manager from discovering CLARiiON storage when SnapView Enabler was not installed on the CLARiiON.


12

Fixed problems

VMFS job failed with "000600 storage device could not be located on supported arrays" error (059866)

This release fixes the problem that caused a VMFS job to fail with a “storage device could not be located on supported arrays” error because Replication Manager tried to resolve storage using a disconnected ESX host.

Mount options did not list all backup hosts (059713)This release fixes the problem that prevented backup hosts that were not on the same platform as the production host from being listed in the mount options window.

Oracle replication failed when archive logs were included in the job (059643)This release fixes the problem that caused Oracle replications to fail when archive logs were included in the job.

Unable to execute RM CLI init file because file not found (059538)This release fixes the problem that prevented Replication Manager from finding the RM CLI init file.

Exchange replications failed with "Index n is out of bounds" error (059545)This release fixes the problem that caused Exchange replications to fail with the error “Index n is out of bounds”.

CLARiiON VSS mounts failed when source LUN corresponded to LUN 0 (059338)This release fixes a problem that caused CLARiiON VSS mount failures on the mount host when the source LUN corresponded to LUN 0.

RMCLI mount script failed with “No valid value found for job argument - job not found” error (059334)

This release fixes the problem that prevented use of the CLI to mount a replica from an application set that was created by an account other than the Administrator account.

Every other CLARiiON snap of clone mount failed on Linux hosts (059198)This release fixes the problem that caused every other CLARiiON snap of clone mount to fail for Linux hosts.

Improved consistency between the Replication Manager Console and CLI (059108)This release resolves some inconsistencies that existed between the Replication Manager Console and the command line interface.


Fixed problems

Unmount failure resolved “unable to find the snap on the mount host” in a VMware VMFS environment (059105)

This release fixes a problem that was preventing Replication Manager from unmounting snap replicas of VMware VMFS.

Restore from mounted RecoverPoint replica failed with 005049 error "Job failed attempting to perform recovery operation to RPA: Error Code 2” (058645)

This problem is resolved as unable to reproduce.

Windows scheduler tasks are no longer removed when a Windows user is removed (058264)

This release fixes a problem that caused all tasks to be removed from the Windows Scheduler if a user who created one of those tasks was removed.

Replication Manager Client service crashed due to memory leak (057359)This release fixes memory leaks on Windows platforms that caused the Replication Manager Client service (irccd) to crash.

AIX mount and unmount performance issue resolved (056821)This release fixes a performance problem that caused mounts and unmounts on AIX systems to take longer than necessary.

Mounts no longer fail on Solaris mount hosts with Veritas Volume Manager (055865)In previous releases, Replication Manager mounts on Solaris using Veritas Volume Manager would sometimes fail. This issue occurred when Replication Manager could not identify all the LUNs that are part of a replica. This fix enables Replication Manager to perform a rescan of the device paths if it finds that not all DMP paths have been initially recognized.

Jobs failed with intermittent "xferfile:poll - poll connection timed out" errors (053400)This release fixes the problem that caused intermittent failures ("xferfile:poll - poll connection timed out") in transferring Replication Manager metadata files between Replication Manager clients and the server on an unreliable network.

Resolution of memory leaks in Replication Manager Server (052585)This release fixes memory leak issues with Replication Manager Server service (ird.exe) in highly stressed environments.


14

Fixed problems


Mount of snap of clone replica failed every other time (058793)This release fixes the problem that caused the mount of a snap of clone replica to fail every other time.

SQL Server replication failed with error “Login failed for user NT AUTHORITY\SYSTEM” (058417)

This release fixes the problem with failed SQL Server replications when a non-administrator domain account, which was a member of the local Administrators group on the source host, was used as the SQL Server user in Replication Manager, and NT AUTHORITY\SYSTEM and BUILTIN\Administrators were not defined as SQL Server users on the production and mount hosts.

Replication Manager Client service crashed during storage discovery (058307)This release fixes a problem that caused Replication Manager Client service (irccd) to crash during storage discovery if there was a CLARiiON connected that had not been configured in the Replication Manager Console.

Mount failed when a storage group contained both iSCSI and fibre devices (058229)This releases fixes the mount problem that occurred when a storage group contained both iSCSI and fibre attached devices.

Symmetrix job failed with error: “Replica was not created pre-migration; it will be invalidated” (057435)

This release fixes the problem that caused a Symmetrix job to fail with the error: “Replica was not created pre-migration; it will be invalidated.”

Oracle replications failed with error ORA-01990: error opening password file (057179)This release fixes the problem that caused the following error to occur when the production instance was restarted by the user: “ORA-01990: error opening password file.”

Incorrect permissions granted to Oracle files and directories on AIX following a restore (057175)

This release fixes the problem that granted incorrect permissions to Oracle files and directories on AIX following a restore.


Fixed problems

LUN surfacing issue on VMware virtual disk mount (056813)This release fixes the problem that caused a LUN surfacing issue during a VMware virtual disk mount in a CLARiiON environment.

Job blocked by VSS lock on mount host was held throughout unmount (056797)This release fixes a problem where the VSS lock on the mount host was being held throughout the unmount action. This prevented other mounts from completing. A long running script during callout 1500 aggravated the problem.

Symmetrix-to-CLARiiON SAN Copy replications failed (056725)This release fixes the problem that caused Symmetrix-to-CLARiiON SAN Copy replications to fail when the host seeing the Symmetrix array did not see a CLARiiON array.

Jobs failed due to intermittent connection failures between Replication Manager Server and Client (056329)

Intermittent connection failures occurred between the Replication Manager Server and Client when multiple jobs ran at the same time, causing jobs to fail. This release fixes the problem.

Installation failure in SRDF/CE clustered environment (056249)This release fixes problems related to installation of multiple Replication Manager components (agent, server, console) when installing in an SRDF/CE clustered environment.

Oracle replication failed with error “Unable to access password file, error 22 (EINVAL)” (055346)

This release fixes the problem that caused Oracle 10.2 replicas to fail with the error “Unable to access password file, error 22 (EINVAL).”

Symmetrix storage discovery failed with “000033 ERROR:Function GetCloneDevices failed” if there were no clone devices (054663)

This release fixes the problem that caused Symmetrix storage discovery to fail with the error “000033 ERROR:Function GetCloneDevices failed” if there were no clone devices in the array.

Missing Oracle information in History log and the output for callout script 600 (054251)This release fixes the problems related to missing Oracle information in the History log and the output from callout script 600. The History log will now display information of all the archive logs transferred. The output of the callout script 600 will now correctly contain information regarding the ASM instance generated by Replication


16

Fixed problems

Manager for the mount host, all the archive logs and details of the password file transferred to the mount host.

Oracle ASM job failed connecting to RMAN instance with “copyArchivedLogsUsingRMAN failed” error (053478)

This release fixes the problem that caused ASM replications to fail with the error “copyArchivedLogsUsingRMAN failed” when the connection to the RMAN instance could not be initiated.

Unable to create Oracle application set on Solaris due to password issue (052311)This release fixes the password problem related to MD5 hashing that prevented creation of an Oracle application set on Solaris.

Deletion of Celerra snapshots too slow (051040)With DART 5.6.41 and later, Replication Manager can perform a synchronous removal of all the resources for a deleted snapshot replica, ensuring that the resources have been removed before creating a new snap. With earlier DART versions, the CC_CELERRA_ROTATION_SECS_DELAY environment variable can be used to introduce a delay between the deletion of an old snap replica, and the creation of a new snap replica to reduce the risk of failure when performing this asynchronous deletion.


Environment and system requirements

Environment and system requirementsVerify that you are using supported platforms and that the hosts meet all requirements.

The Replication Manager Support Matrix provides specific information about supported storage arrays, storage operating environments, software enablers, applications, operating systems, high-availability environments, volume managers, and other supported software. To view the Replication Manager Support Matrix:

1. Point your web browser to http://elabnavigator.EMC.com.

2. Select PDFs and Guides, and scroll down to the Replication Manager section.

Known problems and limitationsThis section lists workarounds for critical problems that could otherwise impede your ability to install and configure Replication Manager.

Information on other known problems and limitations can be found using E-Lab™ Issue Tracker on Powerlink.EMC.com. Issue Tracker offers up-to-date status and information on issues reported by customers, partners, or EMC employees to Engineering that could impact your operations. You can find issues in the Issue Tracker database by matching issue number, product feature, host operating system, fixed version, or other fields.

For Replication Manager advanced searches in E-Lab Issue Tracker, begin by selecting Product Family: Infrastructure Software, then Product: Replication Manager.

For known problems and limitations listed in the base release, refer to the EMC Replication Manager Version 5.2.0 Release Notes.

Some replication settings for SQL Server and UDB are not retained after upgrade to 5.2.2 or greater (065062)

After an upgrade from Replication Manager versions 5.0.x or 5.1.x to 5.2.2 or greater, existing SQL Server and UDB jobs might not retain settings for replication consistency methods and for pre- and postscripts (under Advanced Replication Settings). This applies


18

Technical notes

only to jobs with the “by instance” consistency value. The workaround is to examine the replication options after upgrade and modify if necessary.

Technical notesThis section describes important technical information not available elsewhere.

Support for international operating systems and applicationsThis section describes Replication Manager restrictions and limitations when installed on the following native versions of Microsoft Windows: Japanese, Simplified Chinese, and Korean.

Note: Replication Manager supports no other operating system (such as UNIX) for internationalization in this release.

Support for ASCII and non-ASCII characters

in applications

Replication Manager's support for application character set formats (ASCII vs. non-ASCII) mirrors that of the specific database vendors. In other words, if a replication script (pre-, post-, mount, or backup script) is database-related, the script name can be non-ASCII (for example, Japanese), but the characters used for any internal paths, scripts, and database objects must comply with the application vendor.

For example, since Oracle database objects (such as database name and SID) must be in ASCII, Replication Manager supports ASCII-only Oracle database objects.

For Exchange, the ESEUTIL utility path, storage group names and database names must be ASCII; these are Microsoft restrictions.

General restrictions Replication Manager supports only ASCII characters (English) for the following:

◆ Replication Manager Config Checker

◆ Replication Manager installation wizard, including installation paths and the fields (domain, username, and password) associated with the Windows Task Scheduler

◆ Replication Manager Server license key file extension and path

◆ Oracle, Exchange, and SQL Server authentication credentials


Technical notes

◆ Application database paths including filename and extension (for example K:\sql_server\SQL_db1.mdf)

◆ Exchange Alternate Mount and ESEUTIL paths

◆ Exchange storage group and mailbox associated paths and database names (for example E:\priv1.edb and E:\priv1.stm)

◆ All dialogs, screens, pop-ups, etc., for Invista and Celerra

Replication Manager command line

interface restrictions

The Replication Manager CLI supports Japanese, Simplified Chinese, and Korean Windows operating systems under the following conditions:

◆ When you use an rmcli input file, commands and parameters must be ASCII, and the input file must adhere to the following restrictions:

• Created using Windows Notepad

• Contains only ASCII commands and content

• Saved in ANSI format

◆ When you are not using an rmcli input file, commands must be ASCII, but parameters (for example, application set name) can be non-ASCII; the resulting data objects will display in the appropriate language.

Restrictions related to third-party software

and environment configuration

Replication Manager supports only ASCII characters (English) for the following third-party software and environment configurations:

◆ Default installation paths for Navisphere (including Admsnap), Solutions Enabler, and PowerPath

◆ System hostnames

◆ Mountpoints and mountpoint paths

◆ CLARiiON connectivity username, password, and email address


20

Documentation

DocumentationThis section provides a list of the documentation that supports Replication Manager.

300-010-265 EMC Replication Manager 5.2.3 Administrator’s Guide

300-010-266 EMC Replication Manager 5.2.3 Product Guide

300-010-267 EMC Replication Manager 5.2.3 Release Notes

EMC Replication Manager online help

You can find Replication Manager documentation on the EMC Powerlink® website: http://Powerlink.EMC.com.

Software media, organization, and filesReplication Manager 5.2 SP3 is available as a download from Powerlink.emc.com.

Obtain the service pack by downloading the PRM523_00.tar archive file from Powerlink.

Downloading the service pack

To download the service pack, do the following:

1. Go to the Powerlink website:

http://Powerlink.EMC.com

2. Enter your Powerlink username and password.

3. Navigate to the download page for Replication Manager (Home > Support > Software Downloads and Licensing > Downloads P-R > Replication Manager).

4. Select the Replication Manager 5.2 SP3 service pack and save the PRM523_00.tar file to the appropriate installation directory.

Viewing and printing the documentation

EMC recommends that you read all the product documentation before installing and using Replication Manager. You must have Adobe Acrobat Reader to view and print the documentation included

Part number Name


Installation

on the DVD. You can download Adobe Acrobat Reader from Adobe’s website at http://www.adobe.com/.

InstallationThis section of the release notes provides information on how to install, upgrade to, or uninstall EMC Replication Manager 5.2 SP3.

Before installing Follow the instructions in this section before installing Replication Manager.

Replication Manager requirements

To install this service pack as an upgrade to an existing installation, Replication Manager must be at least at version 5.2.0. If you are upgrading from 5.1.x and version 5.2.0 is being installed as an interim step, refer also to the “Upgrade considerations” in Chapter 2 of the Replication Manager Administrator’s Guide.

In the case of RM Server on Windows Server 2008, install RM 5.2.3 Server as a fresh install, not as an upgrade from 5.2.0.

Table 1 Supported upgrade paths

5.0.x First to 5.2.0 then to 5.2.3

5.1.x First to 5.2.0 then to 5.2.3

5.2.0 Direct to 5.2.3

5.2.1 Direct to 5.2.3

5.2.2 Direct to 5.2.3

5.2.2.1 Direct to 5.2.3

Criteria for fresh install This service pack can be installed as a fresh installation (no previous Replication Manager software present) on Windows platforms only.

Solutions Enabler requirements

Refer to the Replication Manager Support Matrix for the required Solutions Enabler version.

All hosts require the 32-bit version of Solutions Enabler, except for the following, which require the 64-bit version: HP-UX 64-bit Itanium hosts, 64-bit Windows Server 2008 hosts, SRDF/CE hosts, and MirrorView/CE hosts.

From RM version Upgrade path to 5.2.3


22

Installation

On production hosts and mount hosts, Solutions Enabler must be installed in the default location, or syminq (installed as part of Solutions Enabler) must be included in the system environment variable PATH.

Refer to support information on E-Lab

Navigator

For specific information about supported storage arrays, storage operating environments, software enablers, applications, operating systems, high-availability environments, volume managers, and other supported software, refer to the Replication Manager Support Matrix for the latest support information. To access the Replication Manager Support Matrix, go to http://elabnavigator.EMC.com, select PDFs and Guides, and scroll down to Replication Manager.

Replication Manager Server on a cluster

Before upgrading a clustered Replication Manager Server, fail over the Replication Manager Server resource group to the node where Replication Manager Server was originally installed, then install this release on that node only. All changes will automatically propagate to other nodes in the cluster if a failover occurs.

Obtaining a license file

Replication Manager is license-controlled. Any license obtained for Replication Manager 5.x is valid in this release.

During Replication Manager installation you need to specify a license file. To obtain a license file:

1. Obtain a License Authorization Code (LAC) in one of the following ways:

• Locate the LAC on the Replication Manager Software Key Request Card.

• If you lose your code, you can receive a duplicate LAC by sending an email to the following address. Include your site name, site ID, phone number, and product serial number:

[email protected]

The LAC enables you to retrieve your Replication Manager license file from Powerlink Licensing, the web-based license management system.

A single LAC generates all of the licenses for your configuration.


Installation

2. Obtain a license key file at http://Powerlink.EMC.com. Navigate to Support > Software Download and Licensing > License Management. Refer to the EMC License Authorization email you received from EMC. The email contains the LAC, which enables you to retrieve your Replication Manager license file.

3. Follow the directions on the licensing main page.

You will be asked for a locking ID of the computer to be used as the Replication Manager Server. Enter any MAC address associated with the computer (for example, the MAC address of the HBA or a network card).

Make sure you save the license file with a .lic extension (the actual license filename can be unique). When saving the .lic file, the filename extension may default to .txt, which is not recognized by Replication Manager. To ensure it saves with a .lic extension, select All Files in the Save as type field before saving.

4. Once you have the license key file, apply it to the system when installing the Replication Manager Server, or afterwards using the Replication Manager Console.

For information on how licensing works in Replication Manager, refer to “Working with licenses” in Chapter 3 of the Replication Manager Administrator’s Guide.

Checking the version and patch level

You can check the version and patch level of the installed Replication Manager product using the ermPatchLevel tool. To use this tool, do the following:

1. Change directory to the location where you installed Replication Manager. Access the default directory as follows:

cd /opt/emc/rm/ (UNIX)cd "\Program Files\emc\rm" (Windows)

2. Change to the directory where binaries are stored for the particular component you want to check (for example, cd server\bin for the Replication Manager Server component).

3. Execute the appropriate script, depending on the platform:

• On UNIX, execute ermPatchLevel.sh

• On Windows, execute ermPatchLevel.bat


24

Installation

Installing the service pack on Windows

To install the service pack on Windows, do the following:

1. Log in to the machine where you want to install the service pack. If installing the service pack on the server or an agent, log in as Administrator.

2. Verify that there is no activity before you start the installation process. The service pack installation process shuts down Replication Manager.

3. Change your working directory to the directory where the PRM523_00.tar file has been copied and open the PRM523_00.tar archive with the WinZip utility to extract the files to the current directory.

4. Once you extract the tar file, the following files should be listed in the current directory:

• ermpatch.bat — Windows install script

• ermpatch.sh — UNIX/Linux install script

• ermpatch.jar — Compressed files for UNIX/Linux install

• RepMgrServicePack.exe — install executable for Windows, called by ermpatch.bat

• jvms directory — Java runtime environment files

5. Run ermpatch.bat.

6. If engineering patches are found on the system, they are listed and you are informed that they will be removed by installation of the service pack. You have the option of continuing to install the service pack, or to exit installation.

Refer to “Fixed problems” on page 4 to see which engineering patches are contained in this service pack. If a critical engineering patch is not listed in “Fixed problems”, contact Customer Service to learn if an updated engineering patch is available for this release.

7. Follow the remaining wizard prompts.

Errors are logged in rm_update.log in the user’s temp directory.

Installing the service pack on UNIX and Linux

To install the service pack on UNIX or Linux, do the following:

1. Log in as root on the machine where you want to install the service pack.


Installation

2. The service pack installation process shuts down Replication Manager. Verify that there is no activity before you start the installation process.

3. Change your working directory to the directory where the PRM523_00.tar file has been copied and execute the following command:

# tar xvf PRM523_00.tar

4. Once the command is executed, the following files are listed in the current directory:

• ermpatch.bat — Windows install script

• ermpatch.sh — UNIX/Linux install script

• ermpatch.jar — Compressed files, including the install GUI

• RepMgrServicePack.exe — install executable for Windows

• jvms directory — Java runtime environment files

The ermpatch.sh and ermpatch.jar files are required to update a UNIX/Linux machine.

5. Run ermpatch.sh.

6. Click Apply Service Pack to start the installation.

Status messages are displayed on the command line. If an error occurs, an error message is displayed. Check the ERMPatchLogFile for more information. The log file is located in the logs directory, typically /opt/emc/rm/logs.

Repairing the service pack (Windows)The Repair option reinstalls version 5.2.3 on a Windows system where it is already installed.

Note: The Repair option removes any engineering patches that were installed after the original installation of the service pack.

To repair a service pack on Windows:

1. Close the Replication Manager Console.

2. cd to the location where you extracted the service pack files and run ermpatch.bat

3. Select Repair.


26

Installation

The Repair option is an all-or-nothing action. You cannot repair a specific Replication Manager component.


Uninstalling Replication Manager

To uninstall a component of Replication Manager software, follow the steps for the operating system you are using, outlined in this section.

In a cluster environment, you must uninstall the Replication Manager Server component from the node on which you originally installed it.

Uninstalling from UNIXor Linux

To uninstall from UNIX or Linux:

1. Log in as root.

2. cd to the _uninst directory in the location where you installed Replication Manager. For example,

# cd /opt/emc/rm/_uninst

3. Run uninstaller.bin. Follow the instructions on the screen.

Uninstalling from Windows

To uninstall from Windows:

1. Run Windows’ Add or Remove Programs utility.

2. Select Replication Manager from the list of currently installed programs and click Remove.

3. Verify that you want to remove Replication Manager.

Uninstalling a component in

Windows

To uninstall a component from a Windows computer:

1. Close the Replication Manager Console.

2. cd to the location where you extracted the service pack files and run ermpatch.bat

3. Select Modify and click Next.

4. Each installed component is checked. Uncheck the components you want to uninstall and click Next.


6. Click Finish to close the wizard.


Installation

Uninstalling from clustered systems

Follow these steps to remove the Replication Manager from a cluster:

1. Remove the Replication Manager server services from the failover nodes (not from the node where Replication Manager was originally installed):

a. Make sure Replication Manager server is running on the node on which it was originally installed, and make a network share of the location where you installed Replication Manager server (for example, F:\rm\server\bin).

b. Map the share that you created above to a drive on the failover node.

c. Verify that you have access to the files located in the server\bin directory of the share above.

d. On the failover node, open a command prompt window and go into the mapped drive.

e. Run the following command from the directory you shared out in step a.

ins_serv.exe uninstall -cluster

f. On the failover node, Start > Control Settings > Add/Remove Programs. Select Replication Manager to run the uninstall wizard. Select the remaining Replication Manager components (agent, console) that you want to uninstall.

g. On the failover node, disconnect from the network share.

h. Repeat steps b – f for the other failover nodes in the cluster.

(Do not perform steps b – f for the original install node. Uninstalling from the original install node is covered in step 2 below.)

2. On the original install node of the cluster, Start, Control Settings, Add/Remove Programs. Select Replication Manager to run the uninstall wizard.


28

Troubleshooting and getting help

Troubleshooting and getting helpEMC support, product, and licensing information can be obtained as follows.

Product information — For documentation, release notes, software updates, or for information about EMC products, licensing, and service, go to Powerlink (registration required) at:

http://Powerlink.EMC.com

Technical support — For technical support, go to EMC Customer Service on Powerlink. To open a service request through Powerlink, you must have a valid support agreement. Contact your EMC sales representative for details about obtaining a valid support agreement or to answer any questions about your account.

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 regulatory document for your product line, go to the Technical Documentation and Advisories section on EMC Powerlink.

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.


http://powerlink.emc.com

star-rm-300-010-267

Documents

multiple jobs

remaining

function getclonedevices

asm init file

target rac

replication

rmcli input

lab issue