VMCE Backup Job Configuration 2 β Questions and Answers
Question 1: When configuring a Veeam backup job, which storage optimization target is best suited for backing up virtual machines with large, mostly static files?
- Local target (16 TB+ backup files) (Correct answer)
- LAN target (recommended)
- WAN target (low bandwidth)
- Local target (under 16 TB backup files)
Correct answer: Local target (16 TB+ backup files)
The 'Local target (16 TB+ backup files)' block size is best for large, mostly static datasets as it uses 1 MB blocks to maximize deduplication for stable data.
Question 2: A backup administrator needs to ensure that VSS-aware backups are performed but wants to fall back to crash-consistent backups if VSS fails. Which application-aware processing setting achieves this?
- Enable application-aware processing and check 'Try application processing, but ignore failures' (Correct answer)
- Disable application-aware processing entirely
- Enable application-aware processing with 'Require successful processing'
- Use pre-freeze/post-thaw scripts only
Correct answer: Enable application-aware processing and check 'Try application processing, but ignore failures'
Selecting 'Try application processing, but ignore failures' allows Veeam to attempt VSS quiescing and fall back gracefully to crash-consistent if it fails.
Question 3: Which retention policy type in a Veeam backup job retains restore points based on calendar days rather than a fixed count of restore points?
- Simple retention (keep N restore points)
- GFS (Grandfather-Father-Son) retention
- Days-based retention policy (Correct answer)
- Short-term retention with health check
Correct answer: Days-based retention policy
Days-based retention keeps all restore points created within a defined number of days, regardless of how many restore points that produces.
Question 4: In Veeam Backup & Replication, what is the purpose of the 'Defragment and compact full backup file' job schedule option?
- It removes deleted blocks from the VBK file to reclaim disk space (Correct answer)
- It creates a new synthetic full backup
- It merges all incrementals into a single VBK
- It runs a health check on all restore points
Correct answer: It removes deleted blocks from the VBK file to reclaim disk space
Defragment and compact reclaims white space left after old data blocks are no longer referenced, reducing the physical VBK file size.
Question 5: When adding VMs to a backup job using a container (e.g., a vSphere cluster), what happens by default when new VMs are added to that container?
- New VMs are automatically included in the next backup job run (Correct answer)
- New VMs must be manually added to the job
- New VMs are excluded until the job is recreated
- New VMs trigger an immediate full backup cycle
Correct answer: New VMs are automatically included in the next backup job run
Dynamic inclusion means Veeam automatically picks up new VMs added to a container object without manual job editing.
Question 6: A backup job is configured with a 14-day simple retention policy. After running daily incremental backups for 20 days, how many restore points are retained?
- 14 (Correct answer)
- 20
- 7
- Depends on storage space available
Correct answer: 14
Simple retention keeps exactly N restore points; once the limit is reached, the oldest restore point is removed to maintain exactly 14.
Question 7: Which option in backup job advanced settings controls whether Veeam processes multiple VMs within the same job simultaneously?
- Per-VM backup files with parallel processing
- Job parallelism under the Storage tab
- Concurrent task limit in backup proxy settings (Correct answer)
- Task throttling in the job advanced settings
Correct answer: Concurrent task limit in backup proxy settings
The concurrent task limit set on the backup proxy determines how many VM disks can be processed simultaneously across all jobs using that proxy.
When configuring a Veeam backup job, which storage optimization target is best suited for backing up virtual machines with large, mostly static files?