NS0-155 Data ONTAP 7-Mode Administrator Questions and Answers

https://library.netapp.com/ecmdocs/ECMP1196991/html/GUID-06C70D3B-9A06-4D20-B140-EB147B941BDA.html

The data structures that are backed up and restored through SnapVault depend on the primary system.

On systems running Data ONTAP, the qtree is the basic unit of SnapVault backup and restore.

SnapVault backs up specified qtrees on the primary system to associated qtrees on the SnapVault secondary system. If necessary, data is restored from the secondary qtrees back to their associated primary qtrees.

On open systems storage platforms, the directory is the basic unit of SnapVault backup. SnapVault backs up specified directories from the native system to specified qtrees in the SnapVault secondary system.

If necessary SnapVault can restore an entire directory or a specified file to the open systems platform.

The destination system uses a slightly more disk space and directories than the source system.

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

Think of ndmpcopy as a sort of ftp for SAN. You can use it to copy files from one volume to another. Because the file is read from one volume and written to another, the constraints of volume types are not an issue.

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

All the network ports should be assigned correct port roles, and all the network ports should be in the same subnet.

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

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

fcp show adapter [ -v ] [ adapter ]

If no adapter name is given, information about all adapters are shown.

This command displays information such as nodename/portname and link state about the adapter.

If the -v flag is given, this command displays additional information about the adapters.

disk show [ -o < ownername > | -s < sysid > | -n | -v | -a]

Used to display information about the ownership of the disks. Available only on systems with software-based disk ownership. -o lists all disks owned by the filer with the name < ownername > -s lists all disks owned by the filer with the serial number < sysid > -n lists all unassigned disks. -v lists all disks. -a lists all assigned disks.

After you revert a volume to a selected Snapshot copy, you lose all the Snapshot copies that were taken after the selected Snapshot copy.

https://library.netapp.com/ecmdocs/ECMP1196991/html/GUID-80FEDAF8-75FA-4E43-B683-58C1F66B61E2.html

https://communities.netapp.com/servlet/JiveServlet/previewBody/4791-102-2-13466/tr-3466.pdf

Pg 17

OSSV hosts listen for communications from NDMP manager applications on port 10000 by default.

Operations Manager, Protection Manager and Provisioning Manager are all core products of the Unified Manager Platform suite.

snapvault initialize is not a valid command

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

snapvault start -r [options] -S [prim_system:] prim_qtree_path [sec_system:]

sec_qtree_path

pri_qtree_path is not a valid command

http://hd.kvsconsulting.us/netappdoc/801docs/html/ontap/onlinebk/GUID-DB31E1F4-60A8-4F34-A1C4-8F79754E4DE2.html

https://library.netapp.com/ecmdocs/ECMP1196991/html/GUID-06C70D3B-9A06-4D20-B140-EB147B941BDA.html

The data structures that are backed up and restored through SnapVault depend on the primary system.

On systems running Data ONTAP, the qtree is the basic unit of SnapVault backup and restore.

SnapVault backs up specified qtrees on the primary system to associated qtrees on the SnapVault secondary system. If necessary, data is restored from the secondary qtrees back to their associated primary qtrees.

On open systems storage platforms, the directory is the basic unit of SnapVault backup. SnapVault backs up specified directories from the native system to specified qtrees in the SnapVault secondary system.

If necessary SnapVault can restore an entire directory or a specified file to the open systems platform.

The destination system uses a slightly more disk space and directories than the source system.

In takeover mode, this network interface assumes the identity of the network interface on the partner

http://www.wafl.co.uk/tag/ifconfig/#sthash.3rsjaDZD.dpuf

For the partner interface configuration to be persistent across reboots, you must include the ifconfig command in the /etc/rc file

http://hd.kvsconsulting.us/netappdoc/801docs/html/ontap/nag/GUID-525FCF4E-109D-4E6F-9256-C6E56438CA9A.html

https://communities.netapp.com/servlet/JiveServlet/previewBody/4803-102-1-6405/tr-3548.pdf

The maximum cable length supported for 2Gbps is 500m, the same as the max cable length between a NetApp storage system and a FC switch.

Stretch MetroCluster (sometimes referred to as nonswitched) is simply an active-active configuration that can extend up to 500m depending on speed and cable type. It also includes synchronous mirroring (SyncMirror®) and the ability to do a site failover with a single command. See Figure 2. Additional resiliency can be provided through the use of multipathing.

