Data Fabric Solution for Cloud Backup (SnapCenter for NAS File Services including the Data Fabric) July 2017 SL10374 Version 1.1.0

Transcription

1 Data Fabric Solution for Cloud Backup (SnapCenter for NAS File Services including the Data Fabric) July 2017 SL10374 Version 1.1.0

2 1 Introduction This lab demonstrates the SnapCenter Plug-in for NAS File Services capabilities, including use in the NetApp Data Fabric Solution for Cloud Backup (DFSCB). The lab ctivities illustrate some of the basic tasks and workflows of the Data Fabric Solution for Cloud Backup. SnapCenter and its Plug-in for NAS File Services can be used to protect Windows and UNIX file shares in either of the following cases: Backup of NAS File Services from FAS/AFF primary to a Vault relationship on FAS/AFF secondary. As part of the DFSCB solution with AltaVault 4.3 for a solution that allows customers to back up and restore CIFS or NFS to the cloud. In either case, backup contents are cataloged for easy location and retrieval. Both scenarios are covered in this lab guide. This lab uses StorageGRID WebScale (SGWS) as the object storage solution, like a private cloud. SGWS is also used by many service providers to offer a public cloud solution. All the cloud options for AltaVault, except for Amazon Glacier, can be used for the cloud (object) storage. Some of the key features of the SnapCenter Plug-in for NAS File Services include: Provides an efficient, end-to-end file and directory-level backup and recovery solution. Offers integrated SnapMirror protocol with NetApp AltaVault cloud-integrated storage that provides block-level incremental forever backup. Uses SnapCenter management software to manage data protection workflow from end to end. Offers an integrated file catalog that allows file search and recovery. With the plug-in for NAS File services, storage administrators and IT generalists can perform Snapshot copybased data protection operations for Windows and UNIX file shares. The data protection (backups) can be managed from either ONTAP, SnapVault destination, public cloud providers or private cloud object stores. This solution includes NetApp ONTAP, SnapCenter data management software, and AltaVault cloud-integrated storage software to deliver high service levels with fast Snapshot copies, and efficient array-based replication. ONTAP provides storage management and initiation, and management of protection operations using a command-line interface (CLI). SnapCenter provides support for protection operations initiation and management. AltaVault provides storage-optimized space in cloud storage providers for Snapshot copies of file share data from ONTAP. 1 Overview of Solution NetApp SnapCenter and its Plug-in for NAS File Services (including the Data Fabric Solution for Cloud Backup) is intended to provide backup functionality for customers that are using ONTAP. The DFSCB solution offers two replication topology types that are defined by the supported cascade relationships as shown in the following figure. 1. The first topology is ONTAP, running on FAS or AFF, replicating using SnapMirror directly to AltaVault. 2. The second topology is ONTAP replicating using SnapMirror to a disaster recovery FAS/AFF appliance, then to an AltaVault. 3. SnapCenter and its Plug-in for NAS File Services by itself offers the ability to backup, catalog, and restore Windows and UNIX file shares in a FAS/AFF to FAS/AFF vault. These three supported topologies are available in SnapCenter as protection policies. SnapMirror is mentioned in all documentation pertaining to this solution. Anyone with experience using NetApp replication technologies should note that SnapMirror is the transport. In ONTAP, the type of relationship created is SnapMirror XDP. For previous versions of ONTAP there was a differentiation of Snapshot replication technologies using SnapMirror and SnapVault. In ONTAP 9.1, SnapMirror and SnapVault functionality are combined into unified replication using the same engine to move the data. 2

3 The replication to AltaVault uses SnapMirror as the transport, but the retention of the snapshots is the same as what was previously referred to as SnapVault. AltaVault s SnapMirror feature allows for the destination of the replication, the AltaVault, to maintain a separate and non-symmetrical list of Snapshots compared to the primary or source of the replication just like SnapVault did. Figure 1-1: The required configurations for this solution are as follows: SnapCenter 3.0 ONTAP 9.1 FAS or AFF Cluster AltaVault (For DFSCB solution) Cloud storage StorageGRID Webscale SnapMirror configuration SnapCenter user role Replication report Front end report SVM volumes SVM shares 1 Prerequisites This lab has the following prerequisites: 3 Basic understanding of NetApp SnapMirror technology. Basic understanding of SnapCenter see the SnapCenter lab. Basic understanding of AltaVault see the AltaVault lab.

