Around the Storage Block
cancel
Showing results for 
Search instead for 
Did you mean: 

4 data protection scenarios for your remote and branch office environments

StorageExperts

bhatia-gagan.jpg

By Gagan Bhatia, Product Marketing, Information Management and Governance, HPE    @Gagan_bh

The need for a comprehensive data protection is more important than ever. According to analysts Enterprise Strategy Group (ESG), 60% of business information resides outside of the core data center at remote and branch office (ROBO) locations. Whether you are a retailer, a financial institution or a package delivery company, chances are your data is spread across multiple geographically distributed locations. In most cases, the data getting created at these locations are extremely critical to local operations; when that data is lost and can’t be recovered quickly local operations stall.

Sadly, even today, in most organizations the remote office protection is done on a best-effort basis leaving the remote data unprotected or inadequately protected. By leaving ROBO protection out of the core data protection strategy, organizations put their growing amount of critical information at remote sites at significant risk. The big question: Why is remote site protection ignored as part of overall data protection strategy?

Your ROBO data protection requirementsThe simple answer is data protection requirements of remote office and branch office locations are unique. The traditional approaches requiring onsite IT expertise doesn’t work as ROBO locations generally have limited or no IT expertise onsite. What’s more, the scale of infrastructure in these locations is smaller compared to primary data centers at headquarters hence simplicity is the key. Fewer the systems the better. Here are some key elements of a solution for protecting ROBO environments:

  • data protection_umbrella_shutterstock_379611655_blog.jpgCost – Whether a solution can work with existing resources and infrastructure is a key cost consideration. Hardware independence or leveraging existing hardware is best for these environments.  An organization may have thousands of locations that require protection so cost/location has to be low.
  • Flexibility – Different locations may have different requirements. Some location may require local backup for quick recovery while others need direct backup to primary datacenter.
  • Centralization – Centralized operations are required so that IT staff in central location can deploy, protect, and manage backup and recovery process from one place. Configuration has to be simple as well. 
  • Recovery – How soon can the site be recovered in case of a disaster? Keeping data offsite and readily available, if possible in multiple locations, is important for rapid recovery of a local site.

Bringing HPE Data Protector and HPE StoreOnce together

Many large scale organizations with thousands of remote offices leverage ou4 integrated software and hardware solution to standardize their core data center and remote office protection. HPE Data Protector, a backup and recovery software, combined with HPE StoreOnce provide the scale, cost efficiencies and flexibility that meet your key ROBO protection requirements.

Both Data Protector and StoreOnce use the same deduplication technology – HPE StoreOnce – that enables the HPE solution to perform deduplication at any location in the backup stack. This flexibility is key in remote office environments as the decision to what data is already stored vs. what data is new can be made at the remote site itself so that only unique data is transferred over the wire. You benefit from centralized management of backup, disaster recovery and replication processes as well as remote deployment, low-bandwidth data movement across the data centers and remote office locations. Here you see a typical environment with two data centers and different size remote offices that have their own unique data protection requirements.

DPimage2J.jpg

 

Which of these ROBO scenarios seem familiar to your enterprise?

Scenario 1: Large remote site facility with a central data center

In this scenario, HPE Data Protector can manage the backup and recovery process at the remote site by storing backup data on a physical appliance such as HPE StoreOnce. For disaster recovery, the Data Protector cell on the remote site can replicate backup data from a local StoreOnce appliance to a higher capacity StoreOnce appliance such as 6500 in the primary datacenter or in a disaster recovery site.

Since both Data Protector and StoreOnce appliances (physical/virtual) use the same deduplication engine, the data is deduplicated only once and from that point on only the unique smaller size chunks are transferred between different sites. This efficient data transfer enables you to achieve WAN optimized replication between sites with poor connectivity.

Scenario 2: Medium remote site facility with a central data center

For a medium-size remote office that needs local backup for faster recovery but lacks onsite resources for managing the backup and recovery process, a local software based store can be created on any existing server with storage, and can be managed remotely via HPE Data Protector software within the central datacenter. Again, the local software store is based on the same HPE StoreOnce technology, hence the data replication process between remote site and core data center or the disaster recovery site is sending only changed blocks of information.

Scenario 3: Small remote site facility with a central data center

In cases where very small offices have limited infrastructure and lack IT resources, HPE Data Protector can remotely deploy agents directly on the server that is running the application or hosting the filesystem that needs to be protected. This deployment scenario eliminates the need for any local hardware at the remote site, which is a primary requirement for protecting small remote offices. The deduplication is performed directly on the application source and only unique data blocks are backed up to a StoreOnce backup target in the central datacenter.

 In case a disaster recovery site exists, the primary data center can replicate deduplicated data to the DR site. The advantage here is that remote sites can be recovered from either the primary site or the disaster recovery site, whichever is closest and can recover data faster.

Scenario 4: Virtualized remote site facility with a central data center

For remote sites that are highly virtualized and need local backup and recovery management, HPE Data Protector cell can run within a virtual machine and store data on HPE StoreOnce VSA which runs as a virtual appliance, thus avoiding the need for a dedicated physical infrastructure for backup and recovery purposes.

Whichever scenario you can best relate to, we think you’ll find that we offer a truly unique solution for remote office and branch office protection. With our approach, you can take all the data sources – no matter where they’re located or what they reside on – and use a single unified architecture to store data on a wide range of targets, including backup software, virtual backup appliances and hardware backup appliances. All use the same core technology, the same platform.

By providing a single unified management layer from physical infrastructure all the way to backup software, our HPE backup solution enables you to standardize backup and recovery infrastructure across your data centers and different types of remote sites.

Find out more

HPE StoreOnce Backup

HPE Data Protector

0 Kudos
About the Author

StorageExperts

Our team of Hewlett Packard Enterprise storage experts helps you to dive deep into relevant infrastructure topics.