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 service/backup -o yaml$ soultec get service/backup -o json$ soultec get service/backup -o toml$ soultec get service/backup -o xml$ python3 backup.pyPS> ./backup.ps1$ go run backup.go$ node backup.js

apiVersion: soultec.ch/v1kind: Servicemetadata: name: backup locale: en labels: group: infrastructure capability/backup-recovery: 2.14 capability/storage: 2.36 vendor/hpe: 1.99 vendor/veeam: 3.03 annotations: source: src/content/services/en/backup.md route: /en/services/backup/ schema: /nerd/schema/services.json markdown: /en/services/backup.mdspec: title: Backup group: infrastructure audience: [enterprise, provider] order: 6 tags: [backup-recovery, storage] vendors: [hpe, veeam] summary: >- Backed up to 3-2-1-1-0, on immutable storage. The backup estate should be the equal of the primary one, and rarely is. photo: rack-proliant-dl360 photoNeed: >- A restore actually being tested: the screen showing a running restore job, with someone watching it rather than starting it stub: false draft: false sections: - heading:

The standard

body: | Highly available production infrastructure is normal now. Backup infrastructure much less so, even though in a real incident it is the only one that still counts. It should be the equal of the primary: secure, fast, solid, scalable. - heading:

3-2-1-1-0

body: | Three copies, on two kinds of media, one of them off site, one of them immutable, and zero errors on the restore test. The last two digits are the ones missing in practice. **Immutable** is the answer to ransomware. A backup an attacker can delete with the same credentials that reach production is not a backup at the moment it matters. **Zero** means tested. A backup whose restore has never been exercised is an assumption. - heading:

What it protects against

body: | Against deleted data, by users as much as by attackers. Against hardware failure. Against insiders. And against the loss of a whole data centre site, which is rare and takes everything else with it at the same time. - heading:

How we build it

body: | To your requirements, with products that complement each other rather than overlap. Daily operation stays simple: restores, checks and expansions without specialist knowledge. The measure is the RPO and RTO from the requirements. The backup storage and the backup server are sized against them, because a restore that misses the deadline is not one. Offloading backup data to the cloud runs on S3 object storage, stored immutably.status: corpus: 315 solutions: - {ref: solutions/hpe/hpe-storage/hpe-storeonce, score: 1.00} - {ref: solutions/hpe, score: 0.61} - {ref: solutions/hpe/hpe-dhci, score: 0.58} - {ref: solutions/hpe/hpe-storage/alletra-storage-mp-b10000, score: 0.52} alsoLike: - {ref: posts/how-to-deploy-vsan-snapshot-service-appliance, score: 0.70} - {ref: posts/raid-controller, score: 0.67} - {ref: services/managed-object-storage, score: 0.59} experts: - {ref: experts/rico-lenherr, score: 0.54} - {ref: experts/marco-betschart, score: 0.49} - {ref: experts/aldo-gwerder, score: 0.47} search: /en/search.json

