@DustinB3403 was running into the same issues I was on 6.5.
There is dicsussion that some other process is changing it back, but we have not started to troubleshoot that. (I no longer have any XS6.5 boxes here.)
Wasn't Redhat supporting KVM? Or is this the commercial version of KVM?
This is RH's packaged KVM product. KVM is just the hypervisor, not the virtualization platform (think ESXi instead of vSphere, Xen instead of XenServer, etc.)
Ah, ok that makes sense. So this is an appliance or OS version of KVM. Thanks for the clarification.
Ya kind of like how they took Gluster and made Red Hat Storage. So if you want the glusterfs-server package, it's not in the repos.....annoying.
So I was able to make another array, and was also able to make an SR on that array. It's still strange that I'm not able to use thin provisioning by default on install, but for now, it's working.
@stacksofplates for HC3 Move it is actually in partnership with Vision Solutions. The full name is HC3® Move Powered by Double-Take®...Double-Take Move being the product we are OEM-ing for that.
We have played around with virt-v2v and virt-p2v, but haven't integrated them in the product yet.
In scenarios such as these what would be the recommended backup approach: DAS, NAS, Backup Appliance, lower end server, removable disk storage, tapes (intentionally left out cloud)?
Should be separate (physically!) entity non-related to your production cluster. Cheap NAS is OK.
For the average scenario (and I really just mean average) it's Synology or ReadyNAS that I recommend. Easy, supported, cost effective, desktop or rackmount options, well known, good brands, nice features.
I've used their product before. It's pretty cool. If you have multiple servers (and are using the paid version), it will handle load balancing between the servers and all for you, automatically... Last time I tested it was with VMware.
Edit: Only the paid version does the automatic load balancing, IIRC.
And if you look, that EXT3 type is on LVM. Hence the weird confusion 🙂
Yeah that, as I said, is what got me.
So, if you pick EXT is enables thin provisioning by default?
Yes. Because thin provisioning is not actually the option. It's actually just raw LVM vs file based. Files are thin provisioned. LVM raw is not. File based is being called ext3 here.