BACKUP AS A SERVICE FOR SERVICE PROVIDERS USING VEEAM ON HPE INFRASTRUCTURE

Technical white paper

Technical white paper

CONTENTS Executive summary .............................................................................................................................................................................................................................................................................................................. 3

BaaS implementation challenges for service providers ................................................................................................................................................................................................................ 3 Target audience................................................................................................................................................................................................................................................................................................................ 3

Introduction ................................................................................................................................................................................................................................................................................................................................. 3 BaaS offering operation ............................................................................................................................................................................................................................................................................................. 3

Solution overview ................................................................................................................................................................................................................................................................................................................... 4 Functional architecture .............................................................................................................................................................................................................................................................................................. 6 Resource management .............................................................................................................................................................................................................................................................................................. 7 Solution components ................................................................................................................................................................................................................................................................................................... 8 Snapshot orchestration .............................................................................................................................................................................................................................................................................................. 9 Best practices and configuration guidance for the solution .................................................................................................................................................................................................. 11

Alternate configuration .................................................................................................................................................................................................................................................................................................. 11 Alternate solution components ....................................................................................................................................................................................................................................................................... 12 Functional architecture ........................................................................................................................................................................................................................................................................................... 13 Capacity and sizing considerations .............................................................................................................................................................................................................................................................. 14 Solution comparison .................................................................................................................................................................................................................................................................................................. 14

Summary ..................................................................................................................................................................................................................................................................................................................................... 15 Appendix A: Bill of materials ..................................................................................................................................................................................................................................................................................... 16 Appendix B: REST APIs for Veeam functionality ................................................................................................................................................................................................................................... 17

Technical white paper Page 3

EXECUTIVE SUMMARY This white paper describes how hosted service providers can build a reliable data protection infrastructure based on the latest technology and augment their services with a Backup as a Service (BaaS) offering. Solutions are provided for the challenges faced in multitenant environments to achieve efficiency without compromising functionality.

BaaS implementation challenges for service providers Hosted service providers require an environment that hosts multiple tenants with necessary isolation while sharing resources among tenants to achieve efficiency due to aggregation. Some of the challenges are:

• Achieving isolation of tenants at a logical layer (virtual machines [VMs], networks, storage space, administration, and so on)

• Sharing the physical infrastructure among tenants (hypervisors, network switches, and storage arrays) for efficiency

• Scaling out backup infrastructure when new tenants are added without major rework of the data center

• Storing backup data securely so that one tenant cannot access and restore data from another tenant

• Storing backup data securely to thwart data thefts as well as malware and ransomware attacks

• Transmitting backup data securely over networks to handle data-sniffing threats

The solutions described in this paper integrate multiple components and features to address the service provider’s unique requirements.:

• Based on a data protection application that is optimized for virtual environments and for operating with hardware-deduped storage

• Based on the best deduplication and compression technologies for reducing storage utilization and costs

• Effective use of all the new and advanced backup technologies, such as virtual synthetic full for avoiding any new full backup after the first one, source-side deduplication, and ransomware protection

• Designed to operate in a scale-out model that is flexible and easy to manage to address the dynamically changing requirements

Furthermore, the solutions are highly efficient, reduce costs on multiple layers, and enable the service provider to operate within an optimal cost structure, adding more margin to its markup.

Target audience This paper is intended for service providers seeking an efficient and cost-effective data protection solution to protect their users’ hosted virtual machines (VMs). The presented solutions are highly scalable and benefit from the latest integration features between Veeam software and Hewlett Packard Enterprise (HPE) infrastructure, such as HPE 3PAR or HPE Nimble Storage hardware snapshot integration and orchestration, HPE StoreOnce Catalyst source-side deduplication, and virtual synthetic full backup. This paper is based on a VMware® virtual infrastructure that caters to multiple tenants by the service provider.

INTRODUCTION There are two main approaches to BaaS. They differ on the level of autonomy given to users to manage the backup and restore operations:

• Managed service: Managed service is the most common approach. The service provider uses an infrastructure shared among tenants and manages all data protection services. The service provider is responsible for setting the backup policies according to the agreed service level agreement (SLA) and for performing all restore operations after receiving a request from the user.

• Self service: With self service, the service provider uses a partially shared infrastructure and gives users access to the backup application management console to let them define their backup policies and to perform restore operations.

