HPE Reference Configuration for protecting data with Veritas NetBackup and HPE StoreOnce Best practices and recommendations using the HPE StoreOnce Catalyst Plug-in for Veritas NetBackup

Reference Configuration

Reference Configuration

Contents Executive summary ................................................................................................................................................................................................................................................................................................................................ 3 Solution overview ..................................................................................................................................................................................................................................................................................................................................... 3

HPE StoreOnce Catalyst Plug-in for Veritas NetBackup .............................................................................................................................................................................................................................. 3 Solution components ............................................................................................................................................................................................................................................................................................................................ 5

Hardware ................................................................................................................................................................................................................................................................................................................................................... 5 Software ..................................................................................................................................................................................................................................................................................................................................................... 6 Application ............................................................................................................................................................................................................................................................................................................................................... 6

Best practices and configuration guidance ...................................................................................................................................................................................................................................................................... 7 Overview of the Veritas NetBackup OST features compatible with the HPE StoreOnce Catalyst Plug-in ..................................................................................................... 7 Improved backup storage efficiency with HPE StoreOnce appliances ........................................................................................................................................................................................ 16 Using HPE Cloud Bank Storage to cloud-enable your storage, backup, and applications......................................................................................................................................... 18 Copying data to HPE StoreEver tape storage for cost-effective, long-term retention/compliance .................................................................................................................. 31

Summary ...................................................................................................................................................................................................................................................................................................................................................... 36 Appendix A: HPE StoreOnce concepts ............................................................................................................................................................................................................................................................................ 37 Resources and additional links ................................................................................................................................................................................................................................................................................................ 38

Reference Configuration Page 3

Executive summary Most data protection technologies in use today have limitations, including incompatible technology silos, restricted scale and performance, untenable service-level agreements (SLAs) and backup failures, and complex management. To address the limitations of current data protection technologies and provide greater protection, Hewlett Packard Enterprise offers HPE StoreOnce systems built on breakthrough scale-out architecture and federated deduplication that supports up to 20X more backup data storage in the same footprint.

HPE StoreOnce has a tight integration with Veritas NetBackup (NetBackup), enabled by the HPE StoreOnce Catalyst OpenStorage Technology (OST) Plug-in for Veritas NetBackup. This plug-in allows NetBackup-managed movement of deduplicated data across the enterprise, and affords better performance compared to traditional disk backup targets, simplified management with a single console, and greater flexibility for moving data from one site to multiple sites. Users can move data natively, reliably, and cost-effectively to the public, private, or hybrid cloud. This capability is delivered by HPE Cloud Bank Storage, a feature of HPE StoreOnce, and results in long-term retention and reliable disaster recovery that is simple and efficient.

Lastly, Veritas NetBackup software integrates with HPE StoreEver tape storage libraries to deliver seamless archiving and retrieval of backups. With features such as write once read many (WORM), encryption, and proactive monitoring of media and drives, HPE StoreEver tape storage provides the right balance of economics, durability, and reliability needed for long-term backup retention.

Key findings of the paper include:

• Improved backup storage efficiency with HPE StoreOnce systems: 6% overall capacity savings from using HPE StoreOnce for backups as compared to using NetBackup dedupe.

• Cloud-enablement of storage, backup, and applications: When using HPE Cloud Bank Storage with Veritas NetBackup, HPE StoreOnce deduplication minimizes the total volume of transmitted data and the storage footprint. Subsequent backups to the cloud are much smaller and faster because only unique data is transmitted. Conversely, when restoring from HPE Cloud Bank Storage, only the deduplicated data that is not in the local Catalyst store will be restored from the cloud.

• Cost-effective, long-term retention/compliance: By using NetBackup to duplicate the data on an HPE StoreOnce backup appliance to an HPE StoreEver tape library, the storage capacity is increased for the HPE StoreOnce appliance because the data that was duplicated from it can then be expired from the HPE StoreOnce appliance.

Target audience: This document is intended for presales consultants, solution architects, storage operators, and administrators who are designing, implementing, and maintaining application backups using HPE StoreOnce, HPE Cloud Bank Storage, HPE StoreEver tape storage, and Veritas NetBackup software. Readers of this Reference Configuration should have a functional understanding of data protection and backup concepts and technologies, as well as Hewlett Packard Enterprise’s secondary storage portfolio and Veritas NetBackup software.

Solution overview The new, next-generation HPE StoreOnce backup appliance provides a built-for-cloud data protection platform that can scale from small remote offices to the largest enterprises and service providers. HPE StoreOnce can help you reduce cost, risk, and complexity with flash-speed protection in your data center, as well as deliver low-cost archive and disaster recovery in the cloud.

HPE StoreOnce Catalyst Plug-in for Veritas NetBackup The HPE StoreOnce Catalyst Plug-in for Veritas Backup, enabled by the HPE StoreOnce Catalyst interface, is highly efficient in allowing NetBackup-managed movement of deduplicated data from one HPE StoreOnce appliance to another. The HPE StoreOnce Catalyst interface offers multiple advantages for backup to disk compared to traditional NAS and virtual tape interfaces. HPE StoreOnce Catalyst software was developed to dramatically improve the performance, function, and integration of backup applications such as Veritas NetBackup. HPE StoreOnce Catalyst delivers deduplication on an appliance server, media server, or dedicated appliance. Because it uses the same deduplication algorithm globally, data can be moved between platforms without rehydration. HPE StoreOnce Catalyst allows better utilization of advanced, disk-based storage solutions while increasing efficiency and performance.

Reference Configuration Page 4

HPE StoreOnce Catalyst Plug-in for Veritas NetBackup offers:

• Better performance: Achieve significantly enhanced performance by writing to HPE StoreOnce Catalyst compared to traditional disk backup targets. This is accomplished by distributing deduplication processing between NetBackup media servers and the HPE StoreOnce appliance.

• Simplified management: Control data movement centrally with Veritas NetBackup, which allows single console management.

• Greater flexibility: Move data from one site to multiple sites and enable replication across low-bandwidth networks with the bandwidth-reducing HPE StoreOnce deduplication.

HPE StoreOnce systems have moved to an all-inclusive licensing structure. HPE StoreOnce Catalyst and replication are included with the product at no additional charge (an encryption license is available at a nominal charge).

For more details about the HPE StoreOnce Catalyst Plug-in for Veritas NetBackup and to download the Plug-in (HPE Passport user ID and password credentials required), see https://h20392.www2.hpe.com/portal/swdepot/displayProductInfo.do?productNumber=StoreOnceForVERITAS.

Figure 1 shows how the HPE StoreOnce Catalyst Plug-in and Veritas NetBackup are used to deliver complete data protection from remote offices and branch offices (ROBO) to enterprise data centers.

Figure 1. Delivering complete protection from remote office to enterprise data centers using HPE StoreOnce Catalyst Plug-in and Veritas NetBackup

Reference Configuration Page 5

An overview of the HPE StoreOnce concepts discussed throughout this Reference Configuration can be found in Appendix A: HPE StoreOnce concepts.

The following will be demonstrated in this Reference Configuration:

• Overview of the Veritas NetBackup OST features compatible with the HPE StoreOnce Catalyst Plug-in

• Improved backup storage efficiency with HPE StoreOnce appliances

• Using HPE Cloud Bank Storage to cloud-enable your storage, backup, and applications

• Copying data to HPE StoreEver tape storage for cost-effective, long-term retention/compliance

Solution components The HPE Storage Solutions team validated the data protection solution in a lab environment. This section provides details on the hardware, software, and applications used to create this Reference Configuration, while Figure 2 illustrates the solutions lab environment.

Hardware HPE 3PAR StoreServ 9450 storage HPE 3PAR OS version 3.3.1 (MU2) was installed on the HPE 3PAR StoreServ 9450 storage, which had 42 TB of raw storage capacity, and was connected to a 16 Gb Fibre Channel (FC) backend fabric. Storage from the HPE 3PAR StoreServ 9450 storage was exported to the Veritas NetBackup master/media server to use as primary storage for datasets.

