Changing Synchronization Journal using Powershell

[ProblemSolver823]

I am using the Starwind VSAN Free version v8-8.0_20260526_20086 on a three-node cluster that I manage with Powershell. When I update Windows, I drain all VMs from one node and verify that the starwind devices are fully synced before rebooting one the nodes. When one of the cluster nodes restarts after the update the devices go through a full synchronization that takes a long time, especially on the priority 0 device. This takes a very long time to go through this resync on three nodes. The devices are setup with a ram-based write-back cache. Based on reading in the forum, changing to a disk-based cache should help with a fast resync on reboot of one of the nodes and keep the write protection on the device without changing to a write-through for reads only. I plan to use the ModifySyncJournal. ps1 script that is packaged with Starwind to change the cache from RAM based to DISK based. I want to make sure that in using that script as to whether or not the cluster device has to be placed into maintenance mode in order to use that script or does it apply the changes in the header one node at a time so that the cluster does not have to be shutdown and stays in sync. Also, I want to verify that the path to the file-based synchronization journal must already exist but that Starwind will create the file for each device separately in that location for each device that uses a file-based sync journal. Can you please verify these two things before I run the modifysyncjournal script.