DE · EN

Call us

build 6ddc7a35 | content blog-content@417154f · 338 posts | profiles 32 · corpus 315 | ● 0 skipped | built 2026-10-21 12:35 UTC format run

$ soultec get solution/hpe/hpe-zerto -o yaml$ soultec get solution/hpe/hpe-zerto -o json$ soultec get solution/hpe/hpe-zerto -o toml$ soultec get solution/hpe/hpe-zerto -o xml$ python3 hpe/hpe-zerto.pyPS> ./hpe/hpe-zerto.ps1$ go run hpe/hpe-zerto.go$ node hpe/hpe-zerto.js

apiVersion: soultec.ch/v1kind: Solutionmetadata: name: hpe/hpe-zerto locale: en labels: vendor: HPE Zerto Software capability/backup-recovery: 2.14 capability/migration: 2.82 capability/security: 1.91 vendor/hpe: 1.99 annotations: source: src/content/solutions/en/hpe/hpe-zerto.md route: /en/solutions/hpe/hpe-zerto/ schema: /nerd/schema/solutions.json markdown: /en/solutions/hpe/hpe-zerto.mdspec: title: HPE Zerto tags: [backup-recovery, migration, security] vendors: [hpe] summary: >- Continuous replication rather than a nightly job. Recovery measured in minutes and data loss in seconds, and an HPE product since the acquisition. photoNeed: >- HPE hardware in our hands: a ProLiant or Alletra being racked, cabled, or opened, with the model badge readable stub: false draft: false kind: product addon: false sourceNote: >- HPE product page for HPE Zerto Software, read 2026-08-30, filed under Continuous Data Protection. The Swiss project claim is quoted from soultec.ch/partner, read the same day. vendorName: HPE Zerto Software status: current practice: >- Draft, not yet reviewed. soulTec's own partner page says our engineers were on the largest Zerto project in Switzerland, and the Coop Switzerland success story on this site is the public half of that work. For us, the deliverable of a Zerto project is a rehearsed failover. practiceReview: true sections: - heading:

What it is

body: | Zerto replicates continuously instead of on a schedule. Writes are captured as they happen and shipped to the recovery site, so what you lose in a failure is measured in seconds. HPE files it under continuous data protection. Backup and snapshots are still needed alongside it. - heading:

What it is for

body: | Three use cases that share the same mechanism. Disaster recovery, where a site or a platform is lost. Ransomware recovery to the last moment before the data was encrypted. And migration, where workloads move between platforms, on-premises or cloud, while they keep running. - heading:

Failover testing

body: | Failover can be tested without interrupting anything. That is why we build on Zerto for the recovery plans we sign our name to. - heading:

What changed

body: | Zerto was an independent company and is HPE's now, sold as HPE Zerto Software. The technology has stayed the same. Your contract is now with HPE, and you should check it before the next renewal.status: corpus: 315 services: - {ref: services/disaster-recovery, score: 0.67} - {ref: services/cloud, score: 0.58} - {ref: services/engineering, score: 0.48} - {ref: services/datacenter-lifecycle, score: 0.47} experts: - {ref: experts/steven-rodenburg, score: 0.54} - {ref: experts/matthias-grasmueck, score: 0.51} - {ref: experts/yannick-gerber, score: 0.50} neighbours: - {ref: solutions/hpe, relation: parent} - {ref: solutions/hpe/hpe-morpheus/vm-essentials, score: 0.49} - {ref: solutions/hpe/hpe-storage/hpe-storeonce, score: 0.46} search: /en/search.json

