15 ms·
The 3-2-1 Backup Rule – Why Your Data Will Always Survive (2019)
- superjan 5y agoThe article glosses over one thing: you should have at least one backup that is not accessible through the company network. A different site connected to the same network is accessible by ransomware gangs once they are in.
- dredmorbius 5y agoThis is pretty much precisely how Maersk recovered from the NotPetya worm attack, though the circumstances were serendiptous rather than planned: ... After a frantic search that entailed calling hundreds of IT admins in data centers around the world, Maersk’s desperate administrators finally found one lone surviving domain controller in a remote office—in Ghana. At some point before NotPetya struck, a blackout had knocked the Ghanaian machine offline, and the computer remained disconnected from the network. It thus contained the singular known copy of the company’s domain controller data left untouched by the malware—all thanks to a power outage. “There were a lot of joyous whoops in the office when we found it,” a Maersk administrator says. When the tense engineers in Maidenhead set up a connection to the Ghana office, however, they found its bandwidth was so thin that it would take days to transmit the several-hundred-gigabyte domain controller backup to the UK. Their next idea: put a Ghanaian staffer on the next plane to London. But none of the West African office’s employees had a British visa. So the Maidenhead operation arranged for a kind of relay race: One staffer from the Ghana office flew to Nigeria to meet another Maersk employee in the airport to hand off the very precious hard drive. That staffer then boarded the six-and-a-half-hour flight to Heathrow, carrying the keystone of Maersk’s entire recovery process. ... https://tech.industry-best-practice.com/2018/10/14/the-untold-story-of-notpetya-the-most-devastating-cyberattack-in-history/ https://tech.industry-best-practice.com/2018/10/14/the-untol...
- blakesterz 5y agoThis is from 2019, not that the advice ever goes out of date. It's crazy how the seemingly easiest most basic security/backup advice is so easy to give, and so hard to actually do. 3-2-1, so easy to teach and remember! In reality, at any kind of scale, not so easy to do. I am constantly reminded just how hard every aspect of security really is to do. Even for the little/basic stuff.
- philips 5y agoFor local documents I find it way easier than cloud stuff. 1. Local disk 2. Time machine ssd 3. Backblaze backup agent For cloud stuff the services make it so hard. I have been working on a service off and on to backup Google photos to an SD card and then mail it to folks. And the amount of limitations, rate limiting, and random errors out of Google's API can be frustrating.
- wizzwizz4 5y agoTry Google Takeout.
- philips 5y agoIt isn't automated. And in the case of the thing I am building I can't help other people because you can't delegate the creation of a takeout either.
- wizzwizz4 5y ago> you can't delegate the creation of a takeout either. Not through Google's APIs. But you can, through adversarial interoperability.
- dredmorbius 5y agoSorry?
- ghaff 5y agoAnd you can basically just as easily backup to two Time Machine drives for just a little extra piece of mind. Not sure it makes sense to use an SSD for that application though.
- deckard1 5y agoThe difficulty of 3-2-1 increases as your data size goes up. For me, the only sane thing to do is partitioning. My first group would be data that if I were to lose it would cause great pain. I keep the size of this group as small as possible. A few hundred megs or less. You have a live copy, a backup on a USB thumb stick or drive, and a copy you email someone or snail mail a USB drive. It's simple to deal with. It has to be, because it's critical. My second group is data that is important but not a serious threat to me. Photos and videos, mostly. This second group is where the headache starts and logistics, cost, and time become an issue. Offsite backup is either running to the bank deposit box (time consuming), or upload to cloud (also time consuming, and expensive). Containing the bit rot becomes a futile exercise. Especially considering most people aren't running ECC RAM and end-to-end ZFS with redundancy (for recovery) requires significant expertise and time. Parchive files are the best bet for most people. Finally, my third group. I have a NAS with a simple mirrored ZFS setup. Two huge drives. I'll probably add a 3rd drive for added redundancy. There is no backup. This data I don't care that much about. I'd hate to lose it. But I'd hate backing it up much more. I don't live for my data, my data lives for me. You have to ruthlessly prune data that you care to keep. Just like the burden of owning a boat or an overly large house, there is a burden to too much data you care about. The mistake a lot of people make is treating all data the same. Then they end up with terabytes of data of unequal importance and get sloppy protecting the tiny amount of data that truly matters.
- zinekeller 5y agoOh bother, it's down :( (edit: it might no longer) Archive links: https://web.archive.org/web/20211001064106/https://www.vmwareblog.org/3-2-1-backup-rule-data-will-always-survive/ https://web.archive.org/web/20211001064106/https://www.vmwar... https://archive.md/1jHmP https://archive.md/1jHmP
- throwaway2331 5y agoTL;DR 3-2-1: 3 backups 2 different media types 1 off-site
- tacone 5y agoLooks like they have backups :)
- throwaway2331 5y agoRecently learned this lesson. Had 2 backups (1 SD card, 1 HDD) for my "Document" folder. I was trying to replace my GRUB MBR bootloader for REFind's EFI so I could dualboot on a new laptop (and swap-in my old one's SSD without having to reinsall the whole system: Arch). Unfortunately, the boot partition was too small, and needed to be re-sized from 512MB to 1GB. Foolishly, and in a rush, I thought using gparted to change the partition boundaries (shrink the root partition by 512MB from the beginning, and stretch the boot partition to 1GB from the end) was the answer. I completely forgot that EXT4 has a superblock at the beginning, so now it was gone, and the root partition was completely unmountable -- and fsck was of no use. So I scramble to find my backups (to decide whether or not I should figure out how to fix this), and realize that tiny little SD card was missing, and my HDD backup was completely unmountable. Truly, a major fuck-up. Thankfully, I didn't write anything to the boot partition, so throwing a Hail Mary and simply resizing the partitions back to their exact original sizes (thankfully x2 my TTS history was useful), allowed the root drive to mount without a hitch. I was close to losing all of my KeepPassXC passwords and private keys due to shear idiocy. In the end, I set up "cloud" backups (second storage media type, and long and far away), switched to Debian, and continued on my merry way.
- deleted 5y ago[deleted]
- zamadatix 5y agoTo be fair I think the fuck-up was on gparted's part, it's supposed to handle this kind of thing for you during the resize. That being said no tool is ever bug free hence backups :).
- travisby 5y ago> so throwing a Hail Mary and simply resizing the partitions back to their exact original sizes I've made similar mistakes (well, the same effect, but for different reasons. I thought I was over a remote session when I was local and made an entire new partition layout). `testdisk` was able to introspect what partition boundaries _were_ and rebuild the partition table. If you're ever in a similar situation and either don't remember the exact boundaries or don't trust yourself to recreate them, check it out!
- mike_d 5y agoPeople often forget the 3-2-1 rule should also apply to the secrets you use to encrypt/store your backups. If you can't decrypt it, it isn't a backup. I use a crazy long passphrase to encrypt my backups, but should I forget - it is also printed on archival paper inside a sealed envelope in a friends safe deposit box (I also have a copy of his backup passphrase for mutually assured destruction :)). Also, every once in a while run a fire drill and actually restore something from each of your backups. This is when you find out the rsync job has been stuck for the last 80 days.
- philips 5y agoYeah the fire drill to make sure everything works is crazy important. I just wish that storing things like keys on paper was easier. At CoreOS we put some keys on printed QR codes and scanned them with an airgapped laptop every 90 days to confirm the keys were safe.
- denton-scratch 5y ago> Yeah the fire drill I agree. But I've never been allowed to run a fire drill. Rebuilding a network from bare tin is obviously expensive, but not as expensive as losing the business. And then there's the sheer stress of being responsible for the backups, but not being able to test bare-metal recovery. I'm interested in backup ("what kind of weirdo is this!"), but that wasn't a fun responsibility.
- bigiain 5y ago> But I've never been allowed to run a fire drill. Rebuilding a network from bare tin is obviously expensive, but not as expensive as losing the business. Sometime your job is not to be able to take the backups, but to take the blame when a restore can't be done. If you think that might be you, time to polish up that resume... Especially for cloud-based businesses, refusing to let you spend ~8 hours of production platform costs to run a full platform rebuild fire drill is insane, that's about 0.1% of your annual prod AWS budget, and 0.5% of you (or your team's) annual time.
- kunagi7 5y agoI learned this the hard way a few years ago. Having several drives is not enough. I used to keep my important data replicated on 3 drives, from different brands, different capacities, 1 internal, 2 external. One day the internal drive failed, the next day one of the external drives also failed. So... I panicked, shut everything down and bought a brand new hard drive (1tb). While copying from the third drive it also stopped working. So, I had a triple drive failure. I managed to recover most of my data by freezing the external drives and copying from them (until they heated up and had to freeze them again).
- H8crilA 5y agoWhat are the odds. Did you maybe bring some object with some radioactive material inside?
- kunagi7 5y agoWho knows? This happened a decade ago. Maybe it was an electric issue... But that would fry the drive's motherboard instead of making the hard drives click?
- ComputerGuru 5y agoThis may or may not be the case here, but generally speaking… Pretty high for any parity-based multi-disk system. The remaining disks get stress tested when a disk fails and you need to copy everything over to the replacement. It’s why RAID5 is no longer sufficient with today’s disk sizes and why a RAID10 (which can only lose any one disk plus a specific other disk) is actually real-world safer than RAID6 (which can lose _any_ two disks).
- seized 5y agoAlthough with RAID10, the disk that absolutely can't fail is the one under all the restore stress. And likely to be the same age as the failed disk. There is also RAIDZ3 for those who want more safety, which is ZFS triple parity.
- lloeki 5y ago
- CGamesPlay 5y agoI never really liked the 3-2-1 rule because it feels too specific: while it works, simpler solutions also provide the same level of reliability. I think about backups in terms of blast radius. 1) The local machine has the working copy of data and a local backup as permitted by free space. The smallest blast radius where I lose data is "my laptop hard drive fails". 2) My external drive has another backup. The new blast radius is "my house burns down". 3) I maintain a cloud backup. The new blast radius is "a catastrophe on a global scale". Any two of these backups can fail and the data is still salvageable.
- Someone1234 5y ago> while it works, simpler solutions also provide the same level of reliability. It exists and is important because many backup strategies are broken and people don't realize it. For example your own strategy treats a PC's local storage and an external drive as distinct backups when in reality you've only evaluated hardware failures when formulating it and not malicious actors. In 3-2-1, in particular the media type + off-site thing, tries to "trick" you into having a backup which isn't accessible from the same system that it is backing up (i.e. offline backups). Your backup strategy has been used almost verbatim by multiple institutions who got cryto-locked. The external drive was hit and then the cloud backup service happily synced the now encrypted files. They went from "backed up in three places" to backed up in zero places, and are now calling the cloud provider hoping that their backups had unencrypted copies in them. 3-2-1 isn't simple, but it is good, and that's what it tries to be.
- toastedwedge 5y agoBackup versioning is the important distinction here. A backup on its own is only good against loss, but a backup with multiple snapshots in varying states in place protects against the threat of crypto-locked cloud synchronization. Of course if the provider is locked then it's a moot point.
- Someone1234 5y agoSome backup versioning schemes are disabled on purpose by some cryto-malware.
- FullyFunctional 5y agoThe different media types is probably the hardest issue; I'd wager that for most people, backing up > 2 TB on anything but spinning rust will be impractical/prohibitively expensive. A slight twist of this: I now have data old enough that accessing it with modern computers is starting to become a challenge. Thankfully I migrated all my, once enormous collection of 50,000 MB on tape, to just be files on my file server, but I'm worried about the longevity of optical media, and now I nervously glance at my collection of even older media ....
- Someone1234 5y ago> I'd wager that for most people, backing up > 2 TB on anything but spinning rust will be impractical/prohibitively expensive. You'd lose that bet. 2 TB on LTO Ultrium tape costs under $10 (sometimes under $5 depending on volume of tapes ordered).
- Denvercoder9 5y agoAnd how much for the tape machine?
- Someone1234 5y agoThe person above was talking about the cost of HDDs, they didn't include the cost of a machine or NAS to run them in so why should I? Seems like a double standard wherein people are going to pretend housing multiple HDDs costs $0 (unrealistic) but won't even evaluate spending money on a tape drive. You what doesn't get cryptolockered? Yesterday's tape sitting on the shelf.
- Denvercoder9 5y agoBecause we're talking about most people, and most people already have a machine into which they can plug a HDD. Often that's the very machine with the documents they want to backup.
- wongarsu 5y ago
- H8crilA 5y agoWhat's the cloud solution (at major providers) that automatically geographically replicates data? For example, S3 buckets are tied to a region, which cannot be considered reliable - a single DC can always burn down, or even just intermittently unreachable. I'm looking for something that accepts an "upload" command that will (eventually) replicate the data to several regions. Ideally the regions can be changed at any point later, too. This would take care of 3 and 1, sadly not 2 but 2 is pretty hard.
- gnur 5y agoS3 is region based, not AZ based. So it should be able to tolerate an entire AZ (=DC) being lost. They offer an amazing number of 9s for durability, it is very unlikely that a single fire will cause harm to your data.
- H8crilA 5y agoYeah, OK. But apart from the reliability question - what's a one stop shop for uploading files to Europe and the US in one go?
- seized 5y agoFor AWS there are options but require setup. It's not exactly one click setup and can be quite complex depending on your skill level. https://docs.aws.amazon.com/AmazonS3/latest/userguide/replication.html#crr-scenario https://docs.aws.amazon.com/AmazonS3/latest/userguide/replic... https://aws.amazon.com/blogs/aws/new-cross-region-replication-for-amazon-s3/ https://aws.amazon.com/blogs/aws/new-cross-region-replicatio...
- Heliosmaster 5y agoI can't find the article anymore, but a few weeks ago here on HN there was a piece where somebody did a few calculations on how AWS US-East-1 (the most used AWS region in the world) works, and got to the conclusion that all the things that can make that region go BOOM are likely to have major consequences to our civilization. In short: AWS will go down only when you won't care about it anyway
- scrooched_moose 5y agoAre there guidelines for how long a given type of media is considered stable? From experience, hard drives seem safe on the order of years; I've spun drives back up from the early 2000s and they are fully intact. The lifespan of burned optical media is/was counted in minutes. Various flash memory is somewhere in between - I've had all kinda of cheap flash drives die. Even with the multiple media forms they need to be refreshed at some frequency, and I don't know how often that should be.
- gregsadetsky 5y agoI see a lot of results on google for "data storage lifespan" Trying to find an authorative source (loc.gov, archive.org, etc.), I found this, which is not a full answer, but gets into interesting details: "Table 2 - the relative stability of optical disc formats" [0] -- from >100 years down to ... 5-10! [0] https://www.canada.ca/en/conservation-institute/services/conservation-preservation-publications/canadian-conservation-institute-notes/longevity-recordable-cds-dvds.html#t2 https://www.canada.ca/en/conservation-institute/services/con...
- ComputerGuru 5y agoWe’ve come a long way since CD-R; I said this earlier but I guess it’s worth copy-and-pasting here: > There are Blu-ray Discs specifically engineered for long-term archiving and have BER guarantees (anomalous bit read per gb of data stored per year archived or something). Now these are obviously simulated numbers (the tech isn’t even old enough to test) but it’s a start: it means people are at least considering the right questions. I wouldn’t write sensitive to a Blu-ray directly unless it was the kind of data where a bit-flip is not a huge deal (eg a backup of users’ profile images where there are many small files, a bit flip affects the content but doesn’t compromise the overall data, errors aren’t cascading, etc). There’s already bit error correction baked into the analog <-> digital transition layer but it’s not great - but fortunately efficient bit error correction at the file level has been a thing since before binaries on Usenet. Stick some PAR2 files on the Blu-ray or even serve your backup as a Blu-ray Disc plus a DVD-R stuffed to the brim with PAR2 data for the former (I prefer the first approach).
- denton-scratch 5y agoAs far as I can see, this scheme gives you one backup copied to three places, on two different media. What if the source for the backup was already corrupt or broken in some way? If you only have one backup, then your backup is corrupt too. I was taught grandfather-father-son back in the 80s; still three levels of backup, but they're different generations. That fitted the kinds of media available then, but it doesn't really map to modern equipment. I've struggled to work out a backup scheme that is equally adaptable to the needs of a small business, a home network or an individual. Ironically, it's hardest for the individual; a modern business is finished if it loses all its data. For an individual (or even a hobby network), total data-loss is painful, but not usually an existential risk. So it's harder to justify keeping everything in triplicate.
- gsich 5y agoFor source integrity there are other methods available. Checksums, parity, RAID. I don't see this as a backup problem.
- denton-scratch 5y agoThose are checks of binary integrity. They can't confirm that data hasn't been deliberately or accidentally replaced, added or deleted. I would like to have a grandfather, a week old; a father, a day old; and a son, being last night's backup. All on different media, amd ideally not connected to the source machine.
- gsich 5y agoThis is not a backup problem.
- syshum 5y agoit absolutely is a backup problem Ransomware is the #1 thing an enterprise will use a Backup to recover from, the second most common is accidentally deletion. Binary corruption is very very very very very rare and with all the systems in place to prevent it, is not even something I even think about anymore. I worry about Ransomware, and users doing stupid things
- oblib 5y agoI've added offline/local-first to my web app so users to keep a copy and backups of all of their data on site and use the app offline but none of them want to do anything at all to implement it, and I've made very easy. They really don't seem to give it any thought at all, even when I explain to them why they need to do this. Conversely, when they're having network connection issues they don't hesitate to call me, and sometimes in a panic. I'm going to keep pushing them to get on it on their end though.
- throw7 5y agoI think actually physically going through your disaster recovery plan (whatever that would be, 321 or not) reveals how good/bad your backup plan is for you. Personally, I downsized. I made peace with myself that I can live without the gobsmack amount of data I have if it were to be lost tomorrow. I pared down to a small set of data (less than 1GB) that is critical to me. That data is synced to various devices with syncthing (includes even my cellphone!), and then I use restic to two different cloud storage providers. When I'm bored I do an independent, standalone export from cloud storage.
- dharmab 5y agoI did the same with two tiers- a first tier of the data I would need for a true disaster (a few GB), and a second tier of data that is meaningful and difficult to replace (small enough to fit on a flash drive). Everything else is dust in the wind.
- slownews45 5y agoSame here. Since I "restore" this backup pretty frequently just for day to day living (ie, doing taxes) I'm also pretty sure it's accessible. I do pay for versioning for the online sync of this, and I do a period S3 object lock copy (30 days). For me, that's good enough.
- jimmySixDOF 5y agoFunny Story. My first service order way back when was to a engineering office who were in a panic because their primary CAD file server had failed right in the middle of a deadline submittal. I got there when they had just pulled out an identical file server from some other department. They had 'everything' backed up nightly on to a Zip drive. Nice, I thought. So, I plug in the Zip drive and can see all these image files created by their backup software. I ask for the backup app install files and they say its kept in a directory -- on the failed server !!! I should mention this was not in the USA and resulted in a 6+hr long international 42kbps zmodem download session from some random BBS server of the best guess software product and version. I still have one of the failed HDDs from that server as a paper weight on my desk. PS. We got it working in time and the obvious moral of the story is to always test your backup systems (and that goes for both failover and fallback)
- gerdesj 5y agoEvery couple of weeks, I or a colleague wander into our bijou data centre. We turn the power off. The UPSs beep for 10 seconds and the genny fires up. A couple of SMSs land on several mobiles and a Teams channel gets notified. Icinga2 notes the power is up but provided by the genny. I particularly like to do this when showing someone around. You whitter on about power and then you swiftly turn the key on the distribution panel and it makes a satisfying clunk. The status lights switch around and the UPSs start beeping. Then they stop. There is a barely perceptible hum from the genny in the boiler room, three walls (one of them a firewall in the traditional sense) away. It is extremely satisfying to do and customers appreciate it - they have all jumped a bit when they first see it. The UPSs obviously (monitored and fortnightly tested) have enough runtime to switch back if something fails on the genny. At a second location there is just enough IT gear to run my company for a while. Replication via Veeam - 'nuff said. Every couple of weeks, Veeam fires up a small part of my company's IT from backups/replicas at the second location. It runs some scripts which tests some functionality and sends out some status reports via email. I still worry about business continuity. There is way more to it than just backups. However, get backups sorted out first. Nine months back a customer had a fire on the production floor. They are still running out of our place, 50 miles away. We set up offsite backups to our place only the week before: "There but for the Grace of God, go I" etc etc. I had them up and running inside three hours from a standing start. Rather lucky there really - they have a functioning business and I have a success story rather than a potential lawsuit from an ex-customer's liquidators trying to claw back some loot.
- douglee650 5y agoIs that 3 copies per each of the 2 media, ie 6 copies?
- petilon 5y agoThis 3-2-1 backup strategy is missing a dimension: time. Data is rarely unchanging. The 3-2-1 strategy is inadequate for changing data, because if you delete the wrong database table and didn't realize it, the 3-2-1 backups are going to be missing the table too. You need to add the time dimension and have a monthly snapshot for data that is older than a year, weekly snapshot for data within last 1 year, and daily snapshot for the last 90 days.
- SOMA_BOFH 5y agoYes, and validation as well. If backups are not tested by actually retrieving data on a regular basis, you might get a nasty surprise. The Legato NetWorker bug which resulted in 64 bit XFS inodes not getting backed up bit Pixar very hard back in the day (LGTpa40680).
- timdavila 5y agoHow does everyone back up their iDevices? Every article I read talks about iCloud, which is great and I use, but doesn’t follow this principle and you’re out of luck if you lose access to your Apple ID. I’ve found some content specific solutions that will backup photos or contacts for example, but I’m looking for a fairly streamlined comprehensive solution that would back up everything-messages, contacts, photos, emails, bookmarks, basically iCloud 2 but without the Apple lock in.
- colejohnson66 5y agoYou can always plug into your computer and use iTunes for a local backup. Not elegant, but it’s still there for those who want it.
- btgeekboy 5y agoI basically don’t, at least not at the device level. Photos get synced to my home server using PhotoSync every once in a while (manually, but eh, it works). Texts are backed up on my laptop technically, but I pretty much consider them ephemeral. I don’t really care about bookmarks, and everything else on that list is cloud-first.
- crossroadsguy 5y agoThere’s another backup rule that is largely skipped (especially in personal backup space): “Do not backup everything!” - repeatedly clean your data - and discard redundancy and garbage before adding to backup set - otherwise you’ll just to be creating a backup set that’ll turn into a pile of “mostly” garbage soon - and it’ll just be GBs and TBs of “too much” - essentially useless - and costing more as well. Keep your storage footprint in check.
- bccdee 5y agoAbsolutely. Disk image backups feel completely pointless to me — why would I back up my entire system when I can reinstall 90% of it from a live USB? It's only my documents that I care about (including photos, etc). My restic job runs in seconds.
- pyuser583 5y agoTrue. I thought a copy on write system would solve the “too much” issue. It made it so much worse.
- yosito 5y agoIf you're too lazy to do this manually, Restic will handle it for you!
- jszymborski 5y agoThis is very true, and de-duplication can be a great answer for this. Here's the read out from my last Borg backup which says that I'm storing 2.5Tb worth of data in 59Gb ------------------------------------------------------------------------------ Original size Compressed size Deduplicated size This archive: 220.28 GB 66.75 GB 591.11 MB All archives: 2.55 TB 777.85 GB 59.44 GB Unique chunks Total chunks Chunk index: 234389 4706300 ------------------------------------------------------------------------------
- artificialLimbs 5y ago
- password4321 5y agoAnyone using m-disc for archival? Write-once seems valuable in the age of ransomware.
- hhdave 5y agoI've backed up a load of photos (mostly raw, 5 discs so far) onto 100GB M-discs. They seemed like a good choice for long term archival storage - they don't need to be kept in ideal conditions - humidity isn't supposed to be a problem, and leaving them out in the sun is apparently fine! Plus drives for reading them are cheap and readily available. The discs themselves are quite expensive in terms of cost/TB - somewhere around 50-60 GBP from what I've found. I have more confidence in their ability to not lose data if left on a shelf and forgotten about for several years compared to hard drives. I have the same data stored on a ZFS pool too.
- noduerme 5y agoThis reminded me to buy a new hard drive for secondary backup. Is it just the nature of so many reviews these days, or is it impossible to find a drive now that won't likely fail in a few months? I just spent an hour on Amazon and other stores and can't find a single drive that isn't littered with relatively believable 1-star horror stories... many of which include things like "I've had 3 drives from X brand before but this is nowhere near as good as the old ones." (Side note, I also see the same comments about the shoes I want from the company I've bought shoes from forever). Is this comment overload from naive users in the hard drive sector, or has quality control dropped across the board?
- pnutjam 5y agoBackblaze publishes good data about their drive failure rate. I usually judge based on the manufacturer warranty. If they do 3 years, it's probably pretty good. 5 years means top shelf. Stay away from anything with shorter warrenties.
- joconde 5y agoIf you have 0.01% failure rate and sell a million devices, that’s a hundred expected failures. Some of these buyers will want to blame someone, so they’ll go on Amazon telling everyone that their study with a sample size of one shows how incompetent YourDriveBrand has become, and that they should never buy from them again. The average rating is probable a better indicator here.
- namelosw 5y agoIt seems like a solid plan but what's missing is no matter if you're doing 3-2-1 or using simpler solutions, you should test if the backup works periodically. Or else over the years, the backups would die one by one and nobody noticed, it defeats the point of so many redundancies. Also there's a chance the backup data is corrupted or incomplete (especially due to the design) so it's not possible to restore the system. Just test it periodically. If there's a backup process you should also test it too. Scenarios like backup job workers are stuck and the system is not actually backing up is not uncommon.
- bonestamp2 5y agoI test my backups whenever I buy a new computer... I'll transfer the data from my latest backup to the new computer before I wipe my old computer. After I wipe the old computer I will restore the data from the other backups to test them. I should do it more, but I buy a new computer every 2-3 years and testing the backup is most convenient when I have a "spare" computer on hand.
- bonestamp2 5y agoFor my off-site copy, I keep an external hard drive at my parents house and back up to that at least once/month. Time machine handles multiple disk backups beautifully. Ya, it could be a little out of date, but I wouldn't lose that much in a month.
- gibs0ns 5y agoFor those out there using S3 to store their personal backups, I'd like to recommend Wasabi [0] as either a replacement or addition to AWS S3. Wasabi offers object storage in multiple regions, compatible with AWS S3 API and therefore is a drop-in replacement. The storage cost is $6 per TB p/m, with no bandwidth costs. I'm not affiliated with them, just a happy customer enjoying massive cost savings. [0] https://wasabi.com/ https://wasabi.com/
- QuinnyPig 5y agoThere’s something “off” about them that’s difficult for me to put my finger on. I think it might be either their marketing approach, or signs of operational immaturity (GoDaddy domain issue taking them down for most of a day, for instance).
- dotancohen 5y agoThey advertise this on the website: > 80% Less than Amazon S3 Why would I use a service that is 80% less reliable than Amazon S3? And if they mean something other than reliability - such as uptime, price, or transfer speed - then they should state it clearly.
- kortilla 5y agoIt’s not for people that won’t put more than 2 seconds of work into something. It’s a discount service. That line could easily be a decoy to ward off problem customers who don’t know how to use APIs, read specs, etc and would be high customer service load.
- dotancohen 5y agoSo it's 80% less service than S3, I see )) In any case, thanks for mentioning the service. I'm quite happy with [Boto](https://github.com/boto/boto3 https://github.com/boto/boto3) for interfacing with Glacier but it is good to know about alternatives.
- 5y ago
- tlamponi 5y agoYou may want to check out our open source project: Proxmox Backup Server, it supports 3-2-1 relatively integrated by: - integrated tape backup (LTO-4 or newer), this allows to fulfill the two different medium rule and may also help on the offsite one (e.g., but a tape in a safe at CEO's home once a week or so) - efficiently mirroring of backup data to remote PBS (offsite copy) - client-side encryption, because well, backups are good but maybe not so if they're leaked - file-level and block level backup - disclaimer the former currently only for Linux clients and the latter can handle anything but also runs on Linux (VMs are used) The introduction/main feature section of the docs contain more info, if you're interested: https://pbs.proxmox.com/docs/introduction.html https://pbs.proxmox.com/docs/introduction.html If you have your non-Linux workload contained in VMs and maybe even already use Proxmox VE for that it's really covering safe and painless self-hosted backup needs.
- nickdothutton 5y agoI say “you are only as good as your last restore”, a phrase I stole from the Theatre industry where your performance “is only as good as your last rehearsal”. Of course this is most useful in Disaster Recovery scenarios. Rehearsal? Restore? Oh we’ve never tested it.
- dspillett 5y agoFor a couple of VMs I have an automated restore to another VM. The test copies rsync from the latest backup daily and restart themselves, and once a week do a full wipe and resync. A script touches the copy mail store (I currently use Zimbra for a mail server) to check it is up, and that the last item “received” is no older than 24 hours, and emails me to say all is well. If I don't get that daily mail, the restore has failed somehow. I keep meaning to add an extra layer that checks for the daily mail and sends me an SMS if it doesn't arrive, just in case I don't notice. The copy VMs don't need to be high spec, though in theory if the main machines die I could just switch other to them in minutes by DNS+firewall updates (and by giving them a bit more CPU+RAM allocation), just enough that the services start and run fast enough for the occasional manual paranoia check, and they aren't accessible to the outside world (but could be, if I needed to make that switch in a DR situation). Similar for the little web servers I still run and key parts of general data backup (the parts that can't be reobtained at all if both originals and backups are lost): restore from backup after the update of the backups is due to finish, checksum everything older a few hours on both sides, and send a mail if the checksums match. That sometimes give false negatives, if a file is updated between backup and checksum, I have a couple of possible fixes for that in mind but it only happens if I'm working silly late due to when the checks run so I've not been bothered enough to implement one.
- EVa5I7bHFq9mnYK 5y agoMight be important in the age of ransomware: is data protected against someone that has all your passwords? All cloud backup is probably gone in such case. All NAS and other network connected backup is gone too. Physical backups should be good if in write once mode (dvd disks for example).