Umxokelelwane wesnapshot womatshini wenyani owaphukileyo (.VMDK / .VHDX / .QCOW2) kunye nokuhlangula idisk¶

Xa imveliso Virtual Machine (VM) on VMware ESXi / Workstation, Microsoft Hyper-V, Proxmox VE / QEMU-KVM, okanye Oracle VirtualBox ngequbuliso ukwala umbane emva kokuba umsebenzi wogcino ungaphumeleli, idatastore iphuma kwindawo yedisk.0 bytes free), okanye umlawuli uchukumisa ifayile ye-snapshot, ukucofa okukodwa koloyiko kunokucima iinyanga okanye iminyaka yedatha yeshishini eliphilayo. Iifoto zoomatshini obonakalayo ** azikho i-backups epheleleyo ezimeleyo **; ziethe-ethe Khuphela-ngoBhala (CoW) idelta differencing chain (*-000001-delta.vmdk, *.avhdx, okanye ifayile exhasayo .qcow2 izinto ezingaphaya) apho ibhloko nganye ebhaliweyo ukusukela oko kwathathwa umfanekiso okhawulezayo uhlala ngaphakathi komntwana iifayile zedelta, ngelixa isiseko sediski soqobo sihleli emkhenkceni kwixesha elidlulileyo.

Ukuba ubona iimpazamo ezifana "The parent virtual disk has been modified since the child was created (Parent CID does not match)" kwiVMware, "Cannot boot: The chain of virtual hard disks is broken" kwi-Hyper-V, okanye "Could not open backing file: L1/L2 table corrupted" kwiQEMU/Proxmox, ukwalatha kwakhona iVM ngokuthe ngqo kwiBase Disk (flat.vmdk okanye isiseko .vhdx) kwaye ukuyivula kuyingozi. Ukwenza oko kuqalisa iseva njengoko ibikhona kwiinyanga ezi-6 ezidlulileyo xa umfanekiso wokuqala wawusenziwa, ingasebenzi ngoko nangoko ikhonkco lomzali-omntwana we-GUID/CID kunye nokunikezela ngesnapshot nganye ye-delta ukusukela ngaloo mhla iyinkedama kwaye ayidityaniswa.

Esi sikhokelo sibonelela ngenyathelo ngenyathelo lokwakhiwa ngokutsha kwetsheyini elikhawulezayo elingonakalisiyo, ukulungiswa kweheader-descriptor-file, kunye neeprothokholi zokutsalwa kwefayile yeendwendwe eziphuma ngaphandle kwebhendi ezisekwe kwiVMware nguBroadcom Knowledge Base Articles (KB 1007969 / 316578 kunye ne KB 1002511), Microsoft Hyper-V Merge-VHD kwaye Set-VHD iinkcukacha zobunjineli, QEMU qemu-img kwaye libguestfs (guestmount) imigangatho yomthetho, kunye ne-NIST Special Publication 800-86.

Yenza oku ngoku¶

Ukuba umatshini wenyani uyala ukuqalisa okanye uphosa ikhonkco elikhawulezayo elaphukileyo / eyonakeleyo yempazamo yedisk yenyani:

