+ Post New Thread
Results 1 to 11 of 11
Thin Client and Virtual Machines Thread, Fail-Proof client-server architecture for thin client systems. in Technical; Dear Techs, Thin clients bring about incredible security which inturn cuts down on it support cost and increased up time ...
  1. #1

    Join Date
    Nov 2010
    Location
    Cambridge
    Posts
    14
    Thank Post
    0
    Thanked 0 Times in 0 Posts
    Rep Power
    0

    Fail-Proof client-server architecture for thin client systems.

    Dear Techs,

    Thin clients bring about incredible security which inturn cuts down on
    it support cost and increased up time and hence you have greater worker productivity as a result. And the benefits keep going with time.

    Isnt that wonderful new.

    But as we all know there is a singlepoint of failure which could affect every user.

    I would like to know what methods are used in best practise that counter this problem that is posed by thin client - fail proof client-server architecture.

    Your contributions will be greatly appreciated.

  2. #2
    Duke's Avatar
    Join Date
    May 2009
    Posts
    1,017
    Thank Post
    300
    Thanked 174 Times in 160 Posts
    Rep Power
    57
    Okay, I'll bite:

    Redundant SANs in separate locations on site. These are synchronously mirrored and have redundant, high-speed links. The SANs themselves have redundant hardware, power feeds to each PSU come from different supplies and different PDUs. You also have power generation facilities on-site in the case of a site-wide power outage. RAID with a high level of redundancy is used for the disks and each SAN has clustered heads with instant failover support. The SANs are used to store the thin client virtual machine images and VMware (or similar) clusters are used to host these virtual machines. The VMware clusters have failover and Fault Tolerance for instant failover in the case of a host failing, and the two groups of clusters are in different locations on site with redundant links so that one entire cluster can fail over to the other. All your edge locations with thin clients have redundant links back to the core and these are configured to failover automatically in the case of a switch failure.



    Your virtual machine images are backed-up and uploaded to cloud-based storage and a cloud-based VMware instance, your have a redundant, high-bandwidth VPN connection to this and hardware at your end that will route the connections over the internet to present the cloud-based thin client images directly to your thin clients.

    Now all you need is several million pounds.
    Last edited by Duke; 25th November 2010 at 10:07 AM.

  3. #3
    budgester's Avatar
    Join Date
    Jan 2006
    Location
    Enfield, Middlesex
    Posts
    486
    Thank Post
    4
    Thanked 37 Times in 30 Posts
    Rep Power
    24
    Which single point of failure are you talking about ?

    Power ? Networking ? Only using a single Terminal Server (Which would be braindead for an amount of users over 10).

    Are you looking to implement, have implemented, can you give us more info ?

  4. #4
    budgester's Avatar
    Join Date
    Jan 2006
    Location
    Enfield, Middlesex
    Posts
    486
    Thank Post
    4
    Thanked 37 Times in 30 Posts
    Rep Power
    24
    Quote Originally Posted by Duke View Post
    Now all you need is several million pounds.
    Your not really taking into account Kim Jong Ill, Apparently he has nuclear weapons and is a bit unbalanced, so I don't think this will continue to work through a nuclear war.

    Yup, Kim is definately the single point of failure.

  5. #5
    Duke's Avatar
    Join Date
    May 2009
    Posts
    1,017
    Thank Post
    300
    Thanked 174 Times in 160 Posts
    Rep Power
    57
    Quote Originally Posted by budgester View Post
    Your not really taking into account Kim Jong Ill, Apparently he has nuclear weapons and is a bit unbalanced, so I don't think this will continue to work through a nuclear war.

    Yup, Kim is definately the single point of failure.
    Hmm, good point. Okay, the cloud is hosted in either North Korea (they won't blow themselves up, but USA might I guess) or Sweden (no one messes with Sweden).


  6. #6

    dhicks's Avatar
    Join Date
    Aug 2005
    Location
    Knightsbridge
    Posts
    5,623
    Thank Post
    1,240
    Thanked 777 Times in 674 Posts
    Rep Power
    235
    Quote Originally Posted by johno View Post
    But as we all know there is a singlepoint of failure which could affect every user.
    How do you mean, exactly - the network connection, or the server? You can simply have multiple servers for your thin clients - if one fails, the load simply gets distributed to ther other server(s).

    --
    David Hicks

  7. #7

    Join Date
    Nov 2010
    Location
    Cambridge
    Posts
    14
    Thank Post
    0
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    I basically mean the server, if it has to fail there should be a secondary dns server with redunadant data
    Or something this is what I mean!

  8. #8

    Join Date
    Nov 2010
    Location
    Cambridge
    Posts
    14
    Thank Post
    0
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    I only have twenty five users on my network so its pretty small! I don think it will be that complicated.

  9. #9

    dhicks's Avatar
    Join Date
    Aug 2005
    Location
    Knightsbridge
    Posts
    5,623
    Thank Post
    1,240
    Thanked 777 Times in 674 Posts
    Rep Power
    235
    Quote Originally Posted by johno View Post
    I basically mean the server, if it has to fail there should be a secondary dns server with redunadant data
    Failover between two servers is easy enough - just use DRBD or similar to mirror VM disk images between two physical machines.

    --
    David Hicks

  10. #10

    Join Date
    Nov 2010
    Location
    Cambridge
    Posts
    14
    Thank Post
    0
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    thanks dhicks, by vm u mean virtual machines right? im really new to this concept btw.

  11. #11

    dhicks's Avatar
    Join Date
    Aug 2005
    Location
    Knightsbridge
    Posts
    5,623
    Thank Post
    1,240
    Thanked 777 Times in 674 Posts
    Rep Power
    235
    Quote Originally Posted by johno View Post
    thanks dhicks, by vm u mean virtual machines right? im really new to this concept btw.
    Yes, sorry - VM == Virtual Machine. Each virtual machine running on a physical server will need somewhere to store its data - when the VM starts, it'll expect to have a harddrive available. In many cases this is done with a simple file, although in bigger systems designed for use by many users you might assign a VM an actual, physical harddrive or RAID array to itself, depending on just how much disk performance your VM needs.

    --
    David Hicks

SHARE:
+ Post New Thread

Similar Threads

  1. Multipoint Server 2011 and Axel 75 Thin Client
    By plexer in forum Thin Client and Virtual Machines
    Replies: 2
    Last Post: 4th November 2010, 11:07 AM
  2. Thin Client - Server 2008 - HP Blade System
    By daleybaxter in forum Thin Client and Virtual Machines
    Replies: 3
    Last Post: 11th June 2010, 10:57 AM
  3. Thin Client Server And Client OS
    By MicrosoftTechy in forum O/S Deployment
    Replies: 3
    Last Post: 3rd April 2010, 02:18 AM
  4. VNC on Edubuntu 9.04 Thin Client Server
    By dhicks in forum *nix
    Replies: 9
    Last Post: 16th September 2009, 03:17 PM
  5. Virtualisation of Thin Client Server
    By ndavies in forum Thin Client and Virtual Machines
    Replies: 13
    Last Post: 6th May 2008, 09:33 AM

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •