Comment on the IS backup scheme. What can be improved?

Question

Backup

Hello. I am asking for help and advice on the analysis of the existing backup scheme and the development of a new one.
So, recently backup of old infobases has been added to my work responsibilities. All of them run on WinSRV2003R2 (SQL2000, 2005), about 8 virtual machines. There are 77 bases in total, most of which are archival (created once a month). There is no control to the virtualization host (data center, ESXi 5.5), no backup of virtual machines is performed.
Through the xStarter program, the previous employee set up automatic (scheduled) connection of a network drive (storage), then unloading the database to a local drive, archiving the bak file, notification of the creation of the archive and its subsequent movement to the connected network drive. At the same time, there is no access to the storage administration (NetApp FAS2200, located at another site), only a directory and a user with write access to the corresponding directory.
From time to time, failures occur with software, most often with xStarter and 7zip (used when working out a script), less often - with network storage, OS. There were precedents for the deletion / loss of part of the archives from the repository "in an unknown way" ... and the removal of a responsible employee from his position.
There is a great desire to get rid of all this whistle-blowing, but I am for the professional development of IT specialists.
To begin with, I want to organize a second network storage using NAS4Free (AMD A4-5400, 8x2Tb HDD, 8Gb RAM purchased earlier, cannot be replaced/expanded). Create two ZFS pools. One mirror (Mirror) directly for storing backups from two HDDs (2Tb total disk space is more than enough), the second pool - from 5 disks (RAIDZ-1 - analog of RAID5). Leave the remaining 1 disk as a backup (the procedure for agreeing and purchasing equipment takes a very long time, which is unacceptable if any HDD in the NAS fails).
Having decided on the storage space, we move on to the software part. Over time, the virtual machines themselves will be backed up, but this is not the main thing. The main problem for me is to make a script/find a really working backup software. Requirements:
- stable operation
- automatic scheduled
operation - log of performed operations
- support for SQL2000-2005
- sending emails about completed operations (archive creation/file in the directory, etc.)
- automatic deletion of old files (after 7/30/ 365 days, etc.)
- free of charge
At the same time:
- sites with databases and storage in one city, local network - 1Gbps
- 1C databases do not support work with newer versions of SQL, only SQL2000-2005
- there is an SLA in terms of storage time, backup setup time for a "new" (ie test, additional, etc.) base, recovery time.
- on other sites (other cities) other organizations, newer versions of SQL are implemented by scripts, but there are also failures.
Now I'm setting up storage. The whole question is in the software - xStarter is praised by many, but in my opinion it is excellent software for a small desk.
Please help with advice, a link or any information on the described and used backup scheme, as well as on the NAS configuration.

Answer 1

The main question: will old backups be replaced by new ones?

Answer 2

IMHO, to begin with, switch from MSSQL 2005 to more recent ones due to the fact that you have to store archives (as I understand backings using MSSQL for several years?) The problem may become such that after N years you simply cannot restore, suddenly backwards compatibility will be missing. Therefore, at least every 5 - 10 years, update MSSQL for the reason indicated above.
If, again, you need to store backs for so long, maybe you should switch to tape media?
In more recent versions of MSSQL, all your tasks are implemented by regular means in SSMS (SQL Server Management Studio).
Having 77 1C databases on MSSQL and demanding "Free" solutions - this is something from the category of fantasy. It is worth explaining to your employers that it is "NECESSARY", I emphasize, "NECESSARY" to buy a new MSSQL and tape data storage, otherwise in a couple of years it will be problematic, if not impossible, to restore data due to the lack of backward compatibility or crooked backups, which are now so understood through miserable crutches are implemented, by throwing a network drive through the Internet smb, using some third-party organizer, followed by a backup to it via 7zip.
Judging by the hemorrhoids of copying backups to another machine you described, it's easier to raise a cloud, like Cloud Sration.
Just an example:
We have a SAN on which several 1s databases and MSSQL backups are spinning.
On the other side of the country, we have a Synology SAN with Cloud Station deployed on it, which synchronizes backups between devices. Most importantly, it’s not scary that the Internet will disappear in the office. As soon as there is a connection, the backups are synchronized. Very convenient and simple. There are always backups on different machines, at different geo-remoteness, and they do not need a stable connection between each other, due to cloud synchronization.