Data protection for HPE 3PAR File Persona Software with HPE Recovery Manager Central HPE Recovery Manager Central

Contents Introduction .................................................................................................................................................................................................................................................................................... 2

HPE 3PAR File Persona Software ....................................................................................................................................................................................................................... 2 HPE Recovery Manager Central ........................................................................................................................................................................................................................... 2

Traditional backup and recovery approaches ................................................................................................................................................................................................ 2 Network Data Management Protocol .............................................................................................................................................................................................................. 2 Share-based backup ........................................................................................................................................................................................................................................................ 3

Using RMC for local backup and recovery ......................................................................................................................................................................................................... 3 Creating a crash consistent Snapshot Set ................................................................................................................................................................................................... 5 Express Protect backup to StoreOnce ............................................................................................................................................................................................................ 6 Recovering FPGs from Snapshot Sets ............................................................................................................................................................................................................. 6 Recovering FPGs from Express Protect backups ................................................................................................................................................................................. 7

Using RMC for backup and recovery in replicated environments ............................................................................................................................................ 10 Backup and Recovery using snapshots ..................................................................................................................................................................................................... 12 Backup and Recovery using Express Protect ....................................................................................................................................................................................... 12

Summary ....................................................................................................................................................................................................................................................................................... 12

Technical white paper

Technical white paper Page 2

Introduction As organizations increasingly depend on business-critical file data services, data protection and recovery are essential for everyday business operations, especially during major failures or disasters. They are continuously challenged by the fast pace at which their file storage needs to grow, especially when their filesystem protection strategy starts to become unsustainable—single backup jobs can run from days to weeks, depending on the backup and recovery technology, size of the deployed filesystems and their filesystem structure.

When trying to solve these challenges, customers consider various technologies and strategies for protecting, and reliably recovering their business-critical data in a timely manner. The main factors for selecting technologies are cost of downtime, backup windows, maturity of technology, and many more.

While some file storage vendors only offer Network Data Management Protocol (NDMP) and share based backups to protect file data by transporting data between the file storage system and the backup device, HPE 3PAR File Persona Software, in conjunction with HPE Recovery Manager Central (RMC), provides an additional, highly efficient backup and recovery solution.

This integrated solution of RMC with File Persona is an addition to the traditional NDMP and share based backup mechanisms available for File Persona to solve customers’ prime challenge while protecting their file storage systems—meeting backup windows and service level agreements (SLAs).

This guide provides an overview of RMC and its integration into File Persona. It will outline the process, the concept, and usage of RMC for creating local and remote snapshots on HPE 3PAR StoreServ Storage for quick data recovery, in addition to using HPE StoreOnce Storage for long-term data protection and preservation.

HPE 3PAR File Persona Software The HPE 3PAR StoreServ Storage arrays allow customer environments to grow as they continue to expand their infrastructure. The HPE approach for converging block, file, and object access in a single controller is by enabling the HPE 3PAR File Persona feature in the HPE 3PAR OS. HPE 3PAR File Persona Software is a feature of the HPE 3PAR OS that enables a rich set of file protocols and core file data services on an HPE 3PAR StoreServ Storage system.

As a feature of HPE 3PAR OS, File Persona inherits one of the industry-leading architectures and Block Persona benefits of HPE 3PAR StoreServ Storage. It extends the spectrum of primary storage workloads natively addressed by HPE 3PAR StoreServ Storage from virtualization, databases, and applications via the Block Persona to include client workloads such as home directory consolidation, group, and department shares, and corporate shares via the File Persona—all with truly converged controllers, truly agile capacity, and truly unified management. For more detailed information on File Persona, review the HPE 3PAR File Persona User Guide.

HPE Recovery Manager Central HPE Recovery Manager Central (RMC) software integrates HPE 3PAR StoreServ primary storage into HPE StoreOnce Storage systems to provide a converged availability and flat backup service that augments traditional backup approaches. It combines the simplicity of snapshots with the reliability and cost effective retention of backups through a native integration of HPE 3PAR StoreServ and HPE StoreOnce in a seamless, converged data protection solution.

