Re: pairdisplay error

To All,

We added a disk to the primary vol to extend it and then added a disk to the secondary vol to match primary. After that we edit the horc0.conf for primary and horc1.conf for secondary to include target ID's of new disks.

Afterwhich we re-start the horcmgr, then try to do pairresync -g. It is at this point that we get error?

Re: pairdisplay error

Hi,I think your horcm.conf files are not good, normaly, the state of the local (L) and remote (R) volumes are the same, the local volume cannot be PSUS and the remote volume SMPL. They must be (L) P-VOL PSUS and (R) S-VOL SSUS or (L) SMPL and (R) SMPL. Verify your TID with RAIDSCAN and adjust your horcmxx.conf files. Verify also you exported HORCM_INST=xxx and HORCC_MRCF=1

Then, you will just have to do a paircreate on your new disk (these that are SMPL) with this command on the :

Re: pairdisplay error

"fence level" is set up on the MCU. The fence level is a way to maintain the data integrity despite the distance that can between MCU and RCU:

1. data: This fence level is intended to maintain full data integrity at all times. If the RCU is down, all I/O to the P-Vol is prohibited.

2. status: A status level fence requires RAID Manager XP and a network connection between supported hosts. The RAID Managers contact each other to verify if the RCU is down but the ESCON connection is up; I/O to the MCU is still allowed.

3. never: MCU I/O is never interrupted.

sks

A rigid mind is very sure, but often wrong. A flexible mind is generally unsure, but often right.

Re: pairdisplay error

To All,

The scenerio is that we had volumes working jus fine and we could do Business Copy. Now becoz of the growth in our Production DB we had to extend the volumes, this we did. Now the disks we added are all in SMPL and the ones that were already there in the volumes are PSUS.

We need to move to a point where all the volumes are consistent so that we could do a Business Copy?