This section is the part of the OnApp installation procedure. |
---|
Install Control Panel Server > Install Compute Resources > Install Data Stores > Install Backup Server > Download and Configure Templates on Control Panel Server > Configure Cloud |
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.
- Add a backup server via the Control Panel user interface:
- Go to your Control Panel's Settings menu, then press Backup servers icon.
- Click the Create Backup Server button.
- 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.
- Move the Enabled slider to the right to enable the backup server.
- Click the Add Backup Server button.
Update your server:
Code Block bash# yum update
Download the OnApp repository:
Code Block bash# rpm -Uvh http://rpm.repo.onapp.com/repo/onapp-repo-4.1.noarch.rpm
Install the OnApp Backup Server installer package:
Code Block bash# yum install onapp-bk-install
Check and set Backup Server default settings:Anchor config config Expand title Edit 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
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.Anchor installer installer Code Block bash# sh /onapp/onapp-bk-install/onapp-bk-install.sh
Expand title The 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
С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] -f <FILE_TRANSFER_SERVER_IP>
Expand title The full list of configuration options: Usage:
Code Block /onapp/onapp-bk-install/onapp-bk-config.sh [-h CP_HOST_IP] [ -p BK_HOST_IP] [-f FTS_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.
-f FTS_IP
File Transfer Server FQDN or IP address used for daily cron update recovery ISO by recovery.sh
-a
Install AoE
-i [USER:PASSWD]
Install iSCSI utils and configure with USER and PASSWD (if specified)
-s
Install sshfs
-?
Print this help info
Ignore any errors stating stats and that vmon services aren't running. This is the expected behaviour at this stage.
Install CloudBoot Backup Server
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.
- 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 on your cloud, Incremental backups are only supported with a dedicated backup server.
Update CloudBoot and CP server RPMs:
Code Block yum update onapp-store-install yum update onapp-cp-install
Configure CloudBoot settings:
Code Block /onapp/onapp-store-install/onapp-store-install.sh
Create new CloudBoot compute resource with an IP address from the dynamic range. Refer to the Create CloudBoot Compute resource section of the Admin guide for details.
Ensure to choose the 'Backup' option and don't format disks.
- Go to your Control Panel's Settings menu, then press Backup Servers icon.
- Click the Create Backup Server button.
- 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)
- 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:
- Format and mount the local storage:
- SSH to the backup server
Format the storage with your preferred filesystem type, e.g.:
Code Block bash#> mkfs.ext4 /dev/sda
Make folder for backups if it does not exist
Code Block bash#> mkdir /backupstorage
Mount the storage to /onapp/backups:
Code Block bash#> mount /dev/sda /backupstorage
Make folder for storing templates:
Code Block bash#> mkdir /backupstorage/templates
Make folder for storing backups:
Code Block bash#> mkdir /backupstorage/backups
Create symbolic links in /onapp
Code Block bash#> ln -s /backupstorage/backups /onapp/backups
Add the following to custom config file:
Code Block mkdir /backupstorage mount /dev/sda /backupstorage ln -s /backupstorage/backups /onapp/backups ln -s /backupstorage/templates /onapp/templates
Update the database so that the location of the templates is known:
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]';
- To download the base templates during the installation to your Control Panel, download and run the following script:
Code Block bash#> wget http://downloads.repo.onapp.com/get_template.sh bash#> /bin/sh get_template.sh
Note To ensure your backups don't disappear after rebooting the CloudBoot backup server, add a mount command to the CloudBoot backup servers custom config so it is automatically mounted after future reboots.
To fix your custom config settings, you can use one of the following options provided in the examples below (you will have to specify your own device names):If you have a separate partition for backups and templates (/dev/sda1 and /dev/sda2)
Code Block mkdir -p /onapp/backups mkdir -p /onapp/template mount /dev/sda1 /onapp/backups mount /dev/sda2 /onapp/templates
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 -p /onapp mount /dev/sda1 /onapp
This section is the part of the OnApp installation procedure. |
---|
Install Control Panel Server > Install Compute Resources > Install Data Stores > Install Backup Server > Download and Configure Templates on Control Panel Server > Configure Cloud |