Comment My Backup System is Painfully Simple (Score 1) 76
It starts with one premise: If backups (or drive images) aren't made automatically, they will eventually never get made.
I have three drives, call them A, B and C. We have two servers, two desktops, two notebooks, each of which make a DAILY full-image backup to a separate partition on the same computer, which is then copied to a common, external drive (say "A") on one of the servers. Typically, each system has two or three days' worth of local backup images, and the external drive has about the same. We keep data and programs separately; C: is for code (e.g., Windows & Apps), D: is for data. So, to start with, we have (after the first cycle) about ten backups (one on the system, and three or four each on each of three external drives).
Each external 500GB drive holds about three days' worth of backups; I'm thinking about 1TB drives, soon. I "rotate" the drive arrangement once each week: Each week, I move "A" from Active to Standby (I unplug it) and call it "B"; I move "C" (the eldest, retrieved from off-site) to "B" (i.e., I plug it in), and I move the displaced "B" to become the new off-site "C". So, (Active->Standby->Offsite) is A->B->C, then next week, C->A->B, and then B->C->A.
I can claim, accurately, that while this system has holes, there is so much backup that we've never had a catastrophic loss, which is just fine with me, and very cost-effective. I would no more put my business data on a cloud server than stick a sharp fork in my eye; beyond NSA, there is the constant threat that the business will die, or be closed by authorities (think Kim Dotcom).
I have three drives, call them A, B and C. We have two servers, two desktops, two notebooks, each of which make a DAILY full-image backup to a separate partition on the same computer, which is then copied to a common, external drive (say "A") on one of the servers. Typically, each system has two or three days' worth of local backup images, and the external drive has about the same. We keep data and programs separately; C: is for code (e.g., Windows & Apps), D: is for data. So, to start with, we have (after the first cycle) about ten backups (one on the system, and three or four each on each of three external drives).
Each external 500GB drive holds about three days' worth of backups; I'm thinking about 1TB drives, soon. I "rotate" the drive arrangement once each week: Each week, I move "A" from Active to Standby (I unplug it) and call it "B"; I move "C" (the eldest, retrieved from off-site) to "B" (i.e., I plug it in), and I move the displaced "B" to become the new off-site "C". So, (Active->Standby->Offsite) is A->B->C, then next week, C->A->B, and then B->C->A.
I can claim, accurately, that while this system has holes, there is so much backup that we've never had a catastrophic loss, which is just fine with me, and very cost-effective. I would no more put my business data on a cloud server than stick a sharp fork in my eye; beyond NSA, there is the constant threat that the business will die, or be closed by authorities (think Kim Dotcom).