HPE StoreOnce 5250 system For this Reference Configuration, two HPE StoreOnce appliances were used. One HPE StoreOnce appliance was connected only to the primary NetBackup domain and functioned as the primary backup target, and was also connected to Microsoft Azure Blob storage using HPE Cloud Bank Storage. The other HPE StoreOnce appliance was initially connected to the primary NetBackup domain as the remote duplication target, but was later connected to the second NetBackup domain only and used to connect to the HPE Cloud Bank Storage from the primary NetBackup domain to seed that data in the second NetBackup domain. Both HPE StoreOnce 5250 systems used firmware version 4.1, and had 52 TB of raw capacity. Both HPE StoreOnce appliances were connected to a 10GbE network for transferring data and a 1GbE network for management. licenses were installed for encryption, HPE Cloud Bank Storage detach capacity, HPE Cloud Bank Read/Write capacity, Fibre Channel optional hardware (which covers the 16Gb Fibre Channel card), and Network Interface optional hardware (which covers the 10/25GbE card).

HPE StoreEver MSL6480 Tape Library The HPE StoreEver MSL6480 Tape Library had firmware version 5.60 installed, and the LTO-8 Ultrium 30750 tape drive had firmware version J4DB. The HPE StoreEver MSL6480 Tape Library was connected to a 16 Gb FC backend fabric. The HPE StoreEver MSL6480 Tape Library was used to duplicate data from the primary HPE StoreOnce appliance, so that the data on the primary HPE StoreOnce appliance could then be expired.

HPE ProLiant DL380 Gen 10 server The HPE ProLiant DL380 Gen10 server that was used for testing had 256 GB of physical memory, 32-cores (Intel® Xeon® CPU E5-2698 v3 @ 2.30 GHz) and Windows Server® 2016 installed. This server was the Veritas NetBackup master/media server.

Network The local management network was configured to 1GbE. The local data network was configured to 10GbE. The primary storage was configured via 16 Gb FC storage area network (SAN). The internet connection to the Cloud Service Provider was configured to less than 1GbE.

Reference Configuration Page 6

Software Veritas NetBackup 8.1 Veritas Technologies is the leader in the global enterprise data protection and software-defined storage market, with Veritas NetBackup being a leading product in this space. Veritas and Hewlett Packard Enterprise share the common goal of simplifying IT operations with cost-effective solutions that generate measurable value. The tight integration across joint solutions includes ongoing collaboration and testing to ensure quality now and in the future. The joint enterprise solutions are multiplatform (physical and virtual) and multicloud (works with Amazon Web Services [AWS] and Microsoft Azure) to provide integrated data protection across your hybrid IT infrastructure.

HPE Common Test Automation Framework HPE Common Test Automation Framework (CTAF) is the Perl-based testing tool used to generate, modify, and verify the test datasets used in solution testing for this Reference Configuration.

Application Microsoft Azure Blob storage Microsoft Azure Blob storage enables administrators to store all of their unstructured data within the cloud. Data can be scaled up or down as the need for storing data changes. Microsoft Azure Blob storage account options consist of hot, cool, and archive storage tiers that can be selected based on how often the data in the cloud is accessed and what type of data is being stored, backed up, or retrieved.

Figure 2. Solution lab environment

Figure 2 highlights the communication paths between solution components.

Reference Configuration Page 7

Best practices and configuration guidance Overview of the Veritas NetBackup OST features compatible with the HPE StoreOnce Catalyst Plug-in OpenStorage is a Veritas application programming interface (API) that allows NetBackup to communicate with storage that conforms to the API. Hewlett Packard Enterprise’s storage implementation controls the storage format, where the images reside on the storage, and the data transfer method. Consequently, performance and storage utilization are highly optimized. With the HPE StoreOnce Catalyst Plug-in for NetBackup OST, OpenStorage provides the following capabilities:

• Share disks: Multiple heterogeneous media servers can access the same disk volume concurrently.

• Balance load and performance: NetBackup balances backup jobs and storage usage among the media servers and disk pools. For each backup job, NetBackup chooses the least full disk volume and least busy media server.

• Use of disk appliance capabilities, which may include optimized off-host duplication and deduplicated storage capabilities.

• Fast storage provisioning.

• Almost unlimited storage.

• An alternative to off-site vaulting.

• Simplified disaster recovery: Access your data from anywhere over the internet.

The following Veritas NetBackup OST features are compatible with HPE StoreOnce Catalyst Plug-in:

• Whole image optimized duplication

• Auto Image Replication and Targeted Auto Image Replication

• Accelerator

• Granular Recovery Technology (GRT)

• Instant recovery for VMware

Details for setting up the HPE StoreOnce Catalyst Plug-in to be used with Veritas NetBackup OST features can be found in the HPE StoreOnce Catalyst Plug-in for Veritas NetBackup User Guide. To download the user guide, along with the plug-in (HPE Passport user ID and password credentials required), see https://h20392.www2.hpe.com/portal/swdepot/displayProductInfo.do?productNumber=StoreOnceForVERITAS.

Veritas NetBackup OST whole image optimized duplication Whole image optimized duplication uses a storage unit’s maximum fragment size for the data chunk size. Veritas refers to this type of operation as whole image optimized duplication because an entire NetBackup image fragment is transferred. For the remainder of this Reference Configuration, whole image optimized duplication will be specified as optimized duplication. With optimized duplication, backup images on a storage server can be replicated from one HPE StoreOnce appliance to another HPE StoreOnce appliance that reside within the same NetBackup domain. The ability to duplicate backups to storage in other locations, often across various geographical sites, helps facilitate data protection and disaster recovery. Optimized duplication transfers deduped and compressed data between HPE StoreOnce appliances with no additional steps required for the media server other than monitoring the job.

Reference Configuration Page 8

Because larger chunks of data are transferred, fewer copy management requests occur and performance improves. Also, the storage device controls progress reporting. The storage device may report progress when system load is low, rather than consume the resources that are better used for duplication. Or, the storage device may report progress at short intervals, updating the NetBackup user as frequently as NetBackup would for extent-based optimized duplication.

Figure 3 displays a storage unit’s Maximum fragment size.

Figure 3. "Maximum fragment size" used with optimized duplication

Optimized duplication is configured using a Storage Lifecycle Policy (SLP) in NetBackup. Operations are added to the SLP that determine how the data is stored, copied, replicated, and retained. The SLP that was created, manages both the backup job and the duplication job. For the backup destination, a storage unit built from the on premise or primary HPE StoreOnce appliance was the target for the backups. For the duplication destination, a storage unit created from another HPE StoreOnce appliance (remote or secondary) was selected. Then, the backup policy was configured to use the SLP.

Reference Configuration Page 9

Figure 4 presents the Storage Lifecycle Policy screen where the Backup and Duplication operations are defined.

Note The minimum HPE StoreOnce software version required for optimized duplication is 3.16.x.

Figure 4. "Storage Lifecycle Policy" screen showing "Backup" and "Duplication" settings

Figure 5 shows a backup policy with the Policy storage configured to use the previously created SLP.

Figure 5. Backup policy showing "Policy storage" settings using an SLP

Reference Configuration Page 10

An example bpdm log shows whole image optimized duplication being invoked and successfully copied.

For additional information on optimized duplication, see the NetBackup OpenStorage Solutions Guide for Disk from the NetBackup documentation 8.1.2 landing page at https://www.veritas.com/support/en_US/article.100044086.

Auto Image Replication and Targeted Auto Image Replication The backups that are generated in one NetBackup domain can be replicated to storage in one or more target NetBackup domains. The relationship between the originating domain and the target domain or domains is established by using the storage vendor's tools. The originating NetBackup domain has no knowledge of the storage server in the target domain or domains. When the appliances are configured properly, NetBackup images on the originating disk appliance are replicated automatically to the target disk appliance. NetBackup then imports those images.

