dbTalk Databases Forums  

d3 txlogger question

comp.databases.pick comp.databases.pick


Discuss d3 txlogger question in the comp.databases.pick forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
herbr@pfinders.com
 
Posts: n/a

Default d3 txlogger question - 07-13-2005 , 12:25 PM






If I run my transaction logger to a virtual tape file in Linux, is
there any reason to ftp this file along with the file-save virtual tape
files?

If not, what would be a good strategy of ftp-ing txlog files offsite?

Herb
Pathfinders Software
http://www.pfinders.com


Reply With Quote
  #2  
Old   
Mark Brown
 
Posts: n/a

Default Re: d3 txlogger question - 07-13-2005 , 04:16 PM






Herb,

Long time...

You remember the old backup philosophy: Weekly full backup, nightly
incrementals, constant TX Logging.

When you restore, restore the full, restore the most recent incremental,
restore the tx log for that day.

For your offsite storage, I would think you'd want to keep a copy of
whatever was required to restore the system at any given instant. So you'd
send off the Weekly and nightly incrementals, but keep the tx logs local.
That way YOU can get them back to last night's state, THEY can update
themselves up to the minute.

Mark Brown


<herbr (AT) pfinders (DOT) com> wrote

Quote:
If I run my transaction logger to a virtual tape file in Linux, is
there any reason to ftp this file along with the file-save virtual tape
files?

If not, what would be a good strategy of ftp-ing txlog files offsite?

Herb
Pathfinders Software
http://www.pfinders.com




Reply With Quote
  #3  
Old   
herbr@pfinders.com
 
Posts: n/a

Default Re: d3 txlogger question - 07-15-2005 , 11:50 AM



So, what would the sequence of events be with file-save and txlogging?

stop logger
do file-save
start logger

What about updates during the file-save?


Reply With Quote
  #4  
Old   
Mark Brown
 
Posts: n/a

Default Re: d3 txlogger question - 07-15-2005 , 12:11 PM



Don't stop logging during the filesave. The worst thing that happens is a
record shows up twice, once in the save and again in the TXlogger.

Filesave is only a snapshot of how the data looked at that moment. If they
are saving on a live system, they've got to expect that time won't stand
still for them and there may be something either lost or duplicated. In
this case, duplicated is not bad, as the worst case scenario only results in
a record being updated with the same data.

If, for some reason, you want to use the same device for your filesave as
you are for your txlog, simply stop logging to tape but continue to buffer
tx changes. There's a TXLog menu that will show you how.


Mark

<herbr (AT) pfinders (DOT) com> wrote

Quote:
So, what would the sequence of events be with file-save and txlogging?

stop logger
do file-save
start logger

What about updates during the file-save?




Reply With Quote
  #5  
Old   
herbr@pfinders.com
 
Posts: n/a

Default Re: d3 txlogger question - 07-26-2005 , 12:04 PM



Does this make sense:

STOPLOG (K
FILE-SAVE
SET-DEVICE n
STARTLOG (E

This should keep the logger queue-ing all the time, right?


Reply With Quote
  #6  
Old   
Mark Brown
 
Posts: n/a

Default Re: d3 txlogger question - 07-26-2005 , 03:59 PM



Sort of.

The (K option on stoplog will "release the queue back to overflow". I'm not
certain that's always a good thing.

Also, the (E option on the startlog will log all transactions from all files
regardless of the DL in the FDI.

Other than that, it looks ok.

Mark


<herbr (AT) pfinders (DOT) com> wrote

Quote:
Does this make sense:

STOPLOG (K
FILE-SAVE
SET-DEVICE n
STARTLOG (E

This should keep the logger queue-ing all the time, right?




Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.