I can but in the mean time I have a log of the SW service crashing if that's any help?

Ok, thanks. I've been testing the VSA without much success. Initially it booted and configured fine. I created a 1TB volume and connected an ESXi bok to it. Mounted fine and created a Datastore. I used a testing VM with Server 2016 to run a disk benchmark using ATTO and the performance was a good bi...

Thanks, that was it. The new documentation was much clearer.
I see the VSA is not licensed for LSFS devices. Is there a specific reason for this?

It worked connecting the VSA to a local management console. However, logging in and it tells me there are no disks configured for storage in the VSA and to go to the web interface https://10.10.1.154:9090/ to configure them. I tried the URL and it opens a StarWind Virtual Storage Appliance login pag...

Hi

Oh, I thought from reading the docs the VSA was supposed to have everything bundled, including the management console?

Hi

I just downloaded and deployed the latest VSA as a new VM on ESXi. Installed and boots fine, gets an IP from DHCP but nothing appears when I try the IP in a browser.
I can ping the VM but no web interface to manage it.

Any ideas?

Update:

So I created a new test flat disk with L2 WB cache and ran the powershell script. It finished successfully.
However, when I try run the script on any of the existing image files I get the error above.

Hi

We've tried to run this script in a test environment and keep getting the following error:

Start flushing...Exception The variable '$raw' cannot be retrieved because it has not been set.

Any ideas?

Cheers guys, going to test this on our lab environment before we schedule any production downtime.

Hi

Yes we have been told that since and are planning to disable the WB cache once we can safely flush the current cache data to disk and stop the service without corruption occurring.

Hi

We only have a single SW node. No HA in use.

Thanks

We've done both stopping the service and shutdown, the behavior is the same either way. The problem is that we can't risk stopping the service or shutting down again until we can first force a cache flush to disk. If we try stop the service again we will have the same corruption issue are my origina...

We have tried this by shutting down all VMs running on the datastore and shutting down all the hosts after that. Then we left it about 15 mins and tried to shutdown the SW server assuming that all pending writes in the L2 cache had been written out but the SW server sat there for an hour trying to s...

Are any of the Admins able to offer advice on how we can safely shutdown SW so we can disable L2 cache?

Is there a command we can run somewhere to force a cache flush to disk?

Hi Yes, I would happily disable L2 cache at this stage but the problem is that if I try to stop the SW service to upgrade SW or reboot the server or even to just disable L2 cache and bring the targets back online i'm going to wind up with the same situation as before where all data in the L2 WB cach...