Managing V2 Backups and Application Data
Introduction
This sections describes:
- How application data (e.g. all application data and state) for individual V2 applications are managed
- How backups for individual V2 applications are managed
- How backups for VMs are managed
Definitions
Application - An application that manages its state in a database and a set of data files
VM - A virtual machine, in which supporting services and application are run
One or more Applications run on a VM, limited by the capacity of the VM
Host System - A hardware/software platform supporting a set of services and application VMs
One or more VMs run on a Host System, limited by the capacity of the Host System
Service - A host or network service that supports Applications and their underlying infrastructure (see Services)
The entire infrastructure can be scaled by adding additional VMs and Host Systems
Services
Each Host System must have:
DNS server in a VM that resolves the internal names and IP address of the VMs
forwarding-only DNS server that forward DNS requests to the DNS server VM
rinetd daemon that forwards incoming TCP traffic to the appropriate VM based on the port number. Typically
All web traffic (ports 80 and 443) is forwarded to the Reverse Proxy server
- Note that DNS traffic, which uses both TCP and UDP protocols, is managed by the Host System's forwarding-only DNS server
- If the Host System has a VM with a Puppet server then port 8140 is forwarded to it
Reverse Proxy, an Apache module in a web server VM, that forward web requests to the appropriate VM based on the hostname in the HTTP request
Application Data Management
Application Directory structure
Backup Directory Structures
Application Backup Directories
VM Backup Directories