symrecover on SE6.4.2 with windows OS

Could you please show us the values for some variables in the option file ??

run_once
run_until_first_failure

-s-

I think that NOW symrecover is working as expected and that in the past it was somehow broken

symrecover is designed to monitor (every 300 seconds in your file) the status of a given RDF link and to resume it when found suspended.

The manual suggests to schedule it since you want symrecover to be running even after a reboot .. If you schedule the startup (let's say every hour) symrecover will check if it's already running before doing everything else. If symrecover find another instance already running it will silently die .. otherwise it will setup the environment and begin monitoring your group.

If you want to stop symrecover you have to deschedule it AND kill the running process via the task manager.

The options I mentioned may condition the behaviour but not setting them means you want the default behaviuor. And that's why symrecover will monitor your group even if you deschedule it

Hi,Stefano

Thx for your notes.

Here is the part of option file
email_log_level=2
log_level=4
monitor_cycle_time=300
goldcopy_type_r2=bcv
goldcopy_bcv_r2_mirror_state_startup=establish
goldcopy_bcv_r2_mirror_state_post_restart=establish
mode=async

basiclly the problem is when you stop scheduler,it wont stop the symrcover and perl process in windows task manager,Which means symrecover is still working in the backgroud.

BTW:symrecover is using the perl come with the SE6.4.2.

Thanks,G

Hi,Stefinao

Thanks for your reply.

Still confused here:
As you said "If you want to stop symrecover you have to deschedule it AND kill the running process via the task manager."

First,This behavior is not match the symrecover in 6.2.When we have previous verions symrecover,you stop scheduler,it will stop all the process itself.

Second,I could not find any document says you need stop windows process when you deschedul it.

Third,Tech support and EMC engineering says it should stop all process when you descheduler it.

Fourth,Even you want to stop process..you will see 5 sysmrcover and 5 perl process in windows task manager(as we will 5 SRDF/A application),it is hard to tell from windows task manager.You need to use Microsoft utility to tell which process is for which device group.

Thanks,G

George let me answer your questions .. one by one if possible

1) I've never ever used symrecover since we have STAR so symrecover can't be used. I don't know how it performed in the past.. But if I read the manuals, I can find that:

SRDF session recovery is an utility initiated by the symrecover command. This utility runs in the background and monitors the state of ...

It clearly states that you run the symrecover command and it will spawn something in the background that will keep on running.

2) I read S.E. manuals, P/N 300-000-877 A09, page 197 ("Stopping symrecover")
And the manuals states:

To stop symrecover manually, use the Escape key. To stop a symrecover task running in the background use one of the following options:

* Windows - cancel the task in the Sceduled Tasks, or use End Task in the Task Manager.
* UNIX - Issue the kill command.

I understand that "or" does not mean "and" .. But killing the task is one of the options mentioned

3) I've seen a primus that tells something about 5 different symrecover sessions .. But it was still open and someone was working on the problem.

4) Why don't you change the way you run your symrecover ?? You can create 5 different scripts (.bat) and give them different names. At system startup you run (via some run keys in the registry) each process .. So that you'll have 5 different names and it will be easier to kill the right task.

-s-

No doubt about that,we do see it in reality.And symrecover acts like the EMC document.



No doubt about the manual.But it looks like it is not an easy or user-friendly way.And also it is not consistent with prvious version.
From EMC tech support line they wont recommend to kill manually.
They think it is temporary soluation.
Maybe we can have something like "symrecover stop"????



I assume that is my case opend with the EMC.



Can you elaborate that a little bit for bat file?I am using windows scheduler,not bat file.And in the EMC manual it recommends windows scheduler or UNIX cron jobs.
Also each scheduler job is target different device group.
From windows task manager you really can not tell which symrecover is running on which device group.
Depends on Windows processexplorer utility you can tell the above.


Hi,Stefano

Hi George.


If you send me an email with the SR number maybe I can try to understand what's going on. My email address can be easily guessed from my surname and my first name .. Simply forget the space between the two parts that form my surname and put an underscore between the surname and the name.


I don't think that a line in the manual is "a temporary solution"


This may be a nice and smart RFE .. And when a customer opens a RFE it's likely that someone will listen


I was trying to elaborate this but I understood that the problem with batchfiles is the same of the scheduler .. When you start the symrecover command (either from CLI or from scheduler of from a batch) it will spawn a child in the background and you completly loose control over its parent (that will likely RIP).. Unfortunatly my suggestion was worst then the problem itself .. Forget about it.

-s-

Message was edited by:
Stefano Del Corno

Hi,Stefano

The problem was "resolved".
EMC engineer did test in lab.Windows2000 scheduler wont stop the second process or child process with ending scheduler.
But Win2k3 has no issue with it.

Since we have workaround here,it is OK for us now.

So next step will be upgrade OS...
Thanks for your time and help!
G