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

https://communities.netapp.com/groups/chris-kranz-hardware-pro/blog/2009/03/05/fractional-reservation--lunoverwrite

From the article:

"If you reduce the Fractional Reservation to 0, you need to make sure the rate of change is within the volume size, or you need to make sure the volume can auto-grow when required or even snap auto-delete to reduce the reserved blocks and free up space (although I am not a huge fan of snap auto-delete for various reasons)."

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

In order to restrict the NetApp secondary systems that are allowed to initiate backups from an OSSV host, the QSM Access List field can be populated with the hostname of the secondary using the OSSV Configurator utility. When using this option, make sure the “Check QSM Access List” box is enabled.

The snapvault.access option on the NetApp secondary can be used to restrict the OSSV hosts that are allowed to initiate restores from that secondary system. This option can be populated with a list of hostnames for each OSSV host. For example:

options snapvault.access host=ossv1,ossv2,ossv3

Screenshot of the svconfigurator GUI; note the QSM access list checkbox and field.

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.

http://hd.kvsconsulting.us/netappdoc/801docs/html/ontap/smg/GUID-866DD79D-D2A6-4FBA-B0BDA63560FECEFF.html

In OnTap 8.0, when NTFS security style is used, only Windows style security objects are used.

For CIFS clients, security is handled using Windows NTFS ACLs.

For NFS clients, the NFS UID (user id) is mapped to a Windows SID (security identifier) and its associated groups. Those mapped credentials are used to determine file access, based on the NFTS ACL.

ifstat -a provides detailed statistics (multiple pages) about all network interfaces.

netstat -i provides a list of connections and open network sockets (listeners).

netdiag -n will perform a diagnostic but does not provide detailed statistics about networking.

sysstat 1 will provide performance statistics but not detailed statistics about networking.

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

For Data ONTAP to obtain the UID and GIDs for a CIFS user, it must first determine the user’s UNIX-style name. It does this through user mapping.

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.

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.