OADP Virtual Machine Data Protection (VMDP) Design Implementation

Based on OADP Operator PR: #1845

Replaces Previous Designs: #1827, #1830

Overview

The Virtual Machine Data Protection (VMDP) feature introduces a OpenShift-native, client-server architecture that enables file-level backup and restore operations initiated from within OpenShift Virtual Machines. The system integrates seamlessly with OpenShift APIs and the existing OADP infrastructure, while preserving a clear separation of responsibilities between cluster administrators and VM users.

Architecture Overview

VMDP implements a client-server model where:
_ _Backup Server:* Deployed and managed by the OADP Operator using Kopia server technology
_ _VM Clients:* File-level backup operations initiated from within VMs
_ _Repository Management:* Integrated with existing OADP backup storage locations
_ _Authentication:* User-based access control with repository-level security

Key Features

File-Level Backup and Restore

• User-initiated backup operations from within VMs
• Selective file and directory backup capabilities
• Point-in-time restore functionality
• Integration with Kopia backup technology

OpenShift Native Integration

• Seamless integration with OADP infrastructure
• BackupStorageLocationServer (BSLS) CRD for configuration
• OpenShift API compatibility
• Service-based architecture within OADP namespace

Security and Access Control

• User-based authentication (username/password)
• Repository-level access control
• TLS encryption for client-server communication
• Secure credential management

Technical Implementation

BackupStorageLocationServer CRD

• New custom resource for backup server configuration
• Integration with existing DataProtectionApplication (DPA)
• Automated deployment and lifecycle management
• TLS certificate and fingerprint management

Client-Server Communication

• Kopia server deployed as part of OADP operator
• Network connectivity requirements for VM-to-backup-server communication
• Authentication flow: VM User -> [username/password] -> Backup Server -> [repo password] -> Repository

Repository Management

• Integration with existing OADP backup storage locations
• Multi-user repository access
• Backup retention and lifecycle policies
• Storage backend compatibility (S3, etc.)

Design Considerations

Prerequisites

• Internal OpenShift networking must allow VMs to connect to Backup Service in OADP namespace
• Compatible container image for backup server (official Kopia or custom OADP extended image)
• Image override capabilities via DPA configuration

User Experience

• Command-line interface for VM users
• Preflight connectivity checks for troubleshooting
• Network connectivity validation
• Service availability verification
• Performance and bandwidth checks

Administrator Controls

• Integration with DPA configuration or standalone CRD management
• Repository quota and storage cap considerations
• Monitoring and observability features

Scope and Limitations

In Scope

• File-level backup and restore from within VMs
• User-initiated backup operations
• Integration with OADP infrastructure
• Kopia server deployment and management
• OpenShift-native API integration

Out of Scope

_ _Full VM Protection:* Does not modify or replace OADP's snapshot-based backup for entire VMs
_ _Application Quiescing:* No application-level consistency mechanisms (user responsibility)
_ _Block-Level Operations:* No support for raw block devices or unmounted partitions
_ _Graphical User Interface:* No OpenShift Console integration (security and complexity considerations)
_ _Storage Quotas:* No native mechanisms for enforcing storage quotas at repository level (future enhancement)

Security Considerations

Attack Surface Reduction

• No web UI to minimize CVE impact
• Limited network exposure
• Secure authentication mechanisms
• TLS encryption for all communications

Multi-User Repository Management

• Repository-level access control
• Prevention of cross-user interference
• Secure credential isolation
• Configuration protection mechanisms

Testing Strategy

• Unit tests for VMDP components
• Integration tests with OpenShift VMs
• End-to-end backup and restore validation
• Network connectivity and security testing
• Performance benchmarking
• Multi-user scenario validation

Target Release

• Implementation target: OADP 1.6.0
• Technology Preview phase initially
• Future enhancements for storage quotas and UI integration

Benefits

• Enhanced backup capabilities for VM workloads
• User-driven backup operations without cluster admin involvement
• Seamless integration with existing OADP infrastructure
• Improved data protection for virtualized applications
• Flexible file-level restore capabilities

The Virtual Machine Data Protection (VMDP) feature implements a true Zero Trust model for VM data protection, shifting the responsibility and control of backup operations directly to the VM user.

Core Principles

• Zero Trust Architecture: The fundamental design principle is zero trust, ensuring administrators cannot restore or access the backup data. The VM user maintains complete ownership and control over the lifecycle of their data, including ownership of the data, the backup, and the encryption keys required for restoration.

• User Autonomy: The user is solely responsible for choosing what data is backed up and restored. This includes the critical capability to protect data accessible over network file systems, such as Ceph or NFS shares, which are typically excluded by standard OADP backups.

Implementation and Workflow

• Client Application: The feature provides a pre-built, statically linked OADP VMDP client. This client is a reworked version of the Copia CLI and is specifically engineered for VMDP operations.

• Client Access: The client can be easily and securely downloaded directly to the VM via an in-cluster HTTP service.

• Personal Repository: To ensure zero trust, the user must provide their own credentials to create and manage a personal, encrypted repository within the designated S3 storage backend.

• Simplified Backup: Backing up is streamlined to a single command, allowing users to protect any folders and files they can access. This includes local data and external network shares (Ceph/NFS).

• Efficiency: The client leverages Copia's deduplication technology. This ensures data is stored efficiently and subsequent backup runs, even after large file changes or copies, remain very fast as only new or changed data blocks are transmitted.

• Restoration Flexibility: Restoring files to a VM is a fast operation. The user has control over the restore location, allowing them to restore to a different folder or location, and can choose to restore from a specific, historical backup point.

• Architecture: Based on Zero Trust Architecture principles, meaning the VM user is fully responsible for backup and restore operations and owns their data and keys.

• Client: OADP provides a pre-built, statically linked VMDP client, which is a reworked version of the kopia CLI.
• Documentation: Expected to follow the style of the oadp-cli documentation.

1. Discover (Awareness and Introduction)

2. Learn (Prerequisites and Principles)

3. Try (Initial Setup and First Backup)

4. Adopt (Advanced Usage and Security)

5. Expand (Management and Maintenance)

JTBD statement

"As a VM Application Owner, I want to perform encrypt and back up all custom configurations and network share data (e.g., Ceph or NFS) using my own S3 credentials, to achieve full, independent control and ownership of my data and encryption keys, preventing administrator access or reliance for fast restoration."

Personas 
1. The Primary User (Application Owner)

This persona focuses on the core benefit of control and independence offered by the Zero Trust model.

• As a VM Application Owner, I want to perform encrypt and back up all custom configurations and critical network share data (like Ceph or NFS) using my own S3 credentials, to achieve full, independent control and ownership of my data and encryption keys, preventing administrator access or reliance for fast restoration.

2. The Efficiency-Focused User

This persona prioritizes operational speed and minimal resource usage.

• As a Production Engineer, I want to perform run subsequent data protection jobs using a single command, even after copying large amounts of files, to achieve complete my daily backups efficiently and extremely fast, leveraging deduplication so I don't waste time or storage space on redundant data.

3. The Security & Recovery Specialist

This persona focuses on the reliable, immediate, and unauthorized-access-free recovery process.

• As a Recovery Specialist, I want to perform quickly restore specific files or folders to a different location within the VM from a chosen backup point, to achieve ensure immediate business continuity and verify that files are recoverable only by authorized users, strictly adhering to Zero Trust recovery protocols.