Description

What all do I need to do before I start configuring the cloudian on Backup Exec?

• Configure the Cloudian HyperStore server in your environment.
• Obtain the Cloudian HyperStore Server’s access key ID and secret access key.
• Create buckets in the Cloudian HyperStore Server.
• Create a cloud instance for the private cloud storage, i.e. Cloudian HyperStore Server, in BE Media Server.
• Ensure that the DNS is updated with the host and IP details so that both BE and the Cloudian server can communicate with each other.
• Sync the time of your media server with the time of your cloudian storage server.

Note: In this article, sometimes the Cloudian HyperStore may be referred to as a private cloud storage server.


Where can I find the Access Key and the Secret access key on the HyperStore Server?

1. Launch the Cloudian Management Console.
2. Create a new group name, user ID and password.

3. Click the drop-down arrow next to the user name and then click Security Credentials. The Access Credentials page is displayed.

4. On the Access Credentials page, the Access Key ID and the Secret Key are displayed. To get the password, click the View Secret Key link. Save these credentials.

How do I create buckets on the Cloudian HyperStore Server?
Launch the Cloudian Management Console and logon with your user id. Click Buckets & Objects > New. To create the bucket, add a Bucket Name, Region, and Storage Policies. Click Create.
The bucket name must match the following Backup Exec naming requirements.

• Bucket names can contain lowercase letters, numbers, and dashes (or hyphens).
• Bucket names cannot begin with a dash (or a hyphen).

What are the different commands to create, get, set, and remove the cloud instance on Backup Exec?
Following BEMCLI commands were introduced in Backup Exec 15 Feature Pack 5 to provide a way to create a cloud instance:

• New-BECloudInstance
• Get-BECloudInstance
• Set-BECloudInstance
• Remove-BECloudInstance

You can launch the BEMCLI interface from Start > App Menu or :\Program Files\Veritas\Backup Exec

New-BECloudInstance
Creates and configures a new cloud instance in Backup Exec.

Syntax
New-BECloudInstance [-Name] [] [-Provider] [] [-ServiceHost] [] [-SslMode] {Disabled | AuthenticationOnly | Full} [-HttpsPort []] [-Endpoint []] [-HttpPort []] [-UrlStyle {Unknown | Virtual | Path}] [-Confirm []] [-WhatIf []] []

Parameters (Mandatory) -

• Name: Name of the new cloud instance. Cloud instance name must match the Backup Exec naming requirement.
  • Instance names can contain letters, numbers, and dashes (or hyphens).
  • Instance names cannot begin with a dash (or a hypen).
• Provider: Specifies the provider of the cloud instance. Only private cloud provider name can be specified.
• ServiceHost: Specifies the service host of the cloud instance. ServiceHost should be unique for each cloud instance that is created on the server.
• SslMode:  Specifies the SSL mode that Backup Exec will use for communication with the cloud storage server. The valid values are:
  • Disabled – Do not use ssl.
  • AuthenticationOnly – use ssl for authentication only.
  • Full – use ssl for authentication and data transfer also.

Note: Backup Exec supports only Certificate Authority (CA)-signed certificates while it communicates with cloud storage in the SSL mode. Ensure that the private cloud server has CA-signed certificate. If it does not have the CA-signed certificate, data transfer between Backup Exec and cloud provider may fail in the SSL mode. User may choose to opt out of SSL and set SSLMode as Disabled.

More details on SSL is available in the Admin Guide.

Optional Parameters -

• UrlStyle - Specifies the URL style of the cloud instance. The valid values are :
  • Unknown – do not set any value. Will default to Path.
  • Virtual - In a virtual-hosted–style URL, the bucket name is part of the domain name in the URL. For example: http://bucket.s3.amazonaws.com

If you are providing UrlStyle as Virtual for your cloud instance, ensure that you can ping and resolve the bucket name from a virtual hosted style URL. In a virtual-hosted–style URL, the bucket name is part of the domain name in the URL. For example: http://bucket.s3.amazonaws.com. In such case you should be able to resolve and connect to bucket.s3.amazonaws.com. You may want to add an entry in your DNS to resolve the bucket name in virtual style URL.

• Path - In a path-style URL, the bucket name is not part of the domain (unless you use a region-specific endpoint). For example: US East (N. Virginia) region endpoint, http://s3.amazonaws.com/bucket.

