Sorry, it was the daemon.raw file - something happened over that weekend and the file grew and filled up the drive. In an effort to save the backup jobs that were running, we tried to clean up some space, but it used it as soon as we cleared it. I had to stop all the backups and restart Networker.
I couldn't stop the processes on the clients, because the jobs were the index and GST jobs that run on the Networker server. When I stopped the processes on the NW server for these jobs, the GUI showed that the job had completed, but in the monitoring screen, the status was still running. When the job tried to run at it's scheduled time, it thought it was running and didn't start.
Uninstalling and reinstalling the NMC seems to have fixed the problem.
I don't think you will find anyone else seeing similar problems! Firstly, can you clarify:
"even if I figure out what process it's runnning and end that" - does that mean you go onto the affected client and restart the Networker processes, kill any save processes running or some combination of that? Is it the same clients affected each time or random?
"my daemon to go rogue and fill up my drive" which daemon is going rogue and what is it filling your drive with?
Can you confirm the spec of your NMC server? Is this running on the backup server? Have you done any performance monitoring?
A few months ago, I was having issues and the EMC tech moved the NMC install from the C: drive to the D: drive where there was more space and Networker was installed. It looks like the other copy was not completely uninstalled before the new version was installed on the other drive. I uninstalled both copies and then reinstalled the new version on the D: drive.
One word of caution if you need to do this. Write down or screen print the settings for LDAP authentication - - enough said?
stewartk2
20 Posts
0
May 29th, 2012 09:00
David:
Sorry, it was the daemon.raw file - something happened over that weekend and the file grew and filled up the drive. In an effort to save the backup jobs that were running, we tried to clean up some space, but it used it as soon as we cleared it. I had to stop all the backups and restart Networker.
I couldn't stop the processes on the clients, because the jobs were the index and GST jobs that run on the Networker server. When I stopped the processes on the NW server for these jobs, the GUI showed that the job had completed, but in the monitoring screen, the status was still running. When the job tried to run at it's scheduled time, it thought it was running and didn't start.
Uninstalling and reinstalling the NMC seems to have fixed the problem.
Thanks,
Kathy
pn1lDbv3G612259
105 Posts
0
May 21st, 2012 10:00
Hi Kathy,
What is the current Java version running on the NMC box. Please make sure you have the right version in place.
The right version is : Java JRE 1.6 update 26.
http://www.oracle.com/technetwork/java/javase/downloads/jre-6u26-download-400751.html
Please use the above link to download the right version of Java as per your OS and install it on your machine
Please confirm if the backups are started, are they getting completed succesfully?
Are you able to see the backed up data?
If Yes, then the issue can be due to the corrupted GST files.
Perform these steps and let us know if this fix your issue:
Stop the Networker services.
Remove only console from the Control Panel ( Add remove programs)
Rename the folders under Management folder ( lgto_gstdb, GST folders)
Rename tmp, jobsdb and nsrladb folders
Start the Networker services
Install the Console software again in the same Management folder
Then run a test backup
Hope this will solve the issue. Please update your feedback.
Thank you
ShivaKiran
DavidHampson-rY
294 Posts
0
May 22nd, 2012 04:00
Kathy
I don't think you will find anyone else seeing similar problems! Firstly, can you clarify:
"even if I figure out what process it's runnning and end that" - does that mean you go onto the affected client and restart the Networker processes, kill any save processes running or some combination of that? Is it the same clients affected each time or random?
"my daemon to go rogue and fill up my drive" which daemon is going rogue and what is it filling your drive with?
Can you confirm the spec of your NMC server? Is this running on the backup server? Have you done any performance monitoring?
Regards
David
pn1lDbv3G612259
105 Posts
0
May 29th, 2012 03:00
Hi Kathy,
Have you performed the steps and did the issue with Networker has been resolved?
Thank you
Shivakiran
stewartk2
20 Posts
0
May 29th, 2012 09:00
There were two copies of the NMC installed.
A few months ago, I was having issues and the EMC tech moved the NMC install from the C: drive to the D: drive where there was more space and Networker was installed. It looks like the other copy was not completely uninstalled before the new version was installed on the other drive. I uninstalled both copies and then reinstalled the new version on the D: drive.
One word of caution if you need to do this. Write down or screen print the settings for LDAP authentication - - enough said?
Kathy