#SVM mobility with fabric pool
1 messages · Page 1 of 1 (latest)
I don't think it matters if the source aggregate is FlashPool or not. SVM Mobility is basically SnapMirror, and for that it doesn't really matter if the blocks are on HDDs or SSDs
But I thought that FlashPool and S3 Tiering (FabricPool) could not be combined 🤔
correct, you can't do flashpool and fabircpool on the same aggr.
@waxen stone - here's the support features https://docs.netapp.com/us-en/ontap/svm-migrate/#supported-and-unsupported-features
Is the local tier FabricPool? I'm assuming no since you say FlashPool (which isn't supported AFAIK). What are you trying to accomplish exactly and what is your hangup(s) that we can help with?
It is fabricpool on the local tier (local s3) yes, typo. I was attempting to use SVM mobility to migrate to a new cluster but noticed that the only support for fabricpool is on azure netapp files