So....how can I send my logical logs to disk?
Posted in 2000
Topics: Server Administration, Logging & Checkpoints
Hi, I have read a lots of posts on this newsgroup. But, I didn't find an asnwer to this simple question: Do I have to make a misterious configuration to send my logical logs to disk and then to tape???? Or, only changing the LTAPEDEV parameter in my onconfig (like /infx/logs) is enough to do that?? And, once having my logs on disk, I can use any tool to send them to tape??? I need to do this, because I must to backup 4 instances in separate boxes, and I only have ONE TAPE DRIVE!!! Thanks in advance.
Yes, you can change the LTAPEDEV parameter, then use a OS back-up tool to send the logs to tape. JiuG <hnava@argos.com.mx> wrote in message news:39cfd9ca.28578263@news.infolnk.net... > Hi, I have read a lots of posts on this newsgroup. > But, I didn't find an asnwer to this simple question: > Do I have to make a misterious configuration to send my logical logs > to disk and then to tape???? > Or, only changing the LTAPEDEV parameter in my onconfig (like > /infx/logs) is enough to do that?? > And, once having my logs on disk, I can use any tool to send them to > tape??? > > I need to do this, because I must to backup 4 instances in separate > boxes, and I only have ONE TAPE DRIVE!!! > > Thanks in advance.
JiuG wrote:
>
> Hi, I have read a lots of posts on this newsgroup.
> But, I didn't find an asnwer to this simple question:
> Do I have to make a misterious configuration to send my logical logs
> to disk and then to tape????
> Or, only changing the LTAPEDEV parameter in my onconfig (like
> /infx/logs) is enough to do that??
> And, once having my logs on disk, I can use any tool to send them to
> tape???
>
> I need to do this, because I must to backup 4 instances in separate
> boxes, and I only have ONE TAPE DRIVE!!!
>
> Thanks in advance.
Just set LTAPEDEV to a file (using onmonitor if the engine is currently
online otherwise the change will not take effect until the engine bounces)
and run ontape -a or ontape -c or have the ALARMPROGRAM script/executable
run ontape -a everytime a logical log completes. After ontape finishes
rename the file to a new name indicating the logical log sequence number of
the first log in the file (so you know which file to use for a restore
which will ask for log tapes by log number) and use touch or cat</dev/null
to create a new empty archive file (the file must exist and have 660
permissions owner informix group informix just like the chunks).
If you want to try the ALARMPROGRAM method, which I use very successfully,
get my package utils3_ak which contains a version of the log_full.sh script
that works with ontape (the delivered one uses onbar) and my more powerful
and complete alarm event handler program eventalarm.c.
Once the logs are on disk your system back up utilities can archive the
file(s) to tape daily or more often, or for maximum safety you can rcp the
file immediately to a sister machine. Then I have a cron sweep the logical
log backup directory daily and remove logfiles more than a week old so I
will not normally have to scroung for a backup tape to do a restore, the
files will usually still be there.
Art S. Kagel