Page tree
Skip to end of metadata
Go to start of metadata

Flexiant Cloud Orchestrator runs a standard Ubuntu 14.04 LTS operating system, upon which it loads its own software during the install process.

Software

Any backup software that will work with Ubuntu 14.04 LTS can be used to back up the system as required. Individual backup plans and processes will vary dependant on customer requirements, HA configuration etc. Please contact us for more advice if required.

File locations to backup

Config Files

Extility specific configs and private keys are located in this directory:

/etc/extility/

Network configuration, including IP assignments for additional Billing Entities and any customisations are in the following file:

/etc/network/interfaces

Some customers may wish to backup the entire /etc directory. This is a good idea and should not require much storage space.

Database Dumps (Postgres)

Dumps of the xvpmanager & tigerilily Postgres based databases are taken every 3 hours. These are stored in the following location and can be copied straight from disk.

/var/spool/extility/postgres/backups/

You may wish to use your own Postgres-aware backup solution. We provide these automatic dumps for your convenience.

Binary Files

Generally these files are provided by our software packages and should contain no variable data. You may still wish to back these up though.

/opt/extility

This is not a requirement for a successful system restore.

MySQL

The MySQL based 'flexicp' database should be backed up using MySQL-aware backup software. Taking a raw copy of the database files straight off the disk is strongly discouraged.

You may wish to configure master-slave replication, in which case ensure mixed mode or row based replication is used as statement based replication does not work with the UUID() function. Unlike with the smaller Postgres databases, we do not automate regular internal backups of the 'flexicp' database as this can grow fairly large and is sensitive to locking.

You should consult with your current backup solution vendor and establish a method for taking backups of this database.

Restore Procedure

 

If restoring multiple databases, ensure your backups were taken at, or as close to, the same time as each other. Inconsistencies will otherwise occur. Restoring a single database may cause the system to become out of sync. Please contact Flexiant Support before attempting database restores.

Database Restore

If you need to restore your databases to a previous state this can be achieved with the procedure outlined below. This requires you are logged in as 'root' via SSH or the console.

  1. Stop all FCO services
  2. Perform database restore (see database specifics below)
  3. Start all FCO services

MySQL (flexicp) 

  1. Login to MySQL locally
  2. Drop 'flexicp' database
  3. Create 'flexicp; database
  4. Restore all tables & data from backup (mysql flexicp  < /path/to/backup)

Postgres (tigerlily & xvpmanager)

<dbname> should be either 'tigerlily' or 'xvpmanager'

  1. Change to 'postgres' user
  2. Run dropdb <dbname>
  3. Run createdb <dbname>
  4. Restore all tables & data from backup (psql <dbname>  < /path/to/backup)

Full System Restore

You must know which version of Flexiant Cloud Orchestrator a set of backups is for. Attempting to restore to a different version of the software may not work.

  • No labels