EVEO DBaaS (SQL Server)
Overview
Section titled “Overview”EVEO provides a managed SQL Server (DBaaS) used for selected production workloads. Unlike our self-managed SQL instances on VMs/bare metal, this service is provider-managed.
Purpose
Section titled “Purpose”- Run production SQL Server with provider-managed operations (backups, platform availability).
What we have (current)
Section titled “What we have (current)”These values describe the currently provisioned EVEO DBaaS plan (no pricing).
| Item | Value |
|---|---|
| EVEO contract label | dbaas-leftec (SP1) |
| Data center | SP1 (Cotia) |
| SQL Server edition | SQL Server Standard |
| Compute | 2 vCores (provider notes: equivalent to 4 vCPUs) |
| Memory | 16 GB RAM |
| Storage | 300 GB |
| Backups | Daily backups included |
Entry points
Section titled “Entry points”- Backend endpoint (private network):
192.168.50.10:1433 - Preferred client endpoint: use
*.db.lefwhere available (see TCP proxy)
Dependencies
Section titled “Dependencies”- Operator access requires VPN/LAN (see VPN access).
- Clients typically connect through HAProxy (
proxy.core.lef/np-proxy) using stable*.db.lefendpoints (see TCP proxy andtokio-prod.db.lef).
Backup & recovery
Section titled “Backup & recovery”- Backups are provided by EVEO; confirm retention and recovery expectations in the BCDR/backup policies.
Operational notes
Section titled “Operational notes”- Application-side connection strings should prefer
*.db.lefhostnames over direct IPs.
Known risks / failure modes
Section titled “Known risks / failure modes”- If HAProxy routing is misconfigured, DBaaS appears down to clients even when the provider service is healthy.
- VPN/DNS issues prevent access even when the DB is healthy.