CloudBoost Docu71141 NetWorker 8.x With EMC CloudBoost 2.1 Integration Guide
CloudBoost Docu71141 NetWorker 8.x With EMC CloudBoost 2.1 Integration Guide
x with EMC
CloudBoost
Version 2.1
Integration Guide
P/N 302-001-736
REV 1
Copyright 2016 EMC Corporation. All rights reserved. Published in the USA.
EMC believes the information in this publication is accurate as of its publication date. The information is subject to change
without notice.
The information in this publication is provided as is. EMC Corporation makes no representations or warranties of any kind with
respect to the information in this publication, and specifically disclaims implied warranties of merchantability or fitness for a
particular purpose. Use, copying, and distribution of any EMC software described in this publication requires an applicable
software license.
EMC, EMC, and the EMC logo are registered trademarks or trademarks of EMC Corporation in the United States and other
countries. All other trademarks used herein are the property of their respective owners.
For the most up-to-date regulatory document for your product line, go to EMC Online Support (https://support.emc.com).
EMC Corporation
Hopkinton, Massachusetts 01748-9103
1-508-435-1000 In North America 1-866-464-7381
www.EMC.com
Figures 5
Tables 7
Chapter 1 Introduction 11
NetWorker with CloudBoost...........................................................................12
Long term retention to the cloud...................................................... 12
Supported server and client versions.............................................................12
Cloud providers supported by CloudBoost appliances...................................13
Prepare for installing the CloudBoost appliance............................................ 14
Firewall port requirements.............................................................................15
CloudBoost reporting.................................................................................... 44
Upgrading a CloudBoost appliance............................................................... 45
CloudBoost integration with EMC Secure Remote Services ............................45
Registering CloudBoost with EMC Secure Remote Services............................ 46
Increasing the CloudBoost appliance site cache............................................47
Changing log levels for CloudBoost debugging.............................................. 47
Restarting a CloudBoost appliance................................................................48
Recovering a CloudBoost appliance.............................................................. 48
Deleting a CloudBoost appliance...................................................................50
As part of an effort to improve its product lines, EMC periodically releases revisions of its
software and hardware. Therefore, some functions described in this document might not
be supported by all versions of the software or hardware currently in use. The product
release notes provide the most up-to-date information on product features.
Contact your EMC technical support professional if a product does not function properly
or does not function as described in this document.
Note
This document was accurate at publication time. Go to EMC Online Support at https://
support.emc.com to ensure that you are using the latest version of this document.
Purpose
This document describes the integration of NetWorker with CloudBoost.
Audience
This guide is part of the CloudBoost documentation set, and is intended for use by
system administrators who are responsible for setting up and maintaining backups on a
network. Operators who monitor daily backups will also find this guide useful.
Revision history
The following table presents the revision history of this document.
Related documentation
The following EMC publications provide information about CloudBoost.
l EMC CloudBoost Release Notes
Contains information about new features and changes, fixed problems, known
limitations, environment and system requirements for the latest release.
l EMC CloudBoost 100 Installation Guide
Guide for installing the physical CloudBoost 100 appliance, and initial configuration
at command line interface.
l EMC CloudBoost Disk Array Expansion Shelf Installation Guide
Guide for installing the disk array expansion shelf for use with the physical appliance.
l EMC CloudBoost Hardware Component Replacement Guide
Guide for customers replacing hardware components for the CloudBoost physical
appliance.
You may find these publications helpful when integrating CloudBoost with different
systems.
l EMC NetWorker with EMC CloudBoost Integration Guide
Guide for integrating EMC NetWorker with EMC CloudBoost.
The CloudBoost appliance provides an integration into your existing supported backup
environment. This enables you to transfer backups to the cloud. The CloudBoost
appliance enables backups to public, hybrid, or private cloud storage.
CloudBoost decouples metadata from data, which removes a bottleneck for cloud reads
and writes. Encryption keys, metadata, and file system information are housed separately
from the data. All advanced data services, such as chunking, encryption, inline de-
duplication, compression, and bulk data transfers are performed separately from storing
the metadata.
CloudBoost is available as a physical appliance, a VMware virtual appliance, and a virtual
appliance resident in Amazon EC2.
CloudBoost is integrated with EMC Secure Remote Services, which may be enabled to
monitor the health of the appliances.
Individual CloudBoost deployments can support only one target object store. When a
cloud object store is selected and the CloudBoost appliance is configured, the appliance
is locked to that target. To change object storage targets, the appliance must be re-
deployed.
Introduction 11
Introduction
l Support for all clients cloning to the cloud for long term retention.
l Support for all clients back up to the cloud with the following exceptions.
n Microsoft Windows file system block-based backups
n Microsoft Exchange backups
n Microsoft Hyper-V backups
n VMWare image backups
Note
n The minimum version of NetWorker Mobile for Microsoft (NMM) that is supported
with CloudBoost is 8.2.3.6.
n Granular recovery from cloned image level backups (VMWare, Microsoft Hyper-V,
and Microsoft Exchange) is only possible if a backup is cloned back to local
storage first.
EMC ECS Appliance ECS Endpoint, ECS Access Key ID, ECS Secret Access Key
Amazon Web Services (S3) Storage Region, AWS Access Key ID, AWS Secret Access Key
AT&T Synaptic Storage AT&T Synaptic Subtenant ID, AT&T Synaptic User ID, AT&T
Synaptic Secret Key
Note
Microsoft Azure Storage (general Azure Account Name, Azure API Key
purpose accounts, replication
types LRS, GRS, RA-GRS) Note
Note
l Install the EMC NetWorker 8.x server if you have not all ready installed the server. For
more information, see the NetWorker 8.2.x Administration Guide.
Note
It is not recommended to route outbound http traffic from the CloudBoost appliance
through a proxy. This can create a performance bottleneck. In environments where
outbound http traffic is restricted, it is recommended to create an exception for the
appliance in the firewall after consultation with the IT security team.
For information about firewall ports for any system being deployed with CloudBoost, refer
to the documentation for that system.
For information about NetWorker, see Configuring TCP Networks and Network Firewalls for
EMC NetWorker at http://www.emc.com
Before you begin the installation and configuration of your CloudBoost appliance, it is
important that you understand all the requirements ahead of time.
l Solution requirements...........................................................................................18
l CloudBoost sizing and performance considerations.............................................. 19
l CloudBoost appliance cache sizing....................................................................... 21
Solution requirements
Requirements for the CloudBoost appliance.
Minimum deployment virtual machine requirements for ESX
These are the minimum and default requirements for the VMware ESX virtual CloudBoost
appliance.
l ESX 5 or greater
l 4 cores *
l 16 GB of RAM *
l 41 GB of OS and storage node hard disk (SSD recommended for storage)
l 40 GB of metadata store hard disk (SSD recommended for storage)
l 10 GB of site cache hard disk (SSD recommended for storage)
* Numbers must be doubled if a site cache is used.
For more information on metadata store and site cache hard disk sizing, see CloudBoost
sizing and performance considerations on page 19.
Large deployment virtual machine requirements for ESX
These are the requirements for a large deployment of the VMware ESX virtual CloudBoost
appliance.
l 8 cores *
l 32 GB of RAM *
l 41 GB of OS and storage node hard disk (SSD recommended for storage)
l Extendable up to 3 TB of metadata store hard disk (SSD recommended for storage)
l At least 200 GB expandable to 6 TB of site cache hard disk (SSD recommended for
storage)
* Numbers must be doubled if a site cache is used.
For more information on metadata store and site cache hard disk sizing, see CloudBoost
sizing and performance considerations on page 19.
Minimum deployment virtual machine requirements for EC2
These are the minimum and default requirements for the VMware EC2 virtual CloudBoost
appliance.
l 4 vCPUs *
l 16 GB of RAM *
l 100GB IOPS optimized SSD4 storage volume for appliance metadata (example: type
AWS EBS io1) per 400TB of logical backup data under management
The AWS EC2 m4.xlarge is suggested.
Note
Smaller environments can alternatively choose an instance with unified compute and
storage such as AWS EC2 m3.xlarge that includes 4 vCPUs, 15GB memory and 2x40GB
SSD storage.
For more information on metadata store hard disk sizing, see CloudBoost sizing and
performance considerations on page 19.
allows the appliance to address 200 TB of logical capacity. Therefore, to address the
maximum logical capacity of 6 PB, 3 TB of metadata space is needed.
The CloudBoost virtual appliance assumes that the underlying storage is protected. The
CloudBoost virtual appliance does not provide protection against a failed virtual data
disk.
De-duplication and cloud capacity
Both the physical and virtual CloudBoost appliances support up to 6 PB of logical
capacity using 3TB of metadata disk space. This is the total amount of unique data prior
to de-duplication. Based on preliminary test data, CloudBoost expects to achieve a 2x4x
range of de-duplication. Backups of file systems, applications, and databases where file
sizes are typically small are expected to achieve close to 2x de-duplication on average.
Backups of virtual machines where typical virtual disks sizes are larger could see up to 4x
de-duplication. Based on this range of de-duplication, each CloudBoost appliance can
support up to 6 PB of logical capacity. That said, proof of concept testing, or testing with
up-to-date, real data is recommended.
End-to-end bottlenecks
WAN bandwidth is expected to be the most common bottleneck. A properly-resourced
CloudBoost appliance can saturate a 1 GB/s link with 30 ms RTT latency without hitting
any limits within the VM itself. Object store ingest limits are another potential bottleneck.
In some cases we reach the objects/sec limit that can be sustained by a single logical
container in the object store.
Minimum WAN requirements
We recommend a minimum bandwidth of at least 10 Mbit/s to the cloud with a maximum
latency of less than 100 ms RTT for the CloudBoost solution. Extremely low bandwidth
links may result in backup and restore timeouts.
CloudBoost caching
The optional site cache allows backups to complete quickly over the LAN while trickling
more slowly over the WAN. This enables faster backup and recovery for the objects most
recently written to or read from the cloud. This persistent cache is flushed and reused as
needed during these processes.
The ingestion rate for a CloudBoost appliance without site cache enabled has been
measured at up to 100 MB/s. The site cache has a 50 MB/s ingestion rate for the 32 TB
physical appliance and 25 MB/s ingestion rate for all other appliances, improved by de-
duplication and compression, depending on the workload.
The size of the cache cannot be increased by growing the existing data disk size in
vCenter, nor can the size of the cache be reduced. The minimum size of the cache is 200
GB, and it can be increased to up to 6 TB on the virtual appliance by adding additional
disks that match the size of the existing site cache disks. The cache is firewall-friendly, in
that multiple ports do not need to be opened.
Use of the cache is advisable under these circumstances.
l Weak connection to the object store, where bandwidth is low with high latency,
anything less than 200 Mbps (25 MB/s) to the cloud store.
l You do not have streaming workload or continuous backup.
Do not use the cache if you get higher ingestion speed when connecting directly to the
cloud store. If use a site cache with higher ingestion speeds, your backups will exceed
the capacity of the cache.
Metadata disk pool
In addition to the operating system disk pool, there is a pool for metadata, and an
optional pool for the cache. Before starting the appliance, you must ensure that the size
of the metadata pool is the correct size. A 100 GB of metadata allows the appliance to
address 200 TB of logical capacity. To address the maximum logical capacity of 6 PB, 3
TB of metadata space is needed. If at a later date you need to support a larger logical
capacity, you may resize the metadata disk. You have to reboot the appliance in order for
the appliance to see the added capacity.
Multiple clone sessions
For parallelism, we recommend creating multiple AFTD devices under the /mnt/magfs/
base mount point within CloudBoost, and using one clone session per device. One
session per device is recommended for optimal performance and de-duplication. Multiple
clone sessions to the same device can result in lower de-duplication ratios and longer
clone times.
Note
If you are deploying using the AWS AMI, the use of site cache is not supported. The AMI
does not include a site cache hard disk.
The CloudBoost appliance arrives with this configuration, which is appropriate when site
cache is not enabled.
l 4-core virtual CPU
l 16 GB of RAM
l 41 GB of OS and storage node hard disk
l 40 GB of metadata store hard disk
l 10 GB of site cache hard disk
However, you can change these parameters in vCenter virtual machine configurations
before you begin initial CloudBoost configuration at the CLI. It is recommended that you
change these numbers to the appropriate levels based upon the amount of data you plan
to backup.
16 GB of RAM 64 GB of RAM
10 GB with no site cache enabled at least 200 GB site cache data disk, can be increased up to 6
TB
This chapter applies to installing the virtual CloudBoost appliance on ESX. For
information on installing the virtual appliance on Amazon EC2, see Deploy the
CloudBoost Appliance on page 25. For information on installing the physical appliance,
see the EMC CloudBoost Installation Guide.
You must obtain the .OVA file from https://support.emc.com to install the virtual
appliance.
Note
Results
The CloudBoost virtual appliance is installed.
After you finish
You must use the CLI for the virtual appliance to set its IP address and networking before
you can finish deployment within the EMC Cloud Portal.
Note
Site cache is not supported on Amazon EC2 because the network is too fast and disk
space is too expensive.
Procedure
1. Log in to the Amazon EC2 Dashboard, then open the AWS Marketplace.
2. Search for and choose the CloudBoost AMI.
3. Under Private Images, find and launch the CloudBoost image.
4. Under Instance Type, select 8 CPUs and 32 GB of memory.
5. Under Configure Instance Details:
a. Type the number of instances to create.
b. Choose the appropriate network and submask.
c. Enable Auto-assign Public IP.
6. Verify that under Add Storage for Root, Size (GiB) is set to 41, and that the EBS
volume is present for metadata.
The default size for the added volume is 40 GB. The size should be increased based
on a 1:4000 ratio.
7. Under Tag Instance, define up to 10 keys to assist with AMI management.
8. Under Configure Security Group, create or select a security group (set of firewall rules)
to allow or deny public access, keeping in mind the port requirements for the
CloudBoost appliance.
9. Review information about the instance, and if any changes are necessary click
Previous.
10. Choose or create a key pair to use when connecting to the CloudBoost appliance, and
then click Launch instances
Results
The CloudBoost appliance is launched and running in Amazon EC2.
After you start the CloudBoost appliance, you should configure its network settings.
By default, the CloudBoost appliance starts with the IP address obtained via DHCP. It is
also possible to manually set a static IP address.
Note
Both static IP and reserved IP using DHCP are supported. Dynamic DHCP is not supported.
It is best to assign static IP addresses using DHCP (via DHCP reservations) unless you
have disabled DHCP in the data center.
You must configure the resolvable fully qualified domain name (FQDN), such as
cloudboost.example.com. The FQDN must be registered in your DNS with both forward
and reverse domain name resolutions. The FQDN must be in lowercase.
You are required to change the default administrator password to one of your own
choosing, and then you can configure the remaining IP settings and hostname.
Note
The CloudBoost AMI automatically uses the default VPC settings for the appliances IP
address, DNS, and FQDN. If you need to change these network settings, you can use the
commands below.
Procedure
1. Open a CLI window on the CloudBoost appliance.
Option Description
vSphere In the vSphere client, right-click VM > Open Console.
client
EC2 a. Log in to EC2, select your CloudBoost appliance, and then click
Connect.
b. In the Connect To Your Instance wizard, choose whether to connect
with an SSH client or from the browser, and then follow the
instructions.
c. In the SSH terminal, run this command,
where private key is the private key you used as the key pair when
you installed your CloudBoost AMI.
4. To see the current network configuration of the appliance, run this command.
status
The status command also shows the ethernet interfaces to use in the net config
command.
admin@mag-fs> status
Host Configuration:
Hostname: hostname
Domain: domain
FQDN: fqdn
Version Information:
Version: version identifier
Revision: revision identifier
Network Interfaces:
name mode address netmask
---- ---- ------- -------
eth0 dhcp 10.5.96.123 address
Network Routes:
prefix netmask gateway
------ ------- -------
default 0.0.0.0 10.5.96.1
10.5.96.0 address *
DNS Configuration
DNS Servers: 10.5.96.91
Appliance status: Not yet registered
5. To statically set the IP address and netmask, run these commands. If you have
multiple networks you must run this command for each network listed in the status
command.
For example,
For example,
For example:
fqdn servername.yourcompanydomain
Note
For example:
fqdn cloudboost.example.com
9. To verify the networking setup and see the status of the appliance, run this command.
status
For example,
admin@mag-fs> status
Host Configuration:
Hostname: hostname
Domain: domain
FQDN: fqdn
Version Information:
Version: version identifier
Revision: revision identifier
Network Interfaces:
name mode address netmask
---- ---- ------- -------
eth0 static 10.5.96.123 address
Network Routes:
prefix netmask gateway
------ ------- -------
default 0.0.0.0 10.5.96.1
10.5.96.0 address *
DNS Configuration
DNS Servers: 10.8.192.91
Appliance status: Not yet registered
Results
After you have verified the system's basic networking settings, you can register the
appliance and then configure CloudBoost using the EMC Cloud Portal.
Note
Other commands are also available from the command line. To get help, type help or ?.
After you install a CloudBoost appliance and configure it at the CLI, you can register it and
complete configuration in the EMC Cloud Portal. You must create a cloud profile for the
storage provider the appliance will use before you can complete its configuration.
Option Description
vSphere In the vSphere client, right-click VM > Open Console.
client
EC2 a. Log in to EC2, select your CloudBoost appliance, and then click
Connect.
b. In the Connect To Your Instance wizard, choose whether to connect
with an SSH client or from the browser, and then follow the
instructions.
c. In the SSH terminal, run this command,
where private key is the private key you used as the key pair when
you installed your CloudBoost AMI.
Note
The result should be similar to the following, with a list of possible cloud profiles that
are available.
The result should indicate that various BSV CLI commands are being validated.
register
Note
If you have registered a physical CloudBoost appliance, you should immediately apply
any available system upgrades. For more information, see Upgrading a CloudBoost
appliance on page 45.
If you have an EMC Secure Remote Services (ESRS) gateway installation, you can also
register your CloudBoost appliance to be monitored by ESRS. For information about
installing an ESRS gateway and registering a CloudBoost appliance with ESRS, see
Monitor, Manage, and Support CloudBoost on page 43.
3. Share the credentials to be used when mounting with the Windows client with the
people who perform that task.
The user name is remotebackup. The password is the one you created in Step 2.
Results
Remote Windows clients can mount with these credentials. For information about the
Windows client, see the EMC CloudBoost Client Guide.
Procedure
1. Open a CLI window for the appliance, and then log in with the admin username and
password.
2. Run this command.
remote-mount-password disable
Results
For information about the Windows client, see the EMC CloudBoost Client Guide.
4. In the list of appliances, click the appliance that you want to configure.
The Overview page of the appliance opens.
Note
If you are preparing an appliance as the target for recovering a failed appliance,
upgrade if necessary to ensure the target appliance is running the same version as the
appliance to be recovered. Do not configure the target appliance any further. Failed
appliances cannot be recovered to configured target appliances.
Note
8. To prevent this appliance from using a site cache, deselect Enable Site Cache.
Note
Note
CA-signed certificates are preferred because of the higher level of security available
from trusted certificate authorities. To obtain a CA-signed certificate, visit the website
of your preferred authority.
10. To minimize clock drift, select Enable NTP checkbox, and then enter the URL or IP
address for at least one NTP server.
11. To set the frequency of backups, select a schedule for Backup Frequency.
Note
The backups referred to here are for the system state of the appliance and for the
stored metadata. This is not a reference to any backup software integration.
12. To use asymmetric encryption keys, select Enable backup encryption with asymmetric
keys.
a. Refer to the displayed instructions to help you create your private and public
encryption keys. This is the only method of asymmetric key creation supported for
the CloudBoost appliance.
b. Copy the entire public key from the resulting output file and paste it into the text
box below the instructions on the Configure tab.
c. Copy the entire private key from the resulting output file and paste it somewhere
safe. If you created a pass phrase, copy that as well.
CAUTION
You must safely store your private key and pass phrase. They must be provided to
decrypt a recovered backup. Appliances backed up using the public key provided
on the Configure tab cannot be recovered without your private key and pass
phrase.
13. Review your selections, then click Update Configuration to save these settings for the
appliance.
Results
The appliance is configured and a backup immediately begins.
Read this chapter if you are integrating CloudBoost with NetWorker Server 8.1x or
8.2x.
7. In the Networker Device Name field, type the FQDN of the CloudBoost appliance, add
a comment if you want, and then click Next.
8. Select Label and Mount device after creation, select Backup Clone under Pool Type,
select Default Clone under Pool, and then click Next.
9. Review the configuration, click Configure, and then click Finish.
10. Right-click Clones, and then click New.
11. Type the name of the clone and a comment in the Name and Comment fields, and
then in the Storage node to WRITE save sets drop-down select the CloudBoost storage
node you created.
12. Make any other changes you want to the clone, then click OK.
13. Click the Monitoring tab.
14. Under Clones, click the Clones tab, and then right-click the newly created clone and
click Start.
15. To verify that CloudBoost is receiving clones from NetWorker, log in to the EMC Cloud
Portal.
a. Click Cloud Portal, and then click CloudBoost.
b. Select the appropriate appliance.
c. Under Storage Use History at the bottom of the Overview tab, review the storage
consumption information for data sent to the share and received by CloudBoost.
For information about monitoring a CloudBoost appliance, see the Monitor, Manage,
and Support CloudBoost on page 43.
Results
You may also test restoring data from the share by using the NetWorker Recovery Wizard.
You can see status and performance information for CloudBoost appliances, change log
levels, upgrade, restart, recover, and remove appliances. You can also register
CloudBoost appliances with EMC Secure Remote Services.
If CloudBoost appliances are not registered with EMC Secure Remote Services, you will
need to manually monitor their health, collect and review logs, and contact EMC Support
should any issues arise.
l CloudBoost reporting............................................................................................ 44
l Upgrading a CloudBoost appliance....................................................................... 45
l CloudBoost integration with EMC Secure Remote Services ....................................45
l Registering CloudBoost with EMC Secure Remote Services.................................... 46
l Increasing the CloudBoost appliance site cache....................................................47
l Changing log levels for CloudBoost debugging...................................................... 47
l Restarting a CloudBoost appliance........................................................................48
l Recovering a CloudBoost appliance.......................................................................48
l Deleting a CloudBoost appliance...........................................................................50
CloudBoost reporting
You can monitor the health of CloudBoost appliances and see the amount of data sent
over time, and see the corresponding storage consumed over time by de-duplicated data.
When you sign in to the EMC Cloud Portal, click Cloud Portal, then CloudBoost, and then
Appliances to see your list of appliances. On the Appliances page, you can see the status
of each appliance and see whether an upgrade is available. To filter the list of
appliances, type a portion of the name of the appliance or appliances you want to see.
Figure 5 Appliances page
Select an appliance to see information about it, including its configuration and storage
use history.
Figure 6 Appliance configuration details and storage use history
Under Configuration, you can see a brief summary of some of the settings made on the
Configure tab.
Under About, you can see information about the appliance, including how much storage
is used. You can see the deduplication ratio, and the affect of deduplication and
compression as a percentage of the original size of the data, which is sent to the cloud
storage provider.
Under History, you can see the deployment and upgrade history for the appliance.
Storage Use History shows how much raw data the appliance has received, and how
much deduplicated and compressed data was sent to the cloud storage provider. You can
change the view from the default, Hours, to show storage used over the course of days,
weeks, months or years.
You can install the EMC Secure Remote Services gateway version 3.6.0 or later in a VM
separate from the CloudBoost appliance. After your CloudBoost appliance is registered in
the EMC Cloud Portal, you can then also register it with ESRS.
For information about installing the ESRS gateway, refer to the EMC Secure Remote
Services Virtual Edition topics at these sites.
l https://support.emc.com/products/37716_EMC-Secure-Remote-Services-Virtual-
Edition
l https://support.emc.com/products/37716_EMC-Secure-Remote-Services-Virtual-
Edition/Topics/pg58757/
Note
When you install the ESRS gateway, make note of the IP address or URL and the serial
number. You will need to provide them at the CloudBoost CLI when you register the
appliance with ESRS, along with the SID from the email sent from EMC ESRS Support. For
information about registering your CloudBoost appliance with ESRS, see Registering
CloudBoost with EMC Secure Remote Services on page 46.
Note
If a firewall exists between the CloudBoost appliance and the ESRS server, certain ports
(for example, port 9443) must be open. For information about which ports must be
opened, see Firewall port requirements on page 15.
Procedure
1. Find your ESRS SID in the email from EMC ESRS Support.
2. Have the IP address or URL and the serial number of your installed ESRS gateway
available.
3. Establish an SSH session to the IP address for the CloudBoost appliance and log in
with the administrator credentials.
4. Run this command.
esrs_gateway is either the IP address or the FQDN for your ESRS gateway virtual
machine. username and password are the credentials used to set up your ESRS
gateway. sid is the ESRS serial number provided by EMC ESRS Support in an email.
gateway_sn is the serial number for the ESRS gateway.
Note
Results
The CloudBoost appliance is registered with ESRS, and continuous support monitoring
begins.
reboot
Results
The appliance becomes inactive during the soft restart, like any other computer, then
becomes active again. The restart event is logged.
Note
Do not configure the target appliance any further. Failed appliances cannot be recovered
to configured target appliances.
4. Verify that the unconfigured appliance is running the same version as the failed
appliance. Upgrade if necessary.
5. Recover the failed appliance.
l Find the inactive appliance on the Appliances page, and then click Recover for that
appliance.
Figure 8 Appliance to recover
l To test the recovery process with an active appliance, select the appropriate
appliance on the Appliances page, and then on the appliance details page, click
Commands, and then Force recover appliance.
The Recover tab opens.
6. If the appliance being recovered had been configured to use asymmetric encryption,
provide the private key required to decrypt the backed up data.
a. If a pass phrase was created to use with the private key, type that pass phrase.
7. Select the appropriate CloudBoost appliance as the recovery target.
Note
The recovery target appliance must be running the same version of the CloudBoost
software as the appliance being recovered.
The recovery target appliance adopts the FQDN and display name of the recovered
appliance.
8. Provide the remaining configuration information, and then click Start Recover
Operation.
to delete an appliance set up for testing purposes, if its backups had value only for
testing.
An appliance that is inactive or unusable appears in red on the Appliances page. When
you select such an appliance, the status at the top of the appliance detail page is Down.
An appliance is considered active if sufficient configuration has happened, even if no
backups have been made. If an error was made during configuration, such as choosing
the wrong cloud profile, you can delete an active appliance so that you can redeploy it.
Note
If a CloudBoost appliance had been actively used to back up production data, you should
recover it, rather than remove it. For information about recovering an appliance, see
Recovering a CloudBoost appliance on page 48.
Procedure
1. Carefully identify the appliance that must be deleted.
2. Open a CLI window on the CloudBoost appliance.
Option Description
vSphere In the vSphere client, right-click VM > Open Console.
client
EC2 a. Log in to EC2, select your CloudBoost appliance, and then click
Connect.
b. In the Connect To Your Instance wizard, choose whether to connect
with an SSH client or from the browser, and then follow the
instructions.
c. In the SSH terminal, run this command,
where private key is the private key you used as the key pair when
you installed your CloudBoost AMI.
factory-reset erase-everything
The appliance is reset back to its original pre-deployed state. This includes resetting
CloudBoost to its original version. Any upgrades that occurred during its deployment
are no longer in effect.
4. To delete all the data in the cloud, run this command.
destroy-appliance
5. Use a web browser to sign in to the EMC Cloud Portal with the credentials you created
from your invitation.
6. Click Cloud Portal, and then click CloudBoost.
7. In the left menu, click Appliances.
8. Select the appliance to delete.
9. On the appliance details page, click , and then Delete Appliance.
10. In the confirmation message, click Ok.
The Appliances page appears, where you can verify that the appliance was deleted.
Results
The EMC Cloud Portal no longer has a record of this appliance. The appliance is reset to
its original state. You may redeploy the appliance as if it were new.
In production environments, you should use a wildcard SSL certificate signed by a trusted
Certificate Authority. Wildcard certificates are public key certificates that can be used
with multiple sub-domains. Only a single level of sub-domain matching is supported.
The CA-signed wildcard certificate must be suitable for SSL server usage and must cover
all the host names in the CloudBoost deployment. Certificates that do not cover your
entire CloudBoost deployment will be rejected. Additional names (beyond the server the
certificate is being installed on) such as CNAMEs are not automatically validated; the
administrator must manually validate these names.
The signed certificate must not expire in less than one month. If you attempt to upload a
certificate that will expire in less than one month, the server will reject it.
If your signed certificate is due to expire within three months, a warning message
appears within CloudBoost appliance management in the EMC Cloud Portal until the
issue is resolved.
Note
Because self-signed SSL certificates are less secure than those signed by a trusted
Certificate Authority, self-signed certificates should be used only for test deployments.
CloudBoost uses the certificate storage solutions within the operating systems for Mac,
Windows and iOS.
Note
If you use a self-signed certificate, you must push the root CA certificate to the certificate
store of each device.
Note
Changing the SSL certificate has no impact on the data or metadata of the share. Before
you apply your new certificate, you should plan for a short service outage. You must stop
all services for the share before you can update the certificate.
Selecting Use the default self-signed certificate in the EMC Cloud Portal does not provide
a certificate for you to deploy on other machines. Therefore, if you wish to access any
deployed share from a client running on a separate machine, you should generate your
own self-signed certificate.
[req]
distinguished_name = req_distinguished_name
req_extensions = v3_req
[req_distinguished_name]
countryName = US
localityName = Mountain View
organizationalUnitName = <%= brand_name %>
commonName = EMC, inc.
emailAddress = [email protected]
[v3_req]
keyUsage = keyEncipherment, dataEncipherment
extendedKeyUsage = serverAuth
subjectAltName = @alt_names
[alt_names]
DNS.1 = cloudboost1.example.com
DNS.2 = cloudboost2.example.org
Once the private key is generated, a Certificate Signing Request can be generated.
4. To use the CSR to self-sign the CSR, run this command.
5. To self-sign the certificate request, setting a life-span of the certificate, run this
command.
openssl x509 req days 365 in host.csr signkey host.key out host.crt extensions
v3_req extfile config.cnf
6. To combine the files to generate a valid .pem file, run this command.
Note
Procedure
1. In a Linux terminal, execute this command.
Where:
Option Description
foo.com.chain.pem is the concatenation of the intermediate certificate (root is the
last)
foo.com.pem is the *.foo.com certificate
foo.com.key is the private key for the above certificate
passphrase.txt contains the pass phrase to use for the .p12 file
Option Description
Use the default self- This is selected by default. This is acceptable in test
signed certificate environments, but should not be used in a production
environment.
Provide a CA-signed Upload a CA-signed wildcard certificate in the form of a .p12
certificate or .pfx file and if necessary, type the key file password.
Note
These administrative tasks are common across the entire EMC Cloud Portal.
Delete a User
You can delete one or more user accounts with the User Management function in the
portal. Before any account is deleted, however, you are asked to confirm that you want to
delete. For details, see Deleting a Cloud Portal user account on page 63.
Option Description
On the View Users page, select the Opens a slide-out dialog where you can add
Users mode, and then click Invite the email addresses of users you want to
Users. invite to establish an account.
On the View Users page, select the Opens a slide-out dialog where you can add
Invitations mode, and then click the email addresses of users you want to
Invite Users. invite to establish an account.
5. When you have entered email addresses for those you want to invite, click Invite.
a. A popup appears to notify you that the email has been sent to the invitee.
b. The user receives the email invitation, and the email address of the user is added
to the list of invitations sent.
c. (Conditional) If the user accepts the invitation, the email address is added to the
list of users.
d. (Conditional) If the users neglects the invitation, it expires in 90 days.
Note
You can re-invite a user who has already accepted an invitation, but you must use an
alternate email address to add the recipient as a new user.
If the user does not accept the invitation, you can resend it. For more information, see
Resending a Cloud Portal account invitation on page 60.
If you decide to withdraw the user invitation before it is accepted, you can delete it.
For more information, see Deleting a Cloud Portal account invitation on page 61.
Note
You can re-invite a user who has already accepted an invitation, but you must use an
alternate email address to add the recipient as a new user.
If you decide to withdraw the user invitation before it is accepted, you can delete it.
For more information, see Deleting a Cloud Portal account invitation on page 61.
4. When you have selected email addresses for the invitations you want to delete, click
Delete Invitation (or click Delete Invitations, if multiple invitations are to be deleted).
A popup appears to notify you that the email to the invitee(s) has been deleted.
Note
Selecting more than one email address removes the Edit User button from the page.
One of the exposed controls is the Invite Users button and the other is the Delete User
button. For more information about these options, see Adding a new user and sending
a Cloud Portal account invitation on page 59 or Deleting a Cloud Portal user
account on page 63.
6. When you have made the changes you want, click Update.
A popup appears to notify you that the user details have been updated.
Note
One of the exposed controls is the Invite Users button and the other is the Delete User
button. For more information about these options, see Adding a new user and sending
a Cloud Portal account invitation on page 59 or Deleting a Cloud Portal user
account on page 63.
Note
For more information about the other options, see Adding a new user and sending a
Cloud Portal account invitation on page 59 and Editing a Cloud Portal user account on
page 61.
Option Description
Click Delete User. Use this method to delete the user account directly from
the View Users page.
Click Edit User > > Use this method to delete the user account if you decide
Delete User. to do so while in the Edit User mode.
Both of these methods effectively delete the selected user account from Cloud Portal.
Email notifications
By default, email notifications for events are turned on, with the following event types
available for selection:
l Alerts (critical events that require prompt action)
l Errors (operational errors that have occurred in the portal or in a portal plugin)
l Warnings (preemptive messages that draw attention to abnormal operating
conditions)
You can clear the selection of any of these settings or add the Info event type (that is,
status messages regarding the portal or portal plugin operations) to the selection.
The default recipient of these event email messages is the administrator whose email
address was provided when the account was set up or edited. You can add other email
recipients as needed.
Toast notifications
A toast notification is an onscreen alert message that you see as a text box sliding up
from behind the action bar at the bottom of the page. The toast displays for 7 seconds
before fading out. Its content is also added to a drop-down list (signified by the icon)
available in the portal utility bar. While it displays, you can click or tap the toast
notification alert for more information, or you can do the same from the drop-down list. If
an alert remains unopened, the portal reminds you.
By default, toast notifications for events are turned on, with only Alerts selected to
display. You can clear the selection Alerts, or you select other event types (Errors,
Warnings, Info) to display.
1 Active alerts
2 Inactive alerts
3 Errors
4 Warnings
Within each of these categories, the events are sorted by most recent first. Use the
controls at the bottom of the page to navigate to all the events, paged in groups of 30.
The
Cloud Portal Help Page
Note
The help mode icons on the Help home page are repeated as menu options at the top of
every Help subpage. Each subpage also includes a (Search) feature that restricts
its queries according to the help mode selected.
Product
This drop-down selector lists all the EMC Cloud Portal plugins that you have purchased.
Selecting a product name filters the help resources to include items relevant to that
product only.
Community
This button links to the EMC product community page that matches the product filter you
have selected. The respective community pages, which are located outside the portal,
have a built-in Search function that queries community-specific topics only.
Knowledge Base
This button links to a Knowledge Base home page that lists trending and recently
updated Knowledge Base articles. These articles match the product filter that you select.
You can search the entire Knowledge Base using your own search term or you can use
one of the listed popular search terms.
Documentation
This button links to a Documentation home page that lists published guides and release
notes. The content titles on the page match the product filter that you select. If no
product is selected, a page listing all available documentation options is displayed.
Every documentation page is organized with left-hand navigation and nested topics, to
ease browsing.
Other features available on every documentation page include the following:
l Print Article: This button launches the browser's print dialog box, from which you can
print the currently displayed HTML page.
l Download Guide: This button downloads a PDF version of the entire publication.
l Rate Article: This button lets you vote on whether the content on the page was helpful
to you.
l Send Feedback: This button lets you leave feedback for the writer of the content.
Contact Us
This button links to the Contact Us page that lists telephone numbers for EMC Global
support centers and field offices. The page also provides a link to a list of in-country
support phone numbers and another link to the EMC Support home page.
Help Topics
This button links to more articles about using the Cloud Portal, troubleshooting
information, using EMC Support, and so on.
Account Details
This button links to information about your customer account, your account
administrator, and the products and services that your account is entitled to.
As part of an effort to improve its product lines, EMC periodically releases revisions of its
software and hardware. Therefore, some functions described in this document might not
be supported by all versions of the software or hardware currently in use. The product
release notes provide the most up-to-date information on product features.
Contact your EMC technical support professional if a product does not function properly
or does not function as described in this document.
Note
This document was accurate at publication time. Go to EMC Online Support at https://
support.emc.com to ensure that you are using the latest version of this document.
Purpose
This document describes the integration of NetWorker with CloudBoost.
Audience
This guide is part of the CloudBoost documentation set, and is intended for use by
system administrators who are responsible for setting up and maintaining backups on a
network. Operators who monitor daily backups will also find this guide useful.
Revision history
The following table presents the revision history of this document.
Related documentation
The following EMC publications provide information about CloudBoost.
l EMC CloudBoost Release Notes
Contains information about new features and changes, fixed problems, known
limitations, environment and system requirements for the latest release.
l EMC CloudBoost 100 Installation Guide
Guide for installing the physical CloudBoost 100 appliance, and initial configuration
at command line interface.
l EMC CloudBoost Disk Array Expansion Shelf Installation Guide
Guide for installing the disk array expansion shelf for use with the physical appliance.
l EMC CloudBoost Hardware Component Replacement Guide
Guide for customers replacing hardware components for the CloudBoost physical
appliance.
You may find these publications helpful when integrating CloudBoost with different
systems.