Best Server for VMware

Cisco UCS Archives - VMware Tech Alliances (TAP) Blog - VMware Blogs
In summer of 2014, Microsoft acquired a company called InMage Systems that specialized in building enterprise-class Disaster Recovery (DR) products supporting a wide range of platforms and operating systems. Soon after the acquisition, InMage’s flagship product for site-to-site and site-to-hoster DR became part of Microsoft Azure Site Recovery (ASR). We followed this up with the preview of Microsoft Migration Accelerator – a service based on InMage technology that enables our customers to quickly and easily migrate their workloads into Microsoft Azure with the least amount of downtime. Fundamentally, all current offerings leveraging the InMage replication channel are based on the same underlying architecture. The core components involved are:
  • Configuration Server – VM running at the secondary site that is responsible for maintaining replication policies, replication status, and health reports.
  • Master Target – VM running at the secondary site that acts as the repository for all replicated data and change journals.
  • Mobility Service – Light-weight software component that captures data changes being generated on the protected workloads continuously, in real-time and directly from memory, for replication purposes.
  • Process Server – Gateway residing at the primary site that handles all compute and IO intensive aspects of replication.
This blog post provides guidance on sizing and placement of the Process Server component for users implementing ASR with the InMage replication channel or Migration Accelerator the very first time.

What is a Process Server?

The Process Server is a gateway appliance residing at the same location as primary workloads that are being protected. It can be deployed on a physical or a virtual machine running Windows Server 2012 R2. It is responsible for receiving data changes from the primary workloads, performing compression, encryption, caching and bandwidth management, before replicating to a secondary location for DR purposes. This approach off-loads all compute and IO intensive tasks involved in continuous replication to the Process Server, thereby eliminating nearly all overheads on the protected workloads.

Process Server Placement

As a thumb rule, to obtain maximum benefits of InMage’s host off-load architecture, always provision the Process Server at the same location as your primary workloads being protected. This will ensure that compute and IO overheads on the primary workloads are nearly non-existent.

Related posts: