StarWind Virtual SAN for vSphere add VDO Error

mahuan1688 · Sun Mar 15, 2020 11:52 am

Hyper-v New Release is Out，Vsphere version What time？Problem have solved ?

Sun Mar 15, 2020 1:09 pm

The new release will appear at the nearest time.
Check out release notes here: https://www.starwindsoftware.com/releas ... re-vsphere

mahuan1688 · Wed Apr 29, 2020 12:37 pm

StarWind Virtual SAN for vSphere 13569 is out, but add VDO disk is also Error! ZFS is release?

Fri May 01, 2020 5:47 pm

mahuan1688,
The documentation will be available shortly on our website, however, you can use the command below to create the disk:

Code: Select all

vdo create --name=vdo_dedup --device=/dev/disk/by-id/%DRIVE_ID% --emulate512=enabled --vdoSlabSize=2G --sparseIndex=enabled --activate=enabled --indexMem=0.25 --blockMapCacheSize=256M --deduplication=enabled --vdoLogicalSize=%Size%

mahuan1688 · Mon May 18, 2020 4:02 pm

Hello, is the document ready? Are there any versions that support the ZFS file system,this version is released?

Mon May 18, 2020 4:13 pm

ZFS is supported, however, there are no documents on VDO and ZFS configuration yet.

mahuan1688 · Mon May 18, 2020 4:29 pm

Where can I see if zfs is supported, when creating the device?
Last time said that the document will come out soon, how long will it take!

Mon Jun 15, 2020 12:19 pm

ZFS works as a back-end storage with VSA. Optionally, primary path is MDRAID still due to performance reasons.

mahuan1688 wrote:Where can I see if zfs is supported, when creating the device?
Last time said that the document will come out soon, how long will it take!

mahuan1688 · Fri Aug 07, 2020 12:51 pm

By the way, is the documentation ready, about creating VDO devices!

In addition, I have two servers, servera and serverb. I would like to ask whether the witness disk is required for the high availability of the two devices, and where is the witness disk installed? Server a or server B, or add another server C and install it on server C. after the server a or B is down, they will take over each other automatically and the business will not stop.

Sun Aug 09, 2020 1:30 pm

By the way, is the documentation ready, about creating VDO devices!

Working on it.

Now let me answer your question.
Witness is required only if you build a failover cluster out of 2 Windows hosts. Learn more about Microsoft Failover Cluster quorum https://docs.microsoft.com/en-us/window ... ter-quorum.
In a nutshell, you can go with 2 servers and a witness disk.
Actually, it takes some time for the resources to failover automatically (that's how Microsoft Failover Cluster works).

mahuan1688 · Sun Aug 23, 2020 11:05 am

2-Node vSAN NFR on ESX
During the experiment, I allocated 27tb of space and set 80g of cache space. After all the configurations were normal, I shut down the host of a node. Then the virtual machine was damaged and did not take over automatically. The latest program 13586！

Sun Aug 23, 2020 12:43 pm

Could you tell me more about the experiment?
How exactly the virtual machine was damaged? Any specific errors added to this thread will be helpful. What do you mean by "take over automatically"?

Will be waiting for your answers.

mahuan1688 · Sun Aug 23, 2020 1:00 pm

Two vsans for vSphere A and B with HA shut down node A normally. All applications are not automatically linked to node B, and the virtual machine running on the storage is damaged and cannot be recovered ，back cache 80G

Mon Aug 24, 2020 3:12 am

Are StarWind HA devices in sync now?
Please note that it is necessary to run FlushCacheAll.ps1 to flush all the cache for sure. Use the IP address of the server where StarWind Service is running.
You can find the script here C:\Program Files\StarWind Software\StarWind\StarWindX\Samples\powershell.
If you are an NFR user, please log a call with StarWind Support if you require any assistance.