MSA 2060 iSCSI Virtual pool overcommitment

[JakubS93]

Hi,

In March we have purchased two new MSA 2060 iSCSI SANs. They have been configured to run about 70% of their capacity as backup storage for Veeam. Yesterday I went to check on it and I am seeing an error on the health page stating "A virtual pool exceeded its threshold for allocated pages, and the virtual pool is overcommitted." (Unfoaruntely the notifications were configured incorrectly and I wasn't aware of this earlier)

I then went to check the actual volume on the veeam server and I cannot access it at all, the disk is showing as raw. I cannot access the data. 

On the SAN itself, it's reporting as healthy- the pool is 31.1TB with 4.795TGB spare. I had the pool overcommit enabled (now I can see this was a mistake).  But the actual overcommit is 0 so I am baffled by what is happening? 

I have stopped backing up to the other SAN and I'm offloading the data to a spare NAS we have just in case. This SAN is showing the same error but it still works and the data is accessible. Can someone suggest the steps to perhaps rectify this?

I have tried the following things:

-Rebooting the MC

-Rebooting both SC

-Power cycling the unit

-Disconnecting the volume from the host

I would appreciate any insignt.

Thank you

EDIT: It's suggesting to expand the storage, so I will do that on the functining SAN but I really need to get the other one working. 

[JonPaul]

@JakubS93 
I would really recommend working the HPE support as you are currently unable to access your data.
There is a lot to unpack and the support team would need the system logs.

[JakubSACS]

Hi Jon Paul,

I had to make a second account- thank you for the suggestion. The second I typed this post I reaslied the SAN's are under warranty. I have an active case with HPE now. 

Thank you