Moving Basic History data from E drive to F Drive it fails using the SCC tool
The mill requires to log longer and faster for their process trends. The first step is to log the history data in a bigger drive. From 800xA SCC console, this can be done by changing the server data 2 to new location.
A few months ago, I have successfully moved the server data 2 location from original C drive to a bigger E drive. However, the E drive is still not large enough for the mill. They recently bought new extra disks, and I have been tring to move the server data 2 path again from E drive to a new F drive. The new F drive is 1.6 TG. This time, I always have an error in the middle of step 3 “Copying” during the move. Please see the screen capture below. The error message indicates to check on windows event or Applog. Do you know more specific about there to find the Applog or what windows event to check?
See attachment. When the copy fails I do notice all the history data does get copied to the new drive. But it still fails.
A few months ago, I have successfully moved the server data 2 location from original C drive to a bigger E drive. However, the E drive is still not large enough for the mill. They recently bought new extra disks, and I have been tring to move the server data 2 path again from E drive to a new F drive. The new F drive is 1.6 TG. This time, I always have an error in the middle of step 3 “Copying” during the move. Please see the screen capture below. The error message indicates to check on windows event or Applog. Do you know more specific about there to find the Applog or what windows event to check?
See attachment. When the copy fails I do notice all the history data does get copied to the new drive. But it still fails.
Asked 10 months ago
Answers
0
Apart from logging a support case I suggest:
Maintenance Stop
Copy manually
Update registry (HKLM\Software\Wow6432Node\ABB\AFW\Systems\{GUID})
Reboot
Verify
Clean old location
The ServerData vs ServerData2 setting is stored on the Service Definition aspect
”TB” sounds very large for Basic History. Be sure to not exceed performance envelope.
Maintenance Stop
Copy manually
Update registry (HKLM\Software\Wow6432Node\ABB\AFW\Systems\{GUID})
Reboot
Verify
Clean old location
The ServerData vs ServerData2 setting is stored on the Service Definition aspect
”TB” sounds very large for Basic History. Be sure to not exceed performance envelope.
Add new comment