Cloudbyte Complete Documentation

Using the REST APIs

Introduction

CloudByte ElastiStor REST APIs provide a bundle of functions that encompasses all the features in the CloudByte ElastiStor Administrator Console (CloudByte ElastiCenter). You do not need ElastiCenter to configure and manage CloudByte ElastiStor. Rather you can use your own portal.

The CloudByte ElastiStor REST APIs provide powerful, convenient, and simple REST-based APIs which can interact with CloudByte ElastiStor.

Click one of the following links to get a complete list of CloudByte ElastiStor REST APIs and documentation relevant to your administrative privileges:

The following sections explain the implementation.

How to use CloudByte ElastiStor REST APIs

  1. Install CloudByte ElastiCenter. For details, see Installing CloudByte ElastiStor.
  2. Authenticate as Administrator. For details, see Launching CloudByte ElastiCenter.
  3. Obtain the CloudByte REST API authorization token. This token is passed in each request using the API Key request parameter. For details, see the section Obtaining the REST API key.
  4. Form the request URL. For details, see the section Forming the API request.

Obtaining the REST API key

  1. Log in to ElastiCenter as Super Admin.
  2. In the navigation pane, select Delegated Administrator. The list of administrators appears.
  3. From the list of Accounts, click the specific account for which you want to generate the API key.
  4. In the following page, click Generate Keys.

api_reference_generate_keys

  1. Click Yes to confirm. The API key is generated and displayed as shown in the following screen:

api_reference_api_key

Forming the API request

The following is a sample GET request:

https://<elasticenteripaddress>/client/api?command=listSite&apiKey=Jj6GQNj07iqido49QAngCbLjMj4th_T_OW39J4Wtpa7o1Ext_T8gfXsmVop_noQ6PXVdrp_zajPPImKFts5UVw&response=json

Interpreting the URL

URL Component Description
https://10.36.36.50/client/api? Base URL which includes the IP address to access CloudByte ElastiCenter; the web service API entry point.
command=listSite The web service command you execute. For the complete list of commands, see ElastiStor APIs.
apiKey=UjGmN7gGwzMhFsSese3TNNOWiXHGn53eon_7sHx3aL-9_t3sHAOV_rNqVzwTnrJyCaTAg9FucSBvMp49nbnfEQ The API key that you generated.
response=json Response format. This can be XML or JSON. To get an XML response, replace json with xml in the URL.

Apart from these, the URL also has the additional parameters (required or optional) for the command.

Sample response in JSON

{ “listSiteResponse” : { “count”:2 ,”site” : [  {
  “id”: “66291daa-4c40-4462-8747-926ebc488963”,
  “name”: “Bangalore”,
  
“location”: “India”,
  “managedstate”: “Available”,
  “revisionnumber”: 0,
  
“currentUsedSpace”: 29,
  
“currentAvailableSpace”: 9943,
  “currentTotalSpace”: 9972,
  
“currentThroughput”: 605,
  “currentIOPS”: 151,
  “currentLatency”: 163,
  “currentThrottle”: 20,
  “controllers”: [
    {
“nodePools”: “4”,
“id”: “4c6e2246-52c1-3227-b51a-9928cf3b675a”,
“clusterid”: “88bf812b-5142-4780-8ad3-13178bbf30a1”,
“name”: “host1”,
“hostname”: “Both”,
“nodeTsms”: “4”,
“ipaddress”: “10.36.36.50”
}
],
“haclusters”: [
{
“id”: “88bf812b-5142-4780-8ad3-13178bbf30a1”,
“haClusterPools”: “4”,
“haClusterNodes”: “1”,
“name”: “Cluster1”,
“haClusterTsms”: “4”
}
],
“hapools”: [
{
“controllerId”: “4c6e2246-52c1-3227-b51a-9928cf3b675a”,
“id”: “38e66579-bb91-3de3-815a-48c35e2c5943”,
“availiops”: “50”,
“totalthroughput”: “102400”,
“name”: “Pool1”,
“poolTsms”: “1”,
“availthroughput”: “51200”,
“totaliops”: “100”
},
{
“controllerId”: “4c6e2246-52c1-3227-b51a-9928cf3b675a”,
“id”: “226e2e02-a3e5-3609-b70d-aea8ef655f74”,
“availiops”: “75”,
“totalthroughput”: “153600”,
“name”: “Pool2”,
“poolTsms”: “1”,
“availthroughput”: “76800”,
“totaliops”: “150”
},
{
“controllerId”: “4c6e2246-52c1-3227-b51a-9928cf3b675a”,
“id”: “810f428d-9c26-3d91-8675-62cc3ca56da0”,
“availiops”: “100”,
“totalthroughput”: “153600”,
“name”: “pool3”,
“poolTsms”: “1”,
“availthroughput”: “102400”,
“totaliops”: “150”
},
{
“controllerId”: “4c6e2246-52c1-3227-b51a-9928cf3b675a”,
“id”: “11d6fd85-5782-39fe-b85d-079d73742757”,
“availiops”: “175”,
“totalthroughput”: “384000”,
“name”: “P4”,
“poolTsms”: “1”,
“availthroughput”: “179200”,
“totaliops”: “375”
}
],
“tsms”: [
{
“controllerId”: “4c6e2246-52c1-3227-b51a-9928cf3b675a”,
“id”: “1cb805fe-dd22-357e-b198-121fa08d0971”,
“availiops”: “25”,
“totalthroughput”: “51200”,
“name”: “T1”,
“ipaddress”: “10.37.37.51”,
“availthroughput”: “25600”,
“totaliops”: “50”
},
{
“controllerId”: “4c6e2246-52c1-3227-b51a-9928cf3b675a”,
“id”: “90a4e6f8-cb3c-317f-8cdf-3986e8759747”,
“availiops”: “50”,
“totalthroughput”: “76800”,
“name”: “T2”,
“ipaddress”: “10.37.37.52”,
“availthroughput”: “51200”,
“totaliops”: “75”
},
{
“controllerId”: “4c6e2246-52c1-3227-b51a-9928cf3b675a”,
“id”: “cab14af0-84b6-3761-900b-9675b32b6ba5”,
“availiops”: “25”,
“totalthroughput”: “51200”,
“name”: “T3”,
“ipaddress”: “10.37.37.53”,
“availthroughput”: “25600”,
“totaliops”: “50”
},
{
“controllerId”: “4c6e2246-52c1-3227-b51a-9928cf3b675a”,
“id”: “17b17719-137d-3f95-9f4f-468a17a45957”,
“availiops”: “100”,
“totalthroughput”: “204800”,
“name”: “T4”,
“ipaddress”: “10.37.37.54”,
“availthroughput”: “102400”,
“totaliops”: “200”
}
]
}, {
“id”: “74692191-75a9-4294-9b1e-402127c9e327”,
“name”: “test”,
“managedstate”: “Available”,
“revisionnumber”: 0,
“currentUsedSpace”: 0,
“currentAvailableSpace”: 0,
“currentTotalSpace”: 0,
“currentThroughput”: 0,
“currentIOPS”: 0,
“currentLatency”: 0,
“currentThrottle”: 0
} ] } }

Sample response in XML

<listSiteResponse cloud-stack-version=“1.1.0.4.2013-02-06T10:19:20Z”>
  <count>1</count>
  <site>
    
<id>ad63d28a-9de9-443f-8260-4309337f40c3</id>
    <name>site</name>
    
<managedstate>Available</managedstate>
    <revisionnumber>0</revisionnumber>
    
<currentUsedSpace>0</currentUsedSpace>
    <currentAvailableSpace>1996</currentAvailableSpace>
    <currentTotalSpace>1996</currentTotalSpace>
    
<currentThroughput>0</currentThroughput>
    <currentIOPS>0</currentIOPS>
    <currentLatency>0</currentLatency>
    <currentThrottle>0</currentThrottle>
  </site>
</listSiteResponse>

CloudByte ElastiStor overview

What is CloudByte ElastiStor

CloudByte ElastiStor is a full-featured enterprise storage solution for virtualized environments. Its patented technology empowers organizations to spin out Virtual Storage Machines (VSMs) and to scale storage performance higher or lower instantly.ElastiStor makes storage predictable, affordable and easy, even as you scale to thousands of applications.

Installable on a wide range of industry-standard servers, ElastiStor frees enterprises and service providers from vendor lock-ins. ElastiStor lets you custom-build storage infrastructure based on your requirements, with support for SATA, SAS, and SSD hardware as well as NFS, CIFS, and iSCSI protocols.

Cloud-scale Performance

The allocation of application-specific storage silos to deliver performance does not scale well in today’s cloud and virtualized environments. ElastiStor enables you to guarantee performance (IOPS, throughput, and latency) for every application right from a common storage platform. This fully shared data storage solution optimizes your infrastructure, minimizes your CAPEX, and enables more performance applications to move to the cloud.

No Vendor Lock-in

In addition to being software-defined, ElastiStor eliminates the need for you to lock into specific vendors or overspend on proprietary hardware. The benefits of commodity, industry-standard resources are first reflected in minimized CAPEX, and later make shifting vendors easy with no proprietary hardware lock-in.

Hardware Flexibility

Restricting storage media choice is not an ideal scenario when you have a wide variety of performance needs, from archival to big data applications, and it is definitely not practical to fit every performance-sensitive application on an all-SSD array. ElastiStor is software-only so you continue to work with the storage media of your choice – SSD, SAS, SATA, or any mix – optimized for your performance needs.

Simple Management

Managing storage for a large number of applications and their constantly changing performance demands is not for the faint hearted. Manual tuning of spindles or other hardware is no longer an option. Being software-defined, ElastiStor allows you to instantly provision fully-elastic storage volumes for any workload from the shared storage pool to enable fast deployment and reconfiguration options. Now it is a simple matter to schedule backups, migrate sites, and empower customers with comprehensive management rights for their dedicated storage. Additionally, datacenter admins will be able to provision and manage QoS-aware storage volumes for VMs right from VMWare vCenter, Citrix XenCenter, OpenStack Horizon, or CloudStack.

Affordable

With CloudByte ElastiStor you can now replace hundreds of legacy storage silos in your datacenters with a single, extensible storage platform. By fully sharing your infrastructure, deploying industry-standard hardware and optimally choosing your storage media, ElastiStor can significantly reduce your datacenter footprint, leading to 80-90% cost savings over 3-5 years. Add simplified management that brings down your operational costs, and you get the lowest cost storage QoS solution.

Features at a glance

Along with the standard storage features, CloudByte ElastiStor provides certain product-specific features of which some are unique.

CloudByte ElastiStor features

Guaranteed Storage QoS within Shared Storage

Share your storage and deliver predictable performance to every application. For the first time ever, ElastiStor allows storage endpoints to be defined beyond capacity, in terms of IOPS, throughput and latency. This allows applications with diverse workloads to be guaranteed QoS from a shared storage platform. Together with linear scaling, a single extensible shared storage platform from ElastiStor can now replace legacy solutions’ dedicated storage silos. By fully sharing storage and optimally utilizing resources, ElastiStor steeply cuts down your storage footprint, leading to 80-90% cost savings over 3-5 years.

On-Demand Performance Provisioning

Do you still manually configure hardware to provision performance for any new application? Break the need for hardwiring storage with ElastiStor’s on-demand provisioning. Just enter the required SLA/QoS parameters and let ElastiStor automate node selection and resource allocation for you. ElastiStor includes an intelligent heuristics daemon which continuously learns the quantity of various controller resources needed to deliver the required QoS.

vCenter-like Administration Console

ElastiStor makes managing storage as easy as managing VMs, even as you scale to hundreds of applications. Storage admins can now comprehensively manage the entire storage cluster, spanning across multiple sites, from a single web-based console. Further, ElastiStor gives you unprecedented access and control over resource usage within shared storage, right down to the application-level granularity.

REST APIs and Plugins for Easy Integration

Every action performed at ElastiStor admin console translates into a REST based API call in the backend. Using these REST APIs, admins can comprehensively provision and manage ElastiStor volumes from VMware vCenter, Citrix XenCenter, OpenStack Horizon, or any other admin portal. Our plugin for VMware vCenter allows admins to create and manage QoS-aware VMs right from vCenter console.

N-way High Availability

ElastiStor enables N-way High Availability, exponentially increasing reliability (mean time to failure), compared to the standard 2-way HA provided by existing solutions. CloudByte’s storage un-fragmentation and its patented VSM architecture make N-way HA affordable and feasible.

Delegated Administration

A much requested feature from the cloud service providers, delegated administration empowers both CSPs and its customers to monitor and control storage volumes. Management privileges vary based on the admin functionality – for example, a super admin can manage the entire storage cluster, whereas a customer admin can manage just the storage resources allotted to that particular customer.

Standard storage features

The following Storage features are available in CloudByte ElastiStor:

Feature Description
Scalability
  • 128-bit file system
  • Zettabyte storage capacity
  • Unlimited file size
Access Protocols
  • NFSv3
  • NFSv4
  • CIFS
  • ISCSI
  • FC
Storage Connectivity
  • SAS JBODs
Storage Resilience
  • RAID Z1
  • RAID Z2
Storage Efficiency
  • De-duplication
  • Compression
  • Thin Provisioning
Back up
  • Unlimited Clones
  • Unlimited Snapshots
Availability
  • N-way high availability (N-way HA)
  • Partial failure transfer to the available node
  • Active-Active mode
  • HA with/without storage redundancy
Disaster Recovery
  • Tenant level disaster recovery
  • High availability across primary and DR sites
  • Block level replication
  • Synchronous mirroring,
  • Asynchronous mirroring
  • RPO—Last minute
  • RTO—Few minutes
Data Integrity
  • Protection against silent data corruption
  • Fixes corrupt block without having to take the file system offline

Note: The supported capacity of ElastiStor depends on the hardware. With adequate hardware support, ElastiStor can scale up to any extend.

How CloudByte ElastiStor is different from legacy storage solutions

The following table explains the major differences:

Feature Legacy solutions CloudByte ElastiStor
Storage Architecture Monolithic Patented VSM Architecture
Tenant Solution Only at access layers At all Storage Stack layers
Full featured tenants No guaranteed QoS, delegated administration, or complete security Provides guaranteed QoS, delegated administration rights, and complete security
Access to tenant-level resource usage No Yes
Security Limited Fully secure (complete isolation, access with encrypted key)

Patented VSM Architecture

In a CloudByte Controller, each tenant is completely isolated at storage stack levels and unified as a Virtual Storage Machine (VSM). With complete isolation, VSMs can be treated as if they are allotted dedicated storage controller enabling:

  • Shared storage tenants with guaranteed QoS (IOPS, Throughput, and latency), delegated administration rights, and complete security.
  • Easy shared storage management with access to and control over tenant-level resource usage (disk, cache, network, and CPU).

Together with its rich customizability and scalability, CloudByte ElastiStor offers a powerful storage virtualization solution for service providers and enterprises.

CloudByte ElastiStor Editions

CloudByte ElastiStor has the following two editions:

  • Enterprise edition
  • Community edition.

For further details, see Community edition and Enterprise edition.

CloudByte ElastiStor feature highlights

Quality of Service (QoS)

CloudByte ElastiStor assures highly predictable performance using its unique QoS-centric approach to provisioning. The feature highlights include:
  • Guaranteed throughput, latency, and IOPS: Easily commission storage with guaranteed throughput, latency, and IOPS (Input/Output Operations Per Second) at various levels. You can decide to configure QoS at a Pool level, TSM level, or Storage Volume level.
  • Multi-dimensionality: Configure IOPS, throughput, latency, and capacity.
  • Grid-like service: Utilize available unused storage resources efficiently.
  • On-demand modification: Edit settings at a later point of time without restart.

See Also: “Assuring Quality of Service” 

Multi-protocol support

CloudByte ElastiStor provides LUN access using the following protocols:
  • Fiber Channel (FC)
  • iSCSI
  • CIFS
  • NFS

See Also: “Setting up Data Access Protocols” 

Simplified storage provisioning

Assume that you require 20 GB storage and 10000 IOPS. With too many pools and TSMs, manually verifying the apt Pool is a cumbersome task. Instead, use the auto-provisioning feature in ElastiStor to handle this situation. ElastiStor provides a simplified storage provisioning where it intelligently provides a list of best-fit pools. Server disk space is divided into storage spaces based on the number of applications, individualistic requirements, and expected performance from each application. With ElastiStor, you can enter the required SLA/QoS parameters and automate the host selection and resource allocation.

See Also: “Provisioning Storage” 

Delegated administration

Delegated administration lets you determine the actions various administrators can take using administrative tools on different resources. The administration roles are mapped to functions using security policies. You can create and maintain separate administration capabilities depending on your needs.

See Also: “Delegated Administration”

Multi-way High Availability

CloudByte ElastiStor provides N-way High Availability.

See Also: “Configuring High Availability”

Disaster Recovery

CloudByte ElastiStor equips you to effectively recover data in the case of adversities. Use the Mirror feature for remote disaster recovery. When you mirror data, a remote snapshot, a read-only copy of the data on the primary setup, is created in the secondary storage setup. In the case of disaster, you can activate the mirror to take care of the services handled by the primary setup.

See Also: “Configuring remote disaster recovery”

REST APIs for easy integration

CloudByte ElastiStor REST APIs provide a bundle of functions that encompasses all the features available in the CloudByte ElastiStor Administrator Console (CloudByte ElastiCenter). That is, you need not have ElastiCenter to configure and manage CloudByte ElastiStor. Rather you can use your own portal.
The feature highlights include:
  • APIs for all the features in ElastiCenter. The APIs function as an end-to-end translation of the Administrative Console.
  • APIs are pluggable with delegated administration preset.
  • CloudByte provides off-the-shelf plug-ins which you can install and start using. For details, see CloudByte ElastiStor Plug-ins

Intuitive administration console CloudByte ElastiCenter

CloudByte ElastiStor’s centralized management console CloudByte ElastiCenter makes configuration and management of storage simple even when you have thousands of applications. Comprehensively manage your entire storage cluster from a single Web-based console. Monitor, control, and audit storage resource usage down to application-level granularity. The ElastiCenter features include:
  • Wizards that walk you through the entire setup
  • Interactive graphical representations that help you monitor data
  • Highly usable action pods that let you manage tasks, with easy access and minimal navigation

dashboard11

See Also: “ElastiCenter User Interface”

Physical storage infrastructure

The following illustration briefs about the components of ElastiStor:

ComponentOfSite

Building your storage infrastructure starts with the creation of a Site, the fundamental infrastructure building block where your Node and storage and network infrastructure reside. The following illustration shows the composition of a Site:

FundamentalInfrastructureBuildingBlockofElastiStor

See also Setting Setting up your storage and ElastiCenter, ElastiStor’s management console

Simple hardware configuration of ElastiStor

The following figure illustrates a simple hardware setup, to form an HA Group, that you can use to get started:

simple_harware_conf

Connect the SAS cable between the SAS port of the Node and Disk Array’s IN port . To form a daisy chain, connect SAS cable between OUT port of one Disk Array and IN port of another Disk Array. This sets up a group of Nodes.  

An HA Group can have a maximum of four Nodes.

ElastiStor in High Availability mode

The following hardware setup diagram is a typical configuration of CloudByte ElastiStor in High Availability mode. Hardware_setup_diagram_HA

Installation overview

The installation of CloudByte ElastiStor involves installing

You can install the components separately or together.

installation_overview

Note: Installing ElastiCenter and Node together is not recommended for production environments.

Planning your installation

The following illustration is a quick-start representation of ElastiStor installation:
InstallationWorkFlowSource
CloudByte ElastiStor installation comprises the following:

  • Installing ElastiCenter: Install the administrative infrastructure used to manage the Nodes.
  • Installing Nodes: A Node is the storage infrastructure that is managed by ElastiCenter. You can install only one Node per machine. An HA Group can have up to four Nodes.

