SG Vol1 16may2019

HPE StoreOnce Gen4 Service
and Support
Student guide
(1 of 2)
V2.0
Confidential – For Training Purposes Only
Use of this material to deliver training without prior written permission from HPE is prohibited.
 Copyright 2019 Hewlett Packard Enterprise Development LP
The information contained herein is subject to change without notice. The only warranties for
HPE products and services are set forth in the express warranty statements accompanying
such products and services. Nothing herein should be construed as constituting an additional
warranty. Hewlett Packard Enterprise shall not be liable for technical or editorial errors or
omissions contained herein.
This is an HPE copyrighted work that may not be reproduced without the written permission of
Hewlett Packard Enterprise. You may not use these materials to deliver training to any person
outside of your organization without the written permission of HPE.
Printed in the US
HPE StoreOnce Single Node Service and Support

Student guide
Confidential – For Training Purposes Only

HPE StoreOnce Gen4 vILT
Confidential – For Training Purposes Only 1






What depends on you?

The costs of data loss increases with the length of downtime.


Understand the impact of RTO and RPO

A customer’s recovery requirements determine the best way to back up their data, and each case requires a unique
strategy. Factors to consider when designing a BURA solution include:
– Recovery Point Objective (RPO)—How much data is allowed to go unprotected and how far back in time data
must be recovered. RPO can be measured in days, hours, or minutes.
– Recovery Time Objective (RTO)—How long the customer is willing to wait for the data to be recovered and the
maximum allowable downtime.
– Retention—How long the data must be kept available. Retention time can range from seconds to decades,
depending on company policies and government regulations.
A company’s business continuity plan should indicate the RTO and RPO for business processes such as running
payroll, generating orders, and so on. The metrics specified for the business processes must then be mapped to the
underlying IT systems and infrastructure that support those processes.
After the RTO and RPO metrics have been mapped to IT infrastructure, you can determine the most suitable strategy
for each system. However, the business ultimately sets the IT budget, and therefore the RTO and RPO metrics must
fit with the available budget. Most business unit heads want zero data loss and zero time loss, but the cost associated
with that level of protection might make the desired high-availability solutions impractical.


Customer pain points

The bullets above shows customer pain points.
Any additional?


HPE StoreOnce federated deduplication

HPE StoreOnce Deduplication offers an integrated, federated solution. Large Remote Office Branch Offices (ROBO),
medium, and small ROBOs can replicate their backed up data to a central data center for disaster recovery. This
solution integrates software deduplication, for example, HPE Data Protector, as well as hardware-based deduplication
(HPE StoreOnce Backup Systems). For restore purposes, a copy of the data can be stored in the branch office and
replicated to a main data center for disaster recovery. This solution offers a flexible way to back up and recover data
and offers a secure solution to centralize backup data (copy-to-tape). For hardware-based replication using the HPE
StoreOnce D2D Backup System, a replication license is only required on the target appliance. Use Catalyst for a
large-scale federated deduplication.


StoreOnce Backup System

The HPE StoreOnce Backup System is a disk-based storage appliance for backing up host network servers or PCs to
target devices on the appliance. These devices are configured as either Network-Attached Storage (NAS), Virtual
Tape Library (VTL), or Catalyst targets for backup applications.
The total number of backup targets provided by an HPE StoreOnce Backup System is split between VTL, NAS, or
Catalyst devices. These devices can be all VTL, all NAS, or any combination of NAS, VTL, and Catalyst devices. All
HPE StoreOnce devices that are configured for NAS, VTL, or Catalyst automatically use HPE deduplication, ensuring
efficient and cost-effective use of disk space.


NAS share versus VTL share

There are pros and cons for using D2D as NAS or VTL. This slide lists NAS considerations. The following slide lists
VTL considerations.

Deduplication: What is it?

Data Duplication is done across all devices (VTL, NAS Shares and Catalyst Stores) configured in the appliance. Data
deduplication is a method of reducing storage needs by eliminating redundant data so that over time only one unique
instance of the data is actually retained on disk.
Deduplication works by examining the data stream as it arrives at the storage appliance, checking for blocks of data
that are identical and eliminating redundant copies.
If duplicate data is found, a pointer is established to the original set of data as opposed to actually storing the duplicate
blocks — removing or “de-duplicating” the redundant blocks from the volume. The key concept is that the data
deduplication is being done at the block level to remove far more redundant data than deduplication done at the file
level (called single instancing), where only duplicate files are removed.
Data deduplication is especially powerful when it is applied to backup, since most backup data sets have a great deal
of redundancy. The amount of redundancy will depend on the type of data being backed up, the backup methodology,
and the length of time the data is retained.
HPE’s unique StoreOnce deduplication has been specifically designed to provide flexible, low cost deduplication
functionality for smaller and mid-size data centers, allowing typically 20x more backup data to be retained on disk for
longer periods of time. The actual data deduplication ratio you can expect will depend on a number of factors
including; the type of data the backup methodology used the length of time you retain your data However Managing
HPE StoreOnce Backup Solutions data, used, data. However, assuming standard business data mix and extended on-
disk retention (periods of more than 12 weeks) you could expect to see typically a 20x reduction.
HPE StoreOnce also enables data compression by looking at the incoming stream – the HPE StoreOnce will simply
dedup data that is a copy, but if the data is unique (i.e. a first time store), the HPE StoreOnce uses Lempel-Ziv (LZ)
data compression algorithm to compress the data after the deduplication process, and before storing it to disk. Typical
compression ratios are between 1.5:1 and 2:1, but may be higher depending on the data type.
More information directs the delegates to: 00366562 – HPE StoreOnce Solutions (WBT).