1. UNGAZE uhlele izicwangciso zeVM ukuqala ngqo kwiBase Disk (Server.vmdk okanye Server.vhdx) xa idelta ithatha umfanekiso (-000001.vmdk okanye .avhdx) ikhona kulawulo. Lo mzuzu inkqubo yokusebenza yondwendwe iqala ngokuthe ngqo kwisiseko somzali kwidiski nokuba yimizuzwana emi-2, undwendwe lweOS lubhala izitampu zexesha lokuqalisa kunye neNTFS/ext4 uhlaziyo lwejenali kwisiseko sediski, ilungisa umzali diski ID yomxholo (CID) kwiVMware okanye I-GUID yoQhagamshelwano/Isitampu sexesha kwi-Hyper-V. Laa buti inye yophula lonke ikhonkco leefoto zomntwana ezixhomekeke kwisiseko sediski ehlala isuntswana-kumkhenkce. Ukuba igumbi lakho leseva lifumana umlilo osebenzayo, ukusilela kokupholisa, okanye ingozi yomzimba, phuma kwaye utsalele umnxeba kwinombolo yakho yexesha likaxakeka (911 eUnited States naseKhanada, 112 ngaphesheya kweEuropean Union, 999 eUnited Kingdom) okanye khangela amanani kaxakeka.
2. UNGAZE ucime .avhdx, -delta.vmdk, okanye -sesparse.vmdk iifayile kwiWindows Explorer okanye kwi-ESXi Datastore Browser ukuze "ukhulule isithuba sedisk." Ngokungafaniyo neefayile zexeshana eziqhelekileyo, .avhdx kwaye -delta.vmdk iifayile ** NGABA eyakho yangoku ephilayo hard drive **. Ukuba i-snapshot yenziwe kwiinyanga ze-8 ezidlulileyo ngumsebenzi ogciniweyo weVeeam / CommVault kwaye ushiye uqhuba, i-100 ipesenti yentengiselwano nganye yedatha, i-invoyisi, kunye nefayile eyenziwe ngexesha leenyanga ze-8 zokugqibela zigcinwa ngaphakathi kwezo .avhdx okanye -delta.vmdk iifayile. Ukuzicima kususa yonke idatha eyenziwe ukusukela oko kuqale umfanekiso okhawulezayo.
3. ** Khuphela okanye ulinganise zonke .vmdk, .vhdx/.avhdx, okanye .qcow2 iifayile kumthamo wangaphandle / wesibini wogcino NGAPHAMBI kokusebenzisa naluphi na udibaniso, ukuzinikela, okanye umyalelo wokulungisa.** Ukudibanisa ikhonkco elikhawulezayo kubhala zonke iibhloko zedelta ngasemva kwidiski yomzali kwindawo. Ukuba udibaniso aluphumeleli phakathi ngenxa yecandelo elibi lediski okanye ugcino lwedatha impazamo epheleleyo, zombini umzali kunye nomntwana iidiski zonakele ngaphandle kokuba uthathe ifayile ekrwada kuqala.
4. Ukuba i-hypervisor ayiphumelelanga ngenxa yokuba umphathi weDatastore / uMqulu ubethe i-100% igcwele (No space left on device), UNGAZE uzame uku "Cima / Hlanganisa ii-Snapshots" ude wongeze isithuba esikhululekileyo okanye uthelekise ugcino lwedatha enkulu. Ukuhlanganisa ikhonkco leefoto ezininzi kufuna isithuba sokukrola okwexeshana esilingana nobukhulu bedelta yediski enkulu. Ukuzama ukudibanisa kwi-99% yedatha egcweleyo iya kutshabalalisa i-hypervisor mid-commit.
5. Imephu oyena Mzali -> Ikhonkco lokuxhomekeka komntwana usebenzisa imiyalelo yokuhlola ukufunda kuphela (vmkfstools -e, Get-VHD, okanye qemu-img info --backing-chain) phambi kokubamba i-byte enye. Wonke umfanekiso okhawulezayo weheader ubiza ngokuthe ngqo igama lefayile yomzali kunye ne-ID ye-cryptographic yomzali elindele ukuhlala ngqo phezu kwayo.

flowchart TD
    A["I-VM Yala UkuQalisa: Itsheyini le-Snapshot elaphukileyo, Ukungafani kwe-CID yoMzali, okanye i-VMDK/VHDX/QCOW2 eyonakeleyo"] --> B["YIMISA: Sukuvula idisk esisiseko ngokuthe ngqo, kwaye Sukucima naziphi na iifayile ze-delta.vmdk okanye .avhdx"]
    B --> C["Inyathelo 1: Jonga iNdawo yogcino lweNdawo / iNdawo yaMahala yeVolumu (`df -h` / `esxcli uluhlu lwenkqubo yokugcina iifayile`)"]
    C --> D["Inyathelo lesi-2: Khuphela zonke iziseko kunye neefayile ze-snapshot kwi-backup yesibini ye-NAS/SAN/USB drive ngaphambi kokuguqula"]
    D --> E{"Yeyiphi iHypervisor / iFamathi yeDiskhi ebonakalayo echaphazelekayo?"}
    E -->|"1. VMware ESXi / Indawo yokusebenzela (.vmdk / -flat.vmdk / -delta.vmdk / -sesparse.vmdk)"| F["Jonga izichazi zesicatshulwa (`ikati *.vmdk`) & khangela ikhonkco (`vmkfstools -e Server-000002.vmdk`)"]
    F --> G{"Yintoni impazamo yeVMware VMDK?"}
    G -->|"Ukungafani kweCID yomzali (`umzaliCID .= iCID yomzali`)"| H["Hlela inkcazo yombhalo womntwana `.vmdk` ukuze `umzaliCID` ingqinelane ne `CID` yomzali, OKANYE thelekisa idiski yegqabi elisebenzayo kwiVMDK entsha edityanisiweyo (`vmkfstools -i`)"]
    G -->|"Akukho 1-KB inkcazo yokubhaliweyo `.vmdk` (Kuphela `-flat.vmdk` enkulu kakhulu ekhoyo)"| I["Bala ubungakanani bebhayithi echanekileyo / amacandelo angama-512 kwaye uphinda wenze isicatshulwa esicacileyo `.vmdk` nge `vmkfstools -c`"]
    E -->|"2. Microsoft Hyper-V (.vhdx kunye .avhdx chain)"| J["Jonga ikhonkco ukusuka kwentsha `.avhdx` ukuya phezulu: `Fumana-VHD -Indlela *.avhdx | Khetha iNdlela, iNdlela yoMzali`"]
    J --> K["Phinda uqhagamshele isalathi somzali esaphukileyo (`Set-VHD -Path child.avhdx -ParentPath parent.vhdx -IgnoreIdMismatch`) okanye ukudibanisa ngaphandle kweintanethi (`Dibanisa-VHD`)"]
    E -->|"3. Proxmox / KVM / QEMU (.qcow2) okanye VirtualBox (.vdi)"| L["Khangela `ulwazi lweqemu-img --backing-chain`; lungisa i-refcount/L2 tables (`qemu-img khangela -r all`) okanye buyisela kwakhona (`qemu-img rebase -u`)"]
    H --> M["I-Out-of-Band File Rescue Fallback: Nyusa naliphi na ikhonkco ngqo kwimowudi yokufunda-Kuphela nge `guestmount --ro` okanye `7-Zip` / `UFS Explorer`"]
    I --> M
    K --> M
    L --> M

