Skip to main content

We've Moved!

Product Documentation has moved to docs.hitachivantara.com
Hitachi Vantara Knowledge

Migrating the Analyzer server from Windows to Linux

Support for Analyzer server version 10.1.1 for Windows has ended. To use version 10.2.0 or a later of the Analyzer server, you must first temporarily migrate the Analyzer server to Analyzer server version 10.1.1 for Linux. This topic describes how to migrate the Analyzer server that runs on a Windows host to a Linux host.

Perform the following tasks in order:

  1. Upgrade the Analyzer server to version 10.1.1.
  2. Migrate data from Windows to Linux.
  3. Uninstall the Analyzer server from the Windows host.
  4. Upgrade the Analyzer server.

Upgrading the Analyzer server to version 10.1.1

You must upgrade the Analyzer server on the Windows host to version 10.1.1 before migrating your data.

Procedure

  1. Log on to the host where the Analyzer server is installed as Administrator.

  2. Stop any security monitoring software, antivirus software, and process monitoring software.

  3. Run ANALYTICS.msi on the installation media to start the Analyzer server installer. Follow the on-screen prompts and specify the required information.

    You can specify, as an option, whether to back up the data before performing the upgrade (best practice).

    This option is yes by default.

Next steps

Migrating data from Windows to Linux

The procedure for migrating data depends on the server configuration. Check which procedure matches your configuration, and then perform the procedure.

Migrating when Analyzer is not linked to Ops Center Automator

You must revise some of data that was backed up on the Windows host to match the Linux environment, and then restore the data to the Linux host.

Before you begin

  • You have Administrator permissions for the Windows host and root permissions for the Linux host.
  • A new installation of Analyzer server version 10.1.1 was installed on the migration-destination host.
  • The versions of the Analyzer server on the migration-source and migration-destination hosts are both 10.1.1.
  • The host name and IP address of the migration-destination host does not need to match those of the migration-source host.