The deduplication subsystem (1 of 2)

The deduplication subsystem is started by the D2D Manager.
The deduplication subsystem is responsible for the following:
– Deduplicating and recreating data—This is an inline process.
– Housekeeping operations—This is a post-processing operation.
– One deduplication store exists per NAS share/VTL.
The details of the StoreOnce deduplication subsystem are beyond the scope of this course, but the next slide
describes the fundamental blocks within this subsystem.
Deduplication enables you to provide features such as:
– Low-bandwidth replication to occur across a WAN
– Low-bandwidth Catalyst backups and copies

The deduplication subsystem (2 of 2)

Data deduplication
Data deduplication is the ability of a software application or an appliance to compare blocks of data being written to
disk with data blocks that currently reside on that disk. Deduplication technology analyzes backup data and stores
each unique block of data only once, using pointers for additional instances of the same data. When duplicate data is
found, a pointer is established to the original set of data, as opposed to actually storing the duplicate blocks, removing
or “deduplicating” the redundant blocks from the volume.
A very important point is that the deduplication is being done at the block level and not at the file level. In fact, beware
of products that only dedupe at the file level (sometimes called “single instancing”). For example, assume you are
backing up a very large database that changes throughout the day. With a typical backup application, you must back
up, and more importantly, you must store the entire database with each backup. An incremental backup does not help
you in this case.
With block-level deduplication, you can back up the same database to the device on two successive nights and,
because of the ability to identify redundant blocks, only the blocks that have changed will be stored. Any redundant
data will be stored as pointers instead.
Often, deduplication is used in conjunction with other forms of data reduction, such as conventional data compression,
to further reduce the data volume stored.
Key benefits of data deduplication
– Keep more data on disk:
– Allows longer retention of backup data on disk before archiving off, or purchasing more backup storage.
– Improves service levels and business performance—data is available on disk for longer for fast recovery of lost
or corrupt files from multiple backup points
– More efficient storage utilization—Effectively reduces cost per gigabyte for backup data
– Enables more efficient replications network:
– Cuts the costs of data transmission through lower bandwidth lines
– Makes remote backup and disaster recovery more affordable for a wider range of businesses
– Reduces the overhead required at remote sites required for backup, media management, and off-site vaulting

Deduplication technology types

You can use different methods to deduplicate data. The technology variants can be broadly classified under the headings: When,
Where, and How it is done.
Every method/technology has pluses and minuses. There is no one correct solution that fits everyone’s needs. As a result, you
must choose a solution with a deduplication technology that best suits your needs.
When
Deduplication processing actually occurs with the vendors either deduplicating data during the backup process (“inline”), or
completing the data-reduction process after a backup job has been written to disk (“post-process”).
Vendors with post-process deduplication claim to have a performance advantage because they do not impede the backup process.
While inline vendors concede they typically cannot back up data at the same speeds as post-process vendors, they claim that
inline processing is advantageous because deduplicated data can be replicated offsite as soon as a backup job has been
completed, because no additional processing is required.
Where
While some products confine their deduplication processing to the target device that is storing the backup data, others choose to
deduplicate data upstream in the hosts sending the data. Sending hosts are the backup client or the backup server. Deduplicating
data at the client level allows its product to minimize the amount of data that must be sent through the network to backup servers.
This benefit is important, given that such products are typically deployed in remote office environments (which use WAN links to
transmit data back to a company’s data center).
The main drawbacks to host-based deduplication are that it requires the installation of either agents or an appliance at remote
sites, and that these host-based products are typically seen as replacements for traditional tape backup software.
In contrast, target-based deduplication products are designed to complement existing backup wares, and the vendors often claim
that their products can be added quickly into an existing backup implementation. Target-based products do not minimize the
amount of network traffic between clients and their backup servers, but they can boost storage efficiency and allow you to quickly
retrieve data at rates not possible in tape environments.

Chunking example
You can think of this image backup example as a part of a sequence of sentences. This example shows only 1
sentence.
Every file is composed of one or more words. In the example of fixed chunking, every file is a fixed size of 10
characters.



Capacity advantage in StoreOnce

Percentages show reduction in storage achieved by each technology.
To show the benefits of smaller, variable chunking, look at two examples of a 165 MB database (StoreOnce source
code and documentation).
In each example, a single additional file was added. In the first example, fixed 4K chunking in the upper left could only
produce an 18% efficiency in space savings, compared to the 51% efficiency produced with the variable 4K chunking
in the upper right. Even with variable chunking, size matters. Compare the 51% efficiency produced by StoreOnce to
the two competitor examples in the lower left and lower right, which only produced 47% and 41% efficiencies,
respectively.