Ukuqonda indlela amakhonkco esnapshot oomatshini asebenza ngayo ngokwenene¶

Nokuba usebenzisa i-VMware ESXi, iMicrosoft Hyper-V, iProxmox/KVM, okanye i-VirtualBox, yonke i-hypervisor isebenzisa i-snapshots isebenzisa ulwakhiwo olusisiseko olufanayo: uluhlu oludityanisiweyo oludityanisiweyo lweeDiski zoMzali-Kuphela kunye neDiski yokuFunda-Bhala yoMntwana yeDelta.

[Base Disk: Server.vmdk / Server.vhdx]  <-- Frozen Read-Only at Snapshot 1 (e.g., Jan 1)
         ^
         | (Points to Parent Path + Parent CID/GUID: 1234abcd)
[Snapshot 1: Server-000001.vmdk / Server_A.avhdx]  <-- Frozen Read-Only at Snapshot 2 (e.g., June 1)
         ^
         | (Points to Parent Path + Parent CID/GUID: 5678ef01)
[Snapshot 2 (Active Leaf): Server-000002.vmdk / Server_B.avhdx]  <-- Active Read/Write Today (Oct 31)

• Xa iVM ifuna ukubhala ibhloko entsha namhlanje, ibhala KUPHELA kwifayile yegqabi elisezantsi (Snapshot 2).
• Xa iVM ifuna ukufunda ibhloko namhlanje, i-hypervisor iyahlola Snapshot 2 Ekuqaleni. Ukuba loo bloko yatshintshwa ukususela ngoJuni 1, ifundeka kuyo Snapshot 2. Ukuba akunjalo, ijonge phezulu ikhonkco Snapshot 1. Ukuba ayilungiswanga nalapho, ifunda ibhloko yokuqala ukusuka kwi Base Disk.
• Kutheni amatyathanga eqhawuka: Wonke umfanekiso okhawulezayo womntwana ugcina amanqaku amabini angqongqo kwiheda yawo: **(1) Indlela yefayile yomzali wayo osondeleyo **, kunye (2) ne-32-bit Content ID (CID kwi-VMware) okanye i-128-bit yoQhagamshelwano lwe-GUID (ParentUniqueId in Hyper-V) eyenziwa ngokutsha ngalo lonke ixesha idiski yomzali ivulelwa ukubhala. Ukuba nabani na ususa ifayile, athiya ngokutsha incwadi eneenkcukacha, okanye anyuse ngokufutshane idiski yomzali kwindlela yokufunda-bhala, umzali CID / GUID utshintsho, kwaye i-hypervisor ngokukhawuleza iyala ukukhwela i-snapshot yomntwana ukuthintela ukonakala kwebhloko ethe cwaka.

Track 1: Rescuing VMware ESXi & Workstation .vmdk amatyathanga esnapshot¶

Kwi-VMware ESXi, idiski enye enenyani eneneni iqulathe iifayile ezimbini ezahlukeneyo ezahlukileyo zesiseko sediski kwaye iifayile ezimbini ezahlukeneyo kumfanekiso okhawulezayo: 1. Encinci (-500-byte) iFayile yokuchaza umbhalo ongenanto (Server.vmdk kwaye Server-000001.vmdk) ebamba i CID, parentCID, ijiyometri yedisk, kunye nelona gama lefayile yobungakanani bokubini. (Qaphela: Isitokhwe se-ESXi Datastore Browser web GUI ifihla izibini -flat.vmdk kwaye -sesparse.vmdk iifayile zokubini kwaye ibonisa kuphela i icon enye edityanisiweyo, KUFUNEKA usebenzise i SSH iseshoni yesiphelo sendlela kumamkeli we ESXi ukubona iifayile eziyinyani). 2. IFayile yoKwandiswa kweDatha yokubini yeegigabhayithi ezininzi (Server-flat.vmdk kwidiski yesiseko, kunye Server-000001-sesparse.vmdk okanye Server-000001-delta.vmdk kumfanekiso okhawulezayo ngamnye).

