Ku celcelinta OS ama Hyper-V waxay badbaadisaa waqti badan. Si kastaba ha ahaatee, ku- noqoshada Hyper ^{(Replication)}-V^(Hyper-V) sidoo kale loo yaqaan " Hyper-V Replica ," way ka duwan tahay. Habka ku-noqoshada waxa uu kuu ogolaanayaa in aad ku soo koobto hal mashiin oo aad u guurto goob kale oo mashiineed. Erayada fudud, waxay u abuurtaa koobiga mashiinka farsamada tooska ah ee mashiinka khadka tooska ah. Caadi ahaan waxay faa'iido u leedahay istaraatiijiyada soo kabashada musiibada. Maqaalkan, waxaanu ku wadaagi doonaa hagaajinta qaar ka mid ah khaladaadka ku celcelinta hyper-v ee caadiga ah.

Hagaaji khaladaadka ku celcelinta Hyper-V

Waxaa jiri kara sababo badan oo ku-celinta Hyper-V^(Hyper-V) ay u dhici karto. Waxay noqon kartaa arrimo shabakad, martigaliyaha duugoobay, daacadnimada, ama wax kasta oo kale. Hoos^(Below) waxaa ku yaal qaar ka mid ah dhibaatooyinka caadiga ah iyo xallinta:

1. Ku celcelinta Hyper-V oo^(Hyper-V) hakisay mashiinka farsamadaoo ay ugu wacan tahay fashil aan laga soo kaban karin. ( Aqoonsiga mashiinka Virtual).
2. Hyper-V waxay ka hortagtay bilaabista mishiinka farsamada sababtoo ah waxaa loo diyaariyey fashil
3. Hyper-V wuu ku guul daraystay inuu xaliyo magaca Server -ka nuqulka^{(Replica Server)}
4. Hyper-V kuma jiro xaalad lagu aqbalayo ku celcelinta Server^{(Replica Server)} -ka nuqulka ah ee mashiinka farsamada
5. Ku guul daraystay fulinta hawlgalka Hyper-V kuma jiro xaalad ku celcelin sax ah si loo sameeyo qalliinka

Waxaa xiiso leh in la ogaado in inta badan qaladaadka Hyper-V ay dhacaan sababtoo ah waxaa jira arrin isku mid ah oo u dhexeeya iyaga. Ama martigeliyaha ayaa ku jira dayactir, ama server-ka nuqulku waa offline ama diyaar uma aha.

1] Hyper-V ku celcelinta hakinta ee mashiinka farsamada gacanta sababtoo ah guul darrida aan dib loo soo kaban karin. ( Aqoonsiga mashiinka^{(Machine ID)} Virtual )

Sharaxaad buuxda waxaa ka mid  ah- Hyper-V^(Hyper-V) kuma soo celin karo isbeddelada mashiinka farsamadasababtoo ah server-ka nuqulku^(Replica) wuu diiday xidhiidhka. Waxa laga yaabaa inay tahay sababtoo ah waxaa jira hawl-gal ku celcelineed oo la sugayo oo ku jira server^(Replica) -ka nuqulka ee isla mishiinka farsamada, kaas oo qaadanaya wax ka badan intii la filayey ama leh xidhiidh jira. ( Aqoonsiga mashiinka Virtual)

Si aad u xalliso, hubi qodobada soo socda:^{(To resolve, check on the following points:)}

• Midig ku dhufo^{(Right-click)} VM-ka, oo dooro inaad dib u bilawdo habka ku-noqoshada
• Hubi^(Make) in server-ku ku celcelinayo uu online yahay.
• Adeegaha nuqulku^(Replica) waa inuu had iyo jeer lahaadaa meel ku filan
• Baladwidhid^(Enough) shabakad ku filan si loo hubiyo in habka soo noqnoqda uu ku dhammayn karo hal wareeg.

Kuwani waxay hagaajin karaan dhibaatada, sida caadiga ah, laakiin haddii aysan dhicin, ka dibna tirtir nuqulka, oo dib-u-dejinta dib-u-habeeynta mar labaad, waxay soo jeedinaysaa Microsoft . Waa inaad sugtaa ilaa isku-dubbaridu dhammaato. Haddii serfarka soo-saarku uu khadka ka maqnaa muddo dheer, server-ka isha waxa uu kordhiyaa xog aad u badan oo ay noqoto mid aan suurtogal ahayn in dib loo diro.

2] Hyper-V waxay ka hortagtay bilaabista mashiinka farsamada sababtoo ah waxay u diyaarsan tahay fashilka

Markaad dejinayso bogga Server^{(Replica Server page)} -ka nuqulka ah , waxaad u baahan tahay inaad geliso midkood NetBIOS ama FQDN^{( NetBIOS or FQDN)} ee server-ka nuqulka ah. ^(Replica)Haddii serfarka nuqulku^(Replica) ka mid yahay kutlada guul-darraystay, geli magaca dalaaliyaha nuqulka ah ee Hyper-V^{(Hyper-V Replica Broker)} .

