Free Veeam for DGraph Linux Restore
-
@DustinB3403 but what problem does that solve that isnt already covered by what he has? The Veeam Linux tools already do that.
-
@Jimmy9008 said in Free Veeam for Linux/Restore:
@scottalanmiller said in Free Veeam for Linux/Restore:
@Jimmy9008 said in Free Veeam for Linux/Restore:
@scottalanmiller said in Free Veeam for Linux/Restore:
Why no cluster? Not enough hardware?
I imagine that will be the end position. But, the decision is not under my control and as it stands its the single instance. We have the hardware though.
But your backup thought process is 100% dependent on there never being a cluster. So if thats a possibility you have to plan for it
That is correct. Will have a chat when the dev guy is in tomorrow to see where this is going.
The devops approach solves this for a cluster or a single node elegantly.
-
@scottalanmiller said in Free Veeam for Linux/Restore:
@DustinB3403 but what problem does that solve that isnt already covered by what he has? The Veeam Linux tools already do that.
He was asking for a free tool to run the script. Windows Task Scheduler is free in that he already has Windows and it's included.
Assuming he has drivers installed on the VM, those drivers talk to the hypervisor. The hypervisor should manage the pausing of all actions when called into action.
-
@DustinB3403 said in Free Veeam for Linux/Restore:
@scottalanmiller said in Free Veeam for Linux/Restore:
@DustinB3403 but what problem does that solve that isnt already covered by what he has? The Veeam Linux tools already do that.
He was asking for a free tool to run the script. Windows Task Scheduler is free in that he already has Windows and it's included.
Assuming he has drivers installed on the VM, those drivers talk to the hypervisor. The hypervisor should manage the pausing of all actions when called into action.
What he has is a free tool that runs the script though.
No, there are no hooks to do what youbare thinking. The hypervisor cant do that. Thats not how it works.
-
@scottalanmiller said in Free Veeam for Linux/Restore:
@DustinB3403 said in Free Veeam for Linux/Restore:
@scottalanmiller said in Free Veeam for Linux/Restore:
@DustinB3403 but what problem does that solve that isnt already covered by what he has? The Veeam Linux tools already do that.
He was asking for a free tool to run the script. Windows Task Scheduler is free in that he already has Windows and it's included.
Assuming he has drivers installed on the VM, those drivers talk to the hypervisor. The hypervisor should manage the pausing of all actions when called into action.
What he has is a free tool that runs the script though.
No, there are no hooks to do what youbare thinking. The hypervisor cant do that. Thats not how it works.
okay, I'm not in a good mood to deal with this crap today.
-
@DustinB3403 said in Free Veeam for Linux/Restore:
@scottalanmiller said in Free Veeam for Linux/Restore:
@DustinB3403 said in Free Veeam for Linux/Restore:
@scottalanmiller said in Free Veeam for Linux/Restore:
@DustinB3403 but what problem does that solve that isnt already covered by what he has? The Veeam Linux tools already do that.
He was asking for a free tool to run the script. Windows Task Scheduler is free in that he already has Windows and it's included.
Assuming he has drivers installed on the VM, those drivers talk to the hypervisor. The hypervisor should manage the pausing of all actions when called into action.
What he has is a free tool that runs the script though.
No, there are no hooks to do what youbare thinking. The hypervisor cant do that. Thats not how it works.
okay, I'm not in a good mood to deal with this crap today.
Its not crap. You are doing the "hypervisors are magic" myth. He already has everything... the free tool, the script, the VSS style layer, the drivers.... but they dont work in a situation like this. Making a second set of them wont change anything. Just make it harder.
-
When you login to the hypervisor using your elevated credentials, and drivers are installed. At least with Veeam ZIP the VM is paused, a snapshot is created and then an Export is made.
That is how Veeam ZIP works, leveraging the drivers within the VM and the Hypervisor tools and creds to perform the backup operation.
-
@DustinB3403 said in Free Veeam for Linux/Restore:
When you login to the hypervisor using your elevated credentials, and drivers are installed. At least with Veeam ZIP the VM is paused, a snapshot is created and then an Export is made.
That is how Veeam ZIP works, leveraging the drivers within the VM and the Hypervisor tools and creds to perform the backup operation.
Sure. But since we know a paused VM wont do it, only a stopped one, whats the goal? What he has already pauses the VM.
-
@scottalanmiller said in Free Veeam for Linux/Restore:
@DustinB3403 said in Free Veeam for Linux/Restore:
@scottalanmiller said in Free Veeam for Linux/Restore:
@DustinB3403 said in Free Veeam for Linux/Restore:
@scottalanmiller said in Free Veeam for Linux/Restore:
@DustinB3403 but what problem does that solve that isnt already covered by what he has? The Veeam Linux tools already do that.
He was asking for a free tool to run the script. Windows Task Scheduler is free in that he already has Windows and it's included.
Assuming he has drivers installed on the VM, those drivers talk to the hypervisor. The hypervisor should manage the pausing of all actions when called into action.
What he has is a free tool that runs the script though.
No, there are no hooks to do what youbare thinking. The hypervisor cant do that. Thats not how it works.
okay, I'm not in a good mood to deal with this crap today.
Its not crap. You are doing the "hypervisors are magic" myth. He already has everything... the free tool, the script, the VSS style layer, the drivers.... but they dont work in a situation like this. Making a second set of them wont change anything. Just make it harder.
What second set? He would be using the damn tools he already has to pause the VM, take a snapshot and export it. On a schedule.
Nothing in what I've read (granted I didn't read the entire topic because its tripe) says that this wouldn't work.
-
@DustinB3403 said in Free Veeam for Linux/Restore:
@scottalanmiller said in Free Veeam for Linux/Restore:
@DustinB3403 said in Free Veeam for Linux/Restore:
@scottalanmiller said in Free Veeam for Linux/Restore:
@DustinB3403 said in Free Veeam for Linux/Restore:
@scottalanmiller said in Free Veeam for Linux/Restore:
@DustinB3403 but what problem does that solve that isnt already covered by what he has? The Veeam Linux tools already do that.
He was asking for a free tool to run the script. Windows Task Scheduler is free in that he already has Windows and it's included.
Assuming he has drivers installed on the VM, those drivers talk to the hypervisor. The hypervisor should manage the pausing of all actions when called into action.
What he has is a free tool that runs the script though.
No, there are no hooks to do what youbare thinking. The hypervisor cant do that. Thats not how it works.
okay, I'm not in a good mood to deal with this crap today.
Its not crap. You are doing the "hypervisors are magic" myth. He already has everything... the free tool, the script, the VSS style layer, the drivers.... but they dont work in a situation like this. Making a second set of them wont change anything. Just make it harder.
What second set? He would be using the damn tools he already has to pause the VM, take a snapshot and export it. On a schedule.
Nothing in what I've read (granted I didn't read the entire topic because its tripe) says that this wouldn't work.
All things he is already doing and dont work. The situation you recommend is the one this thread is about that doesnt work.
-
Open files cant be backed up any more by agent or agentless processes. Both approaches use drivers to pause the VM. Both require hooks to the app, not the file system. Neither exists for Dgraph.
-
I'm now ignoring this topic as I'm not able to handle this conversation today.
Good luck with whatever custom script devops setup you end up purchasing/building/hooking for.
-
@DustinB3403 said in Free Veeam for Linux/Restore:
@scottalanmiller said in Free Veeam for Linux/Restore:
@DustinB3403 said in Free Veeam for Linux/Restore:
@scottalanmiller said in Free Veeam for Linux/Restore:
@DustinB3403 said in Free Veeam for Linux/Restore:
@scottalanmiller said in Free Veeam for Linux/Restore:
@DustinB3403 but what problem does that solve that isnt already covered by what he has? The Veeam Linux tools already do that.
He was asking for a free tool to run the script. Windows Task Scheduler is free in that he already has Windows and it's included.
Assuming he has drivers installed on the VM, those drivers talk to the hypervisor. The hypervisor should manage the pausing of all actions when called into action.
What he has is a free tool that runs the script though.
No, there are no hooks to do what youbare thinking. The hypervisor cant do that. Thats not how it works.
okay, I'm not in a good mood to deal with this crap today.
Its not crap. You are doing the "hypervisors are magic" myth. He already has everything... the free tool, the script, the VSS style layer, the drivers.... but they dont work in a situation like this. Making a second set of them wont change anything. Just make it harder.
What second set? He would be using the damn tools he already has to pause the VM, take a snapshot and export it. On a schedule.
Nothing in what I've read (granted I didn't read the entire topic because its tripe) says that this wouldn't work.
That still doesn't quiesce the database. Which is the problem that the OP is having. The database still has files open when a backup occurs and that causes issues when they go to restore.
This is a job for the native backup tools.
-
@DustinB3403 said in Free Veeam for Linux/Restore:
I'm now ignoring this topic as I'm not able to handle this conversation today.
Good luck with whatever custom script devops setup you end up purchasing/building/hooking for.
Better than ignoring his corruption entirely and acting like he doesnt have a challenge to tackle and pushing a totally useless solution that requires him to change everything and just puts him back to square zero for no reason.
-
@coliver said in Free Veeam for Linux/Restore:
@DustinB3403 said in Free Veeam for Linux/Restore:
@scottalanmiller said in Free Veeam for Linux/Restore:
@DustinB3403 said in Free Veeam for Linux/Restore:
@scottalanmiller said in Free Veeam for Linux/Restore:
@DustinB3403 said in Free Veeam for Linux/Restore:
@scottalanmiller said in Free Veeam for Linux/Restore:
@DustinB3403 but what problem does that solve that isnt already covered by what he has? The Veeam Linux tools already do that.
He was asking for a free tool to run the script. Windows Task Scheduler is free in that he already has Windows and it's included.
Assuming he has drivers installed on the VM, those drivers talk to the hypervisor. The hypervisor should manage the pausing of all actions when called into action.
What he has is a free tool that runs the script though.
No, there are no hooks to do what youbare thinking. The hypervisor cant do that. Thats not how it works.
okay, I'm not in a good mood to deal with this crap today.
Its not crap. You are doing the "hypervisors are magic" myth. He already has everything... the free tool, the script, the VSS style layer, the drivers.... but they dont work in a situation like this. Making a second set of them wont change anything. Just make it harder.
What second set? He would be using the damn tools he already has to pause the VM, take a snapshot and export it. On a schedule.
Nothing in what I've read (granted I didn't read the entire topic because its tripe) says that this wouldn't work.
That still doesn't quiesce the database. Which is the problem that the OP is having. The database still has files open when a backup occurs and that causes issues when they go to restore.
This is a job for the native backup tools.
And nothing but the native tools. The onky viable work around is a deep investigation into what is holding the files open and a bunch of silly scripting or a full power down of the VM.
-
@scottalanmiller said in Free Veeam for Linux/Restore:
@DustinB3403 said in Free Veeam for Linux/Restore:
I'm now ignoring this topic as I'm not able to handle this conversation today.
Good luck with whatever custom script devops setup you end up purchasing/building/hooking for.
Better than ignoring his corruption entirely and acting like he doesnt have a challenge to tackle and pushing a totally useless solution that requires him to change everything and just puts him back to square zero for no reason.
With a backup that cant be relied upon.
-
@Jimmy9008 said in Free Veeam for Linux/Restore:
@scottalanmiller said in Free Veeam for Linux/Restore:
@DustinB3403 said in Free Veeam for Linux/Restore:
I'm now ignoring this topic as I'm not able to handle this conversation today.
Good luck with whatever custom script devops setup you end up purchasing/building/hooking for.
Better than ignoring his corruption entirely and acting like he doesnt have a challenge to tackle and pushing a totally useless solution that requires him to change everything and just puts him back to square zero for no reason.
With a backup that cant be relied upon.
Exactly. Its crash consistent only.
-
@scottalanmiller said in Free Veeam for Linux/Restore:
a full power down of the VM
Which isn't out of the question... not really. Does this database need to be up 100% of the time?
-
@coliver said in Free Veeam for Linux/Restore:
@scottalanmiller said in Free Veeam for Linux/Restore:
a full power down of the VM
Which isn't out of the question... not really. Does this database need to be up 100% of the time?
Not 100% of the time. No.
But equally, daily downtime just for purposes of a backup is too frequent, even if only a few minutes. Its something we can plan for and will find a way. May be the case of just using the built in backup tool, and having documented rebuild process should the VM fail.
-
@coliver said in Free Veeam for Linux/Restore:
@scottalanmiller said in Free Veeam for Linux/Restore:
a full power down of the VM
Which isn't out of the question... not really. Does this database need to be up 100% of the time?
No. But kinda silly.
