DE · EN

Call us

apiVersion: soultec.ch/v1kind: Servicemetadata: name: backup locale: en labels: group: infrastructure capability/backup-recovery: 2.18 capability/storage: 2.62 vendor/hpe: 2.04 vendor/veeam: 4.22 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 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:

How we build it

body: | To your requirements, with products that complement each other rather than overlap. For all the engineering behind it, daily operation has to stay simple, because a procedure that is tedious day to day gets worked around.status: corpus: 267 solutions: - {ref: solutions/hpe, score: 0.61} - {ref: solutions/hpe/hpe-dhci, score: 0.60} - {ref: solutions/hpe/hpe-data-management, score: 0.54} - {ref: solutions/hpe/hpe-storage, score: 0.54} alsoLike: - {ref: posts/how-to-deploy-vsan-snapshot-service-appliance, score: 0.70} - {ref: posts/raid-controller, score: 0.68} - {ref: services/storage, score: 0.54} experts: - {ref: experts/marco-betschart, score: 0.39} - {ref: experts/rico-lenherr, score: 0.39} - {ref: experts/marco-mattei, score: 0.35}

{ "apiVersion": "soultec.ch/v1", "kind": "Service", "metadata": { "name": "backup", "locale": "en", "labels": { "group": "infrastructure", "capability/backup-recovery": "2.18", "capability/storage": "2.62", "vendor/hpe": "2.04", "vendor/veeam": "4.22" }, "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", "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": "

How we build it

", "body": "To your requirements, with products that complement each other rather than overlap. For all\nthe engineering behind it, daily operation has to stay simple, because a procedure that is\ntedious day to day gets worked around." } ], "status": { "corpus": 267, "solutions": [ { "ref": "solutions/hpe", "score": "0.61" }, { "ref": "solutions/hpe/hpe-dhci", "score": "0.60" }, { "ref": "solutions/hpe/hpe-data-management", "score": "0.54" }, { "ref": "solutions/hpe/hpe-storage", "score": "0.54" } ], "alsoLike": [ { "ref": "posts/how-to-deploy-vsan-snapshot-service-appliance", "score": "0.70" }, { "ref": "posts/raid-controller", "score": "0.68" }, { "ref": "services/storage", "score": "0.54" } ], "experts": [ { "ref": "experts/marco-betschart", "score": "0.39" }, { "ref": "experts/rico-lenherr", "score": "0.39" }, { "ref": "experts/marco-mattei", "score": "0.35" } ] }}

apiVersion = "soultec.ch/v1"kind = "Service"[metadata]name = "backup"locale = "en"[metadata.labels]group = "infrastructure""capability/backup-recovery" = "2.18""capability/storage" = "2.62""vendor/hpe" = "2.04""vendor/veeam" = "4.22"[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"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[[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.'''[[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.'''[[sections]]heading = "

How we build it

"body = '''To your requirements, with products that complement each other rather than overlap. For allthe engineering behind it, daily operation has to stay simple, because a procedure that istedious day to day gets worked around.'''[status]corpus = 267[[status.solutions]]ref = "solutions/hpe"score = "0.61"[[status.solutions]]ref = "solutions/hpe/hpe-dhci"score = "0.60"[[status.solutions]]ref = "solutions/hpe/hpe-data-management"score = "0.54"[[status.solutions]]ref = "solutions/hpe/hpe-storage"score = "0.54"[[status.alsoLike]]ref = "posts/how-to-deploy-vsan-snapshot-service-appliance"score = "0.70"[[status.alsoLike]]ref = "posts/raid-controller"score = "0.68"[[status.alsoLike]]ref = "services/storage"score = "0.54"[[status.experts]]ref = "experts/marco-betschart"score = "0.39"[[status.experts]]ref = "experts/rico-lenherr"score = "0.39"[[status.experts]]ref = "experts/marco-mattei"score = "0.35"

<?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.18</entry> <entry key="capability/storage">2.62</entry> <entry key="vendor/hpe">2.04</entry> <entry key="vendor/veeam">4.22</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> <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> </spec> <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>

How we build it

</heading> <body>To your requirements, with products that complement each other rather than overlap. For allthe engineering behind it, daily operation has to stay simple, because a procedure that istedious day to day gets worked around. </body> </section> </sections> <status> <corpus>267</corpus> <solutions> <item> <ref>solutions/hpe</ref> <score>0.61</score> </item> <item> <ref>solutions/hpe/hpe-dhci</ref> <score>0.60</score> </item> <item> <ref>solutions/hpe/hpe-data-management</ref> <score>0.54</score> </item> <item> <ref>solutions/hpe/hpe-storage</ref> <score>0.54</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.68</score> </item> <item> <ref>services/storage</ref> <score>0.54</score> </item> </alsoLike> <experts> <item> <ref>experts/marco-betschart</ref> <score>0.39</score> </item> <item> <ref>experts/rico-lenherr</ref> <score>0.39</score> </item> <item> <ref>experts/marco-mattei</ref> <score>0.35</score> </item> </experts> </status></manifest>

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.18 Storage 2.62

Vendors HPE 2.04 Veeam 4.22

04Solutions

02Capabilities

02Vendors

267Corpus

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.

How we build it

To your requirements, with products that complement each other rather than overlap. For all the engineering behind it, daily operation has to stay simple, because a procedure that is tedious day to day gets worked around.