Indigo Prime - Data Management, Backup and Recovery

Medium/Small Business System

The simplest and most popular way to use Indigo on a small network. Simply install, click and your data is protected automatically. For a complete tutorial on how to set up the architecture shown above please read the Setting Up Indigo Backup for Corporate Systems Tutorial

Basic Indigo Backup Features

Secure
Remote Administration
Scalable and Predictable
You require copies of Indigo Backup, 2 or more copies of Indigo Grid, client PC or laptops running Windows, 1 server running Windows.
Consider using a more complex Indigo Backup setup if you have a mixed network, or access to two or more servers
Recommended for groups of less than 200 users
Suitable for Indigo Backup versions 1 to 5, and Indigo Grid versions 1 to 2.

Main Drawback of this Architecture

If the combined admin/backup server goes down, monitoring stops until it is back up again, because your Indigo_Admin database is located on the same server as the backup share used by your backup clients. With a split backup and admin system such as that shown in the Full Corporate Systems example this issue is avoided.

Indigo Backup Features You Should Consider Using

A customised Indigo Admin database located on a separate server.
Network Locking - Specify subnets on which Indigo Backup may be active to prevent backup over low speed lines such as VPN
Predictive Monitoring - Get advanced warning of any additional modifications that you may need to make to your backup network to keep it running smoothly

Option Locking - Prevent your users from changing certain options in Indigo Backup.

Automatic Updates - Centralised updates for your users Indigo Backup system

Initial Indigo Setup - Set the basic features up automatically for each user upon install.

Email Remote Administration - Have Indigo Grid email you each scan so that you can keep up-to-date with your backup system from anywhere in the world.

Example Architecture (A)

Example Architecture (A)

Example Architecture A shows you a real example of a working Indigo Backup Network using the Grid system. An Indigo Grid set up as a Master is placed on the Backup Server. The Indigo Grid Master on the Backup Server is set to monitor the Indigo Admin database and backup share health and size on the Backup Server. It is set to conduct monitoring between 2 am and 4 am on Monday morning when the least number of employees are using the network to minimise network impact. The Indigo Grid master is also set to email the results of it's monitoring to the primary admin PC. It has an email client set up on it for this purpose. Indigo Grid automatically interfaces with this client to send the data files. However, because the Indigo Grid master and Indigo Admin database are located on the backup server, should the backup server crash the Indigo Grid system cannot still continue monitoring. For a more robust system you should consider using the Indigo backup setup depicted in the Full Corporate System example.

The primary admin PC has a copy of Indigo Grid loaded onto it but set up as a slave. They can then load the Indigo Grid emailed data files on their local copy of the Indigo Grid software, once loaded the results can be used in exactly the same way as they could be on the master.

Indigo Backup is installed on each of the user PC's and backs up to the Backup Server. As the Indigo Admin database is located on the backup server no customised installation option is required for the Indigo Backup clients on the users PC.

In this way the architecture fulfills the many of the main goals of any secure backup system:

1. Security
2. Reliability
3 . Maintainability
4 . Automation