Trends does not show after replacing Hard drive on CS1
Hi,
We have recently replaced one of the faulty hard drive on connectivity server 1 with new hard drive, from then we are not able to see Trends, I have swapped Basic history service from CS1 to CS2 and vice versa but still does not work, Basic history service is healthy in both the servers, Space available on the both the servers hard drive is same too.
all other services related to CS are working fine.
Any suggestions ?
Thanks.
We have recently replaced one of the faulty hard drive on connectivity server 1 with new hard drive, from then we are not able to see Trends, I have swapped Basic history service from CS1 to CS2 and vice versa but still does not work, Basic history service is healthy in both the servers, Space available on the both the servers hard drive is same too.
all other services related to CS are working fine.
Any suggestions ?
Thanks.
Asked 2 months ago
Answers
0
Hi!
Check the History Source aspect in your Control Network. Make sure it's connected to the correct Service Group.
BR
Check the History Source aspect in your Control Network. Make sure it's connected to the correct Service Group.
BR
Answered 2 months ago
0
What version?
How did you replace the disk? Was it C:\?
In v6, firewall exclusion is made when deploying Basic History service in SCC Configure System. Test by temporary turning off firewall.
If node was removed and readded, a stringent affinity (not including All Nodes group) may block trend clients until you have rigged affinity again.
As mentioned the History Source aspect govern Basic History’s work. Check in Log Config that you have a ”green” service group.
How did you replace the disk? Was it C:\?
In v6, firewall exclusion is made when deploying Basic History service in SCC Configure System. Test by temporary turning off firewall.
If node was removed and readded, a stringent affinity (not including All Nodes group) may block trend clients until you have rigged affinity again.
As mentioned the History Source aspect govern Basic History’s work. Check in Log Config that you have a ”green” service group.
0
Assuming your trend services were setup correctly, when you shutdown CS1 the History services should have pointed to CS2 (redundant server) and all Trend data should have shown automatically. If this is not the case CS2 History services may have been incorrectly setup and there is no data, hence the lack of trends today.
0
Step 1 ... Wait.
**IF** you correctly configured the disks and directories and restarted the history service, then the Connectivity Server will begin to Synchronize. THIS CAN TAKE A LONG TIME !
- Under each history service provider definition is a Service Provider Metrics aspect. Subscribe for Live values and check that the "Percent Synchronized" is increasing or has reached 100%. If the value is 99.999999% then the services are not synchronized yet and ~weird~ things may happen.
- If the percent synchronized is less than 100% but still increasing then relax, sit back and wait for the bang. It just needs time
- If the value is low and / or not increasing then history is not synchronizing and you haven't properly fixed the issue. Data isn't being logged properly and / or there are gaps in the trend data. Check the Disk space allocation and that restarting the History service has correctly created the 800xA History directories and empty files on the repaired connectivity server. CS1 and CS2 should have the same disk Layout, Directory layout and File Names.
**IF** you correctly configured the disks and directories and restarted the history service, then the Connectivity Server will begin to Synchronize. THIS CAN TAKE A LONG TIME !
- Under each history service provider definition is a Service Provider Metrics aspect. Subscribe for Live values and check that the "Percent Synchronized" is increasing or has reached 100%. If the value is 99.999999% then the services are not synchronized yet and ~weird~ things may happen.
- If the percent synchronized is less than 100% but still increasing then relax, sit back and wait for the bang. It just needs time
- If the value is low and / or not increasing then history is not synchronizing and you haven't properly fixed the issue. Data isn't being logged properly and / or there are gaps in the trend data. Check the Disk space allocation and that restarting the History service has correctly created the 800xA History directories and empty files on the repaired connectivity server. CS1 and CS2 should have the same disk Layout, Directory layout and File Names.
Source: Check
Add new comment