HP Backup and Archive Example Configuration Guide technical
Technical white paper
HP Backup and Archive Example
Configuration Guide
Table of contents
Technical white paper | HP Backup and Archive Example Configuration Guide
Introduction
This guide provides example configurations for HP backup and archive solutions. The examples include direct-attach, basic, and extended Storage Area Networks (SANs), plus virtual and archive environments. While this document does not encompass all possible backup and archiving configurations, it should provide information to help build tape and disk-based solutions to meet specific business needs. All hardware items shown in this example guide are listed in the HP Data Agile
BURA Compatibility Matrix. The HP Data Agile BURA Compatibility Matrix provides information for designing data protection solutions, including backup, recovery, and archiving, which scale from entry-level workgroups to enterprise-level data centers.
It includes support for direct-attach Fibre Channel or SAS, and Storage Area Network (SAN).
Point-to-point configuration
Table 1.
Point-to-point description
Configuration
Typical usage
Description
Direct-attach SAS and direct-attach Fibre Channel.
Local and network client backup.
Data flow description
In the following example shown in figure 1, the backup server transfers data to the HP StoreEver Tape Drive or
HP StoreEver Tape Library utilizing backup software, or HP StoreOpen and Linear Tape File System (LTFS) for managing LTFS functionality on HP StoreEver LTO-5 and newer Ultrium Tape Drives. External tape drives will use a SAS interface. Drives contained in an HP StoreEver Tape Library use a Fibre Channel interface.
Clients on the LAN will transfer data first to the backup server, and then send the data to tape storage.
This solution provides data protection for a large number of clients through a dedicated backup server.
Data will flow:
Step From To
HP StoreEver Tape Storage device via Fibre Channel or SAS 1 Backup server
Figure 1.
Point-to-point connectivity and data flow
2
Technical white paper | HP Backup and Archive Example Configuration Guide
HP StoreOpen with Linear Tape File System (LTFS) software
Table 2.
StoreOpen with LTFS description
Configuration
Typical usage
Description
Data flow description
Direct connect between a workstation/host and HP StoreEver Tape Drive or HP StoreEver Tape Library.
Data transfer between a workstation/host and a standalone HP StoreEver Tape Drive or HP StoreEver
Tape Library for backup or data transport between LTFS solutions.
HP StoreOpen is a set of free software utilities that provide disk-like access to HP StoreEver Tape products using
LTFS. HP StoreOpen Standalone mounts a tape drive to the host like a disk or thumb drive, thereby giving access to the data on the tape cartridge just like a disk drive or thumb drive. HP StoreOpen Automation mounts a tape library to a host and presents each tape cartridge that is in the library as a file folder behind the mount letter.
Each file folder is given the name of the barcode label of the tape media and can be accessed like any other folder in the operating system. The user can navigate the directory of an LTO cartridge even if it is not loaded in an LTO
Tape Drive. A cartridge will be loaded automatically if a data read or write operation is needed. HP StoreOpen reads and writes in the LTFS format, thereby making it a great complementary product to other tape solutions that use LTFS, like the HP Tape-as-NAS solution, allowing for data exchange between solutions.
Figures 3 and 4 display the Standalone operating system view and the Automation operating system view.
Standalone data flow:
Step
1
From
Host/workstation
To
HP StoreEver Standalone LTO Tape Drive via direct connected SAS
Automation data flow:
1 Host/workstation
Figure 2.
StoreOpen with LTFS connectivity and data flow
HP StoreEver Tape Library via direct connected SAS or via Fibre Channel
3
Technical white paper | HP Backup and Archive Example Configuration Guide
Figure 3.
StoreOpen Standalone operating system view
Figure 4.
StoreOpen Automation operating system view
4
Technical white paper | HP Backup and Archive Example Configuration Guide
Heterogeneous SAN
Table 3.
Heterogeneous SAN description
Configuration
Typical usage
Description
Data flow description
Heterogeneous Storage Area Network (SAN).
Shared tape and disk storage across multiple servers.
The example in figure 5 illustrates a SAN configuration consisting of multiple servers with different operating systems, connected to shared storage. Each server can access the storage through a single host bus adapter
in this document for more information. Sharing an HP StoreEver Tape Library or HP StoreOnce Backup eliminates the need for multiple systems connected to each server, thereby simplifying data protection management and reducing total cost of ownership.
Data will flow:
Step
1
2
From
Shared SAN-attached disk array
Each SAN-attached backup server
To
Each SAN-attached backup server via Fibre Channel
SAN-attached HP StoreEver Tape Library or HP StoreOnce
Backup via Fibre Channel
Figure 5.
Heterogeneous SAN connectivity and data flow
5
Technical white paper | HP Backup and Archive Example Configuration Guide
Multipath to tape
Table 4.
Multipath to tape description
Configuration
Typical usage
Storage Area Network (SAN).
High-availability storage solution.
Description Advanced path failover (APF) uses capabilities in the HP StoreEver LTO-6 and newer Ultrium Tape Drives and the HP StoreEver Tape Libraries in which they are installed, combined with software drivers running on a host system to provide path failover when multiple paths are available to a tape drive or to a library controller.
Advanced path failover is a licensed feature.
In figure 6, two different servers designated as “server A” and “server B” have two different host interface ports that are connected to two different SANs. Each SAN is connected to the tape library. Each server has separate host bus adapter (HBA) ports dedicated to SAN 1 and SAN 2. All of the drives in the library have two ports with one port connected to SAN 1 and the second port connected to SAN 2. The library in this example has two different drives that are both configured to provide a library control path. Each drive that is configured to provide a library control path will connect to the SAN as two devices, a tape drive and a library controller, at two different SCSI logical units.
Note
Regardless of operating system environment, multipath to tape is not supported (only one of the two configured paths can access the tape devices at the same time).
Figure 6.
Multipath to tape connectivity
6
Additional description
The server is able to evaluate the Worldwide Identifiers to determine that there are two paths to each of two different tape drives and four paths to a library controller. In a typical multipath configuration, all of the paths for each device are available to the application that must resolve redundant paths and choose a preferred path. When advanced path failover drivers are installed on the server, the drivers will query each device for support of advanced path failover and if the device supports advanced path failover, the drivers will select a preferred path for each device and establish a connection using the preferred path. Only one path will be visible to the application.
Technical white paper | HP Backup and Archive Example Configuration Guide
HP StoreOnce Backup to tape offload
Table 5.
HP StoreOnce Backup to tape offload description
Configuration
Typical usage
Description
Data flow description
2
3
Storage Area Network (SAN).
High-speed disk-based backup for smaller backup windows, with tape backup for economical, long-term storage.
The example in figure 7 illustrates a configuration consisting of one to many servers, primary storage
(HP 3PAR StoreServ), HP StoreOnce disk-based storage, and a shared HP StoreEver Tape Library.
This configuration allows high-speed, deduplicated backups to StoreOnce. A tape-to-tape copy can be performed using the backup application to send rehydrated data from the StoreOnce appliance to the
SAN-attached StoreEver Tape Library for longer retention.
Data will flow:
Step
1
From
Primary storage
(HP 3PAR StoreServ Storage)
SAN-attached server
HP StoreOnce Backup
To
SAN-attached server via Fibre Channel
SAN-attached HP StoreOnce Backup via Fibre Channel
SAN-attached server via Fibre Channel
4 SAN-attached server
Figure 7.
HP StoreOnce Backup to tape offload connectivity and data flow
SAN-attached HP StoreEver Tape Storage via Fibre Channel
7
Technical white paper | HP Backup and Archive Example Configuration Guide
HP StoreOnce Catalyst remote site replication
Table 6.
HP StoreOnce Catalyst remote site replication description
Configuration
Typical usage
Description
Data flow description
Storage Area Network (SAN).
Transferring data from a branch office to the main data center or copying data between sites.
HP StoreOnce Catalyst allows source and target-side deduplication. With facilitation from data protection software, data can also be moved between sites without rehydration. In the data center, another copy of the data can be made to tape after rehydration utilizing tape-to-tape copy options in your data protection software.
1
2
Data will flow:
Step From
Server
Server
3
4
HP StoreOnce Backup Storage on branch site
HP StoreOnce Backup Storage on data center site
To
Server-side deduplication
HP StoreOnce Backup Storage at branch site via LAN
HP StoreOnce Backup Storage on Data Center site via WAN (Movement across the WAN can be managed by a data protection application.)
SAN-attached HP StoreEver Tape Storage via Fibre Channel (rehydrated data, utilizing tape-to-tape copy operation in data protection software)
Figure 8.
HP StoreOnce Catalyst remote site replication connectivity and data flow
8
Technical white paper | HP Backup and Archive Example Configuration Guide
SAN zoning
Table 7.
SAN zoning description
Configuration
Typical usage
Storage Area Network (SAN).
Zoning can be helpful in larger SANs to simplify device discovery and reduce chatter between devices.
Description HP recommends the following guidelines for determining how and when to use zoning:
• Use zoning by HBA port. Zoning by HBA port is implemented by creating a specific zone for each server or host by Worldwide Port Name, and adding only those storage elements to be utilized by that host. Zoning by HBA port prevents a server from detecting any other devices or servers on the SAN, and it simplifies the device discovery process.
• Disk and tape on the same HBAs is supported. For larger SAN environments, it is recommended to also add storage-centric zones for disk and backup targets. This type of zoning is done by adding overlapping zones with disk and backup targets separated.
• FC zoning can be implemented using physical switch port numbers, Worldwide Name IDs, or user-defined switch aliases.
Figure 9.
SAN zoning connectivity
9
Technical white paper | HP Backup and Archive Example Configuration Guide
Connecting independent fabrics
Table 8.
Connecting independent fabrics description
Configuration
Typical usage
Connecting multiple Storage Area Networks (SANs).
Sharing storage devices between independent SANs.
Description Figure 10 illustrates a configuration consisting of independent fabrics, or SAN islands, utilizing either a multiprotocol router (MPR) or Fibre Channel routing (FCR) between switches. Multiple servers (those colored gray) connect to their local switch within their independent fabric. Through the MPR or via licensing for
Fibre Channel routing, each server can connect to the shared tape library as if it were in the same independent fabric. This solution enables the interconnection of devices between SAN fabrics without merging those fabrics, thereby providing a more secure, flexible storage networking foundation.
Figure 10.
Connecting independent fabrics connectivity
10
Technical white paper | HP Backup and Archive Example Configuration Guide
HP StoreEver Tape Library partitioning
Table 9.
HP StoreEver Tape Library partitioning description
Configuration
Typical usage
Storage Area Network (SAN).
Segregation of different generations of LTO media, or when multiple departments or data protection applications need to share a single tape library.
Description Figure 11 illustrates a configuration consisting of two independent backup applications or departments accessing a single tape library. Utilizing the partitioning 1 feature in the tape library management console and
HP Command View for Tape Libraries, each backup application or department is presented with a logical library comprised of a subset of drives and slots from the physical library. Tape library partitioning increases flexibility in the data center and lowers total cost of ownership (TCO).
Figure 11.
HP StoreEver Tape Library partitioning connectivity
1 Partitioning is available in HP StoreEver ESL G3 Tape Libraries with optional license.
11
Technical white paper | HP Backup and Archive Example Configuration Guide
Extended SAN
Table 10.
Extended SAN description
Configuration
Typical usage
Description
Data flow description
Storage Area Network (SAN).
Offsite backup and disaster recovery.
Figure 12 illustrates a shared HP StoreEver Tape Library and an HP StoreOnce Virtual Tape Library (VTL) that uses SAN extension technologies to facilitate connectivity between remote sites. Data is read from the disk storage array located at site A and written to the StoreEver Tape Library or the StoreOnce VTL located at site B over the extended network link. While Fibre Channel over IP (FCIP) and Wave Division Multiplexing (WDM) allow connectivity over very long distances, long-wave small form-factor pluggables (SFPs) can accommodate distances of 10–35 km. This solution illustrates a variety of SAN extension technologies, providing offsite connectivity for remote backup and disaster recovery.
Data will flow:
Step
1
2
From
Each disk array
Each SAN-attached server
To
Each SAN-attached server via Fibre Channel
SAN-attached HP StoreEver Tape Library or HP StoreOnce VTL via Fibre Channel
Figure 12.
Extended SAN connectivity and data flow
12
Technical white paper | HP Backup and Archive Example Configuration Guide
HP 3PAR Remote Copy Software
Table 11.
HP 3PAR Remote Copy software description
Configuration
Typical usage
Description
Data flow description
Storage Area Network (SAN).
Disaster tolerance, business continuity, long-distance replication.
Figure 13 illustrates an asynchronous remote copy operation between the arrays at different sites with a tape backup at site B. HP 3PAR Remote Copy software enables multi-site and multi-mode replication with both midrange and high-end arrays. By creating a snapshot of the data at site B and presenting this data to a server at site B, this data can be backed up to the library at site B, thereby creating a remote backup of the data from site A.
Data will flow:
Step
1
2
3
From
HP 3PAR StoreServ Storage at site A
Snapshot of replicated LUNs
HP 3PAR StoreServ Storage at site B
4 Disaster recovery server(s)
Figure 13.
HP 3PAR Remote Copy software connectivity and data flow
To
HP 3PAR StoreServ Storage at site B via WAN
Takes place within the array at site B
SAN-attached disaster recovery server(s) via Fibre Channel
SAN-attached HP StoreEver Tape Library via Fibre Channel
13
Technical white paper | HP Backup and Archive Example Configuration Guide
HP StoreAll backup to HP StoreEver Tape Storage with Symantec NetBackup
Table 12.
HP StoreAll backup to HP StoreEver Tape Storage with Symantec NetBackup description
Configuration
Typical usage
Description
Data flow description
Storage Area Network (SAN) and Ethernet.
HP StoreAll Gateway NAS data protection.
Figure 14 illustrates a Network Data Management Protocol (NDMP) configuration for a three-way NDMP backup of the StoreAll Gateway to a StoreEver Tape Library. It consists of two StoreAll Gateway clusters with
HP 3PAR StoreServ Storage attached, a media or master server, and a StoreEver Tape Library. Cluster 1 acts as the NDMP Host Data Mover or DSP. The NetBackup for NDMP Master or Media Server acts as the data management application (DMA) server, and manages the robotics. During the backup session, StoreAll
Gateway cluster 1 acts as the Tape Data Server and StoreAll Gateway cluster 2 acts as the NDMP Data Server.
Figure 15 illustrates the data flow for a standard tape backup scenario for the HP StoreAll Gateway, where the backup software is installed directly on the Gateway servers, and the StoreAll cluster and StoreEver Tape Library are both SAN-attached.
View white papers for more detailed information: Data Protection for HP StoreAll Gateway NAS for NDMP,
Data Protection for HP StoreAll Gateway NAS.
Data will flow:
Step
1
From
HP StoreAll Gateway cluster 2 (via NDMP)
To
HP StoreAll Gateway cluster 1 (via LAN)
2 SAN-attached HP StoreAll Gateway cluster 1 SAN-attached HP StoreEver Tape Library via Fibre Channel
Figure 14.
HP StoreAll backup HP StoreEver Tape Library with Symantec NetBackup connectivity and data flow
14
Technical white paper | HP Backup and Archive Example Configuration Guide
Table 13.
HP StoreAll backup to HP StoreEver Tape Library with Symantec NetBackup description
Standard backup data flow
Data will flow:
Step From To
1 SAN-attached Gateway cluster SAN-attached StoreEver Tape Library via Fibre Channel
Figure 15.
Standard StoreAll backup to HP StoreEver Tape Library with Symantec NetBackup connectivity and data flow
15
Technical white paper | HP Backup and Archive Example Configuration Guide
HP Enterprise Secure Key Manager (ESKM)
Table 14.
HP ESKM description
Configuration
Typical usage
Description
Data flow description
3
4
Storage Area Network (SAN).
Integration of HP StoreEver encryption tape appliances into existing backup environments to facilitate security protection of data on tape.
The following example (figure 16) shows the integration of encryption tape appliances into a SAN environment consisting of multiple servers, primary disk storage (HP 3PAR StoreServ Storage), and an HP StoreEver Tape
Library. The backup data goes directly to the HP StoreEver LTO Tape Drive. The ESKM sends an encryption key to the tape library across the Ethernet, and the library passes the key to the drive via its management port.
Data will flow:
Step
1
2
5
From
SAN-attached HP 3PAR StoreServ Storage
SAN-attached server
HP StoreEver Tape Library requests/receives key
Library passes key to LTO Tape Drive over management port
ESKM (1)
To
SAN-attached server via Fibre Channel
SAN-attached HP StoreEver Tape Library via Fibre Channel
ESKM via Ethernet
LTO Tape Drive
ESKM (2) keys are automatically replicated between nodes via Ethernet
Figure 16.
HP ESKM connectivity and data flow
16
Technical white paper | HP Backup and Archive Example Configuration Guide
Veeam Backup and Restore to HP StoreEver Tape Storage with HP 3PAR
StoreServ Integration
Table 15.
Veeam backup to tape description
Configuration
Typical usage
Description
Data flow description
3
4
5
6
Storage Area Network (SAN).
SAN backup of VMware® and Microsoft® Hyper-V to a physical tape library.
Figure 17 illustrates a virtual environment with a Veeam backup solution that has HP 3PAR StoreServ integration. Veeam works directly with the HP 3PAR StoreServ Storage to create storage snapshots and mount them to the Veeam Proxy. It’s like Direct SAN Access, but it is less impactful on the infrastructure and the virtual machines (VMs) being backed up.
Figures 18 and 19 illustrate a VM restore from HP StoreEver Tape Storage with Veeam and a user-directed restore from tape with Veeam.
1
2
Data will flow:
Step From
Veeam backup server
ESX server creates snapshot and sends acknowledgement
Veeam backup server
Veeam backup server
HP 3PAR StoreServ Storage snapshot is mounted
Veeam Proxy server stores data
To
ESX server to create a snapshot via LAN/WAN
Veeam Proxy server via LAN
(occurs simultaneously with step 3)
HP 3PAR StoreServ Storage creates snapshot
ESX server deletes snapshot via LAN
Veeam Proxy server via Fibre Channel
Veeam repository server via Fibre Channel
HP StoreEver Tape Storage via Fibre Channel 7 Veeam repository server
Figure 17.
Veeam backup to tape connectivity and data flow
17
Technical white paper | HP Backup and Archive Example Configuration Guide
Table 16.
VM restore from tape with Veeam
Data flow description
3
4
Data will flow:
Step From
1
2
System administrator initiates restore from
Veeam GUI
Veeam backup server sends command to load correct tapes
HP StoreEver Tape Library sends restore image
5
Veeam backup server extracts VM from restore image
Veeam backup server restores VM image
6 Veeam backup server sends command to delete the restore image
Figure 18.
VM restore from tape with Veeam connectivity and data flow
To
Veeam backup server via LAN
HP StoreEver Tape Library via Fibre Channel
Veeam backup server via Fibre Channel
Veeam repository server via LAN
ESX server and datastore LUNs on the
HP 3PAR StoreServ storage via LAN
Repository server via LAN
18
Technical white paper | HP Backup and Archive Example Configuration Guide
Table 17.
User-directed restore from tape with Veeam
Data flow description
Data will flow:
Step From
1
2
3
System administrator initiates restore from
Veeam GUI
Veeam backup server sends command to load correct tapes
HP StoreEver Tape Library sends restore image
4 Veeam backup server sends restore image
5 System administrator manually directs the VM restore, or other restore options such as
Microsoft Exchange or Microsoft SharePoint using the Veeam GUI
Figure 19.
User-directed restore from tape with Veeam connectivity and data flow
To
Veeam backup server via LAN
HP StoreEver Tape Library via Fibre Channel
Veeam backup server via Fibre Channel
Veeam repository server via Fibre Channel
Veeam backup server via LAN
19
Technical white paper | HP Backup and Archive Example Configuration Guide
VMware vStorage API for Data Protection
Table 18.
VMware VADP data protection description
Configuration
Typical usage
Description
Data flow description
3
4
5
Storage Area Network (SAN).
SAN backup of VMware using VMware vSphere APIs for Data Protection (VADP). VADP is a set of APIs that plug into data protection applications that allow for backup of a VMware environment to a backup target.
Figure 20 illustrates a simple VADP backup environment with a vCenter Server, an ESX server running multiple virtual machines, a backup server with data protection software that is integrated with VADP, an HP 3PAR
StoreServ array where the datastore LUNs reside, and StoreOnce Storage or a StoreEver Tape Library for backup. VADP enables backup software to perform centralized virtual machine backups without the overhead of running individual backups from inside each virtual machine.
Data will flow:
Step
1
2
From
VADP integrated backup server requests VM vCenter Server identifies correct ESX server and requests snapshot of target VM
To vCenter Server via Ethernet
ESX server via Ethernet
6
Software snapshot is created within the ESX server
HP 3PAR StoreServ (snapshot image backup data)
Backup server
Backup server sends command to destroy backup snapshot
Within ESX server
Backup server via Fibre Channel
HP StoreOnce Storage or HP StoreEver
Tape Library via Fibre Channel vCenter Server via Ethernet
ESX server via Ethernet 7 vCenter Server directs correct ESX host to destroy backup snapshot
Figure 20.
VMware VADP data protection connectivity and data flow
20
Technical white paper | HP Backup and Archive Example Configuration Guide
Tape-as-NAS archiving with QStar Archive Manager
Table 19.
Tape-as-NAS archiving with QStar Archive Manager description
Configuration
Typical usage
Description
Data flow description
3
4
Step
1
(or) 1
2
Storage Area Network (SAN).
Data archiving for long-term storage.
Figure 21 represents a SAN with QStar Archive Manager (AM) software. The configuration diagrams illustrate a management LAN, as well as a 10 Gigabit Ethernet LAN for moving data via SMB or NFS clients and/or storage applications using SMB/NFS to a virtual QStar mount point residing on the QStar server. QStar AM retains file metadata on the Gateway server, fully accessible to clients. Based on administrator policy settings, files are later transferred from the disk cache over the SAN to the HP StoreEver Tape Library and replaced with file stubs.
Data replication is also managed by QStar AM, and duplicate LTO tapes can be manually moved offsite. Files in the disk cache are replaced with file stubs when the disk cache gets full. QStar AM will automatically move the file from the tape, back to the disk cache if a read request is made and the file is no longer present in the disk cache.
View white paper for more detailed information: Designing and Using a Tape-as-NAS Data Archive.
Data will flow:
From
NFS or SMB clients (Gigabit Ethernet)
Storage applications (Gigabit Ethernet)
QStar AM server
QStar AM cache
HP StoreEver LTO Tape (first tape) copies data
To
QStar AM server via Ethernet
QStar AM server via Ethernet
QStar AM cache via Fibre Channel
HP StoreEver LTO Tape via Fibre Channel
HP StoreEver LTO Tape (second tape)
5 HP StoreEver LTO Tape (manually moved)
Figure 21.
Tape-as-NAS archiving with QStar Archive Manager connectivity and data flow
Offsite tape vaulting
21
Technical white paper | HP Backup and Archive Example Configuration Guide
Tape-as-NAS combined cloud and tape solutions
Table 20.
Tape-as-NAS combined cloud and tape solutions description
Configuration
Typical usage
Description
Data flow description
Storage Area Network (SAN).
Data archiving for long-term storage with cloud and tape replication.
Figures 22 and 23 illustrate a SAN with QStar Archive Storage Manager (ASM) replicating to both an
HP StoreEver Tape Library and HP Helion Cloud. The configuration diagrams illustrate an Ethernet LAN for transferring data from clients to a QStar ASM traditional file system mount point residing on the QStar ASM server. Data is then transferred via a disk cache, to and from the back end storage media. QStar ASM manages the complexity of mapping data to both tape as SCSI commands and cloud as objects, offering data archive replication to both tape and cloud. Replication can be conducted in either a mirrored or tiered configuration.
View white paper for more detailed information: Reducing the complexity and risk of cloud with the tNAS combined cloud and tape solution.
1
2
Tiered data flow:
Step From
3
Clients
QStar ASM server
QStar ASM cache writes data
To
QStar ASM server via Ethernet
QStar ASM cache via Fibre Channel
SAN-attached HP StoreEver Tape
Library via Fibre Channel
HP Helion Cloud Storage via Ethernet 4 QStar ASM cache rewrites that same data and sends it
Figure 22.
Tiered solution connectivity and data flow
22
Technical white paper | HP Backup and Archive Example Configuration Guide
Table 20.
Tape-as-NAS combined cloud and tape solutions description (continued)
Data flow description
1
2
3
Mirrored data flow:
Step From
Clients
QStar ASM server
QStar ASM cache
4 QStar ASM cache
Figure 23.
Mirrored solution connectivity and data flow
To
QStar ASM server via Ethernet
QStar ASM cache via Fibre Channel
HP Helion Cloud Storage via Ethernet
SAN-attached HP StoreEver Tape Library via Fibre Channel
23
Technical white paper | HP Backup and Archive Example Configuration Guide
HP 3PAR File Persona Share Backup
Table 21.
HP 3PAR File Persona Share Backup description
Configuration
Typical usage
Description
Data flow description
Network share.
NAS file storage.
Figure 24 illustrates a Share Backup with HP 3PAR File Persona Software. The configuration diagrams illustrate an Ethernet LAN for reading and transferring data from the HP 3PAR StoreServ 7400c running HP 3PAR
File Persona services to the media server. The media server then uses the appropriate protocol to read the data from the File Persona and writes the data to the target. The target can be an HP StoreEver Tape Library via Fibre Channel, an HP StoreOnce appliance using FC/SMB or NFS depending on the StoreOnce model, or an
HP StoreAll appliance using SMB or NFS protocol.
You can use the entire HP 3PAR StoreServ Converged Controller family in place of the HP 3PAR StoreServ 7400c.
View white paper for more detailed information: Protecting HP 3PAR File Persona data with Share or NDMP backup.
Data will flow:
Step From
1
2
HP 3PAR StoreServ 7400c running File Persona
(Ethernet)
Media server
To
Media server via LAN
SAN-attached HP StoreEver Tape Library via Fibre Channel, HP StoreOnce Storage via FC/LAN, or HP StoreAll Storage via LAN
Figure 24.
HP 3PAR File Persona Share Backup connectivity and data flow
24
Technical white paper | HP Backup and Archive Example Configuration Guide
HP 3PAR File Persona Software NDMP backup
Table 22.
HP 3PAR File Persona NDMP Backup description
Configuration
Typical usage
Description
Data flow description iSCSI.
NAS file storage.
Figure 25 illustrates a NDMP backup between File Persona and HP StoreOnce/iSCSI library via the Gigabit
Ethernet NIC. The configuration diagrams illustrate the HP 3PAR StoreServ 7400c running HP 3PAR File
Persona services acting as the NDMP data mover and the ISV NDMP agent server acting as the data management application (DMA). The DMA controls and maintains the overall backup schedule for the
File Persona systems and arranges the activities between them and the iSCSI library when the backup session starts. When the backup session starts, the DMA gets released from the session and once the session is completed the metadata is then sent to the DMA for review. The independent software vendor NDMP agent controls the metadata and NDMP flow control to the NDMP server, where the data can then be sent to the iSCSI library for backup.
ISV used for NDMP backup must support NDMP. You can use the entire HP 3PAR StoreServ Converged
Controller family in place of the HP 3PAR StoreServ 7400c.
View white paper for more detailed information: Protecting HP 3PAR File Persona data with Share or NDMP backup.
Data will flow:
Step From To iSCSI library via LAN 1 HP 3PAR StoreServ 7400c running
HP 3PAR File Persona services (Gigabit Ethernet)
Figure 25.
HP 3PAR File Persona NDMP Backup connectivity and data flow
25
Technical white paper | HP Backup and Archive Example Configuration Guide
HP StoreOnce Recovery Manager Central for VMware
Table 23.
HP StoreOnce Recovery Manager Central for VMware description
Configuration
Typical usage
Description
Data flow description
4
5
Storage Area Network (SAN) and Ethernet.
Protect VMware virtual machine disks and datastores.
HP StoreOnce Recovery Manager Central (RMC) provides native integration of HP 3PAR StoreServ and
HP StoreOnce in a converged data protection solution that removes the dependency on traditional backup software. Figure 26 illustrates how Recovery Manager Central for VMware (RMC-V) enables protection of
VMware virtual machine disks and datastores using consistent snapshots (which can be used for rapid online recovery) and HP StoreOnce Express Protect Backup by facilitating backups of snapshots from HP 3PAR
StoreServ to HP StoreOnce. Backups on HP StoreOnce are self-contained volumes deduplicated to save space.
The backups can be used to recover data back to the original HP 3PAR StoreServ Storage system or to a different system. Administrators can access all the functionality from within the VMware vCenter Web Client.
2
3
Data will flow:
Step From
1 vCenter administrator initiates HP StoreOnce Express
Protect Backup of a VM or a datastore
VM I/O quiesced and VM snapshots are taken
RMC virtual appliance instructs HP 3PAR StoreServ array to take a snapshot of the virtual volume
VM snapshots are deleted and VM I/O resumes
Copy VM data on HP 3PAR StoreServ array virtual volume snapshot
To
Snapshot is exported to RMC virtual appliance
RMC virtual appliance via Fibre Channel
6 RMC virtual appliance moves data via Catalyst client low-bandwidth transfer
Figure 26.
HP StoreOnce Recovery Manager Central for VMware connectivity and data flow
StoreOnce appliance via Fibre Channel
26
Technical white paper | HP Backup and Archive Example Configuration Guide
IBM iSeries (AS/400) backup with TSI Storage Director
Table 24.
IBM iSeries backup with TSI Storage Director description
Configuration
Typical usage
Description
Data flow description
Storage Area Network (SAN).
Backup Storage Solution for IBM iSeries servers.
Figure 27 illustrates a SAN configuration consisting of multiple IBM iSeries backup servers, connected to the
TSI Storage Director, where data can then be sent to a shared storage location. The TSI Storage Director enables non-IBM storage devices (such as the HP StoreEver Tape Libraries or HP StoreOnce Backup) to be attached to IBM iSeries (AS/400) servers.
Data will flow:
Step
1
From
IBM iSeries backup server
To
TSI Storage Director via Fibre Channel
2 TSI Storage Director
Figure 27.
IBM iSeries backup with TSI Storage Director connectivity and data flow
HP StoreEver Tape Library or HP StoreOnce Backup
27
Technical white paper | HP Backup and Archive Example Configuration Guide
HP StoreOnce VSA and enterprise remote office/branch office (ROBO)
Table 25.
HP StoreOnce VSA and Enterprise ROBO description
Configuration
Typical usage
Connecting branch office environments through WAN.
Managing local backup and offsite backup copies.
Description HP StoreOnce VSA is optimal for centrally managed enterprise remote office or branch office (ROBO) locations with local backup and offsite backup copies. Branch offices can send backup data to a local HP StoreOnce VSA target with data deduplication-optimized copy over a WAN, to a remote HP StoreOnce Backup appliance located at a data center and DR site.
Figure 28.
HP StoreOnce VSA and Enterprise ROBO data flow
28
Technical white paper | HP Backup and Archive Example Configuration Guide
HP StoreOnce VSA and backup as a service (BaaS)
Table 26.
HP StoreOnce VSA and BaaS description
Configuration
Typical usage
Description
Connecting a BaaS environment through WAN.
Managing local backup and offsite services.
HP StoreOnce VSA is optimal in a BaaS environment with local backup and offsite as a service. Figure 29 displays several available options for customers using HP StoreOnce VSA and BaaS for backup.
1
2
Backup data can be sent to a local HP StoreOnce target and low-bandwidth replication (LBR) can be used to copy the backup to the HP StoreOnce VSA offsite service provider.
Backup data can be sent to a local HP Data Protector software store and use low-bandwidth object copy to replicate the backup to the HP StoreOnce VSA offsite service provider.
3 Backup data can be sent directly to the HP StoreOnce VSA offsite service provider using low-bandwidth
Catalyst backup.
4 Once data has been stored to the HP StoreOnce VSA, there is an option to replicate that data to other locations like HP StoreEver Tape or Tape Libraries.
Figure 29.
HP StoreOnce VSA and BaaS data flow
29
Technical white paper | HP Backup and Archive Example Configuration Guide
Veeam backup to HP StoreOnce with tape offload
Table 27.
Veeam backup to StoreOnce with tape offload description
Configuration
Typical usage
Description
Process flow description
Storage Area Network (SAN) and Ethernet.
Offload to tape using Veeam Backup and Replication software.
Figure 30 illustrates how HP StoreEver is used with Veeam backup to tape, to archive data from HP StoreOnce.
Veeam Backup and Replication enables the ability to archive backup files stored in backup repositories to
HP StoreEver Tape.
2
3
Process will flow:
Step
1 The Veeam backup server enumerates backup files in the database backup catalog and tape catalog to detect if any data has been modified since the last backup and queues the changes for archiving.
The Veeam backup server connects to the transport service to start the data transport process.
The modified data flows from the backup repository on the HP StoreOnce VSA to the HP StoreEver Tape.
For this process to occur the source transport service on the Veeam backup server reads data from the
HP StoreOnce VSA and the target transport service on the Veeam backup server writes the data to the
HP StoreEver Tape.
4 The Veeam backup server updates the backup and tape catalogs.
Figure 30.
Veeam backup to HP StoreOnce connectivity and process flow
30
Technical white paper | HP Backup and Archive Example Configuration Guide
Tiered data retention for HP 3PAR StoreServ
Table 28. Tiered data retention for HP 3PAR StoreServ description
Configuration
Typical usage
Description
Data flow description
Storage Area Network (SAN).
Data protection and retention implementation using a tiered strategy that combines disk and tape.
Figure 31 illustrates a Storage Area Network that combines HP 3PAR StoreServ Storage, HP StoreOnce
Backup, and HP StoreEver Tape to offer a complete business protection solution. Users can implement a disk-based solution with HP StoreOnce Backup for daily, short-term backups and fast recovery. HP StoreEver
Tape is used in conjunction with HP StoreOnce Backup to address long-term archive and compliance objectives. As data on the HP StoreOnce Backup appliance becomes infrequently or never accessed, tiered data retention policies can be used to expire data on HP StoreOnce while retaining that data to a secondary copy on HP StoreEver Tape. You can also transport a secondary LTO cartridge offsite for disaster recovery purposes. This reduces risk, increases efficiency, and lowers storage costs, which enables you to maximize the value you get from your data over its entire lifecycle while minimizing TCO.
View white paper for more detailed information: Tiered data retention for HP 3PAR StoreServ using
HP StoreOnce and HP StoreEver.
Data will flow:
Step
1
2
From
Primary storage
(HP 3PAR StoreServ 7440c)
SAN-attached server
To
SAN-attached server via Fibre Channel
SAN-attached HP StoreOnce 4900 and SAN-attached
HP StoreEver MSL6480 via Fibre Channel
3 SAN-attached HP StoreEver MSL6480
Figure 31.
Tiered data retention for HP 3PAR StoreServ connectivity and data flow
Offsite Tape Vaulting
31
Technical white paper | HP Backup and Archive Example Configuration Guide
Useful links
HP Storage
HP Servers
HP Backup, Recovery, and Archive Solutions
HP Backup, Recovery, and Archive (BURA) Solutions design guide
Learn more at hp.com/go/BURA
Sign up for updates hp.com/go/getupdated
Share with colleagues Rate this document
© Copyright 2013, 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. The only warranties for HP 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. HP shall not be liable for technical or editorial errors or omissions contained herein.
Linux is the registered trademark of Linus Torvalds in the U.S. and other countries. Microsoft and Windows are trademarks of the Microsoft group of companies. Oracle is a registered trademark of Oracle and/or its affiliates. VMware is a registered trademark or trademark of VMware, Inc. in the United States and/or other jurisdictions.
4AA5-0386ENW, June 2015, Rev. 1
