Building the index is slow, is there a way to export it afterwards?
Building the index is slow, is there a way to export it afterwards?
It seems, that with tags, comments, longitude and latitude included, building the index can take several hours on some machines, and indexing starts from scratch, if the machine is shut down inbetween. Is there a way to export the whole index as a backup? And if so, will it detect changes afterwards, like new or changed files?
Re: Building the index is slow, is there a way to export it afterwards?
It's always good (IMO) to have dated backups of your .db.
There are various Export options, though what might or might not be included, unsure without testing.
Note that during development, there is a chance that the .db format changes, necessitating a re-index if that were to occur.
There are various Export options, though what might or might not be included, unsure without testing.
Note that during development, there is a chance that the .db format changes, necessitating a re-index if that were to occur.
Re: Building the index is slow, is there a way to export it afterwards?
Ideally, the indexing is only done once.
Everything will detect changes afterwards.
Changing indexing settings can cause Everything to reindex properties.
Everything should be saving the current state and resuming on startup.
Please make sure Windows is shutting down gracefully.
Please make sure Everything is not being terminated on shutdown.
Please try Pausing property indexing from the indexing menu before shutting down.
Please let me know if this issue persists.
You can find this backup in %LOCALAPPDATA%\Everything
With the following filename:
Everything-1.5a.backup.db
Please feel free to backup your Everything-1.5a.db at any time.
Please make sure Everything is not running before you restore your Everything-1.5a.db (File -> Exit)
Everything will detect changes afterwards.
Changing indexing settings can cause Everything to reindex properties.
This shouldn't happen.indexing starts from scratch, if the machine is shut down inbetween.
Everything should be saving the current state and resuming on startup.
Please make sure Windows is shutting down gracefully.
Please make sure Everything is not being terminated on shutdown.
Please try Pausing property indexing from the indexing menu before shutting down.
Please let me know if this issue persists.
Everything 1.5 will make a backup of your Everything.db once per session on shutdown.Is there a way to export the whole index as a backup? And if so, will it detect changes afterwards, like new or changed files?
Top
You can find this backup in %LOCALAPPDATA%\Everything
With the following filename:
Everything-1.5a.backup.db
Please feel free to backup your Everything-1.5a.db at any time.
Please make sure Everything is not running before you restore your Everything-1.5a.db (File -> Exit)
Re: Building the index is slow, is there a way to export it afterwards?
Thanks, therube and void!
And yes, i had also the impression Everything would resume indexing after a shutdown. Not sure, what the reason was, but it didn't happen on my own machine. Will investigate.
And yes, i had also the impression Everything would resume indexing after a shutdown. Not sure, what the reason was, but it didn't happen on my own machine. Will investigate.
Last edited by abr01 on Fri Mar 01, 2024 6:33 pm, edited 1 time in total.
Re: Building the index is slow, is there a way to export it afterwards?
(There is also the [Everything.exe] -save-db switch which will cause the .db to be saved to disk should you not want to actually exit Everything at a particular time [& during which time the disk .db may then not otherwise be [as] current as that stored in RAM].
Did that just this morning to bring my home .db to work.)
Did that just this morning to bring my home .db to work.)
Re: Building the index is slow, is there a way to export it afterwards?
Sounds useful, but how would i use that switch? If possible, as some optional command, since i'm not sure how much time it would take up to save the whole db.therube wrote: ↑Fri Mar 01, 2024 6:30 pm (There is also the [Everything.exe] -save-db switch which will cause the .db to be saved to disk should you not want to actually exit Everything at a particular time [& during which time the disk .db may then not otherwise be [as] current as that stored in RAM].
Did that just this morning to bring my home .db to work.)
Re: Building the index is slow, is there a way to export it afterwards?
I'm curious, how do you open/view this db?Did that just this morning to bring my home .db to work.)
1370a added support for:
Everything64.exe -filelist Everything.db
-and-
File -> Open File List -> Everything.db -> Open
Please note:
-save-db will issue a command to the existing Everything.exe to save the database to disk in the background.
-save-db-now will save the database to disk and not return until this completes.
-save-db
-save-db-now
Easiest way would be to add a shortcut on the Desktop.Sounds useful, but how would i use that switch?
Create a shortcut called:
Save Everything Database to Disk
Set the shortcut target to:
"C:\Program Files\Everything 1.5a\Everything64.exe" -save-db
When opening this shortcut, Saving database... is shown in the Everything status bar.
This text will disappear once the save completes.
Please consider the following savedb.bat file:If possible, as some optional command, since i'm not sure how much time it would take up to save the whole db.
Code: Select all
echo Saving Everything database to disk...
"C:\Program Files\Everything 1.5a\Everything64.exe" -save-db-now
echo Everything Database saved to disk.
pause
Please also consider a bookmark to save your Everything.db to disk:
- From the Bookmarks menu, click Add to Bookmarks....
- Change the Name to:
Save Everything Database to Disk - Change the Search to:
/save-db - Click OK.
Saving database... is shown in the status bar.
This text will disappear once the save completes.
Re: Building the index is slow, is there a way to export it afterwards?
Thanks void, for the tips, i made that .bat and created a current backup.
Re: Building the index is slow, is there a way to export it afterwards?
Simply set up an -instance for it.I'm curious, how do you open/view this db?
(I was only interested in seeing "historical" data, what is or is not there, & not to make any changes.)
GO-HOME-15.BAT:
Code: Select all
cmd /c start .\everything.exe -instance HOME -read-only -no-auto-include