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

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.

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/ECMP1196991/html/GUID-D4D7C7F0-9063-4099-B5CA-8FEE619EEF1D.html

SyncMirror is a feature of Data OnTap used to mirror data to two separate aggregates. It allows for real-time mirroring of data to matching aggregates physically connected to the same storage system.

SyncMirror provides for synchronous mirroring of data, implemented at the RAID level. You can use SyncMirror to create aggregates that consist of two copies of the same WAFL file system. The two copies, known as plexes, are simultaneously updated. Therefore, the copies are always identical. The two plexes are directly connected to the same system.

The following provides information about the activities of SyncMirror:

SyncMirror can be used to mirror aggregates and traditional volumes. (A traditional volume is essentially an aggregate with a single volume that spans the entire aggregate.)

SyncMirror cannot be used to mirror FlexVol volumes. However, FlexVol volumes can be mirrored as part of an aggregate.

SyncMirror is different from synchronous SnapMirror.

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

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

In OnTap 8.0, when UNIX security style is selected, only UNIX security objects can be used. The correct answer is GID, UID and UNIX permissions.

Basic UNIX permissions are organized into three classes: user, group, and others.

UNIX operating systems identify users with a numerical value: a user identifier, also known as a UID or User ID. Each user is a member of a group of the same name as the user. Like UIDs, groups (GIDs) are also specified using a numerical value.

Disks must be assigned to an aggregate to be used as raid group members or spares. Unassigned disks are displayed as "not owned".

http://www.netapp.com/us/system/pdf-reader.aspx?m=ds-3366.pdf &cc=us

Flash Accel utilizes server-based flash storage as cache for the host.