{ "apiVersion": "soultec.ch/v1", "kind": "Solution", "metadata": { "name": "hpe/hpe-zerto", "locale": "en", "labels": { "vendor": "HPE Zerto Software", "capability/backup-recovery": 2.14, "capability/migration": 2.82, "capability/security": 1.91, "vendor/hpe": 1.99 }, "annotations": { "source": "src/content/solutions/en/hpe/hpe-zerto.md", "route": "/en/solutions/hpe/hpe-zerto/", "schema": "/nerd/schema/solutions.json", "markdown": "/en/solutions/hpe/hpe-zerto.md" } }, "spec": { "title": "HPE Zerto", "tags": [ "backup-recovery", "migration", "security" ], "vendors": [ "hpe" ], "summary": "Continuous replication rather than a nightly job. Recovery measured in minutes and data loss in seconds, and an HPE product since the acquisition.", "photoNeed": "HPE hardware in our hands: a ProLiant or Alletra being racked, cabled, or opened, with the model badge readable", "stub": false, "draft": false, "kind": "product", "addon": false, "sourceNote": "HPE product page for HPE Zerto Software, read 2026-08-30, filed under Continuous Data Protection. The Swiss project claim is quoted from soultec.ch/partner, read the same day.", "vendorName": "HPE Zerto Software", "status": "current", "practice": "Draft, not yet reviewed. soulTec's own partner page says our engineers were on the largest Zerto project in Switzerland, and the Coop Switzerland success story on this site is the public half of that work. For us, the deliverable of a Zerto project is a rehearsed failover.\n", "practiceReview": true, "sections": [ { "heading": "

What it is

", "body": "Zerto replicates continuously instead of on a schedule. Writes are captured as they happen\nand shipped to the recovery site, so what you lose in a failure is measured in seconds.\n\nHPE files it under continuous data protection. Backup and snapshots are still needed\nalongside it." }, { "heading": "

What it is for

", "body": "Three use cases that share the same mechanism. Disaster recovery, where a site or a\nplatform is lost. Ransomware recovery to the last moment before the data was encrypted. And\nmigration, where workloads move between platforms, on-premises or cloud, while they keep\nrunning." }, { "heading": "

Failover testing

", "body": "Failover can be tested without interrupting anything. That is why we build on Zerto for the\nrecovery plans we sign our name to." }, { "heading": "

What changed

", "body": "Zerto was an independent company and is HPE's now, sold as HPE Zerto Software. The\ntechnology has stayed the same. Your contract is now with HPE, and you should check it\nbefore the next renewal." } ] }, "status": { "corpus": 315, "services": [ { "ref": "services/disaster-recovery", "score": "0.67" }, { "ref": "services/cloud", "score": "0.58" }, { "ref": "services/engineering", "score": "0.48" }, { "ref": "services/datacenter-lifecycle", "score": "0.47" } ], "experts": [ { "ref": "experts/steven-rodenburg", "score": "0.54" }, { "ref": "experts/matthias-grasmueck", "score": "0.51" }, { "ref": "experts/yannick-gerber", "score": "0.50" } ], "neighbours": [ { "ref": "solutions/hpe", "relation": "parent" }, { "ref": "solutions/hpe/hpe-morpheus/vm-essentials", "score": "0.49" }, { "ref": "solutions/hpe/hpe-storage/hpe-storeonce", "score": "0.46" } ], "search": "/en/search.json" }}

apiVersion = "soultec.ch/v1"kind = "Solution"[metadata]name = "hpe/hpe-zerto"locale = "en"[metadata.labels]vendor = "HPE Zerto Software""capability/backup-recovery" = 2.14"capability/migration" = 2.82"capability/security" = 1.91"vendor/hpe" = 1.99[metadata.annotations]source = "src/content/solutions/en/hpe/hpe-zerto.md"route = "/en/solutions/hpe/hpe-zerto/"schema = "/nerd/schema/solutions.json"markdown = "/en/solutions/hpe/hpe-zerto.md"[spec]title = "HPE Zerto"tags = ["backup-recovery", "migration", "security"]vendors = ["hpe"]summary = "Continuous replication rather than a nightly job. Recovery measured in minutes and data loss in seconds, and an HPE product since the acquisition."photoNeed = "HPE hardware in our hands: a ProLiant or Alletra being racked, cabled, or opened, with the model badge readable"stub = falsedraft = falsekind = "product"addon = falsesourceNote = "HPE product page for HPE Zerto Software, read 2026-08-30, filed under Continuous Data Protection. The Swiss project claim is quoted from soultec.ch/partner, read the same day."vendorName = "HPE Zerto Software"status = "current"practice = '''Draft, not yet reviewed. soulTec's own partner page says our engineers were on the largest Zerto project in Switzerland, and the Coop Switzerland success story on this site is the public half of that work. For us, the deliverable of a Zerto project is a rehearsed failover.'''practiceReview = true[[spec.sections]]heading = "

What it is

"body = '''Zerto replicates continuously instead of on a schedule. Writes are captured as they happenand shipped to the recovery site, so what you lose in a failure is measured in seconds.HPE files it under continuous data protection. Backup and snapshots are still neededalongside it.'''[[spec.sections]]heading = "

What it is for

"body = '''Three use cases that share the same mechanism. Disaster recovery, where a site or aplatform is lost. Ransomware recovery to the last moment before the data was encrypted. Andmigration, where workloads move between platforms, on-premises or cloud, while they keeprunning.'''[[spec.sections]]heading = "

Failover testing

"body = '''Failover can be tested without interrupting anything. That is why we build on Zerto for therecovery plans we sign our name to.'''[[spec.sections]]heading = "

What changed

"body = '''Zerto was an independent company and is HPE's now, sold as HPE Zerto Software. Thetechnology has stayed the same. Your contract is now with HPE, and you should check itbefore the next renewal.'''[status]corpus = 315search = "/en/search.json"[[status.services]]ref = "services/disaster-recovery"score = "0.67"[[status.services]]ref = "services/cloud"score = "0.58"[[status.services]]ref = "services/engineering"score = "0.48"[[status.services]]ref = "services/datacenter-lifecycle"score = "0.47"[[status.experts]]ref = "experts/steven-rodenburg"score = "0.54"[[status.experts]]ref = "experts/matthias-grasmueck"score = "0.51"[[status.experts]]ref = "experts/yannick-gerber"score = "0.50"[[status.neighbours]]ref = "solutions/hpe"relation = "parent"[[status.neighbours]]ref = "solutions/hpe/hpe-morpheus/vm-essentials"score = "0.49"[[status.neighbours]]ref = "solutions/hpe/hpe-storage/hpe-storeonce"score = "0.46"

<?xml version="1.0" encoding="UTF-8"?><manifest kind="Solution"> <apiVersion>soultec.ch/v1</apiVersion> <metadata> <name>hpe/hpe-zerto</name> <locale>en</locale> <labels> <vendor>HPE Zerto Software</vendor> <entry key="capability/backup-recovery">2.14</entry> <entry key="capability/migration">2.82</entry> <entry key="capability/security">1.91</entry> <entry key="vendor/hpe">1.99</entry> </labels> <annotations> <source>src/content/solutions/en/hpe/hpe-zerto.md</source> <route>/en/solutions/hpe/hpe-zerto/</route> <schema>/nerd/schema/solutions.json</schema> <markdown>/en/solutions/hpe/hpe-zerto.md</markdown> </annotations> </metadata> <spec> <title>HPE Zerto</title> <tags> <item>backup-recovery</item> <item>migration</item> <item>security</item> </tags> <vendors> <item>hpe</item> </vendors> <summary>Continuous replication rather than a nightly job. Recovery measured in minutes and data loss in seconds, and an HPE product since the acquisition.</summary> <photoNeed>HPE hardware in our hands: a ProLiant or Alletra being racked, cabled, or opened, with the model badge readable</photoNeed> <stub>false</stub> <draft>false</draft> <kind>product</kind> <addon>false</addon> <sourceNote>HPE product page for HPE Zerto Software, read 2026-08-30, filed under Continuous Data Protection. The Swiss project claim is quoted from soultec.ch/partner, read the same day.</sourceNote> <vendorName>HPE Zerto Software</vendorName> <status>current</status> <practice>Draft, not yet reviewed. soulTec's own partner page says our engineers were on the largest Zerto project in Switzerland, and the Coop Switzerland success story on this site is the public half of that work. For us, the deliverable of a Zerto project is a rehearsed failover. </practice> <practiceReview>true</practiceReview> <sections> <section> <heading>

What it is

</heading> <body>Zerto replicates continuously instead of on a schedule. Writes are captured as they happenand shipped to the recovery site, so what you lose in a failure is measured in seconds.HPE files it under continuous data protection. Backup and snapshots are still neededalongside it. </body> </section> <section> <heading>

What it is for

</heading> <body>Three use cases that share the same mechanism. Disaster recovery, where a site or aplatform is lost. Ransomware recovery to the last moment before the data was encrypted. Andmigration, where workloads move between platforms, on-premises or cloud, while they keeprunning. </body> </section> <section> <heading>

Failover testing

</heading> <body>Failover can be tested without interrupting anything. That is why we build on Zerto for therecovery plans we sign our name to. </body> </section> <section> <heading>

What changed

</heading> <body>Zerto was an independent company and is HPE's now, sold as HPE Zerto Software. Thetechnology has stayed the same. Your contract is now with HPE, and you should check itbefore the next renewal. </body> </section> </sections> </spec> <status> <corpus>315</corpus> <services> <item> <ref>services/disaster-recovery</ref> <score>0.67</score> </item> <item> <ref>services/cloud</ref> <score>0.58</score> </item> <item> <ref>services/engineering</ref> <score>0.48</score> </item> <item> <ref>services/datacenter-lifecycle</ref> <score>0.47</score> </item> </services> <experts> <item> <ref>experts/steven-rodenburg</ref> <score>0.54</score> </item> <item> <ref>experts/matthias-grasmueck</ref> <score>0.51</score> </item> <item> <ref>experts/yannick-gerber</ref> <score>0.50</score> </item> </experts> <neighbours> <item> <ref>solutions/hpe</ref> <relation>parent</relation> </item> <item> <ref>solutions/hpe/hpe-morpheus/vm-essentials</ref> <score>0.49</score> </item> <item> <ref>solutions/hpe/hpe-storage/hpe-storeonce</ref> <score>0.46</score> </item> </neighbours> <search>/en/search.json</search> </status></manifest>

# Code generated by the soultec.ch build. DO NOT EDIT.import jsonPAGE = { "apiVersion": "soultec.ch/v1", "kind": "Solution", "metadata": { "name": "hpe/hpe-zerto", "locale": "en", "labels": { "vendor": "HPE Zerto Software", "capability/backup-recovery": 2.14, "capability/migration": 2.82, "capability/security": 1.91, "vendor/hpe": 1.99, }, "annotations": { "source": "src/content/solutions/en/hpe/hpe-zerto.md", "route": "/en/solutions/hpe/hpe-zerto/", "schema": "/nerd/schema/solutions.json", "markdown": "/en/solutions/hpe/hpe-zerto.md", }, }, "spec": { "title": "HPE Zerto", "tags": ["backup-recovery", "migration", "security"], "vendors": ["hpe"], "summary": "Continuous replication rather than a nightly job. Recovery measured in minutes and data loss in seconds, and an HPE product since the acquisition.", "photoNeed": "HPE hardware in our hands: a ProLiant or Alletra being racked, cabled, or opened, with the model badge readable", "stub": False, "draft": False, "kind": "product", "addon": False, "sourceNote": "HPE product page for HPE Zerto Software, read 2026-08-30, filed under Continuous Data Protection. The Swiss project claim is quoted from soultec.ch/partner, read the same day.", "vendorName": "HPE Zerto Software", "status": "current", "practice": ( "Draft, not yet reviewed. soulTec's own partner page says our engineers were on the largest Zerto project in Switzerland, and the Coop Switzerland success story on this site is the public half of that work. For us, the deliverable of a Zerto project is a rehearsed failover.\n" ), "practiceReview": True, "sections": [ { "heading": "

What it is

", "body": ( "Zerto replicates continuously instead of on a schedule. Writes are captured as they happen\n" "and shipped to the recovery site, so what you lose in a failure is measured in seconds.\n" "\n" "HPE files it under continuous data protection. Backup and snapshots are still needed\n" "alongside it." ), }, { "heading": "

What it is for

", "body": ( "Three use cases that share the same mechanism. Disaster recovery, where a site or a\n" "platform is lost. Ransomware recovery to the last moment before the data was encrypted. And\n" "migration, where workloads move between platforms, on-premises or cloud, while they keep\n" "running." ), }, { "heading": "

Failover testing

", "body": ( "Failover can be tested without interrupting anything. That is why we build on Zerto for the\n" "recovery plans we sign our name to." ), }, { "heading": "

What changed

", "body": ( "Zerto was an independent company and is HPE's now, sold as HPE Zerto Software. The\n" "technology has stayed the same. Your contract is now with HPE, and you should check it\n" "before the next renewal." ), }, ], }, "status": { "corpus": 315, "services": [ { "ref": "services/disaster-recovery", "score": "0.67", }, { "ref": "services/cloud", "score": "0.58", }, { "ref": "services/engineering", "score": "0.48", }, { "ref": "services/datacenter-lifecycle", "score": "0.47", }, ], "experts": [ { "ref": "experts/steven-rodenburg", "score": "0.54", }, { "ref": "experts/matthias-grasmueck", "score": "0.51", }, { "ref": "experts/yannick-gerber", "score": "0.50", }, ], "neighbours": [ { "ref": "solutions/hpe", "relation": "parent", }, { "ref": "solutions/hpe/hpe-morpheus/vm-essentials", "score": "0.49", }, { "ref": "solutions/hpe/hpe-storage/hpe-storeonce", "score": "0.46", }, ], "search": "/en/search.json", },}if __name__ == "__main__": print(json.dumps(PAGE, indent=2, ensure_ascii=False))

# Code generated by the soultec.ch build. DO NOT EDIT.$Page = [ordered]@{ apiVersion = 'soultec.ch/v1' kind = 'Solution' metadata = [ordered]@{ name = 'hpe/hpe-zerto' locale = 'en' labels = [ordered]@{ vendor = 'HPE Zerto Software' 'capability/backup-recovery' = 2.14 'capability/migration' = 2.82 'capability/security' = 1.91 'vendor/hpe' = 1.99 } annotations = [ordered]@{ source = 'src/content/solutions/en/hpe/hpe-zerto.md' route = '/en/solutions/hpe/hpe-zerto/' schema = '/nerd/schema/solutions.json' markdown = '/en/solutions/hpe/hpe-zerto.md' } } spec = [ordered]@{ title = 'HPE Zerto' tags = @('backup-recovery', 'migration', 'security') vendors = @('hpe') summary = 'Continuous replication rather than a nightly job. Recovery measured in minutes and data loss in seconds, and an HPE product since the acquisition.' photoNeed = 'HPE hardware in our hands: a ProLiant or Alletra being racked, cabled, or opened, with the model badge readable' stub = $false draft = $false kind = 'product' addon = $false sourceNote = 'HPE product page for HPE Zerto Software, read 2026-08-30, filed under Continuous Data Protection. The Swiss project claim is quoted from soultec.ch/partner, read the same day.' vendorName = 'HPE Zerto Software' status = 'current' practice = @'Draft, not yet reviewed. soulTec's own partner page says our engineers were on the largest Zerto project in Switzerland, and the Coop Switzerland success story on this site is the public half of that work. For us, the deliverable of a Zerto project is a rehearsed failover.'@ practiceReview = $true sections = @( [ordered]@{ heading = '

What it is

' body = @'Zerto replicates continuously instead of on a schedule. Writes are captured as they happenand shipped to the recovery site, so what you lose in a failure is measured in seconds.HPE files it under continuous data protection. Backup and snapshots are still neededalongside it.'@ } [ordered]@{ heading = '

What it is for

' body = @'Three use cases that share the same mechanism. Disaster recovery, where a site or aplatform is lost. Ransomware recovery to the last moment before the data was encrypted. Andmigration, where workloads move between platforms, on-premises or cloud, while they keeprunning.'@ } [ordered]@{ heading = '

Failover testing

' body = @'Failover can be tested without interrupting anything. That is why we build on Zerto for therecovery plans we sign our name to.'@ } [ordered]@{ heading = '

What changed

' body = @'Zerto was an independent company and is HPE's now, sold as HPE Zerto Software. Thetechnology has stayed the same. Your contract is now with HPE, and you should check itbefore the next renewal.'@ } ) } status = [ordered]@{ corpus = 315 services = @( [ordered]@{ ref = 'services/disaster-recovery' score = '0.67' } [ordered]@{ ref = 'services/cloud' score = '0.58' } [ordered]@{ ref = 'services/engineering' score = '0.48' } [ordered]@{ ref = 'services/datacenter-lifecycle' score = '0.47' } ) experts = @( [ordered]@{ ref = 'experts/steven-rodenburg' score = '0.54' } [ordered]@{ ref = 'experts/matthias-grasmueck' score = '0.51' } [ordered]@{ ref = 'experts/yannick-gerber' score = '0.50' } ) neighbours = @( [ordered]@{ ref = 'solutions/hpe' relation = 'parent' } [ordered]@{ ref = 'solutions/hpe/hpe-morpheus/vm-essentials' score = '0.49' } [ordered]@{ ref = 'solutions/hpe/hpe-storage/hpe-storeonce' score = '0.46' } ) search = '/en/search.json' }}$Page | ConvertTo-Json -Depth 32

