Mirrorclone creation through RSM

[zxcv]

My requirement is as follows ;

Day 1 at 9 pm;

1.Create a Mirrorclone of a Vdisk
2. Fracture the Mirror at 9.15 time
3. Immediately Present the fractured Vdisk (mirrorclone) to a host
4. After 4 hrs. time period unpresent the Vdisk from host
5. Re-establish the Mirrorclone.

6. Fracture the Mirror at x time

7. Present the fractured Vdisk (snapclone) to a host

Day 2 at 9pm;

1. Resync mirrorclone of a Vdisk ( follow the above steps , before that we need to unpresent that fractured Vdisk )

I read RSM user-guide but could not understand containers concept.

I have created managed set for my Vdisk , but stuck at container level.

Also a sample script would be of immense help ( am trying with help of templates too )

[zxcv]

Hi Guys,

My EVA is 6400

Unlimited BC licenses.

Am familiar  with Snapclones but not mirrorclone.

the need arised because we have almost 16 clones ( each Vdisk of atleast 200gb ) to be taken in a window of 2 hrs which chokes my EVA .

thanks in advance.

[zxcv]

Hi ,

Anyone out there to help me.

[Sheldon Smith · Accepted solution]

A container is preallocated space for a virtual disk without all the extra metadata. This lets you control the disk group leveling time. Likewise, there's no release of the storage when done, triggering another leveling event. Your best plan is to create a small (1 or 2 G) dummy vdisk, convert it to a container, create another container like it, convert both to dummy vdisks. Flip them back and forth. Get comfortable with containers.

Now: Your schedule looks like:
Setup:

1. Create a container
2. Create a Mirrorclone of a Vdisk

Operation:

1. Fracture the Mirror
2. Present the mirrorclone to a host
3. Do work
4. Unpresent the Vdisk from host
5. Resync the Mirrorclone

I don't have access to RSM system to look at all the templates. There should be something in there to handle a mirrorclone fracture-present and unpresent-resync.

[zxcv]

Thanks Sheldon.