Procedure

  1. On the Windows host, perform the following backup procedure:

    1. Run the hcmds64srv command to stop all services.

      hcmds64srv /stop 
    2. Run the backupsystem command to back up information about the Analyzer server settings.

      backupsystem /dir output-directory /type Analytics
    3. Run the hcmds64dbtrans command to back up user information.

      hcmds64dbtrans /export /workpath path-of-the-work-folder /file path-of-the-export-file /auto
    4. Manually back up the user-created command that is run by using Execute Action. You can skip this step if no command was created.

      This command is stored in SE.cmd.template.cmdName.string in the following definition file, which was created as an option:

      installation-destination-folder-of-the-Analyzer-server\Analytics\conf\template\command\command-definition-file-of-Execute-Action

    5. Manually back up the user-created command that is run as an event action. You can skip this step if no command was created.

      This command is stored in EventAction.cmd in the following event action definition file:

      installation-destination-folder-of-the-Analyzer-server\Analytics\conf\EventAction.properties

  2. Transfer the information about the Analyzer server settings (information that was backed up in the previous step) from the Windows host to the Linux host.

  3. On the Linux host, revise the backup data to match the Linux environment.

    1. For Analytics_Install_path of backupInfo, specify the Analyzer server installation directory on the restoration-destination host. Change the linefeed code to LF, and then save the file.

    2. Delete the following Common Services setup files. You can skip this step if you are not using Common Services:

      • application_service.json
      • opscenter-auth-client-conf.json
      • opscenter-auth-conf.json
    3. Delete all files with a .jar extension.

    4. Delete the Analyzer detail view server connection definition file (hdcaAccessSetting.conf).

    5. Decompress the following ZIP files, change the linefeed codes to LF, and then compress the files again:

      • ZIP files in the Analytics/data/database/perfEvent directory
      • ZIP files in the Analytics/data/database/systemEvent directory

      The following shows an example of running the command:

      cd path-of-the-ZIP-file
      find . -name "*.zip" -exec sh -c "unzip -q {} && sed -i 's/\r//g' *.json && zip -q -m {} '*.json'" \;

      For path-of-the-ZIP-file, specify Analytics/data/database/perfEvent/ or Analytics/data/database/systemEvent/.

    6. Change the linefeed codes to LF in the following files:

      • All files in the Analytics/data/database/TnmAgentInstance directory
      • All files in the Analytics/data/database/thresholdProfileState directory
      • All files in the Analytics/data/database/prediction/report directory
      • All files in the Analytics/data/database/prediction/history directory
      • All files in the Analytics/data/database/prediction/profile directory
      • All files in the Analytics/data/database/ResourceDiscoveredTime directory
      • The Analytics/conf/system/user_info.properties file
    7. Modify SE.cmd.template.cmdName.string and SE.cmd.template.cmdArgs.string in the following command template file so that they can be used on the migration-destination host. You can skip this step if the command template file is not configured on the migration-source host.

      Analytics/conf/template/command/command-template-file

      The following is an example.

      SE.cmd.template.cmdName.string=/root/scheduledTaskA.sh
      SE.cmd.template.cmdArgs.string=%ANALYTICS_RESOURCENAME%/tmp
    8. Modify the user-created command that is run by using Execute Action so that it can be used on the migration-destination host. You can skip this step if no command was created.

      For example, convert the file that was written in BAT format in Windows into a shell script.

    9. Modify EventAction.cmd in the following event action definition file so that it can be used on the migration-destination host. You can skip this step if the definition file is not configured on the migration-source host.

      Analytics/conf/EventAction.properties

      The following is an example.

      EventAction.cmd=/root/sample/EventActionSample.sh
    10. Modify the user-created command that is run as an event action so that it can be used on the migration-destination host. You can skip this step if no command was created.

      For example, convert the file that was written in BAT format in Windows into a shell script.

    11. Copy the Linux-specific files to the backup directory.

      cp Analyzer-server-installation-directory/conf/template/command/Built-in/CollectGranularData* output-directory/Analytics/conf/template/command/Built-in/ 
  4. On the Linux host, perform the following restore procedure:

    1. Run the hcmds64srv command to stop all services.

      hcmds64srv -stop
    2. Run the hcmds64dbsrv command to start only the database.

      hcmds64dbsrv -start
    3. Run the hcmds64dbtrans command to restore the user information.

      hcmds64dbtrans -import -type Analytics -workpath path-of-the-work-directory -file path-of-the-import-file
    4. Run the restoresystem command to restore information about the Analyzer server settings.

      restoresystem -dir backup-directory -type Analytics -auto
    5. Revise the following definition files on the migration-destination host based on the content that was changed on the migration-source host. If you already specified settings on the migration-destination host, this step is unnecessary.

      • Security definition file

        Common-component-installation-directory/conf/sec/security.conf

      • Configuration file that sets the port number and the host name

        Common-component-installation-directory/uCPSB/httpsd/conf/user_httpsd.conf

        Note: For details on how to edit the user_httpsd.conf file, see Enabling SSL communication for Analyzer server.

    6. Set up a connection with the Analyzer detail view server. For details, see Setting up a connection with Analyzer detail view server.

    7. If the Analyzer server on the Windows host was using Common Services, reconfigure the user information by completing the following steps:

      1. Registering Ops Center Analyzer in Ops Center Common Services.
      2. From Inventory tab > Products window of the Ops Center Portal, deleting the Analyzer server on the Windows host.
      3. Assigning Analyzer permissions to Ops Center user groups.
      Tip

      After the migration is complete, if you cannot log in to the Analyzer server, restart the server because the new authentication information might not have been applied.

Next steps

Be sure to uninstall the Analyzer server on the migration-source host. You cannot configure multiple instances of Analyzer to reference the same Analyzer detail view server; this configuration is not supported. For details, see Removing Ops Center Analyzer server from a Windows host.

Migrating when Analyzer is linked to Ops Center Automator (on the same host)

You must revise some of data that is backed up on the Windows host so that it matches the Linux environment, and then restore the data to the Linux host. After migrating the data, continue using Automator and Common Component on the Windows host, and the Analyzer server on the Linux host. Configure settings so that Automator is used as the primary server, and the Analyzer server is used as the secondary server.

