EMC Integartion Cloudboost With Networker19.2
EMC Integartion Cloudboost With Networker19.2
Version 19.2
Dell 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.” DELL 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 DELL SOFTWARE DESCRIBED
IN THIS PUBLICATION REQUIRES AN APPLICABLE SOFTWARE LICENSE.
Dell Technologies, Dell, EMC, Dell EMC and other trademarks are trademarks of Dell Inc. or its subsidiaries. Other trademarks may be the property
of their respective owners. Published in the USA.
Dell EMC
Hopkinton, Massachusetts 01748-9103
1-508-435-1000 In North America 1-866-464-7381
www.DellEMC.com
PREFACE 7
As part of an effort to improve product lines, periodic revisions of software and hardware are
released. Therefore, all versions of the software or hardware currently in use might not support
some functions that are described in this document. The product release notes provide the most
up-to-date information on product features.
If a product does not function correctly or does not function as described in this document,
contact a technical support professional.
Note: This document was accurate at publication time. To ensure that you are using the latest
version of this document, go to the Support website https://www.dell.com/support.
Purpose
This document describes the integration between the NetWorker software and the CloudBoost
appliance.
Audience
This guide is part of the NetWorker 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.
01 November 15, 2019 First release of this document for CloudBoost 19.2.
Related documentation
The following publications provide information about CloudBoost.
l CloudBoost Release Notes
Contains information about new features and changes, fixed problems, known limitations,
environment and system requirements for the latest release.
You may also find it helpful to refer to these NetWorker publications.
l NetWorker Administration Guide
Describes how to configure and maintain the NetWorker software.
l NetWorker Installation Guide
Provides information about how to install, uninstall, and update the NetWorker software for
clients, storage nodes, and servers on all supported operating systems.
Special notice conventions that are used in this document
The following conventions are used for special notices:
NOTICE Identifies content that warns of potential business or data loss.
Note: Contains information that is incidental, but not essential, to the topic.
Typographical conventions
The following type style conventions are used in this document:
Bold Used for interface elements that a user specifically selects or clicks,
for example, names of buttons, fields, tab names, and menu paths.
Also used for the name of a dialog box, page, pane, screen area with
title, table label, and window.
Italic Used for full titles of publications that are referenced in text.
Monospace Used for:
l System code
l System output, such as an error message or script
l Pathnames, file names, file name extensions, prompts, and
syntax
l Commands and options
You can use the following resources to find more information about this product, obtain support,
and provide feedback.
Where to find product documentation
l https://www.dell.com/support
l https://community.emc.com
Where to get support
The Support website https://www.dell.com/support provides access to product licensing,
documentation, advisories, downloads, and how-to and troubleshooting information. The
information can enable you to resolve a product issue before you contact Support.
To access a product-specific page:
1. Go to https://www.dell.com/support.
2. In the search box, type a product name, and then from the list that appears, select the
product.
Knowledgebase
The Knowledgebase contains applicable solutions that you can search for either by solution
number (for example, KB000xxxxxx) or by keyword.
To search the Knowledgebase:
1. Go to https://www.dell.com/support.
Lotus Yes
Sybase Yes
NetWorker Module for Microsoft Exchange Yes Yes Not applicable Yes
Microsoft
Microsoft Hyper-V
Microsoft SharePoint
Microsoft SQL
NetWorker Module for SAP HANA Yes Yes Yes Not applicable
SAP (NMSAP)
SAP with Oracle Yes
NetWorker Snapshot Not applicable Not applicable Yes Yes, only RHEL Yes
Module (NSM)
vProxy VMware
For clients that cannot back up directly to the cloud, you can send backups through the
CloudBoost appliance or an external NetWorker storage node to the cloud. However, routing
through either the CloudBoost appliance or the external NetWorker storage node limits
performance. Having the data path go directly from the client to the cloud is the most scalable,
efficient, and optimal performance deployment model.
its own deduplication database and cannot deduplicate against backups that are sent to other
devices.
Network dependencies
Cloud backups depend on the network connection that accesses the cloud service. Any disruption
in connectivity or a slowdown in network speed can adversely affect cloud backups or recoveries.
The CloudBoost appliance requires proper DNS name resolution.
Consider the following points before you set up the network for cloud backups:
l If the latency between the source and cloud object store is higher than 50 ms, backup and
restore throughput from the object store might be impacted. NetWorker can sustain 100 ms on
the metadata path. However, packet loss significantly impacts the backup success rate.
l If there is a high-latency link and some packet loss between the NetWorker server, client, and
the CloudBoost appliance, set a high client-retry value for the backup so backups are re-tried.
l An increase of 5 ms latency in the data path (clients to the cloud object store, the CloudBoost
appliance, or the cloud object store), has the following impacts:
n For the initial full backup, throughput is two to two and a half times slower.
n Consecutive backups are about 20 percent slower compared to a full backup.
l A higher-latency link and higher packet losses might result in significantly slower backup
operations.
Note: It is recommended that latency between the NetWorker client and the cloud object store
be limited to less than 50 ms and that packet loss be less than 1 percent.
Supported Regions
The following table lists the regions that are supported by AWS and Azure.
Microsoft Azure Storage l All the regions are supported in Microsoft Azure.
Note:
n ZRS replication is not supported.
n Special Azure regions are not supported.
you consult with the IT security team. To configure a proxy, see Configure CloudBoost to use a
proxy.
The following table outlines the firewall port requirements.
CloudBoost appliance Cloud storage (public 443 HTTPS to access object store
or private) (if supported)
l CloudBoost
appliance for
metadata.
For information about firewall ports for any system that you deploy with CloudBoost, refer to the
documentation for that system.
For information about NetWorker, refer to the NetWorker Security Configuration Guide.
Before you begin the installation and configuration of the CloudBoost appliance, it is important
that you understand all the requirements.
l Solution requirements........................................................................................................... 22
l NetWorker client host requirements......................................................................................24
l CloudBoost sizing and performance considerations...............................................................24
Solution requirements
This section outlines the solution requirements for the CloudBoost appliance in the following
environments.
l VMware ESX
l Amazon Web Services (AWS) EC2
l Microsoft Azure
For more information about metadata store, see CloudBoost sizing and performance
considerations on page 24.
WAN requirements
The following points provide the WAN requirements for the CloudBoost appliance.
l Greater than or equal to 100 Mb/s bandwidth
l Less than or equal to 100 ms RTT latency
Backup/clone via 8 32 GB
CloudBoost appliance
16 64 GB
Backup/Clone via 8 32 GB
CloudBoost appliance
Use the AWS EC2 instance, type m4.xlarge, for small-client direct installations.
Note: For smaller environments, you can choose an instance with unified compute and storage
such as AWS EC2 m3.xlarge, which includes 4 vCPUs, 15 GB memory, and 2x40 GB SSD
storage.
16 64 GB 50 GB 100 GB metadata is
required per 200 TB
of logical capacity
Use the following formula to determine the CloudBoost metadata storage requirements:
where:
l The default chunk size is 256 KB, which is the default.
l Deduplication ratio for the CloudBoost appliance is 2x–8x.
Note: You must use an SSD for metadata storage.
Example 1 Examples
To address 6 PB of logical capacity with a dataset that has 4x data reduction, the
CloudBoost appliance requires 3 TB of metadata storage.
To address 1 PB logical capacity with a dataset that has 4x data reduction, the
CloudBoost appliance requires 500 GB for metadata.
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 in the virtual
machine.
Object store ingest limits present 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.
Note: Before you can finish configuring the virtual appliance in the On-Prem CloudBoost
Management Console, you must set the appliance's IP address and network through the
CLI.
status
admin@mag-fs> status
Host Configuration:
Hostname: hostname
Domain: domain
FQDN: fqdn
Version Information:
Version: version identifier
Internal Version:version identifier
Revision: revision identifier
Network Interfaces:
name mode address netmask
---- ---- ------- -------
eth0 dhcp 10.x.x.123 address
Network Routes:
prefix netmask gateway
------ ------- -------
default 0.0.0.0 10.x.x.1
10.x.x.0 address *
DNS Configuration
DNS Servers: 10.x.x.91
Appliance Configuration
Status: Not Configured
Endpoint: NA
5. If the IP address is dynamically assigned, then skip to step 8. To statically set the IP address
and netmask, type the command net config interface static IP address netmask
netmask address
Note: If you have multiple networks, you must type the following commands for each
network that is listed in the status command output.
For example:
For example:
8. (Mandatory) To set the Fully Qualified Domain Name (FQDN), type the following command:
fqdn servername.yourcompanydomain
For example:
fqdn cloudboost.example.com
Note: You must set the FQDN to access the On-Prem CloudBoost Management
Console.
9. To verify the networking setup and to see the status of the appliance, type the following
command:
status
Results
After you have verified the system's basic networking settings, configure CloudBoost by using the
On-Prem CloudBoost Management Console.
Note: Other commands are available from the command line. To get help, type help or click
the ? icon.
Use the procedures in this section to deploy a CloudBoost appliance with Microsoft Azure
Resource Manager (ARM).
Use the Azure PowerShell to configure Microsoft Azure for the CloudBoost
appliance
Before you begin
The following software and permissions are required:
l Microsoft Azure PowerShell
l Microsoft Azure account
l Azure subscription
Refer to the Microsoft Azure documentation for installation and configuration details.
Procedure
1. Start Microsoft Azure PowerShell.
2. Type the following command:
Add-AzureAccount
$storage_account_name = account_name
$rg_name = resourcegroup_name
$storage_account_key = account_key
where:
l account_name is the name of the Microsoft Azure subscription account.
l resourcegroup_name is name of the resource group.
l account_key is the Microsoft Azure account key.
where:
l <resourcegroup_name> is name of the resource group.
l <template_file> is the name of the Microsoft Azure template file.
Configure Microsoft Azure for the CloudBoost appliance by using the Azure CLI
Before you begin
The following software and permissions are required:
az login
A device code appears with a link to the Microsoft Azure Device Login page.
b. To open the Microsoft Azure Device Login page, click the link.
c. In the Code field, type the device code.
2. In the Azure Resource Manager, perform the following steps:
a. Create or use a storage account with the following properties:
l Deployment Model—Resource Manager
l Account Kind—General Purpose
l Replication—Select any type except ZRS.
b. Set the deployment mode to Resource Mode. Type the following command:
l To retrieve the Azure storage access key, type the following command:
5. Export or set the following environment variables that the Azure CLI will use. The procedure
differs for Linux and Windows operating systems.
export AZURE_STORAGE_ACCOUNT=<storage_account_name>
export AZURE_STORAGE_ACCESS_KEY=<primary_access_key>
Note: On a Linux OS, you can add these environment variables to the .bashrc file
so you do not need to export the variables each time that you want to use them.
l On a Windows system, type the following commands:
set AZURE_STORAGE_ACCOUNT=<storage_account_name>
set AZURE_STORAGE_ACCESS_KEY=<primary_access_key>
export PATH=<Paths>;C:\Go\bin
export GOPATH=<GO_PATH>
Note: On Linux, you can add these environment variables to the .bashrc file, so you
do not have to export the variables each time that you want to use them.
l On a Windows system, type the following commands:
set PATH=<Paths>;C:\Go\bin
set GOPATH=<GO_PATH>
4. Export or set the following environment variables that the Azure CLI template will use.
The procedure differs for Linux and Windows operating systems:
l On a Linux system, type the following commands:
export AZURE_STORAGE_ACCOUNT=<storage_account_name>
export AZURE_STORAGE_ACCESS_KEY=<storage_account_key>
where:
n <storage_account_name> is the name of the storage account where the blob is to be
uploaded.
n <storage_account_key> is the storage account key information.
Note: On Linux, you can add these environment variables to the .bashrc file, so you
do not have to export the variables each time that you want to use them.
l On a Windows system, type the following commands:
set AZURE_STORAGE_ACCOUNT=<storage_account_name>
set AZURE_STORAGE_ACCESS_KEY=<storage_account_key>
where:
n <storage_account_name> is the name of the storage account where the blob is to be
uploaded.
n <storage_account_key> is the storage account key information.
go get github.com/Microsoft/azure-vhd-utils
6. Upload the root VHD file by typing the following command on one line:
where:
l <root.vhd_path> is the file path to the root VHD file.
l <storage_account_name> is the name of the storage account where the blob is to be
uploaded.
l <storage_account_key> is the storage account key information.
l <container_name> is the destination location of the container in the storage account.
l <dest_blob_name> is the name of the blob in which to upload the VHD file.
7. Upload the LVM VHD file by typing the following command on one line:
where:
l <lvm.vhd_path> is the file path to the LVM VHD file.
l <storage_account_name> is the name of the storage account where the blob is to be
uploaded.
l <storage_account_key> is the storage account key information.
l <container_name> is the destination location of the container in the storage account.
l <dest_blob_name> is the name of the blob in which to upload the VHD file.
where:
l <image_to_upload> is the root or lvm VHD file to upload.
l <container_name> is the destination location of the container in the storage account.
l <blob_name> is the name of the blob in which to upload the VHD file.
An output similar to the following appears:
where:
l <deployment_name> is the name of the deployment. Use a unique name.
l <resource_group> is the name of the resource group that deploys the virtual machine.
3. To comply with the virtual machine size and location standards, adjust the JSON file. For
detailed information about Azure virtual machine size, refer to the following Microsoft
documentation:
https://docs.microsoft.com/en-us/azure/virtual-machines/virtual-machines-windows-
sizes
fqdn <FQDN_name>
where <resource_group> is the name of the resource group that was used to deploy the virtual
machine.
status
For example:
admin@mag-fs> status
Host Configuration:
Hostname: hostname
Domain: domain
FQDN: fqdn
Version Information:
Version: version identifier
Internal Version:version identifier
Revision: revision identifier
Network Interfaces:
name mode address netmask
---- ---- ------- -------
eth0 dhcp 10.x.x.123 address
Network Routes:
prefix netmask gateway
------ ------- -------
default 0.0.0.0 10.x.x.1
10.x.x.0 address *
DNS Configuration
DNS Servers: 10.x.x.91
Appliance Configuration
Status: Not Configured
Endpoint: NA
3. Configure the CloudBoost appliance, see Configuring a New CloudBoost Appliance on page
51.
4. To configure NetWorker with the CloudBoost appliance, see Configuring NetWorker with a
CloudBoost appliance on page 57.
Note: Save the private key in a secure and accessible location. After the private key is
created, you will be unable to download the private key again.
fqdn <FQDN_name>
status
For example:
admin@mag-fs> status
Host Configuration:
Hostname: hostname
Domain: domain
FQDN: fqdn
Version Information:
Version: version identifier
Internal Version:version identifier
Revision: revision identifier
Network Interfaces:
name mode address netmask
---- ---- ------- -------
eth0 dhcp 10.x.x.123 address
Network Routes:
prefix netmask gateway
------ ------- -------
default 0.0.0.0 10.x.x.1
10.x.x.0 address *
DNS Configuration
DNS Servers: 10.x.x.91
Appliance Configuration
Status: Not Configured
Endpoint: NA
3. Configure the CloudBoost appliance, see Configuring a New CloudBoost Appliance on page
51.
4. To configure NetWorker with the CloudBoost appliance, see Configuring NetWorker with a
CloudBoost appliance on page 57.
status
admin@mag-fs> status
Host Configuration:
Hostname: hostname
Domain: domain
FQDN: fqdn
Version Information:
Version: version identifier
Internal Version:version identifier
Revision: revision identifier
Network Interfaces:
name mode address netmask
---- ---- ------- -------
eth0 dhcp 10.x.x.123 address
Network Routes:
prefix netmask gateway
------ ------- -------
default 0.0.0.0 10.x.x.1
10.x.x.0 address *
DNS Configuration
DNS Servers: 10.x.x.91
Appliance Configuration
Status: Not Configured
Endpoint: NA
5. If the IP address is dynamically assigned, then skip to step 8. To statically set the IP address
and netmask, type the command net config interface static IP address netmask
netmask address
Note: If you have multiple networks, you must type the following commands for each
network that is listed in the status command output.
Note: If you have multiple networks, you must also add multiple routes to the gateways.
For example:
For example:
8. (Mandatory) To set the Fully Qualified Domain Name (FQDN), type the following command:
fqdn servername.yourcompanydomain
For example:
fqdn cloudboost.example.com
Note: You must set the FQDN to access the On-Prem CloudBoost Management
Console.
9. To verify the networking setup and to see the status of the appliance, type the following
command:
status
Results
After you have verified the system's basic networking settings, configure CloudBoost by using the
On-Prem CloudBoost Management Console.
Note: Other commands are available from the command line. To get help, type help or click
the ? icon.
where:
l <IP> is the IP address of the proxy server.
l <port> is the port number of the proxy server.
l <prefix> is the range of the source IP addresses for which you want to bypass the proxy.
l <mask> specifies the size of the range that is identified by the prefix.
For example, this command sets the proxy to 10.8.196.10:3128 and excludes 10.8.*. *. Note
that (*) is 0–255:
http-proxy 10.8.196.10:3128 exclude 10.8.0.0/16
6. To add exceptions for multiple exclusions, type the following command:
http-proxy <IP>:<Port> exclude <prefix>/<mask>,<prefix>/<mask>,...
where:
l <IP> is the IP address of the proxy server.
l <port> is the port number of the proxy server.
l <prefix> is the range of the source IP addresses for which you want to bypass the proxy.
l <mask> specifies the size of the range that is identified by the prefix.
For example, this command sets the proxy to 10.8.196.10:3128 and excludes 192.8.*. *.* and
100.9.22.24. Note that (*) is 0–255:
After you install a CloudBoost appliance and configure it at the CLI and complete its configuration
in the On-Prem CloudBoost Management Console. You must create a cloud profile for the storage
provider that the appliance will use before you can complete its configuration.
Cloud profiles
Before you configure a CloudBoost appliance in the On-Prem CloudBoost Management Console,
create a cloud profile for the storage that the appliance will use.
The result should be similar to the following output, but with a list of available cloud profiles.
3. To validate the storage credentials against the listed profiles, type the following command:
The "1" represents the cloud profile to validate as listed in the result of Step 2.
The result should indicate that various BSV CLI commands are being validated.
8. Review the selections and click Save to save these settings for the appliance.
CloudBoost is configured.
9. Download the recovery metadata and the private key.
Note:
a. After editing the initial configurations, you must safely store the recovery files. They
must be provided during a Disaster Recovery. Appliances that are backed up cannot
be recovered without the private key and recovery metadata.
b. After you acknowledge, the recovery metadata file and private key will be purged
from the CloudBoost. If you do not acknowledge, the file will be available for
download in the Pending Action.
Note: You can edit only the NTP server field and the backup frequency.
4. Review the changes and click Save to save these settings for the appliance.
CloudBoost is configured.
5. Download the recovery metadata and the private key.
Note:
a. You must safely store the recovery metadata and the private key. They must be
provided during a Disaster Recovery. Appliances that are backed up cannot be
recovered without the private key and recovery metadata.
b. After you acknowledge, the recovery metadata file and private key is purged from
the CloudBoost. If you do not acknowledge, the file will be available for download in
the Pending Action.
This chapter applies to configuring NetWorker with a CloudBoost appliance by using backup to the
cloud. Cloud-based data protection occurs over a TCP/IP network.
The CloudBoost appliance has an embedded storage node which can be used with the NetWorker
server. However, it is recommended that you install the NetWorker storage node on a separate
Linux or Windows server and do not use the embedded NetWorker storage node on the
CloudBoost appliance.
l Configure a CloudBoost device by using an embedded NetWorker storage node.................. 58
l Configure a CloudBoost device on an external storage node..................................................61
l Troubleshoot CloudBoost device configuration issues...........................................................66
l Report information on cloud backup......................................................................................69
b. In the CloudBoost appliance group box, select one of the following options:
l To use a CloudBoost appliance that you have previously configured on the NetWorker
server, select Use an existing CloudBoost appliance.
l To create a CloudBoost appliance, select Create a new CloudBoost appliance and
then type a descriptive name.
c. In the Hostname (FQDN) field, type the Fully Qualified Domain Name (FQDN) of the
CloudBoost appliance.
d. In the Username field, type remotebackup.
e. In the Password field, type the password for the remotebackup account, which you
defined on the CloudBoost appliance by using the remote-mount command.
f. In the Configuration Method group box, select the file system on the CloudBoost
appliance that NetWorker uses as the target data device:
Figure 5 Device Configuration Wizard: CloudBoost Configuration Options
NetWorker validates the CloudBoost username and password that you specified.
NetWorker also updates the NetWorker Device Name and Storage Path fields with the
information.
g. Click Next.
Figure 6 Device Configuration Wizard: Browse and Select the CloudBoost Device Path
11. On the CloudBoost Pool Configuration page, perform the following steps:
Note: For detailed information about NetWorker media pools, refer to the NetWorker
Administration Guide.
Note: The pool that you select cannot contain other device types such as AFTD and
DD Boost devices.
b. In the CloudBoost Appliance group box, select one of the following options:
l To use a CloudBoost appliance that you have previously configured on the NetWorker
server, select Use an existing CloudBoost appliance.
l To create a CloudBoost appliance, select Create a new CloudBoost appliance and
specify a descriptive name.
c. In the Hostname (FQDN) field, specify the Fully Qualified Domain Name (FQDN) of the
CloudBoost appliance.
d. In the Username field, type remotebackup.
e. In the Password field, type the password for the remotebackup account, which you
defined on the CloudBoost appliance by using the remote-mount command.
f. In the Configuration Method group box, select Browse & Select.
The Browse and Select the CloudBoost Device Path page appears.
11. On the Browse and Select the CloudBoost Device Path page, select the file system on the
CloudBoost appliance that NetWorker uses as the target data device:
a. Select New Folder.
b. Create a folder in the /mnt/magfs/base directory. Use a unique name.
For example: /mnt/magfs/base/CBO1
Configure the CloudBoost appliance to cloud profile, the CloudBoost appliance creates a
share on /mnt/magfs/base. The NetWorker software requires that each CloudBoost
device has a unique, customer named, folder.
Note: You cannot create folders outside of the /mnt/magfs/base directory.
e. Click Next.
Figure 9 Device Configuration Wizard: Browse and Select the CloudBoost Device Path
12. On the Configure the CloudBoost Pool page, perform the following steps:
Note: For detailed information about NetWorker media pools, refer to the NetWorker
Administration Guide.
Note: The pool that you select cannot contain other device types such as AFTD and
DD Boost devices.
Results
After the CloudBoost device has been configured with the NetWorker external storage node, the
following information displays:
l The Name field points to the NetWorker external storage node.
l The Device access information field points to the CloudBoost appliance.
l The media type is specified as CloudBoost.
Figure 12 Device information
Operating Procedure
system
Windows a. Open Notepad, and create the nsrcbconfig file with the
configuration options.
b. Save the file in <installation Directory>\Emc Networker
\nsr\debug\ directory without an extension.
You can add one of more configuration options from the following table.
v (lower case only) Provides the capability of different log levels that ranges
from 0-5. Greater the number, more the debug logs printed
in /nsr/logs/cloudboost/*
maxLogFiles Controls the number of log files that are retained in /nsr/
logs/cloudboost/ folder. The default value is 10. The
maximum value is 50.
max_log_size Limits the size of log files. When the value reaches the
maximum file size, the files is zipped and the log continues
in a new file. The default size of log file is 10 MB.
4. In the Configuration tab, clear or select the Disable RPS Clone attribute.
5. Add the CloudBoost appliance using the NetWorker character-based interface (nsradmin)
and then, label and mount the appliance.
l Monitoring CloudBoost..........................................................................................................74
l Connect to the CloudBoost CLI............................................................................................. 74
l Upgrade a CloudBoost appliance........................................................................................... 75
l CloudBoost integration with EMC Secure Remote Services ................................................. 76
l Register CloudBoost with EMC Secure Remote Services...................................................... 77
l Configuring average chunk size............................................................................................. 78
l Specifications for the chunk size setting............................................................................... 78
Monitoring CloudBoost
CloudBoost is integrated with EMC Secure Remote Services (ESRS), which can be enabled to
monitor the health of the appliances. If CloudBoost appliances are not registered with ESRS, you
must monitor health, collect and review logs, and when necessary, contact Support.
Option Description
Option Description
CAUTION If the site cache is enabled in CloudBoost 18.1, then contact the DellEMC support to
assist you in disabling the site cache and upgrade to CloudBoost 19.2.
l The CloudBoost Release Notes contains information about new features and changes, fixed
problems, known limitations, environment, and system requirements for the latest release.
l The NetWorker E-LAB Navigator provides a complete list of supported products and versions.
Note:
l CloudBoost 18.2 and later does not support site-cache.
l The upgrade process usually takes 60 minutes or less.
Procedure
1. Connect to CloudBoost using an SSH client.
For more information about connecting to CLI, see Connect to the CloudBoost CLI.
2. Login to CloudBoost as an administrator and run the following command: upgrade
appliance <URL upgrade path> .
Note: You must host the image of CloudBoost that you want to upgrade to in your LAN
environment. Since downloading the image from the support site requires
authentication, CloudBoost will be unable to download the image from the link.
Results
After the upgrade is complete, type status to view CloudBoost version.
After you finish
By default, the recovery files are saved as recovery.key and recovery.meta. To prevent accidental
overwrite of existing recovery files, Dell EMC recommends that you save the recovery files with a
different file name.
Note: You must download the recovery information immediately. If you fail to download the
recovery file, then you will be unable to perform a disaster recovery on the upgraded
CloudBoost appliance.
Technical Support is notified of issues and can open an SSH session with the appliance to obtain
additional logs and reports.
Auditing
You can audit remote support activity, including the date and time of remote sessions, the ticket
number, and the technician who provided the support.
Registering
You can allow or deny this remote activity for any reason. When a technical support agent starts a
connection through EMC Secure Remote Services, an email that requests access is sent to you.
You can choose to grant or deny the request.
If you choose not to register CloudBoost appliances with EMC Secure Remote Services, you must
manually monitor the appliances. If any issues arise, contact Support.
where:
l esrs_gateway is either the IP address or the FQDN for the EMC Secure Remote Services
gateway virtual machine.
l username and password are the credentials that you used to set up the EMC Secure
Remote Services gateway.
l sid is the EMC Secure Remote Services serial number that EMC Secure Remote
Services Support provided in an email.
l gateway_sn is the serial number for the EMC Secure Remote Services gateway.
Note: If you see this message, Approval Request Pending - Contact EMC
Customer Support, contact Customer Support and ask for the device registration in
EMC Secure Remote Services to be manually approved. After Support approves the
request, you can run the command in step 4 again. After a device is successfully
registered, you can also use the status command to verify the connection. At the
bottom of the window, you will see a list of the EMC Secure Remote Services Server
details.
Results
The CloudBoost appliance is registered with EMC Secure Remote Services, and continuous
support monitoring begins.
256 K 1024 K