At line 1 changed 4 lines |
ServerBeat is a special protocol that will dynamically assign the specified IP between multiple CrushFTP servers. You specify an IP that is free for your Virtual IP. You then set any NAT port mapping or DNS records to point to that IP. The CrushFTP instances that are running configured for that virtual IP via ServerBeat will share the IP. Only one machine will have the IP at any time, and it will hold onto it unless its powered off. In that case, within just a few seconds, the other CrushFTP server will take over and start using the IP. |
|
This is ideally suited for two machines in a failover scenario, but it could be used on 3 or 4 if you really wanted to. Still only one machine is active at any time. When Crush changes the IP, its changing it in the OS. Technically its assigning an IP alias for the machine. |
|
ServerBeat is a special protocol that will dynamically assign the specified IP between multiple CrushFTP servers. You specify an IP that is free for your Virtual IP. You then set any NAT port mapping or DNS records to point to that IP. The CrushFTP instances that are running configured for that virtual IP via ServerBeat will share the IP. Only one machine will have the IP at any time, and it will hold onto it unless its powered off. In that case, within just a few seconds, the other CrushFTP server will take over and start using the IP.\\ |
\\ |
This is ideally suited for two machines in a failover scenario, but it could be used on 3 or 4 if you really wanted to. Still only one machine is active at any time. When Crush changes the IP, its changing it in the OS. Technically its assigning an IP alias for the machine.\\ |
\\ |
We __only support two Priority levels__, a primary and a non-primary node. As long as the primary is live, it will run the Jobs, until it goes down, then another of the non-primary nodes will take over. The Priority numbers should be , for example 200/100/100 in a 3-node cluster, and not 100/150/200, adding a 3rd level means serverbeat randomly does whatever and restricts nothing.\\ |
\\ |
At line 10 added one line |
[{Image src='sb_1.jpg' width='1440' height='..' align='left' style='..' class='..' }] |
At line 9 removed 3 lines |
[attachment|serverbeat.png] |
|
|
At line 13 changed one line |
If you plan on running the CrushFTP instances as a non SYTEM user on the machine, you need to configure access rights to allow it to be able to issue its netsh commands.\\ |
If you plan on running the CrushFTP instances as a non SYSTEM user on the machine, you need to configure access rights to allow it to be able to issue its netsh commands.\\ |
At line 16 changed 4 lines |
In order to ensure that the CrushFTP service on Windows can properly handle updates to the product while running as a low-privilege service account, users should configure the CrushFTP services in the following way: |
|
Service Accounts |
|
If you need to run a job only on one side of the cluster then replace the VIP with the "job", and then it will run only on the machine configured.\\ |
[attachment|serverbeat1.png] |
|
In order to ensure that the CrushFTP service on Windows can properly handle updates to the product while running as a low-privilege service account, users should configure the CrushFTP services in the following way:\\ |
\\ |
Service Accounts\\ |
\\ |
At line 29 changed 3 lines |
|
[attachment|settings.png] |
|
\\ |
[attachment|settings.png]\\ |
\\ |
At line 42 added 9 lines |
---- |
You can customize the commands CrushFTP uses by modifying the prefs.XML for the following fields:\\ |
{{{ |
serverbeat_command: /sbin/ifconfig {adapter}:{index} {ip} netmask {netmask} up |
serverbeat_command_disable: /sbin/ifconfig {adapter}:{index} {ip} netmask {netmask} down |
serverbeat_ifup_command: /sbin/ifup {adapter}:{index} |
serverbeat_ifdown_command /sbin/ifdown {adapter}:{index} |
serverbeat_post_command: #used for things like arping to make a router learn a new MAC of the new owner of the vip. |
}}} |