HPE Reference Configuration for HPE Cloud Bank Storage with S3 Connector and Scality

Transcription

1 HPE Reference Configuration for HPE Cloud Bank Storage with S3 Connector and Scality Solution overview, best practices, and recommendations Reference Architecture

2 Reference Architecture Contents Executive summary... 3 Solution overview... 3 Configuring Scality RING storage for HPE Cloud Bank stores... 5 Comparison of HPE Cloud Bank stores and HPE StoreOnce Catalyst stores... 6 Comparison of HPE Cloud Bank direct restore and optimized restore... 6 Comparison of the value of HPE Cloud Bank with Scality RING vs public cloud (such as AWS)... 7 Veritas NetBackup software... 7 Solution components... 8 Storage components... 8 Application components... 8 Network configuration... 9 Environment setup diagram... 9 Best practices and configuration guidance for HPE Cloud Bank HPE Cloud Bank prerequisites Creating an HPE StoreOnce Cloud Bank store Viewing the HPE Cloud Bank store summary Catalyst Copy to an HPE Cloud Bank store with Veritas NetBackup Configuring an HPE Cloud Bank device in Veritas NetBackup HPE Cloud Bank typical backup cycle HPE Cloud Bank optimized restore HPE Cloud Bank multi-reader capability HPE Cloud Bank disaster recovery HPE Cloud Bank detach and disconnect HPE Cloud Bank reattach Testing summary and recommendations Summary Implementing a proof-of-concept Resources and additional links... 23

3 Reference Architecture Page 3 Executive summary Data is at the core of all organizations, and protecting it is more important than ever. The risks of temporarily or permanently losing access to data are widely documented. Backup remains the key process to mitigate this risk. As data volumes increase, organizations are looking for ways to efficiently and cost-effectively manage backup footprints within their data centers. The question of where to store enterprise backup data is essential. There is a move to use public cloud services to take advantage of pay-as-you-go pricing and flexible data storage, but critical business reasons might exist to keep data on-site. Because choosing among on-premises, cloud, and a hybrid solution requires an analysis outside the scope of this paper, the focus is on on-premises storage of backup data. Refer to the HPE Decision guide: Public cloud versus on-prem storage for an informative reference covering some of these broader questions. HPE Cloud Bank Storage is a feature of HPE StoreOnce systems that is: Designed to lower long-term data retention costs by leveraging on-premises or cloud-based object storage An extension of HPE StoreOnce Catalyst 1 that uses external object storage to store backup data Able to supports multiple on-premises and cloud-based object storage targets such as Scality RING TM software, Amazon Web Services (AWS), and Microsoft Azure Blob storage HPE Cloud Bank Storage amplifies the low costs of object storage with HPE StoreOnce deduplication to enable cost-effective, long-term backup data retention with on-premises and cloud object storage services. This paper focuses on using HPE Cloud Bank Storage with Scality RING. Unlike public clouds, Scality RING lets you budget and control costs with no unexpected fees; for example, retrieval fees for accessing your backup data. For environments that scale to hundreds of terabytes or more, HPE Scalable Object Storage with Scality RING gives the performance and protection of an on-premises solution with the flexibility and economics of the cloud. In typical object storage deployments, a single Scality RING cluster can store backups and provide other storage use cases where objects are beneficial and capacity/bandwidth considerations are practical. This object storage approach allows enterprises to consolidate backup and other workloads into a single large data repository, with data from enterprise backups being one of several types of data stored in Scality RING. Most data needs to persist longer than infrastructure components. For this reason, access to data stored in HPE Cloud Bank Storage is not dependent on a specific HPE StoreOnce system. This also means that in the event an HPE StoreOnce system becomes unavailable or unusable, the data in the cloud remains accessible. An HPE Cloud Bank store can be accessed by reattaching it to a different HPE StoreOnce system, including an HPE StoreOnce Virtual Storage Appliance (VSA) software instance. Using HPE StoreOnce Catalyst Copy, data on the HPE Cloud Bank store can be copied to a local Catalyst store, allowing all data to be efficiently recovered. The result is that HPE Cloud Bank Storage is a versatile, robust, and available backup data store. This Reference Configuration features HPE Cloud Bank Storage with Scality RING as the object storage target and Veritas NetBackup as the data mover. HPE Scalable Object Storage with Scality RING is software-defined storage residing on high capacity HPE Apollo 4000 servers to offer virtually limitless capacity combined with the reliability and availability of the Scality RING. Target audience: Presales consultants, solution architects, storage operators, and administrators who design, implement, and maintain common backup tasks, and others wanting to learn more about HPE Cloud Bank Storage with Scality RING. Solution overview HPE Cloud Bank Storage (HPE Cloud Bank) is an HPE StoreOnce feature that allows the HPE StoreOnce system to use external object storage. In use, an HPE Cloud Bank store behaves almost identically to an HPE Catalyst store. This common behavior enables administrators to utilize HPE StoreOnce deduplication technology when sending, storing, and retrieving their data from private or public cloud storage. The key difference is that an HPE Cloud Bank store is supported as a Catalyst Copy target, not as a backup target. The key Cloud Bank use cases are: Long-term retention of backup data Physically separated private or public cloud copies of backups for disaster recovery Detached Cloud Bank stores for very long-term backup data retention and archiving 1 See HPE StoreOnce Catalyst: A Solution for Enhanced Data Protection

