Netapp NS0-155 - Data ONTAP 7-Mode Administrator

A baseline (aka "full") backup is always required before valid incremental backups can be made.

http://en.wikipedia.org/wiki/Multipath_I/O

Fiber Channel (FC), FCoE and iSCSI encapsulate SCSI-3. FCoE and iSCSI further encapsulate the transport within IP; hence the term IP SAN.

In computer storage, multipath I/O is a fault-tolerance and performance enhancement technique whereby there is more than one physical path between the CPU in a computer system and its mass storage devices through the buses, controllers, switches, and bridge devices connecting them.

A simple example would be a SCSI disk connected to two SCSI controllers on the same computer or a disk connected to two Fibre Channel ports. Should one controller, port or switch fail, the operating system can route I/O through the remaining controller transparently to the application, with no changes visible to the applications, other than perhaps incremental latency.

http://en.wikipedia.org/wiki/Logical_Unit_Number_masking

Logical Unit Number Masking or LUN masking is an authorization process that makes a Logical Unit Number available to some hosts and unavailable to other hosts.

http://www.netapp.com/us/system/pdf-reader.aspx?m=ds-3177-0512.pdf &cc=us

http://www.netapp.com/us/products/platform-os/flashpool.aspx

Flash Pool utilizes SSDs to enhance performance of disk aggregates.

Flash Cache is a controller-attached PCIe intelligent caching solution.

Flash Accel is a host-attached caching solution.

Flash Disk and Flash IO are ambiguous terms.

https://library.netapp.com/ecmdocs/ECMP1196986/html/GUID-8A91F6A2-61B8-42C3-AEAB7D5AA9BBE9CF.html

If a disk fails and no hot spare disk that exactly matches the failed disk is available, Data ONTAP uses the best available spare. Understanding how Data ONTAP chooses an appropriate spare when there is no matching spare enables you to optimize your spare allocation for your environment.

Data ONTAP picks a non-matching hot spare based on the following criteria (and more; in the link above):

If the available hot spares are not the correct size, Data ONTAP uses one that is the next size up, if there is one.

The replacement disk is downsized (aka right sized) to match the size of the disk it is replacing; the extra capacity is not available.

https://library.netapp.com/ecmdocs/ECMP1196979/html/man1/na_options.1.html

nfs.per_client_stats.enable

Enables/disables the collection and display of perclient NFS statistics, as described in na_nfsstat(1). Valid values for this option are on or off. The default value for this option is off.

https://communities.netapp.com/groups/chris-kranz-hardware-pro/blog/2009/03/05/fractional-reservation--lunoverwrite

From the article:

"If you reduce the Fractional Reservation to 0, you need to make sure the rate of change is within the volume size, or you need to make sure the volume can auto-grow when required or even snap auto-delete to reduce the reserved blocks and free up space (although I am not a huge fan of snap auto-delete for various reasons)."

https://library.netapp.com/ecmdocs/ECMP1196993/html/GUID-09C7812F-E6EA-47C6-AB79-EAB803E7A8EB.html

If the user names in the UNIX password database are identical to the Windows names, you need not provide the mapping information in the /etc/usermap.cfg file.

http://vipulvajpayeestorage.blogspot.com/2012/01/manually-failover-activity-in-netapp.html

In order to test or effect a Disaster Recovery operation, you must restrict access to the disaster site node to prevent the node from resuming service. If you do not, you risk the possibility of data corruption.

Access to the disaster site note can be restricted in the following ways:

Turn off the power to the disaster site node Use "manual fencing" (Disconnect VI interconnects and fiber channel cables; either physically or through configuration changes on the fabric switches.)

Isolating the failed node from the surviving node could still lead to the possibility of a split brain, so this is not a correct answer.