Data Fabric Solution for Cloud Backup. February 2017 SL10316 Version 1.0.1

February 2017 SL10316 Version 1.0.1

1 Introduction This lab demonstrates the NetApp. This is a new solution that combines the use of multiple NetApp products to offer a hybrid cloud backup solution. This product combines ONTAP 9.1, AltaVault 4.3 and SnapCenter 2.0 into a solution that allows customers to backup and restore CIFS or NFS shares with a file catalog. 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 this solution include: Provides an efficient, end-to-end file-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, storage administrators and IT generalists can perform Snapshot copy-based data protection operations for Windows and UNIX file shares to and from public or private cloud object stores. Delivering high service levels with fast Snapshot copies and efficient array-based replication, this solution includes NetApp ONTAP, SnapCenter data management software, and AltaVault cloud-integrated storage software. 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 is intended to provide backup functionality for customers that are using ONTAP. This first release of the solution focuses on providing backup of NAS file services. The solution offers two replication topology types that are defined by the supported cascade relationships as shown in the following figure. The first topology is ONTAP, running on FAS or AFF, replicating using SnapMirror directly to AltaVault. The second topology is ONTAP replicating using SnapMirror to a disaster recovery FAS appliance, then to an AltaVault. These two supported topologies are available in SnapCenter as protection policies. The protection policies are pre-defined in SnapCenter. Using these basic topologies, more complex configurations can be implemented using fan-in from one or more ONTAP appliances into a single AltaVault appliance. 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. 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. 2

Figure 1-1: The required configurations for this solution are as follows: SnapCenter Storage ONTAP 9.1 Cluster AltaVault ONTAP 9.1 Cluster Configure CIFS Servers Backup policy AltaVault Cloud storage StorageGRID Webscale SnapMirror configuration SnapCenter user role Replication report Front end report ONTAP System Manager Protection relationships Protection Snapshot Policies Protection Schedules Licenses Network interfaces SVM overview SVM volumes SVM shares 1 Prerequisites 3 Basic understanding of NetApp SnapMirror technology.

Basic understanding of SnapCenter see the SnapCenter lab. Basic understanding of AltaVault see the AltaVault lab. 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

2 Lab Environment Figure 2-1: Figure 2-2: Table 1: Table of Systems 5 Host Name Operating System Role/Function IP Address cluster1 ONTAP 9.1 cluster 192.168.0.101 cluster1-01 ONTAP 9.1 cluster 1 node 1 192.168.0.111 cluster1-02 ONTAP 9.1 cluster 1 node 2 192.168.0.112 svm1 Storage Virtual Machine for VMware datastore on NFS SVM mgmt lif 192.168.0.130 jumphost Windows Server 2012 R2 primary desktop entry point for lab 192.168.0.5 dc1 Windows Server 2008 R2 Active Directory / DNS 192.168.0.253 snapcenter Windows Server 2012 R2 NetApp SnapCenter 2.0 192.168.0.74

Host Name Operating System Role/Function IP Address index1 RedHat Enterprise Linux 7 Index server for SnapCenter 192.168.0.61 altavault AVA-V virtual appliance 192.168.0.75 sgntp SUSE Linux Enterprise 10 Network Time Protocol SP3 server for SGWS 192.168.0.9 sgdc1s3 SUSE Linux Enterprise 11 StorageGRID Webscale 10.3 Storage Node 3 192.168.0.8 sgdc1s2 SUSE Linux Enterprise 11 StorageGRID Webscale 10.3 Storage Node 2 192.168.0.7 sgdc1s1 SUSE Linux Enterprise 11 StorageGRID Webscale 10.3 Storage Node 1 192.168.0.6 sgdc1g1 SUSE Linux Enterprise 11 StorageGRID Webscale 10.3 Gateway Node 192.168.0.11 sgdc1arc1 SUSE Linux Enterprise 11 StorageGRID Webscale 10.3 Archive Node 192.168.0.12 sgdc1adm1 SUSE Linux Enterprise 11 StorageGRID Webscale 10.3 Admin Node 192.168.0.10 NetApp AltaVault 4.3 2 User IDs and Passwords 6 Host Name User ID Password Comments jumphost DEMO\Administrator Netapp1! Domain Administrator cluster1 admin Netapp1! Same for individual cluster nodes svm1 vsadmin Netapp1! svm administrator rhel root Netapp1! 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

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 7 Connect to SnapCenter and Review Configuration on page 12 Connect to AltaVault and Review Configuration on page 19 Provision and Protect a new Volume/share using OnCommand System Manager on page 33 Browse and Restore a Known File on page 44 Search and Restore a File on page 49 3.1 Use SnapCenter to Backup a Volume to Cloud In the 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. If you are not already logged into SnapCenter, login as demo\administrator, with password Netapp1!. 2. From the left hand navigation bar, go to the Resources page. Note: 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 cards are available to protect. 2 Figure 3-1: 3. Click on the Backup to Cloud AltaVault policy. 7

