Storage Migration Services - missing destination volumes

Spencer Kenny 1 Reputation point
2020-12-01T10:40:40.477+00:00

Hello

I'm trying to migrate a physical 2012R2 NAS cluster to a virtual Windows 2019 Server cluster but hitting some problems with not all destination volumes displaying for me to map source data to.

The source has 7 volumes with just over 14Tb of data.

The destination is Windows Server 2019 1809 (for LTSC) two node cluster. 5 intended destination volumes are available on the cluster. Each host has 12 Core CPU and 16Gb RAM for what it's worth.

In SMS, when I scan the destination file cluster, I only see 1 volume available. I'm using an external orchestrator running Windows Server (Core) 1909. The account used to scan and access all nodes has full permissions over each.

Can somebody please give some pointers? Thank you.

Windows Server Storage
Windows Server Storage
Windows Server: A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.Storage: The hardware and software system used to retain data for subsequent retrieval.
631 questions
Windows Server Migration
Windows Server Migration
Windows Server: A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.Migration: The process of making existing applications and data work on a different computer or operating system.
408 questions
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. Mico Mi 1,921 Reputation points
    2020-12-02T08:55:54.13+00:00

    Hi,

    1. Please ensure your system, drivers, firmware and SMS are updated to the latest.
    2. Please ensure a migration account that is an administrator on the source computers and the orchestrator computer. A migration account that is an administrator on the destination computers and the orchestrator computer. The orchestrator computer must have the File and Printer Sharing (SMB-In) firewall rule enabled inbound. The source and destination computers must have the following firewall rules enabled inbound
      • File and Printer Sharing (SMB-In)
      • Netlogon Service (NP-In)
      • Windows Management Instrumentation (DCOM-In)
      • Windows Management Instrumentation (WMI-In)
    3. If the computers belong to an Active Directory Domain Services domain, they should all belong to the same forest. The destination server must also be in the same domain as the source server if you want to transfer the source's domain name to the destination when cutting over.

    And you can read the following article to check if you have configured all things right:
    https://learn.microsoft.com/en-us/windows-server/storage/storage-migration-service/overview
    Thanks for your time!
    Best Regards,
    Mico Mi

    -----------------------------

    If the Answer is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.


  2. Mico Mi 1,921 Reputation points
    2020-12-10T09:44:36.037+00:00

    Hi,
    Because all the things seem to be configured right, the research we can do is limited. If you want to know the root cause, it is suggested to go to open a case in the following link.
    https://support.microsoft.com/en-us/gp/customer-service-phone-numbers

    Best Regards,

    Mico Mi

    If the Answer is helpful, please click "Accept Answer" and upvote it.

    0 comments No comments