Replicating a Qtree to a Volume

[TMADOCTHOMAS]

I am familiar with the procedure for replicating a volume to a qtree.  What is the procedure for replicating a qtree to a volume?  Or, if there isn't one, what is the procedure for moving qtree contents into a volume?

[aborzenkov]

Do you mean moving content below qtree to top level? Just export/share volume and use host based commands to move files around.

[TMADOCTHOMAS]

Thanks for replying aborzenkov.  The scenario is this: we use volume-to-qtree snapmirror to replicate volumes from 2220's in our remote offices to qtrees on our 3270 at headquarters.  In the event of a disaster, we would make the qtrees on the 3270 read-write and use them until a new 2220 was available.  Then we would need to migrate the qtrees back to volumes on the new 2220.  I'm trying to determine the best plan to migrate the qtrees to volumes on a new 2220.  I see what you mean that we could share out both sides and use standard Windows copy commands, but I was hoping there was a snapmirror option.

[aborzenkov]

No, that's not possible. You can either use VSM (any reason you do not?) or arrange data in qtree on source as well.

Отправлено с iPhone

26.09.2013, в 0:07, "TMADOCTHOMAS" <xdl-communities@communities.netapp.com<mailto:xdl-communities@communities.netapp.com>> написал(а):

<https://communities.netapp.com/index.jspa>

Re: Replicating a Qtree to a Volume

created by TMADOCTHOMAS<https://communities.netapp.com/people/TMADOCTHOMAS> in Data ONTAP - View the full discussion<https://communities.netapp.com/message/117340#117340>

Thanks for replying aborzenkov. The scenario is this: we use volume-to-qtree snapmirror to replicate volumes from 2220's in our remote offices to qtrees on our 3270 at headquarters. In the event of a disaster, we would make the qtrees on the 3270 read-write and use them until a new 2220 was available. Then we would need to migrate the qtrees back to volumes on the new 2220. I'm trying to determine the best plan to migrate the qtrees to volumes on a new 2220. I see what you mean that we could share out both sides and use standard Windows copy commands, but I was hoping there was a snapmirror option.

Reply to this message by replying to this email -or- go to the message on NetApp Community<https://communities.netapp.com/message/117340#117340>

Start a new discussion in Data ONTAP by email<mailto:discussions-community-products_and_solutions-data_ontap@communities.netapp.com> or at NetApp Community<https://communities.netapp.com/choose-container.jspa?contentType=1&containerType=14&container=2877>

[TMADOCTHOMAS]

Thanks for the reply!  The only reason I'm not using VSM in this case is the data is in a qtree.  If I can easily copy it from that qtree to the root of the volume and then replicate it using volume-to-volume snapmirror, that would probably be the way to go.  I suppose I could make the volume a CIFS volume and do that.

[aborzenkov]

I do not quite understand. VSM replicates whole volume with all qtrees. How does it matter whether data is in qtree or not?

[TMADOCTHOMAS]

This is simply the standard we operate with: our remote offices have their data stored in volumes, so I want to be able to keep it consistant.