This approach is less common because it requires the user to acquire the necessary skill to manage the backup application. It also adds complexity and restrictions at multiple levels that make the solution less flexible, more complex to manage, and less cost-efficient.

This paper focuses on BaaS with the managed service approach.

BaaS offering operation The architecture is built within the hosted service provider’s data center and works with a VMware infrastructure to back up and restore a tenant’s VMs and applications. The service provider is responsible for creating backup jobs, schedules, and recovery of failed or crashed VMs. The tenant notifies the service provider of backup SLAs for all of the hosted VMs and applications, and the service provider creates the backup jobs accordingly.

Technical white paper Page 4

When a VM fails and needs to be recovered, the tenant requests that the service provider recover the VM either on the same VMware ESX® server or on a different ESX server. The service provider initiates a recovery and notifies the tenant after the recovery is complete. The tenant performs all the necessary validation work on the recovered VM and commissions it for operation. As part of optional additional services, the service provider can make a granular restore and instant VM recovery from the backup storage as well as from the primary storage hardware snapshots.

If the service provider has a self-service portal for tenants for backup and recovery of VMs, then this architecture can be integrated into their environment using the APIs provided by Veeam Backup software. Refer to Appendix B: REST APIs for Veeam functionality for the location of Veeam REST API reference documentation. This customization goes beyond the scope of the presented solutions.

SOLUTION OVERVIEW HPE and Veeam have worked together to implement highly desirable optimizations in backup and recovery operations and this architecture encapsulates the following optimizations, as shown in Figure 1.

• Offload backup processing from production servers using HPE 3PAR storage or HPE Nimble Storage snapshots

Veeam Backup & Replication software integrates with HPE 3PAR or HPE Nimble Storage arrays to create hardware-assisted snapshots on the array and use these snapshots to take VM backups. This Veeam/HPE integrated feature allows Veeam to keep the VM snap active for a very short time, thereby reducing the workload on the production infrastructure that occurs when the VM snap is deleted. In addition to the standard backup process, Veeam can interact with HPE 3PAR and HPE Nimble Storage for making snapshot-only backup jobs. This feature allows the creation of very frequent restore points without the workload of copying the data to secondary storage.

FIGURE 1. Advantages of HPE storage snapshots for backups

• Veeam integration with HPE StoreOnce using Catalyst

Veeam implements source-side deduplication with HPE StoreOnce Catalyst, resulting in a significant reduction in backup time and volume of backup data copied over the network to backup repositories. The network bandwidth reduction between the Veeam proxy/gateway and HPE StoreOnce system is usually in the range of 25:1 for a full backup and 8:1 for an incremental backup. When the Veeam server and the target HPE StoreOnce system are connected over a WAN, Veeam can activate the optional Catalyst compression in addition to the deduplication and increase the bandwidth reduction to about 50:1 for a full backup and 16:1 for an incremental backup. These values are the average measured in many production environments. The difference between the higher and the lower values is rather wide; therefore, HPE recommends against using the average value for sizing a specific environment, but rather to evaluate it case by case.

With HPE StoreOnce Catalyst, a simple 1 GbE can usually transport more data than 10 GbE in a traditional environment. HPE StoreOnce Catalyst source-side deduplication requires fewer network resources and adds more flexibility on the architectural design. To reduce the gateway CPU overhead, HPE StoreOnce Catalyst normally performs the deduplication, leaving the compression task at the target HPE StoreOnce system. If even higher bandwidth reduction is required, such as for WAN connectivity, Veeam can activate the HPE StoreOnce Catalyst compression in addition to deduplication. For restore or read activities, HPE StoreOnce Catalyst does not make any bandwidth reduction and the maximum throughput can be limited by the physical link bandwidth.

Technical white paper Page 5

• Veeam and HPE StoreOnce integration and virtual synthetic full backup

Veeam and HPE StoreOnce engineering have co-developed a new feature to synthetize a full backup from the previous full and incremental backups. The main difference from the other Veeam backup techniques is that it does not require heavy post-process workload on the backup infrastructure, leading to fewer required resources and faster backup time. The process is very efficient and can scale up to support large production environments.

A Veeam incremental backup is usually 10 times less resource-intensive than a full backup. An incremental backup reads less data from production storage, preserving most of the IOPS for applications. For these reasons, Veeam has developed the following techniques to avoid making any other full backups after the first one:

