misterlucio wrote:
Thank you for your reply.
4 out of 6 hosts have the operating system installed on the internal RAID1. the other 2 hosts have the operating system installed on a volume of the 3par. the "vm disk erros" appear on all hosts. the 3par continues to report no problems. we have already restarted one node from the two controller nodes so that the other is the active one. the problems continue. in between is another SAN switch (Cisco NX-OS(tm) m9100). this also reports no errors.
the next step will be that we don't need the san switch anymore, but connect the 3par and the blade system directly. basically the san switch is not really needed anymore.
In a 3PAR system, all nodes are active and serving IO (one hold the master role which is basically management networking). So that reboot of a node did nothing.
Do you understand what Veeam considers «VM disk errors»? I might be wrong but my understanding is that this is a very wide term and the counter doesn’t have to mean an actual error but simply something «not optimal». So unless you are sure about what the counter means I would start by logging a case with veeam. Eliminating other stuff doesn’t really help you because if/when it disappears you have no idea what the actual problem or resolution was.