Storegrid™ Deployment Scenarios

Storegrid™ Deployment

Storegrid™ supports several different deployments. This page provides the details of each of them and the advantages of each of these deployments.

Installing Storegrid™

  • Storegrid™ Client – the client build should be installed in the client machines (Desktops, Laptops & Servers) that need to be backed up. Storegrid™ supports backing up of Servers such as File Servers, MS SQL Database Servers, Exchange Servers etc.
  • Storegrid™ Backup Server – server build should be installed in the Storegrid™ backup server where the backed up data is to be stored. If the backed up data is to be stored in a SAN, NAS, USB Drives or some other disk based storage device, you can install Storegrid™ in a machine and then mount the SAN, NAS devices using networking protocols (CIFS in windows and NFS in Linux). The Storegrid™ Backup Server can then be configured to store the data in the mounted device.
  • Storegrid™ Replication Server – to provide redundancy to the backup server, a replication server can be setup and the backup server can be configured to replicate to it. Storegrid™ Server build should be installed in the replication server machine and during installation, the installation type should be selected as ‘Replication Server’. A typical deployment would be with the Replication Server installed in an offsite location (like a datacenter or a geographically remote location) to replicate a local backup server, to make sure there is an offsite copy of the backed up data in case of disaster recovery.
  • Storegrid™ Cluster – Storegrid™ Backup & Replication Servers can be setup as a cluster, deployed with a centralized RDBMS to serve 100s and 1000s of clients for backup/restore. More on cluster deployment of OpenMinds – Storegrid™ servers


Deployment Scenarios

The following are the major deployment scenarios:

  • Local & Offsite Backups – Store the backup data locally and a redundant copy offsite.
  • Offsite Backups – Store all backup data offsite (via Internet/VPN).
  • Cloud Deployment – Backup or replicate to a server on Cloud.

Local & Offsite Backups

In this deployment, the Storegrid™ Backup Server is setup in the local LAN and it is replicated to a Replication Server in a geographically remote location. This ensures that two copies of the backup data is present, one locally and the other in the remote location. This type of deployment is especially helpful when size of the data-sets is huge and restoring it from a remote backup server might be slow due to limited available bandwidth.

As the backup server is local, the restores are fast, but the offsite redundant storage that the replication server provides is necessary for disaster recovery.

Local Offsite Deployment Schematic

Offsite Backups

In this deployment, the Storegrid™ Backup Server is in an offsite location and it replicates to a Replication Server (optional) in a geographically different location. This provides two copies of backup data in remote locations.

The redundant storage of backup data in the replication server, though optional, is highly recommended. The Replication Server gives the option for the Storegrid™ clients to restore the data from the Replication Server if the Backup Server is down or inaccessible. Also, the backup server can be reconstructed back in case it crashes, from the data in the replication server through the Server Disaster Recovery feature.

Offsite Deployments Schematic

Cloud Deployment

With the advent of cloud technologies (such as Amazon EC2 (Elastic Compute Cloud), Google AppEngine, Windows Azure, etc.), deploying Storegrid™ on the cloud is one of the desirable deployment scenario. Initially, Storegrid™ has been released for the Amazon Cloud (EC2) and in future other cloud deployments will also explored and supported.

Amazon EC2 Deployment

Storegrid™ Backup Server and Storegrid™ Replication Server can be run on Amazon EC2. The Storegrid™ Cloud AMI can be placed as a Remote Backup Server and Remote Replication Server (as in offsite deployment), or as a Remote Replication Server (as in local & offsite deployment).

Amazon EC2 Deployment Schematic

In Storegrid™ deployment in the Amazon Cloud, the Amazon’s EBS(Elastic Block Store) Volume is used as a local cache for improved backup performance. Later, the data is uploaded to Amazon S3 (Simple Storage Service) and is then removed from the local cache.

This enables an unlimited storage pool for Storegrid™ Server using the available Amazon Web Services. Storegrid™ Cloud AMIs are available for United States as well as the Europe data centers of Amazon EC2.

Storegrid™ can also be deployed in the cloud as a Storegrid™ client to backup the Amazon EC2 instances and the data available in the cloud to an offsite Backup Server.

See our Installation Guide