– Incremental-for-ever with rolling full

– Reverse incremental

– Traditional synthetic full

All these techniques enable you to run only incremental, change block tracking (CBT)-based Veeam backups that are lighter for the production infrastructure, but they all require heavy post-process activities on the backup infrastructure. Consequently, these techniques require you to install more resources for the backup infrastructure and demand more time to complete the backup jobs.

The virtual synthetic full backup, instead, does not require any compromise. It is light for the production infrastructure because it is based on incremental backup, and it is light for the backup infrastructure because the workload for converting the incremental backup to a full is offloaded to the HPE StoreOnce system. Additionally, HPE StoreOnce is very efficient for this task because it synthetizes the new full backup by reorganizing its internal metadata, rather than making heavy read/write data movement.

The virtual synthetic full backup process takes the following steps:

a. Veeam executes an incremental backup. A periodic full backup is no longer required, reducing the workload on production storage and servers.

b. Veeam sends the instructions to the HPE StoreOnce system for merging the previous full backup with all of the subsequent incremental backups to finally generate the new synthetic full backup.

c. HPE StoreOnce executes this task at a high speed because it does not need to move the actual data, but only the pointers to the stored deduplicated data segments.

• Complete protection against viruses and ransomware

Backups are the last line of defense against any data corruption threat. Ransomware is a new malware class that has recently grown on the attack frequency and damage relevance. For a good data protection strategy against ransomware, make sure that the Veeam backup files (*.vbk, *.vib, and so on) are protected and are not accessible by any malware. It is important to note that when Veeam backup files are saved to server volumes or to NAS shares, they are directly accessible by the Microsoft Windows® operating system where Veeam is running. Thus, they are visible to any malware that might have infected the server. In this situation, the backup administrator might discover the production VMs as well as the backup are corrupted and no restore points are available.

HPE StoreOnce Catalyst-based Veeam backup repositories are not visible to the Windows operating system where Veeam is running. Malware that might have infected the server cannot get access to the HPE StoreOnce Catalyst store and corrupt the saved files. Figure 2 shows the design to protect against viruses and malware.

FIGURE 2. Traditional compared with Catalyst-based Veeam back up repositories for protection against viruses and malware

Technical white paper Page 6

Functional architecture Figure 3 illustrates the functional architecture of the solution. Each tenant is isolated into a separate VMware resource pool and is connected to a dedicated VLAN. The resource pool allows the service provider to assign an upper limit on VMware resources—CPU cores/RAM/disk space—on a per-tenant basis. New tenants can be added to the existing backup infrastructure by creating a new dedicated resource pool and VLAN for the tenant.

FIGURE 3. Solution components: functional view

The backup infrastructure consists of the following components:

• Primary storage (HPE 3PAR or HPE Nimble Storage) hosting data stores and connected to ESX hypervisors using Fibre Channel or iSCSI.

• HPE StoreOnce system (such as HPE StoreOnce 5100) connected with the Veeam Gateway using HPE StoreOnce Catalyst protocol either via IP or Fibre Channel.

• Veeam physical servers running both Veeam's proxy and gateway services:

– The proxy service uses Veeam Direct Storage Access to directly read data from HPE 3PAR/Nimble Storage snapshots via a Fibre Channel or iSCSI network.

– The gateway service writes data to the HPE StoreOnce system using Catalyst protocol with source-side deduplication enabled.

• Veeam Backup & Recovery server (VM) connected to these components via a management network that connects all the components and is responsible for transporting all control commands to orchestrate backup operations.

Technical white paper Page 7

NOTE Veeam's proxy service does not access the production LUNs, but only their snapshots. This makes the solution more resilient to errors as long as the VMware vSphere® production volumes are never accessed.

The HPE StoreOnce appliance is configured with multiple Catalyst stores. Each tenant is the exclusive owner of one or multiple Catalyst stores. When a new tenant is added or a newer backup workload is introduced, scaling the backup infrastructure is simple:

• When more backup streams and bandwidth are required, a new Veeam Data Mover physical server can be introduced and added to the list of proxies/gateways on the Veeam backup server.

• When more backup capacity is required, additional capacity can be provisioned on the same HPE StoreOnce system or a new appliance can be introduced.

