Pass the Netapp NetApp Certified Data Administrator NS0-155 Questions and answers with ExamsMirror

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

The following commands are available in the lun suite:

Easy to use interactive mechanism for setting up initiator groups, LUNs, and mapping configuration.

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.

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://library.netapp.com/ecmdocs/ECMP1196979/html/man1/na_options.1.html

replication.throttle.enable Enables global network throttling of SnapMirror and SnapVault transfers. The default value for this option is off.

replication.throttle.incoming.max_kbs

This option specifies the maximum total bandwidth used by all the incoming (applied at destination) SnapMirror and SnapVault transfers, specified in kilobytes/sec. The default value for this option is unlimited, which means there is no limit on total bandwidth used. This option is valid only when the option replication.throttle.enable is on.

replication.throttle.outgoing.max_kbs

This option specifies the maximum total bandwidth used by all the outgoing (applied at source) SnapMirror and SnapVault transfers specified in kilobytes/sec. The default value for this option is unlimited, which means there is no limit on total bandwidth used. This option is valid only when the option replication.throttle.enable is on.

https://communities.netapp.com/servlet/JiveServlet/previewBody/9734-102-1-17848/PDF_Tips_Data_Motion_0211.pdf

Non-disruptive Volume Movement is called DataMotion. DataMotion uses SnapMirror for volume migration.

A DataMotion migration occurs in three phases:

1. Setup

2. Data copy

3. Cutover

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.

http://www.ntapgeek.com/2011/03/netapp-storage-encryption-available.html

March, 2011: "With the recent release of Data ONTAP 8.0.1, NetApp now offers full disk encryption to prevent unauthorized access to data at rest."

https://library.netapp.com/ecmdocs/ECMP1196979/html/man5/na_snapmirror.conf.5.html

Each relationship entry of the /etc/snapmirror.conf file is a single line containing space-separated fields.

The entry has this format:

Source destination arguments schedule schedule

This is the schedule used by the destination node for updating the mirror. It informs the SnapMirror scheduler when transfers will be initiated. The schedule field can contain the word sync to specify fully synchronous mirroring, semi-sync to specify semi-synchronous mirroring, or a cron-style specification of when to update the mirror.

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.

Outstanding (deprecated)

This argument controls the performance versus synchronicity trade-off for synchronous mirrors. The value for this argument is a number followed by the suffixes: ops (operations), ms (milliseconds) or s (seconds). Setting a value less than 10s configures the mirror to run in fully synchronous mode. Setting a value greater than or equal to 10s configures the mirror to run in semi-synchronous mode. This argument is ignored for asynchronous mirrors. Please note that this is a deprecated option. Use the schedule field to specify the synchronous mode for the mirror.

cksum

This controls which checksum algorithm is used to protect the data transmitted by SnapMirror. Currently supported values are "none", "crc32c", and "crc32c_header_only". The value "crc32c_header_only" has been added only for volume SnapMirror and is not supported for synchronous SnapMirror and qtree SnapMirror.

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

lun set reservation lun_path [ enable | disable ]

Enables or disables the space reservation on the LUN. If no arguments are supplied after the lun_path, then the space reservation status of the given lun_path is displayed.

lun create -s size -t ostype [ -o noreserve ] [ -e space_alloc ] lun_path

This usage of the lun create command should be employed to create a new LUN of given size, with initially zero contents. The LUN is created at the lun_path given. No file should already exist at the given lun_path. The directory specified in the lun_path must be a qtree root directory.

The size is specified in bytes. Optionally, a number followed by a one-character multiplier suffix can be used: c (1), w (2), b (512), k (1024), m (k*k), g (k*m), t (m*m).

The size of the created LUN could be larger than the size specified, in order to get an integral number of cylinders while reporting the geometry using SAN protocols.

The size of the LUN actually created is reported if it is different from that specified in the command.

The mandatory ostype argument is one of: solaris (the LUN will be used to store a Solaris raw disk in a singleslice partition), windows (the LUN will be used to store a raw disk device in a single-partition Windows disk using the MBR (Master Boot Record) partitioning style), hpux (the LUN will be used to store HP-UX data), aix (the LUN will be used to store AIX data), vld (the LUN contains a SnapManager VLD), linux (the LUN will be used to store a Linux raw disk without any partition table), netware (the LUN will be used to store NetWare data), vmware (the LUN will be used to store VMware data), windows_gpt (the LUN will be used to store Windows data using the GPT (GUID Partition Type) partitioning style), windows_2008 (the LUN will be used to store Windows data for Windows 2008 systems), openvms (the LUN will be used to store Open-VMS data), xen (the LUN will be used to store Xen data), hyper_v (the LUN will be used to store Hyper-V data), solaris_efi

By default, the LUN is space-reserved. To manage space usage manually, -o noreserve can be specified.

Using this option will create a LUN without any space being reserved. Provisioning threshold events can be enabled by specifying -e space_alloc option. This option has to be used in conjunction with -o noreserve.

lun map [ -f ] lun_path initiator_group [ lun_id ]

Maps a LUN to all the initiators in the supplied group. If a LUN ID is not specified, the smallest number that can be used for the various initiators in the group is automatically picked. Note that this command can be used multiple times to configure multiple maps for a LUN, or for an initiator group. Once created, you can use lun show -m to list all the LUN mappings.

The optional -f argument disables checking with the HA partner for LUN mapping conflicts.