Hello,
I have reinstalled my Community Server to switch from DominoDirectory to LDAP directory.
In general this is working fine. Also stnamechange.cmd succeeded, contact lists are displayed - but: The chat history is gone.
I am using the same MongoDB. Also the MongoCompass indicates the chats are still in the database.
How can I link the "pre-LDAP"-chats with the newly installed/configured server ?
Environment:
Windows Server 2016
Domino 11 FP7
SametimePremium (Community Server) 11.6
SametimeProxy 11.6
Any idea appreciated.
Kind regards,
Jan
There is a new database utility in 12.01 that you need to use to migrate the chat data to LDAP format. There was not a utility in 11.6 to do this.
I assume you have access to the V12.01 code - see - https://help.hcltechsw.com/sametime/1201/admin/t_namechangeutility.html
So it is not possible to migrate chat history from a 11.6 ST server to a new 11.6 ST server?
Thank you
You will need to use the utility from 12.01 to accomplish this. We did not have a utility in 11.6.
@Anthony Payne What would be best practice for customers with 11.6 & Domino native ?
Directly jump to v12 environment with a DNS switch & before that running migration tools to get contact list & chat history in LDAP format into MongoDB ?
I wanted to go "step-by-step" (switch to LDAP then switch to V12) which now seems to be a bad choiche due to missing chat history in embedded client.
And could you clarify: I can use the database utility in V12 to connect to a v11.6 MongoDB environment to get the chat-history/reference into LDAP format ?
If the goal is to get them to 12.01 - then I would :
a) set up the new v12 server pointed to LDAP
b) create a new mongodb instance for v12 and use mongodump/restore to move the existing chat data over
c) migrate the user information using the utility to convert vpuserinfo.nsf to ldap and move it into mongodb (https://help.hcltechsw.com/sametime/12/admin/migrating_upgrading.html)
d) use the v12.01 database utility to convert the format of the chatlogging data to ldap format
(https://help.hcltechsw.com/sametime/1201/admin/t_namechangeutility.html)
e) test with a subset of users on the new system. You can use a localhost file to simulate a DNS change and validate things are working as expected and correct as neccesary.
f) if the validation with (e) is as expected - then you can move all the users over using a DNS flip. If you need more time to schedule a DNS change , then you can redo utilities during the change window.
If you don't wish to use a new mongo instance for the v12 environment, then you can, of course, use the utilities against the existing one when you are ready to do the flip.
If the goal is to only migrate v11.6 to LDAP format, then yes, you can use the 12.01 Database utility against the v11.6 data to move it to LDAP format.