Games from that time were actually running mostly in your browser. Meaning that the host, for example Miniclip served you the JavaScript and other files of the game which were then executed locally. So technically you could archive those games as long as you can load them up at least once initially.
Just in case we misunderstood each other. I have executed the minio client inside my minio container deployment. So the network connectivity is exactly the same given that they are inside the same container.
So I was able to add the backblaze backend as an alias site to minio client and then list my buckets content. Even when it was restricted to that particular bucket it behaved as expected. But if I set up the replication via the GUI in minio, it suddenly logs out that the remote bucket is offline. Both URL and access parameters are the same between CLI and GUI
I tried both a general purpose key that had access to all buckets, and one limited to the test bucket. Both times with read-and-write
I use Longhorn for generic PVC and static NFS shares for large files. Longhorn creates scheduled backups to a NFS share, which is then backed up to a Backblaze bucket. I have yet to test restore from Backblaze tho :D
Of course this means that I have 3 copies of the same data across multiple Nodes because of how Longhorn works. That’s why I usually don’t create large volumes, just enough to get the app working