Housekeeping
If data is deleted from the StoreOnce system (e.g. a virtual cartridge is overwritten or erased), any unique chunks will
be marked for removal, any non-unique chunks are de-referenced and their reference count decremented. The
process of removing chunks of data is not an inline operation because it would significantly impact performance. The
process of cleaning up after deletions, termed “housekeeping,” runs on the appliance as a background operation.
Housekeeping runs on a per-cartridge and per-NAS file basis. By default it will run as soon as the cartridge is
unloaded and returned to its storage slot, or as soon a NAS file completes writing and is closed by the appliance
unless it is prevented by a configured housekeeping blackout configuration. The housekeeping blackout windows are
configured across the whole appliance.
Housekeeping places a significant load on the StoreOnce device. The housekeeping process checks for available
resources before running and, if other operations are in progress, the housekeeping dynamically reduces its activity to
prevent impacting the performance of other operations. However, the hold-off is not binary (i.e. on or off) so, even if
backup jobs are in process, some low level of housekeeping can still take place which may have a slight impact on
backup performance unless a blackout window is configured.
Before we could set housekeeping windows, housekeeping ran in the background as soon as the device was closed. If
backups and replication were running, this could lead to unpredictable performance. Now we can control precisely
when Housekeeping runs. It should be scheduled to occur during “quiet times” when no other major activities are
running.

Housekeeping times
Best practices for housekeeping blackout windows:
– Only use housekeeping blackout if backup or replication is not completing in the required window, after a rotation
scheme starts to overwrite backups.
– Blackout windows for housekeeping (and replication) make overall performance more predictable, but might not
deliver the overall quickest completion time.
– Housekeeping is an important process and must be allowed enough time to run.
– Apply a blackout window to cover the backup and replication/tape offload times, to have the greatest impact.
– Some trial-and-error might be required to get the windows in the right place because placing a window will change
backup and replication performance (and therefore the end time).


What is replication?
HPE StoreOnce Replication allows cartridges in slots on a library device that have been configured on one HPE StoreOnce
Backup System (the Source Appliance) to be replicated to corresponding mapped slots on a library device on another HPE
StoreOnce Backup System (the Target Appliance) at another location. Data is always mapped at slot level.
NOTE: If the replication Source Appliance fails and goes offline while it was performing a NAS replication job, the replication
target share appliance may be left in an inconsistent state.
This state may result in failure to recover from some files in the share or perform a list of files in the share because relationsh
between files and folders have been lost. This will automatically be repaired by the target appliance as soon as it detects the
of the source appliance, however it may take up to 10 minutes to complete this repair during which time the share will not be
available for access.
NOTE: Replication-Target libraries are not visible to the host, unless you configure devices to make them visible. See the HP
StoreOnce Backup System user guide for more information.
Once you have set up a replication configuration between Source and Target HPE StoreOnce Backup Systems, it is initiated
automatically whenever a cartridge is returned from a drive to a slot that has been configured for replication or when a file is
created or modified or deleted in a NAS share.
Replication Target libraries are not visible to the host, unless you configure devices to make them visible. See the HPE
StoreOnce Backup System User Guide for more information.
There is no replication for Catalyst Data Stores since objects in Catalyst data stores are copied between Catalyst data stores
an ISV backup application that supports Catalyst so the copy can be scheduled and is known by the backup application.
Catalyst Copy is the equivalent of Virtual library and NAS share replication. The same principles apply in that only the new da
created at the source site needs to be copied (replicated) to the target site. The fundamental difference is that the copy jobs a
created by the backup application and can, therefore, be tracked and monitored within the backup application catalog as well
from the StoreOnce Management GUI.
.

Bidirectional replication
In this example there are two offices, each with an HPE StoreOnce Backup System. The HPE StoreOnce Backup
System in Office A is being used by the host server for backup and restore, and all Replication-Source libraries and
shares are being replicated to matching Replication-Target libraries and shares on the HPE StoreOnce Backup
System in Office B. However, there is also a single host backing up to six cartridges on another library on the HPE
StoreOnce Backup System in Office B. Two of those cartridges are configured to replicate to a Replication-Target
library on the HPE StoreOnce Backup System in Office A. A replication license is required for both HPE StoreOnce
Backup systems.
These are the four main usage models for replication using StoreOnce VTL and NAS devices.
– Active/Passive: A StoreOnce system at an alternate site is dedicated solely as a target for replication from a
StoreOnce system at a primary location.
– Active/Active: Both StoreOnce systems are backing up local data as well as receiving replicated data from each
other.
– Many-to-One: A target StoreOnce system at a data center is receiving replicated data from many other StoreOnce
systems at other locations.
– N-Way: A collection of StoreOnce systems on several sites are acting as replication targets for other sites.


HPE StoreOnce VSA target audience

