StableBit

StableBit CloudDrive 1.1.0.1051 Release Final

Posted in StableBit on August 7th, 2018 by alex – Be the first to comment

StableBit CloudDrive 1.1.0.1051

StableBit CloudDrive 1.1.0.1051 Release Final is now available for download.

Get it here: https://stablebit.com/CloudDrive/Download

Full change log: https://stablebit.com/CloudDrive/ChangeLog

What’s New Since the last Release Final (1.0.2):

  • Added support for Backblaze B2.
  • Added support for Rackspace Cloud Files.
  • Added support for third party Amazon S3 compatible services.
  • Added support for OpenDrive (experimental).
  • Default I/O performance settings for new drives. (see: User Manual)
  • Bug fixes and optimizations.

The user manual has been updated as well to reflect the new features: https://stablebit.com/Support/CloudDrive/Manual

OpenDrive is Experimental

Upon further testing, it became apparent that OpenDrive has a number of troubling server-side issues that needed to be worked around in order to make it usable with StableBit CloudDrive. All of the issues that were discovered in testing have workarounds implemented in this release. But as a precautionary measure, the OpenDrive storage provider is now marked as experimental. You can still create new OpenDrive cloud drives, but you will have to enable experimental storage providers from the Troubleshooting menu in order to do so.

See the user manual for complete instruction on how to connect to OpenDrive in this release final: https://stablebit.com/Support/CloudDrive/Manual?Section=OpenDrive

Additionally, if you’ve created an OpenDrive cloud drive with the previous BETA (or the RC), in order to make that drive compatible with one of the above mentioned workarounds, StableBit CloudDrive will have to reorganize your cloud data on the first drive mount.

This reorganization will happen automatically and is an in-place one way upgrade. You won’t need to recreate your drives, and everything will continue to work as it did before once the reorganization process completes. But be aware that this reorganization can take a while for large cloud drives (e.g. multi-terabyte drives can take an hour or more to complete the first mount).

Drive is Connecting

This is the message that you will see while the reorganization process takes place. If the reorganization process is interrupted or fails for any reason, it will resume where it left off on the next drive mount.

Contact Us

If you encounter any issues with this release, you can let us know at: https://stablebit.com/Contact

StableBit Scanner 2.5.4.3209 BETA

Posted in StableBit on July 21st, 2018 by alex – Be the first to comment

StableBit Scanner 2.5.4.3209 BETA

A new BETA of the StableBit Scanner is now available for download.

Download it here: https://stablebit.com/Scanner/Download

Full change log: https://stablebit.com/Scanner/ChangeLog

This is mostly a bug fix release with some minor enhancements.

Settings Backup and Restore

Settings

Settings Backup and Restore

Under advanced settings and troubleshooting you now have options that enable you to backup and restore the StableBit Scanner settings and application state.

The backup is very straight forward, you simply pick a folder where you would like to store the backed up settings, and your settings will be backed to into that folder. To restore your settings, simply select the same folder and the StableBit Scanner will override all of your existing settings with the settings from the backed up location.

All non-UI related persistent data is backed up and restored. StableBit Scanner settings, notification settings, custom disk names, locations and scan history are among the things that are backed up. UI related data such as window position and state is not included in the backup.

PCIe Speed

PCIe Speed

For NVMe drives, the StableBit Scanner now shows the PCIe version, width and link speed of that drive under Disk Details.

As always, if you encounter any issues with this BETA, please let us know here: https://stablebit.com/Contact

StableBit Scanner 2.5.2.3190 Release Final

Posted in StableBit on July 6th, 2018 by alex – Be the first to comment

StableBit Scanner 2.5.2.3190

StableBit Scanner 2.5.2.3190 Release Final is now available for download.

Get it here: https://stablebit.com/Scanner/Download

Full change log: https://stablebit.com/Scanner/ChangeLog

What’s New Since the 2.5.1 Release Final:

  • Full support for the NVMe 1.3 specification.
  • Updated support for ACS-4 and SATA 3.4.
  • Additional new themes.
  • Bug fixes based on reported issues.

Now let’s talk about some other noteworthy changes since my post about the last BETA.

Pause Scanning

Pause Scanning

