Comments on: Real Case: Implement Storage Replica between two S2D clusters

By: hunter3740

hunter3740 — Thu, 30 Jul 2020 23:42:04 +0000

“As you can see in the following screenshots, I created four log volumes per cluster. The volumes are not CSV.”

but then further down, in screenshot after:
“Once the initial synchronization is finished, the replication status is Continuously replicating.”

your log volumes are showing as csv

did they convert automatically?

curious if I should new-storagePool with ‘ -storageSubsystemFriendlyName “Windows Storage*” ‘ or ‘ -storageSubsystemFriendlyName “Clustered Windows Storage*” ‘ (my first pool I had automatically created with enable-S2Dcluster and it’s 3-way and tiered with nvme journal, so figuring create second pool, no journal, just nvme as 2-way mirror

then my mind wanders: create second pools on each node; and assuming also create all log volumes on all nodes, so that when a nodeOwner changes for a data disk that’s csv, storage replica will relatively just use the non-csv on that new node

By: Romain Serre

Romain Serre — Fri, 15 Mar 2019 08:10:36 +0000

Hello,

I replicated virtual machines. Then I did a script for the customer. In case of disaster, the script is run. The replication way is reversed and VM are register in destination cluster. It works pretty well

By: Gil

Gil — Sun, 10 Mar 2019 10:15:45 +0000

what data did you replicated ? whats it Hyper-V VMs?
I’m testing a similar configuration replicating hyper-v VMs but i found it impossible to start the VMs on the DR site if i cut the replication