4 Reference Architecture Page 4 A key consideration when using private cloud object storage such as Scality RING is the cost of capacity for storing the data. An HPE StoreOnce Catalyst Copy operation efficiently copies deduplicated and compressed backup data sets from an HPE StoreOnce Catalyst store to an HPE Cloud Bank store. Through this deduplication and compression, HPE Cloud Bank reduces the capacity and associated costs of storing the data in on-premises private cloud storage with Scality RING. Thus, HPE Cloud Bank and Scality RING give you the performance and protection of an onpremises backup and archive solution with the flexibility and economics of the cloud. Together, HPE StoreOnce systems with Cloud Bank Storage and HPE Scalable Object Storage with Scality RING deliver an on-premises, private cloud solution for long-term backup data retention. Benefits of this solution include: Low cost storage for backup and retention data HPE Scalable Object Storage is used to extend the usable capacity of HPE StoreOnce systems up to three times the maximum native capacity. The extended capacity is managed using the HPE StoreOnce management console. The HPE Cloud Bank Storage capacity can be further extended by detaching HPE Cloud Bank stores, which allows the detached capacity to be reused. In addition, the same Scality RING can provide object storage for other use cases and applications. HPE StoreOnce advanced data deduplication and compression minimizes network bandwidth use by sending only unique data to and from the Scality RING. This has the added benefit of shortening the time required for copies of backups to be written to or read from the onpremises private cloud storage. The same advanced data deduplication and compression minimizes the storage space required - to amplify the cost benefits of the HPE Scalable Object Storage. Flexibility Immediately cloud-enable supported data protection applications (Micro Focus Data Protector, Veritas NetBackup, HPE Recovery Manager Central, and so on) - with no gateway or other additional infrastructure needed. Choose one or more object-storage vendors to provide capacity for HPE Cloud Bank Storage (Scality, AWS S3, Azure Blob Storage, and so on). Configure your data protection to use the appropriate class of storage from snapshots on primary arrays to long-term retention on HPE Cloud Bank (Scalable Object Storage). Simplicity without risk No process changes needed; existing backup applications continue as the single management point for backup, copy, retention, restore, and disaster recovery. Ensure secure transmission and storage in the cloud with in-flight encryption, at rest encryption, or both, as well as data immutability. If the HPE StoreOnce system hosting the HPE Cloud Bank stores is unavailable - for any reason - these stores can be accessed via another HPE StoreOnce system, including HPE StoreOnce VSA. All data management remains within the data protection application for easy management of the data through its lifecycle.

5 Reference Architecture Page 5 A simplified environment setup for HPE Cloud Bank with Veritas NetBackup and Scality RING storage is shown in Figure 1. Figure 1. Simplified environment setup for HPE Cloud Bank with Scality RING and Veritas NetBackup Configuring Scality RING storage for HPE Cloud Bank stores The possible uses and applications of HPE Scalable Object Storage with Scality RING are many and varied. An HPE Cloud Bank store configured to use Scality RING storage benefits from object store protection, allowing large amounts of data to be stored cost effectively, securely, and under the complete control of your enterprise. This object store protection includes options for setting different levels of Scality Advanced Resilience Configuration (ARC) erasure coding and replication in the Scality RING to provide varying levels of data durability - enabling users to choose data protection levels up to 14-nines. The specified protection level specified in the Scality RING does not impact performance with HPE Cloud Bank. Therefore, the selection of data durability options should be driven by the level of data protection needed in a particular environment. The Scality RING should be sized appropriately to accommodate the maximum HPE Cloud Bank storage capacity of your HPE StoreOnce system. Table 1 lists the maximum supported HPE Cloud Bank storage capacity for each family of HPE StoreOnce, and the minimum recommended Scality RING configuration for each. The three node configurations below, recommended for the HPE StoreOnce 3100, 3520, and 3540, use ARC(7,5) erasure coding. All of the remaining six and nine node configurations use ARC(8,4) + COS 3 erasure coding and replication: Table 1. Recommended minimum Scality RING configurations by HPE StoreOnce model Max HPE Cloud Bank Storage Capacity (with RAM expansion) Minimum recommended Scality RING usable capacity Single-site Scality RING configuration details (where available) HPE StoreOnce TB 175 TB Three HPE Apollo 4200 Gen9 servers, each with 10 x 10-TB 7.2K SATA HDD HPE StoreOnce TB 175 TB Three HPE Apollo 4200 Gen9 servers, each with 10 x 10-TB 7.2K SATA HDD HPE StoreOnce TB 175 TB Three HPE Apollo 4200 Gen9 servers, each with 10 x 10-TB 7.2K SATA HDD HPE StoreOnce TB 443 TB Six HPE Apollo 4200 Gen9 servers, each with 12 x 10-TB 7.2K SATA HDD HPE StoreOnce TB 1772 TB Six HPE Apollo 4510 Gen10 servers, each with 40 x 12-TB 7.2K SATA HDD HPE StoreOnce TB 3456 TB Nine HPE Apollo 4510 Gen10 servers, each with 52 x 12-TB 7.2K SATA HDD

