Expand All

Collapse All

What are the minimum system requirements for Blob?

Blob can only be installed on a computer running Windows Vista or later. Windows XP is not supported. Blob requires Microsoft .NET Framework version 4.5 or later (to make secure TLS v1.2 connections with your remote email, cloud storage and social media accounts). A Pentium class CPU or better; 512 megabytes or more of system memory and 256 megabytes or more of free disk space is recommended. You may need a more powerful system than this if you want Blob to work with a large number of Data Sources or with Data Sources that have large amounts of content.

Please note that Blob currently only supports the (US) English language, so all user prompts, warnings, errors etc. are displayed in English.


How does Blob's licensing work?

When you purchase a Blob license, you acquire a life-time right to use that specific version. You can install a licensed copy of Blob on one computer, unless you purchased a multi-site license that explicitly allows you to install it on multiple computers. Security, bug-fix and small feature updates are free and available for the lifetime of the product for all product types, including the “Free” version of the product (Blob can install these updates automatically). Major version updates require you to purchase a new license for the new version.

A purchased license needs to be “activated”. This is a one-time process that typically runs when you install Blob for the first time, though you can enter or update the license key anytime (for example when you upgrade from the “Free” or “Trial” version to the “Premium” version). Once a license has been activated on a specific computer, it cannot be activated on another computer unless you deactivate it first from the old computer by completely un-installing it. If you are unable to un-install Blob from your old computer before installing it on your new one (e.g. because your old computer has crashed and will no longer power up), please contact Datamaton support (“Contact Us” or send an email to support (AT) datamaton.com).


What is Blob's return/refund policy?

Datamaton provides trial versions of Blob on its website free of cost, and strongly encourages you to use it so you know if it meets your needs and expectations before you purchase it. Datamaton will accept returns only if it meets ALL of the return criteria mentioned here:

  • You may return Blob only up to 30 days from the date of purchase.
  • You must completely un-install Blob (if you installed it) and destroy all copies, including backup copies. Only a full un-install will release the Blob license key you purchased, and this is required for a refund. Please contact Datamaton support (support at datamaton.com ) if you need help.
  • All returns and exchanges must be accompanied by the original purchase or gift receipt.
  • Datamaton reserves the right to refuse returns that it deems to be fraudulent or excessive.

To initiate a return, please send an email to Datamaton support (support at datamaton.com). Please include the name and email address you used to purchase Blob, your receipt ID and your Blob license key (this information is sent to you in your purchase confirmation email). Datamaton will process your return request within 4 weeks of receiving a complete refund request with all required documentation. Approved refunds will be made in the same method as payment unless you select to exchange the item.


How do I detect duplicate content?

To find duplicated files with the same name across all Data Sources, search for the file’s name (or partial name) in all Data Sources (see “How can I find my content using Blob?”). All instances of the file will appear in the search results, and you can sort by name or size to make all instances of the same file appear next to each other in the search results display.
If you want to detect duplicates within the same Data Source (e.g. within the local hard disk), issue a search but restrict it to that single Data Source. Alternatively, you can also double-click on the Data Source to display its details and then sort the display by name or size to make sure duplicate instances show up next to each other (see “How can Blob help with using my content on a day-to-day basis?”).


How can Blob help me clean up my disk or email account?

There are many ways Blob can help you detect large and/or no-longer-needed files, emails etc.

  • Click on the “View” button at the top left corner of Blob, just below the “Add Data Sources” button. Click on the “Large” sub-menu option and click on “Files and Emails”. This will issue a search for all large files and emails across all Data Sources. You can further sort the results based on size or dates to quickly identify and delete content you no longer need.
    View large files and emails

    View large files and emails across all Data Sources.

  • Click on the “View” button and then on the “Old” sub-menu option. Select “Files” or “Emails” to search for old files or emails across all Data Sources. You can further sort the results based on size or dates to quickly identify and delete content you no longer need.
    View old files, emails, appointments and social media posts.

    View old files, emails, appointments and social media posts.

  • If you want to clean up a specific Data Source like a hard disk or email account, issue a date or size based search only to that Data Source (see “How can I find my content using Blob?”).
  • Select a Data Source you are trying to clean-up and double-click on it to display its contents. Select the root of the Data Source (i.e. not a sub-folder) – you will see all content in all sub-folders. You can now sort the content based on date or size to quickly spot and delete content you no longer need (see “How can Blob help with using my content on a day-to-day basis?”).
  • Detect duplicate content using the procedure described in “How do I detect duplicate content” and delete duplicates.