Before you begin

  • You have Administrator permissions for the Windows host and root permissions for the Linux host.
  • A new installation of Analyzer server version 10.1.1 was installed on the migration-destination host.
  • The versions of the Analyzer server on the migration-source and migration-destination hosts are both 10.1.1.
  • The host name and IP address of the migration-destination host does not need to match those of the migration-source host.

Procedure

  1. On the Windows host, perform the following backup procedure:

    1. Run the hcmds64srv command to stop all services.

      hcmds64srv /stop 
    2. Run the backupsystem command to back up information about the Analyzer server settings.

      backupsystem /dir output-directory /type Analytics
    3. Manually back up the user-created command that is run by using Execute Action. You can skip this step if no command was created.

      This command is stored in SE.cmd.template.cmdName.string in the following definition file, which was created as an option:

      installation-destination-folder-of-the-Analyzer-server\Analytics\conf\template\command\command-definition-file-of-Execute-Action

    4. Manually back up the user-created command that is run as an event action. You can skip this step if no command was created.

      This command is stored in EventAction.cmd in the following event action definition file:

      installation-destination-folder-of-the-Analyzer-server\Analytics\conf\EventAction.properties

  2. Transfer the information about the Analyzer server settings (information that was backed up in the previous step) from the Windows host to the Linux host.

  3. On the Linux host, revise the backup data to match the Linux environment.

    1. For Analytics_Install_path of backupInfo, specify the Analyzer server installation directory on the restoration-destination host. Change the linefeed code to LF, and then save the file.

    2. Delete the following Common Services setup files. You can skip this step if you are not using Common Services:

      • application_service.json
      • opscenter-auth-client-conf.json
      • opscenter-auth-conf.json
    3. Delete all files with a .jar extension.

    4. Delete the Analyzer detail view server connection definition file (hdcaAccessSetting.conf).

    5. Decompress the following ZIP files, change the linefeed codes to LF, and then compress the files again:

      • ZIP files in the Analytics/data/database/perfEvent directory
      • ZIP files in the Analytics/data/database/systemEvent directory

      The following shows an example of running the command:

      cd path-of-the-ZIP-file
      find . -name "*.zip" -exec sh -c "unzip -q {} && sed -i 's/\r//g' *.json && zip -q -m {} '*.json'" \;

      For path-of-the-ZIP-file, specify Analytics/data/database/perfEvent/ or Analytics/data/database/systemEvent/.

    6. Change the linefeed codes to LF in the following files:

      • All files in the Analytics/data/database/TnmAgentInstance directory
      • All files in the Analytics/data/database/thresholdProfileState directory
      • All files in the Analytics/data/database/prediction/report directory
      • All files in the Analytics/data/database/prediction/history directory
      • All files in the Analytics/data/database/prediction/profile directory
      • All files in the Analytics/data/database/ResourceDiscoveredTime directory
      • The Analytics/conf/system/user_info.properties file
    7. Modify SE.cmd.template.cmdName.string and SE.cmd.template.cmdArgs.string in the following command template file so that they can be used on the migration-destination host. You can skip this step if the command template file is not configured on the migration-source host.

      Analytics/conf/template/command/command-template-file

      The following is an example.

      SE.cmd.template.cmdName.string=/root/scheduledTaskA.sh
      SE.cmd.template.cmdArgs.string=%ANALYTICS_RESOURCENAME%/tmp
    8. Modify the user-created command that is run by using Execute Action so that it can be used on the migration-destination host. You can skip this step if no command was created.

      For example, convert the file that was written in BAT format in Windows into a shell script.

    9. Modify EventAction.cmd in the following event action definition file so that it can be used on the migration-destination host. You can skip this step if the definition file is not configured on the migration-source host.

      Analytics/conf/EventAction.properties

      The following is an example.

      EventAction.cmd=/root/sample/EventActionSample.sh
    10. Modify the user-created command that is run as an event action so that it can be used on the migration-destination host. You can skip this step if no command was created.

      For example, convert the file that was written in BAT format in Windows into a shell script.

    11. Copy the Linux-specific files to the backup directory.

      cp Analyzer-server-installation-directory/conf/template/command/Built-in/CollectGranularData* output-directory/Analytics/conf/template/command/Built-in/ 
  4. On the Linux host, perform the following restore procedure:

    1. Run the hcmds64prmset command to change the Common component settings.

      hcmds64prmset -host host-name-or-IP-address-of-the-primary-server {-port port-number-of-the-primary-server-(non-SSL-communication) | -sslport port-number-of-the-primary-server-(SSL-communication)}
      NoteAs information about the primary server, specify the host name or the IP address, and the port number for accessing the UI.
    2. Run the hcmds64srv command to stop all services.

      hcmds64srv -stop
    3. Run the restoresystem command to restore information about the Analyzer server settings.

      restoresystem -dir backup-directory -type Analytics -auto
    4. Revise the following definition files on the migration-destination host based on the content that was changed on the migration-source host. If you already specified settings on the migration-destination host, this step is unnecessary.

      • Security definition file

        Common-component-installation-directory/conf/sec/security.conf

      • Configuration file that sets the port number and the host name

        Common-component-installation-directory/uCPSB/httpsd/conf/user_httpsd.conf

        Note: For details on how to edit the user_httpsd.conf file, see Enabling SSL communication for Analyzer server.

    5. Set up a connection with the Analyzer detail view server. For details, see Setting up a connection with Analyzer detail view server.

    6. If the Analyzer server on the Windows host was using Common Services, reconfigure the user information by completing the following steps:

      1. Registering Ops Center Analyzer in Ops Center Common Services.
      2. From Inventory tab > Products window of the Ops Center Portal, deleting the Analyzer server on the Windows host.
      3. Assigning Analyzer permissions to Ops Center user groups.
      Tip

      After the migration is complete, if you cannot log in to the Analyzer server, restart the server because the new authentication information might not have been applied.

