There's nothing wrong with it in that it'll work, but if there's a way I can make this look the same as a newly created share instead of making it yet another exception to the standard, I'd take it.

@Richard: we have a bunch of old qtree shares from the early days of this box that share a flexvol in a 32 bit aggregate. We can't upgrade to 64 bit aggregates on this box, there's no room left in the 32 bit aggregate (and it can't be increased any more), and the volume is now taking 3 days to do a backup. We're taking the highest growth and highest current sized shares and putting them into their own volumes in new aggregates with plenty of headroom.

On Tue, Jan 13, 2015 at 2:45 PM, Payne, Richard richard.payne@amd.com wrote:

Not a solution, but why do you want the data outside a qtree?

--rdp

*From:* toasters-bounces@teaparty.net [mailto: toasters-bounces@teaparty.net] *On Behalf Of *Basil *Sent:* Tuesday, January 13, 2015 2:35 PM *To:* toasters@teaparty.net *Subject:* Is it possible to copy a qtree to its own volume?

I'm trying to take a qtree and move it into its own flexvol (7 mode). It has millions of small files, so robocopy or ndmpcopy are taking too long for the final pre-cutover sync of the migration.

So far, the best option I can come up with is to use qtree snapmirror to copy it into a qtree in a new volume and share that qtree, however this isn't clean, and qtree snapmirror still has to span the filesystem. My other considered option was to use a volume snapmirror and then delete everything but the qtree that I need to keep on the destination volume once it's been split off, however this still leaves me with a cifs share pointing to a qtree instead of a volume. At least it would be a block copy instead of a filesystem copy, though.

Anyone have any ideas?

Basil

---

Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters

Hi Alex, copying them up one level takes me as long as a robocopy from the original volume would. It's an NTFS qtree, which are pretty hard on the processors when you span the filesystem.

On Tue, Jan 13, 2015 at 3:36 PM, Alexander Griesser ag@anexia.at wrote:

Maybe I’m missing something here, but a qtree is just a directory and as long as the gazillions of files are not directly inside the qtree, just copy the qtree over and mount the volume via NFS and move the files one directory up, then delete the qtree (no more files left in there).

Moving files should be very fast and then you don’t have this exception anymore… but I could just have misunderstood you, so if that’s the case, sorry for that.

Best,

*Alexander Griesser*

Head of Systems Operations

ANEXIA Internetdienstleistungs GmbH

E-Mail: ag@anexia.at

Web: http://www.anexia.at

Anschrift Hauptsitz Klagenfurt: Feldkirchnerstraße 140, 9020 Klagenfurt

Geschäftsführer: Alexander Windbichler

Firmenbuch: FN 289918a | Gerichtsstand: Klagenfurt | UID-Nummer: AT U63216601

*Von:* toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net] *Im Auftrag von *Basil *Gesendet:* Dienstag, 13. Jänner 2015 21:22 *An:* toasters@teaparty.net *Betreff:* Re: Is it possible to copy a qtree to its own volume?

There's nothing wrong with it in that it'll work, but if there's a way I can make this look the same as a newly created share instead of making it yet another exception to the standard, I'd take it.

@Richard: we have a bunch of old qtree shares from the early days of this box that share a flexvol in a 32 bit aggregate. We can't upgrade to 64 bit aggregates on this box, there's no room left in the 32 bit aggregate (and it can't be increased any more), and the volume is now taking 3 days to do a backup. We're taking the highest growth and highest current sized shares and putting them into their own volumes in new aggregates with plenty of headroom.

On Tue, Jan 13, 2015 at 2:45 PM, Payne, Richard richard.payne@amd.com wrote:

Not a solution, but why do you want the data outside a qtree?

--rdp

*From:* toasters-bounces@teaparty.net [mailto: toasters-bounces@teaparty.net] *On Behalf Of *Basil *Sent:* Tuesday, January 13, 2015 2:35 PM *To:* toasters@teaparty.net *Subject:* Is it possible to copy a qtree to its own volume?

I'm trying to take a qtree and move it into its own flexvol (7 mode). It has millions of small files, so robocopy or ndmpcopy are taking too long for the final pre-cutover sync of the migration.

So far, the best option I can come up with is to use qtree snapmirror to copy it into a qtree in a new volume and share that qtree, however this isn't clean, and qtree snapmirror still has to span the filesystem. My other considered option was to use a volume snapmirror and then delete everything but the qtree that I need to keep on the destination volume once it's been split off, however this still leaves me with a cifs share pointing to a qtree instead of a volume. At least it would be a block copy instead of a filesystem copy, though.

Anyone have any ideas?

Basil

---

Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters

What do you mean by Qtree snapmirror isn’t a ‘clean’ solution? “and qtree snapmirror still has to span the filesystem”

We use QSM to migrate data around all the time, both NTFS & Unix, between volumes on different file servers. Yes it requires that it walk the snapshot to pull out the files for that qtree, but you can run that over several days and even had it run incremental updates until you’re ready to cutover. The only drawback I see is your CIFS share could changes if it’s a different NetApp on the destination side (unless you’re using DFS or something similar to abstract that).

--rdp

From: toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net] On Behalf Of Basil Sent: Tuesday, January 13, 2015 3:58 PM To: toasters@teaparty.net Subject: Re: Is it possible to copy a qtree to its own volume?