3 Figure 3-2: 4. To protect the vol1 volume, either click on the + sign in the lower right of the volume tile, or click the whole tile and drag it to the policy. 4 Figure 3-3: 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 X in the lower right of the volume tile which will remove it from this job. When vol1 is added, the volume becomes highlighted, the policy it is added to is 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. 8

You also have the ability to drag a volume to the policy you want to assign it to. Figure 3-4: Note: Remember that once a volume has been protected under a policy it cannot be unprotected or moved to a different policy. A volume can be assigned to exactly one backup policy. 5. Click the Create Backup button to start the backup. 5 Figure 3-5: 6. At the bottom of the screen you will see the protection job starting. 9

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

8 9 10 Figure 3-8: 11. From the left hand navigation bar, go to the Resources page. You will now see that vol1 is now showing Protected. 11 Figure 3-9: The operations that are performed are as follows: 11 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. The volume s file structure is traversed with indexing details collected about the contents. The backup (snapshot) is registered with the index server, including the file contents of the volume. When the snapshot finishes copying to SGWS, the AltaVault will mark the operation as complete in the Replication Report. 3.2 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 activity will serve 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). 2. Enter the login credentials - username: demo\administrator, password: Netapp1!. Note: If a user is assigned multiple roles, a selection box is displayed on the login screen that allows the user a choice of roles. 2 Figure 3-10: 3. On the Dashboard screen, point out SnapCenter Plug-in for NAS File Services in the plug-in drop-down selection. 3 Figure 3-11: 12

4. On the left-hand navigation bar select Storage Systems. Notice that there are two storage connections set up; one for the cluster, and the other for the AltaVault system. 4 Figure 3-12: 5. Select the cluster, and click on the Modify button to view the details of the connection. 5 Figure 3-13: 6. Note (but do not change) the following on the Modify Storage Connection screen. The credentials entered must have cluster level permissions. 7. Storage type must be set to ONTAP Cluster. 8. There is a site field for categorization that can be based on user preference (geography, business unit, etc.). 9. Port and timeout can be customized. 10. In the case where there are multiple IP addresses, a preferred address may be specified. 11. Click on the X at the upper right (or press Cancel) of the Modify Storage Connection screen to close the dialog box. 13

11 6 7 Figure 3-14: The Storage System name is also the DNS address used. The User name is the cluster administrator. Site is filled in when the storage is added, and allows an administrator to identify storage ONTAP Cluster is the storage type. There is an ONTAP SVM storage type, but it is not used for the (DFSfCB). 12. Now view the Altavault Storage Connection settings by repeating the same steps of highlighting altavault, and pressing Modify, but do not change anything. The settings are: The Storage System name is also the DNS address used. The User name is the user role that was specifically created for SnapCenter on the AltaVault. Site is filled in when the storage is added, and allows an administrator to identify storage. The Protocol and Port are the default settings. 13. Press Cancel (or press X) to close the window. 14

13 Figure 3-15: 14. Ensure that the cluster connection is selected (not Altavault), 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. 14 Figure 3-16: 15. On the Configure CIFS Servers screen, click the RunAs dropdown box, select cifs for the RunAs account, and click OK. 15

