HPE Zerto

apiVersion: soultec.ch/v1kind: Solutionmetadata: name: hpe/hpe-zerto locale: en labels: vendor: HPE Zerto Software capability/backup-recovery: 2.22 capability/migration: 3.42 capability/security: 2.06 vendor/hpe: 1.97 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. What we take from it: the failover rehearsal is the deliverable, not the installation. 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 rather than in the time since last night's job. HPE files it under continuous data protection, and that phrase is the honest description: it is neither backup nor a snapshot regime, and it does not replace either. - heading:

What it is for

body: | Three things that turn out to be the same mechanism. Disaster recovery, where a site or a platform is lost. Ransomware recovery, where the problem is not losing the data but finding the last moment before it was encrypted. And migration, where workloads move between platforms, on-premises or cloud, while they keep running. The third one surprises people. A DR tool bought for the fire is used for the datacentre move. - heading:

Why the rehearsal is the point

body: | Failover can be tested without interrupting anything. That is the feature that separates a recovery plan from a recovery hope, and it is the reason we build on Zerto for the plans we have to sign our name to. A plan nobody has run is a document. Run it twice a year and it becomes a number you can put in front of a board. - heading:

What changed

body: | Zerto was an independent company and is HPE's now, sold as HPE Zerto Software. Nothing about the technology changed with the badge. What changed is who your contract is with, and that is worth knowing before the next renewal rather than during it.status: corpus: 295 services: - {ref: services/disaster-recovery, score: 0.67} - {ref: services/cloud, score: 0.60} - {ref: services/engineering, score: 0.50} - {ref: services/datacenter-lifecycle, score: 0.48} posts: - {ref: posts/exagrid, score: 0.54} - {ref: posts/how-to-scality-artesca, score: 0.35} - {ref: posts/icas-fs, score: 0.35} - {ref: posts/sichere-backups-mit-blocky-for-veeam, score: 0.35} - {ref: posts/veeam-und-s3-storage-mit-artesca, score: 0.35} - {ref: posts/securing-your-data-with-veeam-surebackup, score: 0.35} experts: - {ref: experts/matthias-frech, score: 0.46} - {ref: experts/marco-betschart, score: 0.44} - {ref: experts/rico-lenherr, score: 0.44} neighbours: - {ref: solutions/hpe/hpe-morpheus/vm-essentials, score: 0.52} - {ref: solutions/hpe/hpe-storage/hpe-storeonce, score: 0.45} - {ref: solutions/hpe, score: 0.40}

