After all units have been created, proceed here as follows:
1. Set the maximum cached transfer size to one with the following CLI command:
SET UnitName MAXIMUM_CACHED_TRANSFER_SIZE = 1
Repeat this step for each unit.
2. Verify that the access on each unit is set to none by using the following CLI command:
SHOW UNITS FULL
You will see a display similar to that in "Example Display 9."
Example Display 9
LUN Uses Used by
---------------------------------------------------------------------------
D1 DISK10000
LUN ID: nnnn-nnnn-nnnn-nnnn-nnnn-nnnn-nnnn-nnnn
NOIDENTIFIER
Switches:
RUN NOWRITE_PROTECT READ_CACHE
READAHEAD_CACHE WRITEBACK_CACHE
MAXIMUM_CACHED_TRANSFER_SIZE = 1
Access:
NONE
State:
ONLINE to this controller
Not reserved
416 Data Replication Manager HSG80 ACS Version 8.5P Operations Guide for Novell NetWare Version 5.1
NOPREFERRED_PATH
Size: nnnnnnnn blocks
Geometry (C/H/S): ( 7000 / 20 / 254 )
3. Distribute the units by setting their preferred path. Use either of the following CLI
commands:
SET UnitName PREFERRED_PATH=THIS_CONTROLLER
or
SET UnitName PREFERRED_PATH=OTHER_CONTROLLER
Keep the busiest units on different host ports.
4. After configuring the units, restart the controllers with these CLI commands.
Otherwise, the preferred path settings will not go into effect:
RESTART OTHER_CONTROLLER
RESTART THIS_CONTROLLER
5. Once the controllers have restarted, ensure that your storage settings are in place with
the following CLI command:
SH OW Storagesets FULL
Configuring a Data Replication Manager Solution 417
Cabling the Target Site
Connect Fiber Optic Cables Between the Controllers and
Fiber Channel Switches
This procedure specifies how to make fiber optic connections. Figure 42 shows the port
locations on the Fibre Channel switch.
CXO7085A
Figure 42. Switch port locations on a Fibre Channel switch
1. Make sure that you have installed all required GBICs into each of the Fibre Channel
switches.
2. Connect a multi-mode, 50-micron fiber optic cable from port 1 of the top controller to
port 2 of the top Fibre Channel switch (as shown by callout 1 in Figure 43).
3. Connect a second multi-mode, 50-micron fiber optic cable from port 2 of the top
controller to port 4 of the top Fibre Channel switch (as shown by callout 2 in
Figure 43).
4. Connect a third multi-mode, 50-micron fiber optic cable from port 1 of the bottom
controller to port 2 of the bottom Fibre Channel switch (as shown by callout 3 in
Figure 43).
5. Connect a fourth multi-mode, 50-micron fiber optic cable from port 2 of bottom
controller to port 4 of the bottom Fibre Channel switch (as shown by callout 4 in
Figure 43).
NOTE: You should see an illuminated green LED on the switch as soon as the cable is inserted
at both ends. This verifies that there is a good connection.
Figure 43 shows what your cabling should look like. The numbered callouts reflect the
steps that you just completed.
418 Data Replication Manager HSG80 ACS Version 8.5P Operations Guide for Novell NetWare Version 5.1
2
1
3
4
CXO7086A
Figure 43. Cabling between the controllers and switches
Connect the Target Site to the External Fiber Link
Locate the connection points at the target site that link the target site to the initiator site.
Look for either a fiber optic cable connector or a patch panel where you can insert a cable.
Long Wave GBICs
1. Connect a single-mode, 9-micron fiber optic cable from port 6 of the top switch to one
connection point (as shown by callout 2 of Figure 44).
2. Connect another single-mode, 9-micron fiber optic cable from port 6 of the bottom
switch to the other connection point (as shown by callout 3 of Figure 44).
Other Transport Modes
Data Replication Manager also uses other long distance transport modes. For connection
information, refer to our website at:
http://www.compaq.com/storage
The target site is now physically linked to the initiator site. See Figure 44 for an
illustrated view of how this cabling should appear.
Configuring a Data Replication Manager Solution 419
NOTE: You can make sure that switches and ports are connected as you have them
documented by issuing the nbrStateShow command at the switch. Issue the topologyShow
command at the switch to reveal if you have more than one fiber optic cable between the
switches on each site.
1
2
3
1
CXO7087A
Figure 44. Cabling from the target site to the initiator site
420 Data Replication Manager HSG80 ACS Version 8.5P Operations Guide for Novell NetWare Version 5.1
Configure the Host at the Target Site
Install the Host Bus Adapters and Drivers
You should install two host bus adapters in each host system. Refer to the Compaq
StorageWorks 66-Bit/66 MHz Fibre Channel Host Bus Adapter Installation Guide for
installation information.
Install Secure Path Agent
For installation information, refer to the Compaq SANWorks Secure Path Version 3.0 for
Novell Netware Installation and Reference Guide.
1. Verify that the Secure Path Agent is installed by going to the server console screen and
typing modules cpqspagt. Ensure that the Secure Path Agent is set for automatic
startup. Normally, the SP Install program sets automatic startup by loading
cpqspagt.nlm in the autoexec.ncf file.
2. Use the Secure Path Agent Configuration screen at the server to grant access to the
client at both the initiator and target sites. To do this:
a. From the NetWare server, toggle to the Secure Path NLM screen.
b. At the Main Menu, select 2) Client Administration, then select 2) Add a Client.
c. Type fully-qualified DNS name for the client, then press Enter.
d. Press Escape to return to Main Menu.
3. You can set the password and allow client access via the Secure Path Agent
Configuration.
a. At the Main Menu, select 1) Agent Administration, then select 1) Change
Password.
b. Type a password for client access, then re-type the password for verification.
c. Press Escape to return to the Main menu.
NOTE: Compaq recommends that you set both the fully qualified and unqualified DNS names as
valid, authorized clients.
Configuring a Data Replication Manager Solution 421
Install Secure Path Manager (SPM)
For installation information, refer to the Compaq SANWorks Secure Path Version 3.0 for
Novell Netware Installation and Reference Guide.
Install SWCC (Optional)
For detailed information about SWCC, refer to the Compaq StorageWorks Command
Console User Guide.
Connect Fiber Optic Cables Between the Hosts and the Switches
Connecting the fiber optic cables involves two stages:
s Connecting the cables
s Renaming the host connections
Both are described in the following sections.
Connecting the Fiber Optic Cable
1. Establish the cabling policy that you plan to follow.
2. Connect a multi-mode, 50-micron fiber optic cable from port 0 of the top switch to one
adapter on a host (as shown by callout 1 of Figure 45).
3. Connect the final multi-mode, 50-micron fiber optic cable from port 0 of the bottom
switch to the other adapter on the same host (as shown by callout 2 of Figure 45).
NOTE: You may choose any available port to connect your cables to, but you must maintain that
identical scheme at the initiator site. Therefore, if port 1 of controller B is connected to port 2 of
the bottom switch at the target site, then port 1 of controller B must be connected to port 2 of
the bottom switch at the initiator site.
4. If you have more than one host (up to six), connect one host bus adapter to one of the
remaining ports on the top switch. Connect the other host bus adapter to the same
numbered port on the bottom switch.
The hosts are now connected to the target site switches via the multi-mode, 50-micron
fiber optic cables. Your cabling should appear as it does in Figure 45.
422 Data Replication Manager HSG80 ACS Version 8.5P Operations Guide for Novell NetWare Version 5.1
5. Verify that the connection between the host and the switch has been made by entering
this CLI command:
SH OW CONNECTIONS
You should see a display similar to that in "Example Display 10."
NOTE: You can also verify that a connection has been made by looking for the illuminated green
LED that flashes on the switch ports.
1 2
CXO7088A
Figure 45. Cabling between the hosts and the switches
Example Display 10
Connection Unit
Name Operating system Controller Port Address Status Offset
!NEWCON00 WINNT THIS 1 210013 online 0
HOST_ID=nnnn-nnnn-nnnn-nnnn .... ADAPTER_ID=nnnn-nnnn-nnnn-nnnn
!NEWCON01 WINNT OTHER 1 200013 online . . . 0
HOST_ID=nnnn-nnnn-nnnn-nnnn .... ADAPTER_ID=nnnn-nnnn-nnnn-nnnn
Configuring a Data Replication Manager Solution 423
Rename the Host Connections at the Target Site
To better identify which hosts you are working with, Compaq recommends that you
rename the host connections, using a meaningful connection name for each one. Each host
bus adapter will appear as a connection. An individual host bus adapter can be identified
by its World Wide Name that you recorded in the Chapter 3, "Getting Started," and that
appears in the connection description.
IMPORTANT: If you will be using scripting to automate failover and failback operations, do not
use dashes (hyphens) as separators in your naming convention--use underscores instead.
Dashes are not allowed by the Perl scripting language.
Initially, each connection is named !NEWCONxx. It is much easier to track connections if
the connection names are meaningful, for example: HostA1.
1. We suggest that you use the worksheet in Figure 46 when renaming your hosts. Fill in
the fields accordingly to prepare for renaming your connections.
!NEWC ONxx World Wide Name Host Name Path Number
Figure 46. Host renaming worksheet
2. When you have completed the worksheet, rename the connections using the following
CLI commands:
RENAME !NEWCONxx TargetHostConnectionNamex
Exam ple: RENAME !NEWCONxx hostA1
RENAME !NEWCONxx TargetHostConnectionNamey
Exam ple: RENAME !NEWCONxx hostA2
424 Data Replication Manager HSG80 ACS Version 8.5P Operations Guide for Novell NetWare Version 5.1
3. Set the connection type to NetWare by enteringentering the following CLI command:
SET TargetHostConnectionNamex OPERATING_SYSTEM = NETWARE
Example: SET HOSTA1 OPERATING_SYSTEM = NETWARE
Perform step 3 for each connection.
4. When you have finished renaming your host connections, enter the following
command to see your new settings:
SH OW CONNECTIONS
You should see a display similar to that in "Example Display 11."
Example Display 11
Connection Unit
Name Operating system Controller Port Address Status Offset
HostA1 NETWARE THIS 1 210013 online . . . 0
HOST_ID=nnnn-nnnn-nnnn-nnnn .... ADAPTER_ID=nnnn-nnnn-nnnn-nnnn
HostA2 NETWARE OTHER 1 200013 online . . . 0
HOST_ID=nnnn-nnnn-nnnn-nnnn .... ADAPTER_ID=nnnn-nnnn-nnnn-nnnn
Configuring a Data Replication Manager Solution 425
Configure the Controllers at the Initiator Site
Prior to configuring the controllers at the initiator site, be sure to follow these steps:
s Identify the World Wide Name on the host bus adapters.
s Establish the name that you will assign to the initiator site. This name should be
different from the one you assigned to the target site.
NOTE: Initiator site procedures are shown as shaded text to differentiate them from the similar
target site procedures.
Controller Configuration Procedure
To get your DT system up and running you must set up and configure the controllers.
These tasks are outlined below:
1. Ensure that all storage enclosures, Fibre Channel switches, Power Distribution
Units (PDUs), and the main power supply are off.
2. Plug all cabinet PDU power cords into the main power receptacles.
3. Be sure that you have a serial connection to each of the controllers.
4. Apply power to the main power source.
5. Turn on all PDUs.
6. Ensure that the Fibre Channel switches are powered on, but not cabled.
NOTE: When the storage enclosures are turned on, the controllers will boot if the PCMCIA
cards are already installed. If there are no cards in the controller slots, insert them now, and
press the reset button. Refer to the Compaq StorageWorks HSG80 Array Controller
ACS V8.5 Configuration Guide for complete instructions on how to properly seat the
controller cards.
7. Turn on the storage enclosures.
8. Establish a local connection to the controllers. Refer to the Compaq StorageWorks
HSG80 Array Controller ACS V8.5 Maintenance and Service Guide for
instructions.
9. Verify that all controllers are on and functional by looking for the CLI prompt on
the maintenance port of each controller.
NOTE: Unless otherwise noted, all operations may be conducted from controller A.
426 Data Replication Manager HSG80 ACS Version 8.5P Operations Guide for Novell NetWare Version 5.1
10. Issue the following CLI command:
SHOW THIS_CONTROLLER
You will see a display similar to that in "Example Display 12."
Example Display 12
Controller:
HSG80 ZG8nnnnnnn Software V85P, Hardware E03
NODE_ID = nnnn-nnnn-nnnn-nnnn
ALLOCATION_CLASS = 0
SCSI_VERSION = SCSI-2
Not configured for dual-redundancy
Controller misconfigured -- other controller present
Device Port SCSI address 7
Time: NOT SET
Command Console LUN is disabled
Host PORT_1:
Reported PORT_ID = nnnn-nnnn-nnnn-nnnn
PORT_1_TOPOLOGY = OFFLINE (offline)
Host PORT_2:
Reported PORT_ID = nnnn-nnnn-nnnn-nnnn
PORT_2_TOPOLOGY = OFFLINE (offline)
NOREMOTE_COPY
Cache:
512 megabyte write cache, version 0012
Cache is GOOD
No unflushed data in cache
CACHE_FLUSH_TIMER = DEFAULT (10 seconds)
Mirrored Cache:
Not enabled
Configuring a Data Replication Manager Solution 427
Battery:
FULLY CHARGED
Expires:
NOCACHE_UPS
Controller misconfigured. Type SHOW THIS_CONTROLLER
11. Verify that the subsystem World Wide Name is set.
If it is, go to step 14.
If the World Wide Name has not been assigned to the controller, you will need
to obtain the name and set it before proceeding.
NOTE: The subsystem's World Wide Name and checksum can be found on a sticker, which
is located on top of the frame that houses the controllers, EMU, PVA, and cache modules.
This sticker also includes a checksum which is required to verify that the World Wide Name
is valid. If there is no label there, contact your Compaq customer service representative for
assistance. Refer to the Compaq StorageWorks HSG80 Array Controller ACS V8.5
Configuration Guide for more information on World Wide Names. Each subsystem's World
Wide Name begins with 5000 and ends in zero, for example 5000-1FE1-FFOC-EEOO. The
controller port IDs are derived from the World Wide Name.
CAUTION: Never set two subsystems to the same World Wide Name, or data
corruption will occur.
12. After the World Wide Name has been located, assign it to the controller using the
following CLI command:
SET THIS NODE_ID=node_ID checksum
You will see a display similar to that in "Example Display 13."
Example Display 13
Warning 4000: A restart of this controller is required before all the
parameters modified will take effect
%CER--HSG80> --09-FEB-1999 10:07:54-- Restart of this controller required
Restart of this controller required
428 Data Replication Manager HSG80 ACS Version 8.5P Operations Guide for Novell NetWare Version 5.1
13. Issue a SHOW THIS_CONTROLLER command to verify that the World Wide
Name has been set.
You will see a display similar to that in "Example Display 14."
Example Display 14
Controller:
HSG80 ZG8nnnnnnn Software V85P, Hardware E03
NODE_ID = nnnn-nnnn-nnnn-nnnn
ALLOCATION_CLASS = 0
SCSI_VERSION = SCSI-2
Not configured for dual-redundancy
Controller misconfigured -- other controller present
Device Port SCSI address 7
Time: NOT SET
Command Console LUN is disabled
14. Configure the controllers for multiple bus failover mode by issuing the following
CLI command:
SET MULTIBUS_FAILOVER COPY=THIS_CONTROLLER
This command automatically restarts the "other" controller.
A %LFL and %EVL prompt will then be displayed. Refer to the Compaq
StorageWorks HSG80 Array Controller ACS V8.5 Maintenance and Service Guide
for more details on these reports.
15. To ensure that the setting from step 14 has been applied, enter:
SHOW THIS_CONTROLLER FULL
Check the display to verify that the controllers have been configured to support
multiple bus failover mode.
You will see a display similar to that in "Example Display 15."
Configuring a Data Replication Manager Solution 429
Example Display 15
Controller:
HSG80 ZG8nnnnnnn Software V85P, Hardware E03
NODE_ID = nnnn-nnnn-nnnn-nnnn
ALLOCATION_CLASS = 0
SCSI_VERSION = SCSI-2
Configured for MULTIBUS_FAILOVER with ZG8nnnnnnn
In dual-redundant configuration
Device Port SCSI address 7
Time: NOT SET
Command Console LUN is lun 0 (NOIDENTIFIER)
NOTE: These settings will automatically be applied to controller B. Therefore, it is not
necessary to repeat these steps again on controller B.
16. Enter the following CLI command:
SET THIS SCSI = SCSI-3
NOTE: D0 (D-zero) can no longer be used as a device LUN.
17. Verify that the settings have been accepted on controller B by using the following
CLI command:
SHOW OTHER_CONTROLLER FULL
18. Change your controller prompts to help you easily identify which component you
are working on. Enter the following CLI commands:
SET THIS_CONTROLLER PROMPT="InitiatorControllerNameTop> "
SET OTHER_CONTROLLER PROMPT="InitiatorControllerNameBottom> "
Example: SET THIS_CONTROLLER PROMPT="BuildngATop> "
Example: SET OTHER_CONTROLLER PROMPT="BuildngABottom> "
NOTE: This action will take effect immediately
430 Data Replication Manager HSG80 ACS Version 8.5P Operations Guide for Novell NetWare Version 5.1
19. Verify that the settings you have established from controller A have been applied to
controller B by using the following CLI command:
SHOW OTHER_CONTROLLER
20. Check to see if mirrored write-back cache is enabled by using the following CLI
command:
SHOW THIS_CONTROLLER
You should see a display similar to that in "Example Display 16."
Example Display 16
Mirrored Cache:
Not enabled
21. If mirrored cache is not enabled, issue the following CLI command:
SET THIS_CONTROLLER MIRRORED_CACHE
The controllers will restart after mirrored write-back cache has been set, and you
will see %LFL and %EVL displays
NOTE: It may take up to five minutes after controller restart to check the cache. The
controllers will reject this command until the cache check is complete. If this command is
rejected, don't restart the controllers. Wait a few minutes, then retry.
22. After the controllers restart, issue the following CLI command to confirm that
mirrored write-back cache is enabled:
SHOW THIS_CONTROLLER
Notice that mirrored write-back cache is now set. You will see a display similar to
that in "Example Display 17."
Configuring a Data Replication Manager Solution 431
Example Display 17
Mirrored Cache:
256 megabyte write cache, version 0012
Cache is GOOD
No unflushed data in cache
NOTE: It is not necessary to repeat this step on controller B.
23. Set the fabric topology for each port on both controllers using the following CLI
commands:
NOTE: You will be prompted to restart the controllers after each command, but you do not
need to restart the controllers until all topologies have been set.
SET THIS_CONTROLLER PORT_1_TOPOLOGY=FABRIC
SET THIS_CONTROLLER PORT_2_TOPOLOGY=FABRIC
SET OTHER_CONTROLLER PORT_1_TOPOLOGY=FABRIC
SET OTHER_CONTROLLER PORT_2_TOPOLOGY=FABRIC
24. Restart the controllers with these CLI commands:
RESTART OTHER_CONTROLLER
RESTART THIS_CONTROLLER
25. After the controllers have restarted, verify that the topology is set correctly with the
following CLI commands:
SHOW THIS_CONTROLLER
SHOW OTHER_CONTROLLER
You will see a display similar to that in "Example Display 18."
Example Display 18
Host PORT_1:
Reported PORT_ID = nnnn-nnnn-nnnn-nnnn
. . . . . . . . . . . . . . . . .PORT_1_TOPOLOGY = CONNECTION DOWN
Address . . . . . . . . . . . . . . . . . . . . . . . . . . =nnnnnn
432 Data Replication Manager HSG80 ACS Version 8.5P Operations Guide for Novell NetWare Version 5.1
Host PORT_2:
Reported PORT_ID = nnnn-nnnn-nnnn-nnnn
PORT_2_TOPOLOGY = CONNECTION DOWN
Address . . . . . . . . . . . . . . . . . . . . . . . . . . =nnnnnn
NOREMOTE_COPY.
26. You are now ready to enable Data Replication Manager. Use the following CLI
command:
SET THIS_CONTROLLER REMOTE_COPY=InitiatorControllerName
Example: SET THIS_CONTROLLER REMOTE_COPY=BuildngA
NOTE: Be sure to specify a meaningful InitiatorName. Do not use "local" and "remote";
these are reserved keywords. The name can be up to eight characters and must be unique
to all of your controllers. Follow the naming guidelines as specified in the Compaq
StorageWorks HSG80 Array Controller ACS V8.5 Configuration Guide.
After you have entered this CLI command, you will see a series of %LFL and %EVL
displays, and the controllers will automatically restart.
27. Use the following CLI command to verify that these settings are in place:
SHOW THIS_CONTROLLER
You will see a display similar to that in "Example Display 19."
Example Display 19
Host PORT_2:
Reported PORT_ID = nnnn-nnnn-nnnn-nnnn
PORT_2_TOPOLOGY = FABRIC (offline)
REMOTE_COPY = BuildngA
Configuring a Data Replication Manager Solution 433
Configure Storage at the Initiator Site
Devices and StorageSets
Before you can configure the storage for Data Replication Manager, you must add the
disks, create the RAIDsets, and create units. Follow the instructions in the Compaq
StorageWorks HSG80 Array Controller ACS V8.5 Configuration Guide, but note the
restrictions listed at the beginning of this chapter in Table 41.
NOTE: Keep in mind that the initiator site must have exactly the same storageset and unit
configuration as the target site.
Creating Storage Units
Refer to the Compaq StorageWorks HSG80 Array Controller ACS V8.5 Configuration
Guide for detailed information.
NOTE: Use the following command to create storage units and to disable all access as the units
are created.
ADD UNIT UnitName StorageSetName DISABLE_ACCESS_PATH=ALL
NOTE: Be sure to issue this command for all units.
1. Verify that the access on each unit is set to none by using the following CLI
command:
SHOW UNITS FULL
You will see a display similar to that in "Example Display 20."
434 Data Replication Manager HSG80 ACS Version 8.5P Operations Guide for Novell NetWare Version 5.1
Example Display 20
LUN Uses Used by
------------------------------------------------------------------------
D10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DISK1000
LUN ID: nnnn-nnnn-nnnn-nnnn-nnnn-nnnn-nnnn-nnnn
NOIDENTIFIER
Switches:
RUN NOWRITE_PROTECT READ_CACHE`
READAHEAD_CACHE WRITEBACK_CACHE
MAXIMUM_CACHED_TRANSFER_SIZE = 32
Access:
NONE
State:
ONLINE to this controller
Not reserved
NOPREFERRED_PATH
Size: nnnnnnnn blocks
Geometry (C/H/S): ( 7000 / 20 / 254 )
2. Distribute the units by setting their preferred path. Use either of the following CLI
commands:
SET Unit PREFERRED_PATH=THIS_CONTROLLER
or
SET Unit PREFERRED_PATH=OTHER_CONTROLLER
Keep the busiest units on different host ports.
3. Restart the controllers after configuring the units. Otherwise, the preferred path
settings will not go into effect.
4. To ensure that your storage settings are in place, use the following CLI command:
SHOW Storagesets FULL
Configuring a Data Replication Manager Solution 435
Cabling the Initiator Site
Connect Fiber Optic Cables Between the Controllers and
Fibre Channel Switches
This procedure specifies how to make fiber optic connections. Figure 47 shows the port
locations on the switch.
CXO7085A
Figure 47. Port locations on the Fibre Channel switches
1. Make sure that you have installed all required GBICs into each of the Fibre Channel
switches.
2. Connect a multi-mode, 50-micron fiber optic cable from port 1 of the top controller
to port 2 of the top Fibre Channel switch (as shown by callout 1 of Figure 48).
3. Connect a second multi-mode, 50-micron fiber optic cable from port 2 of the top
controller to port 4 of the top Fibre Channel switch (as shown by callout 2 of Figure
48).
4. Connect a third multi-mode, 50-micron fiber optic cable from port 1 of the bottom
controller to port 2 of the bottom Fibre Channel switch (as shown by callout 3 of
Figure 48).
5. Connect a fourth multi-mode, 50-micron fiber optic cable from port 2 of the bottom
controller to port 4 of the bottom Fibre Channel switch (as shown by callout 4 of
Figure 48)
NOTE: You should see an illuminated green LED on the switch as soon as the cable is
inserted at both ends. This verifies that there is a good connection.
Figure 48 illustrates what your cabling should look like. The numbered callouts
reflect the steps that you just completed.
436 Data Replication Manager HSG80 ACS Version 8.5P Operations Guide for Novell NetWare Version 5.1
2
1
3
4
CXO7089A
Figure 48. Cabling between the controllers and Fibre Channel switches
Connect the Initiator Site to the External Fiber Link
Locate the connection points at the initiator site that link the initiator site to the target site.
Look for either a fiber optic cable connector or a patch panel where you can insert a cable.
Long Wave GBICs
1. Connect a single-mode, 9-micron fiber optic cable from port 6 of the top switch to
one connection point (as shown by callout 2 of Figure 49).
2. Connect another single-mode, 9-micron fiber optic cable from port 6 of the bottom
switch to the other connection point (as shown by callout 3 of Figure 49).
Other Transport Modes
Data Replication Manager also uses other long distance transport modes. For connection
information, refer to our website at:
http://www.compaq.com/storage
The initiator site is now physically linked to the target site. See Figure 49 for an
illustrated view of how this cabling should appear.
NOTE: You can make sure that switches and ports are connected as you have them
documented by issuing the nbrStateShow command at the switch. Issue the topologyShow
command at the switch to reveal if you have more than one fiber optic cable between the
switches on each site.
Configuring a Data Replication Manager Solution 437
1
2
3 1
CXO7090A
Figure 49. Cabling from the initiator site to the target site
Create Remote Copy Sets
Prepare the Initiator Site
Prior to creating the remote copy set (RCS), create the connections between the
initiator and target sites by entering the following CLI command:
ADD REMOTE RCS199 D199 TargetControllerName\D199
Example: ADD REMOTE RCS199 D199 BuildngB\D199
Error: Initiator unit specified not found
NOTE: This command will fail with the error message "Initiator unit specified not found."
However, it will create and name the connections appropriately.
438 Data Replication Manager HSG80 ACS Version 8.5P Operations Guide for Novell NetWare Version 5.1
Create Connections From the Target Site
1. Prior to creating the remote copy set, create the connections between the target and
initiator sites by entering the following CLI command:
ADD REMOTE RCS199 D199 InitiatorControllerName\D199
Exam ple:ADD REMOTE RCS199 D199 BuildngA\D199
NOTE: This command will fail with the error message "Initiator unit specified not found".
However, it will create and name the connections appropriately.
2. Verify that the target has access to the initiator controller with this CLI command:
SH OW CONNECTIONS
This command will show InitiatorControllerA, InitiatorControllerB,
InitiatorControllerC, InitiatorControllerD.
3. The target units will need to allow access to the controllers at the initiator site. Enable
access with this CLI command:
SET UnitName ENABLE_ACCESS_PATH= (InitiatorControllerConnectionA,
InitiatorControllerConnectionB, InitiatorControllerConnectionC, InitiatorControllerConnectionD)
Exam ple: SETUnitName
ENABLE_ACCESS_PATH=(BuildngAA,BuildngAB,BuildngAC,BuildngAD)
NOTE: Be sure to repeat this command for each Unit Name.
Create Remote Copy Sets from the Initiator Site
1. Verify that the initiator has access to the target controller with this CLI command:
SHOW CONNECTIONS
This command will show InitiatorControllerA, InitiatorControllerB,
InitiatorControllerC, InitiatorControllerD.
2. The initiator units will need to allow access to the controllers at the target site.
Enable access with this CLI command:
SET UnitName ENABLE_ACCESS_PATH= (TargetControllerConnectionA,
TargetControllerConnectionB, TargetControllerConnectionC, TargetControllerConnectionD)
Exam ple: SETUnitName
ENABLE_ACCESS_PATH=(BuildngBA,BuildngBB,BuildngBC,BuildngBD)
NOTE: Be sure to repeat this command for each UnitName.
Configuring a Data Replication Manager Solution 439
3. To create remote copy sets, enter the CLI command below. When you enter this
command, the controllers copy all data from the initiator unit to the target unit. This
process is called normalization.
ADD REMOTE RemoteCopySetName InitiatorUnitName
TargetController Name\TargetUnitName
Example: ADD REMOTE RCS1 D1 BuildngB\D1
NOTE: It is not necessary to repeat this step at the target site.
You will see a %EVL display that includes your remote copy set information. You
will also see a display similar to that in "Example Display 21."
IMPORTANT: If you will be using scripting to automate failover and failback operations, do
not use dashes (hyphens) as separators in your naming convention--use underscores
instead. Dashes are not allowed by the Perl scripting language.
Example Display 21
%EVL--Initra > --13-JAN-1946 05:01:56 (time not set)-- Instance Code:
0E010064
Template: 144.(90)
Power On Time: 0. Years, 36. Days, 6. Hours, 45. Minutes, 22. Seconds
Controller Model: HSG80
Serial Number: ZG8nnnnnnn Hardware Version: Enn(2B)
Software Version: V85P
Informational Report
Target Controller Board Serial Number: " ZG8nnnnnnn"
Initiator WWLID: nnnn-nnnn-nnnn-nnnn-nnnn-nnnn-nnnn-nnnn
Initiator Node Name: "BuildngA"
Initiator Unit Number: n.(nnnnnnnn)
440 Data Replication Manager HSG80 ACS Version 8.5P Operations Guide for Novell NetWare Version 5.1
Target WWLID: nnnn-nnnn-nnnn-nnnn-nnnn-nnnn-nnnn-nnnn
Target Node Name: "BuildngB"
Target Unit Number: n.(nnnnnnnn)
Number of Targets: n.(nnnnnnnn)
Remote Copy Set Name: "RCS1"
Instance Code: 0E010064
Set Failsafe at the Initiator Site (Optional)
When failsafe is set, the remote copy set must contain one initiator member and one target
member. If the remote copy set loses the target member while failsafe is set, no further I/O
will be allowed to the initiator member, and an error will be returned to the host. This is
known as a failsafe locked condition and prevents the system from writing data that is not
protected from a disaster by a copy at the target site.
If you choose to set failsafe, enter the following command:
SET RemoteCopySetName ERROR_MODE=FAILSAFE
Example: SET RCS1 ERROR_MODE=FAILSAFE
NOTE: When you set failsafe, all remote copy sets must be in a normal or normalizing state.
If remote copy sets are copying when you set failsafe, your command will be rejected until
the remote copy sets return to normal mode.
To remove the failsafe lock from a remote copy set and resume normal operation, use
the following CLI command:
SET RemoteCopySetName ERROR_MODE=NORMAL
Example: SET RCS1 ERROR_MODE=NORMAL
You can also use this procedure for remote copy sets where a DT-safe condition is
not required.
NOTE: If the error mode is set to normal and there is no target member, the remote copy set is
no longer considered DT-safe.
Configuring a Data Replication Manager Solution 441
Creating Log Units and Association Sets (Optional)
In this example, hypothetical disks 50100 and 60100 are used as the mirrorset for the log
disk. The log unit is D10. The association set name is AS_D1. The association set is using
remote copy set name RC_D1.
Creating a Log Unit
1. Create a mirrorset for the log disk by issuing the following CLI command:
ADD MIRRORSET MirrorsetName DiskName
Example: ADD MIRR MIR_D1LOG DISK50100 DISK60100
IMPORTANT: If you will be using scripting to automate failover and failback operations, do not
use dashes (hyphens) as separators in your naming convention--use underscores instead.
Dashes are not allowed by the Perl scripting language.
NOTE: To minimize the number of devices used for logging, you can create and use
one-member mirrorsets. Because the data will be written to one disk, the logged data will not
be protected. However, all of this data is also written to the initiator unit. In the case of a log disk
failure, you would incur a full normalization, rather than a mini-merge, when access to the
target is re-established. The command to create a one-member mirrorset is the same as above,
except only one disk is listed.
Example: ADD MIRR MIR_D1LOG DISK 50100.
2. Initialize the mirrorset with the following CLI command:
INITIALIZE ContainerName
Example: INITIALIZE MIR_D1LOG
3. Verify that you have created a mirrorset by issuing the following CLI command:
SHOW MIRRORSET
You will see a display similar to that in "Example Display 22."
Example Display 22
Name Storageset Uses Used by
-----------------------------------------------------------------------
MIR_D1LOG mirrorset DISK50100
DISK60100
442 Data Replication Manager HSG80 ACS Version 8.5P Operations Guide for Novell NetWare Version 5.1
4. Present the log unit to the controller with the following CLI command:
ADD UNIT UnitName ContainerName
Example: ADD UNIT D10 MIR_D1LOG
5. Verify that the controller recognizes the log unit by issuing the following CLI
command:
SH OW UNITS
You will see a display similar to that in "Example Display 23."
Example Display 23
LUN Uses Used by
-----------------------------------------------------------------------
D10 MIR_D1LOG
Create Association Sets and Assign a Log Unit
1. Create an association set with the following CLI command:
ADD ASSOCIATIONS AssociationSetName RemoteCopySetName
Example: ADD ASSOCIATIONS AS_D1 RC_D1
NOTE: You can add additional members to the association set by issuing the following CLI
command:
SET AssociationSetName ADD=RemoteCopySetName
IMPORTANT: If you will be using scripting to automate failover and failback operations, do
not use dashes (hyphens) as separators in your naming convention--use underscores
instead. Dashes are not allowed by the Perl scripting language.
2. Disable node access to the log unit with the following CLI command:
SET UnitNumber DISABLE_ACCESS_PATH= ALL
Example: SET D10 DISABLE_ACCESS_PATH= ALL
3. Disable writeback cache on log units with the following CLI command:
SET UnitNumber NOWRITEBACK_CACHE
Example: SET D10 NOWRITEBACK_CACHE
Configuring a Data Replication Manager Solution 443
4. Check to see that you have disabled access and writeback cache with the following
command:
SHOW D10
You will see a display similar to that in "Example Display 24."
Example Display 24
LUN Uses Used by
--------------------------------------------------------------------
D10 MIR_D1LOG
LUN ID: 6000-1FE1-0001-3B10-0009-9130-8044-0066
IDENTIFIER = 10
Switches:
RUN NOWRITE_PROTECT READ_CACHE
READAHEAD_CACHE NOWRITEBACK_CACHE
MAXIMUM_CACHED_TRANSFER_SIZE = 32
Access:
None
State:
ONLINE to this controller
Not reserved
PREFERRED_PATH = THIS_CONTROLLER
Size: 35556389 blocks
Geometry (C/H/S): ( 7000 / 20 / 254 )
5. To assign the log unit to the association set, use the following CLI command:
SET AssociationSetName LOG_UNIT = D10
Example: SET AS_D1 LOG_UNIT = D10
6. Check to see the switch status of the association set by issuing the following CLI
command:
SHOW AssociationSetName
Example: SHOW AS_D1
You will see a display similar to that in "Example Display 25."
444 Data Replication Manager HSG80 ACS Version 8.5P Operations Guide for Novell NetWare Version 5.1
Example Display 25
Name Association Uses Used by
------------------------------------------------------------------------
AS_D1 association RC_D1
Switches:
NOFAIL_ALL
NOORDER_ALL
LOG_UNIT = D10 (No data logged)
Configure the Host at the Initiator Site
Install the Host Bus Adapters and Drivers
You should install two host bus adapters in each host system. Refer to the Compaq
StorageWorks 64-Bit/66 MHz Fibre Channel Installation Guide for installation
information.
Install Secure Path Agent
For installation information, refer to the Compaq SANWorks Secure Path Version 3.0 for
Novell Netware Installation and Reference Guide.
1. Verify that the Secure Path Agent is installed by going to the server console screen
and typing modules cpqspagt. Ensure that the Secure Path Agent is set for
automatic startup. Normally, the SP Install program sets automatic startup by
loading cpqspagt.nlm in the autoexec.ncf file.
2. Use the Secure Path Agent Configuration screen at the server to grant access to the
client at both the initiator and target sites. To do this:
a. From the NetWare server, toggle to the Secure Path NLM screen.
b. At the Main Menu, select 2) Client Administration, then select 2) Add a Client.
c. Type fully-qualified DNS name for the client, then press Enter.
d. Press Escape to return to the Main menu.
Configuring a Data Replication Manager Solution 445
3. You can set the password and allow client access via the Secure Path Agent
Configuration.
a. At the Main Menu, select 1) Agent Administration, then select 1) Change
Password.
b. Type a password for client access, then re-type the password for verification.
c. Press Escape to return to the Main Menu.
NOTE: Compaq recommends that you set both the fully qualified and unqualified DNS
names as valid, authorized clients.
Install Secure Path Manager (SPM)
For installation information, refer to the Compaq SANWorks Secure Path Version 3.0 for
Novell Netware Installation and Reference Guide.
Install SWCC (Optional)
For detailed information about SWCC, refer to the Compaq StorageWorks Command
Console User Guide.
Connecting Fiber Optic Cables Between the Hosts and the Switches
Connecting the fiber optic cables involves two stages:
s Connecting the cables
s Renaming the host connections
Both are described in the following sections.
446 Data Replication Manager HSG80 ACS Version 8.5P Operations Guide for Novell NetWare Version 5.1
Connecting the Fiber Optic Cable
1. Establish the cabling policy that you plan to follow.
2. Connect a multi-mode, 50-micron fiber optic cable from port 0 of the top switch to
the host (callout 1 in Figure 410).
3. Connect the final multi-mode, 50-micron fiber optic cable from port 0 of the bottom
switch to the host (callout 2 in Figure 410).
4. If you have more than one host (up to six), connect one host bus adapter to one of
the remaining ports on the top switch. Connect the other host bus adapter to the
same numbered port on the bottom switch.
The hosts are now connected to the initiator site via the multi-mode, 50-micron fiber
optic cables. Your cabling should appear as it does in Figure 410.
NOTE: You may choose any available port to connect your cables to, but you must maintain
that identical scheme at the target site. In other words, If port 1 of controller B is connected
to port 2 of the bottom switch at the initiator site, then port 1 of controller B must be
connected to port 2 of the bottom switch at the target site.
1 2
CXO7091A
Figure 410. Cabling between the hosts and the switches
Configuring a Data Replication Manager Solution 447
The cabling at each site is now complete. The initiator and target sites should be cabled
according to the layout shown in Figure 411.
CXO7092A
Figure 411. Data Replication Manager cabling at initiator and target sites
5. Verify that the connection between the host and the switch has been made by
entering this CLI command:
SHOW CONNECTIONS
NOTE: You can also verify that a connection has been made by looking for the illuminated
green LED that flashes on the switch ports.
You will see a display similar to that in "Example Display 26."
Example Display 26
Connection Unit
Name Operating system Controller Port Address Status Offset
!NEWCON00 WINNT THIS 1 210013 online 0
HOST_ID=nnnn-nnnn-nnnn-nnnn ADAPTER_ID=nnnn-nnnn-nnnn-nnnn
!NEWCON01 WINNT OTHER 1 200113 online 0
HOST_ID=nnnn-nnnn-nnnn-nnnn ADAPTER_ID=nnnn-nnnn-nnnn-nnnn
448 Data Replication Manager HSG80 ACS Version 8.5P Operations Guide for Novell NetWare Version 5.1
BUILDNGBA PPRC_TARGET . . . . . . . . . . . . . THIS 2 online 0
HOST_ID=nnnn-nnnn-nnnn-nnnn ADAPTER_ID=nnnn-nnnn-nnnn-nnnn
BUILDNGBB PPRC_TARGET . . . . . . . . . . . . . . . . .OTHER 2 online0
HOST_ID=nnnn-nnnn-nnnn-nnnn ADAPTER_ID=nnnn-nnnn-nnnn-nnnn
BUILDNGBCPPRC_INITIATOR . . . . . . . . . . . . . . . THIS 2 online 0
HOST_ID=nnnn-nnnn-nnnn-nnnn ADAPTER_ID=nnnn-nnnn-nnnn-nnnn
BUILDNGBDPPRC_INITIATOR . . . . . . . . . . . . . . . OTHER 2 online 0
HOST_ID=nnnn-nnnn-nnnn-nnnn ADAPTER_ID=nnnn-nnnn-nnnn-nnnn
Rename the Host Connections at the Initiator Site
To better identify which hosts you are working with, Compaq recommends that you
rename the connection names that are reserved for the host names. You will need to
change the !NEWCON prompt to a meaningful host name. Each host-based adapter will
appear as a connection. An individual host-based adapter can be identified by its World
Wide Name that you recorded in the Chapter 3, "Getting Started," and that appears in the
connection description
IMPORTANT: If you will be using scripting to automate failover and failback operations, do not
use dashes (hyphens) as separators in your naming convention--use underscores instead.
Dashes are not allowed by the Perl scripting language.
1. Compaq suggests that you use the worksheet in Figure 412 when renaming your
hosts. Fill in the fields accordingly to keep an accurate record of connections and
host names.
Configuring a Data Replication Manager Solution 449
!NEWCONxx World Wide Name Host Name Path Number
Figure 412. Host renaming worksheet
2. W hen you have completed the worksheet, rename the !NEWCONxx prompt using
the following CLI commands:
RENAME !NEWCONxx InitiatorHostConnectionNamex
Example: RENAME !NEWCONxx hostA1
RENAME !NEWCONxx InitiatorHostConnectionNamey
Example: RENAME !NEWCONxx hostA2
3. Set the connection type to NetWare by entering the following CLI command:
SET iNITIATORHostConnectionNamex OPERATING_SYSTEM = NETWARE
Example: SET HOSTA1 OPERATING_SYSTEM = NETWARE
Perform step 3 for each connection.
4. W hen you have finished renaming your host connections, enter the following
command to see your new settings:
SHOW CONNECTIONS
You will see a display similar to that in "Example Display 27."
450 Data Replication Manager HSG80 ACS Version 8.5P Operations Guide for Novell NetWare Version 5.1
Example Display 27
Connection Unit
Name Operating system Controller Port Address Status Offset
HOSTA1 NETWARE THIS 1 210013 online . . . . .0
HOST_ID=nnnn-nnnn-nnnn-nnnn ADAPTER_ID=nnnn-nnnn-nnnn-nnnn
HOSTA2 NETWARE OTHER 1 200113 online . . . . .0
HOST_ID=nnnn-nnnn-nnnn-nnnn ADAPTER_ID=nnnn-nnnn-nnnn-nnnn
BUILDNGBA PPRC_TARGET . . . . . . . . . . . . . THIS 2 online 0
HOST_ID=nnnn-nnnn-nnnn-nnnn ADAPTER_ID=nnnn-nnnn-nnnn-nnnn
BUILDNGBB PPRC_TARGET . . . . . . . . . . . . . . . . .OTHER 2 online0
HOST_ID=nnnn-nnnn-nnnn-nnnn ADAPTER_ID=nnnn-nnnn-nnnn-nnnn
BUILDNGBCPPRC_INITIATOR . . . . . . . . . . . . . . . THIS 2 online 0
HOST_ID=nnnn-nnnn-nnnn-nnnn ADAPTER_ID=nnnn-nnnn-nnnn-nnnn
BUILDNGBDPPRC_INITIATOR . . . . . . . . . . . . . . . OTHER 2 online 0
HOST_ID=nnnn-nnnn-nnnn-nnnn ADAPTER_ID=nnnn-nnnn-nnnn-nnnn
At the target site, the initiator host will appear as new connections, !NEWCONxx. These
should be renamed as described above.
Configuring a Data Replication Manager Solution 451
Enable Access to the Hosts at the Initiator Site
1. The initiator units will need to have access to the hosts. Enable access with this
command:
SET UnitName ENABLE_ACCESS_PATH=
InitiatorHostConnectionNamex,InitiatorHostConnectionNamey
Example: SET UnitName ENABLE_ACCESS_PATH=HostA1,HostA2
NOTE: Keep in mind that there should be two paths per host. You will need to repeat this
sequence for each host.
2. After you have enabled hosts access to units, from the Novell server console prompt
type:
SCAN FOR NEW DEVICES
3. Use NWCONFIG to create NetWare partitions and volumes on the newly created
storage.
4. From the server console prompt, type:
MOUNT ALL
5. You are now ready to run Secure Path Manager from your Windows NT/2000 client
machine.
Click Start > Programs > Secure Path > SPM. Specify the server and password that
you prefer.
6. Select the "Save Password" box if you would like to use the same password each
time you log in.
7. The SANworks Secure Path Manager screen appears. You must now verify the
volumes. Left-click on each drive. The device properties will appear in the
right-hand pane. Ensure that each drive can be successfully moved between
controllers.
452 Data Replication Manager HSG80 ACS Version 8.5P Operations Guide for Novell NetWare Version 5.1
Install NetWare Cluster Services (NWCS)
Version 1.01 (Optional)
NWCS Fibre Channel cluster software enables two host servers to share a Fibre Channel
storage subsystem through a Fibre Channel switch. If a failure occurs on the server, the
cluster software detects that failure, and a failover is initiated. The failed components can
be warm-swapped or serviced while the functioning components remain active. This
process requires minimal downtime and ensures high availability of data.
If you are using NetWare 5.1 and wish to run the cluster option, you can safely install it
now. Refer to the Compaq Proliant Cluster for NetWare 5 and Novell NetWare Cluster
Services for NetWare 5 Installation Reference Guide.
Only non-RCS LUNs are supported
Document Your Configuration
Keep a printed copy of your configuration for future reference. Update your records each
time you modify the configuration. Follow the steps outlined below in the sections entitled
" Terminal Emulator Session" and " SHOW Commands" to obtain a status of the
controllers, association sets, remote copy sets, units, and connections. After you have
obtained this information for the initiator site, repeat the steps for the target.
Terminal Emulator Session
1. Use a laptop computer or another computer to connect a serial cable between the COM
port on that machine and the corresponding serial port on the HSG80 controllers.
2. Start a terminal emulator session. On Windows, use the HyperTerminal emulator. Use
these settings: 9600 baud, 8 bits, No parity, 1 stop bit, XON/XOFF.
3. From the Transfer Menu, click Capture Text. The Capture Text dialog box is displayed.
In the c:\ field, type initiator.txt or target.txt.
4. Click Start.
Configuring a Data Replication Manager Solution 453
SHOW Commands
1. To see the full information on this controller, issue the following CLI command:
SHOW THIS_CONTROLLER FULL
You will see a display similar to that in "Example Display 28."
Example Display 28
Controller:
HSG80 ZG91412410 Software S050P-0, Hardware E05
NODE_ID = 5000-1FE1-0001-3AE0
ALLOCATION_CLASS = 0
SCSI_VERSION = SCSI-3
Configured for MULTIBUS_FAILOVER with ZG91416136
In dual-redundant configuration
Device Port SCSI address 6
Time: NOT SET
Command Console LUN is lun 0 (NOIDENTIFIER)
Host PORT_1:
Reported PORT_ID = 5000-1FE1-0001-3AE1
PORT_1_TOPOLOGY = FABRIC ( up)
Address = 220113
Host PORT_2:
Reported PORT_ID = 5000-1FE1-0001-3AE2
PORT_2_TOPOLOGY = FABRIC (fabric up)
Address = 220313
REMOTE_COPY = BuildngA
Cache:
256 megabyte write cache, version 0012
Cache is GOOD
No unflushed data in cache
CACHE_FLUSH_TIMER = DEFAULT (10 seconds)
Mirrored Cache:
256 megabyte write cache, version 0012
Cache is GOOD
454 Data Replication Manager HSG80 ACS Version 8.5P Operations Guide for Novell NetWare Version 5.1
No unflushed data in cache
Battery:
NOUPS
FULLY CHARGED
Expires:
Extended information:
Terminal speed 9600 baud, eight bit, no parity, 1 stop bit
Operation control: 00000000 Security state code: 75184
Configuration backup disabled
2. To see the information for all association sets known to the controller pair, issue the
following CLI command:
SH OW ASSOCIATIONS FULL
You will see a display similar to that in "Example Display 29" for each association set.
Example Display 29
Name Association Uses Used by
-----------------------------------------------------------------------
AS1 association RC1
RC2
RC3
Switches:
NOFAIL_ALL
NOORDER_ALL
NOLOG_UNIT
3. To see information for all remote copy sets known to the controller pair, issue the
following CLI command:
SH OW REMOTE_COPY FULL
You will see a display similar to that in "Example Display 30" for each remote copy
set.
Configuring a Data Replication Manager Solution 455
Example Display 30
Name Uses Used by
-----------------------------------------------------------------------
RC1 remote copy D1 AS1
Reported LUN ID: 6000-1FE1-0001-3AE0-0009-9141-6136-0038
Switches:
OPERATION_MODE = SYNCHRONOUS
ERROR_MODE = NORMAL
FAILOVER_MODE = MANUAL
OUTSTANDING_IOS = 60
Initiator (BuildngA\D1) state:
ONLINE to this controller
Target state:
BuildngB\D1 is NORMAL
4. To see information for all units configured to the controller, issue the following CLI
command:
SHOW UNITS FULL
You will see a display similar to that in "Example Display 31" for each unit.
Example Display 31
D2 DISK10100 BuildngA\RC2
LUN ID: 6000-1FE1-0001-3AE0-0009-9141-6136-0045
NOIDENTIFIER
Switches:
RUN NOWRITE_PROTECT READ_CACHE
READAHEAD_CACHE WRITEBACK_CACHE
MAXIMUM_CACHED_TRANSFER_SIZE = 1
Access:
BuildngBA,BuildngBB,BuildngBC,BuildngBD,HOSTA1,HOSTA2
456 Data Replication Manager HSG80 ACS Version 8.5P Operations Guide for Novell NetWare Version 5.1
State:
ONLINE to this controller
Not reserved
PREFERRED_PATH = OTHER_CONTROLLER
Target NORMAL
Size: 17769177 blocks
Geometry (C/H/S): ( 5258 / 20 / 169 )
5. To see the connection name, operating system, controller, controller port, adapter ID
address, online or offline status, and unit offset, issue the following CLI command:
SH OW CONNECTIONS
You will see a display similar to that in "Example Display 32" for each connection.
Example Display 32
Connection Unit
Name Operating system Controller Port Address Status Offset
!NEWCON28 WINNT THIS 1 634000 OL this 0
HOST_ID=1000-0000-C921-4B5B ADAPTER_ID=1000-0000-C921-4B5B
6. Click Stop to end the Capture Text function. Your work has been saved in the file
created in step 3 in the "Terminal Emulator Session" on page 452
7. Save this file for future reference.
8. Repeat this procedure ("Documenting Your Configuration") for all subsystems in your
configuration.
5
Chapter
Managing Site Failover and Failback Procedures
This chapter describes how to manage Failover and Failback for your Data Replication
Manager solution. This section contains the procedures to ensure that Failover and
subsequent Failback function properly:
s "Power Up Data Replication Manager Systems" on page 52
s "Power Down Data Replication Manager Systems" on page 53
s "Site Failover Basic Description" on page 54
s "Failback Procedure Choices" on page 55
s "Data Replication Manager Configuration Basics" on page 56
s "Planning Considerations" on page 57
s "Planned Failover Procedures" on page 58
s "Simple Failback Procedure" on page 512
s "Unplanned Failover" on page 516
s "Full Failback Procedure" on page 518
s "New Hardware Failback Procedure" on page 525
NOTE: All initiator site procedure text is shaded for ease of visibility and separation from target
site procedures.
52 Data Replication Manager HSG80 ACS Version 8.5P Operations Guide for Novell NetWare Version 5.1
Power Up Data Replication Manager Systems
The procedures below outline how to power on and power off the storage subsystem after
it has been configured.
CAUTION: Compaq recommends that you power up the controllers and switches at
the target site before applying power to the initiator site. Powering up in the wrong
sequence may cause incorrect configurations.
Power on the Data Replication Manager systems in the sequence shown in the following
procedures.
Target Site Powerup Procedures
1. Ensure that all enclosures, switches, and cabinet power distribution units (PDUs) have
their power switches in the OFF position.
2. Apply power to all PDUs.
3. Turn on the power switches for the cabinets from the target site.
4. Ensure that all controllers are on and functional.
5. Apply power to all Fibre Channel switches.
When completed, go to the "Initiator Site Powerup Procedures."
Initiator Site Powerup Procedures
1. Ensure that all enclosures, switches, and cabinet power distribution units (PDU)
have their power switches in the OFF position.
2. Apply power to all PDUs.
3. Turn on the power switches for the cabinets from the initiator site.
4. Make sure that all controllers are on and functional.
5. Apply power to all Fibre Channel switches.
Managing Site Failover and Failback Procedures 53
Power Down Data Replication Manager Systems
Power down the Data Replication Manager systems in the sequence shown in the
following procedures.
Initiator Site Power Down Procedures
1. Issue the following CLI commands (in this order):
SHUTDOWN OTHER_CONTROLLER
SHUTDOWN THIS_CONTROLLER
2. Turn off the Fibre Channel switch.
3. Turn off the power to the enclosures.
4. Turn off the PDUs.
When completed, go to the "Target Site Power Down Procedures."
Target Site Power Down Procedures
1. Issue the following CLI commands (in this order):
SHUTDOWN OTHER_CONTROLLER
SHUTDOWN THIS_CONTROLLER
2. Turn off the Fibre Channel switch.
3. Turn off the power to the enclosures.
4. Turn off the PDUs.
54 Data Replication Manager HSG80 ACS Version 8.5P Operations Guide for Novell NetWare Version 5.1
Site Failover Basic Description
If the initiator site is no longer available, or if there is anticipated downtime that will
prevent operation at the initiator site, you must decide whether or not to perform a site
failover to the target site. Performing a failover enables the target site to assume the role of
the initiator and access (write/read) data until the problem is resolved and a failback can be
issued. Transferring control of system operation to the target site ensures that there will be
minimal interruption in data access after a failure.
NOTE: If you decide to perform a Failover operation, keep in mind that all components must be
failed over. Therefore, if only one component fails, fixing that single component may be
preferable to performing a complete failover. Also, it is important to verify that all components at
the target site are operational before you begin the site failover.
Table 51 outlines example scenarios that may call for a failover and those that may not.
Table 51 Failover Scenarios
When to Failover When Not to Failover (recommended)
s Both controllers fail s Single failed switch
s Extended power outage at the initiator site s Single fiber optic cable malfunctions
s Both host adapters fail (non-clustered hosts) s Single controller fails
s Both initiator switches fail s Single storageset fails
s Disaster (flooding, fire, earthquake, terrorism, s Single disk in redundant storageset fails
etc.) that disables access to the subsystems
s Scheduled event that will prevent computing s Target not in normal state
from the initiator site for an extended period
s All hosts fail
NOTE: If one host in a multi-host environment fails, you must decide whether or not a failover is
the best course of action.
When you decide that a site failover is necessary, identify which scenario best describes
your situation: planned or unplanned failover.
The planned failover procedure should be used when failover is a scheduled event.
Otherwise, Compaq suggests that you use an unplanned failover procedure.
Managing Site Failover and Failback Procedures 55
CAUTION: Be sure to follow the steps outlined in the section Planned Failover
Procedures accurately and completely, or you may incur data loss and extended
downtime.
Failback Procedure Choices
During Failover, the remote copy sets at the target site are in a "copy ready" state, waiting
for the initiator site to become available. When a new initiator site has been established or
the original one has been restored, site operation can resume after a failback procedure has
been performed. This involves synchronizing data on both the initiator and target
subsystems so that operation can be returned to the initiator with minimal downtime.
IMPORTANT: Verify that all components at both sites are operational before performing a
failback.
The failback sequence is a scheduled event. The HSG80 Array Controller requires that a
viable dual-redundant subsystem be available before a failback can take place.
| 122833-001
165993-B21
231844-B21
AA-RFA2D-TE
AA-RFA2F-TE
AA-RFB9D-TE
AA-RHBYA-TE
AA-RHBZA-TE
AA-RMMJA-TE
AA-RN72A-TE
DS-BA370-Se
EK-DRMNN-OA
EK-HSG84-SV
EK-HSG85-CG
EK-HSG85-RG
EK-P20ZG-GA
EK-SE2C8-UA
EK-SW2ZS-UA
QB-6BTAH-SA
|