6 Reference Architecture Page 6 Note The minimum licensed capacity for HPE Scalable Object Storage with Scality RING is 200 TB, even if the physical storage yields a smaller usable capacity. In Table 1, the minimum recommended usable capacity of a single-site Scality RING has been sized to correspond as closely as possible to the maximum HPE StoreOnce Cloud Bank storage capacity. Scality RING capacity need not be limited to this amount, but can be expanded well beyond these values to simultaneously accommodate additional applications and use cases, and meet the capacity needs of your enterprise. With HPE Cloud Bank stores, the backup data is stored on the external object storage. A small amount of metadata is stored on the HPE StoreOnce system to reduce traffic to and from the object storage. Because Scality RING has multiple S3 Connectors on the data network, it is able to handle more bandwidth and throughput than HPE StoreOnce typically sends during a Catalyst Copy operation; therefore, Scality RING is not a performance bottleneck. There are multiple ways to address the data network between the HPE StoreOnce system and Scality RING to make sure that it does not become a limiting factor: Bonded network ports Fast data network: 10 GbE or faster Load balancer feeding multiple S3 Connectors Comparison of HPE Cloud Bank stores and HPE StoreOnce Catalyst stores HPE Cloud Bank stores and HPE StoreOnce Catalyst stores are created and behave in similar ways. Data protection software and business applications that support HPE StoreOnce Catalyst Copy functionality can create backup copies on an HPE Cloud Bank store, see One fundamental distinction between the two stores is that HPE Cloud Bank stores write deduplicated and compressed data to private or public cloud storage, as opposed to a regular HPE StoreOnce Catalyst store where the deduplicated and compressed data is written to the local HPE StoreOnce system. The objects written to an HPE Cloud Bank store in on-premises private cloud or a Cloud Service Provider (CSP) contain all of the information necessary to reconstruct the backup data within the HPE Cloud Bank store. Comparison of HPE Cloud Bank direct restore and optimized restore HPE Cloud Bank data can be recovered through either a direct restore or an optimized restore, as shown in Figure 2. Figure 2. Direct restore and optimized restore data flow

7 Reference Architecture Page 7 Direct restore A direct restore is a restore read from the HPE Cloud Bank store. In this case, all of the data to be restored is read directly from Scality RING, before being written to the restore location. Any block of data that is a duplicate of data already read from the HPE Cloud Bank store must be read again. With this method of restore, a single block of data could be read from the HPE Cloud Bank store multiple times, thus eliminating the benefit of the HPE StoreOnce deduplication technology. The result is higher network usage from the increased reads. It might be desirable to perform a direct restore in cases when the Scality RING, HPE StoreOnce system, and the location where data is being restored are all in the same data center. There are no hidden fees to retrieve your data directly from on-premises private cloud with Scality RING. Optimized restore An optimized restore is a two-step process. The first step is a Catalyst Copy from the HPE Cloud Bank store to a local Catalyst store on the HPE StoreOnce system. The second step is a restore from that local Catalyst store. In this case, only the data chunks that do not exist on the local Catalyst store are read, reducing the amount of data read from Scality RING, and resulting in lower network utilization. Additionally, if a restore is interrupted for any reason, data already read from Scality RING would not have to be retrieved a second time. Optimized restore is most useful when the destination of the restore is in a remote location. For a comprehensive explanation of optimized restore, see HPE Cloud Bank optimized restore. Comparison of the value of HPE Cloud Bank with Scality RING vs public cloud (such as AWS) Using HPE Cloud Bank Storage with Scality RING does not prevent the use of other object storage services. An HPE StoreOnce system can use object storage from multiple private and public Cloud Service Providers (CSPs) at the same time. Even though HPE Cloud Bank is supported with multiple private and public cloud services, there are several distinct advantages to using Scality RING as the object storage associated with HPE Cloud Bank: Your data never goes outside of your enterprise, so you always maintain complete control of your data. With Scality RING, there are no additional fees to retrieve your data. In a disaster recovery scenario, data can be retrieved from the on-premises Scality RING much faster than from public cloud. The Scality RING accommodates either single-site or geo-distributed configurations, which increases fault tolerance and simplifies disaster recovery. With Scality RING, both data availability and data durability are in your control. Scality RING provides several options for erasure coding and internal replication for data durability up to 14-nines to eliminate the potential for the public cloud or any intervening network to render your data unavailable. A single Scality RING can simultaneously be used for many purposes in addition to long-term retention of backup data with HPE Cloud Bank. Such uses include hosting scale-out object storage as a service, nearline archives for media and entertainment companies, medical imaging and records, long-term archives of surveillance information or research data, financial compliance archives, and many other applications. With Scality RING, network speeds of 10 GbE, 40 GbE, and higher are supported, with a load balancer feeding multiple S3 Connectors at the same time. Comparable network bandwidth to a public cloud service would be prohibitively expensive. With multiple network ports bonded together, network speeds of 40 GbE or higher are supported, and a load balancer, Scality RING and the network connection should not become a performance bottleneck. In contrast, with public cloud, the bandwidth of the connection to the cloud can easily become a performance limiter, depending on your network provider bandwidth and SLA. Veritas NetBackup software HPE Cloud Bank stores can be configured with any supported backup application software that allows HPE StoreOnce Catalyst Copy operations. For this solution, Veritas NetBackup was chosen as the backup application. To see a full list of backup applications and plug-ins that support Catalyst Copy operations, refer to the Veritas NetBackup is a leading enterprise software suite for backup/archival solutions that is built to protect large and demanding enterprise environments. NetBackup provides a holistic backup and recovery solution optimized for data protection that scales efficiently with object storage solutions and HPE Catalyst Copy jobs. HPE Cloud Bank stores are configured in Veritas NetBackup as normal disk pools and storage units, just like any other Catalyst store.

