build 001f4800 | content blog-content@c8490fa · 338 posts | profiles 20 · corpus 232 | 0 skipped |
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 capabilities · idf weight Backup and Recovery backup-recovery 2.53 Storage storage 2.53
Vendors vendors · idf weight HPE hpe 2.45 Veeam veeam 4.08
04Solutions
02Capabilities
02Vendors
232Corpus

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.

Experts for this

Focus areas are not yet confirmed, so nobody is suggested here automatically. · 0 experts in corpus (n=232)

You might also like

post 0.70

vSAN Snapshot Service Appliance for vSAN Data Protection

0.7 × caps 1 + 0.3 × vendor 0 = 0.7
post 0.65

RAID controllers

0.7 × caps 0.5 + 0.3 × vendor 1 = 0.65
service 0.51

Storage

0.7 × caps 0.29 + 0.3 × vendor 1 = 0.51