Start a Conversation

This post is more than 5 years old

Solved!

Go to Solution

1103

June 23rd, 2011 10:00

Tree quotas in and existing environment

In a NAS environment with Celerra v6, i know that it is not possible to stablish tree quotas to existing folders. Thus, what is the best way to do it?. I thought creating a new folder structure and move all data to it, then rename it.

Do you any experience with it?

4 Operator

 • 

8.6K Posts

June 24th, 2011 05:00

Windows Explorer „Cut & Paste“ is the worst migration method you could choose

Not only is it slower because its single-threaded – it also does NOT migrate owner and ACLs

Rainer

9 Legend

 • 

20.4K Posts

June 23rd, 2011 10:00

that's what we had to do.

4 Operator

 • 

8.6K Posts

June 23rd, 2011 12:00

Yes that would work

1 Rookie

 • 

28 Posts

June 24th, 2011 00:00

I think we need to stop access to that new folder to be sure no connections are open to make the movement without problems, is it correct?

9 Legend

 • 

20.4K Posts

June 24th, 2011 03:00

you can pre-copy data into the new folder ahead of time, then on the day of cut-over disconnect everybody from the original folder and copy the changes one more time (emcopy/robocopy are good tools for this migrations).

275 Posts

June 24th, 2011 04:00

No because tree quotas are not like directories

The cut/paste will do the same as if done between different file systems

Claude

1 Rookie

 • 

28 Posts

June 24th, 2011 04:00

I've used EMCOPY / ROBOCOPY for data migration in different file systems, but in this case (within the same file system) is it possible to stop the service and then do a "cut and paste" of data into the new folder structure? I think that if there is no open file the "cut and paste" action would be quicker. Is it true?

9 Legend

 • 

20.4K Posts

June 24th, 2011 05:00

cut and paste is not going to be quicker then emcopy as emcopy is a multhi-thread application. There is nothing stopping you from using emcopy with the same file system. You could remove share from the directory you are migrating to ensure no user is accessing the data and connect to the CIFS server at a higher level so your emcopy copy command would look like this:

emcopy \\cifsserver\c$\filesystemname\old_directory \\cifsserver\c$\filesystename\new_directory

No Events found!

Top