This process is referred to as Auto Image Replication. The ability to replicate backups to storage in other NetBackup domains, often across various geographical sites, helps facilitate the following disaster recovery needs:

• A single production data center can back up to a disaster recovery site.

• A single production data center can back up to multiple disaster recovery sites.

• Remote offices in multiple domains can back up to a storage device in a single domain.

• Remote data centers in multiple domains can back up multiple disaster recovery sites.

Auto Image Replication between HPE StoreOnce appliances requires using tpman (topology manager), a Hewlett Packard Enterprise proprietary tool, to create replication topologies between a source and a target storage unit. The HPE StoreOnce Catalyst Plug-in uses this information to initiate automatic replication of data between HPE StoreOnce appliances.

Auto Image Replication can be configured as either:

• Untargeted: NetBackup replicates the data to all defined target storage servers. You cannot select a specific host or hosts as a replication target.

• Targeted: You can select a subset of your trusted NetBackup domains as a target for replication. NetBackup then replicates to the specified domains only rather than to all configured replication targets.

Configuring replication topologies

Tpman is a command line tool, and it provides the ability to add, remove, and show replication topologies between NetBackup storage units. Tpman is installed with the HPE StoreOnce Catalyst Plug-in in the following locations:

• Windows®: C:\Program Files\HPE\StoreOnce\isvsupport\OST\bin\tpman.exe

• Linux®, HP-UX, AIX, and Solaris: /usr/openv/hpe/ost/bin/tpman

For detailed steps in configuring replication topologies, see the Setting up Auto Image Replication (A.I.R.) with NetBackup section of the HPE StoreOnce Catalyst Plug-in 4.2.0 for Veritas NetBackup User Guide. The user guide should be selected for download when obtaining the HPE StoreOnce Catalyst Plug-in software at https://h20392.www2.hpe.com/portal/swdepot/displayProductInfo.do?productNumber=StoreOnceForVERITAS.

13:20:47.236 [5500.5968] <4> optdup_start_job_data_timer: begin throughput timer

13:20:47.236 [5500.5968] <4> copy_whole_image: begin copying backup id ses-host7_1547668910 (duplicate-optimized), copy 1, fragment 1

13:21:27.579 [5500.5968] <4> copy_whole_image: successfully copied (duplicate-optimized) backup id ses-host7_1547668910, copy 1, fragment 1, 104862968 Kbytes at 2598254.863 Kbytes/sec

13:21:27.579 [5500.5968] <4> optdup_stop_job_data_timer: end throughput timer (104862968 40359 2598254)

Reference Configuration Page 11

Adding replication topologies

Figure 6 exhibits an example tpman command structure for adding a replication topology between the source HPE StoreOnce appliance and target HPE StoreOnce appliance.

Figure 6. "tpman" example showing the replication topology setup between the source and target logical storage units

The following is an explanation of the command options used:

• <sts> is the NetBackup storage server address (IPv4, IPv6, Catalyst over Fibre Channel identifier, or fully qualified domain name [FQDN]). For the OpenStorage solutions that use a disk appliance for backups, the disk appliance is the storage server. For this example, the IP address of the source (10.0.0.32) and target (10.0.0.40) HPE StoreOnce appliances were used because those IP addresses were also applied to add each HPE StoreOnce appliance to NetBackup as storage servers.

• <lsu> is the NetBackup storage unit associated with the storage server. A storage unit is a label that NetBackup associates with physical storage. For this example, the storage units that were created for the source (COE-PRIMARY) and target (COE-SECONDARY) HPE StoreOnce appliances were utilized. COE-PRIMARY and COE-SECONDARY are Catalyst stores that were established on separate HPE StoreOnce appliances.

• <client_identifier> is the client that was given access to the HPE StoreOnce Catalyst store. Tpman will prompt for the password when the command is executed. For this example, the client gzw12a.ebs.net had been given full access to the Catalyst stores.

Note The Catalyst over Fibre Channel identifier can be found in the HPE StoreOnce Appliance GUI, with software version 4.1.x installed, under StoreOnce Settings Catalyst Settings Fibre Channel in the navigation tree. The NetBackup storage unit, which is the HPE StoreOnce Catalyst store name, can be found in the HPE StoreOnce Appliance GUI under StoreOnce System Dashboard Catalyst Stores. The client that was given access to the Catalyst store can be located in the HPE StoreOnce Appliance GUI under StoreOnce System Dashboard Catalyst Stores. Select the Catalyst store followed by the Permissions tab for that Catalyst store.

For additional information on Auto Image Replication and Targeted Auto Image Replication, see the NetBackup Deduplication Guide from the NetBackup documentation 8.1.2 landing page at https://www.veritas.com/support/en_US/article.100044086.

Granular Recovery Technology NetBackup Granular Recovery Technology (GRT) leverages Network File System (NFS) to read individual objects from a database backup image or a virtual machine (VM) snapshot backup. Specifically, the NetBackup client uses NFS to extract data from the backup image on the NetBackup media server. The NetBackup client uses “Client for NFS” to mount and access a mapped drive that is connected to the NetBackup media server. The NetBackup media server handles the I/O requests from the client through the NetBackup File System Service (NBFSD). NBFSD runs on the media server, and it mounts the backup image as a file system folder on the NetBackup client over a secure connection.

# tpman --add --source <sts>/<lsu> --target <sts>/<lsu> [--client <client_identifier>]

Reference Configuration Page 12

NetBackup uses GRT and NFS to recover the individual objects that reside within a backup image, such as:

• A user account from an Active Directory database backup

• Email messages or folders from an Exchange database backup

• A document from a SharePoint database backup

• An individual file from a VM snapshot backup

To restore individual items from a backup that uses GRT, you must enable services for Network File System. To enable services for Network File System on a Windows Server 2012, 2012 R2, or 2016 media server, see the Install Network File System on the server with Server Manager section of the Microsoft® Deploy Network File System article at: https://docs.microsoft.com/en-us/windows-server/storage/nfs/deploy-nfs.

After NFS has been successfully installed, create a backup policy in NetBackup with the Enable granular recovery option selected. Figure 7 displays the option under the Attributes tab.

Figure 7. "Enable granular recovery" option

Individual file recovery for VMs is supported from full backups and from incremental backups, as long as the Enable file recovery from VM backup option is enabled for the backup policy. The option is automatically checked when creating a new VMware® backup policy whether the Backup Policy Configuration Wizard is used or the policy is manually created.

Reference Configuration Page 13

Figure 8 demonstrates the Enable file recovery from VM backup option under the VMware tab in the backup policy properties.

Figure 8. "Enable file recovery from VM backup" option

For additional information on Granular Recovery Technology, see the NetBackup Administrator’s Guide, Volume I from the NetBackup Documentation 8.1.2 landing page at https://www.veritas.com/support/en_US/article.100044086.

Reference Configuration Page 14

Accelerator Accelerator is a NetBackup feature which performs a full backup at the speed of an incremental backup. Accelerator leverages change tracking of data on the client, and sends only the changed blocks to the storage server. Therefore, full backups can be synthesized on the disk on the fly with NetBackup by cloning the disk resident portion of the data (copied from previous backups) and the modified data sent to the storage server. The result is a full backup created on the storage server by sending the changed data only. HPE StoreOnce deduplication works at a much finer level of data management (chunking, hashing, and matching) and complements the bandwidth savings of NetBackup Accelerator. The HPE StoreOnce Catalyst OST Plug-in implements support for cloning disk resident data extents to help NetBackup perform an Accelerator backup on HPE StoreOnce appliances.

The section Setting up NetBackup Accelerator with HPE StoreOnce Catalyst in the HPE StoreOnce Catalyst Plug-in 4.2.0 for Veritas NetBackup User Guide includes detailed steps and recommendations for the following:

• Verifying the Accelerator configuration