So, who can take advantage of StoreOnce VSA?
There are three major use cases:
1. Service providers looking to offer Backup as a Service.
2. Enterprise with remote offices.
3. SMB customers looking to avoid dedicated infrastructure.
What do they need in their environment?
1. VMware ESXi, Microsoft Hyper-V, or Ubuntu KVM
2. A supported backup application. Data Protector, Symantec NetBackup and Backup, and Veeam today. More will
be forthcoming.
3. StoreOnce Catalyst.
4. Either StoreOnce VSA or a StoreOnce Converged Storage Appliance.





Use case 1: Backup/disaster recovery as a service

– Service Provider installs the StoreOnce VSA at each customer site.
– The SP can offer varying capacity points from 1 TB to 50 TB, which could be increased on demand.
– Using one of the supported backup applications, the backups are scheduled by the SP per customer requirements
and automatically backed up to and deduplicated by the StoreOnce VSA at the customer site.
– This provides a local copy of the data for the customer for fast restore in the event of loss of data.
– Data can then be automatically replicated from the customer VSA to a dedicated VSA at the SP site.
– Backups can be monitored and tracked either through the backup application, or for more detailed information on
deduplication ratios and so on, using StoreOnce Reporting.
– If an SP has multiple customers or VSAs, each VSA must be managed independently. Reports can be produced
and shared with the customer as to what has been backed up, capacity used, and so on.

Use case 2: Branch office data protection

– VSAs can be deployed in bulk to the branch offices by IT personnel at the data center. There is no need to visit
each branch office.
– A media server must be configured as a virtual machine and contain the backup applications.
– The backup application is then configured for the appropriate backup and replication schedule and backs up the
data to the StoreOnce VSA where it is deduplicated in the traditional manner.
– The data is then replicated from the VSA to a StoreOnce Appliance at the data center or disaster recovery site.
– A local copy of the backed up and deduplicated data is kept at the branch office for fast restore in the event of a
data loss, with a copy also kept at the data center in the event of a site loss.
deduplication ratios and so on, using StoreOnce Enterprise Manager.

Use case 3: SMB data protection

– If the SMB has a VMware environment, they can install the backup application as a Virtual Machine (VM).
– Deploy a StoreOnce VSA and then back up the data using the media server to back up the data to the VSA.
– Set and forget scheduling means that there is no user input required after this time.
deduplication ratios and so on, using StoreOnce Reporting Central.
– While this provides a local backup, this does not provide any disaster recovery scenarios.


HPE StoreOnce Backup with StoreOnce Catalyst

– What is HPE StoreOnce Catalyst?
– How does HPE StoreOnce Catalyst work?
– Provides a new type of backup target optimized for deduplication appliances.
– Provides information to the backup application about status of backup jobs and subsequent copies on
appliances.
– Allows the backup app to control copies and expiration policies
– Allows some of dedupe processing (chunking and hashing) to be carried out on the “source-side” (media
server) while the rest of the processing (match and store) is done by the appliance. This enables:
– Low-bandwidth backup across the media server to the appliance (over LAN or WAN)
– Faster appliance performance

HPE Catalyst source side deduplication

An example of low bandwidth where part of the deduplication occurs on the client.
The HPE StoreOnce Catalyst client side deduplication improves performance by sharing some of the deduplication
process between the backup server and the StoreOnce system. The “client” software is either part of the “plug-in”
software like NetBackup or embedded into the Data Protector media agent.
The data stream is provided by the ISV application and then it is divided into chunks which are between approx. 2 kB
and 10 kB. The hash function computes a 160-bit SHA-1 hash for each chunk. The hash codes are sent in a list
(sometimes referred to as a manifest) to the StoreOnce Catalyst device). The list of hash codes equals approx. 10MB
of user data. The hash codes are “matched” against the sparse indexing system of the store and if matched the
container index is updated for those chunks. Any new chunks go on to the surrogate matcher and in this case are
actually stored as new chunks and the container indexes updated accordingly.

HPE Catalyst target side deduplication (DP)

An example of high bandwidth where all of the deduplication occurs on the StoreOnce. This is no different than a VTL
or NAS share implementation from a deduplication perspective.
When to use server side deduplication vs. target side deduplication?
The decision on whether to use source or server deduplication depends on the WAN/LAN link speed available, the
CPU and memory size of the server running the disk agent and how much load can that server stand. If for example
you have a large database server which is heavily loaded and you are backing up a snapshot it may not be a good
idea to user source or server side deduplication for some jobs. Target side deduplication places fewer loads on the
server.
Small remote office backups over a WAN may really benefit from server side deduplication as their data change rate is
low and they may well be backed up out of hours when server load is not so critical.

Principles of HPE StoreOnce Catalyst

– Starting the at the remote office, the media server has StoreOnce Catalyst installed with Symantec OST or with
HPE Data Protector
– The backup to the media server still requires the full bandwidth, but StoreOnce Catalyst can perform server-side
deduplication on the media server, and then send the deduplicated backup over the WAN to the 6x00 (using lower
bandwidth links).
– When the backup reaches the data center, the 6x00 does not need to rehydrate the data, but with Catalyst in
residence, it can move the deduplicated data set directly on to the DR site. We call this “cascaded data movement,”
but some people call it “multi-hop.”
– While this is happening, the backup application (in the remote office) can track and control the movement of this
data set.
– Restoring data from the DR site to the data center is a simple. It is the same deduplicated data set that you started
with. However, at the data center, the 6x00 must rehydrate the data before sending it back to the remote office for
media server restore.


