When deploying Veeam Backup & Replication (VBR), one crucial decision is selecting the right database and its location. This choice impacts performance, scalability, and overall manageability of your backup infrastructure. This article explores common database options for Veeam – SQL Express, full SQL Server, and PostgreSQL – and discusses the pros and cons of local versus external database server configurations. Drawing from real-world experiences, we aim to guide you in making the optimal database decision for your Veeam environment.
SQL Express: The Entry Point for Smaller Environments
SQL Server Express Edition is often the default choice, especially for smaller deployments. Its key advantage is being free to use, which significantly lowers the initial cost barrier. Many users in smaller environments find SQL Express perfectly adequate.
A user expresses satisfaction with SQL Express in a smaller Veeam environment.
However, SQL Express comes with limitations, most notably a database size limit of 10GB and limitations on memory and CPU usage. For environments with extensive backup jobs, especially those involving file-to-tape, large numbers of VMs, or features like indexing, these limits can quickly become a bottleneck. As one user noted, “Yes I have already hit the SQL Express limit, cause the infrastructure grew up in the times and the Veeam is used for backup, replication, backup copy, tape…” This experience highlights that while SQL Express is a good starting point, it’s essential to anticipate growth and potential limitations.
Full SQL Server: Scalability and Features for Growing Needs
For larger deployments and MSP environments, full editions of SQL Server (Standard or Enterprise) are often the preferred solution. The primary benefit is the removal of the limitations present in SQL Express. Full SQL Server offers significantly higher database size capacity, more robust performance capabilities, and advanced features crucial for enterprise-level operations.
A user jokingly expresses relief at their current database size being well under the SQL Express limit.
MSPs, in particular, frequently opt for full SQL Server for their Veeam infrastructure. As one MSP professional stated, “As an MSP we use full fat SQL on external servers. We usually have multiple Veeam DB’s on 1 server i.e. VBR & EM just to save licensing.” This approach allows for consolidation and better resource utilization within their managed environments.
However, full SQL Server comes with licensing costs. These costs can be substantial, especially when licensing per core in virtualized environments. Therefore, carefully considering the resource requirements and licensing implications is critical when choosing full SQL Server.
PostgreSQL: A Promising Alternative in Veeam V12 and Beyond
With the introduction of PostgreSQL support in Veeam V12, a new database option has emerged. PostgreSQL is an open-source, object-relational database system known for its robustness and scalability. Many users are eager to explore PostgreSQL as a potential alternative to SQL Server, particularly to avoid SQL Server licensing costs and limitations.
The prospect of using PostgreSQL directly on the VBR server is appealing to some, as it could simplify deployments and potentially reduce overhead. One user expressed interest in testing this setup: “Looking forward to testing out a large instance of PostgreSQL with v12 to see how that performs since that could possibly go on the VBR server depending on Veeam BP.”
However, PostgreSQL adoption in Veeam is still relatively new. Thorough testing and understanding best practices for PostgreSQL with Veeam are crucial before widespread implementation, especially in production environments.
Local vs. External Database Server: Deployment Strategies
Another key decision is whether to host the Veeam database locally on the VBR server itself or on a separate, external server. Both approaches have their proponents, and the best choice depends on specific environment needs and priorities.
Local Database Server:
Installing the database locally, often SQL Express, on the VBR server simplifies deployment and reduces dependencies. As one user explained, “Hi @Scott , at the customers we always install the SQL-server on the VBR-server itself (even if the VBR-server is virtual or physical). Why : to make it less complex, no dependencies and because of the performance. In normal circumstances SQL Express is sufficient.” This approach can also reduce network traffic between the VBR server and the database server.
External Database Server:
Deploying the database on an external server is often considered a best practice, particularly for larger environments and for full SQL Server implementations. Externalizing the database offers several advantages:
- Improved Performance and Resource Isolation: Separating the database onto a dedicated server prevents resource contention between the VBR server and the database, potentially improving overall performance.
- Enhanced Scalability and Availability: External databases can be scaled independently of the VBR server. For critical environments, external SQL Server deployments can leverage high availability features like Always On Availability Groups.
- Better Security and Manageability: Separating the database allows for more granular security controls and independent management and maintenance schedules. As one user noted, “I prefer the local DB, or at least a Veeam Specific SQL DB Server. When the DB server gets patched I don’t want to have to check Veeam every time to make sure it’s not backing something up messing with the schedule.” Having a dedicated SQL server for Veeam simplifies patch management in this context.
However, external databases add complexity and require additional infrastructure. Network latency between the VBR server and the external database should also be considered, although in most modern networks, this is minimal.
A user expresses humor while considering moving their SQL Server to a separate VM, acknowledging the learning from community discussions.
Key Considerations for Your Veeam Database Choice
Choosing the right database and deployment model for your Veeam environment involves evaluating several factors:
- Environment Size and Growth: Small environments may be perfectly fine with SQL Express locally. Larger and growing environments, especially those using advanced Veeam features, will likely require full SQL Server or PostgreSQL.
- Veeam Feature Usage: Features like file-to-tape, indexing, and CDP replication significantly increase database load and size, potentially necessitating a more robust database solution.
- Performance Requirements: If backup and restore performance is critical, consider externalizing the database to a dedicated server with sufficient resources.
- Licensing Costs: Factor in SQL Server licensing costs when considering full SQL Server editions. PostgreSQL offers a cost-effective alternative.
- Complexity and Manageability: Local databases are simpler to deploy and manage initially. External databases offer more scalability and control but add complexity.
Conclusion: Tailoring Your Database to Your Veeam Needs
Selecting the appropriate database for your Veeam Backup & Replication server is a crucial step in building a reliable and efficient backup infrastructure. While SQL Express provides a convenient entry point for smaller deployments, growing environments and MSPs should carefully consider full SQL Server or the emerging PostgreSQL option. The decision between local and external database deployment depends on balancing simplicity with scalability, performance, and manageability requirements. By carefully evaluating your specific needs and considering the insights shared in this article, you can make an informed decision and optimize your Veeam database strategy.
A user expresses appreciation for community learning and collaboration in database discussions.
