NS0-162 Exam Dumps : NetApp Certified Data Administrator (ONTAP)

The easiest and fastest way to restore a single file from a Snapshot copy is to use the Windows Shadow Copy Client, which allows the user to access and restore Data ONTAP Snapshot files from the Previous Versions tab in the Properties menu. This does not require any CLI commands or ONTAP System Manager operations. References :- Restoring files from Snapshot copies, Restore a single file from a Snapshot copy

 According to the NetApp best practices, flow control should be disabled on data network ports and cluster network ports using 10GbE Ethernet. This is because flow control can cause excessive pause frames, xon/xoff frames, or packets being re-queued, which can affect the network performance and TCP throughput. Flow control works at the physical link layer and does not consider the upper level protocols. Therefore, it is recommended to disable flow control end-to-end on both data and cluster network ports for optimal performance. References :- How to modify flow control on cluster port in ONTAP, What are the flow control best practices for Ethernet?, Configure your network for best performance

 To find the highest latency seen on restore, you need to look at the output of the table that shows the latency measurements for different operations and sizes. The highest latency is 10021 ms, which is the maximum latency for the GET operation with 8KB size. This means that when the users recover files with the Windows Previous Versions tab, they are reading data from the cloud tier that has been tiered using the snapshot-only policy, which causes high latency and slow restores.

• The other latencies are not correct, as they are lower than 10021 ms. The maximum latency for the PUT operation with 4MB size is 10500 ms, but this is not related to the restore operation, as it is writing data to the cloud tier. The maximum latency for the GET operation with 4KB size is 9591 ms, which is slightly lower than 10021 ms. The maximum latency for the GET operation with 32KB size is 7889 ms, which is much lower than 10021 ms. The maximum latency for the GET operation with 256KB size is 7838 ms, which is also much lower than 10021 ms. References :- FabricPool overview, FabricPool requirements, FabricPool best practices, High READ Latency from the fabric pool aggregate.