• Enabling NetBackup Accelerator for file systems

• Enabling NetBackup Accelerator for VMware

• Restoring VMware accelerated backups

The HPE StoreOnce Catalyst Plug-in 4.2.0 for Veritas NetBackup User Guide should be selected for download when obtaining the HPE StoreOnce Catalyst Plug-in software at https://h20392.www2.hpe.com/portal/swdepot/displayProductInfo.do?productNumber=StoreOnceForVERITAS.

Instant recovery for VMware NetBackup can recover a VM almost instantly, without waiting to transfer the VM's data from the backup. NetBackup starts the VM directly from the backup image and makes it accessible to users on the target VMware ESXi™ (ESXi) host immediately. Files (including virtual machine disk [VMDK] files) can then be copied without restoring the entire VM.

Some example uses for instant recovery:

• Access and restore individual files and folders from any type of OS and then delete the VM.

• Test a patch on a restored VM before you apply the patch to production systems.

• Troubleshoot a VM or host, such as when the production ESXi host is down. You can start the VM from its backup and use it until the production system is back online.

• Permanently recover the VM by means of VMware vSphere® Storage vMotion® (vSphere Storage vMotion).

• Verify the backup image.

• Copy a VMDK file and then delete the VM.

• Verify an application.

Reference Configuration Page 15

By using the Enable file recovery from VM backup option (see Figure 8), individual files can be selected for restore using the Backup, Archive and Restore interface, as seen in Figure 9, where a single file is selected for restore from a VMware backup.

Figure 9. Using the "Backup, Archive, and Restore" interface to restore a single file for a VM

The VM is started directly from the backup image residing on the HPE StoreOnce Catalyst store, and it is available in seconds or minutes. The startup time depends on the network speed and storage speed, not on the size of the VM.

The NetBackup CLI command nbrestorevm is used to access the VM from its backup image. The NBFSD on the media server accesses the backup image file system and mounts the image as an NFS datastore. The datastore becomes accessible to the ESXi host where the VM is to be restored.

To initiate Instant recovery for VMware, activate the VM with the following command (options without brackets are required):

# nbrestorevm -vmw -ir_activate -C vm_client -temp_location temp_location_for_writes

[-S master_server] [-vmpo] [-vmInstanceId] [-vmsn]

[-vmkeephv] [-vmserver vm_server] [-vmproxy vm_proxy]

[-s mm/dd/yyyy [HH:MM:SS]] [-e mm/dd/yyyy [HH:MM:SS]]

[-R absolute_path_to_rename_file]

[-disk_media_server media_server]

Reference Configuration Page 16

See Table 1 for an explanation of the command options.

Note Only -vmw, -ir_activate, -C, and -temp_location are required. If the other options are not specified, NetBackup automatically supplies values for those options from the backup. In most cases, if you do not restore the VM to a different location, you can omit the bracketed options.

Table 1. Options on the "nbrestorevm" command for Instant recovery for VMware

Option Description

HPE StoreOnce concepts

nbrestorevm Command to initiate Instant recovery for VMware.

-vmw Indicates the type of virtual machine to restore (VMware).

-C virtual_machine The name of the virtual machine as identified in the backup. For example, if the policy backed up the virtual machine by its host name, specify that host name.

Note: If a virtual machine with the same name already exists on the target ESXi host, the command fails. You can change the display name of the virtual machine in VMware vCenter (vCenter). As an alternative, use the -R option on nbrestorevm to change the display name or location of the restored virtual machine.

-ir_activate Starts the restore by mounting the backup image of the virtual machine as an NFS datastore. The datastore becomes accessible to the ESXi host where the virtual machine is to be restored.

-temp_location temporary_datastore A temporary datastore on the ESXi server where all writes occur until the virtual machine is restored. All writes occur on this datastore until vSphere Storage vMotion is complete or until you are finished with the virtual machine (such as for troubleshooting).

Note: This datastore must exist before you run nbrestorevm.

-vmpo Turns on the virtual machine after the restore.

An example nbrestorevm command:

This command starts the restore by mounting the backup image of the VM host vm001 as an NFS store. The temporary location temp_loc5 is a temporary datastore on the ESXi server where all writes occur.

For additional information on Instant recovery for VMware, see the NetBackup for VMware Administrator’s Guide from the NetBackup documentation 8.1.2 landing page at https://www.veritas.com/support/en_US/article.100044086.

Improved backup storage efficiency with HPE StoreOnce appliances HPE StoreOnce appliances are capable of delivering huge space savings from high efficiency deduplication and compression so that more data can be stored in a smaller footprint. Hence, less storage capacity needs to be purchased. Depending on the data being protected and the backup schedule, space savings of up to 20X can be achieved.

Backups and restores are also faster compared to traditional disk backups because:

• Performance is enhanced by deduplicating anywhere—at the application source, or at the backup server, or at the target HPE StoreOnce appliance.

• It allows distributing deduplication processing between NetBackup media servers and the HPE StoreOnce appliance.

# nbrestorevm –vmw –ir_activate –C vm001 –temp_location temp_loc5 -vmpo

Reference Configuration Page 17

The storage capacity savings achieved by HPE StoreOnce deduplication technologies was apparent after running the first backup. To provide tangible evidence of the improvement that deduplication has on storage capacity efficiency, a test was conducted as follows:

• A weekly backup schedule was simulated by running seven backups of a dataset to an HPE StoreOnce appliance. The initial backup was a full backup, and the subsequent six backups were differentials—only the changed blocks were backed up.

• The size of the dataset being protected was approximately 200 GB with an initial compression ratio of 2:1.

• The dataset contained 6600 files and 332 folders total.

• Five percent of the data was changed between each backup (also known as “simulated daily change rate”).

Figure 10 summarizes the storage capacity savings. The user data stored is the amount of data that was backed up before deduplication or compression. The size on disk is the capacity utilization of the backup target after deduplication and compression. The size on disk with an HPE StoreOnce Catalyst target and the size on disk with a disk-based target using NetBackup deduplication are compared to the user data stored.

Figure 10. Summary of storage capacity savings using an HPE StoreOnce appliance after a week of backups

For backups completed to the HPE StoreOnce appliance, the amount of data stored was 203 GB when the actual user data was 260.5 GB. This represents a 22% capacity savings compared to the basic disk storage unit using NetBackup deduplication, where the amount of data stored was 216 GB (user data was still 260.5 GB) for a 17% capacity savings.

The overall capacity savings from using the HPE StoreOnce appliance for backups was 6% compared to using NetBackup dedupe.

Reference Configuration Page 18

Using HPE Cloud Bank Storage to cloud-enable your storage, backup, and applications When using cloud-based protection, the cost of transferring data and the associated data storage are primary considerations. When using HPE Cloud Bank Storage with NetBackup, HPE StoreOnce deduplication minimizes the total volume of transmitted data, as well as the storage footprint. Subsequent backups to the cloud are much smaller and faster because only unique data is transmitted. Conversely, when restoring from HPE Cloud Bank Storage, only the deduplicated data that is not in the local Catalyst store will be restored from the cloud.

A few HPE Cloud Bank Storage use cases are as follows:

• Copy data management allows for a backup of a database to be restored from the cloud to another site or sandbox environment

• Long-term retention and archive of backups

• Off-site copies of backups for disaster recovery (secondary appliance)

• Detached HPE Cloud Bank stores for very long-term backup data retention

Best practices and configuration guidance for HPE Cloud Bank Storage, including configuring HPE Cloud Bank stores for Microsoft Azure Blob storage, is provided in the HPE Reference Configuration for HPE Cloud Bank Storage with Microsoft Azure.

For detailed information regarding protecting HPE ProLiant for Microsoft Azure Stack using Veritas NetBackup with HPE storage, see the HPE Reference Architecture for HPE ProLiant for Microsoft Azure Stack data protection with Veritas NetBackup, HPE StoreOnce, and HPE Cloud Bank Storage.

