Action Required: Update Your Microsoft Azure Recovery Services Agent (November 2017)

Table of Contents

This article provides essential information regarding key updates, new features, improvements, and important fixes delivered in version 2.0.9099.0 of the Microsoft Azure Recovery Services (MARS) Agent. This agent is a crucial component utilized by Microsoft Azure Backup and Microsoft Azure Site Recovery (ASR) solutions to facilitate the secure and efficient transfer of data from on-premises Windows servers and clients directly to Azure Recovery Services vaults. Maintaining the MARS agent at the latest version is critical for ensuring optimal performance, leveraging new capabilities, and benefiting from crucial stability and security enhancements. This particular update brings significant advancements, most notably the general availability of System State backup, alongside important feature enhancements and bug resolutions.

System State Backup Achieves General Availability¶

A major highlight of the MARS Agent version 2.0.9099.0 is the announcement that System State backup is now generally available across all Azure regions. Previously in preview, this feature provides robust protection for the core configuration of Windows servers, complementing file and folder backups for comprehensive disaster recovery scenarios. System State backup includes vital operating system components and configuration settings necessary to restore a server to a functional state without performing a full bare-metal recovery, which can often be more time-consuming.

This generally available release offers full production support for safeguarding the system state on various critical server roles. This includes Windows file servers, which hold file system configurations and permissions; Active Directory domain controllers, essential for identity and access management within an organization; and IIS web servers, vital for hosting web applications. Support is provided across a wide range of Windows Server versions, specifically from Windows Server 2008 R2 through to Windows Server 2016. The System State backup capability significantly enhances the disaster recovery posture for these critical infrastructure components.

Protecting the System State alongside traditional file and folder backups ensures a more complete recovery strategy. Should a system failure occur affecting the operating system or core services, having a recent System State backup allows for a granular restoration of these critical configurations. This capability is particularly valuable for Active Directory, where restoring the System State of a domain controller is a standard method for recovering directory services. Integrating System State backup into existing policies using the MARS Agent is designed to be straightforward, typically adding minimal overhead to the overall backup size sent to Azure, making it an efficient addition to your data protection plan. Microsoft provides detailed documentation to assist users in getting started with backing up and recovering the system state using the MARS Agent, outlining the steps from initial configuration through to executing a recovery operation.

New Features Introduced¶

Beyond the general availability of System State backup, this release of the MARS Agent introduces valuable new features that enhance the flexibility and manageability of your backup operations, particularly concerning System State protection. These features are designed to provide administrators with more granular control over their backup policies and enable automation for managing protection at scale.

Flexible Backup Schedule and Retention Policy for System State¶

A key enhancement in version 2.0.9099.0 is the introduction of flexible scheduling and retention options specifically for System State backups. Administrators now have the ability to configure daily System State backups at a preferred time that aligns with their operational windows and recovery point objectives (RPOs). This level of control ensures that System State backups are taken consistently and at a time when the impact on server resources is acceptable.

In addition to scheduling, the update provides enhanced control over how long System State recovery points are retained. Users can now define specific retention ranges for daily, weekly, and monthly System State backups. This allows organizations to adhere to compliance requirements and internal data retention policies more effectively. The ability to set distinct retention periods for different backup frequencies provides a more granular and cost-optimized approach to managing backup data stored in Azure. This flexibility ensures that critical System State recovery points are available for the necessary duration while optimizing storage consumption.

PowerShell Support for System State Backups¶

Recognizing the importance of automation in managing large-scale environments, this MARS Agent release includes comprehensive PowerShell support for System State backups. PowerShell cmdlets are now available to configure, execute, and manage System State backup and recovery operations programmatically. This enables administrators to automate the deployment and configuration of System State protection across numerous Windows servers using scripts, saving significant administrative time and reducing the potential for manual configuration errors.

PowerShell support extends to setting up new System State protection policies, initiating on-demand System State backups, and performing System State recovery operations. This level of automation is invaluable for environments with a large number of servers requiring consistent backup configurations. By integrating System State backup management into existing automation frameworks, organizations can streamline their data protection workflows and ensure consistent application of backup policies across their infrastructure. The availability of PowerShell cmdlets empowers IT teams to manage their Azure Backup environment more efficiently and at scale.

Key Improvements and Fixes¶

