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:
- I don't know where you got this from. All I want is to be able to back up physical Linux servers directly to the MD1000. The only way I can do this is via NFS. The only way to do this via NFS is by some software that will install on the HV06 host itself and allow me to create and host an NFS share in a folder on the MD1000.
From point 1 - you can't reconfigure your backup software to not backup as a single VHD. You made backing up at the VHD level a requirement.
We may be talking about different things...
VHD = Virtual Hard Disk that a Hyper-V VM and/or Hyper-V VM data lives on...
- VM1 (Fedora 27)
- VHD1 (vm1.vhdx)
- VHD2 (vm1-data.vhdx)
- Lives on the MD1000 & backed up to tape
Where VHD2.vhdx is where the NFS share lives on. So now, VHD2.vhdx is on Tape... and if I want to restore something inside of HVD2.vhdx, i have to restore the ENTIRE THING from tape first, before I can get it.
-
@tim_g said in Create NFS file share on Hyper-V Server 2016:
- The mentioned backup software is what I'm stuck with.
That's not an issue. It's not what you have, it's how it is configured.
-
@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:
- I don't know where you got this from. All I want is to be able to back up physical Linux servers directly to the MD1000. The only way I can do this is via NFS. The only way to do this via NFS is by some software that will install on the HV06 host itself and allow me to create and host an NFS share in a folder on the MD1000.
From point 1 - you can't reconfigure your backup software to not backup as a single VHD. You made backing up at the VHD level a requirement.
We may be talking about different things...
VHD = Virtual Hard Disk that a Hyper-V VM and/or Hyper-V VM data lives on...
- VM1 (Fedora 27)
- VHD1 (vm1.vhdx)
- VHD2 (vm1-data.vhdx)
- Lives on the MD1000 & backed up to tape
Where VHD2.vhdx is where the NFS share lives on. So now, VHD2.vhdx is on Tape... and if I want to restore something inside of HVD2.vhdx, i have to restore the ENTIRE THING from tape first, before I can get it.
We are talking about the same thing. Just you want to backup the VM as an image of that VHD. And I want to back it up from the contents of the VHD - doing it my way doesn't present any of the problems you are trying to overcome.
-
@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:
@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:
- I don't know where you got this from. All I want is to be able to back up physical Linux servers directly to the MD1000. The only way I can do this is via NFS. The only way to do this via NFS is by some software that will install on the HV06 host itself and allow me to create and host an NFS share in a folder on the MD1000.
From point 1 - you can't reconfigure your backup software to not backup as a single VHD. You made backing up at the VHD level a requirement.
We may be talking about different things...
VHD = Virtual Hard Disk that a Hyper-V VM and/or Hyper-V VM data lives on...
- VM1 (Fedora 27)
- VHD1 (vm1.vhdx)
- VHD2 (vm1-data.vhdx)
- Lives on the MD1000 & backed up to tape
Where VHD2.vhdx is where the NFS share lives on. So now, VHD2.vhdx is on Tape... and if I want to restore something inside of HVD2.vhdx, i have to restore the ENTIRE THING from tape first, before I can get it.
We are talking about the same thing. Just you want to backup the VM as an image of that VHD. And I want to back it up from the contents of the VHD - doing it my way doesn't present any of the problems you are trying to overcome.
And how do I get the contents of that VHD (vm1-data.vhdx) onto tape through the main tape backup job that HV06 runs?
-
If that VHD lives on the MD1000, it will be put onto tape with everythign else that's on the MD1000.
-
@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:
@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:
- I don't know where you got this from. All I want is to be able to back up physical Linux servers directly to the MD1000. The only way I can do this is via NFS. The only way to do this via NFS is by some software that will install on the HV06 host itself and allow me to create and host an NFS share in a folder on the MD1000.
From point 1 - you can't reconfigure your backup software to not backup as a single VHD. You made backing up at the VHD level a requirement.
We may be talking about different things...
VHD = Virtual Hard Disk that a Hyper-V VM and/or Hyper-V VM data lives on...
- VM1 (Fedora 27)
- VHD1 (vm1.vhdx)
- VHD2 (vm1-data.vhdx)
- Lives on the MD1000 & backed up to tape
Where VHD2.vhdx is where the NFS share lives on. So now, VHD2.vhdx is on Tape... and if I want to restore something inside of HVD2.vhdx, i have to restore the ENTIRE THING from tape first, before I can get it.
We are talking about the same thing. Just you want to backup the VM as an image of that VHD. And I want to back it up from the contents of the VHD - doing it my way doesn't present any of the problems you are trying to overcome.
And how do I get the contents of that VHD (vm1-data.vhdx) onto tape through the main tape backup job that HV06 runs?
By running a backup from an agent in the VM. Like ReaR which can backup to tape.
-
@tim_g said in Create NFS file share on Hyper-V Server 2016:
If that VHD lives on the MD1000, it will be put onto tape with everythign else that's on the MD1000.
That's a configuration problem. Nothing technically causes that problem.
-
@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:
@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:
@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:
- I don't know where you got this from. All I want is to be able to back up physical Linux servers directly to the MD1000. The only way I can do this is via NFS. The only way to do this via NFS is by some software that will install on the HV06 host itself and allow me to create and host an NFS share in a folder on the MD1000.
From point 1 - you can't reconfigure your backup software to not backup as a single VHD. You made backing up at the VHD level a requirement.
We may be talking about different things...
VHD = Virtual Hard Disk that a Hyper-V VM and/or Hyper-V VM data lives on...
- VM1 (Fedora 27)
- VHD1 (vm1.vhdx)
- VHD2 (vm1-data.vhdx)
- Lives on the MD1000 & backed up to tape
Where VHD2.vhdx is where the NFS share lives on. So now, VHD2.vhdx is on Tape... and if I want to restore something inside of HVD2.vhdx, i have to restore the ENTIRE THING from tape first, before I can get it.
We are talking about the same thing. Just you want to backup the VM as an image of that VHD. And I want to back it up from the contents of the VHD - doing it my way doesn't present any of the problems you are trying to overcome.
And how do I get the contents of that VHD (vm1-data.vhdx) onto tape through the main tape backup job that HV06 runs?
By running a backup from an agent in the VM. Like ReaR which can backup to tape.
Okay, let's say I run my tape backup from the Yosemite agent in the VM. Great, now I have all that NFS share backed up to tape.
But that doesn't grab any of the Windows Server Backup data on the MD1000... only the NFS share that contains physical Linux server backups.
That VM isn['t going to see the rest of the MD1000.
-
Still, I would use Yosemite on the Linux VM to back up to tape, not ReaR. Yosemite works better on linux anyways. I'm ONLY using Yosemite for backing up to Tape.
-
If I use the Yosemite backup agent in the VM, and I configure it to back up the MD1000 (not the NFS share) to tape, it will go over the network I believe.
-
I'm going ot have to test this.
I think I understand what you're saying now.
Still have a single tape back up job, but run it all from the Yosemite backup agent on the VM...
I see, that way I can back up the NFS share directly to tape (not the VHD), and in the same job, have it also back up the Windows Server Backup folders.
-
Am I understanding correctly now?
-
If so, this is all dependent on the bulk of the data (the Windows Server Backup stuff) not having to go over the network.
The physical Linux server backups / NFS stuff can.
Yeah, i'm going to set up a test.
-
@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:
@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:
- I don't know where you got this from. All I want is to be able to back up physical Linux servers directly to the MD1000. The only way I can do this is via NFS. The only way to do this via NFS is by some software that will install on the HV06 host itself and allow me to create and host an NFS share in a folder on the MD1000.
From point 1 - you can't reconfigure your backup software to not backup as a single VHD. You made backing up at the VHD level a requirement.
We may be talking about different things...
VHD = Virtual Hard Disk that a Hyper-V VM and/or Hyper-V VM data lives on...
- VM1 (Fedora 27)
- VHD1 (vm1.vhdx)
- VHD2 (vm1-data.vhdx)
- Lives on the MD1000 & backed up to tape
Where VHD2.vhdx is where the NFS share lives on. So now, VHD2.vhdx is on Tape... and if I want to restore something inside of HVD2.vhdx, i have to restore the ENTIRE THING from tape first, before I can get it.
We are talking about the same thing. Just you want to backup the VM as an image of that VHD. And I want to back it up from the contents of the VHD - doing it my way doesn't present any of the problems you are trying to overcome.
And how do I get the contents of that VHD (vm1-data.vhdx) onto tape through the main tape backup job that HV06 runs?
I never said through the main tape backup job, that's never been something I recommended. We've established that that backup job isn't adequate for the task at hand.
-
@tim_g said in Create NFS file share on Hyper-V Server 2016:
Still, I would use Yosemite on the Linux VM to back up to tape, not ReaR. Yosemite works better on linux anyways. I'm ONLY using Yosemite for backing up to Tape.
Either one, that's fine. Or just use tar
-
@tim_g said in Create NFS file share on Hyper-V Server 2016:
If I use the Yosemite backup agent in the VM, and I configure it to back up the MD1000 (not the NFS share) to tape, it will go over the network I believe.
But the agent on the VM you don't want going to the MD1000, right? You want it going to the tape? Just make the VM on the MD1000 to begin with to get the data TO the MD1000.
-
@tim_g said in Create NFS file share on Hyper-V Server 2016:
Am I understanding correctly now?
I'm not sure anymore, lol.
-
@tim_g said in Create NFS file share on Hyper-V Server 2016:
I'm going ot have to test this.
I think I understand what you're saying now.
Still have a single tape back up job, but run it all from the Yosemite backup agent on the VM...
I see, that way I can back up the NFS share directly to tape (not the VHD), and in the same job, have it also back up the Windows Server Backup folders.
Yes, this is what I've been saying for hours.
Yosemite is the only thing that can see inside Hyper-V AND inside the Linux VM99.Backing up the Windows backup file to yosemite (to the tape) will mean you'll have to restore the entire file for Windows Backup before you can restore a single file from inside that backup... so you end up the same issue as the Linux VMs, FYI.
-
@dashrender said in Create NFS file share on Hyper-V Server 2016:
Scott - is there a way to get the data of the backups of the local VM's on HV06 into a VHD that is also on HV06?
Assume VM01 is the 15 TB VM that needs to be backed up... currently Hyper-V backs it up using Windows backup to from (just go with me) c:\vms\vm01.vhd to e:\backup\backupupfile e: being on the MD1000.
Is there a way to backup VM01 to the filesystem inside VM99 instead? Then pass the tape through to VM99 and backup everything inside there?
Can this be done and never touch the network?So I take it there was no merit here?
-
@dashrender said in Create NFS file share on Hyper-V Server 2016:
@dashrender said in Create NFS file share on Hyper-V Server 2016:
Scott - is there a way to get the data of the backups of the local VM's on HV06 into a VHD that is also on HV06?
Assume VM01 is the 15 TB VM that needs to be backed up... currently Hyper-V backs it up using Windows backup to from (just go with me) c:\vms\vm01.vhd to e:\backup\backupupfile e: being on the MD1000.
Is there a way to backup VM01 to the filesystem inside VM99 instead? Then pass the tape through to VM99 and backup everything inside there?
Can this be done and never touch the network?So I take it there was no merit here?
The Hyper-V VM backups via Windows Server Backup are separated and are not in a single VHD. So it's 15 TB separated into appropriate folders depending on the VM and data. There is no single 15TB VM. It's 70 VMs totaling 15 TB. And another few total TBs from physical Linux servers, that need to be backed up to the MD1000.