VMCE Repository and Storage Management 5 — Questions and Answers
Question 1: A Veeam administrator wants to move a backup repository extent out of a Scale-out Backup Repository without losing any backup data. What is the correct procedure?
- Delete the extent from the SOBR settings and re-add it as a standalone repository
- Switch the extent to maintenance mode, evacuate backups to other extents, then remove it from the SOBR (Correct answer)
- Disable the SOBR, copy files manually, and recreate the SOBR without the extent
- Simply remove the extent from the SOBR GUI; Veeam automatically redistributes the data
Correct answer: Switch the extent to maintenance mode, evacuate backups to other extents, then remove it from the SOBR
Placing the extent into maintenance mode triggers automatic evacuation of backup files to other extents in the SOBR before the extent can be safely removed.
Question 2: Which Veeam technology allows a Linux repository to serve as both a backup target and as a secure, air-gapped immutable storage location without requiring a separate appliance?
- Veeam Cloud Connect repository with immutability enabled
- Veeam hardened repository using Linux immutable flag (chattr +i) (Correct answer)
- Veeam Object Storage repository with S3 Object Lock
- Veeam NAS backup repository with WORM filesystem mount
Correct answer: Veeam hardened repository using Linux immutable flag (chattr +i)
The Veeam hardened repository uses Linux's native immutable file attribute (chattr +i) to prevent modification or deletion of backup files for a configurable period, turning a commodity Linux server into an immutable storage target.
Question 3: When Veeam performs a health check on a backup repository, what operation does it carry out?
- It verifies that all VMs in the backup chain can be booted using Instant Recovery
- It reads and CRC-validates all data blocks in the most recent restore point against stored checksums (Correct answer)
- It compares the backup file list against the Veeam configuration database and removes orphaned files
- It runs a full synthetic backup to replace potentially corrupted incremental restore points
Correct answer: It reads and CRC-validates all data blocks in the most recent restore point against stored checksums
The health check reads backup data blocks and validates them against stored CRC checksums to detect silent data corruption without performing a full restore.
Question 4: What is the recommended action when a Veeam administrator receives a 'Repository does not have enough free disk space' warning but no backup jobs have failed yet?
- Immediately run active full backups for all jobs to consolidate restore points
- Expand repository capacity, reduce retention settings, or add a new extent to the SOBR before space is exhausted (Correct answer)
- Enable synthetic full backups to merge incremental files and reclaim space automatically
- Disable health checks to prevent them from consuming additional temporary space
Correct answer: Expand repository capacity, reduce retention settings, or add a new extent to the SOBR before space is exhausted
The warning indicates that space is running low; proactive steps—adding storage, adding extents, or reducing retention—should be taken before jobs start failing.
Question 5: Which Veeam backup repository configuration is best suited for a remote office with limited WAN bandwidth that must store backups locally and replicate only changed blocks to headquarters?
- A remote repository added directly to the central Veeam server using WAN over TCP
- A local repository managed by Veeam Backup & Replication at the remote site with a Backup Copy job using WAN Acceleration (Correct answer)
- An object storage repository at HQ with direct writes from the remote site
- A Scale-out Backup Repository with remote extents connected via a site-to-site VPN
Correct answer: A local repository managed by Veeam Backup & Replication at the remote site with a Backup Copy job using WAN Acceleration
WAN Accelerator technology in Veeam Backup Copy jobs caches and deduplicates data on both ends, significantly reducing the amount of data sent across limited WAN links.
Question 6: In Veeam's immutability model for a hardened Linux repository, what occurs when the immutability period expires for a backup file?
- The file is automatically deleted by Veeam's retention processor
- The file's immutable flag is cleared and Veeam can then delete it according to normal retention rules (Correct answer)
- The immutability period is automatically extended by another identical period to ensure continuous protection
- The file must be manually removed by the Linux root user since Veeam cannot delete it
Correct answer: The file's immutable flag is cleared and Veeam can then delete it according to normal retention rules
Once the immutability period expires, Veeam removes the chattr +i flag, after which standard retention processing can delete the file as scheduled.
Question 7: A Veeam repository is configured with a 30-day retention policy. A backup administrator enables GFS (Grandfather-Father-Son) retention on the same job. How do the two retention settings interact?
- GFS restore points are kept beyond the 30-day rolling retention, while non-GFS restore points still follow the 30-day limit (Correct answer)
- The 30-day retention overrides GFS, so all restore points older than 30 days are deleted regardless of GFS flags
- GFS replaces the 30-day retention entirely; only the defined weekly/monthly/yearly points are retained
- GFS only applies to backup copy jobs and has no effect on primary job retention settings
Correct answer: GFS restore points are kept beyond the 30-day rolling retention, while non-GFS restore points still follow the 30-day limit
GFS flags mark specific restore points (weekly, monthly, yearly) to be retained longer than the standard rolling retention period, so those flagged points survive past the 30-day window.
A Veeam administrator wants to move a backup repository extent out of a Scale-out Backup Repository without losing any backup data.
What is the correct procedure?