Having two background brarchive running at the same time with -f 1 options

[benoit-schmid]

Good morning,

I need to run two brarchive in parallel as background process.

I would like to have on for the save and one for the copy.

I need that because they would have different files.

1. Is this configuration supported or not?

As a file is created for the locking (.lock.bra) I have the feeling that a single process is supported?

2. Just to double check, can I run two brarchive with two different config file in a serial manner

(lauch the 1st one, wait for its end, launch the 2nd one, waits for its end).

3. If you are using that kind script on your systems, could you please provide them?

4. If brarchive is launched by a script how do you shut it?

Do you do just a kill of the script or do you kill it and send another signal to the brarchive if it is currently running?

Thanks in advance for your answers.

[former_member204746]

1. you can only run 1 BRARCHIVE at at time.

2. you can run it twice with different parameters.

3. i let TSM handle the multiple copies save.

4. the same way you shut down any OS program.

[benoit-schmid]

Good afternoon,

>

> 
> 4. the same way you shut down any OS program.

It is a little more subtle than that.

If brarchive is launched by a daemon script,

then killing the script will not automatically

stop brarchive.

Then you end up with a working orphan and locks kept

although you think that you have stop your running brarchive.

A correct handling of forked brarchive must be programmed

in this daemon script.

I would like to avoid reinventing the wheel.

That is why I am interested by the scripts you use in you production environments.

Thanks in advance for your answers.

[former_member204746]

I never used -f option non-stop on a productive system. I only use this option is some special circumstances, such as a client copy (with archiving on).

Why do you want to use option -f 1? what are the reasons being this?

you want to stop brarchive with option -f running? try:

brarchive -f stop

Edited by: Eric Brunelle on Mar 29, 2010 7:36 AM

[benoit-schmid]

Good afternoon Eric,

> Why do you want to use option -f 1? what are the reasons being this?

-f makes it run in background.

For me, there two advantages for doing that.

1. You start it once, when you start sap, and it runs regularly

2. When you stop sap, you stop braarchive. Then you are sure that no crontab jobs are going to be started when you have stopped SAP.

> you want to stop brarchive with option -f running? try:

>

> brarchive -f stop

This is what is currently done right now.

It works well.

I can use it because we do a single copy of the archive log up to now.

We are going to run two brarchives (one to save to a tape robot with backint and one that scp).

I would like this to run as daemon.

Now, that you have answered that I can not have two brarchives running at the same time (thanks for your answer),

I need to write my own daemon in sh or perl that would do:

1. Run brarchive first run (with -p backint init<SID>.sap file)

2. Wait for the en of the brarchive process and log

3. Run brarchive second run (with -p scp/stage init<SID>.sap file)

4. Wait for the end of the brarchive process and log

5. Sleep during a few minutes

6. Handle stop signal so that it ends the forked brarchive that may be running.

I am sure that people on this forum have already wrote such scripts.

I may open another thread as it divert a little from my original question.

Thanks in advance for your help.