4 This lab assumes prior experience with NetApp products including FAS/AFF, AltaVault, and SnapCenter 2.0. A basic understanding of Microsoft Windows is also necessary. Note: There are labs specific to each of these products and technologies in Lab On Demand. If you are not familiar with any of these products, consider taking those labs first. 4

5 2 Lab Environment Figure 2-1: While there are three topologies supported for SnapCenter Plug-in for NAS File Services, including Data Fabric Solution for Cloud backup, for purposes of brevity only the two shown in the figures below are covered in this lab. Figure 2-2: 5

6 Figure 2-3: Table 1: Table of Systems 6 Host Name Operating System Role/Function IP Address cluster1 ONTAP 9.1 cluster cluster1-01 ONTAP 9.1 cluster 1 node cluster2 ONTAP 9.1 cluster cluster2-01 ONTAP 9.1 cluster 1 node svm1 Storage Virtual Machine for VMware datastore on NFS SVM mgmt lif jumphost Windows Server 2012 R2 primary desktop entry point for lab dc1 Windows Server 2008 R2 Active Directory / DNS snapctr1 Windows Server 2012 R2 NetApp SnapCenter index1 RedHat Enterprise Linux 7 Index server for SnapCenter altavault AVA-V virtual appliance sgntp SUSE Linux Enterprise 10 Network Time Protocol SP3 server for SGWS sgdc1s3 SUSE Linux Enterprise 11 StorageGRID Webscale 10.3 Storage Node sgdc1s2 SUSE Linux Enterprise 11 StorageGRID Webscale 10.3 Storage Node NetApp AltaVault 4.3.1

7 Host Name Operating System Role/Function IP Address sgdc1s1 SUSE Linux Enterprise 11 StorageGRID Webscale 10.3 Storage Node sgdc1g1 SUSE Linux Enterprise 11 StorageGRID Webscale 10.3 Gateway Node sgdc1arc1 SUSE Linux Enterprise 11 StorageGRID Webscale 10.3 Archive Node sgdc1adm1 SUSE Linux Enterprise 11 StorageGRID Webscale 10.3 Admin Node User IDs and Passwords 7 Host Name User ID Password Comments jumphost DEMO\Administrator Netapp1! Domain Administrator cluster1 admin Netapp1! Same for individual cluster nodes cluster2 admin Netapp1! Same for individual cluster nodes svm1 vsadmin Netapp1! svm administrator snapctr1 DEMO\scadmin Netapp1! SnapCenter Administrator rhel root Netapp1! index server linux root administrator sgws node root bycast node login sgws admin UI root netapp01 admin node Web management sgws admin UI Vendor Netapp1! admin node Web UI for Vendor

8 3 Lab Activities The purpose of this lab is to ilustrate some of the basic tasks and workflows of the Data Fabric Solution for Cloud Backup. This lab contains the following activities and tasks: Use SnapCenter to Backup a Volume to Cloud on page 25 Connect to SnapCenter and Review Configuration on page 8 Connect to AltaVault and Review Configuration on page 17 Provision and Protect a new Volume/share using OnCommand System Manager on page 33 Browse and Restore a directory of files to their original location on page 47 Search and Restore a File on page 53 Change a volume/share from Backup to Vault to Backup to Cloud on page 60 Modifying a Policy on page Connect to SnapCenter and Review Configuration NetApp SnapCenter Software allows enterprises to leverage a simple and scalable interface to coordinate and manage data protection across multiple applications and databases. Note: If you are not already familiar with the SnapCenter interface, consider the Data Protection Management with NetApp SnapCenter and SnapCenter Plug-ins lab, in Lab On Demand, before proceeding with this lab. This lab activity serves as an introductory tour to the user interface (UI) for the NetApp Plug-in for NAS File Services. You will explore the layout of the UI, and examine areas of adminstrative configuration options. 1. From the Jumphost, open the SnapCenter GUI (double click the desktop shortcut). Figure 3-1: 2. Enter the login credentials - username: demo\scadmin, password: Netapp1!. 8

