NS0-155 Questions and Answers

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

snapvault update [ -k n ] [ -s snapname ] [ -w ] sec_ondary_qtree

Available on the secondary only. Immediately starts an update of the specified qtree on the secondary.

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_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://library.netapp.com/ecmdocs/ECMP1196991/html/GUID-06C70D3B-9A06-4D20-B140-EB147B941BDA.html

The data structures that are backed up and restored through SnapVault depend on the primary system.

On systems running Data ONTAP, the qtree is the basic unit of SnapVault backup and restore.

SnapVault backs up specified qtrees on the primary system to associated qtrees on the SnapVault secondary system. If necessary, data is restored from the secondary qtrees back to their associated primary qtrees.

On open systems storage platforms, the directory is the basic unit of SnapVault backup. SnapVault backs up specified directories from the native system to specified qtrees in the SnapVault secondary system.

If necessary SnapVault can restore an entire directory or a specified file to the open systems platform.

The destination system uses a slightly more disk space and directories than the source system.

You must meet certain prerequisites before using SnapRestore:

- SnapRestore must be licensed on your storage system.

- There must be at least one Snapshot copy on the system that you can select to revert.

- The volume to be reverted must be online.

- The volume to be reverted must not be in use for data replication.

http://hd.kvsconsulting.us/netappdoc/733docs/html/ontap/onlinebk/GUID-A14081A3-9270-47EE-A1C1-EC52D3ABDBD0.html

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

The following commands are available in the aggr suite:

If you use the -d disk1 [ disk2 ... ] argument, the node creates the aggregate with the specified spare disks disk1, disk2, and so on. You can specify a space-separated list of disk names. Two separate lists must be specified if the new aggregate is mirrored. In the case that the new aggregate is mirrored, the indicated disks must result in an equal number of disks on each new plex.

The disks in a plex are not permitted to span spare pools. This behavior can be overridden with the -f option.

The same option can also be used to force using disks that do not have matching rotational speed. The –f option has effect only when used with the -d option specifying disks to use.

The -m option can be used to specify that the new aggregate be mirrored (have two plexes) upon creation. If this option is given, then the indicated disks will be split across the two plexes. By default, the new aggregate will not be mirrored.

aggr mirror aggrname

The -n option can be used to display the command that the system will execute without actually making any changes. This is useful for displaying the automatically selected disks, for example.

https://library.netapp.com/ecmdocs/ECMP1196889/html/GUID-83A15F85-92A1-4EA8-A9EC-B9E0E2269E37.html

https://library.netapp.com/ecmdocs/ECMP1196991/html/GUID-DB31E1F4-60A8-4F34-A1C4-8F79754E4DE2.html

You use the snapvault restore command to restore a backed-up qtree saved to the secondary system. Starting with Data ONTAP 7.3, you can restore the data to an existing qtree on the primary system using baseline restore or incremental restore.

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

snapmirror initialize [ -S source ] [ -k kilobytes ] [ -s src_snap ] [ -c

create_dest_snap ] [ -w ] destination Starts an initial transfer over the network. An initial transfer is required before update transfers can take place.

The initialize command must be issued on the destination node. If the destination is a volume, it must be restricted (see na_vol(1) for information on how to examine and restrict volumes). If the destination is a qtree, it must not already exist (see na_qtree(1) for information on how to list qtrees). If a qtree already exists, it must be renamed or removed (using an NFS or CIFS client), or snapmirror initialize to that qtree will not work.

snapmirror resync [ -n ] [ -f ] [ -S source ] [ -k kilobytes ] [ -s src_snap ]

[ -c create_dest_snap ] [ -w ] destination Resynchronizes a broken-off destination to its former source, putting the destination in the snapmirrored state and making it ready for update transfers. The resync command must be issued on the destination node.

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

http://www.uow.edu.au/~blane/netapp/ontap/cmdref/man1/na_options.1.htm

update [ -S source ] [ -k kilobytes ] [ -s src_snap ] [ -c create_dest_snap ] [ -w ] destination

For asynchronous mirrors, an update is immediately started from the source to the destination to update the mirror with the contents of the source.

For synchronous mirrors, a snapshot is created on the source volume which becomes visible to clients of the destination volume.

The update command must be issued on the destination node.status [ -l | -t | -q ] [ volume | qtree ... ]

Reports status of all the SnapMirror relationships with a source and/or destination on this node. This command also reports whether SnapMirror is on or off. If any volume or qtree arguments are given to the command, only the SnapMirror relationships with a matching source or destination will be reported. If the argument is invalid, there won't be any status in the output.initialize [ -S source ] [ -k kilobytes ] [ -s src_snap ] [ -c create_dest_snap ]

[ -w ] destination Starts an initial transfer over the network. An initial transfer is required before update transfers can take place.

The initialize command must be issued on the destination node. If the destination is a volume, it must be restricted (see na_vol(1) for information on how to examine and restrict volumes). If the destination is a qtree, it must not already exist (see na_qtree(1) for information on how to list qtrees). If a qtree already exists, it must be renamed or removed (using an NFS or CIFS client), or snapmirror initialize to that qtree will not work.snapmirror.access

This option determines which SnapMirror destination filers may initiate transfers, and over which network interfaces. When set to "legacy", SnapMirror uses the older snapmirror.allow to determine access. The option value is a string containing an expression which provides the access filter. An example of the options command for snapmirror.access is options snapmirror.access host=toaster,fridge. The default value is "legacy". See na_snapmirror(1) , na_snapmirror.allow(5) and na_protocolaccess(8) for more details.

The snapmirror.allow file exists on the source filer used for SnapMirror.

iSCSI and Fiber Channel encapsulate SCSI protocol, simulating direct disk access. These are commonly referred to as a block storage protocols. FCoE is another such protocol.

CIFS and NFS, HTTP and FTP provide file access not block access.

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/ECMP1196890/html/man5/na_exports.5.html

The /etc/exports file contains a list of export entries for all file system paths that Data ONTAP exports automatically when NFS starts up.

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

Snapshots can be made of volumes or aggregates; most commonly the former. The question refers to a file system, or more specifically a volume.

You cannot snapshot directories or qtrees alone.

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

The following commands are available in the lun suite:

All data, whether file or block-based, resides in 4KB blocks on disk. A group of related blocks make up a file. To accommodate different file sizes, the WAFL filesystem describes each file with reference pointers called inodes.

https://communities.netapp.com/servlet/JiveServlet/previewBody/5027-102-1-6953/PS%20Tech%20Note%20018%20-%20maxfiles.pdf

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.

The operator must ensure that the partner filer does not become operational at any time while a filer is in a takeover mode initiated by the use of this command

http://backdrift.org/man/netapp/man1/na_cf.1.html

Startup commands for your storage system are stored in the /etc/rc file. The /etc/rc file contains commands that the storage system executes at boot time to configure the system.

Commands in the /etc/rc file configure the storage system to:

Communicate on your network

Use the NIS and DNS services

Save the core dump that might exist if the storage system panicked before it was booted

https://library.netapp.com/ecmdocs/ECMM1278265/html/sysadmin/accessing/concept/c_oc_accs_systemstartup-etc-rc-file.html#c_oc_accs_system-startup-etc-rc-file