Once a backup strategy has been designed, it should be thoroughly tested. In testing the strategy, as many failures as possible should be simulated so you can be sure that there are no vulnerable areas that could jeopardize the recovery of data. For example, you could implement very redundant device and disk mirroring with multiple disks in a computer, so that should any one disk drive fail, you can continue operation uninterrupted. This is a good plan, but it does not eliminate the need to do backups. Asking the question "Will this be sufficient in the event of theft of the computer?" would show that this is a vulnerable area.
Testing a backup strategy will also demonstrate how much time is required to restore the databases from backups. If that amount of time is unacceptable, you may want to reevaluate the frequency with which the databases and transaction logs are being dumped, or you may want to look at the feasibility of maintaining a "warm" backup server. (For more information, see Managing a Backup Server, later in this appendix.)