On Dec 8, 2:27 pm, Thadeus Burgess <[email protected]> wrote: > Agreed, ideally there would be a warm database server ready and > waiting, or at least a cold server that just needs to have the data > uploaded. > > However at this point in time, we have no resources to dedicate to a > backup machine (stupid I know.) I am just wanting to cover all my > basis, and if something does happen, be able to get the system > "running (even if slow)" asap.
A couple of comments: this kind of redundancy is appropriately achieved outside of the infulence of web2py: that is, db replication from the db server end, or (lower level) redundant RAID, etc. > > Thinking about running the system on sqlite while setting a proper > prostres database up, would not be desired, since then exporting from > sqlite to postgres would be a pita. Setting up postgres server is really pretty easy - even a minimal, cheap windows pc (! and why, why, oh why would you even bother running windows! ;-)) will run a postgres server (I think I have one on my netbook, actually, but that's ubuntu). I think this is preferable / easier in the bigger scheme of things, than thinking about cvs / sqlite (blech! spit! arrrr.... hehehe...) :-) > > As far as database redundancy and keeping backups on that end I am ok. > I was curious if the web2py export_to_csv solution should be > considered as on option. At this point, it is looking to not be a > "backup" option, but more of a "migration" option. > > -Thadeus > > On Tue, Dec 8, 2009 at 2:03 PM, Yarko Tymciurak > > > > <[email protected]> wrote: > > > On Dec 8, 1:39 pm, Thadeus Burgess <[email protected]> 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 > > >> <[email protected]> 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 [email protected]. > > To unsubscribe from this group, send email to > > [email protected]. > > For more options, visit this group > > athttp://groups.google.com/group/web2py?hl=en. -- You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/web2py?hl=en.
