OMNISV

[devakumar]

Hi Gurus,

is omnisv -start without omnisv -stop will make any difference?

is't really hungup backup process ?

i have started without stoping omnisv,
pid for crs and mmd remains the same..
is't normal ?



waiting for your valuble tips...

Thanks in advance


Best Regards,
Devakumar,Theivendran

[A. Clay Stephenson]

The man pages don't really make it clear although it is obvious that the intended use is to first issue an "omnisv stop" command before doing an omnisv start --- and that is the way I have always done it. I would issue an omnisv stop and then do a "ps -ef | grep 'omni'" and look for any remaining processes and kill them. You should then issue an "omnisv start" command and all should be well.

[devakumar]

Thanks for your reply...


i understand...

but my question is:
is omnisv -start without omnisv -stop will make any difference?

is't really hungup backup process ?

i have started without stoping omnisv,
pid for crs and mmd remains the same..
is't normal ?

Best Regards,
Devakumar,Theivendran

[lafargeadmin]

Definitely you will get the process hung. Because you are attempting start the active process. You need to kill the process and restart it.

#ps -ef | grep 'omni'
# kill-9 pid's

#omnisv start

[Court Campbell]

I don't believe that running omnisv start is really doing anything if the data protector background processes are already running. you can run omnisv status to check the stauts of the processes. but if you need to restart the processes you need to do a stop and then a start. I don't know if that helps, your question is somewhat hard to understand.

[Court Campbell]

oh, and if the pid's are the same after running the omnisv start command again then it did absolutely nothing.