You now have the option of telling the StableBit Scanner to pause scanning for a period of time. Scanning will be disabled for the selected time period and will automatically be re-enabled for you at the end.

If you need to temporarily disable scanning for any reason, rather than disabling scanning entirely, this is a better option to use so that you don’t forget to re-enable it later.

New Disk Information Columns

Disk Active Percent / Last Scanned

There are 2 new columns that you can enable for each disk, Disk Active % and Last Scanned.

Disk Active % shows you how busy each disk is, with 0% being fully idle, and 100% being fully active. This offers you a quick at a glance view of how busy your entire set of disks are.

Additionally, the Last Scanned column show how long ago the disk was fully scanned. In particular, this takes the time of the oldest scanned block on the disk and show you how long ago that was.

Specification Updates

In addition to adding support for NVMe 1.3, the StableBit Scanner is now updated with support for ACS-4 and SATA 3.4.

Additional TRIM information is also shown, such as whether TRIM is fully enabled and supported by the drive.

SSD SMART Interpretation Rules

This may not be immediately visible in the UI, but SMART interpretation rules (from BitFlock) have also received a large update on the back-end prior to this release. You may start to see SDD life and endurance information for your SATA based SSD where there were none previously.

StableBit CloudDrive 1.1.0.1025 BETA

Posted in StableBit on June 16th, 2018 by alex – Be the first to comment

StableBit CloudDrive 1.1.0.1025 BETA

The latest StableBit CloudDrive BETA features 3 new storage providers, adds support for third party Amazon S3 services, and as always has a number of bug fixes and improvements.

Download it here: https://stablebit.com/CloudDrive/Download

Full change log: https://stablebit.com/CloudDrive/ChangeLog

New Storage Providers

Amazon S3 (Updated)

Amazon S3

Amazon S3 now supports third party service endpoints. Just enter the third party service URL and you’re ready to go.

For example, you can even use something like the the Minio server to set up your own Amazon S3 compatible storage endpoint.

Minio download: https://www.minio.io/downloads.html#download-server-windows

Backblaze B2

Backblaze B2

Backblaze B2 offers business grade storage at an affordable rate.

Service: https://www.backblaze.com/b2/cloud-storage.html

Pricing: https://www.backblaze.com/b2/cloud-storage-pricing.html

OpenDrive

OpenDrive

OpenDrive offers very affordable personal and business plans, and even has unlimited storage space and bandwidth options.

Service: https://www.opendrive.com/

Pricing: https://www.opendrive.com/pricing

Rackspace Cloud Files

Rackspace Cloud Files

Rackspace Cloud Files is an enterprise grade storage solution powered by OpenStack.

Service / pricing: https://www.rackspace.com/cloud/files

Default I/O Performance Settings

Default I/O Performance

Additionally, this BETA features new default I/O performance settings that will get applied automatically to any new cloud drives that you create, saving you the hassle of configuring each new drive individually.

Default I/O Performance Menu

To set up your default I/O performance settings, open the Options menu and select Default I/O Performance…

Release Final

That’s all for now. This is a pretty straightforward release, so we’ll try to make this a short BETA and hopefully have a release final out soon.

As always, please let us know if you encounter any issues at: https://stablebit.com/Contact

StableBit Scanner 2.5.2.3175 BETA

Posted in StableBit on May 9th, 2018 by alex – Be the first to comment

StableBit Scanner 2.5.2.3175 BETA

StableBit Scanner 2.5.2.3175 BETA is now available for download:

https://stablebit.com/Scanner/Download

For a complete list of all of the changes, see the change log:

https://stablebit.com/Scanner/ChangeLog

NVMe Support

This BETA of the StableBit Scanner adds support for the latest NVMe specification (1.3).

Disk Details

This new comprehensive support is on full display when you open up disk details on an NVMe drive:

Disk Details

Each item also features a detailed tooltips that describes what is being shown:

Disk Details Tooltip

NVMe Health

Along with the technical information, StableBit Scanner now has full support for the NVMe on-disk health data:

NVMe Health

