VMware Sanal Makine yedeklemesinde alınan “(6) the backup failed to back up the requested files” hatasının giderilmesi.

Bu makalemde NetBackup 7.7.3 sürümü ile VMware ESXi 6.0 ortamındaki Windows Sanal Makinen yedeklenmesi sırasında alınan “(6) the backup failed to back up the requested files” hatanın giderilmesine değiniyor olacağım.

Hatalı Job İçeriği

03/06/2017 19:00:00 – Info nbjm (pid=4232) starting backup job (jobid=21812) for client WINTEXTVMS, policy WINTEXTVMS-VM-Backup, schedule Full03/06/2017 19:00:00 – Info nbjm (pid=4232) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=21812, request id:{93640FDD-7994-49EB-A1E5-5C80FD7E9909})03/06/2017 19:00:00 – requesting resource EMC_DDBOOST_250003/06/2017 19:00:00 – requesting resource netbackup.kadirkozan.local.NBU_CLIENT.MAXJOBS.WINTEXTVMS03/06/2017 19:00:00 – requesting resource netbackup.kadirkozan.local.NBU_POLICY.MAXJOBS.WINTEXTVMS-VM-Backup03/06/2017 19:00:16 – granted resource  netbackup.kadirkozan.local.NBU_CLIENT.MAXJOBS.WINTEXTVMS03/06/2017 19:00:16 – granted resource  netbackup.kadirkozan.local.NBU_POLICY.MAXJOBS.WINTEXTVMS-VM-Backup03/06/2017 19:00:16 – granted resource  MediaID=@aaaad;DiskVolume=NBU_STU;DiskPool=DD2500_DFC_DDPool01;Path=NBU_STU;StorageServer=DFC-emcdd2500;MediaServer=netbackup.kadirkozan.local03/06/2017 19:00:16 – granted resource  EMC_DDBOOST_250003/06/2017 19:00:56 – estimated 21760658 kbytes needed03/06/2017 19:00:56 – begin Parent Job03/06/2017 19:00:56 – begin VMware: Start Notify Script03/06/2017 19:00:56 – Info RUNCMD (pid=11636) started03/06/2017 19:00:57 – Info RUNCMD (pid=11636) exiting with status: 0Operation Status: 003/06/2017 19:00:57 – end VMware: Start Notify Script; elapsed time 0:00:0103/06/2017 19:00:57 – begin VMware: Step By ConditionOperation Status: 003/06/2017 19:00:57 – end VMware: Step By Condition; elapsed time 0:00:0003/06/2017 19:00:57 – begin VMware: Read File ListOperation Status: 003/06/2017 19:00:57 – end VMware: Read File List; elapsed time 0:00:0003/06/2017 19:00:57 – begin VMware: Create Snapshot03/06/2017 19:00:57 – started process bpbrm (pid=14416)03/06/2017 19:00:57 – Info bpbrm (pid=14416) WINTEXTVMS is the host to backup data from03/06/2017 19:00:57 – Info bpbrm (pid=14416) reading file list for client03/06/2017 19:00:57 – Info bpbrm (pid=14416) start bpfis on client03/06/2017 19:00:57 – Info bpbrm (pid=14416) Starting create snapshot processing03/06/2017 19:00:58 – Info bpfis (pid=6456) Backup started03/06/2017 19:00:59 – snapshot backup of client WINTEXTVMS using method VMware_v203/06/2017 19:01:49 – end VMware: Create Snapshot; elapsed time 0:00:5203/06/2017 19:01:49 – end writing03/06/2017 19:01:49 – Info bpfis (pid=6456) done. status: 003/06/2017 19:01:49 – Info bpfis (pid=6456) done. status: 0: the requested operation was successfully completedOperation Status: 003/06/2017 19:01:49 – end Parent Job; elapsed time 0:00:5303/06/2017 19:01:49 – Info nbjm (pid=4232) snapshotid=WINTEXTVMS_148881965603/06/2017 19:01:49 – begin VMware: Policy Execution Manager Preprocessed03/06/2017 19:16:00 – end VMware: Policy Execution Manager Preprocessed; elapsed time 0:14:1103/06/2017 19:16:00 – begin VMware: Stop On ErrorOperation Status: 003/06/2017 19:16:00 – end VMware: Stop On Error; elapsed time 0:00:0003/06/2017 19:16:00 – begin VMware: Delete Snapshot03/06/2017 19:16:00 – started process bpbrm (pid=8828)03/06/2017 19:16:01 – Info bpbrm (pid=8828) Starting delete snapshot processing03/06/2017 19:16:02 – Info bpfis (pid=11100) Backup startedOperation Status: 603/06/2017 19:16:05 – Info bpbrm (pid=8828) INF – vmwareLogger: removeVirtualMachineSnapshot: Request status 12.INF – vmwareLogger: removeVirtualMachineSnapshot: <ManagedObjectNotFoundFault xmlns=”urn:vim25″ xsi:type=”ManagedObjectNotFound”><obj type=”VirtualMachineSnapshot”></obj></ManagedObjectNotFoundFault>03/06/2017 19:16:05 – Info bpbrm (pid=8828) INF – vmwareLogger: removeVirtualMachineSnapshot: SYM_VMC_ERROR:  SOAP_ERROR03/06/2017 19:16:06 – Info bpbrm (pid=8828) INF – vmwareLogger: removeVirtualMachineSnapshot: Request status 12.INF – vmwareLogger: removeVirtualMachineSnapshot: <ManagedObjectNotFoundFault xmlns=”urn:vim25″ xsi:type=”ManagedObjectNotFound”><obj type=”VirtualMachineSnapshot”></obj></ManagedObjectNotFoundFault>03/06/2017 19:16:06 – Info bpbrm (pid=8828) INF – vmwareLogger: removeVirtualMachineSnapshot: SYM_VMC_ERROR:  SOAP_ERROR03/06/2017 19:16:07 – Info bpbrm (pid=8828) INF – vmwareLogger: removeVirtualMachineSnapshot: Request status 12.INF – vmwareLogger: removeVirtualMachineSnapshot: <ManagedObjectNotFoundFault xmlns=”urn:vim25″ xsi:type=”ManagedObjectNotFound”><obj type=”VirtualMachineSnapshot”></obj></ManagedObjectNotFoundFault>03/06/2017 19:16:07 – Info bpbrm (pid=8828) INF – vmwareLogger: removeVirtualMachineSnapshot: SYM_VMC_ERROR:  SOAP_ERROR03/06/2017 19:16:08 – Info bpbrm (pid=8828) INF – vmwareLogger: removeVirtualMachineSnapshot: Request status 12.INF – vmwareLogger: removeVirtualMachineSnapshot: <ManagedObjectNotFoundFault xmlns=”urn:vim25″ xsi:type=”ManagedObjectNotFound”><obj type=”VirtualMachineSnapshot”></obj></ManagedObjectNotFoundFault>03/06/2017 19:16:08 – Info bpbrm (pid=8828) INF – vmwareLogger: removeVirtualMachineSnapshot: SYM_VMC_ERROR:  SOAP_ERROR03/06/2017 19:16:09 – Info bpbrm (pid=8828) INF – vmwareLogger: removeVirtualMachineSnapshot: Request status 12.INF – vmwareLogger: removeVirtualMachineSnapshot: <ManagedObjectNotFoundFault xmlns=”urn:vim25″ xsi:type=”ManagedObjectNotFound”><obj type=”VirtualMachineSnapshot”></obj></ManagedObjectNotFoundFault>03/06/2017 19:16:09 – Info bpbrm (pid=8828) INF – vmwareLogger: removeVirtualMachineSnapshot: SYM_VMC_ERROR:  SOAP_ERROR03/06/2017 19:16:10 – Critical bpbrm (pid=8828) from client WINTEXTVMS: do_thaw: Unable to remove virtual machine snapshot, status=6 (SYM_VMC_SOAP_ERROR). Error Details: [].03/06/2017 19:16:12 – Critical bpbrm (pid=8828) from client WINTEXTVMS: vfm_thaw: method: VMware_v2, type: FIM, function: VMware_v2_thaw03/06/2017 19:16:12 – Critical bpbrm (pid=8828) from client WINTEXTVMS: snapshot delete returned status 103/06/2017 19:16:12 – Info bpfis (pid=11100) done. status: 103/06/2017 19:16:12 – end VMware: Delete Snapshot; elapsed time 0:00:1203/06/2017 19:16:12 – Info bpfis (pid=11100) done. status: 1: the requested operation was partially successful03/06/2017 19:16:12 – end writingOperation Status: 103/06/2017 19:16:12 – begin VMware: End Notify Script03/06/2017 19:16:12 – Info RUNCMD (pid=13864) started03/06/2017 19:16:12 – Info RUNCMD (pid=13864) exiting with status: 0Operation Status: 003/06/2017 19:16:12 – end VMware: End Notify Script; elapsed time 0:00:00Operation Status: 6the backup failed to back up the requested files  (6)