• If necessary, it is possible to migrate the content of a Veeam backup repository from the current Catalyst store to a new one, eventually on a new HPE StoreOnce system.

Resource management The backup administrator can control the resources used by each tenant working on Veeam and the HPE StoreOnce GUI:

• Bandwidth utilization and stream count: Veeam provides load control per backup repository. As shown in Figure 4, it is possible to limit the number of concurrent tasks to the Catalyst store as well as the maximum bandwidth.

FIGURE 4. Veeam backup job configuration screenshot

• Capacity utilization per HPE StoreOnce Catalyst store: HPE StoreOnce provides both logical and physical quota enforcement per Catalyst store, as shown in Figure 5. When the tenant's used capacity reaches the threshold, an error is generated, and the specific Catalyst store does not accept any more data.

Technical white paper Page 8

FIGURE 5. HPE StoreOnce Catalyst store configuration screenshot

Solution components The following components were used for the solution, as shown in Figure 6:

• VMware infrastructure: VMware cluster-hosting VMs for tenants. Usually consists of multiple hypervisors clustered together.

• VMware vCenter® server: Central management server for VMware infrastructure. It can be a VM or a physical server.

• HPE 3PAR and HPE Nimble Storage arrays: Primary storage array used to store data stores for VMware infrastructure. Veeam can coordinate the hardware snapshot creation inside a backup job. The use of array-based snapshots greatly reduces the overhead of the backup activity on the production infrastructure and services.

• HPE StoreOnce system: Purpose-built backup and archival appliance from HPE. It offers the highest deduplication ratio for Veeam backup data. Veeam and HPE StoreOnce have a rich integrated feature set, such as source-side deduplication, virtual synthetic full, instant VM recovery, and ransomware protection. The interoperability has been fully certified by both companies and has been validated with thousands of customers.

• HPE StoreOnce Catalyst: A feature-rich communication protocol between Veeam and HPE StoreOnce. It enables source-side deduplication to speed up backup operations and to significantly reduce network utilization. It also enables virtual synthetic full backup, which is a feature developed with Veeam that offloads the workload required to create a full backup from Veeam and the production infrastructure.

• Veeam backup server: Veeam Backup & Recovery management server. It controls the backup operations and presents the management interface. It can be a physical server or, more commonly, a virtual server.

• Veeam proxy server: The Veeam service is responsible for interfacing with VMware data stores and for copying data to and from data stores for backup and recovery purposes. Proxy servers support direct storage access for directly reading data from HPE 3PAR and HPE Nimble Storage volumes and hardware snapshots via Fibre Channel or iSCSI. This feature greatly reduces the workload on the production hypervisor because the data path is a storage proxy instead of a storage hypervisor proxy.

• Veeam gateway server: The Veeam service is responsible for writing and reading backup data to and from Veeam backup repositories based on HPE StoreOnce Catalyst stores. For each Veeam backup job, best practice is to keep Veeam proxy and gateway services on the same server to avoid an extra hop in the LAN.

Technical white paper Page 9

FIGURE 6. Solution components: physical view

Snapshot orchestration The integration between Veeam and HPE 3PAR and HPE Nimble Storage provides additional benefits. Starting with release 9.5-Update-3, Veeam not only manages hardware snapshots inside backup jobs, but it can also orchestrate, replicate, and manage snapshots as independent restore points. Snapshot-only backup jobs complement traditional backup jobs to HPE StoreOnce repositories and offer multiple unique advantages:

• Snapshot-only Veeam backup jobs are fast, use few resources, and can be executed multiple times per day.

• Restore operations are faster than using primary storage as a backup target. Instant VM recovery and granular restore operations are highly accelerated.

• Snapshots can be inexpensive. On state-of-the-art storage arrays such as HPE 3PAR and HPE Nimble Storage, it is not a matter of how many snapshots are kept, but rather how old those snapshots are. Usually 36 hours of snapshots can cost as much as 2-5% of extra capacity, which is not a huge cost relative to the benefits you gain.

Service providers can use snapshot orchestration to build new advanced offering tiers to add to their catalog.

How snapshot orchestration works 1. Veeam schedules creation of HPE Nimble or HPE 3PAR snapshots and manages their retention. These snapshots are useful as intra-day

