NETAPP UNIVERSITY. Data ONTAP 7-Mode Administration. Exercise Guide. Course ID: STRSW-ILT-D7ADM-REV02 Catalog Number: STRSW-ILT-D7ADM-REV02-EG

Transcription

1 NETAPP UNIVERSITY Data ONTAP 7-Mode Administration Exercise Guide Course ID: STRSW-ILT-D7ADM-REV02 Catalog Number: STRSW-ILT-D7ADM-REV02-EG

2 ATTENTION The information contained in this course is intended only for training. This course contains information and activities that, while beneficial for the purposes of training in a closed, non-production environment, can result in downtime or other severe consequences in a production environment. This course material is not a technical reference and should not, under any circumstances, be used in production environments. To obtain reference materials, refer to the NetApp product documentation that is located at COPYRIGHT 2015 NetApp, Inc. All rights reserved. Printed in the U.S.A. Specifications subject to change without notice. No part of this document covered by copyright may be reproduced in any form or by any means graphic, electronic, or mechanical, including photocopying, recording, taping, or storage in an electronic retrieval system without prior written permission of NetApp, Inc. U.S. GOVERNMENT RIGHTS Commercial Computer Software. Government users are subject to the NetApp, Inc. standard license agreement and applicable provisions of the FAR and its supplements. TRADEMARK INFORMATION NetApp, the NetApp logo, Go Further, Faster, ASUP, AutoSupport, Campaign Express, Customer Fitness, CyberSnap, Data ONTAP, DataFort, FilerView, Fitness, Flash Accel, Flash Cache, Flash Pool, FlashRay, FlexCache, FlexClone, FlexPod, FlexScale, FlexShare, FlexVol, GetSuccessful, LockVault, Manage ONTAP, Mars, MetroCluster, MultiStore, OnCommand, ONTAP, ONTAPI, RAID DP, SANtricity, SecureShare, Simplicity, Simulate ONTAP, Snap Creator, SnapCopy, SnapDrive, SnapIntegrator, SnapLock, SnapManager, SnapMirror, SnapMover, SnapProtect, SnapRestore, Snapshot, SnapValidator, SnapVault, StorageGRID, Tech OnTap, and WAFL are trademarks or registered trademarks of NetApp, Inc. in the United States and/or other countries. Other product and service names might be trademarks of NetApp or other companies. A current list of NetApp trademarks is available on the Web at E-2 Data ONTAP 7-Mode Administration: Welcome

3 TABLE OF CONTENTS WELCOME... E-1 MODULE 1: THE DATA ONTAP STORAGE ENVIRONMENT... E1-1 MODULE 2: WAFL SIMPLIFIED... E2-1 MODULE 3: BASIC ADMINISTRATION... E3-1 MODULE 4: PHYSICAL STORAGE... E4-1 MODULE 5: LOGICAL STORAGE... E5-1 MODULE 6: ADMINISTRATION SECURITY... E6-1 MODULE 7: NETWORKING... E7-1 MODULE 8: NFS... E8-1 MODULE 9: CIFS... E9-1 MODULE 10: NAS MANAGEMENT... E10-1 MODULE 11: SAN... E11-1 MODULE 12: SNAPSHOT COPIES... E12-1 MODULE 13: SPACE MANAGEMENT... E13-1 MODULE 14: HIGH AVAILABILITY (OPTIONAL EXERCISE)... E14-1 MODULE 15: VIRTUALIZATION SOLUTIONS... E15-1 MODULE 16: BACKUP AND RECOVERY METHODS... E16-1 MODULE 17: DATA COLLECTION TOOLS... E17-1 MODULE 18: DATA ONTAP UPGRADES... E18-1 APPENDIX A: ANSWERS... A-1 E-3 Data ONTAP 7-Mode Administration: Welcome

4 MODULE 1: THE DATA ONTAP STORAGE ENVIRONMENT EXERCISE BASIC ADMINISTRATIVE OPERATIONS This course covers basic administrative operations for Data ONTAP 8.2 operating in 7-Mode. You will be working with simulated hardware platforms for Data ONTAP 8.2 operating in 7-Mode, along with a Microsoft Windows 2012 Server virtual machine and a Linux virtual machine. OBJECTIVES By the end of this exercise, you should be able to: Identify the exercise environment Explore the NetApp Support site TASK 1: IDENTIFY THE EXERCISE ENVIRONMENT This task familiarizes you with the exercise environment that you use for all exercises in this course. 1. With the assistance of your instructor, identify the following essential information: Windows Server Name: Windows Server IP address: Domain administrator Domain administrator s password: 2. With the assistance of your instructor, identify the following essential equipment: First storage system name: Ethernet IP address (e0a): User name: Root password: 3. Use PuTTY to log into the first storage system node. Run this version command: system> version Record the version: E1-1 Data ONTAP 7-Mode Administration: The Data ONTAP Storage Environment

5 4. With the assistance of your instructor, identify the following essential equipment: Second storage system name: Ethernet IP address (e0a): User name: Root password: 5. Use PuTTY to log into the second storage system node. Run this version command: system> version Record the version: 6. With the assistance of your instructor, identify the following essential equipment: UNIX Host Name: IP address: User name: Password: 7. Use PuTTY to log into the UNIX host. Run this version command. # cat /etc/*release* Record the version: E1-2 Data ONTAP 7-Mode Administration: The Data ONTAP Storage Environment

6 TASK 2: EXPLORE THE NETAPP SUPPORT SITE This task familiarizes you with the NetApp Support site, which is a vital tool for any NetApp storage administrator. Answers are in Appendix A of this guide. 1. Open a browser and go to the NetApp Support site at 2. Enter your NetApp user ID and password to log in. 3. Click My Home at the top of the page. 4. Notice the categories that appear across the top of the home page, and list the seven main categories here: 5. Click the documentation link, and navigate through the link to locate the documentation for Data ONTAP operating in 7-Mode. 6. Select All documents. 7. Locate the Data ONTAP Mode System Administration Guide link in HTML, and answer the following questions: 1. What are the methods for accessing the system? 2. What is the command to display the storage system s hardware configuration? END OF EXERCISE E1-3 Data ONTAP 7-Mode Administration: The Data ONTAP Storage Environment

7 MODULE 2: WAFL SIMPLIFIED EXERCISE: DESCRIBING THE WAFL FILE SYSTEM In this exercise, you review how the Data ONTAP operating system and the WAFL (Write Anywhere File Layout) file system execute write and read requests. OBJECTIVES By the end of this exercise, you should be able to: Explain how the Data ONTAP operating system writes data Explain how the Data ONTAP operating system reads data TASK 1: EXPLAIN HOW THE DATA ONTAP OPERATING SYSTEM WRITES DATA In this task, you answer true-or-false questions. 1. WAFL write requests are stored in a buffer in memory, and a copy is added to the NVLOG RAM log. 2. The RAID manager determines where data will go on the disk. 3. The RAID layer transfers data to the physical disks. 4. The WAFL file system acknowledges a write request when the data is physically stored to disk and a consistency point is complete. E2-1 Data ONTAP 7-Mode Administration: WAFL Simplified

8 TASK 2: EXPLAIN HOW THE DATA ONTAP OPERATING SYSTEM READS DATA In this task, you answer true-or-false questions. 1. Read requests are always processed from the disk. 2. A consistency point is a completely self-consistent image of the entire file system that is created when all of the data is written to the disks and a new root inode is determined. 3. A consistency point is initiated when the NVLOG is half full (single controller), after 10 seconds have elapsed, when a Snapshot copy is created, or when the system is halted. 4. Nonvolatile RAM (NVRAM) logs are flushed when a consistency point is completed. END OF EXERCISE E2-2 Data ONTAP 7-Mode Administration: WAFL Simplified

9 MODULE 3: BASIC ADMINISTRATION EXERCISE: PERFORMING BASIC ADMINISTRATION TASKS In this exercise, you initiate a CLI SSH session to the Data ONTAP operating system. After logging in, you execute commands on the NetApp storage system. You also use NetApp System Manager to explore administration of the storage system. OBJECTIVES By the end of this exercise, you should be able to: Log in to the exercise environment Install System Manager Add a storage system to System Manager Use the CLI to access a storage system Explore the help command and privilege levels List the options on a storage system Use the CLI to examine the system configuration of a storage system Use System Manager to configure the DNS (Optional) Use System Manager to configure the AutoSupport support tool TASK 1: LOG IN TO THE EXERCISE ENVIRONMENT In this task, you use the Remote Desktop Connection tool to log in to your assigned exercise environment from your local Windows machine. 1. Click the Remote Desktop Connection link on your desktop. If this link is not available, ask your instructor where to find the tool. 2. In the Computer text box, type your IP address, and then click Connect. 3. If you are prompted to provide authentication, enter the user name and password that your instructor gave you. When the connection is made, the desktop of the remote machine appears. You initiate subsequent tasks from this remote machine. E3-1 Data ONTAP 7-Mode Administration: Basic Administration

10 TASK 2: INSTALL SYSTEM MANAGER 1. On your assigned remote Windows machine, open Windows Explorer and navigate to C:\CourseFiles. NOTE: You might have a shortcut on your desktop to facilitate this step. 2. Double-click sysmgr-setup-3-0-win.exe and, if you are prompted with a security warning, confirm by clicking Run. The installation wizard launches. 3. Click Next to start the wizard. 4. On the license agreement, select I Agree, and then click Next. 5. Accept the default installation location and click Next. 6. Click Next again to accept the Automatically select port number radio button. After the installation is complete, a dialog box indicates that the installation was successful. 7. Click Finish to close the installation dialog box. TASK 3: ADD A STORAGE SYSTEM TO SYSTEM MANAGER In this task, you add a storage system to NetApp System Manager so that you can manage the storage system later. Answers are in Appendix A of this guide. 1. Double-click the NetApp System Manager 3.0 icon on your Windows desktop. NOTE: When you first launch the NetApp System Manager application, you see the Welcome to NetApp System Manager page. 2. Perform these steps: a. If you see a dialog box that asks you for an application update, click the Remind me later button. b. Then click Tools > Options and clear the Check if new version of System Manager is available checkbox. c. Click the Save and Close button. d. If prompted to Refresh all open instances of OnCommand System Manager, click OK to apply the changes. E3-2 Data ONTAP 7-Mode Administration: Basic Administration

11 3. On the Home page, click Add to open the Add a System dialog box. 4. In the Host Name or IP Address text box, enter the management IP address or host name of the storage system that was assigned to you, and then click Add. The system is added to System Manager. 5. Double-click the new node. 6. In the Enter Credentials box, enter the user name and password that were provided to you, and click Sign in. E3-3 Data ONTAP 7-Mode Administration: Basic Administration

12 7. When the dashboard panels for your storage system appear, read the panel names, and answer the question that follows. Which six sections of information do you see? In the left pane, click your storage system, and then continue to expand the left pane s tree menu levels by clicking the > symbols. 9. Notice the categories in the left pane. E3-4 Data ONTAP 7-Mode Administration: Basic Administration

13 TASK 4: USE THE CLI TO ACCESS A STORAGE SYSTEM In this task, you use Secure Shell (SSH) to log in to the CLI. 1. On your desktop, double-click the link to PuTTY. 2. If necessary, enter the IP address of your assigned storage system e0a interface, and select SSH. NOTE: Fresh installs (nonupgrades) of Data ONTAP systems and later operating in 7- Mode default to secure protocols. Therefore, SSH is required. There may be a saved session that you can use to connect to your assigned storage system. If so, then use that session, log in with your root credentials, and skip to step Enter a name in the Saved Sessions text box and click Save to save this configuration for future use. 4. Click Open to open a session with your storage system. 5. In the PuTTY Security Alert dialog box, click Yes. The host is trusted, because you are using SSH. 6. Try a few commands: system> date system> ifconfig a 7. Answer this question: What does the ifconfig command display? 8. Use the sysconfig d command to list the entire disk HA.IDs (device names), along with shelf, bay, and disk serial numbers. Note that for simulated disks the shelf and bay are not populated. system> sysconfig -d TASK 5: EXPLORE THE HELP COMMAND AND PRIVILEGE LEVELS 1. If you have not done it already, access the CLI by establishing an SSH. system> 2. Enter help to see the available commands. system> help E3-5 Data ONTAP 7-Mode Administration: Basic Administration

14 3. Type the question mark (?) character and compare the output to the output of the help command, then answer this question: Do you see the same results? 4. Enter a command, followed by help, then answer the question that follows. Example: system> license help How does using the help command by itself differ from appending help to a command? 5. From the command line, use the man command followed by the useradmin command to view the manual page for useradmin: system> man useradmin 6. From NetApp System Manager, navigate to the help page for adding users. 7. Compare the NetApp System Manager help page with the output of the man command for the same command, and then compare a few other commands. 8. Read the manual page for the priv command: system> man priv 9. Answer this question: What does the q argument do? (Bonus question: When would it be useful?) 10. Run the disk command and note which subcommands are available: system> disk 11. Change to the advanced privilege level and issue the disk command again, then answer the question that follows: system> priv set advanced system*> disk Do you see any new commands? 12. Reset to the admin level: system> priv set admin 13. Verify the services that are available on your storage system: system> license E3-6 Data ONTAP 7-Mode Administration: Basic Administration

15 TASK 6: LIST THE OPTIONS ON A STORAGE SYSTEM 1. From the storage system CLI, enter the options command, and answer the question that follows. system> options What happens? 2. At the prompt, enter the following command, and answer the question that follows: system> man options What happens? 3. To quit the manual page, enter q. 4. At the prompt, enter the following commands, and answer the question that follows: system> options ssh system> options telnet What are the results? E3-7 Data ONTAP 7-Mode Administration: Basic Administration

16 TASK 7: USE THE CLI TO EXAMINE THE SYSTEM CONFIGURATION OF A STORAGE SYSTEM In this task, you explore the sysconfig command to determine which resources are available on the storage system. 1. From the storage system CLI, enter the sysconfig command, and answer the question that follows: system> sysconfig What happens? 2. Enter man sysconfig and determine the correct argument to verify that the expansion cards are in the appropriate slots. system> man sysconfig 3. Compare the outputs of sysconfig a and sysconfig v and answer the question that follows: system> sysconfig a system> sysconfig -v Do you notice any differences? 4. Access System Manager for this storage system and examine the Properties box within the dashboard page, then answer the following question: How does the information from the sysconfig command compare with what you can find by using System Manager? E3-8 Data ONTAP 7-Mode Administration: Basic Administration

17 TASK 8: USE SYSTEM MANAGER TO CONFIGURE THE DNS 1. In the left pane, expand Configuration > Network > DNS. 2. If necessary, configure your storage system for DNS as follows: Click Edit. 3. In the Edit DNS Settings window, on the General tab, enter the DNS settings: a. Select the Enable DNS checkbox. b. Enter the DNS domain name that is appropriate in your environment. c. In the DNS Servers area, in the Server address text box, enter the server address of your first DNS. d. Click Save and Close. TASK 9: (OPTIONAL) USE SYSTEM MANAGER TO CONFIGURE THE AUTOSUPPORT TOOL NOTE: Your exercise environment must be configured for SMTP traffic. Please contact your instructor to see if this task can be completed successfully in your environment. 1. In the left pane, expand Configuration > System Tools > AutoSupport. E3-9 Data ONTAP 7-Mode Administration: Basic Administration

