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?
A.
Create the destination volume on the FabricPool-enabled aggregate and assign the backup tiering policy to the destination volume.
B.
Create both the source and destination volumes on a standard aggregate and assign the backup tiering policy to the destination volume.
C.
Create both the source and destination volumes on the FabricPool-enabled aggregate and assign the backup tiering policy to the source volume.
D.
Create the source volume on the FabricPool-enabled aggregate and assign the backup tiering policy to the source volume.
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.
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.
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.
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
kombayn
8 months, 4 weeks agosafodz
3 years, 9 months agowhoistheg
4 years, 4 months agoBigEars
4 years, 4 months agoB_rad
4 years, 8 months ago010
4 years, 9 months ago010
4 years, 9 months agoandersonneo
5 years, 2 months agogino
5 years, 3 months ago