Bill, 1. Primarily, all our servers are raid HP Kit with redundant power supplies etc. we have 3 servers in total connected in a triangle with gigabit fibre between each point. The HP intelligent hubs can route traffic automatically down any of the triangle legs should any leg fail. Also each fibre link also has a standby duplicate fibre leg in the same ducting.
2. The main primary server real time mirrored onto a secondary server which is on our other site. The software used is Doubletake which you may well have heard me eulogize over in list. If the main server dies the secondary server takes over within 15 seconds and assumes the primary IP address automatically until the primary server is fixed. 3. The secondary server is snapshot every 15 minutes onto a tertiary server, again at a different location and this snapshot is also committed to tape at the same time with each days snapshot(s) tape removed off site daily. 4. The VFP Backup program also saves a VFP snapshot onto the secondary server every hour. 5. The 55Gb of data is also mirrored nightly onto USB 120Gb external drive using Syncback Software (Cycled one per day over a week) and these are taken off site by one of the directors - all data is encrypted needless to say. 6. We also have UPS's on all the PC's and servers as well as a standby generator at each of the server locations which is capable of running about 10 client PC's and the server as all the computers are on a separate electricity sub system to the normal office. At present we run at about 55Gb data storage size in total with the VFP system using up about 1.8Gb and we actually test a real failover once every month as well as a complete restore onto a 4th development server. I think we have covered all the bases, and short of nuclear holocaust breaking out we are covered. Dave Crozier -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bill Arnold Sent: 08 February 2008 07:34 To: [email protected] Subject: RE: Backing up data from a running application 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 [excessive quoting removed by server] _______________________________________________ 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.
