NS0-155 Exam Dumps - Data ONTAP 7-Mode Administrator

http://www.redbooks.ibm.com/redpapers/pdfs/redp4268.pdf

When you are using SnapVault in combination with Volume SnapMirror, it is important to understand their relationship with Snapshot. You cannot utilize SnapVault to protect a Volume SnapMirror destination, because SnapVault and SnapMirror both use the same Snapshot copies; they cannot run simultaneously. Schedules must be managed to accommodate the interlock that keeps SnapVault and SnapMirror from stepping on each other.

Both ‘warn you that there are no available spares from the proper pool’ and ‘halt after 24 hours if spare disk are not added to the proper pool’ are correct answers. However, since Data ONTAP alerts you first, 'warn you that there are no available spares' is the best answer.

https://library.netapp.com/ecm/ecm_download_file/ECMP1196912

https://communities.netapp.com/servlet/JiveServlet/previewBody/4803-102-1-6405/tr-3548.pdf

It is important to remember that this is the case only when a complete site is lost. In the case of a failed controller at one of the sites, a normal cluster failover occurs. Due to the operation of SyncMirror, there is also added protection from multidrive or complete shelf failures. When a storage controller fails in an active-active configuration, the partner detects the failure and automatically (if enabled) performs a takeover of the dataserving responsibilities from the failed controller. Part of this process relies on the surviving controller being able to read information from the disks on the failed controller. If this quorum of disks is not available, then automatic takeover won’t be performed. In a MetroCluster configuration, manually executing a single command will allow a takeover to occur in spite of the lack of a quorum of disks. This "forced takeover" process breaks the mirrored relationships in order to bring the failed controller’s volumes on line.

forcetakeover -d is very dangerous. Not only can it cause data corruption, if not used carefully, it can also lead to a situation where both the node and its partner are operational (split brain). As such, it should only be used as a means of last resort when the takeover and forcetakeover commands are unsuccessful in achieving a takeover. The operator must ensure that the partner node does not become operational at any time while a node is in a takeover mode initiated by the use of this command. In conjunction with RAID mirroring, it can allow recovery from a disaster when the two nodes in the HA pair are located at two distant sites.