Installing function "800xA History" to replace "IM History" in an existing 800xA 6.0.3/2
I'm about to install the function "800xA History" in an existing running 800xA 6.0.3/2 system.
2 new servers will be added for 800xA History dual logs and all trend logs will be redirected
from the existing "IM History" to the new "800xA History" function. Old History data doesn't
need to be migrated.
Could this be done without running into problem?
How can the function "IM History" be uninstalled/removed/disabled to not use license options
as the IM History licenses will be remove and mapped to 800xA History licenses?
/Johnny
2 new servers will be added for 800xA History dual logs and all trend logs will be redirected
from the existing "IM History" to the new "800xA History" function. Old History data doesn't
need to be migrated.
Could this be done without running into problem?
How can the function "IM History" be uninstalled/removed/disabled to not use license options
as the IM History licenses will be remove and mapped to 800xA History licenses?
/Johnny
Asked 2 months ago
Voted best answer
1
800xA History installation can be done in an running 800xA system and there won't be any issues.
From the migration perspective, below are the few point you may have to consider.
- There is no seamless migration of logs from IM to 800xA History. You have to recreate all new log templates and log configurations either manually or using BDM.
- If the trends are configured with logname as "Seamless' then it will automatically take the data from the newly created 800xA History log configuration when the IM log is deleted. Otherwise you have to reconfigure the trends with 800xA History logs.
Regards
Sethu
From the migration perspective, below are the few point you may have to consider.
- There is no seamless migration of logs from IM to 800xA History. You have to recreate all new log templates and log configurations either manually or using BDM.
- If the trends are configured with logname as "Seamless' then it will automatically take the data from the newly created 800xA History log configuration when the IM log is deleted. Otherwise you have to reconfigure the trends with 800xA History logs.
Regards
Sethu
Answered 2 months ago
Answers
1
There are a number of considerations to make with the change to 800xA History 6 on a 6.0.3-2 system.
- Be aware that adding two 800xA History Servers is considered the "High Availability" option. The second History Server will be updated from the Main 800xA History Server through a separate network connection that is only between these two nodes,CCN, see below image.
- There is also a separate network required between the History Servers and the DCN Nodes for the NLB function, see below image.
- The 800xA History Tag logging is done through a separate Log Template than was used for IM History Logs. This will have to be added to the Library Structure. Avoid utilizing the Object Type Structure to implement 800xA History Log Configuration Aspects. Utilize the methods identified in the 800xA History Manuals.
- The IM node can certainly be removed from the 800xA System, suggested to be after the 800xA History Server installation is complete. This will require that the IM Log Configuration Aspects, and Log Template Aspects be removed, which is best done while the IM is still part of the 800xA System.
- With this version of 800xA History, it is suggested/required that the History Server Nodes be part of the 800xA C/S Network since they will be added and updated through the SCC tool.
- Care should be taken when installing the 800xA History DCN software that if it is embedded into existing CS nodes, that there is ample memory, disk space, etc., and that the CPU will not become overloaded.
These are some of the points that should be taken into consideration. The 800xA History documentation can provide you with more details.
As a note, there is an Application available, not as part of the 800xA History Product, that can migrate the IM History DATA into 800xA History Tags/Logs should that be desired. Contact your local L3 support for details on this.
Regards,
Geof Ledin
- Be aware that adding two 800xA History Servers is considered the "High Availability" option. The second History Server will be updated from the Main 800xA History Server through a separate network connection that is only between these two nodes,CCN, see below image.
- There is also a separate network required between the History Servers and the DCN Nodes for the NLB function, see below image.
- The 800xA History Tag logging is done through a separate Log Template than was used for IM History Logs. This will have to be added to the Library Structure. Avoid utilizing the Object Type Structure to implement 800xA History Log Configuration Aspects. Utilize the methods identified in the 800xA History Manuals.
- The IM node can certainly be removed from the 800xA System, suggested to be after the 800xA History Server installation is complete. This will require that the IM Log Configuration Aspects, and Log Template Aspects be removed, which is best done while the IM is still part of the 800xA System.
- With this version of 800xA History, it is suggested/required that the History Server Nodes be part of the 800xA C/S Network since they will be added and updated through the SCC tool.
- Care should be taken when installing the 800xA History DCN software that if it is embedded into existing CS nodes, that there is ample memory, disk space, etc., and that the CPU will not become overloaded.
These are some of the points that should be taken into consideration. The 800xA History documentation can provide you with more details.
As a note, there is an Application available, not as part of the 800xA History Product, that can migrate the IM History DATA into 800xA History Tags/Logs should that be desired. Contact your local L3 support for details on this.
Regards,
Geof Ledin
Add new comment