#1 2020-08-30 12:52:56

Robertkwild
Member
Registered: 2020-05-25
Posts: 20

backup job failing on one vm - disks not found

hi all,

i have a vm failing backup but the thing is it clones both sdX's as both vmdks say 100% done and when i go into my datastore folder i can see both vmdks there

but this is the error i get

./xsibackup: eval: line 1: disk0: not found
./xsibackup: eval: line 1: disk1: not found
Backing up virtual disks...

any help please?

thanks,
rob

Offline

#2 2020-08-31 06:19:53

admin
Administrator
Registered: 2017-04-21
Posts: 1,363

Re: backup job failing on one vm - disks not found

There's some inconsistency in the VM layout. Look for the 'eval' keyword in the source code and debug or check your .vmx file to find the cause. Looks like some missing disk is in the .vmx file.

Offline

#3 2020-08-31 09:22:28

Robertkwild
Member
Registered: 2020-05-25
Posts: 20

Re: backup job failing on one vm - disks not found

thanks administrator,

when you say look at the source code, is the source code in the .vmx file?

Offline

#4 2020-08-31 14:11:18

admin
Administrator
Registered: 2017-04-21
Posts: 1,363

Re: backup job failing on one vm - disks not found

The source in the xsibackup file, you need some minimum Bash coding skills to do that.
If that's not the case, just inspect the VM .vmx file to find out why the program complains about those missing disks

Offline

#5 2020-08-31 20:02:21

Robertkwild
Member
Registered: 2020-05-25
Posts: 20

Re: backup job failing on one vm - disks not found

ok ive had a look in the .vmx file

scsi0:0.deviceType = "scsi-hardDisk"
scsi0:0.fileName = "lon-d-squid.vmdk"
scsi0:0.present = "TRUE"
scsi0:1.deviceType = "scsi-hardDisk"
scsi0:1.fileName = "lon-d-squid_1.vmdk"
scsi0:1.present = "TRUE"

as you can see theres 2 vmdks

if i go in the datastore, browse the vm, i can also see the 2 vmdks

lon-d-squid.vmdk
lon-d-squid_1.vmdk

also if i right click the vm edit and expand both hard drives, i see

vmdk is scsi 0:0
1.vmdk is scsi 0:1

i cant see any problems, or maybe im missing something?

Offline

#6 2020-09-06 22:55:19

Robertkwild
Member
Registered: 2020-05-25
Posts: 20

Re: backup job failing on one vm - disks not found

think i have found the problem

https://33hops.com/esxi-snapshot-errors … tions.html

i have checked and it has no snapshots in manage snapshots

all i can see is vmdk (disk0) and vmdk1 (disk1)

i attach a picture of my vm template

https://i.postimg.cc/gjW6dCyL/vm.png

can you spot the rogue snapshot?

thanks,
rob

Last edited by Robertkwild (2020-09-06 23:19:28)

Offline

#7 2020-09-09 16:17:33

Robertkwild
Member
Registered: 2020-05-25
Posts: 20

Re: backup job failing on one vm - disks not found

so just to clarify, when xsibackup says disk0 and disk1 not found does it mean

disk0 = lon-d-squid.vmdk

disk1 = lon-d-squid_1.vmdk

Offline

#8 2020-09-09 22:58:23

Robertkwild
Member
Registered: 2020-05-25
Posts: 20

Re: backup job failing on one vm - disks not found

ok this is one for you guys as im speechless...

found out the backup fails when the vm is running

when i powered down the vm and kicked off the backup again, guess what it works with no errors

im pretty sure its to do with all the services running on this vm as its squid, i have

squid

squidclamav

clamav

c-icap

im pretty sure clamav or c-icap are messing with the backup

Offline

#9 2020-09-11 11:09:34

admin
Administrator
Registered: 2017-04-21
Posts: 1,363

Re: backup job failing on one vm - disks not found

Are you using ESXi 7.0?, please note that ESXi Free is not compatible with version 7.0 that is stated in the product page.

Offline

#10 2020-09-18 07:34:18

Robertkwild
Member
Registered: 2020-05-25
Posts: 20

Re: backup job failing on one vm - disks not found

no im using esxi 6.7u3

Offline

#11 2020-09-22 16:09:45

admin
Administrator
Registered: 2017-04-21
Posts: 1,363

Re: backup job failing on one vm - disks not found

We followed your issue in VMWare Communities too. We really can't grasp, with the information that you have provided so far, why was this VM failing to be backed up, we have the feeling that it had something to do with the snapshot system, maybe some old snapshot info remained in some config file like .vmsd

We have answered to your post in VMWare Communities with some general advices to help narrow this kind of issues down.
https://communities.vmware.com/thread/642236?start=30

Offline

Board footer