Unsolved
This post is more than 5 years old
2 Posts
0
3424
Replication Manager with Recoverpoint
Environmental details:
Source:
Clariion - CX4- Flarecode 04.28.000.5.706
CX4 Splitter version - 04.28.006.6.008
Recoverpoint - RPA - code - 3.2 SP2
Replication Manager Agent - 5.2
Production Hosts - Windows 2003 Ent SP2
NaviAgent, Navi CLI - 6.28
AdmsnapPP - 5.1.0
Fabric: Cisco MDS
Target:
Clariion - CX4- Flarecode 04.28.000.5.706
CX4 Splitter version - 04.28.006.6.008
Recoverpoint - RPA - code - 3.2 SP2
Replication Manager Server - 5.2.2.1
Mount Host - Windows 2003 Ent SP2 - Virtual Machine on ESX 3.5
NaviAgent, Navi CLI - 6.28
Admsnap
Fabric: Cisco MDS
Problem Description:
We are trying to setup Replication Manager to work with Recoverpoint so that we can schedule a job to unmount/mount the target volumes on mount host using RM.
Recoverpoint appliances are replicating data fine. I have the target volume mounted on the mount host and can access the data in image access mode.
But when I try to add the Source and Target volumes to Replication Manager, Hosts are detected fine but "add storage" gives problems due to which we couldnt create an Application Set.
Questions I have:
1. We are doing storage based replication using CX4 splitter. Do we still need to install IRCCD on production host ?
2. Can we have a virtual mount host or doesnt it need to be physical ?
3. Am I running supported versions of s/w ?
Storage Discovery doesnt detect the source Clariion at all and Fails with the following error message while detecting the target clariion. I know the credentials work fine because, I am logged in to the clariion using the same credentials and I have tried them multiple times.
RM Server - Error log:
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Jan 15, 2010 2:09:21 PM ATLITPREPLMGR1 Starting storage discovery for array RPA@10.75.30.85.
Jan 15, 2010 2:09:21 PM ATLITPREPLMGR1 Discovering storage attached to client ATLITPREPLMGR1.
Jan 15, 2010 2:09:21 PM ATLITPREPLMGR1 Starting storage discovery for array RPA@192.168.15.169.
Jan 15, 2010 2:09:22 PM ATLITPREPLMGR1 Discovering storage attached to client 192.168.15.175.
Jan 15, 2010 2:09:22 PM ATLITPREPLMGR1 Starting array verification for APM00085003130.
Jan 15, 2010 2:09:23 PM ATLITPREPLMGR1 Verifying array attached to client ATLITPREPLMGR1.
Jan 15, 2010 2:09:22 PM ATLITPREPLMGR1 Starting RecoverPoint storage discovery.
Jan 15, 2010 2:09:22 PM ATLITPREPLMGR1 Validating credentials for RPA RPA@10.75.30.85
Jan 15, 2010 2:09:25 PM ATLITPREPLMGR1 100761 ERROR: SymAPI not present, but function "SymApiVersion" invoked.
Jan 15, 2010 2:09:25 PM ATLITPREPLMGR1 100761 ERROR: SymAPI not present, but function "SymErrorSymbol" invoked.
Jan 15, 2010 2:09:25 PM ATLITPREPLMGR1 100761 ERROR: SymAPI not present, but function "SymPerror" invoked.
Jan 15, 2010 2:09:25 PM ATLITPREPLMGR1 000033 ERROR: Function SweClarIdInit failed.
Jan 15, 2010 2:09:25 PM ATLITPREPLMGR1 026101 ERROR: Storage Services showStorage failed with an error as follows: clariion - Check for proper installation of Solutions Enabler and its registry keys.
Jan 15, 2010 2:09:25 PM ATLITPREPLMGR1 026090 ERROR: Storage Services operation getLastError_event failed with an error as follows: handles not initialized.
Jan 15, 2010 2:09:25 PM ATLITPREPLMGR1 026005 ERROR: Storage Services operation processShowStorage failed with an error as follows: See previous errors or RM log files.
Jan 15, 2010 2:09:25 PM ATLITPREPLMGR1 000504 ERROR: Unable to discover APM00085003130 array from any host.
Jan 15, 2010 2:09:25 PM ttsqlbkp Starting RecoverPoint storage discovery.
Jan 15, 2010 2:09:25 PM ttsqlbkp Validating credentials for RPA RPA@192.168.15.169
Jan 15, 2010 2:09:26 PM ATLITPREPLMGR1 001018 ERROR: Validation for APM00085003130 failed. Please check credentials and connectivity.
Jan 15, 2010 2:09:27 PM ATLITPREPLMGR1 Credentials validated
Jan 15, 2010 2:09:28 PM ATLITPREPLMGR1 End of RecoverPoint storage discovery.
Jan 15, 2010 2:09:31 PM ttsqlbkp Credentials validated
Jan 15, 2010 2:09:32 PM ttsqlbkp End of RecoverPoint storage discovery.
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
AranH1
2.2K Posts
1
January 15th, 2010 14:00
There are a few configuration requirements for RM integration with RecoverPoint. I would first review the section on RecoverPoint in the Replication Manager Administrators Guide for some of the requirements.
A quick note on RM though, to setup an Application Set requires the RM agent be installed on the Production and Mount hosts, and those hosts will have to be managed by the same RM server. Lookup your version of RM in the EMC Support Matrix as well for all of the host requirements (SE, MS Hotfixes, etc.) as these are very important. And yes you can mount to a VM, it is all in the Administrators Guide and Product Guide.
The Administrators Guide is located on Powerlink at:
Support > Technical Documentation and Advisories > Software ~ P-R ~ Documentation > Replication Manager > Maintenance/Administration
JamesBEMC
257 Posts
1
January 17th, 2010 23:00
Yes indeed.
Can you check to make sure you have EMC Solutions Enabler installed on all the hosts involved with Replication Manager please?
If you do, try putting the SYMCLI\bin directory into the system PATH variable and restart the IRCCD (Replication Manager Client) Service.
The path to SYMCLI will be dependent on your installation type, it will either be
C:\Program Files\EMC\SYMCLI\bin
or
C:\Program Files(x86)\EMC\SYMCLI\bin
Thanks
James.
Adapa1
2 Posts
0
January 18th, 2010 11:00
Thank you Aran and James,
The issue I had was due to version inconsistencies between RMServer/Mount host and Production host.
When I tried using the same VM as RM server and Mount Host(win2k3-x64bit), I got errors while trying to discover storage "SYMAPI not present" as you can see in my original post. I used a seperate physical server (win2k3-x32bit) as mount host and ran the job successfully.
Have you seen any issues with other environments using same machine as RM server and Mount host or with Mount host being virtual ?
JamesBEMC
257 Posts
0
January 19th, 2010 02:00
Hi Adapa
Glad to hear you got it resolved.
What virtualization platform are you using VMWare or Hyper-V?
If you are not using an in-child (in-VM) iSCSI initiator in your virtual mount host for storage connectivity, you need to pre-expose the LUNs involved in the replica to the virtual mount host.
Pre-expose, but do not mount. I.e. add the LUNs to the physical virtual server's storage group, then add them as disks to the VM.
Thanks
James.
warroko
3 Posts
0
May 7th, 2010 00:00
Just an added comment on VM - I've setup a VM mount host that is also the DR RM server. The disk is a RAW device joined to the VM via direct access versus virtual access. I made the mistake of fully configuring after enabling access via RP and corrupted the RM db.
To clean everything and return it to the condition before, I had to do the below:
1. Remove the RAW disk from the VM and reboot - to clear up the mount point.
2. Rename or deleted symapi_db_emcrm_client.bin and restart the Replication Manager client service - to restore a new copy
After that - running the job to create a replica and mounting worked perfectly.