If you are providing UrlStyle as Path for your cloud instance, ensure that you can resolve and connect the service host from your Backup Exec Server. If not, please add an entry in windows host file to resolve the service host from your machine.

Ensure that the URL is getting resolved from media server. Media server is able to resolve and ping the cloud storage server.

• HttpPort - Specifies the http port of the cloud instance. Default port is 80.
• HttpsPort - Specifies the https port of the cloud instance. Default port is 443.
• Endpoint – specifies the service endpoint.

Examples –

New-BECloudInstance -Name "test1" -Provider "cloudian" -ServiceHost "s3-india.cloud.dom" -HttpPort 80 -HttpsPort 443 -SslMode Disabled -UrlStyle Path

This command creates a cloud instance with name test1 of type cloudian pointing to service host s3-india.cloud.dom. To access the bucket, uses Path style url and ssl mode is set as disabled. Http and https port are configured as 80 and 443.

New-BECloudInstance -Name "test1" -Provider "cloudian" -ServiceHost " s3-india.cloud.dom "–SslMode AuthenticationOnly –UrlStyle Path

This command creates a cloud instance with name test1 of type cloudian pointing to service host s3-india.cloud.dom. To access the bucket, uses Path style URL and ssl mode is set as AuthenticationOnly. Http and https port are not configured hence will use default port number i.e. 80 and 443 respectively.



You can also create the cloud instance by just giving the command New-BECloudInstance and then entering the parameter details individually at each prompt.




Get-BECloudInstance

Gets all of the custom (private) cloud instances configured in Backup Exec. Without parameters, Get-BECloudInstance gets all the private cloud instances configured in Backup Exec. You can also specify a private cloud instance by instance name or pass a private cloud instance object through the pipeline to Get-BECloudInstance.

Parameters (Optional)

• Name: Specifies one or more cloud instances by cloud instance name (wildcards accepted).
• Id: Specifies one or more cloud instances by cloud instance ID (Guid). To specify multiple IDs, use commas to separate the IDs.

Example 1
C:\PS> Get-BECloudInstance
This command gets all of the cloud instances.
Example 2
C:\PS> Get-BECloudInstance -Name "test1"
This command gets the cloud instance named "test1".



Set-BECloudInstance

Sets the properties for a Backup Exec cloud instance. You can modify all the settings, except the name and provider of an existing cloud instance.

Syntax
Set-BECloudInstance -InputObject [] [-Endpoint []] [-HttpsPort []] [-SslMode {Disabled | AuthenticationOnly | Full}] [-ServiceHost []] [-HttpPort []] [-UrlStyle {Unknown | Virtual | Path}] [-Confirm []] [-WhatIf []] []
Example
 
C:\PS> Get-BECloudInstance "test1" | Set-BECloudInstance -ServiceHost "s3-renamed.cloudian.com"

These commands change the service host property of cloud instance named "test1" to “s3-renamed.cloudian.com ".




Remove-BECloudInstance
Removes a cloud instance configured in Backup Exec. The cloud instance is deleted only if there is no private cloud storage attached to the cloud instance.  If you want to delete the cloud instance, you have to delete the private cloud storage devices associated with the cloud instance on the Backup Exec media Server first and then delete the cloud instance.

Syntax
Remove-BECloudInstance -InputObject [] [-PassThru []] [-Confirm []] [-WhatIf []] []

Example

C:\PS> Get-BECloudInstance "test1" | Remove-BECloudInstance
This command remove a cloud instance named "test1".



You are now, all set to start configuring the cloudian storage with Backup Exec 16.


How do I configure the storage for Cloudian HyperStore with Backup Exec 16?
To configure the storage:

1. Navigate to the Storage tab and click Network storage > Cloud Storage.

2. Enter a name and description for the cloud storage.

3. Click S3 to add the Private Cloud storage.

4. Add the Server name in the following format: “cloudian:”
5. For Logon account enter the Access Key ID for user name and Secret Key ID for the password.

6. Select the bucket which you want to use and then click Next.

7. Click Next.

8. Click Yes.

You can now start taking backups on your cloud storage using Backup Exec 16.


 

How to configure storage for Cloudian HyperStore with Backup Exec