To learn more about HPE Cloud Bank Storage with Scality RING, see the HPE Reference Configuration for HPE Cloud Bank Storage with S3 Connector and Scality.

HPE Cloud Bank Storage and Veritas NetBackup integration HPE StoreOnce systems version 3.18 or newer adds the functionality of HPE Cloud Bank Storage. NetBackup can leverage this functionality to use external object storage when sending, storing, and retrieving public or private cloud storage data. This is achieved with NetBackup by using an HPE Cloud Bank store as an optimized duplication target.

Note Direct backups to an HPE Cloud Bank store are not supported. Backups are written to an HPE StoreOnce Catalyst store and then copied to an HPE Cloud Bank store.

A summary of the steps required for configuring NetBackup to use HPE Cloud Bank Storage are as follows:

1. Create an HPE Cloud Bank store from the primary HPE StoreOnce appliance or from a remote HPE StoreOnce appliance.

2. Use the NetBackup Storage Server Configuration Wizard to create a disk storage server for the primary HPE StoreOnce appliance and for the secondary HPE StoreOnce appliance.

3. Create a new Storage Lifecycle Policy (SLP) that uses a standard HPE StoreOnce Catalyst store as the target for backup jobs and the HPE Cloud Bank store as the target for duplication jobs.

4. Create a new policy, and select the newly created SLP for the storage policy.

Reference Configuration Page 19

Figure 11 shows the disk pools that were set up from the Catalyst store and the HPE Cloud Bank store. The 10GbE IP address for the primary HPE StoreOnce appliance was used to create the Storage server, then a disk pool was generated for the Catalyst store (COE-primary) and the HPE Cloud Bank store (CloudBank).

Figure 11. Properties for disk pools created from the Catalyst store and HPE Cloud Bank store

Reference Configuration Page 20

Figure 12 highlights the storage units that were created from the Catalyst store (COE-primary-stu) and the HPE Cloud Bank store (CloudBank-stu) using the primary HPE StoreOnce appliance. Both storage units were configured with a Disk type of OpenStorage (hp-StoreOnceCatalyst).

Figure 12. Properties for the storage units that were created from the Catalyst store and HPE Cloud Bank store

Reference Configuration Page 21

Figure 13 displays the Storage Lifecycle Policy that was created using the storage units that were developed from the Catalyst store and HPE Cloud Bank store. The storage unit from the Catalyst store (COE-primary-stu) was configured for backup operations, and the storage unit from the HPE Cloud Bank store (CloudBank-stu) was configured for duplication operations.

Figure 13. Properties for the SLP that was created to use the Catalyst store "Backup" and HPE Cloud Bank store "Duplication"

Figure 14 exhibits a backup policy created to use the newly established CloudBank SLP.

Figure 14. Attributes for the backup policy with the "CloudBank" SLP selected for the "Policy storage"

Reference Configuration Page 22

Using the settings described, the policy will backup the selected data to the Catalyst store on the primary HPE StoreOnce appliance. After the backup job successfully completes, a duplication job will automatically start. This will result in the backup image in the Catalyst store being copied to the HPE Cloud Bank store (also on the primary HPE StoreOnce appliance).

Direct Restore A Direct Restore is a restore read from the HPE Cloud Bank store, where all of the data to be restored is read directly from Microsoft Azure before being written to the restore location, even if some of the data is duplicated. A Direct Restore is a restore operation that reads from the HPE Cloud Bank store, and it is then written directly to the restore location. The result is higher costs from the increased reads that occur during rehydration in the cloud, and it is generally the most expensive and least efficient restore method from HPE Cloud Bank Storage. In a scenario where an administrator is only recovering a small amount of data from a backup, it may be more cost-effective to read that amount of data directly from Microsoft Azure rather than performing an Optimized Restore from HPE Cloud Bank Storage. See the Optimized Restore section of this Reference Configuration for more information.

For this example, a data folder on the NetBackup master/media server had been deleted, and the original copies of the backup images on the Catalyst store from the primary HPE StoreOnce appliance had expired. Copies of the backup images had been duplicated to the HPE Cloud Bank store and were available due to having longer retention periods. When the primary backup images expired, the duplicate copies were automatically promoted to primary copies that could be used for restoring data. Backup images can be viewed using the NetBackup catalog.

Figure 15 illustrates all of the available search options that were used to view the backup images. The drop-down for Copies was changed to Copy 2, and the results show available backup images for the policy CloudBank. The Copy Number for all of the backup images listed is 2, and all of the backup images indicate Yes under Primary Copy.

Figure 15. Modifying the NetBackup "Catalog" search options to view the backup images in the HPE Cloud Bank store

Reference Configuration Page 23

To restore the folder using the HPE Cloud Bank store, Backup, Archive, and Restore was selected from the left navigation tree. Then, the Restore Files tab was chosen, as seen in Figure 16.

Figure 16. Modifying the restore options

Selecting Restore… opened another window where the restore destination and options related to restoring the files could be changed. Clicking Start Restore initiated the transfer of data from the HPE Cloud Bank store to the desired restore destination. After the restore operation completed, the details for the operation showed that copy 2 of the backup image was successfully restored (see Figure 17).

Figure 17. "Status of restore from copy 2" was successfully completed

Reference Configuration Page 24

Figure 18 shows that the folder (backup2) restored from a backup image in the HPE Cloud Bank store had a newer date than the other backup folder that did not require recovering.

Figure 18. View of the datasets after the restore is completed

Optimized Restore An Optimized Restore is a two-step process. The first step is an optimized duplication from the HPE Cloud Bank store to a local Catalyst store. 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. Rehydration of data occurs in the second step, reducing the amount of data read from Microsoft Azure, resulting in lower costs. Additionally, if a restore is interrupted for any reason, data would not have to be retrieved from Microsoft Azure for the second time.

For this example, the original Catalyst store was inaccessible. A new Catalyst store was set up from the primary HPE StoreOnce appliance. Since the storage server had previously been established, only a new Disk pool (COE-OptimizedRestore) and Storage unit (COE-OptimizedRestore-stu) were generated for the new Catalyst store. It is also possible to use a different HPE StoreOnce system or an HPE StoreOnce Virtual Storage Appliance (VSA) to perform an Optimized Restore. Next, the NetBackup Catalog was used to duplicate a backup image stored in the HPE Cloud Bank store to the newly created Catalyst store. The same backup image from the Direct Restore (see Figure 15) was used again for the Optimized Restore.

Figure 19 shows the NetBackup Catalog and the variables that were used for the duplication operation.

Figure 19. Selecting the "Storage unit" for the new Catalyst store to duplicate the backup image from the HPE Cloud Bank store

Reference Configuration Page 25

After the backup image from the HPE Cloud Bank store was duplicated to the new Catalyst store from the primary HPE StoreOnce appliance, that backup image (Copy 3) could be restored from the Catalyst store to the restore destination. Modify the restore options within the Backup, Archive, and Restore window, as depicted in Figure 16.

Figure 20 shows that copy 3 was successfully restored.

Figure 20. "Status of restore from copy 3" was successfully completed

Figure 21 displays the restored folder (backup2) which has a newer date than the previously restored folder (see Figure 18).

Figure 21. The restored folder with a newer date

Multi-Reader HPE Cloud Bank Storage Multi-Reader functionality grants the ability to read from a single Microsoft Azure Blob storage container, 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 read-only mode.

Reference Configuration Page 26

HPE Cloud Bank Storage Multi-Reader functionality addresses several potential use cases:

• Copy data management allows for a backup of a database to be restored from the cloud to another site or sandbox environment

• Streamlined data archiving while minimizing impact to a production environment

• Mining backup data for analysis without impacting production backup and restore processes

• Restore or restore testing outside of a production environment

• Disaster recovery testing outside of a production environment

• Seeding a new site with an entirely separate SAN environment

