Unsolved

This post is more than 5 years old

18 Posts

1168

July 25th, 2006 00:00

savegrp command

I've executed a savegrp command to make an incremental backup of a single client belonging to a specifig group. As the remote command configured probably get an error, I'd like to stop the ongoing process, but if I try to stop the savegroup by gui, I get a warning that told me 'Only automatically started groups that are currently running can be stopped'. So, as I have other groups running and I don't wanna think about stopping all the processes or doing something like this, what can I do to stop only the savegrp command I've executed by command line? Is a ctrl+c break option ok?

Thanks,
S

6 Operator

 • 

14.4K Posts

 • 

56.2K Points

July 25th, 2006 01:00

Yes it is. If not get free tools from Sysinternals site offering you possibility to identify process's arguments and killing them too.

6 Operator

 • 

14.4K Posts

 • 

56.2K Points

July 25th, 2006 02:00

On few occasions I did see that unexpected exit (and that includes kill) leaves group in running state (on Windows platform). You can try to force the change via nsradmin - didn't try that, but in theory it should work.

18 Posts

July 25th, 2006 02:00

Hi Hrvoje,

well I've tried killing first the savegrp command, but even if I could work with the command line, the group look still running on the gui. Then I've killed some other nsrmmd.exe process, but nothing happens. When I've finished all my bullets I've decided to restart the server, as any other backup process was ended.

2 Intern

 • 

724 Posts

July 25th, 2006 06:00

I see that very often. As usually I keep restarting the group via savegrp (and doing some changes between) until I get this to work, that's not a problem.

When I have to kill the process, and need to keep the status as finished (for the monitoring guys do not worry about that), I usually force the group to Skip level, and run savegrp.

18 Posts

July 26th, 2006 03:00

Yes, well, you can kill savegrp process and excute the same command via command line, with the needed changes. I'm just worried about the 'running' group as shown by the GUI ...

I can play with savegrp command, but if I leave the group 'running' by an unindefied process (...), will the group be started automatically by night, at the scheduled time? I dunno ... Well, I think it won't. That's why, every time I get a "not clear" error excuting savegrp by command line, I'm going to restart the server :-/

By the way, I discover the cause of my problem: I've edit a vbs script to stop some services and it worked fine (execute by remote command savepnpc). The problem is that a program running on that client will restore killed processes automatically, and the backup process hangs ...

Thanks for the hint to set the group to skip level, at least to test any remote command :-)

6 Operator

 • 

14.4K Posts

 • 

56.2K Points

July 26th, 2006 03:00

You could always start "manually" group via nsradmin; I think that should give you a chance to stop it via GUI (not 100% sure).
No Events found!

Top