{ "apiVersion": "soultec.ch/v1", "kind": "Service", "metadata": { "name": "backup", "locale": "en", "labels": { "group": "infrastructure", "capability/backup-recovery": 2.14, "capability/storage": 2.36, "vendor/hpe": 1.99, "vendor/veeam": 3.03 }, "annotations": { "source": "src/content/services/en/backup.md", "route": "/en/services/backup/", "schema": "/nerd/schema/services.json", "markdown": "/en/services/backup.md" } }, "spec": { "title": "Backup", "group": "infrastructure", "audience": [ "enterprise", "provider" ], "order": 6, "tags": [ "backup-recovery", "storage" ], "vendors": [ "hpe", "veeam" ], "summary": "Backed up to 3-2-1-1-0, on immutable storage. The backup estate should be the equal of the primary one, and rarely is.", "photo": "rack-proliant-dl360", "photoNeed": "A restore actually being tested: the screen showing a running restore job, with someone watching it rather than starting it", "stub": false, "draft": false, "sections": [ { "heading": "

The standard

", "body": "Highly available production infrastructure is normal now. Backup infrastructure much less\nso, even though in a real incident it is the only one that still counts. It should be the\nequal of the primary: secure, fast, solid, scalable." }, { "heading": "

3-2-1-1-0

", "body": "Three copies, on two kinds of media, one of them off site, one of them immutable, and zero\nerrors on the restore test. The last two digits are the ones missing in practice.\n\n**Immutable** is the answer to ransomware. A backup an attacker can delete with the same\ncredentials that reach production is not a backup at the moment it matters.\n\n**Zero** means tested. A backup whose restore has never been exercised is an assumption." }, { "heading": "

What it protects against

", "body": "Against deleted data, by users as much as by attackers. Against hardware failure. Against\ninsiders. And against the loss of a whole data centre site, which is rare and takes\neverything else with it at the same time." }, { "heading": "

How we build it

", "body": "To your requirements, with products that complement each other rather than overlap. Daily\noperation stays simple: restores, checks and expansions without specialist knowledge.\n\nThe measure is the RPO and RTO from the requirements. The backup storage and the backup\nserver are sized against them, because a restore that misses the deadline is not one.\nOffloading backup data to the cloud runs on S3 object storage, stored immutably." } ] }, "status": { "corpus": 315, "solutions": [ { "ref": "solutions/hpe/hpe-storage/hpe-storeonce", "score": "1.00" }, { "ref": "solutions/hpe", "score": "0.61" }, { "ref": "solutions/hpe/hpe-dhci", "score": "0.58" }, { "ref": "solutions/hpe/hpe-storage/alletra-storage-mp-b10000", "score": "0.52" } ], "alsoLike": [ { "ref": "posts/how-to-deploy-vsan-snapshot-service-appliance", "score": "0.70" }, { "ref": "posts/raid-controller", "score": "0.67" }, { "ref": "services/managed-object-storage", "score": "0.59" } ], "experts": [ { "ref": "experts/rico-lenherr", "score": "0.54" }, { "ref": "experts/marco-betschart", "score": "0.49" }, { "ref": "experts/aldo-gwerder", "score": "0.47" } ], "search": "/en/search.json" }}

apiVersion = "soultec.ch/v1"kind = "Service"[metadata]name = "backup"locale = "en"[metadata.labels]group = "infrastructure""capability/backup-recovery" = 2.14"capability/storage" = 2.36"vendor/hpe" = 1.99"vendor/veeam" = 3.03[metadata.annotations]source = "src/content/services/en/backup.md"route = "/en/services/backup/"schema = "/nerd/schema/services.json"markdown = "/en/services/backup.md"[spec]title = "Backup"group = "infrastructure"audience = ["enterprise", "provider"]order = 6tags = ["backup-recovery", "storage"]vendors = ["hpe", "veeam"]summary = "Backed up to 3-2-1-1-0, on immutable storage. The backup estate should be the equal of the primary one, and rarely is."photo = "rack-proliant-dl360"photoNeed = "A restore actually being tested: the screen showing a running restore job, with someone watching it rather than starting it"stub = falsedraft = false[[spec.sections]]heading = "

The standard

"body = '''Highly available production infrastructure is normal now. Backup infrastructure much lessso, even though in a real incident it is the only one that still counts. It should be theequal of the primary: secure, fast, solid, scalable.'''[[spec.sections]]heading = "

3-2-1-1-0

"body = '''Three copies, on two kinds of media, one of them off site, one of them immutable, and zeroerrors on the restore test. The last two digits are the ones missing in practice.**Immutable** is the answer to ransomware. A backup an attacker can delete with the samecredentials that reach production is not a backup at the moment it matters.**Zero** means tested. A backup whose restore has never been exercised is an assumption.'''[[spec.sections]]heading = "

What it protects against

"body = '''Against deleted data, by users as much as by attackers. Against hardware failure. Againstinsiders. And against the loss of a whole data centre site, which is rare and takeseverything else with it at the same time.'''[[spec.sections]]heading = "

How we build it

"body = '''To your requirements, with products that complement each other rather than overlap. Dailyoperation stays simple: restores, checks and expansions without specialist knowledge.The measure is the RPO and RTO from the requirements. The backup storage and the backupserver are sized against them, because a restore that misses the deadline is not one.Offloading backup data to the cloud runs on S3 object storage, stored immutably.'''[status]corpus = 315search = "/en/search.json"[[status.solutions]]ref = "solutions/hpe/hpe-storage/hpe-storeonce"score = "1.00"[[status.solutions]]ref = "solutions/hpe"score = "0.61"[[status.solutions]]ref = "solutions/hpe/hpe-dhci"score = "0.58"[[status.solutions]]ref = "solutions/hpe/hpe-storage/alletra-storage-mp-b10000"score = "0.52"[[status.alsoLike]]ref = "posts/how-to-deploy-vsan-snapshot-service-appliance"score = "0.70"[[status.alsoLike]]ref = "posts/raid-controller"score = "0.67"[[status.alsoLike]]ref = "services/managed-object-storage"score = "0.59"[[status.experts]]ref = "experts/rico-lenherr"score = "0.54"[[status.experts]]ref = "experts/marco-betschart"score = "0.49"[[status.experts]]ref = "experts/aldo-gwerder"score = "0.47"

<?xml version="1.0" encoding="UTF-8"?><manifest kind="Service"> <apiVersion>soultec.ch/v1</apiVersion> <metadata> <name>backup</name> <locale>en</locale> <labels> <group>infrastructure</group> <entry key="capability/backup-recovery">2.14</entry> <entry key="capability/storage">2.36</entry> <entry key="vendor/hpe">1.99</entry> <entry key="vendor/veeam">3.03</entry> </labels> <annotations> <source>src/content/services/en/backup.md</source> <route>/en/services/backup/</route> <schema>/nerd/schema/services.json</schema> <markdown>/en/services/backup.md</markdown> </annotations> </metadata> <spec> <title>Backup</title> <group>infrastructure</group> <audience> <item>enterprise</item> <item>provider</item> </audience> <order>6</order> <tags> <item>backup-recovery</item> <item>storage</item> </tags> <vendors> <item>hpe</item> <item>veeam</item> </vendors> <summary>Backed up to 3-2-1-1-0, on immutable storage. The backup estate should be the equal of the primary one, and rarely is.</summary> <photo>rack-proliant-dl360</photo> <photoNeed>A restore actually being tested: the screen showing a running restore job, with someone watching it rather than starting it</photoNeed> <stub>false</stub> <draft>false</draft> <sections> <section> <heading>

The standard

</heading> <body>Highly available production infrastructure is normal now. Backup infrastructure much lessso, even though in a real incident it is the only one that still counts. It should be theequal of the primary: secure, fast, solid, scalable. </body> </section> <section> <heading>

3-2-1-1-0

</heading> <body>Three copies, on two kinds of media, one of them off site, one of them immutable, and zeroerrors on the restore test. The last two digits are the ones missing in practice.**Immutable** is the answer to ransomware. A backup an attacker can delete with the samecredentials that reach production is not a backup at the moment it matters.**Zero** means tested. A backup whose restore has never been exercised is an assumption. </body> </section> <section> <heading>

What it protects against

</heading> <body>Against deleted data, by users as much as by attackers. Against hardware failure. Againstinsiders. And against the loss of a whole data centre site, which is rare and takeseverything else with it at the same time. </body> </section> <section> <heading>

How we build it

</heading> <body>To your requirements, with products that complement each other rather than overlap. Dailyoperation stays simple: restores, checks and expansions without specialist knowledge.The measure is the RPO and RTO from the requirements. The backup storage and the backupserver are sized against them, because a restore that misses the deadline is not one.Offloading backup data to the cloud runs on S3 object storage, stored immutably. </body> </section> </sections> </spec> <status> <corpus>315</corpus> <solutions> <item> <ref>solutions/hpe/hpe-storage/hpe-storeonce</ref> <score>1.00</score> </item> <item> <ref>solutions/hpe</ref> <score>0.61</score> </item> <item> <ref>solutions/hpe/hpe-dhci</ref> <score>0.58</score> </item> <item> <ref>solutions/hpe/hpe-storage/alletra-storage-mp-b10000</ref> <score>0.52</score> </item> </solutions> <alsoLike> <item> <ref>posts/how-to-deploy-vsan-snapshot-service-appliance</ref> <score>0.70</score> </item> <item> <ref>posts/raid-controller</ref> <score>0.67</score> </item> <item> <ref>services/managed-object-storage</ref> <score>0.59</score> </item> </alsoLike> <experts> <item> <ref>experts/rico-lenherr</ref> <score>0.54</score> </item> <item> <ref>experts/marco-betschart</ref> <score>0.49</score> </item> <item> <ref>experts/aldo-gwerder</ref> <score>0.47</score> </item> </experts> <search>/en/search.json</search> </status></manifest>

# Code generated by the soultec.ch build. DO NOT EDIT.import jsonPAGE = { "apiVersion": "soultec.ch/v1", "kind": "Service", "metadata": { "name": "backup", "locale": "en", "labels": { "group": "infrastructure", "capability/backup-recovery": 2.14, "capability/storage": 2.36, "vendor/hpe": 1.99, "vendor/veeam": 3.03, }, "annotations": { "source": "src/content/services/en/backup.md", "route": "/en/services/backup/", "schema": "/nerd/schema/services.json", "markdown": "/en/services/backup.md", }, }, "spec": { "title": "Backup", "group": "infrastructure", "audience": ["enterprise", "provider"], "order": 6, "tags": ["backup-recovery", "storage"], "vendors": ["hpe", "veeam"], "summary": "Backed up to 3-2-1-1-0, on immutable storage. The backup estate should be the equal of the primary one, and rarely is.", "photo": "rack-proliant-dl360", "photoNeed": "A restore actually being tested: the screen showing a running restore job, with someone watching it rather than starting it", "stub": False, "draft": False, "sections": [ { "heading": "

The standard

", "body": ( "Highly available production infrastructure is normal now. Backup infrastructure much less\n" "so, even though in a real incident it is the only one that still counts. It should be the\n" "equal of the primary: secure, fast, solid, scalable." ), }, { "heading": "

3-2-1-1-0

", "body": ( "Three copies, on two kinds of media, one of them off site, one of them immutable, and zero\n" "errors on the restore test. The last two digits are the ones missing in practice.\n" "\n" "**Immutable** is the answer to ransomware. A backup an attacker can delete with the same\n" "credentials that reach production is not a backup at the moment it matters.\n" "\n" "**Zero** means tested. A backup whose restore has never been exercised is an assumption." ), }, { "heading": "

What it protects against

", "body": ( "Against deleted data, by users as much as by attackers. Against hardware failure. Against\n" "insiders. And against the loss of a whole data centre site, which is rare and takes\n" "everything else with it at the same time." ), }, { "heading": "

How we build it

", "body": ( "To your requirements, with products that complement each other rather than overlap. Daily\n" "operation stays simple: restores, checks and expansions without specialist knowledge.\n" "\n" "The measure is the RPO and RTO from the requirements. The backup storage and the backup\n" "server are sized against them, because a restore that misses the deadline is not one.\n" "Offloading backup data to the cloud runs on S3 object storage, stored immutably." ), }, ], }, "status": { "corpus": 315, "solutions": [ { "ref": "solutions/hpe/hpe-storage/hpe-storeonce", "score": "1.00", }, { "ref": "solutions/hpe", "score": "0.61", }, { "ref": "solutions/hpe/hpe-dhci", "score": "0.58", }, { "ref": "solutions/hpe/hpe-storage/alletra-storage-mp-b10000", "score": "0.52", }, ], "alsoLike": [ { "ref": "posts/how-to-deploy-vsan-snapshot-service-appliance", "score": "0.70", }, { "ref": "posts/raid-controller", "score": "0.67", }, { "ref": "services/managed-object-storage", "score": "0.59", }, ], "experts": [ { "ref": "experts/rico-lenherr", "score": "0.54", }, { "ref": "experts/marco-betschart", "score": "0.49", }, { "ref": "experts/aldo-gwerder", "score": "0.47", }, ], "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 = 'Service' metadata = [ordered]@{ name = 'backup' locale = 'en' labels = [ordered]@{ group = 'infrastructure' 'capability/backup-recovery' = 2.14 'capability/storage' = 2.36 'vendor/hpe' = 1.99 'vendor/veeam' = 3.03 } annotations = [ordered]@{ source = 'src/content/services/en/backup.md' route = '/en/services/backup/' schema = '/nerd/schema/services.json' markdown = '/en/services/backup.md' } } spec = [ordered]@{ title = 'Backup' group = 'infrastructure' audience = @('enterprise', 'provider') order = 6 tags = @('backup-recovery', 'storage') vendors = @('hpe', 'veeam') summary = 'Backed up to 3-2-1-1-0, on immutable storage. The backup estate should be the equal of the primary one, and rarely is.' photo = 'rack-proliant-dl360' photoNeed = 'A restore actually being tested: the screen showing a running restore job, with someone watching it rather than starting it' stub = $false draft = $false sections = @( [ordered]@{ heading = '

The standard

' body = @'Highly available production infrastructure is normal now. Backup infrastructure much lessso, even though in a real incident it is the only one that still counts. It should be theequal of the primary: secure, fast, solid, scalable.'@ } [ordered]@{ heading = '

3-2-1-1-0

' body = @'Three copies, on two kinds of media, one of them off site, one of them immutable, and zeroerrors on the restore test. The last two digits are the ones missing in practice.**Immutable** is the answer to ransomware. A backup an attacker can delete with the samecredentials that reach production is not a backup at the moment it matters.**Zero** means tested. A backup whose restore has never been exercised is an assumption.'@ } [ordered]@{ heading = '

What it protects against

' body = @'Against deleted data, by users as much as by attackers. Against hardware failure. Againstinsiders. And against the loss of a whole data centre site, which is rare and takeseverything else with it at the same time.'@ } [ordered]@{ heading = '

How we build it

' body = @'To your requirements, with products that complement each other rather than overlap. Dailyoperation stays simple: restores, checks and expansions without specialist knowledge.The measure is the RPO and RTO from the requirements. The backup storage and the backupserver are sized against them, because a restore that misses the deadline is not one.Offloading backup data to the cloud runs on S3 object storage, stored immutably.'@ } ) } status = [ordered]@{ corpus = 315 solutions = @( [ordered]@{ ref = 'solutions/hpe/hpe-storage/hpe-storeonce' score = '1.00' } [ordered]@{ ref = 'solutions/hpe' score = '0.61' } [ordered]@{ ref = 'solutions/hpe/hpe-dhci' score = '0.58' } [ordered]@{ ref = 'solutions/hpe/hpe-storage/alletra-storage-mp-b10000' score = '0.52' } ) alsoLike = @( [ordered]@{ ref = 'posts/how-to-deploy-vsan-snapshot-service-appliance' score = '0.70' } [ordered]@{ ref = 'posts/raid-controller' score = '0.67' } [ordered]@{ ref = 'services/managed-object-storage' score = '0.59' } ) experts = @( [ordered]@{ ref = 'experts/rico-lenherr' score = '0.54' } [ordered]@{ ref = 'experts/marco-betschart' score = '0.49' } [ordered]@{ ref = 'experts/aldo-gwerder' score = '0.47' } ) 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": "Service", "metadata": map[string]any{ "name": "backup", "locale": "en", "labels": map[string]any{ "group": "infrastructure", "capability/backup-recovery": 2.14, "capability/storage": 2.36, "vendor/hpe": 1.99, "vendor/veeam": 3.03, }, "annotations": map[string]any{ "source": "src/content/services/en/backup.md", "route": "/en/services/backup/", "schema": "/nerd/schema/services.json", "markdown": "/en/services/backup.md", }, }, "spec": map[string]any{ "title": "Backup", "group": "infrastructure", "audience": []any{"enterprise", "provider"}, "order": 6, "tags": []any{"backup-recovery", "storage"}, "vendors": []any{"hpe", "veeam"}, "summary": "Backed up to 3-2-1-1-0, on immutable storage. The backup estate should be the equal of the primary one, and rarely is.", "photo": "rack-proliant-dl360", "photoNeed": "A restore actually being tested: the screen showing a running restore job, with someone watching it rather than starting it", "stub": false, "draft": false, "sections": []any{ map[string]any{ "heading": "

The standard

", "body": "Highly available production infrastructure is normal now. Backup infrastructure much less\n" + "so, even though in a real incident it is the only one that still counts. It should be the\n" + "equal of the primary: secure, fast, solid, scalable.", }, map[string]any{ "heading": "

3-2-1-1-0

", "body": "Three copies, on two kinds of media, one of them off site, one of them immutable, and zero\n" + "errors on the restore test. The last two digits are the ones missing in practice.\n" + "\n" + "**Immutable** is the answer to ransomware. A backup an attacker can delete with the same\n" + "credentials that reach production is not a backup at the moment it matters.\n" + "\n" + "**Zero** means tested. A backup whose restore has never been exercised is an assumption.", }, map[string]any{ "heading": "

What it protects against

", "body": "Against deleted data, by users as much as by attackers. Against hardware failure. Against\n" + "insiders. And against the loss of a whole data centre site, which is rare and takes\n" + "everything else with it at the same time.", }, map[string]any{ "heading": "

How we build it

", "body": "To your requirements, with products that complement each other rather than overlap. Daily\n" + "operation stays simple: restores, checks and expansions without specialist knowledge.\n" + "\n" + "The measure is the RPO and RTO from the requirements. The backup storage and the backup\n" + "server are sized against them, because a restore that misses the deadline is not one.\n" + "Offloading backup data to the cloud runs on S3 object storage, stored immutably.", }, }, }, "status": map[string]any{ "corpus": 315, "solutions": []any{ map[string]any{ "ref": "solutions/hpe/hpe-storage/hpe-storeonce", "score": "1.00", }, map[string]any{ "ref": "solutions/hpe", "score": "0.61", }, map[string]any{ "ref": "solutions/hpe/hpe-dhci", "score": "0.58", }, map[string]any{ "ref": "solutions/hpe/hpe-storage/alletra-storage-mp-b10000", "score": "0.52", }, }, "alsoLike": []any{ map[string]any{ "ref": "posts/how-to-deploy-vsan-snapshot-service-appliance", "score": "0.70", }, map[string]any{ "ref": "posts/raid-controller", "score": "0.67", }, map[string]any{ "ref": "services/managed-object-storage", "score": "0.59", }, }, "experts": []any{ map[string]any{ "ref": "experts/rico-lenherr", "score": "0.54", }, map[string]any{ "ref": "experts/marco-betschart", "score": "0.49", }, map[string]any{ "ref": "experts/aldo-gwerder", "score": "0.47", }, }, "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: "Service", metadata: { name: "backup", locale: "en", labels: { group: "infrastructure", "capability/backup-recovery": 2.14, "capability/storage": 2.36, "vendor/hpe": 1.99, "vendor/veeam": 3.03, }, annotations: { source: "src/content/services/en/backup.md", route: "/en/services/backup/", schema: "/nerd/schema/services.json", markdown: "/en/services/backup.md", }, }, spec: { title: "Backup", group: "infrastructure", audience: ["enterprise", "provider"], order: 6, tags: ["backup-recovery", "storage"], vendors: ["hpe", "veeam"], summary: "Backed up to 3-2-1-1-0, on immutable storage. The backup estate should be the equal of the primary one, and rarely is.", photo: "rack-proliant-dl360", photoNeed: "A restore actually being tested: the screen showing a running restore job, with someone watching it rather than starting it", stub: false, draft: false, sections: [ { heading: "

The standard

", body: "Highly available production infrastructure is normal now. Backup infrastructure much less\n" + "so, even though in a real incident it is the only one that still counts. It should be the\n" + "equal of the primary: secure, fast, solid, scalable.", }, { heading: "

3-2-1-1-0

", body: "Three copies, on two kinds of media, one of them off site, one of them immutable, and zero\n" + "errors on the restore test. The last two digits are the ones missing in practice.\n" + "\n" + "**Immutable** is the answer to ransomware. A backup an attacker can delete with the same\n" + "credentials that reach production is not a backup at the moment it matters.\n" + "\n" + "**Zero** means tested. A backup whose restore has never been exercised is an assumption.", }, { heading: "

What it protects against

", body: "Against deleted data, by users as much as by attackers. Against hardware failure. Against\n" + "insiders. And against the loss of a whole data centre site, which is rare and takes\n" + "everything else with it at the same time.", }, { heading: "

How we build it

", body: "To your requirements, with products that complement each other rather than overlap. Daily\n" + "operation stays simple: restores, checks and expansions without specialist knowledge.\n" + "\n" + "The measure is the RPO and RTO from the requirements. The backup storage and the backup\n" + "server are sized against them, because a restore that misses the deadline is not one.\n" + "Offloading backup data to the cloud runs on S3 object storage, stored immutably.", }, ], }, status: { corpus: 315, solutions: [ { ref: "solutions/hpe/hpe-storage/hpe-storeonce", score: "1.00", }, { ref: "solutions/hpe", score: "0.61", }, { ref: "solutions/hpe/hpe-dhci", score: "0.58", }, { ref: "solutions/hpe/hpe-storage/alletra-storage-mp-b10000", score: "0.52", }, ], alsoLike: [ { ref: "posts/how-to-deploy-vsan-snapshot-service-appliance", score: "0.70", }, { ref: "posts/raid-controller", score: "0.67", }, { ref: "services/managed-object-storage", score: "0.59", }, ], experts: [ { ref: "experts/rico-lenherr", score: "0.54", }, { ref: "experts/marco-betschart", score: "0.49", }, { ref: "experts/aldo-gwerder", score: "0.47", }, ], search: "/en/search.json", },};console.log(JSON.stringify(page, null, 2));

# 76 lines · YAML · validated at build# 111 lines · JSON · validated at build# 115 lines · TOML · validated at build# 134 lines · XML · validated at build# 131 lines · Python · read back at build, equals the JSON record# 128 lines · PowerShell · read back at build, equals the JSON record# 135 lines · Go · read back at build, equals the JSON record# 120 lines · JavaScript · read back at build, equals the JSON record · served at /en/services/backup.md

Service · infrastructure

Backup

Backed up to 3-2-1-1-0, on immutable storage. The backup estate should be the equal of the primary one, and rarely is.

Topics Backup and Recovery 2.14 Storage 2.36

Vendors HPE 1.99 Veeam 3.03

04Solutions

02Capabilities

02Vendors

315Corpus

HPE ProLiant DL360 Gen10 servers in a rack, front panels and status LEDs

The standard

Highly available production infrastructure is normal now. Backup infrastructure much less so, even though in a real incident it is the only one that still counts. It should be the equal of the primary: secure, fast, solid, scalable.

3-2-1-1-0

Three copies, on two kinds of media, one of them off site, one of them immutable, and zero errors on the restore test. The last two digits are the ones missing in practice.

Immutable is the answer to ransomware. A backup an attacker can delete with the same credentials that reach production is not a backup at the moment it matters.

Zero means tested. A backup whose restore has never been exercised is an assumption.

What it protects against

Against deleted data, by users as much as by attackers. Against hardware failure. Against insiders. And against the loss of a whole data centre site, which is rare and takes everything else with it at the same time.

How we build it

To your requirements, with products that complement each other rather than overlap. Daily operation stays simple: restores, checks and expansions without specialist knowledge.

The measure is the RPO and RTO from the requirements. The backup storage and the backup server are sized against them, because a restore that misses the deadline is not one. Offloading backup data to the cloud runs on S3 object storage, stored immutably.