While RMC does manage the scheduling and creation of instant HPE 3PAR StoreServ Virtual Copy snapshots for local recovery, or remote snapshots if replication is being used, the Express Protect feature offers a second-tier of data protection by facilitating direct backups from HPE 3PAR StoreServ to HPE StoreOnce through a streamlined process. For more detailed information on RMC, review the HPE Recovery Manager Central User Guide.

Traditional backup and recovery approaches HPE 3PAR File Persona provides various industry standard mechanisms of protecting business-critical file data. These traditional backup and recovery mechanisms include NDMP, which generally stores backups in a proprietary format, and share-based backups, which is universally usable on any file storage system. Both of these traditional backup mechanisms come with their advantages and caveats.

Network Data Management Protocol NDMP is a protocol used to transport data between file storage systems and backup devices. It provides a mechanism for backup applications to communicate with the file storage device to generate a backup data stream, and control that stream. However, the format in which backups are stored is not defined by NDMP and is therefore generally proprietary, which prevents customers to restore data on third-party devices, and limits them to restore only to the same file storage device.

Technical white paper Page 3

Still, it is very commonly used to protect file storage systems that do not allow the installation of native backup agents, as the backup and restore data path is separate from user traffic and it enables backups of files and folders irrespective of file access protocols, which is essential in cross-protocol environments.

Share-based backup With share-based backups, backup agents on client systems protect the file storage systems by accessing the resources on the file shares remotely. The backup agents use the same access protocols and path as any other file sharing client and are therefore limited to the same capabilities, which may vary, depending on the protocol and the backup software vendor.

This backup option does not provide file storage vendor specific integrations, such as journaling or protocol independency, but it stores file data in a universal format, enabling vendor neutral recovery of individual filesystem objects to any device. The resulting flexibility in backup and restore operations make this backup option very popular in rapidly changing environments, but requires expensive filesystem tree walks to identify filesystem objects to be included in a backup.

HPE 3PAR File Persona works with both of these traditional backup solutions, which are discussed in more detail in the Protecting HPE 3PAR File Persona data white paper.

Using RMC for local backup and recovery As an additional option to traditional backups, RMC integrated with File Persona to create highly efficient backups for disaster recovery purposes. This section outlines using RMC for managing HPE 3PAR StoreServ’s Virtual Copy technology to create local crash consistent backups of File Provisioning Groups (FPGs) for fast backups and restores and how Express Protect is used to implement second-tier data protection on HPE StoreOnce Storage. RMC leverages the self-contained nature of FPGs to create fast, block snapshots to protect entire FPGs, including the contained Virtual File Server (VFS), File Stores and file shares.

Figure 1. File Persona with RMC conceptual architecture

As displayed in figure 1, a FPG consists of one or more Virtual Volumes, depending on the provisioned size of the FPG and the provisioning type. In RMC terminology, the set of Virtual Volumes that build a FPG is called a Recovery Set, which means they will be protected as a single entity in a consistent manner. The following process is required for protecting a FPG using RMC.

Note This paper assumes that HPE StoreOnce RMC is already deployed on a VMware® host and configured with basic settings, that HPE 3PAR StoreServ is configured, and HPE StoreOnce is configured to be used by Express Protect. The detailed instructions for this process, how to create Backup Policies, Recovery Sets, and how to add volumes, are found in the HPE Recovery Manager Central User Guide.

Technical white paper Page 4

1. Add an HPE 3PAR StoreServ Storage array that has File Persona started to RMC as a storage system.

2. Create a Recovery Set using all of the virtual volumes underlying the FPG that will be protected.

The list of Virtual Volumes of an FPG is displayed in the HPE 3PAR Command Line Interface (CLI) after issuing showfpg. In the example below, the FPG TestFPG is comprised of just a single Virtual Volume TestVV.1.

