Hi Jim,
I have read thru document but seem not mention for the terminate
option
in production i used command as below
jlogdup -u5 -l/mkcdfs/stat/jlogdup_info INPUT set=current
terminate=eof OUTPUT set=stdout | rsh p570 /gbdev/kuong/bnk/bnk.run/
jlogacldr.sh
in backup server:
jlogdup -v -l/jBase/tjlog/stats/jlogdup_info INPUT set=stdin
terminate=wait OUTPUT set=database
terminate=eof (I) terminate restore/duplication at eof of eldest log
set
terminate=eos (I) terminate restore/duplication at end of current log
set
terminate=wait (I) switch to elder log sets as required and wait for
new updates
Acleda
On Jun 4, 10:13 am, Jim Idle <[email protected]> wrote:
> You are nearly there. Now you just need to read the knowledgebase
> articles, which will tel you about the continuous replay stuff. Look
> at the terminate option and you should be good to go.
>
> Jim
>
> Sent from my iPhone
>
> On Jun 3, 2009, at 6:16 PM, acleda <[email protected]> wrote:
>
>
>
>
>
> > Hi Jim,
>
> > I got it now. it's working fine when i execute the scripts the jlogdup
> > will replay transactions that we have book ino the backup server.
>
> > It only replaying transactions when we execute scripts but I need is a
> > real time replay is being done onto a remote backup server, in case of
> > a crash, the remote backup server can become the production server and
> > users can continue working with risk of minimal loss of data.
>
> > have you had an ideas to proceed the above?
>
> > Acleda.
>
> > On Jun 3, 1:35 am, Jim Idle <[email protected]> wrote:
> >> acleda wrote:
> >>> Hi Jim,
>
> >>> I have create a seperate unix user with the same group, and login
> >>> for
> >>> running the script but what i have update record SECTOR in
> >>> production
> >>> area is not duplication to the backup area. please see the como of
> >>> script as in the attached file
>
> >>> acleda
>
> >>> -----------
> >>> $ ./jlogacl.sh
> >>> 08:32:22 02 JUN 2009 : STATUS:
> >>> Begin jlogdup process: From set 'set=current terminate=eof' to
> >>> set 'set=stdout'
> >>> 08:31:04 02 JUN 2009 : STATUS:
> >>> Begin jlogdup process: From set 'set=stdin terminate=wait' to
> >>> set
> >>> 'set=database'
>
> >> Error 2:
>
> >> $ ERRMSG 2
>
> >> File not found.
>
> >> Did you restore a copy of the original database first? If you just
> >> start
> >> replaying transactions then there will be no files to write them to.
> >> Read up on the whole procedure, but:
>
> >> 1) Quiesce the live system/switch logs/something similar
> >> 2) Make a jbackup of the live system
> >> 3) Restore the live system on the backup system
> >> 4) Now you can start replaying logs
>
> >> Jim- Hide quoted text -
>
> >> - Show quoted text -- Hide quoted text -
>
> - Show quoted text -
--~--~---------~--~----~------------~-------~--~----~
Please read the posting guidelines at:
http://groups.google.com/group/jBASE/web/Posting%20Guidelines
IMPORTANT: Type T24: at the start of the subject line for questions specific to
Globus/T24
To post, send email to [email protected]
To unsubscribe, send email to [email protected]
For more options, visit this group at http://groups.google.com/group/jBASE?hl=en
-~----------~----~----~----~------~----~------~--~---
