Free Practice Questions for Netapp NS0-155 Exam

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

User and group quotas do not apply to the root user or to the Windows Administrator account; tree quotas, however, do apply even to root and the Windows Administrator account.

A baseline (aka "full") backup is always required before valid incremental backups can be made.

https://library.netapp.com/ecmdocs/ECMP1196991/html/GUID-75BD4540-A103-4E2B-8B0A-E6BBC0D3F43F.html

http://backdrift.org/man/netapp/man5/na_snapmirror.conf.5.html

Two multipath methods are supported:

The multiplexing mode causes snapmirror to use both paths at the same time. If one should fail, it will switch to use the remaining path only and use both again should the failing path be repaired.

Failover mode causes snapmirror to use the first path as the desired path and only use the second path should problems arise with the first path.

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.

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.

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

http://www.geekyfacts.com/index.php?option=com_content &view=article&id=64:snapvault

snapvault snap sched [ -f ] [ -x ] [ -o options ] [ volname [ snapname [ schedule ]]]

schedule is cnt[@day_list][@hour_list] or cnt[@hour_list][@day_list]

In the schedule, cnt tells SnapVault how many of the snapshots to keep for primaries and for non-SnapLock secondary volumes. The snapshots will be numbered newest to oldest from 0 to cnt-1. When creating a new snapshot, SnapVault will delete the oldest snapshots, increment by one the number on the remaining snapshots and then create a new number 0 snapshot. If a snapshot is missing from the sequence (e.g. sv.0, sv.1, and sv.3 exist but sv.2 does not), only snapshots that need to be renumbered to make room for the new sv.0 snapshot will be renumbered. In the example, sv.0 and sv.1 would be renamed to sv.1 and sv.2, but sv.3 would remain unchanged.

The cnt in the schedule is interpreted differently for SnapVault secondary SnapLock volumes. For SnapLock secondary volumes, snapshots are created with a name that includes an encoded date and time of when the snapshot is created. These snapshots are never renamed and they are never automatically deleted. These snapshots may be deleted using snap delete after the retention period of the snapshot has expired. If cnt is 0, no snapshots will be taken. If cnt is any non-zero value, snapshots will be taken and no snapshots will be automatically deleted.

If specified, the day_list specifies which days of the week the snapshot should be created. The day_list is a comma-separated list of the first three letters of the day: mon, tue, wed, thu, fri, sat, sun. The names are not case sensitive. Day ranges such as mon-fri can also be given. The default day_list is mon-sun, i.e. every day.

If specified, the hour_list specifies which hours of the day the snapshot should be created, on each scheduled day. The hour_list is a comma-separated list of the hours during the day, where hours are integers from 0 to 23. Hour ranges such as 8-17 are allowed. Also, step values are allowed in conjuction with ranges. For example, 0-23/2 means "every two hours". The default hour_list is 0, i.e. midnight on the morning of each scheduled day.

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

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.

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.

pktt is part of the Data OnTap command set.

The output of pktt is not very human-readable, but it utilizes the tcpdump format which many traffic analyzers can read or import. Only two such analyzers have been offered here.

Wireshark is the successor of Etherreal, and available for several platforms. Netmon is a Microsoft project, available for Windows, soon to be deprecated by the Microsoft Message Analyzer project.