Free Practice Questions for Netapp NS0-155 Exam

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/ECMP1196979/html/man1/na_lun.1.html

The following commands are available in the lun suite:

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

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.

The resync command can cause data loss on the destination. Because it is effectively making destination a replica of the source, any edits made to the destination after the break will be undone.

For formerly mirrored volumes, the resync command effectively performs a SnapRestore (see na_vol

(1)) on the destination to the newest snapshot which is common to both the source and the destination. In most cases, this is the last snapshot transferred from the source to the destination, but it can be any snapshot which is on both the source and destination due to SnapMirror replication. If new data has been written to the destination since the newest common snapshot was created, that data will be lost during the resync operation.

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/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.

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

http://redhunter.com/blog/2010/02/11/netapp-consistency-points-in-cacti/

cp_from_log_full (log full) - the current NVRAM bank is full and the system switches to the other one and starts writing this to disk. Very heavy write activity.

cp_from_cp (aka Back to Back) - filer is overloaded. The write traffic is coming in faster than it can be written and the filer is running out of NVRAM capacity in one bank before the data in the other bank can be written.

cp_from_busy is not a real cp type

cp_from_timer - 10 seconds since the last CP – it means the system is pretty idle write-wise.