May 16, 20179 yr Community Expert Glad you recovered most of it. I agree that btrfs is not as robust as xfs, specially if there are any hardware issues, and frequent backups are very important, but it also has a much easier way of doing incremental backups with snapshots together with send/receive, I backup my VMs daily, and the snapshot itself is instantaneous, if interested on more info see here:
May 16, 20179 yr Author Thanks for the info...will this type of backup cover me in this type of scenario where I had corruption? Would I just rebuild the pool from scratch and then put the snapshot back on to the new pool?
May 16, 20179 yr Community Expert 9 minutes ago, comfox said: Would I just rebuild the pool from scratch and then put the snapshot back on to the new pool? Yep
May 16, 20179 yr Author Thanks...I took a read through the post. Seems amazing, though looks a bit too complicated for me to setup and maintain. I don't know where to start.
May 17, 20179 yr Community Expert Tom mentioned earlier that he's working on a VM snapshot/backup GUI utility, don't know if it's going to make it for v6.4 though:
May 17, 20179 yr 13 hours ago, johnnie.black said: Tom mentioned earlier that he's working on a VM snapshot/backup GUI utility, don't know if it's going to make it for v6.4 though: Probably won't make into 6.4 but I use a procedure very similar to your "Method 2". FWIW we use btrfs exclusively for all VM vdisks and all development. Haven't had any issues whatsoever.
May 18, 20179 yr Author On 5/17/2017 at 2:10 PM, limetech said: Probably won't make into 6.4 but I use a procedure very similar to your "Method 2". FWIW we use btrfs exclusively for all VM vdisks and all development. Haven't had any issues whatsoever. I will likely go back to it, just wish I knew what caused this corruption in the first place. Loosing a week to rebuild is a bummer.
Archived
This topic is now archived and is closed to further replies.