Netapp NS0-155 Data ONTAP 7-Mode Administrator Exam Practice Test

You can export any file path. Implicitly file paths are filesystem objects. You can export a directory, a qtree, a volume or even a file.

This question is out of date, but its still on the exam as of Sept2013! NOW has been replaced with support.netapp.com.

You should be very familiar with what AutoSupport does. Also if you have done any research, you know that the System Configuration Guide is an invaluable tool that you will use regularly. Neither of those are related to bugs.

Bugs Online (BOL) is located at http://support.netapp.com/NOW/cgi-bin/bol/ Bugs Online provides a suite of tools to help manage and resolve your bug issues.

The Release Bug Advisor is located at

http://support.netapp.com/NOW/cgi-bin/relrec

There is also a Version Comparison tool available at

https://communities.netapp.com/docs/DOC-8168/diff?secondVersionNumber=8

http://hd.kvsconsulting.us/netappdoc/801docs/html/ontap/smg/GUID-866DD79D-D2A6-4FBA-B0BDA63560FECEFF.html

https://library.netapp.com/ecmdocs/ECMP1196891/html/GUID-F6304830-B124-40A5-95D6-C646AA85E9E0.html

Only hostnames and IPs are referenced in /etc/hosts, so A is incorrect. The question states that the qtree was mounted, and B and D would preclude this so they are incorrect.

You need to set a qtree to mixed or unix security style to support UNIX users.

http://www.wafl.co.uk/cf/

http://wafl.co.uk/options/

Negotiated failover is a general facility which supports negotiated failover on the basis of decisions made by various modules.

cf.takeover.on_disk_shelf_miscompare

This option allows negotiated takeover to be enabled when the cluster nodes detect a mismatch in disk shelf count. By default, this option is set to off.

This option is available only when cluster is licensed and changing the value on one filer automatically changes the value on the partner filer.

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

Using the -p option may reduce the extra storage requirements in a flexible volume when reallocation is run on a volume with snapshots. It may also reduce the amount of data that needs to be transmitted by SnapMirror on its next update after reallocation is performed on a SnapMirror source volume.

https://library.netapp.com/ecmdocs/ECMP1210206/html/GUID-A865DB95-9418-4ED2-A993-74F347F674A0.html

1. Validate that you can access the remote storage by entering the following command:

aggr status -r

Note: A (level-0 resync in progress) message indicates that a plex cannot be rejoined.

2. Turn on the power to the node at the disaster site. After the node at the disaster site boots up, it displays the following:

Waiting for giveback...(Press Ctrl-C to abort wait)

3. If the aggregates at the disaster site are online, take them offline by entering the following command for each aggregate that was split:

aggr offline disaster_aggr

disaster_aggr is the name of the aggregate at the disaster site.

Note: An error message appears if the aggregate is already offline.

4. Destroy every target plex that is in a level-0 resync state by entering the following command:

aggr destroy plex_name

5. Re-create the mirrored aggregates by entering the following command for each aggregate that was split:

aggr mirror aggr_name -v disaster_aggr

aggr_name is the aggregate on the surviving site’s node.

disaster_aggr is the aggregate on the disaster site’s node.

The aggr_name aggregate rejoins the disaster_aggr aggregate to reestablish the MetroCluster configuration.

6. Enter the following command at the partner node:

cf giveback

The node at the disaster site reboots.

https://library.netapp.com/ecmdocs/ECMP1196890/html/man5/na_exports.5.html

IP addresses and wildcards can be used when specifying host targets in exports.

User names are not valid exports options, save for the anon option which utilizes a local system UID or user name (i.e. no user name mapping or resolution is performed.)

The highest level in the filesystem that can be specified for an export is the volume level. Implicitly this means that each volume must be exported separately.

An export provides access to paths below the export, implying that multiple paths on the same volume can be exported from an export.

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

Remote Support Agent is the facility to provide NetApp Support Engineers with the ability to remotely trigger AutoSupport.

Remote Support Agent uses HTTP or HTTPS to communicate with the storage controller to initiate commands and to collect files. It uses HTTPS to send system logs and core files from the Data ONTAP root volume to Remote Support Enterprise on the NetApp Support side.

NetApp RSA is not related to the RSA public key encryption algorithm.

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

For Data ONTAP to obtain the UID and GIDs for a CIFS user, it must first determine the user’s UNIX-style name. It does this through user mapping.

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

sysstat reports aggregated filer performance statistics such as the current CPU utilization, the amount of network I/O, the amount of disk I/O, and the amount of tape I/O.

http://scst.sourceforge.net/mc_s.html

http://www.alacritech.com/legacypdf/iSCSI_Multiple_Connections.pdf

Meme: Remember the acronym: MCS or MC/S - Multiple Connections per Session. Microsoft Windows 2008's MPIO driver supports MC/S.

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.

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://backdrift.org/man/netapp/man1/na_quota.1.html

quota resize volume

Adjusts currently active quotas in the specified volume to reflect changes in the /etc/quotas file. For instance, if you edit an entry in /etc/quotas to increase a user's quota, quota resize will cause the change to take effect. The volume name may be omitted if the system has only one volume. quota resize can be used only when quotas are already on. Because it does not rescan the file system to compute usage, quota resize is faster than turning quotas off and then on again. quota resize will apply all updated entries in /etc/quotas; however, it will generally ignore newly added entries. A newly added entry will only take effect if the corresponding user or group has an active quota as a result of updating a file subject to default quotas.

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