9 2 Figure 3-2: 3. On the Dashboard page, notice the SnapCenter Plug-in for NAS File Services in the plug-in dropdown selection. If other plug-ins were enabled they would also be displayed. SnapCenter s role-based access control governs what users have access to (i.e., what they see). 3 Figure 3-3: 4. Storage Connections - On the left-hand navigation bar click Storage Systems. Notice that there are three storage connections set up; one for each cluster, and the other for the AltaVault system. 9

10 4 Figure 3-4: 5. Select the cluster1 entry. 6. Click Modify to view the details of the connection. 6 5 Figure 3-5: 7. Note (but do not change) the following on the Modify Storage Connection screen. 10 Storage Type must be set to ONTAP ClusterNote: There is an ONTAP SVM storage type, but it is not used for this lab. Storage System name is also the DNS address used. User name is the name of the user with cluster level permissions. Site is used for resource categorization that can be based on user preference (geography, business unit, etc.). Protocol, Port and timeout can be customized. In the case where there are multiple IP addresses, a preferred address may be specified. Options are also provided to send SnapCenter Server events to the syslog on the storage system, and if desired also send AutoSupport notification for failed operations to the storage system.

11 8. Click on the X at the upper right of the Modify Storage Connection screen (or click Cancel ) to close the dialog box. 8 Figure 3-6: 9. Now view the Altavault Storage Connection settings by repeating the same steps of highlighting Altavault. 10. Click on Modify. 11

12 10 9 Figure 3-7: 11. Note (but do not change) the following on the Modify Storage Connection screen. Storage Type must be set to AltaVault. Storage System name is also the DNS address used. User name is the user role that was specifically created for SnapCenter on the AltaVault. There is a site field for categorization that can be based on user preference (geography, business unit, etc.). Protocol, Port and timeout can be customized. 12. Click on the X at the upper right of the Modify Storage Connection screen (or press Cancel ) to close the dialog box. 12 Figure 3-8: 12

13 13. Ensure that the cluster1 connection is selected (not Altavault). 14. Click the Configure CIFS servers button at the upper right of the window. This step is done for any storage controllers that will have CIFS shares Figure 3-9: 15. On the Configure CIFS Servers screen, click the RunAs drop-down box, select cifs for the RunAs account, and click OK. This RunAs account allows SnapCenter to mount CIFS shares as necessary. Note: The previous steps are repeated for each cluster from which you want to discover the shares. In this lab we have not done this for cluster2, since it is used strictly as a vault. The Run As name is a name assigned to the credentials. The User name is the domain user with permissions to list or back up the files. The User name is specified as domain\user or user@domain.com. 15 Figure 3-10: 13

14 3.1 Policies A backup policy defines the schedules, retentions, and destinations used in the protection of a volume. It can be used by one or more volumes. 1. On the left-hand navigation bar click Settings. 2. Click on Policies at the top.the three policies indicated by arrows are the canned policies provided for each of the three supported topologies. Backup to Cloud for FAS/AFF to AltaVault Backup to Vault for FAS/AFF to FAS/AFF Backup to Vault to Cloud for FAS/AFF to FAS to AltaVault To use the default templates, the template must be copied and modified. Once copied and modified, the new policy will show on the Resources page. This process is covered in a later step. Note that there is already one policy copied and modified for use ( Backup to Cloud Altavault ). 3. Click on the policy named Backup to Cloud AltaVault, to highlight it in the table. 4. Click Details Figure 3-11: 5. Review the details for this backup policy. The details dialog shows the retention of both the local snapshot copies on the source ONTAP cluster, and the retention of snapshots on the AltaVault. In this example, a total of 2188 snapshots will be retained by AltaVault in cloud storage, with the most recent data cached locally on the AltaVault appliance. Note: AltaVault automatically handles retention of the data in the cloud (object) storage based on when snapshots are added or expired by SnapCenter. 6. Click Close. 14

15 6 5 Figure 3-12: 7. Click Resources. Review volume layout and details. On each of the volumes displayed, note the following: 15 The size of the volume (not the amount used). There is a shield on the right of each volume card. The color has the following meanings. Grey - Not Protected Green with white check - Protected, scheduled for backup Orange with black line - Not available for backup Grey with blue outline and progress circle - In process, temporarily not available Green with white triangle and exclamation mark - Partial unprotected, retry removing protection