cli% showfpg TestFPG

------(GB)-------

FPG -Mountpath- -Size-- Available ActiveStates -DefaultCpg- ---VVs--- State

TestFPG /TestFPG 1024.00 1023.32 ACTIVATED FC_r5 TestVV.1 normal

--------------------------------------------------------------------------------

1 total 1024.00 1023.32

3. If the FPG is extended during its lifetime and if the underlying Virtual Volumes use deduplication, additional Virtual Volumes are being created to cover the additional capacity requirements. These additional volumes need to be added to the Recovery Set created for the FPG as the entire set of Virtual Volumes is required for recovery.

4. If protection of multiple FPGs is required, steps two and three need to be repeated.

5. If the Express Protect feature is sued, HPE StoreOnce needs to be added as a backup system in the RMC configuration and Backup Policies need to be created for each FPG that needs to be protected.

Technical white paper Page 5

On a standalone HPE 3PAR StoreServ Storage array, there are two options for protecting File Persona using RMC:

• Local snapshots of HPE 3PAR StoreServ: RMC will schedule, create, and delete snapshots of HPE 3PAR StoreServ as per the configuration in RMC. Using this technology solely is not different from using the snapshot schedules that are provided by the storage array itself; however, it is required as a precondition for Express Protect backups. Local snapshots are used to instantly recover entire FPGs in case of logical filesystem errors or if larger portions of a filesystem need to be recovered.

• Express Protect backups to HPE StoreOnce: RMC will schedule, create and delete snapshots on HPE 3PAR StoreServ as per the configuration in RMC and backup these snapshots directly to a second-tier HPE StoreOnce Storage system. While snapshots are used for quick recovery, they are not a substitute for a second-tier backup since storing snapshots and primary data on the same file storage system can lead to data loss if the local file storage system fails. Using Express Protect backups, snapshots are efficiently transported to a second-tier HPE StoreOnce backup system, which is faster than any of the traditional backup methods and allows simple recovery in case the entire file storage system fails.

When implementing a proper disaster recovery solution for File Persona using RMC, both of these options, in addition to the File Store snapshots that enable end-users to recover individual files and folders themselves, should be considered.

Creating a crash consistent Snapshot Set The procedure outlined in this section creates a crash consistent Snapshot Set using RMC. A Snapshot Set is a consistent collection of one or more Virtual Copy snapshots that were taken of a Recovery Set. RMC uses this locally stored Snapshot Set to recover entire FPGs instantly.

1. In RMC, navigate to “HPE Recovery Manager Central > Snapshot Sets”.

2. Select the “+ Snapshot Sets” button. In the popup window, set the Snapshot Set type to “Local” and select the Recovery Set created in the previous section. Provide a name and a description.

3. Click “Add” and wait for the background task to complete. This operation will create a crash-consistent snapshot of the FPGs underlying virtual volumes that are included in the Recovery Set. During recovery, HPE StoreOnce will use these snapshots for instant recovery of FPGs.

Note File Persona enables user-driven file recovery by using point-in-time File Store snapshots, which are different from block-level Virtual Copy snapshots at volume level. RMC is using the Virtual Copy snapshots for creating backups, which means only administrators can restore from these snapshots.

Technical white paper Page 6

Express Protect backup to StoreOnce The procedure outlined in this section creates an Express Protect backup to HPE StoreOnce. Since Snapshot Sets will become unavailable if the primary array fails, the Express Protect feature enables recovery from a second-tier HPE StoreOnce system.

1. Login to RMC and navigate to “HPE Recovery Manager Central > Express Protect”.

2. Select the “+ Express Protect” button. In the popup window, provide a name, description for the Express Protect backup and select a backup policy. The creation of a backup policy is not described in this paper, but is discussed in detail in the HPE Recovery Manager Central User Guide.

