Product Requirement Portal

Hello all,

on Friday the 11th I was contacted by a customer, who´s DX200 S5 ran into an error while creating snapshots. The DX200 S5 is set up as an unified system which serves NFS storage to an VMWare Cluster. The NAS volume is protected by an automated snapshot schedule directly on the DX, the build in functionality. The NAS volume has a size of roughly 50TB and the snapshot space is 13 TB. I told the customer, that is could happen, that the snap area will run out of space. The last 5 months this was working smoothly, but on Friday he moved a huge multi-TB file and the next snapshot ran into an error (that was expected as of my prediction 😊) The customer then opened a case with Fujitsu and later that day got in contact with me to support.

Quickly it was clear that the snap area was the problem, it just ran out of space. This was also the feedback from the support.

The main problem in this case was not the failed snapshot itself but the fact that the failed snap made ALL OTHER snaps unreadable and broken!!! I found a hint to this in the “Advanced Copy Function Guide” like this:

1.7.5

If the amount of updated data exceeds the available copy destination SDP/Thin Provisioning Pool (TPP)/

Flexible Tier Pool (FTRP) capacity, the copy session will fail and be unusable. Older sessions will also become inaccessible.

However, newer sessions can be accessed and the copy source can still be used normally.

Is this really true and a wanted solution? I wonder if any other customer ran into the same situation and reported this as a problem? It would be a much better solution to just fail the latest snap but leave the rest untouched! Do you possibly know of any plans to change this?

Bye

Dirk