Study guide
8.3 HPE GreenLake for Backup and Recovery: Architecture, Policies & Ransomware Protection
HPE ATP - Storage Solutions HPE0-J81
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Exam Orientation, Customer Requirements, HPE GreenLake & Portfolio
1.1 HPE0-J81 Exam Facts & the HPE ATP - Storage Solutions Certification Path 1.2 Assessing Storage Requirements, Workload Sizing & SLAs 1.3 HPE GreenLake Basics: Cloud Platform, Workspaces & Consumption Model 1.4 The HPE Storage Portfolio: Current Systems, Legacy Platforms & Positioning
2 Chapter 2: HPE Storage Tools, Reference Resources & Cloud Management
2.1 Assessment, Sizing & Configuration Tools: SAF, NinjaSTARS, Ninja Online & OCS 2.2 Compatibility & Reference Resources: SPOCK, QuickSpecs & HPE Support Center 2.3 Cloud Management & AIOps: Data Services Cloud Console, Data Ops Manager & HPE InfoSight
3 Chapter 3: Storage Topologies, Architectures & Implementation Models
3.1 Storage Topologies Compared: DAS, NAS, and SAN Architectures 3.2 Block, File, and Object Storage Implementations & Protocols 3.3 Converged, Hyperconverged (HCI) & Software-Defined Storage (SDS)
4 Chapter 4: Storage Fabrics, Connectivity & HPE GreenLake Services
4.1 SAN Fabric Design, Zoning & Multi-Protocol Storage Networking 4.2 Network Attached Storage Protocols, Shares & Permissions 4.3 HPE GreenLake Offerings for Storage and Data Protection
5 Chapter 5: HPE MSA Gen7 Storage: Hardware, Software & Data Protection
5.1 HPE MSA Gen7 Hardware: Models, Controllers, Drives & Expansion 5.2 HPE MSA Software: Virtual Storage, MSA-DP+, Automated Tiering & SSD Read Cache 5.3 HPE MSA Data Protection & Management: Snapshots, Volume Copy, Remote Snap & SMU v4
6 Chapter 6: HPE Alletra Storage MP B10000 & X10000
6.1 HPE Alletra Storage MP B10000 & X10000: Features and Positioning 6.2 HPE Alletra Storage MP Hardware: Controller Nodes, JBOFs, Switchless & Switched Systems 6.3 B10000 Resiliency & Data Services: All-Active Nodes, RAID 6, Data Reduction & Replication 6.4 Managing HPE Alletra Storage MP: Onboarding, Provisioning, Monitoring & Local Tools
7 Chapter 7: Data Protection Principles, Replication & Disaster Recovery
7.1 Fundamentals of Data Protection: RPO, RTO & Resiliency Architectures 7.2 Storage Snapshots, Clones & Replication Strategies 7.3 Disaster Recovery Planning, Business Continuity & Immutability
8 Chapter 8: HPE StoreOnce, Tape, GreenLake Backup and Recovery & Zerto
8.1 HPE StoreOnce Systems, Catalyst & Cloud Bank Storage 8.2 HPE Tape Solutions: LTO Technology, MSL Libraries & the Offline Air Gap 8.3 HPE GreenLake for Backup and Recovery: Architecture, Policies & Ransomware Protection 8.4 HPE Zerto Software: Continuous Data Protection, Disaster Recovery & Cyber Resilience
8.3 HPE GreenLake for Backup and Recovery: Architecture, Policies & Ransomware Protection
Key Takeaways Explain This Topic AI
HPE GreenLake for Backup and Recovery is a SaaS data protection service in Data Services Cloud Console; HPE runs and updates the backup software.
On-premises VMware and SQL Server protection uses two HPE-managed virtual machines: the Data Orchestrator and the Protection Store Gateway.
The Protection Store Gateway uses the HPE Catalyst engine to deduplicate, compress and encrypt backups, and it never connects to DSCC directly.
Protection policies can keep copies as array snapshots, in an on-premises protection store and in the HPE Cloud Protection Store; AWS protection needs no on-premises components.
Dual authorization requires a second administrator to approve deleting a backup or snapshot, and backups can be locked as immutable for a set period.
Last updated: October 2026
HPE GreenLake for Backup and Recovery
Quick Answer: HPE GreenLake for Backup and Recovery is backup as a service, run by HPE in Data Services Cloud Console . It protects VMware , Microsoft SQL Server , AWS workloads and HPE array volumes with global protection policies . On premises it uses two HPE-managed VMs, the Data Orchestrator and the Protection Store Gateway , and it stores copies as array snapshots , in an on-premises protection store and in the HPE Cloud Protection Store . Immutability and dual authorization protect backups from ransomware.
What it protects
Workload How it is protected
VMware virtual machines and datastores Image-level, application-consistent backups using VMware change tracking, plus array snapshots on HPE arrays
Microsoft SQL Server databases and instances On VMs and on physical servers, with transaction-log backup and point-in-time roll-forward for SQL on VMware
- AWS EC2 instances and EBS volumes AWS snapshots and/or copies in the HPE Cloud Protection Store
- AWS RDS Orchestrated RDS snapshots in the customer's AWS account
- AWS EKS Protection of Kubernetes applications running in EKS clusters
- HPE array volumes Volume protection groups for volumes created in the block storage service
- Architecture
The service itself runs in the GreenLake cloud and is updated by HPE, so there is no backup server or catalog for the customer to patch.
On-premises components (VMware and SQL Server protection)
Component Role
Data Orchestrator (DO) VM that connects to vCenter, SQL Server and arrays and is the only on-premises component that talks to DSCC
Protection Store Gateway (PSG) VM that processes backup data, using the HPE Catalyst engine to deduplicate, compress and encrypt it, and that hosts an on-premises protection store on a VMFS datastore from any storage array
Both run a hardened Linux operating system, are deployed and managed by the service, and can be recovered with guided recovery if they are damaged. The PSG never connects to DSCC ; its management traffic goes through the Data Orchestrator, and it sends cloud copies over an encrypted link to the Cloud Protection Store. You can deploy several PSGs for more scale. A physical HPE StoreOnce system can also be registered as the on-premises protection store; the service then creates Catalyst and Cloud Bank stores whose names start with hpegreenlake_ .
For AWS workloads, no on-premises components are needed.
Where copies live
- Tier Location Best for
- Array snapshots On the HPE array (local or replicated) Fastest recovery from mistakes and corruption
On-premises protection store PSG datastore or a registered StoreOnce Fast restores without relying on the array that failed
HPE Cloud Protection Store Object storage that HPE manages in the public cloud Offsite copy and longer retention
A policy can combine them, for example hourly snapshots kept for a day, nightly on-premises backups kept for 30 days and weekly cloud copies kept for a year. That gives copies on different media and in different places, which is the 3-2-1 idea from Chapter 7.
Protection policies and groups
Global protection policies define schedules, retention, immutability and targets once and apply them to on-premises and cloud workloads alike.
Protection groups collect assets to protect together. Automatic VMware protection groups can select VMs by VMware tags , so new VMs with the right tag are protected automatically.
For array-hosted workloads that the service does not protect at application level, it can still protect the storage volumes with crash-consistent array snapshots and array-optimized backups.
Ransomware defenses
- Defense Detail
- Immutability A policy can lock backups for a period during which they cannot be deleted or changed
Dual authorization Deleting a backup or snapshot needs approval from a second user with the Administrator or Backup and Recovery Administrator role
- Isolation The PSG does not connect to the cloud console; on-premises components run hardened Linux
- Encryption Backup data is encrypted by the PSG before it is written or sent
- Relationship to StoreOnce and the arrays
GreenLake for Backup and Recovery uses StoreOnce Catalyst technology inside the PSG and can use StoreOnce appliances as targets. It integrates with HPE arrays for array snapshots and, on the B10000, with volume protection groups . StoreOnce remains the right choice when a customer runs a traditional backup application such as Veeam or Commvault; GreenLake for Backup and Recovery suits customers who want HPE to run the backup software as a service.
Scenario
A manufacturer runs 300 VMware VMs and four SQL Server databases on a B10000, plus web servers on AWS EC2. It deploys a Data Orchestrator and two Protection Store Gateways, tags production VMs "gold" and applies a global policy: array snapshots every hour for 24 hours, an on-premises protection store nightly for 30 days, and weekly copies to the Cloud Protection Store for 12 months with a 30-day immutability lock. EC2 instances use the same policy with AWS snapshots and cloud copies. Dual authorization is enabled, so a stolen administrator password alone cannot delete backups.
Common exam traps
"The Protection Store Gateway talks to the cloud console." Only the Data Orchestrator does.
"AWS protection needs a gateway VM." It does not.
"It is a DR orchestrator." For continuous replication and failover, use GreenLake for Disaster Recovery and Zerto (section 8.4).