Follow this procedure to maintain your existing configuration
on new hardware. Alternatively, you can remove the server from your
configuration (see procedure below) and then create a new configuration
after installing the K2 Administration Server software.
To move your existing configuration to new hardware, your
new hardware must be configured the same as the previous machine.
All drives and shares must be named the same and each server must
have the same host name and IP addresses.
To move K2 administration server software to new hardware:
- Take careful note of all aspects of your current Content Search Engine configuration. Record
all share names, host names, server ports, and IP addresses. Record
the server names and ports of all configured server services in the
K2 Dashboard, and their locations.
- If collections are stored on this machine, make a backup
copy.
- Set up your new hardware and ensure the machine host name
and IP address match your previous configuration.
- Follow the Add Additional K2 Administration Servers procedure
above to install the K2 Administration Server software on the new
machine.
- Create the services for this machine in the K2 Master Administration
Server dashboard and ensure all server services are named the same
as your previous configuration and ensure all servers created in the
Autonomy K2 Dashboard are named the same and configured for the same
ports.
You can change the ports; but if you do so,
must reboot the Content Engine servers.
The names of the search servers, index servers and brokers might not
be changed for any items referenced by an index area on the Content Engine servers.
- Restore the collections to the same Root Dir Path (as specified
in the index area properties) as before. If the collections are no
longer available, mark those collections as unavailable, and then
run a reindexing job on those collections. Otherwise copy/restore
those collections via whatever tool you used to save them.
- Modify the appropriate directory path entries in the Verity.cfg file.