Hi Alex, copying them up one level takes me as long as a robocopy from the original volume would. It's an NTFS qtree, which are pretty hard on the processors when you span the filesystem.

On Tue, Jan 13, 2015 at 3:36 PM, Alexander Griesser <ag@anexia.atmailto:ag@anexia.at> wrote: Maybe I’m missing something here, but a qtree is just a directory and as long as the gazillions of files are not directly inside the qtree, just copy the qtree over and mount the volume via NFS and move the files one directory up, then delete the qtree (no more files left in there).

Moving files should be very fast and then you don’t have this exception anymore… but I could just have misunderstood you, so if that’s the case, sorry for that.

Best,

Alexander Griesser Head of Systems Operations

ANEXIA Internetdienstleistungs GmbH

E-Mail: ag@anexia.atmailto:ag@anexia.at Web: http://www.anexia.athttp://www.anexia.at/

Anschrift Hauptsitz Klagenfurt: Feldkirchnerstraße 140, 9020 Klagenfurt Geschäftsführer: Alexander Windbichler Firmenbuch: FN 289918a | Gerichtsstand: Klagenfurt | UID-Nummer: AT U63216601

Von: toasters-bounces@teaparty.netmailto:toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.netmailto:toasters-bounces@teaparty.net] Im Auftrag von Basil Gesendet: Dienstag, 13. Jänner 2015 21:22 An: toasters@teaparty.netmailto:toasters@teaparty.net Betreff: Re: Is it possible to copy a qtree to its own volume?

There's nothing wrong with it in that it'll work, but if there's a way I can make this look the same as a newly created share instead of making it yet another exception to the standard, I'd take it.

@Richard: we have a bunch of old qtree shares from the early days of this box that share a flexvol in a 32 bit aggregate. We can't upgrade to 64 bit aggregates on this box, there's no room left in the 32 bit aggregate (and it can't be increased any more), and the volume is now taking 3 days to do a backup. We're taking the highest growth and highest current sized shares and putting them into their own volumes in new aggregates with plenty of headroom.

On Tue, Jan 13, 2015 at 2:45 PM, Payne, Richard <richard.payne@amd.commailto:richard.payne@amd.com> wrote: Not a solution, but why do you want the data outside a qtree?

--rdp

From: toasters-bounces@teaparty.netmailto:toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.netmailto:toasters-bounces@teaparty.net] On Behalf Of Basil Sent: Tuesday, January 13, 2015 2:35 PM To: toasters@teaparty.netmailto:toasters@teaparty.net Subject: Is it possible to copy a qtree to its own volume?

I'm trying to take a qtree and move it into its own flexvol (7 mode). It has millions of small files, so robocopy or ndmpcopy are taking too long for the final pre-cutover sync of the migration.

So far, the best option I can come up with is to use qtree snapmirror to copy it into a qtree in a new volume and share that qtree, however this isn't clean, and qtree snapmirror still has to span the filesystem. My other considered option was to use a volume snapmirror and then delete everything but the qtree that I need to keep on the destination volume once it's been split off, however this still leaves me with a cifs share pointing to a qtree instead of a volume. At least it would be a block copy instead of a filesystem copy, though.

Anyone have any ideas?

Basil

_______________________________________________ Toasters mailing list Toasters@teaparty.netmailto:Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters

Thank you all for your help- the solution I decided on is to do a QSM to a qtree in the new volume and then use the windows move command (instead of robocopy) to put all the data into the parent volume without actually moving it. The move command itself will only move files and skips directories, but I wrote a script to move them as well.