The snapvault command has a number of subcommands. The set of subcommands differs on the primary and secondary.

On the primary, the subcommands allow users to configure and manage a set of snapshots for potential replication to the secondary, to abort replication transfers to the secondary, to check status, to restore data from the secondary, and to release resources when a primary qtree will no longer be replicated to a secondary.

On the secondary, the subcommands allow users to configure and manage the replication of primary paths to secondary qtrees, to configure and manage the snapshot schedules which control when all the qtrees in a secondary volume are updated from their respective primary paths and how many snapshots to save, to abort transfers, to check status, and to release resources preserved to restart backups from a restored qtree.

When you rejoin split aggregates, Data ONTAP mirrors the data from one aggregate to the other and destroys data that existed on that aggregate before the rejoin.

https://library.netapp.com/ecmdocs/ECMP1196991/html/GUID-B9CB3DA8-E1AF-4BAC-A85B-64C009010F4A.html

https://library.netapp.com/ecmdocs/ECMP1196890/html/man1/na_iscsi.1.html

iscsi security show

Display the default authentication and all the initiator specific authentication information.

Hint: Remember that the iscsi command is mostly structured "iscsi noun verb", unlike the fcp command which is structure "fcp verb noun". Example: iscsi initiator show, fcp show initiator.

http://www.netapp.com/us/media/tr-3326.pdf

http://backdrift.org/man/netapp/man5/na_snapmirror.conf.5.html

http://hd.kvsconsulting.us/netappdoc/733docs/html/ontap/onlinebk/GUID-47724B21-7C7E-4AC9-A497-9505B42C27AF.html

With SnapMirror Sync and SnapMirror Semi-Sync, changes to the source volume do not show up immediately on the destination volume, even though the changes have been replicated. The changes are first shown after the source system creates an automatic Snapshot copy of the source volume.

Snapshot copies created on the source volume are immediately propagated to the destination volume. The automatic Snapshot copies are created every three minutes by default.

To change the interval for automatic Snapshot copies, change the visibility_interval in the

snapmirror.conf file; however, performance can degrade if set to a smaller interval because frequent

Snapshot copies cause additional processing such as cache consistency checking on the destination system.

There is also a disadvantage in setting this to a large value. When the connection between the systems has an outage and SnapMirror goes into asynchronous mode, SnapMirror uses the last common Snapshot copy to transition into synchronous mode. This means that all data from the last valid common Snapshot copy will need to be replicated from the source to the destination storage system. If the visibility_interval is set to a large value, a large amount of data might have to be transferred and it might take longer time for SnapMirror to transition into synchronous mode. For these reasons, keep the default value of three minutes.

visibility_interval

The value for this argument is a number optionally followed by the suffixes: s (seconds), m (minutes) or h (hours). If a suffix is not specified, value is interpreted as seconds. This argument controls the amount of time before an automatic snapshot is created on the source volume that is synchronously mirrored. The value is the number of seconds between automatically created snapshots. The default value is 3 minutes. A small number here can negatively affect the performance of the mirror. This argument is ignored for asynchronous mirrors.

visibility_interval={xs | xm | xh}

Determines the amount of time before an automatic Snapshot copy is created on the source volume that is being replicated using synchronous or semi-synchronous SnapMirror. When replicating synchronously or semisynchronously, using SnapMirror, changes to the source volume do not show immediately on the destination volume, even though the changes have been replicated. The changes are shown only after the source system takes an automatic Snapshot copy of the source volume. This event occurs every three minutes by default.

You can change the interval for automatic Snapshot copies, but performance can degrade if you set smaller intervals because Snapshot copies are taken more often. The smallest interval you can set is 30 seconds.

Note: The s, m, and h suffixes specify seconds, minutes, and hours, respectively.

For a detailed breakdown of the procedure see the following KB

https://kb.netapp.com/support/index?page=content &id=1011576

Section: Data Protection

NetApp also recommends that if deduplication is used on the source volume, then it should also be used on the destination volume. However, you are not restricted using deduplication on the source volume only.

The deduplication schedule is not tied to the qtree SnapMirror update. In other words, the deduplication process does not automatically start at the completion of the qtree SnapMirror transfer.

The fingerprint database and the change log files that are used in the deduplication process are located outside of the volume in the aggregate and are therefore not captured in Snapshot copies

http://www.netapp.com/us/media/tr-3505.pdf

https://library.netapp.com/ecmdocs/ECMP1196890/html/man1/na_cifs_shares.1.html

cifs shares -add sharename path

https://library.netapp.com/ecmdocs/ECMP1196889/html/GUID-8ACE3CAB-D338-4AFC-A530-0D0FEC3B9F94.html

The snaplock command manages compliance related functionality on the system. A volume created using the vol command (see na_vol(1)) is a snaplock volume when either the enterprise or compliance option is chosen.

Enterprise and compliance SnapLock volumes allow different levels of security assurance.

https://library.netapp.com/ecmdocs/ECMP1196889/html/GUID-D4533C47-441D-41AB-A8A2-272A2BFC431C.html

SnapLock operates fundamentally at the file level.

IPSec is an encryption transport that can be used to secure any IP traffic including iSCSI.

snapmirror resume destination

Resumes transfers to destination. The snapmirror resume command can be used either to abort a

snapmirror quiesce in progress or undo a previously completed snapmirror quiesce. The command restores the state of the destination from quiescing or quiesced to whatever it was prior to the quiesce operation.

http://wafl.co.uk/snapmirror/#sthash.5u3eilbK.dpuf