Immutability is an important component of any backup strategy. However, as an S3 provider, immutability can often leave you with data locked for a longer term than you really want. Immutable modes Minio offers three different immutability modes that can be enabled on objects.
Introduction There are some tuning benefits you can utilize for your Minio deployments to make things a bit smoother. Here I’ll walk you through how to configure certain “ethtool” settings and have them persist across reboots, specifically on RX and TX buffers and coalescing values.
backup-disaster-recovery minio veeam 1 comment
Why this article exists I sought to answer a couple of questions for Veeam and Minio buckets: How much space does Veeam backups take up on a Minio-based Object Storage repository? How much does the Block Size setting make on space consumed? What are the object size distributions when the Block Size settings are changed? In an effort to answer these questions, I came across an interesting discovery. When Veeam would delete objects that are no longer required due to retention policy settings, it left behind DeleteMarkers that would never get cleaned up. This amounted to a million DeleteMarkers being created in only two weeks. These expired DeleteMarkers are zero-byte objects that Minio has to deal with. Ouch. Most of the time, these DeleteMarkers are not causing much of a problem. They do not consume a lot of space, nor do they impact the performance of backups or restores.
backup-disaster-recovery minio veeam
Introduction Today we are backing up on-premises vSphere VMs with Veeam direct to a Minio S3 bucket, then restoring that VM to a VMware Cloud Director ORG in the cloud. Once complete, we will then back that VM up direct to a Minio S3 bucket and recover it back to the on-premises vSphere deployment.
