Likely we’ll need more information. How much data in one set of full backup archives? How often do you update the offsite archive? Have you calculated your expected cost for the UrBackup Cloud Server on AWS? Do you have two or more offices that run UrBackup so they could be each others offsite facility? (I’m doing this for the servers in four offices, backing up local workstations plus remote servers.)
Have you considered a separate instance of UrBackup that only runs your archive backups to a mirrored pair of removable hard drives? For example, take one drive offsite each month and let the RAID copy the other to a fresh drive. This gives you reasonably quick access to the backups, as opposed to a possible long download from the Internet, at the cost of 24 drives kept offsite. For disaster recovery you’ll already be keeping a bare-metal backup of the server itself (less the UrBackup archive and using a different product such as Windows Server Backup) to restore your server instance. Once that’s rebuilt, the UrBackup archive is attached and you restore at full speed.
Naturally any of these instances may be virtual, depending on your hardware and company IT capabilities. For reliability and expansion you may also want to use a pair of multi-drive RAID systems such as Drobo instead of a single pair of large drives, and archive one entire set each time, but the idea is the same.