Migrating Your UltraSeedbox Data

Here, you can find some guides on how to transfer your data to your new UltraSeedbox slot.

Migrating Your UltraSeedbox Slot

In this guide we will be doing a migration of your data from your previous slot to your new slot, and then restoring the configurations and data to your respective applications.

We will be using SSH most of this guide, if you are unfamiliar with SSH we have a detailed guide located here: How to connect to your seedbox via SSH


Prerequisites


Migration of Data to the New slot

Transfer Preparation

Using rsync in SSH, we will be making a 1:1 copy of your original slot to your upgraded slot in a directory named transfer located in your upgraded slot's home folder. We will use a utility called screen for this because the processes run in a screen will continue to run even if you close your local SSH terminal.

screen -S transfer

rsync Transfer Proper

The following is our optimized for transfer rsync command to start your migration. This will make a complete 1:1 copy of the original slot's data to a folder named transfer in the destination slot.

rsync transfer command template:

rsync -aHAXxv --numeric-ids --info=progress2 --delete-after --bwlimit=20000 --no-i-r -e "ssh -T -c aes128-ctr -o Compression=no -x" username@lw##.usbx.me:. transfer

So for example, if the username was usb555 and the slot server was LW850.usbx.me where the original slot would be transferring my data from, then the transfer command would be the following

rsync transfer command example:

rsync -aHAXxv --numeric-ids --info=progress2 --delete-after --bwlimit=20000 --no-i-r -e "ssh -T -c aes128-ctr -o Compression=no -x" usb555@lw850.usbx.me:. transfer

After you have copied the rsync transfer command with your ORIGINAL slot details, you will be prompted for your ORIGINAL slot SSH password, after you have entered your password press ENTER to start the migration.

This initial step of rsync "receiving file list ..." may take some time to complete depending on the file/folder count, but rest assured the transfer will proceed to the next step of actually transferring the files

After the receiving file list ... has finished, you will then see the transfer commencing. This example screenshot points out where you can see your transfer % progress and the estimated time for completion.

It may take some time for the rsync process to move on to larger files to actually see these values.

After the transfer is completed, you will see the text stop scrolling and will resemble the example screenshot below of a completed rsync transfer

After confirming your rsync transfer is completed, you can then close out of your terminal screen by entering the command

exit

Some tips on how to use the screen utility

screen -rd  transfer

Restoration of Migrated Data

In this next section, we will be restoring your data and application configuration files on your UPGRADED slot.

If you have followed the above steps for migrating your ORIGINAL slot's data using the rsync transfer template command, you should now have your migrated data located in ~/transfer on your UPGRADED slot.

During this time, you may install your applications to your new slot (but do not set it up, as you will attempt to restore your configuration/data from your old slot). Once you've finished installing your applications, you may proceed to the following sections.

Refer to the Table of Contents on the left-side of this guide to jump to the relevant sections.

Torrent Clients

Prerequisites

First, this restore section assumes that you have already installed the torrent clients you plan to restore on your upgraded slot. It is important to note here that these freshly installed torrent clients should have an empty torrent session with no active torrents, any current torrents that are in your clients will be removed by following this restore procedure.

mv -f ~/transfer/files/* ~/files/
mv -f ~/transfer/SpecialDownloadFolder ~

Deluge

After you have moved all torrent's data to its correct locations for Deluge seeding restoration, we can now proceed to modify Deluge session files to match that of your upgraded slot home directory. To do this, first we will be using a few SSH commands to first get the original slot's home#, and then another command to update your migrated rTorrent session folder data files.

app-deluge stop
cat ~/transfer/.config/deluge/state/torrents.state | grep home --color

As you can see in the screenshot example, the home will be colorized to make it easier to find. The value we need to note here in the example is home8 and we will refer to this value as homeOLD

pwd

In the screenshot example, home34 is the current home number we will be needing, which we will refer to as homeNEW

sed command TEMPLATE:

sed -i 's/homeOLD/homeNEW/g' ~/transfer/.config/deluge/state/torrents.state

sed command EXAMPLE:

sed -i 's/home8/home34/g' ~/transfer/.config/deluge/state/torrents.state
cp -a ~/transfer/.config/deluge/state/* ~/.config/deluge/state/
app-deluge restart

Be sure to reload your Deluge WebUI to confirm that your migrated torrents are now in the session and running as expected.


rTorrent

After you have moved all torrent's data to its correct locations for rTorrent seeding restoration, we can now proceed to modify the session data rTorrent to match that of your upgraded slot home directory. To do this, we will be using a few SSH commands to first get the original slot's home#, and then another command to update your migrated rTorrent session folder data files.

app-rtorrent stop
cat ~/transfer/.config/rtorrent/session/*.rtorrent | grep home --color

As you can see in the screenshot example, the home will be colorized to make it easier to find. The value we need to note here in the example is home8 and we will refer to this value as homeOLD

pwd

In the screenshot example, home34 is the current home number we will be needing, which we will refer to as homeNEW

sed command TEMPLATE:

sed -i 's/homeOLD/homeNEW/g' ~/transfer/.config/rtorrent/session/*.rtorrent

sed command EXAMPLE:

So for example, from the screenshot examples in this section, the sed command would be

sed -i 's/home8/home34/g' ~/transfer/.config/rtorrent/session/*.rtorrent
cp -a ~/transfer/.config/rtorrent/session/* ~/.config/rtorrent/session/
app-rtorrent restart

Be sure to reload your ruTorrent WebUI to confirm that your migrated torrents are now in the session and running as expected.


Transmission

After you have moved all torrent’s data to its correct locations for Transmission seeding restoration, we can now proceed to modify the migrated session data for Transmission to match that of the upgraded slot home directory. To do this, first we will be using a few SSH commands to first get the original slot’s home#, and then another command to update your migrated Transmission session folder data files.

app-transmission stop
cat ~/transfer/.config/transmission-daemon/resume/*.resume | grep -a home --color

As you can see in the screenshot example, home will be colorized to make it easier to find. The value we need to note here in the example is home8 and we will refer to this value as homeOLD

pwd

In the screenshot example, home34 is the current home number we will be needing, which we will refer to as homeNEW.

sed command TEMPLATE:

sed -i 's/homeOLD/homeNEW/g' ~/transfer/.config/transmission-daemon/resume/*.resume

sed command EXAMPLE:

sed -i 's/home8/home34/g' ~/transfer/.config/transmission-daemon/resume/*.resume
cp -a ~/transfer/.config/transmission-daemon/resume/* ~/.config/transmission-daemon/resume/ && cp -a ~/transfer/.config/transmission-daemon/torrents/* ~/.config/transmission-daemon/torrents/

Now that we have our Transmission session data files correctly set to our current home directory, and have moved our Deluge torrent data directories to their correct place, we can restart Transmission with the following SSH command:

app-transmission restart

Be sure to reload your Transmission WebUI to confirm that your migrated torrents are now in the session and running as expected.


Restoration of Applications

In this next section, we will be restoring your data and application configuration files for docker apps on your UPGRADED slot.

If you have followed the above steps for migrating your ORIGINAL slot's data using the rsync transfer template command, you should now have your migrated data located in ~/transfer on your UPGRADED slot.

Refer to the Table of Contents on the left-side of this guide to jump to the relevant sections.

Airsonic

Prerequisites

Steps to Restore Your Migrated Airsonic Configuration Data

app-airsonic stop
mv ~/.apps/airsonic ~/.apps/airsonic.fresh && mv ~/.config/airsonic ~/.config/airsonic.fresh
mv ~/transfer/.apps/airsonic ~/.apps/airsonic && mv ~/transfer/.config/airsonic ~/.config/airsonic
app-airsonic restart

You can now access your Airsonic WebUI URL on your upgraded slot with your migrated Airsonic configuration restored.

rm -rf ~/.apps/airsonic.fresh ~/.config/airsonic.fresh

Bazarr

Prerequisites

Steps to Restore Your Migrated Bazarr Configuration Data

app-bazarr stop
mv ~/.apps/bazarr ~/.apps/bazarr.fresh
mv ~/transfer/.apps/bazarr ~/.apps/bazarr
app-bazarr upgrade

You can now access your Bazarr WebUI URL on your upgraded slot with your migrated Bazarr configuration restored.

rm -rf ~/.apps/bazarr.fresh

CouchPotato

Prerequisites

Steps to Restore Your Migrated CouchPotato Configuration Data

app-couchpotato stop
mv ~/.apps/couchpotato ~/.apps/couchpotato.fresh
mv ~/transfer/.apps/couchpotato ~/.apps/couchpotato
app-couchpotato upgrade

You can now access your CouchPotato WebUI URL on your upgraded slot with your migrated CouchPotato configuration restored.

rm -rf ~/.apps/couchpotato.fresh

Addition WebUI Required Steps for Restoring CouchPotato


Jackett

Prerequisites

Steps to Restore Your Migrated Jackett Configuration Data

app-jackett stop
mv ~/.apps/jackett ~/.apps/jackett.fresh
mv ~/transfer/.apps/jackett ~/.apps/jackett
app-jackett upgrade

You can now access your Jackett WebUI URL on your upgraded slot with your migrated Jackett configuration restored.

rm -rf ~/.apps/jackett.fresh

Jdownloader2

Prerequisites

Steps to Restore Your Migrated Jdownloader2 Configuration Data

app-jdownloader2 stop
mv ~/.config/jdownloader2 ~/.config/jdownloader2.fresh
mv ~/transfer/.config/jdownloader2 ~/.config/jdownloader2
app-jdownloader2 restart

You can now access your Jdownloader2 WebUI URL on your upgraded slot with your migrated Jdownloader2 configuration restored.

rm -rf ~/.config/jdownloader2.fresh

LazyLibrarian

Prerequisites

Steps to Restore Your Migrated LazyLibrarian Configuration Data

app-lazylibrarian stop
mv ~/.apps/lazylibrarian ~/.apps/lazylibrarian.fresh && mv ~/.config/lazylibrarian ~/.config/lazylibrarian.fresh
mv ~/transfer/.apps/lazylibrarian ~/.apps/lazylibrarian && mv ~/transfer/.config/lazylibrarian ~/.config/lazylibrarian
app-lazylibrarian upgrade

You can now access your LazyLibrarian WebUI URL on your upgraded slot with your migrated LazyLibrarian configuration restored.

rm -rf ~/.apps/lazylibrarian.fresh ~/.config/lazylibrarian.fresh

Addition WebUI Required Steps for Restoring LazyLibrarian:


Lidarr

Prerequisites

Steps to Restore Your Migrated Lidarr Configuration Data

app-lidarr stop
mv ~/.apps/lidarr ~/.apps/lidarr.fresh
mv ~/transfer/.apps/lidarr ~/.apps/lidarr
app-lidarr upgrade

You can now access your Lidarr WebUI URL on your upgraded slot with your migrated Lidarr configuration restored.

rm -rf ~/.apps/lidarr.fresh

Addition WebUI Required Steps for Restoring Lidarr


Medusa

Prerequisites

Steps to Restore Your Migrated Medusa Configuration Data

app-medusa stop
mv ~/.apps/medusa ~/.apps/medusa.fresh
mv ~/transfer/.apps/medusa ~/.apps/medusa
app-medusa upgrade

You can now access your Medusa WebUI URL on your upgraded slot with your migrated Medusa configuration restored.

rm -rf ~/.apps/medusa.fresh

Addition WebUI Required Steps for Restoring Medusa


Mylar

Prerequisites

Steps to Restore Your Migrated Mylar Configuration Data

app-mylar stop
mv ~/.apps/mylar ~/.apps/mylar.fresh && mv ~/.config/mylar ~/.config/mylar.fresh
mv ~/transfer/.apps/mylar ~/.apps/mylar && mv ~/transfer/.config/mylar ~/.config/mylar
app-mylar upgrade

You can now access your Mylar WebUI URL on your upgraded slot with your migrated Mylar configuration restored.

rm -rf ~/.apps/mylar.fresh ~/.config/mylar.fresh

NZBget

Prerequisites

Steps to Restore Your Migrated NZBget Configuration Data

app-nzbget stop
mv ~/.apps/nzbget ~/.apps/nzbget.fresh
mv ~/transfer/.apps/nzbget ~/.apps/nzbget
app-nzbget upgrade

You can now access your NZBget WebUI URL on your upgraded slot with your migrated NZBget configuration restored.

To remove the fresh installation configuration data that is no longer needed, run the following SSH command

rm -rf ~/.apps/nzbget.fresh

Addition WebUI Required Steps for Restoring NZBget


NZBHydra2

Prerequisites

Steps to Restore Your Migrated NZBHydra2 Configuration Data

app-nzbhydra2 stop
mv ~/.config/nzbhydra2 ~/.config/nzbhydra2.fresh
mv ~/transfer/.config/nzbhydra2 ~/.config/nzbhydra2
app-nzbhydra2 upgrade

You can now access your NZBHydra2 WebUI URL on your upgraded slot with your migrated NZBHydra2 configuration restored.

rm -rf ~/.config/nzbhydra2.fresh

Ombi

Prerequisites

Steps to Restore Your Migrated Ombi Configuration Data

app-ombi stop
mv ~/.config/ombi ~/.config/ombi.fresh
mv ~/transfer/.config/ombi ~/.config/ombi
app-ombi upgrade

You can now access your Ombi WebUI URL on your upgraded slot with your migrated Ombi configuration restored.

rm -rf ~/.config/ombi.fresh

Addition WebUI Required Steps for Restoring Ombi


Plex Media Server

Prerequisites

Steps to Restore Your Migrated Plex Configuration Data

app-plex stop
mv ~/.config/plex ~/.config/plex.fresh
mv ~/transfer/.config/plex ~/.config/plex
app-plex upgrade
Upgrading your Plex Media Server version (Optional)
app-plex upgrade --plex-version=public
app-plex upgrade --plex-version=latest

You can now access your Plex Media Server on your upgraded slot with your migrated Plex configuration data restored.

rm -rf ~/.config/plex.fresh

Addition WebUI Required Steps for Restoring Plex

If you are experiencing any issues with your Plex.tv account not connecting to your slot's Plex Media Server "Securely" then you may need to reclaim your Plex application with the green actions button in your UCP.


pyLoad

Prerequisites

Steps to Restore Your Migrated pyLoad Configuration Data

app-pyload stop
mv ~/.apps/pyload ~/.apps/pyload.fresh
mv ~/transfer/.apps/pyload ~/.apps/pyload
app-pyload upgrade

You can now access your pyLoad WebUI URL on your upgraded slot with your migrated pyLoad configuration restored.

rm -rf ~/.apps/pyload.fresh

Addition WebUI Required Steps for Restoring pyLoad


Radarr

Prerequisites

Steps to Restore Your Migrated Radarr Configuration Data

app-radarr stop
mv ~/.apps/radarr ~/.apps/radarr.fresh
mv ~/transfer/.apps/radarr ~/.apps/radarr
app-radarr upgrade

You can now access your Radarr WebUI URL on your upgraded slot with your migrated Radarr configuration restored.

rm -rf ~/.apps/radarr.fresh

Addition WebUI Required Steps for Restoring Radarr


SABnzbd

Prerequisites

Steps to Restore Your Migrated SABnzbd Configuration Data

app-sabnzbd stop
mv ~/.apps/sabnzbd ~/.apps/sabnzbd.fresh
mv ~/transfer/.apps/sabnzbd ~/.apps/sabnzbd
app-sabnzbd upgrade

You can now access your SABnzbd WebUI URL on your upgraded slot with your migrated SABnzbd configuration restored.

rm -rf ~/.apps/sabnzbd.fresh

Sonarr

Prerequisites

Restoring Your Migrated Sonarr Configuration Data

app-sonarr stop
mv ~/.apps/sonarr ~/.apps/sonarr.fresh
mv ~/transfer/.apps/sonarr ~/.apps/sonarr
app-sonarr upgrade

You can now access your Sonarr WebUI URL on your upgraded slot with your migrated Sonarr configuration restored.

rm -rf ~/.apps/sonarr.fresh

Addition WebUI Required Steps for Restoring Sonarr


SickChill

Prerequisites

Steps to Restore Your Migrated SickChill Configuration Data

app-sickchill stop
mv ~/.apps/sickchill ~/.apps/sickchill.fresh
mv ~/transfer/.apps/sickchill ~/.apps/sickchill
app-sickchill upgrade

You can now access your SickChill WebUI URL on your upgraded slot with your migrated SickChill configuration restored.

rm -rf ~/.apps/sickchill.fresh

Addition WebUI Required Steps for Restoring SickChill


Syncthing

Prerequisites

Steps to Restore Your Migrated Syncthing Configuration Data

app-syncthing stop
mv ~/.apps/syncthing ~/.apps/syncthing.fresh
mv ~/transfer/.apps/syncthing ~/.apps/syncthing
app-syncthing upgrade

You can now access your Syncthing WebUI URL on your upgraded slot with your migrated Syncthing configuration restored.

To remove the fresh installation configuration data that is no longer needed, run the following SSH command

rm -rf ~/.apps/syncthing.fresh

Tautulli

Prerequisites

Steps to Restore Your Migrated Tautulli Configuration Data

app-tautulli stop
mv ~/.config/tautulli ~/.config/tautulli.fresh
mv ~/transfer/.config/tautulli ~/.config/tautulli
app-tautulli upgrade

You can now access your Tautulli WebUI URL on your upgraded slot with your migrated Tautulli configuration restored.

rm -rf ~/.config/tautulli.fresh

Addition WebUI Required Steps for Restoring Tautulli


Ubooquity

Prerequisites

Steps to Restore Your Migrated Ubooquity Configuration Data

app-ubooquity stop
mv ~/.apps/ubooquity ~/.apps/ubooquity.fresh && mv ~/.config/ubooquity ~/.config/ubooquity.fresh
mv ~/transfer/.apps/ubooquity ~/.apps/ubooquity && mv ~/transfer/.config/ubooquity ~/.config/ubooquity && mv ~/transfer/books/* ~/books/ && mv ~/transfer/downloads/* ~/downloads/
app-ubooquity upgrade

You can now access your Ubooquity WebUI URL on your upgraded slot with your migrated Ubooquity configuration restored.

rm -rf ~/.apps/ubooquity.fresh ~/.config/ubooquity.fresh

ZNC

Prerequisites

Steps to Restore Your Migrated ZNC Configuration Data

app-znc stop
mv ~/.apps/znc ~/.apps/znc.fresh && mv ~/.config/znc ~/.config/znc.fresh
mv ~/transfer/.apps/znc ~/.apps/znc && mv ~/transfer/.config/znc ~/.config/znc
app-znc restart

You can now access your ZNC WebUI URL on your upgraded slot with your migrated ZNC configuration restored.

rm -rf ~/.apps/znc.fresh ~/.config/znc.fresh