You want to use FabricPool technology to tier SnapVault destination volumes to the capacity tier.
In this scenario, which action would you perform to accomplish this task?
You want to use FabricPool technology to tier SnapVault destination volumes to the capacity tier.
In this scenario, which action would you perform to accomplish this task?
To tier a SnapVault destination volume to the capacity tier using FabricPool technology, you should create the destination volume on a FabricPool-enabled aggregate and assign the backup tiering policy to the destination volume. This method allows the data in the SnapVault destination to be efficiently tiered to the capacity tier, optimizing storage utilization and performance.
i think A
I haven't tried it, but the only answer that makes sense to me is A. It doesn't make sense to make the source and destination of a snapvault relationship on the same aggregate because that would break SV fan-in configs (many to one SV relationships) so not B or C, And although you could have a FabricPool Relationship with Both Source and Destination, they are potentially very different because of 'many to one' relationships. So for me, the Answer is A. WRT B_rad comment that you can't assign a policy to destination, I can't see any reference to that in fabricPool docs. It seems a desirable config to establish a fabricPool tiering policy with a snapvault destination.
Yes A is correct
anser is A why?
I think ans is C
Answer is C, you cannot assign a policy to the destination.
have a look at section 2.2 here https://www.netapp.com/us/media/tr-4598.pdf Im leaning towards A. The question is asking about snap vault destination to tier nothing about source.
Next is the backup policy, which is primarily used for DR (more on that later). For the backup policy, you need to have a non-production SnapVault or SnapMirror destination volume.
C makes no sense - such config will move all data of source volume to capacity tier. Correct is A