DDVE Testing & Feedback of Major issues?

Question

I was curious how one should go about leveraging support and investigation of any major problems or unexpected behavior seen with the DDVE preview.  In my case, I had some kind of major crash/panic of a DDVE where I couldn't even log into the web admin or terminal, and we saw the VM console spewing a wall of text.  I had to hard reset the VM and it seemed to boot up just fine.  Granted my DDVE is in a test lab and I have not configured the VM 100% as per the recommendations, but the issue seems major enough that I'd assume EMC would want to gather info and confirm if a bug unique to the code or DDVE itself, or my lack of proper config. As FYI, here is what I had to skip in configuration, as it seemed the test lab ESX environment would not allow these settings, but they don't seem anything too major that I would think to be the cause: - All the disk of the DDVE had to be Thin Provisioned, no option to choose anything else. - CPU & Mem reservations had to be disabled to power on the VM, due to HA cluster config.  Shouldn't be an issue as the test ESX cluster only runs about 30% on either value per esx host, and never even comes close to max. Other facts: - I only have been testing with on-demand test jobs from networker and avamar, and the system operated fine during that testing.  The system was basically inactive and had no backups writing to it when it crashed. - I had filled a 200gb filesystem at the start of testing.  Ran cleaning which cleared 75gb, and then expanded the filesystem with another 300gb disk.  Then I didn't touch the system for about a week and crash occurred sometime in that timeframe. If EMC wants to reach out to me privately for more info on the issue, that would be just great...

BenjaminMclauch · Answer

Hello - I would like to review your support bundle - can we link up so i can check your logs pls?

sethfullyclean2 · Answer

Yes, link away, or contact me privately please.

BenjaminMclauch · Answer

pls email me on benjamin.mclauchlan@emc.com

sethfullyclean2 · Answer

I did some checking and there was an issue with the underlying NFS storage used for that VM datastore that we weren't aware of.  That should explain the issue I saw.  Sorry to have wasted your time.

Data Domain

Was this post helpful?