restore points for an improved recovery point objective (RPO). Obviously, snapshots do not protect against hardware failures and it is necessary to use them along with regular backups to an HPE StoreOnce system.

2. Optional steps:

– (HPE Nimble) Veeam triggers HPE Nimble Storage snapshot replication to a remote array.

– (HPE 3PAR) Veeam create snapshots on peer-persistent remote HPE 3PAR.

3. Veeam backs up to the HPE StoreOnce system reading data from the local or remote storage array snapshots. This further reduces the workload on the production site.

4. Veeam can copy selected backups from HPE StoreOnce to tape for cost-effective long-retention purposes.

5. Finally, Veeam tracks all backups and snapshots in its catalog and shows all the restore points in the usual GUI page.

Figures 7 and 8 show Veeam snapshot orchestration features for HPE Nimble Storage and HPE 3PAR arrays, respectively.

Technical white paper Page 10

FIGURE 7. Veeam snapshot orchestration features for HPE Nimble Storage

FIGURE 8. Veeam snapshot orchestration features for HPE 3PAR

Technical white paper Page 11

Best practices and configuration guidance for the solution The solution design uses the following guidelines in consideration of service provider challenges:

• Tenant isolation in VMware is achieved using two features:

– VMware resource pools to enforce accessibility and resource quotas (CPU/memory/disk) on a per-tenant basis.

– VLAN-based network partitioning for separating tenant data traffic from each other.

• Per tenant resource and quota management:

– The maximum number of concurrent backup streams and the maximum bandwidth can be specified in the Veeam backup repository configuration. (Figure 4)

– The maximum logical (pre dedupe) and physical capacity used by a tenant can be specified in the HPE StoreOnce Catalyst store configuration. (Figure 5)

• Backup data can be encrypted at the target for secure storage.

• Data traffic on the network can be encrypted to handle sniffing threats. Encryption can have considerable performance overhead and can be disabled if adequate traffic isolation is implemented.

• All the tenants are logically isolated using resource pools and VLANs, but they share the entire ESX cluster for better load balancing across the cluster. If strict regional/local compliance rules apply, then a dedicated ESX cluster for each tenant should be considered.

ALTERNATE CONFIGURATION A scaled-down configuration of the solution described previously is possible. The functional diagram in Figure 9 shows the alternate configuration. The main two differences of this configuration, in comparison with the one described previously, are:

• The Veeam proxy/gateway servers are deployed as VMs instead of physical servers.

• The use of HPE StoreOnce Virtual Storage Appliance (VSA) instead of physical appliances.

Technical white paper Page 12

FIGURE 9. Alternate solution components: functional view

Alternate solution components The alternate solution includes two additional components:

• HPE StoreOnce VSA (optional): HPE StoreOnce VSA dedup system hosted on top of standard hypervisors such as vSphere, Microsoft® Hyper-V, or Linux KVM. HPE StoreOnce VSA offers all the features of a physical appliance but can run on storage and compute resources preferred by the service provider.

NOTE HPE StoreOnce VSA is free up to 1 TB of storage capacity, equivalent to 8–20 TB after deduplication. All advanced HPE StoreOnce features are enabled by default on the free VSA version. It is primarily used for pre-production and development environments and for prototyping the final service provider’s solution.

• HPE Apollo servers (optional): Storage density-optimized servers from HPE suitable for running VMware, Hyper-V, or KVM and hosting one or more HPE StoreOnce VSA systems.

Technical white paper Page 13

Functional architecture Veeam Data Mover functionality is implemented on VMs running Veeam proxy and Veeam gateway services to interface with data stores and backup targets respectively. The main differences of this configuration in comparison with the one described previously are:

• The previous configuration uses one or more physical servers connected via Fibre Channel to the primary storage.

• The alternate configuration uses one or more virtual servers connected via iSCSI to the primary storage.

The idea behind this configuration is to deploy the Veeam proxy/gateway VMs along with the production VMs and to evenly distribute the backup workload across the same production infrastructure. Most backup operations usually occur during low workload periods, such as during the night, when there are plenty of unused CPU cycles available for backup operations.

