Avamar VM-sikkerhedskopiering af afbildning tager lejlighedsvis længere tid at fuldføre på grund af brug af nbd i stedet for hotadd

Fuldførelsestiden for sikkerhedskopiering af Avamar VMware-afbildning er inkonsekvent.

Nogle gange fuldføres sikkerhedskopieringen hurtigt.

2017-09-21 05:15:08 avtar Info <5156>: Backup #223 timestamp 2017-09-21 05:15:08, 0 files, 925.0 GB (0 files, 352.2 GB, 38.07% new)
2017-09-21 05:15:08 avtar Info <6083>: Backed-up 925.0 GB in 192.63 minutes: 288 GB/hour (0 files/hour)
2017-09-21 05:15:08 avtar Info <7883>: Finished at 2017-09-21 05:15:08 CEST, Elapsed time: 0003h:12m:37s

På 'langsomme' dage tager sikkerhedskopieringen meget længere tid. Den nedenfor tager 24 timer.

2017-09-23 02:10:04 avtar Info <5156>: Backup #224 timestamp 2017-09-23 02:10:04, 0 files, 925.0 GB (0 files, 334.5 GB, 36.16% new)
2017-09-23 02:10:04 avtar Info <6083>: Backed-up 925.0 GB in 1447.94 minutes: 38 GB/hour (0 files/hour)
2017-09-23 02:10:04 avtar Info <7883>: Finished at 2017-09-23 02:10:04 CEST, Elapsed time: 0024h:07m:56s

Sikkerhedskopierne har lignende størrelser og ændringshastighed. Begge kører som 'syntetisk fuld'. Logfilerne angiver, at den hurtigere backup bruger 'hotadd'

2017-09-21 02:03:06 avvcbimage Info <0000>: Connected with hotadd transport to virtual disk [XXXXX] XXXXXXXX.vmdk. Time to connect: 35082 msecs

Den langsommere sikkerhedskopiering rapporterer et problem med at oprette forbindelse ved hjælp af hotadd. Det falder tilbage til at bruge nbd.

2017-09-22 02:13:22 avvcbimage Info <12006>: hotadd transport is recommended for faster backups and restores and less exposure to network routing, firewall and SSL certificate issues. 
2017-09-22 02:13:22 avvcbimage Info <12007>: One or more of these items may be preventing use of hotadd transport with this VM: 
2017-09-22 02:14:03 avvcbimage Info <12013>: Check that the VM being backed up is in the same datacenter as the backup proxy VM. Hotadd transport cannot cross a Datacenter boundary. . . . 
2017-09-22 02:13:22 avvcbimage Info <0000>: Connected with nbd transport to virtual disk [XXXXX] XXXXXXX.vmdk. Time to connect: 353256 msecs

Hver dag brugte sikkerhedskopien en anden proxy.

Hurtig sikkerhedskopiering:

2017-09-21 02:00:09 avvcbimage Info <18672>: proxy VM Instance name is: xxxxx-proxy-8 

Langsommere sikkerhedskopiering:

2017-09-22 02:00:15 avvcbimage Info <18672>: proxy VM Instance name is: xxxxx-proxy-2 

Den proxy, der blev brugt den 21. september, var ikke tilgængelig den 22. september.
Sikkerhedskopieringen brugte en anden proxy, som havde konfigurationsproblemer.
Når du bruger denne anden proxy, kunne den ikke udnytte den hurtigere 'hotadd' transporttilstand.

Loggen anbefaler, hvad man skal kontrollere, hvis hotadd-transport ikke kan bruges.

Hvis VM-konfigurationen ikke er blevet ændret, skal du kontrollere de proxyrelaterede konfigurationskontroller.
 

2017-09-22 02:13:22 avvcbimage Info <12007>: One or more of these items may be preventing use of hotadd transport with this VM:
2017-09-22 02:14:03 avvcbimage Info <12008>:  Check that the backup proxy VM(127.0.0.2,xxxx-avpro4,10.10.8.53,10.10.7.53) is deployed on an ESX(i) host that has a path to the storage holding the virtual disk being backed up ([XXXXXXXX] XXXXX.vmdk). Also check that the proxy is configured to protect this datastore
2017-09-22 02:14:03 avvcbimage Info <12009>:  Check that the vmfs holding the backup proxy VM has a total capacity equal to the size of the largest virtual disk being backed up. (Capacity merely has to be present - Free space can be less than this amount)
2017-09-22 02:14:03 avvcbimage Info <12010>:  Check that the vmfs holding the backup proxy VM is formatted with a vmfs block size which supports the size of the largest virtual disk being backed up
2017-09-22 02:14:03 avvcbimage Info <12011>:  Check that the VM being backed up has no virtual hard disks designated as independent
2017-09-22 02:14:03 avvcbimage Info <12012>:  Check that the VM being backed up has no IDE virtual hard disks, usually an artifact of a P2v conversion - use SCSI virtual disks instead
2017-09-22 02:14:03 avvcbimage Info <12013>:  Check that the VM being backed up is in the same datacenter as the backup proxy VM. Hotadd transport cannot cross a Datacenter boundary.
2017-09-22 02:14:03 avvcbimage Info <12014>:  Check that no VMs, and no vmdk's within the vCenter have the same name as those associated with the VM being backed up. (unusual but possible)

Du kan finde flere oplysninger om de mulige transporttilstande her under:
https://pubs.vmware.com/vsphere-50/index.jsp?topic=%2Fcom.vmware.vddk.pg.doc_50%2FvddkDataStruct.5.5.html