Our high performance cloud storages are designed with security, speed, availability, flexibility, and ease-of-use in mind. All data is encrypted at rest and stored on enterprise grade SSD disks. Our storage options range across multiple performance classes and storage types, and are able to fulfill even the highest I/O requirements.
Our offering includes the following storage options:
Rocket Storages are backed by NVMe drives attached directly to the Server which boasts increased I/O bandwidth and lower latency. With a RAID 10 implementation over four disks within a compute node, they are not replicated like Distributed Storage over multiple storage servers, therefore it is recommended to have a backup plan to recover your data if anything were to happen.
Our S3-compatible Object Storage offering is developed keeping data sovereignty in mind, designed to be accessed from anywhere including websites, mobile applications or IoT devices. You can read more about our Object Storage offering here.
Your data is replicated across three availability zones within a location allowing our autorecovery and failover mechanisms to make sure that your data will always be available. This is achieved via networking and has certain trade-offs like lower I/O, bandwidth and higher latency. Distributed Storage comes in three performance classes: Standard, High and Insane. See the table below for more information and comparison to our Rocket Storage.
Storage Performance Classes
|Distributed Storage (Standard)||2000||100 MBps|
|Distributed storage (High)||6000||200 MBps|
|Distributed Storage (Insane)||15000||300 MBps|
|Rocket Storage||100000||1000 MBps|
Each storage can only have one connected server.
Rocket Storage currently has a snapshot capacity of one, with four backup schedules, and eight backups per schedule. See servers for limits on connecting storages to servers. All other limits can be lifted, these are static.
We offer multiple OS templates on gridscale like CentOS, Ubuntu, Windows etc.
Please note: Even though you can technically create very large storages, sometimes the underlying operating system cannot take advantage of that, like Windows with the standard MBR partition.
With the Backup Center, a backup schedule can be created to create full image backups. Within the Backup Center interface, you can configure the default backup schedule for all new storage within a project.
Alternatively any snapshot created can be exported to Object Storage, effectively making it a backup.
The first storage connected to the server becomes the boot device. It is possible that a server has no boot device even if multiple storages are connected, this normally happens when removing the boot device after connecting other storage. Simply navigate to the server in the expert panel to configure the boot device.