Properly organize a file share?

Question

FTP

Good afternoon! Advise how to competently organize a file share (file dump).
What is: A shared folder with files, connected by a script to all users in the domain.
You need to do: A server for backup. I will drop various backups from the whole office there.
Hardware:
Asus m2n-mx-se
Amd athlon 4200
2gb: RAM
hdd:2TB
Advise what is better to raise ftp and add everything over the network, or just fumble through folders and sync bittorrentsync from machines? Or is there an even better solution?
Thanks in advance for the replies.

Answer 1

Here the question is why backups:
1) Safety of files at crash of the server.
2) Preservation of files from being overwritten by users and access control.
Since you already have the folder, I think you have the second option and you will be fine with AD + shadow copying a couple of times a day. File versioning again.
If you have option 1, then the approach is simple - do not keep eggs in one basket.

Answer 2

If Windows: Standard folder sharing (samba) - will not work?
roaming profiles?
it's just not clear what EXACTLY is needed: the volume of backups, their frequency, etc.
https://rsync.samba.org/
www.techsoftpl.com/backup/index.php
PS: this answer is the only solution to the problem.

Answer 3

IMHO, you need to build on the capabilities of the software that you backup.
1) The software can only backup in the "ball" - we fumble the folder. It has the right to read a group of accounts on behalf of which the backup software is launched (if there is a need, we make subfolders for each solution that is backed up, we create a separate account for the backup of each solution from under which the software will be launched, and set the write rights already on the subfolders for each account separately)
2) The software can add to ftp - we raise ftp. Here, too, there is room for imagination (for example, for each account from which the connection is made, we make the home directory on ftp and take the rights to the rest of the directories) - a harmonious folder structure for organizing backups
What we have in the output:
- backup security (each subdirectory is write-isolated)
- beautiful :) (especially if you standardize the names of folders, accounts, groups, names of backups and stick to standardization)