Ce site est optimisé pour être consulté depuis un navigateur moderne dans lequel JavaScript est activé.

Bonnes pratiques pour l'organisation des fichiers sur un serveur Hyper-V

ayi

We've got a Hyper-V server set up, et le layout of le files is inconsistent parce que it was set up by plusieurs people. Here are le two différent "templates" that were used:

Template 1

D:\Hyper-V\Virtual Machines\MACHINE_NAME_1\Virtual Hard Disks\MACHINE_NAME_1.vhdx
D:\Hyper-V\Virtual Machines\MACHINE_NAME_1\Virtual Machines\GUID_1
D:\Hyper-V\Virtual Machines\MACHINE_NAME_1\Virtual Machines\GUID_1.xml

D:\Hyper-V\Virtual Machines\MACHINE_NAME_2\Virtual Hard Disks\MACHINE_NAME_2.vhdx
D:\Hyper-V\Virtual Machines\MACHINE_NAME_2\Virtual Machines\GUID_2
D:\Hyper-V\Virtual Machines\MACHINE_NAME_2\Virtual Machines\GUID_2.xml

....

and

Template 2

D:\Hyper-V\Virtual Hard Disks\MACHINE_NAME_1.vhdx
D:\Hyper-V\Virtual Hard Disks\MACHINE_NAME_2.vhdx

D:\Hyper-V\Virtual Machines\GUID_1
D:\Hyper-V\Virtual Machines\GUID_1.xml
D:\Hyper-V\Virtual Machines\GUID_2
D:\Hyper-V\Virtual Machines\GUID_2.xml

Template 1

The argument made FOR Template 1, was that quand you do an export of a VM le export creates a folder avec le machine name, puts separate folders for le disks et vm. Vous pouvez alors simply point to le machine directory quand you run an import.

The argument AGAINST this template style is that it ne make sense for there to be a directory called Virtual Machines si there is seulement one file. The autre argument against is that it appears that that Hyper-V server itself seems to expect that tous hard disks are in one folder, et tous le Virtual Machines are in a différent folder. i.e. it ne create separate folders for chaque VM (execept for le ones nameed by GUID in le Virtual Machines directory)

Template 2

The argument FOR Template 2 is that it seems like that is what Hyper-V expects le layout to be.

The argument AGAINST Template 2, is that you ne peut pas tell qui Virtual Machine files are associated avec a spécifique machine sauf si you look inside le xml files.

J'aimerais love to hear about tout pitfalls to soit layout.

ayi

You really, really want to be able to easily identify qui files belong to qui virtual machine. Even si you lose access to le Hyper-V console.

This comes up quand trying to restore a VM depuis backups. Or quand Hyper-V forgets about tous of votre VMs et you need to import them. Or le VM config files are corrupt, et you have to recreate le VM et point at le old hard drive files (which you now ne peut pas identify, depuis votre config file is corrupt). Or you juste want to quickly check how much disk space chaque VM takes up. Or you need to restore depuis backups où you can see le filenames, mais pas easily read le XML files sans going through le entire restore process first.

Given that, J'aimerais go for something similaire to Template 1, où there is a folder for chaque VM - mais leave out le "Virtual Machines" et "Virtual Machine Hard Disks" subfolders - juste put tous le files related to a VM in a folder avec le VM's name.

You aussi ne need Hyper-V\Virtual machines - pick one of those labels, you ne need both.

So:

D:\Virtual Machines\MACHINE_A\GUID_1.xml
D:\Virtual Machines\MACHINE_A\Machine_a_OS.vhdx
D:\Virtual Machines\MACHINE_A\Machine_a_Data.vhdx

D:\Virtual Machines\MACHINE_B\GUID_2.xml
D:\Virtual Machines\MACHINE_B\Machine_b_OS.vhdx
D:\Virtual Machines\MACHINE_B\Machine_b_Data.vhdx

etc.

Or you might decide you ne need le filenames to match le virtual machine - le folder name is sufficient. Naming it this way would make it easier to clone a VM sans having to worry about renaming c'est files:

D:\VMs\Machine A\GUID_1.xml
D:\VMs\Machine A\OS.vhdx
D:\VMs\Machine A\Data.vhdx

D:\VMs\Machine B\GUID_2.xml
D:\VMs\Machine B\OS.vhdx
D:\VMs\Machine B\SQLData.vhdx
D:\VMs\Machine B\SQLLog.vhdx

The main takeaway here is to organize le files so that by looking at nothing else mais le file structure, you can tell what VM chaque file belongs to, et what that file is for.