Imeko 1A: Ukulungisa "The parent virtual disk has been modified since the child was created (Parent CID mismatch)"¶

1. SSH kwinginginya ye-ESXi kwaye ujonge kuvimba wedatha weVM:

   cd /vmfs/volumes/<Datastore_Name>/<VM_Folder_Name>/
   ls -la *.vmdk
   

2. Shicilela i CID, parentCID, kwaye parentFileNameHint kuyo yonke inkcazo yokubhaliweyo .vmdk iifayile kanye: (Okubalulekileyo: Baleka kuphela cat okanye grep kwingcaciso yombhalo omncinci we-500-byte .vmdk iifayile, HAYI kwi-multi-gigabyte -flat.vmdk okanye -sesparse.vmdk iifayile).

   grep -E "CID|parentFileNameHint|Extent description" -A 2 Server.vmdk Server-00000*.vmdk
   

3. Thelekisa i CID yomzali ngamnye ngokuchasene ne parentCID ngomntwana wakhe wangoku: Jonga imveliso:

   Server.vmdk:           CID=1a2b3c4d
                          parentCID=ffffffff   (ffffffff means this is the root Base Disk)
   
   Server-000001.vmdk:    CID=99887766
                          parentCID=55443322   <-- ERROR: Should equal Server.vmdk's CID (1a2b3c4d)
                          parentFileNameHint="Server.vmdk"
   
   Server-000002.vmdk:    CID=aabbccdd
                          parentCID=99887766   <-- OK: Matches Server-000001.vmdk's CID (99887766)
                          parentFileNameHint="Server-000001.vmdk"
   

4. Lungisa ezaphukileyo parentCID kwisichazi somntwana kwaye uqinisekise nge vmkfstools -e:
5. Okokuqala, gcina ifayile yenkcazo yokubhaliweyo (cp Server-000001.vmdk Server-000001.vmdk.bak).
6. Vula Server-000001.vmdk kwi vi kwaye utshintshe parentCID=55443322 ukuya parentCID=1a2b3c4d (ukudibanisa Server.vmdkyangoku CID).
7. Vavanya imfezeko yetsheyini ukusuka entsha (elona nani liphezulu) umfanekiso okhawulezayo usebenzisa vmkfstools -e:

   vmkfstools -e Server-000002.vmdk
   

8. Ukuba ikhonkco lilungile, iziphumo ze-ESXi: Disk chain is consistent.
9. UHLANGANISO OLUNGANGONALI (vmkfstools -i I-Clone yangaphandle kweNdawo):
10. Ukuba Server.vmdk yalungiswa kancinane phambi kokuba ulungise i parentCID, ungadibanisi endaweni phezu kwekopi yakho ekuphela kwayo. Kunoko, yalatha vmkfstools -i kowona mfanekiso mtsha wegqabi (Server-000002.vmdk)** kwaye udibanise lonke ikhonkco kwi-VMDK entsha, ethe tyaba enye kwindawo yokugcina idatha enendawo esimahla:

    vmkfstools -i Server-000002.vmdk /vmfs/volumes/<Target_Datastore>/Server_Rescue/Server_Merged.vmdk -d thin
    

11. vmkfstools -i ufunda ibhloko nganye ukusuka Server-000002.vmdk phantsi nge Server-000001.vmdk kwaye Server-flat.vmdk ngokungqongqo Imo Yokufunda-Kuphela kwaye ubhale ecocekileyo, engena-snapshot Server_Merged.vmdk ngaphandle kokuchukumisa iifayile zakho zoqobo.

Imeko 1B: Ukudala kwakhona engekhoyo okanye ecinyiweyo 500-byte .vmdk isichazi sokubhaliweyo xa Server-flat.vmdk isaphelele¶

Ngamanye amaxesha umlawuli okanye iskripthi esaphukileyo siyacima Server.vmdk (okanye iyonakala ukuze 0 bytes), ibangela ukuba iSikhangeli seDatastore siyeke ukubonisa idisk enenyani, nangona ubukhulu be-500-gigabyte Server-flat.vmdk ifayile equlethe i-100 yepesenti yedatha yakho yokwenyani isahleli kanye apho kwi-SSH (ls -la *-flat.vmdk).

