Non-High Availability Mode vs. High Availability Mode

Function

Non-High Availability mode

High Availability mode

Startup

Searches for configuration, tries backup files to handle broken configuration, etc. Always creates "clean" configuration if none is loaded.

Loads only the configuration files from the shared location. Creates "clean" configuration only if no configuration present. Fails to start if cannot load configuration.

Shutdown

Updated configuration with latest settings

Does not update configuration.

Authentication managers

GS, NTAD, ODBC, LDAP

Globalscape, NTAD, and LDAP

User database refresh

Allowed

Not allowed

PCI cleanup (administrator/ user remove/ disable for inactivity and send password expiration notifications)

Nightly timer

+ Every time server deals with user/administrator (user/administrator connection, exposing user/administrator to GUI/COM etc.)

Nightly timer

Client Expiration

Every time when server deals with user (user connection, exposing user to GUI/COM etc.)

Nightly timer

Turning off Autosave and using "ApplyChanges" via COM

Allowed

Not allowed

GUI/COM connection

Always allowed

Only one node at a time is allowed to serve GUI/COM connection

Saving changes made by administrator to FTP.CFG

Background task accumulating changes and saving settings

Only one node can be administered at a time. As soon as you log off of the node on which you've made changes and then log on to second node, those changes would be updated on the second node.

Server restore from backup

Allowed

Allowed

Trial state

Registry

Registry

OTP passwords for clients

Allowed

Not allowed

Legacy password hashes

Allowed

Not allowed

User lock state

Continues after service restart

Breaks after service restart

Invalid login history

Continues after service restart

Resets on service restart