Help Center/ Server Migration Service/ User Guide (Kuala Lumpur Region)/ FAQs/ Disk Management/ How Do I Resize Partitions and Disks When I Migrate a Windows Source Server?
Updated on 2024-03-15 GMT+08:00
View PDF
Share

How Do I Resize Partitions and Disks When I Migrate a Windows Source Server?

Scenarios

You need to manually resize partitions and disks if:

  • The system disk of a source server is larger than 1 TB.
  • A file system on the source server is not supported by SMS.
  • There are partitions that do not need to be migrated or there are other resizing requirements.

Scenario 1

The source system disk is 1.1 TB, with 100 GB allocated for the system and boot partitions and 1,024 GB for data disk D. You can prepare a 100 GB and a 1,024 GB disk on the target server for receiving data from the source system disk.

The procedure is as follows:

  1. Go to the Agent configuration directory on the source server.
    • Agent (Python 3)

      C:\SMS-Agent-Py3\config

    • Agent (Python 2)

      C:\SMS-Agent-Py2\config

  2. Modify the disk.cfg file as follows and save it. 
    [volmap]
D = 2
    • D = 2 indicates that data in disk D will be migrated to the second disk on the target server.
    • There are multiple partitions on the source server, and you want to migrate them to different disks on the target server. In this case, modify the disk.cfg file in the same way, such as D=2, E=3, F=4.
  3. Go to the SMS console, and delete the record corresponding to this source server.
  4. Restart the Agent installed on the source server. Go back to the SMS console to check whether the disk information has been changed in the source server details.

This method is not suitable for migrating system and boot partitions, because the system and boot partitions can be migrated only to the first disk on the target server.

Scenario 2

Data disk D on the source server is a FAT32 partition, which caused the source server failed the migration feasibility check. You can exclude this partition from migration using the configuration file.

The procedure is as follows:

  1. Go to the Agent configuration directory on the source server.
    • Agent (Python 3)

      C:\SMS-Agent-Py3\config

    • Agent (Python 2)

      C:\SMS-Agent-Py2\config

  2. Modify the disk.cfg file as follows and save it. 
    [volmap]
D = -1

    D = -1 indicates that disk D will not be migrated.

  3. Go to the SMS console, and delete the record corresponding to this source server.
  4. Restart the Agent. Go back to the SMS console to check whether the disk information has been changed in the source server details.

Scenario 3

The source server has two data disks, disk D and disk E. You want to migrate the two data disks to the same disk on the target server.

The procedure is as follows:

  1. Go to the Agent configuration directory on the source server.
    • Agent (Python 3)

      C:\SMS-Agent-Py3\config

    • Agent (Python 2)

      C:\SMS-Agent-Py2\config

  2. Modify the disk.cfg file as follows and save it. 
    [volmap]
E = 2

    E = 2 indicates that data in disk E will be migrated to the second disk on the target server.

  3. Go to the SMS console, and delete the record corresponding to this source server.
  4. Restart the Agent. Go back to the SMS console to check whether in the source server details, there is only one data disk which consists of partition D and partition E.
Parent topic: Disk Management