8 Reference Architecture Page 8 HPE StoreOnce Catalyst Copy operations are set up and managed in Veritas NetBackup through a Storage Lifecycle Policy and require the HPE StoreOnce Catalyst NetBackup OST plug-in in conjunction with the Veritas NetBackup software on the NetBackup Master and Media servers. Backups are first written to a local HPE StoreOnce Catalyst store. Then the Veritas NetBackup duplication (copy) operation invokes the Catalyst Copy feature of HPE StoreOnce to send a copy of the deduplicated and compressed backup to an HPE Cloud Bank Storage store. This Catalyst Copy operation writes indexing and metadata to the HPE Cloud Bank store residing on the HPE StoreOnce system, but writes all the backup data and metadata to HPE Scalable Object Storage with Scality RING using the Scality S3 Connector. Solution components Storage components HPE StoreOnce Cloud Bank Storage HPE StoreOnce Cloud Bank is an HPE StoreOnce feature that leverages external object storage for the long-term retention of backup copies. By using the HPE StoreOnce deduplication technology, it enables the efficient use of total object storage capacity as well as bandwidth utilization to and from the cloud. HPE Scalable Object Storage with Scality RING Scality RING provides the flexibility to support single-site and geo-dispersed configurations. The minimum RING size for a single-site configuration is three nodes, and it can be expanded in increments of three nodes. A multisite geo-dispersed configuration must be a minimum of six nodes, and must be expanded in increments of six nodes. Whether single-site or geo-dispersed, the Scality RING storage scales virtually without limits, so you can grow your capacity as needed with linear performance in less space and with extreme data availability. No special configuration of the HPE Scalable Object Storage with Scality RING is needed to use object storage with backup applications. The Scality RING is delivered from HPE with a full functionality S3 target, ready to be activated and used immediately with applications such as Veritas NetBackup. A critical step in the configuration of the Scality RING S3 Connector is recording the user access and secret keys. These are required when creating both the HPE Cloud Bank Storage store and the Veritas NetBackup Cloud Storage Server. HPE Apollo 4000 storage servers HPE Apollo 4000 density-optimized storage servers are purpose-built as object-storage platforms and for big data. The power and flexibility of the HPE Apollo 4000 platform enables a robust and scalable object storage solution that with Scality RING provides linear scale-out as a single protected system across multiple sites and thousands of servers. Testing for this solution was conducted on a single-site, six-node cluster of HPE Apollo 4000 storage servers and HPE Scalable Object Storage with Scality RING configured with five S3 connectors. This configuration represents a basic out-of-the-box setup, and is very adequate for use with HPE Cloud Bank Storage. HPE StoreOnce 6600 backup appliance The HPE StoreOnce 6600 backup appliance used firmware version The backup appliance contained one couplet with two drive enclosures containing 36x4 TB drives per shelf. This HPE StoreOnce 6600 backup appliance acted as the primary backup device for all portions of this test. Housekeeping, replication, HPE StoreOnce Catalyst, and HPE Cloud Bank Detach were licensed and enabled. HPE StoreOnce VSA An HPE ProLiant DL core (2x Intel Xeon CPU 1.60GHz) server was configured with 4 TB of HPE 3PAR storage, 96 GB of physical memory, and VMware ESXi The HPE StoreOnce VSA used in testing was created on this platform. The HPE StoreOnce VSA software version was This HPE StoreOnce VSA acted as a disaster recovery device when the primary HPE StoreOnce system was simulated to have a hardware failure, and as a secondary HPE StoreOnce system for the multi-reader and detach tests. Housekeeping, replication, and HPE StoreOnce Catalyst were licensed and enabled. HPE 3PAR 8400 storage The HPE 3PAR 8400 storage array, using 24x1.2 TB hard disk drives and OS version , was connected to a 16 Gb Fibre Channel backend fabric. Storage from this array was used to contain the datasets being backed up. Application components Veritas NetBackup Master Server An HPE ProLiant DL core (2x Intel Xeon CPU 2.00 GHz) server was configured with 48 GB of physical memory. Veritas NetBackup v8.1 Build 0049 was installed on a Windows Server 2012 R2 operating system.

9 Reference Architecture Page 9 Veritas NetBackup Media Servers Two HPE ProLiant DL380p 12-core (2x Intel Xeon CPU 2.00 GHz) servers were configured with 48 GB of physical memory. Both of these were running Windows Server 2012 R2 with Veritas NetBackup 8.1 configured as Media Servers. One additional HPE ProLiant DL380p 12-core (2x Intel Xeon CPU 2.90 GHz) server was configured with 64 GB of physical memory, and running Red Hat Enterprise Linux 7.2 with Veritas NetBackup 8.1 configured to be a Media Server. Network configuration In lab testing, the local management network for all devices was configured using 1 Gb Ethernet. The primary storage (HPE 3PAR 8400) was configured via 16 Gb FC SAN. The local data network was configured using 10 Gb Ethernet. The data network connection to the Scality RING was also configured to be 10 Gb Ethernet. Environment setup diagram Figure 3 shows the environment setup for this solution. Figure 3. Solution test environment setup

