NetApp NS0-155 Online Practice Questions and Exam Preparation

NetApp NS0-155 Online Questions & Answers

• Question 1:

  For OSSV sources, the qtree is the basic unit of SnapVault backups.

  A. True
  B. False
  B. False

  ---

  explanation:

  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.

• Question 2:

  To manage SnapVault relationships with an NDMP management application, you must specify a:

  A. directory path
  B. volume and qtree
  C. SnapVault license
  D. username and password
  D. username and password

  ---

  explanation:

  Add a new backup user to the Backup Operators useradmin group list. Enter the following command:

  useradmin user add backupuser -g "Backup Operators"

  Generate an NDMP password for the new user. Enter the following command:

  ndmpd password backupuser

  The NDMP password is used to authenticate the NetBackup media server to the storage system. This password is required for setup on the NetBackup management station. https://library.netapp.com/ ecmdocs/ECMM1278284/html/

  onlinebk/5snapv37.htm

• Question 3:

  Which three FAS deduplication features exist in ONTAP 8.0 7-Mode?

  A. The deduplication fingerprint and change logs were moved to the root volume /etc/dedup directory.
  B. After breaking the deduplication volume destination mirror, the deduplication (a-sis) process continues uninterrupted.
  C. Qtree SnapMirror is supported on the destination for deduplication by enabling on the source, destination, or both systems.
  D. The fingerprint database and the change logs that the deduplication process uses are located outside the volume, in the aggregate.
  E. The deduplication schedule is not tied to a Qtree SnapMirror update, and can be configured just like the deduplication schedule for any volume.
  C. Qtree SnapMirror is supported on the destination for deduplication by enabling on the source, destination, or both systems.
  D. The fingerprint database and the change logs that the deduplication process uses are located outside the volume, in the aggregate.
  E. The deduplication schedule is not tied to a Qtree SnapMirror update, and can be configured just like the deduplication schedule for any volume.

  ---

  explanation:

  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

• Question 4:

  How do you migrate LUNs under volumes from 32-bit to 64-bit?

  A. lrep
  B. ndmpcopy
  C. rsync
  D. snapvault
  B. ndmpcopy

  ---

  explanation:

  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.

• Question 5:

  What types of migration are supported from 32-bit to 64-bit?

  A. migration of qtrees via QSM
  B. migration of volumes via ndmpcopy
  C. migration of volumes via SnapMirror
  D. Both A and B
  E. Both B and C
  F. Both A and C
  D. Both A and B

  ---

  explanation:

  Volume SnapMirror operates at the physical block level. It replicates the contents of an entire volume, including all Snapshot copies, plus all volume attributes verbatim from a source (primary) volume to a target (secondary) volume. Implicitly,

  the destination volume will be the same as the source volume.

  Since C is incorrect, A and B must be correct.

  Qtree snapmirror operates at the logical level, so it is unimportant that the destination system has a different volume configuration.

  ndmpcopy is similarly operating with data already read from the volume and so the destination volume type is not a consideration.

• Question 6:

  When replicating data between 32-bit and 64-bit aggregates, which two are allowed? (Choose two)

  A. NDMPcopy
  B. QSM
  C. vol copy
  D. VSM
  A. NDMPcopy
  B. QSM

  ---

  explanation:

  http://www.netapp.com/us/system/pdf-reader.aspx?m=tr-3786.pdfandcc=us

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

  Because volume SnapMirror works at the block level, the source and destination must both be FlexVol volumes in the same aggregate type. The source and destination of a volume SnapMirror relationship must either both be FlexVol

  volumes in 32-bit aggregates or both be FlexVol volumes in 64-bit aggregates. Therefore you cannot create a volume SnapMirror relationship from a FlexVol volume in a 32-bit aggregate to a FlexVol volume in a 64-bit aggregate or vice

  versa.

  

• Question 7:

  When troubleshooting a double disk failure with SyncMirror, you decide to remove and destroy a plex from a mirrored aggregate. What steps remove a plex from a mirrored aggregate?

  A. Take the aggregate offline and use the aggr destroy command
  B. Take the aggregate offline and use the destroy -f command
  C. Ensure the plex is online and use the aggr destroy plexname command.
  D. Ensure the plex is offline and use the aggr destroy plexname command.
  D. Ensure the plex is offline and use the aggr destroy plexname command.

  ---

  explanation:

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

  aggr destroy { aggrname | plexname } [ -f ]

  Destroys the aggregate named aggrname, or the plex named plexname. Note that if the specified aggregate is tied to a traditional volume, then the traditional volume itself is destroyed as well. If an aggregate is specified, all plexes in the

  aggregate are destroyed. The named aggregate must also not contain any flexible volumes, regardless of their mount state (online, restricted, or offline). If a plex is specified, the plex is destroyed, leaving an unmirrored aggregate or

  traditional volume containing the remaining plex.

  Before destroying the aggregate, traditional volume or plex, the user is prompted to confirm the operation. The -f flag can be used to destroy an aggregate, traditional volume or plex without prompting the user.

  The disks originally in the destroyed object become spare disks. Only offline aggregates, traditional volumes and plexes can be destroyed.

• Question 8:

  Which SyncMirror command mirrors an existing unmirrored aggregate where Data ONTAP selects the disk drive?

  A. aggr mirror aggrY
  B. aggr mirror aggrY -m
  C. aggr mirror aggrT -d 12@144
  D. aggr mirror aggrY -m 12@144
  A. aggr mirror aggrY

  ---

  explanation:

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

  aggr mirror aggrname

  [ -f ]

  [ -n ]

  [ -v victim_aggrname ]

  [ -d disk1 [ disk2 ... ] ]

  Turns an unmirrored aggregate into a mirrored aggregate by adding a plex to it. The plex is either newlyformed from disks chosen from a spare pool, or, if the -v option is specified, is taken from another existing unmirrored aggregate.

  Aggregate aggrname must currently be unmirrored. Use aggr create to make a new, mirrored aggregate from scratch.

  Disks may be specified explicitly using -d in the same way as with the aggr create and aggr add commands.

  The number of disks indicated must match the number present on the existing aggregate. The disks specified are not permitted to span disk pools. This behavior can be overridden with the -f option. The -f option, in combination with -d, can

  also be used to force using disks that have a rotational speed that does not match that of the majority of existing disks in the aggregate.

  If disks are not specified explicitly, then disks are automatically selected to match those in the aggregate's existing plex.

  The -v option can be used to join victim_aggrname back into aggrname to form a mirrored aggregate. The result is a mirrored aggregate named aggrname which is otherwise identical to aggrname before the operation.

  Victim_aggrname is effectively destroyed. Victim_aggrname must have been previously mirrored with aggrname, and then separated via the aggr split command. Victim_aggrname must be offline. Combined with the -v option, the -f option can

  be used to join aggrname and victim_aggrname without prompting the user.

  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.

• Question 9:

  Which command creates a new SyncMirror aggregate, letting Data ONTAP select the disk drives?

  A. aggr create aggrX -d 12
  B. aggr create aggrX -m 12
  C. aggr mirror aggrX -m 12
  D. aggr mirror aggrX -n 12
  B. aggr create aggrX -m 12

  ---

  explanation:

  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.

• Question 10:

  Which OSSV tool would you use to perform an OSSV unattended installation?

  A. msipackage
  B. svunattendossv
  C. svconfigpackager
  D. unattendpackager
  C. svconfigpackager

  ---

  explanation:

  The reference for this questionis an old version of a TR. It is likely that this question will be removed from the NSO-155 exam.

  The svconfigpackager is a binary in the OSSV client which can be used to create an unattended installation package using an answer file.