Full backup files that store copies of full VM images

Mounts Backups and replicas for File-Level access, browsing the VM guest File System and restoring VM Guest OS Files and application itmes to original location.

______ is used to enable the following features:
• SureBackup: Recovery verification
• Instant VM Recovery®
• Staged Restore
• On-Demand Sandbox™
• Multi-OS File-Level Recovery
• Universal Application-Item Recovery (U-AIR®)

implies that during the first run of a backup job, a full backup
of a VM is created. VM data is copied block by block, compressed at an appropriate
compression level and stored in a resulting full backup file (.vbk). All subsequent backups
are incremental (that is, Veeam Backup & Replication copies only those data blocks that
have changed since the last job run). During reverse incremental backup, Veeam Backup &
Replication “injects” changes into the .vbk file to rebuild it to the most recent state of the
VM. It also creates a reverse incremental backup file (.vrb) containing data blocks that are
replaced when the full backup file is rebuilt. Therefore, the most recent restore point is
always a full backup, and it gets updated after every backup cycle.

When starting a backup or replication job, it fails with an error:
“Current license or ESXi version prohibits execution of the
requested operation.”
Solution: Please upgrade to a paid version of ESX(i). Free ESX(i)
version doesn’t have API, which is used by Veeam Backup &
Replication.

Incremental backup files that store incremental changes of VM images.

Deploys a driver for CBT & COmmunicates with the VSS framework during backup, replication and other jobs.

Used to solve the most common problems that backup administrators encounter during offsite backup and replication are:
• Insufficient network bandwidth to support VM data traffic
• Transmission of redundant data

Veeam Backup & Replication retrieves
VM data from the source datastore
(volume) where the VM resides,
compresses and deduplicates it, and
writes it to the .vbk file on the backup
repository.

statistics that can teach us
about where the jobs are slowing down. This can be
source/network/target/proxy

Configuration Backup File

WIndows SErvices that coordinates all operations performed by Veeam backup and replication such as backup, replicaiton, recovery verification and restore tasks.

_______ is a backup infrastructure component that sits between the
backup server and processed VM. This component is needed if the backup or replication jobs
perform the following processing of VMs:
• Application-aware processing
• Guest file system indexing
• Transaction logs processing

Infrastructure Assessment pack as a ballpark predeployment assessment of the potential
amount of free space that should be available on the target repositories

• Software that provides a fix for the problem (case closed)
• Permanent business or system workaround (case closed)
• Temporary business or system workaround (case severity level is reduced)
• Action plan for the development of a fix or workaround: milestones and
dependencies are set, communicated and tracked (case severity level might be
changed)
• Issue is a customer-specific customization or enhancement and is not covered under
maintenance (customer notification, case closed)

Sharepoint Explorer

Analyses the system installs and upgrades necessary components and services depending on the role selected for the server.

The following components require ____-bit versions of the operation system ONLY:
• Veeam backup server
• WAN Accelerator
• Veeam Explorers

Veeam Backup & Replication does not
retrieve VM data from the source
datastore (volume). Instead, it
“synthesizes” a full backup from data you
already have on the backup repository.
Veeam Backup & Replication accesses
the previous full backup file and a chain
of subsequent increments on the backup
repository, consolidates VM data from
these files and writes consolidated data
into a new full backup file. As a result,
the created synthetic full backup file
contains the same data you would have
if you created a full backup in a regular
manner.

Severity ___ A business-critical software
component or a Veeam managed
system is inoperable or unavailable;
production system is down; there is
an emergency condition; requires
an immediate workaround or
solution. Examples: Excessive
abnormal terminations impacting all
monitoring, backups and schedules
or a down/offline production
system cannot be restored;
application or system failure caused
by Veeam product.

Private & Public encryption keys - Enterprise Manager

Interacts with the virtual infrastrucure to collect and cache the virtual infrastrucure topology

Used to receive email notification about all jobs performed on the Veeam backup server
in one email, configure email notification settings

These files are used by the Veeam CBT driver to keep track of changed
data blocks. For every VHD/VHDX or AVHD/AVHDX file of a VM, there is a separate
CTP file.

Severity __ A non-production issue; the
majority of functions are still
usable, a limited condition that can
be readily circumvented. Example:
Non-production application
response times or system
performance is slow, but system is
available. Some monitoring or
backups are impacted.