Correct. What it appears to be and what it is, are often two very different things. And people often underestimate situations like desaster recovery… Everything is fine and dandy on the day you configure the backup job. But once you need it, that day is a desaster and everything has gone wrong. Now you need your plan to work flawlessly. And there are a lot of things that can go wrong, I’ve only highlighted a few of them. And lots of people have been burned by that before. There is only one way to make sure it works, and that is to test the whole procedure. And ideally not just once right after you configured it because things can go wrong later on, too.
Monitoring if the backup task succeeded is important but that’s tue easy part of ensuring it works.
A backup is only working if it can be restored. If you don’t test that you can restore it in case of disaster, you don’t really know if it’s working.
Correct. What it appears to be and what it is, are often two very different things. And people often underestimate situations like desaster recovery… Everything is fine and dandy on the day you configure the backup job. But once you need it, that day is a desaster and everything has gone wrong. Now you need your plan to work flawlessly. And there are a lot of things that can go wrong, I’ve only highlighted a few of them. And lots of people have been burned by that before. There is only one way to make sure it works, and that is to test the whole procedure. And ideally not just once right after you configured it because things can go wrong later on, too.
Yes, absolutely. Ideally there would be an automated check that runs periodically and alerts if things don’t work as expected.