VMs Hang During Migration Due to Third-Party Data Management Service Issues
search cancel

VMs Hang During Migration Due to Third-Party Data Management Service Issues

book

Article ID: 372007

calendar_today

Updated On:

Products

VMware

Issue/Introduction

Users may experience VMs hanging at 68% during migration on specific nodes within a cluster. This issue can significantly disrupt operations, and understanding the potential causes and resolutions is crucial for effective troubleshooting.

Environment

- VMware vSphere
- VMs hanging during migration
- ESXi host logs
- Third-Party Data Management Service (e.g., Dell EMC PowerProtect Data Manager - PPDM)

Cause

The issue is caused by complications with a third-party data management service integrated into the VMware environment. Specifically, the Dell EMC PowerProtect Data Manager (PPDM) service may interfere with VM migrations if not functioning correctly.

Resolution

To resolve the issue of VMs hanging at 68% during migration, follow these steps:

1. Verify the Third-Party Service Status (e.g., Dell EMC PPDM)
   - Access the ESXi host or the management interface of the third-party service.
   - Check the status of the data management service.
   - If the service is not running or shows errors, restart the service.

2. Generate and Review Logs
   - Collect log bundles from the affected ESXi hosts and the third-party service.
   - Ensure logs are correctly generated and not corrupt. If logs are missing or corrupt, regenerate and upload them again.

3. Check for Configuration Issues
   - Review the configuration files and settings of the third-party service for any discrepancies or errors.
   - Validate that policies and settings are correctly defined and applied.

4. Update or Patch the Third-Party Service
   - Verify that the third-party service is up-to-date with the latest patches and updates.
   - Apply any necessary updates or patches to ensure the service functions correctly.

5. Review Network and Storage Settings
   - Ensure that network and storage settings are properly configured and not contributing to the issue.
   - Verify that the affected node has the correct network and storage access required for VM migration.

6. Test Migration After Resolutions
   - Attempt to migrate a VM after applying the above steps to verify if the issue is resolved.
   - Monitor the migration process to ensure it completes successfully without hanging.

Additional Information