Remove "old" SAP BO server

[former_member403878]

Hi,

We have done a new SAP BO install on a new server which is intended to replace an old SAP BO server (change of Windows OS), however, now when looking at the CMC console on the NEW server, it points to the OLD server (e.g. <OLDSERVER>.AdaptiveJobServer)

How do we remove the old server from the configurations and make everything point to the new server (e.g. <NEWSERVER>.AdaptiveJobServer)

I'm guessing making <NEWSERVER> the master (but can't find where to set that) and then remove the old node...

Thanks

[Joe_Peters1]

I'm assuming what happened was that you used the existing CMS database when you set up the new server. The new installation saw that existing CMS including the old server, and assumed you were adding this new server to an existing node.

There are two approaches to doing this type of activity: simply adding a server to an existing cluster and removing the old server, or creating a new cluster and migrating the old content in.

Each approach has its benefits. Adding a new server to an existing cluster means that you keep the same CMS, file store, cluster names, and object IDs. Creating a new cluster means that you have to migrate the old content in, and you need a second location for the CMS database. But both old and new cluster can run together in parallel for a while, if needed.

By installing the software and pointing to the existing CMS, you've effectively started with the first strategy -- you've added the new server to the existing cluster. If you want to continue with that and just remove the old server's references, you have a couple of options:

1. Uninstall the software on the old server. Its records should be removed from the CMS database, and you'll no longer see its servers in the new server's CMC.
2. If you can't uninstall or the uninstall doesn't complete successfully, then you can be left with artifacts in the CMS, which result in what you're seeing - the old server in the CMC. In this case you'll need to manually remove the old server's info from the CMS, using the "delete from cms_infoobjects7" statement that you pasted above.
3. You could start over, using the steps in the backup/restore note that Omkar provided. The end result of this is two independent but otherwise mostly identical systems. It does mean copying the CMS database and filestore.
4. If the old server is still operational, you could abandon this effort and re-start using the other strategy -- uninstall (or just delete the SIA), and when creating the new SIA use a new, empty CMS database. You'll then have an empty system that you can migrate the content into.
5. Finally, you can simply just delete the old server's entries from the new server's CMC. You won't be able to delete the old node itself, and it'll still show up in "Nodes". Normally, this won't be a problem and you can just leave it like that. But I did see one instance in which an SDK application had sporadic problems connecting to a cluster that still had an old node reference. The application's logs showed that it failed trying to connect to the obsolete server. When we manually deleted the record from the CMS, the problem went away.

One thing to note is that you can't simply re-point the old server's services (ex. AJS) to the new server. They don't work like that. You have to create the servers on the new node either during installation, when creating a new SIA, or manually in the CMC.

[omkarsambare]

When you say "do you see the OLD in the new server", if I click the "Manage Servers" I can see them but in a "Stopped" state. Doing the same on the old shows them in a "Running" state.

The BO versions are the same (only the OS is changing), when you say "delete the entries of the old server", do you mean this

-> No, if you run this query this will delete all the entries new and old. The only viable option is now to delete the entries of OLD server from CMC manually. You will have to delete the server entries manually from CMC-> Servers.

If you have any support contract with SAP better to request for resource who can assist you with it.

[omkarsambare]

Do you see the OLD AJS Running in new Server ? If so you have clustered OLD and NEW Server. If the BO versions are same won'tbe much of issue but if BO versions are different you will have to start from fresh.

The best approach if the new and old BO Server versions are same is to use backup and restore method. In this you will have to delete the entries of the OLD Server refer https://launchpad.support.sap.com/#/notes/1275068.

In case you don't have much expertise on performing the steps from above document or running the queries. It would be better to engage SAP Consultant or Support team.

A quick solution to the current issue is to delete the old server entries if they are not clustered and just see the entries of OLD Server (provided the servers are in stopped state and cannot be started.)

[former_member403878]

Thanks for the response

When you say "do you see the OLD in the new server", if I click the "Manage Servers" I can see them but in a "Stopped" state. Doing the same on the old shows them in a "Running" state.

The BO versions are the same (only the OS is changing), when you say "delete the entries of the old server", do you mean this

It is a new install (and the old server will get completely removed), but uninstalling has proven to be quite a painful exercise so if it can be resolved without uninstalling, I'm keen to try

Ultimate intent is to restore from the prod server back in to dev (this install), is there a way to "reset" the cms database while ensuring the old server doesn't re-attach/make itself master/etc?