Next steps

Be sure to uninstall the Analyzer server on the migration-source host. You cannot configure multiple instances of Analyzer to reference the same Analyzer detail view server; this configuration is not supported. For details, see Removing Ops Center Analyzer server from a Windows host.

Migrating when Analyzer is linked to Ops Center Automator (on another host) that is not linked to Device Manager

You must revise some of data that was backed up on the Windows host to match the Linux environment, and then restore the data to the Linux host. After migration, configure Automator to be the primary server and the Analyzer server to be the secondary server.

NoteIf the Analyzer server is configured as secondary server, your next step is Migrating when Analyzer is linked to Ops Center Automator (on another host) that is linked to Device Manager.

Before you begin

  • You have Administrator permissions for the Windows host and root permissions for the Linux host.
  • A new installation of Analyzer server version 10.1.1 was installed on the migration-destination host.
  • The versions of the Analyzer server on the migration-source and migration-destination hosts are both 10.1.1.
  • The host name and IP address of the migration-destination host does not need to match those of the migration-source host.

Procedure

  1. On the Windows host, perform the following backup procedure:

    1. Run the hcmds64srv command to stop all services.

      hcmds64srv /stop 
    2. Run the backupsystem command to back up information about the Analyzer server settings.

      backupsystem /dir output-directory /type Analytics
    3. Run the hcmds64dbtrans command to back up user information.

      hcmds64dbtrans /export /workpath path-of-the-work-folder /file path-of-the-export-file /auto
    4. Manually back up the user-created command that is run by using Execute Action. You can skip this step if no command was created.

      This command is stored in SE.cmd.template.cmdName.string in the following definition file, which was created as an option:

      installation-destination-folder-of-the-Analyzer-server\Analytics\conf\template\command\command-definition-file-of-Execute-Action

    5. Manually back up the user-created command that is run as an event action. You can skip this step if no command was created.

      This command is stored in EventAction.cmd in the following event action definition file:

      installation-destination-folder-of-the-Analyzer-server\Analytics\conf\EventAction.properties

  2. Migrate the user information to the Common component of Automator. If Automator is running on Windows, perform the following procedure but replace - with / immediately before each argument.

    1. Run the hcmds64srv command to stop all services.

      hcmds64srv -stop
    2. Run the hcmds64prmset command to set the Common component of Automator as the primary server.

      hcmds64prmset -setprimary
    3. Run the hcmds64dbconvert command to migrate the user information that was backed up.

      hcmds64dbconvert -auth -workpath path-of-the-work-folder -file path-of-the-import-file -auto
    4. Run the hcmds64srv command to start the services.

      hcmds64srv -start
  3. Send the settings information of the Analyzer server that is backed up in the previous step from the Windows environment to the Linux environment.

  4. On the Linux host, revise the backup data to match the Linux environment.

    1. For Analytics_Install_path of backupInfo, specify the Analyzer server installation directory on the restoration-destination host. Change the linefeed code to LF, and then save the file.

    2. Delete the following Common Services setup files. You can skip this step if you are not using Common Services:

      • application_service.json
      • opscenter-auth-client-conf.json
      • opscenter-auth-conf.json
    3. Delete all files with a .jar extension.

    4. Delete the Analyzer detail view server connection definition file (hdcaAccessSetting.conf).

    5. Decompress the following ZIP files, change the linefeed codes to LF, and then compress the files again:

      • ZIP files in the Analytics/data/database/perfEvent directory
      • ZIP files in the Analytics/data/database/systemEvent directory

      The following shows an example of running the command:

      cd path-of-the-ZIP-file
      find . -name "*.zip" -exec sh -c "unzip -q {} && sed -i 's/\r//g' *.json && zip -q -m {} '*.json'" \;

      For path-of-the-ZIP-file, specify Analytics/data/database/perfEvent/ or Analytics/data/database/systemEvent/.

    6. Change the linefeed codes to LF in the following files:

      • All files in the Analytics/data/database/TnmAgentInstance directory
      • All files in the Analytics/data/database/thresholdProfileState directory
      • All files in the Analytics/data/database/prediction/report directory
      • All files in the Analytics/data/database/prediction/history directory
      • All files in the Analytics/data/database/prediction/profile directory
      • All files in the Analytics/data/database/ResourceDiscoveredTime directory
      • The Analytics/conf/system/user_info.properties file
    7. Modify SE.cmd.template.cmdName.string and SE.cmd.template.cmdArgs.string in the following command template file so that they can be used on the migration-destination host. You can skip this step if the command template file is not configured on the migration-source host.

      Analytics/conf/template/command/command-template-file

      The following is an example.

      SE.cmd.template.cmdName.string=/root/scheduledTaskA.sh
      SE.cmd.template.cmdArgs.string=%ANALYTICS_RESOURCENAME%/tmp
    8. Modify the user-created command that is run by using Execute Action so that it can be used on the migration-destination host. You can skip this step if no command was created.

      For example, convert the file that was written in BAT format in Windows into a shell script.

    9. Modify EventAction.cmd in the following event action definition file so that it can be used on the migration-destination host. You can skip this step if the definition file is not configured on the migration-source host.

      Analytics/conf/EventAction.properties

      The following is an example.

      EventAction.cmd=/root/sample/EventActionSample.sh
    10. Modify the user-created command that is run as an event action so that it can be used on the migration-destination host. You can skip this step if no command was created.

      For example, convert the file that was written in BAT format in Windows into a shell script.

    11. Copy the Linux-specific files to the backup directory.

      cp Analyzer-server-installation-directory/conf/template/command/Built-in/CollectGranularData* output-directory/Analytics/conf/template/command/Built-in/ 
  5. On the Linux host, perform the following restore procedure:

    1. Run the hcmds64prmset command to change the Common component settings.

      hcmds64prmset -host host-name-or-IP-address-of-the-primary-server {-port port-number-of-the-primary-server-(non-SSL-communication) | -sslport port-number-of-the-primary-server-(SSL-communication)}
      NoteYou can check information about the primary server by running the following command on the migration-source host.
      hcmds64prmset /print
    2. Run the hcmds64srv command to stop all services.

      hcmds64srv -stop
    3. Run the restoresystem command to restore information about the Analyzer server settings.

      restoresystem -dir backup-directory -type Analytics -auto
    4. Revise the following definition files on the migration-destination host based on the content that was changed on the migration-source host. If you already specified settings on the migration-destination host, this step is unnecessary.

      • Security definition file

        Common-component-installation-directory/conf/sec/security.conf

      • Configuration file that sets the port number and the host name

        Common-component-installation-directory/uCPSB/httpsd/conf/user_httpsd.conf

        Note: For details on how to edit the user_httpsd.conf file, see Enabling SSL communication for Analyzer server.

    5. Set up a connection with the Analyzer detail view server. For details, see Setting up a connection with Analyzer detail view server.

    6. If the Analyzer server on the Windows host was using Common Services, reconfigure the user information by completing the following steps:

      1. Registering Ops Center Analyzer in Ops Center Common Services.
      2. From Inventory tab > Products window of the Ops Center Portal, deleting the Analyzer server on the Windows host.
      3. Assigning Analyzer permissions to Ops Center user groups.
      Tip

      After the migration is complete, if you cannot log in to the Analyzer server, restart the server because the new authentication information might not have been applied.

