The problem was that the volumes being vacated were VM datastores being used so the number of read/writes that EQL was handling was very big. So I storage vMotion the VM's off those datastores/volumes and the vacating process took up the speed again. So lessen learned. Don't remove an array where the volumes to be vacated are being heavily used/accessed.
Hi I'm vacating an array from a group. I started the task yesterday and it has gone well until recently it seems to be stuck at 71% and the webinterface takes ages to load and show data, also I'm receiving warning e-mails about snapshots failing and other member port not being reached. I guess the eql group is overloaded. What can I do at this point? Do I need to be worried? Or is this normal and what can I expect?
Worried about loosing data