iTop Hub identifies the instances using two UUIDs: one stored in the database (in the priv_db_properties table) and one stored in the file system (in data/instance.txt.

Both UUIDs are part of the data sent from iTop to iTop Hub when using the “iTop Hub” menus inside iTop to jump to iTop Hub.

If you copy the whole iTop instance to another folder and continue to point to the same database, then iTop Hub will see the same couple of UUIDs and consider the two instances to be the same.

Also if you restore the dump of an iTop database you will get the same database_uuid and could face the same issue.

If the URLs used to access the two instances are different, iTop Hub will warn you that a problem may exists.

Here are your options :

• if you use a different database, please consider deleting the database_uuid value, and run the iTop setup again. iTop will regenerate a new UUID for you.

DELETE FROM priv_db_properties WHERE priv_db_properties.name = 'database_uuid'

• if you use different a file system, but the same database, please consider deleting the data/instance.txt file, and run the setup again. iTop will regenerate a new UUID for you

iTop Hub is designed as a DIY tool for small companies that should not need such advanced hosting design. You should consider subscribing to our professional services.

Despite this warning, if you prefer to continue using iTop hub, then you'll have to choose between having distinct data/instance.txt on each webserver in order to let iTop hub consider them as different instances or to share the same data/instance.txt to see only one instance in iTop Hub.