// Code generated by the soultec.ch build. DO NOT EDIT.package mainimport ( "encoding/json" "os")var page = map[string]any{ "apiVersion": "soultec.ch/v1", "kind": "Solution", "metadata": map[string]any{ "name": "hpe/hpe-zerto", "locale": "en", "labels": map[string]any{ "vendor": "HPE Zerto Software", "capability/backup-recovery": 2.14, "capability/migration": 2.82, "capability/security": 1.91, "vendor/hpe": 1.99, }, "annotations": map[string]any{ "source": "src/content/solutions/en/hpe/hpe-zerto.md", "route": "/en/solutions/hpe/hpe-zerto/", "schema": "/nerd/schema/solutions.json", "markdown": "/en/solutions/hpe/hpe-zerto.md", }, }, "spec": map[string]any{ "title": "HPE Zerto", "tags": []any{"backup-recovery", "migration", "security"}, "vendors": []any{"hpe"}, "summary": "Continuous replication rather than a nightly job. Recovery measured in minutes and data loss in seconds, and an HPE product since the acquisition.", "photoNeed": "HPE hardware in our hands: a ProLiant or Alletra being racked, cabled, or opened, with the model badge readable", "stub": false, "draft": false, "kind": "product", "addon": false, "sourceNote": "HPE product page for HPE Zerto Software, read 2026-08-30, filed under Continuous Data Protection. The Swiss project claim is quoted from soultec.ch/partner, read the same day.", "vendorName": "HPE Zerto Software", "status": "current", "practice": "Draft, not yet reviewed. soulTec's own partner page says our engineers were on the largest Zerto project in Switzerland, and the Coop Switzerland success story on this site is the public half of that work. For us, the deliverable of a Zerto project is a rehearsed failover.\n", "practiceReview": true, "sections": []any{ map[string]any{ "heading": "

