Create NFS file share on Hyper-V Server 2016
-
@scottalanmiller said in Create NFS file share on Hyper-V Server 2016:
@dustinb3403 said in Create NFS file share on Hyper-V Server 2016:
@tim_g said in Create NFS file share on Hyper-V Server 2016:
@dashrender said in Create NFS file share on Hyper-V Server 2016:
Awesome!
@tim_g said in Create NFS file share on Hyper-V Server 2016:
The tape drive is attached to HV06.
Tapeserv is a physical box running the TapeBackup Server SOftware.
HV06 contains the tabe backup software "client".
So you've installed a tape backup software agent inside Hyper-V?
Yeah, I can't back anything up from HV06 without the backup client being installed on the host.
The Hyper-V VMs are not the issue at all. Those are all on the MD1000 and being backed up to tape no problems. If I need to restore a VM, I can restore it from tape.
The trick is that I'm trying to get some physical Linux servers to back up to the MD1000 directly, which has to be done via a NFS share.
So create an NFS share on the MD1000, give it 200TB, install agents on your physical Linux servers, and perform bare metal backups directly to the MD1000!
What the hell is so difficult here?
MD1000 is a DAS, can't "make shares" on it.
Partitions then.
-
@tim_g said in Create NFS file share on Hyper-V Server 2016:
@dashrender said in Create NFS file share on Hyper-V Server 2016:
@tim_g said in Create NFS file share on Hyper-V Server 2016:
The Hyper-V VMs are not the issue at all. Those are all on the MD1000 and being backed up to tape no problems. If I need to restore a VM, I can restore it from tape.
What if you need to restore 1 20 Meg file from one of those VMs on HV06? do you have to restore the whole VHD, then mount it somewhere, then pull the file out?
That's crazy talk!Yeah, but that's not a problem because i ONLY need to restore the VHD of the VM that needs to be restored.
However, with the Linux stuff, ALL linux server backups will be in a single VHD. So to restore anything, I'd have to restore the whole VHD first. See here: https://mangolassi.it/post/373710
- You keep saying this and we keep asking why you'd have to restore this and you never say.
- Why does it have to be a single VHD? That, as well, is not a limitation.
-
@dustinb3403 said in Create NFS file share on Hyper-V Server 2016:
@dashrender said in Create NFS file share on Hyper-V Server 2016:
instead of having just one NFS share - make as many NFS shares as you have physical Linux boxes.
Hyper-V on HV06
- Linux VM acting as storage for backups for physical Linux boxes
- /mnt/l01 - NFS share one
- /mnt/l02 - NFS share two
- /mnt/l03 - NFS share thee
Etc. Each mount will be it's own VHD sized as needed to hold the desired backups for that specific physical Linux box.
Which this is essentially creating agents for each Linux server.
Not really, agents would allow for a single store, while being able to restore single FILES, not just single SERVERS.
- Linux VM acting as storage for backups for physical Linux boxes
-
@dustinb3403 said in Create NFS file share on Hyper-V Server 2016:
@scottalanmiller said in Create NFS file share on Hyper-V Server 2016:
@dustinb3403 said in Create NFS file share on Hyper-V Server 2016:
@tim_g said in Create NFS file share on Hyper-V Server 2016:
@dashrender said in Create NFS file share on Hyper-V Server 2016:
Awesome!
@tim_g said in Create NFS file share on Hyper-V Server 2016:
The tape drive is attached to HV06.
Tapeserv is a physical box running the TapeBackup Server SOftware.
HV06 contains the tabe backup software "client".
So you've installed a tape backup software agent inside Hyper-V?
Yeah, I can't back anything up from HV06 without the backup client being installed on the host.
The Hyper-V VMs are not the issue at all. Those are all on the MD1000 and being backed up to tape no problems. If I need to restore a VM, I can restore it from tape.
The trick is that I'm trying to get some physical Linux servers to back up to the MD1000 directly, which has to be done via a NFS share.
So create an NFS share on the MD1000, give it 200TB, install agents on your physical Linux servers, and perform bare metal backups directly to the MD1000!
What the hell is so difficult here?
MD1000 is a DAS, can't "make shares" on it.
Partitions then.
And Tim has never mentioned backing up partitions either.
He's only ever mentioned backing up VHDs and files inside Hyper-V... but I don't know how that would even work. Is there a backup software inside Hyper-V, or one that you can install INTO Hyper-V? -
@tim_g said in Create NFS file share on Hyper-V Server 2016:
@scottalanmiller said in Create NFS file share on Hyper-V Server 2016:
@tim_g said in Create NFS file share on Hyper-V Server 2016:
NON-VHD Scenario
(NFS share from HV06)- TAPE
- VM1
- VM2
- VM3
- VM4
- VM5
- LinuxServer1
- LinuxServer2
- LinuxServer3
- LinuxServer4
- LinuxServer5
VHD Scenario
(NFS share inside a VM)- TAPE
- VM1
- VM2
- VM3
- VM4
- VM5
- VHDX (containing NFS share)
- LinuxServer1
- LinuxServer2
- LinuxServer3
- LinuxServer4
- LinuxServer5
In the latter, to restore LinuxServer5 from Tape, it appears that I would have to restore the whole VHDX the NFS share lives on. That's what I'm trying to avoid.
No, again, this is not correct. The VHD scenario can STILL be just like the top.
I'm afraid I don't knwo what you mean.
Tape > VHD > Linux Server Images
To restore just a single linux server image, won't I have to first restore the VHD?
No?
No, you really don't. What is causing you to believe that you need to backup as a VHD? How were you going to back up Hyper-V's hosted NFS (assuming you could do it)?
- TAPE
-
@dustinb3403 said in Create NFS file share on Hyper-V Server 2016:
@scottalanmiller said in Create NFS file share on Hyper-V Server 2016:
@dustinb3403 said in Create NFS file share on Hyper-V Server 2016:
@tim_g said in Create NFS file share on Hyper-V Server 2016:
@dashrender said in Create NFS file share on Hyper-V Server 2016:
Awesome!
@tim_g said in Create NFS file share on Hyper-V Server 2016:
The tape drive is attached to HV06.
Tapeserv is a physical box running the TapeBackup Server SOftware.
HV06 contains the tabe backup software "client".
So you've installed a tape backup software agent inside Hyper-V?
Yeah, I can't back anything up from HV06 without the backup client being installed on the host.
The Hyper-V VMs are not the issue at all. Those are all on the MD1000 and being backed up to tape no problems. If I need to restore a VM, I can restore it from tape.
The trick is that I'm trying to get some physical Linux servers to back up to the MD1000 directly, which has to be done via a NFS share.
So create an NFS share on the MD1000, give it 200TB, install agents on your physical Linux servers, and perform bare metal backups directly to the MD1000!
What the hell is so difficult here?
MD1000 is a DAS, can't "make shares" on it.
Partitions then.
How does that help?
-
@scottalanmiller said in Create NFS file share on Hyper-V Server 2016:
@tim_g said in Create NFS file share on Hyper-V Server 2016:
@dashrender said in Create NFS file share on Hyper-V Server 2016:
@tim_g said in Create NFS file share on Hyper-V Server 2016:
The Hyper-V VMs are not the issue at all. Those are all on the MD1000 and being backed up to tape no problems. If I need to restore a VM, I can restore it from tape.
What if you need to restore 1 20 Meg file from one of those VMs on HV06? do you have to restore the whole VHD, then mount it somewhere, then pull the file out?
That's crazy talk!Yeah, but that's not a problem because i ONLY need to restore the VHD of the VM that needs to be restored.
However, with the Linux stuff, ALL linux server backups will be in a single VHD. So to restore anything, I'd have to restore the whole VHD first. See here: https://mangolassi.it/post/373710
- You keep saying this and we keep asking why you'd have to restore this and you never say.
- Why does it have to be a single VHD? That, as well, is not a limitation.
Oh, so your saying something like Dash's answer, having a separate NFS share on it's own VHDX to a LInux VM on HV06?
Yeah I suppose that will do it.... that will cut down on the size of restoration from tape.
-
@tim_g said in Create NFS file share on Hyper-V Server 2016:
@scottalanmiller said in Create NFS file share on Hyper-V Server 2016:
@tim_g said in Create NFS file share on Hyper-V Server 2016:
@dashrender said in Create NFS file share on Hyper-V Server 2016:
@tim_g said in Create NFS file share on Hyper-V Server 2016:
The Hyper-V VMs are not the issue at all. Those are all on the MD1000 and being backed up to tape no problems. If I need to restore a VM, I can restore it from tape.
What if you need to restore 1 20 Meg file from one of those VMs on HV06? do you have to restore the whole VHD, then mount it somewhere, then pull the file out?
That's crazy talk!Yeah, but that's not a problem because i ONLY need to restore the VHD of the VM that needs to be restored.
However, with the Linux stuff, ALL linux server backups will be in a single VHD. So to restore anything, I'd have to restore the whole VHD first. See here: https://mangolassi.it/post/373710
- You keep saying this and we keep asking why you'd have to restore this and you never say.
- Why does it have to be a single VHD? That, as well, is not a limitation.
Oh, so your saying something like Dash's answer, having a separate NFS share on it's own VHDX to a LInux VM on HV06?
Yeah I suppose that will do it.... that will cut down on the size of restoration from tape.
My solution is a horrible hack.
-
What's the name of the backup software?
-
What's the name of the backup software?
-
What's the name of the backup software?
-
What's the name of the backup software?
-
Seriously - we need to know the name of the backup software running on that backup server shown in your picture.
-
@scottalanmiller said in Create NFS file share on Hyper-V Server 2016:
@dustinb3403 said in Create NFS file share on Hyper-V Server 2016:
@scottalanmiller said in Create NFS file share on Hyper-V Server 2016:
@dustinb3403 said in Create NFS file share on Hyper-V Server 2016:
@tim_g said in Create NFS file share on Hyper-V Server 2016:
@dashrender said in Create NFS file share on Hyper-V Server 2016:
Awesome!
@tim_g said in Create NFS file share on Hyper-V Server 2016:
The tape drive is attached to HV06.
Tapeserv is a physical box running the TapeBackup Server SOftware.
HV06 contains the tabe backup software "client".
So you've installed a tape backup software agent inside Hyper-V?
Yeah, I can't back anything up from HV06 without the backup client being installed on the host.
The Hyper-V VMs are not the issue at all. Those are all on the MD1000 and being backed up to tape no problems. If I need to restore a VM, I can restore it from tape.
The trick is that I'm trying to get some physical Linux servers to back up to the MD1000 directly, which has to be done via a NFS share.
So create an NFS share on the MD1000, give it 200TB, install agents on your physical Linux servers, and perform bare metal backups directly to the MD1000!
What the hell is so difficult here?
MD1000 is a DAS, can't "make shares" on it.
Partitions then.
How does that help?
His backup software can target individual partitions, which are connected to a Server and shared as NFS.
-
@dashrender said in Create NFS file share on Hyper-V Server 2016:
@tim_g said in Create NFS file share on Hyper-V Server 2016:
@scottalanmiller said in Create NFS file share on Hyper-V Server 2016:
@tim_g said in Create NFS file share on Hyper-V Server 2016:
@dashrender said in Create NFS file share on Hyper-V Server 2016:
@tim_g said in Create NFS file share on Hyper-V Server 2016:
The Hyper-V VMs are not the issue at all. Those are all on the MD1000 and being backed up to tape no problems. If I need to restore a VM, I can restore it from tape.
What if you need to restore 1 20 Meg file from one of those VMs on HV06? do you have to restore the whole VHD, then mount it somewhere, then pull the file out?
That's crazy talk!Yeah, but that's not a problem because i ONLY need to restore the VHD of the VM that needs to be restored.
However, with the Linux stuff, ALL linux server backups will be in a single VHD. So to restore anything, I'd have to restore the whole VHD first. See here: https://mangolassi.it/post/373710
- You keep saying this and we keep asking why you'd have to restore this and you never say.
- Why does it have to be a single VHD? That, as well, is not a limitation.
Oh, so your saying something like Dash's answer, having a separate NFS share on it's own VHDX to a LInux VM on HV06?
Yeah I suppose that will do it.... that will cut down on the size of restoration from tape.
My solution is a horrible hack.
It's not bad.
The bases of hte new SCDPM backup is everything is on VHDXs... that that itself isn't bad.
It's just that in this case... If i have a lot of different server images contained in a single VHD, and then that single VHD is on tape.... and I need to restore a specific server image...
Well, I need to first get that single VHD off of tape, so that I may pull out the server image I need.
But if each Linux server image is in it's own VHD... when I want to restore from tape, I can find the appropriate VHD just for that server and restore that.
-
What's the name of the backup software?
-
What's the name of the backup software?
-
@dashrender said in Create NFS file share on Hyper-V Server 2016:
What's the name of the backup software?
The software is irrelevant... It's a mix of Windows Server Backup, Yosemite Server Backup, and ReaR.
The reason it's irrelevant is because the software cannot change. I have my constraints, and need to find a way to work within them.
-
@tim_g said in Create NFS file share on Hyper-V Server 2016:
@dashrender said in Create NFS file share on Hyper-V Server 2016:
@tim_g said in Create NFS file share on Hyper-V Server 2016:
@scottalanmiller said in Create NFS file share on Hyper-V Server 2016:
@tim_g said in Create NFS file share on Hyper-V Server 2016:
@dashrender said in Create NFS file share on Hyper-V Server 2016:
@tim_g said in Create NFS file share on Hyper-V Server 2016:
The Hyper-V VMs are not the issue at all. Those are all on the MD1000 and being backed up to tape no problems. If I need to restore a VM, I can restore it from tape.
What if you need to restore 1 20 Meg file from one of those VMs on HV06? do you have to restore the whole VHD, then mount it somewhere, then pull the file out?
That's crazy talk!Yeah, but that's not a problem because i ONLY need to restore the VHD of the VM that needs to be restored.
However, with the Linux stuff, ALL linux server backups will be in a single VHD. So to restore anything, I'd have to restore the whole VHD first. See here: https://mangolassi.it/post/373710
- You keep saying this and we keep asking why you'd have to restore this and you never say.
- Why does it have to be a single VHD? That, as well, is not a limitation.
Oh, so your saying something like Dash's answer, having a separate NFS share on it's own VHDX to a LInux VM on HV06?
Yeah I suppose that will do it.... that will cut down on the size of restoration from tape.
My solution is a horrible hack.
It's not bad.
The bases of hte new SCDPM backup is everything is on VHDXs... that that itself isn't bad.
It's just that in this case... If i have a lot of different server images contained in a single VHD, and then that single VHD is on tape.... and I need to restore a specific server image...
Well, I need to first get that single VHD off of tape, so that I may pull out the server image I need.
But if each Linux server image is in it's own VHD... when I want to restore from tape, I can find the appropriate VHD just for that server and restore that.
But why not just backup the physical servers as their own files to their own partition on the MD1000? (Using a better backup appliance, rather than this POS you refuse to name)
It's band-aid and at this point the community might willfully drink 3 bottles of Fireball to end this conversation . . .
-
@tim_g said in Create NFS file share on Hyper-V Server 2016:
@dashrender said in Create NFS file share on Hyper-V Server 2016:
What's the name of the backup software?
The software is irrelevant... It's a mix of Windows Server Backup, Yosemite Server Backup, and ReaR.
The reason it's irrelevant is because the software cannot change. I have my constraints, and need to find a way to work within them.
I don't want it to change - but I DO want to know how it works so we can talk intelligently about each one and what features they offer.
