To invoke fallback support for two databases in a one-primary to one-fallback configuration, follow the steps that are listed below. Only the system administrator (SA) can invoke the fallback feature. Each sp_fallback_ procedure takes only seconds to complete.
exec sp_addserver 'svrfallback' ,'fallback'
exec sp_addremotelogin 'svrfallback' ,'sa' ,'sa'
exec sp_addserver 'svrprimary'
exec svrfallback...sp_helplogins
exec sp_fallback_enroll_svr_db 'svrprimary' ,'DabSales' exec sp_fallback_enroll_svr_db 'svrprimary' ,'DabProduct'
Note The databases DabSales and DabProduct that are being configured for fallback must be on a switchable disk for fallback to work.
The following steps should be performed each time the fallback server takes over a switchable disk from the primary server and assigns a new drive letter to the disk:
exec sp_fallback_upd_dev_drive 'svrprimary' ,'D:' ,'H:'
exec sp_fallback_activate_svr_db 'svrprimary', '%'
If the underlying fallback architecture supports registering applications that are launched automatically when the fallback server takes over, then an application (using DB-Library or ODBC) could be written that connects to the fallback server and executes the stored procedures after each disk switchover.
Note If your model database is 1 MB, then a database device of only 1 MB can hold an entire database. To experiment and familiarize yourself with setting up fallback, use a standard 1.44 MB floppy diskette. To activate the fallback server, you can transfer the floppy diskette from the primary server to the fallback server after stopping the primary server.