In case you haven't noticed I've been putting out a little bit of content lately regarding Veeam Backup for Microsoft365 v8. So far we've covered how to deploy NATS.io in a scale out manner, how to deploy Linux proxies on Ubuntu 22.04 and now I'm going to do an update to a post from earlier in the year regarding deploying PostgreSQL to round out our scalable VB365 deployment.

Veeam Backup for Microsoft 365 supports multiple retention modes, and backup types. Today I dive into some questions around item-level retention and backup copies.

With the latest release of Veeam's Backup for Microsoft365, version 8, they have started to support both proxy pools and for those proxies to be able to run on Linux. This is important for a number of reasons, not the least of which is cost when it comes to a fully scaled out infrastructure for the product. In short when you have tens if not hundreds of proxies within an environment those Windows Server licenses can really rack up.

Release Information for Veeam Backup for Microsoft 365 8 Cumulative Patches

This article provides advice for optimizing NATS Server configuration when used in conjunction with Veeam Backup for Microsoft 365.

With the release of Veeam's Backup for Microsoft365 version 8 Veeam has begun the move to a more distributed and cloud native approach to supporting the product. The end result is the capability known as proxy pools, where you can create a pool of worker VMs, or proxies, that jobs can have many object storage backed repositories assigned to it and then jobs can load balance across the entire pool for processing.

Veeam has begun advising VB365 administrators in large scale environments to use a project called PGBouncer with the required PosgreSQL server. PGBouncer is essentially a proxy that sits in front of your PSQL server and will allow connection attempts to be managed to keep load on the database server at a manageable level by pooling incoming connections and operating a buffer.