Hata içeriği

03/06/2017 19:16:10 – Critical bpbrm (pid=8828) from client WinTestVMs: do_thaw: Unable to remove virtual machine snapshot, status=6 (SYM_VMC_SOAP_ERROR). Error Details: [].03/06/2017 19:16:12 – Critical bpbrm (pid=8828) from client WinTextVMs: vfm_thaw: method: VMware_v2, type: FIM, function: VMware_v2_thaw03/06/2017 19:16:12 – Critical bpbrm (pid=8828) from client WinTextVMs: snapshot delete returned status 1

Sorun Giderilmesi

Windows işletim sisteminde TCPMAXDATARETRANSMISSIONS değeri varsayılan değer 5 dir. Bu değer ile birikte TCPMAXCONNECTRETRANSMISSIONS değerininde  varsayılan ayarlarından yükseltilmesi Veritas tarafından önerilmektedir. TcpMaxDataRetransmissions  değeri 10’a ve TcpMaxConnectRetransmissions  değeri de 3’e yükselterek bu sorunun ortaya çıkmasını en aza indirebilirsiniz. Bu işlem Windows Registry Editor uygulamasını çalıştırınız ve “HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters” adresine gidiniz. Yeni bir DWORD değeri oluşturunuz ve tavisye edilen decimal değerleri tanımlayınız.