16 7 Figure 3-13: 8. Click the down arrow on vol1 to get more details. The details show the volume status, the storage system, Shares, tags, and the policy to which the volume is attached. In this case since the status is unprotected, there is no policy attached. 8 Figure 3-14: 16

17 3.2 Connect to AltaVault and Review Configuration 1. Login to the AltaVault UI using the browser on the Jumphost. Figure 3-15: 2. The username is admin, and the password is Netapp1! 2 Figure 3-16: 3. The home page is presented when you first login. This page provides an overview of the health and status of the AltaVault appliance. Note: If the wizard displays when logging in to the AltaVault, exit the wizard to return to the home page. The home page provides a green, yellow or red status to indicate overall health. Yellow or red status is shown when there are alerts on the appliance. The appliance can also notify administrators of problems using SNMP, notifications, or AutoSupport. 17

18 The home page provides a quick way to view overall appliance and cloud capacity utilization, OS version, storage optimization (deduplication/compression factor), and cloud connection status. It is also possible to view important background tasks such as reclamation and replication. 3 Figure 3-17: 4. Also notice the Cloud connections status. In this case the AltaVault is connected to a StorageGrid WebScale system. 18

19 4 Figure 3-18: 5. Click the Configure menu, and click SnapMirror. SnapMirror configuration for the AltaVault is performed after the cloud storage is configured. Configuring Cloud storage is a required first step in any AltaVault deployment. You will not be able to configure any of the shares used for backup without first configuring cloud storage. After cloud storage is configured and the AltaVault can connect and validate access, the home page will give a green status showing it is ready for the share to be configured. There are a few steps you need to do to prepare an AltaVault appliance for a SnapMirror backup using SnapCenter. 19 Enable SnapMirror, then restart the storage optimization service. Add the Intercluster LIF IP addresses to the whitelist. This is the list of Intercluster LIFs from any ONTAP cluster that will be sending data to the AltaVault. Enable SnapCenter access. Create a user role for SnapCenter to access the AltaVault appliance for configuration and management.

20 5 Figure 3-19: 6. View that SnapMirror has been enabled. 6 Figure 3-20: 7. Scroll the window to view the Whitelist that contains the IP addresses for the Intercluster LIFs of the ONTAP clusters (cluster1 and cluster2). 20

21 7 Figure 3-21: 8. Scroll the window to view the two remaining settings. Long Term Retention is a setting that SnapCenter enables. This allows the retention of Snapshots beyond the normal DataONTAP retention of 251 for SnapMirror. AltaVault can retain up to 3700 Snapshots to allow daily Snapshots for approximately 10 years. This requires an external application like SnapCenter to manage the longer snapshot retention. This setting tells AltaVault to ignore Snapshot deletes from any DataONTAP DP policy that is using this AltaVault appliance Note: We recommend that you not mix SnapCenter and DataONTAP DP policies to manage Snapshot retention on a single AltaVault appliance. SnapCenter Access must be enabled before the SnapCenter server can access the AltaVault appliance. 21

22 8 Figure 3-22: 9. You must also create a user role before SnapCenter can access an AltaVault appliance. Using the AltaVault admin account is not permitted. Click on the Configure menu, then click User Permissions. 22

23 9 Figure 3-23: 10. Click the arrow next to the scadmin user to expand the user information. 23

24 10 Figure 3-24: 11. View the user details. You can see that a user role was created with the name scadmin. The name can be any name an administrator chooses, and must be the same account configured in SnapCenter when adding the AltaVault as storage. The role-based user account is assigned all permissions in this configuration. In a typical setup, it would more common to give limited access to the SnapCenter user. The minimum permissions required are Read/Write for: 24 General Settings Replication Settings Storage Settings

