NetApp Cloud Volumes Service for AWS documentation Flashcards

Question

Creating an on-demand snapshot for a cloud volume

Answer 1

You can create an on-demand snapshot of a cloud volume from either the Volumes or Snapshots page.

Answer 2

Click the volume name, select Snapshots, and then click + Create new snapshot. Enter a name for the snapshot, or use the automatically generated name. Select the volume name, and then, from the drop-down list, select the volume for which you want to create a snapshot. Click Create snapshot. The created snapshot appears.

Answer 3

Click + Create new snapshot. Enter a name for the snapshot, or use the automatically generated name. From the drop-down list, select the volume for which you want to create a snapshot. Click Create snapshot. The created snapshot is now listed.

Answer 4

You can create or modify a snapshot policy as necessary for a cloud volume. Steps From the Volumes page, click the volume name, and then select Snapshot policy. Select Hourly, Daily, Weekly, or Monthly to specify the frequency for creating snapshots. Configured policies are marked with a green dot. Undefined policies are marked with a red dot. Select the number of snapshots you want to keep. Select the day, hour, and minute when the snapshot should be taken. If you want to create additional snapshots with different frequencies, for example, both monthly and daily snapshots, repeat steps 2 through 4. Snapshot policy If the Enabled button is not already set to ON, click the button to enable or re-enable the policy. Click Save changes.

Answer 5

You can disable a snapshot policy to stop snapshots from being created for a short period of time while retaining your snapshot policy settings. Steps From the Volumes page, click the volume name, and then select Snapshot policy. Click the Enabled button to OFF to disable snapshots from being created. Snapshot policy Enable button Click Save changes. When you want to re-enable the snapshot policy, click the Enabled button to ON and click Save changes.

Answer 6

You can delete a snapshot from the Volumes or Snapshots page.

Answer 7

Click the volume name, and then select Snapshots to see a list of snapshots for the volume. Specify the snapshots that you want to delete by selecting the corresponding checkboxes, click Actions, and then select Delete snapshot/s from the drop-down list. Alternatively, you can click Available under Actions, then select Delete snapshot from the drop-down list. In the confirmation dialog box, type delete to confirm, and then click Delete.

Answer 8

(Optional) Use the search box to filter the listed snapshots. Specify the snapshots that you want to delete by selecting the corresponding checkboxes, click Actions, and then select Delete snapshot/s from the drop-down list. In the confirmation dialog box, type delete to confirm, and then click Delete.

Answer 9

You can restore a snapshot to a new volume as necessary. Steps On the Snapshots page or in the Snapshots section in Volume details, select the snapshot from which to restore, click Available, and then select Restore to Volume. In the Create Volume dialog box, enter a name for the new volume, and edit other settings if necessary. Creating a cloud volume Review the settings and then click Create volume to finish restoring the snapshot to the new volume.

Answer 10

You can use export policies to restrict NFS access to volumes to clients that match specific parameters. Export policies contain one or more export rules that process each client access request. The result of the process determines whether the client is denied or granted access and what level of access. An export policy with export rules must exist on a Vserver for clients to access data. You associate exactly one export policy with each volume to configure client access to the volume. A Vserver can contain multiple export policies. This enables you to do the following for Vservers with multiple volumes: Assign different export policies to each volume of a Vserver for individual client access control to each volume in the Vserver. Assign the same export policy to multiple volumes of a Vserver for identical client access control without having to create a new export policy for each volume. If a client makes an access request that is not permitted by the applicable export policy, the request fails with a permission-denied message. If a client does not match any rule in the volume's export policy, then access is denied. If an export policy is empty, then all accesses are implicitly denied. You can modify an export policy dynamically on a system running Data ONTAP.

Answer 11

Go to the Sync page or the Sync tab for a volume on the Volumes page. Create a data broker by clicking Create data broker. Provide information for the following fields: Name Provide a name for the data broker. Type Select AWS. Region Select an available region. API key Provide the access key for your AWS account. Secret key Provide the secret key for your AWS account. Keypair Select an available keypair. The keypair will be updated after you enter valid keys. VPC Select the VPC that is connected to your Cloud Volumes account. Subnet Select an available subnet to use for the data broker. Creating a Cloud Sync data broker Click Create data broker to start the data broker creation process. It takes a few minutes to create a data broker. After the data broker is created, it is marked with a green dot to indicate that it is ready.

Answer 12

A Cloud Sync relationship enables you to sync data to or from the cloud volume. Before you begin You must already have a Cloud Sync data broker. Creating a Cloud Sync data broker The data broker IP address must have been added to the export policy for both the source and the target volumes. The export policy on the target volume must allow write access to the data broker. Creating additional export policy rules About this task The Cloud Sync functionality that is integrated with Cloud Volumes Service currently supports only NFSv3. If you want to sync between SMB volumes, you use the Cloud Sync Service directly (cloudsync.netapp.com). Steps Go to the Sync page or the Sync tab for a volume on the Volumes page. Create a Cloud Sync relationship by clicking Create new relationship. Take one of the following actions: To sync data to the volume, select Use volume as target. To sync data from the volume, select Use volume as source. Creating a Cloud Sync relationship In the Host field (unpopulated), enter the IP address of the NFS server that you want to sync to or sync from. After a few moments, a list of the available exports is automatically discovered. In the Export field, select one of the available exports. (Optional) Check the Delete files on target when deleted from source box if you want to delete the files on target when they are deleted from source. Click Create relationship. The relationship status is displayed and the file progress fields show the number of files that are copied.

