VMCE Backup Job Configuration Questions and Answers — Questions and Answers
Question 1: An administrator is configuring a backup job for a large file server with over 20 TB of data. To optimize backup file size and job performance when targeting a deduplicating storage appliance, which 'Storage optimization' setting is most appropriate?
- Local target
- LAN target
- Local target (large blocks) (Correct answer)
- WAN target
Correct answer: Local target (large blocks)
The 'Local target (large blocks)' setting, which uses a 4 MB block size, is recommended for backup jobs with more than 16 TB of source data. Larger block sizes can improve performance and are often beneficial for deduplicating storage appliances.
Question 2: A backup job is configured with the 'forever forward incremental' backup method and a retention policy of 14 days. What happens when a new restore point is created after the 14th restore point?
- A new active full backup is automatically created, starting a new chain.
- The oldest incremental restore point is merged into the full backup file (.VBK). (Correct answer)
- The entire backup chain is deleted and a new full backup is created.
- The oldest incremental restore point is deleted without being merged.
Correct answer: The oldest incremental restore point is merged into the full backup file (.VBK).
In a forever forward incremental chain, once the retention policy is met, Veeam merges the oldest incremental backup file (.VIB) into the full backup file (.VBK), advancing the full backup to a more recent point in time. This process avoids the need for periodic full backups.
Question 3: Which of the following backup job settings has the primary trade-off of higher CPU usage on the backup proxy for a smaller backup file size on the repository?
- Storage optimization
- Guest processing
- Backup mode
- Compression level (Correct answer)
Correct answer: Compression level
The compression level setting directly controls the trade-off between CPU usage and backup size. Higher compression levels (like 'High' or 'Extreme') use more CPU resources on the proxy to achieve greater data reduction, resulting in smaller backup files.
Question 4: An administrator wants to ensure the integrity of backup files without scheduling periodic active full backups. Which maintenance option should be enabled in the backup job settings to detect and automatically heal corruption by retrieving correct data blocks from the source?
- Defragment and compact full backup file
- Perform backup file health check (Correct answer)
- Run active full backup periodically
- Enable backup file encryption
Correct answer: Perform backup file health check
The 'Perform backup files health check' option, also known as storage-level corruption guard, periodically scans backup files for corruption. If it finds a corrupt data block, it can retrieve the correct version from the source production storage to heal the backup file.
Question 5: A company needs to create a copy of its backups to an off-site repository. The requirement is that as soon as a new restore point is created by the primary backup job, it should immediately be copied to the secondary location. Which Backup Copy job mode should be configured?
- Periodic copy mode
- Immediate copy mode (Correct answer)
- Reverse incremental mode
- GFS copy mode
Correct answer: Immediate copy mode
The 'Immediate copy mode' is designed for this exact scenario. It monitors the source backup job and, as soon as a new restore point is available, it automatically starts the process of copying that restore point to the target repository.
Question 6: When comparing an Active Full backup to a Synthetic Full backup, what is the primary impact of creating an Active Full?
- It requires more space on the backup repository than a synthetic full.
- It places a higher I/O load on the backup repository.
- It places a higher I/O load on the source production storage. (Correct answer)
- It takes longer to restore from than a synthetic full.
Correct answer: It places a higher I/O load on the source production storage.
An Active Full backup reads all data directly from the source production storage, which creates a significant I/O load on the production environment. A Synthetic Full, in contrast, is created by synthesizing data from existing backup files already on the repository, which primarily impacts the repository's I/O.
An administrator is configuring a backup job for a large file server with over 20 TB of data.
To optimize backup file size and job performance when targeting a deduplicating storage appliance, which 'Storage optimization' setting is most appropriate?