CloudBoot Backup Servers

CloudBoot backup servers are CloudBooted KVM compute resources that can be be used as backup servers. Follow the step-by-step instructions provided in this chapter to configure CloudBoot backup servers in your cloud.

PLEASE NOTE:

  • You should configure some local or remote attached storage for persistent backups on the provisioning/backup server.
  • We strongly recommend you to deploy one or more backup servers for backups and VS provisioning when using a CloudBoot functionality.


To create a CloudBoot backup server:

  1. Update CloudBoot and CP server RPMs:

    yum update onapp-store-install yum update onapp-cp-install
  2. Configure CloudBoot settings:

    /onapp/onapp-store-install/onapp-store-install.sh 
  3. Create new KVM CloudBoot compute resource with an IP address from the dynamic range. Refer to the Create CloudBoot Compute Resource section of the guide for details.

  4. Ensure to choose the 'Backup' option and don't format disks.

  5. Go to your Control Panel > Admin > Settings menu, then press Backup Servers icon.
  6. Click the Create Backup Server button. 
  7.  Fill in the form that appears:
    Tick the Enabled box to enable the backup server.
    • Label - give your backup server a label
    • IP address - enter the IP address of a compute resource you have created at step 1
    • Backup IP address - add a provisioning network IP address
    • Capacity - set the backup server capacity (in GB)
  8. After that, assign your backup server to the backup server zone.

    If you intend to attach LVM-based storage and create backups, you should also add the IP address of the KVM compute resource added in step 1 in the 'Backup IP address' field of each of your compute resources.


Further steps:

  1. Format and mount the local storage:

    a. SSH to the backup server

    b. Format the storage, e.g.:

    #> mkfs.ext4 /dev/sda

    Note that 4 TB or larger drives cannot be formatted in the EXT4 file system under CentOS 6 backup servers. If you plan to use 4TB or larger drives, there are the following solutions:

    • Use a CentOS 7 Backup Server
    • Format drives in EXT4 externally and install them into CentOS 6 backup servers
    • Format drives in the XFS file system


    c. Mount the storage to /onapp:

    #> mount /dev/sda /onapp

    Add mount /dev/sda /onapp to custom config file also.

    d. Make folders for backups and templates:

    #> mkdir /onapp/backups
    #> mkdir /onapp/templates

     

  2. Copy templates from the Control Panel server to the Backup server using SCP:

    #> scp /onapp/templates/*.gz root@[backup_server_ip]:/onapp/templates
  3. Update the database so that the location of the templates is known:

     

    a. Find the database password:

    cat /onapp/interface/config/database.yml |grep password

    b. Open the onapp database in MySQL:

    #> mysql -p #> use onapp; 

    c. Find the ID of the backup server:

    #> select * from backup_servers;

    d. For all of the templates, set the required backup_server_id:

    #> update templates set backup_server_id='[your_id]';
  4. To download the base templates during the installation to your Control Panel, download and run the following script:


    #> wget http://downloads.repo.onapp.com/get_template.sh
    #> /bin/sh get_template.sh

If your backups disappear after rebooting the CloudBoot backup server with LVM storage, add mount command to CloudBoot backup server custom config after the reboot. This is a known issue which will be fixed in the future release.

To fix your custom config settings, use one of the following options provided in the examples below (you will have to specify your own device names):
  1. If you have a separate partition for backups and templates (/dev/sda1 and /dev/sda2):

    mkdir -p /onapp/backups
    mkdir -p /onapp/template
    s mount /dev/sda1 /onapp/backups
    mount /dev/sda2 /onapp/templates
  2. If you current array is detected as /dev/sda1 and currently everything is located in /onapp within templates and backup directories within:

    mkdir -p /onapp
    mount /dev/sda1 /onapp