Ansicht
Dokumentation

05225 - Backup of Journal receivers

05225 - Backup of Journal receivers

Vendor Master (General Section)   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.
SAP E-Book

Backup of Journal receivers

Hi Franz,
What we do here is we shut SAP down weekdays at 4:00 AM.

When SAP is down a job is run to get a list of all the journal receivers and
then generate a new journal receiver.

The journal receivers are saved to a save file with the same name and the
journal receiver is deleted.

The newly created journal receiver is not backed up.


Bill Shane
Technicolor Canada.

-----Original Message-----
From: Lehnardt, Franz [mailto:franz.lehnardtZe...]
Sent: February 27, 2002 9:08 AM
To: 'SAP on System i (E-Mail)'
Subject: Backup of Journalreceivers



Hi all

another poll to the group:

I wonder, how you out there do manage the backup/archive of your JRNRCVs?
How much traffic do you have on your journal?
How often and in which way do you backup your receivers?

The background of my questions:

Once we used BRMS function "Archive" to handle the daily backup of our R/3
JRNRCVs. But it happened sometimes that our PRD system came to a complete
hold because of the Archive job locked the entire PRD journal, so the
current RCV couldn't get changed when it reached its threshold. Msg CPI70E5
"Journal or Journalreceiver not available" was issued.

An additional reason for that conflict was the fact, that the rate of RCV
changes on our system is at some times of day very high (less than 5 min.),
so when the Backup Job runs for about 10-15 minutes, the current receiver is
guaranteed to crash against the wall...

Finally we set a manual procedure which is still in use today:

WRKJRNA to check, what JRNRCVs are in status ONLINE
SBMJOB with command SAVOBJBRM where the known receiver numbers are entered.
This way we make sure, that all the receivers which will be attached during
the backup will not get locked
Last step: Delete all saved receivers also manually.

But this manual input is risky (the human IT-component...) and sure enough -
this week we had another PRD stop, because of accidentially saving the wrong
receiver-number. Now we think of an alternative, fully or partly automatted.

Any insight will help, thanks a lot in advance.

Franz Lehnardt
AS/400 & R/3 Basis Administration
EGG IT Services GmbH
Eschborn, Germany
Tel. ++49 (0) 6196 477-360
Fax ++49 (0) 6196 477-776


[Non-text portions of this message have been removed]



consolut Sponsor



<http://rd.consolut.net/M=217097.1902236.3397169.1261774/D=egroupweb/S=17050073
89:HM/A=960173/R=0/*http://service.consolut.net/consolut/click?bfmid=29150849&site
id=39249818&bfpage=moneyconsolut4>

<http://us.adserver.consolut.net/l?M=217097.1902236.3397169.1261774/D=egroupmai
l/S=1705007389:HM/A=960173/rand=239691936>

Have a look to our homepage at: http://www.consolut.net
<http://www.consolut.net>
DoNotReply@consolut.eu

Your use of consolut is subject to the consolut Terms of Service
<http://www.consolut.net> .




[Non-text portions of this message have been removed]


Durban Tours - Südafrika Safari

TXBHW - Original Tax Base Amount in Local Currency   CPI1466 during Backup  
This documentation is copyright by SAP AG.

Length: 4230 Date: 20240304 Time: 231506     sap01-206 ( 3 ms )