Automate Log shipping

[situ]

Greeting,
I'm using Db2 9.5 for windows.

would anybody please suggest me on how to "automate log shipping "?

Regards,
situ

[Ian]

situ wrote:

Greeting,
I'm using Db2 9.5 for windows.

would anybody please suggest me on how to "automate log shipping "?

HADR is certainly the best method.

On Windows, if both servers can see each other directly, you can do
this by using LOGARCHMETH2 and using a UNC path for a share on the
standby server, as in DISK:\\server2\share. This requires that the
privileges be set up properly (easiest if both machines are in a domain,
and the DB2 instance owner on both servers is the same domain ID).

The alternate method is to write some batch / shell scripts that will
run periodically to copy the archive log files from the primary server
to the secondary.
In both cases, you would need to have a scheduled task that runs on
the standby server to issue the rollforward database command to apply
the new transaction logs that have been shipped from the primary server.

[Pierre StJ]

On Aug 21, 3:44*am, situ <[e-mail]:

Greeting,
I'm using Db2 9.5 for windows.

would anybody please suggest me on how to "automate log shipping "?

Regards,
situ

There are parameters in your db cfg that allow you to do that. HADR
is one possibility.
The simplest is to use LOGARCHMETH1 and LOGARCHMETH2.
You can use the first parm. to archive a copy wherever you need:on
system disk, tape, remote disks, TASM, Veritas, ....
You use the the second parm. to do the same to archive any of the
other places but the one you chose for the first parm.

So if you can map your receiving drives on the remote system where you
want to ship to your DB2 system then all you need to do is update, in
your db cfg:
LOGRETAIN=RECOVERY and LOGARCHMETH1 or METH2 to <remote data path>

From then on, any time a log file fills, whatever the state of the
transactions in it, the log will automatically ship to the target.

Hope this helps, Pierre.