RecoverPoint Implementation Lab 3.3

(1)

RecoverPoint Implementation

Lab Guide

(2)

Copyright

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.

EMC, ICDA® (Integrated Cached Disk Array), and EMC2_{® (the EMC logo), and Symmetrix®, are registered}

trademarks of EMC Corporation. EMC™ and SRDF™ are trademarks of EMC Corporation. All other trademarks used herein are the property of their respective owners.

(3)

Trademark Information

EMC

Trademarks

EMC2, EMC, Symmetrix, Celerra, CLARiiON, CLARalert, Connectrix, Dantz, Documentum, HighRoad, Legato, Navisphere, PowerPath, ResourcePak, SnapView/IP, SRDF, TimeFinder, VisualSAN, and where information lives are registered trademarks and EMC Automated Networked Storage, EMC

ControlCenter, EMC Developers Program, EMC OnCourse, EMC Proven, EMC Snap, Access Logix, AutoAdvice, Automated Resource Manager, AutoSwap, AVALONidm, C-Clip, Celerra Replicator, Centera, CentraStar, CLARevent, CopyCross, CopyPoint, DatabaseXtender, Direct Matrix, Direct Matrix

Architecture, EDM, E-Lab, Enginuity, FarPoint, FLARE, GeoSpan, InfoMover, MirrorView, NetWin, OnAlert, OpenScale, Powerlink, PowerVolume, RepliCare, SafeLine, SAN Architect, SAN Copy, SAN Manager, SDMS, SnapSure, SnapView, StorageScope, SupportMate, SymmAPI, SymmEnabler, Symmetrix DMX,

Universal Data Tone, and VisualSRM are trademarks of EMC Corporation. All other trademarks used herein are the property of their respective owners.

Third Party Trademarks

AIX is a registered trademark of International Business Machines Corporation. Brocade, SilkWorm, SilkWorm Express, and the Brocade logo are trademarks or registered trademarks of Brocade Communications Systems, Inc., in the United States and/or in other countries. Compaq and the names of Compaq products referenced herein are either trademarks and/or service marks or registered trademarks and/or service marks of Compaq. Hewlett-Packard, HP, HP-UX, OpenView, and OmniBack are trademarks, or registered trademarks of Hewlett-Packard Company. McDATA, the McDATA logo, and ES-2500 are registered trademarks of McDATA Corporation. Microsoft, Windows, and Windows NT are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. NobleNet is a registered trademark of Rogue Wave Software, Inc. SANbox is a trademark of QLogic Corporation. Sun, Sun

Microsystems, the Sun Logo, SunOS and all Sun-based trademarks and logos, Java, the Java Coffee Cup Logo, and all Java-based trademarks and logos, Solaris, and NFS, are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries. UNIX is a registered trademark of The Open Group.

(4)

Document Revision History

Rev # File Name Date

1.0 Deployment Workshop 3.0.doc February2008 1.1 Deployment Lab Guide 3.0.doc April 2008 2.0 RP3.1 Workshop Lab Guide.doc December 2008 2.1 RP3.1.1_Workshop_Labguide.doc July 2009

2.2 RPImp_Labguide.doc September 2009

2.3 MR-7CP-NSRPIM_RecoverPoint Implementation Lab Guidev3.3.doc

(5)

Lab Exercise 1: SAN Configuration for RecoverPoint

Purpose:

To configure an EMC SAN environment to function with RecoverPoint appliances.

Tasks:

In this lab, you perform the following tasks:

 Identify WWNs of the RPAs

 Identify storage and host WWNs

 Identify LUNs to be used for repository, journal and host data (replica) volumes

 Implement zoning and LUN masking to support the RPA

References:

_ RecoverPoint Deployment Manager Product Guide

Administrator‘s Guide

(8)

Part 1: Set initial System Layout and Discover WWN’s

Step Action

0 Note1: If using Windows host, download Putty.exe or any other utility that supports SSH.

Note2: Screenshots in this lab guide might slightly differ from aspects in the lab equipment configuration in use.

1 Connect to the first RPA at local site via SSH. Connect into the management IP interface. Use the default user boxmgmt and password boxmgmt to log in.

2 For the sake of lab activities the RPAs management IPs have been defined prior to the class so everything can be performed remotely from the classroom. During this step do not configure RPA management IP address

Note: Perform these steps in all RPAs at each site. login as: boxmgmt

Using keyboard-interactive authentication. Password:

Linux RecoverPoint_P4_Site1_RPA1 2.6.32.2-k1.x64.deb #3 SMP Wed Jan 13 18:01:51 IST 2010 x86_64

Last login: Tue Jun 1 15:37:35 2010 from brcszubirl1c.corp.emc.com

Loading RPA settings... done

Initializing Installation Manager... done Installation Manager - RecoverPoint Version 3.3.P2(e.95)

Do you want to configure a temporary IP address? (y/n)? n ** Main Menu ** [1] Installation [2] Setup [3] Diagnostics [4] Cluster operations

[5] Shutdown / Reboot operations [Q] Quit

(9)

Step Action

3 From the boxmgmt Main menu select Diagnostics > Fibre Channel diagnostics > View

Fibre Channel details.

Fibre Channel Details

Port 0 --- |---|---| | | | |---|---| | Link status | Up | | wwn | 0x50012482001063a0 | | node wwn | 0x50012482001063a1 | | port id | 4f0000 | | operating mode | point to point | | speed | 2 GB | |---|---| Port 1 --- |---|---| | | | |---|---| | Link status | Up | | wwn | 0x50012482013063a0 | | node wwn | 0x50012482013063a1 | | port id | ce0005 | | operating mode | point to point | | speed | 2 GB |

(10)

Step Action

4 Local Site. Record the Port WWN for each FC Port below.

Site 1 RPA 1: Port 0 _______________________________________ Port 1 _______________________________________ Port 2 _______________________________________ Port 3 _______________________________________ Site 1 RPA 2: Port 0 _______________________________________ Port 1 _______________________________________ Port 2 _______________________________________ Port 3 _______________________________________

(11)

Step Action

5 Remote Site. Record the Port WWN for each FC Port below.

Site 2 RPA 1: Port 0 _______________________________________ Port 1 _______________________________________ Port 2 _______________________________________ Port 3 _______________________________________ Site 2 RPA 2: Port 0 _______________________________________ Port 1 _______________________________________ Port 2 _______________________________________ Port 3 _______________________________________

(12)

Part 2: Zoning the RPAs in an MDS Series SAN

Step Action

Before we can replicate volumes using RecoverPoint, we must first expose RPAs HBAs to host HBAs, as well as to storage ports involved in replication at each site. This means a lot of zoning.

At the end of this exercise, in the zones database of every switch there should be several zones representing every component involved in the replication scenario, for example:

