How to Pass the Netapp NS0-155 Exam: Comprehensive Data ONTAP 7-Mode Administrator Guide and Tips

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_vol.1.html

vol options nosnapdir [on|off]

If this option is on, it disables the visible .snapshot directory that is normally present at client mount points, and turns off access to all other .snapshot directories in the volume. The default setting is off.

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

In OnTap 8.0, when NTFS security style is used, only Windows style security objects are used.

For CIFS clients, security is handled using Windows NTFS ACLs.

For NFS clients, the NFS UID (user id) is mapped to a Windows SID (security identifier) and its associated groups. Those mapped credentials are used to determine file access, based on the NFTS ACL.

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.

The pktt command controls a simple on-filer packet tracing facility. Packets can be captured into a trace buffer then dumped to a file, or the captured data can be logged to a file. The data is stored in "tcpdump" format, and can be directly viewed with tcpdump, ethereal, and perhaps other viewers. The output can also be converted using the editcap(1) program to a variety of other formats, including Sniffer, NetMon, and snoop.

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

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

snapmirror 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 snapmirror update command must be issued on the destination filer.

snapmirror release source { filer:volume | filer:qtree }

Tell SnapMirror that a certain direct mirror is no longer going to request updates.

If a certain destination is no longer going to request updates, you must tell SnapMirror so that it will no longer retain a snapshot for that destination. This command will remove snapshots that are no longer needed for replication to that destination, and can be used to clean up SnapMirror-created snapshots after snapmirror break is issued on the destination side.

The source argument is the source volume or qtree that the destination is to be released from. The destination argument should be either the destination filer and destination volume name or the destination filer and destination qtree path. You can use a line from the output of the snapmirror destinations command as the set of arguments to this command. The /etc/snapmirror.conf file exists on the node containing the mirror used for SnapMirror.

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.

https://kb.netapp.com/support/index?

Page=content&id=2010134&actp=LIST_RECENT&viewlocale=en_US&searchid=1296570465177

The svpassword command is available on the OSSV host as part of the agent binaries in the path

\netapp\snapvault\bin.

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

The root volume is always vol0 and etc is contained therein. When exporting the root volume via NFS, the path is/vol/vol0; so the full path to snapmirror log files is /vol/vol0/etc/log.

/etc/log/snapmirror.

This file logs SnapMirror activity. Log file for current week.

/etc/log/snapmirror.[0-5] SnapMirror log files for previous weeks.