Catalyst (API) integration in HPE Data Protector

– Explicit gateways are server-side gateways. At least one explicit gateway should always be defined. Explicit gateways are
assigned, as required, to any server running the Data Protector media agent. The explicit gateway configuration can specify the
maximum number of streams and where the deduplication process is to be performed—on the media server or on the HPE
StoreOnce Backup System. If deduplication in the media agent is selected (by selecting server-side deduplication in the device
properties), this results in a low-bandwidth transfer of data deduplication. The explicit gateway supports HPE Data Protector
Object Copy (Catalyst store replication).
– The explicit gateway could be considered as “client side” deduplication where every client (with a no-cost media agent loaded)
can have access to a Catalyst store using a gateway of the same name and settings to access the Catalyst store. HPE Data
Protector starts the media server code on the correct client to perform this task. The explicit gateway can be configured with
server-side deduplication turned off. In that case, all deduplication will take place in the StoreOnce appliance. This would be
called “target-side” deduplication.
– The implicit gateway is a source-side gateway and is optional. It is configured once only but can be used by any of the clients in
the cell that have a media agent installed. The implicit gateway does not have an assigned media agent but will start media
agents on any server equipped with media agent software. In effect, it is like a “virtual” gateway for every media-agent-
equipped server belonging to the cell where “source-side” deduplication is specified for backup (see configuration examples
later in this section).
– The implicit gateway has the same configuration parameters on every media-agent-equipped backup server. It is designed so
that only files or data resident on the media-agent-equipped backup server can be backed up using this gateway. Files or data
resident on an application server with only the disk agent or application agent installed cannot be backed up or restored using
an implicit gateway.
– The implicit gateway always invokes deduplication in the media agent (which is referred to as source-side deduplication on the
Data Protector Add Device screen). HPE Data Protector Object Copy (Catalyst store replication) is not available using the
implicit gateway. A setting in the implicit gateway can be used to limit the number of parallel streams. This setting (as you
would expect) applies to every server with a media agent using the gateway. So, if set at 2, each media-agent-equipped client
can have a maximum of 2 streams. The user can configure both source and server-side gateways. You could have a backup
server that normally used the source-side gateway for deduplication in the server but has a server-side gateway with
deduplication not selected for “target-side” deduplication (useful for reducing server load at the expense of backup
performance). The current overall limit is 32 gateway instances per session. Data Protector also queries the StoreOnce device
for the maximum number of Catalyst sessions available. (These would be inbound data jobs).
(Continued on the next slide)

(Continued from previous slide)

IMPORTANT!
There is no difference in the deduplication method for either source or server-side deduplication. The different
gateways are essentially for different deployment methods.
Deduplication types with the explicit gateway
The explicit gateway supports both low-bandwidth (server-side) and high-bandwidth (target-side) deduplication.
– Server-side deduplication—Deduplication of data is performed within the dedicated backup server. Server-side
deduplication can be used for data held locally on the backup server and from servers that have a disk agent
installed. In this case, data is transferred over the network to the backup server and then processed by the media
agent and sent on to the Catalyst store. Server-side deduplication must use the “explicit” gateway for the backup
destination, and that gateway requires server-side deduplication selected in the advanced options.
– Target-side deduplication—Data is held on a client with only a disk agent installed. This system can be remote
from the backup server. Server-side deduplication is not selected. All data is transferred at high bandwidth across
the LAN or WAN to a backup server hosting a gateway to the StoreOnce Catalyst appliance. This might be
necessary when Data Protector has only an application/disk agent support for a particular data type (such as
OpenVMS backup).
Key points:
– At least one explicit gateway must be configured. You cannot configure just an implicit gateway.
– For files or data held on an application server with only a DP disk agent installed, backups must be directed to an
explicit gateway.
– The implicit gateway is used for source-side deduplication on any server in the cell running a media agent. A server
running just a disk or application agent cannot select the implicit gateway.
– The parameters (maximum streams and so on) are the same for every server using the implicit gateway. This is
useful for limiting server loading.
– The implicit gateway does not support Object Copy (Catalyst store replication).
– Target-side deduplication is useful when the extra load of deduplication is not wanted on the backup server.
– Only 64-bit servers can be configured for a gateway.
– The deduplication process is exactly the same for server-side and source-side deduplication.
– The StoreOnce deduplication and Catalyst client binaries are built in to the media agent code. There is no
requirement for a plug-in software module, as required for Symantec NetBackup and Backup Exec integration.
– In HPE Data Protector terminology, a Catalyst store is referred to as a Backup to Disk device type.

Object copy, Catalyst replication, federated deduplication

