Unsolved
This post is more than 5 years old
2 Posts
0
877
May 5th, 2010 15:00
Extended Drive Issues After License Expiry
The license for one of our DX servers recently expired. As it would no longer move data to Centera, the extended drive filled up and is now sitting in a full state. We have received a new license and added it to the license server successfully. Unfortunately the DX service will not move any data to Centera. I've tried a manual background scan which appears to have completed but no files were moved. Our move rule hasn't changed, and the Centera media is showing as online.
While looking through things to try and find a solution I noted that our last succesful meta data export was about 2 weeks ago. Since that time the exports seem corrupt. This morning I attempted to start a FULL meta data export, including all files on the extended drives, not just those managed by DX. The meta data export has been running for almost 5 hours now and so far has only written a single file 148 KB file to the export folder.
In Task Manager the DxDmService.exe process is using about 7 - 10% of the CPU and the Mem Usage is continually increasing - it's currently just over 1, 016, 800 KB. I'm beginning to suspect it's caught in some sort of loop and will probably run until it crashes.
Does anyone have any ideas on things I can try to get the system moving files to Centera again? Any idea on how long a full meta data export should take? Our DX server is managing about 5,000,000 files totalling about 12TB on the Centera. The extended drive is 211GB and prior to this failure it sat at about 190GB free, i.e. only 20GB or so for the file stubs has been used.
DX Specs:
v6.0.100 running on W2K3 Enterprise Edition SP1
3.6GHz quad core Xeon, 8GB RAM
211GB extended drive
We have bought 2 new servers and are prepping them with W2K3 64 bit in a 2 node cluster and will be migrating DX to them and upgrading to 6.4 SP1 at the same time. Unfortunately v6.0.100 is out of support so that's why I'm asking for help here.
Dale Schofield
IT Specialist for Clinical Engineering
Alberta Health Services - Calgary
ACHBiomed1
2 Posts
0
May 13th, 2010 09:00
FYI - we were able to convince EMC to aid us in our troubleshooting and we now have a solution to this issue.
When the DX license expired, somehow the DX service reverted to running under the Local System account. How this happened is anyone's guess. This created access issues when scanning the extended drive and hence nothing was flagged for move.
By changing the service to run under an account which has full rights to the extended drive, the scan was able to proceed properly. Our DX box is now back online and we have a kickoff meeting later today to plan the migration to 6.4 SP1.
Lesson learned: the DX service needs to be run under a user account with full rights to the extended drive. Such a simple fix that I'm very thankful for.
2nd Lesson learned: Keep the system updated - if you have a valid support/maintenance contract, use it!
Dale Schofield
IT Specialist for Clinical Engineering
Alberta Health Services - Calgary