Bunker Deployment

Overview

Bunker supports several different deployments. This document gives the details of each of them and the advantages of each of these deployments.

Installing Bunker

Bunker Client: Bunker client build should be installed in the client machines (Desktops, Laptops & Servers) that need to be backed up. Bunker supports backing up of Servers such as File Servers, MS SQL Database Servers, Exchange Servers etc.

Bunker Backup Server: Bunker Server build should be installed in the Bunker 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 Bunker in a machine and then mount the SAN, NAS devices using networking protocols (CIFS in windows and NFS in Linux). The Bunker Backup Server can then be configured to store the data in the mounted device.

Bunker 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. Bunker 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.

Bunker Cluster: Bunker Backup & Replication Servers can be setup as a cluster, deployed with a centralized RDBMS to serve 100s and 1000s of clients for backup/restore.
 
 

Deployment Scenarios

The following are the major deployment scenarios

  1. Local & Offsite Backups - Store the backup data locally and a redundant copy offsite.

  2. Offsite Backups - Store all backup data offsite (via Internet/VPN).

Local & Offsite Backups

In this deployment, the Bunker 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 datasets 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.
 
 

Offsite Backups

In this deployment, the Bunker 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 Bunker 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 Server Disaster Recovery feature of Bunker.