Welcome to our community

I have a customer who has given me a brief overview of an issue with an EVA 4000.

It currently has the (95%) occupancy alarm triggered on one of the VDisks and the front page of Command View EVA 6 shows:

Total: 5,018.15GB
Used: 6,485.70GB
Available: N/A

The suspicion is that this has somehow been caused by a failure of the Data Replication service to its partner which shows some connection fails in the logs. Both EVAs are currently up and running but the presumption is replication has ceased.

Any ideas on a fix without reinitialising the controllers?

If the CA connections go down - the local 'end' will start logging, so inevitably space on the logging disk group will be used up. However, at some point (when there's no space left, or when it gets beyond a certain size) - the remote disks will be marked for 'full copy' and the logging disk(s) will be deleted, thus freeing up space.

Best place to start would be to find out what state the DR groups are in and what amount of space is utilized by the logging disk(s) - you should get this from CVEVA - and looking at the properties, or from the CA, or RSM management GUI. If CA logging is the problem, you really need to get that sorted before anything else.

You say that the occupancy alarm has been triggered by a Vdisk. If this is the case, it could still be the effect of logging activity using up all the spare disk space in the DG, but it could also be a problem with the layout of the DG's.

Hope this helps

FT

Hi,
Above note by FT obvious good info and does need to be investigated.
However, at crossed terms I think.
Occupany alarm [OA] IS NOT an individual vdisk - it is an alarm associated with a disk group.
If the OA is set to 95% for a disk group then this means that at least 95% of the available space within that disk group has been used - the term is assigned. NOTE this DOES NOT mean that this is all real data - just dg capacity that has been assigned.
Now if the alarm has gone off as you suggested then this means that you are running out of space in the dg which means you have a few options - in no particular order:
try deleting old/not used LUNs, snapshots, snapclones etc
change you disk protection level from double to single of none - you need to understand what that is used for as well
add more disks into the disk group
I doubt if the OC going off has stopped CA functioning all that really does is to alert you to the fact that you are running out of space as I said before. It does not stop you creating more LUN's etc UNLESS you actually run out of space in the disk group.
Hopefullt FT's suggestions and the above will help out but if not you will need to provide more info and maybe someone will be able to give more advice.
MEA[T]

Thanks for the replies, I have forwarded them on to our chap on site who is dealing with it. The issue we have is it's a new contract we've inherited and the majority of the kit there we don't normally support. Additionally, it's a secure site so information out is limited.

The site team have finally got a response from HP support (after waiting for almost 3 weeks) and they believe the root cause is a bug in the version of XCS on the controllers and that a forced re-sync should cure the issue at hand before upgrading XCS.

I'll try and update as more info leaks off site.

Hi ChrisH,

Is it fixed ???

MEA[T]