This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Move to new iscsi- target

hello,

(2 node sles10.3 oes2sp3 - connected to iscsi target with volume)

our infrastructure department gave us a new iscsi target where we have to move our clustered volume to.
The old target will not be available soon.

Any ideads on how to "migrate" the volume to this new iscsi target? Is there docu available on this?

thx.
hugo
Parents
  • 0
    There's a few things I can think of:

    1) If your SAN supports copying disks, you can clone/copy the existing iSCSI disk/LUN/volume and then offline the cluster resource of the EXISTING item and possibly online the new one (you'll have to change some IP stuff I imagine). OR possibly be able to re-use the old IP of the old iSCSI LUN and assign that to the copied one.

    2) You can probably use miggui to migrate the data from one to another, although I imagine this will require changing the cluster resource names/volume in the process which may be undesireable (ie, if the volume hosts HOME directories, for example, or if you have items that utilize the UNC path)

    3) Some combination of DST setup. You shadow the current iSCSI disk and basically use the "2nd" scenario described in the cluster docs where you create a secondary volume and basically shadow all the data over to the 2nd shadow volume which exists on the new SAN/whatever. Then offline the resource/break the shadow and then create the new primary on the new iSCSI node and re-link the shadow/DST volume to that. You can keep the same volume name of the primary in that case (I've done that before--just not with iSCSI).
Reply
  • 0
    There's a few things I can think of:

    1) If your SAN supports copying disks, you can clone/copy the existing iSCSI disk/LUN/volume and then offline the cluster resource of the EXISTING item and possibly online the new one (you'll have to change some IP stuff I imagine). OR possibly be able to re-use the old IP of the old iSCSI LUN and assign that to the copied one.

    2) You can probably use miggui to migrate the data from one to another, although I imagine this will require changing the cluster resource names/volume in the process which may be undesireable (ie, if the volume hosts HOME directories, for example, or if you have items that utilize the UNC path)

    3) Some combination of DST setup. You shadow the current iSCSI disk and basically use the "2nd" scenario described in the cluster docs where you create a secondary volume and basically shadow all the data over to the 2nd shadow volume which exists on the new SAN/whatever. Then offline the resource/break the shadow and then create the new primary on the new iSCSI node and re-link the shadow/DST volume to that. You can keep the same volume name of the primary in that case (I've done that before--just not with iSCSI).
Children
  • 0   in reply to 
    On 03.11.2011 20:26, kjhurni wrote:
    >
    > There's a few things I can think of:
    >
    > 1) If your SAN supports copying disks, you can clone/copy the existing
    > iSCSI disk/LUN/volume and then offline the cluster resource of the
    > EXISTING item and possibly online the new one (you'll have to change
    > some IP stuff I imagine). OR possibly be able to re-use the old IP of
    > the old iSCSI LUN and assign that to the copied one.
    >
    > 2) You can probably use miggui to migrate the data from one to
    > another, although I imagine this will require changing the cluster
    > resource names/volume in the process which may be undesireable (ie, if
    > the volume hosts HOME directories, for example, or if you have items
    > that utilize the UNC path)
    >
    > 3) Some combination of DST setup. You shadow the current iSCSI disk
    > and basically use the "2nd" scenario described in the cluster docs where
    > you create a secondary volume and basically shadow all the data over to
    > the 2nd shadow volume which exists on the new SAN/whatever. Then
    > offline the resource/break the shadow and then create the new primary on
    > the new iSCSI node and re-link the shadow/DST volume to that. You can
    > keep the same volume name of the primary in that case (I've done that
    > before--just not with iSCSI).
    >
    >

    4. Not to forget the good old mirroring trick.. ;)

    CU,
    --
    Massimo Rosen
    Novell Knowledge Partner
    No emails please!
    http://www.cfc-it.de