4 ms·
The cloud is just someone else's servers. 3-2-1-0 Applies to all data, at all time, in all places
by syshum 4y ago
The cloud is just someone else's servers.
3-2-1-0 Applies to all data, at all time, in all places
- thisisjasononhn 4y agoNormally it's 3-2-1, what does the 0 represent here? 3 copies 2 different formats (ex. HDD, cloud) 1 offsite 0 lost data? :D
- phone8675309 4y ago0 data leaving the system unencrypted would be my formulation
- nix23 4y ago>2 different formats (ex. HDD, cloud) That's not what "format" means, it's more like DB-Dump and DB-VM-Dump, or pure Files and VM-Dump, or something like restic-repo and rsync(pure files).
- syshum 4y ago2 Media, but the HDD / Cloud is correct The idea is to not have the backups stored on the same hardware or even same type of hardware. Same hardware is obvious but same type of hardware is listed because if a manufacturing defect or a known vulnerability is present it would make all of your backups at risk. So you want to have backups stored on 2 desperate types of storage media. HDD and Tape, or Cloud etc...
- nix23 4y agofor me it was always 2 different formats (db-dump, vm-dump) because i trust (good) storage-media more then backup-software, for example old veeam-backups cannot be restored with new version, old veeam-software runs not on new esxi etc...
- syshum 4y agoVeeam backup chains are backwards compatible with older version of veeam so I am not sure where you get that. As far as running veeam on esxi, you would need to elaborate more on that
- nix23 4y ago>Veeam backup chains are backwards compatible I had some backups that where not backwards compatible from versions that worked with ESX but NOT on ESXi. There's your "backwards compatible". >As far as running veeam on esxi, you would need to elaborate more on that Yeah you know exactly what i mean, no need to elaborate on that.
- syshum 4y ago>compatible from versions that worked with ESX but NOT on ESXi wow, ESX, I have not seen anyone talk about that for a long time, you must really hold a grudge... I never used Veeam with ESX so I can not comment on that. >Yeah you know exactly what i mean, no need to elaborate on that. No I really do not, you do not run Veeam on either ESX or ESXI, veeam connect to vmware with API calls, so .....
- thisisjasononhn 4y agoExactly. If tape was easier for me to implement in my setup, I would do it, but I'd rather just use cloud with a fast fiber connection for now. Offsite I can send data on an external drive to another physical location if needed. I made efforts to buy HDDs from different sellers even, to avoid sequential failures from singular bad batches. That's something else I'd want to add to a "3-2-1", with regards to HDD as a form of backup or storage media.
- thisisjasononhn 4y agoYes seems I used the wrong word here. Indeed I meant media, rather than format, as personally for my backup setups it's different media I want to trust, rather than the actual backup file formats (which are easily interchangeable depending on what's used; read and write data to and from formats if needed).
- syshum 4y ago0 Errors. Technically alot of Backup Planning has moved to 3-2-1-1-0 3 Copies 2 Different Media 1 - Offsite 1 - Offline / Immutable 0 - Errors from Verification Tests
- thisisjasononhn 4y agoInteresting, thanks for clarifying. My 3-2-1 comes from a personal non-professional standpoint, thus not having the extra 1-0. However I have been considering immutable offline backups, using burned DVDs or Blu-Ray discs. That's another project for another time though, for now I'm trusting paid cloud providers. As for verification tests, hashsums are a simple solution in my opinion, but I've moved to ZFS and BTRFS to avoid having blips.