3. If protection of an existing Snapshot Set is required, e.g. the previously created Snapshot Set, the snapshot type “Existing” is used. Alternatively, a new Snapshot Set, including a schedule can be created. Using the second option, RMC will automatically create a Snapshot Set and automatically create an Express Protect backup to HPE StoreOnce in a single step.

4. Select “Add” and monitor the progress of the Express Backup on the “Activity” page. Depending on the size of the FPG and depending on whether it is an incremental or full backup, the duration of the Express Protect backup may vary. Wait for the backup operation to complete.

Note For Express Protect backups, RMC must have access to HPE 3PAR StoreServ and HPE StoreOnce using Fibre Channel or iSCSI. Please check the HPE Recovery Manager Central User Guide for more details.

Recovering FPGs from Snapshot Sets The process outlined in this section describes recovery of FPGs from Snapshot Sets, created by RMC. This process requires downtime for file share access since an entire FPG is being restored, which requires temporarily disabling the associated VFS and its file shares. The following steps should therefore only be executed during a maintenance window or in a disaster case.

1. If the FPG is still active on the array, the administrator first needs to disable this FPG. This is done using the HPE 3PAR CLI. Run the command setfpg -deactivate <FPG name> and insert the name of the FPG that was protected earlier as part of a Recovery Set. Wait for the FPG to become DEACTIVATED.

cli% setfpg -deactivate TestFPG

This action will lead to unavailability of shares on FPG TestFPG.

select q=quit y=yes n=no: y

4231

cli% showfpg TestFPG

------(GB)-------

FPG -Mountpath- -Size-- Available ActiveStates -DefaultCpg- ---VVs--- State

TestFPG /TestFPG 1024.00 1023.32 DEACTIVATED FC_r5 TestVV.1 normal

--------------------------------------------------------------------------------

1 total 1024.00 1023.32

The FPG and its VFS are now unavailable for file share access; however, the data is still in place. At this point, you can still reactivate the current state of the FPG. Once you restore a Snapshot Set, the current data in an FPG will be overwritten.

2. In RMC, navigate to “HPE Recovery Manager Central > Snapshot Sets” and select the Snapshot Set that you want to restore.

3. Once the Snapshot Set is highlighted, select “Actions > Restore”. In the popup window, select the base volumes that will be overwritten. Since all of the volumes of a FPG are required, set the checkmark “Select All” and click “Restore”.

Technical white paper Page 7

4. Wait for the restoration task to complete. Execute setfpg -activate <FPG name> on the HPE 3PAR CLI and wait for the FPG to report ACTIVATED.

cli% setfpg -activate TestFPG

Modifying FPG TestFPG.

select q=quit y=yes n=no: y

4232

cli% showfpg TestFPG

------(GB)-------

FPG -Mountpath- -Size-- Available ActiveStates -DefaultCpg- ---VVs--- State

TestFPG /TestFPG 1024.00 1023.32 ACTIVATED FC_r5 TestVV.1 normal

--------------------------------------------------------------------------------

1 total 1024.00 1023.32

5. Once the FPG shows ACTIVATED, the file shares are again accessible for clients, which need to reconnect to their shares at this point.

Recovering FPGs from Express Protect backups Since the Express Protect backups are stored on a second-tier HPE StoreOnce system, there are multiple different restore options available:

• Recovery to original Recovery Set, which restores an Express Protect backup to the current FPG and overwrites data in place.

• Recovery to a different Recovery Set, which restores an Express Protect backup to a new set of virtual volumes, which will preserve the current data in the FPG, but will require additional capacity on HPE 3PAR StoreServ to store the recovered FPG.

• Recovery to a different Recovery Set on a different HPE 3PAR StoreServ system, which is mainly used as a disaster recovery option, if the primary HPE 3PAR StoreServ array is not available any more.

Recovery to original Recovery Set This section outlines the steps to restore an Express Protect backup to the primary FPG and overwriting existing data. Similar to recovering from a local Virtual Copy snapshot, the recovery requires deactivation of the FPG and therefore downtime.

