Vidjil backup: Difference between revisions
Jump to navigation
Jump to search
(Restore Backup Day) |
(Restore recipe) |
||
| Line 14: | Line 14: | ||
* code is backed up by git | * code is backed up by git | ||
* Vidjil Backup Restore Day: every year, on the second Wednesday of July | * Vidjil Backup Restore Day: every year, on the second Wednesday of July | ||
Backup restore: | |||
* Create a new virtual machine in host 60 | |||
* Add Unidade de DVD to the VM at configurações (HyperV) | |||
* Change to Microsoft UEFI certificate at configurações/segurança (HyperV) | |||
* Install Ubuntu and docker | |||
* Clone the Vidjil wrapper code | |||
* Restore Docker images (docker load client & server) | |||
* Configure .env and propagate | |||
* Start Vidjil wrapper and test | |||
* Restore data dir, except uploads | |||
* Restore uploads and test | |||
* Restore mysql dump | |||
Revision as of 12:25, 10 August 2023
Storage directory structure:
- keep the Vidjil structure
- backup the data directory, including fastq files, analyses, and .vidjil files
- check old backups to make sure there's only one backup storage
Files before 2020:
- store in external hard drives
- no need to store raw data from sequencer if not analyzed by Vidjil
Backup policy:
- use external hard drives, preferably with 5TB each or more
- backup Vidjil's data dir
- backup Vidjil's mysql dump
- code is backed up by git
- Vidjil Backup Restore Day: every year, on the second Wednesday of July
Backup restore:
- Create a new virtual machine in host 60
- Add Unidade de DVD to the VM at configurações (HyperV)
- Change to Microsoft UEFI certificate at configurações/segurança (HyperV)
- Install Ubuntu and docker
- Clone the Vidjil wrapper code
- Restore Docker images (docker load client & server)
- Configure .env and propagate
- Start Vidjil wrapper and test
- Restore data dir, except uploads
- Restore uploads and test
- Restore mysql dump