Shulou(Shulou.com)06/03 Report--

Windows Server 2019 will be officially released by GA at the end of September. At present, foreign countries are holding technical meetings related to Server 2019 in full swing, but Microsoft China has not been able to promote its own enterprise products in China for several years. It is a pity that when Microsoft enterprise products Windows Server and System Center,Sharepoint,Exchange,Hyper-V were also popular in the Chinese market for a while. But now it is rare to see Microsoft enterprise products at domestic technical meetings. If it goes on like this, I am afraid that Microsoft's original enterprise market in China will be occupied by other manufacturers. I feel sorry that at the same time, as an old Microsoft technology enthusiast, I don't want to see Microsoft's enterprise decline in China, so Lao Wang will continue my hobby, studying Microsoft's high availability, private cloud and hybrid cloud. Sharepoint products and bring the latest technology to China through blogs as much as possible

In this article, Lao Wang introduces another new feature of 2019, Storage Migration Service, English Storage Migration Service, which briefly summarizes this function: to help complete the migration of file servers from the old version of Linux/NAS/SAN/ Windows Server to Windows Server 2019 or Azure, providing automatic migration conversion management, migration process visualization, migration records can be traced back.

Before the storage migration service, Microsoft actually had a lot of file server migration tools. FSMT,WSMT,Permcopy, what is the difference between the storage migration service and the previous products? one difference is that the original product is generally Tool, while the storage migration service Microsoft calls it a difference between Service,Service and tool. Service has a better interactive experience than tool, and Service usually includes pre-and post-processing. Service can usually operate on an instance basis, and each instance of operation can be backtracked or referenced.

The storage migration service does do this. In the storage migration service, every time we perform a storage migration, we will first create a migration job in WAC. Each migration job includes three processes of inventory, transfer and conversion of the migration. When the migration ends, you can view the overall report of the migration job, and each migration job will be retained to facilitate audit. Or the administrator refers to the previous procedure.

Store the working components of the migration service

Storage Migration Service Orchestrator:Server 2019 function for orchestration control and job management of storage migration service

Storage Migration Service Proxy:Server 2019 feature, which is installed on the target Server2019 server and controlled by the Orchestrator node

Windows Admin Center: complete the visual operation of storage migration service through Web graphical interface

In this experimental environment, we install Orchestrator in proxy on the same node. In the actual enterprise environment, it is recommended to install a separate server for the Orchestrator node. If Orchestrator and proxy are on the same node, it is theoretically feasible, but when the migration is carried out in the last step of the conversion, and the target node restarts, you will not be able to see the progress of storage migration service through WAC connection to Orachestrator, so the enterprise environment Orchestrator is better to install a separate server. Manage all migration jobs in the environment to the target Server 2019

Take a closer look at the steps of the migration job

Inventory: the administrator selects the node to migrate, WAC connects to the Storage Migration Service Orchestrator scan source node storage, network, security, SMB sharing settings and data to be migrated

Transfer: the administrator pairs the data to be migrated in the inventory with the target node to complete the file transfer.

Translation: the administrator is configured to map the source hostname source network card to the target node, and then the Storage Migration Service Orchestrator automatically maps to the new node. The user accesses the new node using the original name and address, and the original node is offline by changing the name and address.

Storage migration service prerequisites

Orchestrator node and Proxy node must be Windows Server 2019 17744 or above

Windows Admin Center must be updated to the latest version to ensure that the downloaded storage migration service is extended to version 17744

All computers have joined the domain

Provide a migration account that is the administrator of the selected source computer

Provide a migration account that is the administrator on the selected target computer

The following firewall rule INBOUND must be enabled on the source and destination * computers:

File and Printer sharing (SMB-In)

Netlogon Services (NP-In)

Windows Management Specification (DCOM-In)

"Windows Management Instrumentation (WMI-In)"

* Windows Server 2019 with proxy installed will automatically open and close the correct firewall port during migration

7. When downloading the report, the firewall rule INBOUND: file and Printer sharing (SMB-In) must be enabled on the Orchestrator computer

Storage Migration Service support

Orchestrator and Proxy components support installation in Server 2019 Standard Edition, data Center Edition, support for virtual machines, physical machines, any cloud platform

Windows components are supported to be installed in Windows 10, Windows Server 2016 and Windows Admin Center Server 2019

Source nodes supported by the current version

Windows Server 2003

Windows Server 2008

Windows Server 2008 R2

Windows Server 2012

Windows Server 2012 R2

Windows Server 2016

Windows Server 2019 Preview

As you can see, Microsoft has not yet realized his proposed plan. Linux/NAS/SAN has not yet been implemented in the source list. At present, it can only support the migration from the old version of Windows Server to the new version of Windows Server 2019. A major purpose is to help users complete the migration from 2008/R2 to 2019. 2008/R2 support will end in January 2020. At that time, Microsoft will not provide updates and formal support for 2008/R2. This is a dangerous destabilizing factor for enterprise users, so considering that some enterprises will complete the migration of 2008/R2 within these two years, it is not necessary to migrate to Server 2012R2 / 2016. You can learn the difference of each version from the official website and choose the one that is most suitable for enterprises. Microsoft has claimed that the storage migration service supports 2012R2/2016/2019/Azure, but when Lao Wang writes this article, he only supports the target migration to Server 2019. I have not seen any documents about how 2012R2/2016 is the target proxy of the storage migration service. At the same time, the current version has not been connected with Azure. Lao Wang guessed that the storage migration service should connect with Azure in the future. If users want to migrate 2008/R2 directly to Azure There is currently a free tool Azure migrate available at the virtual machine migration level.

Above we discussed the workflow of storage migration service, some friends may think it is a new form, let's further understand it through experiments.

