(click to expand table of contents)
Blueprint Deployment
This section provides details for a “Day 1” deployment that attains simple scaling and efficient storage consumption with an eye towards the least challenging long term growth strategy.
Systems to Deploy and initial Assumptions
| Role | CPU* | RAM (GB)* | Disk Usage (GB) | Network | SQL |
|---|---|---|---|---|---|
| Cloud Connect Server/VBO Server | 8 | 12 | 100 | Management | SQL Express |
| Cloud Gateway | 2 | 4 | 64 | DMZ | |
| Backup for Office 365 Proxy #1 | 4 | 8 | Disk 1: 64Disk 2: ** | Management or O365 proxy network |
* These figures are recommended minimums.
** Disk 2 will be used to store the O365 metadata for each Tenant. The capacity required will be based on the total protected capacity.
| Num of Users | Est. Num of Objects | Proxy CPU | Proxy RAM (GB) |
|---|---|---|---|
| 750 | 1943 | 4 | 8 |
| 6000 | 15040 | 8 | 32 |
The tables above display the estimated amount of both users & objects that can be backed up by the dedicated proxy (#1 above). For simplicity’s sake the minimum recommended compute resources have been defined.
Cloud Connect Server and Cloud Gateway Deployment
- Review documented requirements:
- Install of Backup and Replication
- Obtaining your Veeam Cloud Connect License Key
- This blueprint recommends that this Veeam Cloud Connect deployment is not providing any additional services beyond self-service Microsoft Office 365 recovery. E.g., Do not provide Cloud Connect Backup or Cloud Connect Replication services from this Backup and Replication deployment.
- Install Backup for Office 365
- Add and configure an additional Proxy
- Reminder: We do not recommend using the default Proxy. This will be your “first” Proxy that will be used when creating Backup Jobs.
- Backup Proxy Servers