Dave, This is good, but how do you handle disaster recovery?
Bill > Al, and others, > I have a 24/7 system here running with a VFP backup which > periodically scans the tables in the database and then > creates a new database and uploads the tables to it as > required. The only thing it won't do is copy over stored > procedures and RI conditions as I only use the DBC container > to hold tables and do all the RI stuff programmatically. > > The program works fine and if required I can put a stop on > any database activity (update/insert/amend) whilst the backup > is taking place but I do this from within the application > itself. In addition the backup program also copies over the > current version of the EXE associated with the data as well > as the reports which are in a folder off the main data folder. > > This method means that in the case of a failure we can just > copy over the dbc container and tables and immediately be up > and running. > > The backup is currently scheduled to run every 60 minutes but > this is changeable in the backup app. > > I can quite happily post up the code if required after a > little bit of work > > Picture of running live program as of about 10 minutes ago > whilst in mid backup at: > > www.replacement-software.co.uk/temp/Flexispec_Backup.png > > Dave Crozier _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
