Data Health
The Data Health Check dashboard instantly highlights data and integration issues, helping you spot, troubleshoot and resolve problems before they derail your migration. Healthy data is the bedrock of accurate cost models and reliable planning.
Overview
The Data Health Check page provides an up-to-the-minute view of the health of key dependencies that Dr Migrate relies on. It helps you quickly identify issues and rerun health checks once you believe they are resolved. Use this page regularly to ensure your underlying data sources remain healthy.
Dashboard Components
Summary Health Metrics
The dashboard displays five summary cards that provide a high-level overview of different health aspects:
Health Check Navigator
The Health Check Navigator allows you to drill down into specific areas of the health check. Use the tabs to navigate between different health check categories and view detailed information about each component.
Navigator Tabs
The navigator provides access to the following health check categories. Click each tab to view status details and troubleshooting guidance for that component:
- Azure Migrate Project - Validates connectivity and data transfer from Azure Migrate to Dr Migrate
- Service Principal - Ensures appropriate permissions and access to APIs
- Power BI - Confirms Power BI data sources and reports functionality
- Data Collection - Verifies server performance and network data collection
- Servers - Tracks server-related health checks
- Server Discovery Errors - Shows detailed error information for server discovery issues
Using the Dashboard Effectively
- Run the Health Check regularly to ensure your environment and integrations remain healthy. Ideally do this before starting any new assessment or after making configuration changes.
- Review Summary Metrics on the landing page to spot any failed or degraded components. Red or amber indicators should be addressed before moving on.
- Drill into Tabs using the Health Check Navigator to identify root causes and follow the troubleshooting steps provided for each category.
- Re-run Checks after remediation to confirm the issues have been resolved. A fully green dashboard signals that your environment is ready for planning.
Health Check Categories
Azure Migrate Project
The Azure Migrate Project section displays detailed information about your connected Azure Migrate project and its health status.
Project Selection
Use the Project dropdown to select which Azure Migrate project you want to monitor. The system will display health information specific to the selected project.
Project Information
The project information table displays key details about your selected Azure Migrate project:
| Field | Description |
|---|---|
| Project Name | The name of your Azure Migrate project |
| Endpoint Type | Whether the project uses public or private endpoints |
| Subscription Id | The Azure subscription ID where the project is located |
| Subscription Name | The name of the Azure subscription |
| Resource Group | The Azure resource group containing the project |
| Public Network Access | Whether public network access is enabled or disabled |
Advanced Project Information
The Advanced Information panel provides detailed insights into your Azure Migrate deployment, appliances, and network dependency mapping. This comprehensive view helps you troubleshoot issues and optimize your migration assessment setup.
Azure Migrate Appliance Information
The Azure Migrate Appliance Information section displays detailed information about all Azure Migrate appliances connected to your environment.
Appliance Details Table
The appliance information table shows key details about each appliance:
| Column | Description |
|---|---|
| Appliance Name | The name identifier for the appliance |
| Appliance Type | The type of appliance (e.g., Microsoft.OffAzure/vmwareSites) |
| Machines Attached | Number of machines currently connected to the appliance |
| Location | Azure region where the appliance is deployed |
| Provisioning State | Current deployment status of the appliance |
| Last Heart Beat | Timestamp of the last successful communication from the appliance |
Understanding Appliance Status
- Machines Attached: Shows how many servers are being discovered by each appliance
- Provisioning State: Should show “Succeeded” for healthy appliances
- Last Heart Beat: Indicates when the appliance last communicated with Azure Migrate
- Empty Heart Beat: May indicate connectivity issues or appliance problems
Azure Migrate Projects
The Azure Migrate Projects section displays information about all Azure Migrate assessment projects in your environment.
Project Management
Use the search functionality to find specific projects and manage your Azure Migrate deployment:
- Search: Filter projects by name, subscription, or resource group
- Add Azure Migrate Project: Connect new Azure Migrate projects to Dr Migrate
- Reload: Refresh project data and status information
Project Information Table
| Column | Description |
|---|---|
| Subscription ID | Azure subscription identifier where the project is located |
| Resource Group | Azure resource group containing the project |
| Azure Migrate Assessment Project Name | The name of your Azure Migrate project |
| Last Modified | When the project was last updated |
Project Status Indicators
- Active Projects: Show current assessment projects
- Last Modified: Indicates recent activity or configuration changes
- Resource Group: Shows the Azure resource organization
Network Dependency Mapping Status
The Network Dependency Mapping Status section provides an overview of how well your appliances are performing network dependency mapping.
Dependency Mapping Overview
This section shows the status of network dependency mapping across your appliances:
| Column | Description |
|---|---|
| Appliance Name | The appliance performing the dependency mapping |
| Dependency Mapping Status | Overall success status of the mapping process |
| Machines with Errors | Number of machines that encountered errors during mapping |
Understanding the Status
- Succeeded: Dependency mapping completed successfully for the appliance
- Machines with Errors: Even with successful mapping, individual machines may have issues
- Error Count: High error counts may indicate credential or permission issues
Servers with Network Dependency Errors
The Servers with Network Dependency Errors section provides detailed information about specific errors encountered during network dependency mapping.
Error Analysis Table
| Column | Description |
|---|---|
| Appliance Name | The appliance where the error occurred |
| Error | Detailed error message describing the issue |
| Error Code | Unique identifier for the error type |
| Cause | Root cause analysis of the error |
Common Error Types
Validation Errors:
- Error: “Validation was not successful by any of the smart credential for feature DependencyMap before enabling it”
- Error Code: “ValidationNotSuccessfulBySmartCredBeforeEnablingAction”
- Cause: “None of the potential smart runasaccount is valid for machine”
Troubleshooting Steps
- Check Credentials: Verify that the appliance has valid credentials for the affected machines
- Review Permissions: Ensure the appliance has appropriate access to the machines
- Validate Accounts: Check that the run-as accounts are properly configured
- Network Access: Verify network connectivity between the appliance and target machines
Network Dependency Batch Settings
The Network Dependency Batch Settings section allows you to configure how network dependency mapping is processed across your environment.
Configuration Options
Batch Processing Settings:
-
Machines per Batch:
- Setting: “How many machines can be enabled for network dependency collection at a time”
- Default Value: 800
- Purpose: Controls the number of machines processed simultaneously
-
Processing Interval:
- Setting: “How many days between the next set of machines to process”
- Default Value: 3
- Purpose: Sets the delay between processing batches
Advanced Options:
-
Scope Limitation:
- Setting: “Enable dependency mapping for in-scope machines only”
- Status: Toggle switch (currently disabled)
- Purpose: Restricts mapping to only machines in your migration scope
-
Reset Functionality:
- Setting: “Reset dependency mapping”
- Status: Toggle switch (currently disabled)
- Purpose: Allows you to restart dependency mapping from scratch
Managing Batch Settings
- Save Changes: Click “Save” to apply configuration changes
- Close: Use “Close” to exit without saving changes
- Optimization: Adjust batch sizes based on your network capacity and appliance performance
Health Check Results
The health check results table shows specific health checks for the selected project, including:
| Column | Description |
|---|---|
| Health Check | The specific health check being performed |
| Result | The current status of the health check |
| Action | Any actions that can be taken |
| Last Updated | When the health check was last performed |
| Impact | What happens if this health check fails |
| Resolution | Steps to resolve any issues found |
Service Principal
The Service Principal checks are crucial for ensuring that the appropriate permissions and accesses are in place for the smooth functioning of Azure services. These checks verify access to APIs and the validity of secret values, which are essential for security and functionality.
| Health Check | Impact | Resolution |
|---|---|---|
| The SPN has access to the Azure EA Pricing API. | Customer-specific pricing as defined in the Enterprise agreement cannot be ingested. | Grant the Dr M SPN access to the Cost Management Reader role. |
| The SPN has contributor access to the Azure Migrate Resource Group | The Azure Migrate API cannot be called to ingest assessment data and manage data collection. | Add the Dr M SPN as a contributor to the Azure Migrate Resource Group. |
| The SPN secret value does not have the format of a GUID (ie. Secret ID) | An invalid secret value will halt key functionality including data ingestion, refresh and file management. | Generate a new SPN secret value and request an admin to update it via the SPN Update feature. |
Power BI
The Power BI health checks ensure that data sources, reports, and gateways are functioning correctly. These checks are vital for maintaining the integrity and accessibility of business intelligence data, ensuring that insights can be continuously refreshed and accessed.
| Health Check | Impact | Resolution |
|---|---|---|
| The Power BI data sources are refreshing successfully. | Insights reports cannot be refreshed with new data. | Review your Power BI tenant settings to ensure the correct configuration. Review the deployment guide. |
| The Power BI reports are refreshing successfully. | Insights reports cannot be refreshed with new data. | Review your Power BI tenant settings to ensure the correct configuration. Review the deployment guide. |
| The Power BI gateway is active and functional. | Insights reports cannot be refreshed with new data. | Review your Power BI tenant settings to ensure that the gateway is not restricted. Review the deployment guide. |
| The Power BI workspace is active and functional. | Insights reports cannot be generated or refreshed. | Review your Power BI tenant settings to ensure that the Power BI Security Group has the correct permissions. |
Data Collection
The Data Collection checks focus on verifying that all necessary data is being collected from servers for performance and network analysis. These checks ensure that right-sizing and network affinity analysis can be accurately performed, which is essential for efficient resource management.
| Health Check | Impact | Resolution |
|---|---|---|
| All servers have local admin account privileges assigned. | Server performance data cannot be obtained meaning right sizing cannot be completed for those machines | Review the Azure Migrate documentation. |
| All servers have guest operations credentials provided | Server performance data cannot be obtained meaning right sizing cannot be completed for those machines | Review the Azure Migrate documentation. |
| All servers have guest operations privileges allowed | Server performance data cannot be obtained meaning right sizing cannot be completed for those machines | Review the Azure Migrate documentation. |
| All server network data is being collected | Server software signature generation will not function. Wave planning will not be able to group based on network affinity | Review the Azure Migrate documentation. |
| All server performance data is being collected | Server performance data cannot be obtained meaning right sizing cannot be completed for those machines | Review the Azure Migrate documentation. |
| Server discovery is not blocked by a port restriction | Server performance data cannot be obtained meaning right sizing cannot be completed for those machines | Review the Azure Migrate documentation. |
Servers
The Servers panel in the Health Check Navigator helps you get a detailed view of your virtual machines’ discovery status and health. It shows important information like whether a VM is powered on, if network traffic is being detected, and if key data, such as software and SQL databases, are being discovered.
You can filter results based on operating system, power status, or other metrics to narrow down the list to specific VMs. This detailed server monitoring helps ensure that all components of your migration assessment are functioning properly and that data collection is complete across your entire estate.
Server Discovery Errors
The Server Discovery Errors tab provides a detailed view of all discovered virtual machines (VMs) with errors. It shows discovered device data and key error messages related to server health.
The tab also outlines the Possible Cause of each issue and provides Recommended Actions to resolve them, along with the Severity of each issue. This comprehensive error view helps you troubleshoot your Azure Migrate data capture to ensure that all devices are reporting correctly.
Using the Dashboard
Health Check Status Indicators
The Health Check Navigator uses color-coded status indicators to quickly communicate the health of each component:
- Green - All health checks are passing successfully
- Red - Critical health checks are failing and require immediate attention
Rerunning Health Checks
Once an issue is believed to be resolved, click the Rerun Test button. The test can take between 1-2 minutes to rerun on average. This allows you to verify that the issue has been properly resolved and that the system is functioning correctly.
Navigating Between Sections
- View Summary Metrics - Check the summary cards at the top for a quick overview
- Select Health Check Category - Click on the appropriate tab in the Health Check Navigator
- Review Project Information - In the Azure Migrate Project tab, verify your project details
- Check Health Status - Review the health check results table for any issues
- Take Action - Follow the resolution steps provided for any failed health checks
Best Practices and Troubleshooting
Best Practices for Health Monitoring
- Regular Monitoring - Check the health status regularly, especially after making configuration changes
- Immediate Resolution - Address critical (red) health issues immediately as they impact assessment functionality
- Documentation Review - Use the resolution guidance provided in each health check table
- Testing After Resolution - Always rerun health checks after implementing fixes to verify resolution
- Network Configuration - Many health issues relate to network connectivity and permissions - verify these first
Troubleshooting Common Issues
When health checks fail, start with these common areas:
- Network Connectivity - Ensure Dr Migrate can reach Azure services and your on-premises environment
- Permissions - Verify that service principals have the correct roles and access levels
- Credentials - Check that all required credentials are valid and not expired
- Configuration - Confirm that Azure Migrate projects and appliances are properly configured
- Resource Status - Ensure that all required Azure resources are running and accessible