My Diskstation is my data grave and runs and runs and runs… a stable system, no problems in the last 7 years. But I don’t do critical experiments with it unlike Nethserver.
I had to set up NS completely new several times because I couldn’t fix mistakes and the complete reinstallation was much faster. (that was the reason to think about doing a drive image for disaster recovery)
In the case of the loss of the complete NS installation, I also assume the loss of the LDAP. Synology LDAP would be the surviving system.
I have no experience with restoring NS Backups and would like to avoid bringing in misconfigurations into a fresh installation via restore.
BackupPC is not an easy understandable system, esp.the french instructions do not make it easier.
I have to try a lot… As soon as I have enough confidence in NS and my administration skills, I will also use LDAP.
Thank you for your patience.
Before going any further you need to use Virtual machines - this is a must for testing as you can easily take a snapshot of a machine and return to it in case of an error. It takes only a few seconds to return to a previous machine, you do not have to reinstall…
Hi Michael, you can read minds, that’s exactly why I’m experimenting with Proxmox. I have already installed NS as a VM, but I can’t get it configured as a gateway, because only one of the two physical interfaces can be activated in Proxmox. But this is now a bit off topic here.
Using XCP-NG and XOA I automate my full system VM backups (you might consider this a whole system image) to an SMB/NFS/ISCSI FreeNas share as flat self contained vhd files. Within my Backup jobs I use TAG labels on each of my VM’s that have been defined within my backup jobs that automatically pull their respective VM’s for backup without me having to set policy per VM. Restoration is only limited by my hardware/networking backend and can be automated for disaster recovery detection/automatic deployment.
I’d highly suggest watching Lawrence System’s video to get a quick and dirty explanation/live demo if you were interested in learning about this platform from someone with tons of experience.
It’s just that VEEAM is a highly MS Company. Most Server Products are for VMWare or HyperV, and require a MS Server - to “administrate” a Linux system?
And VEEAM can’t handle KVM well - or not at all…
( or XCP-NG, for that matter!)
Well I have a very good experiense with veeam, and it is backup software, i have tested with nethserver, it’s just very reliable.Of course with kvm you can use image backup.I spoke about backup.With veeam i was able to restore completely, and also with proxmox.Proxmox it’s just great, all on board, than you don’t need any image backup software, and Nethserver have a backup on board. For veeam agent you don’t need MS system, it works from Linux console.
I looked and tested VEEAM against a ESXi 5.5 2 years back.
Not just the Backup, but the whole set of Tools freely available at the time.
I even installed a Windows Server in ESXi to manage it, but that wouldn’t work at all!
Tried even in two separate locations.
Maybe, in those two cases, Novell’s IPX Protocolls (And other, nowadays rare stuff) on the LAN were interrupting, as besides for NetWare, my friend had a very similiar setup, even same hardware, and it was working for him.
Maybe another look might be worth it, as I still have clients running Netware on ESXi, those are the only ESXi I still have running…
