Enterprise Search : Migrating indexing from one TREX to Another?

[Former Member]

Hi All,

We are facing a dilemma in our production ECC system with Enterprise Search configuration active on the server using a TREX backend. We have a lot of search connectors.

We now have a new box for TREX which needs to be used. There are a lot of search connectors and indexing active. Is there any way to directly "Migrate" the configuration with all indexes directly to another TREX. Because if we delete the search connectors and reindex, it takes long here and it would mean a very big outage of productive Enterprise search scenario. We want to avoid that.

Warm Regards,

Ajay Kalra

[former_member217429]

Hi Ajay,

you can export/import the indexes as mentioned by S Sriram. However when you going to start with this procedure you need to suspend all indexing jobs in the ECC. As soon as the indexes will be
imported on the new TREX  you need to switch the application for using this new instance and re-activate the indexing jobs again.

Best regards,
Mikhail

[Former Member]

Thanks Mikhail and Sriram,

But still confused on how to switch. We have built the TREX host new. A new RFC is created to the same. We can export and import the indexes at any time.

To switch ECC to switch to use this RFC instead of the one pointing to older host, we have to run report "ESH_ADM_SET_TREX_DESTINATION". But the same report won't switch the RFC unless there are search connectors in the system. If we delete the same connectors, it wont help even if we export and import the indexes from one to another as search connectors will be recreated new and prepared and have to be reindexed.

If you have more ideas, it would be great help.

Warm Regards,

Ajay Kalra

[Sriram2009]

Hi Ajay

On your ECC system In SM59 you may have two different RFC's for Trex search engine(Old and new host). Normally in our environment(we are using the Trex for SAP DBM) we use to change the RFC in transaction code SES_ADMIN(For this you have open the cross client it will create the local transport) or from development we use to create the change reqest to PRD.

Could you refer the SAP KBA for change the RFC's

1744709 - How to change RFC-destination to TREX

BR

SS

[Former Member]

HI Sriram,

That Note is reffered already. We follow the same process. The note highlights the same thing, that search connectors will have to be deleted first before RFC can be switched using report "ESH_ADM_SET_TREX_DESTINATION".

If search connectors are deleted in ESH_COCKPIT,  they will have to be recreated and reindexed completely once again regardless of previous indexes backup.

Warm Regards,

Ajay Kalra

[Sriram2009]

Hi Ajay

I think once your are switch the new RFC by using ESH_ADM_SET_TREX_DESTINATION,

in palace of rebuild the index just do the restore in the Trex system by using the python script

BR

SS

[former_member217429]

Hi Ajay,

you can do the following:
1) Export the indexes from the old TREX instance
2) Suspend indexing jobs on the application side
3) Stop old TREX instance
4) Remove the RFC Destination for TREX in the tc. SM59
5) Import the indexes on the new TREX instance
6) Create RFC destination using the TREXAdminTool on the new TREX with the same name as the old one
7) Activate real time indexing jobs.

Best regards,
Mikhail

[Former Member]

Thanks Mikhail!

This looks to be the best possible way. I will Try this only. It seems the only way.

[Sriram2009]

Hi Ajay

Just do the backup of exiting business index's and install the new Trex server along with same ECC system configuration and then do the restore the business index to new system, for backup /restore you can refer the SAP Note 975965 - TREX 7.0/7.1: Data backup (online) and recovery

BR

SS