Javier I have a scheduled task that copies the 4 *.rx *.rb files to a different server. This seems to work fine. The only problem is that it does slow the database down for a few minutes.
I just let everyone know that 8:00am, Noon, 4:00pm, 8:00pm and midnight they may experience a slow down. Buddy From: [email protected] [mailto:[email protected]] On Behalf Of Javier Valencia Sent: Monday, June 27, 2011 2:40 PM To: RBASE-L Mailing List Subject: [RBASE-L] - Backup Practices. A week ago, a client (public agency) had it server flooded and I mean that literally. The server room has a dedicated (elevated) AC unit and the server is/was located right under it. There is a tray under the AC unit to catch the condensation and a hose to direct the water from the tray to a drain, I had told them repeatedly in the past that the configuration was a recipe for disaster, and sure enough, last weekend the drain hose and drain clogged and the server got soaked; it will be at least another week before they have a new server installed and running. Luckily, I had downloaded the database a couple of days before so there will not be massive data loss, since their current procedure is to backup weekly to tape. I have a procedure in place to backup the database nightly and what I would like to do is set up a procedure (from within R:Base) that after the database is backed up, it sends a copy off-site; the 4 *.rx_ files are under 500 MB, so it is not too big. I think I would prefer not send it to one of the other County servers, as I am not sure their MIS department is competent enough not to screw it up. Has anyone implemented a procedure like this? Any suggestions? Advice? Caveats? Javier, Javier Valencia, PE 913-829-0888 Office 913-915-3137 Cell 913-649-2904 Fax Visit us at www.vtgonline.com <http://www.vtgonline.com/>
