How Do I Shrink the Disk Partitions on a Source Server Running Windows?
Symptom
When you use SMS to migrate a source server running Windows, the disks on the target server should be at least the size recommended on the Source Management page. Otherwise, the migration may fail. If you have created a target server running Windows, and the disks on the target server are too small, you can shrink the source server disks to be no larger than the target server disks.
Possible Causes
For a migration to be successful, the target server disks must be at least as large as the source disks. If they are not, you need to either scale up the target server disk or shrink the source server disk. On a Windows server, you can shrink disk partitions of the source server using the Windows Disk Management tool.
Procedure
- Choose Start, enter diskmgmt.msc in the search box.
The Disk Management tool is displayed.
- Right-click the partition of the disk you want to shrink and choose Shrink Volume.
The Shrink Volume dialog box is displayed.
- Enter the amount you wish to shrink the partition by in the Enter the amount of space to shrink in MB text box.
- Click Shrink.
The new space available is displayed as unallocated space.Figure 1 Disk partition after shrink
- Log in to the management console.
- Click Service List. Under Migration, click Server Migration Service.
The SMS console is displayed.
- In the navigation pane on the left, choose Servers.
The server list is displayed.
- Locate the source server to be deleted, and in the Operation column, choose More > Delete.
You can also select the target source server and choose More > Delete in the upper left corner of the server list.
- In the displayed Delete Server dialog box, click Yes.
- Report the information about the source server to SMS again.
- If the Agent has been uninstalled from the source server, install the Agent again. For details, see Installing the Windows Agent.
- If the Agent has been installed on your source server, restart the Agent to report the source server information to SMS.
Disk Management FAQs
- Why Was a 40 GB EVS Disk Added to the Target Server During the Migration?
- Why Can't I Attach the Original System Disk Back to a Target Server?
- How Do I Resize Partitions and Disks When I Migrate a Windows Source Server?
- How Do I Shrink the Disk Partitions on a Source Server Running Windows?
- How Do I Exclude a Partition from Migration in Windows?
- How Do I Resolve Error "Target server has fewer disks than source server. Select another target server" When I Configure the Target Server?
- What Are the Requirements on Disks on a Target Server?
- How Can I Migrate a Source Server with a Large System Disk?
- How Do I Resolve Error "Some disks on the target server are smaller than those on the source server. Select another target server" When I Configure the Target Server?
- Can SMS Migrate Local Disks on a Source Server?
- Why Do I Need to Set the Target Server Disk Be at Least 1 GB Larger than the Paired Source Server GPT Disk on Alibaba Cloud?
- Why Can't I Specify Whether to Migrate a Physical Volume When I Resize Disk Partitions in Linux?
- Why Can't I Specify Whether to Migrate a Logical Volume When I Resize Disk Partitions in Linux?
- What Are the Rules for Resizing Volume Groups, Disks, and Partitions?
- How Do I Migrate a Server with a System Disk Larger Than 1 TB?
- How Do I Detach the Temporary System Disk from My Target Server and Re-attach the Original Disk?
- Why Is There Less Data on the Target Server After the Migration Than There Was on the Source Server?
- How Do I Merge Disks During a Linux Migration?
- How Do I Split a Disk During a Linux Migration?
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbotmore
