# Transfer tracker to another server
# In which case the tracker is transferred
Frequent critical failures of the current server where the tracker is installed.
Unsuitable functionality and pricing system.
Not enough disk space and no possibility to increase it at your current cloud provider.
Need to change the data center of the server and save statistics.
Need to make a duplicate, copy of tracker for scaling funnels or testing new GEOs.
# The actual method of migrating a tracker to a new server
All commands are executed on the server to which you want to migrate.
Log in to the server via SSH.
Run the tracker installation script
curl keitaro.io/kctl.sh | bash -s -- install
- After tracker will be installed — run
Processes running inside the screen are not interrupted when the connection to the server is broken.
- Start data migration from the old server to the new one with the command.
[SSH_PASSWORD=somepass] kctl transfers copy-from <OLD-SERVER-IP>
somepass is the ssh password to old server,
OLD-SERVER-IP is the IP address of the old server
SSH_PASSWORD=123123 kctl transfers copy-from 220.127.116.11
If access to the server from which you want to migrate is possible only with a key — upload the key to the new server and run the script
SSH_PATH_TO_KEY="/path/to/my/ssh.private.key" kctl transfer copy-from OLD_SERVER_IP
All statistics and settings, including local landing pages, offers and user lists of bots and user agents are transferred automatically.
Do not create campaigns, affiliate networks, and other entities in the new tracker until the migration process is complete. When the migration script finishes, the new tracker will contain only data from the old tracker.
Wait until the
kctl transfer script finishes it's working and then start working with the new tracker.
# Creating an archive copy of the tracker locally
Create an archive copy of the tracker locally on the current server. Including MySQL data, ClickHouse data, system settings, local landing pages, salt, Postback key, SSL-certificates, filters, custom bot lists, etc.)
kctl transfers dump
Data will be saved in
/var/lib/kctl-transfers and avaliable for downloading.
# Restoring tracker from an archive local copy
Restoring the tracker from local archoeve copy on the current server. Including MySQL data, ClickHouse data, system settings, local landing pages, salt, Postback key, SSL-certificates, filters, custom bot lists, etc.)
kctl transfers restore
Data will be taken from