Skip to main content
Cloud Manager 3.8
A newer release of this product is available.

Managing existing storage

Contributors netapp-bcammett
PDFs

Cloud Manager enables you to manage volumes, aggregates, and CIFS servers. It also prompts you to move volumes to avoid capacity issues.

Managing existing volumes

You can manage existing volumes as your storage needs change. You can view, edit, clone, restore, and delete volumes.

Steps

  1. On the Working Environments page, double-click the Cloud Volumes ONTAP working environment on which you want to manage volumes.

  2. Manage your volumes:

    Task Action

    View information about a volume

    Select a volume, and then click Info.

    Edit a volume (read-write volumes only)

    1. Select a volume, and then click Edit.

    2. Modify the volume's Snapshot policy, NFS protocol version, NFS access control list, or share permissions, and then click Update.

    Note If you need custom Snapshot policies, you can create them by using System Manager.

    Clone a volume

    1. Select a volume, and then click Clone.

    2. Modify the clone name as needed, and then click Clone.

    This process creates a FlexClone volume. A FlexClone volume is a writable, point-in-time copy that is space-efficient because it uses a small amount of space for metadata, and then only consumes additional space as data is changed or added.

    To learn more about FlexClone volumes, see the ONTAP 9 Logical Storage Management Guide.

    Restore data from a Snapshot copy to a new volume

    1. Select a volume, and then click Restore from Snapshot copy.

    2. Select a Snapshot copy, enter a name for the new volume, and then click Restore.

    Create a Snapshot copy on demand

    1. Select a volume, and then click Create a Snapshot copy.

    2. Change the name, if needed, and then click Create.

    Get the NFS mount command

    1. Select a volume, and then click Mount Command.

    2. Click Copy.

    View the target iQN for an iSCSI volume

    1. Select a volume, and then click Target iQN.

    2. Click Copy.

    3. Use the IQN to connect to the LUN from your hosts.

    Change the underlying disk type

    1. Select a volume, and then click Change Disk Type & Tiering Policy.

    2. Select the disk type, and then click Change.

    Note Cloud Manager moves the volume to an existing aggregate that uses the selected disk type or it creates a new aggregate for the volume.

    Change the tiering policy

    1. Select a volume, and then click Change Disk Type & Tiering Policy.

    2. Click Edit Policy.

    3. Select a different policy and click Change.

    Note Cloud Manager moves the volume to an existing aggregate that uses the selected disk type with tiering, or it creates a new aggregate for the volume.

    Delete a volume

    1. Select a volume, and then click Delete.

    2. Click Delete again to confirm.

Managing existing aggregates

Manage aggregates yourself by adding disks, viewing information about the aggregates, and by deleting them.

Before you begin

If you want to delete an aggregate, you must have first deleted the volumes in the aggregate.

About this task

If an aggregate is running out of space, you can move volumes to another aggregate by using OnCommand System Manager.

Steps

  1. On the Working Environments page, double-click the Cloud Volumes ONTAP working environment on which you want to manage aggregates.

  2. Click the menu icon and then click Advanced > Advanced allocation.

  3. Manage your aggregates:

    Task Action

    View information about an aggregate

    Select an aggregate and click Info.

    Create a volume on a specific aggregate

    Select an aggregate and click Create volume.

    Add disks to an aggregate

    1. Select an aggregate and click Add AWS disks or Add Azure disks.

    2. Select the number of disks that you want to add and click Add.

      Tip All disks in an aggregate must be the same size.

    Delete an aggregate

    1. Select an aggregate that does not contain any volumes and click Delete.

    2. Click Delete again to confirm.

Modifying the CIFS server

If you change your DNS servers or Active Directory domain, you need to modify the CIFS server in Cloud Volumes ONTAP so that it can continue to serve storage to clients.

Steps

  1. From the working environment, click the menu icon and then click Advanced > CIFS setup.

  2. Specify settings for the CIFS server:

    Task Action

    DNS Primary and Secondary IP Address

    The IP addresses of the DNS servers that provide name resolution for the CIFS server.

    The listed DNS servers must contain the service location records (SRV) needed to locate the Active Directory LDAP servers and domain controllers for the domain that the CIFS server will join.

    Active Directory Domain to join

    The FQDN of the Active Directory (AD) domain that you want the CIFS server to join.

    Credentials authorized to join the domain

    The name and password of a Windows account with sufficient privileges to add computers to the specified Organizational Unit (OU) within the AD domain.

    CIFS server NetBIOS name

    A CIFS server name that is unique in the AD domain.

    Organizational Unit

    The organizational unit within the AD domain to associate with the CIFS server. The default is CN=Computers.
    If you configure AWS Managed Microsoft AD as the AD server for Cloud Volumes ONTAP, you should enter OU=Computers,OU=corp in this field.

    DNS Domain

    The DNS domain for the Cloud Volumes ONTAP storage virtual machine (SVM). In most cases, the domain is the same as the AD domain.

    NTP Server

    Select Use Active Directory Domain to configure an NTP server using the Active Directory DNS. If you need to configure an NTP server using a different address, then you should use the API. See the Cloud Manager API Developer Guide for details.

  3. Click Save.

Result

