Move TEM server - New IP & DNS

Usage and Config Platform
1

(imported topic written by tnt220)

We are moving our primary and only TEM 8.2 server (and all clients) to a new location meaning that it will get new IP address, DNS and Hostname and have been looking for guides on how to best do this.

So far I only found
This
description which does mentoon some steps, but is not entirely what we are doing.

Have anybody tried this and could give some hints on what to do and be particularly attentive to.

Thanks in advance

2

(imported comment written by Tim.Rice)

As long as your License references the server by DNS name, you should be fine.

Change the DNS entry to the new IP address and flush the DNS Cache on your Relays. I created a Task to do this and scheduled it to run after the server DNS was updated. We were moving the server to the other side of campus so I had a good window of opportunity.

3

(imported comment written by tnt220)

Thanks, but the DNS name will also change so I assume I will need a new license file ?

4

(imported comment written by martinc)

If the DNS name is changing, then you will need to get a new license and set up the new environment. This will mean that you will need to leave the old environment up and start migrating endpoints to the new server. Of course you will also have to rebuild your relays to point to the new server.

Basic steps would be to:

  1. Bring up new server and a couple relays

  2. Create a fixlet in the old server that will deploy the actionsite.afxm file from the new server to an endpoint and then restart the endpoint. Then deploy this fixlet to the endpoints.

As you work through the endpoints you can move some of the relays from the old server to the new server.

Now the biggest part is moving all your content. If you have a lot of fixlets, you will have to edit those and make sure that any downloads point to your new server.

I have used that link you provided to move from one server to another and it has pretty much everything you need to do that type of migration.

This is a real big pain, so if there is any way for you to maintain the DNS name, I would strongly recommend that you do it.

Martin Carnegie

Gulf Breeze Software Partners

5

(imported comment written by Tim.Rice)

Unfortunately, yes and that will then require a new Masthead, and a rebuild of the server I believe. I don’t think you can ‘swap’ Mastheads on the servers.

If you can manage it, there is a task that will replace the masthead files on all your workstations. If you can generate the new masthead before moving, you might be able to have the existing TEM setup swap the mastheads before you shutdown the workstations and move anything. It might save you some legwork. I’ve not had a lot of luck with Relays migrating this way (I think IBM created a task just for migrating Relays, but I’ve not used it yet), but clients have not given me much trouble.

6

(imported comment written by tnt220)

Thanks to you both for your valuable input. It seems that installing a new server and migrating will be the best and safest option.

Thanks