a) RPAs to first Windows host b) RPAs to second Windows host c) RPAs to AIX

d) RPAs to ESX

e) RPAs to CLARiiON SPA port f) RPAs to CLARiiON SPB port g) RPAs to Symmetrix port

Each group will work in a different environment with different switches, hosts and storage ports so there should not be conflicts between groups. Refer to the lab environment

reference document for your specific components.

Note: This lab exercise shows the steps to create zones using command line. If you feel more comfortable working with the GUI, verify with your instructor if there is a host where Fabric Manager is installed. If so, feel free to use it. Just make sure you create all required zones as showed here.

(13)

Step Action

1 Telnet as admin on your first switch at local site.

Verify which RPA ports are logged into this switch by viewing the flogi database. If you

have two RPAs per site and two fabrics at each site, each fabric will have four RPA ports.

RPAs WWN start with 50:01:24:82:xx:xx:xx:xx. Write down the RPA WWNs connected to this switch (port name column).

Command Syntax:

show flogi database vsan <vsan#> Command Example:

mds# show flogi database vsan 20

Command Output: show flogi database without vsan #

Note that the VSAN number may be different in your assigned switches. List the existent VSANs by running ―show vsan‖. Also, there should only be one production VSAN with operational state up and an active zoneset (which will be the VSAN to use). Verify that by running ―show zoneset active‖.

Important: Configuration changes on the switch should only be performed by one user at a time. Each workgroup should coordinate switch configurations to ensure only one user is changing a configuration.

If for some reason RPA ports are in a different VSAN than hosts and storage ports, go ahead and move them to the same VSAN.

s1-mdsa-14-80# show flogi database

--- INTERFACE VSAN FCID PORT NAME NODE NAME --- fc1/4 13 0xce0000 50:06:04:8a:d5:f0:f8:cf 50:06:04:8a:d5:f0:f8:cf fc1/8 30 0x1f0007 50:06:04:8a:d5:f0:f8:c1 50:06:04:8a:d5:f0:f8:c1 fc1/12 30 0x1f02ef 50:06:01:63:3c:e0:2e:6f 50:06:01:60:bc:e0:2e:6f fc1/13 30 0x1f03ef 50:06:01:68:3c:e0:2e:6f 50:06:01:60:bc:e0:2e:6f fc1/14 13 0xce0001 50:06:04:8a:d5:f0:f8:df 50:06:04:8a:d5:f0:f8:df fc1/15 20 0xbc0007 50:06:04:8a:d5:f0:f8:d0 50:06:04:8a:d5:f0:f8:d0 fc2/1 13 0xce0002 50:01:24:82:01:30:a7:a4 50:01:24:82:01:30:a7:a5 fc2/2 13 0xce0003 50:01:24:82:00:10:25:a5 50:01:24:82:00:10:25:a4 fc2/3 30 0x1f0003 50:01:24:82:01:30:b2:9f 50:01:24:82:01:30:b2:9e fc2/4 20 0xbc0005 50:01:24:82:01:30:dd:9f 50:01:24:82:01:30:dd:9e fc2/5 13 0xce0004 50:01:24:82:00:10:aa:a4 50:01:24:82:00:10:aa:a5 fc2/6 20 0xbc0006 50:01:24:82:00:10:c5:a3 50:01:24:82:00:10:c5:a2 fc2/7 20 0xbc0008 10:00:00:00:c9:5e:af:5d 20:00:00:00:c9:5e:af:5d fc2/8 1 0x340019 10:00:00:00:c9:37:0c:0a 20:00:00:00:c9:37:0c:0a

(14)

Step Action

2 Enter the configuration terminal. Command Example:

mds# conf t

3 TARGET Zones. Create a new zone. As per EMC Best Practices, you will add only two

members to this zone. The first one is an RPA port connected to this fabric and the second one the host HBA.

Command Syntax:

zone name <name> vsan <VSAN#>

Command Example:

mds#(config) zone name rpa5_p0_win3a vsan 20

4 Add the pwwn of the first RPA port that is logged into this switch as member of the new zone. Use one of the WWNs saved on step 1.

Command Syntax:

member pwwn <RPA PWWN> Command Example:

mds(config-zone)# member pwwn 50:01:24:82:00:10:42:a5 5 Add the pwwn of the host HBA as a member of the new zone.

Command Syntax:

member pwwn <HBA PWWN> Command Example:

mds(config-zone)# member pwwn 10:00:00:00:c9:69:e1:34 There are many ways to find out the host HBA WWN. Choose the one you are more

comfortable with. Hint, hosts already have zones created to the storage ports, looking at an

existing zone may be the easiest way to discover that. Run “show zoneset active” to list the active zones in the database. But you can cross check that by looking direct at the host operating system.

6 You have created the first zone for your first host with one of the RPAs ports connected to this fabric. Exit the config-zone mode. This will return you to the config prompt.

Command Example:

mds(config-zone)# exit

(15)

Step Action

fabric. At the end, there should be four similar zones (you have created the first), with two members each, being one RPA port and the host HBA.

Please repeat steps 3 through 6. Give different names to the new zones. Use the WWNs saved on step 1.

7 INITIATOR Zones. Create another new zone. As per EMC Best Practices, you will add

only two members to this zone. The first one is an RPA port connected to this fabric and the second one the storage port.

Command Syntax:

zone name <name> vsan <VSAN#> Command Example:

mds#(config) zone name rpa5_p0_symm_fa4ba vsan 20

8 Add the pwwn of the first RPA port that is logged into this switch as member of the new zone. Use one of the WWNs saved on step 1.

Command Syntax:

member pwwn <RPA PWWN> Command Example:

mds(config-zone)# member pwwn 50:01:24:82:00:10:42:a5

9 Add the pwwn of the storage port as a member of the new zone. Command Syntax:

member pwwn <Storage Port PWWN> Command Example:

mds(config-zone)# member pwwn 50:06:04:8a:cc:d2:53:81 Verify which storage port to use in the lab environment reference document. If you are working in a CLARiiON environment zone all CLARiiON SP ports with all RPA ports in one single zone.

There are many ways to find out the storage port WWN. Choose the one you are more comfortable with. Hint, storage ports already have zones created on this switch (zoned with

hosts), looking at an existing zone may be the easiest way to discover that. Run “show zoneset active” to list the active zones in the database.

10 You have created the first zone for your first storage port with one of the RPAs ports connected to this fabric. If you are working in a CLARiiON environment you have created

(16)

Step Action

the required zone.

Exit the config-zone mode. This will return you to the config prompt Command Example:

mds(config-zone)# exit

Now create additional zones using the same storage port with all the other RPA ports in this fabric. At the end, there should be four (one if CLARiiON in place) similar zones (you have created the first), with two members each, being one RPA port and the storage port.