Ungaphinda wenze okubhaliweyo okungenanto okushiyiweyo Server.vmdk ifayile yokuchaza kwimizuzwana engama-60 ngaphandle kokulahlekelwa yi-byte enye yedatha ngaphakathi Server-flat.vmdk:

# 1. Check the exact byte size of your existing Server-flat.vmdk:
ls -l Server-flat.vmdk
# Example output: -rw------- 1 root root 107374182400 Oct 31 12:00 Server-flat.vmdk  (Exactly 107,374,182,400 bytes)

# 2. Create a temporary dummy VMDK of that EXACT byte size in /tmp or the datastore:
vmkfstools -c 107374182400 -d thin temp_dummy.vmdk

# 3. Delete the dummy binary file (temp_dummy-flat.vmdk) and rename the 500-byte descriptor to Server.vmdk:
rm -f temp_dummy-flat.vmdk
mv temp_dummy.vmdk Server.vmdk

# 4. Edit Server.vmdk in 'vi' and change the filename inside quotes from "temp_dummy-flat.vmdk" to "Server-flat.vmdk":
sed -i 's/temp_dummy-flat.vmdk/Server-flat.vmdk/g' Server.vmdk
# (Also delete the line 'ddb.thinProvisioned = "1"' if the original disk was thick-provisioned)

Imeko 1C: Ukuvula a .vmdk itshixiwe yinginginya ye-ESXi exhonyiweyo okanye i-proxy eyaphukileyo egcinayo (Cannot open the disk: Failed to lock the file)¶

Ukuba i-VM iyala ukuqalisa nge Failed to lock the file okanye Cannot open disk: Resource busy, enye inginginya ye-ESXi kwiqela (okanye isixhobo seVeeam/backup HotAdd esantlitheka ngexesha logcino) isabambe i SCSI / VMFS yokutshixa ifayile -flat.vmdk okanye -sesparse.vmdk: 1. Jonga ukuba i-VM ye-proxy eyaphukileyo isenayo i-VM yemveliso yakho .vmdk encanyathiselwe kwisilawuli sayo se-SCSI esinenyani: Hlela useto lweVeeam/CommVault proxy VMs kwaye ususe naziphi na iidiski ezidala ezincanyathiselweyo zokuvelisa (khetha u-"Susa kuMatshini weVirtual," UNGAZE "Cima iifayile kwi-datastore"). 2. Fumana ukuba yeyiphi idilesi ye-MAC yokusingatha i-ESXi kunye nenkqubo yehlabathi ebambe iqhaga le-VMFS:

vmfsfilelockinfo -p /vmfs/volumes/<Datastore>/<VM_Folder>/Server-flat.vmdk

Umkhondo 2: Ukuhlangula iMicrosoft Hyper-V .vhdx kwaye .avhdx amatyathanga esnapshot¶

KwiMicrosoft Hyper-V, yonke indawo yokukhangela (umfanekiso okhawulezayo) yenza umahluko wenyani wehard disk ngolwandiso .avhdx (okanye .avhd kwifomati endala yeVHD) yabelwe igama lefayile ende ye GUID njenge ProdSQL_A1B2C3D4-E5F6-7890-ABCD-1234567890AB.avhdx.

Inyathelo 1: Imephu yolandelelwano lwamaxesha .avhdx umthi womzali-umntwana kwi-PowerShell¶

Ngaphambi kokudibanisa okanye ukudibanisa nantoni na kuMphathi we-Hyper-V, vula i-Elevated Administrator PowerShell* window kwi-Hyper-V host host, yiya kwifolda equlethe yakho. .vhdx kwaye .avhdx iifayile, kwaye usebenzise le liner ukubonisa eyona khonkco lomzali-lomntwana ukusuka kwentsha ukuya komdala:

# Inspect every .vhdx and .avhdx in the directory, sorted by LastWriteTime:
Get-ChildItem -Filter "*.*vhd*" | ForEach-Object {
    Get-VHD -Path $_.FullName -ErrorAction SilentlyContinue |
    Select-Object Path, ParentPath, VhdType, FileSize, Size
} | Format-List

Jonga kwi Path kwaye ParentPath amasimi. Baza kutyhila ulandelelwano lwekhonkco oluchanekileyo: - ProdSQL.vhdx -> ParentPath: (blank) (** Root Base Disk, endala **) - ProdSQL_1111.avhdx -> ParentPath: D:\VMs\ProdSQL.vhdx (Umntwana 1) - ProdSQL_2222.avhdx -> ParentPath: D:\VMs\ProdSQL_1111.avhdx (Umntwana 2) - ProdSQL_3333.avhdx -> ParentPath: D:\VMs\ProdSQL_2222.avhdx (Eyona Diski yegqabi esebenzayo)

