Appsync VMAXAFA exchange - See more than copies to keep?

Have you mounted one of those copies? If not, then you should not be seeing a third copy within AppSync. Have you filed an SR?

Thanks, we are waiting to see if another copy is created or if it is N+1.   The question is how much space will be needed of we want to keep 30 copies, each database is 70TB with ~1% change rate.  Will Appsync create differential copies, so each copy is only the increment on the last,  for example the total copy is approx.   70TB, 1 st copy with snap is 70.7TB,  2nd with snap is 71.4TB    3rd 72.1 so the 30th copy is a total of   94.3 (by the 30th the total extra snap space is only ~25tB)

Like I have mentioned, it is an N+1 but transparent to you in the UI. AppSync will never show that workflow, so you must not see three copies, when expiration is set to two. AppSync does not change the normal change rate, so please, for all concerns about sizing, consult a VMAX AFA or Microsoft (MTC) specialist. A differential copy is supported by AppSync, but this group does not consult on how much space will be used. That falls outside of the scope for the product, since it only creates the copy. The sizing is completely, 100%, up to how the array performs.

I fully understand the advantage of generation naming, but do not agree with your last statement about being storage efficient. Generational naming has zero impact/benefit on the storage space. It would not be more storage efficient. I have validated this with the VMAX group.