You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: cloud-infrastructure/virtualization-solutions/oracle-cloud-vmware-solution/disaster-recovery-to-ocvs-solution-definition/vSphere-Replication-v9.x-Configuration-Deployment-Guide/vSphere Replication - v1.2.md
+14-14Lines changed: 14 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -70,11 +70,11 @@ As of vSphere Replication v9.x there are now 2 modes of replication:
70
70
71
71
**Enhanced Replication** - New default choice
72
72
73
-
73
+
74
74
75
75
**Standard Replication** - Legacy choice
76
76
77
-
77
+
78
78
79
79
| Feature | Enhanced Replication | Standard Replication |
@@ -94,7 +94,7 @@ In OCVS this could be done with Cluster 1 being in AD1 and Cluster 2 being in AD
94
94
95
95
Cluster 2 would have different storage to Cluster 1. Cluster 1 could be VSAN or OCI Block Storage and Cluster 2 could also be VSAN or OCI Block Storage. By doing this the replicated VM data is stored on different storage to the original workloads providing resiliency against a cluster/AD outage.
96
96
97
-
97
+
98
98
99
99
The downsides of using vSphere Replication in this way is that it requires vCenter to do the recovery of VMs, and if the outage impacts the vCenter server, then recovery becomes harder to do and could possibly require the assistance of VMware support.
100
100
@@ -114,11 +114,11 @@ Right lick on the host/cluster/resource pool within vCenter and select "Deploy O
114
114
115
115
You will then be prompted to select the required files as shown below
You then follow the prompts, and you will eventually be asked to pick the network for the OVF deployment
124
124
@@ -174,7 +174,7 @@ Once this has been completed you are able to configure a new site pairing betwee
174
174
175
175
You have the option to peer with a vCenter in the same or different SSO domain, with OCVS it is most likely that your vCenter servers/SDDCs will be in different vSphere SSO domains.
When configuring replications for VMs, you will be offered the choice between Standard and Enhanced Replication, the default should always be Enhanced for new replications.
194
194
195
195
You will select the VMs you wish to replicate and protect.
Once this has been completed you will see this screen
212
212
@@ -264,7 +264,7 @@ Now you can pick which cluster/host/resource pool the VM will sit in
264
264
265
265
As mentioned in the yellow box, the recovered VM will not be connected to any network, this is done to avoid all possible chances of conflict across the network. So as part of your recovery process you will have to connect the VMs vnic to the required network after the recover has completed.
If the original source VM is still in the inventory of the vCenter, you can remove it from the inventory *but do not delete from disk**. The vmdks can now be used as seeds, so only replicated changes need to be transferred minimizing the amount of time and b/w needed to get the replication running.
290
290
@@ -294,11 +294,11 @@ If this has been done correctly you will see the following information and be gi
294
294
295
295
vSphere Replication will automatically map the seed disks, but if for some reason it maps them incorrectly you can modify the selection. **please be careful as if you map them incorrectly it could cause unrecoverable data loss.**
0 commit comments