https://helpcenter.veeam.com/docs/backup/vsphere/immutability.html?ver=110 м?

насколько вижу, про s3 там в один абзац написано

»The immutability period will be equal to the retention period (if any) of the data blocks. All the types of files that are eligible for archive storage can be made immutable.

Благодарю

Запросить у саппорта перед переходом или у сейлзов ?

Ещё не вышедшую статью или что?

1/2 литра же

Лучше просто в бюджет отдела внести)))

Внести в бюджет поллитра? 🤔

Парочку на месяц, думаю норм

с какой версии вим может бросать бэкапы на клауд репозиторий?

Не говори
Мутят они а бюджетировать нам 🤬

кто-нибуть вим агентом бекапит посгри на оле?  как только сервис постгри в системе запущен,  снап в гостевой не делается)

The good news is that VMware did finally fix the driver signing issue and by now we've already tested the signed I/O filter bundle, so those of you using CDP functionality and needing to upgrade to vSphere 7.0 U2 ASAP can contact our support to get the U2-compatible CDP filter and installation instructions. Otherwise, you can just wait for the next patch where it will be included. I do want to remind just in case you missed this in the previous digest that vSphere 7.0 U2 has the confirmed regression with NBD transport performance – so if you rely on this transport mode heavily, your backup window may be impacted following the vSphere upgrade.

Veeam Backup for Microsoft Office 365 users: for many of you, backup and restore operations started to fail last week with the "The remote server returned an error: (403) Forbidden. Access denied" errors appearing out of nowhere. This is one of those "Microsoft suddenly changed API on their end" type of issues again. Lately they happen more often than I'd like, so you do have the right to be frustrated. However, Office 365 is a very actively developed platform, so I get it – one can break nothing only when doing nothing. All I can promise is that our devs will keep doing their best to restore the broken functionality as soon as possible. Anyway, we got very lucky with this particular one, because apparently we got rid of the impacted API queries last month in the latest cumulative patch while fixing some other issue. So, only those of you who did not have the latest patch installed got impacted. You can refer to KB4106 to determine which version you are currently on and how to upgrade to the latest and greatest build.

Словили тоже, но через пару дней само пофиксилось. Но апдейт всё равно накатили.

Вроде без проблем, veeam вроде 10-й, агент - 4.

А логи почитать?

Это не путь джедая

подскажите, что дает добавление СХД в Veeam на вкладке storage infrastructure если лицензия на veeam - enterprise ?