Volumes

Last modified
<< PrevNext >>

The ‘Volumes’ page located under the ‘Configure’ menu allows you to manage the storage volumes that are provisioned on the appliance for your initiators (servers). 

 

Volumes.png

 

The volumes page is shown below.

Volumes_1.png

 

A volume consists of a series of attributes:

  • Name – a descriptive name that must be unique, which will help you identify the volume more easily.  This name is also used in reports when filtering on a specific volume.
  • Cloud – specifies the cloud configuration that should be used for this volume.
  • Online – specifies whether or not the volume is visible to initiators (servers) that are allowed access to utilize the volume.
  • Capacity – specifies how large the volume is going to be, as perceived by the initiator (server).  Capacity specifies the total amount of data that can be stored by the initiator (server).  Volumes are thinly provisioned, and data is de-duplicated. This implies that your appliance doesn’t pre-allocate physical storage capacity internally or on the cloud according to configured volume capacity, rather, capacity is allocated and consumed on demand.
  • Access Type – specifies how the volume is going to be used, providing a helpful reminder when looking at the volume list.  The access type specifies whether or not initiators (servers) that are allowed to access the volume can only read data from the volume, or if they are able to perform both read and write operations.
  • Application - apprises the user as to which application is going to use the volume. Based on the application that is using a volume, the user can select from a Generic, Exchange Mailbox Server Database, Exchange Mailbox Server Transaction Logs, Exchange Mailbox server Archive Database, SharePoint Database, SharePoint Transaction Logs, SharePoint BLOBS, File Server Volume, Cluster Quorum Volume, Backup Target Volume, Virtual Machine Data and Virtual Machine OS Images.
  • Volume Access Groups – specifies the initiators (servers) that are allowed access to this volume.  Initiators that are not members of a volume access group that is associated with the volume will not see the volume.

 

This page also details the common functions related to  'Volumes'  in the following sections -

Back to Top

Creating a Volume

Perform the following steps to create a volume.
  • To create a volume, click the ‘Create Volume’ link found at the bottom of the tabular list view. 
  • This will open the volume properties page, where you can supply the volume parameters as described above. The user has to specify : General Settings and Security Settings, for a given volume.
General Settings

The 'General Settings' tab on the 'Create Volume' dialog is shown below.

 

Volumes_2.png

 

  • On this tab, specify the following parameters:
    • Provide a 'Name' for your volume. 
    • Under 'Type', specify the application that will be using the volume from the drop-down list. 
    • Select a 'Cloud Configuration' by specifying your Cloud Service Provide from a drop-down list.
    • Specify the 'Access Type' from 'Read-Write', 'Read Only'
    • Assign a 'Capacity' to the volume that you wish to create. Note that the capacity of the volume must be between 1 and 102,400GB, and that a cloud account must be selected. 
    • By default, the 'Online' field is checked. This field should be unchecked if the volume needs to be taken offline while the user is trying to delete a volume group or an associated volume.
    • Click the checkbox next to ‘Enable Monitoring’ if you wish to have reports that show data only from statistics collected against this individual volume. With this setting enabled, your appliance will collect statistics specific to this volume, allowing you to filter volume-related reports down to this individual volume.  Only 30 objects can be configured for ‘enabled monitoring’, including both volumes and cloud accounts.  Should you exceed this number, your appliance will not allow you to enable monitoring on another object until it is disabled on one where it is already configured.

 

Note.png Note: Clone Volumes that have been imported from DPC do not have monitoring enabled by default. To see the statistics specific to this volume in reports, the user has to enable monitoring prior to using these.

 

  • Check the 'Daily Cloud Snapshot' field if you wish to create a volume group and an associated policy that would execute daily and result in a Cloud Snapshot of all your data. Checking this field automatically creates a volume group '<volume>' and an associated Cloud Snapshot policy named  ‘<volume>-Auto-Daily-CloudSnapshot’.  This daily policy is enabled by default and executes beginning 10 minutes after the creation of the volume. This policy retains upto seven backups and is set never to expire. The 'Daily CloudSnapshot' option is not available during editing of the volume properties. It is available only when the volume is created. Deletion of the volume will require manual deletion of the associated policies and groups.
