fixed typos #144
@ -170,7 +170,7 @@ In this section, we cover how to make a BorgBackup on the Nextcloud VM and we al
|
|||||||
|
|
||||||
In the section **Backup and restore**, you can set a [BorgBackup](https://www.borgbackup.org/) of your Nextcloud instance.
|
In the section **Backup and restore**, you can set a [BorgBackup](https://www.borgbackup.org/) of your Nextcloud instance.
|
||||||
|
|
||||||
* Add a mount point and a directory name for your backup (e.g. **/mnt/backup**) and click **Submit backup location**.
|
* Add a mount point and a directory name for your backup (e.g. **/mnt/data/backup**) and click **Submit backup location**.
|
||||||
* After the creation of the backup location, write down the **encryption password for backups** somewhere safe and offline.
|
* After the creation of the backup location, write down the **encryption password for backups** somewhere safe and offline.
|
||||||
* Click **Create backup** to create a BorgBackup of your Nextcloud instance.
|
* Click **Create backup** to create a BorgBackup of your Nextcloud instance.
|
||||||
* This will stop all containers, run the backup container and create the backup.
|
* This will stop all containers, run the backup container and create the backup.
|
||||||
@ -188,7 +188,7 @@ After the first manual backup of your Nextcloud instance is complete, you can se
|
|||||||
|
|
||||||
To allow for another layer of redundancy, you can set a secondary VM on the grid and make a daily backup from the BorgBackup of your Nextcloud instance to the secondary VM. The following shows how to do this. It is based on the [File Transfer section](system_administrators@@file_transfer) of the manual.
|
To allow for another layer of redundancy, you can set a secondary VM on the grid and make a daily backup from the BorgBackup of your Nextcloud instance to the secondary VM. The following shows how to do this. It is based on the [File Transfer section](system_administrators@@file_transfer) of the manual.
|
||||||
|
|
||||||
For the following, we take into account that the BorgBackup is located at `/mnt/backup` on the VM running Nextcloud.
|
For the following, we take into account that the BorgBackup is located at `/mnt/data/backup` on the VM running Nextcloud.
|
||||||
|
|
||||||
You will need to deploy a full VM on the TFGrid and SSH into this secondary VM.
|
You will need to deploy a full VM on the TFGrid and SSH into this secondary VM.
|
||||||
|
|
||||||
@ -249,7 +249,7 @@ nano /root/rsync_nextcloud_backup.sh
|
|||||||
```
|
```
|
||||||
#!/bin/bash
|
#!/bin/bash
|
||||||
|
|
||||||
sudo rsync -avz --progress --delete --log-file=/root/nextcloud_backup/rsync_nextcloud_storage.log /root/nextcloud_backup/ root@<Nextcloud_VM_IP_Address>:/mnt/backup
|
sudo rsync -avz --progress --delete --log-file=/root/nextcloud_backup/rsync_nextcloud_storage.log root@<Nextcloud_VM_IP_Address>:/mnt/data/backup /root/nextcloud_backup/
|
||||||
```
|
```
|
||||||
* Give permission to execute the script
|
* Give permission to execute the script
|
||||||
```
|
```
|
||||||
|
@ -71,6 +71,10 @@ We show the steps to prepare the VM to run the network instance.
|
|||||||
|
|
||||||
If you are deploying on testnet or devnet, simply replace `mainnet` by the proper network in the following lines.
|
If you are deploying on testnet or devnet, simply replace `mainnet` by the proper network in the following lines.
|
||||||
|
|
||||||
|
- Set the prerequisites
|
||||||
|
```
|
||||||
|
apt update && apt install -y git nano ufw
|
||||||
|
```
|
||||||
- Download the ThreeFold Tech `grid_deployment` repository
|
- Download the ThreeFold Tech `grid_deployment` repository
|
||||||
```
|
```
|
||||||
git clone https://github.com/threefoldtech/grid_deployment
|
git clone https://github.com/threefoldtech/grid_deployment
|
||||||
@ -79,8 +83,8 @@ If you are deploying on testnet or devnet, simply replace `mainnet` by the prope
|
|||||||
- Generate a TFChain node key with `subkey`
|
- Generate a TFChain node key with `subkey`
|
||||||
- Note: If you deploy the 3 network instances, you can use the same node key for all 3 networks. But it is recommended to use 3 different keys to facilitate management.
|
- Note: If you deploy the 3 network instances, you can use the same node key for all 3 networks. But it is recommended to use 3 different keys to facilitate management.
|
||||||
```
|
```
|
||||||
echo .subkey_mainnet >> .gitignore
|
echo .nodekey_mainnet >> .gitignore
|
||||||
../subkey generate-node-key > .nodekey_mainnet
|
../../apps/subkey generate-node-key > .nodekey_mainnet
|
||||||
cat .nodekey_mainnet
|
cat .nodekey_mainnet
|
||||||
```
|
```
|
||||||
- Create and the set environment variables file
|
- Create and the set environment variables file
|
||||||
|
Loading…
Reference in New Issue
Block a user