Activate Your Data

Topology options for Backup

Topology 1 (MA Server and Storage Sizing)

Topology 1 Direct backup to cloud library MA On prem and storage in cloud

Site Source Data (TB) Target disk for defined retention (TB) MA Config

BDC 1 0.9 1.4 XS

BDC 8 1.6 2.7 XS

Extra Small (XS) - Windows Physical/VM, 2 cores/4 vCPUs, 16GB/24GB RAM, 600 GB on 15k rpm Disk
Space, 300GB usable on 15K for OS disk, 4x1GbE or 2x10GbE Ethernet ports

The retention period of backups has been considered as..

a. 28 Daily Incremental Backups : Means that at any time, restoration points for any day in the last 28 days are
available
b. 5 Weekly Full Backups : Means that at any time, 4 weekly restoration points in the last 1 month are available
c. 13 Monthly Full Backups : Means that at any time, 12 monthly restoration points for the last 1 year are
available
2
Topology 2 (MA Server and Storage Sizing)

Topology 1 Direct backup to cloud library MA On prem and storage in cloud

Site Source Data (TB) Target disk for defined retention (TB) MA Config

BDC 1 0.9 1.4 XS

BDC 8 1.6 2.7 XS

Extra Small (XS) - Windows Physical/VM, 2 cores/4 vCPUs, 16GB/24GB RAM, 600 GB on 15k rpm Disk
Space, 300GB usable on 15K for OS disk, 4x1GbE or 2x10GbE Ethernet ports

The retention period of backups has been considered as..

a. 28 Daily Incremental Backups : Means that at any time, restoration points for any day in the last 28 days are
available
b. 5 Weekly Full Backups : Means that at any time, 4 weekly restoration points in the last 1 month are available
c. 13 Monthly Full Backups : Means that at any time, 12 monthly restoration points for the last 1 year are
available
3
Topology 3 (MA Server and Storage Sizing)

Topology 3 Backup consolidated to MA in BDC3ABC MA and Storage on Prem

Site Source Data (TB) Target disk for defined retention (TB) MA Config

BDC10P 20.43 Nil, data backed uo to BDC3ABC

BDC3ABC 25.64 68 L

Large (L) - Windows Physical/VM - 12 cores/vCPUs, 64 GB RAM, 2 TB SSD Usable Space, 400GB usable on
15K or SSD for OS disk, 4x1GbE or 2x10GbE Ethernet ports

The retention period of backups has been considered as..

a. 28 Daily Incremental Backups : Means that at any time, restoration points for any day in the last 28 days are available
b. 5 Weekly Full Backups : Means that at any time, 4 weekly restoration points in the last 1 month are available
c. 13 Monthly Full Backups : Means that at any time, 12 monthly restoration points for the last 1 year are available
4
Additional Notes
1) COMMSERVE (MASTER BACKUP SERVER) CONFIG :
There will be a separate server (Physical or Virtual) required for Commserve and its Passive DR partner (recommended
but optional). The configuration of each would be as follows : 12 CPU cores, 32GB RAM, 150GB of disk space
excluding OS partition), 600+ IOPS, 2 x 1GbE Ethernet. The Commserve servers are kept in synch using MSSQL Log
Shipping)

2) PERFORMANCE :
For best performance, when deploying a Media Agent on a VM, it is highly recommended to provision a dedicated
datastore built on SSDs (or 15K RPM drives)

3) FIREWALL :
Designated Firewall ports will need to be opened for communication between Media Agent and Cloud Target

4) REPLICATION :
Commvault replication (performed between Media Agents) preserves dedupe and compression making it WAN and
Target storage efficient.

5) ALTERNATE DATA PATH :

In case a MA unavailability in a certain site, due to hardware or VM failure, the backups from the site can be re-routed 5
through another MA.
Advantages to from Commvault Solution
 No intermediate device is required to backup to cloud. The Cloud target can be directly connected to on-prem
Commvault Media Agent

 The data restore location can be in cloud, even if the data was backed up from on-premise or vice-versa

 Media agent hardware failure still ensures restores because target has information which can be read by a new Media
Agent.

 In case of Media Agent hardware failure, backup can be rerouted through another one.

 Parallel copy enables data availability on two different targets managed by the same Media Agent.

 Source based dedupe (at client) combined with Inline deduplication at Media Agent ensures reduced data transfer over
LAN, MAN and WAN.

 Replication of data (in backups) is an inbuilt feature that can be used between any two Media Agents and in multiple
ways (On-prem to Cloud, Cloud to On-prem, On-Prem to On-Prem, Cloud to Cloud)

 Media Agent can be deployed on physical or virtual machine, on premise or in Cloud/MSP 6