Next steps

Be sure to uninstall the Analyzer server on the migration-source host. You cannot configure multiple instances of Analyzer to reference the same Analyzer detail view server; this configuration is not supported. For details, see Removing Ops Center Analyzer server from a Windows host.

Migrating when Analyzer is linked to Ops Center Automator (on another host) that is linked to Device Manager

You must revise some of data that was backed up on the Windows host to match the Linux environment, and then restore the data to the Linux host.

Before you begin

  • You have Administrator permissions for the Windows host and root permissions for the Linux host.
  • A new installation of Analyzer server version 10.1.1 was installed on the migration-destination host.
  • The versions of the Analyzer server on the migration-source and migration-destination hosts are both 10.1.1.
  • The host name and IP address of the migration-destination host does not need to match those of the migration-source host.

Procedure

  1. On the Windows host, perform the following backup procedure:

    1. Run the hcmds64srv command to stop all services.

      hcmds64srv /stop 
    2. Run the backupsystem command to back up information about the Analyzer server settings.

      backupsystem /dir output-directory /type Analytics
    3. Manually back up the user-created command that is run by using Execute Action. You can skip this step if no command was created.

      This command is stored in SE.cmd.template.cmdName.string in the following definition file, which was created as an option:

      installation-destination-folder-of-the-Analyzer-server\Analytics\conf\template\command\command-definition-file-of-Execute-Action

    4. Manually back up the user-created command that is run as an event action. You can skip this step if no command was created.

      This command is stored in EventAction.cmd in the following event action definition file:

      installation-destination-folder-of-the-Analyzer-server\Analytics\conf\EventAction.properties

  2. Transfer the information about the Analyzer server settings (information that was backed up in the previous step) from the Windows host to the Linux host.

  3. On the Linux host, revise the backup data to match the Linux environment.

    1. For Analytics_Install_path of backupInfo, specify the Analyzer server installation directory on the restoration-destination host. Change the linefeed code to LF, and then save the file.

    2. Delete the following Common Services setup files. You can skip this step if you are not using Common Services:

      • application_service.json
      • opscenter-auth-client-conf.json
      • opscenter-auth-conf.json
    3. Delete all files with a .jar extension.

    4. Delete the Analyzer detail view server connection definition file (hdcaAccessSetting.conf).

    5. Decompress the following ZIP files, change the linefeed codes to LF, and then compress the files again:

      • ZIP files in the Analytics/data/database/perfEvent directory
      • ZIP files in the Analytics/data/database/systemEvent directory

      The following shows an example of running the command:

      cd path-of-the-ZIP-file
      find . -name "*.zip" -exec sh -c "unzip -q {} && sed -i 's/\r//g' *.json && zip -q -m {} '*.json'" \;

      For path-of-the-ZIP-file, specify Analytics/data/database/perfEvent/ or Analytics/data/database/systemEvent/.

    6. Change the linefeed codes to LF in the following files:

      • All files in the Analytics/data/database/TnmAgentInstance directory
      • All files in the Analytics/data/database/thresholdProfileState directory
      • All files in the Analytics/data/database/prediction/report directory
      • All files in the Analytics/data/database/prediction/history directory
      • All files in the Analytics/data/database/prediction/profile directory
      • All files in the Analytics/data/database/ResourceDiscoveredTime directory
      • The Analytics/conf/system/user_info.properties file
    7. Modify SE.cmd.template.cmdName.string and SE.cmd.template.cmdArgs.string in the following command template file so that they can be used on the migration-destination host. You can skip this step if the command template file is not configured on the migration-source host.

      Analytics/conf/template/command/command-template-file

      The following is an example.

      SE.cmd.template.cmdName.string=/root/scheduledTaskA.sh
      SE.cmd.template.cmdArgs.string=%ANALYTICS_RESOURCENAME%/tmp
    8. Modify the user-created command that is run by using Execute Action so that it can be used on the migration-destination host. You can skip this step if no command was created.

      For example, convert the file that was written in BAT format in Windows into a shell script.

    9. Modify EventAction.cmd in the following event action definition file so that it can be used on the migration-destination host. You can skip this step if the definition file is not configured on the migration-source host.

      Analytics/conf/EventAction.properties

      The following is an example.

      EventAction.cmd=/root/sample/EventActionSample.sh
    10. Modify the user-created command that is run as an event action so that it can be used on the migration-destination host. You can skip this step if no command was created.

      For example, convert the file that was written in BAT format in Windows into a shell script.

    11. Copy the Linux-specific files to the backup directory.

      cp Analyzer-server-installation-directory/conf/template/command/Built-in/CollectGranularData* output-directory/Analytics/conf/template/command/Built-in/ 
  4. On the Linux host, perform the following restore procedure:

    1. Run the hcmds64prmset command to change the Common component settings.

      hcmds64prmset -host host-name-or-IP-address-of-the-primary-server {-port port-number-of-the-primary-server-(non-SSL-communication) | -sslport port-number-of-the-primary-server-(SSL-communication)}
      NoteYou can check information about the primary server by running the following command.
      hcmds64prmset -print
    2. Run the hcmds64srv command to stop all services.

      hcmds64srv -stop
    3. Run the restoresystem command to restore information about the Analyzer server settings.

      restoresystem -dir backup-directory -type Analytics -auto
    4. Revise the following definition files on the migration-destination host based on the content that was changed on the migration-source host. If you already specified settings on the migration-destination host, this step is unnecessary.

      • Security definition file

        Common-component-installation-directory/conf/sec/security.conf

      • Configuration file that sets the port number and the host name

        Common-component-installation-directory/uCPSB/httpsd/conf/user_httpsd.conf

        Note: For details on how to edit the user_httpsd.conf file, see Enabling SSL communication for Analyzer server.

    5. Set up a connection with the Analyzer detail view server. For details, see Setting up a connection with Analyzer detail view server.

    6. If the Analyzer server on the Windows host was using Common Services, reconfigure the user information by completing the following steps:

      1. Registering Ops Center Analyzer in Ops Center Common Services.
      2. From Inventory tab > Products window of the Ops Center Portal, deleting the Analyzer server on the Windows host.
      3. Assigning Analyzer permissions to Ops Center user groups.
      Tip

      After the migration is complete, if you cannot log in to the Analyzer server, restart the server because the new authentication information might not have been applied.

Next steps

Be sure to uninstall the Analyzer server on the migration-source host. You cannot configure multiple instances of Analyzer to reference the same Analyzer detail view server; this configuration is not supported. For details, see Removing Ops Center Analyzer server from a Windows host.

Removing Ops Center Analyzer server from a Windows host

Remove the Analyzer server from a Windows host by setting the Startup type to Automatic or Manual and then removing it using the Windows control panel.

Procedure

  1. Log on to the Analyzer server by using a user account with the Administrator permission.

  2. Stop any security monitoring software, antivirus software, and process monitoring software.

  3. If you are using the functionality for connecting with Ops Center Automator, reset the settings of the Common component. For details, see Resetting Common component settings.

  4. Run the following command to stop the services of products that use the Common component:

    hcmds64srv /stop 
  5. Set Startup type for the Analyzer server services to Automatic or Manual.

    In a Windows environment, if the Startup type is set to Disabled, the removal process might fail because the services cannot be started.
  6. To remove Analyzer server, go to Control Panel Programs Programs and Features and select Hitachi Ops Center Analyzer, and then click Uninstall.

Next steps

The settings files remain in the installation folder. You must delete the settings files manually as necessary.

 

  • Was this article helpful?