Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


 This section is the part of the OnApp installation procedure.
 Install Control Panel Server > Install Compute Resources > Install Data Stores > Install Backup Server > Configure vCloud Director Integration > Configure Cloud

 

 

Follow one of two processes to set up a backup server in your cloud:

  • Install Static Backup Server
  • Install CloudBoot Backup Server

Choose the one that suits you best.

On this page:

Table of Contents

 


 

Install Static Backup Server


 

To install static backup server, run the following procedure. Skip this section if you are using a CloudBoot method. We recommend installing CentOS from the minimal CentOS ISO for static backup servers.

 

  1. Add a backup server via the Control Panel user interface:

    1. Go to your Control Panel's Settings menu, then press Backup servers icon.
    2. Click the Create Backup Server button.
    3. Fill in the form that appears:
      • Label - give your backup server a label
      • IP address - enter the backup server IP address (IPv4)
      • Backup IP address - add a provisioning network IP address
      • Capacity - set the backup server capacity (in GB)
      • Backup server zone - select the backup server zone to which this backup server will be assigned.

    4. Move the Enabled slider to the right to enable the backup server.
    5. Click the Add Backup Server button.
     
  2. Update your server:

    Code Block
    bash# yum update


  3. Download the OnApp repository:

    Code Block
    bash# rpm -Uvh http://rpm.repo.onapp.com/repo/onapp-repo-5.1.noarch.rpm


  4. Install the OnApp Backup Server installer package:

    Code Block
    bash# yum install onapp-bk-install


  5. Anchor
    config
    config
    Check and set Backup Server default settings:

    Expand
    titleEdit Backup Server default settings by editing the /onapp/onapp-bk.conf file:

    OnApp BK tools custom version

    Code Block
    BK_VERSION=""

    OnApp StorageAPI custom version

    Code Block
    API_VERSION=""

    Default server to synch time on the HV

    Code Block
    NTP_TIME_SERVER='pool.ntp.org'

    The number of retries for WGET to download the file

    Code Block
    WGET_TRIES=5

    OnApp templates directory.

    Note
    Please refer to the corresponding settings at OnApp Control Panel web interface


    Code Block
    TEMPLATES_DIR='/onapp/templates'

    OnApp backups directory.

    Note
    Please refer to the corresponding settings at OnApp Control Panel web interface


    Code Block
    BACKUPSS_DIR='/onapp/backups'



    Code Block
    bash# vi /onapp/onapp-bk.conf

     

  6. Anchor
    installer
    installer
    Run the installer. It is recommended to download Base, Load Balancer and CDN templates while running the installer. You may rerun the installer later with the -t option.

    Code Block
    bash# sh /onapp/onapp-bk-install/onapp-bk-install.sh 


    Expand
    titleThe full list of installer options:

    Usage:

    Code Block
    /onapp/onapp-bk-install/onapp-bk-install.sh [-c CONFIG_FILE] [-a] [-y] [-t] [-h]

    Where:

    -c CONFIG_FILE 

    Custom installer configuration file. Otherwise, preinstalled one is used.

    -a 

    Do NOT be interactive. Processe with automatic installation.

    -y 

    Update OS packages (except of OnApp provided) on the box with 'yum update'.

    -t 

    Initiate Base, Load Balancer and CDN templates download.

    The download is initiated if '-a' option is used.

    -h 

    Print this info


     

     

  7. Сonfigure the backup server for your cloud. This step is also required for the SNMP statistics receiver configuration:

    Code Block
    bash#> /onapp/onapp-bk-install/onapp-bk-config.sh -h <CP_HOST_IP> -p [BK_HOST_IP] 


    Expand
    titleThe full list of configuration options:

    Usage:

    Code Block
    /onapp/onapp-bk-install/onapp-bk-config.sh [-h CP_HOST_IP] [ -p BK_HOST_IP] [-a|-i [USER:PASSWD]] [-s] -?

    Where:

    -h CP_HOST_IP

     FQDN or IP Address of the management server which should receive all status reports and is authoritative for this backup server.

    -p BK_HOST_IP

     FQDN or IP Address of Backup Server which will serve all stats related and other requests send by the CP_HOST_IP.

    Used by snmpd and StorageAPI.

    -a

     Install AoE

    -i [USER:PASSWD]

     Install iSCSI utils and configure with USER and PASSWD (if specified)

    -s

     Install sshfs

    -?

     Print this help info


     


  8. Run the following commands:

    Code Block
    # yum install gdisk


Install CloudBoot Backup Server


 

CloudBoot backup servers are CloudBooted KVM

compute