10 Reference Architecture Page 10 Best practices and configuration guidance for HPE Cloud Bank HPE Cloud Bank prerequisites Object storage buckets on Scality RING The S3 Connector API stores objects in containers called buckets. When using HPE Scalable Object Storage and the Scality S3 Connector with HPE Cloud Bank stores, you must specify a bucket name that already exists in Scality object storage. Neither HPE StoreOnce nor Veritas NetBackup include a client interface for creating or viewing buckets on Scality - they must be created using a separate application. There are several tools and applications that provide the ability to create and view buckets on Scality object storage. One such tool is CloudBerry Explorer, a free S3-compatible browser that enables you to create and view the buckets that are used for HPE Cloud Bank stores. To use CloudBerry Explorer to create the buckets, perform the following steps: 1. Add an account specification to CloudBerry to access the Scality S3 Connector. To do this, launch CloudBerry Explorer, and then select File New S3 Compatible Account. 2. Select Scality as the cloud storage provider. 3. Enter a descriptive account name to display. 4. For Service point, enter the IP address or fully qualified domain name of the S3 Connector, as well as the service port (port 80). 5. Enter the Access key and Secret key that were generated when the S3 Connector and user account were configured on the Scality RING object storage. 6. Un-check the Use SSL box before completing the account definition, because SSL is not used with Scality object storage. 7. Click the Test Connection button to verify that the connection details and access keys are correct, and that the server can connect to the HPE Scalable Object Storage with Scality RING. If everything is correct, a pop-up window appears indicating Connection success. 8. Click Close on the Connection success window, and OK to save the settings and create the new storage account in the CloudBerry user interface. A completed Add New Scality Storage Account dialog box is shown in Figure 4. Figure 4. Using CloudBerry to create a new Scality storage account

11 Reference Architecture Page 11 To create a new bucket using CloudBerry Explorer, perform the following steps: 1. Select the storage account on Scality S3 as the Source. 2. Click the icon of a blue cube with a star on it, as shown circled in red in Figure 5. This is the New Bucket icon. 3. Enter a descriptive name and click OK. 4. The newly created bucket will appear in the CloudBerry Explorer display, and will also be available for use in creating HPE Cloud Bank stores. Figure 5. Using CloudBerry to create and view buckets in Scality RING Caution CloudBerry Explorer allows you complete control of the S3 buckets as well as their contents. This includes adding and deleting buckets and files at will. Use CloudBerry Explorer or another application only to create the buckets needed by HPE StoreOnce, or to view buckets and contents. Be careful not to delete any buckets or files used by the HPE Cloud Bank Store. Configuring the HPE Cloud Bank proxy server Proxy servers can be enabled to connect an HPE Cloud Bank store to the on-premises private cloud or public cloud service. If a proxy is necessary in your environment, follow these steps to configure the proxy server: 1. Log in to the HPE StoreOnce Management Console. 2. Go to StoreOnce StoreOnce Catalyst. 3. Under StoreOnce Catalyst, select Settings. 4. Under the Proxy Server section, select Edit.

12 Reference Architecture Page Input the host address and the port number of the proxy server, as shown in Figure 6. Optionally, input the username and password for the proxy server. 6. Click Update. Figure 6. Configuring proxy server settings for the HPE Cloud Bank server in the HPE StoreOnce Management Console HPE Cloud Bank stores Before HPE StoreOnce can utilize external object storage, an administrator must create an HPE Cloud Bank store, which is configured in the HPE StoreOnce Management Console. Creating an HPE Cloud Bank store requires an HPE StoreOnce Catalyst license and HPE Cloud Bank licenses to cover the planned capacity of the HPE Cloud Bank stores. For existing HPE Cloud Bank stores, HPE StoreOnce provides the option to connect with read-write or read-only access. These options are explained in more detail in HPE Cloud Bank detach and disconnect. To utilize HPE Cloud Bank functionality, the following criteria must be met: An HPE StoreOnce system based on an HPE ProLiant Gen9 or newer server with the following: Firmware version or newer HPE StoreOnce Catalyst license Sufficient HPE Cloud Bank licenses for the capacity of the connected stores Sufficient local storage for reconnected HPE Cloud Bank store metadata: approximately 1% of the store capacity A cloud-hosted HPE StoreOnce VSA could also be used if the VSA contains sufficient storage. For reconnection to an HPE Cloud Bank store, the following criteria must also be met: Less than 60 days since the HPE Cloud Bank store was disconnected from an HPE StoreOnce system. If the HPE Cloud Bank store is encrypted, the encryption key and encryption password are required. Note Administrators should also consider capacity expansion, depending on how close to maximum capacity they plan to utilize their local storage. Creating an HPE StoreOnce Cloud Bank store An administrator can create an HPE StoreOnce Cloud Bank store by following the steps below. The HPE Cloud Bank store must be associated with a cloud storage provider (in this case, Scality RING). All of the usual HPE Catalyst store options are available. Perform these steps to create an HPE Cloud Bank store using HPE Scalable Object Storage with Scality RING: 1. Log in to the HPE StoreOnce Management Console. 2. In the navigator pane on the left side of the window, go to StoreOnce StoreOnce Catalyst Stores.

