Your cookie settings

We use cookies. By clicking "Submit Preferences" you are consenting to the use of cookies and understand that you can update your cookie preferences at any time. For more information about which cookies we use and how to change your preferences please visit our Privacy Policy page.

Some cookies are necessary for the usual function of our website. These are destroyed when you close your browser and do not store any of your details. Please note that choosing this option will result in you seeing this message each time you visit a new page as we are not storing any preferences for you.

In order for us to remember the preferences you select today and ensure that you don’t see this message again, we need to store a cookie to remember you. This is the only tracking cookie we will store if you select this option.

By selecting ‘all cookies’, you are consenting to the use of cookies and understand that you can update your cookie preferences at any time. For more information about which cookies we use and how to change your preferences please visit our Privacy Policy page.

Secure Archive Cloud

Secure Archive Cloud

Our storage leverages IBM’s IDA (Information Dispersal Algorithms), which slices your data and replicates it across 3 geographically separate UK data centres. Data from a single node is secure; it is not recoverable, but only 2 sites are needed to allow you to operate ensuring application availability in the event of a single data centre outage or multiple node failure.

Is it right for me?

Traditional storage only scales to a point before becoming difficult to manage, prone to reliability issues and expensive, in both capital expenditure and engineering time. When storing data on traditional media, for instance, the risks of compromising the integrity, availability and security of the data increases when the amount stored exceeds the limitations of the hardware. Bit error rates and rebuild times of traditional RAID systems, for example, can be, at best, detrimental to your performance and, in the worst case scenario, cause a complete outage while recovery takes place.

However, short or long term storage of backup and archive data needn’t require expensive disk arrays, tape loaders or NAS devices. Our 3 UK data centres, each with full resiliency and extensive physical security measures, means than you can store and distribute your data safely, effectively and with high availability. Alongside guaranteed UK data sovereignty and residency.

Negate the need for expensive, large capacity storage hardware with The Bunker’s Cloud Object Storage for your data backup and archive.

Why choose The Bunker?

The Bunker’s object storage offers the resiliency and flexibility of the popular industry storage systems, but with the key advantages of knowing where your data is stored and being provided with 2 industry standard APIs: S3 and OpenStack. Alternatively, the simple object interface can be integrated into your code, allowing you to simply store your metadata to referenced objects.

The aforementioned API flexibility allows you to bring your data into our UK data centres by porting across your existing applications, either as their primary function or for scaling between providers. You can rest easy, confident that your applications will be operational and functional during a single provider outage.

How Secure Archive Cloud works

Data is received into one of our data centres through our global load balancing services, routed externally or through our dedicated “direct connect” services subject to your business’ needs. Further resiliency is provided between each accessor node by our dedicated object based storage load balancing. The Accessor encrypts, encodes and disperses the data, which is then stored on the Slicestore devices across 3 UK tier4 data centre sites.

Using sophisticated mathematical algorithms, data is separated and dispersed into slices using erasure codes to manipulate the data and provide redundancy via error correction techniques. Errors during transit are minimised using forward error correction, which allows the data to self-heal using extra information added by the system, without the need to re-transmit the entire slice of data again. The very same technique is applied to data at rest, and the extra data means that a user only requires a percentage of the “slices” to re-create data.