Which two actions protect an Infinite volume from the loss of a namespace constituent? (Choose
two)
A.
Minor the namespace constituent by using an intracluster data protection mirror
B.
Mirror the namespace constituent by using an Intercluster data protection mirror
C.
Mirror the namespace constituent by using a load-sharing mirror
D.
Mirror the namespace constituent by using a FlexCache mirror
Explanation:
http://www.globbtv.com/microsite/18/Adjuntos/_TR-4078_INFINITEVOLUME_BPG.PDF (page 15, 6.2, see best practices)
I think this answer could be wrong. Whats peoples thoughts?
The netapp documentation i have read indicates that a infinite volume namespace constituent DP mirror is an intracluster function:
“What a namespace mirror constituent is
A namespace mirror constituent is an intracluster data protection mirror copy of the namespace
constituent in an Infinite Volume. The namespace mirror constituent performs two roles: It provides
data protection of the namespace constituent, and it supports SnapDiff for incremental tape backup of
Infinite Volumes.”
https://library.netapp.com/ecm/ecm_download_file/ECMP1196874
0
0
i would imagine the second answer would be a LS mirror. This could then be promoted in the event of a DR scenario.
An intercluster snapmirror would indicate to me that the infinite volume is being mirrored to a DR site. So the whole volume would be mirrored rather than just the namespace.
0
0
A, B
https://library.netapp.com/ecmdocs/ECMP1196819/html/GUID-39787F6A-1537-4094-8D08-6575776BD727.html
0
0
Answer is A and B
0
0