Miles Neale (8/22/2012)
I guess I have a question about this. The first thing is to insure that it is being backed up. Is part of that insurance proof that the backup that is being cerated using the backup plan is usable, available, and secure? Or is just knowing there is a plan in place enough?
You might think this is totally stupid, but there have been times when a backup plan was in place and the output of the process was unusable. It is nice to be able to prove the backup by a valid restore or recovery process, and should be required as part of a business disaster recovery and resumption plan.
I am probably being too picky. But it caused me to think as I read this.
Perfectly sound advice! Case in point: At my current workplace, we have backups of all files on our servers running every night after hours. When I started working here, the backup process was explained to me, and I reasoned that it was sound enough, so I left it as it was.
A few months ago, the OS drive on one of the servers got corrupted for one reason or another, and so we had to restore the files from backup to get ourselves running again. Ok, no problem, a bit time-consuming, but easy. So, I just need to point the restore process at the backups and... Wait, where are
After much searching and asking around, it seems that the company just knew that backups were being taken; where
they were being taken at, and how to restore them, were both completely unknown to anyone in the office. Eventually, we just decided to format the OS disk (losing some data in the process, but it was deemed acceptable) and reinstalling.
At that point, I was able to see locations in the drive listing that weren't available before. It turns out that the previous network admin that worked here had created the backup plans, then hidden the folder with them and blocked access from all accounts in the building, even the admin account, for some indeterminate reason. Whatever the case was, I started the restore from the backups and we had everything back in order, though it took quite a few more hours than it should've had I known where to restore from in the first place.