Veeam Backup & Replication 12.2 (build 12.2.0.334) has been recently re...
VMware® vCenter Converter Standalone provides an easy-to-use solu...
VMware ESXi partitions layout includes some old FAT partitions used for the...
The legacy C# vSphere Client for Windows is no more available for vSphere 6...
In ESXi the partitions schema is automatically defined by the installation...
One of the new feature of VMware vSphere 6.7 is the full support for Truste...
Omnissa ONE will probably be the first big official event of Omnissa, after...
VMware by Broadcom has just released vSphere 8.0 Update 3 (8.0.3). Note tha...
Veeam® Software today announced the release of Veeam Data Platfor...
Debian like distributions have a nice option to manage distribution upgrade...
Reading Time: 4 minutes With the introduction of Postgre SQL as the “embbeded” database in Veeam Backup & Replication 12, several new deployments now use the default database in the same machine of Veeam Backup Server. I don’t want to consider in this post all the pros and cons of the embedded approach. But it’s fully supported and can can also to an interesting number of protected workload (tested with more than 1000).
Reading Time: 5 minutes As descrived in the previous post (Optimize the consumed space of the Veeam Backup Catalog) the Veeam Backup Catalog is a feature of Veeam Backup & Replication that stands for VM guest OS file indexing. It’s not a server role, but it’s a service of the Veeam Server, for this reason required space must be planned carefully. By default, the indexing data is stored in the VBRCatalog folder (C:\VBRCatalog) on the Backup Server.
| Disclaimer & Copyright
