...
Currently, DU does not support an active-active or an active-passive High Availability configuration. This means that DU is not designed to be run concurrently on two servers for high availability purposes, and there is no built-in functionality for automatic failover or files synchronization (generated JSON / CSV) between servers. In the event that the primary server running DU fails, the service will not automatically resume on a secondary server. Furthermore, because there is no automatic synchronization of files or processing states, if you were to start DU on a secondary server after a failure, it would not continue from where the primary server left off uploading generated files. If the client chooses to use high availability on the database level from SQL, they can use that option.
SQL can be High availability by adding a SQL failover cluster with at least two nodes, checking the Enable always on availability groups and adding a listener.
...
Can multiple users log into the DataUploader server to view jobs?
...