Redundancy

From ThinManager Knowledge Base
Jump to: navigation, search

ThinManager Ready thin clients need to connect to a ThinManager Server to receive its firmware and configuration as part of the boot process. If the ThinManager Server fails, the ThinManager Ready thin clients will continue to run as they are not dependent on ThinManager.
If these thin clients are rebooted while the ThinManager Server is down, however, the thin clients will be unable to download the firmware and configuration, and will wait until the ThinManager Server is restored before proceeding.
Because of this, using a second redundant ThinManager Server is a common form of insurance. There are 3 types of redundancy:

  • Single ThinManager Server (No Redundancy)- If a system has a single ThinManager Server all the terminals will boot from that computer, receive their configuration, then connect to the assigned terminal servers. If the ThinManager Server fails the terminals will continue to function as designed. If they reboot, however, they will be unable to connect to the failed ThinManager Server and will not receive their configuration or connect to a terminal server.
  • Fully Redundant ThinManager Servers - If the system has two ThinManager Servers that are synchronized with the same configuration the thin clients can be configured to point to either ThinManager Server to receive their configuration. If the first ThinManager Server has failed a rebooted thin client can connect to the backup ThinManager Server and receive the proper configuration and connect to the proper terminal servers.

Redundancy requires an identical license set on both ThinManager Servers. Each ThinManager Server is fully functional and can be used to change or configure the thin clients.

  • Mirrored Redundancy is a feature that allows a pair of ThinManager Server to be synchronized with the same configuration so the thin clients can receive their configuration from the backup if it goes down. Mirrored redundancy is less expensive than full redundancy but mirrored redundancy installs the second ThinManager Server as a headless server. It doesn't allow changes to be made to the configuration except from the primary ThinManager Server. If the primary ThinManager Server fails the thin clients can boot from the secondary ThinManager Server but the configuration cannot be changed until the primary ThinManager Server is returned to service.


Single ThinManager Server - No Redundancy

Single ThinManager Server - No Redundancy
Single ThinManager Server - No Redundancy
  • One set of licenses.
  • Thin Clients receive configuration from 1 ThinManager Server.
  • Configuration sends thin client to any number of terminal servers.
  • If the ThinManager Server fails the thin clients will continue running until they reboot.
  • If the ThinManager Server is not running when the thin client boot then thin clients cannot retrieve their configuration until the ThinManager Server is restored.

Mirrored Redundancy- Two ThinManager Servers

Mirrored Redundancy- Two ThinManager Servers
Mirrored Redundancy- Two ThinManager Servers
  • One set of Mirrored licenses.
  • Requires Auto-synchronization.
  • Thin Clients receive configuration from either ThinManager Server.
  • Management and control are limited to Primary ThinManager Server.
  • Configuration allows thin client to connect to any number of terminal servers.
  • Provides redundancy at a lower cost than full redundancy.
  • Configuration changes can be made only on the primary ThinManager Server. If it fails the thin clients are able to retrieve their configuration but configuration changes must wait until the primary ThinManager is restored.
  • If the ThinManager Server fails the thin clients will continue running until they reboot.
  • If the primary ThinManager Server is not running when the thin client boots then thin client will boot from the secondary ThinManager Server, retrieve the configuration, and connect to the terminal servers.

Full Redundancy - Two ThinManager Servers

Full Redundancy - Two ThinManager Servers
Full Redundancy - Two ThinManager Servers
  • One set of Redundant licenses or two sets of regular licenses.
  • Requires Auto-synchronization.
  • Thin Clients receive configuration from either ThinManager Server.
  • Management and control are available on either ThinManager Server.
  • Configuration allows thin client to connect to any number of terminal servers.
  • If a ThinManager Server fails, the other ThinManager Server will provide configuration.
  • The ThinManager configuration can be changed on either ThinManager Server at anytime.
  • If the ThinManager Server fails the thin clients will continue running until they reboot.
  • If the primary ThinManager Server is not running when the thin client boots then thin client will boot from the secondary ThinManager Server, retrieve the configuration, and connect to the terminal servers.
Personal tools
Namespaces

Variants
Actions
Navigation
Events
Toolbox