10-Data Protection Flashcards
Recovery Services Vault
Home for all backup jobs
3 steps to back up data whether in cloud or on-prem
- Create recovery services vault
- Define your goal, your workload
- Configure backup policy
MARS agent
Backup or recovery files and folders on physical or virtual Windows OS (VMs can be on-prem or in Azure)
No separate backup server required
Not application aware; file, folder, and volume-level restore only
No support for Linux
Implementing On-Prem File and Folder Backup
- Create the recovery services vault
- Download the agent and credential file
- Install and register agent
- Configure the backup
Options for Backup
- Snapshots
- Azure backup
- Azure site recovery
Snapshots
Managed snapshots provide a quick and simple option for backing up VMs that use Managed Disks
Azure backup
Azure Backup supports application-consistent backups for both Windows and Linux VMs
Azure Site Recovery
Azure Site Recovery protects your VMs from a major disaster scenario when a whole region experiences an outage
Workload Protection Needs
Many backup options are available
How workload is being protected today?
How often the workload is backed up?
What types of backups are being done?
Is disaster recovery protection in place?
Virtual Machine Backup
- Snapshot is taken
2. Snapshot is transferred to vault
Implement VM Backups
- Create vault
- Define backup
- Backup the VM
Azure Backup Server
App-aware backups, file/folder/volume backups, and machine state backups (bare-metal, system state)
Backup Component Comparison
Azure Backup (MARS) agent
vs
Azure Backup Server (MABS)
Soft Delete
Backup data is retained for 14 additional days
Recover soft deleted backup items using an ‘Undelete’ operation
Natively built-in for all the recovery services vaults
Azure Backup Center
Single pane of glass to manage backups across a large and distributed Azure environment
Datasource-centric management focused on what you are backing up
Connected experiences with native integrations that enable management at scale