PPDM - Sovellustietoinen virtuaalikoneen palautus epäonnistui ja näytti "Levyjä ei voi palauttaa luku-/kirjoitustilaan VSS quiesce -toiminnon jälkeen, kun ne on määritetty vain luku -tilaan"

Summary: Sovellustietoinen virtuaalikoneen palautus epäonnistui sanomalla "Levyjä ei voi palauttaa luku-/kirjoitustilaan VSS quiesce -toiminnon jälkeen, aseta ne vain luku -tilaan", koska hakusolmussa ei ole muistia. ...

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.

Symptoms

PowerProtect Data Managerin sovellustietoisten virtuaalikoneiden palautus epäonnistui ja antoi virheilmoituksen
Unable to reset disks to read-write mode after VSS quiesce operation set them to read-only

PowerProtect Data Manager_*******.log -kohdassa
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 ilmoitettu alla VAROITUS, joka osoittaa muistin puutteen, ennen kuin heität pois VIRHEEN levyjen palauttamiseksi luku-/kirjoitustilaan.
    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

Prosessia vm-file-extractor ei voi suorittaa, koska PowerProtect Data Managerin hakusolmussa ei ole riittävästi muistia. Vapaan muistin vähimmäisvaatimus on 800 Mt. Vain luku -bitin virheellinen suorittaminen aiheutti sen, että vain luku -bittiä ei asetettu oikein. Tämä johtaa virheeseen "Levyjä ei voi palauttaa luku- / kirjoitustilaan VSS quiesce -toiminnon jälkeen, aseta ne vain luku -tilaan".

Resolution

1. Kirjaudu PowerProtect Data Manager -laitteeseen SSH-yhteydellä, vaihda pääkäyttäjään ja hae PowerProtect Data Manager -hakusolmun salasana suorittamalla alla olevat komennot.

source /opt/emc/vmdirect/unit/vmdirect.env && /opt/emc/vmdirect/bin/infranodemgmt get -secret -node_type SearchNode

2. Kirjaudu kuhunkin hakusolmuun tunnistetiedoilla vaiheessa 1.
3. Tarkista hakusolmun muistin käyttö suorittamalla alla oleva komento.

free -m

4. Jos vapaata muistia on alle 800 Mt, lisää muistia hakusolmuun tai käynnistä hakusolmu uudelleen, kun PowerProtect Data Manager on käyttämättömänä, jotta varattu muisti vapautuu.
5. Suorita virtuaalikoneen palautus uudelleen.

Affected Products

PowerProtect Data Manager Appliance
Article Properties
Article Number: 000226205
Article Type: Solution
Last Modified: 02 Sept 2025
Version:  2
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.