Subscribe

Cloning a Volume/Lun

Hi, I was wondering if I could get some help on cloning a volume/lun.

Right now I have 8 servers and only 1 of them has an OS installed (RHEL 5.5, pre-patch). I would like to clone the volume/lun to deploy the OS faster. Would I clone the entire volume or just the LUN?

Also, which method woul dbe the best to use, Snapmirror or a LUN clone?

Thanks in advance.

Re: Cloning a Volume/Lun

My preference would be to clone the volume so you can snapshot the LUNs independently.


I hope this response has been helpful to you.

At your service,


Eugene E. Kashpureff
ekashp@kashpureff.org
NetApp Instructor and Independent Consultant
http://www.linkedin.com/in/eugenekashpureff

(P.S. I appreciate points for helpful or correct answers.)

Re: Cloning a Volume/Lun

Would you mind helping me map out the steps on how to do this, it's actually my first time. Thanks

Re: Cloning a Volume/Lun

I don't mind - I'll try !

Shut down the server with your original LUN.

See the man pages for:

'vol clone create' to clone your volume with the LUN in it for each new LUN.

'igroup create' to create an igroup for each new machine.

'lun map' to map each new LUN to each new igroup.


I hope this response has been helpful to you.

At your service,


Eugene E. Kashpureff
ekashp@kashpureff.org
NetApp Instructor and Independent Consultant
http://www.linkedin.com/in/eugenekashpureff

(P.S. I appreciate points for helpful or correct answers.)

Re: Cloning a Volume/Lun

There is also a 3rd way... we have vol and lun clone which are tied to snapshots...you can split to release the snap... but there is also the "clone start" command which was originally called sis clone... it creates a clone of a lun or volume (in the same volume) using the dedup (asis) process..  so there is no additional overhead to the lun after creation and it is not tied to a snapshot either after creation.  The volume does need sis enabled since sis is used to create the clone.  This method requires a flexclone license... the same as vol clone.. but lun clone is free.  You could lun clone, clone split, then run asis to get the same result but in 3 steps instead of one.

Re: Cloning a Volume/Lun

I apologize, but where would you enter the commands to clone the volume if the server is down.

Re: Cloning a Volume/Lun

I believe we have a flexclone license. Would you mind helping me with the steps on how to proceed with that. Thank you

Re: Cloning a Volume/Lun

Syntax for the clone (sis clone) command...specify a lun or file /vol/volname/qtreename/lun1.lun for example..

clone start <src_path> <dest_path> [-n] [-l]  
    # -n to NOT create temp snapshot during clone
    # -l to enable change logging on all clone blocks and that will be used by deduplication

Data ONTAP performs necessary metadata operations for LUN cloning

clone start <src_path> [dest_path] [-n] [-l] <-r <src_fbn>:<dest_fbn>:<fbn_cnt> ...>.
    # for API to clone file within a lun from a host (src/dest_fbn)

clone status [vol-name [ID]]
clone stop <vol-name> <ID>
clone clear <vol-name> <ID>

Re: Cloning a Volume/Lun

It's the RedHat server you need to shut down, not the filer.

You'd want it to be shut down so that the LUN is in a consistent state when you take the snapshot for the clone.


I hope this response has been helpful to you.

At your service,


Eugene E. Kashpureff
ekashp@kashpureff.org
NetApp Instructor and Independent Consultant
http://www.linkedin.com/in/eugenekashpureff

(P.S. I appreciate points for helpful or correct answers.)

Re: Cloning a Volume/Lun

Or use the 'vol clone' command to clone the volume instead of the LUN.

Advantage is to be able to take seperate snapshots for each of the 8 machines.


I hope this response has been helpful to you.

At your service,


Eugene E. Kashpureff
ekashp@kashpureff.org
NetApp Instructor and Independent Consultant
http://www.linkedin.com/in/eugenekashpureff

(P.S. I appreciate points for helpful or correct answers.)