# Home Welcome to Weap.io ### Weap.io Weap.io is a service that allows you to perform native snapshots for various cloud providers. ### Documentation Here you will find answers to your questions and useful information in order to benefit at maximum of what Weap.io has to offer. ### Contact us If your question is not answered here, you need help with something special, or you just want to say hi, feel free to reach us using our live chat or at `hi@weap.io` 🙂 # What are Provider Snapshots? Overview of Provider Snapshots. ### Introduction A native snapshot is a backup created and stored directly inside the infrastructure of your provider. ### What providers are supported? Currently, we support the following poviders: * DigitalOcean * Hetzner * AWS EC2 * AWS Lightsail * Google Cloud Platform * Alibaba Cloud * UpCloud * Scaleway * OVH * Exoscale ### How a native snapshot is created and retained? In order to create native snapshots, Weap.io uses the API provided by the cloud provider. Following the preferences of your retention policy, Weap will keep an optimal number of active snapshots. ### What are the benefits of using native snapshots? * more frequent, up to hourly backups * more flexible retention * choose the time when to create the snapshots * more cost effective: * DigitalOcean charges you 20% of the server plan to offer weekly backups. Using snapshots, you will pay only 0.05$/GB/month * Hetzner charges you 20% of the server plan for daily backups. Using snapshots, you will pay only 0.01€/GB/month * securely stored inside the infrastructure of the cloud provider * simple & fast recover by restoring an existent server or creating a new one # What are Database Backups? Overview of Database Backups ### Introduction In case you host your database on a DigitalOcean/Hetzner/AWS instance and you need to backup it, native snapshots may not be the best option if the database has a lot of write operations. To overcome this drawback, we offer a fully managed backup solution for MySQL and PostgreSQL. ### Is important where I host my databases? No. We can backup any supported database as long as the server used to create the backup has SSH enabled. ### What databases are supported? Currently we support `MySQL` and `PostgreSQL`. ### Where are the backups stored? Each plan has 5GB, 25GB or 250GB of storage included and you always have to possibility to connect your own cloud storage if you want to replace or extend the storage included in the plan. ### What storage providers are supported? We support `AWS S3`, `Wasabi`, `DigitalOcean Spaces` and `Backblaze B2`. # What are File Backups? Overview of File Backups. ### Introduction With File Backups you can backup your server files to an external storage. Compared to Provider Snapshots, where the whole server is included in the backup, for File Backups you have the flexibility to choose which files should included (or excluded) from the backup. ### Is important where I host my servers? No. You can backup files from any server that has SSH enabled. ### What files can I backup? You can backup any type of files. ### Where are the backups stored? Each plan has 5GB, 25GB or 250GB of storage included and you always have to possibility to connect your own cloud storage if you want to replace or extend the storage included in the plan. # Alibaba Cloud Schedule frequent snapshots of your Alibaba Cloud ECS Instances. By connecting your Alibaba Cloud account to Weap.io, you will be able to schedule automatic snapshots of your ECS Instances. # Get started Learn how to connect your Alibaba Cloud account in order to schedule automatic snapshots of your ECS Instances. In order to start scheduling automated & frequent native snapshots of your ECS Instances, you must connect your Alibaba Cloud account. After connecting the account, Weap.io will automatically import all your ECS Instances and you will be able to choose the ones that should be backed-up, configure the backup frequency and finally the retention policy. ### 1. Open the Weap.io Provider Snapshots page Open your Weap.io dashboard and click the **`Provider Backups`** button located in the top menu. On the page just opened, click the button **`Connect cloud account`**. ![](https://3208313484-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MFo23y3kKRLVuJ9Nhx_%2F-MKFRVwetQMDQCJEruNo%2F-MKFS79za8hO2odyBa8d%2Fimage.png?alt=media\&token=b1ee03bb-8381-4571-bbc9-3f1e8382d7d6) ### 2. Generate your Alibaba Cloud Access Key In order for Weap.io to be able to create snapshots of your Alibaba Cloud ECS Instances, you must create an Access Key. Open the Alibaba Cloud Console in a new tab, hover the mouse over your profile image and click **`AccessKey Management`**. On the opened page, click the button Create **`AccessKey`**. Your Alibaba Cloud Access Key was created. ![](https://3208313484-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MFo23y3kKRLVuJ9Nhx_%2F-MKFwQOmiuUAmtnDPbI2%2F-MKG-fcrKCl6QvbPHNWv%2Fimage.png?alt=media\&token=13702ca9-a02e-4a8d-bef7-c31e44beffe6) ### 3. Select the Alibaba Cloud provider, choose a name for the account and provide your Access Key details Go back to Weap.io and in the modal opened at step 1, select the **`Alibaba Cloud`** provider and type an intuitive name that will help you easily recognize the account later. Paste the Access Key Id & Access Key Secret generated in the previous step and choose the location of your ECS Instances. When done, click the **`Save`** button. ![](https://3208313484-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MFo23y3kKRLVuJ9Nhx_%2F-MKFwQOmiuUAmtnDPbI2%2F-MKG5I3lpsszpEWTuadX%2Fimage.png?alt=media\&token=8830cc26-e614-45ec-9e93-7c14fbcf585c) ### 4. Synchronize the account After clicking the **`Save`** button, the list of your connected accounts will be reloaded and the newly connected account will appear. The last thing you have to do is clicking the button **`Synchronize account`**. By doing that, Weap.io will import all your Alibaba Cloud ECS Instances. If you don't press the button, Weap.io will automatically run the synchronization after some minutes. Once synchronized, all your ECS Instances will be visible and you will be able to configure the backup frequency, retention or even completely pause the backups for some of them. ![](https://3208313484-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MFo23y3kKRLVuJ9Nhx_%2F-MKFwQOmiuUAmtnDPbI2%2F-MKG7d7QCXss6JeOC5D2%2Fimage.png?alt=media\&token=75f71a87-8061-4890-8083-ed7a42e5a50a) # AWS EC2 Schedule frequent snapshots of your AWS EC2 Instances. By connecting your AWS account to Weap.io, you will be able to schedule automatic snapshots of your EC2 Instances. # Get started Learn how to connect your AWS account in order to schedule automatic snapshots of your EC2 Instances. In order to start scheduling automated & frequent native snapshots of your EC2 Instances, you must connect your AWS account. After connecting the account, Weap.io will automatically import all your EC2 Instances and you will be able to choose the ones that should be backed-up, configure the backup frequency and finally the retention policy. ### 1. Open the Weap.io Provider Snapshots page Open your Weap.io dashboard and click the **`Provider Backups`** button located in the top menu. On the page just opened, click the button **`Connect cloud account`**. ![](https://3208313484-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MFo23y3kKRLVuJ9Nhx_%2F-MKFRVwetQMDQCJEruNo%2F-MKFS79za8hO2odyBa8d%2Fimage.png?alt=media\&token=b1ee03bb-8381-4571-bbc9-3f1e8382d7d6) ### 2. Generate your AWS Access Key In order for Weap.io to be able to create snapshots of your AWS EC2 Instances, you must create an Access Key. Open the AWS Console in a new tab, go to the IAM service and create a new policy using the following JSON: ``` { "Version": "2012-10-17", "Statement": [ { "Sid": "WeapIo", "Effect": "Allow", "Action": [ "ec2:CreateImage", "ec2:DescribeImages", "ec2:DeregisterImage", "ec2:DescribeInstances", "ec2:CreateSnapshot", "ec2:DeleteSnapshot", "ec2:DescribeSnapshots", "ec2:CreateTags", "ec2:DescribeVolumes" ], "Resource": [ "*" ] } ] } ``` Give an intuitive name to the policy to easily recognize it later, for example **`weap_backups`**. Now it's time to create a new user (again from the IAM service). Make sure to select **`Programmatic access`** as **`Access type`**. When done, click the button **`Next: Permissions`** ![](https://3208313484-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MFo23y3kKRLVuJ9Nhx_%2F-MKG9U1xXT0SsPESzuoa%2F-MKJ66ofIPjHQqlLdra7%2Fimage.png?alt=media\&token=b4fbefb9-c3b1-4d1c-b8bb-7a22d7a0bfcf) In the Permissions view select the option **`Attach existing policies directly`** and search the policy you just created previously. Once found, select it and click the button **`Next: Tags`** ![](https://3208313484-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MFo23y3kKRLVuJ9Nhx_%2F-MKG9U1xXT0SsPESzuoa%2F-MKJ6ZGyr55aVm8k9W16%2Fimage.png?alt=media\&token=17142b40-ad15-4736-bafb-306681b1d21c) The Tags step can be omitted. Click the button **`Next: Review`**. In the next view click **`Create User`**. ![](https://3208313484-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MFo23y3kKRLVuJ9Nhx_%2F-MKG9U1xXT0SsPESzuoa%2F-MKJ7L_QNKE7zeTx8bTi%2Fimage.png?alt=media\&token=f073b1e1-84d9-4346-bc4d-b72f0e65aaa3) In the last view you will find the Access Key details that must be provided when connecting the AWS account to Weap.io ### 3. Select the AWS EC2 provider, choose a name for the account and provide your Access key Go back to Weap.io and in the opened modal select the **`AWS EC2`** provider. Type an intuitive name that will help you easily recognize the account later. Paste the Access Key ID & Secret generated in the previous step and choose the location of your EC2 instances. When done, click the **`Save`** button. ![](https://3208313484-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MFo23y3kKRLVuJ9Nhx_%2F-MKG9U1xXT0SsPESzuoa%2F-MKJY6AWQBEi3kg5xrup%2Fimage.png?alt=media\&token=7a38b42d-e371-4646-925c-433a467eb6df) ### 4. Synchronize the account After clicking the **`Save`** button, the list of your connected accounts will be reloaded and the newly connected account will appear. The last thing you have to do is clicking the button **`Synchronize account`**. By doing that, Weap.io will import all your AWS EC2 Instances. If you don't press the button, Weap.io will automatically run the synchronization after some minutes. Once synchronized, all your EC2 Instances will be visible and you will be able to configure the backup frequency, retention or even completely pause the backups for some of them. ![](https://3208313484-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MFo23y3kKRLVuJ9Nhx_%2F-MKG9U1xXT0SsPESzuoa%2F-MKJXVEfIrAsT_npdOI3%2Fimage.png?alt=media\&token=0b3fd3d4-952d-4813-b8ff-589d5cda5339) # AWS Lightsail Schedule frequent snapshots of your AWS Lightstail Instances. By connecting your AWS account to Weap.io, you will be able to schedule automatic snapshots of your Lightsail Instances. # Get started Learn how to connect your AWS account in order to schedule automatic snapshots of your Lightsail Instances. In order to start scheduling automated & frequent native snapshots of your Lightsail Instances, you must connect your AWS account. After connecting the account, Weap.io will automatically import all your Lightsail Instances and you will be able to choose the ones that should be backed-up, configure the backup frequency and finally the retention policy. ### 1. Open the Weap.io Provider Snapshots page Open your Weap.io dashboard and click the **`Provider Backups`** button located in the top menu. On the page just opened, click the button **`Connect cloud account`**. ![](https://3208313484-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MFo23y3kKRLVuJ9Nhx_%2F-MKFRVwetQMDQCJEruNo%2F-MKFS79za8hO2odyBa8d%2Fimage.png?alt=media\&token=b1ee03bb-8381-4571-bbc9-3f1e8382d7d6) ### 2. Generate your AWS Access Key In order for Weap.io to be able to create snapshots of your AWS Lightsail Instances, you must create an Access Key. Open the AWS Console in a new tab, go to the IAM service and create a new policy using the following JSON: ``` { "Version": "2012-10-17", "Statement": [ { "Sid": "WeapIo", "Effect": "Allow", "Action": [ "lightsail:GetInstances", "lightsail:GetInstance", "lightsail:GetInstanceState", "lightsail:GetInstanceSnapshots", "lightsail:GetInstanceSnapshot", "lightsail:CreateInstanceSnapshot", "lightsail:DeleteInstanceSnapshot", "lightsail:GetOperation" ], "Resource": "*" } ] } ``` Give an intuitive name to the policy to easily recognize it later, for example **`weap_backups`**. Now it's time to create a new user (again from the IAM service). Make sure to select **`Programmatic access`** as **`Access type`**. When done, click the button **`Next: Permissions`** ![](https://3208313484-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MFo23y3kKRLVuJ9Nhx_%2F-MKG9U1xXT0SsPESzuoa%2F-MKJ66ofIPjHQqlLdra7%2Fimage.png?alt=media\&token=b4fbefb9-c3b1-4d1c-b8bb-7a22d7a0bfcf) In the Permissions view select the option **`Attach existing policies directly`** and search the policy you just created previously. Once found, select it and click the button **`Next: Tags`** ![](https://3208313484-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MFo23y3kKRLVuJ9Nhx_%2F-MKG9U1xXT0SsPESzuoa%2F-MKJ6ZGyr55aVm8k9W16%2Fimage.png?alt=media\&token=17142b40-ad15-4736-bafb-306681b1d21c) The Tags step can be omitted. Click the button **`Next: Review`**. In the next view click **`Create User`**. ![](https://3208313484-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MFo23y3kKRLVuJ9Nhx_%2F-MKG9U1xXT0SsPESzuoa%2F-MKJ7L_QNKE7zeTx8bTi%2Fimage.png?alt=media\&token=f073b1e1-84d9-4346-bc4d-b72f0e65aaa3) In the last view you will find the Access Key details that must be provided when connecting the AWS account to Weap.io ### 3. Select the AWS Lightsail provider, choose a name for the account and provide your Access key Go back to Weap.io and in the modal opened at step 1 select the **`AWS Lightsail`** provider. Type an intuitive name that will help you easily recognize the account later. Paste the Access Key ID & Secret generated in the previous step and choose the location of your Lightsail instances. When done, click the **`Save`** button. ![](https://3208313484-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MFo23y3kKRLVuJ9Nhx_%2F-MKJaNdF_UKO9voNDkCN%2F-MKJh922MT3SEAqjrNs2%2Fimage.png?alt=media\&token=86562dab-7141-493f-9298-cc9101ed7c4b) ### 4. Synchronize the account After clicking the **`Save`** button, the list of your connected accounts will be reloaded and the newly connected account will appear. The last thing you have to do is clicking the button **`Synchronize account`**. By doing that, Weap.io will import all your AWS Lightsail Instances. If you don't press the button, Weap.io will automatically run the synchronization after some minutes. Once synchronized, all your Lightsail Instances will be visible and you will be able to configure the backup frequency, retention or even completely pause the backups for some of them. ![](https://3208313484-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MFo23y3kKRLVuJ9Nhx_%2F-MKJhK-5V2ia351hKz8o%2F-MKJiJAidCX9YjcJLy_C%2Fimage.png?alt=media\&token=dd648832-df8d-4944-b2ec-accfd80c6447) # DigitalOcean Schedule frequent snapshots of your DigitalOcean droplets & volumes. DigitalOcean offers a backup service (only for Droplets) which creates a backup per week and retains the last 4 backups. You have to pay 20% of your Droplet plan for it. By connecting your DigitalOcean account to Weap.io, you will be able to schedule automatic snapshots for both Droplets and Volumes and you will pay 0.05$ per GB per month. Additionally, you will be able to replicate your Droplet snapshots in multiple DigitalOcean regions at no additional cost. This means that if you replicate a 10GB snapshot to 3 regions, you will still pay only for 10GB, not 30GB. # Get started Learn how to connect your DigitalOcean account in order to schedule automatic provider snapshots. In order to start scheduling automated & frequent native snapshots of your DigitalOcean droplets & volumes, you must connect your DigitalOcean account. After connecting the account, Weap.io will automatically import all your Droplets & Volumes and you will be able to choose the ones that should be backed-up, configure the backup frequency and finally the retention policy. ### 1. Open the Weap.io dashboard Open your Weap.io dashboard and click the `Provider Backups` button located in the top menu. On the page just opened, click the button `Connect cloud account`. ![](https://3208313484-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MFo23y3kKRLVuJ9Nhx_%2F-MKFRVwetQMDQCJEruNo%2F-MKFS79za8hO2odyBa8d%2Fimage.png?alt=media\&token=b1ee03bb-8381-4571-bbc9-3f1e8382d7d6) ### 2. Choose a name for the account Type an intuitive name to easily recognize the account later and click the `Save` button. After that, you will be redirected to your DigitalOcean account. ![](https://3208313484-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MFo23y3kKRLVuJ9Nhx_%2F-ML-4mLeSvMpffZYg3RX%2F-ML13aHCAO-2dcbj4SOp%2Fimage.png?alt=media\&token=d011f6a4-5017-40ea-a410-bc13e0793368) ### 3. Authorize Weap.io from your DigitalOcean account Weap.io uses the DigitalOcean API in order to create frequent backups for your Droplets & Volumes. In order to do that, you must authorize Weap.io from the DigitalOcean page you have been redirected. ![](https://3208313484-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MFo23y3kKRLVuJ9Nhx_%2F-MGPfdK17Ua2zlxNGZ4D%2F-MGPfz6M7cM-JBHMr_ps%2Fimage.png?alt=media\&token=bc345f7f-6523-4950-a804-c38d97754a00) After authorizing the API access, you will be redirected back to your Weap.io dashboard. ### 4. Synchronize the account ![](https://3208313484-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MFo23y3kKRLVuJ9Nhx_%2F-ML-4mLeSvMpffZYg3RX%2F-ML14SAS2Ej5G2_i4ho7%2Fimage.png?alt=media\&token=ddedb1ad-8b48-4ff6-ae35-31d57722019a) The last thing you have to do is clicking the big button `Synchronize account`. By doing that, Weap.io will import all your Droplets & Volumes. If you don't press the button, Weap.io will automatically run the synchronization after some minutes. Once synchronized, all your Droplets & Volumes will be visible and you will be able to configure the backup frequency, retention or even completely pause the backups for some of them. # Multi-region replication Learn how to enable multi-region replication for your DigitalOcean droplets. ### 1. Go the page of the Droplet you want to replicate in multiple regions Go to the page of the Droplet you want to replicate in multiple DigitalOcean regions, hover the mouse on its name and click `Region replication`. ![](https://3208313484-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MFo23y3kKRLVuJ9Nhx_%2F-MW4po3JDNY4ti2M6rcT%2F-MW4qGVMy2laEa7gOSsr%2Fimage.png?alt=media\&token=0ede5ae4-efca-4172-aa5a-117cb6826e2d) ### 2. Select the regions where to replicate the snapshots In the modal just opened you have to select in which regions you want to replicate the snapshots. Once you selected your regions, click the button `Save`. ![](https://3208313484-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MFo23y3kKRLVuJ9Nhx_%2F-MW4po3JDNY4ti2M6rcT%2F-MW4r1LyIibQdOYsBtYX%2Fimage.png?alt=media\&token=09fdf618-2a0b-4fa8-8b92-1b4c21d132a6) # Trigger manual snapshots ### What are manual snapshots? A manual snapshot is a snapshot which is triggered by the user and not by the system. Manual snapshots are not taken into consideration by the retention policy. This means that a manual snapshot will stay active until you choose to delete it. ### How to trigger a manual snapshot? Go to the page of the cloudlet you want to backup and hover the mouse on its name. From the dropdown that opened click the option `Take snapshot now`. ![](https://3208313484-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MFo23y3kKRLVuJ9Nhx_%2Fuploads%2FPUCt8e40tU86JpZst1vH%2Fimage.png?alt=media\&token=37d29b61-fff9-46ad-8565-1a4b2717bce9) # Exoscale Schedule frequent snapshots of your Exoscale Compute Instances. By connecting your Exoscale account to Weap.io, you will be able to schedule automatic snapshots of your Exoscale Compute Instances. # Get started Learn how to connect your Exoscale account in order to schedule automatic snapshots of your Exoscale Compute Instances. In order to start scheduling automated & frequent native snapshots of your Exoscale Compute Instances, you must connect your Exoscale account. After connecting the account, Weap.io will automatically import all your Exoscale Compute Instances and you will be able to choose the ones that should be backed-up, configure the backup frequency and finally the retention policy. ### 1. Open the Weap.io Provider Snapshots page Open your Weap.io dashboard and click the **`Provider Backups`** button located in the top menu. On the page just opened, click the button **`Connect cloud account`**. ![](https://3208313484-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MFo23y3kKRLVuJ9Nhx_%2F-MKFRVwetQMDQCJEruNo%2F-MKFS79za8hO2odyBa8d%2Fimage.png?alt=media\&token=b1ee03bb-8381-4571-bbc9-3f1e8382d7d6) ### 2. Generate your Exoscale API Key In order for Weap.io to be able to create snapshots of your Exocale Compute Instances, you must create an API Key. Open the Exoscale Console in a new tab, go to the **`IAM`** page and click the button **`ADD`** button. ![](https://3208313484-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MFo23y3kKRLVuJ9Nhx_%2F-ML-0ktw_7RT6NOxLpZ7%2F-ML-1u3xjizkgf3b1Pu3%2Fimage.png?alt=media\&token=830591e2-6a87-4ec4-9876-bf640ea129d4) Give an intuitive name to the key, select **`Unrestricted`** as access type and click the **`Create`** button. ![](https://3208313484-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MFo23y3kKRLVuJ9Nhx_%2F-ML-0ktw_7RT6NOxLpZ7%2F-ML-2Kvxq-NZS8E1f3Iy%2Fimage.png?alt=media\&token=374f5bc9-f436-4b2c-ba57-2c898d7f734d) After clicking **`Create`**, you will see your new key. ![](https://3208313484-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MFo23y3kKRLVuJ9Nhx_%2F-ML-0ktw_7RT6NOxLpZ7%2F-ML-2o-dbpL6m0WqxCcX%2Fimage.png?alt=media\&token=6c3cc312-bfb2-4567-b239-7a68ca28b150) ### 3. Select the Exoscale provider, choose a name for the account and provide your API key Go back to Weap.io and in the opened modal select the **`Exoscale`** provider. Type an intuitive name that will help you easily recognize the account later. Paste the API Access & Secret key generated in the previous step and click **`Save`**. ![](https://3208313484-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MFo23y3kKRLVuJ9Nhx_%2F-ML-0ktw_7RT6NOxLpZ7%2F-ML-3hx8NkRU61Xy-2ea%2Fimage.png?alt=media\&token=d2d465e5-5744-48f0-9fd0-a5e788e961c7) ### 4. Synchronize the account After clicking the **`Save`** button, the list of your connected accounts will be reloaded and the newly connected account will appear. The last thing you have to do is clicking the button **`Synchronize account`**. By doing that, Weap.io will import all your Exoscale Compute Instances. If you don't press the button, Weap.io will automatically run the synchronization after some minutes. Once synchronized, all your Exoscale Compute Instances will be visible and you will be able to configure the backup frequency, retention or even completely pause the backups for some of them. ![](https://3208313484-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MFo23y3kKRLVuJ9Nhx_%2F-ML-0ktw_7RT6NOxLpZ7%2F-ML-4Faes-Y3smBeAOGP%2Fimage.png?alt=media\&token=51c96202-b408-4391-9845-a69242edabc9) # Google Cloud Platform Schedule frequent snapshots of your Google Cloud Platform Compute Instances. By connecting your GCP account to Weap.io, you will be able to schedule automatic snapshots of your GCP Compute Instances. # Get started Learn how to connect your GCP account in order to schedule automatic snapshots. In order to start scheduling automated & frequent native snapshots of your GCP Disks, you must connect your GCP account. After connecting the account, Weap.io will automatically import all your GCP Disks and you will be able to choose the ones that should be backed-up, configure the backup frequency and finally the retention policy. ### 1. Open the Weap.io Provider Snapshots page Open your Weap.io dashboard and click the **`Provider Backups`** button located in the top menu. On the page just opened, click the button **`Connect cloud account`**. ![](https://3208313484-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MFo23y3kKRLVuJ9Nhx_%2F-MKFRVwetQMDQCJEruNo%2F-MKFS79za8hO2odyBa8d%2Fimage.png?alt=media\&token=b1ee03bb-8381-4571-bbc9-3f1e8382d7d6) ### 2. Generate your Google Service Account JSON Login into [Google Cloud Platform](https://console.cloud.google.com/home/dashboard) and navigate to the project you want to backup. In the left sidebar hover the mouse on **`IAM & Admin`** and click **`Service Accounts`**. ![](https://3208313484-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MFo23y3kKRLVuJ9Nhx_%2F-MKJj8vtiNhyJAktV27J%2F-MKJqvIdb8uhaUyDq4Dd%2Fimage.png?alt=media\&token=07c13b6a-19f6-43da-b2a3-77f9f0e8b82d) In the page just opened, click **`Create Service Account`**. ![](https://3208313484-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MFo23y3kKRLVuJ9Nhx_%2F-MKJj8vtiNhyJAktV27J%2F-MKJrgIh6l1e5AlwlOzp%2FScreenshot%202020-10-23%20at%2011.50.56.png?alt=media\&token=8e530be3-bd4a-4729-8dd5-b5d2c917ae51) Give a name to the account and click **`Create`**. ![](https://3208313484-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MFo23y3kKRLVuJ9Nhx_%2F-MKJj8vtiNhyJAktV27J%2F-MKJrtkV8BLEHhUKDee1%2Fimage.png?alt=media\&token=b3fc83ab-7b9d-47f7-8742-f102fde5107b) Now it's time to choose a role. Search for **`Compute Admin`**, select it and click **`Continue`**. Ignore the step 3 by clicking **`Done`**. ![](https://3208313484-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MFo23y3kKRLVuJ9Nhx_%2F-MKJj8vtiNhyJAktV27J%2F-MKJs3GOGYt_pxGkDZZ6%2Fimage.png?alt=media\&token=3f2b421d-336d-4355-bbc5-58f9e7da0c0b) Click the actions icon of the account just created and click **`Create key`**. ![](https://3208313484-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MFo23y3kKRLVuJ9Nhx_%2F-MKJj8vtiNhyJAktV27J%2F-MKJsqDpTwOA_TFS4UsX%2Fimage.png?alt=media\&token=ea157954-f9df-4c77-b141-2df6d741da92) Choose JSON and click **`Create`**. ![](https://3208313484-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MFo23y3kKRLVuJ9Nhx_%2F-MKJj8vtiNhyJAktV27J%2F-MKJsyHry-zj7gdysU_Y%2Fimage.png?alt=media\&token=68ae710e-4643-4bc2-8d8b-9582a7d9d860) After clicking **`Create`**, a file will be downloaded. Open it with a text editor and copy the content. ![](https://3208313484-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MFo23y3kKRLVuJ9Nhx_%2F-MKJj8vtiNhyJAktV27J%2F-MKJtKaDccMOgKFRTOOG%2Fimage.png?alt=media\&token=81ede7bd-568b-4b9d-8b18-4acf10616e77) ### 3. Select the GCP provider, choose a name for the account and provide your Access details Go back to Weap.io and in the modal opened at step 1 select the **`GCP`** provider. Type an intuitive name that will help you easily recognize the account later. Paste the Google Account Service JSON generated in the previous step and choose the location of your GCP instances. When done, click the **`Save`** button. ![](https://3208313484-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MFo23y3kKRLVuJ9Nhx_%2F-MKJtSDVPcU-uXogaNfR%2F-MKJu33JyX1mObe5v0fT%2Fimage.png?alt=media\&token=b1d7a017-2130-4a70-bea0-8aaebd3576b0) ### 4. Synchronize the account After clicking the **`Save`** button, the list of your connected accounts will be reloaded and the newly connected account will appear. The last thing you have to do is clicking the button **`Synchronize account`**. By doing that, Weap.io will import all your GCP Disks. If you don't press the button, Weap.io will automatically run the synchronization after some minutes. Once synchronized, all your GCP Disks will be visible and you will be able to configure the backup frequency, retention or even completely pause the backups for some of them. ![](https://3208313484-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MFo23y3kKRLVuJ9Nhx_%2F-MKJuLGkjD7aIZXUWi6f%2F-MKJunzbCyx56qUed4JX%2Fimage.png?alt=media\&token=0f866d92-1764-4659-b1cb-5a23fe04b11a) # Hetzner Schedule frequent snapshots of your Hetzner Cloud Servers. Hetzner offers a backup service for Cloud Servers which creates a backup once per day and retains the last 7 backups. You have to pay 20% of your Cloud Server plan for it. By connecting your Hetzner account to Weap.io, you will be able to schedule automatic snapshots for both Droplets and Volumes and you will pay only 0.01€/GB/month. # Get started Learn how to connect your Hetzner account in order to schedule automatic snapshots of your Hetzner Cloud Servers. In order to start scheduling automated & frequent native snapshots of your Hetzner Cloud Servers, you must connect your Hetzner account. After connecting the account, Weap.io will automatically import all your Hetzner Cloud Servers and you will be able to choose the ones that should be backed-up, configure the backup frequency and finally the retention policy. ### 1. Open the Weap.io Provider Snapshots page Open your Weap.io dashboard and click the **`Provider Backups`** button located in the top menu. On the page just opened, click the button **`Connect cloud account`**. ### 2. Generate your Hetzner API Key In order for Weap.io to be able to create snapshots of your Hetzner Cloud Servers, you must create an API Key. Open the [Hetzner Console](https://console.hetzner.cloud/) in a new tab, select your project and click the **`Security`** item in the left sidebar. Choose the **`API Tokens`** tab and click the **`Generate API Token`** button. ![](https://3208313484-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MFo23y3kKRLVuJ9Nhx_%2F-MKJv-xOa-crbnknUBu5%2F-MKKltXpIPZRKvcNwQJf%2Fimage.png?alt=media\&token=095379e8-f509-4f10-8288-e1f436cb07f0) Given an intuitive name to key, select the **`Read & Write`** option and click the button **`Generate API Token`**. ![](https://3208313484-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MFo23y3kKRLVuJ9Nhx_%2F-MKJv-xOa-crbnknUBu5%2F-MKKmlfeqO9oruU2gOQ-%2Fimage.png?alt=media\&token=a1916d42-5c87-4ffd-a4a1-9f823adfe51b) Once created, the API key will be displayed to you only once. Copy it. ![](https://3208313484-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MFo23y3kKRLVuJ9Nhx_%2F-MKJv-xOa-crbnknUBu5%2F-MKKnLbcs93Nd_qoa_BC%2Fimage.png?alt=media\&token=23588ed6-268d-42ef-9bba-3c81d6cd1268) ### 3. Select the Hetzner provider, choose a name for the account and provide your API key Go back to Weap.io and in the opened modal select the **`Hetzner`** provider. Type an intuitive name that will help you easily recognize the account later. Paste the API key generated in the previous step and click the **`Save`** button. ![](https://3208313484-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MFo23y3kKRLVuJ9Nhx_%2F-MKJv-xOa-crbnknUBu5%2F-MKKZKd7ECkr-N5H4_nH%2Fimage.png?alt=media\&token=b4da1a8f-2c6e-4136-a098-309e1622afad) ### 4. Synchronize the account After clicking the **`Save`** button, the list of your connected accounts will be reloaded and the newly connected account will appear. The last thing you have to do is clicking the button **`Synchronize account`**. By doing that, Weap.io will import all your Hetzner Cloud Servers. If you don't press the button, Weap.io will automatically run the synchronization after some minutes. Once synchronized, all your Hetzner Cloud Servers will be visible and you will be able to configure the backup frequency, retention or even completely pause the backups for some of them. ![](https://3208313484-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MFo23y3kKRLVuJ9Nhx_%2F-MKJv-xOa-crbnknUBu5%2F-MKKonTEnCpxX5Kuhvaa%2Fimage.png?alt=media\&token=5728dcff-8ed6-4fc0-abdd-deae55d3a482) # OVH Schedule frequent snapshots of your OVH Public Cloud Compute Instances. By connecting your OVH Cloud account to Weap.io, you will be able to schedule automatic snapshots of your OVH Public Cloud Compute Instances. # Get started Learn how to connect your OVH account in order to schedule automatic snapshots of your OVH Compute Instances. In order to start scheduling automated & frequent native snapshots of your OVH Compute Instances, you must connect your OVH account. After connecting the account, Weap.io will automatically import all your OVH Compute Instances and you will be able to choose the ones that should be backed-up, configure the backup frequency and finally the retention policy. ### 1. Open the Weap.io Provider Snapshots page Open your Weap.io dashboard and click the **`Provider Backups`** button located in the top menu. On the page just opened, click the button **`Connect cloud account`**. ![](https://3208313484-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MFo23y3kKRLVuJ9Nhx_%2F-MKFRVwetQMDQCJEruNo%2F-MKFS79za8hO2odyBa8d%2Fimage.png?alt=media\&token=b1ee03bb-8381-4571-bbc9-3f1e8382d7d6) ### 2. Select the OVH provider & choose a name for the account In the opened modal, select the **`OVH`** provider and type an intuitive name that will help you easily recognize the account later. Next, select the location of your OVH account. The default location is Europe. When done, click the **`Save`** button. ![](https://3208313484-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MFo23y3kKRLVuJ9Nhx_%2F-MKFRVwetQMDQCJEruNo%2F-MKFSxorgywJz57cuqVt%2Fimage.png?alt=media\&token=15930d25-abd7-4f42-9ceb-4ba3461a378d) ### 3. Authorize the API access After clicking save, you will be redirected to the OVH authorization page where you must Log In with your OVH account. Remember to select `Unlimited` as validity, otherwise Weap.io will not be able to create snapshots when the validity expires. ![](https://3208313484-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MFo23y3kKRLVuJ9Nhx_%2F-MKFRVwetQMDQCJEruNo%2F-MKFUQGVwdU0aDzAxJdy%2Fimage.png?alt=media\&token=1e8fd74c-0f7d-40bf-8ed9-29564d6f087e) ### 4. Synchronize the account After authorizing the OVH API access, you will be redirected back to the Weap.io dashboard where you will find the new connected OVH account. The last thing you have to do is clicking the button `Synchronize account`. By doing that, Weap.io will import all your OVH Compute Instances. If you don't press the button, Weap.io will automatically run the synchronization after some minutes. Once synchronized, all your OVH Compute Instances will be visible and you will be able to configure the backup frequency, retention or even completely pause the backups for some of them. ![](https://3208313484-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MFo23y3kKRLVuJ9Nhx_%2F-MKFRVwetQMDQCJEruNo%2F-MKFZ_LzSDp88TTdQ4ni%2Fimage.png?alt=media\&token=24a40e72-404d-4e3a-bfcd-1661e61d098b) # Scaleway Schedule frequent snapshots of your Scaleway Compute Instances. By connecting your Scaleway account to Weap.io, you will be able to schedule automatic snapshots of your Compute Instances. # Get started Learn how to connect your Scaleway account in order to schedule automatic snapshots of your Scaleway Compute Instances. In order to start scheduling automated & frequent native snapshots of your Scaleway Compute Instances, you must connect your Scaleway account. After connecting the account, Weap.io will automatically import all your Scaleway Compute Instances and you will be able to choose the ones that should be backed-up, configure the backup frequency and finally the retention policy. ### 1. Open the Weap.io Provider Snapshots page Open your Weap.io dashboard and click the **`Provider Backups`** button located in the top menu. On the page just opened, click the button **`Connect cloud account`**. ![](https://3208313484-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MFo23y3kKRLVuJ9Nhx_%2F-MKFRVwetQMDQCJEruNo%2F-MKFS79za8hO2odyBa8d%2Fimage.png?alt=media\&token=b1ee03bb-8381-4571-bbc9-3f1e8382d7d6) ### 2. Generate your Scaleway API Key In order for Weap.io to be able to create snapshots of your Scaleway Compute Instances, you must create an API Key. Open the Scaleway Console in a new tab, select your project and choose the **`Credentials`** tab. Next, click the **`Generate API Key`** button. ![](https://3208313484-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MFo23y3kKRLVuJ9Nhx_%2F-MKFc8CJe6jHrHd_VNVI%2F-MKFhN_UDglGAPiVigwu%2Fimage.png?alt=media\&token=95212417-999f-4681-b96a-3c0bb7427ba2) ### 3. Select the Scaleway provider, choose a name for the account and provide your API key Go back to Weap.io and in the opened modal select the **`Scaleway`** provider. Type an intuitive name that will help you easily recognize the account later. Paste the API Access & Secret key generated in the previous step and choose the location of your Scaleway project. When done, click the **`Save`** button. ![](https://3208313484-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MFo23y3kKRLVuJ9Nhx_%2F-MKFisvOmcPN61IXWheX%2F-MKFjAvEl4JvAaXVU5vx%2Fimage.png?alt=media\&token=5b1bf2e1-0e54-4fa9-b05c-bc47667d781f) ### 4. Synchronize the account After clicking the **`Save`** button, the list of your connected accounts will be reloaded and the newly connected account will appear. The last thing you have to do is clicking the button **`Synchronize account`**. By doing that, Weap.io will import all your Scaleway Compute Instances. If you don't press the button, Weap.io will automatically run the synchronization after some minutes. Once synchronized, all your Scaleway Compute Instances will be visible and you will be able to configure the backup frequency, retention or even completely pause the backups for some of them. ![](https://3208313484-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MFo23y3kKRLVuJ9Nhx_%2F-MKFisvOmcPN61IXWheX%2F-MKFlLq95UEEWceZZAlF%2Fimage.png?alt=media\&token=5bbacae8-a91e-4e47-b2a4-27887d3f9e26) # UpCloud Schedule frequent snapshots of your UpCloud Cloud Storages. By connecting your UpCloud account to Weap.io, you will be able to schedule automatic snapshots of your UpCloud Cloud Storages. # Get started Learn how to connect your UpCloud account in order to schedule automatic snapshots of your Cloud Storages. In order to start scheduling automated & frequent native snapshots of your UpCloud Cloud Storages, you must connect your UpCloud account. After connecting the account, Weap.io will automatically import all your UpCloud Cloud Storages and you will be able to choose the ones that should be backed-up, configure the backup frequency and finally the retention policy. ### 1. Open the Weap.io Provider Snapshots page Open your Weap.io dashboard and click the **`Provider Backups`** button located in the top menu. On the page just opened, click the button **`Connect cloud account`**. ![](https://3208313484-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MFo23y3kKRLVuJ9Nhx_%2F-MKFRVwetQMDQCJEruNo%2F-MKFS79za8hO2odyBa8d%2Fimage.png?alt=media\&token=b1ee03bb-8381-4571-bbc9-3f1e8382d7d6) ### 2. Create your UpCloud user The UpCloud API uses your account username and password for authentication. You can use your main user or create a new sub-account for giving Weap.io API access. If you choose to create a sub-account, open the UpCloud dashboard in a new tab, click the **`People`** button in the top navigation and click the button **`Add member`**. You will see a page where you must type the details of the new sub-account. Remember that the **`username`** and **`password`** will be used for the API authentication. {% hint style="warning" %} In the permissions section you must check the option **`Allow API connection from`** and select the option **`All addresses`**. The option **`Access to control panel`** should not be selected. {% endhint %} ![](https://3208313484-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MFo23y3kKRLVuJ9Nhx_%2F-MKFlRRBuGKLtt8-Vkmy%2F-MKFo6i_6rCud-JQjRx6%2Fimage.png?alt=media\&token=06a18793-f4ff-477b-88e6-0c8a50ef5a98) ### 3. Select the UpCloud provider, choose a name for the account and provide your API access credentials Go back to Weap.io and in the opened modal select the **`UpCloud`** provider. Type an intuitive name that will help you easily recognize the account later. Next, paste the API Username & Password of your account (or sub-account created in the previous step). When done, click the **`Save`** button. ![](https://3208313484-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MFo23y3kKRLVuJ9Nhx_%2F-MKFramvCmM7dbX0U2Ej%2F-MKFtE8fWEr9tp0DTf8q%2Fimage.png?alt=media\&token=26ad4dd5-adb7-486a-a0e9-18715aeb1086) ### 4. Synchronize the account After clicking the **`Save`** button, the list of your connected accounts will be reloaded and the newly connected account will appear. The last thing you have to do is clicking the button **`Synchronize account`**. By doing that, Weap.io will import all your UpCloud Cloud Storages. If you don't press the button, Weap.io will automatically run the synchronization after some minutes. Once synchronized, all your UpCloud Cloud Storages will be visible and you will be able to configure the backup frequency, retention or even completely pause the backups for some of them. ![](https://3208313484-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MFo23y3kKRLVuJ9Nhx_%2F-MKFramvCmM7dbX0U2Ej%2F-MKFv4wpwJw-2se05nA9%2Fimage.png?alt=media\&token=ad51cfe7-deb6-4656-ab60-f02b87ac7330) # MySQL backups Weap.io allows you to easily take automated backups of your MySQL databases. # Get started Get started with MySQL backups. Weap.io allows you to schedule backups for your MySQL databases and to choose the storage location (`AWS S3`, `Wasabi`, `DigitalOcean Spaces` and `Backblaze B2`). {% hint style="success" %} Our MySQL backup solution comes with a default storage location of up to 250GB. That's in case you don't want to bring your own storage. {% endhint %} Thanks to the intuitive user interface, getting started with your first MySQL backup is simple and fast. ### 1. Open Weap.io dashboard Open your Weap.io dashboard and click on the `Database Backups` menu button. On the page just opened, click the button `Add database`. ![](https://3208313484-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MFo23y3kKRLVuJ9Nhx_%2F-MKzwtuWpzgsGrUTjEXs%2F-MKzx18m7nqKbODKaz0t%2Fimage.png?alt=media\&token=6a1432b3-886c-424a-acad-f0e47d44e8ce) ### 2. Add a new server {% hint style="info" %} If your server was already added previously, you can skip this step by clicking "Choose an existent server". {% endhint %} Weap.io needs to be able to connect to a server that can connect to your MySQL database. It can be the server on which the database is hosted or simply another server. Next, you need to enter the server details: * `Friendly name`: a friendly name that will help you recognize the server later * `Server user`: the user that Weap.io will use to SSH into the server. It can be `root` or one specially created for Weap. If you need help creating a new user, check this guide. * `Server IP or hostname`: the IP or hostname of the server. * `Server port`: The SSH port of the server. The default one is 22. After filling the details, click the button `Next`. ![](https://3208313484-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MFo23y3kKRLVuJ9Nhx_%2F-MFovHUohKupkW9oamA6%2F-MFovfQExZ1C7-WtTNuI%2Fimage.png?alt=media\&token=57c9da25-594e-426b-ab52-01d1d4948691) ### 3. Add the SSH key to the server {% hint style="info" %} If your server was already added previously, you can skip this step by clicking "Choose an existent server". {% endhint %} Weap.io generated a new SSH key for your server. The key must be added to your `authorized_keys` file. All the required instructions are already displayed during the setup process. ![](https://3208313484-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MFo23y3kKRLVuJ9Nhx_%2F-MFp-5abO7DOI001W111%2F-MFunHJAXwmkgXLHcu8G%2Fimage.png?alt=media\&token=70cf6359-eff3-4e04-96dd-6f609658e102) ### 4. Connect to the database If everything went ok with the previous step, Weap.io was able to SSH into your server. Now it's time to establish a connection with your MySQL database. To be able to do that, you will need to enter the details of the database: * `User`: the user of the database. It can be root a one specially created for Weap. If you need help creating a new MySQL user, check this guide. * `Password`: the password of the MySQL user. * `Host`: the host of the database. If the database is stored on the same server added previously, it's `localhost` or `127.0.0.1`. If the database is running on a remote server, the host will be the IP (or hostname) of that server. * `Port`: the port of the database, usually 3306. ![](https://3208313484-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MFo23y3kKRLVuJ9Nhx_%2F-MFoom94rLOk2u3GIJVl%2F-MFoovTDlmvtQ1-F_ARa%2Fimage.png?alt=media\&token=5e329e0b-cf67-4119-a4ab-096dca90f26e) ### 5. Select the databases to backup After successfully connecting to the database, Weap will show you a list of all databases available. You can select 1, more or all databases available. After selecting the databases, click the button `Backup selected databases`. ![](https://3208313484-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MFo23y3kKRLVuJ9Nhx_%2F-MForlrARkkkn4yNlB5V%2F-MFosVpcvc7_weawO6OR%2Fimage.png?alt=media\&token=21f2e1a4-8835-4799-bc65-a205b782dc10) ### 6. Conclusion Congratulations! Your database is now automatically backed-up using the default retention policy and stored on your default storage location (the one provided by Weap if you didn't change it). The next steps for you are: * How to change the backup frequency & retention policy of a database * How to change the storage of a database # Encrypted MySQL backups Learn how to encrypt your MySQL backups. Weap.io allows you to encrypt your MySQL backups using asymmetric encryption. ### 1. Generate an encryption key First of all, you have to generate an encryption key. If you already have an encryption key, you can skip this step. In order to see how to generate an encryption key, check [this guide](/encryption-keys/how-to-generate-an-encryption-key). ### 2. Enable the encryption Open the Weap.io dashboard and select the MySQL database you want to encrypt. Once selected, hover the mouse on its name and choose the option **`Configure backups encryption`**. ![](https://3208313484-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MFo23y3kKRLVuJ9Nhx_%2F-MRP224G_I__FuCQ7S4C%2F-MRP7pft_5MXZ9_SbFsU%2Fimage.png?alt=media\&token=6a7d428c-1362-4644-9c37-b97fb46b7dc1) On the modal just opened, check the **`Enable encryption`** checkbox and select the encryption key that should be used. As a last step, click the button **`Enable encryption`**. ![](https://3208313484-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MFo23y3kKRLVuJ9Nhx_%2F-MRP224G_I__FuCQ7S4C%2F-MRPE7Cze2b2zxwHzH_W%2Fimage.png?alt=media\&token=8f4b3885-b0c9-44f6-b571-23fbf103a24e) From now on, all the future backups of the selected database will be encrypted with the selected encryption key. # Exclude certain tables from the backups Find out how you can exclude certain tables from the backups. When creating backups for a MySQL database, you may need to have the possibility to exclude some tables. This can be useful if you have one or more tables containing not important data, such as logs. ### 1. Open the Weap.io dashboard and go to your database Open the Weap.io dashboard, go to your database and hover the mouse on the database name. In the dropdown shown, click the option **`Configure backup options`**. ![](https://3208313484-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MFo23y3kKRLVuJ9Nhx_%2F-M_-43wEODKSQG3r5cg3%2F-M_-6H86I4BeKZNou4gC%2Fimage.png?alt=media\&token=c333c257-75f5-421c-9a6c-efb585d1a011) ### 2. Choose which tables to exclude In the modal just opened you have to select the option **`All tables except`**. In the input below the option, you must enter the names of the tables you want to exclude. If you want to exclude more than one table, enter the names comma separated. Next, click **`Save`**. From now on, the selected tables will be excluded from future backups. ![](https://3208313484-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MFo23y3kKRLVuJ9Nhx_%2F-M_-43wEODKSQG3r5cg3%2F-M_-6ykzTD4xOgd-EP0O%2Fimage.png?alt=media\&token=5fdbcb64-9bbb-4178-9f7b-d20dc75593f1) # PostgreSQL backups Weap.io allows you to easily take automated backups of your PostgreSQL databases. # Get started Get started with PostgreSQL backups. Weap.io allows you to schedule backups for your PostgreSQL databases and to choose the storage location (`AWS S3`, `Wasabi`, `DigitalOcean Spaces` and `Backblaze B2`). {% hint style="success" %} Our PostgreSQL backup solution comes with a default storage location of up to 250GB. That's in case you don't want to bring your own storage. {% endhint %} Thanks to the intuitive user interface, getting started with your first PostgreSQL backup is simple and fast. ### 1. Open Weap.io dashboard Open your Weap.io dashboard and click on the `Database Backups` menu button. On the page just opened, click the button `Add database`. ![](https://3208313484-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MFo23y3kKRLVuJ9Nhx_%2F-MKzwtuWpzgsGrUTjEXs%2F-MKzx53eZzRu_35Ac37E%2Fimage.png?alt=media\&token=2b034f2e-7c5f-4982-b96e-c28da278ff30) ### 2. Add a new server {% hint style="info" %} If your server was already added previously, you can skip this step by clicking "Choose an existent server". {% endhint %} Weap.io needs to be able to connect to a server that can connect to your PostgreSQL database. It can be the server on which the database is hosted or simply another server. Next, you need to enter the server details: * `Friendly name`: a friendly name that will help you recognize the server later * `Server user`: the user that Weap.io will use to SSH into the server. It can be `root` or one specially created for Weap. If you need help creating a new user, check this guide. * `Server IP or hostname`: the IP or hostname of the server. * `Server port`: The SSH port of the server. The default one is 22. After filling the details, click the button `Next`. ![](https://3208313484-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MFo23y3kKRLVuJ9Nhx_%2F-MFoBmHKlLaS2XFkdPiZ%2F-MFokrmO4W6O0gbIa5qV%2Fimage.png?alt=media\&token=dc0f990a-484a-41f4-85f1-c4b726b50caa) ### 3. Add the SSH key to the server {% hint style="info" %} If your server was already added previously, you can skip this step by clicking "Choose an existent server". {% endhint %} Weap.io generated a new SSH key for your server. The key must be added to your `authorized_keys` file. All the required instructions are already displayed during the setup process. ![](https://3208313484-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MFo23y3kKRLVuJ9Nhx_%2F-MFp-5abO7DOI001W111%2F-MFunHJAXwmkgXLHcu8G%2Fimage.png?alt=media\&token=70cf6359-eff3-4e04-96dd-6f609658e102) ### 4. Connect to the database If everything went ok with the previous step, Weap.io was able to SSH into your server. Now it's time to establish a connection with your PostgreSQL database. To be able to do that, you will need to enter the details of the database: * `User`: the user of the database. It can be root a one specially created for Weap. If you need help creating a new PostgreSQL user, check this guide. * `Password`: the password of the PostgreSQL user. * `Host`: the host of the database. If the database is stored on the same server added previously, it's `localhost` or `127.0.0.1`. If the database is running on a remote server, the host will be the IP (or hostname) of that server. * `Port`: the port of the database, usually 3306. ![](https://3208313484-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MFo23y3kKRLVuJ9Nhx_%2F-MKzx9JHng6dMLE9dVsD%2F-MKzxmQPu8oX99ZsYZF4%2Fimage.png?alt=media\&token=b65d0387-d49f-4a2a-980e-56ee6d93d5d8) ### 5. Select the databases to backup After successfully connecting to the database, Weap will show you a list of all databases available. You can select 1, more or all databases available. After selecting the databases, click the button `Backup selected databases`. ![](https://3208313484-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MFo23y3kKRLVuJ9Nhx_%2F-MKzx9JHng6dMLE9dVsD%2F-MKzxcpGNhe5v3XorXo-%2Fimage.png?alt=media\&token=9d931e3e-ca2f-49fe-9f20-a7908b6d2676) ### 6. Conclusion Congratulations! Your database is now automatically backed-up using the default retention policy and stored on your default storage location (the one provided by Weap if you didn't change it). Feel free to change the retention & frequency as needed. # Auto-synchronize your PostgreSQL databases ### 1. Go to the server page Open the page of the server containing the databases you want to synchronize and hover the mouse on **Server settings.** Select the option **Databases auto-synchronization**. ![](https://3208313484-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MFo23y3kKRLVuJ9Nhx_%2F-Mgb_iDW8mOkUQeManiM%2F-MgbaBg64osM11zvotm3%2Fimage.png?alt=media\&token=0f6d89f2-e615-469f-8d68-e85d6b10bfb9) ### 2. Enable the auto-synchronization Enable the auto-synchronization and select what should happen with the backups of deleted databases. ![](https://3208313484-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MFo23y3kKRLVuJ9Nhx_%2F-Mgb_iDW8mOkUQeManiM%2F-MgbaeXtKTmY--oixZIo%2Fimage.png?alt=media\&token=8e10f519-6cec-4528-aa5a-dfdc969e64f4) # How to decrypt a database backup If you take MySQL or PostgreSQL backups with encryption enabled, you will have to decrypt the backup before the restore. ### Decrypting a backup For this example, we assume the private key is named `my-key.pem` and the encrypted backup file is named `my-db-backup.sql.gz`. {% hint style="danger" %} In order to decrypt encrypted backups, you need the private key generated when you enabled the ecryption. If you don't have the key, the content of the backups is lost! {% endhint %} {% tabs %} {% tab title="Linux" %} ``` cat my-db-backup.sql.gz | openssl smime -decrypt -inform DER -inkey my-key.pem | gunzip > my-db-backup.sql ``` {% endtab %} {% tab title="MacOS" %} ``` cat my-db-backup.sql.gz | openssl smime -decrypt -inform DER -inkey my-key.pem | gunzip > my-db-backup.sql ``` {% endtab %} {% endtabs %} After running the command above, a new file `my-db-backup.sql` will be created with the decrypted database backup. # Get started Get started with File Backups. Weap.io allows you to backup your server files to an external storage of your choice (`AWS S3`, `Wasabi`, `DigitalOcean Spaces` and `Backblaze B2`). {% hint style="success" %} Our Server files backup solution comes with a default storage of up to 250GB. That's in case you don't want to bring your own storage. {% endhint %} Thanks to the intuitive user interface, getting started with your first backup for your server files is simple and fast. ### 1. Open Weap.io dashboard Open your Weap.io dashboard and click on the `File Backups` menu button. On the page just opened, click the button `Schedule new backup`. ![](https://3208313484-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MFo23y3kKRLVuJ9Nhx_%2F-MKzq9C-hQR0dwcSIkbZ%2F-MKzrBJtwLw_aGEv1vo3%2Fimage.png?alt=media\&token=d36093cd-951b-49ee-951e-da8515b5a0f2) ### 2. Add a new server {% hint style="info" %} If your server was already added previously, you can skip this step by clicking "Choose an existent server". {% endhint %} Weap.io needs to be able to connect via SSH to the server you want to backup. in order to connect, provide the following details: * `Friendly name`: a friendly name that will help you recognize the server later * `Server user`: the user that Weap.io will use to SSH into the server. It can be `root` or one specially created for Weap. If you need help creating a new user, check this guide. * `Server IP or hostname`: the IP or hostname of the server. * `Server port`: The SSH port of the server. The default one is 22. After filling the details, click the button `Next`. ![](https://3208313484-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MFo23y3kKRLVuJ9Nhx_%2F-MKzq9C-hQR0dwcSIkbZ%2F-MKzrlYJT-vIQbZaNHL6%2Fimage.png?alt=media\&token=748e0e39-625f-477d-a5dc-4f747d40cb9a) ### 3. Add the SSH key to the server {% hint style="info" %} This step will appear only when adding a new server. It will not be visible when choosing and existent server with a working SSH connection. {% endhint %} Weap.io generated a new SSH key for your server. The key must be added to your `authorized_keys` file. All the required instructions are already displayed during the setup process. ![](https://3208313484-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MFo23y3kKRLVuJ9Nhx_%2F-MKzq9C-hQR0dwcSIkbZ%2F-MKzsIN5zaPAQoafgF9A%2Fimage.png?alt=media\&token=773b45df-478a-4c49-9c85-f9ed732e720e) ### 4. Choose the files to backup Now it's time to give an intuitive name to your backup schedule. In our example it was named `my-files`. The next two things to configure are the paths of the files you want to include in the backups and the ones you want to exclude (if any). In our example, all the files under the paths `/var/lib` and `/media` will be included. Because the directory `/var/lib/not-important-directory` was added to the excluded paths, it will not be part of the backup. {% hint style="info" %} It's mandatory to use absolute paths. {% endhint %} When done, click the button `Create`. ![](https://3208313484-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MFo23y3kKRLVuJ9Nhx_%2F-MKzq9C-hQR0dwcSIkbZ%2F-MKzv5vWnQoJcOvq2Am_%2Fimage.png?alt=media\&token=3213033f-62ac-4382-b323-2af7afb4a4b1) ### 6. Conclusion Congratulations! Your server file are now automatically backed-up using the default retention policy of the server and stored on your default storage location (the one provided by Weap if you didn't change it). Feel free to change the retention & frequency as needed. ![](https://3208313484-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MFo23y3kKRLVuJ9Nhx_%2F-MKzq9C-hQR0dwcSIkbZ%2F-MKzwloyENBQIS1W1vjB%2Fimage.png?alt=media\&token=6c7923a1-cfd2-45f0-9dc3-16180613356e) # Overview When using [Database](https://weap.io/database-backups/mysql) & [File](https://weap.io/file-backups) backups, a storage is required. Weap.io provides you a ready to use storage. However, you are free to extend (or replace) it by connection your own storages. Currently, we support the following cloud storage providers: * AWS S3 * DigitalOcean Spaces * Wasabi * Backblaze B2 You can connect as many storages as you want. # How to connect your AWS S3 storage Lear how to connect your AWS S3 storage to Weap.io Connecting your AWS S3 storage is very simple and quick. ### 1. Create a new S3 bucket Log in into your AWS console, open the S3 service and click the **`Create Bucket`** button. Give a name to your bucket and select a region. In our case we used **`weap-backups`** as the name of the bucket and the region eu-central-1. The other options are ok like they are. The option `Block all public access` should be checked. Scroll at the bottom of the page and click the button **`Create Bucket`**. ![](https://3208313484-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MFo23y3kKRLVuJ9Nhx_%2F-MOXC0P8yMhOtyfcvn-t%2F-MOXDWgWJMjepRvgC-LW%2Fimage.png?alt=media\&token=849fab73-9fc7-446b-8b59-426a4bc43664) ### 2. Create a new IAM user Open the IAM service, go to the users section and click the button **`Add user`** ![](https://3208313484-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MFo23y3kKRLVuJ9Nhx_%2F-MOXC0P8yMhOtyfcvn-t%2F-MOXFjGGORx_DSUX-7VR%2Fimage.png?alt=media\&token=b083e735-1d7b-400e-b69b-c8257ecf7764) Give a name to the user, check the option **`Programmatic access`** and click the button **`Next: Permissions`**. ![](https://3208313484-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MFo23y3kKRLVuJ9Nhx_%2F-MOXC0P8yMhOtyfcvn-t%2F-MOXG-iIVB2QXgh2K5KL%2Fimage.png?alt=media\&token=b5c82cfa-00cd-4bb8-b446-b4033be14f35) Skip the permissions page by clicking the button **`Next: Tags`**. We will not add any tag. Click the button **`Next: Review`**. Finally, click the button **`Create user`**. Save the Access key ID and Secret access key because are visible only once. ![](https://3208313484-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MFo23y3kKRLVuJ9Nhx_%2F-MOXC0P8yMhOtyfcvn-t%2F-MOXHgJFK7Gvi4YlhzVr%2Fimage.png?alt=media\&token=e8640f10-ecba-42d7-a594-d5b4b38daae4) ### 3. Attach S3 permissions to the IAM user Again in the IAM service, search for the user you just created and open it. On the user page, click **`Add inline policy`**. ![](https://3208313484-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MFo23y3kKRLVuJ9Nhx_%2F-MOXC0P8yMhOtyfcvn-t%2F-MOXJHnRpcF7cVxSjSWt%2FScreenshot%202020-12-14%20at%2018.32.52.png?alt=media\&token=0d966c26-4320-4da5-8346-6bc5cf54207d) Choose the **`JSON`** editor and paste the policy below. {% hint style="warning" %} Replace **`weap-backups`** with the name of the bucket you created at step 1 (if you used a different name). {% endhint %} ``` { "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Action": [ "s3:*" ], "Resource": [ "arn:aws:s3:::weap-backups/*", "arn:aws:s3:::weap-backups" ] } ] } ``` Click the button **`Review policy`** and give it an intuitive name. Next, click the button **`Create policy`**. ### 4. Add the storage to Weap.io Open your Weap.io dashboard and go to the **`Storages`** settings. Click the **`Add storage`** button and fill the form with the details from the previous steps. ![](https://3208313484-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MFo23y3kKRLVuJ9Nhx_%2F-MOXKmke9l3VCbJVig-T%2F-MOXLt58URbK7okDk3m-%2Fimage.png?alt=media\&token=c38b445e-eff0-4dad-880f-6501afaf648e) Congratulations! Your S3 storage is now connected to Weap.io and can be used to store your [Database](https://weap.io/database-backups/mysql) & [File](https://weap.io/file-backups) backups. # How to connect your Backblaze B2 storage Connecting your Backblaze B2 storage to Weap.io is simple and quick. ### 1. Create a new Backblaze B2 bucket Log in into your Backblaze account, select **`Buckets`** on the left menu and on the page just opened click **`Create a Bucket`**. ![](https://3208313484-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MFo23y3kKRLVuJ9Nhx_%2F-MUTKLxIz6thRqL8DJJi%2F-MUTM0iWjWsOV-Y4Y5wC%2Fimage.png?alt=media\&token=15b825cb-5c61-4c2f-bbce-a24f7db205d2) Give a name to you bucket to easily recognize it later. ![](https://3208313484-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MFo23y3kKRLVuJ9Nhx_%2F-MUTKLxIz6thRqL8DJJi%2F-MUTN4MsIgdHIQfN-ETZ%2Fimage.png?alt=media\&token=51acd1a4-3652-4f7f-9c98-1e6ad8218acb) ### 2. Create a new Application Key Click **`App Keys`** on the left side menu and then click **`Add new Application Key`**. ![](https://3208313484-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MFo23y3kKRLVuJ9Nhx_%2F-MUTKLxIz6thRqL8DJJi%2F-MUTQOqiGbWX_-MI-ZKh%2Fimage.png?alt=media\&token=003ee046-5286-40fb-959d-30b1937e60ad) Give an intuitive name to the key and select the bucket created previously. Make sure the type of access is **`Read and Write`**. {% hint style="warning" %} Make sure you generate an **`Application Key`**, not a **`Master Application Key`**. If you generate a Master Application Key, it will not work. {% endhint %} ![](https://3208313484-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MFo23y3kKRLVuJ9Nhx_%2F-MUTKLxIz6thRqL8DJJi%2F-MUTQjE5RSpPIiMmSXPF%2Fimage.png?alt=media\&token=13c0667a-fd0a-4c18-90d8-03109ca62c03) Click **`Create New Key`**. Your key was created and the details are displayed. ![](https://3208313484-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MFo23y3kKRLVuJ9Nhx_%2F-MUTKLxIz6thRqL8DJJi%2F-MUTRJqsgMWQKBata2qS%2Fimage.png?alt=media\&token=bfa09459-35c3-4ed0-a819-b478ae25506f) ### 3. Add the storage to Weap.io Open your Weap.io dashboard and go to the **`Storages`** settings. Click the **`Add storage`** button, select Backblaze B2 as storage provider and fill the form with the details from the previous step. ![](https://3208313484-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MFo23y3kKRLVuJ9Nhx_%2F-MUTKLxIz6thRqL8DJJi%2F-MUTRznIF3RIQ_kZw_Sd%2Fimage.png?alt=media\&token=ce16e175-09db-48ea-ab00-68745cac41ea) Congratulations! Your Backblaze B2 storage was connected to your Weap.io dashboard and can be used to store your [Database](https://weap.io/database-backups/mysql) & [File backups](https://weap.io/file-backups). # How to connect your Azure Blob Storage Learn how to connect your Azure Blob Storage to Weap.io Connecting your Azure Blob Storage account to Weap.io is simple and quick. ### 1. Create an Azure Storage account Open your Azure portal and on the sidebar hover your mouse over `Storage accounts` until a small modal appears. On the modal click `Create`. ![](https://3208313484-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MFo23y3kKRLVuJ9Nhx_%2F-Mc3gHolrcsOqs3YkHB6%2F-Mc4w-JvnsMsQV5N3grk%2Fimage.png?alt=media\&token=e9f971d6-d425-4081-ab24-38bc21f69465) Now it's time to configure the new storage. Create a new resource group with an intuitive name (we named it `weap-backups` for this example). Next, you must type a unique `Storage account name`. This must be unique across all existent Azure storage names. The next thing is to select a region. For this example, we selected `Germany West Central`. The `Standard` performance is more than enough but if you want, feel free to choose `Premium`. As `Redundancy` we selected GRS, but again, fell free to change it if you have different requirements. As the final step, click the button `Review + create` and proceed with the creation of the new storage. ![](https://3208313484-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MFo23y3kKRLVuJ9Nhx_%2F-Mc3gHolrcsOqs3YkHB6%2F-Mc5AqBwGS0g7EVOjRdL%2Fimage.png?alt=media\&token=9f96832e-c224-4e5c-a8d4-7f4444261223) ### 2. Create a new container After creating the storage, click the button `Go to resource`. ![](https://3208313484-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MFo23y3kKRLVuJ9Nhx_%2F-Mc5C5SUHOC2IvHpYDl_%2F-Mc5CMeBRhrqyd-NCacN%2Fimage.png?alt=media\&token=4687121f-21cd-420d-ad44-4d38522d694c) On the resource page, click `Containers` on the left sidebar and then click `+ Container` to create a new container. ![](https://3208313484-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MFo23y3kKRLVuJ9Nhx_%2F-Mc5C5SUHOC2IvHpYDl_%2F-Mc5Dr7xNe1ub_7d10pS%2Fimage.png?alt=media\&token=b1828cb6-2502-449a-a1e5-57350972b23b) A new sidebar on the right will appear. Give a name to your container and click `Create`. Remember this name because you will need it later. ![](https://3208313484-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MFo23y3kKRLVuJ9Nhx_%2F-Mc5C5SUHOC2IvHpYDl_%2F-Mc5ECU8lZQkkY_i1eJu%2Fimage.png?alt=media\&token=e92538fa-c119-4946-b913-aa9a4611f58c) ### 3. Generate the Access Key On the resource page click `Access keys` on the left sidebar. ![](https://3208313484-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MFo23y3kKRLVuJ9Nhx_%2F-Mc5C5SUHOC2IvHpYDl_%2F-Mc5CjeE47D-zK0ZFhc_%2Fimage.png?alt=media\&token=9cf66551-4ccf-4bfe-9aec-027da395d008) Now you can see the access keys for your new storage. Copy the `Storage account name` and the first `Key`. ![](https://3208313484-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MFo23y3kKRLVuJ9Nhx_%2F-Mc5C5SUHOC2IvHpYDl_%2F-Mc5DOEsxNN4W4CbDsmS%2Fimage.png?alt=media\&token=8d01a7b4-0428-46d5-80b4-a994e4785479) ### 4. Add the storage to Weap.io Open your Weap.io dashboard and go to the **`Storages`** settings. Click the **`Add storage`** button, select the `Azure Blob Storage` provider and fill the form with the follwoing details: * `Friendly name`: a name to easily recognize your storage account later in the Weap.io dashboard * `Azure account`: the name of your Azure Storage account you choosed at step 1. For this example we used `weapbackups` * `Azure Access Key`: the key you generated at step 3 * `Azure Blob Container`: the container you generated at step 2. We used `my-backups-container` for this example ![](https://3208313484-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MFo23y3kKRLVuJ9Nhx_%2F-Mc5C5SUHOC2IvHpYDl_%2F-Mc5FTxjUdbvKoLl5dHf%2Fimage.png?alt=media\&token=0983a880-6018-4891-a5b9-e8f1f3bc3d78) # How to connect your SFTP storage Weap.io allows you to store your backups on an SFTP storage. ## Connect any SFTP storage Open the Weap.io dashboard, go to the storages page and click the button `Add new storage`. In the modal select `SFTP` and fill the form with the details of your SFTP server. * `host`: the host of your SFTP server * `user`: the user of your SFTP server * `password`: the password of your SFTP server * `port`: the port of your SFTP server. `22` is the default one ![](https://3208313484-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MFo23y3kKRLVuJ9Nhx_%2Fuploads%2FeEcdkKuuksZZcNdun1s8%2Fimage.png?alt=media\&token=3fca16d2-07dd-44a8-b00d-eb3857ab5135) ## Connect a Hetzner Storage Box via SFTP In order to connect a Hetzner Storage Box, follow the same stepts as connecting any SFTP storage but fill the form with the details of the storage box. * `host`: The host of the server is found on the Storage Box details page. In our example is `u142873.your-storagebox.de` * `user`: The user is the first part of the host. In our example is `u142873` * `password`: the password you received when your Storage Box was created. In case you don't find it, you can always reset it and get a new one * `port`: the storage boxes from Hetzner are using the default SSH port which is `22` ![](https://3208313484-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MFo23y3kKRLVuJ9Nhx_%2Fuploads%2FW4FinaWZexRKnokwMB7b%2Fimage.png?alt=media\&token=bb784640-72cb-41e2-bab9-ba91b1073f5c) # How to generate an encryption key Learn how to generate an encryption key. ### Encrypted backups Weap.io allows you to encrypt your backups using asymmetric encryption. This means that your backups will be encrypted using a public key and only the person which has the private key will be able to decrypt them. If the private key is lost, you will not be able to decrypt your backups. ### How to generate an encryption key Open the Weap.io Dashboard, go to the settings and choose **`Encryption keys`** in the left menu. ![](https://3208313484-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MFo23y3kKRLVuJ9Nhx_%2F-MROxyQ7UAGmINiKjR_7%2F-MRP-Gj1CQ9UKXypiwvr%2Fimage.png?alt=media\&token=fe436da0-5dff-4ba7-bde2-80c174e09cf8) On the page just opened, click the button **`Create encryption key`**. Type an intuitive name to easily recognise the encryption key laster and check the checkbox that tells you to store the encryption key in a secure location. Next, click the button Generate encryption key. The download of your private key will start. {% hint style="danger" %} The key must be kept safe because without it you will not be able to decrypt the backups. We don't store the private key, it's your responsibility to make sure it is safely stored. {% endhint %} ![](https://3208313484-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MFo23y3kKRLVuJ9Nhx_%2F-MROxyQ7UAGmINiKjR_7%2F-MRP02HBH_kbngboUcdJ%2Fimage.png?alt=media\&token=3adf436e-2ae3-4e09-b78f-884cdd989e57) Your encryption key was generated and it's ready to be used. ### Generating multiple encryption keys You are able to generate as many encryption keys as wanted. This is useful in case you want to use a different encryption key for each database.