I would look at what you want your backups to protect you from - building and server being destroyed, upset intern/secretary/partner deleting files, bad actors attempting to lock files for ransom, etc. and then look at what combo of solutions solves your anticipated problems in a manner that you can live with.
Problem with cloud backups becomes data transfer, especially for very large files, and especially if you have a typical asynchronous speed connection (most connections are much faster download than upload in 'murica, 'cause "consume!"). Not an issue if you have a Real connection (that comes with a SLA, uses real routers etc - fiber, leased lines, etc)
OK, so instead just keep all the data in the cloud! Problem there becomes working with large files (remote file systems suck even at 1gbps LAN speeds, never mind most internet connections), and then of course you are dependent on your high speed internet connections not having any issues.
However... since you specifically mention SolidWorks....
Consider using a pay-for Subversion hosting service, or set up your own subversion server on an Amazon or Azure or Linode or whatever VM that has expandable storage. And then use subversion (svn) to do your backups.
https://gotomation.info/2020/01/svn-or-git-with-solidworks/
Each project can get its own repo, when you are done with changes you push them to the repository. At any point, you can re-pull the repository AND go back in time with various changes. When you need more space locally, delete your local copy and rock on. When you get a new computer, just re-pull down the repositories.