I have a 2-node mode VAS installed and running for few weeks in our lab. Some how, after a power outage, the esx servers power up when power recovery. Everything works all right for a day. But suddenly, VSADs-0 and VSADs-1 became inactive and all the VMs were inaccessible. After browsing the internet, that might be VSA-0 or VSA-1 went to the maintance mode. I checked it from VAS manager and from console. And i found out one of the VSA machine kept reboot itself just 5 mins after it complete startup and showing the prompt. And the other VSA member won't pick up the job, whole system went offline.

Because I spent few days within a testing machine within the VSA cluster, I relly like to clone/mirgate this VM out. Any one could help? either extract the VM files from crash VSA or recover to whole VSA.

I'd suggest a first step might be to look at the log files on one of the appliances to try determine why the cluster went offline in the first place and is not coming back online. You can log into the appliance via the console using svaadmin user and look at the following log file /var/log/sva.log to see what exceptions are present. Perhaps you could post the details here

Also you could try the steps listed in this article. Posting the results here from 'getSvaServerInfo' for each VSA node might also help us to further troubleshoot

There's nothing obvious indicating the source of the problem from the details you've provided so far. You could try getStorageCluster command also from WSCLI using below command which might help give us more insight. Also, there should be a small period (~30 seconds) before the troublesome node reboots again when it is attempting to come online. You could try ping the front end and back-end IP addresses during that window to see if either respond or not.

After endless reboot of troublesome VSA, it became more unstable. It only will last a few seconds after complete restart. I did not see how can I repair it and I returned the server back. And the server was reinstalled another OS for other purposes.

For storage log please refer to attached text file.

Really appreciate your time. And I am kind of giving up to fix it since there is not a quick fix exist.