Networker 8.1117 NMC problem: gstd.exe service don't start after mmrecov

a) You should ask this in NetWorker community - this is general ECN area

b) you should really start colleting bootstrap reports instead of scanning if you care about good DR practice

c) With 8.1 mmrevov is depreciated and you should use nsrdr

Now, in respect to NMC service, I assume this runs on the same box?  By default data from NMC should not be affected as it just reads data from NSR database which you restored.  Why it doesn't run you should check in NMC logs.

Additional question; when you reinstalled NMC, did you also remove old NMC database or you kept old one?

Hi,

As author on right side you should have option to move it.  If not, one of admins here will do it.

I guess you can skip scanner part as it just takes time.  Given that you do not remove mdb record prior to your test, there is no point of scanning at all.

It is really strange that service does not start even if you removed DB because this means that service does not start due to not reading its own data most likely and this data is not touched by mmrecov in any way (different data).  Normally, gstd should even remain running while you were doing mmrecov (it would not collect data due to nsrexecd being bounced on and off, but that should not matter - at least on UNIX/Linux hosts it does not).  So, the way description goes now if might be that gstd is not running for reason not related to mmrecov at all.

When you check event log, do you see at which point gstd service started to have issues?  Note that with new DB NMC would know nothing of your setup so this is why I doubt it is related to NSR actions.  What you can do, just to be 100% sure, is uninstall NMC, remove completely folder structure from NMC so that nothing on file system is left of NMC, install it and see if it works then.

Thanks for your answer Hrvoje.

a) It's my first time on this forum... Can I move my ask to Networker community ?

b) I'm also collecting bootstrap reports, but I still scann (for double check I suppose )

c) I don't know nsrdr, I will give a look.

Yes, NMC is installed on the same box.

I have ckecked the NMC log but the service failed before writing anything in the logs. When I run gstd.exe from command line, I have informations written in the log, but no error because it works...

When I have reinstalled NMC, I have tried both, keeping the database or removing everything: same problem. 

But one question - this is test system?  And you are placing back data from that system and not any other?

Well, I'm going to restart from the begining. I'm removing everything. I will install the whole package again. And restore my data using nsrdr instead of mmrecov and I will let you know.

I assume that for production you do not have NMC on the same host?  Well, you might have it, but if I remember correctly recommendation is that if you have 50+ clients you have separate box for NMC.

yes it's my test system for Data Recovery Plan. I'm trying to update my Recovery procedure with NW 8.1. It was working fine with NW 7.6 but we have upgraded the production server to 8.1 this summer.

I have moved it, I hope it's the right place.

About NMC reinstallation, I have also tried to remove all the path and reboot before install it again. I even tried to change the installation directory (it's installed on D: drive on our production server...) it's still the same song.

And if I remove everithing and do a fresh install for the whole package (networker server +client +NMC) it works. Until I restore "res" folder from tape.

Welcome to right place

It is strange.  Because NMC and NSR are independent of each other.  So, you have nsr and that part works.  Now, assuming NMC is installed on top, you install it and it is tabula rasa when starting from no data.  At that point, service should already run.  If this is not the case, res by NW has nothing to do with it as NMC even doesn't have your server defined yet.

If NMC would crash after you add backup server to NMC, then, that would be different story.

1. I have reinstall from the begining. Networker 8.1117 and NMC were working fine.
2. I have load a tape with bootstrap backup and run nsrdr command.
3. I have followed the nsrdr and replied the questions...
4. nsrdr stopped the NW services (including the gstd)
5. at the end of nsrdr process, I restart the NW services but the gstd don't start.

Yes, NMC is on the same host in production. But don't worry, we have less than 15 clients.

ok, if you are in the mood for play, try these two variation:

Variation 1:

- do the same thing, but now stop NMC services before doing nsrdr - this way NMC is not affected in any way by DR.  Run NMC service.

Variation 2:

- do same as variation 1, but this time also copy while NMC folder (including binaries and database).  When done with DR, put back data and try to run NMC service

If this doesn't work, then I can't see what can be causing this because nsrdr should not touch any DB or service dependent thing for NMC.  Of course, you can go even further by comparing nsr folder which has been returned with original one when it all works (assuming that in test scenario there is no difference between them so you should not expect to see any difference after nsrdr). 

Let me suggest that you

  - try to start the the service from the command line (net start gstd)

  - run gstd from the command line

  - investigate the log file gstd.raw for details.

If no problem is visible you should increase the debug level.

I will try the 2 variations you have suggested. But first, I can tell you that bringing back the installation's "res" folder allows the service to start again... so that's definitively linked. Isn't it ?

Hi Bingo,

• "net start gstd" is not working better than service : "service is not responding..."
  
• Running gstd.exe from command line is working fine.

is it possible to run the service with debug option ?