How do I store my esports cafe data in the cloud?

Ask five owners what they mean by putting the cafe in the cloud and you get five answers. One wants the member list safe. One wants to see today's revenue from their phone at dinner. One is thinking about the 6 TB of games on the server and quietly hoping someone will store that for them too. They are asking about three different things and only one of them has a clean answer.

So before the how, the what. Which of your data actually belongs on a cloud server?

Your cafe does not have one pile of data

Two piles. They behave nothing alike.

The first is the database. Member accounts and wallet balances, every session your PCs have billed, revenue and expense records, pricing rules, your settings, the audit log. On a venue that has been running tournaments for three years this is a file measured in tens or hundreds of megabytes. Small. Irreplaceable. If it disappears, nobody on earth can rebuild it, because the information only ever existed on your machine.

The second pile is files. Game installs, patch data, launcher caches, the posters and icons your client menu shows, driver packages. Terabytes of it. Also completely replaceable, because Steam and Epic still have every byte and will hand it back for the cost of a long download.

Guess which one owners worry about. It is usually the terabytes, because that is the number that looks scary on the disk usage screen. The pile that actually ends careers is the small one.

The database is what goes up

Storing esports cafe data in the cloud, in HandyCafe, means the Backup and Sync tab on the Cloud page. It uploads an encrypted snapshot of your database to HandyCafe servers, off your premises, restorable onto any HandyCafe install. That last part is what makes it a real answer to a dead disk. The snapshot is not tied to the machine that made it.

There is a Back Up Now button that pushes a snapshot immediately. Useful before you do something you might regret, like a big member cleanup on a slow Tuesday. The backup that saves you, though, is the scheduled one. Automatic backup runs daily, weekly or monthly at an hour you pick. Retention keeps it from piling up: at most a set number of snapshots, nothing older than a set number of days, whichever limit hits first.

Restore is an administrator action. Pick a snapshot and confirm. It downloads and replaces your current database, then the app restarts. Before it overwrites anything it saves a safety copy of the current database. A wrong choice can be walked back. A failed restore leaves your live data alone. The step by step is in the Cloud Backup and Sync guide. There is a longer version of why any of this matters in the post about the morning a cafe lost everything.

The part people are disappointed by

File Sync is not cloud storage. This trips up people who see a sync feature and assume their game library is now safe somewhere.

What File Sync does is push files from your server to your client PCs across the local network. It builds a manifest with checksums, each client compares it against what it already has, then only the new or changed files move, in chunks over the file port. That is a genuinely good way to get a 40 GB patch onto twenty rigs before Friday night without walking to each one. It is distribution. The files never leave the building and there is no copy of them anywhere else.

I would not want it any other way. Uploading a game library to a cloud service every night would saturate your line for the sake of content Valve already stores for free. Spend the bandwidth on the database instead.

Which data lives where

Live data is a separate thing entirely

The owner who wants to check revenue from their phone is not asking about storage at all. They are asking about the Live Link, the real-time connection between your server and the HandyCafe cloud. The Manager app relays through it to read the live state of the cafe: which PCs are online, active sessions, the day's figures. Nothing is being stored on your behalf there. The cloud is acting as a wire.

Which brings up the honest limitation of the whole arrangement. Cloud backups run only while the Live Link is active. If your scheduled hour is 04:00 and someone kills the switch after closing, there is no snapshot for that night. A fibre drop at 03:00 does the same. Nothing warns you at the time. The Overview tab reports the connection as Cloud disconnected with the last error. You have to go and look.

For a venue that runs events, set the backup hour for shortly after the last session closes, while the room is still powered and someone is still there. A tournament Saturday is exactly the day whose member sign-ups, wallet top-ups and session records you would most hate to lose. It is also the day the server is most likely to get restarted for something. That combination has bitten people. Set the hour where it fits your actual closing routine, not at some tidy number in the middle of the night.

What leaves in aggregate

One more category, since it is fair to know what else goes out. If you are on a Cloud subscription, your server contributes anonymized figures to the Benchmark cohort, which is how you get to see where your revenue, occupancy and utilization sit against comparable venues in your country as percentile ranges. A cohort only forms once at least twenty cafes in the region are contributing. You never see another cafe's details and they never see yours. If that trade is not one you want to make, it is worth knowing it exists.

What I would actually set up

Four things, in this order. None of them take long.

1. Turn on scheduled local backups on the Database Maintenance page. These live on the server's own disk, which makes them fast and perfect for the everyday mistake, like the staff member who wiped the wrong member account.
2. Turn on automatic cloud backup, daily, at an hour when the machine is definitely on. Set retention so old snapshots clear themselves.
3. Check the Live Link on the Cloud Overview tab once a week. It takes five seconds and it is the difference between having backups and believing you have backups.
4. Restore one snapshot onto a spare machine, once, on purpose. A backup you have never restored is a theory. Nobody wants to test their theory on the worst morning of the year.

Keep both layers. A local snapshot does nothing when the disk itself dies or the machine walks out the door. A cloud snapshot is slower to reach for when all you did was delete a price rule by accident. They cover different failures and together they cover most of what actually happens. There is more on how the pieces fit on the features page. If you are still choosing a system for a tournament room, the esports venue software post covers the rest of the checklist.

The pattern is the same every time it goes wrong. The owner backed up the thing that could be re-downloaded and left the thing that could not on a single spinning disk under the counter.