18 2. Click Enable to turn on AutoSupport. 3. Click Edit. The Edit AutoSupport Settings dialog box appears. 4. On the Recipient tab, enter configuration information: a. In the From Address text box, enter b. In the Recipients area, click Add. c. Enter an address in the format where # is the number that was given to you by your instructor and mailhost is the host name or IP address of your mail host. d. In the Mail Hosts text box, enter the IP address of your classroom mail host. Typically, the mail host is the UNIX machine in your exercise environment. 5. On the Others tab, select a transport protocol: a. From the Transport protocol list, select SMTP. b. Click OK. 6. Click OK to finish configuring the AutoSupport support tool. 7. Click Test to generate a test message. 8. In the AutoSupport subject field, enter Test Mail and click Test. 9. When you are notified that the test message was successfully generated, click OK. END OF EXERCISE E3-10 Data ONTAP 7-Mode Administration: Basic Administration

19 MODULE 4: PHYSICAL STORAGE EXERCISE: EXPLORING DISKS AND AGGREGATES In this exercise, you use the CLI and System Manager to explore how disks and aggregates work on a storage system. OBJECTIVES By the end of this exercise, you should be able to: Explore the current disk configuration Understand the impact of disk scrub on a storage system Run the Storage Configuration Wizard Create a 64-bit aggregate Create a 32-bit aggregate and upgrade to 64-bit Cause a disk to fail Add disks to an aggregate TASK 1: EXPLORE THE CURRENT DISK CONFIGURATION 1. Use the CLI to log in to the storage system. 2. Enter this command: system> sysconfig r How many parity disks are in /aggr0/plex0/rg0? How many data disks are there? What are the disk sizes? 3. Enter this command: system> sysconfig c Are there any configuration errors? 4. Enter this command: system> aggr status What is the state and status of aggr0? 5. Enter the following commands to investigate the types of disks that are connected to the storage system and ensure that all disks are assigned: system> disk show system> disk show n 6. If there are unowned disks, enter the following command to assign all the disks to the current node. system> disk assign all E4-1 Data ONTAP 7-Mode Administration: Physical Storage

20 TASK 2: UNDERSTAND THE IMPACT OF DISK SCRUB ON A STORAGE SYSTEM In this task, you answer the questions based on what you learned from the lecture for the module. Then you use your assigned storage system to run a disk scrub. 1. Answer these questions: True or false? RAID scrubbing identifies media errors and rewrites information to another location on the disk. True or false? Increasing the time interval during which the system can operate in degraded mode is a smart and safe way of handling the system so that you don t need to reboot every 24 hours. True or false? Two RAID groups of 10 disks each are more fault-tolerant for critical data than a RAID group of 20 disks. True or false? The Data ONTAP operating system automatically identifies an unqualified disk. True or false? A RAID group with 18 SAS disks is recommended for optimal performance and fault tolerance. Which options command enables you to set scrub performance? a) options raid.reconstruct_speed b) options raid.scrub.perf_impact c) options disk scrub d) options disk.performance.cpu 2. Issue this command to view system statistics every second: system> sysstat 1 When you are ready, use Ctrl-C to stop this command. Can you confirm whether or not the disks are in use from the output? 3. Issue this command to view more information from the sysstat command: system> sysstat x s 1 Use Ctrl-C to stop this command to stop execution of this command. What does this command do? 4. Start the disk scrub by entering this command: system> aggr scrub start Is there any visible sign that the scrub has begun? E4-2 Data ONTAP 7-Mode Administration: Physical Storage

21 5. While the disk scrub is running, issue the following command: system> sysstat 1 Use Ctrl-C to stop the execution of this command. How does this output compare to the output before the disk scrub? 6. Enter this command to stop the scrub: system> disk scrub stop TASK 3: RUN THE STORAGE CONFIGURATION WIZARD In this task, you use the Storage Configuration Wizard to provision the storage. 1. In the left pane, click Storage. If you do not see the left pane, double-click your storage system name. 2. Click the Storage Configuration Wizard. The wizard launches. 3. On the Welcome page of the wizard, click Next. E4-3 Data ONTAP 7-Mode Administration: Physical Storage

22 4. On the Configure Aggregates page, select Manually create aggregates because you do not want to create an aggregate with all of the remaining disks. 5. Click Next. 6. Click Finish to close the wizard. TASK 4: USE NETAPP SYSTEM MANAGER TO CREATE A 64-BIT AGGREGATE 1. In the left pane, expand Storage > Aggregates and notice that only one aggregate (aggr0, the default aggregate) is currently available. 2. In the right pane, click Create to start the Create Aggregate Wizard. E4-4 Data ONTAP 7-Mode Administration: Physical Storage

23 3. Click Next. The Aggregate Details page appears. 4. In the Aggregate Name field, enter aggr1 and retain the default values for RAID Type. 5. Click Next. 6. Click the Select disks button, select FCAL and change the number of capacity disks to use to Click Save and Close. 8. On the Create Aggregate Wizard page, click Create. 9. After the wizard successfully creates the aggregate, click Finish. 10. In the Aggregates pane, verify that the aggregate that you created is included in the list of aggregates. This aggregate has five disks. Is the available space five times the size of one disk? Explain why or why not. E4-5 Data ONTAP 7-Mode Administration: Physical Storage

24 TASK 5: USE THE CLI TO CREATE A 64-BIT AGGREGATE 1. Determine which aggregates are currently on the storage system: system> aggr status 2. Create a 64-bit aggregate called aggr2 with five disks: system> aggr create aggr Verify that you have created the aggregate: system> aggr status What is the default RAID type of an aggregate? NOTE: By default, Data ONTAP 7-Mode creates 64-bit aggregates. Creating a 32-bit aggregate is an advanced command: 7Node1> priv set advanced Warning: These advanced commands are potentially dangerous; use them only when directed to do so by NetApp personnel. If you want to create a 32-bit aggregate, use the option B 32 in the command: 7Node1*> aggr create aggr3 -B 32 5 TASK 6: CAUSE A DISK TO FAIL 1. At the storage system CLI, enter one of these two commands to view the disk ID numbers for aggr1: system> aggr status aggr1 r system> sysconfig r 2. Record the ID of a disk in aggr1. Are there any failed disks? 3. At the storage system CLI, enter this command: system> options raid.reconstruct.perf_impact high 4. Verify the current aggregates: system> aggr status E4-6 Data ONTAP 7-Mode Administration: Physical Storage

25 5. At the storage system prompt, enter this command: system> disk fail <device_id_from_step_1> Note: use the ID of the disk that was identified and recorded in step 1 a) of this task. What messages were displayed on the CLI? 6. Answer y to prefail the disk. What would happen if you failed a disk in aggr1 with no hot spare available? 7. When the reconstruction is complete, make sure that the failed (broken) disk is available for use later in the class by entering the following at the storage system CLI: NOTE: Wait until the reconstruction is complete before you continue. system> sysconfig r system> priv set advanced system> disk unfail <disk id> system> priv set system> sysconfig -r system> disk zero spares TASK 7: ADD DISKS TO AN AGGREGATE 1. Access the storage system CLI. 2. Determine the availability of hot spares: system> sysconfig -r 3. View automatic disk selection: system> aggr add aggr1 n 1 What output is returned on the CLI? NOTE: This command does not add a disk to the aggregate aggr1. 4. Copy the returned command, enter it at the storage system prompt, and view the output. E4-7 Data ONTAP 7-Mode Administration: Physical Storage

26 5. Verify the addition of a disk: system> sysconfig r 6. View the aggregate s options: system> aggr options aggr1 7. Change the aggr1 RAID type to RAID 4: system> aggr options aggr1 raidtype 4 8. Change the aggr1 RAID type to RAID DP: system> aggr options aggr1 raidtype dp NOTE: There are no volumes in this aggregate yet. You add volumes in the next module. However, if you had created a volume for this aggregate, you could enter the following at the storage system CLI to view the activity for the RAID-type change. system> sysstat 1 The output from this command would show two to three times more reads than writes. The system would be computing the double parity and writing it to the dp disk. 9. Press Ctrl-C to stop the display. 10. Open System Manager and, in your storage system tree, expand Storage > Aggregate. 11. If six disks are not displayed for aggr1, click the Refresh button. 12. In the left pane, click Disks. 13. Use System Manager, figure out how to add a spare disk to aggr1. END OF EXERCISE E4-8 Data ONTAP 7-Mode Administration: Physical Storage

27 MODULE 5: LOGICAL STORAGE EXERCISE: WORKING WITH FLEXIBLE VOLUMES AND QTREES In this exercise, you use System Manager and the CLI to create and delete flexible volumes and qtrees on the storage system. OBJECTIVES By the end of this exercise, you should be able to: Create a flexible volume by using NetApp System Manager Resize a volume Destroy a volume Create qtrees Delete qtrees TASK 1: USE SYSTEM MANAGER TO CREATE A VOLUME In this task, you create a flexible volume in the aggr1 aggregate. 1. In System Manager, in the left pane, expand Storage > Volumes. The Volumes page appears. 2. Click Create. E5-1 Data ONTAP 7-Mode Administration: Logical Storage

28 3. In the Create Volume dialog box, enter volume configuration information: a. In the Name text box, type NASvol. b. In the Aggregate text box, type aggr1. c. Enter 1 GB for the total size. NOTE: Although flexible volumes can grow as needed, you should start with a reasonable size. Although 1 GB would be tiny in a real-life scenario and is unusually small for a simulated environment, it is sufficient for this exercise. d. Accept the default percentage for the Snapshot reserve, 5. e. Select the Thin Provisioned check box. 4. Click Create to add your new volume. How much space is available for data? E5-2 Data ONTAP 7-Mode Administration: Logical Storage

29 TASK 2: RESIZE A VOLUME 1. In the main pane, select NASvol. 2. Click the Resize button. The Volume Resize Wizard appears. 3. Click Next. 4. Set the total capacity of NASvol to 1.5 GB. 5. Click Next. The Delete Snapshot Copies page appears. It lists Snapshot copies that can be deleted to reclaim space. 6. Click Next. 7. Review the Summary Page and click Next. 8. Verify that the resizing of NASvol was successful, click Next and click Finish to complete the wizard. 9. From the CLI, check the status and size of the volume: system> vol status NASvol system> df h NASvol 10. Resize the volume to 2 GB: system> vol size NASvol 2g system> vol status NASvol system> df h NASvol E5-3 Data ONTAP 7-Mode Administration: Logical Storage

30 TASK 3: DELETE A VOLUME Occasionally, you will want to delete a volume. Perhaps a volume was created accidentally or perhaps you want to delete a volume to create more space on an aggregate. In this task, you delete a volume by using System Manager and by using the CLI. 1. From the System Manager console tree, click your storage system to display a subtree of management features. 2. Click Storage > Volumes. The Volumes page appears. 3. Select the NASvol volume, then click Status > Offline. 4. In the Offline Volume dialog box, click Offline to confirm. 5. Select the NASvol volume and click Delete. The system displays a confirmation window. 6. Select the OK to delete the volume(s) and all its data check box and click Delete. 7. From the CLI, create a volume and check its status: system> vol create vol1 aggr1 100m system> vol status vol1 8. Take the volume offline: system> vol offline vol1 system> vol status vol1 9. Delete the volume: system> vol offline vol1 system> vol destroy vol1 E5-4 Data ONTAP 7-Mode Administration: Logical Storage

31 10. Enter y to confirm deletion. 11. Check the status: system> vol status 12. Use either System Manager or the CLI to create a 1-GB volume that is called NASvol in aggr1, with the default Snapshot reserve (5%). 13. Fully provision this volume. TASK 4: CREATE QTREES 1. In NetApp System Manager, in the left pane, expand Storage > Qtree. The Qtree page appears. 2. Click Create. 3. In the Create Qtree dialog box, enter qtree configuration information: a. Enter the name NASqt1. b. Enter the volume name NASvol. c. Enable oplocks. d. Select the UNIX security style. 4. Click Create. How much space is available for data in the NASqt1 qtree? 5. From the CLI, create another qtree in NASvol called NASqt2: system> qtree create /vol/nasvol/nasqt2 system> qtree status 6. In NetApp System Manager, expand Storage > Qtrees, and note that NASqt2 now appears on the list of qtrees. E5-5 Data ONTAP 7-Mode Administration: Logical Storage

32 TASK 5: DELETE QTREES 1. In the left pane, expand Storage > Qtree. The Qtree page appears. 2. Select NASqt2 and click Delete. A confirmation dialog box appears. 3. Select the OK to delete the qtree(s) check box and click Delete. NASqt2 should no longer be on the list of qtrees. 4. From the CLI, change the interface to the advanced privilege set: system> priv set advanced 5. Delete the NASqt1 qtree from the NASvol volume: system*> qtree delete /vol/nasvol/nasqt1 6. Reset the interface for the default privilege set and verify that the qtree was deleted: system*> priv set system> qtree status END OF EXERCISE E5-6 Data ONTAP 7-Mode Administration: Logical Storage

33 MODULE 6: ADMINISTRATION SECURITY EXERCISE: WORKING WITH USER ACCOUNTS, GROUPS, AND ROLES In this exercise, you set up a storage system with a local user account. You then associate the user account with groups and associate the groups with roles. OBJECTIVES By the end of this exercise, you should be able to: Use System Manager to create an administrative user account Use the CLI to configure administrative security Log in with a new user account TASK 1: USE SYSTEM MANAGER TO CREATE AN ADMINISTRATIVE USER ACCOUNT In this task, you use NetApp System Manager to create a user account. Answers are in Appendix A of this guide. 1. In NetApp System Manager, in the left pane, click Configuration > Local Users and Groups > Users. 2. Click Create. The Create User dialog box appears. 3. In the Create User dialog box, enter the configuration information that is displayed here: a. User Name: Fred b. Full Name: Long c. Description: Backup Admin d. Password: Netapp123 e. Confirm Password: Netapp123 f. Group: Administrators NOTE: User names are case-insensitive. Therefore, you cannot create a user named fred if you already have a user named Fred. You can have a maximum of 96 administrative users on a storage system. By default, the Data ONTAP 8.0 operating system and later require hardened security password policies. Provide a strong password. 4. Click Create. 5. Open a CLI session to your storage system to test the new user account and, at the login prompt, enter the new user name and the new password, then answer this question: Are you able to log in? 6. In NetApp System Manager, click Configuration > Local Users and Groups > Groups. E6-1 Data ONTAP 7-Mode Administration: Administration Security

34 7. Select Administrators (the group in which you placed your new user) and click Edit. The Properties dialog box for the group appears. NOTE: A dialog box that says CIFS Not Running appears. Click OK. 8. On the General tab, verify that your newly created user belongs to this group. 9. Click the Roles tab and notice which roles are associated with this group. NOTE: You cannot create a role by using System Manager. 10. When you are finished, click Cancel. TASK 2: USE THE CLI TO CONFIGURE ADMINISTRATIVE SECURITY In this task, you use the CLI of your assigned storage system and create a role, a group, and a local user. 1. Use a CLI session or the console to access the CLI. 2. Check the current security options to determine password rules, and answer the question that follows: system> options security What is the value for the security.passwd.rules.enable option? NOTE: When the security.passwd.rules.enable option is set to on, the password for the new local user must meet these criteria: It must be at least eight characters long. It must contain at least two alphabetic characters. It must contain at least one digit. If the security.passwd.rules.enable option is set to off, then these restrictions are not enforced when you create a password. 3. Create a role that includes only the capability to log in to the storage system through the console: system> useradmin role add r_login a login-telnet,login-ssh NOTE: If you want to enable users with this role to successfully log in by using the console port, you must add the login-console option to the command. 4. Create a storage system group that is associated with the new role (r_login): system> useradmin group add g_login r r_login 5. Add a local user (with your name) to the storage system group called g_login: system> useradmin user add <your_name> g g_login NOTE: User names are not case-sensitive. 6. Enter a password for the user and record it here: (suggestion: Netapp123) E6-2 Data ONTAP 7-Mode Administration: Administration Security