This update also incorporates several important fixes and general improvements aimed at enhancing the reliability, compatibility, and user experience of the MARS Agent. These fixes address specific issues that users may have encountered in previous versions, ensuring smoother backup operations and more reliable recovery capabilities. Addressing these issues is crucial for maintaining the integrity of backup data and the ability to recover systems effectively when needed.

The update resolves an issue that caused backup failures on Windows 10 clients running the RS3 Fall Creators Update. Previously, users on this specific version of Windows 10 might have encountered an error message related to the Virtual Disk Service (VDS), preventing backups from completing successfully. The error message “The backup could not be started because of an unexpected error in the virtual disk service. Restart the virtual disk service and try the backup operation again. If the issue persists, check the system event log for virtual disk service events. (0x086C6)” is now resolved by this update. The Virtual Disk Service is integral to creating volume shadow copies required for point-in-time backups, so resolving this VDS-related issue is critical for ensuring backup functionality on affected systems.

Another significant fix addresses an issue that led to failures when backing up compressed or encrypted files. In prior versions, attempting to back up data that was compressed or encrypted at the file system level could result in an inconsistency detection error during the verification phase of the backup process. This would prevent the creation of a valid recovery point and trigger an error message: “Microsoft Azure Recovery Services Agent has detected inconsistencies while verifying the latest backup. A new recovery point could not be created. The next backup will attempt to transfer the data again. If the issue persists, contact Microsoft support (0x086D5)”. This fix ensures that the MARS Agent can reliably back up compressed and encrypted data, preserving the integrity and recoverability of such files.

Furthermore, this release fixes an issue affecting users performing Offline backups when integrating the MARS Agent with System Center Data Protection Manager (SCDPM) or Azure Backup Server. The issue prevented users from modifying offline backup parameters after an offline backup job had been initially configured. Offline backup is a method used for the initial seeding of large datasets to Azure, and the ability to modify parameters after configuration is important for flexibility and error correction. This fix restores the expected behavior, allowing necessary adjustments to be made to offline seeding configurations.

Finally, the update includes several accessibility fixes and general improvements. While not tied to specific error codes or functionalities, these enhancements contribute to a more inclusive and user-friendly experience for administrators interacting with the MARS Agent interface and processes. General stability improvements and performance optimizations are often part of such updates, contributing to the overall robustness of the agent.

Here is a summary of the key fixes included in version 2.0.9099.0:

Issue Category	Description	Error Code (if applicable)
Backup Failure on Windows 10 RS3	Backups fail due to an unexpected error in the Virtual Disk Service.	0x086C6
Compressed/Encrypted File Backup	Backup verification detects inconsistencies when backing up compressed or encrypted files, preventing RP creation.	0x086D5
Offline Backup Parameter Modification	Unable to modify Offline backup parameters after initial configuration in SC DPM/Azure Backup Server scenarios.	N/A
Accessibility & General Stability	Various improvements to enhance accessibility and agent stability.	N/A

How to Apply the Update¶

To benefit from the new features, improvements, and critical fixes included in version 2.0.9099.0, it is highly recommended to update your Microsoft Azure Recovery Services Agent on all protected servers and clients. Keeping the MARS Agent updated is essential not only for new functionalities but also for applying the latest security patches and ensuring compatibility with ongoing Azure service updates. The update process is straightforward and can be performed by downloading and installing the latest agent package.

The necessary installer package for this update is available for download directly from the Microsoft Download Center. You can obtain the file by navigating to the Microsoft Download Center website and searching for the Azure Recovery Services agent update or using the direct download link provided in the original announcement. The file name for this specific version is typically in the format MARSAgentInstaller.exe. It is important to download the installer file to a location accessible by the server or client machine where the MARS Agent is installed.

The version number for this specific update of the Microsoft Azure Recovery Services Agent is confirmed as 2.0.9099.0. Verifying the version number after installation is a good practice to ensure the update has been successfully applied.

For environments with multiple servers registered to one or more Azure Recovery Services Vaults, Microsoft provides a convenient method to manage updates directly from the Azure portal. This centralized approach helps administrators track the agent versions across their protected infrastructure and initiate updates efficiently. To update multiple servers using the Azure portal, follow these recommended steps:

