I see that hardened repository has a number of limitations documented, especially type of backups that are immutable like transaction backups (MSSQL Logs, RMAN?).
Object storage immutable backup documentation does not mention the same limitations but a considerable smaller list.
Is the documentation correct in that there is a difference in which type of backups that are immutable or is it a documentation issue?
References:
https://helpcenter.veeam.com/docs/backu ... ml?ver=110
https://helpcenter.veeam.com/docs/backu ... mutability
-
- Enthusiast
- Posts: 29
- Liked: never
- Joined: Apr 11, 2019 11:37 am
- Full Name: Dejan Ilic
- Contact:
-
- Product Manager
- Posts: 14322
- Liked: 2890 times
- Joined: Sep 01, 2014 11:46 am
- Full Name: Hannes Kasparick
- Location: Austria
- Contact:
Re: Immutable storage limitations : Hardened repository vs object storage
Hello,
yes, it's correct that there are differences. It's two different technologies.
Best regards,
Hannes
PS: We are working on supporting more workloads for hardened repository.
yes, it's correct that there are differences. It's two different technologies.
Best regards,
Hannes
PS: We are working on supporting more workloads for hardened repository.
-
- Enthusiast
- Posts: 29
- Liked: never
- Joined: Apr 11, 2019 11:37 am
- Full Name: Dejan Ilic
- Contact:
Re: Immutable storage limitations : Hardened repository vs object storage
Thank you. That answers my thoughts.
-
- Product Manager
- Posts: 14322
- Liked: 2890 times
- Joined: Sep 01, 2014 11:46 am
- Full Name: Hannes Kasparick
- Location: Austria
- Contact:
Re: Immutable storage limitations : Hardened repository vs object storage
ah, I forgot... there is another section to look at... for example MS SQL logs are not copied to capacity tier / object storage. So that's why they are not listed in the limitations for object storage for example
Who is online
Users browsing this forum: Bing [Bot], Google [Bot] and 113 guests