Haddii ay jiraan wax ka baxsan waxa aan kor ku wadaagnay, markaa waxaad yeelan doontaa qaladkan sababtoo ah habka guul-darradu ma awoodo inuu helo. Si aad u hagaajisid, waa inaad wax ka beddeshaa bogga habaynta ku-noqoshada oo aad magaca ku beddesho NetBIOS ama FQDN^(FQDN.Once) . Marka la hagaajiyo, ma heli doontid qaladka Hyper-V Replication^{(Hyper-V Replication Error)} .

3]  Hyper-V wuu ku guul daraystay inuu xaliyo magaca Server -ka nuqulka^{(Replica Server)}

Sida^(Same) kor ku xusan, waana qalad cad. Haddii Hyper-V uusan awoodin inuu xalliyo magaca server-ka nuqulka ah^{( Hyper-V is not able to resolve the replica server name)} , waxaad u baahan tahay inaad hubiso inaad isticmaalayso NetBIOS ama FQDN. Haddii aad isticmaalayso qaabka saxda ah, markaa waa arrin DNS ah. Waa inaad ka hubisaa server-ka DNS^{(DNS server)} si aad u ogaato sababta uu u awoodi waayay inuu xalliyo ciwaanka Server -ka ee la filayo .

4] Hyper-V kuma jiro xaalad lagu aqbalayo ku celcelinta Server^{(Replica Server)} -ka nuqulka ah ee mashiinka farsamada

Marka ku-noqoshada lagu furo VM, nidaamku wuxuu abuuraa faylalka^(Replica) mashiinka farsamada ee nuqulka ah halkaasoo wax walba lagu kaydiyo. Mid kasta oo ka mid ah galkaas wuxuu leeyahay magac u taagan GUID . Waa u gaar server il kasta. Haddii, sabab qaar ka mid ah, Hyper-V setup wizard uu leeyahay isla UID , sababtoo ah mar hore ayaa la habeeyey, markaas waxaad heli doontaa qaladkan. Maaddaama hawshu ay hubiso mishiin kasta oo farsamada gacanta ah ka hor inta aan la dhamaystirin, khaladku wuu soo baxayaa.

Beddelka habkan maaha in la isticmaalo GUID . Microsoft Docs waxay soo jeedinaysaa kuwan soo socda:

1. Enable replication for the virtual machine, and ensure initial replication is not started immediately (You can choose to schedule the initial replication for a later time)
2. Once Replica virtual machine is created, use the Move wizard to move the storage of the virtual machine to the path of your choice (Storage migration)
3. Once the storage migration is complete, you can start the initial replication for the virtual machine

5] Ku guuldarraystay inuu fuliyo hawlgalka, Hyper-V kuma jiro xaalad ku celcelineed sax ah si loo fuliyo hawlgalka

Waxay u dhacdaa laba sababood dartood. Midda koowaad waa marka aan server-ka loo habayn inuu noqdo server-ka nuqul ka mid ah. Markaa marka isha uu bilaabo habka ku-noqoshada, dhamaadka kale ma garanayo waxa lagu samaynayo gelinta. Midda labaad^(Second) waa marka uu seerfarku xannibo gelitaanka Hyper-V ee server-ka Rep0lication .

In kasta oo sababta koowaad lagu xallin karo diyaarinta server-ka nuqul ka mid ah, tan labaad waa arrin ka badan dab-damis oo maamulaha IT-gu uu kuu xallin karo adiga.

Waxaan rajeynayaa inaad awooday inaad xalliso kuwan caadiga ah ee Hyper-V^{(Hyper-V Replication Errors)} . Waan hubaa inay wax badan ka heli karaan, markaa haddii aad mid la kulanto, noo soo sheeg, annaguna waxaan u heli doonnaa xal.

How to fix common Hyper-V Replication errors

Replicating an OЅ or Hypеr-V saves a lot of time. Howeνer, Replication of Hyper-V also called “Hyper-V Replica,” is different.  The replication process allows you to replicate from one virtual machine to another virtual machine environment. In simple words, it creates a copy of a live virtual machine to an offline virtual machine. It is typically useful for a disaster recovery strategy. In this post, we will share fix to some of the common hyper-v replication errors.

Fix Hyper-V Replication errors

There can be multiple reasons why Hyper-V Replication may fail. It can be network issues, an outdated host, integrity, or anything else. Below are some of the common problems and resolutions:

1. Hyper-V suspended replication for virtual machine <VMName> due to a non-recoverable failure. (Virtual Machine ID <VMId>).
2. Hyper-V prevented starting virtual machine because it is prepared for failover
3. Hyper-V Failed to resolve the Replica Server name
4. Hyper-V is not in a state to accept replication on Replica Server for virtual machine <VM Name>
5. Failed to perform the operation. Hyper-V is not in a valid replication state to perform the operation

It is interesting to note that most of the Hyper-V errors occur because there is a sync issue between them. Either the host is in maintenance, or the replica server is offline or not ready.

