Migrating the Smart Hub
You can migrate the existing Smart Hub that involves the following tasks:
- Installing a new Smart Hub.
- Migrating data from the existing Redis Server to the new Redis Server.
If the Smart Hub Gateway is installed, you can migrate it to the same host where the Smart Hub is migrated. For details, see migrating the Smart Hub Gateway.
Migration scenarios
The following scenarios are supported:
Scenario | Can migrate to |
---|---|
The Smart Hub is installed on a Windows or a Linux system and it uses the packaged Redis Server. | The new Smart Hub installed on a Windows or a Linux system, and migrate data to the Redis Server packaged with the new Smart Hub or an external Redis Server. |
The Smart Hub is installed on a Windows or a Linux system and it uses the external Redis Server. | The new Smart Hub installed on a Windows or a Linux system, and use the existing external Redis Server or migrate data to the Redis Server packaged with the new Smart Hub. |
To migrate the Smart Hub
Do the following:
- Install the new Smart Hub on a Windows or a Linux system. For the installation instructions, see Installing-the-Smart-Hub-and-Smart-Hub-Gateway-using-the-installation-script.
- Register the new Smart Hub in the Application Server. For details, see Configuring-the-Smart-Hub-and-Smart-Hub-Gateway.
- On the existing Smart Hub host, do the following:
- Copy the data folder from this path to the host where the new packaged or external Redis Server is installed:
<smarthub_installation_location>/data/ - Check the following certificate and key file names in the config.json file at opt/bmc/smarthub/config:
- certificateFile
- caCertificateFile
- privateKeyFile
- certificateKeyFile
- Copy these certificate and key files from the following path to the same path on the new Smart Hub host:
<smarthub_installation_location>/certs
- Copy the data folder from this path to the host where the new packaged or external Redis Server is installed:
- Update the Smart Agent configuration properties to establish Smart Agent communication with the new Smart Hub:
- Log in to the system where the RSCD Agent is installed.
- Navigate to the following path:
- (Windows) c:\windows\rsc
- (Linux) /etc/rsc
Open the smartagent.conf file and edit the following properties:
rest_api":{
"host":"<new_smarthub_host>",
"port":<new_smarthub_port>,- Save the changes.
- Restart the Smart Agent. For details, see Managing-the-Smart-Agent.
- Repeat these steps for the other targets where the RSCD and Smart Agents are installed.
- (optional) If you are using an external Redis Server, update the configuration file with the recommended values:
- Log in to the system where the Redis Server is installed.
- Navigate to the following path:
- (Windows) <installation_directory>\redis.windows.conf
- (Linux) <installation_directory>/redis.conf
Open the configuration file, and update values of the following properties:
"dbfilename":"redisdb.rdb",
"appendonly":"yes",
"appendfsync":"always",
"auto-aof-rewrite-min-size":"1gb"- Save the changes.
To migrate the Smart Hub Gateway
Do the following:
- Install the new Smart Hub Gateway on the same host where the new Smart Hub is installed.
- Copy the following data from the existing Smart Hub Gateway host to the new Smart Hub Gateway host:
- <smarthub_Gateway_installation_location>/conf/applicaton.properties
- <smarthub_Gateway_installation_location>/conf/infraId.txt
- <smarthub_Gateway_installation_location>/conf/cert/*
- Restart the new Smart Hub Gateway:
Do the following to start or stop the Smart Hub Gateway:- (Windows) Open the Windows services and start or stop the following service:
TrueSight Server Automation Smart Hub Gateway Service - (Linux) Use these systemctl commands:
- systemctl start smarthub.gateway.service
- systemctl stop smarthub.gateway.service
- (Windows) Open the Windows services and start or stop the following service:
- Register the new Smart Hub Gateway in the Application Server. For instructions, see Configuring-the-Smart-Hub-and-Smart-Hub-Gateway.