What it is

", "body": "Zerto replicates continuously instead of on a schedule. Writes are captured as they happen\n" + "and shipped to the recovery site, so what you lose in a failure is measured in seconds.\n" + "\n" + "HPE files it under continuous data protection. Backup and snapshots are still needed\n" + "alongside it.", }, map[string]any{ "heading": "

What it is for

", "body": "Three use cases that share the same mechanism. Disaster recovery, where a site or a\n" + "platform is lost. Ransomware recovery to the last moment before the data was encrypted. And\n" + "migration, where workloads move between platforms, on-premises or cloud, while they keep\n" + "running.", }, map[string]any{ "heading": "

Failover testing

", "body": "Failover can be tested without interrupting anything. That is why we build on Zerto for the\n" + "recovery plans we sign our name to.", }, map[string]any{ "heading": "

What changed

", "body": "Zerto was an independent company and is HPE's now, sold as HPE Zerto Software. The\n" + "technology has stayed the same. Your contract is now with HPE, and you should check it\n" + "before the next renewal.", }, }, }, "status": map[string]any{ "corpus": 315, "services": []any{ map[string]any{ "ref": "services/disaster-recovery", "score": "0.67", }, map[string]any{ "ref": "services/cloud", "score": "0.58", }, map[string]any{ "ref": "services/engineering", "score": "0.48", }, map[string]any{ "ref": "services/datacenter-lifecycle", "score": "0.47", }, }, "experts": []any{ map[string]any{ "ref": "experts/steven-rodenburg", "score": "0.54", }, map[string]any{ "ref": "experts/matthias-grasmueck", "score": "0.51", }, map[string]any{ "ref": "experts/yannick-gerber", "score": "0.50", }, }, "neighbours": []any{ map[string]any{ "ref": "solutions/hpe", "relation": "parent", }, map[string]any{ "ref": "solutions/hpe/hpe-morpheus/vm-essentials", "score": "0.49", }, map[string]any{ "ref": "solutions/hpe/hpe-storage/hpe-storeonce", "score": "0.46", }, }, "search": "/en/search.json", },}func main() { enc := json.NewEncoder(os.Stdout) enc.SetEscapeHTML(false) enc.SetIndent("", " ") if err := enc.Encode(page); err != nil { os.Exit(1) }}