15 Figure 3-17: Note: The Run As name is a name assigned to the credentials. The User name is the domain user with permissions to list or backup the files. The User name is specified as domain\user or user@domain.com. 16. On the left-hand navigation bar select Settings, then if necessary click on Policies at the top. The two policies indicated by arrows are the canned policies provided for each of the two supported topologies. Backup to Cloud for FAS/AFF to AltaVault. Backup to Vault to Cloud for FAS/AFF to FAS to AltaVault. 16 Figure 3-18: These policies can be copied then customized for specific protection needs. This process will be covered in a later task. Note that there is already one copied and modified for use (Backup to Cloud Altavault). 17. Click on Resources. Review volume layout and details. On each of the volumes displayed, note the following: 1. 2. The size of the volume (not the amount used). There is a shield on the upper right of each volume tile. The color has the following meaning: 16 Green This volume is protected (at this point there are none). Gray This volume is unprotected. Red This volume is unprotected and not capable of being protected. In this case because it is vol0.

17 Figure 3-19: 18. Click the down arrow on vol1 to get more details. The details show the volume status, the storage system, Shares, tags (covered later) and the policy to which the volume is attached. In this case since the status is unprotected, there is no policy attached. 18 Figure 3-20: 3.2 Review the Existing Backup Policy A backup policy defines the destinations used in the protection of a volume, as well as the retentions used. The schedule is defined in the source ONTAP cluster. 17

1. 2. 3. 4. Click on Settings. If needed, click on Policies. Click on the policy named Backup to Cloud AltaVault, to highlight it in the table Click on the details icon view the policy. 2 4 1 3 Figure 3-21: When SnapCenter is deployed, two default policy templates are provided. One is for backup directly from ONTAP to AltaVault, and the other is to create a cascade where the first ONTAP cluster uses SnapMirror to replicate data to a second ONTAP cluster, then from the second ONTAP cluster 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. 5. Review the details for this backup policy. 18

5 Figure 3-22: 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. 3.3 Connect to AltaVault and Review Configuration 3.3 AltaVault Configuration Review 1. Login to the AltaVault UI using the browser on the Jumphost. The username is admin, and the password is Netapp1!. 19

1 Figure 3-23: 2. 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 you login 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, email notifications, or AutoSupport. 2 Figure 3-24: 20

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. To review the Cloud Storage settings (StorageGRID WebScale), click on the Configure menu, and select Cloud Settings. 3 Figure 3-25: 4. Review the cloud settings for StorageGRID Webscale. 21

Figure 3-26: 5. Click the Configure menu, and select SnapMirror. 22

5 Figure 3-27: 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 is able to connect and validate access, the home page will give a green status showing it is ready for the share to be configured. To prepare an AltaVault appliance for a SnapMirror backup using SnapCenter for this solution, there are a few steps that are done on the AltaVault appliance. 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. 6. View that SnapMirror has been enabled. 23

6 Figure 3-28: 7. Scroll the window to view the Whitelist that contains the IP addresses for the Intercluster LIFs of the ONTAP cluster (cluster1). 7 Figure 3-29: 8. Scroll the window to view the two remaining settings. 24

8 Figure 3-30: 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 recomend 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. 9. You must create a user role before SnapCenter can access an AltaVault appliance. Using the AltaVault admin account is not permitted. Click on the Configure menu, and select User Permissions. 25

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

10 Figure 3-32: 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. 11 Figure 3-33: 27

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: General Settings Replication Settings Storage Settings 3.3 AltaVault Reports Review AltaVault has a rich set of graphic reports. These reports are very helpful in determining how cloud storage and SnapMirror are used in the solution. From the AltaVault view, data is read and written by DataONTAP using SnapMirror or a backup application using SMB (CIFS), NFS or OST. The data transfer is referred to as front-end traffic, meaning from the backup source. The AltaVault refers to the appliance network ports that are used for this traffic as data interfaces. Data interfaces on the AltaVault can be assigned to VLANs, or combined into bonded interfaces called virutal interfaces (VIFs). Replication to cloud (object) storage is referred to as back-end traffic. Accordingly, you will see a front-end throughput report and a back-end throughput report. These are for traffic to the backup source and traffic to the cloud storage destination. It is also important to understand that all data is written to the cloud storage destination. This is important as that is the long-term offsite storage from which a disaster recovery of an AltaVault appliance could be performed at any point in time. 1. Click the Reports menu, and click Replication. 1 Figure 3-34: 28