When more than one HPE StoreOnce system is connected to the object store, the first HPE StoreOnce system can be set for read-write access. Access for additional systems is limited to read-only. The HPE Cloud Bank Storage licensed capacity for each HPE StoreOnce system must be equal to or greater than the physical capacity of the data held in the HPE Cloud Bank Storage. If the capacity of the HPE Cloud Bank store exceeds the licensed capacity, a warning is issued. An HPE StoreOnce system grants a seven-day grace period to allow an administrator to apply the required HPE Cloud Bank Storage license. After that time, the HPE Cloud Bank Storage Multi-Reader feature is disabled until the appropriate HPE Cloud Bank Storage license is applied.

For this example, a second NetBackup domain existed and there was a need to copy data from the HPE Cloud Bank store in the primary NetBackup domain to an HPE StoreOnce appliance in the second domain. This was completed by:

1. Connecting an HPE StoreOnce appliance in the second NetBackup domain to the HPE Cloud Bank store from the primary NetBackup domain (as read-only)

2. Creating a storage server, disk pool, and storage unit from the new HPE Cloud Bank store on the NetBackup master/media server in the second domain

3. Importing the backup image metadata from the read-only HPE Cloud Bank store to populate the second NetBackup master/media server’s catalog

4. Creating a Catalyst store on the HPE StoreOnce appliance in the second NetBackup domain

5. Creating a storage server, disk pool, and storage unit from the new Catalyst store on the NetBackup master/media server in the second domain

6. Performing an Optimized Restore to duplicate the imported images to the new Catalyst store then restoring the data to the NetBackup server in the second domain. See the Optimized Restore section of this Reference Configuration for more information.

To connect the remote HPE StoreOnce appliance in the second NetBackup domain to the HPE Cloud Bank store in the primary NetBackup domain, the Connect to Store option was selected in the HPE StoreOnce Management Console: System Dashboard Cloud Bank Stores Actions (represented by three dots in the upper right corner) Connect to Store (see Figure 22).

Figure 22. Selecting to connect to an HPE Cloud Bank store in the HPE StoreOnce Management Console

Reference Configuration Page 27

Next, select the Service Provider then enter the Storage Account Name, the HPE Cloud Bank store Access Key, and the Container Name. Figure 23 exhibits the settings for connecting to Microsoft Azure Blob storage.

Figure 23. Settings to connect to an existing HPE Cloud Bank store

A confirmation of the HPE Cloud Bank store settings was displayed with the option to connect to the HPE Cloud Bank store as read-only, as seen in Figure 24.

Figure 24. Connecting to an existing HPE Cloud Bank store as read-only

Reference Configuration Page 28

Figure 25 presents the HPE Cloud Bank store connected as Read Only on the HPE StoreOnce appliance that was connected to the second NetBackup domain.

Figure 25. HPE Cloud Bank store successfully connected as "Read Only"

Figure 26 depicts the details for the same HPE Cloud Bank store from the HPE StoreOnce appliance in the primary NetBackup domain.

Figure 26. Details for the same HPE Cloud Bank store from the HPE StoreOnce appliance in the primary NetBackup domain

Now that the HPE StoreOnce appliance for the second NetBackup domain had been connected to the HPE Cloud Bank store, the backup images in the HPE Cloud Bank store had to be imported into the second NetBackup domain. This required creating a storage server, disk pool, and storage unit for the read-only HPE Cloud Bank store. Next, the NetBackup Catalog was used to import the backup images by selecting NetBackup Management Catalog then choosing Actions Initiate Import…, as shown in Figure 27.

Figure 27. Using the NetBackup "Catalog" to initiate an import of the backup images

Reference Configuration Page 29

Figure 28 shows the selections made to import the backup images from the read-only HPE Cloud Bank store.

Figure 28. Options used to import the backup images

All of the imported backup images were then listed in the NetBackup Catalog, as demonstrated in Figure 29.

Figure 29. Backup images successfully imported to the second NetBackup domain from the HPE Cloud Bank store

Reference Configuration Page 30

After the backup images were successfully imported from the read-only HPE Cloud Bank store to the second NetBackup domain, the next step was to perform an Optimized Restore to duplicate those images to a Catalyst store on the HPE StoreOnce appliance in the second NetBackup domain then use the duplicated images to restore the data. See the Optimized Restore section of this Reference Configuration for more information.

After the duplication job successfully completed, the backup images could be restored by selecting Backup, Archive, and Restore from the NetBackup left navigation tree. In Figure 30, the Specify NetBackup Machines and Policy Type was modified so that the Destination client for restores was the NetBackup master/media server for the second domain. The other NetBackup master/media server was selected by default.

Figure 30. Specifying the storage unit created from the Catalyst store to have the imported backup images duplicated

Figure 31 shows the details for the restore job, specifically that data (E:\backup2) backed up from the primary NetBackup domain was successfully restored to the second NetBackup domain (C:\retores\backup2).

Figure 31. Folder "backup2" from the primary NetBackup domain was successfully restored to the second NetBackup domain

Reference Configuration Page 31

A summary of using the HPE Cloud Bank Storage Multi-Reader functionality that was completed without impacting the primary NetBackup domain:

• The NetBackup master/media server (ses-host7) from the primary domain created the backup images that were copied to the HPE Cloud Bank store when NetBackup was originally configured to use HPE Cloud Bank Storage.

• That the HPE Cloud Bank store was then connected to the NetBackup master/media server (ses-host10) in the second domain as read-only using an HPE StoreOnce appliance also in the second NetBackup domain.

• The backup images from the read-only HPE Cloud Bank store were imported into NetBackup.

• The data was then restored locally on the second NetBackup master/media server.

Detach If long-term storage is required, an administrator can choose to detach an HPE Cloud Bank store. Detaching an HPE Cloud Bank store removes it from the HPE StoreOnce Management Console and returns any HPE Cloud Bank capacity licenses to the HPE StoreOnce system for later use. A detached store can be reattached within 60 days after disconnection or moved to the archive tier of Microsoft Azure storage. Archive tier data is optimized to be the least expensive access tier for long-term data storage (see Microsoft Azure Blob storage). Once in an archived state, a cost based on the number of read operations is present when moving a Blob from archive tier access to a cool or hot tier access.

Note HPE Cloud Bank Detach is a licensed feature that requires HPE Cloud Bank capacity licenses. Detaching an HPE Cloud Bank store recycles HPE Cloud Bank capacity licenses for later use.

As shown in Table 2, three options are presented when removing an HPE Cloud Bank store: disconnect, detach, and delete.

Table 2. Disconnect, detach, and delete options for an HPE Cloud Bank store

Disconnect Detach Delete

Cloud data state after executing Read-write Read-only Unavailable

Removes objects from the cloud storage No No No

Removes store from the HPE StoreOnce appliance

Yes Yes Yes

Options after executing Connect (read-write) after 24 hours and up to 60 days after disconnect

Connect (read-only) within 60 days after disconnect

Connect (read-only) within 60 days after disconnect

No longer accessible

Copying data to HPE StoreEver tape storage for cost-effective, long-term retention/compliance Tape storage is a critical component for comprehensive data protection and archiving. Traditional tape storage continues to be in strong demand as a cost-effective, reliable, and secure storage method to protect and retain your data in the long term. For this Reference Configuration, backup images from the primary HPE StoreOnce appliance were duplicated to an HPE StoreEver MSL6480 tape library for long-term retention and compliance. Then, the backup images on the primary HPE StoreOnce appliance were expired to manage the storage capacity of the primary HPE StoreOnce appliance.

The latest HPE StoreEver Compatibility Matrix should be used whenever adding an HPE StoreEver tape library to your data protection solution. The HPE StoreEver Compatibility Matrix is a single point of reference for the latest HPE StoreEver tape storage product’s interoperability and device compatibility details. It contains tape device connectivity details including supported servers, operating systems, controllers, and infrastructure components, as well as Backup and Archival ISV partner compatibility. The matrix is a rolling support document with new products, firmware, and software support being added monthly. The HPE StoreEver Compatibility Matrix can be found at: https://h20272.www2.hpe.com/SPOCK/Pages/spock2Html.aspx?htmlFile=hw_storeever.html (HPE Passport account is required).

