Highlighted
david_waters
1 Copper

1 src to 2 target SanCopy to a Win 2003 Cluster

Looking for direction or success stories:

In working with a server team, we are performing a SanCopy from 1 source device to 2 target devices.  Once the copy is complete, the server team would like to bring both target devices online to a Win 2003 Cluster.  Of course, there is the disk signature issue.

What I am looking for is direction and/or success stories of someone that may have performed this type of operation before.  How did you change the disk signature on one of the devices?  Were you able to preserve data after changing the disk signature.

Thanks.

Labels (1)
0 Kudos
2 Replies
dynamox
6 Gallium

Re: 1 src to 2 target SanCopy to a Win 2003 Cluster

David,

how do you feel about going to Symmetrix land a little bit, this is where all the good stuff is at

1) Download Solutions Enabler 7.1 from here

Home  >  Support  >  Software Downloads and Licensing  > Downloads S  > Solutions Enabler

2) Install with default options

3) Present both targets to the host and run this commad:

C:\Program Files\EMC\SYMCLI\bin>symntctl.exe list -signature

  \\.\PhysicalDrive0 - A27EA27E

  \\.\PhysicalDrive2 - 1234ABCD

  Total Disks: 2

in my example i have one local drive and one external drive. In your situation you will see two physical drives with the same signature. Let's say you want to change signature on physicaldrive2

4) Run this command, not only will it erase existing signature but it will also assign a random signature

C:\Program Files\EMC\SYMCLI\bin>symntctl.exe signature -pd \\.\PhysicalDrive2 -erase

  Successfully erased the disk signature.

5) Let's verify how it looks now

C:\Program Files\EMC\SYMCLI\bin>symntctl.exe list -signature

  \\.\PhysicalDrive0 - A27EA27E

  \\.\PhysicalDrive2 - 90808344

  Total Disks: 2

Hopefully that's what you are looking for.

0 Kudos
AranH1
4 Germanium

Re: 1 src to 2 target SanCopy to a Win 2003 Cluster

Changing the disk signature doesn't affect the data on the partitioni of the LUN so you are fine there. Microsoft has a cluster tool that is used to change disk signatures, but I think the process Dynamox documented will be easier.

One thing, these LUNs that you are presenting are not already Cluster resources are they? If you are presenting two clones of an existing cluster disk to a cluster that will be problematic for the resource until you get the disk signature fixed.

0 Kudos