Hi all.
I just wanted to request whether someone who has a good grounding in the area could write up a discussion of backup strategies. You know, the sort of factors that go into such a decision, that sort of thing.
We keep getting questions in the VB forum asking things like "I'm writing an accounting software. How do I back up my stuff?"
I'm sure you can all see that the question is nothing like so simple. Obviously, we can describe details of any specific technique such as a simple file copy, or cloning a database, copying selected records, and so on and so forth. But the point is, these users generally have no idea of what type of backup they want to do, how often, where to, whether anyone will be using the data at the time, blah blah blah.
What we really need is somewhere we can point them to, and say "read this and come back when you've figured out what you want to do, and we can help with the how". I'd say this sort of decision should be largely made by the business, not the developer.
I just wanted to request whether someone who has a good grounding in the area could write up a discussion of backup strategies. You know, the sort of factors that go into such a decision, that sort of thing.
We keep getting questions in the VB forum asking things like "I'm writing an accounting software. How do I back up my stuff?"
I'm sure you can all see that the question is nothing like so simple. Obviously, we can describe details of any specific technique such as a simple file copy, or cloning a database, copying selected records, and so on and so forth. But the point is, these users generally have no idea of what type of backup they want to do, how often, where to, whether anyone will be using the data at the time, blah blah blah.
What we really need is somewhere we can point them to, and say "read this and come back when you've figured out what you want to do, and we can help with the how". I'd say this sort of decision should be largely made by the business, not the developer.
Comment