Please repeat steps 7 through 10. Give different names to the new zones. Use the WWNs saved on step 1.

11 Display the name of the active zoneset for your VSAN. You will need this name to add the new zones to the zoneset and activate the zoning changes in the next several steps. Add „do‟

in front of the command if you are in the config prompt level.

Command Syntax:

do show zoneset active vsan <VSAN#> Command Example:

mds(config)# do show zoneset active vsan 20

Output: show zoneset active

s1-mdsa-14-80# show zoneset active

zoneset name bos1_rpa_BE_zoneset vsan 10

zone name s1_sun1_hba1_dmx155_fa16cA vsan 10 pwwn 10:00:00:00:c9:5e:af:d1

pwwn 50:06:04:8a:d5:f0:f8:cf

zone name s1_rpa_all_dmx155_fa16cA vsan 10 pwwn 50:06:04:8a:d5:f0:f8:cf

pwwn 50:01:24:82:01:30:a7:a4 pwwn 50:01:24:82:00:10:25:a5 pwwn 50:01:24:82:00:10:aa:a4 pwwn 50:01:24:82:01:30:63:a0

(17)

Step Action

12 From the config prompt add the new zones to the zoneset. Command Syntax:

conf t

zoneset name <Zoneset Name> vsan # member <Zone Name>

Command Example: mds# conf t

mds(config)# zoneset name prod1_H2S_fabA vsan 20 mds(config-zoneset)# member rpa5_p0_win3a

mds(config-zoneset)# member rpa5_p2_win3a mds(config-zoneset)# member rpa6_p0_win3a mds(config-zoneset)# member rpa6_p2_win3a

mds(config-zoneset)# member rpa5_p0_symm_fa4ba mds(config-zoneset)# member rpa5_p2_symm_fa4ba mds(config-zoneset)# member rpa6_p0_symm_fa4ba mds(config-zoneset)# member rpa6_p2_symm_fa4ba

Note that this lab exercise only showed the steps to create zones from the RPAs to a host and zones from the RPAs to the storage port. You might need to create additional zones for the other hosts and storage ports. Refer to the lab environment reference document.

13 Exit the config-zoneset mode. This will return you to the config prompt. Command Example:

mds(config-zoneset)# exit 14 Activate the zoneset.

Command Syntax:

zoneset activate name <Zoneset Name> vsan <VSAN#> Command Example:

mds(config)# zoneset activate name prod1_H2S_fabA vsan 20

15 Exit the config mode. This will return you to the switch prompt. Command Example:

mds(config)# exit

16 Display the modified active zoneset for your VSAN. You should see your new zones there. Command Syntax:

(18)

Step Action

show zoneset active vsan <VSAN#> Command Example:

mds# show zoneset active vsan 20

17 Copy the running configuration to the startup configuration so changes are persistent across reboots.

Command Syntax:

mds# copy running-config startup-config Command Example:

mds# copy run start

You have now taken care of zoning on the first fabric at local site. Telnet into your second switch at local site and do the same thing (steps 1 to 17) – obviously the zone names and the zoneset name may be different there.

18 Check the zoning configuration from the RPAs. Log into each RPA as the boxmgmt user. From the Main menu select Diagnostics > Fibre Channel diagnostics > Detect Fibre

Channel targets.

Each ports should display the WWNs of the host HBA ports and storage ports.

Important: When you are done with zoning at local site (both switches), move on to remote site.

Telnet into your first and second switches at remote site and do the same thing (steps 1 to 18) – obviously the zone names and the zoneset name may be different there.

(19)

Part 3: Zoning the RPAs in a Brocade SAN

Step Action

Before we can replicate volumes using RecoverPoint, we must first expose RPAs HBAs to host HBAs, as well as to storage ports involved in replication at each site. This means a lot of zoning.

At the end of this exercise, in the zones database of every switch there should be several zones representing every component involved in the replication scenario, for example:

h) RPAs to first Windows host i) RPAs to second Windows host j) RPAs to AIX

k) RPAs to ESX

l) RPAs to CLARiiON SPA port m) RPAs to CLARiiON SPB port n) RPAs to Symmetrix port

Each group will work in a different environment with different switches, hosts and storage ports so there should not be conflicts between groups. Refer to the lab environment

reference document for your specific components.

Note: This lab exercise shows the steps to create zones using command line. If you feel more comfortable working with the GUI (WebTools) feel free to use it. Just make sure you create all required zones as showed here.

(20)

Step Action

1 Telnet as admin on your first switch at local site (S1-brocade1_a, S1-brocade3_a etc). Verify which RPA ports are logged into this switch. If you have two RPAs per site and two fabrics at each site, each fabric will have four RPA ports. The name server shows RPA entries as the ‗KASHYA‘ vendor. RPAs WWN start with 50:01:24:82:xx:xx:xx:xx. Write down the RPA WWNs connected to this switch (port name).

Command Example: nsshow

Output: nsshow

Important: Configuration changes on the switch should only be performed by one user at a time. Each workgroup should coordinate switch configurations to ensure only one user is changing a configuration.

