Video Screencast Help
Search Video Help Close Back
to help
New in the Rewards Catalog: Vouchers for "Symantec Technical Specialist" and "Symantec Certified Specialist" exams.

Client fail over

Updated: 29 Jul 2010 | 2 comments
masonda's picture
+1 1 Vote
Login to vote
This issue has been solved. See solution.

We have done a multi site workspace streaming deployment for a client but load balancing  is not deployed at all sites as the number of users is small at the branch offices.

is there any way to set a client to fail over to a backup or secondary remote streaming server in the event that the client cannot contact the  primary local server, so that it is transparent to the user

Comments

trb48's picture
01
Jul
2009
0 Votes 0
Login to vote

Good idea

I am not sure if this feature is supported. I have looked through my Streaming Console and haven't seen anything like it.

I like this idea. You should click on the "Ideas" tab and submit it into the folks at Symantec, 

balachandar_manimala's picture
14
Jul
2009
0 Votes 0
Login to vote

Answer

I guess you have setup a multinode environment without a failover. Please follow the steps below to configure the streaming servers for failover.

Say you have a primary server group with a streaming server and launch server. Then you installed another set of these servers on a different machine to act as a backup.

All you need to do is (if you have no hardware load balancer)

  • Login to the Symantec Worksapce Streaming Console.
  • Navigate to Console Setup->Server Group. Add a new Server Group.
  • Stop the AWE Streaming Server, AWE Launch Server and AWE Data Access Server (if any) on the back up server.
  • Navigate to Console Setup->Component. Add the back up front end servers (Streaming server/Launch Server and DA Server) to the new server group.
  • Navigate to Configuration->Server Group. Select Default Server Group.
  • Click on Configure.
  • Click on the External Address Tab.
  • Under Back Up Streaming Servers type the Host Name or IP Address of the Back Up Streaming Server and click on Add.
  • Under Back Up Launch Servers type the Host Name or IP Address of the Back Up Launch Server and click on Add.
  • Click on Save.
  • Similarly, Navigate to Configuration->Server Group. Select the new i.e. backup Server Group.
  • Click on Configure.
  • Click on the External Address Tab.
  • Under Back Up Streaming Servers type the Host Name or IP Address of the Streaming Server in the Default Server Group and click on Add.
  • Under Back Up Launch Servers type the Host Name or IP Address of the Launch Server in the Default Server Group and click on Add.
  • Click on Save.
  • Restart  all the streaming and launch servers.

Your front end failover is complete. To test the failover you may additionally perform the below:

  • Upload two packages and enable them on both the server groups.
  • Set the one package for online execution and the other as offline.
  • Login to a client machine and stream both the online and offline packages from the primary server.
  • Launch both the apps.
  • Log off from the client machine.
  • Stop the Streaming and Launch Servers on the default server group.
  • Login to the client machine again.
  • Launch the Streaming Agent GUI (by clicking on the tray icon).
  • All offline applications and online applications will launch without any glitches.
  • Say you want to stream a new package, click on the portal button and the user will be prompted to select one of the launch servers. The user would need to select the server which is up and start streaming the package.

Please let us know if you would need more details on this.

Cheers,
Bala