Ansicht
Dokumentation

05255 - Backup of Journalreceivers

05255 - Backup of Journalreceivers

CPI1466 during Backup   CPI1466 during Backup  
This documentation is copyright by SAP AG.
SAP E-Book

Backup of Journalreceivers

Thanks to all of you who have responded.

Your information gave me valuable clues for an alternative long term saving
concept.
For a short term solution we will re-activate our BRMS archive scenario, now
with parm RCVSIZOPT(*MAXOPT1), which works well .

Thanks again,
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


-----Ursprüngliche Nachricht-----
Von: Gueldenpfennig, Volker
[mailto:volker.gueldenpfennigZs...]
Gesendet am: Donnerstag, 28. Februar 2002 17:14
An: 'Lehnardt, Franz'
Cc: Sap400 (E-mail)
Betreff: RE: Backup of Journalreceivers

Hi Franz,

nobody asked you to change the threshold to 1TB and I wouldn't do
so,
because then your system would definitely blow up!
That would mean, that a receiver would get only changed after 1TB!!!

The change described below ONLY changes the MAXIMUM receiver size to
1TB, so
that it doesn't stop working at 2GB and run into MSGW.

Regards

Volker

> -----Original Message-----
> From: Lehnardt, Franz [mailto:Franz.LehnardtZe...]
> Sent: Donnerstag, 28. Februar 2002 14:51
> To: Gueldenpfennig, Volker
> Cc: SAP on System i (E-Mail)
> Subject: AW: Backup of Journalreceivers
>
>
> Hi Volker,
>
> sometimes in the past we were advised by SAP to decrease the
> RCV-size-threshold from 2 GB to 500 MB. Don't ask me what for.
> When I now set this threshold up to 1 TB, will it cause any
> trouble, i.e. do
> I have to adjust any additional screws before doing that?
>
> Regards,
> Franz
>
> 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
>
>
> -----Ursprüngliche Nachricht-----
> Von: Gueldenpfennig, Volker
> [mailto:volker.gueldenpfennigZs...]
> Gesendet am: Mittwoch, 27. Februar 2002 15:37
> An: 'franz.lehnardtZe...'
> Cc: Sap400 (E-mail)
> Betreff: RE: Backup of
Journalreceivers
>
> Hi Franz,
>
> I would recommend the following:
> V4R5:
> CHGJRN JRN(R3SIDDATA/QSQJRN) RCVSIZOPT(*MAXOPT1)
>
> V5R1:
> CHGJRN JRN(R3SIDDATA/QSQJRN) RCVSIZOPT(*MAXOPT2)
>
> Then the journal receivers can grow up to 1 GB, because I
guess,
> that the
> problem is, that the system is not able to change the
receiver
> before it
> reached 2GB which is normally the maximum.
>
> Regards
>
> Volker
>
> > -----Original Message-----
> > From: Lehnardt, Franz [mailto:franz.lehnardtZe...]
> > Sent: Mittwoch, 27. Februar 2002 15:08
> > 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
> >
> >
>

Durban Tours - Südafrika Safari

ABAP Short Reference   Vendor Master (General Section)  
This documentation is copyright by SAP AG.

Length: 6542 Date: 20240302 Time: 152545     sap01-206 ( 3 ms )