Windows Full System Recovery and Bare Metal Restoration with Rubrik
Overview of Windows Full System Recovery
- Definition: Full system recovery provides the ability to protect and restore an entire Windows system to either a physical host or a virtual host.
- Primary Focus: While virtual hosts are generally covered by virtualization-specific workflows, this methodology is specifically tailored for physical hosts where image-level virtualization backups are not applicable.
- Initial Setup: Protection is established by installing the Rubrik Backup Service (RBS) on the Windows host and assigning an SLA (Service Level Agreement) policy via the Rubrik interface.
Key Technical Terminology
- Bare Metal Restore (BMR) / Bare Metal Recovery: A data recovery technique used to restore a system to a host—typically physical, though sometimes virtual—that does not have a pre-installed operating system.
- Volume Group: A group of volumes categorized as a "snappable."
- Snappable: A proprietary term used to identify a specific Rubrik workflow for interacting with and protecting a specific data object.
- Host Layout: A description encompassing the links, types, and attributes of the physical disks associated with a specific host.
- Windows Pre-installation Environment (WinPE): A lightweight version of Windows used for the deployment of PCs, workstations, and servers, or for troubleshooting an operating system while it is offline. It provides a target for the Rubrik cluster to mount shares during recovery.
Use Cases and Deployment Scenarios
- Physical to Virtual (P2V): Restoring data from a physical source host to a virtual target machine when physical hardware is unavailable.
- Physical to Physical (P2P): The standard restoration path for maintaining physical hardware deployments.
- Raw Device Mapping (RDM): capturing volumes presented via physical mode RDMs, which standard virtualization image-level backups cannot typically capture.
- Cloud Integration and Migration:
- Backing up from an on-premises CDM (Cloud Data Management) and restoring to an Azure environment.
- Cross-cloud restoration, such as migrating volume group backups between AWS and Azure or vice versa.
System Requirements and Configuration Constraints
- BMR Target Hardware Requirements:
- The target host must have a disk layout similar to the source host. For example, if the source has two physical disks with stretched volumes, the target must also have two physical disks.
- Virtual machine targets require an equivalent number of disks (e.g., two VMDKs for a two-disk source).
- The target and source must have like-for-like hardware, including identical CPUs and similar disk space capacities.
- Network and Connectivity:
- Communication between the Rubrik Backup Service (RBS) and the Rubrik cluster utilizes the SMB protocol.
- Port must be open to facilitate inbound SMB connections to the Rubrik cluster.
- Operating System Support:
- Supported Systems: Windows Server or newer.
- Domain Requirements: Windows Server or newer hosts must be joined to a domain. Windows Server and hosts may use either a domain user or a local host.
- File System Support:
- Supported: NTFS and ReFS volumes.
- Unsupported: FAT32.
- Encryption (BitLocker):
- Backup and restoration of BitLocker-encrypted volumes are fully supported.
- CDM cannot index the contents of BitLocker volumes, meaning individual file-level restores via Rubrik search are not possible; only complete volume restoration is available.
- Unsupported Configurations:
- Dual-boot or multi-boot systems (multiple operating systems on a single computer) are not supported.
- Dynamic simple volumes over in size are mentioned within the context of volume types.
Protection Workflow for Windows Volumes
- Execution Steps:
- Log in to the Rubrik Security Cloud (RSC) UI.
- Navigate to "Windows Volumes."
- Select the specific host for protection.
- Select "Manage Protection."
- Volume Selection: Users may choose specific volumes to protect. Volumes containing data with dedicated Rubrik workflows (e.g., SQL Server files or Oracle database files) should be excluded from the volume group backup to avoid conflict with their specific protection workflows.
- Backup Format: Protected volume groups are stored as VHDX (virtual disk) files.
- Backup Resumability: Volume backup resumability is built-in to handle internal failures (e.g., service restarts) or external failures (e.g., network outages). The backup process will hang indefinitely until the connection or service is resumed, preventing total job failure.
Volume Filter Driver (VFD)
- Purpose: A utility designed to track changes in individual blocks of a volume to improve the performance of incremental backups.
- Mechanism: The VFD provides a bitmap of changed blocks to the CDM, allowing for faster transfer speeds by eliminating the need for CDM to perform a full scan before each incremental backup.
- Installation:
- Installation is optional but recommended for performance.
- It can be deployed to multiple hosts simultaneously via the Rubrik Security Cloud.
- Installing or uninstalling the VFD requires a mandatory system reboot.
Restoration Methodology Options
There are three primary options for restoring volume group backups:
Option 1: Live Mount to Host with RBS
- Requirement: Target host must have a Windows OS and the Rubrik Backup Service (RBS) installed.
- Process: Rubrik presents an SMB share to the host and creates a mount point.
- Default Path: Mounted volumes appear at
C:\RubrikMountson the target host. - Usage: Allows for browsing and accessing the contents of the restored volume immediately.
Option 2: Live Mount to Host without RBS
- Requirement: Target host has Windows OS but lacks RBS.
- Process: Select the "No Host" option in the wizard. A client IP address must be provided.
- Access: The SMB path is retrieved from the Live Mount section of the Rubrik UI.
- Data Migration: The utility
volumedatacopy.exe(downloaded from the Rubrik support portal) is used to copy data from the attached virtual disks (SMB share) to the target host disks.
Option 3: Bare Metal Recovery (BMR)
- Requirement: Target host (physical or virtual) has no operating system.
- WinPE ISO Preparation:
- The Windows Pre-installation Environment ISO must be created in advance.
- Creation Requirements: A server running Windows Server or higher, the Windows Assessment and Deployment Kit (ADK) installed, and PowerShell version or above.
- The ISO must be accessible via network boot, USB drive, or datastore (for VMs).
- Restoration Steps:
- Boot the target host into the WinPE environment.
- Select the snapshot and the "No Host" option in the Rubrik UI.
- Provide the client IP of the WinPE target and obtain the SMB share path.
- Launch PowerShell within the WinPE environment.
- Execute PowerShell scripts/commands (as detailed in Rubrik Knowledge Base documentation) to migrate data from the SMB share to the physical or virtual drives.
- Perform a full restore of the Windows host environment.