On Dec 8, 1:39 pm, Thadeus Burgess <thade...@thadeusb.com> wrote: > I am thinking that if the database on 1 goes down, a sqlite can be set > up fairly quickly if csv is available, while allowing time to get > another 1 database up and running.
Don't forget that a native db backup creates a file - it can be on any machine (e.g. copy it to another machine and start up). While you _could_ setup sqlite as db on some backup machine, why not then setup the SAME db for a fallback? (sqlite has all sorts of limits and behaviors that may not be consistent with "full size" dbs, so you may have trouble). That said, a final backup to _whatever_ db from a csv seems like a fine last line of defense (I am only saying there are other, easily available and better recovery lines of defense available - set those up ahead of the "last one" :-)). - Yarko > > That is assuming that there are no warm/cold standby servers. > > -Thadeus > > On Tue, Dec 8, 2009 at 1:31 PM, Yarko Tymciurak > > > > <resultsinsoftw...@gmail.com> wrote: > > sv data backup: provides portable data backup, easily > > accessible and manipulatab -- You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to web...@googlegroups.com. To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/web2py?hl=en.