1. First, download the latest installer package (MARSAgentInstaller.exe) from the Microsoft Download Center to a secure location. This file will need to be transferred to your protected servers.
2. Navigate to the specific Recovery Services Vault in the Azure portal where your servers are registered for backup or site recovery.
3. Within the Recovery Services Vault blade, locate and click on Backup Infrastructure under the Manage section of the settings menu. This section provides details about the components used in your Azure Backup configuration.
4. Under Management Servers, click on Protected Servers. Here, you will see a list of servers registered to the vault. Ensure that “Azure Backup Agent” is selected as the Backup Management Type to filter the list to show only servers using the MARS agent directly.
5. Review the list of protected servers and identify those for which the currently installed Agent version number is earlier than 2.0.9099.0. Select a server that requires the update. On the server’s detail blade that appears, you will find information about the server, including its current agent version. Click on the Connect option. This action will typically download a Remote Desktop Connection (.rdp) file, allowing you to establish a remote session to the selected server.
6. Once connected to the server via Remote Desktop, copy the previously downloaded MARS Agent update installer file (MARSAgentInstaller.exe) to the server. Execute the installer file on the server to begin the update process for the MARS Agent. Follow the on-screen prompts to complete the installation.
7. After successfully updating the agent on one server, you can return to the Azure portal, select other servers that still have agent versions earlier than 2.0.9099.0, and repeat the process of connecting via RDP, copying the installer, and running the update. This allows you to systematically update all necessary MARS agents registered to that vault.

This method streamlines the process of identifying outdated agents and provides a direct way to access the servers requiring updates, especially useful in large environments where manual tracking might be cumbersome.

Restart Information¶

For users who have the MARS Agent installed on specific older versions of Windows Server, a system restart may be required after applying this update to ensure the changes take full effect. If your server is running Windows Server 2008 (either SP2 or R2 SP1, regardless of the specific edition), it is necessary to restart the computer after the successful installation of the MARS Agent update version 2.0.9099.0. This ensures that all components are correctly initialized with the updated version.

However, if you have installed the MARS Agent on any other supported Windows Server versions newer than Windows Server 2008 R2 SP1, you are generally not required to restart the computer after applying this update. The update process for these newer operating systems is designed to integrate the changes without necessitating a system reboot. Always refer to any specific instructions provided by the installer itself, but the general guideline is that only Windows Server 2008 (SP2/R2 SP1) requires a restart.

Replacement Information¶

This update for the Microsoft Azure Recovery Services Agent, version 2.0.9099.0, is designed to replace any previously released versions of the agent. Specifically, this update supersedes and replaces the update detailed in Microsoft Knowledge Base article KB 4041236. If you have a previous version of the MARS Agent installed, installing version 2.0.9099.0 will automatically upgrade your agent to the latest version. It is not necessary to uninstall previous versions before applying this update; the installer handles the upgrade process. Ensuring you have the latest version is crucial for optimal performance and access to the newest features and fixes.

Prerequisites¶

Before applying the Microsoft Azure Recovery Services Agent update version 2.0.9099.0, especially if you are integrating the MARS agent with System Center Data Protection Manager (SC DPM) or Azure Backup Server, there are certain prerequisites regarding the version of DPM or Azure Backup Server you are running. Meeting these prerequisites ensures compatibility and proper functioning of the integrated backup solution.

If you are utilizing System Center 2016 Data Protection Manager (SC DPM) as your backup management platform, Microsoft strongly recommends that you have at least Update Rollup 1 for System Center 2016 Data Protection Manager installed, or a later version. Applying Update Rollup 1 or a subsequent update ensures that your SC DPM environment is compatible with the latest features and changes introduced in the MARS Agent update.

Similarly, if your environment is running System Center 2012 R2 Data Protection Manager (SC DPM), it is recommended to apply Update Rollup 12 for System Center 2012 R2 Data Protection Manager or a later version. Maintaining an up-to-date version of SC DPM is essential when using it in conjunction with the MARS agent for managing backups to Azure. These prerequisites ensure seamless integration and reliable data transfer capabilities between your DPM server and Azure Recovery Services vaults. Always check the documentation for your specific DPM version and the MARS agent for the most current compatibility requirements.

Maintaining the MARS Agent, along with any integrated components like SC DPM or Azure Backup Server, at supported and updated versions is a critical aspect of a healthy and reliable backup infrastructure. This update provides valuable new capabilities and fixes, enhancing the overall effectiveness of your Azure Backup and Azure Site Recovery solutions.

Have you applied this update to your MARS Agents? What has been your experience with the new System State backup feature? Share your thoughts and questions in the comments below!