Once I try this on the heavily loaded production system, I'll see whether qtree snapmirror has any issues with the large number of files in the dataset or heavily utilized processors, but even if it goes more slowly than a volume snapmirror, I can let the initial sync take the time it'll take and then use an update to reduce the outage window drastically, compared to the initial robocopy or ndmpcopy plan.

Thanks again!

On Tue, Jan 13, 2015 at 4:15 PM, Basil basilberntsen@gmail.com wrote:

@Justin: I'll try that from the command line and see if I can avoid the copy. Thank you!

@Richard: What I meant was that having a qtree shared rather than the volume was not clean- qtree snapmirror is fine.

On Tue, Jan 13, 2015 at 4:05 PM, Payne, Richard richard.payne@amd.com wrote:

...

What do you mean by Qtree snapmirror isn’t a ‘clean’ solution? “and qtree snapmirror still has to span the filesystem”

We use QSM to migrate data around all the time, both NTFS & Unix, between volumes on different file servers. Yes it requires that it walk the snapshot to pull out the files for that qtree, but you can run that over several days and even had it run incremental updates until you’re ready to cutover. The only drawback I see is your CIFS share could changes if it’s a different NetApp on the destination side (unless you’re using DFS or something similar to abstract that).

--rdp

*From:* toasters-bounces@teaparty.net [mailto: toasters-bounces@teaparty.net] *On Behalf Of *Basil *Sent:* Tuesday, January 13, 2015 3:58 PM *To:* toasters@teaparty.net *Subject:* Re: Is it possible to copy a qtree to its own volume?

Hi Alex, copying them up one level takes me as long as a robocopy from the original volume would. It's an NTFS qtree, which are pretty hard on the processors when you span the filesystem.

On Tue, Jan 13, 2015 at 3:36 PM, Alexander Griesser ag@anexia.at wrote:

Maybe I’m missing something here, but a qtree is just a directory and as long as the gazillions of files are not directly inside the qtree, just copy the qtree over and mount the volume via NFS and move the files one directory up, then delete the qtree (no more files left in there).

Moving files should be very fast and then you don’t have this exception anymore… but I could just have misunderstood you, so if that’s the case, sorry for that.

Best,

*Alexander Griesser*

Head of Systems Operations

ANEXIA Internetdienstleistungs GmbH

E-Mail: ag@anexia.at

Web: http://www.anexia.at

Anschrift Hauptsitz Klagenfurt: Feldkirchnerstraße 140, 9020 Klagenfurt

Geschäftsführer: Alexander Windbichler

Firmenbuch: FN 289918a | Gerichtsstand: Klagenfurt | UID-Nummer: AT U63216601

*Von:* toasters-bounces@teaparty.net [mailto: toasters-bounces@teaparty.net] *Im Auftrag von *Basil *Gesendet:* Dienstag, 13. Jänner 2015 21:22 *An:* toasters@teaparty.net *Betreff:* Re: Is it possible to copy a qtree to its own volume?

There's nothing wrong with it in that it'll work, but if there's a way I can make this look the same as a newly created share instead of making it yet another exception to the standard, I'd take it.

@Richard: we have a bunch of old qtree shares from the early days of this box that share a flexvol in a 32 bit aggregate. We can't upgrade to 64 bit aggregates on this box, there's no room left in the 32 bit aggregate (and it can't be increased any more), and the volume is now taking 3 days to do a backup. We're taking the highest growth and highest current sized shares and putting them into their own volumes in new aggregates with plenty of headroom.

On Tue, Jan 13, 2015 at 2:45 PM, Payne, Richard richard.payne@amd.com wrote:

Not a solution, but why do you want the data outside a qtree?

--rdp

*From:* toasters-bounces@teaparty.net [mailto: toasters-bounces@teaparty.net] *On Behalf Of *Basil *Sent:* Tuesday, January 13, 2015 2:35 PM *To:* toasters@teaparty.net *Subject:* Is it possible to copy a qtree to its own volume?

I'm trying to take a qtree and move it into its own flexvol (7 mode). It has millions of small files, so robocopy or ndmpcopy are taking too long for the final pre-cutover sync of the migration.

So far, the best option I can come up with is to use qtree snapmirror to copy it into a qtree in a new volume and share that qtree, however this isn't clean, and qtree snapmirror still has to span the filesystem. My other considered option was to use a volume snapmirror and then delete everything but the qtree that I need to keep on the destination volume once it's been split off, however this still leaves me with a cifs share pointing to a qtree instead of a volume. At least it would be a block copy instead of a filesystem copy, though.

Anyone have any ideas?

Basil

---

Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters

---

Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters