We have one physical server (or a hypervisor with a handful of VMs) and want Veeam set up properly.

Veeam B&R Community Edition (free up to 10 workloads) is often enough for small SMB. The weak point is almost never install, it's repository choice and restore-testing. Get those two right and you're well covered.

Try this first

1. 1Install Veeam B&R on a separate management VM or box, not on the server you're backing up. Otherwise a crash kills your data and your backup tool together.
2. 2Create two repositories: a local one (NAS, USB, dedicated disk) and an offsite one (cloud object storage like Backblaze B2, Wasabi or S3). Local-only isn't 3-2-1.
3. 3Set a job that runs nightly with retention matching your RPO. For SMB, daily incremental with weekly full and 30 days retention is a reasonable starting point.
4. 4Enable immutability on the offsite repository (S3 Object Lock or Veeam hardened repo). Without immutable, an attacker inside your domain can wipe offsite too.
5. 5Schedule a SureBackup job or a manual test-restore to an isolated VM network. Once per quarter is enough, as long as you actually do and log it.
6. 6Set email alerts on job failure and on unusually short/long runs. Send to a shared mailbox or ticketing tool, not one person, so it survives holidays.

None of the above fits?

Describe your situation below. We pass your input plus the steps you already saw to our AI and return tailored next-step advice. If it's too risky to DIY, we'll say so.