"Include in database"

Discussion related to "Everything" 1.5.
Post Reply
ChrisGreaves
Posts: 821
Joined: Wed Jan 05, 2022 9:29 pm

"Include in database"

Post by ChrisGreaves »

I have asked questions about indexing before. Here is a brief summary by topic
In this thread I am not looking for a solution to a problem, but am seeking conformation of how removable drives are indexed within Version 1.5.0.1396a (x64)

I am currently (still!) playing with my daily (Y:) and weekly (Z:) backup drives, USB drives encrypted with Veracrypt.
My data files are on the laptop hard disk as a partition encrypted by Veracrypt and assigned to T:
T: shows up (Tools, Options, Indexes) as a FAT drive.
Y: shows up as an NTFS drive.
Z: shows up as a FAT drive.

(1) I think that months ago I made an error. Clearly Veracrypt can encrypt a partition as either a FAT or an NTFS partition. (T:, Z:)
(2) Clearly Veracrypt can encrypt a partition as either a NTFS or an FTS partition. (Y:, Z:)
(3) I think that consistency on my part should demand that both USB backup drives (Y:, Z:) should be identical in file systems.

I can fix that up by re-crypting the FAT Z: in place over the next few nights, to become an NTFS file system

(4) Meanwhile, all three drives are checked ON for "Include in Database"
(5) A simple search shows a file on all three drives. So far so good. If I want to start by checking that a data file has been backed up, the answer is instant: yes, on all three drives. I can't complain.

(6) For all three drives, the three checkboxes "Automatically include new fixed volumes", "Automatically include new fixed volumes", and "Automatically remove offline volumes", are checked OFF.

If I have explained so far a valid foundation for a trial then I want to start a trial with combinations of these last three settings.

If you think I should first convert the encrypted drive Z: to NTFS, then I will make that my next step.

Thanks, Chris
void
Developer
Posts: 19870
Joined: Fri Oct 16, 2009 11:31 pm

Re: "Include in database"

Post by void »

If I have explained so far a valid foundation for a trial then I want to start a trial with combinations of these last three settings.
I recommend leaving these three settings OFF and manually including each volume in your index.



Automatically include new fixed volumes

Everything will automatically include new fixed volumes in your Everything index.
Everything will perform a fast re-index to include your new volume.

This setting can cause trouble with Microsoft image mounted volumes.
Windows 10+ normally mounts these images as part of the system.
-You can end up with thousands of different image mounted volumes.
For this reason, I recommend enabling Automatically remove offline volumes if you enable Automatically include new fixed volumes.

If you are plugging in many external drives, the fast re-index might be unwanted and you might end up with a massive list of volumes.
Some which might share the same drive letter.

External USB drives are consider fixed volumes by Microsoft Windows. (even when they have the safely remove option)

USB thumb drives are consider removable volumes by Microsoft Windows.



Automatically remove offline volumes

You might want to keep the volume indexed in case of hard drive failure.
If enabled, and the hard drive fails, the volume is removed from your Everything index.
Not really a big deal anymore as you can always access the previous database with Everything.backup.db



Everything tracks volumes by Volume Name (\\\?\\Volume{01234567-0123-0123-0123-0123456789ab}), Volume Path (C:) and Volume Root (normally empty/SUBST drives).

The volume name should uniquely identify a volume.
It should never change and is maintained by the Microsoft Windows Volume Manager.

Is Everything still occasionally forgetting your C: drive?
Post Reply