2
Smartermail Enterprise and failover
Question asked by Deepak Kaushal - 6/22/2021 at 6:29 AM
Answered
Greetings

we have recently take up smartermail  enterprise
 We are looking for setup  of   Smartermail enterprise where it provide failover 
setup too
in requiremenst it specify  SMB share too
we will be using ESxi Vmware for setting up Vms in environemnt
if it necessary to have  RAID10?
or normal  UNC share will work?

does this   mean
we can  have 2 severs  ,  setup NLB, install  smartermail


and create normal  UNC share on one of the server itself?
or  have  third windows server ?

also  is  failover   going to work  if   UNC share     is seup

or  NFS  or  SAN  volume required in windows  ?

we understand  Smartermail failover  is      only if first server fails then secondary server service can be started?




please advise all   setup tiosn other than NLB  also

as we will having these servers in production sooon

1 Reply

Reply to Thread
0
Kyle Kerst Replied
Employee Post Marked As Answer
Hello Deepak, I hope this comment finds you well. I wanted to provide some guidance on your queries here: 

if it necessary to have  RAID10 or normal  UNC share will work? <-- Which drive setup you choose is up to you. RAID will provide better reliability, but any UNC share should do the trick!


and create normal  UNC share on one of the server itself or have third windows server? 
<-- Typically this should be a third server which is dedicated to storage and both the primary and secondary SmarterMail servers should have full read/write access to it's shares.

we understand  Smartermail failover is only if first server fails then secondary server service can be started? <-- This is correct. SmarterMail works in a live/standby configuration, and the failover to your secondary server is scripted and implemented via Microsoft LB. 

I hope this helps point you in the right direction but let me know if you have any follow-up questions I can help with. Have a good one!
Kyle Kerst IT Coordinator SmarterTools Inc. www.smartertools.com

Reply to Thread