Introduction
The VegaOps tool chain data, including GitLab repositories, CI/CD pipelines, database and its related configuration are to be backed up regularly to reliable Backup Hosting provider.
As this data is mission-critical for businesses, the VegaOps Clients are advised to leverage the below-mentioned Managed Backups services offered by VegaOps.
Backup Hosting Provider
It is recommended to have a reliable Backup Hosting provider, to upload backup files in a durable storage, and to be able to quickly restore them during a crisis.
🌳 Amazon S3
Most recommended by VegaOps.
Works for VegaOps Cloud and On-Premise installations.
Requirements
- AWS S3 bucket
- IAM user Access Key and Secret Key (with LIST, GET, PUT permissions)
Pros
- Faster and reliable data uploads and retrievals.
- 11 nines (99.999999999%) durability, and 99.99% availability.
- Version-controlled data files. Learn more.
- Lifecycle policy and Expiring objcets to save consumed storage. Learn more.
- Secure encrypted data files. Learn more.
Cons
- Slightly complex pricing schema.
🦈 DigitalOcean Spaces
Recommended by VegaOps.
Apt for VegaOps Cloud and On-Premise installations.
Requirements
- DigitalOcean Spaces (preferrably in a separate account)
- Spaces Access Key and Secret Key (can’t define any permissions).
- Note: This key will be able to access all the Spaces in the DO account. Hence, using a separate dedicated account is recommended.
Pros
- Faster and reliable data uploads and retrievals.
- 99.99% uptime.
- Simple and predictable pricing, starting with just 5 USD.
Cons
- No support for lifecycle policies.
- Encryption support for data availables isn’t supported.
- Version-controlling for backup files (objects) isn’t supported. 1️⃣
💾 Local Disk
Not recommended by VegaOps.
Apt for VegaOps On-Premise installations.
Requirements
- Shared disk mounted to VegaOps Main Server, in a specific mount path
/vo-data/backups. - Read-write access to the disk. Same filesystem as the VegaOps Main Server.
Pros
- Faster data uploads and retrievals (if within same network).
Cons
- Durability, uptime and reliability concerns.
- Version-controlling for backup files (objects) isn’t supported.
- No support for lifecycle policies.
- Encryption support for data availables isn’t supported.
Backup frequency
VegaOps tool chain data is backed up as per a set frequency to a designated Backup Hosting Provider, that can be restored anytime.
Available Frequency options
- Daily (most recommended)
- Alternate days
- Weekly (say every Friday)
Backup Trigger Time
Data Backups will be triggered at a set trigger time (defaults to 3 AM), and will be processed in about 40-60 minutes, based on the backup size and bandwidth limits.
During the Data Backup, VegaOps GitLab performance may be reduced, but downtime isn’t expected.