Reference Configuration Page 32

Considerations when using HPE StoreEver tape storage Although many factors contribute to the overall performance of tape storage, there are several factors that should be understood whenever adding an HPE StoreEver tape library to your data protection solution.

• Buffer Allocation: HPE StoreEver tape storage supports configurable buffer sizes with NetBackup, which can improve performance.

• File (Data) Compression Ratio: The amount of compression has a direct impact on the rate at which a tape drive can read/write data.

• Source Disk and File System: Consider the data source, local disk, RAID array storage, file system type, and volume type.

• Tape Drive: These are the various types of supported tape drives in HPE StoreEver tape storage.

Buffer allocation

Buffer sizes can be set to maximize the performance of tape drives. Two text files, SIZE_DATA_BUFFERS and NUMBER_DATA_BUFFERS, created in <install path>/netbackup/db/config/, are used to optimize the tape drive buffers. For documentation on modifying buffer sizes, search the Veritas support site for SIZE_DATA_BUFFERS or NUMBER_DATA_BUFFERS at https://www.veritas.com/support/en_US.html.

Note If either SIZE_DATA_BUFFERS or NUMBER_DATA_BUFFERS are modified, be sure that the new specifications are appropriate for all devices on that NetBackup media server or backup and restore jobs might fail.

File (Data) Compression Ratio

Not all data can be compressed equally, and the compression ratio affects the amount of data that can be stored on each tape cartridge, as well as the speed at which the tape drives can read or write the data. Incompressible data will back up slower than higher compressible data. For example, JPEG files are not very compressible, but database files can be highly compressible. The accepted standard for quoting tape backup specifications revolves around an arbitrary figure of 2:1 compressible data. Table 3 shows typical compression ratios of various applications.

Table 3. Typical file compression ratios

Data type Typical compression

CAD 3.8:1

Spreadsheet/word processing 2.5:1

Typical file/print server 2.0:1

Microsoft Exchange/SQL Server databases 1.4:1

Oracle/SAP® databases 1.2:1

Source Disk and File Systems

In the past, tape performance was typically identified as a bottleneck. However, tape performance has now surpassed many of the source systems available today. Items to consider when calculating desired throughput and performance metrics include:

• Source hardware (disk subsystems)

• Source file system status

• Server configuration

Reference Configuration Page 33

The following factors critically affect the speed of backup from disk to tape:

• Data file size: The larger the number of smaller files, the larger the overhead associated with backing them up. The worst-case scenario for backup is large numbers of small files due to system overhead of file accession.

• Disk array performance: It is often overlooked that data cannot be put onto tape any faster than it can be read from disk. Backup is more sequential in nature than random (from a disk array access perspective). Disk array performance depends on the number of disks, RAID configuration, the number of Fibre Channel ports accessing the array, and queue depth available, for example.

• Fragmentation: The more fragmented the files are on disk, the more random the disk access method will be. Hence, the backup will take longer. If the system has a defragmentation utility, it is advisable to run it before full backups or on a regularly scheduled basis to ensure that files are contiguously arranged on the disk.

Tape drive

HPE StoreEver tape drives have varying levels of performance. While factors such as data file size, directory depth, and data compressibility all affect the system performance, data interleaving—alternately writing multiple clients’ data to a single tape—during backup also affects the tape drive performance during a restore. Table 4 shows performance information for various HPE StoreEver tape drives.

Table 4. HPE StoreEver tape drive throughput speed (native)

Tape drive Native throughput MB/s

Ultrium 30750 (LTO-8 FH) 300

Ultrium 15750 (LTO-7 FH) 300

Ultrium 15000 (LTO-7 HH) 300

Ultrium 6650 (LTO-6 FH) 160

Ultrium 6250 (LTO-6 HH) 160

Ultrium 3280 (LTO-5 FH) 140

Ultrium 3000 (LTO-5 HH) 140

Duplicating data from a primary backup device to tape Retaining copies of your data for archival and long-term retention can be done more efficiently using HPE StoreEver tape storage. By using NetBackup to duplicate the data on an HPE StoreOnce appliance to an HPE StoreEver tape library, the storage capacity is increased for the HPE StoreOnce appliance, because the data that was duplicated from it can then be expired from the HPE StoreOnce appliance.

HPE StoreEver tape libraries address long-term storage needs with a scale-out architecture that can be upgraded quickly and without disruption to your data protection solution. Furthermore, the data stored in an HPE StoreEver tape library can be safeguarded, after export and when it is off-site, with several security encryption offerings. A 30-year shelf life1 for HPE StoreEver media makes it ideal for long-term retention and disaster recovery.

For this example, the following is a summary of steps executed:

1. The NetBackup Device Configuration Wizard was utilized to discover and then configure the HPE StoreEver MSL6480 tape library.

2. An inventory of the robot for the HPE StoreEver MSL6480 tape library was performed to detect the tape media.

3. All of the tape media were labelled for use with NetBackup.

4. The NetBackup Catalog was run to identify then duplicate the desired backup images to the HPE StoreEver MSL6480 tape library.

5. The NetBackup Catalog was used to expire the copies of the backup images on the HPE StoreOnce appliance.

6. The backup images were restored from the HPE StoreEver MSL6480 tape library to the NetBackup master server.

1 In normal ambient conditions.

Reference Configuration Page 34

To expand on the above summary, the NetBackup Device Configuration Wizard was launched by selecting the NetBackup Master Server from the left navigation tree then choosing Configure Storage Devices from the available options. This was the easiest option for adding and configuring the HPE StoreEver MSL6480 tape library. For more details regarding adding robots and tape drives in NetBackup, see the NetBackup Administrator’s Guide, Volume I from the NetBackup Documentation 8.1.2 landing page at https://www.veritas.com/support/en_US/article.100044086.

The media in the HPE StoreEver MSL6480 tape library had to be scanned, added to the inventory, and then labelled before being used for the duplication job.

The NetBackup Catalog was then used to view the backup images that could be duplicated from the HPE StoreOnce appliance to the HPE StoreEver MSL6480 tape library. Catalog was selected from the left navigation tree under NetBackup Management, then a search was performed for primary copies that could be duplicated. The desired backup images were selected, then Duplicate was chosen by right-clicking on the selected images. Figure 32 shows the selected backup images, of which both are primary copies. These backup images will be duplicated to a tape library.

Figure 32. Duplicating backup images to an HPE StoreEver MSL6480 tape library

Reference Configuration Page 35

Figure 33 represents the detailed outcome of the successful duplication job which resulted in copy 3 of the data being created. The destination storage unit (ses-host7-hcart2-tld-0) is the storage unit that was created from the HPE StoreEver MSL6480 tape library, and the backup images (ses-host7_1549918533 and ses-host7_1549918532) are being copied to a destination media ID (1910L8) for an HPE StoreEver Ultrium LTO-8 tape media. The source path (@aaaak) that the backup images are being duplicated from is the HPE StoreOnce appliance.

Figure 33. Duplicating backup images to an HPE StoreEver MSL6480 tape library

The backup images were then expired from the HPE StoreOnce appliance to increase the storage capacity of the HPE StoreOnce appliance. Using the NetBackup Catalog again, Primary Copy was selected from the Copies drop–down. Then, the primary copies that were duplicated to tape were right-clicked on so that Expire could be chosen—all of the backup images on the HPE StoreOnce appliance had media IDs starting with “@” (for example, @aaaak). After Expire was selected, the copies of the backup images that were on the HPE StoreOnce appliance were immediately removed from the NetBackup catalog. The same process was repeated for copy 2 of the backup images, which were the backup images that were copied from the primary HPE StoreOnce appliance to a remote HPE StoreOnce appliance. The only remaining copies of the backup images (copy 3) were on the HPE StoreEver MSL6480 tape library.