13 Reference Architecture Page Click Create at the top right of the window. The New Store window will appear, as shown in Figure If multiple Service Sets are displayed, select the Service Set to be used for the HPE Cloud Bank store and click OK. 5. Create a Name and Description for the HPE Cloud Bank store and set other configuration settings as necessary. If encryption of the store is desired, select Store Encryption Enabled. 6. Check the box next to Cloud Bank Storage to configure as an HPE Cloud Bank store. 7. From the Cloud Service Provider drop-down list, select Scality. This will add five lines to the bottom of the New Store window, where you can enter the access information for the Scality RING. 8. Enter the Access key and Secret Key for your Scality RING. The access key and secret key were created at the time the Scality S3 Connector was configured on the Scality RING. 9. Enter the IP address or domain name of the Host where your S3 Connector or load balancer is configured. This field must include the prefix. Https is not supported in this field, but the store will be encrypted if Store Encryption Enabled was selected during step 5 above. 10. Change the Port number to 80. The default port number does not work in this application. 11. Enter the Bucket Name to be used on the Scality RING. This bucket must already exist. See Object storage buckets on Scality RING for details on creating buckets in your Scality RING object storage. 12. Click Create. Figure 7. Creating a new HPE Cloud Bank store with Scality RING 13. If Store Encryption is enabled, an encryption key is generated and a password is required for that encryption key. A prompt is displayed to enter an Encryption Key password. Enter and confirm a password and click OK. Figure 8 and Figure 9 highlight these steps.

14 Reference Architecture Page 14 Important The encryption password is necessary for reconnection. It must be stored in a safe place. Figure 8. Creating a password for the encryption key for an HPE Cloud Bank store Figure 9. Generating an encryption key after creating an HPE Cloud Bank store

15 Reference Architecture Page 15 Note Direct backups to an HPE Cloud Bank store are not supported for performance reasons. Backups are written first to a regular HPE StoreOnce Catalyst store and then copied to the HPE Cloud Bank store, using Catalyst Copy operations. Note When selecting the checkbox for HPE Cloud Bank, Store Encryption is enabled by default. HPE recommends enabling Store Encryption with HPE Cloud Bank stores to protect the data on the external object storage. Viewing the HPE Cloud Bank store summary The HPE StoreOnce Catalyst stores section in the HPE StoreOnce Management Console displays the HPE StoreOnce Catalyst and HPE Cloud Bank stores. The table entries for each HPE Cloud Bank store show the capacity of data stored externally to HPE StoreOnce in HPE Scalable Object Storage with Scality RING (Size in Cloud) and any other configured object storage targets. Figure 10 shows the HPE Cloud Bank store summary. Figure 10. HPE Cloud Bank store summary Catalyst Copy to an HPE Cloud Bank store with Veritas NetBackup The primary method of transferring backup data into an HPE Cloud Bank store involves HPE StoreOnce Catalyst Copy technology already present in many backup applications. HPE StoreOnce Catalyst Copy efficiently transfers deduplicated data from one Catalyst store to another. To perform an HPE StoreOnce Catalyst Copy with Veritas NetBackup, a Catalyst Copy job must be configured as part of a Storage Lifecycle Policy. The data protection application feeds data to the local Catalyst store, then copies the data to the HPE Cloud Bank store on Scality RING object storage by initiating a Catalyst Copy. Figure 11 shows the data flow for backup and copy operations with Veritas NetBackup, HPE Cloud Bank, and HPE Scalable Object Storage with Scality RING. Figure 11. Backup and Copy operations data flow

16 Reference Architecture Page 16 Configuring an HPE Cloud Bank device in Veritas NetBackup Before the HPE StoreOnce Cloud Bank store can be used by Veritas NetBackup, a new Storage Server, Disk Pool, and Storage Unit must be created for it. Then a Catalyst Copy job must be configured to write data to HPE Cloud Bank. The sections below provide the steps necessary to incorporate an HPE Cloud Bank Storage store into NetBackup copy operations: Create the Veritas NetBackup storage resources necessary to use the HPE Cloud Bank Storage Catalyst store. Create a Veritas NetBackup Storage Lifecycle Policy directing backups to an HPE StoreOnce Catalyst store and duplication operations to an HPE Cloud Bank Storage store. Create a Veritas NetBackup Policy that specifies the Storage Lifecycle Policy as the policy storage. Create the Veritas NetBackup storage resources necessary to use the HPE Cloud Bank Storage Catalyst store Creating a storage server based on the HPE Cloud Bank Storage Catalyst store follows the same procedure used to create a storage server based on a regular HPE StoreOnce Catalyst store. To create the necessary storage resources, perform the following steps in the Veritas NetBackup Administration Console: 1. To create a new storage server for HPE Cloud Bank storage, expand Media and Device Management Credentials. 2. Right click Storage Servers and select New Storage Server. 3. In the wizard window, select OpenStorage as the type of disk storage to create, and click Next. 4. Select a media server from the drop-down list. Note that the only media servers available to choose from are those media servers that have the HPE StoreOnce Catalyst NetBackup OST plug-in already installed. 5. For Storage server type, enter hp-storeoncecatalyst. If this is the first time this storage server type is used, this must be typed in manually. 6. For Storage server name, enter the data network IP address of the storage server (HPE StoreOnce system) to be added. 7. Enter the login credentials for the HPE StoreOnce system and finish the wizard. 8. You may proceed directly into the Disk Pool wizard, or launch the wizard separately by selecting Configure Disk Pool from the NetBackup Administration Console. 9. Select OpenStorage (hp-storeoncecatalyst) as the storage server type. 10. For Storage server name, enter or select the data network IP address of the HPE StoreOnce system where the HPE Cloud Bank Store was created. 11. Enter the login credentials for the HPE StoreOnce system, if prompted. 12. The Volume Name list will include the names of all the Catalyst stores discovered on the selected HPE StoreOnce storage server. Select the desired HPE Cloud Bank store. 14. Continue on with the wizard to complete the creation of the storage unit, and exit the wizard when finished. Create a Veritas NetBackup Storage Lifecycle Policy In Veritas NetBackup, an HPE StoreOnce Catalyst Copy operation is managed with a Storage Lifecycle Policy. This Storage Lifecycle Policy must be configured with an additional duplication job after the initial full or incremental backup. When the Storage Lifecycle Policy is created, you have the option to have the duplication operation initiated immediately after successful completion of the backup, or you may choose to postpone creation of the copy until the backup is about to expire. After this behavior is defined in the Storage Lifecycle Policy, it is applied consistently across all backups where that Storage Lifecycle Policy is used. In addition to the behavior of when the duplication operation is initiated, the Storage Lifecycle Policy also defines the storage units that will be used in a combined backup/duplication operation. Creating a Storage Lifecycle Policy to use an HPE Cloud Bank store is no different than creating a Storage Lifecycle Policy for any other Catalyst store. To add a Catalyst Copy (duplication) job to a Storage Lifecycle Policy, complete the following steps: 1. From the NetBackup Administration Console, select Storage Lifecycle Policies, right click and select New, and proceed through the wizard normally.

