Overview
- MARS (Azure Recovery Services agent): a lightweight agent installed on a Windows machine to back up files and folders directly to an Azure Recovery Services vault. It does not require a separate backup server.
- MABS (Microsoft Azure Backup Server): a full-featured on-premises backup server based on System Center Data Protection Manager (DPM) technology. MABS performs application-aware snapshots, maintains a local copy for low-latency restores, and synchronizes data to an Azure Recovery Services vault for offsite retention.
Quick comparison table
Benefits
MARS agent- Lightweight and easy to deploy on Windows machines for direct cloud backup.
- Ideal for protecting files and folders when you want a simple, serverless approach.
- Quick recovery scenarios where direct recovery from the Recovery Services vault is acceptable.
- Application-aware backups and consistent snapshots for supported workloads (for example, Microsoft SQL Server, Exchange, SharePoint).
- More granular recovery options: volume-level, item-level, and application-consistent restores.
- Local copy of backup data for low-latency restores and fast recovery operations.
- Supports protection of Hyper-V and VMware workloads and integrates with supported Linux VMs where applicable.
- Integrates DPM technology with Azure Backup without requiring a separate System Center license for backup functionality.
Limitations
MARS agent- Scheduling limited to three time slots per day.
- Not application-aware — cannot provide application-consistent snapshots for databases or transactional services.
- Recovery options limited to files, folders, and volumes (no application-item level restores).
- Supports Windows only.
- Does not support backing up Oracle workloads.
- Requires an active Azure subscription to use cloud-copy and offsite storage via the Recovery Services vault.
- Does not support tape targets for long-term archival; design focuses on disk-based local retention and cloud copy.
Choose MARS for simple file-and-folder cloud backups on Windows hosts. Choose MABS when you need application-aware snapshots, local copies for fast restores, and more advanced recovery options.
What they protect
- MARS agent: Files and folders (and volume-level backups) on Windows systems.
- MABS (Backup Server): Files, folders, volumes, virtual machines, and supported applications/workloads (application-aware protection for supported Microsoft workloads and VM platforms).
Storage behavior
- MARS agent: Stores backed-up data directly in the Azure Recovery Services vault. No local copy is maintained by MARS, so restores are performed from the cloud.
- MABS: Keeps a local copy of backup data on the backup server (providing low-latency restores) and synchronizes backup data to the Azure Recovery Services vault for offsite/cloud retention.
When to choose which (decision checklist)
-
Use MARS if:
- You need a lightweight, zero-infrastructure agent for basic file/folder protection.
- You want direct backups to the Recovery Services vault without maintaining a backup server.
- Your environment is Windows-only and application-consistent backups are not required.
-
Use MABS if:
- You require application-consistent backups for SQL Server, Exchange, SharePoint, or other supported workloads.
- You need a local cache for fast restores and flexible restore granularity.
- You protect VMs (Hyper-V/VMware) and complex on-premises workloads and want an integrated on-premises-to-cloud backup solution.
Example scenarios
- Small business with only file servers (no databases): MARS is a simple, low-cost option to back files directly to Azure.
- Enterprise with on-premises SQL and Exchange plus VMs: MABS provides application-aware protection, local restores, and cloud copy for offsite retention.
Additional resources
- Azure Backup overview
- Recovery Services vault documentation
- Azure Backup Server (MABS) documentation
Summary
- MARS is a lightweight agent best for straightforward Windows file- and folder-level backups directly to Azure.
- MABS is the preferred choice for application-aware backups, granular restores, and environments that benefit from a local backup cache plus cloud synchronization—keeping in mind its limitations (no Oracle support, requires Azure subscription for cloud copy, no tape support).