Volume to qtree migration limitations

[dhaneswarsingh]

Hi,

i am having a query, In DATA Ontap 7-mode volume to qtree conversion...

say i have a volume which needs to migrate into a qtree of same filer in a different volume.

what are the surprises i can see in attempting this task.

i just need to know the limitations if i perform this task.

-J

[vims]

Hi 

I am not really getting what are you trying to achive. Let's make it clear. 

As per documentation: 

Qtrees -  A qtree is a subdirectory of the root directory of a volume. You can use qtrees to subdivide a volume in order to group LUNs. 

So, volume is a container for qtrees and luns. Obviously volume can't be converted to qtree. 

Review your goals and post it. 

Cheers 

[dhaneswarsingh]

Thanks for the quick reply,

we're having a situation where we need to migrate a volume into a qtree using Snapmirror in the same filer.

Just need to enquire about the what are the limitations in performing this task.

[vims]

ok. Snapmirror is DR technology based on volume to volume or qtree to qtree.

So you can set up relationships between  volumes or qtrees.

there is Snapmirror documentation on NetaApp site, you can read.

In regards of limitations:  

- second volume will be RO until you bring it online

- there will be a base snapshot on source volume, which is required a space allocation

- transfer time take a while and it depends on volume size

etc...

Cheers

[dhaneswarsingh]

in that case,

Can we do a SM between Volume to qtree in the same filer... ?

If yes, then what are the limitations in do such an activity.

Please elaborate...

Thanks in advance.

-J

[vims]

---

@dhaneswarsingh wrote:

in that case,

Can we do a SM between Volume to qtree in the same filer... ?

-- no, as per documentation  - vol tol or qtree to qtree  

If yes, then what are the limitations in do such an activity.

what you mean by limitations? Limitation of what ?

Cheers

[dhaneswarsingh]

cant we perform this command ?

>>>snapmirror initialize –S Srcfiler:/vol/srcvol/-  Srcfiler:/vol/newsrcvol/newqtreename

But as per my research we can do this,

FYI,https://library.netapp.com/ecmdocs/ECMM1277793/html/onlinebk/GUID-DDC2E417-F227-45BB-AD3A-7D6469BD93D7.html

i just posted this question what kind of surprises | limitations i can see in performing this acitivity.

[vims]

sure you can.

this is the snapmirror activity

filer> snapmirror status

netapp-opr3:samappbackup                              netapp-opr3:samappbackup             Snapmirrored            22:34:25   Idle
netapp-opr3:samappbackup2014                       netapp-opr3:samappbackup2014      Uninitialized  -          Transferring  (15 TB done)

---

---

@dhaneswarsingh wrote:

cant we perform this command ?

>>>snapmirror initialize –S Srcfiler:/vol/srcvol/-  Srcfiler:/vol/newsrcvol/newqtreename

But as per my research we can do this,

FYI,https://library.netapp.com/ecmdocs/ECMM1277793/html/onlinebk/GUID-DDC2E417-F227-45BB-AD3A-7D6469BD93D7.html

i just posted this question what kind of surprises | limitations i can see in performing this acitivity.

---

[dhaneswarsingh]

So here is my direct question,

I am having a 1.5 TB of volume which needs to migrate into a qtree of the same filer.

so my filer specs are having:

DataONtap: NetApp Release 7.3.6

Model: FAS 2020.

and this volume is a CIFS shared volume,

if i convert this volume to qtree

1). I need to do the qtree level CIFS share.

2).  For the newly created qtree i have to change the mode as NTFS to visible for cifs share.

like this what kinds of pre-checks need to do be taken care off.

[vims]

---

@dhaneswarsingh wrote:

So here is my direct question,

I am having a 1.5 TB of volume which needs to migrate into a qtree of the same filer.

so my filer specs are having:

DataONtap: NetApp Release 7.3.6

Model: FAS 2020.

and this volume is a CIFS shared volume,

if i convert this volume to qtree

1). I need to do the qtree level CIFS share.

2).  For the newly created qtree i have to change the mode as NTFS to visible for cifs share.

like this what kinds of pre-checks need to do be taken care off.

---

you will not convert volume to qtree, you will have another volume with qtree in it. your data will be transfered to that specific qtree.
in order to have access to a share on destination volume you most likely have to edit a path to that share,  i.e was \vol\vol1\share1 is \vol\vol1\qt1\share1

cheers

managing CIFS shares