Looking at my lab, where the images are on the root of the E: drive, the permission on one file are: PS C:\Windows\system32> fileacl "E:\storage1_1.spspx" E:\storage1_1.spspx;BUILTIN\Administrators:F E:\storage1_1.spspx;BUILTIN\Administrators:F[I] E:\storage1_1.spspx;NT AUTHORITY\SYSTEM:F[...

It's taken me a while to twig what the "Clusters" interface actually does in StarWind v8, i.e. it's primarily a visual/user interface layer on top of the replication between servers. Specifically, you can remove a cluster and HA carries on working... all you've done is remove the managemen...

Hi Anatoly - I think you need to do that with the original poster jimbyau. I've got involved in this thread because I'm doing lots of lab work on v8 and HA. My lab work isn't quite finished yet.

Cheers, Rob.

Actually, you don't have to even power down. Simply restart the service and the synchronisation goes from synchronised to unsynchronised. This just seems a little odd to me. No data is being written to the storage so IMO it should not go unsynchronised just because the service is restarted. Cheers, ...

Another snippet here. In the attached screenshot, I've just shutdown the second node and it's disconnected from the console as expected. However, note that it says that the primary node is synchronised. So how come when I shut this server down and restart it, it changes to Unsynchronised? Nothing ha...

I'm still getting inconstancy here in the lab with this. Summary: SAN node #1 running SAN node #2 running Test server running using iSCSI Single LSFS storage without deduplication Perform clean shutdown: Shutdown test server and wait for iSCSI targets to disconnect on both nodes Count to 10 to allow...

Quick question over the attached dialog. Does this priority only control initial synchronisation when a HA node is created/has to be re-synced (e.g. after failure or downtime) or is it always applicable? What exactly are "client requests"? My understanding of HA (plus linked in with other ...

See attached screenshots. In sshot-36, you can see there is already storage called "Storage1". In sshot-37, I'm going through creating additional storage. This is where the bug starts to appear - it should have queried the cluster/nodes to work out the next free storage name - Storage2 in ...

Additional question - when you use the "Create clustered storage wizard", are the LSFS devices created with auto-defragmentation turned on or off? One doesn't know because a) it doesn't ask you during the wizard - just asks if you want it deduplicated or not and b) there doesn't appear to ...

A bit like in this screenshot. Cheers, Rob.

Is this by design? In sshot-33, you can see a HA set-up between SAN90 & SAN91. In sshot-34, I've removed the replica but this also removes both the target and device from SAN91. Is this by design? It freaked me out a little when I first did it ;-) One can re-attach the devices but would it not b...

Hmm, intriguing. I've just got my lab back after doing some low-level disk checks & benchmarking and I'm unable to repeat this. On the LSFS storage I've just created, the replication manager option is there. Will keep an eye on this.

Cheers, Rob.

Lab is nearly back online so some more tests this week.

It's not mission critical - more of an annoyance. If you manually type in the fully qualified server names, target naming is consistent.

Cheers, Rob.

BTW - have you tried removing disk I/O as much as possible from the equation by trying this with a RAM disk?

Cheers, Rob.