1. In the HPE 3PAR CLI, run removefpg -forget <FPG name> to disable the FPG and making it accessible for the restore operation.

cli% removefpg -forget TestFPG

Removing fpg: TestFPG

This FPG will no longer be available or listed in showfpg until it is added back with the “createfpg -recover" command. Ok to continue?

select q=quit y=yes n=no: y

4488

2. In RMC, navigate to “HPE Recovery Manager Central > Express Protect” and select the backup that you want to restore.

Technical white paper Page 8

3. Once the Express Protect backup is highlighted, select “Action > Restore”. In the popup window, select the volumes that will be recovered. Since all of the volumes are required for the FPG, set the checkmark “Select All” and continue with “Restore”.

4. Once the restore task completed successfully, execute createfpg –recover <restored volumes> on the HPE 3PAR CLI and wait for the operation to complete.

cli% createfpg -recover TestVV.1

4230

cli% showtask -d 4230

Id Type Name Status Phase Step -------StartTime-------

------ FinishTime------- -Priority- -User--

4230 background_command createfpg_task done --- --- 2016-02-22 05:31:53 CET

2016-02-22 05:33:18 CET n/a 3paradm

Detailed status:

2016-02-22 05:31:53 CET Created task.

2016-02-22 05:31:53 CET Updated Executing “createfpg_task" as 1:22991

2016-02-22 05:31:53 CET Updated Attempting recovery of FPGs:

2016-02-22 05:31:54 CET Updated vv TestVV.1 attached to node 0 File Services

2016-02-22 05:31:54 CET Updated vv TestVV.1 attached to node 1 File Services

2016-02-22 05:32:05 CET Updated FPG ID d44e06ae-f7fe-47c6-8370-df04529fb9b6 discovered. Attempting recovery

2016-02-22 05:32:25 CET Updated FPG TestFPG recovered.

2016-02-22 05:32:57 CET Updated FPG TestFPG activated.

2016-02-22 05:33:07 CET Updated No domains available for recovery

2016-02-22 05:33:18 CET Completed scheduled task.

5. Using the command showfpg <FPG name> will display the activation status of the FPG, which will be ACTIVATED after a successful recovery.

Recovery to a different Recovery Set This section outlines the steps to restore an Express Protect backup to a new FPG in case the original virtual volumes of the old FPG are broken or deleted, or if the data in the original FPG should be retained.

1. Recreate the Virtual Volumes with the same size and naming convention as the old volumes and create a new Recovery Set in RMC using these volumes. As per the example below, FPG “TestFPG” is comprised of one 1TiB volume, which needs to be recreated for the restore operation. If, during the lifetime of the FPG, it is extended beyond 16TiB and if the Virtual Volumes use deduplication, a second volume needs to be created.

Technical white paper Page 9

2. Navigate to “HPE Recovery Manager Central > Express Protect” and select the backup that you want to restore.

3. Once the Express Protect backup is highlighted, select “Actions > Restore”. In the popup window, change the destination of the backup to “Other Recovery Set” and select the Recovery Set that you created earlier. Click “Restore” and wait for the task to complete.

4. (Optional) If the original FPG is still available on the HPE 3PAR StoreServ array, for example if you are testing the disaster recovery case, you will first have to deactivate it. This is because the FPG contains the definition of virtual IP addresses and other file sharing related configuration items that will conflict with the active FPG. Execute removefpg –forget <FPG Name>.

Note The removefpg –forget <FPG name> command will not delete the FPG data, but remove it from the inventory. If you are testing your disaster recovery strategy, you can recover the FPG using the same command used for the restore process.

5. Once the restore operation is complete, execute createfpg –recover <restored volumes> on the HPE 3PAR CLI and wait for the background task to complete.

cli% createfpg -recover DiffVol_TestVV.1

4233

