Netapp Updated NS0-593 Exam Questions and Answers by avi

 If both root aggregates are destroyed in a two-node cluster, the cluster will be inoperable and the data will be inaccessible. To recover from this situation, you need to perform the following actions:

• Install ONTAP from a USB device on one of the nodes. This will create a new root aggregate and a new cluster on that node.
• Rejoin the second node to the re-created cluster. This will also create a new root aggregate on the second node and synchronize it with the first node.
• Restore the cluster configuration and data from a backup, if available. References =
• ONTAP 9 Documentation Center
• Storage System Recovery Troubleshooting
• Recovering from a root aggregate failure

= The NetApp Cloud Volumes ONTAP Release Notes provide the most up-to-date and accurate information about the storage limits for different cloud platforms, licenses, and configurations. The release notes also include details about supported features, known issues, and limitations for each version of Cloud Volumes ONTAP. References = Storage limits - NetApp, Storage limits | NetApp Documentation, Storage limits in AWS | NetApp Documentation, Storage limits in Azure | NetApp Documentation

• SnapMirror is a data replication technology that allows efficient and flexible data protection and disaster recovery for NetApp ONTAP storage systems1
• SnapMirror transfers data between source and destination volumes using a network connection. SnapMirror can use storage efficiency features such as compression and deduplication to reduce the amount of data transferred and stored1
• SnapMirror transfers are scheduled and controlled by policies that define the frequency, retention, and priority of the transfers. SnapMirror policies can also specify the network bandwidth limit for the transfers2
• SnapMirror transfers are considered background tasks that run in the absence of user workload. SnapMirror transfers can consume CPU and disk resources on both source and destination systems, depending on the amount and type of data being replicated3
• SnapMirror transfers can throttle up or down depending on the availability of system resources and network bandwidth. SnapMirror transfers will throttle up when there is nouser workload, and throttle down when there is user workload. This is to ensure that SnapMirror transfers do not impact the performance of user operations3
• Therefore, if a customer is concerned with high CPU and disk utilization on their SnapMirror destination system, the best answer is to explain that background tasks such as SnapMirror throttle up in the absence of user workload. This is normal and expected behavior, and it does not indicate a problem with the system3

References:

1: ONTAP 9 Data Protection - SnapMirror - The Open Group 2: ONTAP 9 Data Protection - SnapMirror Policies - The Open Group 3: SnapMirror storage efficiency configurations and behavior - Resolution Guide - NetApp Knowledge Base

A MetroCluster configuration requires the ISLs between the sites to be up and running for the switchover to occur. If the ISLs are down, the MetroCluster configuration cannot communicate with the other site and cannot perform the switchover. Additionally, a MetroCluster configuration requires all aggregates to be mirrored across the sites for data protection and availability. If a site has unmirrored aggregates, the switchover will fail because the data on those aggregates will not be accessible from the other site. References = Configuring the MetroCluster software in ONTAP, NetApp MetroCluster FC for ONTAP 9.8