Compare Figure 32 with Figure 34, which shows that backup images ses-host7_1549918533 and ses-host7_1549918532 are still primary copies. Note, however, that the copy number is now 3 (it was 1), and the media ID is 1910L8 (it was @aaaak), which is from the HPE StoreEver Ultrium LTO-8 tape media in the HPE StoreEver MSL6480 tape library.

Figure 34. Backup images duplicated to tape are listed as the primary copies after expiring the backup images from the HPE StoreOnce appliances

When data was restored from the date that the backup images were duplicated to the HPE StoreEver MSL6480 tape library, the restore job displayed that the HPE StoreEver Ultrium LTO-8 tape media (1910L8) was required to complete the restore job, as seen in Figure 35.

Reference Configuration Page 36

Figure 35. HPE StoreEver Ultrium LTO-8 tape media required to restore data

The selected data was successfully restored from the HPE StoreEver MSL6480 tape library (copy 3) to the NetBackup master server, as shown in Figure 36.

Figure 36. Data that was copied to tape "copy 3" was successfully restored to the NetBackup master server

Summary To address limitations of current data protection technologies and provide greater protection, HPE StoreOnce appliances simplify data protection and can reduce cost, risk, and complexity with a cloud-ready data protection platform. HPE StoreOnce appliances are built for the cloud and do not need a separate gateway or virtual appliance. You will be able to seamlessly cloud-enable your backup and enterprise apps,

Reference Configuration Page 37

natively integrate your choice of cloud, and backup only unique data to the cloud for 20x lower cloud storage costs2, as well as store encrypted, self-describing backup data for simple cloud disaster recovery.

In addition, Veritas NetBackup’s data protection solution brings together a full generation of traditional and next-generation data protection from backup to disk, to replication management, to tape—under one platform. The HPE StoreOnce Catalyst OST Plug-in for Vertias NetBackup has a tight integration with Veritas NetBackup that achieves the following:

• Improved backup storage efficiency due to better deduplication with HPE StoreOnce systems.

• When using HPE Cloud Bank Storage with Veritas NetBackup, HPE StoreOnce deduplication reduces the storage footprint in the cloud and minimizes the total volume of transmitted data for both backups and restores.

• Cost-effective, long-term retention/compliance: Duplicating the data on an HPE StoreOnce backup appliance to an HPE StoreEver tape library with NetBackup reclaims storage space on the HPE StoreOnce appliance while retaining access to the data on the physical tape.

In summary, Hewlett Packard Enterprise and Veritas NetBackup deliver an integrated, end-to-end data protection and data management solution to enhance business continuity and resiliency.

Appendix A: HPE StoreOnce concepts Table 5 provides an overview of HPE StoreOnce concepts that are important to understanding the use cases demonstrated in this Reference Configuration.

Table 5. Explanation of HPE StoreOnce terms

Term Explanation

HPE StoreOnce Concepts

HPE Catalyst HPE StoreOnce Catalyst is a Hewlett Packard Enterprise-developed backup protocol that is optimized for disk-based backup. HPE StoreOnce Catalyst allows data to be backed up to a target store on an HPE StoreOnce appliance. Data can also be copied from a Catalyst store on the source appliance to a different appliance that can be in the same location as the source appliance or in a remote location. The Defining HPE StoreOnce Catalyst: Backup Appliance and Data Protection Solution video explains in further detail what HPE StoreOnce Catalyst is and how it works.

Catalyst store Catalyst stores are created on an HPE StoreOnce appliance and are the backup target in which snapshot backups are stored. The Catalyst store can be a Fibre Channel device, referred to as Catalyst over Fibre Channel, or it can be an Ethernet device, referred to as Catalyst over Ethernet.

HPE Cloud Bank Storage HPE Cloud Bank Storage is an HPE StoreOnce feature that allows Catalyst stores to use external object storage. In use, an HPE Cloud Bank store behaves almost identically to a Catalyst store. This common behavior enables administrators to utilize HPE StoreOnce deduplication technology when sending, storing, and retrieving public or private cloud storage data. The key difference is that an HPE Cloud Bank store is supported as a Catalyst Copy target only, and directly backing up to an HPE Cloud Bank store is not supported.

HPE Cloud Bank stores and HPE StoreOnce Catalyst stores comparison

HPE Cloud Bank stores and HPE StoreOnce Catalyst stores are created and behave in similar ways. Any data protection software that supports the HPE StoreOnce Catalyst Copy functionality can create backup copies on an HPE Cloud Bank store. One fundamental distinction between the two stores is that HPE Cloud Bank stores write deduplicated data to public or private cloud storage, as opposed to a regular HPE StoreOnce Catalyst store where data is written to disk in the HPE StoreOnce appliance. The objects written to the Cloud Service Provider contain all of the information necessary to reconstruct the backup data within the HPE Cloud Bank store.

HPE StoreOnce Virtual Storage Appliance (VSA)

HPE StoreOnce VSA is software-defined storage that can be deployed when dedicated storage hardware is not required or, in the case of a disaster recovery scenario, where the primary backup device is no longer accessible. HPE StoreOnce VSA comes with a 90-day trialware license for evaluation. The HPE StoreOnce homepage provides additional details.

2 Assuming dedupe ratio of 20:1, as compared to a fully hydrated backup.

Reference Configuration

Sign up for updates

© Copyright 2019 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, Microsoft Azure, Windows, and Windows Server are registered trademarks of Microsoft Corporation in the United States and/or other countries. Linux® is the registered trademark of Linus Torvalds in the U.S. and other countries. Intel Xeon is a trademark of Intel Corporation in the U.S. and other countries. VMware, VMware ESXi, VMware vSphere Storage vMotion, and VMware vCenter are registered trademarks or trademarks of VMware, Inc. in the United States and/or other jurisdictions. Oracle is a registered trademark of Oracle and/or its affiliates. SAP is the trademark or registered trademark of SAP SE in Germany and in several other countries. All other third-party marks are property of their respective owners.

a00075087enw, June 2019

Resources and additional links HPE Cloud Bank Storage video, https://www.hpe.com/h22228/video-gallery/us/en/products/data-storage-hybrid-cloud/82bb7581-3547-4f55-ab57-3eeacebb2b56/hpe-cloud-bank-storage/video/

HPE Reference Architecture for HPE ProLiant for Microsoft Azure Stack data protection with Veritas NetBackup, HPE StoreOnce, and HPE Cloud Bank Storage, https://h20195.www2.hpe.com/v2/getdocument.aspx?docname=a00043062enw

HPE Reference Configuration for HPE Cloud Bank Storage with Microsoft Azure, https://h20195.www2.hpe.com/V2/GetDocument.aspx?docname=a00043317enw

HPE Reference Configuration for HPE Cloud Bank Storage with S3 Connector and Scality, https://h20195.www2.hpe.com/v2/getdocument.aspx?docname=a00047299enw

HPE StoreOnce Data Protection Backup Appliances, hpe.com/us/en/storage/storeonce.html

HPE StoreOnce Compatibility Matrix, https://h20272.www2.hpe.com/SPOCK/Pages/spock2Html.aspx?htmlFile=hw_storeonce.html (HPE Passport account is required)

HPE StoreEver Compatibility Matrix, https://h20272.www2.hpe.com/SPOCK/Pages/spock2Html.aspx?htmlFile=hw_storeever.html (HPE Passport account is required)

Microsoft Azure, https://azure.microsoft.com

Veritas NetBackup, https://www.veritas.com/product/backup-and-recovery/netbackup-8

Veritas Support NetBackup Documentation Landing Page, https://www.veritas.com/content/support/en_US/article.100040135.html

HPE Servers and Server systems, hpe.com/servers

To help us improve our documents, please provide feedback at hpe.com/contact/feedback.

Learn more at hpe.com/storage