25 11 Figure 3-25: 3.3 Use SnapCenter to Backup a Volume to Cloud In this activity, you are going to protect a volume. The volume vol1 has been discovered by SnapCenter, and a policy has been created ( Backup to Cloud AltaVault ). This workflow not only does a backup, but sets up a replication relationship including provisioning at the destination. 1. Log onto the SnapCenter GUI by clicking the SnapCenter icon on the desktop of the Jumphost, using the credentials demo\scadmin, with password Netapp1!. 2. From the left-hand navigation bar, click Resources. The Resources page opens and displays the volumes available and their protection status. Volumes are displayed in cards that have colors to indicate their status. Volumes with grey shields are available to protect. Volumes with yellow shields indicate they are not available for protection (offline, root volume, etc.) 25

26 2 Figure 3-26: 3. Click on the Backup to Cloud AltaVault policy. 4. To protect the vol1 volume, either click on the + sign in the lower right of the volume tile, or click the whole card and drag it to the policy. You can now see there is one volume assigned to be protected under that policy. If there was more than one volume you wanted to protect you could continue to click the + sign for each volume, or click and drag it to the policy. If you make a mistake you can click the - sign in the lower right of the volume tile to remove it from this policy. When vol1 is added, the volume becomes highlighted and the policy shows a Create Backup link in the lower right corner of the policy card. If there were multiple policy cards, you would first select the policy you want to add to, then click the + sign. Note: Remember that a volume can be assigned to exactly one backup policy. It can be unprotected and re-protected under a different policy (covered later). 3 4 Figure 3-27: 5. Click Create Backup to start the backup. 26

27 5 Figure 3-28: 6. At the bottom of the screen you will see the protection job starting. The operations that are performed include the following: The configuration is validated. A snapshot is taken of the volume in ONTAP. A relationship is created between the ONTAP cluster and the AltaVault for SnapMirror when the create button is clicked on the policy. The snapshot is used as the baseline transfer from ONTAP to AltaVault. As soon as the data is received by the AltaVault, it deduplicates, compresses and encrypts the data, and immediately starts replicating to StorageGRID Webscale. 27 The volume s file structure is traversed with indexing details collected about the contents. The backup is registered with the index server, including the file contents of the volume. When the backup finishes copying to SGWS, the AltaVault will mark the operation as complete in notify SnapCenter.

28 6 Figure 3-29: 7. You can monitor the job for completion here in the activity panel, or proceed to step 8 to view the details of the job. Note: SnapCenter considers the successful backup to the AltaVault as in the cloud. 8. On the left-hand navigation bar, click Monitor, click the top job Applying Protection, and click Details. 8 Figure 3-30: 9. Each of the steps can be expanded to reveal more details of the backup job. 10. When you are done reviewing the details, click Close. 28

29 9 10 Figure 3-31: 11. From the left-hand navigation bar, click Resources. You will now see that the volume vol1 is now showing Protected. 12. Hover over the shield icon to see the status definitions. 29

30 11 12 Figure 3-32: 3.3 Review Data ONTAP Data Protection Relationship and Network Interfaces in OnCommand System Manager 1. Launch the OnCommand System Manager using the shortcut on the desktop. Figure 3-33: 2. Login to System Manager with username admin and password Netapp1!. 30

31 2 Figure 3-34: 3. OnCommand System Manager shows the current protection relationships. Protection relationships show the SnapMirror relationship that SnapCenter created from the cluster to the AltaVault. From the menu, click Protection, and choose Relationships. 3 Figure 3-35: 4. The Relationships view shows that svm1 vol1 is SnapMirrored. The details in the bottom of the view shows the destination as the AltaVault IP address. The schedule for this relationship is controlled by SnapCenter. So, there is no schedule associated with this policy in OnCommand System Manager (it is considered externally managed from ONTAP). 31

32 4 Figure 3-36: 5. Click Network from the top menu. 5 Figure 3-37: 6. Click the Network Interfaces tab to view the configured network interfaces. The left column is the name of the logical interface (LIF) The cluster_mgmt LIF is an important managment interface that is used to access System Manager, and is used by SnapCenter to perform cluster related tasks such as volume discovery, snapshot creation and SnapMirror tasks. The LIF role must be Cluster Management, and is a dedicated LIF. Important interfaces for SnapMirror to AltaVault are the cluster_ic1, and cluster_ic2 LIFs. There are the cluster interconnect LIFs that are used for SnapMirror protocol to send data to AltaVault. The LIF role must be Intercluster, and is a dedicated LIF. 32

