Download Free Trial Contact Us Search
Call UltraBac Software Japanese Pages
 
  • slide 3
  • slide 2
  • slide 1
       Home   Company   First-to-Market Software Innovations   Cloud-Based Redundant File & Block Elimination API for OEMs

Cloud-Based Redundant File and Block Elimination API for OEMs


UltraBac Software has developed a hybrid file/block-based deduplication system called GCFOS (Global Common File Object Store). It can be easily integrated into Partner and OEM file and image-based backup solutions, enabling faster backups with less storage overhead. While all end users benefit from faster backups, Partners and OEMs will have the additional benefit of significantly reducing storage space through redundant file elimination (RFE). There are four ways that GCFOS can be deployed by Partners and OEMs:

GCFOS UltraBac Cloud-Based Repository
If an OEM uses UltraBac's single repository cloud infrastructure, all files found to be common would be copied and stored in UltraBac's Cloud, which are then accessible to all GCFOS clients. Pooling the common files of all clients in one "master" repository offers efficiencies of scale, and provides for backup time savings with a corresponding reduction of storage space. As new clients begin to use solutions that have been integrated with GCFOS, they will quickly discover that all of their common files already stored in UltraBac's Cloud are automatically eliminated. Having a significant number of clients actively subscribed to GCFOS, new common files are routinely introduced (for example, from a Windows update). These files will quickly be identified and transferred from the client for storage in UltraBac's repository. Once new common files have been backed up and added to GCFOS by the first client, the deduplication process is then automatic across all UltraBac clients, and for all clients of all UltraBac Partners and OEMs that use the GCFOS UltraBac Cloud-Based Repository option.

GCFOS Partner/OEM Cloud-Based Repository
Partners and OEMs can choose to create and manage their own GCFOS cloud servers. The repository can be configured to use Amazon S3, Microsoft Azure, Google, HP Helion, Rackspace, OpenStack, or a local/remote file store. The flexibility of the system allows the creation of a single shared GCFOS cloud, or creation of multiple cloud repositories depending on client requirements. Creating a single master repository (like with the UltraBac Cloud) would de-duplicate files across all Partner clients. Alternatively, a Partner can create a GCFOS cloud repository per client if and when required.

GCFOS Local Repository
For highly secure environments where even sharing a file hash could be deemed a security risk, GCFOS can be installed and run on a Windows Server located within a protected end user's private network. When configured in this way, service discovery and configuration of client machines is completely automatic. End users also have the option to create a GCFOS private cloud through a direct account with Amazon S3, Microsoft Azure, Google, HP Helion, Rackspace, OpenStack, or a local/remote file store. Additionally, block-level deduplication can be enabled for additional elimination of common data by enabling a common "block store" shared by all backup servers.

GCFOS Local Repository with Secondary Repository
This configuration works identically to the "Local Repository" option above, except that all data for common files stored on the primary repository will be duplicated on a secondary repository. Either repository can be a local filesystem or a cloud service. During any retrieval, the primary is checked first and will automatically fail-over to the secondary, providing redundancy for the repository.

NEW!  UltraBac now provides a .NET interface for client applications interacting with the GCFOS server. This allows you to add data deduplication capabilities to any Managed code solution, such as C# or Visual Basic (VB). The interface is fully documented, and comes with a simple example program in C# illustrating the use of the various methods available.

To begin the first step in adding GCFOS technology to your application, please fill out the OEM Form.


Type
Pros
Cons
UltraBac Cloud-Based Repository
  • No hardware to purchase/maintain
  • Simple to configure & setup
  • Access to pre-built enormous repository of already present common files
  • Low likelihood of files being donated to server
  • Higher latency than local
  • Security consideration – files are shared between all clients
  • Storage/retrieval of files determined by internet/cloud storage speeds
 
GCFOS Partner/OEM Cloud-Based Repository
  • Allows sharing of common files between all clients of the server
  • Medium likelihood of files being donated to server
  • Higher latency than local
  • Still security consideration – files are shared between all clients of the OEM/Partner
  • OEM/Partner must install, set up, and configure GCFOS in cloud
  • OEM/Partner must maintain GCFOS server and pay for cloud server & storage
  • Storage/retrieval of files determined by internet/cloud storage speed
 
Local Repository
  • Very low latency queries
  • Fast storage/retrieval of common files – limited only by local network/storage speed (when using local path)
  • No cloud provider charges for storage and network traffic
  • Can be augmented with block-level deduplication
  • Storage/retrieval of files still limited by internet/cloud provider when using cloud repository
  • Server for GCFOS must be purchased and maintained
  • GCFOS software must be installed, configured, and maintained
  • Steps must be taken to ensure that the repository is not lost, i.e., backups, if stored on a local path
  • High likelihood of files being donated to server
 
Local Repository (local path) with Secondary Repository (Cloud)
  • Very low latency queries
  • Fast storage/retrieval of common files – limited only by local network/storage speed (when using local path)
  • Redundancy assured of repository (using cloud storage provider)
  • Can be augmented with block-level deduplication
  • Server for GCFOS must be purchased and maintained
  • GCFOS software must be installed, configured, and maintained
  • Storage charges from cloud provider (traffic charges only in the case of local path unavailability)
  • High likelihood of files being donated to server
 

For more details on GCFOS, please visit our additional information page or frequently asked questions page.





Privacy Policy   |   Terms of Use   |   Site Map  |   Copyright © 1992 - UltraBac Software