Installing on production environments

CloudByte recommends you to install ElastiCenter and Nodes on separate machines.

Installing on development environments

You can install both ElastiCenter and Nodes together on the same machine. This is the typical installation used for development and test setups. Here you play around with test data for evaluation, rather than production where you have business critical data.

System requirements

The following topics explain the system requirements for installing CloudByte ElastiStor.

  • CloudByte Storage Controller node is built on commodity servers.
  • The connectivity between Controller and Storage is either on Ethernet (iSCSI) or on SFF-8088 SAS cables.
  • ElastiStor OS is built using FreeBSD 9 as the base platform and therefore CloudByte ElastiStor’s Hardware Supported List is similar to that of FreeBSD 9 Release version.

Minimum hardware requirements to build CloudByte ElastiStor Node

  • Supported AMD64, Intel 64 (x86-64), or i386 Processor and System Board (with Dual Core Processor and 8GB of RAM)
  • Four 1 Gigabit Ethernet Controller Cards
  • One or more SAS HBAs, depending on the number of disk arrays connected
  • OS boot disk drive size of 20 GB. However, the recommended size is 2.4 * RAM size + 33GB

Minimum hardware requirements for CloudByte ElastiCenter

  • Supported AMD64, Intel 64 (x86-64), or i386 Processor and System Board (with Dual Core Processor and 8GB of RAM)
  • OS boot disk drive size of 20 GB. However, the recommended size is 2.4 * RAM size + 33GB
  • 1 Gigabit Ethernet Controller Cards

For supported list of

High Availability requirements

For details, see HA prerequisites.

Hardware Compatibility List

For the complete list of compatible hardware, see Hardware Compatibility List.

Network configuration details

You need the following network configuration details to proceed. CloudByte provides a set of values by default.
Option Description
Host Name of the host, for example CloudByte.
Root Password The password assigned to the root account.
IP address The IPv4 addresses that you want to access.
Net Mask The IPv4 subnet mask, for example 255.255.255.0.
Gateway The IPv4 gateway IP address, for example 10.0.0.1.
DNS The IPv4 address of the DNS server, for example 8.8.8.8.
Search Domain search, for example lab.engineering.cloudbyte.com.

Installation options

The installation wizard provides the following installation options.
  • Only ElastiCenter: Installs only ElastiCenter, which is the central administrative console to manage your Nodes. Choose if you prefer to install Node later. For procedures, see Installing CloudByte ElastiCenter.
  • Only Node: Installs only the Node, which is managed using ElastiCenter. Choose if you prefer to install ElastiCenter later. For procedures, see Installing Node.
  • Both ElastiCenter and Node: Installs both ElastiCenter and Node. This installation is not recommended for production deployments. For procedures, see Installing Both ElastiCenter and Node.

Installing ElastiCenter

  1. Insert the CloudByte ElastiStor installation disk into your computer’s DVD or CD drive and boot up your Node (ensure that the disk drive is set as your system’s primary boot device). The installation starts up and the following screen with the boot options appear:

    Installation_EC_1

    By default, the boot option Boot CloudByte ElastiStor is selected. So you need not interfere. To select a different boot option, see “Boot options”.

    The Welcome screen appears.

    Installation_ES_2

  2. In the following screen, accept the license agreement.

    Installation_EC_3

  3. Select Only ElastiCenter option. For details, see Installation options.

    Installation_EC_4

  4. (If you have multiple disks) At prompt, select the disk where you want to install CloudByte ElastiStor.
  5.  

    Installation_EC_5

  6. (If you have multiple Ethernet Interfaces) At prompt, select the Ethernet Interface and click OK.

    Installation_EC_6

    The following screen appears:

    Installation_EC_7

  7. Specify the networking configuration details.
  8. Click OK. The following screen appears:

    Installation_EC_8

  9. Select Continue to confirm the settings so that the installation can start up. To modify any of the values, select Back. Installation starts and the wizard shows the progress.

    Installation_EC_9

  10. In the following screen, specify the region you belong to:

    Installation_EC_10

  11. Confirm the country and then confirm the time zone.

    Installation_EC_11

    The installation completes and the following screen appears:

    Installation_EC_12

    After installing the packages, CloudByte ElastiStor reboots (indicated by the following screen).

    Installation_EC_13

    Wait till the system automatically reboots. The following screen welcomes you after the reboot:

    Installation_EC_14

    The following screen with a login prompt indicates that installation is successful. You can proceed to configure CloudByte ElastiStor.

    Installation_EC_15

 

