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

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

aggr split aggrname/plexname new_aggrname

Removes plexname from a mirrored aggregate and creates a new unmirrored aggregate named

new_aggrname that contains the plex. The original mirrored aggregate becomes unmirrored. The plex to be split from the original aggregate must be functional (not partial), but it could be inactive, resyncing, or out-ofdate.

Aggr split can therefore be used to gain access to a plex that is not up to date with respect to its partner

plex, if its partner plex is currently failed.

If the aggregate in which plexname resides is embedded in a traditional volume, aggr split behaves identically to vol split. The new aggregate is embedded in a new traditional volume of the same name.

The aggregate in which plexname resides must contain exactly one flexible volume, aggr split will by default rename the flexible volume image in the split-off plex to be the same as the new aggregate.

If the original aggregate is restricted at the time of the split, the resulting aggregate will also be restricted. If the restricted aggregate is hosting flexible volumes, they are not renamed at the time of the split. Flexible volumes will be renamed later, when the name conflict is detected while bringing an aggregate online. Flexible volumes in the aggregate that is brought online first keep their names. That aggregate can be either the original aggregate, or the aggregate resulting from the split. When the other aggregate is brought online later, flexible volumes in that aggregate will be renamed.

If the plex of an aggregate embedded within a traditional volume is offline at the time of the split, the resulting aggregate will be offline. When splitting a plex from an aggregate that hosts flexible volumes, if that plex is offline, but the aggregate is online, the resulting aggregate will come online, and its flexible volumes will be renamed. It is not allowed to split a plex from an offline aggregate.

A split mirror can be joined back together via the -v option to aggr mirror.

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

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

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

cifs shares -add sharename path

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

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

igroup show [ -v ] [ initiator_group ] Displays the nodes in an initiator group and their aliases, set with the fcp wwpnalias command. If no initiator_group is specified, the members of all initiator groups are displayed. You can use the -v option to get a verbose listing.

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

lun show [ -v | -m | -c ] [ all | mapped | offline | online | unmapped | staging |

-g initiator_group | -n node | -l vol_name | lun_path ] Displays the status (lun_path, size, online/offline state, shared state) of the given LUN or class of LUNs. With the -v option supplied, additional information (comment string, serial number, LUN mapping, HA Pair Shared Volume Information) is also displayed. With the -m option supplied, information about lun_path to initiator_group mappings is displayed in a table format. With the -c option supplied, information about LUN cloning status is displayed.

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.

Open Systems Snap Vault runs on servers, so the objects that can be selected for backup will be host-based.

Qtrees are objects on the storage system.

SnapRestore overwrites all data in the file or volume. After you use SnapRestore to revert to a selected

Snapshot copy, you cannot undo the reversion.

http://hd.kvsconsulting.us/netappdoc/733docs/html/ontap/onlinebk/GUID-80FEDAF8-75FA-4E43-B683-58C1F66B61E2.html

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