HDR Replication and event alarm log backup
Hi Folks,
I got replication up and running finally. The process was as
described in the manuals and everything looks good for now. The on bar alarm
program ( /etc/log_full.sh ) which backs up the log files when they fill up
is failing though. The message is:
07:46:47 Process exited with return code 142: /bin/sh /bin/sh -c
/opt/ids2k/v9r21uc5/etc/log_full.sh 2 23 "Logical Log 2837 Complete.""Logical Log 2837 Complete."
I know this message is not always a problem but I had investigated and in my
case it is failing. I have replaced this with a cron shell script which
backs to disk for now.
My question is: My cron script backs up the logs periodically ( 6 hours ).
Some log files are partially full when they are backed up. Since they are
backed up they will not be used again. Is this a problem for replication ?
The manual mentions that the log records are shipped to the secondary when
the logical log files are backed to disk. Does it matter how they are backed
to disk ?
TIA,
Jack
not a problem
FYI - the log records are shipped to the secondary when they are written to
disk, not when they are backed up.
M.P.
"Jack A" <jacka8@excite.com> wrote in message
news:ccd3086c3ac104bb122bbec6f79ba7bb@news.teranews.com...
> Hi Folks,
> I got replication up and running finally. The process was as
> described in the manuals and everything looks good for now. The on bar
alarm
> program ( /etc/log_full.sh ) which backs up the log files when they fill
up
> is failing though. The message is:
>
> 07:46:47 Process exited with return code 142: /bin/sh /bin/sh -c
> /opt/ids2k/v9r21uc5/etc/log_full.sh 2 23 "Logical Log 2837 Complete."> "Logical Log 2837 Complete."
>
> I know this message is not always a problem but I had investigated and in
my
> case it is failing. I have replaced this with a cron shell script which
> backs to disk for now.
>
> My question is: My cron script backs up the logs periodically ( 6 hours ).
> Some log files are partially full when they are backed up. Since they are
> backed up they will not be used again. Is this a problem for replication ?
> The manual mentions that the log records are shipped to the secondary when
> the logical log files are backed to disk. Does it matter how they are
backed
> to disk ?
>
> TIA,
> Jack
>
>
Great. Thanks again.
"Madison Pruet" <mpruet@comcast.net> wrote in message
news:_fhgb.508022$Oz4.358468@rwcrnsc54...
> not a problem
>
> FYI - the log records are shipped to the secondary when they are written
to
> disk, not when they are backed up.
>
> M.P.
>
>
> "Jack A" <jacka8@excite.com> wrote in message
> news:ccd3086c3ac104bb122bbec6f79ba7bb@news.teranews.com...
> > Hi Folks,
> > I got replication up and running finally. The process was as
> > described in the manuals and everything looks good for now. The on bar
> alarm
> > program ( /etc/log_full.sh ) which backs up the log files when they fill
> up
> > is failing though. The message is:
> >
> > 07:46:47 Process exited with return code 142: /bin/sh /bin/sh -c
> > /opt/ids2k/v9r21uc5/etc/log_full.sh 2 23 "Logical Log 2837 Complete."> > "Logical Log 2837 Complete."
> >
> > I know this message is not always a problem but I had investigated and
in
> my
> > case it is failing. I have replaced this with a cron shell script which
> > backs to disk for now.
> >
> > My question is: My cron script backs up the logs periodically ( 6
hours ).
> > Some log files are partially full when they are backed up. Since they
are
> > backed up they will not be used again. Is this a problem for replication
?
> > The manual mentions that the log records are shipped to the secondary
when
> > the logical log files are backed to disk. Does it matter how they are
> backed
> > to disk ?
> >
> > TIA,
> > Jack
> >
> >
>
>