Re: volume shadowing question

Given the way your question is worded, I'll assume you aren't already using shadowsets. If that's the case, you will at least have to dismount the current disk to re-mount it as a one-member shadowset to get the process started.

But then, yes, you should be able to "transfer" the data this way. Then after the data is transferred you'd have to dismount the shadowset and remount the new disk. It'll complain though if you try to re-mount the device as a non-shadowset.

Considering you will have to dismount the original disk before the transfer and dismount the target disk after the transfer, I don't see the advantage of this "shadow" tranfer method. You might as well, make the storage you want on the EVA, then BACKUP the content from one disk to another.
You're going to have "downtime" on that disk either way.

You may have licenses for shadowing on the IA64 already. If you have the MCOE (Mission Critical Operating Environment) license, which it seems you do if you have clustering, then I believe that also covers volume shadowing. You're good to go there.


On Thu, 13 Sep 2007, Syltrem wrote:

Hello

We are installing an EVA4000 in replacement of an MSA1000.

I was wondering if I could use HBVS to switch my data onto the new storage,
online.

That is: create a new drive on the EVA4000, mount it as a shadow member of
the existing one on MSA1000.
When the merge is complete, dismount the member that's on the MSA1000.

A possible technical problem:
The VMScluster is comprised of 2 Alphaservers and one IA64 server. When I
mount /cluster the shadow member, will all nodes see it properly (different
architecture should not be a problem on VMS) ?

And is there something obvious that I do not see ? Is this a workable plan ?
I remember 5-6 years ago, HBVS would not mount members of different sizes so
that will certainly be a problem if it's still the case.

And I hope HP can lend me HBVS licenses for a week or two... I may still
have some for Alpha but certainly not for IA64.

Just thinking, looking for feedback
.

Relevant Pages

  • Re: long, boring explanation of minicopy (and HBVS, in general)
    ... > immediately kick the missing disk out of the shadow set. ... For a quick, planned reboot, I agree. ... it appears that the proper DISMOUNT command is enough. ...
    (comp.os.vms)
  • Shadow Volume Copy
    ... We have a shadow logical disk, with two members. ... $ dismount lda1: ...
    (comp.os.vms)
  • Re: Shadow Volume Copy
    ... They want to copy the physical files which form the shadow to another ... $ dismount lda1: ... When I ran the commands manually one bye it works ... When I put them in the DCL, dismounts and copies the first file and I ...
    (comp.os.vms)
  • Re: VOL Shadow an mounted drive
    ... you cannot convert a mounted disk into a shadow disk. ... you will have to FIRST dismount the physical disks. ... carefully and surely backup one of these disks because its data will ... Also, I mount all my disks as shadow sets, even the single ones. ...
    (comp.os.vms)
  • Re: shadow sets, cluster, merge, MVTIMEOUT, dismount
    ... merge of the shadow set in question takes about 8 hours, ... dismount them from other nodes in the cluster. ... F$GETDVITHEN GOTO DISK_LOOP ... $ ENDIF ...
    (comp.os.vms)