EldoS | Feel safer!

Software components for data protection, secure storage and transfer

Storing CBFS inside a single file

Also by EldoS: CallbackFilter
A component to monitor and control disk activity, track file and directory operations (create, read, write, rename etc.), alter file data, encrypt files, create virtual files.
Posted: 05/20/2015 02:13:22
by Dax  (Basic support level)
Joined: 05/20/2015
Posts: 2

Is there an easy solution to store the CBFS inside a single file on HDD, and re mount it from there. (Using it like a VHD)
Posted: 05/20/2015 02:35:35
by Eugene Mayevski (EldoS Corp.)

Thank you for a good question.

The answer depends on what particular functions of CBFS you want to have.

CBFS itself is a redirector of filesystem requests to your application. As such it does not care where your code keeps the actual data.

We have a couple of products which do keep the data. These are SolFS ( https://www.eldos.com/solfs/ ) and CallbackDisk ( https://www.eldos.com/cbdisk/ ). Both of these products let you create a virtual disk.

SolFS offers a way to store the data in a single container, which can be stored as a file on the filesystem (or in other places such as in the cloud). SolFS is an engine that implements its own powerful filesystem, with optional compression and encryption.

SolFS comes in two editions, OS edition that offers a virtual disk, and Application edition which is embedded in the application and is accessed only via SolFS APIs.

CBFS is sometimes used by our customers together with SolFS Application edition to keep all data in single container, and still have flexibility that CBFS offers (access control, virtual data etc).

CBFS + SolFS App edition is probably what you were asking about. We have a sample for them working together.

SolFS OS edition can be used without CBFS if you don't need CBFS features and need just a container which can be mounted as a virtual disk.

Another option, as said above, is CallbackDisk. CallbackDisk lets you create a virtual disk and keep the disk image anywhere (with file on the real disk being the most likely backend storage). CallbackDisk doesn't implement its own filesystem, but once the "disk device" is mounted, you can format it to NTFS or FAT and on next mount you have a ready-to-use virtual NTFS disk.

CallbackDisk is not as flexible as CBFS though. While it lets you keep the backend container anywhere including the file on the disk, CallbackDisk doesn't offer control over individual files and directories on the virtual disk.

There's a comparison chart on https://www.eldos.com/virtual-storage/vs_compare.php that will shed some light on capabilities of each product.

Also if you describe in details what tasks you have and how your final design should look like, we'll be able to recommend you the correct product or combination of products.

Sincerely yours
Eugene Mayevski
Posted: 05/20/2015 19:37:24
by Dax  (Basic support level)
Joined: 05/20/2015
Posts: 2

Thanks Eugene,

My solution would be to use CBFS + SolFS App edition as you have mentioned. Can you please send me that sample.
Posted: 05/21/2015 00:26:28
by Eugene Mayevski (EldoS Corp.)

There will be an update of CBFS 5 today, and the sample for C++ will be included there. .NET sample is on the way.

Also you can easily modify Mapper sample to use SolFS instead of the system APIs -- SolFS API closely resembles the system one, so you would be able to do the replacements yourself easily.

Sincerely yours
Eugene Mayevski



Topic viewed 2170 times

Number of guests: 1, registered members: 0, in total hidden: 0


Back to top

As of July 15, 2016 EldoS Corporation will operate as a division of /n software inc. For more information, please read the announcement.

Got it!