Free Veeam for DGraph Linux Restore
-
@Obsolesce you already know from this thread that that doesnt solve the problem. You are just repeating the same issue that he was trying to resolve.
VSS causes this issue the same as any other LVM.
Read the thread. Weve beaten this to death. VSS isnt magic.
-
While Jared likes to pretend Im pushing agent backup, ive clearly nit recommended agent or agentless. Ive explained ad nauseum how they share a mechanism that doesnt work here and neither can work without a native backup.
-
@scottalanmiller said in Free Veeam for DGraph Linux Restore:
@Obsolesce you already know from this thread that that doesnt solve the problem. You are just repeating the same issue that he was trying to resolve.
VSS causes this issue the same as any other LVM.
Read the thread. Weve beaten this to death. VSS isnt magic.
I will have to read more. I posted after only really reading the OP.
-
@Obsolesce said in Free Veeam for DGraph Linux Restore:
The free Veeam you are using in your Windows VMs will not back up VMs via the host... meaning you cannot install the free Veeam edition on your Hyper-V host and expect it to back up your VMs.
Actually it absolutely does do this. You are limited to ad-hoc VeeamZIP creation, but it works perfectly.
-
@Obsolesce said in Free Veeam for DGraph Linux Restore:
@scottalanmiller said in Free Veeam for DGraph Linux Restore:
@Obsolesce you already know from this thread that that doesnt solve the problem. You are just repeating the same issue that he was trying to resolve.
VSS causes this issue the same as any other LVM.
Read the thread. Weve beaten this to death. VSS isnt magic.
I will have to read more. I posted after only really reading the OP.
His DB doesnt quiesce and he cant find processes to stop manually. So anything using an LVM whether a Linux agent or Hyper-V's LVM called VSS will be expected to corrupt sometimes. Even when not clustered. Becayse it is a DB, not a storage quiescence problem.
-
@JaredBusch said in Free Veeam for DGraph Linux Restore:
@Obsolesce said in Free Veeam for DGraph Linux Restore:
The free Veeam you are using in your Windows VMs will not back up VMs via the host... meaning you cannot install the free Veeam edition on your Hyper-V host and expect it to back up your VMs.
Actually it absolutely does do this. You are limited to ad-hoc VeeamZIP creation, but it works perfectly.
Perfectly but not with a database like this. Takes backups as well as the agent. Which is not good.
-
@scottalanmiller said in Free Veeam for DGraph Linux Restore:
@JaredBusch said in [Free Veeam for DGraph Linux
Shit is not, ever, as black and white and Scott tries to make it.
Actually it is black and white. You are pretending it isnt to push your darling product that you always push without looking into what his issue is or understanding how the LVM layer issue is identical between solutions.
Actually, no. You have no idea if this is true. Veeam absolutely can (and should when configured right) use the native guest tools. But it doe snot require it. Making a snapshot form the host has no requirement that the guest OS even do anything.
I also was not pushing hypervisor level as the solutoin. I was asking if it was tried or not.
-
@scottalanmiller said in Free Veeam for DGraph Linux Restore:
@JaredBusch said in Free Veeam for DGraph Linux Restore:
@Obsolesce said in Free Veeam for DGraph Linux Restore:
The free Veeam you are using in your Windows VMs will not back up VMs via the host... meaning you cannot install the free Veeam edition on your Hyper-V host and expect it to back up your VMs.
Actually it absolutely does do this. You are limited to ad-hoc VeeamZIP creation, but it works perfectly.
Perfectly but not with a database like this. Takes backups as well as the agent. Which is not good.
You have no idea if that is the case or not as it was never attempted to our knowledge.
-
@JaredBusch said in Free Veeam for DGraph Linux Restore:
@Obsolesce said in Free Veeam for DGraph Linux Restore:
The free Veeam you are using in your Windows VMs will not back up VMs via the host... meaning you cannot install the free Veeam edition on your Hyper-V host and expect it to back up your VMs.
Actually it absolutely does do this. You are limited to ad-hoc VeeamZIP creation, but it works perfectly.
Yeah you're right, I'm not disagreeing, but I wouldn't use that in a production environment. I don't consider that usable outside of PC or lab use.
-
@Obsolesce said in Free Veeam for DGraph Linux Restore:
@JaredBusch said in Free Veeam for DGraph Linux Restore:
@Obsolesce said in Free Veeam for DGraph Linux Restore:
The free Veeam you are using in your Windows VMs will not back up VMs via the host... meaning you cannot install the free Veeam edition on your Hyper-V host and expect it to back up your VMs.
Actually it absolutely does do this. You are limited to ad-hoc VeeamZIP creation, but it works perfectly.
Yeah you're right, I'm not disagreeing, but I wouldn't use that in a production environment. I don't consider that usable outside of PC or lab use.
Neither do I. But a lot of others do, and it is possible.
-
@scottalanmiller said in Free Veeam for DGraph Linux Restore:
@Obsolesce said in Free Veeam for DGraph Linux Restore:
@scottalanmiller said in Free Veeam for DGraph Linux Restore:
@Obsolesce you already know from this thread that that doesnt solve the problem. You are just repeating the same issue that he was trying to resolve.
VSS causes this issue the same as any other LVM.
Read the thread. Weve beaten this to death. VSS isnt magic.
I will have to read more. I posted after only really reading the OP.
His DB doesnt quiesce and he cant find processes to stop manually. So anything using an LVM whether a Linux agent or Hyper-V's LVM called VSS will be expected to corrupt sometimes. Even when not clustered. Becayse it is a DB, not a storage quiescence problem.
Okay, so it's a DB. I did a quick Google search after reading your comment here. I also searched their website for backup info, nothing. I'm still going to assume there's some way via the DGraph CLI to back up or dump the DB. Something like that can be done while it's running, so no down time, via CRON, before the Host-level backup.
If the thing is just fuxored, there's also the option of using Hyper-V replication to replicate the CentOS VM to another simple host to do some testing, or either to back that up instead.
Try that, if you can, replicate the VM to something else, then spin it up off the network to see if it starts up and test.
Question, if you back up the DGraph database, then after a full VM restore, if you restore the backed up database, will it start then?
I can't read every post atm, so excuse my ignorance if some of this was answered.
-
@Obsolesce said in Free Veeam for DGraph Linux Restore:
@JaredBusch said in Free Veeam for DGraph Linux Restore:
@Obsolesce said in Free Veeam for DGraph Linux Restore:
The free Veeam you are using in your Windows VMs will not back up VMs via the host... meaning you cannot install the free Veeam edition on your Hyper-V host and expect it to back up your VMs.
Actually it absolutely does do this. You are limited to ad-hoc VeeamZIP creation, but it works perfectly.
Yeah you're right, I'm not disagreeing, but I wouldn't use that in a production environment. I don't consider that usable outside of PC or lab use.
I wouldnt go that far. Just very... crufty? Cheap? Good for places where labour is cheap but software is expensive.
-
@JaredBusch said in Free Veeam for DGraph Linux Restore:
@scottalanmiller said in Free Veeam for DGraph Linux Restore:
@JaredBusch said in [Free Veeam for DGraph Linux
Shit is not, ever, as black and white and Scott tries to make it.
Actually it is black and white. You are pretending it isnt to push your darling product that you always push without looking into what his issue is or understanding how the LVM layer issue is identical between solutions.
Actually, no. You have no idea if this is true. Veeam absolutely can (and should when configured right) use the native guest tools. But it doe snot require it. Making a snapshot form the host has no requirement that the guest OS even do anything.
I also was not pushing hypervisor level as the solutoin. I was asking if it was tried or not.
There is no native guest tool to use. I do know this. Making a reliable snap absolutely requires the guest to do something. For things like SQL Server this is automated and made to seem like magic. For things like MongoDB, it just doesnt work.
A snap of corrupt data is still bad data even when the snap is good.
-
@Obsolesce said in Free Veeam for DGraph Linux Restore:
@scottalanmiller said in Free Veeam for DGraph Linux Restore:
@Obsolesce said in Free Veeam for DGraph Linux Restore:
@scottalanmiller said in Free Veeam for DGraph Linux Restore:
@Obsolesce you already know from this thread that that doesnt solve the problem. You are just repeating the same issue that he was trying to resolve.
VSS causes this issue the same as any other LVM.
Read the thread. Weve beaten this to death. VSS isnt magic.
I will have to read more. I posted after only really reading the OP.
His DB doesnt quiesce and he cant find processes to stop manually. So anything using an LVM whether a Linux agent or Hyper-V's LVM called VSS will be expected to corrupt sometimes. Even when not clustered. Becayse it is a DB, not a storage quiescence problem.
Okay, so it's a DB. I did a quick Google search after reading your comment here. I also searched their website for backup info, nothing. I'm still going to assume there's some way via the DGraph CLI to back up or dump the DB. Something like that can be done while it's running, so no down time, via CRON, before the Host-level backup.
If the thing is just fuxored, there's also the option of using Hyper-V replication to replicate the CentOS VM to another simple host to do some testing, or either to back that up instead.
Try that, if you can, replicate the VM to something else, then spin it up off the network to see if it starts up and test.
Question, if you back up the DGraph database, then after a full VM restore, if you restore the backed up database, will it start then?
I can't read every post atm, so excuse my ignorance if some of this was answered.
Yes. We covered that solution... if you backup via the native tool locally THEN any backup tool will work - but restores require an extra step.
That was our "silly but works" option.
-
So, circling back. How is the backup project going?