Compute resources that can be be used as backup servers.

 Follow

 Follow the step-by-step instructions provided in this chapter to configure CloudBoot backup servers in your cloud.

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.
  • We strongly recommend you to deploy one or more backup servers on your cloud
,
  • . Incremental backups are only supported with a dedicated backup server.
  • CentOS now defaults to NFSv4. This is known to cause compatibility issues so we strongly recommend that you use NFSv3 for all mounts. This can be done by passing -t nfs -o vers=3 in any mount commands.
  • To use the backup server, you have to add it to a backup server zone and assign it either to a compute resource or a compute zone.

 
To create a CloudBoot backup server:


  1. Update CloudBoot and CP server RPMs:

    Code Block
    yum update onapp-store-install yum update onapp-cp-install


  2. Configure CloudBoot settings:

    Code Block
    /onapp/onapp-store-install/onapp-store-install.sh 


  3. Create

new
  1.  new CloudBoot compute resource

with an IP address from the dynamic range. Refer
  1. : at the first step of the creation wizard choose the type - Backup (CloudBoot Provisioning and Backup Resource). Refer to the Create CloudBoot Compute

resource
  1. Resource section of

the Admin
  1. this guide for details.

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

    1. Go to your Control Panel's Settings menu, then press 
    Backup Servers
    1. Compute Resources icon.
    2. Click the 
    Create Backup Server
    1. Add New CloudBoot Compute Resource button. 
    2. In wizard menu click Backup (CloudBoot Provisioning and Backup Resource). 
    3. Select right MAC address of it.

    4. Fill in the form that appears:


    Tick the Enabled box to enable the backup server.
        • Label - give the compute resource a name
        • Pxe IP address - select an IP address for this compute resource from the address pool available
        • Enabled - move the slider to the right to allow VSs to be installed/booted on this compute resource
        • Compute Zone - select the compute zone, to which this compute resource will be assigned, from the drop-down list
        • Custom Config - specify any custom commands you want to run when compute resource is booted
    1. At this step, specify the Backup Server properties:

      • Label - give your backup server a label
      • IP address - enter the IP address of a
    compute
      • 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)

    1. Then, you shouldn't assign any drive, but it needs right NIC to be applied to the storage network.
    2. 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
    1. 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:

      1. SSH to the backup server
      2. Format the storage with your preferred filesystem type, e.g.:

        Code Block
        bash#> mkfs.ext4 /dev/sda


      3. Make folder for backups if it does not exist

        Code Block
        bash#> mkdir /backupstorage


      4. Mount the storage to /onapp/backups:

        Code Block
        bash#> mount /dev/sda /backupstorage


      5. Make folder for storing templates:

        Code Block
        bash#> mkdir /backupstorage/templates


      6. Make folder for storing backups:

        Code Block
        bash#> mkdir /backupstorage/backups


      7. Create symbolic links in /onapp:

        Code Block
        bash#> ln -s /backupstorage/backups /onapp/backups
        bash#> unlink /onapp/templates
        bash#> ln -s /backupstorage/templates /onapp/templates
     Add

      1. Add the following to custom config file:

        Code Block
        mkdir /backupstorage
        mount /dev/sda /backupstorage
        ln -s /backupstorage/backups /onapp/backups
        unlink /onapp/templates
        ln -s /backupstorage/templates /onapp/templates


    1. Update the database so that the location of the templates is known:

      
    1. a. Find the database password:

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

      b. Open the onapp database in MySQL: 

      Code Block
      bash#> mysql -p bash#> use onapp; 

      c. Find the ID of the backup server:

      Code Block
      bash#> select * from backup_servers;

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

      Code Block
      bash#> update templates set backup_server_id='[your_id]';


    2. To download the base templates during the installation to your Control Panel, download and run the following script:



    1. Code Block
      bash#> wget http://downloads.repo.onapp.com/get_template.sh
      bash#> /bin/sh get_template.sh


    Note
    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)

       

      Code Block
      mkdir /backupstorage
      mkdir /backupstorage/templates
      mkdir /backupstorage/backups
      mount /dev/sda1 /backupstorage/backups
      mount /dev/sda2 /backupstorage/templates
      ln -s /backupstorage/backups /onapp/backups
      unlink /onapp/templates
      ln -s /backupstorage/templates /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:

      Code Block
      mkdir /backupstorage
      mount /dev/sda1 /backupstorage/
      ln -s /backupstorage/backups /onapp/backups
      
      unlink /onapp/templates
      ln -s /backupstorage/templates /onapp/templates



     

     

     

     This section is the part of the OnApp installation procedure.
    Install Control Panel Server > Install Compute Resources > Install Data Stores > Install Backup Server > Configure vCloud Director Integration > Configure Cloud