VBM does not support tape. You can add Object repository and do copies to that from the primary repository, but nothing to tape. I would recommend having object offsite.

Immutable offsite object storage effectively replaces tape in your solution.

I do not recommend using the same repositories that you are using for VBR. VB365 is architected very differently so you need to have a good understanding of your needs before you implement it. VB365 cannot store data on hardened VBR repositories but can leverage immutable object storage repositories.

For backup copies, keep in mind the following:

"Both source and target backup repositories for backup copy must be extended with object storage and located on the same backup proxy server and have the same retention type. For more information on how to extend a backup repository with object storage, see Specify Object Storage."

The retention type is either snapshot-based or item-level. Make sure you plan that correctly.

https://helpcenter.veeam.com/docs/vbo365/guide/vbo_backup_copy.html?ver=70

Hin is absolutely right here, I’d just add have a read of this Veeam blog post and all the reasons that friends don’t let friends use block storage for VB365 backups!  https://www.veeam.com/blog/storage-decision-guide-microsoft-365.html

In a nut shell:

• Better data compression by dar
• Backup copy support
• immutability support (for the backup copy)
• scales far easier!

Disclaimer straight away: Object First SE here.
As gentlemen noted, Object Storage is a great way to go to achieve immutability of your VBM backups. Object First Ootbi was designed as a fully-equipped on-prem S3 storage solution. Immutability is an important feature this day, so it is supported as well. Ootbi was specifically developed to work with Veeam. https://objectfirst.com/object-storage/

This is a great appliance and software that works with Veeam.