{ "apiVersion": "soultec.ch/v1", "kind": "Solution", "metadata": { "name": "hpe/hpe-zerto", "locale": "en", "labels": { "vendor": "HPE Zerto Software", "capability/backup-recovery": "2.22", "capability/migration": "3.42", "capability/security": "2.06", "vendor/hpe": "1.97" }, "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. What we take from it: the failover rehearsal is the deliverable, not the installation.\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\nrather than in the time since last night's job.\n\nHPE files it under continuous data protection, and that phrase is the honest description:\nit is neither backup nor a snapshot regime, and it does not replace either." }, { "heading": "

What it is for

", "body": "Three things that turn out to be the same mechanism. Disaster recovery, where a site or a\nplatform is lost. Ransomware recovery, where the problem is not losing the data but finding\nthe last moment before it was encrypted. And migration, where workloads move between\nplatforms, on-premises or cloud, while they keep running.\n\nThe third one surprises people. A DR tool bought for the fire is used for the datacentre\nmove." }, { "heading": "

Why the rehearsal is the point

", "body": "Failover can be tested without interrupting anything. That is the feature that separates a\nrecovery plan from a recovery hope, and it is the reason we build on Zerto for the plans we\nhave to sign our name to.\n\nA plan nobody has run is a document. Run it twice a year and it becomes a number you can\nput in front of a board." }, { "heading": "

What changed

", "body": "Zerto was an independent company and is HPE's now, sold as HPE Zerto Software. Nothing\nabout the technology changed with the badge. What changed is who your contract is with, and\nthat is worth knowing before the next renewal rather than during it." } ], "status": { "corpus": 295, "services": [ { "ref": "services/disaster-recovery", "score": "0.67" }, { "ref": "services/cloud", "score": "0.60" }, { "ref": "services/engineering", "score": "0.50" }, { "ref": "services/datacenter-lifecycle", "score": "0.48" } ], "posts": [ { "ref": "posts/exagrid", "score": "0.54" }, { "ref": "posts/how-to-scality-artesca", "score": "0.35" }, { "ref": "posts/icas-fs", "score": "0.35" }, { "ref": "posts/sichere-backups-mit-blocky-for-veeam", "score": "0.35" }, { "ref": "posts/veeam-und-s3-storage-mit-artesca", "score": "0.35" }, { "ref": "posts/securing-your-data-with-veeam-surebackup", "score": "0.35" } ], "experts": [ { "ref": "experts/matthias-frech", "score": "0.46" }, { "ref": "experts/marco-betschart", "score": "0.44" }, { "ref": "experts/rico-lenherr", "score": "0.44" } ], "neighbours": [ { "ref": "solutions/hpe/hpe-morpheus/vm-essentials", "score": "0.52" }, { "ref": "solutions/hpe/hpe-storage/hpe-storeonce", "score": "0.45" }, { "ref": "solutions/hpe", "score": "0.40" } ] }}

apiVersion = "soultec.ch/v1"kind = "Solution"[metadata]name = "hpe/hpe-zerto"locale = "en"[metadata.labels]vendor = "HPE Zerto Software""capability/backup-recovery" = "2.22""capability/migration" = "3.42""capability/security" = "2.06""vendor/hpe" = "1.97"[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. What we take from it: the failover rehearsal is the deliverable, not the installation.'''practiceReview = true[[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 secondsrather than in the time since last night's job.HPE files it under continuous data protection, and that phrase is the honest description:it is neither backup nor a snapshot regime, and it does not replace either.'''[[sections]]heading = "

What it is for

"body = '''Three things that turn out to be the same mechanism. Disaster recovery, where a site or aplatform is lost. Ransomware recovery, where the problem is not losing the data but findingthe last moment before it was encrypted. And migration, where workloads move betweenplatforms, on-premises or cloud, while they keep running.The third one surprises people. A DR tool bought for the fire is used for the datacentremove.'''[[sections]]heading = "

Why the rehearsal is the point

"body = '''Failover can be tested without interrupting anything. That is the feature that separates arecovery plan from a recovery hope, and it is the reason we build on Zerto for the plans wehave to sign our name to.A plan nobody has run is a document. Run it twice a year and it becomes a number you canput in front of a board.'''[[sections]]heading = "

What changed

"body = '''Zerto was an independent company and is HPE's now, sold as HPE Zerto Software. Nothingabout the technology changed with the badge. What changed is who your contract is with, andthat is worth knowing before the next renewal rather than during it.'''[status]corpus = 295[[status.services]]ref = "services/disaster-recovery"score = "0.67"[[status.services]]ref = "services/cloud"score = "0.60"[[status.services]]ref = "services/engineering"score = "0.50"[[status.services]]ref = "services/datacenter-lifecycle"score = "0.48"[[status.posts]]ref = "posts/exagrid"score = "0.54"[[status.posts]]ref = "posts/how-to-scality-artesca"score = "0.35"[[status.posts]]ref = "posts/icas-fs"score = "0.35"[[status.posts]]ref = "posts/sichere-backups-mit-blocky-for-veeam"score = "0.35"[[status.posts]]ref = "posts/veeam-und-s3-storage-mit-artesca"score = "0.35"[[status.posts]]ref = "posts/securing-your-data-with-veeam-surebackup"score = "0.35"[[status.experts]]ref = "experts/matthias-frech"score = "0.46"[[status.experts]]ref = "experts/marco-betschart"score = "0.44"[[status.experts]]ref = "experts/rico-lenherr"score = "0.44"[[status.neighbours]]ref = "solutions/hpe/hpe-morpheus/vm-essentials"score = "0.52"[[status.neighbours]]ref = "solutions/hpe/hpe-storage/hpe-storeonce"score = "0.45"[[status.neighbours]]ref = "solutions/hpe"score = "0.40"

<?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.22</entry> <entry key="capability/migration">3.42</entry> <entry key="capability/security">2.06</entry> <entry key="vendor/hpe">1.97</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. What we take from it: the failover rehearsal is the deliverable, not the installation. </practice> <practiceReview>true</practiceReview> </spec> <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 secondsrather than in the time since last night's job.HPE files it under continuous data protection, and that phrase is the honest description:it is neither backup nor a snapshot regime, and it does not replace either. </body> </section> <section> <heading>

What it is for

</heading> <body>Three things that turn out to be the same mechanism. Disaster recovery, where a site or aplatform is lost. Ransomware recovery, where the problem is not losing the data but findingthe last moment before it was encrypted. And migration, where workloads move betweenplatforms, on-premises or cloud, while they keep running.The third one surprises people. A DR tool bought for the fire is used for the datacentremove. </body> </section> <section> <heading>

Why the rehearsal is the point

</heading> <body>Failover can be tested without interrupting anything. That is the feature that separates arecovery plan from a recovery hope, and it is the reason we build on Zerto for the plans wehave to sign our name to.A plan nobody has run is a document. Run it twice a year and it becomes a number you canput in front of a board. </body> </section> <section> <heading>

What changed

</heading> <body>Zerto was an independent company and is HPE's now, sold as HPE Zerto Software. Nothingabout the technology changed with the badge. What changed is who your contract is with, andthat is worth knowing before the next renewal rather than during it. </body> </section> </sections> <status> <corpus>295</corpus> <services> <item> <ref>services/disaster-recovery</ref> <score>0.67</score> </item> <item> <ref>services/cloud</ref> <score>0.60</score> </item> <item> <ref>services/engineering</ref> <score>0.50</score> </item> <item> <ref>services/datacenter-lifecycle</ref> <score>0.48</score> </item> </services> <posts> <item> <ref>posts/exagrid</ref> <score>0.54</score> </item> <item> <ref>posts/how-to-scality-artesca</ref> <score>0.35</score> </item> <item> <ref>posts/icas-fs</ref> <score>0.35</score> </item> <item> <ref>posts/sichere-backups-mit-blocky-for-veeam</ref> <score>0.35</score> </item> <item> <ref>posts/veeam-und-s3-storage-mit-artesca</ref> <score>0.35</score> </item> <item> <ref>posts/securing-your-data-with-veeam-surebackup</ref> <score>0.35</score> </item> </posts> <experts> <item> <ref>experts/matthias-frech</ref> <score>0.46</score> </item> <item> <ref>experts/marco-betschart</ref> <score>0.44</score> </item> <item> <ref>experts/rico-lenherr</ref> <score>0.44</score> </item> </experts> <neighbours> <item> <ref>solutions/hpe/hpe-morpheus/vm-essentials</ref> <score>0.52</score> </item> <item> <ref>solutions/hpe/hpe-storage/hpe-storeonce</ref> <score>0.45</score> </item> <item> <ref>solutions/hpe</ref> <score>0.40</score> </item> </neighbours> </status></manifest>

What it is

What it is for

Why the rehearsal is the point

What changed

What it is

What it is for

Why the rehearsal is the point

What changed

What it is

What it is for

Why the rehearsal is the point

What changed

What it is

What it is for

Why the rehearsal is the point

What changed

What it is

What it is for

Why the rehearsal is the point

What changed

What we do with it

Posts about it

ExaGrid – secure and immutable backup storage

Scality ARTESCA

iTernity iCAS FS

Secure backups with Blocky for Veeam

Veeam and S3 storage with ARTESCA

Securing your data with Veeam SureBackup

Who works with it

Matthias Frech

Marco Betschart

Rico Lenherr