NetWorker: o nsrclone falha ao clonar o saveset que anteriormente falha ao clonar automaticamente por meio de um script quando o DD Retention Lock está ativado

Summary: O nsrclone falha ao clonar o saveset que anteriormente falha ao clonar automaticamente usando um script quando o DD Retention Lock está ativado.

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.
Check out other resources

Symptoms

  • Alguns savesets anteriormente falham ao clonar usando um script ou automaticamente.
  • O saveset "ghost" pode ser exibido sem o nome do volume com mminfo (veja abaixo).
  • Verifique se o file system de destino mostra o arquivo de saveset, mas NÃO o arquivo "notes".
  • O comando de saveset do scanner apresenta falha (veja abaixo).
  • Outras tentativas de clonar o saveset falham com o erro: Err: 5004-nfs lookup failed (nfs: Não existe esse arquivo ou diretório)
A saída da CLI mminfo mostra o saveset de clone com falha com o indicador "E": 
# mminfo -q ssid=928093938 -r ssid,cloneid,ssretent,clretent,ssflags,clflags,copies
ssid         clone id retent  clretent ssflags clflg copies
928093938   1532073714 08/24/2018 08/20/2018 vrF         2
928093938   1532252170 08/24/2018 08/24/2018 vrF   E     <--- This is the incomplete clone.

No entanto, depois de adicionarmos o switch de "volume", apenas uma linha é relatada: 
# mminfo -q ssid=928093938 -r ssid,cloneid,ssretent,clretent,ssflags,clflags,copies,volume
ssid         clone id retent  clretent ssflags clflg copies volume
928093938   1532073714 08/24/2018 08/20/2018 vrF         2 source-volume-name
                                                         ^ ---2 copies yet only 1 shows in the output.

Resultado da CLI do scanner: 
8909:scanner: using 'DD-name_destination-device-path' as the device name
8936:scanner: scanning Data Domain disk destination-volume-name on DD-name_destination-device-path
8939:scanner: Data Domain disk destination-volume-name already exists in the media index
107505:scanner: Opening the file '/nw-server-name/destination-device-path/08/04/notes/705d0dc6-00000004-5982f3fd-599ed855-190c442c-4c9896fd' failed [5004] ([57525] [140043448723232] Wed Aug  1 13:18:50 2018
        ddp_open_file() failed for File: //nw-server-name/destination-device-path/08/04/notes/705d0dc6-00000004-5982f3fd-599ed855-190c442c-4c9896fd, Err: 5004-nfs lookup failed (nfs: No such file or directory)
).
107505:scanner: Opening the file '/nw-server-name/destination-device-path/08/04/notes/705d0dc6-00000004-5982f3fd-599ed855-190c442c-4c9896fd' failed [5004] ([57525] [140043448723232] Wed Aug  1 13:18:50 2018
        ddp_open_file() failed for File: //nw-server-name/destination-device-path/08/04/notes/705d0dc6-00000004-5982f3fd-599ed855-190c442c-4c9896fd, Err: 5004-nfs lookup failed (nfs: No such file or directory)
).
8761:scanner: done with Data Domain disk destination-volume-name
Resultado da CLI nsrclone:  
80470:nsrclone: Following volumes are needed for cloning
80471:nsrclone:         source-volume-name (DD)
100303:nsrclone: Cloning savesets from storage node 'nw-server-name'
142165:nsrclone: Number of clone threads per client is set to 256. Max number of savesets per thread is set to 0. Max client threads is set to 0.
104860:nsrclone: Concurrent proxy clone started for service type DD.
Cloning save sets from the volume source-volume-name
Total client count in a volume source-volume-name is 1
77426:nsrclone: Cloning save sets from the volume source-volume-name
104861:nsrclone: Total client count in a volume source-volume-name is 1
104864:nsrclone: Number of clone threads per client set to 1. Max number of savesets per thread is set to 0. Max client threads is set to 30 for volume source-volume-name
174908:nsrclone: Saving the backup data in the pool 'destination-pool'.
175019:nsrclone: Received the media management binding information on the host 'nw-server-name'.
174910:nsrclone: Connected to the nsrmmd process on the host 'nw-server-name'.
32379:nsrclone: Cloning save set index:705d0dc6-00000004-5982f3fd-599ed855-190c442c-4c9896fd (ssid/cloneid 928093938/1532073714)
75360:nsrclone: Cloning of size 1 KB is in progress...
72985:nsrclone: Source volume 'source-volume-name' ready for cloning
75675:nsrclone: Failed to initiate the save nsrmmd to create a clone instance.
Direct File Save failed for /nw-server-name/destination-device-path/active/df304e8e-00000006-375196f2-5b5196f2-23ce16ac-34ae8c2d on volume destination-volume-name
75267:nsrclone: Failed to initiate mmd session for ssid 928093938.
75712:nsrclone: Cloning failed for save set : index:705d0dc6-00000004-5982f3fd-599ed855-190c442c-4c9896fd (ssid 928093938)
77276:nsrclone: Total size cloned so far: 0 KB.

141764:nsrclone: Unable to perform clone of client saveset. Error: proxy_clone_rs failed.

104863:nsrclone: Concurrent proxy clone completed for sevice type DD.
67790:nsrclone: Total size cloned: 0 KB.
77275:nsrclone: DD cloning failed
Proxy clone failed to clone all or few savesetsSome of the clones failed
Some of the clones failed

Cause

O DD tem o Retention Lock ativado. Isso impediu que o saveset original incompleto seja removido e impede que a próxima tentativa de clonagem supere os dados no caminho de destino.

Resolution

Solução temporária:

Na tentativa de scanner acima, localize o caminho do saveset no destino: 
//nw-server-name/destination-device-path/08/04/notes/705d0dc6-00000004-5982f3fd-599ed855-190c442c-4c9896fd

Precisamos do caminho do próprio saveset, que será um nível acima das "notas", por exemplo: 
//nw-server-name/destination-device-path/08/04/

Em seguida, adicione o caminho de mtree do DD, que sempre inicia /data/col1/mtree-name. "mtree list" na CLI do DD mostra os Mtrees configurados. Normalmente, o nome da Mtree corresponde ao nome do servidor do NetWorker do host. Em seguida, adicione o nome do saveset longo ao final.
Neste exemplo, o caminho completo se torna: 
/data/col1/nw-server-name/destination-device-path/08/04//705d0dc6-00000004-5982f3fd-599ed855-190c442c-4c9896fd

Devemos usar esse caminho para desativar o bloqueio de retenção no sistema Data Domain de destino:
  • Na CLI do DD de destino, execute: mtree retention-lock revert [path] (path from above) Isso solicita a senha do sysadmin.
  • Clone o saveset novamente - isso agora deve funcionar sem erro porque agora ele pode gravar no caminho de destino.
  • As consultas mminfo para os savesets clonados agora devem funcionar corretamente.
  • Repita para todos os outros savesets afetados.

Affected Products

NetWorker

Products

NetWorker
Article Properties
Article Number: 000052916
Article Type: Solution
Last Modified: 27 Sept 2023
Version:  3
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.