Skip to main content
Start a Conversation

Unsolved

This post is more than 5 years old

vbangia

4 Posts

2206

January 28th, 2008 08:00

Server with newly installed DiskXtender 6.2 for Windows crashes

I've just rolled out DiskXtender 6.2 on our big file server. It's running Windows 2003 SP1. We've setup move rules to move office docs (.doc, .xls, .ppt, .mdb) .pdf's, .txt, .bmp and .jpg files. The move rules I setup were conservative in nature, only move files that were last written to 1800 days ago, ~ 5 years. Background scan ran fine and moves went well, taking 4 hours and 2 hours respectively. The 2nd tier storage is on the local LAN as well, beefy server w/ direct attached storage.

In the past 3-hours the file server has crashed 3-times. In the past year, the server has crashed only once. I've disabled the DX and DX License Manager service and the server has not crashed since. Has anyone experienced this on servers w/ DX installed? I've opened a case w/ EMC but am awaiting a call back.

Any thoughts, clues?

Thanks.

szekelyk

129 Posts

February 22nd, 2008 05:00

Hi I have the same problem at a customer it seems that there is a memory leak in DX, it fills up the nonpaged pool memory area. EMC promised us, fix is in DX6.2 SP4, which is not released yet.

Ryan9

45 Posts

February 29th, 2008 08:00

Not having the patches installed or not having reboot the server after the patch installations can cause this.

I've also seen this happen on systems that are running DFS in replication mode. Obiously you can't use DFS in replication mode anyway because DFS will replicate the stub to a server that doesn't know what to do with it.

Engineering told me that this should be supported come sometime Q4.

szekelyk

129 Posts

March 5th, 2008 01:00

MS and EMC tracked down the problem, this is a bug on DX side, promised to be fixed in SP4.

KAT4

3 Posts

December 3rd, 2008 11:00

I am running DX 6.3.200 Patch 01 and have the same issue with filling up the nonpaged pool memory area and crashing my server. I have disabled Indexing, background scans, metadata exports, etc. In fact, the only thing going on is that I am allowing fetches back from the media (centera). I am currently dead in the water AND I am having to reboot my file server (also the DX server) every week or so so far.

Any one else with the new DX with this issue?

Thank you,

Kari A. Thompson

Wisers

2 Intern

 • 

138 Posts

December 4th, 2008 06:00

I'm going to look out for this problem on our DX 6.3 server, also running EX.

To be clear, when you are having the problem the nonpaged memory under "Kernel" in task manager on the performance tab reads "0" ?

I just want to know how you are monitoring the situation so I can look out for it.

Wisers

2 Intern

 • 

138 Posts

December 4th, 2008 06:00

Thanks I'll keep an eye on the event log as well.

KAT4

3 Posts

December 4th, 2008 06:00

The two times it has happened, I have noticed the event in the System log only. The next time the issue comes up (probably this comming Wednesday) I will make sure that I check that. I will let you know.

Thanks,

KAT...

rfranke

9 Posts

January 14th, 2009 08:00

We had this issue also. For us, it was fixed with DX 6.2 SP1 655. It is caused by a memory leak.

FYI: While your server is having issues with maxing out the memory, you are prone to writing corrupt data out to the Centera.

rama_maddodi

1 Rookie

 • 

66 Posts

January 11th, 2011 06:00

Hey I am getting the same issues. I was having issues with my windows server 2003 R2 getting hunged and eventually got crashed. So I applied DX 6.3  SP1 patch 02, and on the release notes, it was mentioned that they fixed the memory leak issue. But no luck, I am still having issues. Any clue or any idea  anyone?? I was reading DX 6.4 upgrade option but not sure should I be doing that.

Thank You

Rama

Vinodraj_Daniel

12 Posts

January 12th, 2011 01:00

Hi Rama,

Could you get in touch with DX support so that the logs can be looked into to identify the cause for the issue?

Thanks,

Vinod

Was this post helpful?

View All

No Events found!

Top