The structure of a Dup Finder database has space for two independent sets of data, called   master and slave.

The functions / activities that can be carried out on the two parts are almost identical.

The idea is that the master part of the database is where you would place the scanned information that you want to keep, whilst the slave part is where temporary data would go.

Please please please, remember that a Dup Finder database does not store a copy of the file. It scans a file and saves information such as: file name, path name, file size, file MD5 hash checksum..., in a database.

Scenario A:

  • I get lots of PDF files sent to me, often I get sent the same PDF but with a different name.
  • I have a database called myPDFs, in the master part of the database I keep the scan information of the unique PDFs.
  • When I get a PDF I scan the PDF and place the scan information into the slave part of the database, and then run a duplicate check between the master and the slave parts.
  • Then I can see if the PDF is really “new” or if I already have it.
  • If it is new then I copy the PDF to a folder for unique files, and then scan that file into the master part.

Scenario B:

  • Before installing software, I sometimes scan the entire disk into the master part of a new database.
  • Then I install the software
  • Then I scan the disk, but this time in to the slave part of the database.
  • A duplicate check between the master and the slave parts (takes less than 1 minute) will then show me which files have been added or modified.
  • Then I use the display options to show the duplicate files and decide which copy of the duplicate files should be deleted, and delete them

Scenario C:

  • I have digitised my vinyl based record collection, and that of my wife. I also archieved our CDs as MP3.
  • Over the years the collected MP3 files have been backed-up on to various hard disks. And of course the older disks are relatively small and so do not hold a “full” set of files.
  • When I suffered a failure of my main MP3 disk, I found that there was no one backup disk that contained everything.
  • So:
    • I copied all of the disks to one massive disk.
    • Then I scanned all of that new disk in to the master part of a new database.
    • Then I ran a duplicate check. There are three duplicate checks: master to itself, master to the slave, and slave to the master.
    • And then deleted the unwanted duplicates.

[Home] [Uses] [History] [Goals] [First Steps] [Displaying Entries] [Display Filters] [Scan Filters] [Import Export] [Finding Duplicates] [Removable Storage] [Maintenance] [FAQ]