Create NFS file share on Hyper-V Server 2016
-
@dashrender said in Create NFS file share on Hyper-V Server 2016:
@scottalanmiller said in Create NFS file share on Hyper-V Server 2016:
What I'm unclear on, is if BOTH the initial server AND the backup host have failed at the same time, why do we want to restore a single file?
I don't believe that is the failure situation we're talking about here.
If there wasn't a failure, he could restore directly from the existing NFS share.
-
There is a single Tape backup job that is ran from HV06, which backs up the MD1000 to Tape.
The idea is that this MD1000 will contain backups of all HV01 vms, HV06 vms, and physical Linux server backups.
So all of that will be backed up to tape in one big "swoop".
Each VM is has it's backup on the MD1000, and each VM backup is archived to Tape. To restore a HV06 VM, I simply can restore just that VM from a Tape. No problem there.
In order to back up the physical Linux servers to the MD1000, I NEED an NFS share.
This NFS share needs to be on the MD1000.
HV06 can't do an NFS share because it's Hyper-V Server.
If I create a VM on HV06 to host an NFS share, then any Linux server I back up to that NFS share will be located in a single VHDX.
-
@dustinb3403 said in Create NFS file share on Hyper-V Server 2016:
@scottalanmiller said in Create NFS file share on Hyper-V Server 2016:
What I'm unclear on, is if BOTH the initial server AND the backup host have failed at the same time, why do we want to restore a single file?
I've had cases where entire systems have gone up, and literally nothing but a single Crystal Report file was critical for production.
So I can understand the need to restore just a single file, as that file can be run anywhere, once you have a working system on which to run it.
Yes, but this is a DOUBLE system failure we are talking about. He has to lose the original AND lose the backup, all at once.
-
@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.
The idea is that this MD1000 will contain backups of all HV01 vms, HV06 vms, and physical Linux server backups.
So all of that will be backed up to tape in one big "swoop".
That would impact the Hyper-V backups the same as the Linux VM ones.
-
@tim_g said in Create NFS file share on Hyper-V Server 2016:
If I create a VM on HV06 to host an NFS share, then any Linux server I back up to that NFS share will be located in a single VHDX.
Which, we've established, has no downsides and is ideal. So this is definitely the way to go.
Since having a VHDX in no way implies that you'll back it up that way.
-
@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:
What I'm unclear on, is if BOTH the initial server AND the backup host have failed at the same time, why do we want to restore a single file?
I've had cases where entire systems have gone up, and literally nothing but a single Crystal Report file was critical for production.
So I can understand the need to restore just a single file, as that file can be run anywhere, once you have a working system on which to run it.
Yes, but this is a DOUBLE system failure we are talking about. He has to lose the original AND lose the backup, all at once.
Yeah no, I understand. I was just answering your question, as to why a single file may be more important than every VM.
-
@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 said in Create NFS file share on Hyper-V Server 2016:
What I'm unclear on, is if BOTH the initial server AND the backup host have failed at the same time, why do we want to restore a single file?
I've had cases where entire systems have gone up, and literally nothing but a single Crystal Report file was critical for production.
So I can understand the need to restore just a single file, as that file can be run anywhere, once you have a working system on which to run it.
Yes, but this is a DOUBLE system failure we are talking about. He has to lose the original AND lose the backup, all at once.
Yeah no, I understand. I was just answering your question, as to why a single file may be more important than every VM.
Right, but my question is in the case of double system failure, when you've lost BOTH the servers AND the backups, at that extreme point, when do we care?
-
OK we've been told that the backup software can only backup to a NFS share - ok, nothing really wrong with that...
Now we're (OK ME) assuming that the backup software we're talking about is the software that's on the Linux physical machines. So that backup is stored somewhere - anywhere, that has a NFS share on it.Though - now I'm wondering - how does the backup software work for the Linux VM that's ON the HV06 host? Tim mentioned that the software has to backup locally because it's 15TB and over the network would take to long.
SOOoooo how does that transfer happen? Do you need to create a partition on thd MD1000 that will be mounted directly to the Linux VM on the HV06 so that a "local" type backup is performed at Line Speed?Now my next question is - What software is in use on the Tape drive? How does the tape drive on the backup server (seen in picture) get the data - what software is pulling in that data?
-
@scottalanmiller said in Create NFS file share on Hyper-V Server 2016:
@dashrender said in Create NFS file share on Hyper-V Server 2016:
@scottalanmiller said in Create NFS file share on Hyper-V Server 2016:
What I'm unclear on, is if BOTH the initial server AND the backup host have failed at the same time, why do we want to restore a single file?
I don't believe that is the failure situation we're talking about here.
If there wasn't a failure, he could restore directly from the existing NFS share.
Unless he wanted to restore a backup that was done say 3 months ago.
-
@dashrender said in Create NFS file share on Hyper-V Server 2016:
@scottalanmiller said in Create NFS file share on Hyper-V Server 2016:
@dashrender said in Create NFS file share on Hyper-V Server 2016:
@scottalanmiller said in Create NFS file share on Hyper-V Server 2016:
What I'm unclear on, is if BOTH the initial server AND the backup host have failed at the same time, why do we want to restore a single file?
I don't believe that is the failure situation we're talking about here.
If there wasn't a failure, he could restore directly from the existing NFS share.
Unless he wanted to restore a backup that was done say 3 months ago.
Even then, if he kept his versioning there he could, which is the expectation as it is a backup repo.
-
@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?
-
@scottalanmiller said in Create NFS file share on Hyper-V Server 2016:
@dashrender said in Create NFS file share on Hyper-V Server 2016:
@scottalanmiller said in Create NFS file share on Hyper-V Server 2016:
@dashrender said in Create NFS file share on Hyper-V Server 2016:
@scottalanmiller said in Create NFS file share on Hyper-V Server 2016:
What I'm unclear on, is if BOTH the initial server AND the backup host have failed at the same time, why do we want to restore a single file?
I don't believe that is the failure situation we're talking about here.
If there wasn't a failure, he could restore directly from the existing NFS share.
Unless he wanted to restore a backup that was done say 3 months ago.
Even then, if he kept his versioning there he could, which is the expectation as it is a backup repo.
/sigh.. it's past what storage allows for - gee do we really need this spelled out?
-
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.
- TAPE
-
Going back to respond to questions.... give me some time!
-
-
@dashrender 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".
-
@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.
So don't backup using this mechanism.
Backup all of your linux servers individually, where is this mandate that you need to backup in this method?
- TAPE
-
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?
-
@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.
-
@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?
