Using external database

In this section, we describe a new way to setup TSS application in our Virtual Appliance by externalizing databases.

In this mode, the management of the entire database is not managed locally on a MySQL server running into the Virtual appliance anymore. Instead, the administrator gets to use the full management capacity of one of its database server instances, and can use it to run several TSS firmware in parallel.

One direct impact on the runtime is that the Virtual Appliance does not spend any CPU cycle or IO for running a local database engine anymore, which means the TSS should be able to manage more turrets per instance and use less disk bandwidth.  Furthermore, the administrator is also free to optimize its database server runtime and hardware to realize its full potential.

Another advantage in this mode is the capacity to deploy from one to six TSS instances targeting the same database, where the classic VA setup limits itself to two replicated nodes.

Finally, once you have setup a primary node, nothing will prevent the addition or removal of a secondary node at any point in time, which offers more flexibility than a class VA setup.