33 6 Figure 3-38: 3.4 Provision and Protect a new Volume/share using OnCommand System Manager In this activity you create a new volume, add a file to that volume, create a new protection policy, and protect the new volume using that policy. 3.4 Provision a new volume using System Manager 1. From the Jumphost, open the OnCommand System Manager cluster1 (double click the desktop shortcut). 2. Enter the login credentials - username: admin, password: Netapp1!. 3. Click SVMs. 3 Figure 3-39: 4. Click svm1. 33

34 4 Figure 3-40: 5. Click Volumes. 5 Figure 3-41: 6. Click Create to create a new volume. 6 Figure 3-42: 7. In the Create Volume wizard, use the following parameters illustrated in the screen below, then click Create. 34 Name: vol2. Aggregate: aggr1_01. Storage type: NAS (Used for CIFS or NFS access).

35 Size: 20 GB. 7 Figure 3-43: 8. Make sure the new vol2 volume is selected, then click on the Data Protection tab at the bottom. Notice there is no protection relationship at this point. 35

36 8 Figure 3-44: 9. If you click on vol1 you will see that there is a relationship established in a previous exercise. 10. With svm1 still selected, click Shares Figure 3-45: 11. Click Create Share. 36

37 11 Figure 3-46: 12. In the Create Share dialog box, set the parameters as shown, and click Create. Folder to share: /vol2. Share Name: vol2. 12 Figure 3-47: 13. From the Jumphost desktop, double-click on the vol1 (svm1-cifs.demo.netapp.com) shortcut. 37

38 Figure 3-48: 14. Click in the address box at the top. 14 Figure 3-49: 15. Change vol1 to vol2, then click Enter. 38

39 15 Figure 3-50: 16. Drag Example File from the desktop to the vol2 share window. Figure 3-51: 17. The file will be copied to the new share on the new volume. 17 Figure 3-52: 3.4 Create a New Policy for the Newly Created Volume If not logged in already, log into SnapCenter as demo\scadmin with password Netapp1!. On the left-hand navigation bar click Settings. Click on Policies at the top. Select the Backup to Vault policy.

40 5. Click the Copy button to make a copy of the Backup to Vault policy Figure 3-53: 6. In the Copy Policy dialog box accept the proposed name, and click OK. 6 Figure 3-54: 7. Click the newly created Backup to Vault Copy policy, and click the Modify button. 7 Figure 3-55: 8. On the Provide a policy name screen, accept the default and click Next. 40

41 8 Figure 3-56: 9. Review the retention settings. 9 Figure 3-57: 41

42 10. Click the Hourly field for the local copies, and scroll down to review the retention settings for local backups. 10 Figure 3-58: 11. Click the Daily field for the Vault copies. SnapCenter uses SLO based data protection which is created based on these policies. When selecting on a secondary storage system you will also be prompted to make selections on the secondary configuration, as SnapCenter will create the necessary secondary relationships and protection policies. 42

43 11 Figure 3-59: 12. Under Vault Configuration click the drop-down for the Choose Storage Cluster field, and select cluster2.demo.netapp.com. 13. Click Next. 43

44 12 13 Figure 3-60: 14. On the Summary screen click Finish. 14 Figure 3-61: 44

45 3.4 Protect the New Volume with the New Policy 1. If not logged in already, log into SnapCenter as demo\scadmin with password Netapp1!. 2. On the left-hand navigation bar click Resources. 3. Click the Refresh Resources button. 3 2 Figure 3-62: 4. You should now see the newly created vol2 volume. 5. Click the Backup to Vault Copy policy at the lower right. 6. Add the vol2 volume to the policy by either clicking on the + sign at the lower right of the vol2 volume tile, or click and drag the vol2 tile to the policy. 6 5 Figure 3-63: 45

46 7. If desired, click the Details button on the lower left of the Backup to Vault Copy policy to review details. If you scroll the details window down to the bottom, you will notice you can choose to have an notification sent, and to run the initial backup at a specific time or immediately. 8. Click the Create Backup button to execute a backup. 8 7 Figure 3-64: 9. The activity bar at the bottom will list the status. 9 Figure 3-65: 10. On the left-hand navigation bar, click Monitor and verify the job Applying Protection completed successfully. This may take several minutes to complete. 10 Figure 3-66: 11. On the left-hand navigation bar, click Resources, and verify that vol2 is now showing a protected status. 46