Yapılan bu değişikliğin ardından işletim sisteminizi yeniden başlatınız ve hata veren yedekleme policy’nizi yeniden çalıştırınız.

Test

 03/07/2017 08:03:19 – Info nbjm (pid=4232) starting backup job (jobid=22035) for client WINTEXTVMS, policy WINTEXTVMS-VM-Backup, schedule Full03/07/2017 08:03:20 – estimated 21760658 kbytes needed03/07/2017 08:03:20 – Info nbjm (pid=4232) started backup (backupid=WINTEXTVMS_1488866599) job for client WINTEXTVMS, policy WINTEXTVMS-VM-Backup, schedule Full on storage unit EMC_DDBOOST_2500 using backup host rns-netbackup01.kadirkozan.local03/07/2017 08:03:20 – started process bpbrm (pid=16012)03/07/2017 08:03:21 – Info bpbrm (pid=16012) WINTEXTVMS is the host to backup data from03/07/2017 08:03:21 – Info bpbrm (pid=16012) reading file list for client03/07/2017 08:03:21 – Info bpbrm (pid=16012) accelerator enabled03/07/2017 08:03:25 – Info bpbrm (pid=16012) starting bpbkar32 on client03/07/2017 08:03:25 – Info bpbkar32 (pid=5592) Backup started03/07/2017 08:03:25 – Info bpbkar32 (pid=5592) accelerator enabled backup, archive bit processing:<disabled>03/07/2017 08:03:25 – Info bptm (pid=7484) start03/07/2017 08:03:25 – Info bptm (pid=7484) using 262144 data buffer size03/07/2017 08:03:25 – Info bptm (pid=7484) setting receive network buffer to 1049600 bytes03/07/2017 08:03:25 – Info bptm (pid=7484) using 30 data buffers03/07/2017 08:03:25 – connecting03/07/2017 08:03:25 – connected; connect time: 0:00:0003/07/2017 08:03:26 – Info bpbkar32 (pid=5592) INF – Backing up vCenter server 192.168.100.20, ESX host HPESXHOST01.kadirkozan.local, BIOS UUID 4205ed01-8d7b-0357-31fd-c1ee35425608, Instance UUID 50050ba8-1cb0-04d6-db2b-24477cde59b1, Display Name WINTEXTVMS, Hostname WINTEXTVMS.kadirkozan.local03/07/2017 08:03:29 – Info bptm (pid=7484) start backup03/07/2017 08:03:30 – begin writing03/07/2017 08:05:29 – Info bpbkar32 (pid=5592) INF – Transport Type =  nbd03/07/2017 08:06:17 – Info bptm (pid=7484) waited for full buffer 897 times, delayed 8969 times03/07/2017 08:06:17 – Info bpbkar32 (pid=5592) accelerator sent 469120512 bytes out of 18553913344 bytes to server, optimization 97.5%03/07/2017 08:06:18 – Info bpbkar32 (pid=5592) bpbkar waited 1 times for empty buffer, delayed 1 times.03/07/2017 08:06:32 – Info bptm (pid=7484) EXITING with status 0 <———-03/07/2017 08:06:32 – Info bpbrm (pid=16012) validating image for client WINTEXTVMS03/07/2017 08:06:34 – Info bpbkar32 (pid=5592) done. status: 0: the requested operation was successfully completed03/07/2017 08:06:34 – end writing; write time: 0:03:04the requested operation was successfully completed  (0)

Kaynaklar

https://support.microsoft.com/en-us/help/170359/how-to-modify-the-tcp-ip-maximum-retransmission-time-out

https://www.veritas.com/support/en_US/article.TECH37307