Catalyst Copy
Catalyst Copy is the equivalent of virtual library and NAS share replication. The same principles apply; that is, only the
new data created at the source site must be copied (replicated) to the target site. The fundamental difference is that
the copy jobs are created by the backup application and can, therefore, be tracked and monitored within the backup
application catalog as well as from the StoreOnce Management GUI.
Should it be necessary to restore from a Catalyst copy, the backup application can restore from a duplicate copy
without the need to reimport data to the catalog database.
Catalyst Copy should not be considered like VTL and NAS replication. There are effectively no hard constraints other
than capacity on how many Catalyst stores can be copied (replicated) into a Catalyst store at a central site.
Furthermore, because Catalyst copies are controlled by the backup application, multi-hop replication is possible using
Catalyst devices. However, Catalyst replication blackout windows can be set on the StoreOnce appliance to dictate
when the copy job actually happens and bandwidth throttling can also be enforced to limit the amount of WAN link
consumed by StoreOnce Catalyst copy; in this respect, it is similar to NAS and VTL replication.
Catalyst Copy has the following features:
– The copy job is configurable from within the backup application software.
– Several source Catalyst stores can be copied into a single target Catalyst store.
– Multi-hop copy is configurable using the backup software—Source to Target 1 then onto Target 2.
– One-to-many copy is also configurable but happens serially one after the other.
– With the Catalyst agents running on remote office media servers, HPE StoreOnce Catalyst technology can back up
directly from remote sites to a central site, using what is known as low-bandwidth backup; essentially, this uses
HPE StoreOnce replication technology.



The ability to connect StoreOnce Catalyst to internal and external cloud service providers
Supported with major Cloud Service Providers (MS Azure, Amazon S3) as well as internal Scality ring
Only available as Catalyst copy target NOT DIRECT BACKUP TARGET
Ideal for off site data storage such as data archiving
Cost effective disaster recovery option
Catalyst copy available with ISV’s, Catalyst Plugin and HPE RMC
Cloud Bank Storage is a StoreOnce feature to allow a customer to store the deduplicated data in public clou
storage (AWS/Azure) or private cloud storage (Scality) as opposed to within the StoreOnce System.
The functionality addresses three potential use cases:
-Customer wants long term offsite retention of backups
-Customer wants offsite disaster recovery copies of backups
-Customer wants to reduce the cost of running a StoreOnce VSA in the cloud
-Objects written to cloud storage contain all the information necessary to reconstruct all the backup data within the Cloud
Bank Catalyst Store.
-Locally the Cloud Bank Catalyst Store will also maintain a Catalyst database containing details of each Catalyst Item for th
purposes of providing quick listing responses to data protection software and dedupe will maintain a Sparse Index and
copies of all the Container Indexes for the purpose of providing quick deduplication matching responses
HK766S H.00 M11-52

Use Case 1 – Long Term Backup Retention

Wants to retain data for a long time as cheaply as possible.
Plan to seldom read the data, if every.
Use Case 2 – Offsite Disaster Recovery Protection

Want to regularly send backups offsite for the purposes of DR protection.
No secondary site to replicate to.
Only plan to read the data for DR recovery.
Use Case 3 – StoreOnce VSA in the Cloud backed by Object Storage

Using StoreOnce VSA as a backup/replication target within Cloud Compute.
Would like to reduce running costs by hosting data on cheaper object storage.
WWAS 2018 – Confidential M11-53

Writing directly to the Cloud Bank Store

Whilst SLP’s and Policies can be configured to write backups directly to a Catalyst Cloud Bank Store.
Direct writes are not supported and so attempts to backup directly to the Catalyst Cloud Bank Store will
be cancelled by the StoreOnce System with a cancellation reason of “Operation Not Supported”.
Disaster Recovery from local Catalyst Store or Cloud Bank Store

Although the primary method of transferring data out of a Catalyst Cloud Bank Store will be using
Catalyst Copy, it will also be possible to directly recover data from the Cloud Bank Store. To do so, a
user would simply start a recovery from within the data protection software. The recovery will retrieve all
the necessary objects from the Cloud Service Provider, as needed, in order to satisfy the recovery read
requests



HK766S H.00 M11-57





Bonding modes
See http://linux.cloudibee.com/2008/02/network-bonding-part-ii-modes-of-bonding/








Change: Update only for multi

Static routing on the management subnet

The data subnet has been configured on bonded ports ens1f2 and ens2f2 to use the gateway 1.1.1.3, which gives
access across the WAN. This gateway has also been configured as the default gateway.
The management subnet has been configured on bonded ports eno0 and eno2.
The company wishes to use a management workstation on a 192.168.1.7 network and has configured a gateway to
access this network (192.168.1.1).
The company also requires access to a second management network where the AD server is located on a 2.2.2.x
network.
To achieve this it configures static routing for the management subnet, either directly to the AD server at 2.2.2.5 or to
the 2.2.2.x network, using the gateway 2.2.2.1.

