how to use lgdup/emcopy/sharedup maybe batch examples
Hey EMC-Community,
i have to migrate a an old fileserver to an new fileserver (emc vnx 5300). I created a new virtual data mover. At the new VDM i created a CIFS Server. I want to migrate the old fileserver incl. ACL, Permissions, Share to the new VNX5300. I searched a while and found the "Using EMC Utilities for the CIFS Environment.pdf"
I found out that i have to run the "lgdup.exe" to copy the local groups to the vnx 5300
After that i have to run the "emcopy.exe" to copy all files incl. the acls and permissions
After i copied the files with "emcopy.exe" i have to run the "sharedup.exe" to copy all shares to the new fileserver.
So far so well, i created for each tool a batch. They looks like that:
To copy the share to the new fileserver is my problem. I dont understand to export the shares on the oldfileserver to txt. file with sharedup. Can anyone give me an example how to use the sharedup? Got anyone experience with that tool how to use it right?
Thxs for your help experts. I am new here. Iam sorry for my englisch.
srcdrive Drive letter of the server source to select for the
duplication (example C:). Specify "ALL", to select all
drives of the source server.
So, in my case, "CRCNAS02" is an old Windows 2003 server and "CRCNAS02-tmp" is the CIFS server on my VG2. I used the following command at the command line:
X:\SHAREDUP \\CRCNAS02 \\CRCNAS02-temp ALL /LU /LOG+:SHAREDUP.txt
and I get the following written into the logfile called "SHAREDUP.txt"
SHAREDUP 02.03
Copyright (C) 2008-2010, All Rights Reserved,
by EMC Corporation, Hopkinton MA.
Source server:DFDNAS02 5.0
Target server:DFDNAS02-TMP 5.0 EMC-SNAS:T7.0.14.0
SHAREDUP
\\dfdnas02
\\dfdnas02-tmp
ALL
/LU
/LOG+:SHAREDUP.txt
---
Fri Jan 20 19:16:52 2012
Creating share "\\DFDNAS02-TMP\asa01collections$"
to export directory "C:\fs_ev02collections\data"...
-> OK
Now, on my VG2, I have a hidden share (note the "$" indicates a hidden share) on my new VG2 for the filesystem. All the output was appended to the LOG file (note the "+" indicates append to log file, not overwrite), which I can review for errors.
You can also use the flag /FO: to write out all the shares to a text file. At a later time, you can use /FI: to read back in that same file and create the shares, based on the entries in the text file.
The /FI flag stands for "File Input". It tells SHAREDUP to read in the Share from the text file you supplied and write it to the destination CIFS server. In my example above, I copied the permissions directly from the source Windows server to the destination CIFS server without writing to a file - only the output was logged to my file, not the share listing.
If you want to write out the share permissions to a file, you must use SHAREDUP with the /FO flag to write the share permissions to your file in one step. Then, you must run SHAREDUP with the /FI flag to read in from your text file and write to the destination CIFS server. Does that make sense?
I agree that reading the docs and understanding the options is better than just copy&paste commands without know whether or not they are the best choice for your particular environment
to re-iterate what Karl mentioned, if this is your first migration to this platform you can setup a test CIFS server or practice with a virtual appliance
No worries, Riccardo - the included README.txt files with each has shows each flag for each command. I strongly urge you to try each command out and understand how the flags affect each command. You must understand what happens if you include/remove certain flags. If you blindly run commands - mine or anyone else's here - you run the risk of failing to copy shares, groups or ACL information and be forced to do all the work all over again.
My suggestion for the process is:
0) TEST, TEST and TEST until you understand the entire process and your fallback options
1) copy local groups with LGDUP and review the logs
2) copy shares with SHAREDUP and review the logs
3) copy files with EMCOPY and review the logs
For LGDUP, your commands might look like LGDUP -L+ \\SOURCE \\DESTINATION:
LGDUP -s -v -l+ M1S02-CIFS01-LGDUP.txt \\M1S02 \\CIFS01 (note the direction and number of backslashes)
This would copy any local groups to the destination and attempt to merge any local groups found, but not set any local groups members in case of an error. Why would I do this instead of another flag? I leave that as an exercise for you to figure out.
For SHAREDUP, if you wanted to write out your shares to a file, your commands might look like SHAREDUP \\SOURCE \\DESTINATION /FO: /LOG+:
SHAREDUP \\M1S02 \\CIFS01 ALL /SD /FO:LSL-NAS01-SHAREDUP.SHR /LOG+:LSL-NAS01-SHAREDUP.txt
For EMCOPY, you want to understand your flags before you use the command. One possible string might look like:
I can't say strongly enough that you need to test this with a subset of your data, then check your permissions and ACLs. It will greatly simply things. Thanks!
Rainer_EMC
6 Operator
•
8645 Posts
4771
0
Posted June 17th, 2013 03:00
See https://community.emc.com/message/614865#614865