At 01:54 PM 5/3/2002 -0400, Steve Durham wrote:
>I am designing a disaster recovery procedure that will require >me to copy a live Rbase 6.5++ database approximately five >times a day. I am looking for some suggestions. The database >does use an ODBC driver to an archived database of older data >prior to upgrade of 6.5++. If the database server were to go down, >I would like to have another copy of the database at an off-site >location, and redirect users on Citrix to that off-site server. I am >beginning to research the best possible way to do this if possible >at all. I am open for suggestions. I thank you all in advance. Steve, With all the wonderful suggestions you have received, you may also want to look into the very powerful and cool option of MIRRORing your database using The Glorious R:BASE 2000 (ver 6.5++), Build:1.842xRT03 and higher. SET MIRROR maintains a duplicate copy of the database. This duplicate copy is created and maintained in the directory designated in path. Syntax : SET MIRROR <path> SET MIRROR OFF/DELETE DEFAULT: OFF The duplicate database will have the same name, therefore path must designate a backup directory. With this setting, all modifications to the original database are duplicated in the mirrored database. Be sure all users are mapped to the save drive letters. SET MIRROR OFF turns off mirroring of the database. SET MIRROR DELETE turns off mirroring and then deletes the duplicate database. Note: Only the OWNER of the database can use the SET MIRROR command and it must be executed while in single-user mode. The setting is stored in the database. Once set, MIRROR is ON until the database is again connected in single-user mode and MIRROR is set OFF. If SET MIRROR <path> directory is created on the network drive, then, make sure that the directory has all RIGHTS Also, SET MIRROR ON will NOT protect you from "Bad Code" that does the wrong thing. However it WILL protect you from hardware failures such as a crashed disk drive. Also, You cannot connect to the Mirrored Copy you can only connect to the "real" copy. Only R:SCOPE 2000 (version 6.5++) database repair utility will be able to CONNect and RESET any MIRRORed database(s). R:SCOPE 2000 (version 6.5++) Database Information Screen will also display the Mirror Path of the connected database, if any. All Developers, Users, Corporate, Educational and Government Clients who are using R:BASE 2000 (ver 6.5++) and higher and running mission critical operations (24x7x365), may request a special UNMIRROR Utility to turn MIRRORed database into a LIVE database instantly! Enjoy the BENEFITS of staying CURRENT and Up-To-Date! Very Best Regards, Razzak. ================================================ TO SEE MESSAGE POSTING GUIDELINES: Send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: INTRO rbase-l ================================================ TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: UNSUBSCRIBE rbase-l ================================================ TO SEARCH ARCHIVES: http://www.mail-archive.com/rbase-l%40sonetmail.com/