35 7. Verify that the local user was added to the storage system, and answer the question that follows: system> useradmin user list your_name system> useradmin role list What are the allowed capabilities for this user? 8. Verify the allowed capabilities for the root account, and answer the question that follows: system> useradmin user list root What are the allowed capabilities for the root user? 9. View the list of all local storage system users, and answer the question that follows: system> useradmin user list Which local users are listed? TASK 3: LOG IN WITH A NEW USER ACCOUNT In this task, you use the user account that you created in Task 2 to log in to the console. 1. Press Ctrl-D to log out of your current CLI session. 2. Use a new CLI session to access the CLI. 3. Log in as your_name and enter the password that you created earlier. 4. At the storage system prompt, view the RAID group configuration, and answer the questions that follow: system> sysconfig -r What was the response? Which capability do you need in order to execute this command? 5. Press Ctrl-D to log out of your current CLI session. 6. Use a new CLI session to access the CLI. 7. Log in as root. E6-3 Data ONTAP 7-Mode Administration: Administration Security

36 8. Modify the role to grant your user the capability that is required to issue the sysconfig command: system> useradmin role modify r_login a login-telnet,login-ssh,clisysconfig NOTE: If you want to enable users with this role to successfully log in by using the console port, you must add the login-console option to the command. You must specify all the capabilities for the role when you modify it. 9. Press Ctrl-D to log out of your current CLI session. 10. Use a new CLI session to access the CLI. 11. Log in as your_name and enter the password that you created earlier. 12. At the storage system prompt, view the RAID group configuration and answer the question that follows: system> sysconfig -r Did the command execute properly? END OF EXERCISE E6-4 Data ONTAP 7-Mode Administration: Administration Security

37 MODULE 7: NETWORKING EXERCISE In this exercise, you configure network settings and host name resolution in the Data ONTAP operating system. NOTE: Depending on your environment, your instructor might request that you use a different interface than the one that is mentioned for the tasks in this module. If you have any questions, ask your instructor. OBJECTIVES By the end of this exercise, you should be able to: Configure network settings by using System Manager Configure network settings by using the CLI Create a single-mode interface group by using the CLI Create a multimode interface group by using the CLI TASK 1: USE THE SYSTEM MANAGER TO CONFIGURE NETWORK SETTINGS In this task, you create an interface group from the interface for data traffic using e0b and e0c. Follow best practices and use only e0a or e0m (if available) as the management port. 1. In System Manger, in the left pane, expand Configuration > Network > Network Interfaces. 2. Click Create VIF to start the Create VIF wizard, and then click Next. E7-1 Data ONTAP 7-Mode Administration: Networking

38 3. Enter VIF parameters: a. In the Virtual Interface (VIF) Name text box, type igmain. b. In the Interfaces linked to VIF area, perform one of these actions: If the e0c and e0d interfaces are listed, select the e0c and e0d check boxes. If you don t see one or both of these interfaces in the list, exit the wizard and verify that the required interfaces are disabled. An interface that doesn t appear is probably being used. c. In the Trunk Mode area, select the Single option. d. Click Next. 4. On the Network Interface Configuration Option page, select the This interface will not be part of another virtual interface option, and click Next. 5. Add the IP address and subnet mask provided by your instructor, verify that the Trusted Network check box is selected, and click Next. 6. Review the configuration and click Next to create the interface group. 7. Click Finish. 8. Verify that the new interface group is included on the list of interfaces. TASK 2: USE THE CLI TO CONFIGURE NETWORK SETTINGS In this task, you configure network settings and answer various questions. Answers are in Appendix A of this guide. 1. Open PuTTY and access the CLI. 2. At the command prompt, enter the ifconfig command without any options to see the syntax information. system> ifconfig E7-2 Data ONTAP 7-Mode Administration: Networking

39 3. Display all of your interface configuration settings: system> ifconfig a 4. Notice that the igmain interface group, which you created in the previous task, is displayed. 5. Display the configuration settings for the e0a interface: system> ifconfig e0a Record the values below. Interface name: Is the interface up or down? IP address: Netmask value: Media type: 6. Change the IP address of the e0a interface for the system: system> ifconfig e0a XX In this command, XX is the last octet of your storage system s IP address. The PuTTY session terminates. NOTE: Changing the IP address using ifconfig is not persistent across reboots. To make the IP address persistent across reboots, you must also edit the /etc/rc and /etc/hosts files. 7. Use the e0b address to connect to the storage system. 8. Take the e0a interface down: system> ifconfig e0a down 9. Re-enter the correct network information for the interface: system> ifconfig e0a <original_ip address> 10. Bring the interface back up: system> ifconfig e0a up 11. Using the storage system IP address or name, open a telnet session to the storage system. You can use PuTTY to open the session. Were you able to connect? E7-3 Data ONTAP 7-Mode Administration: Networking

40 TASK 3: USE THE CLI TO CREATE A SINGLE-MODE INTERFACE GROUP In this task, you review the purpose of interface groups and create a single-mode interface group. 1. Answer these questions: Which statement describes the purpose of a single-mode interface group? a. A single-mode interface group provides failover if one port fails. b. A single-mode interface group provides load-balancing capabilities. c. A single-mode interface group provides security. d. A single-mode interface group allows you to configure the interface to work for only one client at a time, thus improving performance. Which two of these statements describe what a multimode interface does? (Choose two.) a. Provides failover if one port fails b. Provides load-balancing capabilities c. Provides more security options d. Allows you to configure the interface to work for only one client at a time, thus improving performance How many interfaces can you configure in a multimode interface group? a. One or more b. Two or more 2. Open a console session to the storage system. 3. At the command prompt, verify your current interfaces: system> ifconfig a 4. Disable the interface group that you created in System Manager: system> ifconfig igmain down 5. Destroy the interface group that you created in System Manager: system> ifgrp destroy igmain NOTE: You must also remove the reference to igmain from the /etc/rc file. 6. Choose two unused and disabled interfaces to add to this new interface group. NOTE: You can use e0c and e0d, now that igmain has been destroyed. First interface: Second interface: 7. Check the syntax of the ifgrp command: system> ifgrp create E7-4 Data ONTAP 7-Mode Administration: Networking

41 8. Use the two interfaces that you chose two steps earlier to create a single-mode interface group: system> ifgrp create single singletrunk1 <first_interface> <second_interface> 9. Use the ifconfig command to give this interface an IP address and netmask: system> ifconfig singletrunk1 <IP address> up netmask <netmask> 10. Verify the interface group: system> ifconfig a 11. Attempt to destroy the interface group while it is up: system> ifgrp destroy singletrunk1 What happens? 12. Ensure that you are connected through the console and take the interface down: system> ifconfig singletrunk1 down 13. Destroy the new interface: system> ifgrp destroy singletrunk1 14. Verify that you have destroyed the interface: system> ifconfig a E7-5 Data ONTAP 7-Mode Administration: Networking

42 TASK 4: USE THE CLI TO CREATE A MULTIMODE INTERFACE GROUP 1. At the command prompt, verify your current interfaces: system> ifconfig a 2. Choose two unused and disabled interfaces to add to this new interface group. First interface: Second interface: 3. Create a multimode interface group: system> ifgrp create multi multitrunk1 b ip <first_interface> <second_interface> 4. Verify that the new interface group exists: system> ifconfig multitrunk1 5. Verify your current interfaces: system> ifconfig a 6. Use the ifconfig command to give this interface an IP address and netmask: system> ifconfig multitrunk1 <IP_address> up netmask <Netmask> 7. Check the status of the new interface group: system> ifgrp status What is the load-balancing policy? How many links are active? What is the interface group type? 8. Ensure that you are connected through the console and take the interface down: system> ifconfig multitrunk1 down 9. Destroy the interface: system> ifgrp destroy multitrunk1 10. Verify that you have destroyed the interface: system> ifconfig a END OF EXERCISE E7-6 Data ONTAP 7-Mode Administration: Networking

43 MODULE 8: NFS EXERCISE: CONFIGURING NFS In this exercise, you configure the NFS service on a storage system. OBJECTIVES By the end of this exercise, you should be able to: License NFS Export a volume by using System Manager Export a volume by using the CLI Mount exports from an administration host TASK 1: USE SYSTEM MANAGER TO LICENSE AND ENABLE NFS 1. In System Manager, in the left pane, expand Configuration > System Tools > Licenses. The License list appears. NOTE: Licenses might already be configured on your system. 2. Click the Add button to display the Add License Packages dialog box. 3. If necessary, obtain the license code from your instructor. 4. In the New license key text box, enter the license code, and then click Add. 5. Ensure that the NFS license is listed in NetApp System Manager. In the Licenses node, you can see the name, type, key, and date of expiration for each license. 6. Verify if NFS is enabled system> nfs status If the output states, NFS is not running: system> nfs on Verify NFS is running: system> nfs status E8-1 Data ONTAP 7-Mode Administration: NFS

44 TASK 2: USE NETAPP SYSTEM MANAGER TO EXPORT A VOLUME 1. In the left pane, click Storage > Exports, and notice the exports that have been automatically created. 2. Highlight vol0. 3. Highlight and select All hosts, at the bottom of the page, and then click Edit. 4. Select All Hosts, select Edit, and then change access to Read Only. 5. Click Modify. TASK 3: USE THE CLI TO EXPORT A VOLUME In this task, you create a volume and export it. 1. Using the storage system IP address, open an SSH session to your storage system. 2. Log in as root. 3. Verify the contents of the /etc/exports file: system> rdfile /etc/exports E8-2 Data ONTAP 7-Mode Administration: NFS

45 4. Verify whether automatic exporting of new volume is enabled: system> options nfs.export.auto-update Is this option enabled? NOTE: When the option nfs.export.auto-update is enabled, new volumes are exported upon creation. 5. Create a volume: system> vol create NFSvol aggr1 100m 6. Verify that the new volume has been exported: system> rdfile /etc/exports 7. Load the current list of defined exports from the /etc/exports file: system> exportfs -a 8. List the current exports: system> exportfs Were other existing volumes exported when you licensed NFS? 9. Using the IP address, open a CLI session to your assigned UNIX server. 10. Log in as root. 11. Verify that the client can see the volume that you exported: # showmount e <storage_system_ip> After NFS is licensed, volumes are exported as soon as they are created, but qtrees must still be exported manually. NOTE: There is a chance you might have to restart the NFS service on the storage controller (nfs off, nfs on). 12. Create a qtree to use when verifying that qtrees are not automatically exported: system> qtree create /vol/nfsvol/nfs_tree1 13. Verify that the new qtree is visible from the client: # showmount e <storage_system_ip> Can you see the new qtree nfs_tree1 from the client? 14. Verify that the qtree has not been automatically exported: system> exportfs 15. Export the qtree: system> exportfs i o rw /vol/nfsvol/nfs_tree1 NOTE: When you use the exportfs -i -o command, the /etc/exports file is not changed, and your export is temporary. 16. Verify that nfs_tree1 has been exported: system> exportfs E8-3 Data ONTAP 7-Mode Administration: NFS

46 17. From the client system, verify that the export is now visible: # showmount e <system_name> 18. Use the -p switch with the exportfs command to create a persistent export: system> exportfs -p rw /vol/nfsvol/nfs_tree1 NOTE: You can also update the /etc/exports file by mounting the root volume and editing the file or by using NetApp System Manager to add the export. A fourth method of updating the /etc/exports file is to use the wrfile command to append the file: system> wrfile a /etc/exports "/vol/nfsvol/nfs_tree1 sec-sys,rw" 19. Verify the /etc/exports file: system> rdfile /etc/exports 20. Remove your new entry from system memory: system> exportfs u /vol/nfsvol/nfs_tree1 21. Verify that nfs_tree1 is no longer available: system> exportfs 22. Reload the exports file: system> exportfs a system> exportfs Was the nfs_tree1 qtree loaded into memory? TASK 4: MOUNT EXPORTS FROM AN ADMINISTRATION HOST In this task, you mount the exports that you created earlier in this exercise. 1. Establish a telnet session to the administration host and create a directory for your storage system: # mkdir /mnt/<system_name> NOTE: In this command, system_name is a variable. Do not create a directory with the name system_name. 2. Create a subdirectory called vol0 in the /system_name directory: # mkdir /mnt/<system_name>/vol0 3. Using the storage system name or IP address, mount the storage system root volume (vol0), and then view the contents: # mount o nolock <system IP_address>:/vol/vol0 /mnt/<system_name>/vol0 # cd /mnt/<system_name>/vol0 E8-4 Data ONTAP 7-Mode Administration: NFS

47 4. View the directory structure of your storage system s root volume: # ls al /mnt/<system_name>/vol0 How does this compare with the local client root? (Hint: # ls al /) 5. Try to create a file at the root of the storage system: # touch foo Were you able to create a file? 6. Create a mountpoint on the client: # mkdir /mnt/<system_name>/nfs_tree1 7. Execute the mount command: # mount o nolock <IP_address>:/vol/NFSvol/nfs_tree1 /mnt/<system_name>/nfs_tree1 8. Change to your mounted directory and make some files: # cd /mnt/<system_name>/nfs_tree1 # man csh > file1 # dd if=/dev/zero of=/mnt/<system_name>/nfs_tree1/file2 bs=8192 count= Check the disk usage on your storage system: system> df h /vol/nfsvol Can you verify that the files that you created earlier reside on the storage system? END OF EXERCISE E8-5 Data ONTAP 7-Mode Administration: NFS

48 MODULE 9: CIFS EXERCISE: CONFIGURING CIFS In this exercise, you configure CIFS in a Windows domain environment and verify CIFS setup on a storage system through the console, telnet, and OnCommand System Manager. OBJECTIVES By the end of this exercise, you should be able to: License CIFS service by using OnCommand System Manager Configure CIFS service by using OnCommand System Manager Create a Windows domain user View and create shares by using the CLI and by using OnCommand System Manager View and create shares by using Windows Computer Management Map shares to drive letters Modify user permissions Display CIFS sessions Configure the SMB 2.0 protocol Terminate CIFS sessions TASK 1: USE ONCOMMAND SYSTEM MANAGER TO LICENSE CIFS SERVICE When your storage system is installed at the factory, the licenses that you purchased are added. If your storage system was installed later or you purchased the license later, you must add the license. In this task you license CIFS service on the storage system. 1. In OnCommand System Manager, click Configuration > Protocols. Is CIFS listed? 2. Click Configuration > System Tools > Licenses. 3. Only perform steps 3-5 if necessary. Click Add. The Add License dialog box appears. 4. Enter the software license code that was provided by your instructor and click Add. 5. Verify that the CIFS license was added successfully. E9-1 Data ONTAP 7-Mode Administration: CIFS 2015 OnCommand, Inc. This material is intended only for training. Reproduction is not authorized.

49 TASK 2: USE ONCOMMAND SYSTEM MANAGER TO CONFIGURE CIFS SERVICE 1. In OnCommand System Manager, click Configuration > Protocols > CIFS and notice that CIFS has not been configured yet. 2. Click Setup to start the CIFS Setup Wizard. 3. Click Next. 4. In the Security Style text box, accept the default security style, Multiprotocol, and click Next. 5. On the Windows Authentication page, select Active Directory and click Next. 6. Enter the fully qualified domain name and domain administrator s credentials that were provided by your instructor, and click Next. 7. In the Password field and the Confirm Password field, enter the storage system root user password, and then click Next. 8. Verify the default name of the system and do not enter any WINS server addresses. NOTE: The name of your storage system should be the default name of the system. 9. Click Next. E9-2 Data ONTAP 7-Mode Administration: CIFS 2015 OnCommand, Inc. This material is intended only for training. Reproduction is not authorized.

