Customer Backup » History » Revision 16
« Previous |
Revision 16/20
(diff)
| Next »
Jin-Guk Kwon, 12/18/2023 10:55 AM
Managed Customer Backup¶
- Table of contents
- Managed Customer Backup
This document concerns end-users/customers. See [[datacenterlight:Backup]] page for server-side documentation.
Status¶
This document is a DRAFT.
Overview¶
- Official product page: https://ungleich.ch/u/products/backup/
- Related DatacenterLight FAQ entry: https://redmine.ungleich.ch/projects/open-infrastructure/wiki/FAQ_at_Data_Center_Light#Backup
We make use of the ccollect software, which runs every day at 3AM Europe/Zurich. The backup server and storage clusters are in a location (place5) physically separated from the customer VMs (place6).
VM Backup¶
FAQ¶
How to enable this service?¶
You will have to contact our support and give them the following details:
- Address of the VM to backup (IPv6 or domain with AAAA field).
- Directories to backup. Default is
/
excluding/sys
and/proc
.
ccollect makes use of rsync
to transfer data and needs to connect to your server over SSH (rsync itself is not encrypted!). You need to configure an user - root for a full system backup - with the following SSH key (to put in ~/.ssh/authorized_keys
):
# backup.place5.ungleich.ch ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQC7LsZp048K5D2kSWwiI5fux5pv4Ji7eTtMZGpOu0MviZEuGG3T5NeSKPmdlG1Rr3/oLpIqaFPzB7la3SI0OX5/E3v/yWcSrIsXdoIlSJMx7yaWrd4rm3yICukg4v5cZm2iDGBzIffpRxN1aPg46XnwmSvID3dD18yHMfgKyOFJgMwpTeI0d+K99cRYdf0D+QoUUyJlEes8xOw29lfT+1gg3KXBfYeggXLxMQ1xOH5L91j3Lg1taaD0EfyvkjO+TspcEwIwEtcBwdGRDbkjNkZOgFUEoWpxEFESLFRvr+JxgDJjvkLD4Q7l6tNOvW30oq7iI961NbXSwgM1cH0gNPED ungleich-backup
What is the pricing model?¶
See product page.
What is the retention policy?¶
The default retention policy is: 5 daily backups, 4 weekly backups, 12 monthly backups.
How can I access my backups?¶
You can access the files over SFTP using your ungleich account (username + password) against backup.place5.ungleich.ch
. You can use any SFTP client such as command-line sftp
(@sftp myusername@backup.place5.ungleich.ch) or Filezilla (graphical client).
Note: at the moment, backup.place5.ungleich.ch
is only available over IPv6.
Glarnercloud Backup¶
FAQ¶
How to enable this service?¶
Simply contact our customer support in order to enable the backup of your Glarnercloud instance.
The support team will then enable the automated backup service (similar to VM Backup but restricted to your Glarnercloud data)
What is the pricing model?¶
See product page.
What is the retention policy?¶
The default retention policy is: 5 daily backups, 4 weekly backups, 12 monthly backups.
How can I access my backups?¶
You can access the files over nextcloud via cloud-backup.glarner.cloud
. Our customer support team will hand you your credentials as soon as the service is enabled for you.
Otherwise, you can access the backup via SFTP. Here again, the customer support will contact you and communicate your credentials as soon as the service is enabled for you. You can use any SFTP client such as command-line sftp
(@sftp myusername@cloud-backup.glarner.cloud) or Filezilla (graphical client).
Note: at the moment, cloud-backup.glarner.cloud
is only available over IPv6.
Glarnercloud Backup of k8s¶
FAQ¶
How to enable this service?¶
Simply contact our customer support in order to enable the backup of your Glarnercloud instance.
The support team will then enable the automated backup service.
We are using restic(s3 bucket) for cloud of k8s.
How can I access my backups?¶
Backup customer access their s3 bucket with secure key
ex) s3cmd --host=s3.k8s.place5.ungleich.ch --access_key=XXXXXXXXXX --secret_key=XXXXXXXXXX ls s3://bucket_address/snapshots/
or
ex) export RESTIC_REPOSITORY=s3:https://s3.k8s.place5.ungleich.ch/[bucket_address]; export RESTIC_PASSWORD=XXXXXXXXXX; export AWS_ACCESS_KEY_ID=XXXXXXXX; export AWS_SECRET_ACCESS_KEY=XXXXXXXX; restic snapshots
Dump backup with restic
ex) export RESTIC_REPOSITORY=s3:https://s3.k8s.place5.ungleich.ch/[bucket_address]; export RESTIC_PASSWORD=XXXXXXXXXX; export AWS_ACCESS_KEY_ID=XXXXXXXX; export AWS_SECRET_ACCESS_KEY=XXXXXXXX; restic restore [snapshot_ID] --target /restore
Updated by Jin-Guk Kwon 12 months ago · 16 revisions