Jesus > > Single server without downtime is a myth anyway. > The problem is not downtime is how much downtime. Backup and restore is > so much downtime.
If that is the case, how much downtime is acceptable? There are a couple of possible solutions which would reduce the downtime; - a new backup/restore tool which would use multiple readers/writers to minimize execution time, - a "data port" utility which would allow for data to be ported from a live database to a new database while live is active but would need a finalization step where the live database is shutdown to apply the final data changes and add FK constraints. There are, however, certain "realities" which cannot be overcome; disk throughput/IO performance. Sean ------------------------------------------------------------------------------ Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Explore the Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