Date columns show dates in different colors. What do the different colors mean?

These colors are visual cues that let you quickly determine how old the content is. A date/time that is within the last 24 hours from the current date/time is shown in red color. A date/time that is within the last 7 days from now is shown in dark green color. A date/time that is within the last 30 days from now is shown in orange color. A date/time that is older than 30 days from now is shown in the normal blackcolor.

What date colors mean.

Date color tells you how old the content is.


How can I measure the performance impact of Blob on my system?

The performance impact Blob has on your system depends on how many Data Sources you have, how frequently they are being checked for content updates and how many tasks you have set up. If you feel that your system is getting sluggish and suspect Blob as a possible cause, you can check the current performance impact of all Blob related tasks using the Blob “Dashboard” (including the background tasks that re-index Data Sources and run the backup tasks you have created). To open the Dashboard, open Blob, click on the “Help” button (the “?” question mark button on the main menu of Blob) and then click on the “Dashboard” button.

Blob Help Menu Button

Click on the “?” Help button to open the help menu.

Blob Dashboard

Click on the “Dashboard” button to open the Dashboard.

The Dashboard will display performance information for all Blob and background processes, including any back-up or synchronize tasks that are currently running. You can terminate a task if it is making the system unusable by hogging too many system resources.

View the performance impact of all Blob related processes currently running.

View the performance impact of all Blob related processes currently running.


How can I reduce Blob's performance impact on my system?

The Blob Dashboard will show you if one of the Blob related processes is having a large performance impact on your system (see “How can I measure the performance impact of Blob on my system?”). Depending on which process is causing problems, you can try one or more of the following things to reduce the performance impact:

  • Check “large” Data Sources for content updates less often: Blob lets you control how often a Data Source is checked for new, modified or deleted content (see “How often are my Data Sources indexed?”). If a Data Source is being checked more often than you need, you can set it to a higher value (see “How can I control the indexing process?”). Many times, checking a single “large” Data Source less frequently (e.g. a network attached drive with 1 terabyte of storage) will be sufficient to significantly reduce the performance impact on the system.
  • Make sure your local hard disk is set to be checked “Constantly”: Windows will provide Blob with a notification any time a files is created, modified or deleted on your local hard drives (e.g. C:\, D:\ etc.). This happens only if you have set their “Check Data Source for content updates” setting to “Constantly” (this is the default behavior). Blob can update your drive’s index files much more efficiently with these Windows notifications. The alternative is for Blob to periodically scan your entire drive for changes – a far more performance intensive operation.
  • Run backup tasks less often: When a backup task runs, it first evaluate the rules that determine what content it should back up (or synchronize). It then checks each affected file, email etc. to see if an identical copy exists at the destination. If not, it then copies the content to the destination. Reducing the frequency of this process may reduce the performance impact on your system.
    Note that backup tasks that are set to run “Immediately after content is added or modified at source” are generally not the problem. These tasks generally run when Blob gets a direct notification about new or changed content. Such notifications provide details about the affected files/folders that allow the backup task to operate just on the affected folders in a quick and efficient manner.
  • Terminate the “Blob.exe” process if you don’t need it: The “Blob.exe” process is just the interface to you, the user. It does not directly check your Data Source for content updates or run your backup tasks – these jobs are performed by background processes that are automatically started and stopped as needed. If you are not actively doing anything with Blob, feel free to terminate it by clicking on the “X” (terminate) button at the top right corner.
    When “Blob.exe” is running, it will reload the index files for a Data Source if a background process (e.g. “Cataloger” or “File Monitor”) updates them. Some Data Sources like the C:\ drive change very often (more than once per second!), so reloading its index files repeatedly can slow down your system.


Will Blob let me search for Windows system files, program installation files, registry entries etc.?

Not by default, since Blob’s primary focus is the personal digital content you create and use. Most computers have hundreds of thousands of Windows system and program installation files that we will never browse or search, and these files can change very often (some Windows system files can change several times per second!). Indexing and re-indexing them at every change can significantly slow down your system, so Blob skips these folders by default. However, you can tell Blob to index such folders and files too. Select your Windows installation drive (typically C:\) and change its settings using the procedure described in “How can I control the indexing process?”. You can tell Blob to index the entire C:\ drive, or selectively include or skip specific folders.
Blob cannot index the Windows Registry, so you cannot search for registry entries.