You can now

  1. Launch ElastiCenter in Mozilla Firefox Web browser (by specifying the URL, provided in the network configuration details, in the format https://<ipaddress>).
  2. Log in.
  3. Perform the configuration procedures. For details, see “Configuring CloudByte ElastiStor“.

Boot options

Option Description
Boot CloudByte The default option. Select to start the installation with all standard options enabled.
Escape to loader prompt Lets you perform advanced configuration in a CLI environment.
Reboot Select to reboot.
Boot CloudByte with ACPI Select to boot with advanced configuration and power interface. Helpful for power management.
Boot CloudByte with Safe Mode Diagnostic mode with reduced functionality.
Boot CloudByte with Single User Mode Lets only a single user to login. That is the root user.
Boot CloudByte with Verbose To view behind the scene activities that occur during the installation. Particularly useful for troubleshooting .

Installing Node

  1. Boot up your Node server and insert the CloudByte ElastiStor installation disk into your computer’s DVD or CD drive. The installation starts up and the following screen with the boot options appear:

    Installation_ES_1

    By default, the boot option Boot CloudByte ElastiStor is selected. So you need not interfere. To select a different boot option, see “Boot options”.

    The Welcome screen appears.

    Installation_ES_2

  2. In the following screen, accept the license agreement.

    Installation_ES_3

  3. Select the installation option. For details, see Installation options.

    Installation_ES_4

  4. At prompt, specify the ElastiCenter IP address and then click OK.

    Specify_ElastiCenter_IP_address

  5. (If you have multiple disks) At prompt, select the disk where you want to install CloudByte ElastiStor and then click OK.

    Installation_ES_5

  6. (If you have multiple Ethernet Interfaces) At prompt, select the Ethernet Interface and then click OK.

    Installation_ES_6

    The following screen appears:

    Installation_ES_7

  7. Specify the networking configuration details.
  8. Click OK. The following screen appears:

    Installation_ES_8

  9. Select Continue to confirm the settings so that the installation can start up. To modify any of the values, select Back. Installation starts and the wizard shows the progress.

    Installation_ES_9

  10. In the following screen, specify the region you belong to:

    Installation_ES_10

  11. Confirm the country and then confirm the time zone.

    Installation_ES_11

    The installation completes and the following screen appears:

    Installation_ES_12

    After installing the packages, CloudByte ElastiStor reboots (indicated by the following screen).

    Installation_ES_13

    Wait till the system automatically reboots. The following screen welcomes you after the reboot:

    Installation_ES_14

    The following screen with a login prompt indicates that installation is successful. You can proceed to configure CloudByte ElastiStor.

    Installation_ES_15

ElastiCenter, ElastiStor's management console

Introduction

ElastiCenter is the centralized management tool that you use to configure, monitor, manage, and deploy the services provided by CloudByte ElastiStor.

ElastiCenter lets you

  • Use the Graphical User Interface to manage the storage environment
  • Generate statistical and configuration reports to help troubleshoot
  • Delegate administration tasks
  • Track events
  • Globally control various settings

Using ElastiCenter, the entire ElastiStor deployment, consisting of multiple geographical sites spanning multiple clusters and servers, can be managed from a single browser session. Storage management tasks such as High Availability and disaster recovery can be done from the same session. To illustrate, let us examine the processing of a file recovery request for a particular storage tenant using a legacy solution and CloudByte ElastiStor:

Legacy solution CloudByte ElastiStor
The administrator has to
  1. Manually recover the file from the DR storage system
  2. Manually transfer to the primary site
  3. Merge with the primary site.
In CloudByte ElastiStor, using ElastiCenter, the administrators can perform actions remotely from the management portal. The administrator can, from the same browser session,
  1. Log in to the primary site.
  2. Identify the storage file system that needs to be recovered.
  3. Browse for the corresponding backup copies on the remote DR site.
  4. Recover data with a single click.

The following illustration shows the workflow to setup a storage environment using CloudByte ElastiCenter:
WorkflowToSetupYourStorageEnvironmentUsingCloudByteElastiCenter


ElastiCenter User Interface

The following topics orient you with the ElastiCenter User Interface.

Note: The screenshots in the documentation are captured from the Enterprise Edition of ElastiStor. However, except for the color schemes, the user interface and functionality are identical for both Community Edition and Enterprise Edition.

Navigation pane

The navigation pane in the left-hand side of ElastiCenter provides a list of options.

When you select an option, you are taken to a specific component page. Use the component pages to perform various configuration and management tasks.
elasticenter_navigation_pane

Note: The options displayed in the navigation pane depend on the administrative privileges you have. If you are a super administrator, you have all the options. For further details, see Managing CloudByte ElastiStor.

Content pane

The content pane displays the component pages that provide options and data to configure CloudByte ElastiStor. For example, if you select Sites in the navigation pane, the Sites page appears.

elasticenter_content_pane

Summary pane

Summary pane sums up the number of storage components, such as Sites or Pools, in the storage infrastructure.

elasticenter_summary_pane

Actions pane

Action Pane, in the right-hand side of the content pane, provides a list of configuration options. For example, in the HA Groups page, go the Actions pane and add administrator.

elasticenter_actions_pane

Notification menu

The information menu in the top right-hand side of ElastiCenter lets you access Alerts, Events, Reports, and Administrator data. You also have the option to go back to the Home page.

elasticenter_notification_pane

See Also: Monitoring and CloudByte ElastiStor reporting

Admin options

The Admin options help you with various administrative tasks.

elasticenter_admin_options

See Also: CloudByte ElastiStor API Reference, Licensing, and Delegated administration.

Launching CloudByte ElastiCenter

CloudByte ElastiCenter is a browser based console which you can launch using any of the popular browsers such as Mozilla Firefox or Google Chrome.

Note:Ensure that you have updated Adobe Flash Player to the most recent version.

To access ElastiCenter,

  1. Launch Mozilla Firefox Web browser.
  2. Specify the URL in the following format: https://IP Address

Note:The IP Address you specify is the one that you configured in the installation screen. See Installing CloudByte ElastiStor. Installing CloudByte ElastiCenter.

Authentication

You need credentials (username and password) to log in to CloudByte ElastiCenter.

  1. After installation is completed, launch ElastiCenter using the URL in the following format: https://IP Address.

welcome_cloudbyte_elasticenter_login_page

  1. Specify the following default credentials:
CredentialsValue
User nameadmin
Passwordpassword

After you login, you can change the password.

Reset password and configure auto-alert options

After you log in, you are prompted to:

  • Change your password
  • Update your profile. CloudByte Technical Support might use this information to contact you when your storage infrastructure encounters any issues.
  • Review the auto-alert details that CloudByte Technical Support collects automatically. Technical Support might use the information to resolve potential problems that your storage infrastructure encounters. You have the option not to share particular information.

To reset password and configure auto-alert options,

  1. Login to ElastiCenter using the default credentials (admin|password). The following screen appears:

elasticenter_change_password

  1. Specify a new password and then confirm.
  2. Update your profile.
  3. Review the auto-alert information, and uncheck the options that you do not want to share.
  4. Click Update.

Replacing default SSL Certificate

The connection between ElastiCenter and browser is secured using SSL. If required, you can replace the default certificate using the following procedures.

Note:The utility used to perform the following tasks is keytool. You can use a utility of your preference.

  1. In the ElastiCenter console, run the command as shown in the following example:
     keytool -genkey -alias primarycb -keyalg RSA -keystore myprimary.keystore -keysize 2048
    . At prompt, provide password and the domain details.
  2. In the ElastiCenter console, generate Certificate Signing Request (CSR) by executing the command as shown in the following example:
    keytool -certreq -keyalg RSA -alias primarycb -file mycertreq.csr -keystore myprimary.keystore
    . You are then prompted to specify a password for keystore.
  3. Get the CSR signed by the trusted CA. (for example, VeriSign or Thawte).
  4. (Optional) Append the certificate with intermediate CA and trusted root CA.
  5. Import the CA’s certificate into your keystore as a trusted certificate using the following command
  6. keytool -importcert -file verisign.cer -keystore myprimary.keystore -alias primarycb
  7. Copy the keystore to the directory
    /usr/local/apache-tomcat-6.0.33/conf
    .
  8. Edit the following lines in the file
    server.xml
    in the directory
    /usr/local/apache-tomcat-6.0.33/conf/
  9. keystoreFile="conf/myprimary.keystore"
    keystorePass="cloudbyte"
  10. Run the following command to shut down Tomcat:
    /usr/local/apache-tomcat-6.0.33/bin/shutdown.sh
  11. Kill Java processes using the following command:
     pkill java
  12. Execute the following command to ensure that no Java process is running:
    pgrep java
  13. Start Tomcat using the command
    /usr/local/apache-tomcat-6.0.33/bin/startup.sh

Configuring CloudByte ElastiStor

CloudByte ElastiStor is configured and managed using the administrator console named CloudByte ElastiCenter. The following topics explain the configuration and management tasks that you can perform.

Setting up your storage

In CloudByte ElastiStor, the set of configurations that you perform can be divided in to tasks related to

  • Infrastructure, the base structure of your storage service
  • Accounts, that you have to create for storage specific needs

The following figure shows how your infrastructure and account are organized in CloudByte ElastiStor:

HowInfrastructureAndAccountOrganized

The following sections explain the concepts in detail:

Sites

Building your storage infrastructure starts with the creation of a Site, the fundamental infrastructure unit where your Node and storage and network infrastructure reside.

The following figure depicts the structure of a site:

component_of_site

The following figure explains each component of the site
ComponentOfSite1

Accounts

After you set up the storage infrastructure, you build the account infrastructure. That is, you set up the client/customer for using your storage infrastructure.

The following figure explains how an account is constituted in CloudByte ElastiStor.

HowAccountIsCconstitutedInCloudByteElastiStor

The following figure explains each component associated with the account.

Storage_volume_definition (1)

Creating a Site

A Site represents a data center or part of a data center. Building storage infrastructure starts with the creation of Site. It is the fundamental infrastructure unit where your Node, storage, and network infrastructure reside.

Use the Sites page (ElastiCenter > Sites) to create a Site.

The Sites page provides a graphical representation of the Sites that you have created. It provides the Site details such as the HA Groups, Pools, Provisioned Storage, and TSMs that you have set up.

Click any of the Site details link for specific review and configuration. For example, click HA Groups to access details of the HA Groups associated with the Site.

To create a Site

  1. In the Sites page, click Add Site in the actions pane.

The Add Site page appears.

Add_Site_Enter_details_2

  1. Specify the following details:
Field Description
Name Unique name for the site
Location Where the site is located
Description A meaningful description for the Site
  1. Click Add.

Creating an HA Group

An HA Group houses a group of Nodes. HA Group enables takeover during failures. Workload of a failed Node is assigned to another Node in the same HA Group based on availability and performance requirements.

All Nodes in the HA group you create must be on the same
  • Public network: used in Node management
  • Private network: used in data transfer with VSMs

Use the HA Groups page (ElastiCenter > HA Groups) to create an HA Group.

Creation of HA Groups leads to the formation of High availability Clusters. For details, see Configuring High Availability.

  1. In the HA Groups page, click Add HA Group.
  2. The Add HA Group page appears.

     Add_HA_Group_enter_details_2

      1. Specify the following options and then click HA Group.
    Field Description
    Site The Site to which you add the HA Group.
    Name Unique name for the HA Group.
    Description Meaningful description for the HA Group.
    HA Group Health Check IP Address Range Provide a range of dedicated IP addresses (first and last) in the management network. For instance, 10.11.12.11-10.11.12.12. The IP addresses you specify are used to check the heartbeat between Nodes. Note: Ensure that you do not specify the IP addresses used for Node or ElastiCenter.

    Changing the HA Group health check IP address range

    1. Bring Node1 to maintenance mode.
    2. Bring Node2 to maintenance mode.
    3. In the HA Groups page, select the HA Group for which you want to change the Health Check IP address range.
    4. Click Settings in the actions pane.
    5. In the following page, click edit and then change the details.
    6. Change hagroup ip range

    7. Click Save

Adding a Node

Node is a physical machine on which you configure ElastiStor. You can have a minimum of two and maximum of four Nodes in an HA Group.

  1. In the ElastiCenter navigation pane, click Nodes.
  2. In the actions pane, Click Add Node.
  3. config_add_node

  4. In the Add Node page, specify the following details:

Field Description
Site Select a Site.
HA Group Select the HA Group to which the Node has to be added.
Name Unique name for the Node.
Address IP address of the Node.

  1. Click Add.

Deleting a Node from an HA Group

Follow the procedures to delete a Node from a single Node HA Group:

  1. Delete all the Storage Volumes on the Node.
  2. Delete all the VSMs on the Node.
  3. Delete all the Pools on the Node.
  4. Bring down the Node to maintenance mode.
  5. Click the delete icon to remove the Node from HA Group.

Follow the procedures to delete a Node from an HA Group with more than one Node:

  1. Bring down the Node to maintenance mode.
  2. Click the delete icon to remove the node from HA Group.

Configuring Disk Array Enclosure

After you add Node, you are redirected to the Node page.

When there is no Disk Array attached to the Node, the following page appears. Ensure that you attach a Disk Array to the Node and then click Refresh Hardware.

Note: When you attach a new Disk Array to a Node, click Refresh Storage/Refresh Hardware to make it visible on the ElastiCenter.

Disk_Array_Enclosure

To configure a newly attached Disk Array enclosure, follow the procedures:

  1. In the Node page, click the image in the section Shared Storage.

config_disk_array_enclosure_1

The following screen appears:

config_disk_array_enclosure_2

  1. Click Specify Disk Array Configuration. The Disk Array Configuration page appears:

config_disk_array_enclosure_3

  1. Specify the Name, Bay Alignment, Number of columns and Number of Rows. For details, see the following section Configuration details.
  2. Click Next and do the following:
      • Click the option under the column Blink. For details, see the section SCSI Enclosure Service at the bottom of this page.
      • Specify the bay location for the disks from the drop down list under the column Bay.

    config_disk_array_enclosure_4

  3. Click Apply. On successful configuration, the Node page appears with a representation of the shared storage:disk_array_enclosure_configuring
Note: You can also partially configure a Disk Array Enclosure. Suppose you have 12 disks, you can initially configure around 8 disks and other 4 disks can be configured as per the requirement.

Configuration details

Horizontal and vertical alignments

The Disk Arrays can be idealized either in terms of horizontal or vertical alignments.

The following figure represents a vertical alignment:


JBod-VerticalAlignment

The following figure represents a horizontal alignment:

JBod-Horizontal

Slots per row

Slots per row is the number of disks each row can accommodate. For example, three slots per row implies that a single row can accommodate three disks.

JBod-SingleRow JBod-SingleRow

 

SCSI Enclosure Service

SCSI Enclosure Service (SES) helps monitor the status of each device in a disk array enclosure such as disk slots, fans, heat sinks, or power supplies.

The service helps you

  • Identify a disk or verify the slot in which the disk is located.
  • Locate and disable a faulty disk.
  • With specific and general alerts on enclosure components.

Blink identification

Blink identification LED on the disk slot of a disk array. When you click Blink, at the physical location of the disks, the identification LED in the specified disk slot blinks. If the disk is not in the SCSI enclosure, the LED blink does not occur.

If the disk is in the SCSI enclosure and still if the blink does not occur, verify the health of the disk.

Enclosure component alerts

CloudByte ElastiStor provides common and specific alerts for the enclosure components such as disk slots, power supplies, voltage sensors, current sensors, temperature sensors, fans, and audible alarm.

The common alerts which apply to all components include the ones related to

  • Removal and installation of the component
  • State in which the component is, such as critical, non-critical, OK, or unrecoverable

Specific alerts are generated for the following enclosure components: power supply, voltage sensor, current sensor, and temperature sensor.

By default, CloudByte sends alerts over mail to the email you specified when you updated your profile the first time you logged in to CloudByte ElastiCenter. For details, see “Reset password and configure auto-alert options”.

To expand the mailing list, add the IDs separated by comma in the Global settings (Information Pane > Admin > Global Settings > alert.email.addresses).

To view alerts in CloudByte ElastiCenter, click Alerts in the information pane.

Deleting a Disk Array

  1. Delete all Pools in the Disk Array.
  2. In the HA Groups page, select the HA group from which Disk Array has to be deleted.
  3. For the Disk Array to be deleted, click Manage Disk Array and then click the delete icon.

Creating a Pool

Pool is physical storage device on which you store data. One or more RAID groups form the Storage Pool. Pools are created on the drives such that each Pool is owned by one of the Nodes at any given point in time. These Pools can be taken over by any other Node when needed, since the underlying drives are visible to all the Nodes.

  1. Go to the Node page (ElastiCenter > Nodes).
  2. From the list of Nodes, select the one for which you create the storage Pool.
  3. In the actions pane go to the Tasks and then, click Add Pool.

add_pool_1

The Add Pool page appears:

Create Storage pool_1

  1. Select the Site, HA Group, and Node to which the Pool belongs.
  2. Specify a name for the Pool and then click Next.
  3. In the following screen, specify the RAID storage type and then choose one or more of the available disks.
  4. Note: The list of disks displayed shows Yes if disks are Write Cache Enabled.
  5. (Optional) Enable Sector Size.

Note: For optimal performance, ensure that all the disks in a Pool belong to the same disk array enclosure.

create_storage_pool_3

    1. Click Next. The QoS settings page appears.

create_pool_qos_settings

  1. Specify the details:

Field Description
Total IOPS The maximum per second I/O limit for the Pool.
Average Latency The desired average latency in milliseconds per I/O. Latency is the round-trip time per I/O request-response as measured by the client.

  1. Click Add Pool.

Note:The number of disks required to create a Pool depends on the RAID type and protection/performance you look for. For example, for a high performance application, you can create RAID 10 Pool. Similarly for a high capacity application, you can set up RAID z1 with 8 disks.

Configuring Spare

  1. Go to the Pools page (Navigation pane > Pools).
  2. In the Actions pane, click Manage RAID Configuration. The Disk Group page appears.
  3. In the Actions pane, select Add Spare.
  4. In the Add Spare page, select a disk from the drop-down list.
  5. Click Add.

Migrating a Pool

You cannot migrate a pool. Only a VSM can be migrated.

Configuring grace

Grace is the provisioning of unused IOPS/throughput of Pools to Storage Volumes based on the performance requirements. You can configure Grace at Pool level and Storage Volume level.

For example, assume that you have a Pool with the capacity of 100 IOPS and Grace enabled. Two TSMs named TSM A and TSM B, with a capacity of 30 IOPS and 60 IOPS respectively are created under the Pool.

  • Under TSM A (with 30 IOPS capacity), Storage Volumes named E and F are created, and assigned 10 IOPS and 15 IOPS respectively.
  • Under TSM B (with 60 IOPS capacity), Storage Volume G is created and assigned 35 IOPS.
  • The grace available in this scenario is 40 IOPS.

Configuring_grace_diagram

Configuring Grace at the Pool Level

Grace is enabled by default at the Pool level. You can edit Grace after creating the Pool.

To edit,
  1. Go to the Pool page and then in the actions pane, click Settings.
  2. Click Edit and then choose to enable/disable Grace.
  3. Grace_last

Configuring Grace at the Storage Volume level

To enable Grace at the Storage Volume level, ensure that Grace is enabled at the respective Pool level.

To edit,
  1. Go to the Storage Volume page and then in the actions pane, click Settings.
  2. Click Edit and then choose to enable/disable Grace
  3. enable_grace_edit_settings (2)

  4. Click Save.

Creating an Account

Use the Account page (ElastiCenter > Accounts) to create Account.

  1. Click Add Account

The Add Account page appears.

add_account_1

  1. Specify the following details

Field Description
Name Unique name for the account
Description A meaningful description of the account
Assign Admin Select the type of administrator that you want to create.When you select an administrator type, the username and password fields appear.For details, see Delegated Administration

  1. Click Add Account.The account is created.The wizard prompts you to continue and provision TSM.
  2. Click Provision TSM to continue.

Delete account user

  1. In ElastiCenter, select Accounts in the navigation pane.
  2. From the list of Accounts, select the Account from which you want to delete a user.
  3. Go to the Tasks section of the actions pane and then select Account Users.
  4. Click the delete icon for the account user that you want to delete.
  5. At prompt, click Yes.

Setting up data access protocols

CloudByte ElastiStor provides LUN access using the following protocols:

  • Fiber Channel
  • iSCSI
  • CIFS
  • NFS

When you create a Storage Volume, you are provided with an option to select the access protocols that you want to enable.

Deleting a Storage Volume disables the protocol access services automatically.

The following sections help you configure data access protocols supported by CloudByte ElastiStor:

Data access using iSCSI

iSCSI is Internet SCSI (Small Computer System Interface), an Internet Protocol (IP)-based storage networking standard for linking data storage connections. By offering SCSI commands over IP networks, iSCSI is used to transmit data over intranets. For further details, see http://en.wikipedia.org/wiki/ISCSI.

iSCSI concepts

Authentication Group: A grouping of multiple iSCSI users.

Use this option if you use CHAP or mutual CHAP. You can configure Authentication group at both VSM and Storage Volume levels.

CHAP: An authentication method which uses a user/secret or IQNs for outgoing authentication. The Storage Volumes on CloudByte ElastiStor authenticate the initiator.

Mutual CHAP: A super set of CHAP which uses peer user/peer secret for outgoing/incoming authentication between Storage Volumes and initiator.

Initiator group: Defines who can initiate the LUN.

It is a combination of multiple IQNs. By default, CloudByte ElastiStor creates two initiator groups (all where everyone can initiate the LUN and none where no one can). After you create the Storage Volume, when you manage the iSCSI options, you are prompted to choose an initiator group. You can either select the default one or the ones that you create. You configure initiator group in the Storage Volume.

Configuring Data Access using iSCSI_1

iSCSI configuration workflow

You configure iSCSI at the following levels:

  • Account
  • VSM
  • Storage Volume

The following figure illustrates the work flow for configuring the iSCSI protocol options:

ConfiguringiSCSIprotocolOptions

Account iSCSI options

Configuring iSCSI at account level involves the following tasks:

  1. In the ElastiCenter, select Accounts.
  2. In the Accounts page, select the account for which you want to specify the protocol options.
  3. In the actions pane, select the protocol option and then specify the details.

data_access_protocol_options_iscsi

The following options are available:

Manage iSCSI Authentication Groups

In the Add Authentication Group dialog box, specify the following details:

Field Description
Name A unique name for the authentication group.
Description A meaningful description for the authentication group.
CHAP Username Username for CHAP authentication. For uniqueness, specify the initiator IQN name as username.
CHAP Secret Password for CHAP authentication in alpha-numeric format. The password must have 12 to 16 characters.
Mutual CHAP Username Username for mutual CHAP authentication. For uniqueness, specify the initiator IQN name as username. The value must be same as that of the CHAP user.
Mutual CHAP Secret Password for mutual CHAP authentication (should be different from CHAP secret). The password must have 12 to 16 characters.

Intiator Groups

In the Add Intiator Group dialog box, specify the following details:

Field Description
Name Unique name of the initiator group.
Allowed Intiator List of allowed initiators, separated by comma.
Authorized Networks List of allowed networks followed by subnet mask in the format 10.0.0.0/8, separated by comma.

VSM iSCSI Options

This is the set of iSCSI options specific to a VSM. By default, CloudByte ElastiStor creates a default VSM iSCSI options group named default which contains industry standard options.

After you create the VSM, when you manage the iSCSI options, you are prompted to choose the VSM iSCSI options group. You can either select the default one or the ones that you create.

Field Description
IQN Name Specify a unique IQN.
Number of worker threads Select the number of worker threads.
Discovery Auth Method Specify the authentication method.
Discovery Auth Group Specify the authentication group.
Timeout Sets the limit on how long an I/O can be outstanding before an error occurs. Values range from 0 to 300 with a default of 30.
NOPIN Interval  The frequency of sending a NOP-IN packet in seconds. The values range from 0 to 300. The default value is 20
MAX R2T Specify a value between 1 and 255. The default value is 32
Max Sessions Specify a value between 1 and 64. The default value is 8.
Max Connections Specify a value between 1 and 64. The default value is 16.
First Burst Length Maximum data in bytes that an iSCSI software initiator may send to the target during the execution of a single iSCSI command unsolicited. Values range from 1 to 2^32. The default value is 65,536.
Max Burst Length Maximum WRITE size in bytes the target is willing to receive between R2Ts. Values range from 1-2^32. The default value is 262,144.
Max Receive Data Segment length In bytes. Values range from 1 to 2^32 with a default of 262,144.
Max Outstanding R2T Maximum number of ready to receive packets (R2Ts) the target can have as outstanding. This is for a single iSCSI command,where larger values should yield performance increases until MaxOutstandingR2T exceeds the size of the largest Write I/O divided by MaxBurstLength. Values range from 1 to 255. The default value is 16.
Default time to wait Minimum time in seconds to wait before attempting a logout or an active task reassignment after an unexpected connection termination/ reset. Values range from 1 to 300. The default value is 2
Default time to retain Maximum time in seconds after Time2Wait before which an active task reassignment is still possible after an unexpected connection termination/reset. Values range from 1 to 300. The default value is 60.

Volume iSCSI Options

This is the set of iSCSI options specific to a Storage Volume. By default, CloudByte ElastiStor creates a default Volume iSCSI options group default which contains industry standard options. After you create the VSM, when you manage the iSCSI options, you are prompted to choose the Volume iSCSI options group. You can either select the default one or the ones that you create.

Field Description
Status Select either Enabled or Disabled.
IQN Name Specify the unique IQN.
Authentication Method Specify the authentication method.
Authentication Group Specify the authentication group.
Initiator Group Specify the initiator group.
Initial Digest Select one of the advanced data integrity options.
Block Length By default the value is set to 512 bytes.
Queue Depth Pending I/O requests for the Volume. The values range from 0-255. 0 implies that the status disabled. The default value is 32.

Configuration scenarios

The following scenarios explain iSCSI configuration in detail:

Scenario 1: Assigning the same iSCSI initiator groups to two Storage Volumes under a VSM

iSCSIConfigurations-I

iSCSI initiator groups can be configured for only Storage Volumes based on initiator groups in the account. For example, Storage Volumes under the VSM can have different iSCSI initiator groups.

Scenario 2: Assigning different authentication groups to multiple Storage Volumes under a VSM

iSCSIConfigurations

You can have different authentication groups for VSMs and Storage Volumes.

iSCSI access control workflow

An initiator group defines who can initiate the LUN. After you create the Storage Volume, when you manage the iSCSI options, you are prompted to choose an initiator group.

Data access to the iSCSI Storage Volume can be restricted to either a single machine or to multiple machines in a Subnet.

Configuring initiator group and restricting access

  1. In the ElastiCenter, select Accounts.
  2. In the Accounts page, select the account for which you want to specify the protocol options.
  3. Select Manage iSCSI Initiator Groups in the Actions pane.
  4. select_manage_iscsi_initiator_groups

  5. Select Add Initiator Group in the Tasks menu.
  6. (In the following page)Provide the required details.
  7. Field Description
    Name Unique name of the initiator group.
    Allowed Intiator List of IQNs, separated by comma for restricting the access to iSCSI Storage Volume from multiple machines in a Subnet.
    Authorized Networks List of allowed networks, followed by subnet mask in the format 10.0.0.0/8, separated by comma.
  8. Click OK.
  9. In the Storage Volumes page, select the Storage Volume to which you want to assign the initiator.
  10. Select Manage iSCSI Configuration (Actions pane > Tasks).
  11. select_manage_iscsi_configuration1

  12. Click Edit, enter the required details, and then save the changes.
  13. manage_iscsi_initiator_group_selectinitgroup

  14. At the confirmation prompt, click Modify.

iSCSI authentication workflow

An iSCSI Authentication Group is a grouping of multiple iSCSI users. You can select the users who can access the iSCSI software target. After you create users, you can group them as iSCSI users for authentication.

  1. In the ElastiCenter, select Accounts.
  2. In the Accounts page, select the account for which you want to specify the protocol options.
  3. Select Manage iSCSI Authentication Groups in the Actions pane.
  4. select_manage_authentication_group

  5. Click Add Authentication Group in the following page:
  6. Enter the required details and then save the changes.
  7. manage_iscsi_auth_group_addauthgroup_details

    Field Description
    Name A unique name for the authentication group.
    Description A meaningful description for the authentication group.
    CHAP Username Username for CHAP authentication. For uniqueness, specify the initiator IQN name as username. CHAP is an authentication method which uses a user/secret or IQNs for outgoing authentication. The Storage Volumes on CloudByte ElastiStor authenticate the initiator.
    CHAP Secret Password for CHAP authentication in alpha-numeric format.The password must have 12 to 16 characters.
    Mutual CHAP Username Username for mutual CHAP authentication. For uniqueness, specify the initiator IQN name as username. The value must be same as that of the CHAP user. Mutual CHAP is a super set of CHAP which uses peer user/peer secret for outgoing/incoming authentication between Storage Volumes and initiator.
    Mutual CHAP Secret Password for mutual CHAP authentication (should be different from CHAP secret).
    Description The password must have 12 to 16 characters.
  8. Click OK.
  9. In the Storage Volumes page, select the Storage Volume for which you want to assign the authentication group.
  10. Select Manage iSCSI Configuration (Actions pane > Tasks).
  11. select_manage_iscsi_configuration1

  12. Click Edit, enter the required details, and then click Save. In the following screen, you have selected CHAP as the authentication method.
  13. manage_iscsi_auth_group_choose_authmethod

  14. At the confirmation prompt,click Modify.

Restricting access to iSCSI VSM by managing Authentication Groups

The procedures are same as in the section Restricting access to iSCSI Storage Volume by managing Authentication Groups except that, instead of Storage Volume, you have to select VSM from step 7 onward.

Installing MPIO on Windows Server

Multipath I/O (MPIO) is a Microsoft-provided framework that allows storage providers to develop Multipath solutions that contain hardware-specific information required to optimize connectivity with storage arrays.

MPIO provides an alternate data path between storage devices and Windows operating system. MPIO is protocol-independent and can be used with Fibre Channel (FC), Internet SCSI (iSCSI) and Serial Attached SCSI (SAS) interfaces.

Installing MPIO functionality involves the following procedures:

Note: The following documentation is for Windows Server 2008. The procedures are similar for other versions of Windows Server. However, there might be minor variations owing to the differences in UI strings and navigation.

  1. On Windows Server, select Multipath I/O and then click Install (Server Manager Console > Add Features Wizard).
  2. Note: This step can be skipped if Multipath I/O is already installed.

    mpio_multipath_1

  3. Restart the Windows Server after you complete the installation.
  4. After reboot, configure Multipath as follows:
    1. Open MPIO application (Start > Administrative Tools > MPIO).
    2. Click Discover Multi-paths tab.
    3. Enable Add support for iSCSI devices.
    4. Click Add.

    mpio_configure_4

  5. In the Reboot required dialog box click Yes. After reboot, a new device called “MSFT2005IBusType 0x9” (or similar ID) appears in the MPIO Properties.
  6. mpio_mpio_properties_6

Configuring Multipath on ElastiCenter

Prerequisites:

  • In the Network Interface Cards page (Nodes> Network Interface Cards), configure static IP addresses for each interface to configure multipath.

config_static_ip

Procedures

  1. In the VSMs page, click Provision VSM and then complete the procedures to create a VSM.
  2. Select the provisioned VSM and then in the VSM page select Advanced Settings.
  3. tsm_page_advanced_settings_edit

  4. In the Advanced Settings page, click Edit. Provide the required details and then click Save.
  5. tsm_page_advanced_settings_edit

    Field Description
    Secondary IP Address Alternate IP Address to configure multipath for a single LUN.
    Secondary Subnet Subnet address for multipath configuration.
    Secondary Interface Alternate Interface to configure multipath.
  6. Provision a Storage Volume in the VSM on which Multipath I/O is configured.
  7. (In the following page) Enter the required details and complete the procedures.

Configuring MPIO on Windows Server for a LUN in ElastiStor

Adding the first path to the iSCSI target

  1. Add two target portal IP addresses of the Disk Station (iSCSI Initiator Properties > Discovery)
  2. mpio_iscsiinitiatorprop_12

  3. Select a target that uses MPIO and then click Log On (iSCSI Initiator Properties page > Target
  4. Select the option Automatically restore this connection when the computer starts.
  5. Select the option Enable multi-path.
  6. Click Advanced.
  7. mpio_iscsiinitiatorprop_logon_13

  8. In the Advanced Settings page, check the following options:
    • Microsoft iSCSI Initiator.
    • First Subnet of the Initiator Computer
    • First Subnet of the DiskStation (both the IP addresses of the initiator and the target are within the same Subnet)
    • Click OK and ensure that the target has been connected.

    mpio_advancedsettings_14

  9. Close the iSCSI Initiator Application.

Adding the second path to the iSCSI target

  1. In the iSCSI initiator properties page:
    1. Select the Target to use MPIO (ensure that it is connected).
    2. Click Log on.
  2. mpio_logon2_15
  3. In the Advanced Settings page, check the following:
    1. Microsoft iSCSI inititator
    2. Second Subnet of the Initiator Computer
    3. Second Subnet of the DiskStation (both the IP addresses of the Initiator and the Target are within the same Subnet).
    4. Click OK.
  4. mpio_advancedsettings_OK_16
  5. Select Details in the iSCSI Initiator Properties page.
  6. mpio_iscsiinitiatorprop_details_17
  7. In the Target Properties page, click Devices tab.
  8. mpio_targetprop_devices_18
  9. Select a device name and then click Advanced.
  10. mpio_targetpropadvanced_19
  11. Select a load balance policy and then click OK. The following screenshot shows Round Robin with Subset as the Load balance policy.
  12. mpio_devicedetails_mpio_20

Data access using CIFS

The following workflow explains how to configure CIFS options:

configuringCIFSprotocolOptions

Configure VSM CIFS options at the VSM level. File system CIFS options can be configured at the Storage Volume level (if you have enabled the protocol option).

VSM CIFS options

By default, CloudByte ElastiStor creates a default VSM CIFS options group with industry standard options.

After you create the VSM, when you manage the CIFS options, you are prompted to choose the VSM CIFS options group. You can either select the default one or the one that you create.

Field Description
Authentication Model By default the Authentication Model is user.
NetBIOS Name A unique name for the VSM CIFS options template.
Server Description A meaningful description of the VSM CIFS options template.
Workgroup The workgroup that the server will appear to be in.
DOS Charset The character set that is used while communicating with the Windows clients. The default is CP 437.
UNIX Charset The character set that is internally used. The default is UTF-8.
Log Level Sets the amount of log/debug messages that are sent to the log file. Default is Minimum. Keep it this way for best performance unless more information is needed for troubleshooting.
Time Server Determines whether or not ElastiStor advertises itself as a time server to Windows clients.

File system CIFS options

By default, CloudByte ElastiStor creates a default file system CIFS options group with industry standard options. After you create the Storage Volume, when you manage the CIFS options, you are prompted to choose the Storage Volume CIFS options group. You can either select the default one or the one that you create.

Option Description
Status If Enabled, CIFS Share can be accessed. If Disabled, CIFS Share cannot be accessed.
Name A unique name for the file system CIFS options template.
Description A meaningful description of the CIFS options template.
Read Only If checked, prohibits write access to the share.
Browseable If selected, clients when they browse the shared directory using Windows Explorer, can see the list of shares. If unselected, client has to explicitly specify the full server path in Windows Explorer.
Inherit Permissions If selected, permissions on new files and directories are inherited from parent directory.This option is (particularly) helpful in scenarios where there are large systems with many users involved. Inheriting permissions let a single home share to be used flexibly by each user. Leave this unselected if Type of ACL is set to Windows in the Volume’s permissions.
Recycle Bin If selected, instead of purging the files, they are moved to recycle bin on deletion.
Hide Dot Files Dot files (unlike on UNIX) appear on Windows. Select the option to hide the Dot files.
Hosts Allow Host-based protection feature. Comma-separated or space separated list of IP addresses that are allowed to access the shares. If nothing is specified, the default value ALL applies.
Hosts Deny Host-based protection feature. Comma-separated or space separated list of IP addresses that are denied access to the file system. If you specify ALL, IP Addresses that are not listed in the Host Allow field are denied permission.

CIFS authentication workflow

A CIFS Authentication Group is a grouping of multiple CIFS users. You can select the users who can access the CIFS share.

  1. In the ElastiCenter, select Accounts.
  2. In the Accounts page, select the account for which you want to specify the protocol options.
  3. Select Manage CIFS Authentication Groups in the Actions pane.
  4. select_manage_cifs_auth_group

  5. Click Add Authentication Group in the following page.
  6. Specify the required details and then click OK.
  7. cifs_auth_group_specify_details

    Field Description
    Name A unique name for the authentication group.
    Description A meaningful description for the authentication group.
    User name Specify a name for the user.
    Password Specify a password for the user.
    Full name Specify full name of the user.
  8. In the VSM page, select the VSM for which you want to assign the authentication group.
  9. Select Manage CIFS Configuration (Actions pane > Tasks).
  10. cifs_auth_group_manage_cifs_configuration

  11. Click Edit, select a Discovery Authentication Group from the drop-down list and then click Save.
  12. cifs_auth_discovery_auth_group

  13. In the confirmation prompt, click Modify.

Data access using FC

Fiber Channel (FC) Protocol is the standard transport protocol for delivering serial SCSI commands over Fiber Channel interconnects. Fiber Channel Protocol is designed to operate in a highly-efficient manner using hardware for protocol offload engines (POEs). Fiber Channel is fast, reliable, and scalable data transport system. For further details, see http://en.wikipedia.org/wiki/Fibre_Channel.

Supported Hardware for Fibre Channel

QLogic HBA is used by CloudByte as FC targets. The client can use any available HBAs in the market (such as Emulex or Brocade).

For more information, see the “Hardware Compatibility List”. 

FC in CloudByte ElastiStor

The following figure illustrates how you configure the FC setup in CloudByte ElastiStor:confg_fc_setupi

Access over FC protocol involves an initiator group and a target group. Initiator represents the client, for example a Windows client and target is the CloudByte Node.

FC Initiator group

An FC initiator group is the list of initiators who are authorized to access the FC LUN. By default, CloudByte creates a default initiator group named none that does not allow access to any LUN. You can create the initiator group, add initiators, ports, and mask the LUNs to that initiator added.

The initiator group is a list of WWPNs. You can create the initiator group, add initiators and ports, and then mask the LUNs to the added initiator.

You create the initiator group at the account level and assign it at the Storage Volume level.

FC Target group

You group the FC target ports to form a target group. This means, all the FC target ports which you have grouped are used for this particular group. The Node’s WWPNs uniquely identify each target port on the system. By default, CloudByte creates a default target group named ALL that allows access to all targets. You can create a new initiator group and replace the default one.

You create the target group at the account level and assign it at the Storage Volume level.

Creating an initiator group

  1. In ElastiCenter, select Accounts.
  2. In the Accounts page, select the account for which you want to specify the protocol options.
  3. In the Action Pane, select Access Protocol Options > Manage FC Initiator Group.
  4. manage_fc_initiator_groups1

  5. Refresh Hardware (Nodes > select the specific Node> select Refresh Hardware in the Tasks section of the task list).

    Note: Step 4 applies only if you have added FC ports to the Node after adding the Node to the HA Groups.

  6. In the following page, click Add Initiator Group.
  7. Specify a unique name and select the appropriate WWPNs of the FC initiators to form the group.
  8. fc_initiator_group

  9. Click Add.

Creating a target group

  1. In ElastiCenter, select Accounts.
  2. In the Accounts page, select the account for which you want to specify the protocol options.
  3. In the Action Pane, select Access Protocol Options > Manage FC Target Group.
  4. Refresh Hardware (Nodes > select the specific Node> select Refresh Hardware in the Tasks section of the task list).

    Note: Step 4 applies only if you have added FC ports to the Node after adding the Node to the HA Groups.

  5. In the following page, click Add Target Group.
  6. Specify a unique name and a comma-separated list of WWPNs to form the group.
  7. Click Add.

Assigning Storage Volume to initiator groups/target groups

  1. In the Storage Volumes page, select the Storage Volume for which you want to assign the initiator group/target group.
  2. In the Actions pane, select Tasks > Manage FC Configuration.
  3. In the FC Configuration page, click Edit and then replace the default initiator/target group.
  4. manage_fc_configuration_editsettings_2

  5. Click Save.
You can also perform the same task at the Account level (Accounts > select Account > Manage FC Initiator Group/Target Group).

Data access using NFS

Network File System (NFS) allows a server to share directories and files with clients over a network.

The following section details the setup:

VSM NFS options

  1. In the VSM Page, click Manage NFS Configuration (Actions > Tasks).
  2. (In the following page) Click Edit, change the Number of NFS Worker Threads, and then save the settings.

File system NFS options

  1. In the navigation pane, select Storage Volumes.
  2. In the Storage Volume page, select the Storage Volume for which you want to specify the NFS options.
  3. In the following page, select Manage NFS Configuration in the Tasks section of the Actions pane.
  4. select_mangage_nfs_configuration

  1. In the NFS clients page, click Add NFS Clients.
  2. add_nfs_clients

  3. Specify the following options:
Option Description
Network/IP addresses Single Network ID with subnet mask (for example,10.10.1.100/8). You can also provide space-separated list of IP addresses for which access has to be provided (for example,10.20.10.120 10.20.10.121) instead.
Map as Root Users Yes restricts all users to root.
Read-only Yes prohibits writing to the share.

  1. Click Add.

Provisioning a VSM

VSM is a Virtual storage controller capable of hosting Storage Volumes and LUNs. VSMs are the fundamental units of ElastiStor and the logical containers for holding performance parameters and logical storage. For all practical purposes, VSMs are equivalent of self-contained hardware storage boxes.

Use either the Create Account wizard or Virtual Storage Machines page (ElastiCenter > Virtual Storage Machines) to provision VSM.

  1. Click Provision VSM.

Provision_TSM_1

The Provision VSM page appears.

Provision_TSM_2

  1. Specify the following details:

Field Description
Account The account for which you create the VSM.
Name A unique name for the VSM.
Capacity The amount of disk space to be allotted for the VSM.
Total IOPS The maximum per second I/O limit for all QoS groups you define for the VSM.
Total Throughput Select to control throughput. If selected, the option Total Throughput appears. Specify the throughput in Kbps. This is the maximum throughput for all QoS groups you define for the VSM.

  1. Click Next and then specify the provisioning details by selecting a Pool from the list.

Provision_TSM_3

  1. Click Next.
  2. Select the network interface, specify the tenant IP address, and default Gateway.

Provision_TSM_4

  1. Click Provision VSM.

Multipathing

Multipathing is the ability to configure a server with multiple paths to the storage for take over on network failure. CloudByte ElastiStor supports multipathing for iSCSI. When network failure occurs, redundant network takes over and ensures that the iSCSI LUN is available.

Note: SATA disks or any disk with SATA interface is not supported for HA and multipathing configuration.

The details of the supported Maximum Multiple Connections (MCS) per LUN are as follows:

  • 8 connections per LUN
  • 16 sessions per LUN

To enable multipathing,

  1. In ElastiCenter, select Virtual Storage Machine.
  2. In the VSM page, select the VSM for which you want to enable multipathing.
  3. In the action pane, select Advanced Settings.
  4. Click Edit.
  1. Specify the required details.

provision_tsm_5

Field Description
Secondary IP address Provide secondary IP address to enable multipathing.
Secondary Interface Select an interface from the list.
  1. If partial failover of Pool is enabled (which is enabled by default), click yes at the prompt to disable it.

Configuring VSM migration

The objective of VSM migration is to optimize QoS. VSM migration helps to control the QoS parameters within a Pool and to move data.

You can migrate VSM from a Pool to another within the same Node or to a different Node. Also, you can migrate VSMs across Sites.

To migrate VSM,

  1. In the VSM page, select a VSM from the list.
  2. In the actions pane, click Schedule.

migrate_vsm_schedule

  1. In the following page, specify the required details:

migrate_vsm_schedule_1

Field Description
Site Select a Site to migrate the VSM.
IOPS The IOPS of the primary VSM is populated by default. You can modify the value to provision IOPS required for migration.
Throughput The throughput of the primary VSM is populated by default. You cannot modify this value as this depends on IOPS and Block Size.

  1. Click Next. 
  2. Select the Pool to migrate VSM and then click Next. 

configuring_vsm_migration_select_pool_3

  1. Select the Backup interface, IP Address, and schedule of migration (in the format minutes/hours/days/month/year).

configuring_tsm_migration_specify_backup_interface_4

    1. Click Add to create migrant VSM.

Migrant VSM activation

Activation consideration

  • The Migrant VSM can be activated only after the base snapshot is successfully transferred from the primary VSM. You can check the status of data transfer by clicking View Transfer Status (Actions > Tasks).
  • The backup interface and IP address range of the native and the migrant VSMs must be same.

Note: After activation, this backup IP address will not be active and therefore need to be removed at the Pool level.

  1. In the migrant VSM page, click Settings in the Actions pane. migrant_vsm_settings
  2. In the Settings page, click Edit and then select an interface from the drop-down list.migrant_tsm_select_interface
  3. Click Save.
  4. Click the VSM, the Migrant VSM, and then click Activate.tsm_migration_activate
  5. At prompt, click Yes.

After the VSM migration is active, the re-mount prompt appears. Ensure that you re-mount the Storage Volumes before you proceed. For details, see Connecting to ElastiStor.

Provisioning storage

  • Before you provision a Storage Volume, you must create a VSM.
  • The maximum supported size of the Storage Volume depends on the available capacity of VSM.
  • There is no limit to the number of Storage Volumes that you can create. But the composite capacity of the created Storage Volumes must be less than or equal to the capacity of the VSM they belong to. For example, if the total capacity of the VSM is 1 TB, then you can create a Storage Volume with the capacity of 1 TB or multiple storage volumes where the total capacity of all volumes is less than or equal to 1 TB.
  • You can enable both data compression and data deduplication on the same Storage Volume.
  • File system storage (NFS and CIFS) works together on the same Storage Volume, but block level storage (iSCSI or FC) does not.
  • You can back up Storage Volume by creating snapshots and then rolling back when required. For details, see Configuring local backup.

Note: By default, ElastiStor Storage Volume is thin provisioned. You can expand the Storage Volume up to the size of the Pool, provided the Pool has available storage.

Use the Storage Volumes page (ElastiCenter > Storage Volumes) to provision storage.

  1. Click Provision Storage.

provision_storageclick_1

  1. The Add Storage Volume page appears.

provision_storage_specifydetails_2

  1. Specify the following details:

Field Description
Account Account for which you provision the storage.
Name Unique name for the storage.
Capacity Amount of disk space to be allocated.
Provision Mode Shared or Dedicated.
Block Size Block size of the volume.
Average Latency Desired average latency in milliseconds per I/O. Latency is the round trip time per I/O request-response.
Required IOPS Select the required IOPS using the slider.

  1. Click Next and then select the VSM on which you want to provision the Storage Volume.

provision_storage_selectTSM_31

  1. Click Next. The screen to specify the advanced settings appears.

provision_storage_advancedsettings_4

  1. Specify the following details:

Field Description
Volume Hierarchy The VSM on which the Storage Volume is mounted.
Record Size The block size to which data has to be divided.
Synchronization Leave the default settings as it is.
Deduplication If ON, new data is deduplicated.
Compression If ON, new data is compressed.
Mount Point (Applies only for NFS and CIFS) Specify the Storage Volume mount point for the client to use the storage.
Enable NFS Select to access the Volume using NFS protocol.
Enable CIFS Select to access the Volume using CIFS protocol.
Enable iSCSI Select to access the Volume using iSCSI protocol.
Enable FC Select to access the Volume using FC protocol.

  1. Click Provision.

Note: Disconnect all associated clients before you delete an iSCSI Storage Volume.

Choosing a Pool to provision VSM

CloudByte ElastiStor follows a QOS-centric approach to provisioning. When you provision a VSM, your choice of the Pool depends on the availability of Pools that satisfy the required throughput and IOPS.

Selecting the Pool

  1. In the ElastiCenter navigation pane, click Tenant Storage Machine.
  2. Click Add VSM.
  3. After you specify the VSM details such as Name and the QoS details, click Next.
  4. In the following screen, select the Pool after evaluating the IOPS.
  5. Click Next to specify the Network details.

Choosing a VSM to provision Storage Volume

When you provision storage, your choice depends on the availability of VSMs that satisfy the required throughput and IOPS.

To provision storage,

  1. In ElastiCenter, click Storage Volumes in the navigation pane.
  2. Click Provision Storage.
  3. In the following screen, specify the basic storage details and then click Next.
  4. Select a VSM that satisfies the QoS requirements. The graphical representation helps you with the IOPS data.
  5. Click Next and then proceed to complete the provisioning.

Auto-Provisioning

ElastiStor can automate Node selection and resource allocation if you provide the required SLA/QoS parameters. Sensing the level of storage performance and capacity the application requires, ElastiStor automatically allots the right Pool.

Auto-provisioning is particularly helpful when you have innumerable Pools/VSMs. CloudByte ElastiStor chooses the appropriate Pool/VSM for provisioning automatically.

How to auto-provision

  1. In ElastiCenter, select Global Settings.
  2. auto_provisioning_global_settings

  1. Click the Edit icon for provisioning.sb.auto and provisioning.tsm.auto.
  2. In the Value column, specify yes (instead of the default no which implies provisioning is manual) as shown in the following screen:

Auto-Provisioning_2

Example

Assume that auto-provisioning is enabled and there are three Pools (pool1 with 500 IOPS, pool2 with 400 IOPS, and pool3 with 300 IOPS respectively). If the administrator wants to create a VSM with 100 IOPS, pool1 (the Pool with the highest IOPS value) is automatically selected for VSM creation.

Modifying QoS after provisioning VSM

Assume that you have provisioned storage for a VSM and now you want to change the QoS settings. For example, your pool has an IOPS limit of 100. You have provisioned VSM with 50 IOPS. You can modify the values.

Note: In the example, you can increase the value up to 100 (which means, the entire IOPS is consumed).

To modify the QoS settings,

    1. In the ElastiCenter, select Virtual Storage Machines.
    2. Select the VSM for which you want to modify the QoS settings.
    3. In the QoS settings section of the actions pane, click Basic Settings. The highlighted section displays the QoS-related settings.
    4. Modifying-QoS-after-Provisioning-TSM-1

    5. Click the Edit icon and then modify the editable fields.
    6. Click Apply.

    Modifying QoS after provisioning Storage Volume

    1. In ElastiCenter, select Storage Volumes.
    2. Select the Storage Volume for which you want to modify the QoS settings.
    3. In the Storage Volume page, click Settings.

    modify_qos_storagevolume_settings

    1. Click the edit icon and then modify the QoS details.

    Modifying-QoS-after-you-Provision-Storage-Volume_2

    1. Click Save.

    Modifying storage capacity

    1. In ElastiCenter, select Storage Volumes.
    2. Select the Storage Volume for which you want to modify the storage capacity.
    3. In the following page, click Settings.
    4. In the following screen, click Edit and then modify the quota.
    5. modifying-storage-capacity_2

    6. Click Save.
    7. Note: The quota of the Storage Volume cannot exceed the VSM size.

Configuring High Availability

CloudByte ElastiStor supports High Availability in two-way, three-way, and four-way configurations.

Note: SATA disks or any disk with SATA interface is not supported for HA and multipathing configuration.

HA prerequisites

Ensure the following on all Nodes in the HA Group:

  • JBOD (same capacity disks) is shared among all the Nodes in the HA Group
  • Same NIC (for example, if em0 is the interface used on one Node, the same should apply for all Nodes)
  • Same system hardware configuration
  • Identical SAS HBA (identical firmware and driver)
  • Identical FC HBA (identical firmware and driver)

Procedures

The following procedures explain how to configure a two-way High Availability setup:

  1. Set up your hardware. For details see Hardware setup diagram for High Availability.
  2. Create a Site. For details, see Creating a Site.
  3. Create an HA Group. For details, see Creating an HA Group.
  4. When you specify the IP address range while adding the HA Group, ensure that you specify a range that matches the number of Nodes you add.

  5. Add a Node (Node1). For details, see Adding a Node.
  6. Label shared disks. For details, see Configuring Disk Array Enclosure.
  7. Note: You can perform this step later, after you add all other Nodes. In that case, you have to refresh the hardware (Nodes > select specific Node > select Refresh Hardware in the Tasks section of the action pane) for labeling to take effect.

  8. Add Node 2. For details, see Adding a Node.

Now you have established a two-way HA. The following screen provides a visual representation of the configuration.

HA_group_2_node

Proceed to create Pools, VSMs, and Storage Volumes.

Hardware setup diagram for High Availability

Hardware_setup_diagram_HA

Bringing Node to maintenance mode

When you want to service your Node, change its status to maintenance mode. In this mode, the Node is up and controlled by the administrator, but is not an active part of the High Availability Group.

To bring a Node to maintenance mode,

  1. Select the Node that you want to bring to maintenance mode (ElastiCenter > Nodes).
  2. In the Node Page, go to the actions pane and then click Move to maintenance icon.
  3. maintenance_mode

    The Change State of Node dialog box appears.

  4. Select Maintenance as the state.
  5. Optionally specify a reason for changing the state and then click OK.

Take Over

When Node failure occurs, takeover happens as illustrated in the following screens:

  • The following screen depicts the Node Page that lists a two-way HA. Here, Node2 is in maintenance mode.

node_in_maintenance_mode

  • In the following screen, Node1 has taken over.

nodes_list

Note: In ElastiStor, every Node has a designated partner. If the Node goes down, the resources of that Node are failed over to the partner Node.

Making a Node available

After a downtime, when you bring up the Node, you have to manually change the status to Available.

  1. Select the Node that you want to bring up (ElastiCenter > Node).
  2. In the Node page, go to the actions pane and then click Move to available icon.
  3. Select Available as the state.
  4. Optionally specify a reason for changing the state and then click OK.

HA Jobs

To view the details of the past High Availability events, perform the following procedures;

  1. (In ElastiCenter)In the HA Groups page, select an HA Group for which you want to view event details.
  2. In the Actions pane, click View Jobs.

select_view_jobs

You can view the details of the past HA events and the time taken to perform these events as shown in the following screen:

View_job_details

Configuring local backup

Backup refers to copying and archiving of data. In the event of data loss, you can use the backup to restore the original data.

You can create a

  • Snapshot, which is a read-only virtual copy of your Storage Volume and VSM.
  • Clone, which is a real copy of your Storage Volume

In CloudByte ElastiStor, backup operates as follows:

  • The first backup is a full backup.
  • The first backup is followed by incremental backups based on snapshot technology.
  • Incremental snapshots can consume volume space. If the incremental data is major, large volume size will be consumed for snapshots. CloudByte recommends you to dedicate 30 percent of your Volume space for snapshots.
  • Snapshots are captured at the Storage level. They may not be application consistent.
  • Ensure that the application is in quiesce mode before you capture a snapshot.

ElastiStor supports continuous production during snapshot recovery of a Storage Volume.

Backing up VSM

  1. In ElastiCenter, select Virtual Storage Machines in the navigation pane.
  2. From the list, select the VSM to create local backup.
  3. In the following page, go to the Backup section of the actions pane and then select either of the following options:
  • Schedule: Schedule your backup by choosing a frequency.
  • Snapshot: Manually create a snapshot on demand.

configuring_local_backup_options_1

Add schedule

  1. In the Backup section, click Add Snapshot schedule. The Add Snapshot Schedule page appears.
  2. Specify the following details and then click Add.
  • Name: A unique name for the backup schedule.
  • Retention Copies: Specify the number of backup copies that you want to create.
  • Schedule:Select the frequency.
Backup best practice

As a best practice, CloudByte recommends a multiple backup schedule.

For example, you can configure a multiple backup schedule comprising

Frequency Retention copies
Every 15 minutes 4
Every hour 24
Every day 30

Add snapshot

  1. In the Backup section, click Create Snapshot.
  2. In the Create Snapshot dialog box, specify a unique name.
  3. Click OK.

View snapshots and schedules

To view the snapshots and schedules that you have created, click View Schedules/View Snapshots in the backup section. You have options to rollback and disable the schedules/snapshots.

Restore snapshots

  1. In ElastiCenter, select Virtual Storage Machines in the Navigation pane.
  2. From the list of VSMs, select the one for which you want to restore data.
  3. In the following page, go to the Backup section of the task pane and then click Manage Snapshots.

Backing up Storage Volume

  1. In ElastiCenter, select Storage Volume in the Navigation pane.
  2. From the list, select the Storage Volume to create snapshot.
  3. In the following page, go to the Local Backup section of the actions pane and then click Create Snapshot.

cinfiguring_localbackup_storagevolume_1

  1. In the Create Snapshot dialog box, specify a unique name for the snapshot and then click OK.

Restoring Snapshots at Volume level

  1. In ElastiCenter, select Storage Volumes in the navigation pane.
  2. From the list, select the Storage Volume to restore data.
  3. In the following page, go to the Local Backup section of the actions pane and then click Manage Snapshots.

configuring_local_backup_managesnapshots_1

  1. From the list of snapshots, select the one that you want to restore, click the restore icon, and then confirm at prompt.

local_backup_click_restore_icon1

Note: The time required to create a snapshot depends on the size of the changed data.

Cloning the Storage Volume

You can create a READ/WRITE copy of your Storage Volume using the clone option. Unlike Snapshot which is a read-only virtual copy, clone is a real copy of your Storage Volume. It consumes the same disk space as the parent Storage Volume.

ElastiStor uses snapshot as the point of reference for your clone. The workflow is as follows:

  1. Create a Storage Volume.
  2. Create a snapshot.
  3. Create a Clone of the Storage Volume using Snapshot as the point of reference.

Creating a clone

  1. In ElastiCenter, select Storage Volume in the navigation pane.
  2. From the list, select the Storage Volume to create a clone.
  3. In the following page, go to the actions pane and then select Local Backup > Create Snapshot.
  4. In the Create Snapshot dialog box, specify a name and then click OK.
  5. Click Manage Snapshot (actions pane > Local Backup).
  6. From the list of snapshots, go to the one which you want to use as reference for creating the snapshot and then click the Clone icon (highlighted in the circle).
  7. local_backup_click_clone_icon

  8. Specify a unique clone name, where to mount the clone, and then click OK.

Configuring remote disaster recovery

The disaster recovery mechanism in CloudByte ElastiStor helps you effectively retrieve data in disaster situations.

Currently, ElastiStor supports disaster recovery for a single Site. You can rebuild a primary Site using the disaster recovery copy. ElastiStor provides disaster recovery across WANs.

Setting up remote disaster recovery

  1. In the ElastiCenter navigation pane, click Virtual Storage Machines.
  2. From the list of VSMs, select the one for which remote disaster recovery has to be configured.
  3. In the actions pane, click Create DR VSM in Remote Backup.
  4. Note: This option is available only if you have not created a disaster recovery VSM (DR VSM). If a DR VSM is already created, you can modify the settings.

    remote_backup_create_dr_tsm

  5. In the Add DR VSM page, 
    1. Select the Site on which you want to configure DR VSM.
    2. Specify a name for the DR VSM.
    3. Click Next.
  6. In the following page, specify the Pool and then click Next.
  7. Select the Backup interface, IP Address, and specify a schedule for the DR VSM (in the format minutes/hours/days/month/year).
  8. Click Add.

A message appears to confirm that the DR VSM has been added.

Managing remote disaster recovery

For a specific VSM, use the Remote Backup section in the actions pane to configure remote disaster recovery.

  1. In the ElastiCenter navigation pane, click Virtual Storage Machines.
  2. From the list, select the VSM to manage remote disaster recovery.
  3. In the actions pane, use the options in the section Remote Backup.
  4. remote_backup_manage_dr_tsm

Disaster Recovery options

  • Name: Provides details of the secondary node and displays the transfer details.
  • Disable Transfer: Select and confirm to disable disaster recovery.
  • Edit Schedule: Edit the disaster recovery schedule.
  • Delete DR VSM: Remove a disaster recovery setup that you have configured.

Recovering data

Note: The DR VSM can be activated only after the base snapshot is successfully transferred from the primary VSM. You can check the status of data transfer by clicking View Transfer Status (Actions > Tasks).

  1. In the ElastiCenter navigation pane, click Virtual Storage Machines.
  2. From the list of VSMs, select the DR VSM that is associated with the Primary VSM where the disaster occurred.
  3. In the DR VSM page, go to actions pane and then click Tasks > Activate.
  4. remote_backup_click_activate

  5. In the Network settings dialog box, specify the network details of the DR VSM and then click OK.
  6. image (6)
  7. At the confirmation prompt, click Yes.
After you activate the DR VSM, the re-mount prompt appears. Ensure that you re-mount the Storage Volumes before you proceed. For details, see Connecting to ElastiStor.

Upgrading a High Availability DR setup

Follow the procedures to seamlessly upgrade a High Availability disaster recovery environment.

Node 1 and Node 2 imply the nodes on primary cluster. Similarly, DR Node 1 and DR Node 2 imply the nodes on the secondary cluster:

  1. Upgrade ElastiCenter. For details, see Upgrading to CloudByte ElastiStor 1.4 Patch 3.
  2. Move the Node 1 to maintenance mode. For details, see Configuring High Availability.
  3. Upgrade Node 1. For details, see Upgrading to CloudByte ElastiStor 1.4 Patch 3.
  4. Bring the Node 1 to Available mode. For details, see Configuring High Availability.
  5. Move the Node 2 to Maintenance mode.
  6. Upgrade Node 2.
  7. Bring the Node 2 to Available mode.
  8. Move the DR Node 1 to Maintenance mode.
  9. Upgrade DR Node 1.
  10. Bring the DR Node 1 to Available mode.
  11. Move the DR Node 2 to Maintenance mode.
  12. Upgrade DR Node 2.
  13. Bring the DR Node 2 to Available mode.

Confirm if the DR Transfer occurs after the upgrade as scheduled. In the case of any exceptions, contact CloudByte Technical Support.

Assuring Quality of Service

Introduction

Assuring quality of service makes your storage performance predictable. CloudByte ElastiStor is unique in its QoS offering as it lets you

  • Easily commission storage with guaranteed IOPS at various levels. You can decide to configure QoS at a Pool level, TSM level, or Storage Volume level.
  • Configure multidimensional QoS involving IOPS, throughput, latency, and capacity.
  • Utilize untapped system resources. For example, assume that have three TSMs but only one is active. In this case, the active TSM can use the entire system’s capability.
  • On-demand modification of settings without system restarts.

Choosing your QoS

The following points help you choose an appropriate QoS:

Endpoint: Decide at what level you want to implement QoS.

Select a capable pool: Based on TSM’s requirements, you provision it on a capable Pool that can meet the requirements. Define the pool level QoS, based on Pool configuration and the controller level. QoS is determined based on the Pool capacity, which is the underlying storage capability.

QoS provisioning: Understand your TSM’s QoS requirements across the data access and data protection needs. Based on the requirement of the TSM, you can either choose QoS automatically or manually. Ensure that you are aware of the Pool settings and how effectively you want to use it at the TSM level.

Sub-divide QoS: Within a TSM, based on varying needs, further sub-divide QoS across Storage Volume, based on the guarantee that the administrator wants to set. For example, when a TSM is used to store logs in the database, since logs need higher IOPS and lower throughput and latency, set it accordingly. Whereas a database requires low IOPS, high throughput, and high latency.

Configuration

Use ElastiCenter to configure QoS settings. The configuration can be at the following levels:

  • Pool: For details,see Creating a Storage pool.
  • Account: For details, see Creating an Account.
  • TSM: For details, see Provisioning TSM.

Configuring Grace

What is Grace

Grace is the provisioning of unused IOPS/throughput of Pools to Storage Volumes based on the performance requirements. You can configure Grace at Pool level and Storage Volume level.

For example, assume that you have a Pool with the capacity of 100 IOPS and Grace enabled. Two TSMs named TSM A and TSM B, with a capacity of 30 IOPS and 60 IOPS respectively are created under the Pool.

Configuring_grace_diagram
  • Under TSM A (with 30 IOPS capacity), Storage Volumes named E and F are created, and assigned 10 IOPS and 15 IOPS respectievely.
  • Under TSM B (with 60 IOPS capacity), Storage Volume G is created and assigned 35 IOPS.
  • The grace available in this scenario is 40 IOPS.

Configuring Grace at the Pool level

Grace is enabled by default at Pool level. You can edit Grace after creating a storage Pool.

  1. Go to the pool page and then in the Actions pane, click Settings
  2. Edit the settings and enable/disable Grace.

Monitoring QoS

QoS monitoring features will be available in the future releases.

QoS tips

Storage capacity

Discs, storage Connectivity, and type

Capability: Ensure that you are well aware of the capabilities of your storage subsystem. For example, the right interconnection between the controller and storage, the type of disks on the disk array, and the ability to expand the capacity.

Limitations: Ensure that you have assessed the limitations. For example, increasing storage capacity does not make any sense if the network does not support.

Controller characteristics

RAM, CPU, and network:

CPU: If the storage is more I/O bound than CPU bound, it is more effective. CPU load should not be more than 60-70 percent, or you add more cores.

RAM: RAM determines the ability to cache. Larger RAM means more filesystem caches. In a READ-centric scenario, larger RAM helps generate better QOS. That is, more I/O and throughput but lesser latency.

Network: Network capacity decides data access and data protection. Assure adequate network bandwidth to export performance to clients. Network should do justice to the storage system.

Segregation: Segregate data access and data protection so that protection workloads do not interfere with data access workloads.

Pool Creation

Storage group tips

As a best practice, create storage with 8 to 10 disks.

When you add storage groups, keep them identical. For example, do not add disparate groups to the same Pool. For example, if a group has SATA disks, and another group has SAS disks, then do not assign both to the same Pool. That is, do not create hybrid Pools.

Multiple Pools within a Controller

Tips to avoid contention points: Be judicious when you add multiple Pools to a controller. For example, it does not make sense if network bandwidth is already utilized to the maximum with the existing Pools, or CPUs are already busy serving the existing Pools. QoS also suffers because of over provisioning.

When to combine multiple pools: When no conflict pertaining to bandwidth, CPU, or Memory exist, you can combine Pools.

Optimizing QoS

Disk characterstics: Better the disk characteristics, better the QOS. For example, the IOPS, throughput, and latency of SATA disks are not as good as that of SS disks.

Disk layout: Better the disk layout, better the QoS. For example, keep the disk layout to 8 to 10 disks.

Improving WRITE performance: If the application requires synchronous WRITES, associate high performing disk to the Pool to speed up the WRITEs. This guarantees better QOS.

Improving READ performance: To improve the READ performance or increase the filesystem cache hit rate, add high performing disks as cache devices to the Pool.

CloudByte ElastiStor plugin for VMWare vCenter

Introduction

VMware vCenter administrators, you can perform the following tasks, performed using CloudByte ElastiCenter, in the vCenter console itself. CloudByte provides a plugin to create, configure, and manage all ElastiCenter tasks.

  • Mount an NFS datastore created in ElastiCenter and then create VMs under the datastore.
  • Manage QoS properties for each VM.

CloudByte lets you manage your VMs based on two major features Shared QoS and Dedicated QoS. For details, see QoS FAQs.

The following topics explain how to install and use the ElastiStor plugin for vCenter.

Pre-requisites

  • CloudByte-plugin.exe (the client-side CloudByte installer)
  • vCenter client (installed on your desktop)
  • .NET Framework 4.0
  • Windows operating system ( Windows 7 Professional, Windows XP, or Windows 2008 R2)

Installing CloudByte vCenter plugin

  1. Insert the CloudByte plugin installation disk into your computer’s DVD or CD drive.
  2. Right-click the CloudByte-plugin.exe and then select Run as administrator.

1

  1. Select the default installation path and then click Yes.

Vcenter-2

The following message appears on successful installation:

Vcenter-3

    1. In the powerCLI command prompt, run the following command: Set-ExecutionPolicy Unrestricted.
    2. Run the following command to verify if the execution policy is set to unrestricted mode: Get-ExecutionPolicy.
    3. On your desktop, double-click the CloudByte plugin icon.

This installs PowerCLI (if not already installed) and displays the shortcuts on the desktop and the CloudByte registration form appears.

Vcenter-4

  1. Specify the VCenter server credentials.
  2. Click OK to confirm.

Vcenter-5

  1. Log in to vCenter server and then select Plug-ins > Manage Plug-ins.
  2. In the Plug-in Manager, see if ElastiStor plugin is listed.

Vcenter-6

Plug-in tips

Ensure the following:

  • A bin folder is created under C:\Program Files (Program Files (x86) for 64-bit)\VMware\Infrastructure\Virtual Infrastructure Client\Plugins\bin.
  • You have specified the VCenter credentials correctly; else the plugin fails.
  • When you modify the VCenter credentials, ensure that you register the credentials (as explained in Step 1). The credentials are created in the folder C:\Documents and Settings\Administrator\Application Data\VMware\credstore.

Configuring CloudByte vCenter plugin

  1. In the vCenter home page, click CloudByte Administration icon to register the CloudByte Control Station.

Vcenter-7

  1. In the following screen, Click Add and then specify the CloudByte Management Station account details.

Vcenter-8

  1. In the vCenter home page, select Datastore Clusters (Inventory > Datastores and Datastore Clusters).
  2. Right-click the datacenter and then select New CloudByte Datastore.

Vcenter-9

  1. In the following page, select the datacenter/Node and then click Next.

Vcenter-10

  1. Enter the Datastore Name and then click Next.

Vcenter-11

  1. Select CloudByte Management Station, Account, and TSM and then click Next.

Vcenter-12

  1. Select a storage bucket from the list and then click Next to see the summary page.

Vcenter-13

The Summary page appears as follows:

Vcenter-14

  1. Click Finish to create a New Datastore.

Creating a secure Virtual Machine

  1. In the vCenter home page, go to Datastores and Datastore Clusters (Home > Inventory).
  2. Right-click the datacenter and then select New CloudByte Secure VM. The VM creation wizard page appears.
  3. Select the location for the Virtual Machine and then click Next.
  4. Select the datacenter/Node under which the new Virtual Machine has to be created and then click Next.

Vcenter-15

A list of CloudByte datastores appears.

  1. Select the CloudByte datastore for creating VM and then click Next.

Vcenter-16

  1. Select the guest operating system and then click Next.

Vcenter-17

  1. Select the network configurations for the Virtual Machine and then click Next.

Vcenter-18

  1. Select the virtual disk size and then click Next.

Vcenter-19

A summary of selections made while creating a new Virtual Machine appears.

Vcenter-20

  1. Click Finish to create a new Secure Virtual Machine. The secure VM appears under the datacenter it is created.
  2. Verify the secure VM attributes such as IOPS, Latency, and Throughput.

Troubleshooting scenarios

I get an error message that says there is no free disk space. Why?

This is because you have specified a virtual disk size higher than the available disk size.

How will I edit secure Virtual Machine attributes from the plugin?

  1. Right-click the secureVM to choose the Virtual Machine operations.
  2. Select Edit QoS. The Edit QoS screen appears.
  3. Change the QoS parameters as per your requirements.

Vcenter-21

After you change the QoS values, select Update to update the QoS values in ElastiCenter.

How will I unregister ElastiCenter plugin?

    1. In the vCenter Homepage, go to CloudByte Administration > Remove.

Vcenter-22

  1. At prompt, click Yes.
 

Limitations

The current release has the following limitations which will be addressed in future:

  • No confirmation message to suggest successful installation on both vCenter server and client.
  • If you modify the QoS properties in CloudByte ElastiCenter, it does not reflect in the vCenter plugin console.
  • Allows deletion of file system from ElastiCenter even when a Virtual Machine is created on the datatsore.
  • You cannot uninstall the plug-in. Instead you can delete the bin folder from C:\Program Files (x86)\VMware\Infrastructure\Virtual Infrastructure Client\Plugins, and the CloudByte Folder from C:\Users\user, and the shortcut created on desktop.
  • A VM created under default QoS group using the plugin, cannot be deleted from the controller. But you can delete it from vCenter.
  • A VM created under a dedicated QoS group, does not get completely deleted.This is because the deleted VM folders are still present in the datastore. However, you can manually delete the folders.

Delegated administration

Administration in CloudByte can be categorized based on services. You can have administration at the Site level or at the Account level. Your Site can have multiple Site administrators.

As the root administrator, you can distribute the tasks to administrators. Delegated administration is an act of providing and restricting privileges by establishing access control based on the responsibility of each individual administrator.

  • Delegated administration lets you determine the actions that each administrator can take using administrative tools on different resources.
  • Delegated administration roles are mapped to administrative functions using security policies. You can create and maintain separate administration capabilities, depending on your needs.
  • You establish delegated administration by creating role hierarchy.
  • Role hierarchy enables you to keep a tight control on how delegation happens and who can delegate what to whom. One administrator can create sub-roles for other administrators with limited administrative privileges.

Role hierarchy

The following is a pictorial representation of how role-hierarchy functions in CloudByte ElastiStor administration:

roleHierarchyFunctionsInElastiStorAdministrations-v003
AdministratorCanCannot
Super administratorPerform all possible actions across Sites, Accounts, and VSMsNot applicable
Site administrator
  • Manage permissible actions within the permitted Sites
  • Manage more than one Site
  • Have only read-only access
  • Create/Delete/Modify accounts (if permitted by super administrator)
Delete/Modify/Create another Site administrator
Account super administrator
  • Manage only that Account
  • Do everything permissible for an account administrator
  • Manage anything outside the Account
  • Manage anything with respect to the infrastructure
Account administratorManage what is permitted within the AccountManage other account admins within the Account.
View administrator
  • View all the permitted Sites and underlying infrastructure
  • Have only read-only access
  • View all the permitted Accounts
  • View more than one Site
  • View Cluster administrators and Account administrators
  • Generate reports
  • Delete/Modify/Create another View administrator
  • View Site administrators

Note: You can only have one super administrator. Only the super administrator can change his/her password. Administrators can change their password and passwords of administrators under them.

Adding delegated administrators

Create Site administrators or view administrators

Note: You can create Site administrators or view administrators only if you are a super administrator.

  1. Log in as a super administrator.
  2. In the navigation pane, select Delegated Administrator. The Delegated Administrators page appears.
  3. add_delegated_admin_1

  4. Click Add Delegated Admin.
  5. In the Add Delegated Admin Details page, specify the following details:
  6. View_Only_Delegated_Admin

    • Username: Unique username for the site administrator or view administrator.
    • Password: Administrator password.
    • Delegated Admin Type: Select a type of Delegated Administrator from the drop down menu.
  7. Click Next and then drag and drop one or more Sites for which you want to delegate administration as seen in the following screen:
  8. View_Only_Delegated_Admin_Drag_Drop

  9. Click Add.

Create Account administrators

You can create Account administrators for either existing or new accounts.

Create Account administrators for a new account

Note: The type of administrator that you can assign tasks to depends on the privileges you have.

  1. In ElastiCenter, select Accounts in the navigation pane.
  2. In the Accounts page, click Add Account.
  3. In the Account Details page, when you specify the account details, choose the type of administrator that you want to create (Account Super Admin or Account Admin).

add_account_select_admin_type

  1. Specify the credentials for the administrator and then click Add Account.

Create Account administrators for an existing account

Note: The type of administrator that you can assign task to depends on the privileges you have.

  1. In ElastiCenter, select Accounts in the navigation pane.
  2. In the Accounts page, select the account for which you want to add new administrators.
  3. In the following page, click Add Administrator in the Delegated Administration section of the tasks pane.

account_add_administrator

  1. In the Add Account dialog box, specify the details and then click OK.

Global Settings

Global settings let the administrator configure various options used to control CloudByte ElastiStor. For example, email configuration. To configure global settings,

  1. In ElastiCenter, select Global Settings.
  2. Select a target category. A list of settings is provided by default.
  3. Edit the relevant settings.

Note: You cannot add new settings

Monitoring

Monitoring provides an intuitive visualization of storage statistics.

Monitoring foregrounds relevant backend activities in an easy user interface for administrators. It provides a generic outlook of the components such as storage, input/output, throughput, latest data, status, alerts, and system configuration.

Various dashboards dynamically represent disk utilization, storage utilization, throughput, input/output, and status of network interface cards attached to the system.

Alerts and Events feature keeps a regular check on what is happening with the product. All events – even adding an additional IP address or modifying an existing one – get registered and monitored.

The feature also provides a notification system where the administrator is informed through email/text messages when an alert is generated in the system.

Continuous monitoring of your network

  • Helps you discover problems long before they become critical
  • Enables you to take proactive measures
  • Ensures that performance is always at expected levels
  • Ensures that resources are being effectively utilized

Monitoring in CloudByte ElastiStor

Monitoring in CloudByte ElastiStor can be classified as follows:

  • Node level alerts: The alert information specific to the node.
  • Dashboard alerts: Graphical representation of monitoring statistics at granular levels.
  • Events: A snapshot of all ElastiCenter-specific events

Node level alerts

Node level alerts provide a list of alerts specific to the nodes.

  1. In ElastiCenter, click Alerts. All alerts associated with the node are displayed.
  2. Click the Acknowledge icon to acknowledge the alert and it disappears from the list. To acknowledge all the alerts, click Bulk Acknowledge in the Actions pane.
  3. alerts_bulk_acknowledge

Emailing alerts

The following settings in Global Settings let you email alerts:

  • By default , alerts are not emailed. To receive alerts over email, set alert.email.enable to true . The alerts are mailed to the email ID that you specified when you updated your profile. For details, see Launching CloudByte ElastiCenter. To add multiple users, add the email IDs separated by comma in alert.email.addresses.
  • You can set a filter to the alerts mailed based on severity using the option alert.email.severity. By default, all alerts are mailed (as the value set is 4).
  • To specify the sender email ID, use the option alert.email.sender. If you do not specify an ID, the ElastiCenter domain name is displayed along with IP address of ElastiCenter.

Events

To get a list of ElastiCenter events,
  1. In ElastiCenter, click Events.
  2. Select Events in the Select View. All events are listed.
To get a list of specific events, go to the component page and then click Events. For example, for events related to only Storage Volumes:
  1. In the Storage Volumes page, select a Storage Volume for which you want to generate events.
  2. In the following page, click Events in the actions pane.

Dashboard Alerts

Dashboard provides a visual representation of monitoring statistics such as performance, usage, capacity, and availability.

To see the details, select the component and then make a specific selection. The following figure is a dashboard representation of the alerts:

dashboard_view_of_alerts

Advanced debugging options

The Troubleshooting option provided in the Node page, Pool page, and VSM page provides a set of information that help you with advanced debugging. The options provide information such as the following:

  • For Pools: Pool I/O Status and Pool Properties
  • For VSMs: NIC and Netstat information
  • For Nodes: IO Status of various disks, GMultipath status, and Camcontrol device list for all available disks

When you select an option, details are provided in a tabular format. To access the Troubleshooting options,

  1. In the Node/Pool/VSM page, click a specific Node/Pool/VSM.
  2. In the Actions pane, click Troubleshooting under Tasks.
  3. Select the action and then click Update.
  4. advanced_debugging_options_troubleshooting

Drill-down Features

A monitoring feature in Pools, Storage Volumes, and VSMs that lets you monitor

  • IOPS
  • Throughput
  • Latency
  • Average block size (applicable only to Storage Volume)
  • READ vs WRITE (applicable only to Storage Volume)

Select a time interval option such as start time and end time, last 24 hours, or last week to plot a graph.

Using the drill-down feature

To use the drill down feature, select the component and then select a specific feature.

Drill-down procedure for Site

  1. From the list, select a Pool for which you want to monitor IOPS.
  2. Click Compare Volumes.

drill_down_procedure_comparevolumes

  1. In the following page, set the desired parameters.

ha_pool_detailed_mirroring

  1. Click Update.

Comparing IOPS

  1. From the list, select the Pool for which you want to monitor Storage Volume IOPS.
  2. Click Compare Volumes.
  3. In the following page, set the desired parameters.
  4. Click Update.

Note: IOPS comparison is applicable only for Storage Volumes under the same Pool.

CloudByte ElastiStor reporting

CloudByte ElastiStor provides detailed reports that you can save or print. The reports can be generated in the formats PDF, HTML, and CSV. You can schedule reports and email the generated reports.

CloudByte provides the following reports, which you can generate, print, and circulate:

  • Account IOPS Provisioning
  • Pool IOPS Provisioning
  • Account Storage Provisioning
  • Pool Storage Provisioning
  • Account QoS
  • Pool QoS
  • Account Storage
  • Pool Storage
  • Volume Usage
  • HA Group Info
  • Global Accounts IOPS Storage Provisioning

Note: In future releases, you can define your own reports and add new report types.

Accessing the reports

  1. In ElastiCenter, select Reports.
  2. select_reports

    The reports are displayed.

  3. Click the respective icon to generate or schedule a report.
  4. In the dialog box that appears, specify the relevant details and then click OK.

Configuring email for reports

To send the generated reports over mail, Click Generate new Report icon in the Actions pane and then specify the address to which the report has to be mailed.

generate_new_report

To change the default settings for configuring email for reports, select Global Settings and then specify the details for the highlighted options:

    1. Click Generate Report icon and then specify the address to which the report has to be mailed.
    2. In ElastiCenter, select Global Settings and then specify the details for the highlighted options:

report_template_email

Mapping CIFS share to clients

Mapping CIFS share to the clients

On Windows Server 2008

The following procedures explain how to map CIFS share from CloudByte ElastiStor on Windows Server 2008.

Discovering the CIFS share

Note: The mapping procedures are similar for other versions of Windows Server. However, there might be minor variations owing to the differences in UI strings and navigation.

  1. Ensure that you have enabled CIFS. For details, see “Configuring CIFS protocol options” on page 1.
  2. On Windows Server, launch Map Network Drive dialog box (Computer > Map Network Drive).
  3. Specify IP address of VSM and its access path in the following format:
     \\VSM IP Address\Access Path 
    .
  4. Click Finish.
  5. (If you are using the VSM for the first time) At prompt, specify the credentials in the Enter Network Password dialog box. This is the username and password that you have created for the account user in CloudByte ElastiCenter.
  6. cifs_map_1

  7. Click OK.
  8. (If again prompted) Specify the credentials in the Enter Network Password dialog box.
  9. Ensure that CIFS share is connected, as shown in the following screen:

cifs_map_2

On Windows Server 2012

The following procedures explain how to map CIFS share from CloudByte ElastiStor on Windows Server 2012.

Discovering the CIFS share

Note: The mapping procedures are similar for other versions of Windows Server. However, there might be minor variations owing to the differences in UI strings and navigation.

  1. Ensure that you have enabled CIFS. For details, see “Configuring CIFS protocol options” on page 1.
  2. On Windows Server 2012, launch Map Network Drive dialog box (Computer/Shortcut on Desktop to Computer > Map Network Drive).

    cifs_map_3

    The Map Network dialog box appears.

  3. (If you are using the VSM for the first time) At prompt, specify the credentials in the Enter Network Password dialog box. This is the username and password that you have created for the account user in ElastiCenter
  4. cifs_map_4

  5. Click Finish.
  6. (If again prompted) Specify the credentials in the Enter Network Password dialog box.
  7. Ensure that CIFS share is connected, as shown in the following screen:

cifs_map_5

Mapping FC LUN to the clients

Note: Do not present the same LUN to multiple clients/initiators until an OS Clustering (for example, Red Hat Cluster Suite (RHCS) or Microsoft Cluster Server (MSCS)) uses the shared LUN.

On VMware vSphere client

  1. Ensure that you have enabled FC for the particular Storage Volume. For details, see Configuring FC protocol options
  2. In the vSphere Client, go to Configuration > Storage.
  3. Click Devices and then select Rescan All.

Deploying-Fibre-Channel-(FC)-from-CloudByte-ElastiStor-1

  1. In the Rescan dialog box, click OK.

Deploying-Fibre-Channel-(FC)-from-CloudByte-ElastiStor-2

  1. The refreshed list of devices appears.
  2. Select the device and then click Datastore.
  3. In the datastore list, select the datastore and then click Add Storage.

Deploying-Fibre-Channel-(FC)-from-CloudByte-ElastiStor-3

The Add Storage wizard appears.

Deploying-Fibre-Channel-(FC)-from-CloudByte-ElastiStor-4

  1. Follow the instructions on the Wizard and then complete the procedures to add storage.

Mapping FC LUN on Windows Server 2008

Discovering the FC target

Note: The mapping procedures are similar for other versions of Windows Server. However, there might be minor variations owing to the differences in UI strings and navigation.

Note: Microsoft Multipath I/O (MPIO) takes care of presenting a pseudo device.

  1. Ensure that you have enabled FC for the particular Storage Volume. For details, see Configuring Fibre Channel (FC) protocol options.
  2. On Windows Server 2008, select Server Manager > Disk Management > Rescan Disks.

Deploying-Fibre-Channel-(FC)-from-CloudByte-ElastiStor-5

After rescan, the Volumes that you have created for FC are discovered.

Deploying-Fibre-Channel-(FC)-from-CloudByte-ElastiStor-6

  1. Right-click the unallocated space and then click Online.
  2. Once online, right-click and then select Initialize Disk.

Deploying-Fibre-Channel-(FC)-from-CloudByte-ElastiStor-6

The Initialize Disk dialog box appears.

Deploying-Fibre-Channel-(FC)-from-CloudByte-ElastiStor-7a

  1. Click OK.
  2. Right-click the unallocated space and then select New Simple Volume as shown in the following screen:

Deploying-Fibre-Channel-(FC)-from-CloudByte-ElastiStor-7

The New Simple Volume Wizard appears.

Deploying-Fibre-Channel-(FC)-from-CloudByte-ElastiStor-9

  1. Follow the instructions and complete the wizard to create the partition.
  2. Ensure that the created disk is added to the Disk management console (indicated by the blue ribbon).

Deploying-Fibre-Channel-(FC)-from-CloudByte-ElastiStor-10

  1. Ensure that the drive created out of FC LUN is shown (as in) the following screen:

Deployin-Fibre-Channel-(FC)-from-CloudByte-ElastiStor-11

On Kernel-based Virtual Machine

  1. Do either of the following:
    • As root, make an SSH connection to the KVM client.
    • On the KVM client, log in as root.
  2. At command prompt, do the following to map FC LUN to KVM.
  3. Run the following command to verify the number of FC Hosts:
    ls /sys/class/fc_host/
    . The following is a sample output:
    host0 host1 host2 ..........hostX
    .
  4. Note: The number that follows host (1, 2, or X) is the HBA number of the FC Host.

  5. Run the following command to discover the FC LUNs:
    echo "1" >/sys/class/fc_host/hostHBA number/issue_lip
    . For example,
    echo "1" >/sys/class/fc_host/host7/issue_lip
    .
  6. Repeat the step 4 for all the FC Hosts.
  7. Run the following command to fetch the WWPN of the FC Host:
    cat /sys/class/fc_host/host<HBA number>/port_name
    . For example,
    cat /sys/class/fc_host/host7/port_name
    .
  8. Run the following command to add each FC LUN as a device to the KVM client:
    echo "scsi add-single-device h c t l" > /proc/scsi/scsi
  9. Parameter Description
    h HBA number of the Host.
    c Channel ID on the HBA.
    t SCSI target ID.
    l FC LUN ID.
  10. Run the following command to to list the disks:
    fdisk -l

Mapping iSCSI LUN to the clients

Note: Do not present the same LUN to multiple clients/initiators until an OS Clustering (for example, Red Hat Cluster Suite (RHCS) or Microsoft Cluster Server (MSCS)) uses the shared LUN.

On Linux

The following procedures might work on most of the Linux setups. However the certified versions are

  • OpenSUSE-11.4-x86 -64 bit and 12.1 version
  • Red Hat Enterprise Linux Server release 6.0
  • CentOS-6.4-x86

Without CHAP authentication

  1. At command prompt, run the following command, to discover the iSCSI target:
    iscsiadm -m discovery -t st -p <VSM_IP_address:port>.

The iSCSI target (iqn) is displayed as shown in the following example:

10.10.8.201:3260,1 iqn.2012-09.CertStorage:isci-on-iscsiSet
  1. Connect to the target in either of the following ways:
    • To connect to all targets, run the following command:
      iscsiadm –m node –l
    • To connect to an individual target, run the command as shown in the sample command:
      iscsiadm –m node –T <target_name_displayed_when_you_run_discover_command> –p <VSM_IP_address:port> –l

    A success message is displayed.

  1. To create multiple partitions from the LUN, run the following command:
    fdisk -l
    .

All available disks and partitions are listed.

  1. Use the following command to create the partition:
    fdisk <disk(Discovered LUN)>
  2. (Optional) Enter the command
    m 
    to list the commandline help.
  3. Create a partition using the command
    n 
    (primary or extended).
  4. Specify the cylinder size and value.
  5. Specify the size of the partitions and enter
    w 
    for WRITE changes.
  6. Create a file system on the created partitions using the following command:
    mkfs.<ext2,ext3,ext4,ntfs,vfat> <partition>
  7. Create an empty directory using the following command:
    mkdir <directoryname>
  8. Mount the partitions to the empty directory using the following command:
    mount <partition name> <directoryname>
  9. Perform READ and WRITE operations on mount point.

Sample CLI snapshot

[root@qaprod ~]# iscsiadm -m discovery -t st -p 10.10.8.201
10.10.8.201:3260,1 iqn.2012-09.CertStorage:isci-on-iscsiSet
[root@qaprod ~]# iscsiadm –m node –l
iqn.2012-09.CertStorage:isci-                                   
on-iscsiSet –portal 10.10.8.201:3260 –login
Logging in to [iface: default, target: iqn.2012-09.CertStorage:isci-
on-iscsiSet,                                                                                                                     
portal: 10.10.8.201,3260]
Login to [iface: default, target: iqn.2012-09.CertStorage:isci-on-iscsiSet, 
portal: 10.10.8.201,3260] successful.
[root@qaprod ~]# fdisk -l
Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00018542
   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1          64      512000   83  Linux
Partition 1 does not end on cylinder boundary.
/dev/sda2              64       60802   487873536   8e  Linux LVM
Disk /dev/dm-0: 53.7 GB, 53687091200 bytes
255 heads, 63 sectors/track, 6527 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Disk /dev/dm-0 doesn't contain a valid partition table
Disk /dev/dm-1: 10.3 GB, 10284433408 bytes
255 heads, 63 sectors/track, 1250 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Disk /dev/dm-1 doesn't contain a valid partition table
Disk /dev/dm-2: 435.6 GB, 435607830528 bytes
255 heads, 63 sectors/track, 52959 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Disk /dev/dm-2 doesn't contain a valid partition table
Disk /dev/sdb: 1073 MB, 1073741824 bytes
255 heads, 63 sectors/track, 130 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 4096 bytes / 1048576 bytes
Disk identifier: 0x4408a443
   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1               1         131     1045504    7  HPFS/NTFS
Partition 1 has different physical/logical endings:
     phys=(129, 254, 63) logical=(130, 42, 40)
[root@qaprod ~]# fdisk /dev/sdb1
WARNING: DOS-compatible mode is deprecated. It's strongly recommended to
         switch off the mode (command 'c') and change display units to
         sectors (command 'u').
Command (m for help): m
Command action
   a   toggle a bootable flag
   b   edit bsd disklabel
   c   toggle the dos compatibility flag
   d   delete a partition
   l   list known partition types
   m   print this menu
   n   add a new partition
   o   create a new empty DOS partition table
   p   print the partition table
   q   quit without saving changes
   s   create a new empty Sun disklabel
   t   change a partition's system id
   u   change display/entry units
   v   verify the partition table
   w   write table to disk and exit
   x   extra functionality (experts only)
Command (m for help): n
Command action
   e   extended
   p   primary partition (1-4)
p
Selected partition 1
First cylinder (1-1008, default 1):
Using default value 1
Last cylinder, +cylinders or +size{K,M,G} (1-1008, default 1008):
Using default value 1008
Command (m for help): w
The partition table has been altered!
Calling ioctl() to re-read partition table.

With CHAP authentication

For all targets
  1. Open /etc/iscsi/iscsid.conf using an editor and then specify the details for the following section:
node.session.auth.password = <CHAP secret>
node.session.auth.username_in= <Mutual CHAP username> (give only when you are doing mutual CHAP)
node.session.auth.password_in = <Mutual CHAP secret> (give only when you are doing mutual CHAP)
discovery.sendtargets.auth.authmethod = CHAP
discovery.sendtargets.auth.username = <CHAP username>
discovery.sendtargets.auth.password = <CHAP secret>
discovery.sendtargets.auth.username = <Mutual CHAP username> (give only when you are doing mutual CHAP)
discovery.sendtargets.auth.password_in = <Mutual CHAP secret> (give only when you are doing mutual CHAP)
  1. Restart the iSCSI daemon using the following command:
    /etc/init.d/iscsi restart
    .
  2. Follow the procedures in the section “Without CHAP authentication” on page 1.
For a specific target

Specify the details as follows at command prompt:

iscsiadm -m node -T "<Target_Name>" -p <VSM_IP_address>:<port> --
op=update --name node.session.auth.authmethod --value=CHAP
 
iscsiadm -m node -T "< Target_Name >“ -p < VSM_IP_address >:<port> --
op=update --name node.session.auth.username --value=<CHAP_username>
 
iscsiadm -m node -T "< Target_Name >“ -p < VSM_IP_address >:<port> --op=update
--name node.session.auth.password --value=<password>
 
iscsiadm -m node –T "<Target_ Name>" -p < VSM_IP_address >:<port> -l

Resizing iSCSI LUN

The following procedures explain how to expand your iSCSI storage volume on CentOS:

  1. Exporting the iSCSI LUN (On CentOS Console)
  2. In the CentOS console, run the commands provided in the table in sequence to export the iSCSI LUN:

    Step Task Command Example Details
    1 Discover the iSCSI targets. iscsiadm -m discovery -t st -p <Target IP Address> iscsiadm -m discovery -t st -p 11.11.11.11 Outputs the complete target name.
    2 Log in to the iSCSI target. iscsiadm -m node -T <Complete Target Name> -l iscsiadm -m node -T iqn.2014-02.FCAcc.Test:FCAcciscsivol1 -l
    3 Display the current partitions on the hard disk. fdisk –l The partition is displayed in the output.
    4 Create a file system on the hard disk drive. mkfs.ext3 <Partition name> mkfs.ext3 /dev/sdc At prompt, confirm by typing y as shown in the following example: /dev/sdc is entire device, not just one partition! Proceed anyway? (y,n) y
    5 Create a directory. mkdir <Directory name> mkdir /mnt/cbdata
    6 Mount the partition into your directory. mount <Partition name> <Directory name> mount /dev/sdc /mnt/cbdata -o sync  
    7 (Optional) Retrieve the current size of the mounted LUN. df –kh
    8 Copy some data to the directory /mnt/cbdata. cp
    9 Unmount directory from the disk. umount <Directory name> umount /mnt/cbdata
    10 Log out of iSCSI target. iscsiadm -m node -u -T <Complete target name> -p <Target IP Address> iscsiadm -m node -u -T iqn.2014-02.Acc1.TSM3:TSM3TSM3ISCSI11 -p 11.11.11.11
  3. Editing Quota Size (in ElastiCenter)
    1. In the ElastiCenter, select Storage Volumes.
    2. In the Storage Volumes page, click Settings > Edit.
    3. Increase the Quota size of the LUN and then click Save.

    resizing_iscsi_lun_edit_quota_size

  4. LUN expansion and resizing file system (on CentOS Console)

In the CentOS console, run the commands provided in the table in sequence to expand the LUN and resize the file system:

Step Task Command Example Details
1 Log in to iSCSI target. iscsiadm -m node -T <Complete target name> -p <Target IP Address> –l iscsiadm -m node -T iqn.2014-02.Acc1.TSM3:TSM3TSM3ISCSI11 -p 16.10.10.3 –l
2 Display current partitions on the hard disk. fdisk –l Check the output to see if the disk size has increased.
3 Mount the partition into the directory. mount partition name <Directory name> -o sync mount /dev/sdb /mnt/cbdata/ -o sync
4 Resize the expanded volume. resize2fs /dev/sdb/ <total space of volume> resize2fs /dev/sdb/ 5G In this example, 5G is the total space on the resized Volume.
5 Retrieve the current size of the resized LUN. df –kh

On Windows Server 2008

Discovering the iSCSI target

Note: The mapping procedures are similar for other versions of Windows Server. However, there might be minor variations owing to the differences in UI strings and navigation.

  1. Ensure that you have enabled iSCSI. For details, see “Data access using iSCSI” on page 1.
  2. On Windows Server 2008, launch iSCSI Initiator (Programs > Administrative Tools > ISCSI Initiator).
  3. In the Target tab, specify the target (tenant IP address).
  4. Deploying CIFS and iSCSI from CloudByte ElastiStor on Windows Server 2008-1

  5. Click Quick Connect. The Quick Connect screen appears, displaying the target name.
  6. Click Done.

Create storage drive to use the iSCSI target

  1. Launch Server Manager and then select Disk Management in the left pane.
  2. Deploying CIFS and iSCSI from CloudByte ElastiStor on Windows Server 2008-2

  3. Right-click the unallocated space (the highlighted section) and then select Initialize Disk. The Initialize Disk dialog box appears.
  4. Deploying CIFS and iSCSI from CloudByte ElastiStor on Windows Server 2008-3

  5. Click OK.
  6. Right-click in the space and then select New Simple Volume as shown in the following screen:

Deploying CIFS and iSCSI from CloudByte ElastiStor on Windows Server 2008-4

The New Simple Volume wizard appears.

  • Follow the instructions to complete the wizard, to create the partition.
  • Ensure that the created disk is added to the Disk management console.
  • On Kernel-based Virtual Machine

    Note:The following section provides procedures performed on RHEL 6.3. The procedures might be similar on other flavors of Linux.

    1. On your Linux desktop, select Applications > System Tools > Virtual Machine Manager.
    2. Select a host machine.
    3. Click Edit > Connection Details.
    4. iscsi_kvm_conf

    5. Click Storage tab.
    6. Click the Add Storage Pool + icon at the bottom left side of the dialog box. The Add a New Storage Pool wizard appears.
    7. iscsi_kvm_conf_storage_tab

    8. Specify a name for the Pool, select iSCSI as the type, and then click Forward.
    9. iscsi_kvm_conf_add_pool

    10. In the following screen, specify the required details.
    11. iscsi_kvm_conf_add_pool_details

      Field Description
      Target Path Path of the target directory (to use for the Storage Pool).
      Host Name Host name or IP address of the iSCSI target.
      Source Path iSCSI target IQN.
      IQN Select the check box and then enter the IQN for the initiator.
    12. Click Finish.

    Mapping NFS share to clients

    On Red Hat Enterprise Linux

    1. Ensure that you have enabled the NFS. For details, see Configuring NFS protocol options.
    2. On your RedHat Enterprise Linux server, at command prompt, specify the following command to verify the NFS export: showmount -e <IP of Tenant>. If correctly exported, the path to the filesystem along with the authorized network is displayed.
    3. Create a directory to mount the NFS using the following command: mkdir <directoryname>
    4. Mount the NFS on this directory using the following command: mount <tenant IP address>:<exported path> <directoryname>
    5. Enter the following command: mount .
    6. If successfully mounted, the following is displayed in the mount list: <tenant IP address>:<exportpath> on <directoryname> type nfs (rw,addr=<tenant IP address>)

    Sample CLI snapshot

     [root@localhost ~]# showmount -e 20.10.26.199
      Export list for 20.10.26.199:
         /acctsample (everyone)
         #Here everyone implies that the exported path is shared to all (as configured in NFS page).
     If you specify a specific client IP, that IP is displayed.
     [root@qaprod ~]# mkdir /mnt/nfslocal
     [root@qaprod ~]# mount -t nfs -o vers=3,proto=tcp,nolock,sync 20.10.26.199:/acctsample /mnt/nfslocal/
     [root@qaprod ~]# mount
     /dev/mapper/VolGroup-lv_root on / type ext4 (rw)
    proc on /proc type proc (rw)
    sysfs on /sys type sysfs (rw)
    devpts on /dev/pts type devpts (rw,gid=5,mode=620)
    tmpfs on /dev/shm type tmpfs (rw,rootcontext="system_u:object_r:tmpfs_t:s0")
    /dev/sda1 on /boot type ext4 (rw)
    none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
    sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
    gvfs-fuse-daemon on /root/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev)
    20.10.26.199:/acctsample on /mnt/nfslocal type nfs (rw,sync,vers=3,mountproto=tcp,addr=20.10.26.199,mountaddr=20.10.26.199)
    
    

    On Kernel-based Virtual Machine

    Note:The following section provides procedures performed on RHEL 6.3. The procedures might be similar on other flavors of Linux.

    1. On your Linux desktop, select Applications > System Tools > Virtual Machine Manager.
    2. Select a host machine.
    3. Click Edit > Connection Details.
    4. iscsi_kvm_conf

    5. Click Storage tab.
    6. Click the Add Storage Pool + icon at the bottom left side of the dialog box. The Add a New Storage Pool wizard appears.
    7. iscsi_kvm_conf_storage_tab

    8. Specify a name for the Pool, select Network Exported Directory as the type, and then click Forward.
    9. nfs_kvm_conf_add_pool

    10. In the following page, specify the required details.
    11. nfs_kvm_conf_add_pool_details

      Field Description
      Target Path Path of the target directory (to use for the Storage Pool).
      Format Set the Format option to NFS.
      Host Name Host name or IP address of the NFS Server.
      Source Path Enter the NFS path (path on the Host that is being shared).
    12. Click Finish.

    CloudByte Elastistor Product FAQs

    Is it possible to scale-out using CloudByte ElastiStor?

    Each CloudByte ElastiStor node can be scaled to 1 PB of raw storage capacity. You can linearly increase capacity and performance by adding additional ElastiStor nodes.

    Can I use ElastiStor to improve the performance of storage solutions such as EMC Symmetrix or Hitachi Unified Storage?

    Like other storage systems, CloudByte ElastiStor is an independent storage system with distinct architecture.

    ElastiStor does not improve performance but shares the performance between competing applications granularly in a desired way. However, CloudByte recommends you to use raw disk for storage media rather than storage from other vendors.

    How many flavors and versions of CloudByte ElastiStor are available in the market?

    CloudByte ElastiStor 1.0 was the pioneering release of the product. The ongoing release is CloudByte ElastiStor 2.0 x

    Which RAID levels are supported by CloudByte ElastiStor?

    RAID5, RAID6, RAID10, RAID50, RAID60

    Are there any CloudByte ElastiStor management plug-ins available?

    Yes. The plug-ins for VMWare vCenter, Apache CloudStack and OpenStack Cinder are available off-the-shelf.

    Can I use the same IP address for tenants?

    Each tenant is identified by unique IP address.

    Does ElastiStor support iPV6?

    Current version of CloudByte ElastiStor does not have built in support for iPV6.

    What is the skill set required to manage and configure ElastiStor?

    Basic storage administration (SAN and NAS) and networking skills.

    Provide ElastiStor specifications in terms of the supported number of logical table entries, for example, the maximum number of simultaneous tenant networks, maximum number of storage clients, maximum number of LUNs, maximum number of NFS mount points, etc.

    ElastiStor does not have theoretical limitations on the number of Storage Volumes, VLANs and VSMs per Node as revealed in the tests done with 12000 Volumes. Also, ElastiStor supports unlimited snapshots and clones. For details, see ElastiStor Scalability

    The CloudByte documentation (http://www.docs.cloudbyte.com/enabling-out-of-band-communication-between-nodes-in-an-ha-group/ ) refers to configuring IPMI between Nodes in an HA Group. Is such a configuration required for ElastiCenter HA also?

    No. IPMI based out of band communication between peer Nodes is used during Node HA process when necessary. This configuration is not mandatory for ElastiCenter HA. However, it is helpful to have the IPMI configured for the regular remote access and troubleshooting.

    Is SNMP monitoring support available on ElastiStor?

    Yes.

    Is SNMP based IOPS and capacity monitoring support available on ElastiStor?

    SNMP support for volume statistics such as IOPS will be available in the future releases.

    How to configure a spare disk?

    Follow the procedures at the URL http://www.docs.cloudbyte.com/disk-replacement-scenarios/.

    In pages where Graphs ought to appear, I see a message invalid data throughout ElastiCenter. Why?

    Try using a different browser.
    Adobe Flash is required to see the charts. For details, see http://www.docs.cloudbyte.com/wp-content/uploads/CloudByte_troubeshooting_invalid-data_graphs.pdf. Future releases will provide HTML5 support.

    How to set up a secondary ElastiCenter manually?

    This scenario applies if you haven’t configured ElastiCenter HA during installation. If ElastiCenter fails, you can promote the secondary ElastiCenter to primary ElastiCenter. For procedures, see Setting up secondary ElastiCenter

    I encountered the error weak ephemeral Diffie-Hellman key while trying to access ElastiCenter. I am using Mozilla Firefox version 39 browser. Is there a workaround to access ElastiCenter?

    Yes. Do the following to access ElastiCenter on Mozilla Firefox version 39:

    1. Launch Mozilla Firefox browser.
    2. In the Address bar, type the following:
      about:config
      .
    3. In the Search bar, search for the following parameter:
      security.ssl3.dhe_rsa_aes_128_sha
    4. Set the parameter to
      false (security.ssl3.dhe_rsa_aes_128_sha = false)
      by doing either of the following:
      • Right click the parameter and then select Toggle.
      • Double click the parameter.
    5. firefox_v39
    6. Repeat step 3 and step 4 for the parameter
      security.ssl3.dhe_rsa_aes_256_sha
    7. Open a new tab in the browser.
    8. Launch ElastiCenter.

    I am unable to access ElastiCenter on the browser Chrome (version 45). Is there a workaround to access ElastiCenter?

    If you are using Chrome version 45, do the following to ensure that ElastiCenter is compatible:

    1. SSH to ElastiCenter as root.
    2. Download the
      server.xml
      file from the following URL:
      http://cloudbyte.com/downloads/server.xml
    3. Backup the existing xml file in the location
      /usr/local/apache-tomcat-6.0.33/conf/server.xml
    4. Run the following command to replace the existing server.xml file with the new xml (that you downloaded):
      cp new_server.xml  /usr/local/apache-tomcat-6.0.33/conf/server.xml
    5. Run the following commands to restart Tomcat service:
      1. /usr/local/apache-tomcat-6.0.33/bin/shutdown.sh
      2. pgrep java
      3. (Optional, if the java service is running)
        pkill java
      4. /usr/local/apache-tomcat-6.0.33/bin/startup.sh
    6. Open a new tab in the browser.
    7. Launch ElastiCenter.

    I cannot access the configuration file config.xml from ElastiCenter. How can I access it otherwise?

    The following procedures let you manually restore a earlier file version to its original location:

    1. Move the Node to Maintenance mode. For details, see Bringing Node to Maintenance mode
    2. Run the following command to copy the latest config.xml file from the backup location: cp /var/backups/node/config.xml YYYY-MM-DD-HH-00-00 /cf/conf/config.xml.
    3. YYYY-MM-DD-HH-00-00 is the date and time when the file was backed up .

    4. Move the Node to available mode. For details, see Make a Node Available

    Does ElastiStor supports NPIV?

    No

    What is API Key?

    The API Key is used to authenticate the CloudByte REST API token requests. See, Using the REST APIs to obtain a Rest API Key.

    How to retrieve scalability limitations of a SAS HBA?

    You can retrieve the details using the command mpsutil show iocfacts. The following is a sample output:
    sas-expanders

    Installation FAQs

    I cannot access CloudByte ElastiCenter after successful installation. Why?

    This might be because of one of the following reasons:

    • Java Service is not running
    • Database is not up and running

    To resolve this issue, do either or both of the following:

    1. In the ElastiCenter server, at command prompt, run the following command:
      pgrep mysql
      .
    2. If you do not get the MySql process ID, run the following command to bring up the database service:

      service mysql-server onerestart			

    3. In the ElastiCenter server, at command prompt, run the following:
      pgrep java
      .

      If you don’t get the Java process ID, run the following command to bring up the Java service:

      service cbdevman onerestart
      			

    4. Try accessing ElastiCenter.

    Can you explain the memory requirements for installing CloudByte ElastiStor?

    The following table provides the details. The values are same for installing both Node and ElastiCenter. Also, the same values apply if you install both Node and ElastiCenter on the same machine:

    Memory Minimum Recommended
    RAM 1 GB 8 GB or higher
    Hard Disk 20 GB (2.4 X RAM size + 32 GB) or higher. For example, if the RAM is 8 GB, for better performance, 52 GB or higher is recommended

    If you do not comply with the recommended hard disk memory, you might encounter a message that prompts correction (for better performance). However, if you meet the minimum memory requirements, even if you ignore the message, installation will be successful.

    I get the message ‘Installation cannot proceed as no NIC is present’. What will I do?

    You encounter this issue because the NIC that you use is not supported. For a list of supported NICs and other hardware, see the Hardware Compatibility List.

    I get the message ‘Installation cannot proceed as no disk is present’. What will I do?

    This is because the internal RAID/SAS card in the server is not supported. For a list of supported disks and other hardware, see the Hardware Compatibility List.

    What if I get a mountroot during installation?

    Retry installing by reinserting the CD. Also ensure that there are no network issues.

    If the issue persists, use the following command to proceed:

     mountroot > cd9669:/dev/cd0 ro

    Why am I not able to access the system after the first reboot post installation?

    Verify the following:

    • ElastiStor has correctly rebooted. This is indicated by the root login prompt when the installation concludes.
    • Network port connectivity
    • Network details are correctly added

    Will the installation rollback on failure?

    Yes.

    Explain the upgrade options for ElastiStor?

    You can upgrade based on the option that you have selected in the existing installation. That is, if you have opted to install both Node and ElastiCenter, then you have the option to upgrade both.

    What happens to the installation when there is a hard disk failure?

    Installation may or may not be successful, but the product is unlikely to function.

    What happens if the CD ROM gets disconnected while installing?

    Reconnect and start the installation from the beginning.

    Do I need an internet connection for installing CloudByte?

    No. But it is recommended because it facilitates time synchronization with NTP.

    What happens if the network connection is lost and system boots after installing?

    It waits for the connectivity to be restored and then boots up.

    Is it mandatory to do a disk mirror while installing?

    Recommended for production environments.

    What happens to the installation during a power loss?

    You have to reinstall.

    Can I install ElastiStor my laptop?

    Yes. If you meet the minimum hardware requirements, the installation is not devise dependent.

    Can I install ElastiCenter on a virtual machine?

    Yes. CloudByte recommends you to have a minimum requirement of 8 GB RAM on your VM.

    Is ElastiStor installation possible over SAN boot?

    Yes

    Can I downgrade my ElastiStor installation?

    Not currently supported

    Can I do a network installation of CloudByte ElastiStor?

    Not currently supported

    After I installed ElastiCenter on ESX 5.0, my virtual machine stopped responding. Why?

    If your virtual machine on ESX 5.0 hangs, do the following:

    1. (In the ElastiCenter command prompt) Run the following command:
      sysctl kern.timecounter.hardware=ACPI-fast
    2. Run the following command to edit the loader.conf file:
      vi /boot/loader.conf
    3. Append the loader.conf with the following line:
      kern.timecounter.hardware=ACPI-fast

    I did not come across the ElastiCenter HA option while installing ElastiCenter. Why?

    The option to configure ElastiCenter HA is available only when you choose the installation option Both ElastiCenter and Node i.e., installing both ElastiCenter and Node on a single machine. For details, see http://www.docs.cloudbyte.com/installing-both-elasticenter-and-node/

    Can I back up ElastiCenter even if I haven’t configured ElastiCenter HA?

    Yes. You can setup a secondary ElastiCenter (secondary setup) to ensure backup in the case your primary ElastiCenter (primary setup) fails. If a failure occurs, you can promote your secondary setup. For details, see http://www.docs.cloudbyte.com/cloudbyte-elastistor-product-faqs/promoting-secondary-elasticenter-and-backing-up-configurations/

    Does installing ElastiCenter in HA mode involve any manual procedures?

    No. During installation, one ElastiCenter is installed as primary and the second one as secondary.

    Is it mandatory to have ElastiCenters and ElastiStor Nodes on the same subnet?

    Not necessary for them to be on the same Subnet as long as the IP address is reachable.

    Pool FAQs

    What is the recommended storage pool RAID configuration?

    If you need high performance, data mirroring is recommended. For larger SATA drives (for example 4TB), CloudByte recommends RAIDz2.

    How can I expand the tpool size?

    1. SSH to the Node.
    2. Run the following command:
      cd /usr/local/cb/bin.
    3. Run the following to expand the tpool size:
      ./expandtpool OS_disk_name
      . For example,
      ./expandtpool ada0

    The size of the tpool increases by 10G.

    Can I create a mixed disk pool, for example with SATA and SSD disks?

    Yes. But CloudByte does not recommend this because you get only the performance of the lowest disk, in this case SATA.

    How many log devices can I attach to a pool?

    Depends on the workload. For instance, in a WRITE intense scenario, a higher ZIL improves your WRITE performance.

    How much L2ARC should I add to the pool?

    Depends on the workload. For instance, in a READ intense scenario, a higher L2R improves READ performance.

    How to improve the performance of L2ARC and the log device?

    L2ARC and log device are intended to improve the READ and WRITE respectively. Therefore, high performance SSD storage is recommended for an L2ARC or ZIL

    What pool do you recommend for a data protection use case?

    A large RAIDz Group with high performance data disks and one or two parity disks are ideal.

    What is the recommended RAID-Z configuration?

    For RAID-Z1, RAID-Z2, and RAID-Z3 CloudByte recommends a 2^n + p configuration.

    Parameter Description
    n RAID-Z 1, RAID-Z 2, and RAID-Z 3.
    p Parity: p=1 for RAID-Z1, p=2 for RAID-Z2 and p=3 for RAID-Z3 where RAID-Z1 = 3, 5, 9, 17, …, RAID-Z2 = 4, 6, 10, 18, …, RAID-Z3 = 5, 7, 11, 19, …

    Is single parity RAID equivalent to well known RAID 5?

    Almost similar. Also it eliminates the WRITE HOLE problem in RAID 5.

    Is double parity RAID equivalent to well known RAID 6?

    Almost similar. Also, it eliminates the WRITE HOLE problem in RAID 5.

    What is RAID triple parity and when should I use it?

    RAID triple parity tolerates failure of three disks in a RAID group. Use it when you handle critical data and want to evade chances of disk failure.

    Do you recommend NFS/CIFS/ISCSI/FC on the same pool or should I have the access protocols on different pools?

    It doesn’t matter. Configure based on the usage and requirement.

    Can a VSM span multiple pools?

    Not in the current release.

    Is pool IOPS derived from the disk?

    Disk plays a role in deriving IOPS, but it is also based on RAM and L2ARC.

    Can I extend the pool IOPS by extending the pool?

    Yes

    Can I delete a Pool with active Storage Volume?

    No

    Can I identify the failed disks in a pool?

    ElastiCenter Alerts provides you with the details.

    What happens if you pull a disk from a pool that has a spare disk?

    Spare disk is attached to the pool.

    What happens if you pull a disk from a pool that does not have a spare disk?

    Leaves the Pool in a degraded list.

    How do I disable SCSI reservation on disks?

    Warning: Do not disable SCSI reservation on production environments. The following procedures are recommended only for troubleshooting on development and testing setups.

    1. Make an SSH connection to the Node.
    2. Run the following command touch /etc/disablescsi.

    When you move the setup from test to production environment, ensure that all disks are SCSI reservation-enabled.

    If the disablescsi file exists,

    1. Run the following command to remove it: rm /etc/disablescsi.
    2. Create new Pool.

    How will I clear the pools created in an older setup?

    If you add a new Pool on the disks being consumed by existing Pool, it will be deleted automatically. However, to manually clear the Pools from an older setup, do either of the following (depending on the scenario):

    • Reinstalled ElastiStor without removing the Pools: In the Nodes page, go to the section Existing Pools (at the bottom of the page) and then click the Clear link under the column Clear.
    • Connected disk arrays (with Pools) to a different Node: Apply Refresh Hardware after connecting to the new Node. All existing Pools are displayed in the Nodes page. Go to the section Existing Pools (at the bottom of the page) and then click the Clear link under column Clear.

    How do I configure partial failover?

    CloudByte ElastiStor supports selective failover of Pools. If partial failover is enabled, in the case of network failure, the secondary node in the cluster takes over.

    By default, partial failover is enabled. If not enabled, go to the Pool settings and enable.

    1. In ElastiCenter, select Pools in the left pane.
    2. In the Pools page, select the Pool for which you want to enable partial failover.
    3. In the Actions pane, select Settings.
    4. Click Edit and then enable partial failover.
    5. enable_partial_pool_failover

    Can I set AD-level authentication for a VSM?

    Yes. For details, see Active Directory integration with ElastiStor

    Access protocol FAQs

    Can I use same secret key for mutual authentication in the case of LUN export?

    No. The key must be unique.

    What is the maximum number of NFS or iSCSI LUNs that you can have on ElastiStor?

    You can create N number of NFS or iSCSI LUNs based on your requirement.

    Can I send an I/O of 1MB size in a single request on NFS?

    Yes. NFS volumes are currently allowed to be mounted with an rsize/wsize of 1M. You can use the following sample mount option:

    mount -o vers=3,rsize=1048576,wsize=1048576,mountproto=tcp,sync 20.10.26.199:/acctsample /mnt/nfslocal/

    Can I disable the configuration options related to the protocols I do not use, in ElastiCenter?

    Yes. The current release supports disabling of FC-specific options.

    1. In the ElastiCenter, click admin > Global Settings.
    2. Go to ui.protocol.enablefc, click the Edit icon, and then specify false.
    3. disable_fc
    4. For the changes to take effect, either relogin to ElastiCenter or refresh the browser.

    All FC-specific options disappear from ElastiCenter UI.

    When I use FC I see a LUN with the ID 0 and size 1MB displayed though i did not create it. Why?

    This is a system LUN and is not for use.

    Deleting data on my CIFS share doesn’t increase the free space. Why?

    This is because the data is not permanently deleted. Instead, data is moved to the CIFS share recycle bin. To delete data permanently, do the following:

    On ElastiCenter
    1. In the Storage Volumes page, select a CIFS Storage Volume.
    2. Click Manage CIFS configuration in the actions pane.
    3. Click Edit and then disable the CIFS share Recycle bin option.
    4. cifs_disable_recycle_bin

    5. Click Save.
    On Windows client

    If you have not disabled this option (earlier) and then data is already moved to the CIFS share Recycle Bin, to clear the data, you must do the following:

    • (If Show hidden files and folders option is enabled) Go to the folder .recycle and then clear the data.
    • (If Show hidden files and folders option is disabled) Do the following:
      1. Go to Control Panel > Folder Options > View tab.
      2. protocol_faq_recyclebin

      3. Enable hidden files, folders, and drives. Now you can view the .recycle folder.
      4. Clear the data.

    I am on a common NFS Share. Is there a way to restrict an other user on this share from deleting my files?

    Yes. If you want a home directory kind of NFS share, when configuring the NFS Storage Volume (see the following screen), set the option Map as Root Users to No.

    nfs_home_directory

    I changed the primary IP address of the VSM. Now I cannot access the iSCSI Storage Volumes. What should I do?

    Do the following:

    1. Log out of all the iSCSI Volumes on the clients.
    2. Delete the login entries of the VSM on the clients.
    3. Relogin to the clients with the new IP address.

    Storage Volume FAQs

    Can I migrate a storage volume?

    No. You can only migrate VSM.

    Can I mirror a storage volume?

    You can do a DR of your storage volume.

    Can I keep storage volume in a sleep state?

    No

    Can a storage volume span multiple pools?

    No

    Will enabling compression and deduplication impact the performance?

    Yes, they can significantly impact. Compression and deduplication are CPU and memory intensive processes.

    What is the right latency number to specify for the storage volume?

    Depends on the disk from which the pool is created. For example, SSDs are of lower latency when compared with SATA.

    I enabled READ-only property for iSCSI Volume mounted on a Windows client, and observe that the property hasn’t taken effect. How can I make the Volume READ only?

    For the READ-only property to take effect, disconnect the iSCSI Volume and then remount it on the client.

    Can I have storage volume with same names under different accounts?

    Yes

    Can the storage capacity be changed after configuring a storage volume?

    Yes

    QoS FAQs

    What is QoS?

    Assuring your client/application the promised IOPS, throughput, and latency.

    Is QoS applicable only to Cloud Service Providers?

    No. QoS is applicable to enterprise scenarios as well.

    What is the maximum IOPS I can set?

    The maximum IOPS directly depends on the underlying storage. SSD is the best choice followed by SAS and SATA.

    Is QoS disk dependent?

    Yes

    Is QoS a licensed option?

    No

    What is the difference between dedicated and shared options?

    Dedicated: If the Storage Volume needs exclusive QoS configuration.

    Shared: If the Storage Volume can share the QoS configuration with another Storage Volume.

    The following figure explains the concepts:

    sharingIOPS

    For example, if both Storage Volume 1 and Storage Volume 2 are committed to busy service round the clock, Dedicated would be your choice. Whereas, if Storage Volume 1 and Storage Volume 2 represent services in a cross-geographical setup where activities related to Storage Volume 1 ends toward the time activities related to Storage Volume 2 start, Shared would be your choice.

    Do I have to set all the QoS parameters (IOPS, Latency, and Throughput)?

    No. IOPS is must. Depending on requirement, you can choose to configure Latency and Throughput.

    What is the difference between IOPS, Latency, and Throughput?

    IOPS: The READ/WRITE capability

    Latency: Time that ElastiStor takes to acknowledge a READ/WRITE back to the client

    Throughput: Data that can be transferred as part of READ/WRITE operations.

    Is it must to set QoS?

    Yes

    Can I increase/decrease QoS on-the-fly?

    Yes

    Is QoS guaranteed in an HA environment?

    Yes

    Can I set QoS for my backups?

    Yes

    Can I set QoS for my DR operations?

    Yes

    Can I get the same QoS on the secondary Node in the case of a disaster?

    Yes, provided you have the same or better infrastructure quality.

    What is the upper limit for setting FC LUNS?

    255 per target

    How do you calculate IOPS, latency, and throughput?

    Throughput = IOPS * Block Size.

    Latency depends on the following factors:

    • Workload characteristics such as L2ARC Size and ZIL size.
    • Seek time on the disk
    • Workload access patterns such as sequential, random, read only, read write, write only.
    • Speed of the underlying disks, that is, if spinning disks such as SAS or SATA or faster ones such as SSDs
    • Dataset cached in the L1ARC caches and L2ARC caches.
    • Presence of Intent log ZIL to log the writes and respond quickly.
    • How the ZIL is configured, that is if it is on spinning disks or SSD disks.
    • Underlying RAID configuration, for example striped or mirrored.
    • System load in terms of CPU cycles available.

    What are the recommended QoS settings in a HA environment?

    In multiway HA, for example in a two- way HA, each Node should be provisioned max to 50 percent of the capacity.

    Can I set QoS for my backups?

    Not for the current release.

    Can I set QoS for my DR operations?

    Not for the current release.

    Can I get the same QoS on the secondary node in the case of a disaster?

    Yes, provided the secondary node has same system configuration as the primary.

    When do I use Grace?

    Particularly useful when you check if the IOPS and throughput set for a particular Storage Volume are correct. If a particular Storage Volume is continuously eating up grace, it is an indication that it is over-provisioned and deserves more IOPS/throughput.

    How can I compare the QoS values of selected Volumes?

    1. In CloudByte ElastiCenter, click Pools in the left pane.
    2. In the Pools page, select the Pool for which you want to compare the QoS values of the selected Storage Volumes.
    3. Select the Storage Volumes.
    4. Select the QoS parameter (IOPS, throughput, or latency) that you want to compare.
    5. Click Update.

    The chart on top of the page displays the comparison with time stamp as the reference.

    Component FAQs

    How to change the IP Address of ElastiCenter and Node?

    Changing the IP address of ElastiCenter and Node can be performed in the backend.

    To change the IP address of ElastiCenter,follow the steps given below:

    1. Change the IP address,subnet mask and default router address in the file /etc/rc.conf.
    2. Change the IP address in /etc/hosts
    3. Finally reboot the machine to ensure that all the services are started again.

    To change the IP address of a Node, follow the steps given below:

    1. Change the IP address,subnet mask and default router address in the file /etc/rc.conf.
    2. Provide the IP address of ElastiCenter in /usr/local/agent/listener/cbc.conf.
    3. Change the IP address in /etc/hosts
    4. Change the IP address in /usr/local/etc/apache22/extra/httpd-ssl.conf
    5. Finally reboot the machine to ensure that all the services are started again.

    Licensing

    When you install the Community Edition of CloudByte ElastiStor, a free perpetual license file is already uploaded to ElastiCenter. You can use the license for up to 25TB usage of storage on CloudByte ElastiStor.

    The license file has relevant details that implement license to use various features that you have purchased. CloudByte provides license file in the format L4J.

    The following FAQs help you with licensing.

    How do I access license details?

    1. Click Admin (at the top-right corner of the page).
    2. Select License from the drop-down list.

    licensing_click_license

    The License page appears.

    I want to evaluate CloudByte ElastiStor. How will the trial license be enforced?

    When you install a the Community Edition of CloudByte ElastiStor, the free  perpetual license file is, by default, uploaded. You need not do any licensing tasks.

    I received the license file from CloudByte. How will I proceed?

    1. Place the license file (with the extension .l4j) on the machine from which you access CloudByte ElastiCenter.
    2. Log in to CloudByte ElastiCenter.
    3. In the Actions pane, click Upload New License and then Upload License.

    license_2

    The Add License wizard appears.

    licene_upload_wizard

        1. Choose the license file that you have received and then click Upload.

    The Check screen confirms the validity of the license and the Finish screen provides the license details. When you get back to the License page, all license details are listed.

    Can I check the past licensing activities?

    In the License page, click View History. The details of the license are listed.

    Can I get support from CloudByte for the Community Edition of the product?

    For Community Edition, support is limited to basic setup. Contact CloudByte technical support at support@cloudbyte.com

    Glossary

    Glossary familiarizes the terms specific to ElastiStor.
    Terms Description
    Account An entity with specific storage needs. Account represents a department of an Enterprise or a customer of a Cloud Service Provider.
    Alerts Notifications that demand action. Alerts can be on a range of issues such as network cable pullout or degradation of a Pool.
    Asynchronous replication The process of writing data to local storage and then queuing it up for replication on remote storage at assigned time intervals. If the local storage fails before the data is written in remote storage, then replication fails.
    Auto-Provisioning ElastiStor can automate Node selection and resource allocation if you provide the required SLA/QoS parameters. Sensing the level of storage performance and capacity the application requires, ElastiStor automatically allots the right Pool.
    Block Size The size of a block in data storage and file systems. Block is a sequence of bytes or bits, having a nominal size.
    CIFS For details, see http://technet.microsoft.com/en-us/library/cc939973.aspx
    HA Group Houses a group of Nodes. HA Group enables takeover during failures. Workload of a failed Node is assigned to  another Node in the same HA Group based on availability and performance requirements.
    Dashboard A graphical representation of the key performance indicators. It presents an overview of all the Sites in ElastiCenter in an organized manner. You can update information instantaneously.
    Delegated Administration The process of distributing administrative tasks and content in the portal to dedicated administrators. Using access control lists, you determine the actions administrators take on various resources. Delegated administration roles are mapped to administrative functions using security policies. You can create and maintain separate administration capabilities depending on your needs.
    Disaster Recovery Disaster implies unplanned outage. Your storage system must be capable of effective backup and recovery so that there is no damage to the data that is handled in the case of any adversity
    Disk Array Popularly called JBODs, disk array is a set of disks clubbed to single disk shelf.
    Disk Type The type of disk supported by CloudByte ElastiStor. The supported disk types are SAS, SATA, and SSD.
    Domain Search Searching the DNS to which you want to add a controller.
    Event Any storage activity. ElastiStor notifies events based on the configuration.
    FC (Fibre Channel) A high-speed interconnect between controllers and back-end disk enclosures. FC components include HBAs, hubs, and switches. The term also refers to a high-speed, fully duplex serial communication protocol permitting data transfer up to 10GB per second.
    FTP (File Transfer Protocol) An application layer protocol used to transfer bulk-volumes of files between machines or hosts.
    Global Settings Lets the administrator configure options that control ElastiStor.
    Grace Provisioning of Pool’s unused IOPS/Throughput to Storage Volumes based on their performance requirements.
    High-Availability High Availability minimizes/prevents the consequences of downtime in the storage setup. A typical High Availability environment comprises of two setups: one active while the partner remains dormant. In a downtime, the passive setup takes over the storage tasks that the active setup was performing. This effects a reversal of states each setup was in. When the downtime is over, all events are given back to the original active setup.
    Node Physical machines on which you configure ElastiStor.
    Initiator Group When an initiator group is associated with a LUN, only initiators from that group can access the LUN. Initiators are identified by unique addressing methods.
    IOPS (Input/Output operations per second) The number of READs or WRITEs per second. It is used to measure the performance of storage solution. Total IOPS is the average input/output operations per second, Read IOPS: is the average READ operations per second, and Write IOPS is the average WRITE operations per second.
    iSCSI Internet Small Computer Systems Interface is a client-server protocol used to enable the transfer of SCSI packets over a TCP/IP (Ethernet) network.
    Lagg Interface Allows integration of multiple network interfaces with a single virtual interface. This helps in fault-tolerance and high-speed multi-link throughput.
    LUN (Logical Unit Number) Unique address to identify a logical unit. Logical unit is the conceptual subunit of a storage disk or set of disks.
    Mirrored Disks A High Availability setup where you have a different set of disks on each node. Active disks are replicated/mirrored on the partnering node.
    Mirroring Storing duplicate copies of data on one or more sets of additional Storage Volumes, apart from the set of Storage Volume that stores the original copies of data.
    Monitoring Provides an intuitive visualization of storage statistics. Monitoring foregrounds relevant back end activities in an easy user interface for the administrator.
    Network Failure Indicates that the system is unable to reach the network. For example, due to physical port failure.
    NFS  A distributed file system protocol that lets clients access files over a network in the same way they access local storage.
    Physical Infrastructure Real entities pertaining to the hardware.
    Pool Physical storage devices on which you store data.
    Provisioning A set of steps to allocate storage to Nodes and applications. For example, creating Storage Volumes in Pools.
    QoS (Quality of Service) Lets you easily commission storage with guaranteed IOPS at various levels. You can decide to configure QoS at a Pool level, VSM level, or Storage Volume level.
    Report Detailed information related to configuration. Use Configuration Reports for component configuration details. Dynamic Reports provide QoS statistics.
    Rest APIs Every action performed at ElastiStor admin console translates into a REST based API call in the back end. This enables administrators to fully manage ElastiStor from their portals. CloudByte plugin for VMware vCenter (also based on REST API) enables storage management from vCenter.
    Shared Disks A High Availability setup where you have a common set of disks shared between primary and secondary nodes. The disks can be either hard disks or iSCSI disks.
    Shared Storage Storage devices that are connected to and used by two or more systems.
    Site Represents a data center or part of a data center. Building storage infrastructure starts with the creation of Site. It is the fundamental infrastructure unit where your Node, storage, and network infrastructure reside.
    Snapshot Copy of a Storage Volume created at specific intervals.
    Storage Capacity The overall disk space and not the free disk space.
    Striping Writes data across two or more disks in an array, but utilizes only a part of the space on each disk. The amount of space used by stripe on each disk is always the same. A virtual disk may write several stripes on the same set of disks in the array.
    Synchronous Replication The process of writing the same data to two separate volumes, stored on different physical hardware, before the application receives an I/O complete message. This results in both the volumes being always in sync.
    Takeover The process of taking over the storage control activity from a node. Typically, when there is a downtime on the primary node, the secondary node takes over the control of storage.
    Thin Provisioning The process of optimizing efficiency of using the available storage space. It is the allocation of disk storage space flexibly among multiple users, based on the minimum space required by each user requires at any given time.
    Throughput Amount of work a system can perform at specific intervals. It is also the amount of data moved successfully from one place to another in a given time period.
    VSM (Virtual Storage Machine) Virtual storage controller capable of hosting Storage Volumes and LUNs.
    VSM Architecture Unique to CloudByte ElastiStor, this is a patented architecture. In a Storage Controller Node, each application is fully isolated across all storage stack levels and unified under a Virtual Storage Machine (VSM). VSM isolation allows controller  resources allotted to each applications to be easily monitored, controlled, and provisioned.
    VMware vSphere client A Microsoft Windows desktop application that enables you to access VMware ESXi and VMware vCenter