50 10. Review the CIFS Set up Summary page and click Next. 11. Verify that the CIFS Setup Wizard was successful and click Finish. 12. In OnCommand System Manager, click the Configuration tab and review the information. 13. Click the Domain tab and review the information. TASK 3: CREATE A WINDOWS DOMAIN USER In this task, you install the Remote Server Administration Tools feature, log in to the Microsoft Active Directory Users and Computers tool, and create a domain user. 1. Open Server Manager on Windows Server In the upper right corner, select Tools and click Active Directory Users and Computers. E9-3 Data ONTAP 7-Mode Administration: CIFS 2015 OnCommand, Inc. This material is intended only for training. Reproduction is not authorized.

51 3. Expand the domain_name and select Users. 4. Click Action, select New, and then select User. 5. Complete the fields of the New Object User dialog box to create UserXX, where XX are your initials. NOTE: Do not create UserXX without replacing the XX with your initials. If you are not sure what number to use, ask your instructor. E9-4 Data ONTAP 7-Mode Administration: CIFS 2015 OnCommand, Inc. This material is intended only for training. Reproduction is not authorized.

52 6. Click Next, and then set a user password that meets the password complexity requirements: Passwords cannot contain the user s account name or parts of the user s full name that exceed two consecutive characters. Passwords must be at least six characters in length. Passwords must contain characters from three of the following four categories: 1. English uppercase characters (A through Z). 2. English lowercase characters (a through z). 3. Base 10 digits (0 through 9). 4. Non-alphabetic characters (for example,!, $, #, %). Select the Password never expires check box. Click Next. 7. Click Finish. TASK 4: USE THE CLI AND ONCOMMAND SYSTEM MANAGER TO VIEW AND CREATE SHARES In this task, you view shares, create NTFS qtrees, and share the qtrees. 1. Resize the NFSvol volume and add 100 MB to its size. 2. View the shares on the storage system: system> cifs shares 3. In OnCommand System Manager, click Storage > Qtrees. 4. Click Create. E9-5 Data ONTAP 7-Mode Administration: CIFS 2015 OnCommand, Inc. This material is intended only for training. Reproduction is not authorized.

53 5. In the Create Qtree dialog box, enter configuration information: a. In the Name text box, type cifs_tree1. b. In the Volume text box, type NASvol. c. Select the Enable oplocks check box. d. Select the NTFS security style. 6. Click Create. 7. Click Storage > Shares, and notice the default shares that have been created. 8. Highlight ETC$, click Edit, and explore the ETC$ share. 9. Click the Permissions tab and examine the current (default) permissions for this share. 10. Click Cancel to close the Edit ETC$ Setting dialog box. 11. On the Shares page, click Create. The Create Share and Export Wizard appears. 12. Click Browse. E9-6 Data ONTAP 7-Mode Administration: CIFS 2015 OnCommand, Inc. This material is intended only for training. Reproduction is not authorized.

54 13. Expand aggr1, expand NASvol, and select cifs_tree Click OK. 15. Click Create and notice that the new share is on the list. 16. Create a qtree in NFSvol named cifs_tree2: system> qtree create /vol/nfsvol/cifs_tree2 NOTE: A qtree that is created in NFSvol has the UNIX security style because it inherits the security style from its containing volume. 17. Verify the current security style: system> qtree status 18. Change the security style to NTFS: system> qtree security /vol/nfsvol/cifs_tree2 ntfs 19. View the qtree information. system> qtree status NOTE: Other qtrees from previous exercises are also displayed. E9-7 Data ONTAP 7-Mode Administration: CIFS 2015 OnCommand, Inc. This material is intended only for training. Reproduction is not authorized.

55 20. Access the storage system console and create a CIFS share: system> cifs shares add cifs_tree2 /vol/nfsvol/cifs_tree2 21. View the new share: system> cifs shares cifs_tree2 22. Add a comment to the share: system> cifs shares -change cifs_tree2 -comment 'Share created via CLI' 23. View the change to the share: system> cifs shares cifs_tree2 TASK 5: CREATE A NEW SHARE WITH COMPUTER MANAGEMENT In this task, you use the Microsoft Computer Management tool to view and create shares. 1. Use the CLI or OnCommand System Manager to create an NTFS qtree called cifs_tree3 in NASvol. 2. Open Server Manager, and select Computer Management from the Tools menu 3. Click Action, and then select Connect to another computer. 4. Use the Browse feature to locate and highlight the name of your storage system, or type the IP address of the storage system and click OK. 5. In the left pane, click System Tools > Shared folders > Shares, and notice the list of currently shared directories on the right. 6. Right-click the Shares folder and select New Share. The Create a Shared Folder Wizard appears. 7. Click Next. 8. Enter the folder to share, C:\vol\NASvol\cifs_tree3, and click Next. 9. Configure the shared folder: a. In the Share name text box, type cifs_tree3. b. In the Description text box, type Share for cifs_tree3. c. Click Next. E9-8 Data ONTAP 7-Mode Administration: CIFS 2015 OnCommand, Inc. This material is intended only for training. Reproduction is not authorized.

56 10. Select Customized permissions and click Custom. 11. Add UserXX from the previous exercise and give UserXX Full control permissions. 12. Click OK. 13. Click Finish. 14. On the Sharing was Successful page, click Finish. 15. Notice that the new shared directory, cifs_tree3, is displayed in the shared directories for the storage system. 16. Close the Computer Management dialog box. TASK 6: MAP SHARES TO DRIVE LETTERS 1. From the Windows desktop, click Start > Computer > Map Network Drive. 2. Enter the network drive information: a. In the Drive text box, type any unused letter. b. Enter this folder path: \\<storage_system_name or IP address>\cifs_tree1. 3. Click Finish to accept the changes and close the window. 4. Map the cifs_tree2 and cifs_tree3 shares to different drive letters. 5. Copy some files from your Windows machine to cifs_tree1 and cifs_tree3. You will use the files in a later module. E9-9 Data ONTAP 7-Mode Administration: CIFS 2015 OnCommand, Inc. This material is intended only for training. Reproduction is not authorized.

57 TASK 7: MODIFY USER PERMISSIONS In this task, you configure permissions on cifs_tree2 for the domain user that you created earlier. 1. Access the storage system console and give the user that you created earlier (UserXX) access to cifs_tree2: system> cifs access cifs_tree2 <userxx> rwx 2. Verify the result on the storage system console: system> cifs shares 3. Open Server Manager and then select Computer Management from the Tools menu to view the access change in Windows Computer Management. 4. Connect to your storage system. 5. Click System Tools > Shared folders > Shares. 6. Right-click cifs_tree2 and select Properties. 7. Click the Share permissions tab and note that the permissions are set to Full control. 8. Change the permissions on the storage system for the cifs_tree2 share to read-only: system> cifs access cifs_tree2 <userxx> read 9. Verify the settings for the share on the storage system: system> cifs shares 10. Use Windows Computer Management to review the permissions for userxx on cifs_tree2. E9-10 Data ONTAP 7-Mode Administration: CIFS 2015 OnCommand, Inc. This material is intended only for training. Reproduction is not authorized.

58 TASK 8: DISPLAY CIFS SESSIONS In this task, you display CIFS sessions from OnCommand System Manager, Computer Management, and the CLI. 1. In OnCommand System Manager, click Diagnostics > Session, and notice that you have at least one session. 2. Open Computer Management and connect to your storage system. 3. Click System Tools > Shared Folders > Sessions. 4. From the storage system, verify the open sessions: system> cifs sessions 5. Compare the output of the cifs sessions command with the output from OnCommand System Manager and Computer Management. TASK 9: TERMINATE CIFS SESSIONS In this task, you terminate a CIFS session by using Computer Management and then you stop and restart CIFS service from the CLI and from OnCommand System Manager. 1. Open Computer Management and connect to your storage system. 2. Click System Tools > Shared Folders > Sessions. 3. Right-click a session and select Disconnect All Sessions. Did it close? Why or why not? 4. Close Computer Management. 5. Verify the open sessions from the storage system: system> cifs sessions 6. Terminate all sessions: system> cifs terminate E9-11 Data ONTAP 7-Mode Administration: CIFS 2015 OnCommand, Inc. This material is intended only for training. Reproduction is not authorized.

59 7. Verify the results: system> cifs sessions 8. Restart the CIFS service from the storage system console: system> cifs restart 9. In System Manager, click Configuration > Protocols > CIFS. 10. Ensure that the Configuration tab is selected. 11. Click Stop to stop the CIFS service. 12. When a dialog box appears to confirm the operation, select OK to stop CIFS service and click Stop. 13. Click Diagnostics > Session. Are there any CIFS sessions? 14. Navigate back to Protocols > CIFS. 15. Ensure that the Configuration tab is selected. 16. Click Start to restart the CIFS service. 17. Click Diagnostics > Session. Are there any CIFS sessions? What do you need to do to reestablish the CIFS session? END OF EXERCISE E9-12 Data ONTAP 7-Mode Administration: CIFS 2015 OnCommand, Inc. This material is intended only for training. Reproduction is not authorized.

60 MODULE 10: NAS MANAGEMENT EXERCISE: MANAGING QUOTAS AND QTREES In this exercise, you create a qtree and define quotas for that qtree. You also work with the native fileblocking mechanism. OBJECTIVES By the end of this exercise, you should be able to: Create and manage quotas Generate a quota report Modify the /etc/quotas file and implement quota changes Create qtrees and quotas for the qtrees by using the CLI Create a native file-blocking policy TASK 1: CREATE AND MANAGE QUOTAS In this task, you use System Manager and the CLI to create and manage quotas. 1. In System Manager, click Storage > Qtrees. 2. Click Create. 3. In the Create Qtree dialog box, enter configuration information: a. In the Name text box, type nas_tree1. b. In the Volume text box, type NASvol. c. Select the Enable oplocks check box. d. Select the NTFS security style. 4. Click Create. 5. In System Manager, click Storage > Shares and create a CIFS share for nas_tree1. 6. From the storage system, verify the current values in the /etc/quotas file: system> rdfile /etc/quotas Example output: #Auto-generated by setup NOTE: For this task, you intentionally use tight restrictions. 7. In System Manager, click Storage > Quotas. There are currently no quotas. E10-1 Data ONTAP 7-Mode Administration: NAS Management

61 8. Click Create. The Add Quota Wizard appears: 9. Click Next. 10. For the volume, select /vol/nasvol/nas_tree1, and for the quota type, select Qtree. 11. Click Next. E10-2 Data ONTAP 7-Mode Administration: NAS Management

62 12. On the Quota Limits page, enter these values: Disk Space Hard Limit: 12 MB Disk Space Soft Limit: 8 MB Threshold: 8 MB Files Hard Limit: 2K Files Soft Limit: 1K 13. Click Next. 14. On the Quota Summary page, verify the quota and click Next. 15. Click Finish to complete the wizard. 16. Return to the storage system CLI and review quota status: system> quota status 17. From the storage system, verify the current values in the /etc/quotas file: system> rdfile /etc/quotas Example output: 18. Return to the Windows client. 19. Open Windows File Explorer. E10-3 Data ONTAP 7-Mode Administration: NAS Management

63 20. Select the Computer icon in the left pane and click Computer on the menu bar. 21. Click Map Network Drive. 22. In the Map Network Drive dialog box, enter these values: a. In the Drive text box, select any unused letter. b. Enter this folder path: \\IP_of_Storage_System\nas_tree1. c. Clear the Reconnect at login check box. Click the Finish button. 23. Click OK. 24. Add at least 8 MB of data to the nas_tree1 directory. NOTE: You can do this easily by copying files from the local C:\ drive to the mapped drive. 25. When you exceed the quota threshold, what do you see on the CLI? When you exceed the quota threshold, what do you see on the client? When you exceed the quota soft block value, what do you see on the CLI? When you exceed the quota soft-block value, what do you see on the client? E10-4 Data ONTAP 7-Mode Administration: NAS Management

64 26. How much more data do you need to add to the share to exceed the hard block quota? 27. Add enough data to exceed the hard block quota. What do you see on the CLI? When you exceed the quota hard-block value, what do you see on the client? TASK 2: CREATE A QUOTA REPORT 1. From the storage system CLI, enter this command: system> quota report 2. In System Manager, click Storage > Quotas. 3. Click the Quota Report tab and compare the details with the CLI output. 4. How much disk space is being used by all users in nas_tree1? 5. How many files were created on your storage system for nas_tree1? TASK 3: MODIFY THE /ETC/QUOTAS FILE AND IMPLEMENT QUOTA CHANGES 1. In System Manager, click the User Defined Quotas tab. 2. Select NASvol and click Edit Limits. 3. Click the Space Limit tab. 4. Change the hard space quota from 12 MB to 15 MB. E10-5 Data ONTAP 7-Mode Administration: NAS Management

65 5. Click Save and Close. 6. Do your changes take effect automatically? 7. Click the Quota Status on Volumes tab. Each volume is listed with its quota status. 8. From the storage system, verify the current values in the /etc/quotas file: system> rdfile /etc/quotas Example output: 9. Attempt to exceed the hard block quota again. 10. In System Manager, click Diagnostics > Logs > Syslog. NOTE: A syslog message appears for the soft limit you exceeded previously but you cannot exceed the hard block quota so no syslog message appears for this action. 11. Read the manual pages for the quota report command and give a brief description of the following arguments. (Use the man command.) -q -s -t -u -x 12. Continue to review the manual page for the quota command. What is the purpose of the logmsg subcommand? TASK 4: USE THE CLI TO CREATE QTREES AND QUOTAS FOR THE QTREES 1. Use the CLI to create two qtrees in the NASvol volume, naming the first qtree cobra and the second qtree firebird : system> qtree create /vol/nasvol/cobra system> qtree create /vol/nasvol/firebird E10-6 Data ONTAP 7-Mode Administration: NAS Management

66 2. View the qtrees that you just created. What is the security style? 3. Configure the newly created qtrees: a. Edit the correct file to give the cobra qtree a hard size limit of 50 MB with a threshold of 45 MB. If editing from Windows use WordPad. b. Give the firebird qtree a hard size limit of 20 MB with a threshold of 18 MB. c. Limit the files on firebird to 10 K. d. Use tree for the type on both quotas. Which file did you edit? Record the entries that you create. # TARGET TYPE DISK FILE THRESHOLD SDISK SFILE 4. How did you edit the file? 5. What does the entry look like that gives the /vol/nasvol flexible volume a default quota of 150 MB of disk space with a threshold of 145 MB for any user? # TARGET TYPE DISK FILE THRESHOLD SDISK SFILE 6. Enable quotas, then set the interval for the log to two hours on /vol/nasvol: system> quota on /vol/nasvol Which command lets you view the thresholds for all quotas? 7. Change the quotas for the firebird qtree to the same settings as the cobra qtree. When you change the size of a quota, what command do you enter to cause the changes to take effect? E10-7 Data ONTAP 7-Mode Administration: NAS Management

67 TASK 5: CREATE A NATIVE FILE-BLOCKING POLICY 1. Using the console prompt, verify that CIFS file policy service is enabled: system> options fpolicy 2. If the FPolicy feature of the Data ONTAP operating system is not enabled, enable it, and then verify that it is on: system> fpolicy 3. Create a new FPolicy file-screening policy: system> fpolicy create mp3blocker screen 4. Verify the policy: system> fpolicy show mp3blocker 5. Add the.mp3 extension to the FPolicy file-screening policy: system> fpolicy ext inc set mp3blocker mp3 6. Set the mp3blocker policy to required : system> fpolicy options mp3blocker required on 7. Set up a monitor for the FPolicy file-screening policy to restrict creation and renaming of files through the CIFS protocol: system> fpolicy monitor set mp3blocker p cifs create,rename A message appears to warn you about the complete blocking of files. 8. Answer Y to the warning message to prevent all users from creating or renaming.mp3 files because you don t have third-party applications. NOTE: If you want to configure the policy so that certain users can create.mp3 files and others cannot, you must set a third-party file-screening server. 9. Enable the FPolicy file-screening policy: system> fpolicy enable mp3blocker -f 10. From the console prompt, enter: system> fpolicy show mp3blocker 11. Try to copy Song.mp3 from the C:\course files classroom folder to a mapped drive that is associated with your storage system (NASvol). Were you able to copy the file? 12. Disable the policy: system> fpolicy disable mp3blocker 13. Return to the Window workstation. 14. Can you copy the Song.mp3 file now? END OF EXERCISE E10-8 Data ONTAP 7-Mode Administration: NAS Management

68 MODULE 11: SAN EXERCISE: MANAGING ISCSI LUNS In this exercise, you set up an iscsi LUN on a storage system and attach it as a drive on the Windows system. OBJECTIVES By the end of this exercise, you should be able to: License and start the iscsi service Configure iscsi for Windows Server 2012 Create a LUN using System Manager Create a LUN from the CLI Access LUNs from Windows Server 2012 Nondisruptively move a volume containing a LUN (optional) TASK 1: LICENSE AND START THE ISCSI SERVICE 1. From your assigned storage system, verify that iscsi service is licensed: system> iscsi status 2. If necessary, add the license: system> license add OnCommand System Manger licenses iscsi and starts the iscsi service when you add the license. However, when you license iscsi from the CLI, the service is not automatically started. You must start the service the first time, and after that, the service starts automatically each time the system reboots. The system will prompt you to enable other iscsi-related options; follow the prompts. 3. Enable the iscsi option: system> options licensed_feature.iscsi.enable on 4. If necessary, start iscsi service: system> iscsi start E11-1 Data ONTAP 7-Mode Administration: SAN 2015 OnCommand, Inc. This material is intended only for training. Reproduction is not authorized.

69 5. In OnCommand System Manager, click Protocols > iscsi to verify that the iscsi service has been started. You may have to refresh OnCommand System Manager. E11-2 Data ONTAP 7-Mode Administration: SAN 2015 OnCommand, Inc. This material is intended only for training. Reproduction is not authorized.

70 TASK 2: CONFIGURE ISCSI ON WINDOWS SERVER 2012 In this task, you configure Windows Server 2012 to be an iscsi initiator. 1. Start Microsoft Windows and open Server Manager (if it doesn t open automatically) by clicking the Server Manager icon next to Start on the Windows 2012 desktop. Server Manager appears. E11-3 Data ONTAP 7-Mode Administration: SAN 2015 OnCommand, Inc. This material is intended only for training. Reproduction is not authorized.

71 2. Click Tools>iSCSI Initiator in Server Manager. 3. If an error message appears, indicating that the Microsoft iscsi service is not running, click Yes to start the service. 4. The iscsi Initiator Properties dialog box appears. E11-4 Data ONTAP 7-Mode Administration: SAN 2015 OnCommand, Inc. This material is intended only for training. Reproduction is not authorized.

72 5. Click the Configuration tab. 6. In the Initiator Name field, note the Windows Server 2012 node name, and record it here: Next you will configure the iscsi service to see the e0a target portal group for your assigned storage system. 7. Click the Discovery tab. E11-5 Data ONTAP 7-Mode Administration: SAN 2015 OnCommand, Inc. This material is intended only for training. Reproduction is not authorized.

73 8. Click the Discover Portal button. The Discover Target Portal dialog box appears. 9. Enter the IP address of e0a on your assigned storage system, leave the port as 3260, and click the Advanced button. The Advanced Settings dialog box appears. 10. From the Local adapter drop-down list, select Microsoft iscsi Initiator. 11. From the Initiator IP drop-down list, select the interface on your Windows Server 2012 machine that is in the same IP subnet as your OnCommand controller and click OK. 12. Click OK to add the target port. E11-6 Data ONTAP 7-Mode Administration: SAN 2015 OnCommand, Inc. This material is intended only for training. Reproduction is not authorized.

74 13. Click the Targets tab and notice that it shows one discovered target. What is the current status of this target? 14. Highlight the target and click the Properties button. How many current sessions are there? 15. Click the Portal Groups tab. How many portal groups has Windows identified? 16. Click OK to close the Properties dialog box. Next you bind to the storage system and create a session. 17. On the Targets tab, ensure that the storage system s iscsi Qualified Name (IQN) is highlighted, and click the Connect button. 18. In the Connect to Target dialog box, enter settings: Ensure that Add this connection to the list of Favorite Targets is selected. E11-7 Data ONTAP 7-Mode Administration: SAN 2015 OnCommand, Inc. This material is intended only for training. Reproduction is not authorized.

75 19. Click OK again to return to the iscsi Initiator Properties dialog box. The status of the target is now Connected. TASK 3: USE ONCOMMAND SYSTEM MANAGER TO CREATE A LUN In this task, you use OnCommand System Manager to create a volume and a LUN, and you attach the LUN to an iscsi initiator group (igroup). 1. In the Windows 2012 iscsi Initiator Properties screen, click the Configuration tab and copy the initiator name for this Windows 2012 system. 2. In OnCommand System Manager, click Storage > LUNs. 3. Click the Create button The Create LUN Wizard appears. 4. Click Next. E11-8 Data ONTAP 7-Mode Administration: SAN 2015 OnCommand, Inc. This material is intended only for training. Reproduction is not authorized.

76 5. On the General Properties page, enter these values: a. In the Name text box, enter lun1. b. In the Description text box, enter LUN for iscsi exercise. c. In the Size area, enter 100 MB. d. From the Type drop-down list, select Windows Click Next. 7. On the LUN Container page, select Create a new flexible volume in, keep the defaults for aggr and volume name, and click Next. 8. On the Initiator Mapping page, click the Add Initiator Group button. The Create Initiator Group dialog box appears. 9. In the Name field, enter the name for the igroup, w2k12_igroup 10. Click the Initiators tab and click Add. 11. In the Name field, copy and paste the initiator name, and click Ok. 12. Click the Map LUN box 13. Select the newly created initiator group and click Next. 14. Review the LUN Summary page and click Next to create the LUN. 15. Click Finish to complete the wizard. 16. On the LUN Management tab, examine the features of lun1. E11-9 Data ONTAP 7-Mode Administration: SAN 2015 OnCommand, Inc. This material is intended only for training. Reproduction is not authorized.

77 TASK 4: USE THE CLI TO CREATE A LUN In this task, you create another LUN and map it to an iscsi igroup by using the CLI command lun setup. 1. From the storage system, view the current LUNs: system> lun show -m 2. Create a volume to contain the new LUN: system> vol create lun2 aggr1 100m system> vol options lun2 nosnap on system> snap reserve lun At the prompt, enter the command that starts the LUN wizard: system> lun setup 4. When the LUN wizard asks if you want to create a LUN, enter Y. 5. For the LUN multiprotocol type, enter windows_2008 because you will use this LUN in a Windows environment. 6. Enter this LUN path to place the LUN on the lun2 volume that you created earlier: /vol/lun2/lun2 NOTE: The new LUN is lun2, and it is inside a volume that is also called lun2. 7. Enter Y to turn on space reservation for the LUN. 8. Enter 50m to create a very small LUN (50 MB). NOTE: When you work on a simulator, space is an issue. 9. Type any description of the LUN that you want, and press Enter. 10. The name of the igroup that you created in the previous task appears in [ ] brackets, so press Enter. NOTE: You can type? to list the current igroups. 11. Press Enter without specifying a LUN ID for the new LUN. NOTE: If you do not specify a LUN ID, the Data ONTAP operating system automatically assigns a valid ID. 12. Type Y to accept the configurations that you have entered. 13. Type N to decline to create another LUN. The LUN has now been created. 14. Verify that the LUN has been created: system> lun show m E11-10 Data ONTAP 7-Mode Administration: SAN 2015 OnCommand, Inc. This material is intended only for training. Reproduction is not authorized.

78 TASK 5: ACCESS LUNS FROM WINDOWS SERVER On your assigned remote Windows Server 2012 machine, click the Server Manager icon. 2. Click File and Storage Services from the tree pane. 3. Select Disks from the tree. The two new LUNs (one that was created with OnCommand System Manager in Task 3, and one that was created with the CLI in Task 4) are not visible. 4. Click iscsi from the tree pane, and in the iscsi Virtual Disks area, click the link To install iscsi Target Server, start the Add Roles and Features Wizard. 5. Click Next on the following two screens then Click Install. The iscsi Target Server installation starts. Click Close when the installation has finished. 6. In Server Manager, click Tools>Computer Management. 7. Click Disk Management in the left pane, and then select lun1, right-click Disk #, and select Online to bring lun1 online. (You might need to re-scan disks to see the LUN) 8. Select lun2, right-click Disk #, and select Online to bring lun2 online. 9. Right-click Disk # on lun1 and select Initialize Disk. The Initialize Disk dialog box appears, with information for both disks (one for lun1 and the other for lun2). 10. Verify that the master boot record (MBR) partition style is selected for both LUNs (because you created both LUNs with this partition style), and then click OK. E11-11 Data ONTAP 7-Mode Administration: SAN 2015 OnCommand, Inc. This material is intended only for training. Reproduction is not authorized.

79 11. Right-click the new unallocated disk for lun1 and select New Simple Volume from the menu. The New Simple Volume Wizard appears. NOTE: In this task, you provision the LUN with the New Simple Volume Wizard, but you can also use the Provisioning Storage Wizard from the Share and Storage Management tool to provision the LUN. 12. Click Next. 13. On the Specify Volume Size page, choose the maximum possible LUN size and click Next. 14. Assign an available Drive Letter, such as E, and click Next. 15. Select Format the LUN with the following settings, from the File system drop-down list, select NTFS, and then click Next. E11-12 Data ONTAP 7-Mode Administration: SAN 2015 OnCommand, Inc. This material is intended only for training. Reproduction is not authorized.

80 16. On the Completing the New Simple Volume Wizard page, review the values and click Finish. After a moment, the LUN becomes available. 17. Navigate to the drive letter of the LUN and write a test file to the LUN to verify that it is working correctly. 18. Repeat steps 9 to 17 for lun2. E11-13 Data ONTAP 7-Mode Administration: SAN 2015 OnCommand, Inc. This material is intended only for training. Reproduction is not authorized.

81 TASK 6: NONDISTRUPTLY MOVE A VOLUME THAT CONTAINS A LUN In this task, you move a volume containing LUN2 to a new aggregate and then move it back. 1. Remove the LUN2 export from the /etc/exports file and unload its export from memory: system> exportfs -z /vol/lun2 2. On your Windows server, open the mapped drive for LUN2, and begin a copy of the course files folder from the desktop. After you start the operation, do not disrupt access to the LUN while the LUN s volume is being moved to a new aggregate. 3. Move LUN2 s volume, originally on aggr1, to aggr2: system> vol move start lun2 aggr2 NOTE: The nondisruptive volume move requires similar aggregates on both source and destination (32-bit to 32-bit or 64-bit to 64-bit only). 4. Check the status of the move operation: system> vol move status lun2 5. Keep using the LUN from the client and continue to check the status on the storage system until the move is complete. 6. When the move is complete, verify that you can continue to access LUN2 on your Windows server. 7. Move the volume that contains LUN1 back to aggr1 but this time do a manual move: system> vol move start lun2 aggr1 m 8. Open the mapped drive for LUN2 on your Windows server and begin a copy of several files. 9. Perform the move: system> vol move cutover /vol/lun2 10. When the move is complete, verify that you can continue to access LUN2 on your Windows server. END OF EXERCISE E11-14 Data ONTAP 7-Mode Administration: SAN 2015 OnCommand, Inc. This material is intended only for training. Reproduction is not authorized.

82 MODULE 12: SNAPSHOT COPIES EXERCISE: MANAGING SNAPSHOT COPIES In this exercise, you use System Manager and the CLI to create and manage Snapshot copies, and you use the Snapshot directory and SnapRestore data recovery software to restore data. OBJECTIVES By the end of this exercise, you should be able to: Create a Snapshot copy by using System Manager Restore a Windows file from a Snapshot copy Restore a Linux file from a Snapshot copy Manage Snapshot copies by using System Manager Restore a file by using the Windows Previous Version tool License and configure SnapRestore technology Restore a volume by using SnapRestore technology Restore a file by using SnapRestore technology TASK 1: USE SYSTEM MANAGER TO CREATE A SNAPSHOT COPY 1. In System Manager, click Storage > Volumes. 2. Select the volume for which you want to create a Snapshot copy for this exercise, select the NFSvol volume. 3. Click Snapshot Copies > Create. The Create Snapshot dialog box appears. 4. Enter snapnfs as the name of the new Snapshot copy and click Create. 5. In the lower pane, click the Snapshot Copies tab. The new Snapshot copy appears in the list of Snapshot copies. E12-1 Data ONTAP 7-Mode Administration: Snapshot Copies

83 TASK 2: RESTORE A WINDOWS FILE FROM A SNAPSHOT COPY In this task, you delete a Windows file from the storage system /etc directory and restore it from a Snapshot copy. 1. Before you make a Snapshot copy, check to see if the create_ucode and convert_ucode options are set to on in the vol0 volume: system> vol options vol0 2. If they are not on, turn them on so that you can you will not be able to navigate to the Snapshot directory without receiving a permission denied or access not allowed error message: system> vol options vol0 create_ucode on system> vol options vol0 convert_ucode on 3. Ensure that vol0 has at least one Snapshot copy. system> snap create vol0 snapa 4. At the storage system console prompt, enable the option to make Snapshot copies visible: system> options cifs.show_snapshot If the option is not on, enable the visibility. system> options cifs.show_snapshot on This step ensures that the ~snapshot directory will be displayed. 5. On your Windows 2012 server, open File Explorer. E12-2 Data ONTAP 7-Mode Administration: Snapshot Copies

84 6. Select the Computer icon in the left column. From the top menu, click Computer>Map network drive 7. In the Folder box type \\<storage system IP>\c$ Make sure that both check boxes are selected ( Reconnect at sign-in and Connect using different credentials ). 8. Click Finish. 9. In the Windows Security screen, type the user name learn\administrator and its password, and then click OK. 10. Navigate to the /etc directory. E12-3 Data ONTAP 7-Mode Administration: Snapshot Copies

85 11. Locate and delete the exports.bak file. 12. If you do not see the ~snapshot directory because the storage system is not configured to display hidden files and folders, take these steps: a. Click View. b. Click the Hidden items check box. c. Select the Show hidden files and folders option. 13. If you still do not see the ~snapshot directory, disconnect the mapped drive and map it again. The Snapshot directory appears at the level that the drive is mapped to. 14. Navigate to the ~snapshot/snapa/etc/ directory and locate the exports.bak file. 15. Copy the file back to its original location at /etc/exports.bak. TASK 3: R ESTORE A LINUX FILE FROM A SNAPSHOT COPY In this task, you delete a Linux file from the storage system /vol/nfsvol/nfs_tree1/ directory and restore it from a Snapshot copy. 1. From the Linux CLI, navigate to /mnt/<storage_name>/nfs_tree1 and delete file1 (which you created in a previous exercise): # cd /mnt/<storage_name>/nfs_tree1 # rm file1 # y 2. Mount the volume NFSvol and navigate to the.snapshot directory : # mkdir /mnt/<storage_name>nfsvol # mount <storage_ip>:/vol/nfsvol /mnt/<storage_name>/nfsvol cd /mnt/storage_name/nfsvol/.snapshot/snapnfs 3. Copy the file from the Snapshot directory to the original directory: # cp file1 /mnt/<storage_name>/nfs_tree1 4. Change directory to the original location of the file: # cd /mnt/<storage_name>/nfs_tree1 5. Verify that the file has been restored from the Snapshot copy: # ls l file1 E12-4 Data ONTAP 7-Mode Administration: Snapshot Copies

86 TASK 4: USE SYSTEM MANAGER TO MANAGE SNAPSHOT COPIES In this task, you manage Snapshot copies and Snapshot backup schedules. 1. In System Manager, click Storage > Volumes. 2. Select the NASvol volume. 3. Click Snapshot Copies > Configure. The Configure Volume Snapshots dialog box appears. 4. Configure hourly Snapshot copies for the NASvol volume to occur at 10 a.m., 12 p.m., 2 p.m., and 5 p.m.: 5. Click OK. 6. Do hourly Snapshot copies occur every hour? 7. How can you view the Snapshot copy schedule for the root volume? 8. Can you change the percentage for the Snapshot reserve? E12-5 Data ONTAP 7-Mode Administration: Snapshot Copies

87 9. Select a volume and click the Snapshot Copies tab to examine the amount of space that is used by the Snapshot copy. Record the totals for snapa on NFSvol: snapa Total: snapa Used: TASK 5: RESTORE A FILE BY USING THE WINDOWS PREVIOUS VERSION TOOL In this task, you create a file that is called test1.txt in vol0 and you create a Snapshot copy of that file. You then modify the test1 file and restore the original version from the Snapshot copy by using the Windows Previous Version tool. 1. Create a file named test1.txt in vol0 that contains the text This is line 1. system> wrfile /vol/vol.0/test1.txt This is line 1 2. Enter Control-C to break out the file. The following output is displayed: read: error reading standard input: Interrupted system call 3. View the Snapshot copies on vol0: system> snap list vol0 4. Create a Snapshot copy of vol0: system> snap create vol0 snap1 5. View the contents of test1.txt in vol0: system> rdfile /vol/vol0/test1.txt 6. Overwrite the contents of test1.txt on vol0: system> wrfile -a /vol/vol0/test1.txt After snap1 7. View the contents of test1.txt on vol0: system> rdfile /vol/vol0/test1.txt 8. Connect to the c$ share again. 9. View the contents of test Select the test1.txt file, right-click and select Properties. 11. Click the Previous Versions tab. How many versions do you see? E12-6 Data ONTAP 7-Mode Administration: Snapshot Copies

88 12. Select the version and then click to view the file. What do you see? TASK 6: LICENSE AND CONFIGURE SNAPRESTORE TECHNOLOGY In this task, you configure your assigned storage system for SnapRestore data recovery software. 1. Check the status of your existing NFSvol volume. system> vol status NFSvol 2. Create a file named mystuff1 in your cifs_tree2 share. system> wrfile /vol/nfsvol/cifs_tree2/mystuff1 3. Type some data for the file: This is new data for the SnapRestore exercise. 4. Press Ctrl-C. The following output appears: read: error reading standard input: Interrupted system call 5. Create a Snapshot copy named mystuffsnap1 that will include your new file: system> snap create NFSvol mystuffsnap1 6. Create a second file in the same volume: system> wrfile /vol/nfsvol/cifs_tree2/mystuff2 7. Type some data for the file: This is a second new file for the SnapRestore exercise. 8. Press Ctrl-C. The following output appears: read: error reading standard input: Interrupted system call 9. Create a Snapshot copy named mystuffsnap2 that includes the new file: system> snap create NFSvol mystuffsnap2 10. Create a third file in the same volume. system> wrfile /vol/nfsvol/cifs_tree2/mystuff3 11. Type some data for the file: This is third new file for the SnapRestore exercise. This file is not very big. E12-7 Data ONTAP 7-Mode Administration: Snapshot Copies

89 12. Press Ctrl-C. The following output appears: read: error reading standard input: Interrupted system call 13. Create a third Snapshot copy named mystuffsnap3 that includes the new file: system> snap create NFSvol mystuffsnap3 14. Verify that all of the Snapshot copies exist: system> snap list NFSvol TASK 7: REVERT A VOLUME USE SNAPRESTORE TECHNOLOGY TO RESTORE A VOLUME In this task, you restore NFSvol by using SnapRestore technology. 1. Use SnapRestore technology to restore the volume: system> snap restore t vol /vol/nfsvol The Data ONTAP operating system displays a warning message and prompts you to confirm your decision to restore the volume. 2. Type y to confirm that you want to restore the volume. The Data ONTAP operating system lists the Snapshot copies that are available for the volume NFSvol and prompts you to indicate which Snapshot copy you want to use for the reversion. 3. Enter mystuffsnap2 and type y to confirm that you want to proceed. After the reversion is complete, which files are still present in NFSvol? 4. List the Snapshot copies for NFSvol. Compare this list to the list of Snapshot copies before the volume reversion. Do the lists differ? Why or why not? E12-8 Data ONTAP 7-Mode Administration: Snapshot Copies

90 TASK 8: USE SNAPRESTORE TECHNOLOGY RESTORE A FILE In this task, you use SnapRestore technology to restore the mystuff file. 1. Overwrite the content of mystuff1 on /vol/nfsvol/cifs_tree2: system> wrfile /vol/nfsvol/cifs_tree2/mystuff1 2. Type some data for the file: Now I m overwriting the contents of mystuff. 3. Press Ctrl-C. The following output appears: read: error reading standard input: Interrupted system call 4. Verify your changes to the file. system> rdfile /vol/nfsvol/cifs_tree2/mystuff1 5. Revert the mystuff1 file from the Snapshot copy mystuffsnap1. system> snap restore /vol/nfsvol/cifs_tree2/mystuff1 How did the restore command differ this time from when you restored a volume? 6. What is the timestamp of the restored file? 7. Verify the content in the restored file. system> rdfile /vol/nfsvol/cifs_tree2/mystuff1 END OF EXERCISE E12-9 Data ONTAP 7-Mode Administration: Snapshot Copies

91 MODULE 13: SPACE MANAGEMENT EXERCISE: MANAGING SPACE CONSUMPTION AND SPACE GUARANTEES In this exercise, you analyze factors that affect volume space consumption and experiment with space guarantees and file reservations to guarantee writes to a file. You also configure deduplication services for a volume. OBJECTIVES By the end of this exercise, you should be able to: Explore volume space consumption Explore file space consumption (Optional) Configure deduplication for a volume TASK 1: EXPLORE VOLUME SPACE CONSUMPTION In this task, you create a fully provisioned volume and a thin-provisioned volume and compare the results of writing to the volumes to determine when space from the containing aggregate and volume is used. 1. From NetApp System Manager or the CLI, create an aggregate called aggr3 that contains five disks (use defaults RAID_DP, 64-bit). 2. Determine how much space is available in aggr3, note it, then answer the question that follows: system> aggr show_space aggr3 -m Space available: What is the Snapshot reserve in aggr3? Size: 3. Create a fully provisioned 30-MB volume in aggr3 that is named FULLvol: a. In NetApp System Manager, start the Create Volume wizard. b. Ensure that Thin Provisioning is unchecked. c. Verify that the volume is properly exported to your Linux client. Make sure that you have root access. E13-1 Data ONTAP 7-Mode Administration: Space Management

92 4. Analyze the results, and answer the questions that follow: What is the available space in aggr3? MB: Percentage: What is the Snapshot reserve in aggr3? MB: Percentage: What is the available space in FULLvol? MB: Percentage: What is the Snapshot reserve in FULLvol? MB: Percentage: 5. Create a new thin-provisioned 30-MB volume in aggr3 that is named THINvol: a. In NetApp System Manager, start the Create Volume wizard. b. Select the Thin Provisioning checkbox. c. Verify that the volume is properly exported to your Linux client. Make sure you have root access. 6. Analyze the results, and answer the questions that follow: What is the available space in aggr3? MB: Percentage: What is the Snapshot reserve in aggr3? MB: Percentage: What is the available space in THINvol? MB: Percentage: What is the Snapshot reserve in THINvol? MB: Percentage: 7. Open a CLI session to your assigned UNIX client, using the IP address or name. 8. Log in as root. E13-2 Data ONTAP 7-Mode Administration: Space Management

93 9. Verify that the client sees the exported volumes: # showmount e storage_system_ip NOTE: New volumes are automatically exported because of the nfs.export.auto-update option. 10. Mount FULLvol and THINvol: # mkdir /mnt/<system_name>/fullvol # mount o nolock IP_address:/vol/FULLvol /mnt/<system_name>/fullvol # mkdir /mnt/<system_name>/thinvol # mount IP_address:/vol/THINvol /mnt/<system_name>/thinvol 11. Write 100% to FULLvol: # cd /mnt/<system_name>/fullvol # dd if=/dev/zero of=foo bs=1k conv=notrunc 12. Analyze the results, and answer the questions that follow: What is the available space in aggr3? MB: Percentage: What is the Snapshot reserve in aggr3? MB: Percentage: What is the available space in FULLvol? MB: Percentage: What is the Snapshot reserve in FULLvol? MB: Percentage: 13. Write 100% to THINvol: # cd /mnt/<system_name>/thinvol # dd if=/dev/zero of=foo bs=1k conv=notrunc E13-3 Data ONTAP 7-Mode Administration: Space Management

94 14. Analyze the results, and answer the questions that follow: What is the available space in aggr3? MB: Percentage: What is the Snapshot reserve in aggr3? MB: Percentage: What is the available space in THINvol? MB: Percentage: What is the Snapshot reserve in THINvol? MB: Percentage: TASK 2: EXPLORE FILE SPACE CONSUMPTION In this task, you create a volume with space that is reserved for files and create fully provisioned and thinprovisioned files within it. You then compare the space consumption within the containing aggregate and volume. 1. Using the CLI, create a 30-MB volume in aggr3 that reserves space for files and is called FILEvol. System> vol create FILEvol -s file aggr3 30m 2. Analyze the results, and answer the questions that follow: What is the available space in aggr3? MB: Percentage: What is the Snapshot reserve in aggr3? MB: Percentage: What is the available space in FILEvol? MB: Percentage: What is the Snapshot reserve in FILEvol? MB: Percentage: E13-4 Data ONTAP 7-Mode Administration: Space Management

95 3. Mount FILEvol: # mkdir /mnt/<system_name>/filevol # mount o nolock IP_address:/vol/FILEvol /mnt/<system_name>/filevol 4. Create a fully provisioned 10-MB file in FILEvol that is called FULLfile: # cd /mnt/<system_name>/filevol # dd if=/dev/zero of=fullfile bs=1000 count= Analyze the results, and answer the questions that follow: What is the available space in aggr3? MB: Percentage: What is the Snapshot reserve in aggr3? MB: Percentage: What is the available space in FILEvol? MB: Percentage: What is the Snapshot reserve in FILEvol? MB: Percentage: 6. Create a sparse 10-MB file called SPARSEfile in FILEvol: # dd if=/dev/zero of=sparsefile bs=1 count=0 seek= Analyze the results, and answer the questions that follow: What is the available space in aggr3? MB: Percentage: What is the Snapshot reserve in aggr3? MB: Percentage: What is the available space in FILEvol? MB: Percentage: What is the Snapshot reserve in FILEvol? MB: Percentage: E13-5 Data ONTAP 7-Mode Administration: Space Management

96 TASK 3: (OPTIONAL) CONFIGURE DEDUPLICATION FOR A VOLUME In this task, you configure deduplication on NASvol. To complete this task, you must have created the NASvol volume in Exercise 4 and copied data to NASvol in Exercise 9 Task Turn on the deduplication service on NASvol: system> sis on /vol/nasvol 2. Check the status of the deduplication service on NASvol: system> sis status /vol/nasvol Notice the default deduplication schedule. 3. Configure the deduplication service on NASvol to run on the flexible volume when the percentage of fingerprints in the change log reaches the default threshold (20%): system> sis config s auto /vol/nasvol This configures deduplication on NASvol volume for future data, but not for existing data. 4. Start the deduplication process for existing data: system> sis start -s /vol/nasvol System> y In this exercise environment, you might not have a lot of duplicate data on NASvol. You copied several duplicate files in Exercise 9 (the CIFS exercise). 5. Wait for a minute, then check the space savings: system> df -s /vol/nasvol END OF EXERCISE E13-6 Data ONTAP 7-Mode Administration: Space Management

97 MODULE 14: HIGH AVAILABILITY (OPTIONAL EXERCISE) (This exercise must be performed on real hardware, not a simulator) EXERCISE: MANAGING CONTROLLER FAILURE AND GIVEBACK In this exercise, you enable a high-availability (HA) configuration and observe how it works. NOTE: This exercise is not currently compatible with the Data ONTAP 8.x 7-Mode simulator. OBJECTIVES By the end of this exercise, you should be able to: Enable controller failover Perform a controller failover Perform a controller giveback TASK 1: ENABLE CONTROLLER FAILOVER In this task, you identify your partner and work together to fail over one of the storage systems. If you have difficulty identifying your partner, contact your instructor. Answers are in Appendix A of this guide. 1. Look at the hardware on your system, and answer the questions that follow: Do you see any indication that your storage system is cabled for high availability? Which command provides information about the hardware that is installed on your storage system? 2. Identify the system that will be system and the system that will be system2. system system2 3. Enable high availability: Starting with Data ONTAP 8.2 operating in 7-Mode, a license for high availability is no longer needed. You need to enable high availability with the options cf.mode ha: system> cf status system> options cf.mode ha 4. Enable high availability on system2: system2> cf status system2> options cf.mode ha 5. Reboot the system: system> reboot 6. Reboot system2: system2> reboot E14-1 Data ONTAP 7-Mode Administration: High Availability (Optional Exercise)

98 7. Enable high availability on system2, and answer the question that follows: system2> cf enable How does this affect system? NOTE: You could run the controller-failover enable command from either system within the HA pair. 8. Check the status on system: system> cf status 9. Check the status on system2: system2> cf status 10. In both Windows environments, open NetApp System Manager and select the System Manager node in the left pane. 11. Click Refresh, and answer the questions that follow: What happens? Why? 12. Add your storage system again, and answer the question that follows: What happens? 13. Use System Manager to navigate to your storage system interface configuration. 14. Select the e0b interface. This interface should have been cabled to the network properly before class. 15. Right-click and select Edit. E14-2 Data ONTAP 7-Mode Administration: High Availability (Optional Exercise)

99 16. Within the Edit Network Interface dialog box, enter the configuration information: a. In the HA failover mode area, select Standby. b. From the Partner Interface drop-down list, select e0a. 17. Click Save and Close to accept the changes. 18. Verify the network configuration. 19. At the console, verify that e0b is up: system> or system2> ifconfig e0b up E14-3 Data ONTAP 7-Mode Administration: High Availability (Optional Exercise)

100 TASK 2: PERFORM A CONTROLLER FAILOVER In this task, you fail over the first storage system (system) to the second system (system2). 1. On the first system (system), locate the files that you created in a previous exercise. 2. From your Windows host, view the mapped drive for the share cifs_tree1 and then view the drive that is associated with the iscsi LUN on your storage system. Later, you verify that you can still access these files during a takeover. 3. In NetApp System Manager, in the left pane, click the HA Configuration node: 4. Click the Takeover button for system2 to have it take over for system. The Takeover Operation page appears. E14-4 Data ONTAP 7-Mode Administration: High Availability (Optional Exercise)

101 5. Select Normal Takeover and click Takeover. 6. Click Close to complete the takeover operation. 7. Click Next again and close the wizard when the takeover is complete. 8. Check the console of system2, and answer the question that follows: How long did it take for system2 to complete the takeover? 9. Observe the results on the clients, and answer the question that follows: What happened to the Windows client connection? 10. Check the mountpoint on the UNIX client, and answer the questions that follow: What happened to the UNIX connection? What caused the difference between the NFS and CIFS connections during takeover? 11. On system2, notice the new prompt: system2(takeover)> 12. On system, notice the new prompt: system> Waiting for giveback 13. Run the following commands: system2(takeover)> sysconfig r system2(takeover)> sysconfig v system2(takeover)> sysstat Now run the same commands from within the system that has been taken over, and answer the question that follows: system2(takeover)> partner system2/system> sysconfig r system2/system> sysconfig v system2/system> sysstat 1 Was there a difference between the two storage system outputs? E14-5 Data ONTAP 7-Mode Administration: High Availability (Optional Exercise)

102 15. From your client, access system s cifs_tree share, and answer the questions that follow: Can you still access the data? Can you still access the LUN? TASK 3: PERFORM A CONTROLLER GIVEBACK In this task, you use the command-line interface (CLI) or a single NetApp System Manager session to give back the controller from system2 to system. 1. Restore the failover storage system to service by rebooting system. 2. On system, when you are prompted with the message waiting for giveback, either issue the giveback -f command on the system2 CLI or use NetApp System Manager. a. CLI method: system2> giveback -f b. Answer these questions: Do you need the f option? Why or why not? c. NetApp System Manager method: In NetApp System Manager, click the Giveback button: E14-6 Data ONTAP 7-Mode Administration: High Availability (Optional Exercise)

103 3. Check the HA status: system> cf statussystem2> cf status You can also analyze the status of your HA pair with NetApp System Manager. END OF EXERCISE E14-7 Data ONTAP 7-Mode Administration: High Availability (Optional Exercise)

104 MODULE 15: VIRTUALIZATION SOLUTIONS EXERCISE: WORKING WITH THE MULTISTORE FEATURE In this exercise, you practice configuring the MultiStore feature of the Data ONTAP operating system. OBJECTIVES By the end of this exercise, you should be able to: Create two MultiStore systems with separate IP aliases Create a CIFS share on a MultiStore system TASK 1: CREATE TWO MULTISTORE SYSTEMS WITH SEPARATE IP ALIASES In this task, you create two MultiStore units with separate IP aliases and associate them to the same physical network. 1. Create a volume for each MultiStore storage system: system> vol create vfiler1 aggr1 500m system> vol create vfiler2 aggr1 500m system> vol status 2. Enable the MultiStore software licensed feature from the CLI, and record the information that follows: system> options licensed_feature.multistore.enable on Current limit: Current usage: Platform hard limit: 3. Use the vfiler create command to create a MultiStore storage system on your host storage system: system> vfiler create vfiler1 i xxx.xxx.xxx.xxx /vol/vfiler1 NOTE: When you run this command, your system automatically starts the setup for the MultiStore storage system. The system continues with CIFS setup. Consult the instructor for the IP addresses to assign to your vfiler unit. 4. In System Manager, click vfiler units to create a MultiStore storage system. 5. Click Create. The Create vfiler unit Wizard appears. 6. Click Next. 7. In the vfiler Unit Details page, enter the following: a. Name: vfiler2 b. Select existing volume/qtree c. Volume/Qtree: /vol/vfiler2 8. Click Next. E15-1 Data ONTAP 7-Mode Administration: Virtualization Solutions

105 9. In the Network Details page, enter the following: a. IP address: <IP address> b. NetMask/Prefix: Netmask c. Interface: e0b 10. Click Next. 11. In the Protocols page, select the following: a. NFS b. CIFS c. iscsi Click Next. 12. In the Administration page, type in the root user password and click Next. 13. In the DNS, add the DNS information: NIS Information (skip) Click Next. In the vfiler unit Summary page, click Next. 14. Click Finish to complete the wizard. 15. Check the status of your new MultiStore system, and answer the question that follows: system> vfiler status r system> ifconfig a How many virtual storage systems does the system report? TASK 2: CREATE A CIFS SHARE ON A MULTISTORE SYSTEM In this task, you switch to the context of one of your MultiStore units and configure CIFS. 1. From the storage system CLI, connect to the MultiStore system: system> vfiler context vfiler1 2. Determine whether any shares exist, and answer the question that follows: vfiler1@system> cifs shares How is this different from what you see on the host storage system? E15-2 Data ONTAP 7-Mode Administration: Virtualization Solutions

106 3. Create a qtree to share on the MultiStore system: vfiler1@system> qtree create /vol/vfiler1/vtree1 vfiler1@system> qtree status vfiler1@system> qtree security /vol/vfiler1/vtree1 ntfs vfiler1@system> cifs shares -add vtree1 /vol/vfiler1/vtree1 4. From the Windows Server, map a network drive letter to the vfiler1 c$ share. 5. Check the system for the new CIFS session from the context of vfiler0: system> vfiler context vfiler0 system> cifs sessions 6. Check for cifs sessions in vfiler1 from the context of vfiler0, and answer the questions that follow: system> vfiler run vfiler1 cifs sessions How is this different from when you ran the same command in the context of the MultiStore system? What does the vfiler run command do? END OF EXERCISE E15-3 Data ONTAP 7-Mode Administration: Virtualization Solutions

107 MODULE 16: BACKUP AND RECOVERY METHODS EXERCISE: USING THE NDMPCOPY COMMAND In this exercise, you use NDMP to copy a volume. OBJECTIVE By the end of this exercise, you should be able to: Use the ndmpcopy command to copy a volume TASK: USE THE NDMPCOPY COMMAND TO COPY A VOLUME In this task, you copy data from a one aggregate to another. You use your assigned storage system as both the source and the destination system. 1. Log in to the storage system and ensure that the WAFL (Write Anywhere File Layout) default security style is set to ntfs: system> options wafl.default_security_style 2. Enable and configure NDMP: system> options ndmpd.enable on system> options ndmpd.access all 3. Create the source flexible volume on aggr1: system> vol create src_vol aggr1 100m 4. Verify that the volume is available and online: system> vol status src_vol 5. Create the destination flexible volume on aggr2: system> vol create dst_vol aggr2 105m 6. Verify that the volume is available and online: system> vol status dst_vol 7. Create a CIFS share for the source and destination volumes: system> cifs shares add source /vol/src_vol system> cifs shares add destination /vol/dst_vol E16-1 Data ONTAP 7-Mode Administration: Backup and Recovery Methods

108 8. Map the source share and copy and paste some files into the source volume. 9. Transfer data from the source volume to the destination volume: system> ndmpcopy /vol/src_vol /vol/dst_vol When the source and destination systems are the same, you can omit the -sa and -da options and the hostname from the ndmpcopy command. 10. Verify that the data was copied to the destination volume by mapping the destination share on your Windows host. END OF EXERCISE E16-2 Data ONTAP 7-Mode Administration: Backup and Recovery Methods

109 MODULE 17: DATA COLLECTION TOOLS EXERCISE: GATHERING DATA FOR SYSTEM MANAGEMENT In this exercise, you retrieve statistical information from the Data ONTAP operating system. OBJECTIVES By the end of this exercise, you should be able to: Identify the commands that you can use to troubleshoot problems Run the statit command on a storage system Run the stats command on a storage system TASK 1: IDENTIFY THE COMMANDS THAT YOU CAN USE TO TROUBLESHOOT PROBLEMS In this task, you run commands that are used for gathering information about MAC, TCP/IP, and protocol issues. 1. Run this command, and record the information that is requested: system> ifconfig a The command produces this type of information: 2. Run this command, and record the information that is requested: system> ifstat a The command produces this type of information: 3. Run this command, and record the information that is requested: system> arp a The command produces this type of information: 4. Run this command, and record the information that is requested: system> netstat r The command produces this type of information: 5. Run this command, and record the information that is requested: system> nfsstat The command produces this type of information: 6. Run this command, and record the information that is requested: system> exportfs The command produces this type of information: 7. Run this command, and record the information that is requested: system> cifs stat The command produces this type of information: E17-1 Data ONTAP 7-Mode Administration: Data Collection Tools

110 8. Run this command, and record the information that is requested: system> nbtstat The command produces this type of information: 9. Run this command, and record the information that is requested: system> cifs domaininfo The command produces this type of information: TASK 2: RUN THE STATIT COMMAND ON A STORAGE SYSTEM In this task, you use the statit command to view system statistics, disk utilization data, and performance data for various system operations. You can use this information to optimize system write performance. 1. Enter the advanced command mode and begin capturing data: system> priv set advanced system*> statit b 2. Wait a few minutes, and end the data capture and display a report: system*> statit e 3. Review the results, and answer the questions that follow: What percentage of the time were disks busy? Which RAID groups show activity? 4. Set the interface back to the administrative mode: system*> priv set admin TASK 3: RUN THE STATS COMMAND ON A STORAGE SYSTEM In this task, you use the stats commands to view system statistics, disk utilization data, and performance data for various system operations. You can use this information to help optimize system write performance. 1. Run this command and read through the stats manual page: system> man stats 2. Run this command and view the help: system> stats 3. Run this command and view the list syntax: system> stats list 4. Run this command to view objects that are associated with your system: system> stats list objects E17-2 Data ONTAP 7-Mode Administration: Data Collection Tools

111 5. Run this command to show all aggregates and traditional volumes in your system: system> stats list instances aggregate 6. Experiment by listing instances of other objects: system>stats list instances cifs system>stats list instances volume system> stats list instances disk system> stats list instances system system> stats list instances processor NOTE: Some objects might not have any instances when they are viewed. They are populated as you administer your system. 7. Run these commands: system> stats list instances qtree system> qtree create /vol/nasvol/stats_qtree 8. Now view the qtree instances again: system> stats list instances qtree Notice that the newly created qtree has been added as an instance. 9. Run this command to view the counters for an instance: system> stats list counters qtree Five counters are listed. 10. Run this command and view the command syntax: system> stats explain 11. Run these commands and read the explanations: system> stats explain counters qtree nfs_ops system> stats show qtree 12. Run this command and read the explanation: system> stats explain counters disk user_writes END OF EXERCISE E17-3 Data ONTAP 7-Mode Administration: Data Collection Tools

112 MODULE 18: DATA ONTAP UPGRADES There is no exercise for this module. E18-1 Data ONTAP 7-Mode Administration: Data ONTAP Upgrades

113 NETAPP UNIVERSITY Data ONTAP 7-Mode Administration Appendix A: Answers Course Number: STRSW-ILT-D7ADM-REV02 Catalog Number: STRSW-ILT-D7ADM-REV02-EG

114 MODULE 1: THE DATA ONTAP STORAGE ENVIRONMENT TASK 2: EXPLORE THE NETAPP SUPPORT SITE 1. Open a browser and go to the NetApp Support site at 2. Enter your NetApp user ID and password to log in. 3. Click the My Home tab. 4. Notice the categories across the top of the home page List the 7 main categories _My Home Products Downloads Cases & Parts Documentation Partners Tools 5. Click the documentation link, and navigate through the link to locate the documentation for Data ONTAP operating in 7-Mode. 6. Select All documents. 7. Locate the Data ONTAP Mode System Administration Guide link in HTML, and answer the following questions: 1. What are the methods for accessing the system? _A Telnet session A Remote Shell connection A web browser A secure shell client application. 2. What is the command to display the storage system s hardware configuration? _sysconfig A-2 Data ONTAP 7-Mode Administration: Appendix A: Answers

115 MODULE 2: WAFL SIMPLIFIED TASK 1: EXPLAIN HOW THE DATA ONTAP OPERATING SYSTEM WRITES DATA 1. WAFL write requests are stored in a buffer in memory, and a copy is added to the NVLOG RAM log. True. 2. The RAID manager determines where data will go on the disk. False. This is determined by the WAFL file system. 3. The RAID layer transfers data to the physical disks. False. The storage layer transfers data to physical disks. 4. The WAFL file system acknowledges a write request when the data is physically stored to disk and a consistency point is complete. False. The WAFL file system acknowledges receipt as requests are received. TASK 2: EXPLAIN HOW THE DATA ONTAP OPERATING SYSTEM READS DATA 1. Read requests are always processed from the disk. False. The WAFL file system might be able to satisfy the request from a read cache buffer. 2. A consistency point is a completely self-consistent image of the entire file system that is created when all of the data is written to the disks and a new root inode is determined. True. 3. A consistency point is initiated when the NVLOG is half full (single controller), after 10 seconds have elapsed, when a Snapshot copy is created, or when the system is halted. True. 4. Nonvolatile RAM (NVRAM) logs are flushed when a consistency point is completed. True. A-3 Data ONTAP 7-Mode Administration: Appendix A: Answers

116 MODULE 3: BASIC ADMINISTRATION TASK 3: ADD A STORAGE SYSTEM TO NETAPP SYSTEM MANAGER 7. When the dashboard panels for your storage system appear, read the panel names. Which six sections of information do you see? 1. Storage Capacity 2. Notifications/Reminders 3. Aggregates 4. Volumes 5. Properties 6. Disks TASK 6: LIST THE OPTIONS ON A STORAGE SYSTEM 1. From the storage system CLI, enter the options command, and answer the question that follows. system> options What happens? A long list of options is displayed. 2. At the prompt, enter the following command, and answer the question that follows: system> man options What happens? The manual page for the options command is displayed. 3. Quit the manual page by entering q. A-4 Data ONTAP 7-Mode Administration: Appendix A: Answers

117 4. At the prompt, enter the following commands: system> options ssh system> options telnet What are the results? Data ONTAP 7.3.X output: system> options ssh system> options ssh ssh.access * ssh.enable ssh.idle.timeout 0 ssh.passwd_auth.enable off on ssh.port 22 ssh.pubkey_auth.enable ssh1.enable ssh2.enable system> options telnet telnet.access telnet.distinct.enable telnet.enable on off off legacy off on Data ONTAP Mode and later output: system> options ssh system> options ssh ssh.access * ssh.enable on ssh.idle.timeout 0 ssh.passwd_auth.enable on ssh.port 22 ssh.pubkey_auth.enable on ssh1.enable off ssh2.enable on system> options telnet telnet.access legacy telnet.distinct.enable off telnet.enable off A-5 Data ONTAP 7-Mode Administration: Appendix A: Answers

118 TASK 7: USE THE CLI TO EXAMINE THE SYSTEM CONFIGURATION OF A STORAGE SYSTEM 1. From the storage system CLI, enter the sysconfig command. system> sysconfig What happens? You get system configuration output 4. Access System Manager for this storage system. Examine the Properties box within the dashboard page. How does the information from the sysconfig command compare with what you can find using System Manager? Both methods provide information about the system, including the model, version of Data ONTAP, and so on. NetApp System Manger formats the information, making it easier to read. But you must move to more than one screen to view all of the information. The sysconfig command shows more hardware information about the slots where hardware is installed. A-6 Data ONTAP 7-Mode Administration: Appendix A: Answers

119 MODULE 4: PHYSICAL STORAGE TASK 2: UNDERSTAND THE IMPACT OF DISK SCRUB ON A STORAGE SYSTEM 1. Answer these questions: 1. True or false? RAID scrubbing identifies media errors and rewrites information to another location on the disk. _True 2. True or false? Increasing the time interval that the system can operate in degraded mode is a smart and safe way of handling the system so that you don t need to reboot every 24 hours. _False 3. True or false? Two RAID groups of 10 disks each are more fault-tolerant for critical data than a RAID group of 20 disks. True 4. True or false? The Data ONTAP operating system automatically identifies an unqualified disk _True 5. True or false? A RAID group with 18 disks is recommended for optimal performance and fault tolerance. False. The default and recommended RAID group size is 16 disks. _ 6. Which options command enables you to set scrub performance?_b a. options raid.reconstruct_speed b. options raid.scrub.perf_impact c. options disk scrub d. options disk.performance.cpu 2. Issue this command to view system statistics every second: system> sysstat 1 Use Ctrl-C to stop this command when you are ready. Can you confirm whether or not the disks are in use from the output? Yes. The sysstat command shows disk activity even when you are not connected to clients and serving data. In this, there is probably little or no disk activity. 3. Issue this command to view the manual page for the sysstat command: system> sysstat x s 1 Use Ctrl-C to stop this command when you are ready. What does this command do? This command displays extra fields of information. 4. Start the disk scrubbing by entering this command: system> aggr scrub start Is there any visible sign that the scrub has begun? _No A-7 Data ONTAP 7-Mode Administration: Appendix A: Answers

120 5. While the disk scrub is running, issue the following command: system> sysstat 1 How does this output compare to the output before the disk scrub? No difference 6. Enter this command to stop the scrub: system> disk scrub stop TASK 4: USE NETAPP SYSTEM MANAGER TO CREATE A 64-BIT AGGREGATE 1. In the left pane, expand Storage > Aggregates and notice that only one aggregate (aggr0, the default aggregate) is currently available. 2. In the right pane, click Create to start the Create Aggregate Wizard. 3. Click Next. The Aggregate Details page appears. A-8 Data ONTAP 7-Mode Administration: Appendix A: Answers

121 4. In the Aggregate Name field, enter aggr1 and retain the default values for RAID Type. 5. Click Next. 6. Click the Select disks button, select FCAL and change the number of capacity disks to use to Click Save and Close. 8. On the Create Aggregate Wizard page, click Create. 9. After the wizard successfully creates the aggregate, click Finish. 10. In the Aggregates pane, verify that the aggregate that you created is included in the list of aggregates. This aggregate has five disks. Is the available space five times the size of one disk? Explain why or why not. No. There are some disks used for parity. TASK 5: USE THE CLI TO CREATE A 64-BIT AGGREGATE 3. Verify that you have created the aggregate. system> aggr status What is the default RAID type of an aggregate? _RAID_DP A-9 Data ONTAP 7-Mode Administration: Appendix A: Answers

122 TASK 6: CAUSE A DISK TO FAIL 1. At the storage system CLI, enter one of these two commands to view the disk ID numbers for aggr1: system> aggr status aggr1 r system> sysconfig r 2. Record the ID of a disk in aggr1. Are there any failed disks? 3. At the storage system CLI, enter this command: system> options raid.reconstruct.perf_impact high 4. Verify the current aggregates: system> aggr status 5. At the storage system prompt, enter this command: system> disk fail device_id_from_step_1 What messages were displayed on the CLI? You will see messages related to the disk being failed 6. Answer y to prefail the disk. What would happen if you failed a disk in aggr1 with no hot spare available? You will see a warning related to the lack of spare disks 7. When the reconstruction is complete, make sure that the failed (broken) disk is available for use later in the class by entering the following at the storage system CLI: NOTE: Wait until the reconstruction is complete before you continue. system> sysconfig -r system> disk zero spares A-10 Data ONTAP 7-Mode Administration: Appendix A: Answers

123 MODULE 5: LOGICAL STORAGE TASK 1: USE SYSTEM MANAGER TO CREATE A VOLUME 4. Click Create to add your new volume. How much space is available for data? _79.92MB TASK 4: CREATE QTREES 4. Click Create. How much space is available for data in the NASqt1 qtree? The total amount of available space in the volume: 79.92MB A-11 Data ONTAP 7-Mode Administration: Appendix A: Answers

124 MODULE 6: ADMINISTRATION SECURITY TASK 1: USE SYSTEM MANAGER TO CREATE AN ADMINISTRATIVE USER ACCOUNT 5. Open a telnet session to your storage system to test the new user account. At the login prompt, enter the new user name and the new password. Are you able to log in?_ Yes TASK 2: USE THE CLI TO CONFIGURE ADMINISTRATIVE SECURITY 7. Verify that the local user was added to the storage system by entering the following command: system> useradmin user list your_name What are the allowed capabilities for this user? Allowed Capabilities: login-telnet 8. Verify the allowed capabilities for the root account by entering the following command: system> useradmin user list root What are the allowed capabilities for the root user? Allowed Capabilities: * 9. View the list of all local storage system users by entering the following command: system> useradmin user list Which local users are listed? Answers may vary. A-12 Data ONTAP 7-Mode Administration: Appendix A: Answers

125 TASK 3: LOG IN WITH A NEW USER ACCOUNT 4. At the storage system prompt, view the RAID group configuration by entering the following command: system> sysconfig -r What was the response? system> sysconfig -r Permission denied, user x does not have access to sysconfig [useradmin.unauthorized.user:warning]: User 'x' denied access - missing required capability: 'cli-sysconfig' What capability do you need in order to execute this command? You need to belong to a group with the required capability: 'cli-useradmin' 12. At the storage system prompt, view the RAID group configuration: system> sysconfig -r Did the command execute properly? Yes A-13 Data ONTAP 7-Mode Administration: Appendix A: Answers

126 MODULE 7: NETWORKING TASK 3: USE THE CLI TO CREATE A SINGLE-MODE INTERFACE GROUP In this task, you review the purpose of interface groups and create a single-mode interface group. NOTE: In Data ONTAP 7.3.X, interface groups are called virtual interfaces (or vifs). Use either the vif command or the ifgrp command for your OS release. 1. Answer these questions: Which statement describes the purpose of a single-mode interface group? Answer: A Which two of these statements describe what a multimode interface does? (Choose two) Answer: A and B How many interfaces can you configure in a multimode interface group? Answer: A, but you would probably have more than just one 11. Attempt to destroy the interface group while it is up: system> ifgrp destroy singletrunk1 What happens? The ifgrp has to be down first TASK 4: USE THE CLI TO CREATE A MULTIMODE INTERFACE GROUP 7. Check the status of the new interface group: system> ifgrp status What is the load-balancing policy? IP Balanced How many links are active? both What is the interface group type? multi A-14 Data ONTAP 7-Mode Administration: Appendix A: Answers

127 MODULE 8: NFS TASK 3: USE THE CLI TO EXPORT A VOLUME 4. Verify whether automatic exporting of new volume is enabled: system> options nfs.export.auto-update Is this option enabled? _Yes 8. List the current exports: system> exportfs Were other existing volumes exported when you licensed NFS? _No, the nfs.export.auto-update option only exports the volume. _ 13. Verify that the new qtree is visible from the client: # showmount e storage_system_ip Can you see the new qtree nfs_tree1 from the client? No 22. Reload the exports file: system> exportfs a system> exportfs Was the nfs_tree1 qtree exported? _Yes TASK 4: MOUNT EXPORTS FROM AN ADMINISTRATION HOST In this task, you mount the exports that you created earlier in this exercise. 4. You should now be able to view the directory structure of your storage system s root volume. # ls al/mnt/system_name/vol0 How does this compare with the local client root? (Hint: # ls al /) The export path is the root volume of the storage system and the root of the local UNIX machine. 5. Try to create a file at the root of the storage system: # touch foo Were you able to create a file? No, because the export has read-only permissions. 9. Check the disk usage on your storage system. system> df h /vol/nfsvol Can you tell that the files you created earlier reside on the storage system? _Yes A-15 Data ONTAP 7-Mode Administration: Appendix A: Answers

128 MODULE 9: CIFS TASK 1: USE ONCOMMAND SYSTEM MANAGER TO LICENSE CIFS SERVICE 1. From OnCommand System Manager, click Configuration > Protocols. Why is CIFS not listed? _Because it hasn t been licensed yet CIFS is not listed, because it hasn t yet been licensed. TASK 9: TERMINATE CIFS SESSIONS 3. Right-click a session and select Disconnect All Sessions. Did it close? Why or why not? No, because there is only one session and computer management is using that session. If there were multiple sessions, you would be able to close other sessions not used by Computer Management. 13. Click Diagnostics > Sessions. Are there any CIFS sessions? _No 17. Click Diagnostics > Session. Are there any CIFS sessions? No What do you need to do to reestablish the CIFS session? On the client reconnect to the share A-16 Data ONTAP 7-Mode Administration: Appendix A: Answers

129 MODULE 10: NAS MANAGEMENT TASK 1: CREATE AND MANAGE QUOTAS 25. When you exceed the quota threshold, what do you see on the CLI? Example output: [quota.softlimit.exceeded:notice]: Threshold exceeded for tree 1 on volume NASvol When you exceed the quota threshold, what do you see on the client? Nothing When you exceed the quota soft block value, what do you see on the CLI? Example output: [quota.softlimit.exceeded:notice]: Threshold exceeded for tree 1 on volume NASvol When you exceed the quota soft-block value, what do you see on the client? Nothing 26. How much more data do you need to add to the share to exceed the hard block quota? 4MB 27. Add enough data to exceed the hard block quota. What do you see on the CLI? Example output: [quota.hardlimit.exceeded:notice]: Threshold exceeded for tree 1 on volume NASvol When you exceed the quota hard-block value, what do you see on the client? A message that you are out of disk space TASK 3: MODIFY THE /ETC/QUOTAS FILE AND IMPLEMENT QUOTA CHANGES 6. Do your changes take effect automatically? _No 13. Read the manual pages for the quota report command and give a brief description of the following arguments. (Use the man command.) Answers will vary A-17 Data ONTAP 7-Mode Administration: Appendix A: Answers

130 14. Continue to review the manual page for the quota command. What is the purpose of the logmsg subcommand? allows the user to specify a time interval for a volume during which quota messages for that volume will be disabled. With no arguments, the quota logmsg command displays the current interval settings. TASK 4: CREATE QTREES AND QUOTAS FOR THE QTREES USING THE COMMAND-LINE INTERFACE 2. View the qtrees that you just created. What is the security style? unix 3. Edit the correct file to give the cobra qtree a size limit of 50 MB with a threshold of 45 MB, and the firebird qtree a limit of 20 MB with a threshold of 18 MB. Limit the files on firebird to 10. Use tree for the type on both quotas. Which file did you edit? /etc/quota Record the entries you create. # TARGET TYPE DISK FILE THRESHOLD SDISK SFILE /vol/nasvol/cobra tree 50M - 45M /vol/nasvol/firebird tree 20M 10 18M 4. How did you edit the file? wordpad 5. What does the entry look like that gives the /vol/vol0 flexible volume a default quota of 150 MB of disk space with a threshold of 145 MB for any user? # TARGET TYPE DISK FILE THRESHOLD SDISK SFILE /vol/vol0 user 150M - 145M 6. Enable quotas, then set the interval for the log to two hours on /vol/vol0/eng: system> quota on /vol/vol0 system> quota logmsg on 120m -v /vol/vol0 Which command lets you view the thresholds for all quotas? quota report t A-18 Data ONTAP 7-Mode Administration: Appendix A: Answers

131 7. Change the quotas for the firebird qtree to the same settings as the cobra qtree. When you change the size of a quota, what command do you enter for changes to take effect? quota resize TASK 5: CREATE A NATIVE FILE-BLOCKING POLICY 11. Try to copy Song.mp3 from the C:\_files\D7ADM classroom folder to a mapped drive associate with your storage system. Were you able to copy the file?_no 14. Can you create a.mp3 file now? Yes. A-19 Data ONTAP 7-Mode Administration: Appendix A: Answers

132 MODULE 11: SAN TASK 2: CONFIGURE ISCSI ON WINDOWS SERVER 2012 In this task, you configure Windows Server 2012 to be an iscsi initiator. Answers are in Appendix A of this guide. 17. Click the Targets tab and notice that it shows one discovered target. What is the current status of this target? inactive 18. Highlight the target and click the Properties button. How many current sessions are there? Answers will vary 19. Click the Portal Groups tab. How many portal groups has Windows identified? Answers will vary A-20 Data ONTAP 7-Mode Administration: Appendix A: Answers

133 MODULE 12: SNAPSHOT COPIES TASK 4: USE SYSTEM MANAGER TO MANAGE SNAPSHOT COPIES 6. Do hourly Snapshot copies occur every hour? No, only when scheduled 7. How can you view the Snapshot copy schedule for the root volume? Look at vol0 8. Can you change the percentage for the Snapshot reserve? Yes; select the volume and click Snapshot Configure 9. Select a volume and click the Snapshot Copies tab to examine the amount of space that is used by the Snapshot copy. Record the totals for snapa on NFSvol: snapa Total: Answers will vary snapa Used: Answers will vary TASK 5: RESTORE A FILE USING THE WINDOWS PREVIOUS VERSION TOOL 11. Click the Previous Versions tab. How many versions do you see? _1 12. Select the version and then click to view the file. What do you see? You see the first version of the file. TASK 7: REVERT A VOLUME USE SNAPRESTORE TECHNOLOGY TO RESTORE A VOLUME In this task, you restore NFSvol by using SnapRestore technology. Answers are in Appendix A of this guide. 3. Enter mystuffsnap2 and type y to confirm that you want to proceed. After the reversion is complete, which files are still present in NFSvol? 2 4. List the Snapshot copies for NFSvol. Compare this list to the list of Snapshot copies before the volume reversion. Do the lists differ? Why or why not? Yes, because restoring the mystuffsnap2 also deleted some snapshots that occurred after mystuffsnap2 A-21 Data ONTAP 7-Mode Administration: Appendix A: Answers

134 TASK 8: USE SNAPRESTORE TECHNOLOGY RESTORE A FILE 5. Revert mystuff1 file from the Snapshot copy mystuffsnap1. system> snap restore /vol/nfsvol/cifs_tree2/mystuff1 How did the restore command differ this time from when you restored a volume? This time you provided a file name and the command responded with a warning that you are about to overwrite an existing file. 6. What is the timestamp of the restored file? Answers will vary A-22 Data ONTAP 7-Mode Administration: Appendix A: Answers

135 MODULE 14: HIGH AVAILABILITY (OPTIONAL EXERCISE) TASK 1: ENABLE CONTROLLER FAILOVER 1. Look at the hardware on your system. Do you see any indication that your storage system is cabled for HA? Yes Which command provides information about the hardware that is installed on your storage system? sysconfig 3. system> cf status Cluster disabled. VIA Interconnect is down (link 0 down, link 1 down). Partner is unknown 7. Enable HA on system2. system2> cf enable How does this affect system? Enables cf on both nodes 11. Click Refresh. What happens? The previously configured system is gone. Why? The separate systems are really one now. 12. Add your storage system again. What happens? Both storage systems are added. TASK 2: PERFORM A CONTROLLER FAILOVER 8. Check the console of system2. How long did it take for system2 to complete the takeover? Answers will vary 9. Observe the results on the clients. What happened to the Windows client connection? The connection dropped 10. Check the mountpoint on the UNIX client. What happened to the UNIX connection? The connection did not drop What caused the difference between the NFS and CIFS connections during takeover? NFS is a stateless protocol A-23 Data ONTAP 7-Mode Administration: Appendix A: Answers

136 14. Now run the same commands from within the system that has been taken over: system2(takeover)> partner system2/system> sysconfig r system2/system> sysconfig v system2/system> sysstat 1 Was there a difference between the two storage system outputs? No 15. From your client, access system s cifs_tree share. Can you still access the data? Yes Can you still access the LUN? Yes A-24 Data ONTAP 7-Mode Administration: Appendix A: Answers

137 TASK 3: PERFORM A CONTROLLER GIVEBACK 2. On system, when you are prompted with the message waiting for giveback, either issue the giveback -f command on the system2 CLI or use NetApp System Manager. CLI method: system2> giveback -f Do you need the f option? Why or why not? If there are active CIFS sessions then you could use the f to force the giveback NetApp System Manager method: In NetApp System Manager, click the Giveback button: A-25 Data ONTAP 7-Mode Administration: Appendix A: Answers