Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!


New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

VPS backup & restore

jeffsheadjeffshead Member
edited September 21 in Providers

I have a VPS with a provider that includes backup/restore functionality with the service.

For the first time, I restored an image and the result is a non-functioning server.

If a backup is taken of a fully functioning system, shouldn't the system be fully functional when that backup is restored?

I feel like I'm getting the run around because the provider states that the backup and restore were successful because the server boots and can be logged into. They said it's not their problem that the server is not functioning as it was when the backup was created.

Is this acceptable? What's the point of offering backups if you can't restore your server to a working state?

Comments

  • It depends on what exactly is broken and it depends on what type of backup it is.

    Backups (should) ensure that data is retrievable in case of a disaster.

    Backups do not necessarily contain system state and cannot take external factors into account (such as a change of IP), so it's not entirely unreasonable for there to be some work required (by the user) to bring the server back to an operational state.

    What exactly happened?
    What is and isn't working?
    Was there data lost?

  • jeffsheadjeffshead Member
    edited September 21

    @Dupondt said:
    What exactly happened?
    What is and isn't working?
    Was there data lost?

    I run Netbird on the VPS. I made several changes. Rather than undoing those changes, I restored a backup thinking it would save time. I do this all the time with the VM's on my LAN with Veeam B&R. It never lets me down.

    Getting a 404 when accessing the Netbird admin and none of the clients can connect.

    Not sure about data loss. Everything seems to be there.

  • So does OVHcloud or any other VPS provider include full snapshot copy of the entire system state so one can simply restore a backup and expect everything to be restored and functioning just as it was at the time of backup? If not, then what are the contributing factors as to why this cannot be done with VPS providers?

    I use Veeam B&R on my network and when I restore a VM, it restores the system to the working state of when the backup was taken. It always works. This can't be done with VPS providers?

  • kukara4kukara4 Member, Patron Provider

    Most likely the backup is fine, and docker or some service just didn't start after the restore. Check docker ps and the service status.

  • DupondtDupondt Member
    edited September 21

    If all the data is there, you probably just need to restart some services. IP change, time change, cache expiry, et cetera. I can think of lots of little reasons why it doesn't just work like a time machine.

    I don't think I've ever used a VPS backup the way you describe. I can see how intuitively it might seem like it should just work. But a backup doesn't necessarily work like that. I can see how restoring from a backup would still require user intervention to get it back to an operational state. Unless you're paying for a managed server, I don't think it's an unreasonable thing to expect the user to know how to do.

  • Thanks for all of the responses.

    This is actually the first time I've tried to restore a VPS backup. All of my backup/restore experiences have been with Veeam and server VM's on my LAN.

    Below is what I get on the VPS:

    [root@netbird ~]# docker ps
    CONTAINER ID   IMAGE                             COMMAND                  CREATED         STATUS                           PORTS                                                                          NAMES
    aa51245b4607   netbirdio/reverse-proxy:latest    "/go/bin/netbird-pro…"   3 minutes ago   Up 3 minutes                     8443/tcp, 0.0.0.0:51820->51820/udp, [::]:51820->51820/udp                      netbird-proxy
    8919e3b4a2d7   crowdsecurity/crowdsec:v1.7.7     "/bin/bash /docker_s…"   3 minutes ago   Up 3 minutes (healthy)                                                                                          netbird-crowdsec
    cb18ac31e80a   traefik:v3.6                      "/entrypoint.sh --lo…"   3 minutes ago   Up 3 minutes                     0.0.0.0:80->80/tcp, [::]:80->80/tcp, 0.0.0.0:443->443/tcp, [::]:443->443/tcp   netbird-traefik
    614fd212c890   netbirdio/dashboard:latest        "/usr/bin/supervisor…"   3 minutes ago   Restarting (139) 5 seconds ago                                                                                  netbird-dashboard
    647b54b5cfee   netbirdio/netbird-server:latest   "/go/bin/netbird-ser…"   3 minutes ago   Up 3 minutes                     0.0.0.0:3478->3478/udp, [::]:3478->3478/udp                                    netbird-server
    
  • A few possible things come to mind:

    • Did you ever try to reboot the server and did it come back correctly?
    • Were there some other changes made at time of backup that weren't taken into effect (e.g. because a daemon wasn't restarted), but with restarting after the restore did get applied?
    • Are there databases involved and is the backup possibly not a state-backup?

    If the machine boots and filesystem etc seem to be OK, technically you have a restored backup. The problem is either something in configuration or the backup wasn't a state/snapshot backup - something Veeam in most cases is

  • jeffsheadjeffshead Member
    edited September 21

    Did you ever try to reboot the server and did it come back correctly?

    Yes. Several times and it seems to be OK except for Netbird.

    Were there some other changes made at time of backup that weren't taken into effect (e.g. because a daemon wasn't restarted), but with restarting after the restore did get applied?

    No.

    Are there databases involved and is the backup possibly not a state-backup?

    SQLite. Based on the back and forth emails from the VPS provider, I'm assuming they use snapshot backups.

    I have deleted the containers and re-pulled the images. Get same results.

  • Well, first you have the dashboard container restarting, start by checking its docker logs to see why, then with this up you maybe can see some netbird-specific diagnostic on that dashboard. I would check all the other containers logs for errors too.
    This is probably some database hickup - often when data is being written when a snapshot is taken, the data is corrupted and would be restored by a backup or checked/fixed by some db command (like mysqlcheck for mysql). The system snapshot can only guarantee that it restores exactly was on the disk at that point in time, but the running programs of that time are now gone.

  • Nothing returned when I attempted to access the logs. Maybe my command wasn't correct. I spent a lot of time before giving up. I reinstalled the OS and Netbird.

    This is what I get now:

    [root@netbird]# docker ps
    CONTAINER ID   IMAGE                             COMMAND                  CREATED         STATUS                   PORTS                                                                          NAMES
    13d108629b3e   netbirdio/reverse-proxy:latest    "/go/bin/netbird-pro…"   3 minutes ago   Up 3 minutes             8443/tcp, 0.0.0.0:51820->51820/udp, [::]:51820->51820/udp                      netbird-proxy
    c74dc0ab1c3d   crowdsecurity/crowdsec:v1.7.7     "/bin/bash /docker_s…"   3 minutes ago   Up 3 minutes (healthy)                                                                                  netbird-crowdsec
    01a69d96ec8f   traefik:v3.6                      "/entrypoint.sh --lo…"   3 minutes ago   Up 3 minutes             0.0.0.0:80->80/tcp, [::]:80->80/tcp, 0.0.0.0:443->443/tcp, [::]:443->443/tcp   netbird-traefik
    6d7ac36d1e69   netbirdio/dashboard:latest        "/usr/bin/supervisor…"   3 minutes ago   Up 3 minutes             80/tcp, 443/tcp                                                                netbird-dashboard
    3af0e8571b47   netbirdio/netbird-server:latest   "/go/bin/netbird-ser…"   3 minutes ago   Up 3 minutes             0.0.0.0:3478->3478/udp, [::]:3478->3478/udp                                    netbird-server
    [root@netbird]# docker network ls
    NETWORK ID     NAME              DRIVER    SCOPE
    6a520df48d4d   bridge            bridge    local
    cb445e863f41   host              host      local
    6b7d7e08871a   netbird_netbird   bridge    local
    2b9101c7da96   none              null      local
    
  • first concern is how's ur data.
    Don't rely on the provider's backup. Imagine they terminate ur service, data is also gone.

  • Thanks everyone for the comments.

    I was finally able to get Netbird and Veeam to play nicely together. Using the overlay VPN, I can now quickly and securely backup my remote VPS's with application aware processing and file indexing. I did a couple of full volume restores and had the VPS's up in no time without having to adjust any VPS settings and without worrying about database glitches.

Sign In or Register to comment.