Cloud Volumes ONTAP updates the CIFS server with the changes.

Moving a volume

Move volumes for capacity utilization, improved performance, and to satisfy service-level agreements.

You can move a volume in System Manager by selecting a volume and the destination aggregate, starting the volume move operation, and optionally monitoring the volume move job. When using System Manager, a volume move operation finishes automatically.

Steps

  1. Use System Manager or the CLI to move the volumes to the aggregate.

    In most situations, you can use System Manager to move volumes.

    For instructions, see the ONTAP 9 Volume Move Express Guide.

Moving a volume when Cloud Manager displays an Action Required message

Cloud Manager might display an Action Required message that says moving a volume is necessary to avoid capacity issues, but that it cannot provide recommendations to correct the issue. If this happens, you need to identify how to correct the issue and then move one or more volumes.

Steps

  1. Identify how to correct the issue.

  2. Based on your analysis, move volumes to avoid capacity issues:

Identifying how to correct capacity issues

If Cloud Manager cannot provide recommendations for moving a volume to avoid capacity issues, you must identify the volumes that you need to move and whether you should move them to another aggregate on the same system or to another system.

Steps

  1. View the advanced information in the Action Required message to identify the aggregate that has reached its capacity limit.

    For example, the advanced information should say something similar to the following: Aggregate aggr1 has reached its capacity limit.

  2. Identify one or more volumes to move out of the aggregate:

    1. In the working environment, click the menu icon, and then click Advanced > Advanced allocation.

    2. Select the aggregate, and then click Info.

    3. Expand the list of volumes.

      Screen shot: Shows the list of volumes in an aggregate in the aggregate information dialog box.

    4. Review the size of each volume and choose one or more volumes to move out of the aggregate.

      You should choose volumes that are large enough to free space in the aggregate so that you avoid additional capacity issues in the future.

  3. If the system has not reached the disk limit, you should move the volumes to an existing aggregate or a new aggregate on the same system.

    For details, see Moving volumes to another aggregate to avoid capacity issues.

  4. If the system has reached the disk limit, do any of the following:

    1. Delete any unused volumes.

    2. Rearrange volumes to free space on an aggregate.

      For details, see Moving volumes to another aggregate to avoid capacity issues.

    3. Move two or more volumes to another system that has space.

      For details, see Moving volumes to another system to avoid capacity issues.

Moving volumes to another system to avoid capacity issues

You can move one or more volumes to another Cloud Volumes ONTAP system to avoid capacity issues. You might need to do this if the system reached its disk limit.

About this task

You can follow the steps in this task to correct the following Action Required message:

Moving a volume is necessary to avoid capacity issues; however, Cloud Manager cannot perform this action for you because the system has reached the disk limit.
Steps

  1. Identify a Cloud Volumes ONTAP system that has available capacity, or deploy a new system.

  2. Drag and drop the source working environment on the target working environment to perform a one-time data replication of the volume.

    For details, see Replicating data between systems.

  3. Go to the Replication Status page, and then break the SnapMirror relationship to convert the replicated volume from a data protection volume to a read/write volume.

    For details, see Managing data replication schedules and relationships.

  4. Configure the volume for data access.

    For information about configuring a destination volume for data access, see the ONTAP 9 Volume Disaster Recovery Express Guide.

  5. Delete the original volume.

    For details, see Managing existing volumes.

Moving volumes to another aggregate to avoid capacity issues

You can move one or more volumes to another aggregate to avoid capacity issues.

About this task

You can follow the steps in this task to correct the following Action Required message:

Moving two or more volumes is necessary to avoid capacity issues; however, Cloud Manager cannot perform this action for you.
Steps

  1. Verify whether an existing aggregate has available capacity for the volumes that you need to move:

    1. In the working environment, click the menu icon, and then click Advanced > Advanced allocation.

    2. Select each aggregate, click Info, and then view the available capacity (aggregate capacity minus used aggregate capacity).

      Screen shot: Shows the total aggregate capacity and used aggregate capacity available in the aggregate information dialog box.

  2. If needed, add disks to an existing aggregate:

    1. Select the aggregate, and then click Add disks.

    2. Select the number of disks to add, and then click Add.

  3. If no aggregates have available capacity, create a new aggregate.

    For details, see Creating aggregates.

  4. Use System Manager or the CLI to move the volumes to the aggregate.

  5. In most situations, you can use System Manager to move volumes.

    For instructions, see the ONTAP 9 Volume Move Express Guide.

Reasons why a volume move might perform slowly

Moving a volume might take longer than you expect if any of the following conditions are true for Cloud Volumes ONTAP:

  • The volume is a clone.

  • The volume is a parent of a clone.

  • The source or destination aggregate has a single Throughput Optimized HDD (st1) disk.

  • The Cloud Volumes ONTAP system is in AWS and one aggregate uses an older naming scheme for objects. Both aggregates have to use the same name format.

    An older naming scheme is used if data tiering was enabled on an aggregate in the 9.4 release or earlier.

  • The encryption settings don't match on the source and destination aggregates, or a rekey is in progress.

  • The -tiering-policy option was specified on the volume move to change the tiering policy.

  • The -generate-destination-key option was specified on the volume move.