This content has been marked as final. Show 5 replies
Think I got it... copied the SDMCFG.INI file from the old server to the new server and copied over the SBDATA folder. At least the data is there, now to edit the client file to connect to MEE.
Hello. It is work now? You have old DB ID on new server?
no, he moved the software to a new physical box by copying it - effectively it's the same DBServer running on new hardware.
Sorry about that, yes I copied over the SBDATA folder over from my old server to my new server, and copied the INI file as well. I had an issue since the old server name was listed - I deleted it within MEE, and created a new server, which created a new server key. Then, I copied/pasted that server key into the SDMCFG.INI file in order for the clients to connect. The SDMCFG.INI file on the clients will get updated to connect to the new server.
I couldn't create a new database on the new server - I couldn't find a way for the production data to use a new database license file. Therefore I used the prod license file and prod data on the new server.
If I was just upgrading the hardware and keeping the same name of the server, I don't
think it would have been this involved. But I am going to a new server and new server name as well. I am also using a DNS alias to point the clients to the new server as well during the cutover period.
If anyone knows of an easier way, I am more than willing to listen.
You just needed to copy everything (the whole EEM folder) to the new box, rename and reconfigure the existing server entry in EEM, then right-click it and do "add to databases", then it would have been listed for new install sets.
If you wanted to change the client connection details, you just needed to change the dns name in their sdmcfg.ini - but as you're using DNS routing even that was not required.