Azure Recovery Services Scout 8.0.1: Navigating Feature & Platform Support Post-Upgrade

Table of Contents

Azure Recovery Services Scout 8.0.1 represents a significant update that impacts the features and platform support for users of Azure Site Recovery. This version discontinues support for several key functionalities and platforms that were available in previous iterations. Specifically, features like Application Protection, Peer-to-Peer (P2P) replication, Backup Solutions, virtual snapshot capabilities, and support for Unix-based platforms are no longer supported in Azure Recovery Services Scout 8.0.1. While these options might still appear within the product interface, their continued use is not endorsed and falls outside the scope of Microsoft’s standard support agreement. Users are strongly advised to review the end-of-life (EOL) support depreciation list to gain a comprehensive understanding of the features and configurations that are no longer supported.

It is important to note that the feature set offered in Azure Recovery Services Scout 8.0.1 is designed to be functionally equivalent to the InMage vContinuum feature set. For users seeking a detailed breakdown of the functionalities included in Azure Recovery Services Scout 8.0.1, the compatibility matrix serves as a crucial resource. This document provides an exhaustive list of supported features and configurations. Furthermore, Microsoft has ceased the distribution of ScoutOS ISOs across all versions. Consequently, users are now required to independently download the necessary CentOS ISO from the internet. Following this, they must manually install the prerequisite packages before proceeding with the installation of RX.

Deprecated Solutions (Not Supported)¶

Several solutions and features have been deprecated in Azure Recovery Services Scout 8.0.1 and are no longer supported. These changes impact how users can leverage the platform for protection and recovery purposes. Understanding these deprecated solutions is critical for planning and adapting disaster recovery strategies. The removal of these features necessitates a review of current configurations and potentially requires the adoption of alternative methods for achieving similar functionalities.

The following solutions are no longer supported:

• Any Application aware features: This includes protection, failover, and failback capabilities for a wide range of applications such as MSSQL, File Server, MS Exchange, Oracle, Oracle RAC, DB2, MySQL, SharePoint, and BES. The discontinuation of application-aware features means that recovery processes might require more manual intervention and could potentially lead to longer recovery times for these applications. Users relying on application-aware recovery will need to reassess their strategies and consider alternative approaches or solutions for application consistency and recovery.
• Backup features: A range of backup-related features are also deprecated. This includes Virtual Snapshot, backup validation, volpack, long-term retention, and Scout Mail Recovery. The removal of these features significantly alters the backup capabilities within Azure Recovery Services Scout 8.0.1. Users who previously utilized these features for data protection and retention will need to explore alternative backup solutions to maintain their desired data protection levels. The absence of long-term retention, in particular, might necessitate a shift in data archiving and compliance strategies.
• Fx and any Fx based solutions: Solutions based on Fx technology are also no longer supported. The specifics of “Fx based solutions” would require further context, but generally, this indicates a deprecation of a certain architectural approach or technology within the Azure Recovery Services Scout framework. Users who have deployed solutions relying on Fx components need to understand the implications of this deprecation and identify migration paths or alternative solutions.

Deprecated Deployment and Configuration (Not Supported)¶

Beyond specific features, certain deployment configurations that were previously possible are now deprecated and unsupported in Azure Recovery Services Scout 8.0.1. These changes in deployment support directly affect the architecture and scalability options available to users. Understanding these limitations is vital for designing and maintaining compliant and supported disaster recovery environments. The restrictions on deployment configurations may require adjustments to existing infrastructures or necessitate a rethinking of deployment strategies for new implementations.

The following deployment and configuration options are no longer supported:

• 1 to many replications: The ability to replicate a single source to multiple targets is no longer supported. This deprecation impacts scenarios where a centralized source needed to be protected across multiple recovery sites simultaneously. Users who relied on one-to-many replication will need to re-architect their replication strategy, potentially employing multiple one-to-one replications or exploring alternative solutions that cater to multi-site recovery needs. This change could increase the complexity and resource requirements for maintaining redundancy across multiple locations.
• CX HA (Configuration Server High Availability): High availability configurations for the Configuration Server (CX) are no longer supported. The removal of CX HA implies a single point of failure for the configuration management component of Azure Recovery Services Scout 8.0.1. Users need to consider the implications of this single point of failure on their overall disaster recovery posture. Mitigation strategies might involve enhanced monitoring, robust backup and restore procedures for the Configuration Server, or alternative architectures that minimize the impact of CX unavailability.
• Standby CX: The use of a standby Configuration Server is also deprecated. Similar to the removal of CX HA, the deprecation of a standby CX further emphasizes the single-instance nature of the Configuration Server in Azure Recovery Services Scout 8.0.1. The rationale and implications are similar to the removal of CX HA, requiring users to adapt their operational procedures and infrastructure design to account for the potential unavailability of the Configuration Server.

Deprecated Platforms (Not Supported)¶

Platform support has also been significantly revised in Azure Recovery Services Scout 8.0.1. This version removes support for several operating systems and environments that were previously compatible. These platform deprecations are crucial for ensuring compatibility and avoiding unsupported configurations. Users operating in environments that utilize these deprecated platforms must understand that Azure Recovery Services Scout 8.0.1 is no longer a supported solution for these systems.

