The file in which a Veeam Plug-in stores compressed database backup data, whether full, incremental or log. When kept on a hardened repository it turns immutable a day after it is written.
Also called Veeam Plug-in backup file.
Read more: Veeam Help Center
In the Ultra Transcenders books
Each book explains VAB in context, with comparison tables and the common traps.
Terms in this definition
- Schema
The middle part of a Unity Catalog name (
catalog.schema.table), grouping tables, views, volumes, functions and models inside a catalog. A grant on it covers everything in it now and later, and nothing inside can be reached withoutUSE SCHEMA. - Deployment modes
The two ways ARM can deploy: Incremental, the default, creates or updates what the template lists and ignores everything else; Complete also removes resource group contents absent from the template.
- log
Text written by a component to record something that happened. VCF Operations for logs takes these in, and after integration with VCF Operations they can be searched from its Analyze page and Log Analysis widget.
- hardened repository
A Linux repository that locks backups for a defined time so nobody, root included, can delete, change or move them, which sets it apart from governance mode.
Related terms
- VACM
Written once for each Veeam Plug-in backup job to describe that job. Whereas VAB and VASM files can become immutable on a hardened repository, this metadata file never does.
- VASM
A metadata file that accompanies every VAB file and that Veeam Backup & Replication reads for details of Veeam Plug-in backups. If the VACM file goes missing, it can be rebuilt from these files.