// Code generated by the soultec.ch build. DO NOT EDIT.const page = { apiVersion: "soultec.ch/v1", kind: "Solution", metadata: { name: "hpe/hpe-zerto", locale: "en", labels: { vendor: "HPE Zerto Software", "capability/backup-recovery": 2.14, "capability/migration": 2.82, "capability/security": 1.91, "vendor/hpe": 1.99, }, annotations: { source: "src/content/solutions/en/hpe/hpe-zerto.md", route: "/en/solutions/hpe/hpe-zerto/", schema: "/nerd/schema/solutions.json", markdown: "/en/solutions/hpe/hpe-zerto.md", }, }, spec: { title: "HPE Zerto", tags: ["backup-recovery", "migration", "security"], vendors: ["hpe"], summary: "Continuous replication rather than a nightly job. Recovery measured in minutes and data loss in seconds, and an HPE product since the acquisition.", photoNeed: "HPE hardware in our hands: a ProLiant or Alletra being racked, cabled, or opened, with the model badge readable", stub: false, draft: false, kind: "product", addon: false, sourceNote: "HPE product page for HPE Zerto Software, read 2026-08-30, filed under Continuous Data Protection. The Swiss project claim is quoted from soultec.ch/partner, read the same day.", vendorName: "HPE Zerto Software", status: "current", practice: "Draft, not yet reviewed. soulTec's own partner page says our engineers were on the largest Zerto project in Switzerland, and the Coop Switzerland success story on this site is the public half of that work. For us, the deliverable of a Zerto project is a rehearsed failover.\n", practiceReview: true, sections: [ { heading: "

