I have recently have done this also. I just restored data the data from a Veeam Backup out of hours keeping permissions, then just re-created the shares. You can as stated before just create new server and move VMDK drives over, but we wanted fresh drives creating due to someone changing the disks to Dynamic Disks Create your folder structure with Robocopy on the new server and point the folder targets to old and new server.
Let DFS replication do it's magic. If replication is finished, remove the folder targets for the old server in DFS configuration of just disable them at first and you're done. If we moved to new share server we shall change all the folder target names to add new server name for DFS. Robocopy works very nicely.
Mirror for several days and cutover on a weekend. Use the proper switches for permissions etc as you require. Create the shares on the new box and use this to keep them in sync.. Also a fan of Robocopy, don't forget to set retries and timeouts to something sensible though and then output to log for you to check. I agree with everyone who suggested RoboCopy. I just completed a migration from an old Server R2 file server to a new Server machine. I use the following article as my guide and it made the job very easy.
To continue this discussion, please ask a new question. Get answers from your peers along with millions of IT pros who visit Spiceworks. Popular Topics in File Sharing. Spiceworks Help Desk. The help desk software for IT. Track users' IT needs, easily, and with only the features you need. Does the tool preserve the necessary file fidelity supported by your source and target locations? In some cases, your target storage doesn't support the same fidelity as your source.
If the target storage is sufficient for your needs, the tool must match only the target's file-fidelity capabilities. When a tool supports an option to mirror a source to a target, you can often run it multiple times on the same source and target while the source stays accessible. The first time you run the tool, it copies the bulk of the data. This initial run might last a while. It often lasts longer than you want for taking the data source offline for your business processes.
The run is much faster because it needs to transport only source changes that occur after the previous run. Rerunning a copy tool this way can reduce downtime significantly. The following table classifies Microsoft tools and their current suitability for Azure file shares:.
RoboCopy is one of the tools most applicable to file migrations. It comes as part of Windows. The main RoboCopy documentation is a helpful resource for this tool's many options.
Azure File Sync scales primarily with the number of items files and folders and not with the total storage amount. The TreeSize tool lets you determine the number of items on your Windows Server volumes. You can use the tool to create a perspective before an Azure File Sync deployment.
You can also use it when cloud tiering is engaged after deployment. In that scenario, you see the number of items and which directories use your server cache the most. The tested version of the tool is version 4.
It's compatible with cloud-tiered files. The tool won't cause recall of tiered files during its normal operation. Skip to main content. This browser is no longer supported. Download Microsoft Edge More info. This helps ensure any old accounts with forgotten and weak passwords on the source don't continue to be a security problem on the destination. Select Start transfer to start transferring data. The first time you transfer, we'll move any existing files in a destination to a backup folder.
For destination servers running Azure File Sync with cloud tiering, this backup option is not supported. We otherwise fully support Azure File Sync with cloud tiering and include updated transfer information details in Windows Admin Center. On subsequent transfers, by default we'll refresh the destination without backing it up first. Also, Storage Migration Service is smart enough to deal with overlapping shares—we won't copy the same folders twice in the same job. After the transfer completes, check out the destination server to make sure everything transferred properly.
Select Error log only if you want to download a log of any files that didn't transfer. If you want to keep an audit trail of transfers or are planning to perform more than one transfer in a job, click Transfer log or the other log save options to save a CSV copy.
Every subsequent transfer overwrites the database information of a previous run. If you're migrating a large number of files, you may need to adjust the timeout for saving this CSV file. If your goal is to sync the files with Azure, you could set up the destination servers with Azure File Sync after transferring files, or after cutting over to the destination servers see Planning for an Azure File Sync deployment.
In this step you cut over from the source servers to the destination servers, moving the IP addresses and computer names to the destination servers. After this step is finished, apps and users access the new servers via the names and addresses of the servers you migrated from. After migrating a server or cluster, evaluate the environment for possible post migration operations:.
Skip to main content. This browser is no longer supported. Download Microsoft Edge More info. Contents Exit focus mode. Is this page helpful?
Please rate your experience Yes No. Any additional feedback? An existing Azure Compute resource group where you have Create rights. An existing Azure Virtual Network and subnet. Note Migrated user accounts are disabled on the destination and assigned a character password that's both complex and random, so you'll have to enable them and assign a new password when you're finished to keep using them.
Note If you want to keep an audit trail of transfers or are planning to perform more than one transfer in a job, click Transfer log or the other log save options to save a CSV copy.
0コメント