How do I move my Hub Instance to a new server?
Last Updated: August | Applicable Hub Versions: All
Last Updated: August | Applicable Hub Versions: All
To move your Hub Instance to a new server, please see the instructions below.
Note: When moving your instance to a new server, please ensure that the server timezone is not changed. Updating the server timezone may result in duplicate comments or unintentional artifact changes.
1. Stop all of your integrations on the old server.
2. Shut down the Hub service on the old server.
3. Install the same version of Hub on the new server.
4. Copy the C:\ProgramData\Tasktop
directory from the old server to the new server.
Note: This is the default location of the Hub program data directory. If you originally installed it to a different location, use that location.
5. Edit the C:\ProgramData\Tasktop\db\tasktop-db.json
file, as shown below:
{ "url": "jdbc:sqlserver://your-database-location;databasename=yourdatabasename", "username": "yourusername", "password": "yourpassword" }
6. Save the tasktop-db.json
file.
7. Start the Hub service on the new server.
8. Login to Hub and enter the Master Password (if you can't remember your Master Password, click here). 9. Ensure all of your integrations exist on the new Hub instance.
10. Restart all of your integrations.
Note: If using \ or " characters when setting a password, both characters should be escaped.
1. Stop all of your integrations on the old server.
2. Shut down the Hub service on the old server.
3. Copy the Hub installation directory from the old server to the new server.
Note: This is the location where you unzipped the Hub installer package.
4. Edit the <installation directory>\db\tasktop-db.json
file to add the password as shown below:
{ "url": "jdbc:sqlserver://your-database-location;databasename=yourdatabasename", "username": "yourusername", "password": "yourpassword" }
5. Save the tasktop-db.json
file.
6. Start the Hub service on the new server.
7. Login to Hub and enter the Master Password (if you can't remember your Master Password, click here). 8. Ensure all of your integrations exist on the new Hub instance.
9. Restart all of your integrations.
Note: If using \ or " characters when setting a password, both characters should be escaped.