The choice of using iSCSI is a key component of this configuration because it allows integration with the storage-level snapshots inside the backup job. The use of storage-level snapshots is recommended for large environments because it helps to provide better SLAs to tenants with less infrastructure resources. With storage-level snapshots, VMware hypervisors are relieved of the resource usage due to long-lasting VM snapshots and their consolidation (delete) that occurs at the end of the backup operations. Unlike the Fibre Channel protocol, iSCSI is supported for operation within a VM and does not require a physical server. Both HPE 3PAR and HPE Nimble Storage support iSCSI connectivity.

The backup target device is an HPE StoreOnce VSA deployed on top of HPE Apollo 4200 servers. Any of the supported hypervisors, such as VMware, Hyper-V, or KVM, can be used to host one or multiple virtual appliances.

The HPE StoreOnce VSA is configured with multiple Catalyst stores. Each Catalyst store is assigned to a specific tenant, as shown in Figure 10.

When a new tenant is added or a newer backup workload is introduced, backup bandwidth and streams can be scaled by introducing a new Veeam Data Mover VM.

NOTE Veeam Data Mover VMs can reside on the VMware infrastructure used by tenants because they do not contain any backup data. Remember to direct the Veeam catalog backup to the HPE StoreOnce system and not to the local Veeam server disk.

When more backup capacity is required, the single VSA can be expanded up to 50 TB, or a new VSA can be deployed on the same HPE Apollo server. A new HPE Apollo node with HPE StoreOnce VSA can be added as well.

NOTE HPE does not recommend hosting an HPE StoreOnce VSA on the same VMware infrastructure used for serving tenant workloads because both primary and backup data end up being stored on the same physical array. A hardware failure could corrupt both primary and backup data.

Technical white paper Page 14

FIGURE 10. Alternate solution components physical view

Capacity and sizing considerations The Data Mover VM (Veeam proxy and gateway) must have at least 16 GB of memory and one CPU core per concurrent backup process. It also requires additional CPU resources for executing HPE Catalyst source-side deduplication: 1 GHz core and 70 MB RAM for 50 MB/s backup throughput using Catalyst in source-side deduplication mode.

In addition, keep the following considerations in mind:

• HPE StoreOnce 5100: 36 TB to 216 TB of usable capacity

• HPE ProLiant DL360 Gen10 server: Data Mover physical server

• HPE Apollo 4200 server with 24 + 4 LFF SATA drives for up to 280 TB of raw capacity

Solution comparison The following table compares the HPE StoreOnce physical appliance with the HPE StoreOnce VSA.

TABLE 1. Solution comparison

HPE StoreOnce physical appliance HPE StoreOnce VSA

Select this solution when the easier sizing and management of a physical backup appliance are required.

Select this solution when the service provider wants to use existing storage and compute resources.

An HPE StoreOnce physical appliance supports many more Catalyst Stores per system, allowing multiple tenants on the same unit.

Select this solution when you need a large number of small tenants. Although HPE StoreOnce VSA supports fewer Catalyst stores than larger physical units, it is possible to deploy multiple VSAs on the same physical host. This increases the number of supported Catalyst stores and tenants.

Capacity, throughput, and number of concurrent backup streams is generally higher on physical appliances, allowing a higher number of concurrent jobs and easier management.

Capacity, throughput, and number of concurrent backup streams is generally smaller on HPE StoreOnce VSA, but multiple VSAs can run on the same physical server.

Technical white paper Page 15

SUMMARY The data protection infrastructure described in this document helps service providers build an effective data protection solution for their hosted services, based on VMware VMs, and to offer it to their customers.

The solution not only fulfills the main service provider’s technical requirements, such as advanced features, scalability, and easy management, but also delivers an excellent cost/performance ratio.

Using the provided guidelines, service providers can build their own data protection offering and include it in their service catalog. The final product is price-competitive for their users, while also highly profitable for the service provider.

Technical white paper Page 16

APPENDIX A: BILL OF MATERIALS Table 2 lists the major components used in testing this solution. This is not an exhaustive requirements list. For example, power and cabling details are not listed because these items are often different for each organization.

TABLE 2. HPE StoreOnce 5500 physical appliance

Qty Part number Description

1 BB917D HPE StoreOnce 5500 60TB System

2 BB926A HPE StoreOnce 10GbE Network Card

2 BB926A 0D1 Factory integrated

1 BB929A HPE StoreOnce 16Gb Fibre Channel Card

1 BB929A 0D1 Factory integrated

1 BB906A HPE StoreOnce 4900/5500 Catalyst LTU

