Vidjil backup: Difference between revisions
Jump to navigation
Jump to search
(disk) |
(OS later) |
||
| Line 17: | Line 17: | ||
Backup restore: | Backup restore: | ||
* Create a new Generation 2 virtual machine in host 60, with 8GB of RAM, WAN2 network, with enough disk space to hold the data | * Create a new Generation 2 virtual machine in host 60, with 8GB of RAM, WAN2 network, with enough disk space to hold the data | ||
* Say you will install the OS later | |||
* Add a DVD unit to the VM at configurações (HyperV) | * Add a DVD unit to the VM at configurações (HyperV) | ||
* Change to Microsoft UEFI certificate at configurações/segurança (HyperV) | * Change to Microsoft UEFI certificate at configurações/segurança (HyperV) | ||
Revision as of 12:32, 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 Generation 2 virtual machine in host 60, with 8GB of RAM, WAN2 network, with enough disk space to hold the data
- Say you will install the OS later
- Add a DVD unit 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