gui:architecture
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| gui:architecture [2023/12/03 11:59] – [Complex Deployment Farm] emcodem | gui:architecture [2026/02/28 20:50] (current) – [Multiple Servers + NAS] emcodem | ||
|---|---|---|---|
| Line 10: | Line 10: | ||
| ===== Typical Scenarios ===== | ===== Typical Scenarios ===== | ||
| - | {{gallery>: | + | {{:gui: |
| - | ==== Simple Deployment Single Server | + | ==== Local Machine |
| You can run FFAStrans on a standalone PC without the need for further Hard- and Software. In this case the installation files and Media files are on the local drives of your PC. | You can run FFAStrans on a standalone PC without the need for further Hard- and Software. In this case the installation files and Media files are on the local drives of your PC. | ||
| Line 19: | Line 19: | ||
| - | ==== Common Deployment Single Server | + | ==== PC + NAS ==== |
| If you have one or multiple NAS Servers where your Media files come from and go to but still only one Server that runs FFAStrans, make sure that: | If you have one or multiple NAS Servers where your Media files come from and go to but still only one Server that runs FFAStrans, make sure that: | ||
| Line 27: | Line 27: | ||
| - | ==== Complex Deployment | + | ==== Multiple Hosts (Farm) + NAS ==== |
| - | If you need more than one server/host to take care about your workflows, you can utilize FFAStrans farming abilities. | + | If you need more than one server/host to take care about your jobs, you can utilize FFAStrans farming abilities. |
| FFAStrans runs in an **Active-Active** Pattern. This means that there is no "Main Server" | FFAStrans runs in an **Active-Active** Pattern. This means that there is no "Main Server" | ||
| - | How it works is that you just place the FFAStrans installation directory on the SMB Server - let us call it **Quorum** - with the highest availability possible. | + | How it works is that you just place the FFAStrans installation directory on the SMB Server - let us call it **Database Share** - with the highest availability possible. |
| - | === How to choose Quorum Location === | + | This means that the FFAStrans.exe App needs to be started from a UNC Path on every host (especially before installing the Service) |
| + | * In a Farm Environment, | ||
| + | * Example: \\FFASTRANSDB\FFAStrans\FFAStrans.exe | ||
| - | As described above, the Quorum | + | === How to choose Database Share Location === |
| - | The Quorum | + | |
| + | |||
| + | As described above, the Database Share is a Windows Share location that contains the FFAStrans installation Files when running a transcoding farm (or better processing Farm). | ||
| + | The Database Share will only contain minimal amounts of data, e.g. control files and log files. In difference to the cache location that contains temporary per job working files. You can see the Database Share as the database. | ||
| Private persons and small companies are recommended to elect one of the servers in the farm to the " | Private persons and small companies are recommended to elect one of the servers in the farm to the " | ||
| - | For larger setups we strongly recommend to set up a small Windows VM that does nothing but serve a share for the ffastrans installation files. Setups with Linux SMB and similar often lead to problems. | + | For larger setups |
| + | |||
| + | === Networking === | ||
| + | |||
| + | In Farm Setups, it is recommended to have a separate " | ||
| + | The reason for this is that when a Network Card/Cable is utilized for Media Transfer, the Latency for File access on this network raises from milliseconds to many seconds. This can cause different issues like Webinterface " | ||
| + | {{: | ||
| --------------------------------------------- | --------------------------------------------- | ||
gui/architecture.1701604770.txt.gz · Last modified: 2023/12/03 11:59 by emcodem