1 BB906A 0D1 Factory integrated

2 BB949A HPE StoreOnce 10GbE Netwrk Exp LTU

2 BB949A 0D1 Factory integrated

1 BB952A HPE StoreOnce 16Gb Fibre Channel Card LTU

1 BB952A 0D1 Factory integrated

1 H1K92A3 HPE 3Y Proactive Care 24x7 Service

1 H1K92A3 SSY HPE StoreOnce 4900/5500 Catalyst Supp

1 H1K92A3 XZW HPE StoreOnce 5500 60TB Base Supp

1 HA113A1 HPE Installation Service

1 HA113A1 5KK HPE StoreOnce Basic Installation SVC

2 HF383A1 HPE Training Credits for Storage SVC

1 H1SR4AS HPE TS Support Credits SVC

1 H0JD4A1 HPE 1Y TS Support Credits 10 Per Yr SVC

8 H0JD4A1 WFM HPE TS Support Credits 10 Per Yr SVC

1 H8E02A1 HPE StoreOnce Integration Level 1 SVC

1 HA124A1 HP Technical Installation Startup SVC

1 HA124A1 5T7 HPE StoreOnce Sing N Catalyst Startup SVC

1 HA124A1 55Q HPE StoreOnce System startup SVC

1 HA124A1 5V0 HPE StoreOnce Addl 1 day Startup SVC

TABLE 3. HPE StoreOnce VSA license

Qty Part number Description

1 P9L05AAE HPE StoreOnce VSA 50TB E-LTU

1 H1K92A3 HPE 3Y Proactive Care 24x7 Service

1 H1K92A3 XYN HPE StoreOnce VSA 50TB LTU Supp

TABLE 4. Veeam licenses (for example, depending on Veeam Cloud & Service Provider [VCSP])

Qty Part number Description

1 Q1K19A Veeam BU Repl Ent+ VMware 1yr Maint LTU

1 H5UR4A1 HPE Deployment Services for Veeam SVC

1 H5UR4A1 001 HPE Deploy of Veeam Base SVC

1 Q1K20A Veeam Add 2yr BU Repl Ent+ VMware Maint

1 H5UR4A1 HPE Deployment Services for Veeam SVC

1 H5UR4A1 001 HPE Deploy of Veeam Base SVC

Technical white paper Page 17

APPENDIX B: REST APIS FOR VEEAM FUNCTIONALITY The integration between Veeam and HPE Nimble provides additional benefits. Working with HPE Nimble, Veeam not only manages hardware snapshots inside backup jobs, but it can also orchestrate hardware snapshots and manage them as independent restore points. Veeam provides a comprehensive set of APIs to monitor and manage Veeam-based backup infrastructure. The APIs are documented in detail at the Veeam Help Center.

Technical white paper

Make the right purchase decision. Contact our presales specialists.

Share now

Get updates

© Copyright 2018, 2020 Hewlett Packard Enterprise Development LP. The information contained herein is subject to change without notice. The only warranties for Hewlett Packard Enterprise 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.

Microsoft, Windows, and Windows Server are registered trademarks of Microsoft Corporation in the United States and/or other countries. VMware, vCenter, and vSphere are registered trademarks or trademarks of VMware, Inc. in the United States and/or other jurisdictions. Veeam and Backup & Replication are trademarks of Veeam Software, registered in the U.S. and/or other countries. All third-party marks are property of their respective owners.

a00046770ENW, March 2020

Check if the document is available in the language of your choice.

Resources, contacts, or additional links HPE Storage networking

HPE Data Protection Storage

HPE StoreEver Tape Storage

HPE reference architectures Data Protection of Virtual Machines with HPE StoreEver Tape Storage using Veeam Backup and Recovery software

Managing HPE Nimble Storage snapshots, replication, and backup to HPE StoreOnce with Veeam

Better data availability for the Always-On Enterprise

Veeam resources:

• HPE + Veeam: Better Together

• Veeam with HPE StoreOnce Catalyst Configuration Guide

• Data Availability without Limits

• Veeam Help Center: HPE StoreOnce

• Veeam Availability Suite - HPE Storage Integration video

• Veeam Backup from HPE Storage Snapshot video

• HPE Storage Snapshot-orchestration Blog

LEARN MORE AT hpe.com/storage