Migrating Shared Folder 2008 R2 Standard to Windows 2012 Standard

The other night I scheduled an outage for one of my old file servers (Win 2008 R2 Std.).  Reason:  Want to migrate a shared folder on that server to a new file server (Win 2012 Std).

I did this by using Windows Server Backup.  I took a full backup of the folder on the server (2008 R2 Standar) and then restored onto the new Win 2012 box.   After the restore finished, I check to make sure that the folder size match that of the source.  To my surprise the folder size did not match that of the source, nor did some of the permissions on the folders/files match that of the source.

What is the best way to migrate the folder to the new server without losing the NTF permission?  I don't care much about the sharing permissions as it is shared to everyone.

Anyone have a good simple solution?  One wouldn't think this would take a ton of knowledge to complete, but I guess I'm wrong...

Thanks for you help in advance!
tnimsAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

dipopoCommented:
Yes please migrate windows shares in this fashion:

1. Robocopy <source> <destination> /S /E /ZB /SEC /R:3 /W:2 /MON:10
2. Copy Registry entry Lanmanserver\Shares from source to destination
3. Switch FQDN/IP/DNS from old server to new

http://support.microsoft.com/kb/125996

/S :: copy Subdirectories, but not empty ones.
/E :: copy subdirectories, including Empty ones.
/ZB :: use restartable mode; if access denied use Backup mode.
/SEC :: copy files with SECurity (equivalent to /COPY:DATS).
/R:n :: number of Retries on failed copies: default 1 million.
/W:n :: Wait time between retries: default is 30 seconds.
/MON:n :: MONitor source; run again when more than n changes seen.
0
Mohammed KhawajaManager - Infrastructure:  Information TechnologyCommented:
Robocopy is the way to go. Robocopy also allows to restart copying where it left off if the copy failed, skip files in use as well as logging to ensure if there are issues.
0
tnimsAuthor Commented:
Awesome!  Thanks dipopo & mnkhawaja.

After doing some research I put together this command:

Robocopy <source> <destination> /E /ZB /DCOPY:T /COPYALL /R:60 /W:1 /V /TEE /LOG:C:\Robocopy.log

My main goal is to copy all information from the source to the destination.  Will this command suffice?

After the copy has completed, if I run the same command again, will this basically be like a incremental copy or will it take the same amount of time to complete as the initial copy?
0
Newly released Acronis True Image 2019

In announcing the release of the 15th Anniversary Edition of Acronis True Image 2019, the company revealed that its artificial intelligence-based anti-ransomware technology – stopped more than 200,000 ransomware attacks on 150,000 customers last year.

dipopoCommented:
Hi there,

To perform incremental type copies with Robocopy you only need include the /MON:n This monitors for changes and will copy changes after the stated nth time.

/MON:n :: MONitor source; run again when more than n changes seen.

Else look at the /MAXLAD

 /MAXLAD:n :: MAXimum Last Access Date - exclude files unused since n.

[This will work well for only copying new files since the stipulated last copy date, so all files that have changed since then get copied]
0
tnimsAuthor Commented:
OK so here is my next question:

when i run the following copy command:

robocopy Z:\Fileserver D:\ /E /ZB /DCOPY:T /COPYALL /MON:1 /R:60 /W:1 /V /TEE /LOG:C:\robocopy.log

I notice that robocopy doesn't actually copy the Z:\Fileserver folder from the source and copy to the D:\ directory.   What happens is robocopy only copies the contents of the Fileserver folder from the Z:\ to the D:\.  Essentially, I would like to see the Fileserver folder on the D drive (ex.  D:\Fileserver) with all data, attributes, time stamps, ACL, Owner, Audition info copied over.
0
dipopoCommented:
Then you may run:

robocopy Z:\ D:\ /E /ZB /DCOPY:T /COPYALL /MON:1 /R:60 /W:1 /V /TEE /LOG:C:\robocopy.log

Unless there are other folders at the root then run:

robocopy Z:\Fileserver D:\Fileserver /E /ZB /DCOPY:T /COPYALL /MON:1 /R:60 /W:1 /V /TEE /LOG:C:\robocopy.log
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
tnimsAuthor Commented:
Sweet!   I'll use that command and test it out.

What command should I run after this initial command to only copy the files that have changed since the last copy?
0
dipopoCommented:
robocopy Z:\Fileserver D:\Fileserver /E /ZB /DCOPY:T /COPYALL /MAXLAD:yyyymmdd /R:60 /W:1 /V /TEE /LOG:C:\robocopy.log

Although you were already monitoring and copying changes before with /MON:1 so, unless there is a time lapse between first and second where robocopy "STOPPED" then /MON:1 would have captured these changes.

Else specify /MAXLAD: as date before robocopy stopped.
0
tnimsAuthor Commented:
You all rock!

Here is the command I used to copy my file server directory to my new server:

robocopy <source> <destination> /E /Purge /ZB /DCOPY:T /COPY:DATSOU /MON:1 /EFSRAW /R:0 /W:0 /V /TEE /LOG:C:\robocopy.log

Thank you all for your help!
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2008

From novice to tech pro — start learning today.