What it is

", body: "Zerto replicates continuously instead of on a schedule. Writes are captured as they happen\n" + "and shipped to the recovery site, so what you lose in a failure is measured in seconds.\n" + "\n" + "HPE files it under continuous data protection. Backup and snapshots are still needed\n" + "alongside it.", }, { heading: "

What it is for

", body: "Three use cases that share the same mechanism. Disaster recovery, where a site or a\n" + "platform is lost. Ransomware recovery to the last moment before the data was encrypted. And\n" + "migration, where workloads move between platforms, on-premises or cloud, while they keep\n" + "running.", }, { heading: "

Failover testing

", body: "Failover can be tested without interrupting anything. That is why we build on Zerto for the\n" + "recovery plans we sign our name to.", }, { heading: "

What changed

", body: "Zerto was an independent company and is HPE's now, sold as HPE Zerto Software. The\n" + "technology has stayed the same. Your contract is now with HPE, and you should check it\n" + "before the next renewal.", }, ], }, status: { corpus: 315, services: [ { ref: "services/disaster-recovery", score: "0.67", }, { ref: "services/cloud", score: "0.58", }, { ref: "services/engineering", score: "0.48", }, { ref: "services/datacenter-lifecycle", score: "0.47", }, ], experts: [ { ref: "experts/steven-rodenburg", score: "0.54", }, { ref: "experts/matthias-grasmueck", score: "0.51", }, { ref: "experts/yannick-gerber", score: "0.50", }, ], neighbours: [ { ref: "solutions/hpe", relation: "parent", }, { ref: "solutions/hpe/hpe-morpheus/vm-essentials", score: "0.49", }, { ref: "solutions/hpe/hpe-storage/hpe-storeonce", score: "0.46", }, ], search: "/en/search.json", },};console.log(JSON.stringify(page, null, 2));