The NVMe health data includes:

  • The disk life used percent, as reported by the drive.
  • The current composite temperature. The composite temperature is the overall temperature of the drive when multiple temperature sensors are present.
  • The Warning and Critical temperatures as defined by the manufacturer.
  • Whether the drive has ever exceeded either the Warning or the Critical temperatures over its lifetime and for how long.
  • The remaining space capacity, along with a manufacturer defined threshold (if provided).
  • The total bytes read and written along with the number of commands sent.
  • The number of power cycles that the drive has gone through.
  • The number of unsafe shutdowns (power loss events).
  • The number of data integrity errors that the drive has reported over its lifetime.
  • Whether the drive has ever throttled itself due to overheating, and for how long if it has.

If any of these attributes start indicating that the drive may be experiencing issues, StableBit Scanner will let you know by issuing a Warning or a Critical Warning, along with an explanation of what has gone wrong.

S.M.A.R.T. vs NVMe Health

S.M.A.R.T. Settings

For all intents and purposes, while looking similar to the S.M.A.R.T. data that was always available for SATA drive, StableBit Scanner treats the NVMe health data entirely separately. Any options that are S.M.A.R.T. related do not apply to NVMe.

Notifications

NVMe Notifications

NVMe health notifications support all of the existing notification methods, and are enabled by default. But you can disable them if you so choose to.

Temperature Warnings

Temperature Settings

For overheat warnings, if you have Use manufacturer specified maximum operating temperature checked, then the StableBit Scanner will issue an overheat warning if the drive ever exceeds the NVMe Health Warning Temperature, as reported by the drive.

Additionally, if you have the Warning Threshold checked, then an overheat warning will be issued when the drive temperature exceeds the warning temperature as defined by the drive, or the critical temperature minus the warning threshold, whichever is lower.

You don’t really have to worry about how this all works because the default settings should work just fine.

No Temperature Thresholds

Not all NVMe drives will report warning / critical temperature thresholds.

Maximum Temperature

For drives that don’t, the StableBit Scanner will simply issue a warning when the drive exceeds the Maximum Temperature, as specified in the StableBit Scanner settings.

Override Maximum Temperature

As before, you can always override the maximum temperature on a per-drive basis from Disk Settings. The maximum temperature you specify here, is simply used as is without applying any additional logic.

New Themes

This version includes a number of new themes. In addition to the new Office 2016 theme, which is shown above, we have:

Material Theme

Fluent Theme

OS Dependent Theme Selection

If you have automatic theme selection enabled, the StableBit Scanner will now select an appropriate theme depending on whether it’s running on a server based Operating System or not.

For Example, on Windows Server 2016, the Office 2016 theme is used:

Windows Server 2016 Essentials

While on Windows 10, the Material theme is used:

Windows 10 (Material)

WSSX Installer

Starting with this BETA, the Windows Server Essential WSSX installer is no longer available. But don’t worry, the server essentials dashboard add-in is still fully supported. It’s simply being rolled into a single unified installer (just like the other StableBit installers).

It’s also really simple to upgrade from the old WSSX installer to the new unified installer.

If try to install the new BETA, and you’ve previously used the WSSX installer, you will see this message:

Uninstall Add-in

Simply open the Windows Essentials Dashboard, select the add-ins tab.

Remove Add-in

Choose the StableBit Scanner and click Remove the add-in.

Close the Dashboard

Don’t forget to close the Dashboard to complete the add-in removal.

Once the add-in is removed, simply run the new EXE installer and it will reinstall both the Dashboard add-in and the standalone version. All of your existing settings and scan data will not be affected.

Windows Home Server 2011

Volume Map

Volume Map

Finally, the Volume Map was extracted from the StableBit Scanner UI into a separate application that can be launched from the start menu. It has received some enhancements and will also follow the new OS dependent theme rules, just like the main StableBit Scanner UI in Auto mode. Unlike the StableBit Scanner UI, the currently active theme of the Volume Map cannot be changed.

Release Final

Coming up next for the StableBit Scanner is the release final of 2.5.2. If you experience any issues with this BETA, do let us know @ https://stablebit.com/Contact

StableBit DrivePool 2.2.0.906 Release Final

Posted in StableBit on March 10th, 2018 by alex – Be the first to comment

StableBit DrivePool 2.2.0.906

StableBit DrivePool 2.2.0.906 is now available as a Release Final.

Download it here: https://stablebit.com/DrivePool/Download

Full change log: https://stablebit.com/DrivePool/ChangeLog

