Ransomware attackers specifically target and attempt to destroy backup systems to increase the probability of payment. Hardening your system is critical. Please ensure you have reviewed your platform security using the Security Hardening Checklist
Cohesity

COHESITY Documentation

Explore our documentation to get started, discover products & new features, access troubleshooting guides, register sources, platforms support.

Products
Data Security Alliance
Visit Cohesity.com
Demos
Support
Blogs
Developers
Partner Portals
Cohesity Community
© 2026 Cohesity, Inc. All Rights Reserved.
Terms of Use|
Privacy Policy|
Legal|
  1. Home
  2. NetBackup™ Release Notes
  3. Operational notes
  4. NetBackup Bare Metal Restore operational notes
  5. Mirrored dynamic volume may not receive a drive letter after Windows BMR DDR restore
NetBackup™ Release Notes

Mirrored dynamic volume may not receive a drive letter after Windows BMR DDR restore

In Windows Bare Metal Restore (BMR) environments that use Dissimilar Disk Restore (DDR), mirrored (RAID‑1) dynamic volumes may not automatically receive a drive letter after the restore. This behavior is expected due to the way Windows Disk Management and DDR handle dynamic disks during disk reconstruction and system startup.

Cause

During a BMR DDR restore, disk and volume reconstruction is prioritized over drive‑letter assignment. The BMR process focuses on restoring the disk layout, partition structure, and dynamic disk metadata. Drive letters for non‑system volumes are not guaranteed to be reassigned during this stage.

After the restore, mirrored dynamic volumes may appear in the following states:

  • Resynching

  • Degraded

  • Healthy (no drive letter assigned)

Windows may delay drive‑letter assignment until the dynamic mirror is fully recognized and stabilized. Additionally, if the original drive letter is already reserved, temporarily assigned, or conflicting with another volume during boot, Windows may withhold letter assignment to avoid collision.

In DDR scenarios that involve dissimilar hardware, changed disk order, or other mapping differences, only the system volume (C:) is guaranteed to be auto‑mapped. Other volumes may be restored successfully but remain unmounted. In Disk Management, the mirrored volume typically appears as:

  • Healthy

  • Dynamic

  • No drive letter

The volume is accessible but not mounted, and applications may fail until a drive letter is manually assigned.

Workaround

After the system boots, manually assign the drive letter using Windows Disk Management:

  1. Open Disk Management.

  2. Right‑click the mirrored volume.

  3. Select Change Drive Letter and Paths.

  4. Assign the desired drive letter.

After the letter is assigned, the volume becomes fully functional. No rebuild, reformat, or additional restore operation is required.

Feedback

Was this page helpful?
Previous

NetBackup Bare Metal Restore on AWS hangs when restoring a Windows 2025 client

Next

BMR Restore Failure for ReFS Volumes on Windows (2016 - 2025)

Feedback

Was this page helpful?