DRD XP12000 and CA

[Keith W Upton]

we have an issue with one of our XPs, which has raised the question about whether there is anyone else using (11.23) DRD vg00 on an XP and using CA to another site for Disaster Recovery. Because the current DRD only alows one disk the LUN on the XP is a LUSE disk, so we would like to know if there are any issues using CA on a LUDE disk

[Torsten.]

The XP in general is a supported boot device, no matter if the disk is a LUSE or not.

[Keith W Upton]

yes ... but is the combination DRD LUSE CA supported ? ;-) (sorry about the spelling that should of course be LUSE no LUDE!!!)

[melvyn burnard]

As far as the XP and CA are concerned, CA just replicates to the Svol what has been written to the Pvol, so it shouldn't care.
If, as I suspect, your question is about the actual DRD clone copy, again, you present 1 LUN to the host and DRD clone to it. The fact that this specific LUN is paired should have no effect.
If you need an official statement from HP, then I would place an official call in to HP.

[Keith W Upton]

morning Melvin
The question is not about the clone. the issue, with think at this time is on the remote XP (from a CA point of view). The question has been asked (given we now have an issue with the XP) is whether any one else is using DRD LUSE and CA as it is one of the changes made since the last successful disaster recovery test!
Keith

[Torsten.]

You are creating a DRD clone on your local XP and duplicate it via CA to the remote XP.
The clone is not dynamically changing, so you have a static copy. From the production server point of view you write to a "local" disk. For the server the LUSE device is still a single disk device (like each other array LUN).

You could even clone directly to the remote XP without CA, it would be the same, more or less.

So you only need to find and configure the remote LUN as a boot device for the DR server.

[Keith W Upton]

=You are creating a DRD clone on your local XP and duplicate it via CA to the remote XP.
we have created a LUSE disk, presented it to the system, cloned vg00, and booted the system on the DRD ...

=The clone is not dynamically changing, so you have a static copy. From the production server point of view you write to a "local" disk. For the server the LUSE device is still a single disk device (like each other array LUN).
agree, we actualy have 2 DRD and flip between them with a patch kit is applied and update the VPar table and EFI for the new boot path

=You could even clone directly to the remote XP without CA, it would be the same, more or less.
No ... Our disaster Recover uses HPs DTCS function, which downs the server at say Data Centre 1, horctakeover the CA pairs (so the PVOL is now in Data Centre 2) and brings up the server at DC2.

=So you only need to find and configure the remote LUN as a boot device for the DR server.
we have a process that copies the VPar and EFI information between the two superdomes

[Torsten.]

>>we have created a LUSE disk, presented it to the system, cloned vg00, and booted the system on the DRD ...

So everything is ok now?

[Keith W Upton]

NO the problem is that when we swap between the Data Centres (horctakeover) doesn't switch all of the LUNs for the System ... So the question is : Is there an issue with Using DRD (LUSE) disks on an XP with CA between to XPs, The answer is (If there is anyone else using it THEN probably NOT, Therefore we must have a problem with our XP or setup, ELSE If there is NO one else doing this then there may be an Issue with DRD LUSE and XP CA! )