Recovery to a different HPE 3PAR StoreServ array This section outlines the steps to restore an Express Protect to a secondary HPE 3PAR StoreServ Storage system in a disaster case, when there is no access to the primary storage system any more. For this procedure to be possible, a secondary HPE 3PAR StoreServ Storage system that has File Persona started is required and registered with RMC. The configuration of File Persona on this system must match with the original system in terms of authentication settings, as these settings are not incorporated in the FPG backup. Refer to the Replication and Disaster Recovery Guide for File Persona for more details.

1. On the target HPE 3PAR StoreServ system, create new volumes with the same size and naming convention as the volumes on the old array and create a new Recovery Set in RMC using these volumes.

2. Navigate to “HPE Recovery Manager Central > Express Protect” and select the backup that you want to restore.

3. Once the Express Backup is highlighted, select “Actions > Restore”. In the popup window, change the destination of the backup to “Other Recovery Set” and select the Recovery Set that you have created earlier in this section. Click “Restore” and wait for the task to complete.

4. (Optional) If the original FPG is still available on the original HPE 3PAR StoreServ array, for example if you are testing the disaster recovery case, you will first have to deactivate it. Execute removefpg –forget <FPG Name> on the original array.

Technical white paper Page 10

5. Once the recovery task is complete, activate the restored FPG using the HPE 3PAR CLI command createfpg –recover <restored volumes>.

cli% createfpg -recover Target_TestVV.1

421

Note To access data on the target HPE 3PAR StoreServ Storage system while keeping the source share active, the user needs to change the IP configuration using removefsip/createfsip to avoid an IP conflict. Refer to the Replication and Disaster Recovery Guide for File Persona for more details on the process.

Using RMC for backup and recovery in replicated environments As part of their disaster recovery strategy, enterprises do not solely rely on a single storage system and a backup device, but take advantage of HPE 3PAR Remote Copy to ensure business continuity. Here, business critical data is replicated between multiple HPE 3PAR StoreServ Storage systems synchronously or asynchronously, depending on bandwidth and latency between the two systems.

File Persona benefits from the replication solution of HPE 3PAR StoreServ and uses the asynchronous periodic and synchronous replication modes in unidirectional or bidirectional modes to provide business continuity. Similarly, to other disaster recovery approaches of File Persona, the Virtual Volumes comprising a FPG are protected. The Virtual Volumes are replicated as a consistent set to a secondary 3PAR StoreServ Storage system.

Note All virtual volumes comprising a FPG must be in the same Remote Copy group if the FPG consists of multiple virtual volumes. Please refer to the Replication and Disaster Recovery Guide for File Persona for more information.

Replication alone does not protect against logical errors of applications, for example if files and folders are unintentionally deleted or changed. RMC helps protecting business-critical data from accidental deletion or modification and enables recovery from backups from any array. This section summarizes how RMC is used to protect File Persona data in a replicated environment.

Figure 2. Conceptual File Persona Remote Copy configuration

Technical white paper Page 11

In a Remote Copy environment, as displayed in figure 2, RMC creates synchronized point-in-time snapshots on both HPE 3PAR StoreServ arrays. Similar to the local protection capabilities using RMC that were discussed in earlier sections of this paper, these snapshots are used for quickly restoring data in case of a disaster on either array.

Figure 3. Recovery operations in a) normal, b) failover, c) failback state

Restore operations operated by RMC are be performed on the primary or remote storage array, depending on the current failover state of the environment. As depicted in figure 3, during normal operations, recovery is done on the primary array. After failover, during a disaster, snapshots that were created on the remote site are used for restores. Once the primary storage system is recovered, snapshots on the primary site can be used again.

It is important that both HPE 3PAR StoreServ Storage systems are configured equally with regards to authentication settings as these are not replicated as part of the FPGs. A simple example why this is important is the case of local user and group accounts. If the users and groups that are defined on the primary array are not configured on the remote system, users will not be able to connect to their file shares after a failover as authentication fails. Refer to the Replication and Disaster Recovery Guide for File Persona for more details on configuring and using HPE 3PAR StoreServ for replicating File Persona.