DS_4100B:admin> nsshow {

Type Pid COS PortName NodeName TTL(sec) N 010300; 3;50:01:24:82:00:10:4a:a0;50:01:24:82:00:10:4a:a1; na FC4s: FCP [KASHYA KBOX2_S2-BOS4 0001]

Fabric Port Name: 20:03:00:05:1e:02:c6:63 Permanent Port Name: 50:01:24:82:00:10:4a:a0 Port Index: 3

Share Area: No

Device Shared in Other AD: No Redirect: No

N 010400; 3;50:06:04:8a:d5:f0:e6:40;50:06:04:8a:d5:f0:e6:40; na FC4s: FCP

PortSymb: [38] "EMC SYMMETRIX 000190301081 SAF- 1cA " NodeSymb: [38] "EMC SYMMETRIX 000190301081 SAF- 1cA " Fabric Port Name: 20:04:00:05:1e:02:c6:63

Permanent Port Name: 50:06:04:8a:d5:f0:e6:40 Port Index: 4

Share Area: No

N 010600; 3;50:01:24:82:01:30:e3:9d;50:01:24:82:01:30:e3:9c; na FC4s: FCP [KASHYA KBOX2_S2-BOS4 0001]

Fabric Port Name: 20:06:00:05:1e:02:c6:63 Permanent Port Name: 50:01:24:82:01:30:e3:9d Port Index: 6

Share Area: No

(21)

Step Action

2 Display the effective configuration. You will need the configuration name to add new zones to it. Command Example: cfgactvshow Output: cfgactvshow DS_4100B:admin> cfgactvshow Effective configuration: cfg: L_Winspltr_allZONES_cfg zone: L_WINaf8f_15ca_1ca_SPa0 10:00:00:00:c9:5e:af:8f 50:06:01:60:3c:e0:09:c1 zone: L_WINspltr_allRPAs 10:00:00:00:c9:5e:af:8f 50:01:24:82:00:10:4a:a0 50:01:24:82:00:10:ab:a4 50:01:24:82:01:30:be:9f 50:01:24:82:01:30:e3:9d zone: L_allRPAs_allSTORAGE 50:01:24:82:00:10:4a:a0 50:01:24:82:00:10:ab:a4 50:01:24:82:01:30:be:9f 50:01:24:82:01:30:e3:9d 50:06:01:60:3c:e0:09:c1

(22)

Step Action

3 TARGET Zones. Create a new zone. As per EMC Best Practices, you will add only two

members to this zone. The first RPA port connected to this fabric and the host HBA. Use one of the RPA WWNs saved on step 1.

Command Syntax:

zonecreate ―zone name‖, ―RPA3 PWWN 0; Host HBA PWWN‖ Command Example:

zonecreate "rpa3_p0_win2a", "50:01:24:82:01:30:75:a4; 10:00:00:00:c9:69:e6:92"

There are many ways to find out the host HBA WWN. Choose the one you are more

comfortable with. Hint, hosts already have zones created to the storage ports, looking at an

existing zone may be the easiest way to discover that. Run “cfgactvshow” to list the active zones in the configuration. But you can cross check that by looking direct at the host operating system.

Now create additional zones using the same host HBA with all the other RPA ports in this fabric. At the end, there should be four similar zones (you have created the first), with two members each, being one RPA port and the host HBA.

Please repeat step 3. Give different names to the new zones. Use the RPA WWNs saved on step 1.

4 INITIATOR Zones. Create another new zone. As per EMC Best Practices, you will add

only two members to this zone. The first one is an RPA port connected to this fabric and the second one the first storage port. If you are working on a CLARiiON environment zone all CLARiiON SP ports in this fabric with all RPA ports in one single zone.

Command Syntax:

zonecreate ―zone name‖, ―RPA3 PWWN 0; Storage Port PWWN a‖ Command Example:

zonecreate "rpa3_p0_spA2", "50:01:24:82:01:30:75:a4; 50:06:01:62:3c:e0:05:91"

Verify which storage port (s) to use in the lab environment reference document. There are many ways to find out the storage port WWN. Choose the one you are more comfortable with. Hint, storage ports already have zones created on this switch (zoned with

hosts), looking at an existing zone may be the easiest way to discover that. Run “cfgactvshow” to list the active zones in the configuration.

At the end, in a CLARiiON environment there should be one zone with all RPA ports and all storage ports as members. Or, in a DMX environment, four zones with two members each, being one RPA port and one of the storage ports.

(23)

Step Action

Please repeat step 4. Give different names to the new zones. Use the RPA WWNs saved on step 1.

5 Add the new zones to the active configuration and enable the new configuration. Command Syntax:

cfgadd ―configuration name‖, ―zone name; zone name; ...‖ cfgenable ―configuration name‖

Command Syntax:

cfgadd ―s1_7600a_cfg‖, ―rpa3_p0_win2a; rpa3_p2_win2a; rpa4_p0_win2a; rpa4_p2_win2a; rpa3_p0_spA2; rpa3_p0_spB3; rpa3_p2_spA2; rpa3_p2_spB3; rpa4_p0_spA2; rpa4_p0_spB3; rpa4_p2_spA2; rpa4_p2_spB3‖

cfgenable ―s1_7600a_cfg‖

6 Display the active configuration. You should see your new zones in the active configuration.

Command Example: Cfgactvshow

Note that this lab exercise only showed the steps to create zones from the RPAs to a host and zones from the RPAs to the storage ports. You might need to create additional zones for the other hosts and storage ports (if present). Refer to the lab environment reference

document.

You have now taken care of zoning on the first fabric at local site. Telnet into your second switch (S1-brocade2_b, S1-brocade4_b etc) at local site and do the same thing (steps 1 to 6) – obviously the zone names and the configuration name may be different there.

7 Check the zoning configuration from the RPAs. Log into each RPA as the boxmgmt user. From the Main menu select Diagnostics > Fibre Channel diagnostics > Detect Fibre

Channel targets.

Each ports should display the WWNs of the host HBA ports and storage ports.

Important: When you are done with zoning at local site (both switches), move on to remote site.

Telnet into your first and second switches at remote site and do the same thing (steps 1 to 7) – obviously the zone names and the configuration name may be different there.

(24)

Part 4: LUN Masking for the RPA – Symmetrix

Step Action

1 Before we can replicate volumes using RecoverPoint, we must first present the repository, journals, and host volumes (replica) to all RPAs at each site. This means a lot of masking. Refer to the lab environment reference guide for repository, journals, and host volumes (replica) information assigned to you RPA cluster group. You will also need information about the storage ports. Finally, WWNs of the RPA ports will be used in this exercise. You can use the syminq or inq command on your hosts to identify the host data (replica) volumes that must be seen by the RPA ports. You will need the Symmetrix device numbers to verify that these volumes are seen by the RPAs.

Command Example: syminq or inq

Sample Output: inq

2 Verify which Symmetrix ports are connected to the host. You will need the director number and port number for the masking commands.

Command Example:

symcfg list –connections

Sample Output: symcfg list –connections

# inq

--- DEVICE :VEND :PROD :REV :SER NUM :CAP(kb) --- /dev/rdsk/c1t5006048AD5F0F8E1d0s2 :EMC :SYMMETRIX :5772 :5500020341 : 92160 /dev/rdsk/c1t5006048AD5F0F8E1d81s2 :EMC :SYMMETRIX :5772 :5500071341 : 4128000 /dev/rdsk/c1t5006048AD5F0F8E1d82s2 :EMC :SYMMETRIX :5772 :5500072341 : 4128000 /dev/rdsk/c1t5006048AD5F0F8E1d83s2 :EMC :SYMMETRIX :5772 :5500073341 : 4128000 /dev/rdsk/c1t5006048AD5F0F8E1d84s2 :EMC :SYMMETRIX :5772 :5500074341 : 4128000 /dev/rdsk/c1t50012482001063A0d0s2 :KASHYA :KBOX2_S1-BOS1 :0001 : : 983500000 /dev/rdsk/c1t500124820130AAA4d0s2 :KASHYA :KBOX1_S1-BOS1 :0001 : : 983500000 /dev/rdsk/c2t5006048AD5F0F8CFd0s2 :EMC :SYMMETRIX :5772 :5500020480 : 92160 /dev/rdsk/c2t5006048AD5F0F8CFd81s2 :EMC :SYMMETRIX :5772 :5500071480 : 4128000 /dev/rdsk/c2t5006048AD5F0F8CFd82s2 :EMC :SYMMETRIX :5772 :5500072480 : 4128000 /dev/rdsk/c2t5006048AD5F0F8CFd83s2 :EMC :SYMMETRIX :5772 :5500073480 : 4128000 /dev/rdsk/c2t5006048AD5F0F8CFd84s2 :EMC :SYMMETRIX :5772 :5500074480 : 4128000 /dev/rdsk/c2t50012482013063A0d0s2 :KASHYA :KBOX2_S1-BOS1 :0001 : : 983500000 /dev/rdsk/c2t500124820010AAA4d0s2 :KASHYA :KBOX1_S1-BOS1 :0001 : : 983500000 /dev/rdsk/c2t50012482001025A5d0s2 :KASHYA :KBOX2_S1-BOS1 :0001 : : 983500000 /dev/rdsk/c2t500124820130A7A4d0s2 :KASHYA :KBOX1_S1-BOS1 :0001 : : 983500000

(25)

Step Action

3 Log into the RPA as boxmgmt to get the RPA PWWNs. You can also use the WWNs identified in the first exercise. From the boxmgmt main menu select Diagnostics > Fibre

Channel diagnostics > View Fibre Channel details.

View Fibre Channel Details – Sample Output

Verify which Symmetrix ports are connected to the RPAs. Command Example:

Symmask list logins –wwn 50012482001063a0

4 Use symcli to mask the replication volumes, journal volumes, and repository volume to the RPA ports.

Command Syntax:

symmask –sid <Symm S/N> –dir <FA#> –p <Port> –wwn <RPA PWWN> add dev <―DEV#:DEV#‖>

Port 0 --- |---|---| | | | |---|---| | Link status | Up | | wwn | 0x50012482001063a0 | | node wwn | 0x50012482001063a1 | | port id | 4f0000 | | operating mode | point to point | | speed | 2 GB | |---|---|

(26)

Step Action

Command Example:

symmask –sid 525 –dir 1c –p 0 –wwn 5001248201b48316 add dev ―79:7c‖

Sample Output: symmask add dev

Note1: Using a device range (for example: ―79:7c‖) works for consecutive device numbers. You will need to re-run the command for each device that is not within a range.

Note2: You will need to re-run the command for all RPA ports in the fabric zoned to the storage port.

5 After masking the replica volumes, the journal volumes, and the repository volume to the RPA ports, use symcli to refresh the vcmdb. Your masking changes will not take effect until you refresh the database.

Command Example:

symmask –sid 525 refresh

6 Verify your changes by listing the masking database. Command Syntax:

symmaskdb list database –dir <FA#> -port <Port#> Command Example:

symmaskdb list database –dir 1c –port 0

(27)

Step Action

7 Log into the RPA as boxmgmt and verify the masking configuration. From the Main menu select Diagnostics > Fibre Channel Diagnostics > Detect Fibre Channel LUNs. You should see the volumes you just masked listed there.

Important: Repeat the procedure for all hosts and RPAs at both local and remote sites. Important: Be sure to perform the following:

 Masking procedure for all RPA ports.

o All RPAs shall see all host data volumes (replica) involved in replication as well as the repository and journal volumes.

 Repeat the procedure using RPA ports and storage ports in the second fabric.

 Repeat the procedure for site 2 (both fabrics).

(28)

Part 5: LUN Masking for the RPA – CLARiiON

Step Action

1 Before we can replicate volumes using RecoverPoint, we must first present the repository, journals, and host volumes (replica) to all RPAs at each site. This means a lot of masking. Refer to the lab environment reference guide for repository, journals, and host volumes (replica) information assigned to you RPA cluster group.

You can use the inq or navicli command on your hosts to identify the host volumes (replica) that must be in a CLARiiON storage group with RPA ports. You will need the CLARiiON LUNs information to verify that these volumes are seen by the RPAs.

Command Example: inq or navicli

Sample Output: inq –clar_wwn

2 Launch Navisphere Manager. Refer to the lab environment reference document for the CLARiiON SP IP addresses to be used by your group.

Inquiry utility, Version V7.3-891 (Rev 2.0) (SIL Version V6.5.2.0 (Edit Lev

el 891)

...

--- DEVICE :VEND :PROD :REV :SER NUM :CAP(kb) --- \\.\PHYSICALDRIVE0 :( :ST310210A :3.17 : : --- \\.\PHYSICALDRIVE1 :KASHYA :KBOX1_SOUTHBORO :0001 : : --- \\.\PHYSICALDRIVE2 :KASHYA :KBOX2_SOUTHBORO :0001 : : --- \\.\PHYSICALDRIVE3 :KASHYA :KBOX2_SOUTHBORO :0001 : : --- \\.\PHYSICALDRIVE4 :KASHYA :KBOX1_SOUTHBORO :0001 : : --- \\.\PHYSICALDRIVE5 :KASHYA :KBOX2_SOUTHBORO :0001 : : --- \\.\PHYSICALDRIVE6 :KASHYA :KBOX1_SOUTHBORO :0001 : : --- \\.\PHYSICALDRIVE7 :KASHYA :KBOX2_SOUTHBORO :0001 : : --- \\.\PHYSICALDRIVE8 :KASHYA :KBOX1_SOUTHBORO :0001 : : --- \\.\PHYSICALDRIVE9 :DGC :RAID 5 :0428 :0B00005A : 5242880 \\.\PHYSICALDRIVE10 :DGC :RAID 10 :0428 :1F00005C : 2097152 \\.\PHYSICALDRIVE11 :DGC :RAID 10 :0428 :1E00005C : 2097152

(29)

Step Action

3 Register the RPA ports on the Connectivity Status Window. In the Enterprise Storage dialog box, navigate to the icon for the storage system whose RPA ports you want to register. Right-click it and select Connectivity Status to open the Connectivity Status dialog box. 4 In Initiator Records, select the HBA that you want to register, and then click Register to

open the Register Initiator Record dialog box.

The selected HBA must have a No value in the Registered column to enable the Register button. There should be 16 of these entries (which are ‗logged in‘). These represent 4 HBAs from each RPA going to 2 CLARiiON SP ports. These entries were created after you

finished your zones.

Connectivity Status Window

Note: If RPA ports are not listed check your zones on both fabrics and fix any issue they

might have.

Note: If RPA ports are not ‗logged in‘, this is a known and possible issue with CLARiiON

arrays. If no I/O happens against the SP ports the initiator will not log in them. To fix this:

 SSH into each RPA as the boxmgmt user.

 From the Main menu select Diagnostics > Fibre Channel diagnostics > Detect

Fibre Channel LUNs.

 Running this should make the RPAs to log into the CLARiiON SP ports. Therefore, the initiators ‗logged in‘ status should change to ‗Yes‘.

(30)

Step Action

5 Verify that the HBA WWN and the SP Port ID are correct and set Initiator Type to

RecoverPoint Appliance. Set Failover Mode to 4. Unless the storage system is connected

to a Solaris server, set Unit Serial Number to Array. Enter the Vendor and Model for the initiator. Under ―This HBA Belongs to‖, click New Host and enter RPA name and address or click Existing Host, and then from the list, select the RPA. Save your changes and close the dialog box to return to the Connectivity Status dialog box.

Register Initiator Window

Note: Alternatively, you can use group edit (previous window) and register all RPAs HBAs

as one single entity.

 Initiator type is RecoverPoint Appliance (31).

 Failover mode should be set to 4.

 Use the management IP of the first RPA to identify the host.

6 You will need to make the host volumes (replica) visible to the RPA ports by adding the volumes to a RPA storage group. View the existing host storage group to verify which volumes are visible. Alternately, you can use inq, syminq or navicli from the host itself.

(31)

Step Action

7 Create a new storage group for the RPAs. You will be adding the host volumes (replica LUNs), the journal volumes, and the repository volume to this storage group. From the

Storage tab of the Enterprise Storage dialog box, navigate to the icon for the storage

system on which you want to create the storage group, right-click, and then select Create

Storage Group.

Creating a Storage Group

8 Assign a name to your storage group, and click OK or Apply to save your changes.

9 Add the RPAs to the storage group. From the Storage tab of the Enterprise Storage dialog box, navigate to the icon for the storage group to which you want to connect a server, right-click, and then select Connect Hosts.

(32)

Step Action

10 Add the RPAs as Hosts to be Connected. Click Apply to save the changes.

Adding RPAs to the Storage Group

Note: In case you used ‗group edit‘ in the RPA HBA registration window (connectivity status), there will be only one RPA listed here.

(33)

Step Action

11 Click on the LUNs tab. Under the Show LUNs: drop down select All. Select all the host volumes (replica LUNs) to be used for replication, select all the LUNs to be used as journal volumes, and select the LUN to be used as the repository volume. LUN information for each

group are listed in the lab environment reference document. Click OK or Apply to save the

changes.

Adding LUNs to the Storage Group

12 Expand the Hosts and LUNs icons under your storage group to view the resulting configuration.

(34)

Step Action

13 Log into the RPA as boxmgmt and verify the masking configuration. From the Main menu select Diagnostics > Fibre Channel Diagnostics > Detect Fibre Channel LUNs. The LUNs you just masked to the RPA should be listed there.

Sample Output: Detect Fibre Channel LUNs

Important: Be sure to perform the following:

 Masking procedure for all RPA ports.

o All RPAs shall see all host data volumes (replica) involved in replication as well as the repository and journal volumes.

 Repeat the procedure for site 2.

End of Lab Exercise

|---|---|---|---|---|---|---| | |Size |Vndr |Product |Name |UID |Site | |---|---|---|---|---|---|---| | 1. | 3.94GB | EMC | SYMMETRIX | DEV ID: 00A2 | 60,06,04,80, | | | | | | | | 00,01,90,30, | | | | | | | | 11,55,53,30, | | | | | | | | 30,30,41,32 | | | 2. | 3.94GB | EMC | SYMMETRIX | DEV ID: 0073 | 60,06,04,80, | | | | | | | | 00,01,90,30, | | | | | | | | 11,55,53,30, | | | | | | | | 30,30,37,33 | |

(35)

Lab Exercise 2: Installation of RecoverPoint Appliances

Purpose:

Install the RecoverPoint Appliances using Deployment Manager. Once connected to the RPA over the IP network you will have to configure all RPA parameters for your specified cluster. Once the RPAs are installed they are ready to be configured for replication activities.

Tasks:

 Connect to the RPAs using the RecoverPoint Deployment Manager and perform configuration of site layout, replication method, site information, IP parameters, and repository volume.

References:

 RecoverPoint Student Guide

 RecoverPoint Administrator‘s Guide

(36)

Part 1: RPA Cluster Installation

Step Action

1 Log into all RPAs in both site 1 and site 2 as boxmgmt and make sure they allow communications.

As previously noted, all RPAs already have management IP so activities can be performed from the classroom. Therefore, you can skip this step.

2 From a Remote Desktop Connection into one of the Windows hosts assigned to your group, launch RecoverPoint Deployment Manager (install.exe). You should be able to find it in drive C: folder \software\. If you cannot find it, download it from RecoverPoint Software Downloads page on Powerlink. Login as ‗EMC personnel‘; username: admin / password:

(37)

Step Action

3 Select ‗RecoverPoint Installer Wizard‘.

4 Ensure the requirements for running the Installer are met. Select checkbox ‗I have fulfilled

(38)

Step Action

5 Create a new installation configuration file. Name the file to something convenient and

(39)

Step Action

6 Define the ‗Installation Structure‘ including Local and Remote sites general networking details.

Number of Sites: 2 Number of RPAs per site: 2

WAN IP type: IPv4

Remote replication to be done over: IP

Site 1 Settings Site name: Local Time zone: GMT-05:00 Management IP type: IPv4

Domain name: <blank>

Primary DNS server: <refer to lab info sheet> Secondary DNS server: <refer to lab info sheet>

NTP Server 1: <refer to lab info sheet> NTP Server 2: <blank>

Site 2 Settings Site name: Remote Time zone: GMT-05:00 Management IP type: IPv4

Domain name: <blank>

Primary DNS server: <refer to lab info sheet> Secondary DNS server: <refer to lab info sheet>

NTP Server 1: <blank> NTP Server 2: <blank>

Notes:

1. Set time zones for both sites.

2. In this lab deployment use the same Primary and Secondary DNS Servers at both sites. 3. Leave the fields for Local Domain blank.

(40)

Step Action

7 Enter Local Site and RPAs IP information.

Please note that the “Site Management IP” and “RPA Management IP” are not the same. “Site Management IP” (floating) is an unique address per site. Each RPA has two IP addresses: one for management and one for replication.

(41)

Step Action

8 Leave Local Site advanced settings window with the default values.

Note: Choose „Yes‟ in the first option if you have zoned and masked the ESX Server available in your setup. That is OK if you plan on doing those steps later.

(42)

Step Action

9 Enter Remote Site and RPAs IP information.

Please note that the “Site Management IP” and “RPA Management IP” are not the same. “Site Management IP” (floating) is an unique address per site. Each RPA has two IP addresses: one for management and one for replication.

(43)

Step Action

10 Leave Remote Site advanced settings window with the default values.

Note: Choose „Yes‟ in the first option if you have zoned and masked the ESX Server available in your setup. That is OK if you plan on doing those steps later.

(44)

Step Action

11 Login as user boxmgmt and install Local and Remote sites. All RPAs in both sites must

have management IP address information set in order to succeed in this step.

(45)

Step Action

13 Move on to next step as zoning and masking tasks have been performed previously.

Note: When zonings and masking have not been completed yet at this point, use the RPA WWNs information displayed here to complete these tasks.

(46)

Step Action

14 SAN diagnostics check. Issues with zoning and masking will be verified during this step.

Note: RPAs shall see host and storage ports. Also, RPAs must have access to all volume types: repository, journals and host data volumes.

(47)

Step Action

15 Select the ‗unique‘ Repository volume at Local site. The volume should have been

presented to all RPAs at the site via masking. Refer to the lab information sheet to identify

the Repository volume assigned to your group.

16 In our lab environment there is a mix of storage array types. Our replication structure is from CLARiiON to Symmetrix or vice-versa. One important note to make is that the

Repository volume size recommendation is 3GB and extra space is not used. Ignore warning messages in case the repository volume assigned to your group is greater than 3GB. Of

course, you do not want to do the same at a customer environment as you would be “wasting” storage space.

(48)

Step Action

17 Verify that you have selected the correct volume to be the Repository at Local site. Be

careful, as result of this task the volume will be formatted.

18 Local site RPAs attach and reboot. After repository volume is formatted, all

RPAs at the site attach to cluster and reboot. The Installer waits and holds the session until all RPAs are back online.

(49)

Step Action

19 After all RPAs at the site reboot, the Installer displays a summary of Local site installation, including repository volume details.

At this point all RPAs at Local site are installed and configured, now move on to install and configure RPAs at Remote site.

20 As part of the process of installing and configuring RPAs at Remote site, select

and format the unique Repository volume at that site.

21 Remote site RPAs attach and reboot. After repository volume is formatted, all

RPAs at the site attach to cluster and reboot. The Installer waits and holds the session until all RPAs are back online.

22 After all RPAs at the site reboot, the Installer displays a summary of Remote site installation, including repository volume details.

(50)

Step Action

23 When RPAs at both Local and Remote sites are completed installed and configured, the RPA cluster is deployed. You can now connect into the

RecoverPoint Management Application by either launching it from the Final Summary window or firing up Internet Explorer and pointing it to the site management IP (floating IP) at either Local or Remote site.

Note: A configuration file is created and saved locally in your service station. Refer to step 5 for the name of the file. This file can be used to reconstruct the RPA cluster, initial install only – repository volumes are formatted if Installer used again. Therefore, it should not be used for RPA cluster changes.

(51)

Part 2: RPA Installation – Add RecoverPoint License

Step Action

1 Open Internet Explorer and point the browser to the Site Management IP (floating) of either Site 1 or Site 2. Log in as user admin on the RecoverPoint Management Application. Click

Yes on the License Problem pop-up - OR

Click on the link on the lower left-hand corner of the main window and enter the account ID and license key. There is no activation code for our environment.

First Time Login as admin: Prompt for license information

2 Enter the Account ID, company name and contact info then click the Update button to add the license key. You will not be adding software serial ID neither an activation code for the lab environment. Ask your instructor for these information.

(52)

Step Action

3 Enter the License Key and click OK.

Update License Key

(53)

Lab Exercise 3: Installing Host Splitter Drivers

Purpose:

Perform the installation of the Host Splitter Driver (kdriver) on Windows, Solaris and AIX hosts

Tasks:

 Installation of the Windows splitter driver

 Installation of the Solaris splitter driver

 Installation of the AIX splitter driver

References:

 Lecture material

 Administrators Guide

(54)

Part 1: Host Splitter Driver Installation - Windows

Step Action

1 Log on to your assigned server as ―Administrator‖.

2 _{Copy the kdriver installation package to a temporary directory on your server. Be sure to} copy a version of the kdriver that supports the RecoverPoint revision on the RPAs.

Note: The lab servers may already have the installation package in C:\software. If not,

download it from the RecoverPoint software downloads page on Powerlink.

3 Extract the contents of the kdriver installation package. To install the kdriver, double-click on the file setup.exe.

(55)

Step Action

5 Select Typical when prompted for the Installation Mode to accept the defaults for log file location and size. To change the log file location and size, select Custom.

6 When zoning and volume presentation has been correctly configured, you should not receive any errors; your view will be something similar to this:

SAN Diagnostics – No Errors

Note: During the install, the setup.exe program will run diagnostics on the system and the state of its configuration. If the host has not been zoned and does not see SAN connectivity or appliance volumes, these configurations should either be made or rectified.

(56)

Step Action

7 Once the installation completes, click Finish to exit the setup and restart the computer.

Restart Host

8 After the system reboots verify the kdriver is running by checking Services for the KDriverWatchdog service.

(57)

Step Action

9 Run an inq or syminq command and verify that the host sees the appliance as a disk. Important: Repeat Steps 1 through 9 for each Windows host in the replication environment (both sites).

(58)

Part 2: Host Splitter Driver Installation – Solaris

Step Action

1 Log on to your assigned server as ―root‖.

2 Copy the kdriver installation package to a temporary directory on your server. Be sure to copy a version of the kdriver that supports the RecoverPoint revision on the RPAs.

Note: The lab servers may already have the installation package in /software/. If not, download it from the RecoverPoint software download page on Powerlink.

3 Decompress the file. Command Example: gunzip filename

Decompress File

sl—sunl /software/solaris/kdriver ls —la total 19956

drwxr—xr—x 2 root root 512 Sep 8 08:27 drwxr—xr—x 7 root other 512 Sep 8 08:27 —ru—r——r—— 1 root root 10199278 Sep 8 08:28

EMC_RecoverPoint_driver_sol5x_rel3.3.P2_e.95_md5_29d9ef567b9f46cd31432f42 aa81d7f0.pkg.gz

sl—sunl /software/solaris/kdriver gunzip

EMC_RecoverPoint_driver_sol5x_rel3.3.P2_e.95_md5_29d9ef567b9f46cd31432f42 aa81d7f0.pkg.gz

sl—sunl /software/soiaris/kdriver ls —la total 83604

drwxr—xr—x 2 root root 512 Sep 8 08:29 drwxr—xr—x 7 root other 512 Sep 8 08:27

—rw—r——r—— 1 root root 42767360 Sep 8 08:28 kdriver_3.3.e.95_sol.pkg s1—sun1 /software/solaris/kdriver

(59)

Step Action

4 Use pkgadd –d to install the kdriver package:

Beginning Pkgadd Installation

5 When prompted, enter y to continue the installation.

6 Correct any errors detected by SAN diagnostics.

Note: The system conducts a series of automatic tests that are designed to identify a variety of

the most common problems regarding the host configuration in the SAN environment on which RecoverPoint is being installed. It is desirable to identify these problems before installing the kdriver on the host. Upon completion of these tests, a report confirms successful completion of the SAN diagnostics (i.e., no errors or warnings), or details the errors or potential errors (i.e., warnings) detected in the host configuration on the SAN.

7 When prompted, designate the directory in which to store log files and designate the maximum log file size (default is 500 MB). The default destination folder is /kdriver/log.

Setting Log Directory and Size

Do you want to proceed with the installation (y/q)? y

Please enter the log files directory (q-quit)? [/kdriver/log] Please enter the log files maximum size [MB] (q-quit)? [500] kconfigure – success

installation of <kdriver> was successful.

sl—sunl /software/solaris/kdriver pkgadd -d kdriver_3.3.e.95_sol.pkg The following packages are available:

1 kdriver kdriver

(sparc) 3.3(e.95)

Select package(s) you wish to process (or 'all' to process all packages). (default: all) [?,??,q]:

(60)

Step Action

8 When the installation completes, reboot the host. Command Example:

reboot -- -r

Note: From this point, the kdriver is started automatically any time the system is rebooted. To manually start or stop the kdriver use the /etc/init.d/kdrv start and /etc/init.d/kdrv stop commands. The /etc/init.d/kdrv status command returns the current status of the driver (UP or DOWN).

9 There are several commands that can be run on Solaris to verify that the splitter driver is installed and running properly. The pkginfo command displays information about software packages that have been installed on the system. Look at the STATUS field to verify the driver was installed.

Command Example:

pkginfo –l kdriver

Sample Output: pkginfo –l kdriver

10 The modinfo command will display information about loaded kernel modules. Command Example:

modinfo | grep -i splitter

s1-sun1 / modinfo | grep –I splitter

286 78666000 2a450 282 1 splitter (KashyaSplitter)

sl—sunl /software/solaris/kdriver pkginfo –l kdriver

PKGINST: kdriver NAME: kdriver CATEGORY: application ARCH: sparc VERSION: 3.3 BASEDIR: / PSTAMP: sol15920080219184442 INSTDATE: Sep 2 2009 10:43 STATUS: completely installed

FILES: 118 installed pathnames 13 directories

48 executables

(61)

Step Action

11 The ps command displays the status of processes running on the system. Command Example:

ps –ef | grep kdriver

Sample Output: ps –ef | grep kdriver

12 Run an inq or syminq command and verify that the host sees the appliance as a disk.

Sample Output: inq

Important: Repeat these steps for each Solaris host in the replication environment (both sites)

End of Lab Exercise

s1-sun1 / syminq | grep KASHYA

/dev/rdsk/c2t0d0s2 KASHYA KBOX2_S1BOS1 0001 N/A 983500000 /dev/rdsk/c2t1d0s2 KASHYA KBOX1_S1BOS1 0001 N/A 983500000 /dev/rdsk/c4t0d0s2 KASHYA KBOX1_S1BOS1 0001 N/A 983500000 /dev/rdsk/c4t1d0s2 KASHYA KBOX2_S1BOS1 0001 N/A 983500000 /dev/vx/rdmp/c2t0d0s2 KASHYA KBOX2_S1BOS1 0001 N/A 983500000 /dev/vx/rdmp/c2t1d0s2 KASHYA KBOX1_S1BOS1 0001 N/A 983500000 /dev/vx/rdmp/c4t0d0s2 KASHYA KBOX1_S1BOS1 0001 N/A 983500000 /dev/vx/rdmp/c4t1d0s2 KASHYA KBOX1_S1BOS1 0001 N/A 983500000

s1-sun1 / ps –ef | grep kdriver

root 462 461 0 10:49:50 ? 0:03 /kdriver/bin/kdriver root 461 1 0 10:49:50 ? 0:00 /kdriver/bin/kdrive_swd 60 /kdriver 1 60 0

(62)

Part 3: Host Splitter Driver Installation – AIX

Step Action

1 Copy the installation file to the AIX host. Decompress the file by running the command:

gunzip filename

Use the installp command to install the kdriver on both the Site 1 and Site 2 hosts: installp -d install_file kdriver 2.0.0.0

Be sure to copy a version of the kdriver that supports the RecoverPoint revision on the RPAs.

Note: The lab servers may already have the installation package in /software/. If not, download

it from the RecoverPoint software download page on Powerlink. # ls .toc EMC_RecoverPoint_driver_aix52_53_rel3.3.P2_e.95_md5_3340323768c23fff7a ccc8154ed589f9.bff # installp -d EMC_RecoverPoint_driver_aix52_53_rel3.3.P2_e.95_md5_3340323768c23fff7a ccc8154ed589f9.bff kdriver 2.0.0.0 +---+ Pre-installation Verification... +---+ Verifying selections...done Verifying requisites...done Results... SUCCESSES ---

Filesets listed in this section passed pre-installation verification and will be installed.

Selected Filesets --- kdriver.bin 2.0.0.0 # kdriver kdriver.hlr 2.0.0.0 # kdriver kdriver.info_collector 2.0.0.0 # kdriver kdriver.install 2.0.0.0 # kdriver kdriver.kutils 2.0.0.0 # kdriver kdriver.lib 2.0.0.0 # kdriver kdriver.log 2.0.0.0 # kdriver kdriver.modules 2.0.0.0 # kdriver kdriver.tweak 2.0.0.0 # kdriver

(63)

Step Action

2 Examine the install output to verify the splitter was successfully defined.

3 After the installation completes, run the rc.kdrv configure command to configure the splitter. # rc.kdrv configure _ __ _____ _ | |/ /| __ \ (_) | ' / | | | | _ __ _ __ __ ___ _ __ | < | | | || '__|| |\ \ / // _ \| '__| | . \ | |__| || | | | \ V /| __/| | |_|\_\|_____/ |_| |_| \_/ \___||_| Running kconfigure

Installing RecoverPoint.AIX.5.2_5.3.1.0.0.0 from /kdriver/install/ RecoverPoint.AIX.5.2_5.3.1.0.0.0 alredy installed

Searching for RecoverPoint devices... Loading the 64 bit module...

Running SAN diagnostics. This may take a few moments...

SAN diagnostic information:

--- COPYRIGHT NOTICE ---

. . . << End of copyright notice for kdriver >>. . . .

Creating the splitter device splitter0 Defined

Adding the Config_Rules to the ODM Please run rc.kdrv configure

Creating link for /usr/sbin

RecoverPoint Implementation Lab 3.3