BEFORE YOU BEGIN
Check before you begin
Bare Metal Image Backup is a separate selection from File Backup. The inspected Agent Policy template uses windows_bare for Windows and linux_bare for Linux. An image entry alone does not establish coverage of every system disk, boot partition, application consistency or boot on different hardware.
Screenshots were captured from the actual lab interface on 16 October 2026. The interface is in English; explanations follow your selected language. Resource names, dates and settings are examples; use values for your own environment.
Some lab screenshots are withheld pending privacy review. Follow the documented steps and use your own environment values.
Visual verification limit: Firefox lab control could not reliably read the current page content during this inspection; no new Bare Metal screen was captured. The shared Agent Policy image below is reused unchanged from the earlier authorized inspection and has File Backup selected; it is not evidence of Bare Metal disk selection or restore. Bare Metal steps are based on inspected source templates; the installed release, disk inventory, recovery media and end-to-end boot require separate validation. No policy/backup/restore was started.
- OS, agent/master releases and disk inventory
- Boot mode, partition layout and encryption dependencies
- Repository capacity, recovery point and access
- Isolated destination disk and boot/data acceptance plan
011. Inventory the server and disk scope
Record the Linux distribution/kernel and agent/master releases. Inventory disk serial/WWN, capacity, GPT/MBR, UEFI/BIOS, root, /boot and EFI layout. Map LVM, mdraid, multipath and separate data disks; a / mount entry alone is not full-machine scope.
Expected resultAll required disks and boot dependencies are recorded.
022. Check agent and repository access
Find the correct OS agent under Home → Policies → Agent Policy. Verify service, privileges, master/agent connectivity, TLS and repository capacity. Responsive status is a connection check only, not disk-read or image-creation acceptance. Keep encryption keys/passwords and recovery credentials out of screenshots.
Shared Agent Policy access example: File Backup was selected in the earlier real inspection. This is not a Bare Metal disk selection, image catalog or recovery screen; it illustrates agent identity and connection prechecks only.
Expected resultCorrect agent and repository prerequisites are verified.
033. Open a Bare Metal Image Backup draft
In Create Agent Policy → Attribute, select the correct Agent, a unique Policy Name and Storage. Use Policy Type → Bare Metal Image Backup; its internal source type is linux_bare. Do not substitute File Backup or a different platform’s VM policy. Do not save until source selection is complete.
Expected resultAn OS-appropriate image draft is prepared.
044. Match Clients disks by identity
Compare physical disks, model, capacity and child partition/mount lists in Clients against the inventory. The inspected Linux template filters type=disk items and summarizes selected disks. Names such as /dev/sda are order-dependent and are not sufficient identity; match boot/data disks by serial/WWN. Stop on an empty list or errors.
Expected resultDisk selection and summary match the required physical scope.
055. Define consistency and special-storage requirements
Define an approved consistency/quiesce method for changing filesystems. Assess LUKS, LVM, mdraid, multipath and special storage/controller conditions within release scope. Plan key, initramfs and bootloader dependencies; do not assume automatic LVM/RAID/encryption recovery.
Expected resultConsistency and special-storage scope are separately defined.
066. Plan retention and the first image test
Validate Advanced Settings and Schedules against the installed release; compare method, time window, data size and repository capacity. Do not infer Full/incremental support from a generic menu alone. Plan initial acceptance on an approved test server after reviewing disk scope and retention-chain requirements.
Expected resultThe test window and retention fit the image scope.
077. Accept the image through a recovery test
After an approved test, record task result, repository output, backup ID, disk scope and catalog point together. Active status is not proof of a successful image. Use the separate Bare Metal restore guide to accept disks/boot, data hashes and services on an isolated target; a running source server does not prove the image is bootable.
Expected resultCatalog records are matched with actual boot/data acceptance.
COMMON QUESTIONS
Does an image entry guarantee full-system recovery?
No. Disk/partition scope, media, drivers, encryption and destination boot/data acceptance need separate validation. Agent disk restore, ISO/Recovery and application recovery are assessed separately.