Section: Data Protection

NetApp also recommends that if deduplication is used on the source volume, then it should also be used on the destination volume. However, you are not restricted using deduplication on the source volume only.

The deduplication schedule is not tied to the qtree SnapMirror update. In other words, the deduplication process does not automatically start at the completion of the qtree SnapMirror transfer.

The fingerprint database and the change log files that are used in the deduplication process are located outside of the volume in the aggregate and are therefore not captured in Snapshot copies

http://www.netapp.com/us/media/tr-3505.pdf

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

The following commands are available in the aggr suite:

If you use the -d disk1 [ disk2 ... ] argument, the node creates the aggregate with the specified spare disks disk1, disk2, and so on. You can specify a space-separated list of disk names. Two separate lists must be specified if the new aggregate is mirrored. In the case that the new aggregate is mirrored, the indicated disks must result in an equal number of disks on each new plex.

The disks in a plex are not permitted to span spare pools. This behavior can be overridden with the -f option.

The same option can also be used to force using disks that do not have matching rotational speed. The –f option has effect only when used with the -d option specifying disks to use.

The -m option can be used to specify that the new aggregate be mirrored (have two plexes) upon creation. If this option is given, then the indicated disks will be split across the two plexes. By default, the new aggregate will not be mirrored.

aggr mirror aggrname

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.

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

If no Host Agent is installed, how can the management tool query the host?

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

The fstab file reflects the defined filesystem mount paths (including NFS mounts).

Always check network connectivity when a problem arises with a network service.

The exportfs command will display the active exports on the storage system.

The ' lun ' in the path is irrelevant. The 0 at the end of each statement denotes the LUN ID.

LUN IDs must be unique per igroup.

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

cifs shares -add sharename path

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

The following commands are available in the lun suite:

Easy to use interactive mechanism for setting up initiator groups, LUNs, and mapping configuration.

https://library.netapp.com/ecmdocs/ECMP1120690/html/frameset.html

Changes to deduplication in 8.1 7-mode

Starting with Data ONTAP 8.1, you can enable the deduplication feature without adding a license. For

deduplication, no limit is imposed on the supported maximum volume size. The maximum volume size limit is determined by the type of storage system regardless of whether deduplication is enabled.

https://library.netapp.com/ecmdocs/ECMP1196986/html/GUID-E5AD37DE-2F44-47DB-90A3-C8E115FCBFB7.html

SnapVault replicates at the file level not the block level.

Deduplication is always a post-processed activity for Data OnTap, while compression is an inline process.

The deduplication schedule depends on the SnapVault update schedule on the destination system.

A new Snapshot copy replaces the archival Snapshot copy after deduplication finishes running on the destination system. (The name of this new Snapshot copy is the same as that of the archival copy, but the Snapshot copy uses a new timestamp, which is the creation time.)

The SnapVault update recognizes the deduplicated blocks as changed blocks. Thus, when deduplication is run on an existing SnapVault source for the first time, all saved space is transferred to the destination system.

Section: OnTap Administration

Explanation

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

https://communities.netapp.com/servlet/JiveServlet/previewBody/18684-102-5-34635/TR4090PerformanceAdvisorFeatures%26Diagnosis.pdf

https://communities.netapp.com/groups/chris-kranz-hardware-pro/blog/2009/04/01/performance-stats-withoutperfstat-or-ops-mgr

Note in the diagram below how the performance tools integration with Data OnTap. statit and sysstat interface directly with the performance counters while the other tools - including stats, a command line tool -integrate with the Counter Manager.

http://scst.sourceforge.net/mc_s.html

http://www.alacritech.com/legacypdf/iSCSI_Multiple_Connections.pdf

Meme: Remember the acronym: MCS or MC/S - Multiple Connections per Session. Microsoft Windows 2008 ' s MPIO driver supports MC/S.

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

wafl.default_security_style

Specifies the default security style assigned to a new volume. All qtrees created on the volume get this as their security style. Legal values for this option are `unix ' , `ntfs ' , or `mixed ' . The default value for this option is `unix ' , unless the node is an NTFS-only node, in which case the default is `ntfs ' .

Note: if cifs setup is run after setting wafl.default_security_style, the filer will become an NTFS security style filer.

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

