HyperBDR Documentation

website·Indexed 32 days ago

https://docs.oneprocloud.com

User guides and technical documentation for HyperBDR, focusing on disaster recovery (DR) setup, failback procedures, and platform pre-settings for cloud environments including Huawei Cloud, Azure, Alibaba Cloud, Oracle Cloud, OpenStack, and VMware. Includes the HyperBDR 5.6.x - 5.11.x Upgrade Guide, Linux Kernel Support Matrix, and administrative portal configurations for MFA and WebHooks.

Tokens
240K
Snippets
463
Records
1.7K
Agent score
53%

What's inside HyperBDR

  1. Overview of Migration Policy Settings

    The Policy Settings module allows for the central configuration of control policies for migration processes. There are three primary policy types:

    • Sync Policy: Defines the frequency and method of data synchronization.
    • Speed Limit Policy: Controls network or IO usage during synchronization to manage bandwidth.
    • Retention Policy: Sets the snapshot or replica retention period and count to optimize storage and ensure recovery.
  2. Overview of HyperMotion & HyperBDR Disaster Recovery

    HyperMotion & HyperBDR is a cloud-native disaster recovery solution designed for the seamless movement of x86 host resources across diverse platforms. It supports one-click disaster recovery from physical machines, virtualization, hyper-converged platforms, and private/public clouds to destinations including public clouds, private clouds, or VMware. The solution provides minute-level Recovery Point Objective (RPO) and Recovery Time Objective (RTO) capabilities.

    Key cloud-native architectural features include:

    • Deep integration with cloud platform interfaces using over 50 APIs.
    • Use of cloud-native storage (block storage snapshots and object storage) and 'Boot in Cloud' technology for cost-effective, rapid recovery.
    • Direct data transmission from the source end to cloud storage, eliminating the need for local caching.
  3. Overview of Disaster Recovery (DR) and Failback

    OneProCloud provides two primary strategies for business continuity management:

    • DR (Disaster Recovery): Used when the source host fails or becomes unavailable. It allows for a quick switch of business operations to a standby platform to ensure data safety and continuity.
    • Failback: Used after a DR event is resolved to smoothly migrate business operations back from the standby platform to the original source platform.
  4. Overview of DR Policy Types

    The policy settings module allows for the central management of control policies for Disaster Recovery (DR) processes. There are three primary policy types:

    • Sync Policy: Defines the frequency and method of data synchronization.
    • Speed Limit Policy: Controls network or IO usage during synchronization to manage bandwidth.
    • Retention Policy: Sets the snapshot or replica retention period and count to optimize storage and ensure recovery requirements are met.
  5. Overview of HyperBDR AWS Agentless Model

    HyperBDR version 5.6.0 and above utilizes the AWS EBS Direct API to perform agentless incremental data synchronization. This model eliminates the need for installing agents on production EC2 instances by interacting directly with EBS snapshots. Key capabilities include:

    • Creating and reading/writing data directly to EBS snapshots.
    • Identifying incremental changes between two snapshots without creating new volumes or deploying additional EC2 instances for comparison.
    • Reducing operational costs and complexity for backup and disaster recovery workflows.
  6. Introduction to HyperBDR Cloud-Native Backup and Disaster Recovery

    HyperBDR is a cloud-native backup and disaster recovery platform designed to manage the full lifecycle of data protection and business orchestration. It provides tools for daily system inspections, monitoring via dashboards, regular disaster recovery drills, and rapid failover to ensure business continuity in production environments.
  7. Overview of HyperBDR Disaster Recovery Failback

    Disaster recovery failback is the process of switching business systems from a disaster recovery environment back to the original production environment after a DR takeover. HyperBDR uses block-level full and incremental synchronization to ensure data integrity and minimize downtime during the transition.
  8. Overview of OneProCloud System Architecture

    OneProCloud utilizes a modular architecture designed to handle the end-to-end lifecycle of data—including collection, transmission, storage, and management—from a production site to a target site. This architecture is built to support business scenarios such as data migration and disaster recovery, while providing unified scheduling and visualized operations and maintenance (O&M) capabilities.
  9. Overview of VuePress theme-hope layout components

    The VuePress theme-hope layout consists of global elements and page-specific components that can be customized via theme options and page frontmatter.

    Global Layout Elements:

    • Navbar
    • Sidebar
    • Footer

    Page-Specific Elements:

    • Breadcrumbs
    • Page Title and information
    • Table of Contents (TOC)
    • Meta information (update time and contributors)
    • Comments section

    Interface Elements:

    • Dark Mode toggle button
    • Back to top button
    • Print button
  10. Overview of Markdown enhancements in VuePress Theme Hope

    VuePress generates pages from Markdown files using markdown-it. Theme Hope extends this functionality through two primary layers: standard VuePress enhancements and additional theme-specific enhancements provided by the vuepress-plugin-md-enhance plugin. These extensions allow for richer content including interactive components, charts, and advanced layout options.
  11. Overview of Prophet Auto Host Info Collector

    Prophet is an open-source automated collection and analysis tool designed for cloud migration and disaster recovery planning. It gathers key technical metrics from source hosts (physical servers, cloud hosts, and VMware) to ensure smooth migration. Key capabilities include network host scanning via nmap, detailed information collection for VMware (via API), Linux (via Ansible), and Windows (via WMI), as well as data anonymization and technical report generation.