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.
-
@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:
@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:
There is a single Tape backup job that is ran from HV06, which backs up the MD1000 to Tape.
How is this possible? Do you have backup software running inside Hyper-V that reads all the VHDX's directly from Hyper-V and backs them up?
I am backing up each VM to the MD1000 via HV06 on the hypervisor level.
I'm not actually sure what this mean? You're backing up the VMs on HV06 (internal storage) to the MD1000 before spinning it to tape?
He is taking a block level backup of HV06 and saving it to the MD1000.
That is why the LinuxServer#'s would all have to be opened to restore just one file. It's just stupid to continue the conversation, unless @Tim_G realizes that he needs to change the way the backups are created and saved on the MD1000.
-
@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:
@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:
There is a single Tape backup job that is ran from HV06, which backs up the MD1000 to Tape.
How is this possible? Do you have backup software running inside Hyper-V that reads all the VHDX's directly from Hyper-V and backs them up?
I am backing up each VM to the MD1000 via HV06 on the hypervisor level.
I'm not actually sure what this mean? You're backing up the VMs on HV06 (internal storage) to the MD1000 before spinning it to tape?
Yes. The MD1000 contains on-prem backups for a given retention period.
The MD1000 is then archived to tape for off-site storage for a different retention period.
-
@stacksofplates 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:
@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:
There is a single Tape backup job that is ran from HV06, which backs up the MD1000 to Tape.
How is this possible? Do you have backup software running inside Hyper-V that reads all the VHDX's directly from Hyper-V and backs them up?
I am backing up each VM to the MD1000 via HV06 on the hypervisor level. VM backup is agentless.
OK - Is there an agent option?
There doesn’t need to be. Mount the VHD on the host and have it back up that directory. Then EVERY Linux server on that NFS export will be backed up directly to tape.
Assuming the agent inside Hyper-V... can a mounted VHD be seen by that agent to see the files to back them up? I'm guessing it can't. From the sounds of it.. the agent inside Hyper-V can only see the VHDs. Hence the issue.
-
@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?
-
@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?
I cannot create an NFS share on the MD1000 because HV06 (the server the MD1000 is attached to) is running Hyper-V Server.
-
@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! -
@dashrender said in Create NFS file share on Hyper-V Server 2016:
@stacksofplates 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:
@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:
There is a single Tape backup job that is ran from HV06, which backs up the MD1000 to Tape.
How is this possible? Do you have backup software running inside Hyper-V that reads all the VHDX's directly from Hyper-V and backs them up?
I am backing up each VM to the MD1000 via HV06 on the hypervisor level. VM backup is agentless.
OK - Is there an agent option?
There doesn’t need to be. Mount the VHD on the host and have it back up that directory. Then EVERY Linux server on that NFS export will be backed up directly to tape.
Assuming the agent inside Hyper-V... can a mounted VHD be seen by that agent to see the files to back them up? I'm guessing it can't. From the sounds of it.. the agent inside Hyper-V can only see the VHDs. Hence the issue.
That’s a pretty sad backup application if it can’t backup anything on the host at all.
-
@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
-
@tim_g 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?
I cannot create an NFS share on the MD1000 because HV06 (the server the MD1000 is attached to) is running Hyper-V Server.
Why can't you create an share on this MD1000, attach it to a VM share the attachment out as NFS and then backup the Linux Servers?
You're stating that the MD1000 can only do 1 thing at a time.
And it may, but you haven't stated so as of yet. . . .
-
@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:
@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?
I cannot create an NFS share on the MD1000 because HV06 (the server the MD1000 is attached to) is running Hyper-V Server.
Why can't you create an share on this MD1000, attach it to a VM share the attachment out as NFS and then backup the Linux Servers?
You're stating that the MD1000 can only do 1 thing at a time.
And it may, but you haven't stated so as of yet. . . .
The MD1000 is basically just a hard drive inside of a physical server running the free Hyper-V Server 2016.
I can have multiple partitions on the MD1000 (which I already do), but that's about it. They HOST sees the MD1000 as a hard drive. And being that the HOST isn't running Windows (it's running Hyper-V Server), I cannot create an NFS share located on the MD1000.
-
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.
- Linux VM acting as storage for backups for physical Linux boxes
-
@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.
Hmm, that's a good idea... and also prevents me from having to restore everything to get at the one I want.
- Linux VM acting as storage for backups for physical Linux boxes
-
@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.
- Linux VM acting as storage for backups for physical Linux boxes
-
@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.
This will allow (what appears to be horrible backup software) to backup each separate VHD, and then only the associated VHD need be restore from tape when that physical Linux box needs to be restore from a tape based source.
- Linux VM acting as storage for backups for physical Linux boxes
-
@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.
- TAPE
-
@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:
There is a single Tape backup job that is ran from HV06, which backs up the MD1000 to Tape.
How is this possible? Do you have backup software running inside Hyper-V that reads all the VHDX's directly from Hyper-V and backs them up?
I am backing up each VM to the MD1000 via HV06 on the hypervisor level. VM backup is agentless.
Right, stop doing that
"At the hypervisor level" is not something we often advise and regardless about its general utility, it clearly doesn't work here. So just don't do that. -
Tim - why won't you tell us the backup software name? Embarrassed by it?
-
@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:
@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:
There is a single Tape backup job that is ran from HV06, which backs up the MD1000 to Tape.
How is this possible? Do you have backup software running inside Hyper-V that reads all the VHDX's directly from Hyper-V and backs them up?
I am backing up each VM to the MD1000 via HV06 on the hypervisor level. VM backup is agentless.
OK - Is there an agent option?
Has to be, or he'd not be able to backup files hosted from Hyper-V directly ruling out his plan anyway.
-
@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?
- TAPE
