What's the correct/preferable way to backup in MSSQL?

Question

Database administration

There is a server on which MSSQL is twisted. Service plans are configured in accordance with the tasks. A full copy is made every day at night (stored for 7 days), a full copy on Sunday (control, stored for 2 months), copies of transaction logs (every 30 minutes, stored for 3 days). All backups are stored on an adjacent physical disk on the same server. Which of course is not good. Need more backups on other physical devices. This is where the question actually arose, how to do them correctly.
I see two options so far:
First. I just use any utilities to make copies of copies to, for example, a network drive. Everything is simple here.
Second. I am raising another instance of the mssql server on a neighboring server. It seems to me that this option is preferable, since I can get a failover cluster. If I understand correctly, there are two options with the second server: make scheduled copies to it and write to it in real time (something like that). Here I would like to hear advice on how "adult guys" do it. What resources are needed in this case on the backup server? Should it be the same in performance? Or will something simple fit (less RAM, less CPU computing resources)? Is it possible to transfer from a standalone server to a cluster without stopping workflows for a long time (6 or more hours - in my case a lot)?
Thanks in advance.

Answer 1

backup via sql query to local disk + Cobian Backup to local NAS/ftp/etc

Answer 2

Innobackupex. We have been using it in production for a long time and fruitfully.