SAN technologies
– In order to share the resources, storage area networks (SAN) are quite common (such as a backup server and
media agent sharing the same D2D appliance).
– Depending on the model, the StoreOnce D2D supports two types of SAN: FC-SAN and iSCSI-SANs.
– In order to consolidate all three types of networks (LAN, iSCSI, and FC), a new technology has been established.
– The so-called “Converged Enhanced Ethernet (CEE)” also uses the Ethernet network technology of the LAN/iSCSI
networking for the FC protocol.
– Interfaces that can handle all three types protocol (LAN, iSCSI, and FC) are the converged network adapters
(CNAs) used in HPE BladeSystem, for example.
– A SAN is built up of different components: HBA–Fabric–Target
– HBAs used in a SAN:
– iSCSI: Network interface card (NIC)
– FC: Host bus adapter (HBA)
– In a SAN, iSCSI devices are connected using the ISCSI Qualified Name (IQN). A host must have an iSCSI initiator
installed, in order to connect to an iSCSI SAN when using normal Ethernet NICS.
– In an FC SAN, devices are recognized using the World-Wide-Name (WWN). This information is stored, for
example, on an FC HBA, or emulated by software (such as StoreOnce) for target devices.
– Fabric components in a SAN:
– Local SANs use switches for connection between server and storage devices:
– FC: FC switch ( 8 Gb or 16 Gb)
– iSCSI: iSCSI switch (1 Gb or 10 Gb)
– These switches need some characteristics in order to work with a HPE StoreOnce D2D Backup System. An FC
SAN switch must support NPIV to virtualize N-Ports to use more than one device on a physical port.
– An iSCSI switch needs flow control and Jumbo Frame support to work in an iSCSI SAN correctly.

FC SAN settings (1 of 2)
– As compared to iSCSI-SANs, FC-SANs have a fixed bandwidth. The main focus is the traffic separation.
– It is important because Windows based servers attempt to write volume labels to all available LUNs. This can
render the LUNs unusable by other operating systems, and can result in data loss.


iSCSI SAN settings

As compared to FC-SAN, iSCSI-SANs might be inundated with retransmits, and they do not have a guaranteed
bandwidth.
When designing a D2D backup solution-based iSCSI SAN infrastructure, it is important that iSCSI SANs support the
following features:
– Jumbo frames:
– Not standardized size. Jumbo means just more than the default MTU size of 1500 bytes.
– For correct function, all participating components must have the exactly same size. If it is not clear, it is better to
leave it at the standard size.
– Flow control:
– IP communication has its seeds in WAN traffic where package losses are recoverable but require additional
time for retransmitting, which is reason for performance degradation.

Backup device technologies

Using StoreOnceD2D represents backup-to-disk, or disk-to-disk technology.
StoreOnce D2D is a disk-based device that can be accessed from the backup server in two different manners, VTL or
NAS.
– Virtual tape (library) VTL:
– Even though the D2D appliance is a disk device, it emulates a tape drive, autoloader, or tape library.
– VTLs can be implemented simply in existing backup environments. The access is identical to a physical tape
drive in a block orientated manner. The supported protocols are iSCSI and FC.
– Because no network file system is used, the performance is better than NAS.
– NAS:
– This abbreviation stands for network attached storage, which means the data is represented in a file system in a
network, in contrast to block-oriented.
– The most common NAS protocols are CIFS (Windows systems) and NFS (UNIX, LINUX systems).
– Even though NAS is designed for file sharing, many backup software products support NAS as a backup target.
– For long-term storage or additional disaster recovery, another copy of the backup set is put on a physical tape.
This technology is named disk-to-disk-to-tape and must be performed by the backup application (HPE Data
Protector: Object Copy).
















StoreOnce Gen4 is built completely on ProLiant DL380 Gen10

Utilize Proliant LFF chassis for entry level configs (no JBODs required for 1st 12 data drives)
Utilize Proliant SFF chassis for mid-range and high end configs (LFF data drives only in external JBODs)
All StoreOnce Gen4 models boot from Smart Array controller using SFF Enterprise SAS drives
All StoreOnce Gen4 models come with enough memory to make them “Cloud Bank” ready,
no memory expansion needed on the server node.
New 8TB drive support – only in D6020 JBODs
New 32G FC HBA (no 8G FC HBA supported on the StoreOnce Gen4)
New 25G SFP HBA – also supports 10GbE SFP.
The D6020 enclosures support 2 drive drawers with a total of 70 disks
HK766S H.00 92
Credits – Technical Marketing

The HPE StoreOnce appliance is based on a Linux operating system with a heavily tuned and
customised configuration. Customer have limited access to the operating system but use a web-based
management interface and a command line interface. The backup (media) server communicate via fibre
channel for virtual tape or IP network connection for iSCSI virtual tape, NAS or StoreOnce Catalyst. The
disk storage is arranged in RAID configuration. Backup servers, sometimes know as media servers,
running data protection software read/write data via virtual tape drives, NAS shares, or catalyst stores.
Credits -Tech Marketing



512 emulation(512e) 4K physical sectors on the drive media with 512 byte logical configuration
512n – 512 byte sector size







Skylake SP (Skylake Scalable Performance) is the code name for Intel's series of
server multiprocessors based on the Skylake microarchitecture as part of the Purley platform serving as a
successor to both Broadwell EX and Broadwell EP. These chips support up to 8-way multiprocessing, up to 28
cores, and incorporate a new AVX-512 x86 extension. Skylake SP-based chips are manufactured on an
enhanced 14nm+ process and utilize the Lewisburg chipset. Skylake SP-based models are branded as
the processor families: Xeon Bronze, Xeon Silver, Xeon Gold, and Xeon Platinum.

























