An incremental log backup file kept alongside the image backup files, holding shipped transaction logs from Microsoft SQL Server, archived logs from Oracle or WAL files from PostgreSQL.
Also called log backup file.
Read more: Veeam Help Center
In the Ultra Transcenders books
Each book explains VLB in context, with comparison tables and the common traps.
Terms in this definition
- 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.
- Microsoft SQL Server
Microsoft's database engine. It can hold Veeam's configuration database in place of PostgreSQL, and is protected with a dedicated plug-in, Veeam Explorer, and application-aware processing plus log backup.
- write-ahead log
The log files in which PostgreSQL records its transactions. Because Veeam captures these files with image-level backups, a database can be brought back to a moment in between restore points.
- PostgreSQL
Short for Azure Cosmos DB for PostgreSQL, a Citus-based distributed relational service that scales writes out horizontally. New projects are steered away from it towards Azure Database for PostgreSQL elastic clusters.
Related terms
- VLM
Holds a log backup job's metadata. Whenever logs from PostgreSQL, Oracle or SQL Server are protected, it sits next to the VLB files.
- VOM
Oracle archived log data sits in this file type, kept in the repository together with VLB and VLM files.
- VPM
PostgreSQL WAL data sits in this file type, kept in the repository together with VLB and VLM files.
- VSM
SQL Server transaction log data sits in this file type, kept in the repository together with VLB and VLM files.