Unsolved
This post is more than 5 years old
2 Posts
0
2376
October 15th, 2012 07:00
Data Migration using EMCopy
I am looking for an tool to use to copy Celerra FS data directories, that are spread across multiple filesystems but I need to drop the existing security on the files as part of the migration to clean up of the data. I have created the directory structure on the new target and set the correct permissions that I want the files to inherit but I need to be able to copy without carrying the existing permissions. Is there a switch on EMCopy that will drop permissions?
No Events found!
dynamox
9 Legend
•
20.4K Posts
0
October 15th, 2012 08:00
Remove /o ?
umichklewis
3 Apprentice
•
1.2K Posts
0
October 15th, 2012 09:00
By default, /o allows the copy command to replace the copy account with the file's owner, that is, if you copy as DOMAIN\COPYADMIN, it will read the file's owner from the filesystem and write that as the owner on the destination. Without /o, it would change the owner of the file to COPYADMIN.
I think want to look at using /nosec, which will ignore the security options on the source file and folder. If you've already got your destination permissions in place, this is probably the option you want. From the EMCOPY readme:
The "/nosec" option disables the copy of the NT security properties of
the file or the directory. By default, discretionary access control-lists
are replicated on the created file or directory. This option takes priority
on the "/o", "/a", "/lg", "/i" options.
As with all things you should test a partial copy and see if you get the expected results.
Let us know if this helps!
Karl
scm165
2 Posts
0
October 16th, 2012 08:00
Thanks for your help and suggestions. I used the /nosec which seemed to work fine during the test. I started the process but when I later checked the script it is occasionally giving the following error: "unable to set attributes on directory". Any thoughts or suggestions? I am copying a 5TB filesystem with thousands of small directories and files..
umichklewis
3 Apprentice
•
1.2K Posts
0
October 16th, 2012 09:00
One possibility is to set the parameters in Solution ID emc46968. Dynamox posted the full text of the solution ID on the forum, in case you can't find it. These are typically used for Windows to Celerra migrations. In your case, this might be the one to set:
In this case, this should suppress the errors being reported, but I'm curious about other things. Have you looked at any of the directories in question? Do the files have a legitimate SID?