PPDM: la restauración de VM orientada a las aplicaciones fallaba con el mensaje "No se pueden restablecer los discos al modo de lectura/escritura después de que la operación de reposo de VSS los configuró en solo lectura"
Summary: La restauración de VM orientada a aplicaciones fallaba con el mensaje "No se pueden restablecer los discos al modo de lectura/escritura después de que la operación de reposo de VSS los configura en solo lectura" debido a la falta de memoria en el nodo de búsqueda. ...
Symptoms
Unable to reset disks to read-write mode after VSS quiesce operation set them to read-only
En "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 informa a continuación PRECAUCIÓN, que indica la falta de memoria, antes de lanzar el ERROR para restablecer los discos al modo de lectura/escritura.
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
El proceso vm-file-extractor no se puede ejecutar debido a la falta de memoria en el nodo de búsqueda de PowerProtect Data Manager. El requisito mínimo de memoria libre es de 800 MB. La falla de la ejecución de vm-file-extractor causó que el bit de solo lectura no se configurara correctamente. Por lo tanto, se genera el error "No se pueden restablecer los discos al modo de lectura/escritura después de que la operación de reposo de VSS los configure en solo lectura".
Resolution
1. Inicie sesión en el dispositivo PowerProtect Data Manager mediante SSH, cambie al usuario raíz y ejecute los siguientes comandos para obtener la contraseña del nodo de búsqueda de PowerProtect Data Manager.
source /opt/emc/vmdirect/unit/vmdirect.env && /opt/emc/vmdirect/bin/infranodemgmt get -secret -node_type SearchNode
2. Inicie sesión en cada nodo de búsqueda con las credenciales obtenidas en el paso 1.
3. Ejecute el siguiente comando para comprobar el uso de memoria del nodo de búsqueda.
free -m
4. Si la memoria libre es realmente menor que 800 MB, agregue más memoria al nodo de búsqueda o reinicie el nodo de búsqueda cuando PowerProtect Data Manager esté inactivo para liberar la memoria asignada.
5. Vuelva a ejecutar la restauración de la máquina virtual.