Avamar VM Image-sikkerhetskopiering tar av og til lengre tid å fullføre på grunn av bruk av NBD i stedet for Hotadd

En fullføringstid for sikkerhetskopiering av Avamar VMware-imaget er inkonsekvent.

Noen ganger fullføres sikkerhetskopieringen raskt.

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å "trege" dager tar sikkerhetskopien mye lengre tid. Den nedenfor tar 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

Sikkerhetskopiene har lignende størrelser og endringsfrekvens. Begge kjører som "syntetisk full". Loggene indikerer at den raskere sikkerhetskopieringen bruker '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 tregere sikkerhetskopien rapporterer et problem ved hjelp av hotadd. Det faller tilbake til å bruke 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 brukte sikkerhetskopien en annen proxy.

Rask sikkerhetskopiering:

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

Tregere sikkerhetskopiering:

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

Fullmakten som ble brukt 21. september var ikke tilgjengelig 22. september.
Sikkerhetskopien brukte en annen proxy, som hadde konfigurasjonsproblemer.
Når du bruker denne forskjellige proxyen, kunne den ikke utnytte den raskere "hotadd" transportmodusen.

Loggen anbefaler hva du bør sjekke hvis hotadd-transport ikke kan brukes.

Hvis VM-konfigurasjonen ikke er endret, kontrollerer du de proxy-relaterte konfigurasjonskontrollene.
 

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)

Hvis du vil ha mer informasjon om mulige transportmoduser, kan du se:
https://pubs.vmware.com/vsphere-50/index.jsp?topic=%2Fcom.vmware.vddk.pg.doc_50%2FvddkDataStruct.5.5.html