Updated user manual: https://stablebit.com/Support/DrivePool/2.X/Manual

Translations

For those who have participated in the community translation effort, thank you for doing that. This version has some significant community edits to the Japanese and Italian translations since the last RC, among other corrections.

If you’d like to participate in the community translation effort, head on over to http://translate.covecube.com (powered by OneSky) and submit your corrections, or simply vote on some of the existing ones. Your edits will be included in the next release.

Compared to version 2.1.1.561, this version now includes 3 new languages:

  • Dutch
  • Japanese
  • Russian

Bug Fixes

Aside from the new features, a very big part of this release was about fixing any existing bugs and ensuring the stability of the application. In fact, if you look at the full change log, almost every change prefixed with [Issue #…] is a fix that resulted from a user having a conversion with technical support that ended up spawning a Code Change Request. Most code change requests eventually ended up in a fix made to the code.

For the more complex code changes, sometimes additional information was made publicly available on our issue tracking system, for example see: Issue #27704

After a lot of hard work, today, we are down to 0 open bugs for StableBit DrivePool. As a result this version is being made available as a Release Final.

But we’re not done, if you do encounter an issue that you’d like to report, you can do so here: https://stablebit.com/Contact

I’d like to give a big thank you to Christopher Courtney for heading up the technical support effort and for handling the myriad of issues that have come up over the testing cycle of this release.

In this post, I want to highlight the most significant new features or changes since the last release final of StableBit DrivePool, which was version 2.1.1.561. Because I’ve already talked about some of the new features available in this release in previous blog posts, I won’t be going into much detail on those topics again.

Let’s dive right into a short summary of each new feature that I would like to highlight.

User Feedback

User Feedback

One very visible new feature is the new user feedback system.

StableBit DrivePool is built as a task-oriented application. That means that almost every long running action is treated like a task that can end in various levels of success or failure. With user feedback, this is now exposed in the user interface.

User Feedback Colors

The result of each finished task is color coded using the above levels of severity.

Additionally, a failed task may have actions that you can perform on it in order to resolve the failure.

See user manual: UI Overview > Feedback

Drive Removal Overhaul

Files in Use

The process of removing a drive from the pool was mostly overhauled for this release in order to make it more robust and less intrusive.

In summary:

  • The pool no longer becomes read-only while a drive is being removed.
  • Duplicated open files can remain open on a drive that’s being removed.
  • Unduplicated open files can be force closed (safely) on a drive that’s being removed.

For more information see my previous blog post (under Drive Removal Improvements): http://blog.covecube.com/2017/09/stablebit-drivepool-2-2-0-847-beta/

See user manual: Removing a Drive from the Pool

Hierarchical Pooling

HybridPool Hierarchy

Hierarchical pooling support is a major new feature of this release, and I’ve covered it extensively in a previous blog post.

In summary:

  • A pool can now be added to an existing pool, just like a regular drive.
  • Each pool in the hierarchy has separate file duplication, file placement and balancing settings.
  • A child pool can set individual file duplication, file placement and balancing settings on files that are stored in a parent pool.

For more information see my previous blog post (under Hierarchical Pooling): http://blog.covecube.com/2017/09/stablebit-drivepool-2-2-0-847-beta/

See user manual: Adding a Drive to the Pool > Hierarchical Pooling

Read Striping Priorities

Each pool member (drive or pool) now has a read striping priority associated with it, and StableBit DrivePool will always try to read from the highest priority class available for each duplicated file.

For example, if a file exists both locally and in the cloud, that file will always be read from the local drive or pool. Similarly, if a file exists on an internal drive as well as on an external USB drive, it will always be read from the internal drive.

See user manual: Performance Options > Read Striping

Disk Tooltip Updates

Disk Tooltip

Disk tooltips have been updated as well with more information about each pool member.

A Cloud Pool

The type of the pool member will also be shown like this.

See user manual: Disks List > Tooltips

Performance UI Updates

Pool Performance

In addition to showing the instantaneous read and write speeds on the pool, StableBit DrivePool will now show how many files are currently open on the pool. Hovering over the open file count will bring up the file open rate tooltip (i.e. file opens per second).

If your pool is consuming CPU cycles, and you’re not sure why, this is an important performance metric to take into account.

See user manual: Performance UI > Pool Performance

File System Performance Improvements

This version of StableBit DrivePool features some significant low-level performance improvements to the pooling file system. It should boot faster and require less overhead when opening files on the pool.

Mount Speed Improvements

In order to speed up pool mount time and avoid missing disk warnings, each pool is now aware of how many pool parts it is comprised of.

At boot time, a pool will wait for new disks to arrive for up to 10 seconds, but only if any pool parts are missing. Otherwise, the pool is mounted instantly.

Many Thousands of Open Files

Previous versions of StableBit DrivePool would struggle to maintain a good file open rate when dealing with many thousands of concurrently open files. This would cause CPU bottlenecks, especially when dealing with large pools and Windows Search.

Thanks to an updated algorithm, version 2.2.0.906 can now handle up to 1 million concurrently open files without suffering a performance penalty in its pooling file system (provided that you have enough RAM).

DPCMD Updates

DPCMD is the command line utility that comes with StableBit DrivePool and offers some additional functionality.

In this version, DPCMD can now list all of the open files on the pool.

list-open-files

Additionally, you can now force close one or more open files like this:

>dpcmd force-close-open-files P:\ *.MP4

Unlike other methods of force closing handles, this will safely close only pool part handles by communicating with the pooling file system directly. It will leave the pool handle open, but any I/O attempted on the pool with that handle will fail form that point on.

Miscellaneous Updates

Here are some other miscellaneous but noteworthy updates:

  • Real-time file size tracking was reworked.
  • Reparse points were reworked:
    • Proper support for remote to local symbolic links.
    • Support for non-Microsoft reparse points.
  • Advanced settings are now stored in the JSON format at: %PROGRAMDATA%\StableBit DrivePool\Service\Settings.json

For a complete list of all of the changes, see the full change log.

StableBit CloudDrive 1.0.2.976

StableBit CloudDrive 1.0.2.976

The Release Final of StableBit CloudDrive 1.0.2.976 is now available as well.

Download it here: https://stablebit.com/CloudDrive/Download

Full change log: https://stablebit.com/CloudDrive/ChangeLog

This release features mostly bug fixes and is meant to be used together with StableBit DrivePool 2.2.0.906.

StableBit DrivePool 2.2.0.900 RC

Posted in StableBit on January 19th, 2018 by alex – Be the first to comment

StableBit DrivePool 2.2.0.900 RC

The Release Candidate of the next version of StableBit DrivePool is now available.

Download it here: https://stablebit.com/DrivePool/Download

Compared to the last BETA (2.2.0.881) this version includes optimized performance when dealing with many thousands of open files, a more intelligent mounting process and localization support for 10 languages.

Translations

This release features professional translations to 4 languages: French, German, Italian and Spanish. It also features community translations for: Bulgarian, Dutch, Japanese, Polish and Russian.

If you are a native speaker of any of those languages and you’d like to make corrections to any of those translations, head on over to http://translate.covecube.com and submit your corrections. Don’t forget to star your translations because the build system will always pick the translations with the greatest number of votes.

If you’d like to see a new language added, send us a note at https://stablebit.com/Contact. Any corrections submitted will be integrated into the next release final. Thank you everyone who has participated in the translation process thus far, we really appreciate it.

English Fallback

Switch to English

If you find the new translations problematic, you can easily switch back to English by opening Settings and selecting Switch to English.

If you see another issue with the translations that can’t be easily resolved, please let us know at: https://stablebit.com/Contact

StableBit CloudDrive RC

StableBit CloudDrive 1.0.2.975 RC is also now available.

Download here: https://stablebit.com/CloudDrive/Download

This is a companion release that improves compatibility with StableBit DrivePool when both are used together, and as always it also includes some bug fixes.

Release Final

Coming up next is the release final and I’ll make a more comprehensive blog post about what has changed since the last release final, version 2.1.1.561.

Thank You for 2017

A huge thank you to everyone who has purchased a license, recommended our software to someone else, and supported us throughout 2017. I hope everyone has a great 2018, and we have some really great things planned for this year, so stay tuned.

StableBit DrivePool 2.2.0.847 BETA

Posted in StableBit on September 15th, 2017 by alex – Be the first to comment

StableBit DrivePool 2.2.0.847 BETA

StableBit DrivePool 2.2.0.847 BETA is now out.

Get it here: https://stablebit.com/DrivePool/Download

This new BETA comes with a substantial list of bug fixes, support for ReFS, an improved drive removal process, along with a brand new feature called hierarchical pooling.

Let’s dive right into the big new feature.

Hierarchical Pooling

What is hierarchical pooling?

Simply put, hierarchical pooling allows you to add another pool to an already existing pool, or to create a new pool from an already existing pool. Just like in previous versions, each pool has its own separate folder duplication rules and file placement rules which give you fine grained control over how your files are protected and where they are stored. With hierarchical pooling, in addition to that, you can now control how the contents of the parent pool is duplicated across the child pool, and you can even use file placement rules to control which drives (or pools) should be used to store the contents of the parent pool.

This is best illustrated with an example.

Example

LocalPool

Let’s say that I currently have a pool that stores all of its data on a number of local disks. Let’s call this my LocalPool.

StableBit CloudDrive

Now, let’s say that I have access to some cloud storage available across a number of providers, and that I’d like to utilize that storage to create a number of encrypted cloud drives.

CloudPool

For convenience, I pool all of those cloud drives into one virtual pool using StableBit DrivePool. Let’s call this my CloudPool.

I then decide that I want some of my data to be stored both locally and in the cloud (for backup purposes). But at the same time, I still want some of that data to remain duplicated locally, just in case a local drive fails.

I could of course manage all of this manually by copying files around across the different drives, but with hierarchical pooling in StableBit DrivePool, this is no longer necessary.

HybridPool

All I have to do is create a new pool that stores its data on CloudPool and LocalPool, and I’m going to call this my HybridPool.

HybridPool Hierarchy

With this simple setup, I now have great flexibility over the data that is stored on HybridPool.

HybridPool Folder Duplication

Here, using the file duplication settings on HybridPool, I’ve told StableBit DrivePool that I want “Documents”, “Pictures”, and “Software” to be stored both locally and in the cloud.

HybridPool File Placement

While at the same time, using file placement rules, I’ve configured “Videos” to be stored locally.

Any data on HybridPool will now get automatically reorganized in the background to follow those rules. Any new data written to HybridPool will automatically follow those rules in real-time.

But I want to go a few steps further. I want to have even greater control over how the data is stored both locally and in the cloud.

By setting the folder duplication rules on LocalPool, I can control how HybridPool’s data gets stored locally.

LocalPool File Duplication

Here, I’ve set up “Documents” and “Pictures” to be duplicated across 2 local disks, while “Software” and “Videos” will remain unduplicated.

LocalPool File Placement

Using the file placement rules on LocalPool, I’ve told StableBit DrivePool that I want HybridPool’s “Videos” to be stored on a particular local disk.

Now that I’m done setting up how my data should be stored locally, I’m going to set up how it should be stored in the cloud.

CloudPool Folder Duplication

Using the folder duplication settings on CloudPool, I’ve set it up so that HybridPool’s “Documents” and “Pictures” will be stored across all 3 of my cloud storage providers.

CloudPool File Placement

And using CloudPool’s file placement rules, I’ve limited “Software” to be stored specifically on Dropbox.

Summary

HybridPool Folders

What I’ve done here is set up very specific rules on how my data should be stored both locally and in the cloud using the new hierarchical pooling support in StableBit DrivePool.

It’s worth noting that, while my existing files on HybridPool will be reorganized in the background to follow these rules, any future changes to HybridPool will be automatically applied in real-time.

After setting up these rules, any data that I write to HybridPool will be transparently placed in the correct location, in real-time. The rules that we’ve set up are real-time file placement rules that are implemented in the Operating System’s kernel (for the best performance possible).

While I chose to use StableBit CloudDrive in conjunction with StableBit DrivePool for this example, you can certainly use hierarchical pooling without StableBit CloudDrive and still benefit from the greater control offered by it.

Drive Removal Improvements

In addition to hierarchical pooling, this new BETA has an upgraded drive removal process. Previously, when you removed a drive from the pool, the entire pool had to be made read-only in order to maintain data consistency while the drive was being removed. With this new BETA, that’s no longer necessary. You can now continue to use your pool normally, even while a drive is being removed.

Files in Use

The only limitation here, is that for unduplicated files, if files are in use on the drive that’s being removed, then drive removal will abort and you will get the above error message.

You can close the applications that are using those files and try removing the drive again, which will resume the removal process from where it left off.

Force Close Files

Alternatively, you can choose to force close those files from the Remove Options dialog.

ReFS Support

ReFS Pool

With this BETA, StableBit DrivePool is able to create ReFS pools. You can now use an existing ReFS volume to create a new pool or add a ReFS volume to an existing ReFS pool. Mixing ReFS and NTFS volumes in the same pool is not allowed.

Other Changes

There are a lot of other smaller changes in this BETA as well, such as:

  • An updated dpcmd command line interface.
  • Improved real-time file size tracking.
  • Support for some new Windows 10 / Server 2016 specific APIs.
  • Improved compatibility with StableBit CloudDrive.

See the full change log for all of the details.

Release Final

StableBit DrivePool 2.2 is now headed towards a release final. There will not be any more new features added at this point, only bug fixes.

As always, thank you for testing the BETAs (I know the 2.2 BETA has been a rather long one). Let us know of any issues that you encounter @ https://stablebit.com/Contact

StableBit CloudDrive 1.0.2.929 BETA

Posted in StableBit on September 12th, 2017 by alex – Be the first to comment

StableBit CloudDrive 1.0.2.929 BETA

StableBit CloudDrive 1.0.2.929 BETA is now out.

Get it here: https://stablebit.com/CloudDrive/Download

In addition to some bug fixes and optimizations, this release offers better compatibility with the forthcoming StableBit DrivePool BETA. When used together with StableBit DrivePool, you will be able to create all kinds of hierarchical pools, some of which can even be cloud and local hybrid pools. You will also be able to set individual folder duplication and file placement rules at each point of the pooling hierarchy.

Look for the new StableBit DrivePool BETA and much more information about hierarchical pooling coming very soon.

Minimum Download Size

One important optimization that is new in this version of StableBit CloudDrive is native support for a minimum download size.

Minimum Download Size

When set, StableBit CloudDrive will try to optimize your cloud drive’s read speed by always trying its best to download at least this much data from the storage provider, regardless of how much data is actually being read from the disk. The extra data that’s not needed is stored in the local cache (with a lower priority), just in case it’s needed in the future.

This new setting is implemented in the low level kernel disk driver itself for the best performance possible, and it also coordinates with the prefetcher to ensure that the prefetched data is using the correct block size.

Most storage providers will now default to a 1 MB minimum download size, but you can certainly increase that or even disable it completely at any time.

StableBit CloudDrive 1.0.1.879 Release Final

Posted in StableBit on June 8th, 2017 by alex – Be the first to comment

StableBit CloudDrive 1.0.1.879 is now available for download.

Get it here: https://stablebit.com/CloudDrive/Download

If you’re using Dropbox with StableBit CloudDrive, you should update to this version soon because Dropbox is discontinuing their older v1 API by the end of this month (June 2017). This version of StableBit CloudDrive implements the v2 Dropbox API, which Dropbox is requiring from all 3rd party applications.

Read-only Drives

A new read-only mode is now available in StableBit CloudDrive. When enabled, a cloud drive will report as a read-only medium, and it will actively reject any write I/O requests directed to it.

With the prevalence of ransomware today, this option can be useful in thwarting such malware from modifying the data on your cloud drive.

Mount Disconnected

A new option to mount your cloud drives in disconnected mode is now available for data recovery and troubleshooting purposes.

If you ever permanently lose access to your storage provider, it is now possible to mount any attached cloud drives without connecting to the storage provider.

Simply select Mount Disconnected from the Troubleshooting menu and click Retry…

Your cloud drive will now be mounted without connecting to the storage provider. It will use whatever data is available in the local cache in order to complete the drive mount. In disconnected mode, the cloud drive will remain read-only, and certain functionality, such as drive resizing, will not be available.

If you are able to restore the connection to your storage provider, you can exit disconnected mode by choosing the Reconnect… option under Manage Drive.

Edit: StableBit CloudDrive 1.0.1.880 fixes a small but significant bug that was present in the driver unload code of 1.0.1.879.