Backup copy of server?

[crusher11 1101]

Is it possible to have a backup copy of my server running on a different machine, so that if my server machine ever goes down the server itself will stay up in some form?

I've just got a NAS, and it's not good enough to handle most, or perhaps any, transcoding so the server itself is still running on my PC. But it would be good to have emby on the NAS as well so if my PC is shut down for whatever reason the server is still accessible even if not fully featured.

 

@@cayars

[Lhreaper 2]

Is it possible to have a backup copy of my server running on a different machine, so that if my server machine ever goes down the server itself will stay up in some form?

 

I've just got a NAS, and it's not good enough to handle most, or perhaps any, transcoding so the server itself is still running on my PC. But it would be good to have emby on the NAS as well so if my PC is shut down for whatever reason the server is still accessible even if not fully featured.

If you are running nginx, you could setup a fallover server.

 

Sent from my SM-G960U using Tapatalk

[crusher11 1101]

I am, but I have no idea what that means or how to go about it. Also, it would only work remotely right?

Edited April 23, 2020 by crusher11

[Lhreaper 2]

I will put together an example for you in a little bit.

 

Sent from my SM-G960U using Tapatalk

[rbjtech 5284]

It really depends on whether you want it 'seemless' or if a quick re-config on the client is acceptable.  If 'seemless', then you basically need something 'in-front' of the two devices to act as a gatekeeper - options range from a simple DNS round robin type approach, to full load balancing.  If you just want the option of using both but manual intervention is fine - then just setup your clients with server options for both.  I believe your license, as long as it's in the same home, will extend to both machines without issues.

 

As I use local DNS (and clients point to a DNS name as opposed to an IP) - If I ever wanted to use my backup server, I would just change the DNS record to point to the new IP address, no need to change any local or remote clients.

Edited April 23, 2020 by rbjtech

[crusher11 1101]

I am, but I have no idea what that means or how to go about it. Also, it would only work remotely right?

Plus NGINX is running on the PC that would be down in this hypothetical...

[pir8radio 1312]

Plus NGINX is running on the PC that would be down in this hypothetical...

 

Then what he was talking about wouldnt work for you...    nginx can run on a Raspberry Pi but I have not tested performance (the RPi 4 might work well)... I would'nt do it, it also runs on some NAS devices.  nginx is probably the easiest way to fail-over.    

But he was going to tell you something like this:

upstream backend {
    server 192.168.1.10:8096;
    server 192.168.1.20:8096   backup;

}

server {
    location / {
        proxy_pass http://backend;
    }
}

Edited April 27, 2020 by pir8radio

[crusher11 1101]

I don't have a Pi, I'm not entirely sure what one even is. I'm running a DS1819+, can I run NGINX off that?

 

Apparently it should be capable of transcoding, despite the Plex NAS guide saying otherwise, so if that's the case I'd rather shift the whole server over to the NAS really.

[pir8radio 1312]

I don't have a Pi, I'm not entirely sure what one even is. I'm running a DS1819+, can I run NGINX off that?

 

Apparently it should be capable of transcoding, despite the Plex NAS guide saying otherwise, so if that's the case I'd rather shift the whole server over to the NAS really.

 

I dont know much about it, but quick reading says nginx is already on that DS1819+ ?         a Raspberry Pi is pretty cheap like 35-60 bucks (US) with a case and, its just a little low power computer...   https://www.pishop.us/product/raspberry-pi-4-model-b-2gb/?src=raspberrypi

 

nginx on Raspberry Pi:

https://www.raspberrypi.org/documentation/remote-access/web-server/nginx.md

Edited April 28, 2020 by pir8radio

[crusher11 1101]

I mean, I already have the NAS, seems silly to buy yet another machine.

 

So, how would I go about running the NGINX thing on my NAS and shifting my domain etc over to that server?

[pir8radio 1312]

I mean, I already have the NAS, seems silly to buy yet another machine.

 

So, how would I go about running the NGINX thing on my NAS and shifting my domain etc over to that server?

 

I dont use synology or have one to test on, but this guy says nginx is already installed, i guess its what serves the nas management web pages...   If so you can just add your emby reverse proxy configs into the synology and change your port forwards from the router..  But keep in mind you will need to put some security in that synology config to hide that interface from the internet users,  maybe move the synology "server" section to listen on a different port other than 80 and 443...

 

https://primalcortex.wordpress.com/2018/05/07/synology-reverse-proxy-revisited-again/

[crusher11 1101]

So I tried this and...broke everything. I can't even get to my server via my IP and the PC server's port (I used different ports for the NAS server so I could run both). Halp!

[pir8radio 1312]

uh oh..  what does your nginx config look like now?   do you know what it looked like before?      maybe @@Luke knows who uses synology on here that can help with that part?

on the plus side, sounds like you DO have nginx on the nas! 

 

OH I just re-read your post, you cant get to emby?   or you cant get to the nas?    Can you explain what you tried to do,  like changed emby port to XX changed firewall to XXX  did this in the nas.....

Edited April 30, 2020 by pir8radio

[crusher11 1101]

I copied my Windows config (which still works, if I run NGINX on the PC I can access my server but if I stop it and run NGINX on the NAS it times out), and changed the port numbers, local IP and the location of the logs/certs. That's it.

 

The Windows config was just your config minus that thing adding it to always-redirect-to-HTTPS lists or whatever it was, I forget the name at the moment.

[crusher11 1101]

Okay, turns out I had a Docker issue, and I can now access my Emby server via IP:PORT. The domain still gives a 522 error, however.