The following commands are available in the lun suite:

Easy to use interactive mechanism for setting up initiator groups, LUNs, and mapping configuration.

lun map [ -f ] lun_path initiator_group [ lun_id ]

Maps a LUN to all the initiators in the supplied group

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.

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.

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

http://www.netapp.com/us/products/platform-os/flashpool.aspx

Flash Pool utilizes SSDs to enhance performance of disk aggregates.

Flash Cache is a controller-attached PCIe intelligent caching solution.

Flash Accel is a host-attached caching solution.

Flash Disk and Flash IO are ambiguous terms.

* Unix-like operating systems identify users within the kernel by an unsigned integer value called a user identifier, often abbreviated to UID or User ID. The range of UID values varies amongst different systems; at the very least, a UID represents a 15-bit integer, ranging between 0 and

The UID value references users in the /etc/passwd file. Shadow password files and Network Information Service also refer to numeric UIDs. The user identifier has become a necessary component of Unix file systems and processes.

* In POSIX-compliant environments the command-line command id gives the user ' s user identifier number as well as more information on the user account like the user name, primary user group and group identifier (GID).

* Files and directories are owned by a user. The owner determines the file ' s owner class. Distinct permissions apply to the owner.

Files and directories are assigned a group, which define the file ' s group class. Distinct permissions apply to members of the file ' s group members. The owner may be a member of the file ' s group.

Users who are not the owner, nor a member of the group, comprise a file ' s others class. Distinct permissions apply to others.

The effective permissions are determined based on the user ' s class. For example, the user who is the owner of the file will have the permissions given to the owner class regardless of the permissions assigned to the group class or others class.

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

SMB 2.0 support was included in Data OnTap 8.1.

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

exportfs [ -v ] [ -io options ] path -i Ignores the options specified for a file system path in the /etc/exports file. If you do not specify the –I option with the -o option, Data ONTAP uses the options specified for the file system path in the /etc/ exports file instead of the options you specify on the command line.

https://library.netapp.com/ecmdocs/ECMP1196986/html/GUID-87340429-8F4A-4AA6-B081-0F5040089C78.html

Data compression requires 64-bit aggregates.

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.

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.

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.

http://www.ntapgeek.com/2011/03/netapp-storage-encryption-available.html

March, 2011: " With the recent release of Data ONTAP 8.0.1, NetApp now offers full disk encryption to prevent unauthorized access to data at rest. "

https://library.netapp.com/ecmdocs/ECMP1196991/html/GUID-35C9A4BA-02BA-4965-A366-698C1299E29D.html

You can restore a file only to the volume where it was originally located. The directory structure to which a file is to be restored must be the same as that specified in the path. If this directory structure does not exist, you must create it before restoring the file.

https://communities.netapp.com/docs/DOC-1059

Performance and Statistics Collector (perfstat) is a data collection tool with several key properties:

Captures all needed performance information with one command

Captures information from host(s) and filer(s)

Captures all information simultaneously for cross correlation

Operates on all host platforms and all filer platforms

All captured data is recorded in a single plain-text output file

Perfstat comes in exactly two flavors:

Unix/Linux version (perfstat.sh)

Windows version (perfstat.exe)

Supported platforms:

Unix: AIX, HP-UX, Linux, OSF1, Solaris, FreeBSD

Windows: 2000/XP/2003

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_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/ECMP1196890/html/man1/na_ifstat.1.html

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

ifstat - display device-level statistics for network interfaces

netdiag - perform network diagnostics

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

snap restore [ -f ] [ -t vol | file ] [ -s snapshot_name ] [ -r restore_as_path ]

vol_name | restore_from_path

Reverts a volume to a specified Snapshot copy, or reverts a single file to a revision from a specified Snapshot copy.

Before reverting the volume or file, the user is requested to confirm the operation. The -f option suppresses this confirmation step.

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

fcp show initiator [ -v ] [ adapter ]

If no adapter name is given, information about all initiators connected to all adapters are shown.

The command displays the portname of initiators that are currently logged in with the Fibre Channel target adapters. If the portname is in an initiator group setup through the igroup command, then the group name is also displayed. Similarly, all aliases set with the fcp wwpn-alias command for the portname are displayed as well.

If the -v flag is given, the command displays the Fibre Channel host address and the nodename/portname of the initiators as well.