Ansicht
Dokumentation

05229 - Backup of Journalreceivers

05229 - Backup of Journalreceivers

Fill RESBD Structure from EBP Component Structure   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by SAP AG.
SAP E-Book

Backup of Journalreceivers

We run a backup (savlib)of the journal library twice a day. We run
one at noon and the other after the nightly backup of the database.
Our operators will then delete the saved receivers after the backups.
The backup done at night is really a worthless backup for the
journals. We probably would never use these receivers since we backup
the database at the same time. We use this backup just to get the
receivers to a saved status so they can be deleted. We use CL
programs to perform the backups.

--- In SAP on System iZy..., "Lehnardt, Franz" <franz.lehnardtZe...>
wrote:
> 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]


Durban Tours - Südafrika Safari

PERFORM Short Reference   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by SAP AG.

Length: 3086 Date: 20240426 Time: 061824     sap01-206 ( 3 ms )