# 80 lines · YAML · validated at build# 111 lines · JSON · validated at build# 116 lines · TOML · validated at build# 132 lines · XML · validated at build# 131 lines · Python · read back at build, equals the JSON record# 129 lines · PowerShell · read back at build, equals the JSON record# 133 lines · Go · read back at build, equals the JSON record# 118 lines · JavaScript · read back at build, equals the JSON record · served at /en/solutions/hpe/hpe-zerto.md

Solution · HPE

HPE Zerto

The vendor calls it: HPE Zerto Software

Continuous replication rather than a nightly job. Recovery measured in minutes and data loss in seconds, and an HPE product since the acquisition.

HPE Gold Partner

Topics Backup and Recovery 2.14 Migration 2.82 Security 1.91

Vendors HPE 1.99

04Services

03Capabilities

315Corpus

photograph wantedHPE hardware in our hands: a ProLiant or Alletra being racked, cabled, or opened, with the model badge readable

What it is

Zerto replicates continuously instead of on a schedule. Writes are captured as they happen and shipped to the recovery site, so what you lose in a failure is measured in seconds.

HPE files it under continuous data protection. Backup and snapshots are still needed alongside it.

What it is for

Three use cases that share the same mechanism. Disaster recovery, where a site or a platform is lost. Ransomware recovery to the last moment before the data was encrypted. And migration, where workloads move between platforms, on-premises or cloud, while they keep running.

Failover testing

Failover can be tested without interrupting anything. That is why we build on Zerto for the recovery plans we sign our name to.

What changed

Zerto was an independent company and is HPE’s now, sold as HPE Zerto Software. The technology has stayed the same. Your contract is now with HPE, and you should check it before the next renewal.

What we do with it

Draft, unreviewed

Draft, not yet reviewed. soulTec's own partner page says our engineers were on the largest Zerto project in Switzerland, and the Coop Switzerland success story on this site is the public half of that work. For us, the deliverable of a Zerto project is a rehearsed failover.

This paragraph is a draft and nobody at soulTec has confirmed it yet. Everything above it describes the product and is checkable against the vendor.