Hi,
what you are looking for is
https://www.veeam.com/documentation-guides-datasheets.html

On this site here community members are trying to help with specific questions on a volunteering basis.

If you’re ever not sure, a question on here goes a long way, and there is a search on here which is great as it searches post title & content.

Alternatively, years ago Veeam put together a great custom search engine (driven by Google) that allows you to search through their various resources from a single query. If you’re more a self-help type of person, try this:

http://vee.am/VeeamCustomSearch

I’d also point you in the direction of the Best Practices guide 

https://bp.veeam.com/vbo/

lots of excellent information contained within

All of the above mentioned sites are great resources especially the best practice one.

This walks through an installation: Installing Veeam Backup for Microsoft 365 and Veeam Explorers - Veeam Backup for Microsoft 365 Guide

Thanks for the helpful links.

Well, with a fresh install of v5.0.3.1063 of the community edition of backup for office 365, I am seeing the warning below, and can find no clues as to how to fix it (other than 2½-year-old stuff about opening a support case because there is no workaround -- https://forums.veeam.com/veeam-backup-for-microsoft-365-f47/warning-site-was-moved-to-another-url-t63663.html)

2022-05-16 10:05:23 PM :: Processing site https://tenant.sharepoint.com/sites/WorkSafe finished with warning: Site URL has been changed.

The site’s URL has indeed been changed since the backup was configured.  How do I get veeam to recognize the old site is gone (that is, just use the correct URL, without the warning)?  XML file? ini file? regedit?

Morning, any reason why you’re using v5? V6 includes support for renamed domains, the “What’s new” doc is here: https://www.veeam.com/veeam_backup_m365_whats_new_wn.pdf

8 cores required.  Client’s server has 4

That’s the recommendation, it’ll still work without it but it’ll just warn btw. There’s no hard fail. Just an FYI for when v5 ends support.

Yes it is recommended to move to V6 as there are many enhancements.  As noted specs are just recommended not required.

actually, v6 install failed, hard, on the hardware with 4 cores. No ability to carry on.

I will try upgrading to v6 and see what happens.

That is interesting and good to know for others. So looks like minimum is 8 cores.

I'll need to double check but I think less then 8 cores should still work, besides getting a warning about the minimum requirements.

Before doing the upgrade to v6, I fixed the problem this way: (courtesy of link to wayback machine copy of support.cybersecure.com solution)

In an elevated privilege powershell window (in Win10 21h2):

Install-Module -Name Microsoft.Online.SharePoint.PowerShell
Connect-SPOService -Url "https://tenant-admin.sharepoint.com"
Get-SPOSite -Identity https://tenant.sharepoint.com/sites/WorkSafe
Remove-SPOSite -Identity https://tenant.sharepoint.com/sites/WorkSafe
Get-SPOSite -Identity https://tenant.sharepoint.com/sites/WorkSafe

Then run the backup again. No warnings. The new (renamed) site is also backed up.  Useless log noise successfully eliminated.

Install-Module -Name Microsoft.Online.SharePoint.PowerShell
Connect-SPOService -Url "https://tenant-admin.sharepoint.com"
Get-SPOSite -Identity https://tenant.sharepoint.com/sites/WorkSafe
Remove-SPOSite -Identity https://tenant.sharepoint.com/sites/WorkSafe
Get-SPOSite -Identity https://tenant.sharepoint.com/sites/WorkSafe

Nice to see you could fix this. Going to keep this command handy.

Upgrade to v6 worked as described . Manually started the backup. Number of objects is the same, no warnings (none expected).  So the 8 cores is definitely not a requirement for upgrading from v5.

Good to hear.