[rsyslog-notify] Forum Thread: Send logs to primary and backup server - (Mode 'post')

[noreply at adiscon.com]

User: emilbart 
Forumlink: http://kb.monitorware.com/viewtopic.php?p=25713#p25713

Message: 
----------
Hello,
I would like to make sure here how the rsyslog should work in my
configuration. 
rsyslog version 5.10.1 installed on SLES 11, RELP protocol.
I'm trying to up the following configuration:
- send log using RELP to server: server1 (10.0.0.1)
- if server1 is unavailable, send log using RELP to server2 (10.0.0.2)
- if server1 and server2 are unavailable, keep log in local memory buffer.
- when either server1 or server2 become available again, resend buffered
logs using RELP

This is my configuration on client side:

$ModLoad omrelp

*.* :omrelp:10.0.0.1:20514
$ActionExecOnlyWhenPreviousIsSuspended on
& :omrelp:10.0.0.2:20514
$ActionExecOnlyWhenPreviousIsSuspended off

In general this configuration works but I wonder about one behavior of
rsyslog.
The problem starts when server1 is down, then there is some time (for
example 5 minutes) when rsyslog will discover that server1 is unavailable.
During this time it stores logs in local queue assigned to server1, but
doesn't forward logs to server2. Then rsyslog finds out that server1 is
down and it starts sending logs to server2, but only new logs. Rsyslog
doesn't send logs to server2 which are store in queue assigned to server1.
It sends them to server1 when it is restored.
I would like to ask if it is normal behavior of rsyslog. 
Is it possible to force rsyslog that he will start send logs stored in
queue assigned to server1 when it discovers that server 1 is down? So that
when rsyslog starts send logs to backup server2 there is no logs in queue
assigned to server1.

Thanks for any help