VMCE Backup Job Configuration 5 — Questions and Answers
Question 1: In Veeam Backup & Replication, what is the recommended approach when backing up VMs that host Microsoft SQL Server with transaction log backups configured?
- Enable application-aware processing with log backup and specify the log backup frequency (Correct answer)
- Use a dedicated SQL Server backup agent instead of the VM backup job
- Disable VSS to avoid conflicts with SQL Server's own VSS writer
- Back up the SQL VM in crash-consistent mode only
Correct answer: Enable application-aware processing with log backup and specify the log backup frequency
Application-aware processing with Veeam's SQL log backup integration allows both VM-level and transaction log backups from a single job configuration.
Question 2: Which transport mode should be selected when backing up VMs on a VMware cluster where the backup proxy is a physical server connected via Fibre Channel to the same SAN as the datastores?
- Direct SAN access mode (Correct answer)
- Virtual appliance (hotadd) mode
- Network (NBD) mode
- Backup from storage snapshots
Correct answer: Direct SAN access mode
Direct SAN access allows the physical proxy to read VM data directly from the SAN LUN, bypassing ESXi hosts for maximum throughput.
Question 3: When a Veeam backup job is configured with 'Reverse incremental' mode, what is the structure of restore points on the repository?
- The latest restore point is always a full VBK; older restore points are stored as reverse incremental VRB files (Correct answer)
- All restore points are stored as VIB incremental files
- The first restore point is a full VBK and all others are forward VIB files
- Each restore point is stored as an independent full VBK
Correct answer: The latest restore point is always a full VBK; older restore points are stored as reverse incremental VRB files
In reverse incremental mode, Veeam rolls forward incrementals into the full so the newest restore point is always a complete VBK, with older points stored as VRB deltas.
Question 4: An administrator enables 'Backup from storage snapshots' in a Veeam job. Which additional infrastructure component is required for this feature on a NetApp storage system?
- Veeam Storage Integration plugin and a configured NetApp storage system in Veeam (Correct answer)
- A Veeam Gateway Server on the NetApp filer
- A dedicated backup proxy installed directly on the NetApp appliance
- NetApp SnapMirror license on the destination volume
Correct answer: Veeam Storage Integration plugin and a configured NetApp storage system in Veeam
Backup from storage snapshots requires adding the NetApp storage system to Veeam and using the storage integration plugin to leverage native array snapshots.
Question 5: What is the effect of configuring 'Limit maximum concurrent tasks' to 1 on a backup repository in Veeam?
- Only one VM disk can be written to the repository at any given time, regardless of how many jobs target it (Correct answer)
- Only one backup job can run against the repository simultaneously
- The repository processes one restore point per day
- One concurrent read task and one write task are allowed
Correct answer: Only one VM disk can be written to the repository at any given time, regardless of how many jobs target it
The concurrent task limit on the repository controls how many simultaneous disk write streams it accepts; setting it to 1 serializes all backup writes.
Question 6: In a Veeam backup job, which pre-job script execution scenario is correct?
- The pre-job script runs once before the job starts processing any VMs in the job (Correct answer)
- The pre-job script runs before each individual VM is processed
- The pre-job script runs on each guest VM before VSS quiescing
- The pre-job script runs on the backup repository before data is written
Correct answer: The pre-job script runs once before the job starts processing any VMs in the job
Pre-job scripts execute once on the Veeam backup server before the job begins, not per-VM; per-VM scripts are configured under guest processing.
Question 7: Which setting in Veeam backup job configuration controls the maximum time allowed for a single VM backup task before it is considered timed out?
- Maximum allowed time per VM task under advanced job settings (Correct answer)
- Backup window time frame under scheduling
- Job timeout under the job's General settings
- Proxy timeout in the backup infrastructure settings
Correct answer: Maximum allowed time per VM task under advanced job settings
The per-task maximum time limit in advanced settings aborts individual VM tasks that exceed the threshold, preventing one slow VM from blocking the entire job.
In Veeam Backup & Replication, what is the recommended approach when backing up VMs that host Microsoft SQL Server with transaction log backups configured?