Answer 13

When a Cloud Sync relationship is initially created, auto sync is enabled by default and scheduled to run once a day. You can modify the Cloud Sync schedule as appropriate. Steps Go to the Sync page or the Sync tab for a volume on the Volumes page to see the Cloud Sync relationships. Sync relationships To turn off auto sync for a Cloud Sync relationship, click the blue ON slider for the relationship. Auto sync slider To change the sync schedule, click the drop-down list under Schedule, select Day/s or Hour/s, select an interval number, and then click the checkmark. Modifying the Cloud Sync schedule To start Cloud Sync immediately, click Done under Action, select Sync Now, and click Sync Now again to confirm.

Answer 14

You can delete a Cloud Sync relationship that is no longer needed. Steps Go to the Sync page or the Sync tab for a volume on the Volumes page. Click the box for the relationship you want to delete, click Actions, and then select Delete relationship/s. In the confirmation dialog box, type delete to confirm, and then click Delete.

Answer 15

You can delete a Cloud Sync data broker that is no longer needed. About this task This task removes the data broker from cloud volumes, but it does not delete the data broker instance in AWS. To delete the data broker instance in AWS, you must go to the AWS console for your account, locate the EC2 instance for the broker by name, and then terminate it as needed. Before you begin All Cloud Sync relationships that use the data broker must have already been deleted before you can delete the data broker. Deleting a Cloud Sync Relationship Steps Go to the Sync page or the Sync tab for a volume on the Volumes page. Delete a data broker by clicking the data broker’s name and click the trash can icon. In the confirmation dialog box, type delete to confirm, and then click Delete.

Answer 16

02/14/2019 Contributors netapp-juliec You can back up NFS cloud volumes by using Cloud Backup Service. Cloud Backup Service expands the data protection capabilities of Cloud Volumes Service by delivering dedicated backups for long-term recovery, archive, and compliance. Backups created by the service are stored in AWS S3 object storage, independent of cloud volume snapshots that are available for near-term recovery or cloning. Cloud Backup Service is currently in a beta release and supports only Cloud Volumes Service in the AWS US-WEST-2 region. Before using Cloud Backup Service, you must understand and accept the terms, requirements, and considerations for using the beta software. See Setting Up Cloud Backup Service for NetApp Cloud Volumes Service for AWS for details and instructions about using the service.

Answer 17

The cost for Cloud Volumes Service for AWS is based on the service level and the allocated capacity that you select. Selecting the appropriate service level and capacity helps you meet your storage needs at the lowest cost. All pricing information in this article is based on the list prices as of September 12, 2018. The information is provided for example purposes only and is subject to change.

Answer 18

The service levels are catered to different storage capacity and storage bandwidth needs: Standard (capacity) If you want capacity at the lowest cost, and your bandwidth needs are limited, then the Standard service level might be most appropriate for you. An example is using the volume as a backup target. List Price: $0.10 per GB per month (as of September 12, 2018) Bandwidth: 16 KB of bandwidth per GB provisioned capacity Premium (a balance of capacity and performance) If your application has a balanced need for storage capacity and bandwidth, then the Premium service level might be most appropriate for you. This level is less expensive per MB/s than the Standard service level, and it is also less expensive per GB of storage capacity than the Extreme service level. List Price: $0.20 per GB per month (as of September 12, 2018) Bandwidth: 64 KB of bandwidth per GB provisioned capacity Extreme (performance) The Extreme service level is least expensive in terms of storage bandwidth. If your application demands storage bandwidth without the associated demand for lots of storage capacity, then the Extreme service level might be most appropriate for you. List Price: $0.30 per GB per month (as of September 12, 2018) Bandwidth: 128 KB of bandwidth per GB provisioned capacity

Answer 19

You specify your allocated capacity for the volume when you create or modify the volume. Creating cloud volumes Modifying cloud volumes While you would select your service level based on your general, high-level business needs, you should select your allocated capacity size based on the specific needs of applications, for example: How much storage space the applications need How much storage bandwidth per second the applications or the users require Allocated capacity is specified in GBs. A volume’s allocated capacity can be set within the range of 100 GB to 100,000 GB (equivalent to 100 TBs).

Answer 20

The combination of both the service level and the allocated capacity you select determines the maximum bandwidth for the volume. If your applications or users need more bandwidth than your selections, you can change the service level or increase the allocated capacity. The changes do not disrupt data access.

Answer 21

To select the most appropriate service level and allocated capacity for your needs, you need to know how much capacity and bandwidth you require at the peak or the edge.