Re: Volume shadowing between FC Storage at different sites, and the allocation class
From: Michael Austin (maustin_at_firstdbasource.com)
Date: 06/29/04
- Next message: healyzh_at_aracnet.com: "Re: jGRASP for OpenVMS"
- Previous message: Charlie Hammond: "Re: Equipment release policy?"
- In reply to: Lee: "Re: Volume shadowing between FC Storage at different sites, and the allocation class"
- Next in thread: Keith Parris: "Re: Volume shadowing between FC Storage at different sites, and the allocation class"
- Reply: Keith Parris: "Re: Volume shadowing between FC Storage at different sites, and the allocation class"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Tue, 29 Jun 2004 18:54:07 GMT
>
> Andrew Rycroft wrote:
>
>> Hi,
>>
>> I have just connected to some Fibrechannel based storage from my VMS
>> system. I see all the devices as $1$DGAxxx. Even thought the ALLOCLASS
>> parameter is 6 for the system.
>>
>> This system will be in a cluster with a system at a remote site also
>> connected to FC storage, and I am sure I will also see the devices as
>> $1$DGAxxx.
>>
>> I want to use Volume Shadowing to mirror the two sites, but I am a bit
>> concerned that because the allocation class is 1 for fibre channel
>> storage at both sites this may cause confusion for the cluster
>> software.
>>
>> If anybody else has done this or has suggestions I would appreciate
>> the feedback.
>>
>> With regards
>> Andrew
>
Lee wrote:
> I have done multiple tests on these disks across a multi-site cluster.
> I was able to shadow $1$DGA disks with Storageworks $2$DUA
> disks (with the same number of blocks of course) with no problems.
> There was no difference in functionality of the two types of
> physical disks or the mix of shadow sets created.
> Be warned that under current 7.3-1 VMS, any $1$/$1$ or $1$/$2$
> shadow sets you create will undergo long shadow merges
> (5-12 hours) if any of your cluster nodes reboots or hiccups.
>
Or, you use the EVA technology and utilize Business copy to "replicate"
the entire EVA. The XP series (rebranded Hitachi) also has this sort
of long-distance update and removes the overhead from the system and
gives it back to the storage controller where it belongs in either sync
or async modes...
Michael Austin.
- Next message: healyzh_at_aracnet.com: "Re: jGRASP for OpenVMS"
- Previous message: Charlie Hammond: "Re: Equipment release policy?"
- In reply to: Lee: "Re: Volume shadowing between FC Storage at different sites, and the allocation class"
- Next in thread: Keith Parris: "Re: Volume shadowing between FC Storage at different sites, and the allocation class"
- Reply: Keith Parris: "Re: Volume shadowing between FC Storage at different sites, and the allocation class"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|