17 Reference Architecture Page When specifying the storage unit for the Backup operation, select the storage unit mapped to the local Catalyst store. 3. When entering the storage unit for the Duplication operation, be sure to select the storage unit mapped to the HPE Cloud Bank store. 4. On the same page where you specify the storage unit for the duplication operation, you may also select when the duplication should be performed. To postpone this duplication operation until the original backup is about to expire, mark the appropriate checkbox. If you leave the checkbox unmarked, the duplication will begin immediately upon successful completion of the backup. 5. Exit the wizard when finished. The first storage unit (specified in step 2 above) will be the target for the backup operation, which is normally the local Catalyst store on the HPE StoreOnce system. This storage unit then becomes the source location for the duplication (copy) operation. The second storage unit (specified in step 3 above) will be the target of the duplication operation, in this case the HPE Cloud Bank store, which in turn sends data to the Scality RING. Create a NetBackup Policy to use the Storage Lifecycle Policy The Storage Lifecycle Policy created above only specifies the storage units to be used in a combined backup/duplication operation. It does not specify any of the parameters of the backup job itself; that is the function of a NetBackup Policy. One of the key attributes in any policy is the selection of the storage to be used by the policy. To launch a combined backup/duplication operation, a defined Storage Lifecycle Policy must be specified as the Policy Storage to be used by the policy. By specifying the Storage Lifecycle Policy in the Policy Storage attribute of the policy definition, backups are directed to the HPE StoreOnce Catalyst store, and HPE StoreOnce performs a Catalyst Copy operation to copy the deduplicated backup sets to the HPE Cloud Bank Storage store. As with the storage resources and Storage Lifecycle Policy described above, creating a policy for use with HPE Cloud Bank storage is the same as creating a policy for any other HPE StoreOnce Catalyst stores. When creating the policy, be sure to set the Policy Storage attribute in the new policy to the name of the Storage Lifecycle Policy created above. HPE Cloud Bank typical backup cycle In a typical backup scenario, backups are first written to an HPE StoreOnce Catalyst store. Upon completion of the backup, the Catalyst Copy operation is either launched immediately or waits until the backup is about to expire, depending on your selection in the Storage Lifecycle Policy. When the copy operation is performed, it sends a copy of the deduplicated and compressed backup set to an HPE Cloud Bank Storage store. Index information is written to the Cloud Bank store on the HPE StoreOnce system, while backup data and metadata is written to Scality RING using the Scality S3 Connector. Note Housekeeping is an important process to maximize the deduplication efficiency of the HPE StoreOnce appliance. An administrator must ensure that the housekeeping process has enough time between backup windows to complete. A common backup practice is to define different retention periods for the local Catalyst store and the HPE Cloud Bank store. For example, backups held in the local Catalyst store are typically retained for a relatively short period such as one month, while the copies of backups contained in the Cloud Bank store can be retained for a much longer time. (For example, three months or one year, as dictated by corporate policy, internal governance, or regulatory compliance.) These retention periods are set in Veritas NetBackup when a backup policy is created, or can be modified later by editing the policy schedule. Another common practice is to do weekly full backups with daily incremental backups. For this testing, a four-week backup schedule was simulated by running a full backup followed by six incremental backups, representing one simulated week of backups. This schedule was then repeated three more times, for a total of 28 simulated days of backups. The size of the dataset being backed up was slightly larger than 100 GB with an initial compression ratio of 2:1. 1% of the data was changed between each backup. At the end of the 28-day cycle, the amount of User Data Stored was GB. The Size On Disk of the local Catalyst store was GB. The Size In Cloud (amount of data stored in the Scality RING) was GB. Thus the amount of storage capacity required in the Scality RING can be significantly less than the volume of data backed up. While the reduction of capacity required in the cloud-based object storage in this limited test is typical, the actual amount of capacity required in the Scality RING will vary based on a number of factors, including the type and compressibility of the data, the amount of deduplication, and how long the data is retained before it is expired. With the backup of a typical

