vSAN1

Hi, we are planning a DRP test in our vSAN Streched Cluster. We will be shutting down an entire site for, at least, 4 hours. As this is a planned scenario we will change the Object Repair Timer for 6 hours, at least. How can we know or track how much time vsan needed to copy the deltas from the alive site to the outage site once it is productive again?

Hello Lucas,

"As this is a planned scenario we will change the Object Repair Timer for 6 hours, at least."

Actually this shouldn't matter at all with a Fault-Domain/Site unavailable there will be no repair resync until that site is available again - think of it like a 3-node cluster usign FTT=1,FTM=RAID1 with one node gone, there is no applicable location to start resync that would not violate the Storage Policy.

"How can we know or track how much time vsan needed to copy the deltas from the alive site to the outage site once it is productive again?"

This is a 'how long is a piece of string' question - it depends entirely on the particular piece of strings length :smileygrin:

The amount of data that will have to be resynced is the amount of data that has been changed in the sites absence.

How fast this will resync depends on the storage and network capabilities of the cluster and how much other workloads contend with this.

Bob

Thanks for your reply bob. I'm not asking for an ETA. I'm asking the log where we can keep track of the delta syncronization once the failed site come back to life

Hello Lucas,

No need to look in the logs - this information is visible from the UI:

Cluster > Monitor > vSAN > Resyncing Components.

Or from RVC:

> vsan.resync_dashboard <pathToCluster>

Bob

Thanks! The vsan delta copy process will appear in the resyncing components? I thought that that information, or the resync_dashboard info were for objects migrating for one diskgroup to another,

Yes it should show there (in modern vSAN versions at least) - should show these as 'Intent' 'Compliance'

Bob