Servers - How do you approach data transfer from old to new?

[BadBoy House]

Hi guys.

Just wanted some opinions on a couple of server setup points:

1. When setting up a new server from scratch for a client (not a migration), on installation day how do you approach the transfer of their data from the old server?

Say if the client has 100GB of data in a shared folder, do you tell them to not make any changes and then start copying it to an external drive or do you have a different method?

When I'm on-site doing something like this I like to be as efficient as possible with my time. i.e. start one process going (like transferring their shared data) and then doing something else at the same time.

2. When it comes to Outlook data I normally ensure all workstations are logged on to the old server/domain, and then doing a straight Outlook PST backup to the C: drive. Then when the workstation is connected to the new server/domain I just import it back into Outlook.

 

[TAPtech]

Migrate the data after business hours. Maybe you can setup remote access and start the transfer later at night.

 

[drjones]

First, yes, I'd do off-hours in case something goes wrong and to ensure people aren't making any changes.

Next, it might not be a bad idea to do a fresh backup with whatever backup system they use and restore from that backup to the new server; this way, you test the integrity of the backup and also get an idea how long it would take to restore.

I did that recently when I had to setup a new workstation for a client; rather than copy the data over USB, I restored it from GFI...discovered it is SLOW to restore....

 

[HankArnold]

Robocopy

I used Robocopy. I ran it during the day and then migrated it to the new server. Once everything was running, I scheduled an off-hour period where access to the server (other than the console) was turned off. Ran another Robocopy to get the new and modified files. Final migration, turn access back on and turn off access to old server.

I then removed the old server from the domain and added an alias in DNS to point to the new server. This was to cover folks who ignored the instructions on how to access the nes server.

 

[YeOldeStonecat]

Varies...based on how much data, what kind of data, when I'm there.
Typically lots of this is done outside of production hours for larger offices...and if I'm working remotely, I'll be copying across the LAN.

Sometimes when I'm onsite I'm also employing some external USB drives...but I guess more often than not I'm doing copies across the LAN.

I usually have Outlook to Exchange Server..so that's easy....but for the few people that do have POP I'll setup Outlook in their new profile and then just import their old PST from their prior profile....also while in old profile dig up favorites, desktop stuff. My Docs are usually redirected to the server anyways.

 

[BadBoy House]

Totally forgot about Robocopy. Deffinitely the way to go. Initial backup in advance to capture the bulk of the data then another robocopy the night before.

Cheers.

 

[marley1]

If I plan accordingly I like to put an external in the week of install. Do a backup of folders with sync back. Pull it and bring back to office. Then when install day happens either so another sync to external or to server. Shouldn't take long.

Outlook usually export and import

 

[HankArnold]

I used Robocopy. I ran it during the day and then migrated it to the new server. Once everything was running, I scheduled an off-hour period where access to the server (other than the console) was turned off. Ran another Robocopy to get the new and modified files. Final migration, turn access back on and turn off access to old server.

I then removed the old server from the domain and added an alias in DNS to point to the new server. This was to cover folks who ignored the instructions on how to access the nes server.

I should clarify that this is an easy transition if you are moving between servers on the same domain. Last year we migrated the majority of our servers (including a file server) to a vendor's cloud. We found that file and folder migration worked well, but things like security settings did not. I believe it was due to different SIDs for the user accounts. The vendor ended up writing some PowerScript batch files to export and map accounts and import the security settings.

 

[pceinc]

For server to server migration we use Microsoft File Server Migration Toolkit. Not sure if you can migrate from a workstation share or not. Worth a test.

 

[Nerm]

Another vote for robocopy for file transfers between servers.