Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Next revisionBoth sides next revision
cloudappliance/highavailabilitysetup [2019_10_29 00:52] – stevencloudappliance:highavailabilitysetup [2021_06_18 09:22] – smeadmin
Line 1: Line 1:
 ===== SME File Fabric HA Setup "2 x 2" ===== ===== SME File Fabric HA Setup "2 x 2" =====
 +== last edited on Jun. 18, 2021 ==
 ==== Disclaimer ==== ==== Disclaimer ====
  
 The information in this document is provided on an as-is basis. You use it at your own risk.  We accept no responsibility for errors or omissions, nor do we have any obligation to provide support for implementing or maintaining the configuration described here.  Furthermore, we do not warrant that the design presented here is appropriate for your requirements.  The information in this document is provided on an as-is basis. You use it at your own risk.  We accept no responsibility for errors or omissions, nor do we have any obligation to provide support for implementing or maintaining the configuration described here.  Furthermore, we do not warrant that the design presented here is appropriate for your requirements. 
  
-SME designs, implements and supports HA File Fabric solutions for customers on a paid professional services basis.  For more information please contact sales@storagemadeeasy.com+SME designs, implements and supports HA (High Availability) File Fabric solutions for customers on a paid professional services basis.  For more information please contact sales@storagemadeeasy.com
  
 ==== Introduction ==== ==== Introduction ====
Line 76: Line 77:
 </code> </code>
  
 +<WRAP center round info 100%> 
 +Please note this information above was updated with the 2106 release of the File Fabric. Please see this [[cloudappliance/high-availability-cron|guide for further information]]. 
 +</WRAP>
  
 ==== Part II - Database Servers ==== ==== Part II - Database Servers ====
Line 97: Line 100:
  
 == crontab == == crontab ==
-You must also disable some jobs in crontab, these should only run on one application server. Again, as root on smesql01 and smesql02:+You must also disable some jobs in crontab. Again, as root on smesql01 and smesql02:
 <code> <code>
 # crontab -e -u smestorage # crontab -e -u smestorage
 </code> </code>
  
-Place a "#" infront of the seven jobs listed, when you are done, it should look like this:+Place a "#" in front of the lines to mirror the output below: 
 + 
 +``` 
 +MAILTO='' 
 +#Ansible: 
 +#* * * * * /var/www/smestorage/cron/scheduler_minute.pl 
 +#Ansible: #3 
 +#5 4 * * * /var/www/smestorage/cron/scheduler_daily.pl 
 +#Ansible: #2 
 +#* * * * * /var/www/smestorage/cron/taskmanager.pl 
 +#Ansible: #5 
 +#10 2 1 * * /var/www/smestorage/cron/scheduler_monthly.pl 
 +#Ansible: #4 
 +#5 * * * * /var/www/smestorage/cron/scheduler_hour.pl 
 +#Ansible: #7 
 +30 1 * * * /var/www/smestorage/cron/logroller.pl 
 +#Ansible: #6 
 +#10 * * * * /var/www/smestorage/cron/scheduler.pl 
 +* * * * * /var/www/smestorage/cron/scheduler_syncnodes.pl 
 +```
  
-{{::407ae286-9576-4a13-97bb-e2f0489a2a17.png?400|}}+<WRAP center round info 100%> 
 +Please note this information above was updated with the 2106 release of the File Fabric. Please see this [[cloudappliance/high-availability-cron|guide for further information]]. 
 +</WRAP>
  
 === iptables for dbservers === === iptables for dbservers ===
Line 405: Line 429:
  
 ==== Part III - Application Servers ==== ==== Part III - Application Servers ====
 +
 +<WRAP center round important 100%>
 +If you will be using a load balancer to distribute traffic to your web servers, configure the load balancer to provide session stickiness.
 +</WRAP>
  
 === Configure the application servers === === Configure the application servers ===
Line 456: Line 484:
  
 == crontab == == crontab ==
-You must also disable crontab on the smeweb02 server, crontab should only run from one application server.+The majority of smestorage's cron jobs should run on one of the application servers; only one of smestorage's cron jobs, logroller, should run on the other  application server.
 **As root on smeweb02 only:** **As root on smeweb02 only:**
 <code> <code>
Line 462: Line 490:
 </code> </code>
  
-Place a # in front of the seven jobs listed in the crontab schedule. For a screenshot, refer to the DB section above.+Your crontab should mirror the following: 
 + 
 +``` 
 +MAILTO='' 
 +#Ansible: 
 +#* * * * * /var/www/smestorage/cron/scheduler_minute.pl 
 +#Ansible: #3 
 +#5 4 * * * /var/www/smestorage/cron/scheduler_daily.pl 
 +#Ansible: #2 
 +#* * * * * /var/www/smestorage/cron/taskmanager.pl 
 +#Ansible: #5 
 +#10 2 1 * * /var/www/smestorage/cron/scheduler_monthly.pl 
 +#Ansible: #4 
 +#5 * * * * /var/www/smestorage/cron/scheduler_hour.pl 
 +#Ansible: #7 
 +30 1 * * * /var/www/smestorage/cron/logroller.pl 
 +#Ansible: #6 
 +#10 * * * * /var/www/smestorage/cron/scheduler.pl 
 +* * * * * /var/www/smestorage/cron/scheduler_syncnodes.pl 
 +``` 
 + 
 +<WRAP center round info 100%> 
 +Please note this information above was updated with the 2106 release of the File Fabric. Please see this [[cloudappliance/high-availability-cron|guide for further information]]. 
 +</WRAP>
  
 Restart both servers, so on both smeweb01 and smeweb02, execute a reboot. Restart both servers, so on both smeweb01 and smeweb02, execute a reboot.
© Copyright 2024 Nasuni.