DanielUK,
There are several issues here. You seem to be worried that someone is going to steal your systems, and/or your database being destroyed/corrupted, and/or you can recover and get back up quickly, etc., so it is essential you have daily backups running.
If daily backups are not good enough, then you need to look at having redundant servers running together, and need to really define the real problem. At this point I do not understand what you are really trying to protect against, and the threat will define the method to use. Remember the old addage: The real problem is to define the problem!
A Suggestion: Get a cheap IDE box with a large (READ: Hundreds of GB!) drive capacity to act as a backup function, then run your daily backup from the servers to store the backup on this cheap/large drive system at night, or at low use periods. Much faster than tape. If your data base is really critical, then run batch files several times a day to take snapshots of the data to save to the "backup machine". I presume you are using something like SQL for your data base, and it provides the ability to run "Hot" backups of the data base.
Next, having done this backup to a file/folder on the "backup system", you are free to back this up to tape during the day without causing any impact to your operation, and this tape backup should be stored off site.
This method has some nice features: it is cheap, does not have to be a server, does not disrupt the day-to-day operations, is always available immediately on site for quick repair functions, and is also available from off-site for disaster repair is the servers need to be rebuilt from scratch/replaced. Keeping another system off site is a great idea, but a real bear to keep up-to-date with the active system, unless it replicates very often on a regular basis. Remember too, the if you use a replicate approach vs a tape restore, if the online systems get taken over, then the offline system may also get the same bugs, etc.
HTH,
David