There is not as much to do with FTP. There are only a handful of protocol options which will need to be in sync. FTP is system zone only so only the SmartConnect Zones associated with the System Zone apply. Those zones would need to be updated to point to the other cluster just as your SMB clients so if Superna helps make that work for SMB, it will work for FTP as well.
If you fail over, any active FTP connection will fail and will have to be restarted. But the restart should request a new IP address so once DNS is set properly, it should receive an address on the remote side and so it should continue..again like SMB2.
Superna eyeglass can manage zero touch failover of FTP smartconnect zones today (for system zone) and using Dual delegation feature in your DNS (setup before hand), the failover will move the smartconnect zone to the remote cluster AND no DNS changes are need at all (works for SMB and NFS as well). All the data SyncIQ steps are automated in this use case by Eyeglass now.
We also have pre and post failover scripting so you could shutdown application start failover, make target cluster writeable, smartconnect zone failover, DNS dual delegation handles no DNS updates etc.... and restart application with a single button.
We also offer full rest API to launch failover as per above as well. In addition we offer a curl builder that allows you to navigate the API and have the GUI generate the CURL command need to launch the entire automation above.
This does leave one item remaining which is local users, which are not synced between clusters today, assuming they were synced, the password can not be synced. We could look at enhancement to sync local users but set to random password on sync or some other solutions (passwords are a problem to sync in general).
AdamFox
254 Posts
0
April 12th, 2016 13:00
There is not as much to do with FTP. There are only a handful of protocol options which will need to be in sync. FTP is system zone only so only the SmartConnect Zones associated with the System Zone apply. Those zones would need to be updated to point to the other cluster just as your SMB clients so if Superna helps make that work for SMB, it will work for FTP as well.
If you fail over, any active FTP connection will fail and will have to be restarted. But the restart should request a new IP address so once DNS is set properly, it should receive an address on the remote side and so it should continue..again like SMB2.
Newday3000
57 Posts
0
April 12th, 2016 16:00
Hi kvfestorage,
Superna eyeglass can manage zero touch failover of FTP smartconnect zones today (for system zone) and using Dual delegation feature in your DNS (setup before hand), the failover will move the smartconnect zone to the remote cluster AND no DNS changes are need at all (works for SMB and NFS as well). All the data SyncIQ steps are automated in this use case by Eyeglass now.
We also have pre and post failover scripting so you could shutdown application start failover, make target cluster writeable, smartconnect zone failover, DNS dual delegation handles no DNS updates etc.... and restart application with a single button.
We also offer full rest API to launch failover as per above as well. In addition we offer a curl builder that allows you to navigate the API and have the GUI generate the CURL command need to launch the entire automation above.
This does leave one item remaining which is local users, which are not synced between clusters today, assuming they were synced, the password can not be synced. We could look at enhancement to sync local users but set to random password on sync or some other solutions (passwords are a problem to sync in general).
video on curl to failover with embedded eyeglass scripting and API
rest API overview with curl builder tool
If you want a demo or deeper discussion on how eyeglass can be used for your FTP failover use case, let me know.
You can email me at andrew.mackay@superna.net
Regards
Andrew
kvfestorage
1 Rookie
•
2 Posts
0
April 13th, 2016 11:00
Thanks very much for the answers!