Architectural Decisions to maximize ANF investment in HANA N+M Scale-Out Architecture - Part 1

Hi Moaz,

Thanks you so much for this nice blog. Very nicely constructed, have very concise and to the point info. I really liked it.

I have question, you suggested to have one ANF Account per region to host hana volumes (hana/data, hana/log. hana/shared/ data/backup and log backup and non-hana volumes) for all the systems across all the landscapes(sbx, dev, qa, uat and prod) so by doing this we will forcing all the systems in single PPG and single DC or we can pin single ANF Account to multiple PPG(i think it is not possible). And if pining is based on the ANF Capacity pool then my question is, can we pin different capacity pool(in same ANF account) to different PPG's.

Actually we have different ANF Account and PPG's for each landscape(sbx, dev, qa, uat and prod) so how we will do the system refresh to another landscape because we can restore the ANF snapshot to the same Vnet/subnet, ANF account and capacity pool.

Again it is very nice blog and we have been waiting for the next part of it.

Thanks in advance.