47 11 Figure 3-67: 3.5 Browse and Restore a directory of files to their original location In this exercise, you restore a single file when you know the file you are looking for. 1. From the Jumphost desktop, double-click on the vol1 (svm1-cifs.demo.netapp.com) shortcut. Figure 3-68: 2. Select the VMware tools folder and delete it. 47

48 2 Figure 3-69: 3. Click Yes to confirm deletion. 3 Figure 3-70: 4. Return to SnapCenter, login if necessary, and on the left-hand navigation bar click Resources. 5. Click on... at the lower right of vol1 volume tile. and click More actions. 48

49 4 5 Figure 3-71: 6. This will open the protection topology view. 6 Figure 3-72: 7. Click the Cloud backups box to view the backups out on the cloud. 49

50 7 Figure 3-73: 8. Select the latest backup listed below. 9. Click the Restore button. 8 9 Figure 3-74: 10. Click to open \\CIFS\vol1. 10 Figure 3-75: 11. Check the box next to the file VMware Tools folder (scrolling may be required). 50

51 11 Figure 3-76: 12. Observe the Restore to options of the Restore panel. You have the choice of restoring this directory to its original location, or to specify an alternate location. The alternate location (default) must be on the same Storage Virtual Machine (SVM). 13. Click on the Original location option. Note: You also can specify an notification if SMTP has been configured in SnapCenter, but that is not part of this lab. 14. Click Restore at the bottom right (scrolling may be required) Figure 3-77: 51

52 15. You will be given a warning that the restore operation will overwrite any existing file by that name. Click Yes to continue. 15 Figure 3-78: 16. Watch the activity panel, or go to the Job Monitor to view the job status from the Monitor page. 16 Figure 3-79: 17. Monitor the status for job completion. 52

53 17 Figure 3-80: 18. Once the job is complete, return to Windows Explorer on the Jumphost desktop, and you will see that the directory has been restored. 18 Figure 3-81: 3.6 Search and Restore a File Another likely file restore situation includes when you are not sure of the file name. This exercise takes you through that task. 1. If you are not already logged in, log into SnapCenter as demo\scadmin with password Netapp1!. 2. From the left-hand navigation bar, click Dashboard. 3. Click on Restore Backups. 53

54 2 3 Figure 3-82: 4. In the Share Name field of the Advanced Search panel, enter vol1. 5. Click Apply. 54

55 4 5 Figure 3-83: 6. In the File Types field of the Advanced Search panel, enter.pdf. 7. Click Apply. 55

56 6 7 Figure 3-84: 8. In the File field of the Advanced Search panel, enter Cloud_Appliance. 9. Click Apply. 10. Click on \\CIFS\vol1\DS _Cloud_Appliances.pdf. 56

57 Figure 3-85: 11. Click on the oldest backup to have that file. 12. Drag it to the Drag Here to Restore card Figure 3-86: 13. On the Restore panel verify the Restore to Alternate location option is selected. 14. In the restore path, change vol1 to vol2. 57

58 13 14 Figure 3-87: 15. Click Restore to restore the file from the selected backup. 15 Figure 3-88: 16. When prompted to confirm the restore, click Yes. 58

59 16 Figure 3-89: 17. Watch the activity panel below for the restore job to complete successfully. 18. Click on the Go to Job Monitor button Figure 3-90: 19. Examine the status of the job on the Job Monitor. 59

60 19 Figure 3-91: 20. From the Jumphost, open the Windows Explorer and navigate to vol2 (svm1-cifs.demo.netapp.com) shortcut. 21. Notice that the file DS _Cloud_Appliances.pdf has been restored to the vol2 folder Figure 3-92: 3.7 Change a volume/share from Backup to Vault to Backup to Cloud In this exercise you are going to take a volume that has been protected by a ONTAP to Vault policy and change it to an ONTAP to Cloud policy. Unprotect a volume 1. If not logged in already, log into SnapCenter as demo\scadmin with password Netapp1!. 2. On the left-hand navigation bar click Resources. 3. On the vol2 card, click on Details at the lower left. 60

