NS0-155 Practice Exam Questions with Answers Data ONTAP 7-Mode Administrator Certification

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

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

nfsstat and sysstat are OnTap commands used for performance information.

sio_ntap_soll is not an OnTap command.

Perfstat is a GUI performance tool, not an OnTap command. Think of PerfMon for Windows to remind you that PerfStat is a Windows tool. Note how many of the ONTAP performance commands end in stat.

You can export any file path. Implicitly file paths are filesystem objects. You can export a directory, a qtree, a volume or even a file.

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

The -p option requests that reallocation of user data take place on the physical blocks in the aggregate, but the logical block locations within a flexible volume are preserved.

Aggregate reallocation is not supported on aggregates created prior to Data ONTAP 7.2.

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.

Volume SnapMirror Interoperability Matrix.

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

https://library.netapp.com/ecm/ecm_download_file/ECMM1278920

What SnapDrive does

SnapDrive software integrates with the Windows Volume Manager so that NetApp filers can serve as virtual storage devices for application data in Windows 2000 Server and Windows Server 2003 environments.

SnapDrive is dependent on the virtual disk service. The virtual disk service must be started on the host prior to installing SnapDrive. SnapDrive manages virtual disks (LUNs) on a NetApp filer, making these virtual disks available as local disks on Windows hosts. This allows Windows hosts to interact with the virtual disks just as if they belonged to a directly attached redundant array of independent disks (RAID).

SnapDrive provides the following additional features:

It enables online storage configuration, virtual disk expansion, and streamlined management.

It integrates NetApp Snapshot technology, which creates point-in-time images of data stored on virtual disks.

It works in conjunction with SnapMirror® software to facilitate disaster recovery from either asynchronously or synchronously mirrored destination volumes.

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.

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.

For a detailed breakdown of the procedure see the following KB

https://kb.netapp.com/support/index?page=content &id=1011576

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

aggr mirror aggrname

[ -f ]

[ -n ]

[ -v victim_aggrname ]

[ -d disk1 [ disk2 ... ] ]

Turns an unmirrored aggregate into a mirrored aggregate by adding a plex to it. The plex is either newlyformed from disks chosen from a spare pool, or, if the -v option is specified, is taken from another existing unmirrored aggregate. Aggregate aggrname must currently be unmirrored. Use aggr create to make a new, mirrored aggregate from scratch.

Disks may be specified explicitly using -d in the same way as with the aggr create and aggr add commands.

The number of disks indicated must match the number present on the existing aggregate. The disks specified are not permitted to span disk pools. This behavior can be overridden with the -f option. The -f option, in combination with -d, can also be used to force using disks that have a rotational speed that does not match that of the majority of existing disks in the aggregate.

If disks are not specified explicitly, then disks are automatically selected to match those in the aggregate's existing plex.

The -v option can be used to join victim_aggrname back into aggrname to form a mirrored aggregate. The result is a mirrored aggregate named aggrname which is otherwise identical to aggrname before the operation.

Victim_aggrname is effectively destroyed. Victim_aggrname must have been previously mirrored with

aggrname, and then separated via the aggr split command. Victim_aggrname must be offline. Combined with the -v option, the -f option can be used to join aggrname and victim_aggrname without prompting the user.

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.

This option causes the file system to remain the same size and not grow or shrink when a SnapMirrored volume relationship is broken, or when a vol add is performed on it. This option is automatically set to be on when a volume becomes a SnapMirrored volume. It will remain on after the snapmirror break command is issued for the volume. This allows a volume to be SnapMirrored back to the source without needing to add disks to the source volume. If the volume size is larger than the file system size, turning off this option will force the file system to grow to the size of the volume. The default setting is off.

http://wafl.co.uk/vol-2/#sthash.DbEHR4YS.dpuf

snapmirror resume destination

Resumes transfers to destination. The snapmirror resume command can be used either to abort a

snapmirror quiesce in progress or undo a previously completed snapmirror quiesce. The command restores the state of the destination from quiescing or quiesced to whatever it was prior to the quiesce operation.

http://wafl.co.uk/snapmirror/#sthash.5u3eilbK.dpuf

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

http://backdrift.org/man/netapp/man5/na_stats_preset.5.html

Data ONTAP provides some XML files that output a predetermined set of statistics that you can use without having to construct a script or type in a complicated command on the command line.

The preset files are located in the /etc/stats/preset directory. To use a preset file, you add -p filename to your stats show or stats stop command line. You can also add counters on the command line. If any options you specify on the command line conflict with the preset file, your command line options take precedence.

You can also create your own preset files.

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

The command to create a 64-bit aggregate is the same aggr create command that is present in Data ONTAP 7G for aggregate creation. The aggr create command has a new flag, -B, to specify the type of aggregate to create. It takes a value of either 32 or 64 and creates the respective type of aggregate. Therefore the aggr create command with -B 64 creates a 64-bit aggregate. The aggr create command without the -B flag by default creates a 32-bit aggregate.

Here are some commands for creating different aggregate types in Data ONTAP 8.0:

Creating a 64-bit aggregate:

aggr create aggr_64 -B 64 5

Creating a 32-bit aggregate using –B flag:

aggr create aggr_32 -B 32 5

Creating a 32-bit aggregate without using –B flag:

aggr create default_aggr_32 5

Note: the man pages do not include this option in later versions of DOT because 64-bit is now the default.

If a scheduled transfer fails (for example, due to network failure), SnapMirror automatically retries the transfer the next minute.

http://hd.kvsconsulting.us/netappdoc/733docs/html/ontap/onlinebk/GUID-511EAA86-069A-42E8-B62E-3168C7F0A83D.html

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

When you rejoin split aggregates, Data ONTAP mirrors the data from one aggregate to the other and destroys data that existed on that aggregate before the rejoin.

https://library.netapp.com/ecmdocs/ECMP1196991/html/GUID-B9CB3DA8-E1AF-4BAC-A85B-64C009010F4A.html

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

http://wafl.co.uk/ndmpcopy/

Because volume SnapMirror works at the block level, the source and destination must both be FlexVol volumes in the same aggregate type. The source and destination of a volume SnapMirror relationship must either both be FlexVol volumes in 32-bit aggregates or both be FlexVol volumes in 64-bit aggregates.

Therefore you cannot create a volume SnapMirror relationship from a FlexVol volume in a 32-bit aggregate to a FlexVol volume in a 64-bit aggregate or vice versa.