Inyathelo lesi-2: Ukulungisa "The chain of virtual hard disks is broken" okanye "Differencing disk parent ID mismatch" (Set-VHD -IgnoreIdMismatch)¶

Kuthekani ukuba umntu uye wasusa ifolda yeVM ukusuka C:\VMs\ ukuya E:\VMs\, okanye iqalwe ngempazamo ProdSQL.vhdx imizuzwana emi-5, kubangela ProdSQL_1111.avhdx ukusilela nge: The chain of virtual hard disks is broken. The system cannot locate the parent virtual hard disk for the differencing disk okanye There is a mismatch in the virtual disk identifiers?

Sebenzisa esemthethweni Hyper-V PowerShell cmdlet Set-VHD ne -IgnoreIdMismatch iflegi (emva kokuxhasa iifayile kuqala):

# Relink a child .avhdx to its parent .vhdx/.avhdx (adding -IgnoreIdMismatch if the parent timestamp/GUID shifted):
Set-VHD -Path "E:\VMs\ProdSQL_1111.avhdx" -ParentPath "E:\VMs\ProdSQL.vhdx" -IgnoreIdMismatch

Inyathelo 3: Ukudibanisa inkedama ngezandla .avhdx ikhonkco ukusuka ENTSHA ukuya ku-OLDEST (Merge-VHD)¶

Xa i-arhente yokugcina ishiya i-15 iinkedama .avhdx iifayile kwifolda yakho ezingasabonakaliyo ngaphakathi koMphathi we-Hyper-V GUI "Iindawo zokuHlola", kufuneka uzidibanise ngesandla kwi-PowerShell ngelixa i-VM icinyiwe.

Yenza le miyalelo kanye ye-PowerShell kwi-ikopi esebenzayo yesiqulathi seefayili:

# Step 1: Merge Child 3 (Newest) into Child 2:
Merge-VHD -Path "E:\VMs\ProdSQL_3333.avhdx" -DestinationPath "E:\VMs\ProdSQL_2222.avhdx"

# Step 2: Merge Child 2 into Child 1:
Merge-VHD -Path "E:\VMs\ProdSQL_2222.avhdx" -DestinationPath "E:\VMs\ProdSQL_1111.avhdx"

# Step 3: Merge Child 1 into the Base .vhdx:
Merge-VHD -Path "E:\VMs\ProdSQL_1111.avhdx" -DestinationPath "E:\VMs\ProdSQL.vhdx"

Umkhondo 3: Ukuhlangula i-Proxmox VE / QEMU / KVM .qcow2 kunye neVirtualBox .vdi imixokelelwane¶

1. Ukujonga kunye nokulungisa eyonakeleyo QCOW2 L1/L2 Cluster & Refcount Tables (qemu-img check)¶

Xa i-Linux KVM okanye i-Proxmox host inengxaki yokucima kombane ngequbuliso ngaphandle kwe-cache exhaswa yibhetri, .qcow2 idiski enenyani ihlala isilela ukuqalisa nge qcow2: Marking image as corrupt: L2 table offset unaligned okanye Refcount block corrupted. 1. Qala ukhuphele ifayile .qcow2 ifayile (cp vm-100-disk-0.qcow2 vm-100-disk-0.qcow2.bak). 2. Hlola ikhonkco lokuxhasa kunye noluhlu lwangaphakathi olukhawulezayo:

qemu-img info --backing-chain vm-100-disk-0.qcow2
qemu-img snapshot -l vm-100-disk-0.qcow2

qemu-img check -r all vm-100-disk-0.qcow2

2. Ukulungisa i-QCOW2 eyaphukileyo yeFayile yokuxhasa iFayile (qemu-img rebase -u)¶

Ukuba umfanekiso weQCOW2 wangaphandle (overlay.qcow2) iyasilela ukuvula ngenxa yokuba ifayile yokuxhasa umzali wayo (base.qcow2) yasiwa kulawulo olutsha okanye indawo yokugcina, hlaziya isalathisi sefayile exhasayo ngokungakhuselekanga (-u, i-header-kuphela) indlela ngaphandle kokuphinda ubhale iibhloko zedatha:

qemu-img rebase -u -b /new/path/to/base.qcow2 -F qcow2 overlay.qcow2

3. Ukwenza ityathanga le-QCOW2 eethe-ethe okanye iVMDK okanye iVHDX ibe ngumfanekiso ozimelayo omtsha kraca (qemu-img convert)¶