The following platforms are no longer supported:

• Linux CX (Configuration Server and Process Server): Running the Configuration Server and Process Server components on Linux operating systems is no longer supported. This indicates a shift in the supported operating system for these critical components, likely towards a Windows-centric approach. Users who previously deployed these servers on Linux will need to migrate them to a supported operating system, which may involve infrastructure changes and migration efforts.
• Ubuntu: The Ubuntu Linux distribution is no longer supported. This deprecation affects users who utilized Ubuntu servers within their protected infrastructure. These users will need to transition away from Ubuntu for systems intended to be protected by Azure Recovery Services Scout 8.0.1, potentially migrating workloads to other supported operating systems.
• RHEL4 (Red Hat Enterprise Linux 4): Support for Red Hat Enterprise Linux 4 has been removed. Given the age of RHEL4, this deprecation is likely part of a broader effort to modernize supported platforms and align with current enterprise operating system standards. Users still running RHEL4 systems need to upgrade to a supported version of RHEL or migrate to a different supported operating system if they intend to use Azure Recovery Services Scout 8.0.1 for protection.
• Debian: The Debian Linux distribution is also no longer supported. Similar to Ubuntu and RHEL4, this deprecation narrows the range of Linux distributions compatible with Azure Recovery Services Scout 8.0.1. Users relying on Debian will need to consider alternative operating systems for their protected workloads.
• AIX (Advanced Interactive eXecutive): IBM’s AIX operating system is no longer supported. This deprecation impacts users with AIX-based systems in their environment. Protecting AIX workloads with Azure Recovery Services Scout 8.0.1 is no longer a viable option, and users need to explore alternative disaster recovery solutions for these systems.
• Solaris: Oracle Solaris is also among the platforms no longer supported. The removal of Solaris support affects organizations that utilize Solaris-based servers. Like AIX, Solaris users will need to seek alternative disaster recovery solutions, as Azure Recovery Services Scout 8.0.1 is no longer compatible with this platform.

Deprecated Hypervisors (Not Supported)¶

The scope of supported hypervisors has also been adjusted in Azure Recovery Services Scout 8.0.1, with significant implications for virtualized environments. The changes primarily revolve around virtual-to-virtual protection scenarios and the supported target hypervisors for physical-to-virtual conversions. These hypervisor deprecations are crucial for users in heavily virtualized environments to understand and adhere to the compatibility limitations.

The following hypervisor scenarios are no longer supported:

• All virtual to virtual scenarios are deprecated (except VMware 5.1 and 5.5): With the exception of VMware vSphere versions 5.1 and 5.5, all virtual-to-virtual protection scenarios are deprecated. This represents a major shift in the supported virtualization landscape. Protecting virtual machines running on hypervisors other than VMware 5.1 and 5.5 in a virtual-to-virtual manner is no longer supported by Azure Recovery Services Scout 8.0.1. Users with diverse hypervisor environments will need to carefully assess the implications of this limitation and potentially reconsider their disaster recovery architecture.
• For Physical to Virtual, target has to be VMware 5.1 or 5.5: In physical-to-virtual scenarios, the target hypervisor is restricted to VMware vSphere 5.1 or 5.5. This constraint limits the flexibility in choosing target virtualization platforms for physical server recovery. While physical-to-virtual recovery remains an option, the target environment must specifically be VMware 5.1 or 5.5. Users need to ensure their target infrastructure aligns with this requirement when planning for physical server protection. For source details in physical-to-virtual scenarios, users are advised to consult the Azure Recovery Services Scout 8.0.1 compatibility matrix for a comprehensive list of supported source platforms.

Additional Considerations¶

Beyond the deprecated features, deployments, platforms, and hypervisors, there are other important considerations for users of Azure Recovery Services Scout 8.0.1. These points further define the limitations and operational parameters of this version.

• Maximum supported retention size is up to 15 days: The maximum supported retention period for recovery points is limited to 15 days. This constraint impacts data retention policies and recovery point objectives (RPOs). Users requiring longer retention periods for compliance or operational reasons will need to consider this limitation and potentially implement supplementary backup or archiving solutions to meet their data retention needs.
• Appliances using InMage Scout products are no longer supported: Physical or virtual appliances that are based on InMage Scout products are no longer supported. This deprecation likely targets older hardware or pre-packaged solutions that were previously offered. Users who deployed such appliances need to understand that they are no longer supported and should transition to supported deployment models or alternative solutions. The specifics of “appliances using InMage Scout products” would require more detailed product history, but generally indicates a move away from appliance-based deployments.

It is highly recommended to thoroughly review the official Azure Recovery Services Scout 8.0.1 compatibility matrix and end-of-life documentation to gain a complete understanding of all changes, deprecations, and supported configurations. This information is crucial for ensuring a smooth transition and maintaining a supported and effective disaster recovery environment.

If you have any questions or experiences regarding the Azure Recovery Services Scout 8.0.1 update, feel free to share them in the comments below!