1 (866) 885-5606

Legacy Fax into Modern Business Intelligence

To make forum posts, you must be a registered user of AllAboutFoIP.com.

Username   Password       Forgot your password?  Forgot your username?  Create an account

** FORUM for AllAboutFoIP.com™ **

The FoIP Forum is now live and active.  Register and be one of the first to start a forum thread.  FoIP experts frequent the forum regularly to post replies.

This forum does not accept backlink signature lines in forum posts. SPAMMERS KEEP OUT.

Right fax 9.4 redundancy not working

Right fax 9.4 redundancy not working

Hi  Friends,

I have a problem with Right fax redundancy, I have 2 right fax servers ver 9.4 FP1 SR3 with shared services.
I have the Database on the First Server RF1  & second server RF2 points to this Database on the RF1.
The RF client is pointing to RF1 , but while testing redundancy when I make RF1 server down, The RF client on my PC does not automatically point to RF2.
I have to close the RF client & open manually the RF2 by typing the  hostname.
I have done the necessary changes in the Registry still we have to do thing manually.

Can some one help me to resolve this.

Thanks in advance,
Oliver

OLIROD79
ranks
useravatar
Offline
1 Posts
Administrator has disabled public posting

Re: Right fax 9.4 redundancy not working

Oliver,

The best thing to do is to contact REDACTED.  NO BACKLINKS ACCEPTED.
They will be able to assist you.

Matthew

mattbrine
ranks
useravatar
Offline
1 Posts
Administrator has disabled public posting

Re: Right fax 9.4 redundancy not working

Oliver,
This sounds to me like there is no utilization of load balancing in place which would allow the IP to float between the two servers. With the clients pointed to the virtual IP (VIP) or DNS name the load balancer will allow the machines to hit either RF1 or RF2. From what you've described it sounds as if you have the client machines pointed at RF1 and when that goes offline you have to repoint it to RF2. What you're describing sounds like you're not using a load balancer. If you want the seamless connection across the servers, I would recommend looking into a load balancing solution such as Big IP, Netscaler, etc.
Hope this helps,
Jen

JShoun
Manager- Technical Services
ranks
useravatar
Offline
21 Posts
Administrator has disabled public posting

Re: Right fax 9.4 redundancy not working

Oliver:  Thanks for checking in with us.  A few comments, and we welcome you contact us at One Touch if you have further questions.

In speaking to some engineers, there are a few prerequisites to think about, and some limited and full blown solutions.  As Jen pointed out, first it is important to determine whether you have a full version of SQL instead of SQL Express.  Of course I am curious why you keep a SQL database resident on RF1 as this defeats high availability.  That being addressed, obviously an IP load balancer is a clear direction, but I imagine if you do not have SQL in HA, getting a load balancer may be prohibited.

The other option would be to use MS Cluster or MS NLB to achieve a virtual or floating DNS.  Check out this tech note for starters:  http://technet.microsoft.com/en-us/library/cc732855(WS.10).aspx 

I was told about another solution that is actually problematic called DNS Round Robin or Multi-homed DNS.  You can use a multihomed dns which is just a fancy way of saying two dns entries with the same IP address.  The client is supposed to pick one at random.  However, it won’t automatically flip over to the other if the one it picks is down.  Another issue with DNS Round Robin can be problems with print-to-fax jobs being delivered incorrectly, especially with 9.3 clients.  The problem was Round-Robin didn't always keep a 'persistent' connection when making requests.

Hope this helps, and again, please contact One Touch Support if you need more help.  Thank you, Scott

srileyotgt
CEO @ www.otgt.com
ranks
useravatar
Offline
31 Posts
Administrator has disabled public posting

Re: Right fax 9.4 redundancy not working

Scott,
You make reference to running a load balancer in front of two RightFax servers.  Can you shed any light on how the load balancer may need to be configured, to make this happen?  I understand that this is very broad, but my server team has recently came to me with an issue related to the current load balancing design.  The existing config has been in place far before the Shared SQL DB was added.  My hope is that having the Shared SQL DB will make the load balancing config very simple.  Even Round Robin, with no persistence required, as my hope is that all state info is in the DB
Thanks,
Kev

abuzz4me
ranks
useravatar
Offline
1 Posts
Administrator has disabled public posting

Re: Right fax 9.4 redundancy not working

Kevin:  I have a couple of engineers with more scar tissue on this than I do.  However, a few thoughts to start with. 

First, in reference to a shared SQL, you would set up RightFax as a collective, which requires 2 to 4 active nodes (full licenses), with the shared DB external with a shared queue, and likely, a shared SAN space for the image repository.  In a situation of higher volume, I would also recommend RightFax 10.5, which has vastly improved the technology and speed using nested image paths and messaging queuing, likely allowing NAS implementations.

As far as the load balancers, this would obviously permit client, production stream and API access to multiple Rightfax servers, but you need to make the sessions sticky.  Also, another area load balancers really help is allowing Fax over IP distributed sharing of traffic, both as a primary/secondary strategy, and/or also as a load balancing strategy, including mutiple sites.  If we do this with special SIP trunks, we can facilitate some of this without a load balancer.

The main question I have revolves around your environment and purpose for using a load balancer, given your comment about the SQL environment.

srileyotgt
CEO @ www.otgt.com
ranks
useravatar
Offline
31 Posts
Administrator has disabled public posting

Re: Right fax 9.4 redundancy not working

Another option to explore for higher availability is using SIP Trunks, which with the correct implementation can allow multiple termination points for the same fax numbers.  In this scenario, SIP Trunks can be set up as "active-Active" for load balancing and HA, as well as in an "active-passive" failover that is automatic or user controlled.

For starters, I recommend you read this white paper, and if you have any questions or want to try the service for Fax or VoIP, such as Lync, please let me know.
http://www.faxservervm.com/cloud-faxing-with-sip-trunks

srileyotgt
CEO @ www.otgt.com
ranks
useravatar
Offline
31 Posts
Administrator has disabled public posting

Board Info

Board Stats:
 
Total Topics:
99
Total Polls:
0
Total Posts:
44
Dormant:
User Info:
 
Total Users:
14093
Newest User:
davisfraley0830
Members Online:
0
Guests Online:
46

Online: 
There are no members online

Forum Legend:

 Topic
 New
 Locked
 Sticky
 Active
 New/Active
 New/Locked
 New Sticky
 Locked/Active
 Active/Sticky
 Sticky/Locked
 Sticky/Active/Locked
Concord Technology TargetFax FoIP Faxing Solutions cisco_logo Microsoft FoIP Fax Parnter
etherfax-180px DiaLogic FoIP Faxing Solutions Faxcore FoIP Faxing Solutions One Touch Global Technologies FoIP Faxing Solutions
babyTEL-logo_BLUE-Sml Open Text FoIP Faxing Solutions XMediusFAX FoIP Faxing Solutions logo-kofax