Esinye sezixhobo eziguquguqukayo ekuhlanguleni koomatshini yi qemu-img convert (efundeka ngokomthonyama .qcow2, .vmdk, .vhdx, .vhd, kwaye .vdi). Xa ukhomba qemu-img convert ku umfanekiso wegqabi elitsha wekhonkco elisebenzayo, ifunda lonke ulawulo lomzali nomntwana kwi- imowudi engqongqo yokufunda-Kuphela kwaye ibhala idiski entsha kraca, ezimeleyo, engenasifinyezo kwindawo yokugcina yokuhlangula:

# Non-destructively flatten an entire QCOW2, VMDK, or VHDX chain into a single clean image:
qemu-img convert -p -O qcow2 top_snapshot_leaf.qcow2 /mnt/rescue_storage/flattened_clean.qcow2

Umkhondo 4: Ukuhlangulwa kwefayile engaphandle kwebhendi (Ukukhupha iifayile xa iVM ingasayi kuqalisa)¶

Kuthekani ukuba inkqubo yokusebenza yeendwendwe ngaphakathi kwediski enenyani ayivulekiyo, okanye umfanekiso ophakathi kwitsheyini wonakaliswe ngokuyinxenye kwaye kufuneka ukhuphe idatabase yeSQL (.mdf/.ldf), iifayile ze-QuickBooks, /var/lib/mysql, okanye amaxwebhu enkampani kwimizuzu engama-30 ezayo?

**Akukho mfuneko yokuba uvule uMtshini weVirtual ukukhupha iifayile ngaphakathi kwihard drive yayo.

Indlela yoku-1: nyusa nayiphi na .vmdk, .vhdx, .qcow2, okanye .vdi kwiNdlela yokuFunda-Kuphela kwiLinux usebenzisa libguestfs (guestmount / qemu-nbd)¶

Faka libguestfs-tools (sudo apt install libguestfs-tools qemu-utils ku-Ubuntu/Debian/Proxmox) kwaye unyuse iumfanekiso wegqabi elitsha ngokungqongqo Imo Yokufunda-Kuphela (--ro):

# Option A: Using guestmount (Automatically detects internal guest LVM/partitions and mounts read-only):
sudo mkdir -p /mnt/vm_rescue
sudo guestmount -a /path/to/Newest_Leaf_Snapshot.vmdk -i --ro /mnt/vm_rescue
# (If guest OS partitions fail auto-inspection due to dirty NTFS journal, list partitions with 'virt-filesystems -a disk.vmdk -l'
# and mount the specific partition directly with '-m /dev/sda2 --ro -o norecover')

# Option B: Attaching the virtual disk chain as a Read-Only Network Block Device (/dev/nbd0):
sudo modprobe nbd max_part=16
sudo qemu-nbd --read-only --connect=/dev/nbd0 /path/to/Newest_Leaf_Snapshot.qcow2
sudo partprobe /dev/nbd0
lsblk /dev/nbd0
# Now mount /dev/nbd0p2 read-only (with -o ro,norecover for NTFS or -o ro,noload for ext4):
sudo mount -o ro,norecover /dev/nbd0p2 /mnt/vm_rescue

Indlela yesi-2: Utsalo olukhawulezayo lokufunda-kuphela kwiWindows usebenzisa 7-Zip okanye Disk Management -> Attach VHD (Read-Only)¶

• Usebenzisa i-7-Zip (Iyasebenza .vmdk, .vhdx, .vhd, .qcow2, kwaye .vdi): Cofa ekunene kwindawo ezimeleyo okanye yasicaba .vmdk, .vhdx, okanye .qcow2 ifayile kwiWindows kwaye ukhethe ** 7-Zip -> Vula i-Archive **. I-7-Zip iyacalula i-GPT/MBR iitafile zezahlulo kunye ne-NTFS/ext4 iinkqubo zefayile ngaphakathi kweediski ezinenyani kwimowudi yokufunda kuphela eyi-100%, ikuvumela ukuba utsale kwaye uwise iifolda zeendwendwe ngqo kwi-desktop yakho ngemizuzwana.
• ** Ukusebenzisa iWindows Disk Management (Ye .vhdx / .avhdx):** Vula diskmgmt.msc -> Isenzo -> Qhoboshela i-VHD -> Khangela kwelona phepha litsha .avhdx** (okanye .vhdx), KHANGELA IBHOKISI [X] Read-only ( KUBALULEKILEYO: Ungaze ulibale ukujonga Funda-kuphela, okanye iWindows iya kuyilungisa iheader yediski), kwaye ucofe u-OK*. I-VM yakho C: kunye no-D: iidrive zivela ngoko nangoko kwi-Windows File Explorer.

Indlela yesi-3: Ukwakha kwakhona amatyathanga awonakele kakhulu nge UFS Explorer Professional Recovery¶