In order to enable RMC to be used in a Remote Copy environment a couple of configuration adjustments need to be performed in HPE RMC.

1. Register both HPE 3PAR StoreServ arrays that are part of the replication setup as storage systems in RMC.

2. Register a remote RMC appliance on the primary HPE StoreOnce RMC appliance—it is required to manage the creation and deletion of snapshots on the remote storage array.

Note A single RMC appliance can be used to manage both the primary and the remote HPE 3PAR StoreServ system, which we have chosen to do in this white paper. However, in a production environment, using a secondary, remote appliance is recommended as in a disaster case, access to the primary HPE StoreOnce RMC appliance is not guaranteed. Please refer to the HPE Recovery Manager Central User Guide for more information on Remote Copy and multiple RMC appliances.

3. Create a new Recovery Set, similar to the ones created earlier in this guide, but using the type “Remote” and selecting all of the virtual volumes underlying the FPG that is replicated to the remote HPE 3PAR StoreServ array. Two Recovery Sets will be created after this step—one for the source system and one for the remote system.

4. Ensure the HPE StoreOnce Storage system is added as Backup System and backup policies are created similarly to the ones used earlier in this paper.

Technical white paper Page 12

Backup and Recovery using snapshots Backup and recovery from snapshots is comparable to creating backups and performing restore operations in non-replicated environments. However, when using RMC in a replicated environment, some alterations to the process described in Recovering FPGs from Snapshot Sets need to be done.

During the creation of a new Snapshot Set in RMC set the selection for Snapshot Set type to “Remote” instead of “Local”. This will trigger synchronized, crash-consistent snapshots on both the primary storage array as well as the remote storage array and allow recovery from the same data set in both normal state and during disasters.

While performing a restore from a snapshot in either the primary or the remote site, the target array, where the restore is performed, needs to be in an active state. The failover and failback procedures for File Persona are explained in depth in the Replication and Disaster Recovery Guide for File Persona.

Backup and Recovery using Express Protect Creating Express Protect backups from replicated virtual volumes is not different from creating local Express Backups from non-replicated virtual volumes and is separate from the synchronized, crash-consistent remote snapshots explained in the previous section.

Figure 4. Express Protect for Remote Copy configurations

If Express Protect backups are required in both the primary and remote site, RMC will create local Express Protect backups in each site, each with an independent configuration. Please review section Express Protect backup to StoreOnce to setup Express Protect in each site. Figure 4 highlights that Express Protect is a separate configuration and process on both systems, where a RMC instance in the primary site is managing Express Protect backups in the primary site, and another RMC instance in the remote site is managing Express Protect backups in the remote site.

Summary HPE 3PAR File Persona Software provides multiple options for protecting business critical file data, using NDMP to provide protocol independent protection using certified backup ISVs, using share-based backups to provide fast, vendor-independent, single-file restores, and HPE Recovery Manager Central integration to provide quick protection for disaster recovery purposes.

As discussed in this paper, File Persona, integrated with RMC, offers streamlined data protection in large file storage environments by augmenting traditional backup approaches. It combines the simplicity of snapshots with the reliability and cost effective retention of backups through a native integration of HPE 3PAR StoreServ and HPE StoreOnce in a seamless, converged data protection solution.

Technical white paper

Sign up for updates

© Copyright 2016–2017 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.

VMware is a registered trademark or trademark of VMware, Inc. in the United States and/or other jurisdictions. All other third-party trademark(s) is/are property of their respective owner(s).

4AA6-4642ENW, February 2017, Rev. 2

Resources Additional information on protecting File Persona data can be found in the following locations:

HPE 3PAR File Persona User Guide

HPE Recovery Manager Central version 3.0.0 User Guide

Replication and Disaster Recovery Guide for File Persona

HPE 3PAR Command Line Interface Reference

Protecting HPE 3PAR File Persona data

Learn more at hpe.com/storage/3parfilepersona