Migrating from Single Machine to Clustered Bugsnag On-premise
To get started with your migration from Single Machine to Clustered Bugsnag On-premise, you’ll need the following things prepared in advance:
The migration can take some time and is dependent on the number of events you have, however you can continue to use your current Single Machine instance whilst the data is migrating. We estimate that it takes around 1 hour to migrate 8 million events of data. There will be some downtime after the data has been migrated and Clustered Bugsnag On-premise starts, this may take around 10-15 mins.
Run migrating-settings.sh on the currently running Bugsnag machine. This will generate a copy of the config required for the migration:
.ship folder from where you will be starting the migration.
Run the following to run the configuration tool:
docker pull replicated/ship && \ docker run -it -p 8800:8800 --rm -v `pwd`:/out \ -v /var/run/docker.sock:/var/run/docker.sock \ -e HTTP_PROXY -e HTTPS_PROXY -e NO_PROXY \ replicated/ship init --preserve-state \ "replicated.app/bugsnag-clustered"
You will be asked to enter your Bugsnag On-premise license. Enter the license you received from Bugsnag to continue to the next step.
The configuration tool will be available at
You can check the progress of the uploads migration by running the following on the Bugsnag machine:
docker logs bugsnag_migrate-uploads
Once this states “Migration of uploads completed.”, this migration is complete.
You can check the progress of the MongoDB migration by checking the status of the replica set:
kubectl -n <NAMESPACE> exec -it mongo-0 -- mongo-local --eval "rs.status()"
If the MongoDB instance in Kubernetes is in
STARTUP2 mode you can check the progress of the collection copying using:
kubectl -n <NAMESPACE> logs -f mongo-0 | grep "repl writer worker"
Once the instance is in
SECONDARY mode you can use the following to check the replication lag:
kubectl -n <NAMESPACE> exec -it mongo-0 -- mongo-local --eval "rs.printSlaveReplicationInfo()"
Once this states that the MongoDB instance is 0 secs behind master, this migration is complete.
Once MongoDB has finished migrating run migrate-redis.sh on the Bugsnag machine and select “Backup redis data” option to begin backing up the redis data from your current Bugsnag instance. Once that has completed you can use the “Restore redis data to kubernetes” option to begin the restore. If you do not have access to the Kubernetes cluster from that machine you should copy the output archive to machine which does and run migrate-redis.sh using the restore option and specifying the archive location to begin migrating the redis data.
Once all the migration are complete:
Configure the current Bugsnag machine via Replicated settings to disable migration mode and restart:
Run the following to reconfigure Bugsnag:
docker pull replicated/ship && \ docker run -it -p 8800:8800 --rm -v `pwd`:/out \ -v /var/run/docker.sock:/var/run/docker.sock \ -e HTTP_PROXY -e HTTPS_PROXY -e NO_PROXY \ replicated/ship edit
Disable migration mode and apply the generated Kubernetes YAML.