Community

Subscribe
Highlighted
Accepted Solution

Cannot create LUN on a read-only volume or qtree

I am creating a lun on DR filer, and getting the message as titled. I understand this is because the DR volume is in restric mode,My question is following:
To create a LUN, can I "vol online vol_name", and then after done with creating the lun, do "vol restric vol_name"? Is this how people would do to create a LUN under a restricted DR volume?

Thanks for your inputs

Re: Cannot create LUN on a read-only volume or qtree

What do you call "DR volume"? I have never seen such term in NetApp documentation.

Re: Cannot create LUN on a read-only volume or qtree

I hope you are talking in the terms of volume snapmirror.

if so, once you break the relationship of snapmirror it will make the Volume online and luns will be made available to map.

Re: Cannot create LUN on a read-only volume or qtree

Once you break the snapmirror, the volume will be online automatically and LUN can be created in this Volume. But if you resume the snapmirror again, the DR volume will again be a mirror image of the source volume. I hope I am making my point clear.

Re: Cannot create LUN on a read-only volume or qtree

understand all your comments. However, I have one more question.

let's say the volume on primary site is vol1, and dr site is dr_vol1, I created /vol1/lun1, break up the snapmirror on DR site, and then create /dr_vol1/dr_lun1.

Now, my second thought is: how lun1 data is sync'ed to dr_lun1? I understand the entire vol1 including lun1 will be updated to dr_vol1, but how metadata about lun1 is recognized by dr_lun1? Hope you understand what I am saying here.

Re: Cannot create LUN on a read-only volume or qtree

I think you've got yourself a bit confused.

If you're using snapmirror (volume or qtree) you don't need the lun on the target volume, the initial snapmirror does that for you.

snapmirror also copies the entire lun (typically the whole volume) block for block on the initial set up and then any changed blocks on the schedule you set.

In a DR situ you need to mount that lun on the DR server, and will need to have set up the equivalent igroups etc on the DR filer.

Re: Cannot create LUN on a read-only volume or qtree

Hi nigelg1965,

I admit that I am not 100% understanding you.

Do I then need to create the lun on DR site, since data will be replicated anyway in volume basis?

If I need to create the lun on DR site, how does the filer know dr_lun1 will be matching with lun1? it seems to be dr_vol1 has no knowledge on the relationship between dr_lun1 and lun1.

You are absolutely right ,  that I've got myself a bit confused...

Re: Cannot create LUN on a read-only volume or qtree

Hi

Once you create the snapmirror relationship and it completes the initial replication, the LUN will be there. What won't be there are the igroup settings.

Re: Cannot create LUN on a read-only volume or qtree

Correct. You don't have to create the lun in DR again, what you need to do is may be create the Igroup and Map the Lun. or if you have already I group is there, map the lun to correct Igroup.

Re: Cannot create LUN on a read-only volume or qtree

Okay. So, should I remove the dr_lun1 from DR site then? If I remove it, the lun with the same name as the one on primary site would show up on my DR filer?