2. On the right side is a legend that shows the time period being viewed. There are quick access links for 5 minutes, 1 hour, 1 day, 1 week, or all. There is a smaller graph at the bottom that can be dragged to select specific time periods to view. In the legend, an overall metric is displayed to show the performance over the time being viewed. If you hover the mouse over the line on the graph, it will display a bubble that includes specific details of that point in time on the graph. All of the main AltaVault reports offer this overall functionality. The Replication report shows the total data that is pending replication to cloud (object) storage. This is an important report on the AltaVault, as it indicates any data that has not been written to cloud as well as a cloud synchronization date and time. When you create a SnapMirror relationship Data ONTAP sends large amounts of data. This causes the AtlaVault replication times to appear to take longer, so the job status lists as pending because all the data is unique. But after the initial baseline relationship copy is done, replication goes faster because Data ONTAP only sends small changes to the data. At this point, replication reports in AltaVault go much quicker. It is also possible to set schedules for the replication service where during peak network times the replication is limited, or paused based on a schedule. See the Cloud Settings page, and Replication and Bandwidth tabs for these settings. Figure 3-35: 3. Click the Reports menu, and click Front-End Throughput. 29

3 Figure 3-36: 4. The front-end throughput report shows the total data being read or written by a backup application, or SnapMirror, to the AltaVault appliance. In this lab, it shows the data that was sent by SnapMirror when you created the initial baseline transfer after clicking Create Backup in SnapCenter for vol1. Figure 3-37: 5. Continue to review the additional reports. 30

Since this is a lab with a small amount of data transfer, the reports do not show significantly large numbers for throughput, optimization, and other statistics. A POC or production appliance would show better statistics. These statistics are displayed as a simple example of where to view production appliances. 3.3 Review Data ONTAP Data Protection Relationship and Network Interfaces in OnCommand System Manager 1. Launch IE using the OnCommand System Manager shortcut on the desktop. 2. Accept the security warning about the self-signed certificate. 2 Figure 3-38: 3. Login to System Manager with username admin, and password Netapp1!. Figure 3-39: 4. 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. 31

Figure 3-40: 5. 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). Figure 3-41: 6. Click Network from the top menu. 7. Click the Network Interfaces tab to view the configured network interfaces. 32

Figure 3-42: The left column is the name of the logical interface (LIF) Important interfaces for management are the cluster_mgmt LIF, which is used to access System Manager as well as 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 will be used for SnapMirror protocol to send data to AltaVault. The LIF role must be Intercluster, and is a dedicated LIF. 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 (double click the desktop shortcut). 2. Enter the login credentials - username: admin, password: Netapp1!. 3. Click on SVMs, then click to select svm1. 3 Figure 3-43: 4. Click on Volumes. 33

4 Figure 3-44: 5. Click the Create button to create a new volume. 5 Figure 3-45: 6. In the Create Volume wizard, use the following parameters illustrated in the screen below, then click Create. 6 Figure 3-46: 7. 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. If you click on vol1 you will see that there is a relationship established in a previous exercise. 34

7 Figure 3-47: 8. With svm1 still selected, click Share. 8 Figure 3-48: 9. Click Create Shares. 9 Figure 3-49: 10. In the Create Share dialog box, set the parameters as shown, and click Create. 35

10 Figure 3-50: 11. From the Jumphost desktop, double-click on the vol1 (svm1-cifs.demo.netapp.com) shortcut. 11 Figure 3-51: 12. Click in the address box at the top, and change vol1 to vol2, then press Enter. 36

12 Figure 3-52: 13. Drag Example File from the desktop to the vol2 share window. 13 Figure 3-53: 37

3.4 Create a New Policy for the Newly Created Volume 1. If not already, log into SnapCenter as demo\administrator with password Netapp1!. 2. On the left-hand navigation bar select Settings, then if necessary, click on Policies at the top. Click to select the Backup to Cloud policy. 2 Figure 3-54: 3. Click the Copy button to make a copy of the Backup to Cloud policy. 3 Figure 3-55: 4. In the Copy Policy dialog box accept the proposed name, and click OK. 4 Figure 3-56: 5. Select the newly created Backup to Cloud Copy policy, and click the Modify button. 38

5 Figure 3-57: 6. On the Provide a policy name screen, accept the default and click Next. 6 Figure 3-58: 7. Review the retention settings. 39

7 Figure 3-59: 8. Click the Hourly field of the topology, and scroll down to review the retention settings for local backups. 8 Figure 3-60: 9. Click the Daily field of the Cloud copies, and scroll down to review the retention settings for cloud backups. 10. Click Next. 40

