VDP 5.1.11.3 - Problem to backup 4 of all my VMs

gpriou · ‎10-02-2013

Hi,

I'm encontering a problem to backup just 4 VMs of all my VMs since I upgrade from ESXi 4.1 to 5.1.

To begin, I have 2 VMware ESXi.

All was OK with VMware ESXi 4.1 and VMware Data Recovery.

When I upgraded from 4.1 to 5.1, impossible for me to megrate old bachkup from VDR because of the plugin version used of VDR : v 1.x

So, after upgrading to ESXi 5.1, i began from scratch.

I created a new datastore of 3.6To (on a NAS with iSCSI LUN)

I created 3 tasks backup.

And now I have always the same problem on always the same 4 vritual machines.

VDP : Échec de l'opération à cause d'un snapshot existant. (Fail due to an existant snapshot)
erreur
02/10/2013 16:30:16
VDP : procédure de sauvegarde
vSphere Data Protection
DOMAIN\vdp

The problem is that when I check the snapshot manager, there are no snapshot for those VMs.

When I browse the datastore, strangely, many many files like this :

VmName-0000xx.vmdk

VmName_1-0000xx.vmdk

So what is the issue ?

An other problem, maybe in link with my problem, I often have this message in logs :

Impossible de connecter DOMAIN\vdp@192.168.180.7 (Impossible to connect DOMAIN\vdp@192.168.180.7) : 192.168.180.7 is my VDP appliance IP

erreur

02/10/2013 16:34:03

DOMAIN\vdp

Thanks a lot for your help

OscarDavey · ‎10-02-2013

To resolve this issue, you must configure a DNS host record before deploying a vSphere Data Protection (VDP) appliance. Make sure you have configured your DNS server for the VDP appliance with a pointer for mapping the IP address to the VDP appliance, and that it is created according to your vendor's specifications.

for more info please check this KB :

VMware KB: IP/DNS could not be resolved during vSphere Data Protection (VDP) 5.1.x installation

Hope this helped .

Best regards

Your Oscar

gpriou · ‎10-02-2013

Hi,

Thanks for your help, but I did it when I installed VDP.

To install VDP, I used the manual.

I verified just now :

Envoi d'une requête 'ping' sur vmvspheredataprotection.domain.local [192.168.180.7]

avec 32 octets de données :

Réponse de 192.168.180.7 : octets=32 temps<1ms TTL=64

Statistiques Ping pour 192.168.180.7:

Paquets : envoyés = 3, reçus = 3, perdus = 0 (perte 0%),

Durée approximative des boucles en millisecondes :

Minimum = 0ms, Maximum = 0ms, Moyenne = 0ms

Ctrl+C

^C

C:\Users\gpr>nslookup 192.168.180.7

Serveur : pdc.domain.local

Address: 192.168.180.15

Nom : vmvspheredataprotection.domain.local

So problem is not here.