Environment introduction

08DC 10.0.0.2

FileSrv 10.0.0.18 2008R2 File Server

19WAC 10.0.0.66 2019WAC Server

19FileServer 10.0.0.51 2019 Storage Migration Service Orchestrator node and Proxy node

The current 2008R2 file server has four shares

Permissions are set separately for doc shares.

Update WAC to the latest version, download and install storage migration extension 17744 online

For the 19FileServer installation function, the Orchestrator node needs to install Storage Migration Service,Storage Migration Service Proxy,Storage Migration Service tools (install Storage Migration Service automatic installation), the function installation can use the service manager, WAC,Powershell, if the target node is installed separately, only install Storage Migration Service Proxy.

Ensure that WAC settings-recommendations-New features Windows Storage Migration Service check Yes

Open WAC and connect to the coordinator node. If the operating system version and WAC extension version are installed correctly, you can see the storage migration service in the left toolbar.

Click to create a new job to name the migration process

Click OK to complete the job establishment, and then proceed to the first step of the migration job, inventory, Microsoft China to translate into inventory, I do not think it is very appropriate, this step should be similar to inventory, inventory, inventory

The first step of stocktaking is to enter the source user name and source password. This user needs local administrator permission for the source Windows device. Job Setting chooses whether to include the administrator share of the device, which is usually unchecked.

Click next to add devices, and you can add multiple source devices. All source devices will share the above source user name and password to perform sharing and configuration collection operations.

Click start scanning after the addition is completed, and the coordinator node will use the source user to obtain the source node's sharing, configuration, network card settings and other information. The scanning ends to display the collected information and prompt whether it can be migrated. At this point, the inventory step is over.

Click next to proceed to the second step of transfer, and enter the local administrator credentials of the target Windows device

For source-destination sharing, the disk volume is configured for mapping. This step only includes the mapping between the share and the volume, not the mapping between the network card and the machine name.

Click next to set the transfer settings and pre-set the problems that may occur during the transfer process.

Next, transfer review, click verify, and connect the coordinator node to the source and destination nodes to evaluate whether the file transfer process can proceed normally.

Click the blue word "pass" at the bottom of the verification to see the evaluation items for this transmission.

After confirmation, the next step is to see the transfer interface. Click to start the transfer, and the coordinator node will coordinate the migration from the source node to the target node according to the configuration. File data + file attributes + permission settings will complete the migration in this step. This interface is refreshed in real time. The current migration speed is equivalent to the performance of single-thread Robocopy. The GA version may be improved. The administrator can provide the following details, SMB details. Check the granularity status of the transfer process. When the migration is over, you can download the transfer log in the details.

Click next at the end of the transfer to proceed to the conversion step, configure the conversion credentials, and still have the local administrator permission account for the target node.

Configure the network card mapping setting to automatically map the IP of the source node to the target node network card. After mapping to the target node, you can specify manually what address the source node IP should use, or check to use DHCP. The source machine name will also be automatically mapped to the target node, and the source node machine name can be set to random or custom.

Configure the direct conversion timeout (in minutes), which is usually kept by default

Perform a conversion check and click verify, which will verify whether the conversion configuration is ready and whether the transformation mapping can be completed normally.

Next, enter the final conversion interface. When ready, click start conversion. The storage migration service will coordinate the conversion of the source node to the target node, and automatically configure the translation mapping of the IP/ machine name. During this period, both the source node and the target node will be restarted many times, and the administrator does not need to participate in this process manually. If the coordinator node is on the same node as the target node, when the target node restarts This step will not be able to view the progress of the migration, and a separate installation of the coordinator node will see the whole process, ending with the login of the domain user before the migration after the target node is restarted.

The migration job is declared to be finished after the conversion is completed, and the administrator can trace the migration process in the coordinator node storage migration service interface through WAC.

After the migration, the source node is set to DHCP IP, and the machine name is random.

The destination node is set to the source node IP and the machine name is set to the source node name

Users use the same name to access the share

Normal migration of share permissions and NTFS permissions

Migration effect: after Lao Wang measured NTFS permissions + sharing permissions can be migrated normally, the parent directory subdirectory timestamp can be migrated normally, the file timestamp in the directory cannot be migrated, the encryption attribute cannot be migrated normally, and the effect is not as good as Permcopy+Robocopy, but in terms of step interaction, it is better than FSMT,WSMT with the same effect, which automatically helps us to complete some things that need to be operated manually before, which is a brand-new mode. But at present, in addition to the interaction of the migration process, automatic switching, consistency, and traceability, there are no great benefits compared with FSMT,WSMT. If you can successfully support migration from devices such as linux/nas and integrate with Azure file in the future, it will be much better than several other tools.

Suggestion: Microsoft has given the route planning of storage migration service, network scope and AD source computer scanning inventory, Samba,NAS, San source support, NFS for Windows and Linux, block replication transfer rather than file-level transfer, NDMP support, hot and cold data detection on the source allows the discharge of untouched old files, Azure file synchronization and Azure migration integration, in Lao Wang's view, such a plan is very good, if it can be realized. That will be a very practical and powerful tool. In addition, Lao Wang also suggests increasing migration performance to show advantages. It is best to integrate DFSN, for example, to complete the mapping and migration of the entire 2008R2DFSN from root target to link, and to be able to directly add newly migrated shares to DFSN. At present, the report of storing the migration job is still in the form of text, and it would be better if you can provide a graphical report.

Storage migration service, system insight and Cluster Set are the three new functions that Lao Wang thinks are the most important for enterprise data center management in 2019, and they are also new features that I think are more practical, so I write them in the hope that more technical people will know and those who hope to see will gain something.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.