VMCE Veeam Backup & Replication Architecture 5 — Questions and Answers
Question 1: What is Veeam's 'Immutable Backup' feature and which repository type supports it natively in Veeam v12?
- Immutable backups cannot be modified or deleted for a set period; supported on Linux hardened repositories using immutable flag (chattr +i) and S3-compatible object storage with object lock (Correct answer)
- Immutable backups are encrypted backups that cannot be decrypted without the original key; supported on all repository types
- Immutable backups are read-only backup files; supported only on NetApp ONTAP SnapLock volumes
- Immutable backups use WORM tape media; supported only on physical tape libraries with WORM cartridges
Correct answer: Immutable backups cannot be modified or deleted for a set period; supported on Linux hardened repositories using immutable flag (chattr +i) and S3-compatible object storage with object lock
Veeam supports immutability on Linux hardened repositories (using OS-level immutable flags without root SSH access) and S3 object storage with Object Lock, protecting backups from ransomware deletion.
Question 2: In Veeam's architecture, what is a 'Hardened Repository' and what makes it secure?
- A Linux-based backup repository configured so that Veeam connects via a single-use credential with no persistent SSH access, and backup files are made immutable (Correct answer)
- A backup repository with AES-256 hardware encryption enforced at the storage controller level
- A Windows repository configured with BitLocker full-disk encryption and mandatory backup file checksums
- A backup repository isolated in a DMZ with no network access except through the Veeam Backup Server
Correct answer: A Linux-based backup repository configured so that Veeam connects via a single-use credential with no persistent SSH access, and backup files are made immutable
The hardened repository uses a Linux OS where Veeam elevates privileges only temporarily during deployment, then revokes SSH access — combined with immutable file flags, this prevents backup deletion even if credentials are compromised.
Question 3: What is Veeam's 'Capacity Tier' in a Scale-out Backup Repository used for, and which storage types are supported?
- Long-term retention of older backup data offloaded from Performance Tier extents; supports S3-compatible object storage, Azure Blob, Google Cloud Storage, and IBM Cloud Object Storage (Correct answer)
- Short-term high-speed storage for active backups; supports NVMe SSDs and SAN LUNs only
- Encrypted archival storage; supports only AWS Glacier and Azure Archive tiers
- Metadata-only storage for backup catalog indexing; supports any SMB/NFS share
Correct answer: Long-term retention of older backup data offloaded from Performance Tier extents; supports S3-compatible object storage, Azure Blob, Google Cloud Storage, and IBM Cloud Object Storage
The Capacity Tier automatically offloads older backup data from fast Performance Tier extents to cost-effective object storage, with support for major cloud and on-premises S3-compatible platforms.
Question 4: How does Veeam handle backup of VMs with large disks efficiently using 'Parallel Processing'?
- Veeam can simultaneously read multiple VM disks in parallel using separate data streams, reducing total backup time for multi-disk VMs (Correct answer)
- Veeam splits each disk into equal blocks and assigns each block to a different proxy server simultaneously
- Veeam compresses all disks in parallel on the backup server CPU before writing to the repository
- Veeam uses multiple snapshot chains simultaneously, one per disk, to capture changes in parallel
Correct answer: Veeam can simultaneously read multiple VM disks in parallel using separate data streams, reducing total backup time for multi-disk VMs
Parallel processing allows Veeam to open multiple concurrent read streams for different VM disks simultaneously, significantly reducing backup windows for VMs with many or large disks.
Question 5: In Veeam's replication architecture, what is a 'Replica Seeding' and when would you use it?
- Pre-populating a replica at the DR site using a backup transported via physical media (ship-and-seed), then synchronizing only incremental changes over WAN — used when initial full replication over WAN is impractical (Correct answer)
- Creating a replica from a backup file instead of directly from the source VM — used for VMs that cannot tolerate snapshot overhead
- Automatically replicating only seed VMs (templates) used to provision new VMs — used in VDI environments
- Scheduling replication to only run during off-peak hours using a seed schedule — used for bandwidth management
Correct answer: Pre-populating a replica at the DR site using a backup transported via physical media (ship-and-seed), then synchronizing only incremental changes over WAN — used when initial full replication over WAN is impractical
Replica seeding allows the initial large dataset to be transported physically to the DR site, after which Veeam only needs to synchronize incremental changes over the WAN link.
Question 6: What Veeam technology enables 'SureBackup' jobs to verify backup recoverability, and how does it work?
- SureBackup uses a Virtual Lab (isolated network sandbox) to automatically power on backed-up VMs from backup files and run verification scripts to confirm they boot and applications respond (Correct answer)
- SureBackup performs a byte-by-byte hash verification of backup files against the source VM disks
- SureBackup uses VMware vSphere Data Protection APIs to verify snapshot integrity without powering on VMs
- SureBackup sends backup file checksums to Veeam's cloud service for validation against known-good hashes
Correct answer: SureBackup uses a Virtual Lab (isolated network sandbox) to automatically power on backed-up VMs from backup files and run verification scripts to confirm they boot and applications respond
SureBackup starts VMs directly from backup files in an isolated Virtual Lab environment, runs VMware Tools heartbeat checks and optional custom scripts to verify each VM boots successfully and applications are functional.
Question 7: Which Veeam feature allows a backup administrator to restore a VM to any point in time between scheduled backups using journal-based recovery?
- Veeam DataLabs On-Demand Sandbox with continuous journal replay
- Veeam Explorer for Storage Snapshots with sub-job scheduling
- Veeam Continuous Data Protection (CDP) with near-zero RPO replication using VMware vSphere APIs for I/O filtering (Correct answer)
- Veeam Instant Recovery with time-slider granular point-in-time selection
Correct answer: Veeam Continuous Data Protection (CDP) with near-zero RPO replication using VMware vSphere APIs for I/O filtering
Veeam CDP uses VMware vSphere APIs for I/O Filtering (VAIO) to capture every write to VM disks in real time, enabling recovery to any second within the retention window — far beyond scheduled backup granularity.
VMCE Veeam Backup & Replication Architecture 5
What is Veeam's 'Immutable Backup' feature and which repository type supports it natively in Veeam v12?