Nethserver - How do you backup and RESTORE

Good evening to the long time nethserver specialists.

Coming from SME and using over years affa, I’d like to know how are you backing up AND IN CASE RESTORE your production server to separate hardware, means a real hardware spare server?

thank’s for any reply

We need a bit more Infos abt your IT-Infra…


Use Proxmox virtualization…

Migration in 90 seconds to another hardware…

Even less for a snapshot rollback after a botched update…

My 2 cents

Backed up Nethserver from Proxmox PVE to Proxmox PBS in 7 seconds when files on Nethserver are untouched and dirty bitmap of Proxmox is OK :grinning:

PBS is fantastic!
Using it at home, NS is 400 GB, 250 used.
Backup (incremental) takes 9 minutes - Proxmox and PBS are both 8 years old hardware… :slight_smile:


Thanks for jumping in.

IMO very simple. Firewall OPNSense --> NS-Server --> Backup-Server. All real hardware.

Hi Andy,

I understand that NS has two backups implemented. One for config and one for data. Why underlying another OS for virtualization? Is there a problem with the standard backup - restore way?

I like to have a machine dedicated for a server OS. Not a machine running proxmox and on top NS (or any other or even more different OSs). I don’t want start a flame war - personal only for me, I want to have a dedicated machine with exactly one OS.

I’m interested in the way you see it.

In one environment (firewall + FreePBX) I use hotsync, in some others environment where I have VMware ESXi I use VM replication on another SAN.

In all others situations I use backup and restore (night backup).

Just sooo much more flexible, faster and less risk.

You can’t “snapshot” a real server before an update - it takes too long using Backup (Any form).
Change CPU, RAM and Disks without any screwdriver… :slight_smile:
And much more features.

What’s 20 minutes to install a pristine Proxmox? I can do that on almost any hardware, maybe as requirement enough diskspace for Nethserver as VM (Or using shared storage on your NAS, that can be passed over) and enough RAM for the NS-VM (8 GB RAM?)

It’s so simple!

And yes, I do have clients running Proxmox just to run NethServer on top - because Nethserver has become important… !

Thank’s to all for the insights.

Question to the VE supporters - in case of a hardware fault, you need a second server, correct? Backing up (snapshots) the PVE on a running server includes for safety to move the snapshot to a running second physical machine with a running PVE. I understand basically two machines are needed. Both have to run 24/365 with a PVE. Snapshots have to be moved from the production server to the backup server. Am I wrong?



You need at least two servers, yes.

Depending on the Virtual Environment, and of course on what exactly goes defective on the server.

Proxmox for example can use:

  • Local Storage, when single server.
  • Shared Storage, eg in a Cluster.
  • ZFS synched Storage, eg in a Cluster
  • CEPH Storage

With Local Storage, you need to move the data of the VM - or you need to revert to Backup.

All other three you can think of a file on a file server. If one PC is not using it, an other can use the file. Migration only entails the RAM contents. Migration is extremly fast!
No need for snapshotting for this!

This means you can achieve true full High Availability. In this Version VMs can “Migrate” on their own, if the underlying hardware fails.

And it does NOT matter if one Proxmox has an Intel CPU, the other has an AMD - the VMs use a “KVM” CPU, which exists for AMD and Intel.

Migrating a VM on a Proxmox cluster means moving the RAM contents to another Server, as the “HD” of the VM is on shared storage, like an Excel file on a file Server, and can be opened by any other member of the cluster. This is all done automatically, you just choose “Migrate” and the target server, if more than one…

These functions provide for availability (Also through Abstraction) which a real hardware running system can’t ever achieve…

You’ve heard several people suggest using virtualization here… :slight_smile:

Also, as the underlying Proxmox has hardly any configuration, it’s installed in 20-30 minutes on any hardware.

You also have two Backups, one by the VM itself, and one by Proxmox. The second is very fast, especially for Disaster Recovery scenarios…

With more than 3-4 Servers, you can also “switch on” Servers as needed. Wake on LAN, scripts monitoring Server Load, etc…

Proxmox includes all tools needed to do live backups of all VMs. And complete Backup Versioning with deduplication and delta sync, if using the free PBS (Proxmox Backup Server). This is extremly fast!
For Windows, Proxmox even uses ShadowCopy technologies to make correct backups… :slight_smile:
All for free!

My 2 cents

I do two levels of backup - machine and guest. As a VMware user I tend to know and use Veeam for the daily machine level. I then run an RSync script to give me versions on a mounted NAS drive (/backup):

rm -rf /backup/bu.5
mv /backup/bu.4 /backup/bu.5
mv /backup/bu.3 /backup/bu.4
mv /backup/bu.2 /backup/bu.3
mv /backup/bu.1 /backup/bu.2
cp -al /backup/bu.0 /backup/bu.1
rsync -av --delete-delay /var/lib/nethserver /backup/bu.0/

The beauty of that one is the -l symlink option in the copy (cp). It saves on space by not literally copying all the files of course.

If you want to get your files out of the network, have a look at this:

For VMWare users, if you haven’t seen this one yet, it is also nice:


Any experiences with laptops? For testing purposes only… It understand that a guest OS is not able to access the ap. At least not out of the box, even if the host is in bridged mode.



Virtualization on Notebooks generally work, but some have issues passing thru the WLan.

On my Macbook using Parallels, I can access the WLan with my Windows VM.
But this seems to be an exception…

Mostly, what works is Host mode, where the Notebook becomes a “router” with NAT for the VMs.

I have set up Proxmox on Notebooks, mostly to “show” Proxmox. Here I let Proxmox provide a NAT “firewall” - or used wired LAN…

The problem is not with Proxmox, but how WLans and WLan-APs work. The MAC Address of the VM is not “allowed” when the underlying hosts registers…

My 2 cents

Thank’s to all for the insights.

After reading a lot about PVE I came to the conclusion, that for me the old fashioned way is the best. One machine - one software. A dedicated backup server, like affa or hotsync, will be in case of a hardware failout fast enough for me in production. Backups with rsync don’t take much time. I have no need running on an underlying OS (proxmox or whatever) different or multiple applications (NS). An underlying OS means additional dependencies/risks I don’t want to have or maintain on a server running on top.


For me, the maintening of a seperate hardware serving no special purpose in the meantime, but eating power 24/7 is too much work - for nothing.

Using Proxmox, on the other hand, has saved me and my clients countless hours.

One shoe does NOT have to fit all.
Your use case may be different from mine.

And I don’t use hardware servers (non hypervisors) now for a very long time!

My 2 cents