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.
-
@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.
-
@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:
@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.
OK none of that changes my question.
-
Key Points:
- The bulk of the data (about 15 TB) comes from about 70 VMs on HV06 being backed up onto the direct-attached MD1000 DAS via SAS cable.
- A few TB worth of physical Linux server backups also need to end up on the MD1000. This has to be done remotely via an NFS share, either hosted from HV06 or a VM running on HV06 (with NFS share data stored on the MD1000).
Goals:
- The bulk data (15 TB of VM backups) should not touch the network. They should be transferred directly from the MD1000 to the Tape.
- The few TB of physical Linux backups needs to be on the MD1000, and needs to be backed up to tape. This CAN be done over the network, but needs to be part of the same (single) tape backup job. (which is just an additional "location" to add in the configuration)
- I don't want to have to restore any more data from Tape than what is needed. Example: I don't want to have to restore ALL Linux server backups from tape in order to restore a single Linux server.
-
@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:
@scottalanmiller Why does this need exist to backup from the VM directly to tape?
He is currently backup to Disk first and then to tape.
Why not use the same approach, but with an agent within the VM.
Backup to the same Disk, and let whatever is managing the Disk and Tape copy the backup to tape?
Huh?
Because "the VM" and "to a disk" are the same thing here. So how do you get from the VM to the tape if you don't let the VM talk to the tape?
You said conflicting things.
My point is, his physical linux systems, can be backed up to a VM on Hyper-V which would get it's storage from the MD1000.
Then from Hyper-V use what ever tape solution he has to copy the file to tape.
Um, have you even read this thread? That's what he was ALREADY doing that he's trying to fix.
Nevermind, I must be tired
-
A VM (the VHD which lives solely on the MD) could act like a NAS - so the Windows Server backup solution could backup to that VM, the physical servers can all backup to this "NAS" via the NFS,
Then you can use Yosemite to backup the contents of the "NAS" to the tape via passthrough to the tape.Even if you have to use the network, you should be able to use a 10 GB vNetwork inside the host, never touching the physical network outside the box for the data that lives on the HV06 host.
-
@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:
@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.
OK none of that changes my question.
Oh I see the question. Yes you can pass a tape drive to a VM using SW tape redirector... but it's slower.
I have a few things to test, but i'm going in order of least work required. So first I'm going to try the following:
- Set up Linux VM to host an NFS share in a .VHDX on the MD1000.
- Make sure that .VHDX is EXCLUDED in the main tape backup job.
- Install Yosemite client in the Linux VM hosting the NFS share.
- See if I can configure Yosemite to:
- Back up Hyper-V Backups directly from MD1000 to tape (as they currently are)
- Back up contents of NFS share to tape.
