PPDM - Applicatiebewust VM-herstel is mislukt met de functie 'Kan schijven niet terugzetten naar de lees-/schrijfmodus na VSS quiesce operation set them to read-only'
Summary: Applicatiebewust VM-herstel is mislukt met de functie 'Kan schijven niet terugzetten naar de lees-/schrijfmodus nadat VSS ze op alleen-lezen heeft ingesteld' vanwege het ontbreken van geheugen op het zoekknooppunt. ...
Symptoms
Unable to reset disks to read-write mode after VSS quiesce operation set them to read-only
In "PowerProtect Data Manager_*******.log"
vmdm.log: 2024-06-19T01:51:39.916Z ERROR [] [request-dispatch-update-91] [00000000-0000-4000-a000-000000000000][][][TRACE_ID:b78abd00d05a58d4;JOB_ID:af29df7e344de2ee][] [c.e.b.v.r.a.BaseRestoreOp.doFailureStatus(561)] - Recover VM failed. vmdm.log: 2024-06-19T01:51:39.917Z ERROR [] [request-dispatch-update-91] [00000000-0000-4000-a000-000000000000][][][TRACE_ID:b78abd00d05a58d4;JOB_ID:af29df7e344de2ee][] [c.e.b.v.r.a.BaseRestoreOp.getSessionError(740)] - VM Proxy restore job session failed. Session '8fbda571-ab2d-4597-8fe7-4791993b836d' is unsuccessful: Unable to reset disks to read-write mode after VSS quiesce operation set them to read-only.
Vmdirect_******.log hieronder WAARSCHUWING, wat aangeeft dat er te weinig geheugen is, voordat de FOUT wordt weggegooid om schijven terug te zetten naar de lees-/schrijfmodus.
2024-06-19 09:36:57+0800 164 WARNING ppdm.local 58736 processmanager.go(336) main.(*ProcessManager).isThresholdMemoryConsumptionReached Available system memory (364 MB) is less than minimum required system resources (800 MB)
2024-06-19 09:36:57+0800 165 WARNING ppdm.local 58736 processmanager.go(251) main.(*ProcessManager).waitForCurrentSearchClientProcessesToComplete Max number of vm-file-extractor processes are running. Cancelling run of vm-file-extractor for vm EC020DB01 after 10 minutes
2024-06-19 09:36:57+0800 166 WARNING ppdm.local 58736 main.go(323) main.main Max number of vm-file-extractor processes are running. Cancelling the process after 10 minutes as not enough system resources are available. The metadata extraction and indexing of this VM will be handled later by the offline-indexing process.
2024-06-19 09:36:57.001+0800 167 ERROR ppdm.local 58736 main.go(838) main.exitWithError abort extraction with Max number of vm-file-extractor processes are running. Cancelling the process after 10 minutes as not enough system resources are available. The metadata extraction and indexing of this VM will be handled later by the offline-indexing process.
2024-06-19 09:36:57.001+0800 169 ERROR ppdm.local 58736 main.go(848) main.exitWithError {"State":"Skipped","Error":"Max number of vm-file-extractor processes are running. Cancelling the process after 10 minutes as not enough system resources are available. The metadata extraction and indexing of this VM will be handled later by the offline-indexing process.","LogFile":"","DetailedStatus":"{\"State\":\"Skipped\",\"Error\":\"\",\"DiskStatus\":[]}"}
2024-06-19 09:36:57.001+0800 170 ERROR ppdm.local 58736 main.go(855) main.exitWithError abort extraction of VM metadata for asset EC020DB01 (vm-53132)
RecoverVmSessions-b1d958e1-f05b-46a8-af3c-d7d1e5840631.log: 2024-06-19T01:36:57.092Z WARN: [aaa7a1018b9ad483;86443860fffb28d7] VM File Extractor plugin was unsuccessful. Max number of vm-file-extractor processes are running. Cancelling the process after 10 minutes as not enough system resources are available. The metadata extraction and indexing of this VM will be handled later by the offline-indexing process.
RecoverVmSessions-b1d958e1-f05b-46a8-af3c-d7d1e5840631.log: 2024-06-19T01:36:57.092Z ERROR: [aaa7a1018b9ad483;86443860fffb28d7] Unable to repair disk properties which were modified by the VSS Quiesce operation. VM File Extractor plugin was unsuccessful. Max number of vm-file-extractor processes are running. Cancelling the process after 10 minutes as not enough system resources are available. The metadata extraction and indexing of this VM will be handled later by the offline-indexing process.
RecoverVmSessions-b1d958e1-f05b-46a8-af3c-d7d1e5840631.log: 2024-06-19T01:36:57.092Z ERROR: [aaa7a1018b9ad483;86443860fffb28d7] Unable to reset disks to read-write mode after VSS quiesce operation set them to read-only.Cause
Het proces vm-file-extractor kan niet worden uitgevoerd vanwege een gebrek aan geheugen op het PowerProtect Data Manager zoekknooppunt. De minimale vereiste van het vrije geheugen is 800 MB. Het mislukken van het uitvoeren van vm-file-extractor heeft ervoor gezorgd dat de alleen-lezen bit niet goed is ingesteld. Dit leidt tot de foutmelding "Unable to reset disks to read/write mode after VSS quiesce operation set them to read-only."
Resolution
1. Meld u aan bij de PowerProtect Data Manager appliance met behulp van SSH, schakel over naar de rootgebruiker en voer onderstaande opdrachten uit om het wachtwoord van het PowerProtect Data Manager-zoekknooppunt op te halen.
source /opt/emc/vmdirect/unit/vmdirect.env && /opt/emc/vmdirect/bin/infranodemgmt get -secret -node_type SearchNode
2. Meld u aan bij elk zoekknooppunt met de referenties die u in stap 1 hebt gekregen.
3. Voer de onderstaande opdracht uit om het geheugengebruik van het zoekknooppunt te controleren.
free -m
4. Als het vrije geheugen inderdaad minder dan 800 MB is, voegt u meer geheugen toe aan het zoekknooppunt of start u het zoekknooppunt opnieuw op wanneer PowerProtect Data Manager inactief is om het toegewezen geheugen vrij te maken.
5. Voer de VM-herstelbewerking opnieuw uit.