1] Hyper-V suspended replication for virtual machine due to a non-recoverable failure. (Virtual Machine ID)

The full description includes— Hyper-V could not replicate changes for virtual machine <VMName> because the Replica server refused the connection. It may be because there is a pending replication operation in the Replica server for the same virtual machine, which is taking longer than expected or has an existing connection. (Virtual machine ID <VM ID>)

To resolve, check on the following points:

• Right-click on the VM, and choose to resume the replication process.
• Make sure the replication server is online.
• Replica server should always have enough space
• Enough network bandwidth to make sure the replication process can complete in one cycle.

These can fix the problem, usually, but if it doesn’t, then delete the replica, and re-setup replication again, suggests Microsoft. You will have to wait until the synchronization is complete. If the replication server was offline for a long time, the source server acclimates so much data that it becomes impossible to send it over.

2] Hyper-V prevented starting virtual machine because it is prepared for failover

When setting up the Replica Server page, you need to enter either the NetBIOS or FQDN of the Replica server. If the Replica server is part of a failover cluster, enter the name of the Hyper-V Replica Broker.

If there is anything apart from what we shared above, then you will have this error because the failover process is not able to find it. To fix it, you will have to edit the replication setup page and replace the name with NetBIOS or FQDN.Once the fix is made, you will not receive the Hyper-V Replication Error.

3]  Hyper-V Failed to resolve the Replica Server name

Same as above, and it’s a clear error. If the Hyper-V is not able to resolve the replica server name, you need to check if you are using the NetBIOS or FQDN. If you are using the correct format, then its a DNS issue. You have to check with the DNS server to find out why it is not able to resolve the expected Server address.

4] Hyper-V is not in a state to accept replication on Replica Server for virtual machine

When replication is enabled on a VM, the process creates Replica virtual machine files where everything is stored. Each of these folders has a name that represents the GUID. It is unique for each source server. If, for some reason, Hyper-V setup wizard has the same UID, because it was already configured once, then you will receive this error. Since the process checks for any duplicate virtual machine before finalizing, the error shows up.

The alternative to this method is not to use the GUID. Microsoft Docs suggests the following:

1. Enable replication for the virtual machine, and ensure initial replication is not started immediately (You can choose to schedule the initial replication for a later time)
2. Once Replica virtual machine is created, use the Move wizard to move the storage of the virtual machine to the path of your choice (Storage migration)
3. Once the storage migration is complete, you can start the initial replication for the virtual machine

5] Failed to perform the operation, Hyper-V is not in a valid replication state to perform the operation

It happens because of two reasons. The first is when the server is not configured to be a replica server. So when the source initiates the replication process, the other end doesn’t know what has to be done with the input. Second is when the server blocks access to Hyper-V on the Rep0lication server.

While the first cause can be fixed by preparing the replica server, the second is more of a firewall issue that an IT admin can resolve it for you.

I hope you were able to resolve these common Hyper-V Replication Errors. I am sure there can be more, so if you face any, let us know, and we will find a resolution for it.

Related posts

• Darawalku waxa uu ku ogaaday cilad darawalka gudaha DeviceVBoxNetLwf

• Hagaaji qaladka Runtime R6025 Wicitaanka Function Virtual Saafi ah

• BlueStacks ma bilaabi karto marka Hyper-V la furo

• Software kaabta ugu fiican ee bilaashka ah ee VMware iyo Hyper-V mishiinada

• Sida loogu beddelo VHD VHDX iyadoo la isticmaalayo Hyper-V Manager

• Hagaaji qaladaadka OOBEKEYBOARD, OOBELOCAL, OOBEREGION

• Wax baa khaldamay, Demi software ka-hortagga fayraska, 0x8007045d

• Hagaaji Qaladka Load Application 5:0000065434 Windows 10

• Hagaaji qaladka Codsiga 0xc0150004 gudaha Windows 11/10

• Hagaaji ShellExecuteEx wuu fashilmay; qaladka code 8235 ee Windows10

• Khaladka nidaamka 6118, Liiska adeegayaasha kooxdan shaqada lama heli karo

• Sida loo rakibo oo loo awood Hyper-V Windows 11/10 Guriga

• Sida loo xaliyo dhibaatada isku dhaca Saxeexa Disk ee gudaha Windows 11/10

• Hagaaji Crypt32.dll lagama helin ama khalad ka maqan Windows 11/10

• Cilad 1327 Invalid Drive marka la rakibayo ama la furayo barnaamijyada

• Hagaaji ShellExecuteEx qalad ku fashilmay Windows 11/10

• Madax adag ayaa heshay fariin khaldan oo xog xun Windows 10

• Xidhmada Fix lagama diiwaan gashan karo Windows 11/10

• Hagaaji Code Error Code 30038-28 marka la cusboonaysiinayo Xafiiska

• Habkani waxa uu u baahan yahay warbaahin meesha laga saari karo - Qaladka dib u dejinta erayga sirta ah