Migrating QPKGs between NAS - OneCDOnly/sherpa GitHub Wiki
It's possible to migrate your sherpa application configs between an old NAS and a new NAS. Here's a basic guide showing how to do this.
[!IMPORTANT] Wait until your applications have finished processing all current downloads, TV show updates, etc... before starting this.
Your sherpa applications will be installed automatically on the new NAS if a configuration backup is found for each package. Your remaining QPKGs will require manual installation.
Host, volume and path names stored in each application config must be updated manually if they differ between your old and new NAS. If-required, it's beyond the scope of this guide.
Login via SSH on your old NAS.
- Begin by stopping (and disabling) all sherpa QPKGs. If these remain active, their databases will drift out-of-sync with the instances on your new NAS very-quickly:
sudo sherpa stop installed disable installed - Backup all your sherpa QPKGs. Only those that support
backupwill do-so, those that don't support it don't need backups:sudo sherpa backup installed - Create a single archive of your backups to transfer across to the new NAS. This archive file will be created in
/share/Publicon the old NAS. There's an online script to do this:curl -skL https://tinyurl.com/build-sherpa-archive | sudo bash - At this point, you'll need to manually copy (or move) the archive file across to the new NAS and put it in
/share/Public. The file is:
Any method is fine: USB drive, across your LAN with SMB, NFS etc, or even/share/Public/sherpa-backup-archive.tar.gzscpif you're feeling adventurous.
Now, login via SSH on your new NAS.
- Deploy the backup files into the correct location (with another online script):
curl -skL https://tinyurl.com/deploy-sherpa-archive | sudo bash - Ensure you've installed sherpa:
curl -skL https://tinyurl.com/get-sherpa > /share/Public/sherpa.qpkg; sudo sh /share/Public/sherpa.qpkg; sudo sherpa check - Rebuild your QPKGs. Only QPKGs with backup files will be rebuilt. A
rebuildinstalls the QPKG, then restores the backup data into the application configuration again:sudo sherpa rebuild all - You won't need the archive file now, so it can be deleted:
rm /share/Public/sherpa-backup-archive.tar.gz
And, you're done!