P1224 – One internal and one external SAS port connectivity

P1228 – Two External SAS port connectivity














D6020 Storage JBOD

Differences from the D6000:
– There are now three I/O module LEDs, instead of 1.
– I/O module port LEDs x2 (see Guided Troubleshooting [GTS] for more information).














































Confidential – For training purposes only 189



Catalyst and Replication deployment SKU’s stay the same as with Gen3.
HA124A1#5V0 and HA124A1#5V1 (add’l hours) will also be available for Gen4
StoreOnce Catalyst Service Data sheet: https://www.hpe.com/h20195/v2/GetPDF.aspx/4AA4-

9988ENN.pdf

What will arrive from the factory?

With the current release of HPE StoreOnce products, customers will can factory configure everything they want to
order, which includes the following:
– Configured storage including capacity upgrade kits
– Installation of optional hardware purchased
– Applied licenses

Installation checklist
DHCP network addressing is enabled by default. For a Quick Install, connect the HPE StoreOnce appliance to LAN
port 1. If your network uses static IP addressing, you will need IP addresses, domain names, and gateway details for
all ports that are to be connected. If you intend to use network port bonding, you will need to know which bonding
mode is required for your network.
NOTE: An installation, planning, and preparation guide and checklist is available at hpe.com to support the customer
and installer through this process.






























Flex is triggered by installation of a flex config license or a system start/reboot. You can re-trigger the
flex config validation be re-installing a flex license – the installation will fail if the license already exists
in the store, but this will still trigger a re-evaluation of the hardware and licenses.
Cards are validated, licensed and activated by type and location.
For example if the customer had installed cards in the following configuration:
Slot 1 NIC 10G

Slot 2 NIC 10G
Slot 4 HBA 16G
Slot 5 NIC 10G
Flex would determine that the two NIC cards in slots 1 & 2 were correctly installed and would activate
them if suitable licenses were installed. However, slot 4 contains an HBA card so the NIC card in slot 5
is incorrect as there is a gap in the installed load order (the HBA card in slot 4). This card would not be
licensed.
Flex would then attempt to validate the installed HBA cards. The HBA card in slot 4 is invalid as there is
a non HBA card in slot 5.










































































14 May 2019




14 May 2019



























329
330
331
332
333
334
335
336
337
338
339
340
341











SG Vol1 16may2019

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SG Vol1 16may2019

Uploaded by

Copyright:

Available Formats

HPE StoreOnce Gen4 Service

HPE StoreOnce Single Node Service and Support

Confidential – For Training Purposes Only

Confidential – For Training Purposes Only 1

Confidential – For Training Purposes Only 2

Confidential – For Training Purposes Only 3

Confidential – For Training Purposes Only 4

Confidential – For Training Purposes Only 5

Confidential – For Training Purposes Only 6

What depends on you?

Confidential – For Training Purposes Only 7

Confidential – For Training Purposes Only 8

Understand the impact of RTO and RPO

Confidential – For Training Purposes Only 9

Confidential – For Training Purposes Only 10

Customer pain points

Confidential – For Training Purposes Only 11

Confidential – For Training Purposes Only 12

HPE StoreOnce federated deduplication

Confidential – For Training Purposes Only 13

Confidential – For Training Purposes Only 14

StoreOnce Backup System

Confidential – For Training Purposes Only 15

Confidential – For Training Purposes Only 16

NAS share versus VTL share

Confidential – For Training Purposes Only 17

Deduplication: What is it?

Confidential – For Training Purposes Only 18

The deduplication subsystem (1 of 2)

Confidential – For Training Purposes Only 19

The deduplication subsystem (2 of 2)

Confidential – For Training Purposes Only 20

Confidential – For Training Purposes Only 21

Deduplication technology types

Confidential – For Training Purposes Only 22

Confidential – For Training Purposes Only 23

Confidential – For Training Purposes Only 24

Confidential – For Training Purposes Only 25

Capacity advantage in StoreOnce

Confidential – For Training Purposes Only 26

Confidential – For Training Purposes Only 27

Confidential – For Training Purposes Only 28

Confidential – For Training Purposes Only 29

Confidential – For Training Purposes Only 30

Confidential – For Training Purposes Only 31

Confidential – For Training Purposes Only 32

HPE StoreOnce VSA target audience

Confidential – For Training Purposes Only 33

Confidential – For Training Purposes Only 34

Confidential – For Training Purposes Only 35

Confidential – For Training Purposes Only 36

Confidential – For Training Purposes Only 37

Use case 1: Backup/disaster recovery as a service

Confidential – For Training Purposes Only 38

Use case 2: Branch office data protection

Confidential – For Training Purposes Only 39

Use case 3: SMB data protection

Confidential – For Training Purposes Only 40

Confidential – For Training Purposes Only 41

HPE StoreOnce Backup with StoreOnce Catalyst

Confidential – For Training Purposes Only 42

HPE Catalyst source side deduplication

Confidential – For Training Purposes Only 43