Skip to content

Commit 9a650b7

Browse files
authored
Merge pull request #108876 from davidsmatlak/ds-pr106158
Adds clarification on process server HA
2 parents 34cf651 + 2ca6dfd commit 9a650b7

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

articles/site-recovery/vmware-azure-common-questions.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,8 @@
11
---
2-
title: Common questions about VMware disaster recovery with Azure Site Recovery
2+
title: Common questions about VMware disaster recovery with Azure Site Recovery
33
description: Get answers to common questions about disaster recovery of on-premises VMware VMs to Azure by using Azure Site Recovery.
4-
author: rayne-wiselman
5-
manager: carmonm
6-
ms.service: site-recovery
74
ms.date: 11/14/2019
85
ms.topic: conceptual
9-
ms.author: raynew
106
---
117
# Common questions about VMware to Azure replication
128

@@ -63,7 +59,7 @@ Site Recovery needs access to VMware servers to:
6359

6460
### Is replication data sent to Site Recovery?
6561

66-
No, Site Recovery doesn't intercept replicated data and doesn't have any information about what's running on your VMs. Replication data is exchanged between VMware hypervisors and Azure Storage. Site Recovery has no ability to intercept that data. Only the metadata needed to orchestrate replication and failover is sent to the Site Recovery service.
62+
No, Site Recovery doesn't intercept replicated data and doesn't have any information about what's running on your VMs. Replication data is exchanged between VMware hypervisors and Azure Storage. Site Recovery has no ability to intercept that data. Only the metadata needed to orchestrate replication and failover is sent to the Site Recovery service.
6763

6864
Site Recovery is certified for ISO 27001:2013 and 27018, HIPAA, and DPA. It's in the process of SOC2 and FedRAMP JAB assessments.
6965

@@ -300,6 +296,10 @@ Updates in versions 9.24 and later now display the [health of the process server
300296

301297
Beginning with [version 9.24](service-updates-how-to.md#links-to-currently-supported-update-rollups), more alerts have been added to indicate the health of the process server. [Update your Site Recovery components to version 9.24 or later](service-updates-how-to.md#links-to-currently-supported-update-rollups) so that all alerts are generated.
302298

299+
### How can I ensure high availability of the process server?
300+
301+
By configuring more than one process server, the design provides flexibility to move protected machines from an unhealthy process server to working process server. Movement of a machine from one process server to another must be initiated explicitly/manually via the defined steps here: [moving VMs between process servers](vmware-azure-manage-process-server.md#move-vms-to-balance-the-process-server-load).
302+
303303
## Failover and failback
304304

305305
### Can I use the on-premises process server for failback?

0 commit comments

Comments
 (0)