4 ms·
As a lot of companies I bet they HAVE backup, just never tested if the backup process works. It is absurdly common...
by yulaow 9y ago
As a lot of companies I bet they HAVE backup, just never tested if the backup process works. It is absurdly common...
- gaius 9y agoThis is trivial tho'. Just setup a regular refresh of the dev env via the backup system. Sure it takes longer because you have to read the tapes back but it's worth it for the peace of mind, and it means that every dev knows how to get at the tapes if they need to.
- joncrocks 9y agoWell yes, but there's a string of WTFs here, lots of 'trivial' stuff that wasn't done!
- csydas 9y agoMost likely something like this. There is probably backup software running but it's either nothing but failed jobs or misconfigured so the backups aren't working correctly.
- lb1lf 9y agoMy favourite in that regard is an anecdote shared by a customer; he said one of their techs had discovered (luckily in time) that the long-running automated backup script on a small, but important server wrote the backup volume to... ...RAM.
- hulahoof 9y agoAnd here I've been wondering how could it get worse than writing to local storage ...
- csydas 9y agoI can tell you since I work support for a backup product. Lot of people think that naming a folder on a local drive "Disaster Recovery" counts as having an offsite Disaster Recovery copy of backups. The number of large corporations whose backups are in the hands of such people is frightening.
- dennisgorelik 9y agoFrom my experience, if I do not test my backups they stop working in about 1 year. So if I do not test backups for over a year then my assumption is that I probably do not have working backups.