VeeamON 2024 - Use Code "COMMUNITY10" for 10% Off!
Hey! Thanks for the shout-out @Kseniya and @Rick Vanover. That was actually my second post. :) If your interested, the first is a post-job PowerShell script that will completely automate storage snapshot replication to secondary arrays for VBR Snapshot Only Jobs. Pretty cool since this feature is currently missing for USAPI based storage integration. Asking if we can do this is one of the top Veeam related requests I get from Pure folks using the Plug-In. Bonus! It works in both v10 and v11 (yes there were some small changes required).
I’ve done both XFS an EXT4 with Hardened Linux Repo, both worked fine. If you’re using a physical repo server with JBOD storage I would probably lean toward XFS so you can get the block clone features, especially since you have to use Forward Incremental with periodic fulls with HLR. I was using SAN storage with really good built in native dedup, so in that case I decided to stick with EXT4 since I didn’t really need the block clone benefits. @jdw , thanks for your feedback! Keep in mind, Block Clone also saves time (because it reduces needed IOs dramatically) when merging last increment into last full. Do you have any good test results showing real world comparison? This test is on my to-do list for the blog, but not had the time yet; would be great to see some other comparison if they exist. My theory is that it will be far more important for low end storage but I’m not sure if it will have as much advantage on the QLC-flash systems I primarily work with.
I have installed a SOBR with three extents of XFS in our largest VCC datacenter. It works extremely well and have not had issues. We did mix it with ReFS but that was a bad idea and created a new SOBR just for XFS alone and no mixing. We also try to keep SOBRs at 2-3 extents maximum and then create new ones as needed. Thanks Chris! What was the problem(s) when mixing XFS with ReFS in a SOBR? One thing to note is the block size for ReFS is recommended on Veeam to be 64K and XFS is 4K, so I believe that alone would be a problem if trying to mix in one SOBR. Also keep in mind that Microsoft only supports Trim/UNMAP for ReFS on Storage Spaces. ReFS shouldn’t be used with SAN storage or you could get some really weird space accounting. Anton also calls this out in the R&D Forum.
There’s been speculation of ransomware on ESXi but it appeared to be nothing more than an unsecured host that was connected to and someone executing a payload. Replicas and Backups are different and protect from different events. But in both scenarios, good security policies are an excellent line of defence. Going back to your original point of connecting directly to the datastore, whilst I’m speculating here it’s likely it was an NFS datastore that wasn’t sufficiently secured to be accessed by specific devices only. It’s just a matter of time. Here is a new article describing ESXi attacks. https://www.crowdstrike.com/blog/carbon-spider-sprite-spider-target-esxi-servers-with-ransomware/
I could use a K8S desk reference… “add to cart!”
I started a few months ago. It’s been a ton of fun! Great use case for the #HomeLab. Biggest hurdle to getting started was just figuring out how to get a dependable lab up and running. I tried a lot of different methods, each with merits but so far have settled on Kubeadm. Wrote up a step-by-step on my blog back in December. Also, for training, I’ve been super impressed with Mumshad Mannambeth’s courses on Udemy. They come with free hands-on-labs which is also super helpful. He has both an Absolute Beginners course and a CKA course. Yes can only agree that his courses are brilliant along with Nigel Poulton on Pluralsight both covering the same topics with different approaches. Yes! Reading Nigel’s book now. Was lucky enough to get the Klingon Edition with red cover.And no, I’m not fluent… the content is still in English. ;)
I’ve done both XFS an EXT4 with Hardened Linux Repo, both worked fine. If you’re using a physical repo server with JBOD storage I would probably lean toward XFS so you can get the block clone features, especially since you have to use Forward Incremental with periodic fulls with HLR. I was using SAN storage with really good built in native dedup, so in that case I decided to stick with EXT4 since I didn’t really need the block clone benefits.
I started a few months ago. It’s been a ton of fun! Great use case for the #HomeLab. Biggest hurdle to getting started was just figuring out how to get a dependable lab up and running. I tried a lot of different methods, each with merits but so far have settled on Kubeadm. Wrote up a step-by-step on my blog back in December. Also, for training, I’ve been super impressed with Mumshad Mannambeth’s courses on Udemy. They come with free hands-on-labs which is also super helpful. He has both an Absolute Beginners course and a CKA course.
Super simple but super helpful! CKA is next on my list, so this is perfect.
Hi Regnor. Management is done via the GUI, CLI, and API. All methods enforce the SafeMode policies.I agree, it’s important to understand how any immutability feature is enabled/disabled. My post talks about immutability for block storage, but I also like the S3 Object Lock API as implemented by AWS for this reason. When it’s used in compliance mode, even an admin user can’t circumvent it. My concern with non-AWS implementations of Object Lock however are that they don’t inherently address the administrative access concerns. That would require additional considerations by the particular S3 vendor.
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