Security Settings

When you have finished specifying general settings, click the ‘Security’ tab to assign volume access groups, as shown below.

 

 Volumes_3.png

 

Adding a volume access group to the volume properties will explicitly allow any initiator (server) that matches the volume access group configuration to have access to this volume.  If you do not add a volume access group to the properties of a volume, no initiators will have access to the volume.

 

Perform the following steps to create a new volume access group.

  • Click the ‘Add New Record’ link at the bottom of the tabular list view of volume access groups. The display will change into editing mode, as shown below.

 

Volumes_4.png

  

  • Choose the volume access group you wish to assign to this volume from the drop-down list in the ‘Volume Access Group’ column.  If you do not have a volume access group configured, please visit the Configure > Security Settings > Volume Access Groups page to do so. 
  • Choose a ‘Preferred LUN’ or leave it set to ‘No Preference’.  This setting is helpful when you wish to have your appliance try to provide this volume to the initiators in the volume access group using a specific Logical Unit Number (LUN).  If this LUN is unavailable, your appliance will use a different number.  However, if this LUN is available, your appliance will use the configured value.
  • To save the volume access group entry, click the check icon  within the row that you are editing.  When you have finished adding volume access groups, click ‘Save’ to save the volume.

Note.png Note: Clicking ‘Save’ will only save changes in rows where you have clicked the check icon. Be sure to click the check icon to save the row changes or the ‘delete’ icon to discard row changes prior to clicking ‘Save’.

Back to Top

Editing a Volume

To edit a volume that has already been configured, click the ‘Edit’ icon found on the left side of the tabular list on the same row as the volume you wish to edit.  This will display the volume properties pages as shown above.  All volume properties can be changed, aside from the cloud account associated with the volume.  Should you wish to move the data from one cloud account to another, you will need to create a separate volume, and use RAID-1 on the initiator between the two volumes, or another data migration tool.

Click the ‘Save’ button when you have finished making any changes you wish to make, or ‘Cancel’ to discard the changes.

Back to Top

Deleting a Volume

Deleting a volume destroys its data.  Use this operation only when you either no longer need the data or when you have an independent copy of the data elsewhere.

Volume deletion can be different depending upon whether the volume in question has an associated backup.

Deleting volumes with no associated Backups

Perform the following steps to delete a volume that has no backups associated with it. This will include the volumes created with 'Daily Cloud Snapshot' enabled but being deleted in under 10 minutes from the time of creation as there will be no associated backups. Note that the 'Daily Cloud Snapshot' policy will execute beginning 10 minutes after the creation of the volume. 

  • Volumes can be deleted only if they are taken offline.  To take a volume offline, edit the volume properties and uncheck the box next to “Online”, and click ‘Save’. 
  • In the volume list view, click the ‘delete’ icon  on the left side of the row containing the volume you wish to delete. 
  • Your appliance will prompt you for confirmation, requiring you to type in the word ‘CONFIRM’. 

 

Volumes_5.png

 

  • The user can now delete the volume.
  • After the user confirms the deletion of a volume, a pop-up is presented to the user. The user is advised to manually delete all the associated volume groups and backups after the volume is deleted.
Deleting volumes with associated Backups

A volume that has associated backups cannot be removed. Specifically, if the 'Daily Cloud Snapshot' was enabled, there will be backups associated with your volume. Delete all the backups that are associated with the volume in question. Now follow all the steps listed under "Deleting volumes with no associated Backups" to delete this volume.

 

Note.png Note: When you delete a volume, it may take some time for the capacity consumed by that volume on your appliance and on the cloud to be freed. You may notice that capacity consumption charts do not immediately reflect the capacity becoming available after deleting a volume.

 

Back to Top

<< PrevNext >>

Related

 

Page statistics
1795 view(s) and 83 edit(s)
Social share
Share this page?

Tags

This page has no custom tags.
This page has no classifications.

Comments

You must to post a comment.

Attachments