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 |
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:
bash# yum update
Download the OnApp repository:
bash# rpm -Uvh http://rpm.repo.onapp.com/repo/onapp-repo-5.1.noarch.rpm
Install the OnApp Backup Server installer package:
bash# yum install onapp-bk-install
Check and set Backup Server default settings:
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.
bash# sh /onapp/onapp-bk-install/onapp-bk-install.sh
Сonfigure the backup server for your cloud. This step is also required for the SNMP statistics receiver configuration:
bash#> /onapp/onapp-bk-install/onapp-bk-config.sh -h <CP_HOST_IP> -p [BK_HOST_IP]
Run the following commands:
# yum install gdisk
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 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:
Update CloudBoot and CP server RPMs:
yum update onapp-store-install yum update onapp-cp-install
Configure CloudBoot settings:
/onapp/onapp-store-install/onapp-store-install.sh
Create new CloudBoot compute resource: at the first step of the creation wizard choose the type - Backup (CloudBoot Provisioning and Backup Resource). Refer to the Create CloudBoot Compute Resource section of this guide for details.
- Go to your Control Panel's Settings menu, then press Compute Resources icon.
- Click the Add New CloudBoot Compute Resource button.
- In wizard menu click Backup (CloudBoot Provisioning and Backup Resource).
Select right MAC address of it.
Fill in the form that appears:
- 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
At this step, specify the Backup Server properties:
- 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)
- Then, you shouldn't assign any drive, but it needs right NIC to be applied to the storage network.
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.:
bash#> mkfs.ext4 /dev/sda
Make folder for backups if it does not exist
bash#> mkdir /backupstorage
Mount the storage to /onapp/backups:
bash#> mount /dev/sda /backupstorage
Make folder for storing templates:
bash#> mkdir /backupstorage/templates
Make folder for storing backups:
bash#> mkdir /backupstorage/backups
Create symbolic links in /onapp:
bash#> ln -s /backupstorage/backups /onapp/backups bash#> unlink /onapp/templates bash#> ln -s /backupstorage/templates /onapp/templates bash#> ln -s /onapp/tools/recovery /data
Add the following to custom config file:
mkdir /backupstorage mount /dev/sda /backupstorage ln -s /backupstorage/backups /onapp/backups unlink /onapp/templates ln -s /backupstorage/templates /onapp/templates ln -s /onapp/tools/recovery /data
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:
bash#> mysql -p bash#> use onapp;
c. Find the ID of the backup server:
bash#> select * from backup_servers;
d. For all of the templates, set the required backup_server_id:
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:
bash#> wget http://downloads.repo.onapp.com/get_template.sh bash#> /bin/sh get_template.sh
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):
- If you have a separate partition for backups and templates (/dev/sda1 and /dev/sda2)
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
If you current array is detected as /dev/sda1 and currently everything is located in /onapp within templates and backup directories within:
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 |