>>> You can do the backup and after that do an integrity check on the >>> backup. Surely you're backing up on a different >>> server, don't you? If the back up pass the integrity check it a real >>> backup, if not, launch a warning. >> >> Yeah, that's a good idea. >> Ohh boy, why I didn't think about that my self ? :-) > > In this process, you have to prevent that you overwrite your last > "working" backup! Which database will you use, if you realize, that the > backup is a corrupt database?
Yes, it creates a few backups over last N Days prior starting to overwrite the oldest one. It is not a embedded environment, so no problem. I could create backups of a few month if necessary.. Thanks Marcus > > On a webserver you should have enough space to make additional copies. > In an embedded environment, this could be difficult. > > Thomas > >> >> Thanks >> >> Marcus >> >>> >>>> Sure I could try to simulate that, but probably somebody here >>>> knows the answer. >>>> >>>> Thank you. >>>> >>>> Marcus >>> >>> >>> _______________________________________________ >>> sqlite-users mailing list >>> sqlite-users@sqlite.org >>> http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users >>> >> _______________________________________________ >> sqlite-users mailing list >> sqlite-users@sqlite.org >> http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users >> > > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
