2. Organizational Requirement Vs Azure Native Backup: Tier I*, Tier II RPO/RTO requirements can not be
achieved ( improved recently ) with Azure Native Backup
* Tier I RPO & RTO requires the application to support high-availability functionality (such as clustering, database availability
groups, etc.). These requirements cannot be met with backups and DR orchestration
Business Requirement
TIER RPO RTO
I* 0.25 – 1 Hour 1 Hour
II 1 – 12 Hours 4 – 24 Hours
MACHINE BACK UP LIMITATION
AZURE VMS
(NO BACKUP
SERVER)
Backed up to vault
Backup once a day(RPO 24 Hours)
App-aware backup for Windows VMs, File
consistent backup for Linux VMs(App
Consistency need custom scripts)
AZURE VM WITH
DPM
Backed up to DPM running in
Azure (to a disk locally
attached to the DPM server
DPM then backs up to vault
Backup twice a day(RPO 12 Hours)
App-aware snapshots
Oracle not supported
Tape isn't supported
AZURE VM WITH
MABS
Backed up to MABS running
in Azure (to a disk locally
attached to the MABS
server)
MABS then backs up to the
vault
Backup thrice a day(RPO 8 Hours)
App-aware snapshots with full
granularity for backup and recovery but
Oracle not supported
Tape isn't supported
Organizational Requirement Azure Native Backup Support Matrix
3. Based on the limitations of Azure native backup , identified DELL EMC Networker DD solution as a 3rd party
Enterprise class backup solution for the below identified items
• IaaS-based non-MSSQL Database: Will be covered by DELL EMC Networker DD solution( Example: Oracle)
• Application: Azure VM Backup (unless RPO <24 hours: Will be covered by DELL EMC Networker DD solution
• Files & Folders: Azure VM Backup (unless RPO is <24 hours): Will be covered by DELL EMC Networker DD
solution
• Application specific workloads that require application-aware backup solutions not protected by Azure native
backups: Will be covered by DELL EMC Networker DD solution
Security requirement :Data Security: Data encryption for backup and recovery of data, at rest and in-flight
• Customer wishes to have an Enterprise level but cost effective solution with high security standards , hybrid
capability and wide range of application support
Example: Different flavours of Databases ,Oracle , Sap HANA
Business Requirement
4. Solution/Design
• There are many 3rd party backup
solution available in Azure .Based on
high-level comparison , chosen DELL EMC
Backup and Recovery solution in Azure –
Networker + Data Domain
• Sizing:D16s v3 compute unit for both
DDVE, NVE to get Premium disk
throughout, to support more than 100K
jobs
• Each region will have a Data
Domain(DDVE) to backup clients in their
respective region
• Central US Networker(NVE) will act as a
master for client servers in both regions.
NVE will be configured with ASR to
manage the regional disaster
• Backup replication across WE, NE will be
using DD replicator and global vNET
peering
• Networker instance will be recovered
through Availability zone, ASR in case of
disaster
5. Advantages and Limitation
Advantages
• Networker client direct back up technology enables the client to send de-duplicated, compressed and
encrypted data directly to Data Domain. Data domain will eventually store the backup data onto Azure blob
storage
• 5-15 mins real time RPO can be achieved
• It can also support both CIFS and NFS protocols simultaneously
• Replication: Between On-prem and Cloud, between the same or different regions in the cloud are possible
• Cross replicated backup means backup can be restored from any region
• Application specific workloads that require application-aware backup solutions not protected by Azure native
backups which will be covered by DELL EMC Networker DD solution such as Oracle, JVM configuration, etc
• Linux support for granular file recovery is limited in Azure native backup but which is not a limitation with
DELL EMC Networker DD solution
• DD VE can scale up to 96TB per instance
Limitation
In case of region failure the RPO of mission critical clients with Zero/Minimum will be deferred