Supported Scan Targets

Platform Support Overview¶

DMC supports scanning across multiple platform types. Use the cards below to navigate to specific platform information.

Scanning Mode Best Practices¶

Understanding the Two Scan Modes¶

VMware Mode scans infrastructure via vCenter / VMware APIs and discovers VMs with their configuration and relationships. Physical Scan Mode scans machines directly at the OS / host level and treats each machine as an independent asset.

Each mode uses a different discovery mechanism and asset identity model. When you mix modes for the same machine, DMC cannot recognize them as the same asset.

Why This Matters¶

When the same machine is scanned using different modes:

• DMC treats it as two separate assets
• Duplicate or conflicting records appear in Dr Migrate
• Relationships, metrics, and lifecycle tracking break
• Reports and recommendations become inaccurate

Example: VM_1 is scanned via VMware mode from vCenter, then later scanned via Physical mode. Result: VM_1 appears twice in Dr Migrate with inconsistent data. This is not a supported configuration.

Which Mode Should I Use?¶

Pre-Scan Checklist¶

Before running any DMC scan:

First-Time Scan: - [ ] What type of infrastructure am I scanning? - [ ] Do I have vCenter access? - [ ] Which mode is appropriate? - [ ] Have I documented this decision?

Subsequent Scans: - [ ] Have I scanned this infrastructure before? - [ ] Which mode did I use previously? - [ ] Am I using the same mode now?

For Mixed Environments (VMs + Physical Servers)¶

If you have both VMware VMs and physical servers:

Do this: 1. List all vCenter-managed VMs → scan with VMware Mode 2. List all physical servers → scan with Physical Mode
3. Document which machines use which mode 4. Never scan the same machine with both modes

Do NOT: - Scan vCenter VMs with VMware Mode, then rescan with Physical Mode "to get more data" - Re-scan an already-discovered VM using a different mode - Mix modes for testing or convenience

Key Rule¶

One machine. One scan mode. Always.

If you've already mixed modes, contact support immediately for data cleanup. For questions or uncertainty, escalate before scanning, not after.

VMware Environment¶

DMC supports scanning of on-premises VMware environments.

DMC supports scanning of the below guest operating systems running on the VMware environment.

Physical Servers¶

DMC supports scanning of physical Windows and Linux servers.

Hyper-V¶

DMC supports scanning of Windows and Linux servers hosted on Hyper-V.

Nutanix¶

DMC supports scanning of Windows and Linux servers hosted on Nutanix.

SQL Server Discovery and Assessment¶

DMC supports discovery and assessment of SQL Server instances across all supported scan targets.

Supported SQL Server Versions¶

DMC supports discovery and assessment of SQL Server instances. Supported versions differ based on the operating system platform:

SQL Server on Windows:

SQL Server on Linux:

SQL Server Discovery¶

SQL Server instances are automatically discovered during infrastructure scans (VMware, Physical, Hyper-V, and Nutanix). When SQL Server is detected on scanned machines, DMC collects instance information including:

• SQL Server version and edition
• Instance names and configurations
• Database inventory
• Server properties

SQL Server Assessment¶

SQL Server assessment is a separate workflow that can be performed after infrastructure discovery. DMC assesses SQL Server instances for Azure migration readiness.

For detailed information about SQL Server assessment requirements and capabilities, see Database Assessment Requirements and SQL Assessment Metrics.

Azure¶

DMC supports scanning of Azure Virtual Machines to collect infrastructure configuration, performance metrics, software inventory, network dependencies, SQL Server instances, and Azure resource inventory.

Azure Monitor metrics are collected for all VMs regardless of OS. Guest-level data collection (software, network, database) is supported on the following operating systems:

There are two Azure scan types:

AWS¶

DMC supports discovery and assessment of Amazon Web Services environments. The collector runs from a machine inside your AWS environment and uses read-only access you create, with no agents installed and Dr Migrate never connecting in to your environment.

There are two AWS scan types:

The two scans are independent and can run from the same collector host.

Captured Metrics¶