Recommendations
- It is not recommended to share a PostgreSQL instance with any other services. It should be dedicated to host the Veeam Backup for Microsoft 365 configuration database and cached metadata only.
- For the latest supported version, please check the System Requirements page.
Sizing
| PostgreSQL | ||
|---|---|---|
| OS | Remote Linux server* | |
| CPU | 16 Cores | |
| RAM | 64 GB | |
| Disk | 100 GB | OS + software installation + logs. |
| IOPS | 7500 | Minimum. SSD storage is highly recommended. |
Note: The sizing above provides sufficient resources for ~50 VB365 Proxies. Using > 50 Proxies will require additional compute resources.
Note: Although Windows is supported, it is recommended to use Linux as OS for PostgreSQL. For Linux OS, disable RAM swapping or overcommit as stated in the docs.
Performance tweaking
Consider the following:
- If you select to “Install a new instance, the installation wizard will apply the right performance settings to the PostgreSQL Instance.
- If you select Use existing Instance, you should run Set-VBOPSQLDatabaseServerLimits after installing VB365.
- If the CPU or RAM resources are changed after Veeam Backup for Microsoft 365 installation, you must run this cmdlet again to adjust hardware resources of the PostgreSQL instance.
Note: You must restart the PostgreSQL service after you run this cmdlet.
Cache databases for Object Storage Repositories
Since version 8, cache is stored as a PostgreSQL database and is used to avoid most API calls.
For each Object Storage Repository, a database will be created.
As a rule of thumb provide 1% of the source data size as local cache for metadata.