/usr/share/doc/slony1-2-doc/adminguide/slony-logshipping.html

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
<HTML
><HEAD
><TITLE
>slony_logshipping</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
REV="MADE"
HREF="mailto:slony1-general@lists.slony.info"><LINK
REL="HOME"
TITLE="Slony-I 2.2.4 Documentation"
HREF="index.html"><LINK
REL="UP"
TITLE="Reference"
HREF="reference.html"><LINK
REL="PREVIOUS"
TITLE="SLONIK CLONE FINISH"
HREF="stmtclonefinish.html"><LINK
REL="NEXT"
TITLE="Appendix"
HREF="appendix.html"><LINK
REL="STYLESHEET"
TYPE="text/css"
HREF="stylesheet.css"><META
HTTP-EQUIV="Content-Type"
CONTENT="text/html; charset=ISO-8859-1"></HEAD
><BODY
CLASS="REFENTRY"
><DIV
CLASS="NAVHEADER"
><TABLE
SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="5"
ALIGN="center"
VALIGN="bottom"
><SPAN
CLASS="PRODUCTNAME"
>Slony-I</SPAN
> 2.2.4 Documentation</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="top"
><A
HREF="stmtclonefinish.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="top"
><A
HREF="cmds.html"
>Fast Backward</A
></TD
><TD
WIDTH="60%"
ALIGN="center"
VALIGN="bottom"
></TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="top"
><A
HREF="appendix.html"
>Fast Forward</A
></TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="top"
><A
HREF="appendix.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><H1
><A
NAME="SLONY-LOGSHIPPING"
></A
><SPAN
CLASS="APPLICATION"
>slony_logshipping</SPAN
></H1
><DIV
CLASS="REFNAMEDIV"
><A
NAME="AEN8234"
></A
><H2
>Name</H2
><SPAN
CLASS="APPLICATION"
>slony_logshipping</SPAN
>&nbsp;--&nbsp;slony_logshippping daemon</DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN8238"
></A
><H2
> <SPAN
CLASS="APPLICATION"
>slony_logshipper</SPAN
> Tool </H2
><A
NAME="AEN8241"
></A
><P
> slony_logshipper is a tool designed to help
apply logs.  It runs as a daemon and scans the archive directory for new .SQL files which it then applies to the 
target database. It can be run with three sorts of parameters:</P
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN8244"
></A
><H2
>Options</H2
><P
></P
><UL
><LI
><P
> Options, chosen from the following: </P
><P
></P
><UL
><LI
><P
><TT
CLASS="OPTION"
>h</TT
> </P
><P
>    display this help text and exit </P
></LI
><LI
><P
><TT
CLASS="OPTION"
>v</TT
> </P
><P
>    display program version and exit </P
></LI
><LI
><P
><TT
CLASS="OPTION"
>q</TT
> </P
><P
>    quiet mode </P
></LI
><LI
><P
><TT
CLASS="OPTION"
>l</TT
> </P
><P
>    cause running daemon to reopen its logfile </P
></LI
><LI
><P
><TT
CLASS="OPTION"
>r</TT
> </P
><P
>    cause running daemon to resume after error </P
></LI
><LI
><P
><TT
CLASS="OPTION"
>t</TT
> </P
><P
>    cause running daemon to enter smart shutdown mode </P
></LI
><LI
><P
><TT
CLASS="OPTION"
>T</TT
> </P
><P
>    cause running daemon to enter immediate shutdown mode </P
></LI
><LI
><P
><TT
CLASS="OPTION"
>c</TT
> </P
><P
>    destroy existing semaphore set and message queue            (use with caution) </P
></LI
><LI
><P
><TT
CLASS="OPTION"
>f</TT
> </P
><P
>    stay in foreground (don't daemonize) </P
></LI
><LI
><P
><TT
CLASS="OPTION"
>w</TT
> </P
><P
>    enter smart shutdown mode immediately </P
></LI
></UL
></LI
><LI
><P
> A specified log shipper configuration file </P
><P
> This configuration file consists of the following specifications:</P
><P
></P
><UL
><LI
><P
> <TT
CLASS="COMMAND"
>logfile = './offline_logs/logshipper.log';</TT
></P
><P
> Where the log shipper will leave messages.</P
></LI
><LI
><P
> <TT
CLASS="COMMAND"
>cluster name = 'T1';</TT
></P
><P
> Cluster name </P
></LI
><LI
><P
> <TT
CLASS="COMMAND"
>destination database	= 'dbname=slony_test3';</TT
></P
><P
> Optional conninfo for the destination database.  If given, the log shipper will connect to this database, and apply logs to it. </P
></LI
><LI
><P
> <TT
CLASS="COMMAND"
>archive dir = './offline_logs';</TT
></P
><P
>The archive directory is required when running in <SPAN
CLASS="QUOTE"
>"database-connected"</SPAN
> mode to have a place to scan for missing (unapplied) archives. </P
></LI
><LI
><P
> <TT
CLASS="COMMAND"
>destination dir = './offline_result';</TT
></P
><P
> If specified, the log shipper will write the results of data massaging into result logfiles in this directory.</P
></LI
><LI
><P
> <TT
CLASS="COMMAND"
>max archives = 3600;</TT
></P
><P
> This fights eventual resource leakage; the daemon will enter <SPAN
CLASS="QUOTE"
>"smart shutdown"</SPAN
> mode automatically after processing this many archives. </P
></LI
><LI
><P
> <TT
CLASS="COMMAND"
>ignore table "public"."history";</TT
></P
><P
> One may filter out single tables  from log shipped replication </P
></LI
><LI
><P
> <TT
CLASS="COMMAND"
>ignore namespace "public";</TT
></P
><P
> One may filter out entire namespaces  from log shipped replication </P
></LI
><LI
><P
> <TT
CLASS="COMMAND"
>rename namespace "public"."history" to "site_001"."history";</TT
></P
><P
> One may rename specific tables.</P
></LI
><LI
><P
> <TT
CLASS="COMMAND"
>rename namespace "public" to "site_001";</TT
></P
><P
> One may rename entire namespaces.</P
></LI
><LI
><P
> <TT
CLASS="COMMAND"
>post processing command = 'gzip -9 $inarchive';</TT
></P
><P
> Pre- and post-processing commands are executed via <CODE
CLASS="FUNCTION"
>system(3)</CODE
>. </P
></LI
></UL
><P
> An <SPAN
CLASS="QUOTE"
>"@"</SPAN
> as the first character causes the exit code to be ignored.  Otherwise, a nonzero exit code is treated as an error and causes processing to abort. </P
><P
> Pre- and post-processing commands have two further special variables defined: </P
><P
></P
><UL
><LI
><P
> <TT
CLASS="ENVAR"
>$inarchive</TT
>  - indicating incoming archive filename </P
></LI
><LI
><P
> <TT
CLASS="ENVAR"
>$outnarchive</TT
>  - indicating outgoing archive filename </P
></LI
></UL
></LI
><LI
><P
> <TT
CLASS="COMMAND"
>error command = ' ( echo
"archive=$inarchive" echo "error messages:" echo "$errortext" ) | mail
-s "Slony log shipping failed" postgres@localhost ';</TT
></P
><P
>  The error command indicates a command to execute upon encountering an error.  All logging since the last successful completion of an archive is available in the <TT
CLASS="ENVAR"
>$errortext</TT
> variable. </P
><P
> In the example shown, this sends an email to the DBAs upon
encountering an error.</P
></LI
><LI
><P
> Archive File Names</P
><P
> Each filename is added to the SystemV Message queue for
processing by a <SPAN
CLASS="APPLICATION"
>slony_logshipper</SPAN
>
process. </P
></LI
></UL
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="stmtclonefinish.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="appendix.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>SLONIK CLONE FINISH</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="reference.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Appendix</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>
slony1-2-doc 2.2.4-3 / usr / share / doc / slony1-2-doc / adminguide / slony-logshipping.html
