PPDM - A restauração de VMs com reconhecimento de aplicativos apresentou falha com a mensagem "Unable to reset disks to read/write mode after VSS quiesce operation set them to read-only"
Summary: A restauração de VMs com reconhecimento de aplicativos apresentou falha com "Unable to reset disks to read/write mode after VSS quiesce operation sets sets to read-only" devido à falta de memória no nó de pesquisa. ...
Symptoms
Unable to reset disks to read-write mode after VSS quiesce operation set them to read-only
Em "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 relatou abaixo o AVISO, indicando a falta de memória, antes de lançar o ERRO ao redefinir os discos para o modo de leitura/gravação.
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
Não é possível executar o processo vm-file-extractor devido à falta de memória no nó de pesquisa do PowerProtect Data Manager. O requisito mínimo de memória livre é 800 MB. A falha na execução do vm-file-extractor fez com que o bit somente leitura não fosse definido corretamente. Assim, levando ao erro "Não é possível redefinir os discos para o modo de leitura/gravação após a operação de desativação do VSS, defina-os como somente leitura".
Resolution
1. Faça log-in no equipamento PowerProtect Data Manager usando SSH, alterne para o usuário root e execute os comandos abaixo para obter a senha do nó de pesquisa do PowerProtect Data Manager.
source /opt/emc/vmdirect/unit/vmdirect.env && /opt/emc/vmdirect/bin/infranodemgmt get -secret -node_type SearchNode
2. Faça log-in em cada nó de pesquisa usando as credenciais obtidas na etapa 1.
3. Execute o comando abaixo para verificar o uso de memória do nó de pesquisa.
free -m
4. Se a memória livre for realmente inferior a 800 MB, adicione mais memória ao nó de pesquisa ou reinicialize o nó de pesquisa quando o PowerProtect Data Manager estiver ocioso para liberar a memória alocada.
5. Execute novamente a restauração da VM.