Download Network Appliance.NS0-155.Train4Sure.2018-12-09.109q.tqb

https://library.netapp.com/ecm/ecm_download_file/ECMM1278920What 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.

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.

https://library.netapp.com/ecmdocs/ECMP1196979/html/man1/na_snapmirror.1.htmlhttps://library.netapp.com/ecmdocs/ECMP1196979/html/man5/na_snapmirror.conf.5.htmlsnapmirror update [ -S source ] [ -k kilobytes ] [ -s src_snap ] [ -c create_dest_snap ] [ -w ] destination For asynchronous mirrors, an update is immediately started from the source to the destination to update the mirror with the contents of the source. For synchronous mirrors, a snapshot is created on the source volume which becomes visible to clients of the destination volume. The snapmirror update command must be issued on the destination filer. snapmirror release source { filer:volume | filer:qtree }Tell SnapMirror that a certain direct mirror is no longer going to request updates. If a certain destination is no longer going to request updates, you must tell SnapMirror so that it will no longer retain a snapshot for that destination. This command will remove snapshots that are no longer needed for replication to that destination, and can be used to clean up SnapMirror-created snapshots after snapmirror break is issued on the destination side. The source argument is the source volume or qtree that the destination is to be released from. The destination argument should be either the destination filer and destination volume name or the destination filer and destination qtree path. You can use a line from the output of the snapmirror destinations command as the set of arguments to this command. The /etc/snapmirror.conf file exists on the node containing the mirror used for SnapMirror.