61 2 3 Figure 3-93: 4. You will see that it is protected by the Backup to Vault Copy policy. 5. Click on... at the lower right of vol2 volume tile, and select Remove protection. 4 5 Figure 3-94: 6. On the Remove Protection dialog box select Delete all Backups. 7. Click Remove Protection. 61

62 6 7 Figure 3-95: 8. On the activity panel below verify the job completed successfully. 8 Figure 3-96: 9. The panel for the vol2 volume will change to the Not Protected status. 62

63 9 Figure 3-97: Protect a volume/share to the cloud 1. On the left-hand navigation bar click Resources. 2. Click to select the Backup to Cloud AltaVault policy. 1 2 Figure 3-98: 3. Add the vol2 volume to the policy by either clicking on the + sign at the lower right of the vol2 volume tile, or click and drag the vol2 tile to the policy. 4. Click the Create Backup button to execute a backup. 63

64 3 4 Figure 3-99: 5. You will see on the shield for vol2 that there is an ongoing activity for that volume. 6. On the left-hand navigation bar, click Monitor, and verify the job Applying Protection completed successfully. 6 5 Figure 3-100: 7. The Monitor page will update with the status. 64

65 7 Figure 3-101: 8. On the left-hand navigation bar, click Resources, and verify that vol2 is now showing a protected status. 8 Figure 3-102: 9. Click on Details, and verify the volume is not protected to the cloud (Backup to Cloud- AltaVault) 65

66 9 Figure 3-103: 3.8 Modifying a Policy In this exercise you will modify the schedule for the volumes being protected by the Backup to Cloud- AltaVault policy. 1. If you are not already logged in, log into SnapCenter as demo\scadmin with password Netapp1!. 2. On the left-hand navigation bar click Settings. 3. Click on Policies. 3 2 Figure 3-104: 4. Click to select the Backup to Cloud- AltaVault policy. 5. Click Modify. 66

67 4 5 Figure 3-105: 6. On the Provide a policy name screen, click Next. 6 Figure 3-106: 7. On the Configure Protection policy screen, click the down arrow for the Daily schedule screen. 67

68 7 Figure 3-107: 8. Click the Clock icon next to the Backup Creation Time field, and change the time from 10:15 to 11:15 pm. 9. Click Next, 68

69 8 9 Figure 3-108: 10. Click Finish. 69

70 10 Figure 3-109: 11. On the left-hand navigation bar click Resources. 12. Click on Details on the lower left of the Backup to Cloud AltaVault policy Figure 3-110: 13. You will see that the daily backup start time has changed. Note: Remember that a change to a policy affects all volumes protected by that policy. While retention and schedules at any tier of a policy may be modified, the destination cannot. 70

71 13 Figure 3-111: 71

72 4 References The following references were used to create this lab guide. Data Fabric Solution for Cloud Backup Workflow Guide Data Fabric Solution for Cloud Backup FAQ (Sales & Technical) SnapCenter FAQ (Sales & Technical) AltaVault Technical FAQ AltaVault Sales Frequently Asked Questions 72

73 5 Version History 73 Version Date Document Version History July 2017 Initial Release

74 Refer to the Interoperability Matrix Tool (IMT) on the NetApp Support site to validate that the exact product and feature versions described in this document are supported for your specific environment. The NetApp IMT defines the product components and versions that can be used to construct configurations that are supported by NetApp. Specific results depend on each customer's installation in accordance with published specifications. NetApp provides no representations or warranties regarding the accuracy, reliability, or serviceability of any information or recommendations provided in this publication, or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS, and the use of this information or the implementation of any recommendations or techniques herein is a customer s responsibility and depends on the customer s ability to evaluate and integrate them into the customer s operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document. Go further, faster 2017NetApp, Inc. All rights reserved. No portions of this document may be reproduced without prior written consent of NetApp, Inc. Specifications are subject to change without notice. NetApp, the NetApp logo, Data ONTAP, ONTAP, OnCommand, SANtricity, FlexPod, SnapCenter, and SolidFire are trademarks or registered trademarks of NetApp, Inc. in the United States and/or other countries. All other brands or products are trademarks or registered trademarks of their respective holders and should be treated as such.