Hello,
I wanted to use “Local Storage” as a data backup method and the goal of “local storage” under NETH8. This seemed easy to set up and also fits into my security concept.
When setup, only one name for the backup configuration could be assigned but there was no way to specify a (local) storage location (preferential local drive)?
After the setup, the location was not displayed, I am only displayed by a webdav source.
The backup works - but where to? And how can I define that?
The GUI seemed to be used directly and without contortions for the creation of the local backup - and without information that additional commands would be required. Later, of course, I looked into the documentary and there I also see that I have to make preparatory work regarding the security target. However, it does not give me any information about the predefined memory - i.e. where the backups stored so far now consume space unnecessarily.
Where are these data backups stored by default? Where can I delete the backups made so far?
What is the current way to define your own arget for the backup? The existence of both paths - the (apparently) functioning GUI and the commands specified in the documentary power a little puzzled. Is that only optional or in any case required?
An additional question:
In Nethserver 7, every data backup e.g. also a database protection ahead, e.g. The Sogo. These dumps were then included in the backup. Is it still like that and if so where are these dumps?
Regards Yummiweb
Background:
I would like to set up data backups under NETH8. As a result, it should be “pull” data backups, i.e. the NethServer should not put data on the (final) goal (push) but the backup server should get the data itself (pull). This is intended to prevent the server from compromising the respective data backups.
The primary backup is image -based, in which the VM Images from the Proxmox VE (PVE) or the Proxmox Backup Server (PBS) are secured directly. This means that a complete system can be easily restored with the time X (in the event of a system failure or a drive problem). Thanks to Andy for the tip with PBS, has been running easily for years, especially remote.
The secondary backup is (as usual) a file -based backup. This is carried out (including versioning) via RSYNC (pulled from a distance), so that all cases are covered with a file (or configuration file) or the restoration of an email etc.
In addition, I have always used my own methods, e.g. The Restic Backup on the Nethserver 7.
Also under NETH8 I would like to use an additional at least one NethServer own backup methods so that e.g. individual containers (after update problems?) Can be restored without the rest of the system to be restored (*)
There are various methods for the NETH8 to choose from, but the most clouds are based - which for various reasons does not fit into my backup strategy. The “S3 compatible” variant for the self -skin of an S3 storage would be a variant, but I don’t like it for other reasons either.
So data backups remain on a “Windows file approval” and on a “local memory”. The “Windows file release” is out of the question because it works according to the “push” principle (I want “pull”).
There is still the variant “local memory”, which is also a “push” data backup, which I can have from the backup server via RSYNC as usual. So I would then have a quick, local availability on the NETH8 and could possibly copy older (non -comprised) fuses on the NETH8 to record them.
- So far, I had always been specifically on separate drives (in the standard paths coined drives), so that system recovery was also possible without losing the current status of service data. The container and the non -helpful numbering of the containers unfortunately seems blocked.