Ukuba umzali diski kwi VMDK okanye VHDX tyathanga iqalwe ngempazamo kwaye yalungiswa, okanye ukuba VMFS/NTFS ugcino lwedatha urhwaphilizo yahlulwe inxalenye ye -sesparse.vmdk okanye .avhdx ifayile ukuze izixhobo ze-hypervisor ziyala, UFS Explorer yoBuyiselo loBuchule (okanye R-Studio Technician) ikuvumela ukuba uhlanganisele ngesandla isiseko sediski ekrwada kunye nomfanekiso ngamnye wedelta yomntwana kwisiko Isitaki seDelta seVirtual kwisoftware ye-RAM, ugqitha i-hypervisor. CID/GUID iheader ijonga ukukrola kunye nokukhupha iifayile zendwendwe ezingaguqukiyo.

Umkhondo 5: Ukufumana kwakhona ifayile yoqwalaselo yenkedama yeVM (.vmx, .xml, okanye <vmid>.conf)¶

Ngamanye amaxesha ikhonkco lediski yenyani ngokwayo (*.vmdk, *.vhdx, okanye *.qcow2) yi 100 yepesenti engaguqukiyo kuluhlu logcino, kodwa ifayile yoqwalaselo encinci echaza ubeko lwehardware lukaMatshini Obonakalayo (.vmx kwi VMware ESXi, <GUID>.vmcx / .xml kwi-Hyper-V, okanye /etc/pve/qemu-server/<vmid>.conf in Proxmox VE) yonakele, icinywe ngempazamo, okanye ikhutshwe ngaphandle ngexesha lentlitheko yenginginya.

Ukuba uphinda ubuyisele iqokobhe le-VM ngomlawuli ongalunganga wogcino olunenyani okanye imowudi ye-firmware, inkqubo yokusebenza yeendwendwe iya kuntlitheka kwangoko kwi-boot nge INACCESSIBLE_BOOT_DEVICE (IiWindows) okanye yehla kwi-a dracut / initramfs iqokobhe likaxakeka (Linux). Tshatisa ezi zicwangciso ezine zehardware kuqwalaselo lwakho loqobo lweendwendwe phambi kokuba uncamathele kwidiski yakho enenyani ehlangulweyo:

Imibuzo edla ngokubuzwa¶

Imithombo ijongiwe¶

• VMware nguBroadcom Technical Knowledge Base: KB 1007969 / 316578 (Ukusombulula "I-virtual disk yomzali ilungisiwe ukususela oko umntwana wadalwa" CID Mismatch Errors), KB 1002511 (Recreating a Missing Virtual Machine Disk Descriptor .vmdk Ifayile), kunye KB 10051 (Ukuqonda Izifinyezo zoomatshini kwi-ESXi).
• IMicrosoft Learn / Windows Server Hyper-V Engineering Documentation: Hyper-V PowerShell Reference for Get-VHD, Set-VHD -IgnoreIdMismatch, kwaye Merge-VHD Udibaniso lweDiski ngaphandle kweintanethi.
• Iprojekthi yeQEMU kunye neRed Hat Enterprise Linux Virtualization Documentation: Esemthethweni qemu-img Incwadi (info --backing-chain, check -r all, rebase -u, convert) kunye libguestfs (guestmount --ro) Funda-Kuphela Uhlolo lweDiski ebonakalayo.
• Uxwebhu lobuGcisa lweOracle VirtualBox: VBoxManage showmediuminfo kwaye clonemedium Umahluko kuYilo loMfanekiso.
• Iziko leSizwe leMigangatho kunye neTekhnoloji (NIST, eUnited States): NIST Special Publication 800-86: Isikhokelo sokuHlanganisa ubuChwepheshe boBuchule kwiMpendulo yeSiganeko (UkuGcinwa koMfanekiso weMifanekiso eVirtual).

Izikhokelo ezinxulumeneyo¶

• I-NAS kunye ne-RAID i-array ithotywe, ukungaphumeleli kwe-drive ezininzi, kunye ne-ZFS / Btrfs recovery
• I-NVMe okanye i-SSD ngokukhawuleza ingena kwimodi yokufunda kuphela okanye iyanyamalala kwi-BIOS
• Ukungaphumeleli kwe-hard drive kunye nokubuyisela idatha kaxakeka
• Ukusilela kwenkqubo yeLinux kunye nokulungiswa kweGRUB
• Windows Blue Screen (BSOD) kunye nokulungiswa kwe-boot
• Ukugcinwa kwekhompyuter: isicwangciso se-3-2-1 kunye nokubuyiswa kweentlekele
• Iinombolo zikaxakeka zehlabathi