limbosolutions.com/git.limbosolutions.com
1
0
Fork 0
Code Issues Pull Requests Actions Projects Releases Wiki Activity

.

Browse Source
This commit is contained in:
Márcio Fernandes
2022-10-08 16:56:26 +01:00
parent c96dfcac5b
commit 74b13252fe
2 changed files with 22 additions and 40 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
README.md
View File

@@ -1,11 +1,11 @@
# git.limbosolutions.com
## Setup
for more information check /documentation/setup.md
## Backup Strategy
Duplicati running on docker.

56
documentation/setup.md
View File

@@ -27,58 +27,40 @@ Access duplicati (http://ipaddress:8200) and set a password
### Process
1) Recreate stack gitea _[Docker Compose](../docker/docker-compose.yaml)_ removing read only restrictions on duplicati volumes
1) Check Every Container is ok and running
1) Stop Every Container except duplicati (including portainer, if restoring portainer is a requirement)
_note: restore portainer not tested_
1) Check every Container is ok and running
1) Stop every Container except duplicati and portainer
_note: restore of portainer/duplicati not tested_
1) Enter Duplicati (http://githost:8200)
1) Import Backup job (if not possible next steps must be adapted)
- Restore with permissions checked
- All Imported jobs schedules must be disabled (or disable write permissions on backup host)
- Remove references to scripts (example:run-script-before-required)
- Recreate duplicati local database (home-> backup-> advanced-> database-> Recreate (delete and repair))
- Remove references to scripts (example:run-script-before-required, /data/myScripts/backupdb.sh)
1) Recreate duplicati local database (home-> backup-> advanced-> database-> Recreate (delete and repair))
1) Restore all files to original location
- If database engine is diferent do not restore db_data and check restore database **before next steps**
- Restore to duplicati only custom scripts (duplicati-data/myScripts), dot not restore full duplicati with this processs because duplicati is running!
- From duplicati only restore custom scripts (duplicati-data/myScripts), dot not restore full duplicati with this processs because duplicati is running!
1) Recreate stack gitea _[Docker Compose](../docker/docker-compose.yaml)_ with original read only restrictions on duplicati volumes
1) Confirm everything is ok and running
1) Return to duplicati on schedule job add script to run-script-before-required /data/myScripts/backupdb.sh
1) Execute a backup
1) Reenable Scheduling
### Database
Only required of database data files not recovarable (example: diferent database engine from backup)
Only required if database data files not recovarable. (Example: diferent database engine from backup)
1) Start Portainer container (if stopped in restore process)
2) Start Database container (if stopped in restore process)
3) Enter dabase container bash (by using portainer)
4) Execute Command
````bash
```bash
#check last files db-dumps
ls /git/db-dumps
#pick file to import (maybe the last one :))
```
import file
3) Enter Database container bash (by using portainer)
4) Execute:
```bash
#select a file to import
ls /db-dumps
#select a file to import
DB_FILE=filenametoimport
# by default duplicati container dont have de enviroment varible ${DB_ROOT_PASSWORD}
mysql -uroot -p'${MYSQL_ROOT_PASSWORD}' $MYSQL_DATABASE < /db-dumps/$DB_FILE
mysql -uroot -p $MYSQL_DATABASE < /db-dumps/$DB_FILE
and enter rootpassword
mysql --host db -uroot -p'${MYSQL_ROOT_PASSWORD}' < /git/db-dumps/$DB_FILE
DB_FILE= "file name to import"
#
mysql --host db -uroot -p ${MYSQL_DATABASE} < /db-dumps/$DB_FILE
#enter root password (root password is in enviromnent variable ${MYSQL_ROOT_PASSWORD})
```
````
3) start all stop containers and check everyting is ok
4) Execute backup on duplicati
5) Check backup is restorable
6) Re Enable schedule backups on duplication