9 10 Figure 3-61: 11. On the Summary screen click Finish. 12. On the left hand navigation bar, go to the Monitor page, and verify the job Update Policy 'Backup to Cloud Copy' completed successfully. 12 Figure 3-62: 3.4 Protect the New Volume with the New Policy 1. If you are not already, log into SnapCenter as demo\administrator with password Netapp1!. 2. On the left-hand navigation bar select Resources, then click the Refresh Resources button. 3. You should now see the Backup to Cloud Copy policy at the lower right. Click to select the policy. 41

Figure 3-63: 4. 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. 5. If desired, click the down arrow on the lower left of the Backup to Cloud Copy policy to review details. Figure 3-64: 6. Click the Create Backupbutton to execute a backup. 42

Figure 3-65: 7. On the left-hand navigation bar, go to the Monitor page and verify the job Applying Protection completed successfully. Figure 3-66: 8. On the left hand navigation bar, go to the Resource page, and verify that vol2 is now showing a protected status. 43

Figure 3-67: 3.5 Browse and Restore a Known File In this exercise, we are going to restore a single file when we know the file we are looking for. 1. From the Jumphost desktop, double-click on the vol1 (svm1-cifs.demo.netapp.com) shortcut. 1 Figure 3-68: 2. Click in the address box at the top, and change vol1 to vol2, then press Enter. 2 Figure 3-69: 3. Open the vol2 folder and delete the example file. 44

3 Figure 3-70: 4. Return to SnapCenter, login if necessary, and on the left hand navigation bar click to select Resources. 5. Click on Actions on the vol2 volume tile. 4 5 Figure 3-71: 6. This will open the protection topology view. 45

Figure 3-72: 7. Click the cloud backups box to view the backups out on the cloud. 7 Figure 3-73: 8. Click to select the single backup listed below, then click the eye icon "Browse" button. 8 Figure 3-74: 9. Click to open \\CIFS\vol2. 46

9 Figure 3-75: 10. Check the box next to the file Example File.txt. Observe the restore location for the file. This is the original location that the file was backed up from. The functionality to rename or restore to an alternate location is not yet available. 11. Click Restore at the bottom right (scrolling may be required). 10 11 Figure 3-76: 12. You will be warned that this restore operation will overwrite any existing file by that name. Click Yes to continue. 47

12 Figure 3-77: 13. Watch the activity panel or go to the the Job Monitor to view the job status from the Monitor page. 13 Figure 3-78: 14. If you return to Windows explorer on the Jumphost desktop you will see that the file has been restored. 14 Figure 3-79: 48

3.6 Search and Restore a File Another likely situation in restoring a file is when we are not exactly sure of the name of the file. This exercise will take us through this task. 1. If you are not already, log into SnapCenter as demo\administrator with password Netapp1!. 2. From the left hand navigation bar, go to the Dashboard page. 2 Figure 3-80: 3. Click on Restore Backups. 3 Figure 3-81: 4. In the Share Name field of the Filters panel, on the right enter vol1. 5. Click Apply. 49

4 5 Figure 3-82: 6. In the File Types field of the Filters panel enter.pdf. 6 Figure 3-83: 7. Click on \\CIFS\vol1\White Paper - SteelStore Technology Overview Guide 3.2.pdf. 50

7 Figure 3-84: 8. Click on the last (oldest) backup to have that file, and drag it to the Drag Here to Restore tile. 8 Figure 3-85: 9. Click Restore at the lower right to restore the file from the selected backup. 51

9 Figure 3-86: 10. When prompted to confirm the restore click Yes. 11. Watch the activity panel below for the restore job to complete successfully. 11 Figure 3-87: 52

4 References The following references were used to create this lab guide. Workflow Guide https://library.netapp.com/ecm/ecm_download_file/ecmlp2590889 FAQ (Sales & Technical) https://fieldportal.netapp.com/content/476103 SnapCenter FAQ (Sales & Technical) https://fieldportal.netapp.com/content/262140 AltaVault Technical FAQ https://fieldportal.netapp.com/content/209092 AltaVault Sales Frequently Asked Questions https://fieldportal.netapp.com/content/362361 53

5 Version History 54 Version Date Document Version History 1.0.0 February 2017 Initial Release 1.0.1 February 2017 added credentials for SGWS

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.