Automatic Restore By Script ...

I´m looking for some feedback on an automated restore system for SQL server i wrote. Any hints and discussion will be appreciated.
Here is the concept. It´s not only an idea, it is existing and it is working:

Goal
If our main SQL servers may have crashed and cannot be fixed, what we all want is to restore our lasted backup of the database to another system in the shortest possible period of time.

All this begann, when I realized, that a restore of a full backup + all TRN-Backups to a new "clean" Sql system would be a nightmare when having some 80 TRN-files (we save the T-Logs every 10 minutes), since that new Sql server won´t have any backup history. One of the solutions I was offered, was the usage of ArcServe, but I´m not one of the fans of that software.
Besides that, I wanted to shorten the time, until my StandBy Server would be up und running to a MINIMUM.

My current solution for this are 2 VB-scripts I wrote. YES - this has been realized with VBS. The Transact SQl commands are only the subsequent steps in that szenario.

What we´ve got
We have a main SQL server, and a "Standby Server" with the SQL Server software pre-installed. If the main server crashes (although there is extreme redundancy) we want to RESTORE the latest full backup plus all TRNs stored after that full backup to the Stby Server and work can go on.

We do a full backup every night at 1:00 am and TRNs every 10 minutes from 6:00 am to 9:00 pm, and store these files to a 1.5 TB NAS device. We don´t like tapes, have no experience with those and the VN scripts will only work for backups sent to disk!

VB-script 1
This script is executed every morning at 5:00 am on the Standby machine by the task manager. It:

- searches the latest Backup on the NAS device
- deletes an existing DB on the StdBy with the same name as the one to restore by calling OSQL.EXE with an TSQL command (sp_detach_db)
- additionally deletes all files oh that DB (sp_detach should do that, but doesn´t ...?)
- again calls OSQL.EXE with another TSQL command, that is generated dynamically by the VB script and contains the path and name of the full backup with the NORECOVERY option.

So when this script has been executed automatically, we do have a restored Database from the recent backup with the state "loading ..."
(we´ve got it all in german, where it´s "Lädt...")

VB-script 2
This script will ONLY be used, when the main SQL server has crashed and the DB is lost. It:

- searches all TRN files on the NAS device, that have been stored AFTER the latest full backup and stores them to an array
- all of the found TRN-files within the array will be sorted by date and time to get into correct order
- it writes the sorted TRN-files to a <xxx>.sql file by adding TSQL code > "RESTORE LOG .... <trn-file> ... NORECOVERY"
- for the last LOG to restore it will of course end the line with a RECOVERY statement

That means, by running this 2nd VB script we get a TSQL script file, that we can load into our query analyzer on our standby server and execute all commands with a singe F5 hit.

The gerenation of the TSQL script takes less than 10 seconds in our environment. The execution of the RESTORE LOGS commands of course depend on their size, but usually this is a job of minutes ...

Conclusion
Since we do the full backup every morning automatically, we can get a fully restored Standby server within less than 5 minutes until this system will be up and running.

Comments
I´m a real beginner to SQL server, and may have made severe mistakes or choosen the wrong way - please let me know. If anyone ist interested in the VB scripts send me an e-mail, or let me know, where to upload them in this forum.

Pidi