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 Runbook RelatedΒΆ

While adding a DR Runbook, the Source drop-down list in the Add Source dialog does not display sources replicated from a remote site using the Copy from remotely managed RPS protection type. Only locally managed sources are available for selection. When recovering a Windows source as a EC2 instance, the disk order and disk numbers assigned to Amazon EBS volumes may differ from the source instance and can change across reboots or recovery methods. This behavior is expected on AWS Nitro-based instances, where EBS volumes are detected in a dynamic order during system boot. As a result, disk numbers are not guaranteed to remain consistent. Do not use disk numbers as persistent identifiers. Use EBS Volume IDs or drive letters instead.

Next
Gateway Related
Previous
Data Store Related
Copyright © 2026, Arcserve
Made with Sphinx and @pradyunsg's Furo