VMCE Repository and Storage Management 2 — Questions and Answers
Question 1: What is the purpose of the Veeam Data Mover service running on a repository server?
- It compresses and deduplicates backup data before writing to disk
- It transfers data between source and target components during backup and restore jobs (Correct answer)
- It manages repository capacity and triggers alerts when thresholds are exceeded
- It schedules backup jobs and maintains the Veeam configuration database
Correct answer: It transfers data between source and target components during backup and restore jobs
The Veeam Data Mover is a runtime process that handles data transfer between infrastructure components such as source hosts and backup repositories.
Question 2: Which repository type in Veeam leverages native deduplication and compression provided by the underlying storage system?
- Windows repository with ReFS
- Linux repository with XFS
- Deduplicating storage appliance repository (Correct answer)
- Scale-out Backup Repository with capacity tier
Correct answer: Deduplicating storage appliance repository
Deduplicating storage appliance repositories (such as Dell EMC Data Domain or HPE StoreOnce) offload deduplication and compression to the appliance's native capabilities.
Question 3: When configuring a Scale-out Backup Repository, what is the role of the performance tier?
- It stores long-term archive copies of backups on object storage
- It acts as the primary landing zone for new backups and restores (Correct answer)
- It replicates data to a secondary site for disaster recovery
- It hosts the Veeam configuration database for high availability
Correct answer: It acts as the primary landing zone for new backups and restores
The performance tier in a SOBR serves as the primary storage layer where new backups are initially written and from which fast restores are performed.
Question 4: What happens to existing backup chains stored on a repository when you change the backup file format from per-machine with separate metadata files to per-machine without separate metadata files?
- Veeam automatically converts existing backup files to the new format during the next active full backup
- Existing backup chains remain in the old format; the new format applies only to new backup chains created after the change (Correct answer)
- Veeam deletes existing backup files and starts a new active full backup immediately
- The repository becomes read-only until an administrator manually migrates all files
Correct answer: Existing backup chains remain in the old format; the new format applies only to new backup chains created after the change
Format changes are not retroactive; existing backup chains retain their original format and only newly created chains use the updated format.
Question 5: Which Veeam repository role allows a CIFS (SMB) share to be used while still enabling Veeam-managed data movers for improved throughput?
- SMB share configured as a direct-attached repository
- Gateway server added as a Windows-based repository pointing to the SMB path (Correct answer)
- Linux hardened repository mounted via CIFS
- Object storage repository using S3-compatible CIFS endpoint
Correct answer: Gateway server added as a Windows-based repository pointing to the SMB path
A Windows server acting as a gateway mounts the CIFS share and runs the Veeam Data Mover locally, giving Veeam more control over data transfer compared to a pure network share.
Question 6: What is the maximum recommended percentage of repository capacity that Veeam should use before triggering a warning by default?
- 70%
- 80%
- 85% (Correct answer)
- 90%
Correct answer: 85%
By default, Veeam warns administrators when repository free space drops to 10 GB or when capacity utilization reaches 85%.
Question 7: In Veeam Backup & Replication, which setting on a repository controls how many concurrent tasks can write backup data to it simultaneously?
- Backup I/O control
- Concurrent task limit (Correct answer)
- Per-VM backup chains
- Data mover thread count
Correct answer: Concurrent task limit
The concurrent task limit on a repository defines how many simultaneous backup or restore tasks are allowed to read from or write to that repository.