18 Reference Architecture Page 18 business data set over a period of more than three months, users might expect to see a deduplication ratio of 20:1 2 for daily incremental and weekly full backups, or more for daily full backups. Scality RING, with the data reduction available with HPE StoreOnce deduplication and HPE Cloud Bank, is a very cost-effective way to keep all your backups with less worry that a long retention period will overflow your storage. Viewing bandwidth utilization to and from the cloud As of HPE StoreOnce version 3.18, a new Cloud Bank tab has been added to Reports in Reporting Central of the HPE StoreOnce Management Console. This tab is used to monitor upload and download bandwidth for the HPE Cloud Bank store, as well as the number of requests that are being sent to and received from the cloud. Individual HPE Cloud Bank stores can be selected for viewing and time periods can be selected, as required. When using HPE Scalable Object Storage with Scality RING, there are no specific costs associated with the amount of data sent to or retrieved from the HPE Cloud Bank store. The upload and download bandwidth information, along with the Disk Utilization report page, is useful in characterizing usage and can aid in capacity planning for the Scality RING. HPE Cloud Bank optimized restore In an optimized restore, the backup image is read back from the cloud-based storage in its deduplicated and compressed state. This minimizes the amount of data transferred from the cloud-based object storage to the local Catalyst store on the HPE StoreOnce system. With the onpremises private cloud implementation of Scality RING, data retrieval in an optimized restore or disaster recovery scenario is much faster than from public cloud. To perform an optimized restore with Veritas NetBackup and HPE Cloud Bank storage, do the following steps: 1. In the Catalog page of the NetBackup Administration Console, set the Action in the upper left corner of the Search window to Duplicate, and set the Media Disk Type to OpenStorage (hp-storeoncecatalyst). 2. On the right side of the pane, change Copies: to Copy 2, assuming Copy 1 (the Primary copy) is the backup contained on the local Catalyst store, and Copy 2 is the copy of the deduplicated backup contained on the HPE Cloud Bank store. If the data retention periods are different for the local Catalyst store and the HPE Cloud Bank store, Copy 1 (the primary copy) might have already expired and been removed. 3. Make sure the Date/Time Range specified includes the time of the backup you want to restore. 4. Click the Search Now button. This will show the backups contained in HPE Cloud Bank that are available to be duplicated back to the local Catalyst store. 5. Right click the backup image you want to copy to the local Catalyst store, and select Duplicate. 6. In the Setup Duplication Variables window that appears, leave Copies set to 1 (the number of copies of the object to create in the destination storage unit), and set Storage unit to the name of the NetBackup Storage Unit mapped to the local Catalyst store on the HPE StoreOnce system. 7. If you want the duplicated copy to become the Primary copy in the NetBackup catalog, mark the appropriate checkbox. Otherwise, leave the checkboxes unmarked. 8. Click OK to exit the dialog window and OK again to confirm the Duplication operation and initiate the Catalyst Copy from the HPE Cloud Bank store on Scality RING back to the local Catalyst store. You can observe the progress of the duplication in the Activity Monitor of Veritas NetBackup, and on the Activity page of the HPE StoreOnce Management Console. Note If you used multiple streams when the backup was originally done, the number of backup objects in the catalog will be equal to the number of streams used. All backup objects must be duplicated back to the local Catalyst store in order to perform a restore. Only one object can be selected and duplicated at a time. You can run several object duplication operations at the same time, but each one must be initiated individually. 9. After the duplication operation is complete, the backup should appear in the Backup, Archive, and Restore application for the server where the backup was originally performed. It can then be restored in the same way as restoring from a normal Catalyst store. 2 See What's so great about StoreOnce federated deduplication?

19 Reference Architecture Page 19 Benefits of optimized restore Direct restore When backups are restored directly from an HPE Cloud Bank store, the data is rehydrated as it is read back from the cloudbased storage. As data is being read back from the HPE Cloud Bank store, the HPE StoreOnce system determines if any given block of data was marked as a duplicate. If so, that one block must be read from the cloud-based storage multiple times. This act of reading the same block of data multiple times increases the volume of data transferred out of the cloud-based storage back to the local Catalyst store on the HPE StoreOnce system, and in turn, increases the cost for retrieving that data from a public cloud service such as AWS. While this is an important consideration with public cloud services, it is less crucial with Scality RING because there are no hidden fees associated with the amount of data sent to or retrieved from an HPE Cloud Bank store when using HPE Scalable Object Storage with Scality RING. Optimized restore Optimized restore eliminates this multiple reading of the same block of data. Because optimized restore takes advantage of the Catalyst Copy functionality built into every HPE StoreOnce system, the data is transferred from the cloud-based storage back to the local Catalyst store in its compressed and deduplicated state. Thus, each block of data is transferred only once. To complete the restore process, rehydration of the data is performed by the HPE StoreOnce system using the local Catalyst store, just as it would be for a restore operation from any other Catalyst store. Thus, the fully reconstructed data stream for the restore is only transferred over the local network, not the connection to the cloud-based storage. HPE Cloud Bank multi-reader capability HPE Cloud Bank multi-reader functionality grants the ability to read from an HPE Cloud Bank store residing on Scality RING or another object storage target, concurrently using multiple backup applications. Only one backup application at a time can write to the object storage target, while multiple backup applications from other locations can simultaneously access the storage data in a read-only mode, as shown in Figure 12. Figure 12. HPE Cloud Bank multi-reader functionality