Article ID: 113963, created on May 25, 2012, last review on Dec 1, 2016

  • Applies to:
  • Operations Automation

Configure OA system backup

Pay attention to protecting your business by developing the Disaster Recovery Plan. The goal of the Disaster Recovery Plan is to enable an organization to survive and re-establish normal business operations after disaster. Surviving means having an ability to recover all critical operations that can resume a business within a reasonable time frame.

There are many backup and recovery methods and specialized software and hardware applications, third-party backup and recovery solutions are not covered in this article. Instead, it helps configure OA built-in backup and recovery tools (for example, Windows Server Backup tool). For information on using the third-party Backup and Recovery software, refer to the corresponding manufacturer's documentation.

General notes

  • Configure periodic tasks to create full backups (weekly or monthly) and partial backups (daily) of servers in OA infrastructure.

  • If OA servers are installed Virtuozzo containers then use native Virtuozzo backup tools vzbackup/vzabackup to create backup of servers.

  • Configure periodic backup tasks of Virtuozzo containers registered in OA Provider Control Panel at Top > Services > Cloud Infrastructure > > Setup > VPS Backup Schedules (for legacy VPS module)

OA Management Node backup

OA MN on Linux

The following files and folders have to be backed up:

  • The folder where OA application is installed (by default - /usr/local/pem)

  • /etc/init.d/pem

Provided that OA is installed in the folder /usr/local/pem exclude the following directories from the backup:

  • /usr/local/pem/vhosts

  • /usr/local/pem/vhosts/sysvhosts

  • /usr/local/pem/vhosts/var/cores

Use the scripts /usr/local/pem/bin/backup.sh and /usr/local/pem/bin/restore.sh for backing up and restoring OA Management Node (MN). Run the scripts on OA MN under the root user's permissions. Put OA MN backup task into cron to run backups periodically.

Backup:

# /usr/local/pem/bin/backup.sh [-o output_directory] [–z] –t mn

  • -o output_directory – specify output directory (optional, default, current directory),

  • -z – compress with gzip (optional),

  • -t mn - the tag, which specifies that Management Node files should be backed up.

OA MN can run during backup script execution, so backup can be performed on a live system without downtime.

The format of backup filename is backup-YYYYMMDDhhmm-mn.tar[.gz]

YYYYMMDDhhmm - timestamp, it is a time when the backup was started.

OA MN on Windows

If OA database is running on the same host with OA Management Node exclude database from OA MN backup (it will be backed up separately).

Full backup:

  • Use the native Windows tool ntbackup.exe to create backup of system state and local drive(s) where OS and OA application binaries are installed.

Partial backup:

  • Use the native Windows tool ntbackup.exe to create backup of system state and the folder where OA application is installed (C:\Program Files\SWsoft\PEM or C:\Program Files (x86)\SWsoft\PEM).

Create scheduled task to create backups periodically:

  • Full backup - monthly
  • Partial backup - daily

OA UI server

OA UI Server on Linux

The folder /usr/local/pem/ui has to be backed up on UI server.

Run the script /usr/local/pem/bin/backup.sh as root on OA MN to create backup of all UI servers:

# /usr/local/pem/bin/backup.sh [-o output_directory] [-d dbhost] [–z] –t ui

The backup.sh script requires password-less SSH access from OA MN to UI servers, generate and put SSH DSA key of the user root on OA MN to the file /root/.ssh/authorized_keys on all UI servers.

OA UI Server on Windows

Use the instructions provided for OA MN on Windows above to backup UI server.

OA Database Server

PostgreSQL

Run the script /usr/local/pem/bin/backup.sh as root on OA MN to create backup of OA database:

# /usr/local/pem/bin/backup.sh [-o output_directory] [-d dbhost] –t db

Microsoft SQL Server

Use the backup_dbs.sql script included into OA distribution (doc/Scripts/backup_dbs.sql) to create backup of OA database running on Microsoft SQL server. By default backup will be stored in the folder c:\temp\sqlbak, the following data will be placed into it:

  • Content of the master database is placed in the master.bak file

  • The content of each database is placed in a separate N-name.bak file

    • N is an internal database number of SQL server

    • name is a name of a database.
  • The restore_dbs.sql file is generated during the backup process (with the backup_dbs.sql script). This file is used by the restore_dbs.cmd script which is also included into distribution (doc/Scripts/restore_dbs.cmd).

    Refer to the Disaster Recovery User's Guide for backup/restore instructions for all types of servers in OA infrastructure.

Additional information

See the global article OA Maintenance Guide for checking other important settings.

Search Words

psasysbckp

vps is missing in odin controlpanel

disaster recovery guide

vps info

backup MN

OA maintenance guide

disaster recovery

OSA and PBA backup and restore

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF