So, I've been dealing with an infrastructure team that didn't have backups of a web server recently... We were told "You don't need backups - that's what you have VSS for, right?"
Maybe its just because I came up on the "operations" side of IT, and the backups were my highest priority, but it took me a while to realize they were serious. As in "we're gonna argue about this for a while." For better or worse, the infrastructure guys carry a lot of clout at the company I work for now, so I couldn't just scowl at them and tell them how stupid this sounded to me. I had to try and reason about something that just seemed obvious to me.
One thing I've learned is that anything that seems "obvious" to me probably means I don't understand the whole thing :)
I thought I had a perfect, easy to understand example of why that idea doesn't work - config files. We deploy these apps with certain things configurable after the fact, and some other support type person can change these settings without our knowledge, I explained. Our copy in VSS would be unaware of any edits that have gone in since the app was deployed.
No dice. The infrastructure guys were even pushy enough to get the development boss to start wondering if perhaps we should make sure that whenever anyone updates the config files those should be checked into VSS. Forget the fact that different deployments might have different configs, yet only one VSS. "We can make a subdirectory for each one."
I just refused to roll over and die on this one, which got me some nasty comments after the meeting. We did hammer out a tentative "in a catastrophic failure you can beg and plead and we will grab stuff from tape for you - but you had better first help yourself by having copies of your files in email or subdirectories or something."
So please tell me - Am I just wrong on this? Is my own past experience of being responsible for "the backups" making me want to place too much burden on the infrastructure team? After all, this is a different company, with different priorities and challenges, etc.
| posted on Thursday, January 31, 2008 7:39 AM