[2018-Feb-New]High Quality Braindump2go NS0-155 Exam Dumps PDF 195Q Free Share[89-99]
2018 Feb New NetApp NS0-155 Exam Dumps with PDF and VCE Free Updated Today! Following are some new NS0-155 Real Exam Questions:
1.|2018 Latest NS0-155 Exam Dumps (PDF & VCE) 195Q&As Download:
2.|2018 Latest NS0-155 Exam Questions & Answers Download:
When using MetroCluster in a forced takeover mode, identify two methods for restricting access to the disaster site node. (Choose two.)
A. Use manual fencing.
B. Use the cf giveback -f command.
C. Use the cf forcetakeover -d command.
D. Turn off power to the disaster site node.
E. Isolate the failed node from the surviving node.
In a fabric-attached MetroCluster, a “site failure” is described as a __________.
A. failure of the Inter-Switch-Links (ISL)
B. failure of the interconnect cable
C. complete failure of the primary controller and disk shelves
D. malfunction of the Fibre Channel adapter on the cluster node
Which two statements are true of the cf forcetakeover -d command? (Choose two.)
A. Mirrored volumes are implicitly split.
B. Partner mailboxes must be available.
C. The failed cluster node is powered off automatically.
D. The surviving cluster node takes over the functions of the failed partner.
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.
Protection Manager is an optional component of the Operations Manager that can be licensed and accessed from the NetApp Management Console (NMC).
Operations Manager, Protection Manager and Provisioning Manager are all core products of the Unified Manager Platform suite.
Operations Manager can monitor and manage only NetApp storage hosts that have the NetApp Host Agent installed.
If no Host Agent is installed, how can the management tool query the host?
Which are three valid data protection solutions? (Choose three.)
A. SnapVault toVolume SnapMirror
B. SnapVault toVolume SnapMirror to SnapVault
C. SnapVault toVolume SnapMirror toVolume SnapMirror
D. Volume SnapMirror to SnapVault
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.
Protection Manager has policies that allow for tape-based protection as well as disk-based protection.
When using a Protection Manager policy to manage Open Systems SnapVault backups on a UNIX server, which three are valid objects to include in the data set? (Choose three.)
A. A file
B. A qtree
C. A directory
D. The entire client
Open Systems Snap Vault runs on servers, so the objects that can be selected for backup will be host-based.
Qtrees are objects on the storage system.
XML-files in /etc/stats/preset are used together with the sysstat command to customize the output.
Data ONTAP provides some XML files that output a predetermined set of statistics that you can use without having to construct a script or type in a complicated command on the command line.
The preset files are located in the /etc/stats/preset directory.
To use a preset file, you add -p filename to your stats show or stats stop command line.
You can also add counters on the command line. If any options you specify on the command line conflict with the preset file, your command line options take precedence.
You can also create your own preset files.
When migrating from Data ONTAP 7G to Data ONTAP 8.0 7-mode, existing non-traditional aggregates are designated as ________.
Aggregates are never converted as part of an upgrade. An upgrade will not touch your data!
To create a 64-bit aggregate, which optional switch/flag/parameter/option to the aggr create command must be included?
A. b 64
B. B 64
C. l 64
D. L 64
E. No optional switch/flag/parameter/option is needed because 64-bit aggregates are the default
The command to create a 64-bit aggregate is the same aggr create command that is present in Data ONTAP 7G for aggregate creation. The aggr create command has a new flag, -B, to specify
the type of aggregate to create. It takes a value of either 32 or 64 and creates the respective type of aggregate. Therefore the aggr create command with -B 64 creates a 64-bit aggregate. The aggr create command without the -B flag by default creates a 32-bit aggregate.
Here are some commands for creating different aggregate types in Data ONTAP 8.0:
Creating a 64-bit aggregate:
aggr create aggr_64 -B 64 5
Creating a 32-bit aggregate using -B flag:
aggr create aggr_32 -B 32 5
Creating a 32-bit aggregate without using -B flag:
aggr create default_aggr_32 5
Note: the man pages do not include this option in later versions of DOT because 64-bit is now the default.