|
Home > Archive > Data Storage > October 2005 > EMC SRDF Data Migration Question
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
EMC SRDF Data Migration Question
|
|
| Wennovate 2005-10-24, 9:44 am |
| Hi.
Migrating an older symm to DMX, since R1/R2 conversion needs a bin
file change in the old symm, we are using existing SRDF relationship to
migrate data from DMX to old Symm. Now the question is, there are a
few devices that are visible to a HP-UX host that don't have SRDF
relationship (not in the R1 device group). My question is, what are
the steps to convert standard volumes to R1, so I can SRDF them to the
old symm?
DMX is the source (R1) and Older Symm is the Target (R2)
Went through emc docs, but all the examples are about existing R1s, but
don't I have to convert the remaining standards to R1 to accomplish
full data migration?
Also need to know if any change in switch mode (FC_AL) is necessary.
Thanks much in advance.
| |
| Jon Metzger 2005-10-24, 9:44 am |
| Wennovate wrote:
> Hi.
>
> Migrating an older symm to DMX, since R1/R2 conversion needs a bin
> file change in the old symm, we are using existing SRDF relationship to
> migrate data from DMX to old Symm. Now the question is, there are a
> few devices that are visible to a HP-UX host that don't have SRDF
> relationship (not in the R1 device group). My question is, what are
> the steps to convert standard volumes to R1, so I can SRDF them to the
> old symm?
>
> DMX is the source (R1) and Older Symm is the Target (R2)
>
> Went through emc docs, but all the examples are about existing R1s, but
> don't I have to convert the remaining standards to R1 to accomplish
> full data migration?
>
> Also need to know if any change in switch mode (FC_AL) is necessary.
>
> Thanks much in advance.
>
Not sure if this will work for you. It may depend on the code level
you're at on your old Symm. I have converted standard devices to R1s
before via this process:
Create a text file called convert.txt with these contents all on a
single line. Device 100 here is the device you want converted to R1 and
device 200 is the device in the remote Symm you want converted to R2.
convert dev 100 to RDF1, ra_group=01, remote_dev=200, invalidate=R2,
start_copy=yes;
Then run "symconfigure -sid <sid of Symm that owns device 100> -f
convert.txt commit". (You'll probably want to do a preview and a
prepare before the commit, and my synatax here may be a little off here
or there.) This will create the R1/R2 relationship and immediately
start copying the data from device 100 over the top of device 200.
**All the data that was on device 200 will be destroyed and overwritten
with device 100's data**. I'm a little unclear as to whether or not
that's exactly what you want, but it should give you an idea where to
get started.
Jon
| |
| Wennovate 2005-10-24, 9:44 am |
| Thanks much for the info Jon, I am using microcode 5568, and according
to emc docs, this should support dynamic srdf (even R1/R2 volume swap
without bin file change) on symm 8530, but don't know why symrdf
createpair -file pairfile command fails.
One other problem I incurred trying to mount the disks, is the
following--
In an effort to solve non-contiguous lun not appearing on HP-UX hosts,
I set the offset feature. Now, I can see the devices, but somehow the
gatekeeper disappeard. Eearlier today I backed up symmaskdb in a file.
What's the procedure to restore symmaskdb and gatekeeper?
This is the error I get for any symmask command
"A path to the device masking database could not be found"
>From the device masking guide-
To set LUN base and offset values for a skip hole within an HBA to
director channel, use the following syntax:
symmask -sid SymmID set lunoffset on offset base -awwn awwn -dir # -p #
Any help will be greatly appreciated!
-Shahriar Chowdhury
|
|
|
|
|