You shouldn't need to back up the shm file as this will be recreated if needed.
You naming convention is also off, you mean mydatabase.sqlite-journal mydatabase.sqlite-wal mydatabase.sqlite-shm so mydatabase.sqlite* would be what's required (which would include the unneeded shm file). Paul www.sandersonforensics.com skype: r3scue193 twitter: @sandersonforens Tel +44 (0)1326 572786 http://sandersonforensics.com/forum/content.php?195-SQLite-Forensic-Toolkit -Forensic Toolkit for SQLite email from a work address for a fully functional demo licence On 3 December 2015 at 14:45, Simon Slavin <slavins at bigfraud.org> wrote: > > On 3 Dec 2015, at 10:17am, Murdare, Vijaykumar S (GE Oil & Gas) > <vijaykumar.murdare at ge.com> wrote: > >> 1) If read operation is in progress, then can I take backup safely with >> file copy or any other third party tool? > > When taking a backup of the database file you should also copy all other > files with similar names in the same folder. So suppose your database name > is 'mydatabase.sqlite'. You should either copy every file in its folder or > use a technique which will include also > > mydatabase-journal.sqlite > mydatabase-wal.sqlite > mydatabase-shm.sqlite > > Including mydatabase-*.sqlite or even mydatabase*.* will create no problems > and may help to future-proof your procedure. > > Doing this will aid in automatic database recovery should either of the > following occur: > > 1) A backup is accidentally taken while one or more apps is engaged in a > database operation. > 2) A backup is taken after an app crashed while it had the database open, > before the database was opened again to automatically recover the best > available data. > > As Dr Hipp replied to your second question, since SQLite has no client/server > architecture, there is no delay on writes to the database. > > Simon. > _______________________________________________ > sqlite-users mailing list > sqlite-users at mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
