Bowl Workflows - Traveling with a Server

Traveling with Server to Bowl Site: Using Full Thunder Network

Use Case: If your coaching staff feels they need full access to their server like they have at home, then a travel server can be utilized. This workflow will involve more moving parts for the preparation and setup.  Also consider the RXIMP Workflow, which is the recommended workflow to share edits in travel mode without the need to setup server environments.

Prep Before Departure:

Media Migration: Media will need to be copied to the DB server traveling to the bowl. 

Option 1: 

• On the DB server, launch Catapult Server AdminTool.  

• Select Media servers to Copy from. 

• Right-click assets to copy and select "Copy To" and choose the server going to the Bowl       

Option 2: 

• On a Thunder Client with Thunder launched, click on Thunder HD in the upper left of the program. 

• Select Administration 

• Select Asset Management 
• Select Media Servers to Copy from, allow the assets to load. 

• Right click assets to copy and select "Copy To" and select the DB server that will be going to the Bowl site.

Hotel Requirements: Ahead of travel, you will want to ensure the hotel has sufficient network infrastructure to handle the requirements of a Thunder Server Setup. 

Attached is our full hotel check list which we recommend you share with the hotel. 

A few important points to ensure are: 

• Private Dry VLAN capability with at least 1gb connection
• Ethernet ports in any meeting room needing Thunder connection
• Internet connection speeds sufficient for ThunderCloud media push and TC Sync (at least 100mbps)

Meeting Room Essentials: 

• Multi-port 1GB switches for meeting rooms with multiple laptops (Staff Rooms, Video Office, etc) 
• Ethernet cords (multiple length options) 
• Extension cords
• Docks and/or laptop power supply

On Site: 

Thunder Network Setup:

• Plug Server into a designated location with ethernet connection. (Recommendations and Requirements for this location are in the Hotel Checklist document above)
• Test each port in meeting spaces to confirm connectivity
• Catapult Rep who was assigned to your scheduled migration will get logged in remotely and begin DB migration
• iPerf testing to confirm connection speed is at least 1GB
• On all client machines, Open Exchange Agent and select Options. 

• Select Replication and change the Publisher to the name of your travel server. Click OK

• If anyone did work while in Travel Mode pointed to the server at home, you will need to XIMP (NOTE: not RXIMP) any work out while still in travel mode and import it to the Bowl site environment.

(Note: DO NOT drop and create a new subscription until all work from the laptop has been recovered. Once there is a new subscription, the work is lost if not already recovered via XIMP) 

• Test Travel Mode Sync and Media Surge to ensure there are no firewall limitations. 

TC Setup: 

Two Options, bring your transcode server from home, or convert a laptop to a TC Server

• Catapult Rep configures TC Server or Laptop to run in your bowl environment
• VC workflow does not change. Push to cloud as you would at home

Checklist: 

Pre Departure: 

• Media Migration to Travel server (This will take days/weeks depending on how much media is needed)
• Set up scheduled time with Support to get DB backed up and copied to the travel environment
• Pack ethernet cables needed for as many meeting rooms and offices as needed
• Pack as many 1gb switches as needed for rooms with multiple laptops being used
• Speak with Hotel IT and ensure connection speed is at least 1gb 
• Share the network topography with hotel IT to ensure dry VLAN is possible with their infrastructure
• Ensure the Hotel has an appropriate location for the server
• Put machines into travel mode before departure in the event coaches want to work in transit and attempt to recover the work at the bowl site
• Stop and Disable TC Sync Service at home. Remove the IP from Cloud Settings Manager

Arrival: 

• XIMP (Not RXIMP) any work done in travel mode. This work will not sync back to the travel server publisher. 
• After all work is saved via XIMP, drop the subscription and change the publisher to the travel server
• Create new subscription 
• Run iPerf testing in every room to ensure network connection speed
• Set up TC server, or have a time scheduled with support to have TC Server set up in the new environment

Returning Home:

• Setup Time with Support to remote in and backup DB to restore at home
• Power down and disable TC Sync at the Bowl site 
• Re-enable TC Sync at home
• Put all machines in travel mode to edit the game and allow coaches to work on the trip home
• XIMP out any work done in travel mode to recover it back home
• After all work is recovered, drop subscription, add the home server into the Publisher
• Copy media off of the travel server to the home servers via AMS workflows