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

Aggregates are never converted as part of an upgrade. An upgrade will not touch your data!

The snapmirror.access option is the preferred method for controlling snapmirror access on a snapmirror source filer.

http://www.wafl.co.uk/snapmirrorallow/#sthash.4Cb8IqqN.dpuf

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

lun clone create clone_lunpath [ -o noreserve ] -b parent_lunpath parent_snap

By aligning the performance of the source and destination, optimal data transfer (aka replication) rates can be attained. Flexvols don't matter, and there is no measurable difference between the performance of a network over a 30m or 3m cable.

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

It is important to remember that this is the case only when a complete site is lost. In the case of a failed controller at one of the sites, a normal cluster failover occurs. Due to the operation of SyncMirror, there is also added protection from multidrive or complete shelf failures. When a storage controller fails in an active-active configuration, the partner detects the failure and automatically (if enabled) performs a takeover of the dataserving responsibilities from the failed controller. Part of this process relies on the surviving controller being able to read information from the disks on the failed controller. If this quorum of disks is not available, then automatic takeover won’t be performed. In a MetroCluster configuration, manually executing a single command will allow a takeover to occur in spite of the lack of a quorum of disks. This "forced takeover" process breaks the mirrored relationships in order to bring the failed controller’s volumes on line.

forcetakeover -d is very dangerous. Not only can it cause data corruption, if not used carefully, it can also lead to a situation where both the node and its partner are operational (split brain). As such, it should only be used as a means of last resort when the takeover and forcetakeover commands are unsuccessful in achieving a takeover. The operator must ensure that the partner node does not become operational at any time while a node is in a takeover mode initiated by the use of this command. In conjunction with RAID mirroring, it can allow recovery from a disaster when the two nodes in the HA pair are located at two distant sites.

You can use the snapmirror resync command to reestablish the connection between the source and the destination. This command is applied after the SnapMirror relationship between the source and destination is broken.

https://library.netapp.com/ecmdocs/ECMP1196991/html/GUID-5D846D24-0903-4982-A429-71AE5C0F9033.html

https://library.netapp.com/ecmdocs/ECMP1196991/html/GUID-EEBC8B52-BEA9-4B49-874F-7EC78D3F602E.html

Each open systems platform, when prompted by the secondary system, transfers initial base images of specified directories to qtree locations on the secondary system.

Note: There are no primary-side Snapshot copies in Open Systems SnapVault.

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.

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.

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

https://library.netapp.com/ecmdocs/ECMP1196993/html/GUID-09C7812F-E6EA-47C6-AB79-EAB803E7A8EB.html

If the user names in the UNIX password database are identical to the Windows names, you need not provide the mapping information in the /etc/usermap.cfg file.

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://www.wafl.co.uk/cf/

http://wafl.co.uk/options/

Negotiated failover is a general facility which supports negotiated failover on the basis of decisions made by various modules.

cf.takeover.on_disk_shelf_miscompare

This option allows negotiated takeover to be enabled when the cluster nodes detect a mismatch in disk shelf count. By default, this option is set to off.

This option is available only when cluster is licensed and changing the value on one filer automatically changes the value on the partner filer.

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

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

The following commands are available in the lun suite:

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

The following commands are available in the lun suite:

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

http://www.ntapgeek.com/2011/12/how-in-place-expansion-works.html

To upgrade an aggregate in-place, the only available method is to add disks to expand the aggregate to >16TB.