Contents Menu Expand Light mode Dark mode Auto light/dark, in light mode Auto light/dark, in dark mode Skip to content
Arcserve Console Release Notes 1.0 documentation
Logo
Arcserve Console Release Notes 1.0 documentation
  • Legal Notice
  • Contact Arcserve Support
  • Overview
  • Features
    • New Features and Enhancements (July, 2026)
    • Enhancements (January, 2026)
    • New Features and Enhancements (November, 2025)
    • New Features and Enhancements (July, 2025)
    • New Features and Enhancements (April, 2025)
    • New Features and Enhancements (October, 2024)
    • Enhancements (November, 2023)
    • Enhancements (August, 2023)
    • New Features and Enhancements (June, 2023)
    • New Features and Enhancements (January, 2023)
  • Platform Support
  • Issues Fixed
  • Known Issues
    • Arcserve Cyber Resilient Storage Account Related
    • Arcserve Cyber Resilient Data Store Related
      • Read-Only Data Store Related
    • Arcserve Cloud Cyber Resilient Data Store Related
    • Backup Related
    • Console Related
    • DR Related
    • Instant Virtual Machine Related
    • Metadata Synchronization Related
    • Proxmox Related
    • RMAN Related
    • Virtual Standby Related
  • Limitations
    • Assured Security - Malware Scan Related
    • Assured Security - AI Anomaly Detection Related
    • Arcserve Cyber Resilient Storage Account Related
    • Arcserve Cloud Cyber Resilient Data Store Related
    • Console Related
    • Data Store Related
    • DR Runbook Related
    • Gateway Related
    • Instant VM Related
    • License Related
    • Nutanix Related
    • Proxmox Related
    • Restore Related
    • RMAN Related
    • UDP Related
  • Language Support
  • Periodic Maintenance
Back to top
View this page

DR Related¶

After a block-level DRaaS restore, Windows marks disks that were previously configured as Dynamic Disks (Logical Disk Manager, LDM) as Invalid¶

After a DRaaS block-level restore, Windows marks disks that were previously configured as Dynamic (LDM) as invalid. This happens due to disk metadata misalignment after restore.

To prevent this, the system automatically converts supported Dynamic disks to Basic disks during the EC2 Prepare Phase. This ensures the restored VM can boot successfully and data remains accessible without user intervention.

Solution

No action is required from the user; the DRaaS proxy performs the conversion automatically. This step is required to realign disk structures and make volumes accessible to Windows.

Important! After the conversion, volume labels may change. Verify the updated labels before performing any post-recovery operations, as they may no longer match the original configuration.

The following table outlines the supported and unsupported configurations for automatic Dynamic-to-Basic disk conversion during recovery.

Disk type

Partition style

Volume type

Conversion Support

Dynamic

GPT

Simple (single partition per volume)

Yes

Dynamic

MBR

Simple (single partition per volume)

Yes

Dynamic

GPT

Spanned / Striped / Mirrored

No; conversion skipped

Dynamic

MBR

More than 4 volumes

No; exceeds MBR primary partition limit

Basic

Any

Any

No action taken

Next
Instant Virtual Machine Related
Previous
Console Related
Copyright © 2026, Arcserve
Made with Sphinx and @pradyunsg's Furo
On this page
  • DR Related
    • After a block-level DRaaS restore, Windows marks disks that were previously configured as Dynamic Disks (Logical Disk Manager, LDM) as Invalid