Want to get a second OMV box for hardware transcoding (advice needed)

I am using a rockpro64 but basically hardware transcoding is not possible I ran into this guide https://forums.serverbuilds.ne…icksync-and-nvenc/1408and I am really interested to go this way since Intel with its quiksync look like the way to go.

So they are two options, just get an hp prodesk mini,micro or similar and share my hard dives between the two OMV boxes (not sure yet how to do that with mount point etc..) or get rid of the arm OMV and get a bigger intel desktop where I could attach my drives, but I am pretty sure I prefer the first option in term of purchase cost, energy,noise and redundancy since I got 2 systems instead of one so I really need advice from the experts about what to do ?

Well I got 1 or 2 clients outside I think they do transcode maybe subtitle use? Where is this function in emby for managing non-realtime "transcoded" files?

so my data are in ext4 so is it imperative to use NFS ? I definitely read remote mount plugin with offline drives Just kind of late right now.

any recommendation in term of x86 box?

So just to make sure I have got to reformat my data drive (ext4-movies) to NFS in order to be able to share it between two omv?

Zitat von gderf

No.

So why do I need NFS in this case?

Sorry did not see the reply from ryecoaaron i think I got it now!

NFS services was always in front of my eyes nevever pad attention to it LOL!

Well I am wondering about my letsencrypt Certificate cant it be use on the second OMV (NFS sharing) since I have only one domain for all my app using wildcard or should I get an extra domain from duckdns and add an other docker for letsencrypt also I read than Hardware transcoding is not really supported from container any info bout that?

Zitat von johnvick

What you can do is have the cert on one device and use its webserver to forward certain addresses to the second device

let's say I have got emby.xmydomainx.duckdns.org going to192.168.2.30 how exactly I forward the certificate to 192.168.2.45, is it from the emby.subdomain.conf I assuming by changing this line proxy_pass http://192.168.2.30:8096; by proxy_pass http://192.168.2.45:8096;

Is there a way to keep two emby.subdomain.conf with 2 addresses in case I want to go back to the other OMV?

server {
    listen 443 ssl;

    server_name emby.my-domain.*;

add_header X-Robots-Tag "noindex, nofollow, nosnippet, noarchive";
    include /config/nginx/ssl.conf;

    client_max_body_size 0;

    location / {
        include /config/nginx/proxy.conf;
        resolver 127.0.0.11 valid=30s;
        set $upstream_emby emby;
        proxy_pass http://192.168.2.30:8096;
        proxy_set_header Range $http_range;
        proxy_set_header If-Range $http_if_range;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "upgrade";
    }
}

Regarding NFS and pardon my ignorance sine in the meantime I am testing from192.168.2.30 to on an old i386 computer I enabled NFS on both, I made a share for my media with access to the client 192.168.2.167/24 I gave RW extra option says subtree_check,insecure but so far I cannot see the share folder on the remote OMV

can it be done from the GUI or should I use the CLI?