Skip to main content

Updated vmware to 4.1.0 988178 and all vmtools. Now backups do not run

Thread needs solution

Since upgrading vmware 4.1.0 U3 version to the latest update 988178, and then updating the vmtools on every virtual machine, vmProtect cannot produce backups.

The logs ALL inducate cannot find any disk or volumes to back up which is odd because further up the log it says "adding virtual hard disk" and it lists a VMDK file, so part of Acronis knows there are hard disks, but part of it does not (Step 14 below).

Here is an example of one machine. Note they all say this except the mail server.
Backup has failed. Please check the log for additional information.
1 Information 2/24/13 10:00:01 AM Task 'ITWORKPC' changed its state from 'idle' to 'running'.
2 Information 2/24/13 10:00:01 AM Task 'ITWORKPC' was started.
3 Information 2/24/13 10:00:07 AM Backing up VM(s).
4 Information 2/24/13 10:00:07 AM Successfully connected to 'VMware vCenter Server 4.1.0 build-799345'.
5 Information 2/24/13 10:00:07 AM Successfully connected to 'VMware ESX 4.1.0 build-988178' through VMware vCenter Server.
6 Information 2/24/13 10:00:08 AM Successfully connected to 'VMware ESX 4.1.0 build-988178' through VMware vCenter Server.
7 Information 2/24/13 10:00:08 AM Successfully connected to 'VMware ESX 4.1.0 build-988178' through VMware vCenter Server.
8 Information 2/24/13 10:00:09 AM Successfully connected to 'VMware vCenter Server 4.1.0 build-799345'.
9 Information 2/24/13 10:00:11 AM Successfully connected to 'VMware vCenter Server 4.1.0 build-799345'.
10 Information 2/24/13 10:00:11 AM Successfully connected to 'VMware ESX 4.1.0 build-988178' through VMware vCenter Server.
11 Information 2/24/13 10:00:20 AM Creating snapshot (2/24/13 10:00:11 AM).
12 Information 2/24/13 10:00:20 AM Successfully connected to 'VMware ESX 4.1.0 build-988178' through VMware vCenter Server.
13 Information 2/24/13 10:00:21 AM Load virtual machine 'vm://86E16424-D25B-4E0D-AB44-B3544AC9B64A/529439e7-a248-bcb4-68e7-a1b09569aa64?host=host-10&type=vmwesx' into the disk subsystem.
14 Information 2/24/13 10:00:21 AM Adding virtual hard disk '[vm3-sas] ITWORKPC/ITWORKPC.vmdk' to '0:1'.
15 Information 2/24/13 10:10:27 AM Detaching hard disk 'SCSI0:1'.
16 Error 2/24/13 10:10:33 AM Failed to open raw hard disk data file '[vm3-sas] ITWORKPC/ITWORKPC.vmdk'.
Additional info:
--------------------
Error code: 94
Module: 83
LineInfo: 1b5da992938b2ae1
Fields:
Message: Failed to open raw hard disk data file '[vm3-sas] ITWORKPC/ITWORKPC.vmdk'.
--------------------
Error code: 64
Module: 83
LineInfo: 7feed46a356d56b9
Fields:
Message: Failed to add SCSI disk to the system. Host: 2; Target: 1.
--------------------
Error code: 64
Module: 83
LineInfo: 7feed46a356d56b0
Fields:
Message: Cannot find attached hard disks in the system.
--------------------
17 Information 2/24/13 10:10:34 AM Remove snapshot (snapshot-8200).
18 Information 2/24/13 10:10:34 AM Task 'ITWORKPC' changed its state from 'running' to 'idle'.
19 Error 2/24/13 10:10:34 AM Task 'ITWORKPC' failed: 'Failed to create a backup.
Additional info:
--------------------
Error code: 3
Module: 435
LineInfo: 555b5abba09501ce
Fields:
Message: Failed to create a backup.
--------------------
Error code: 32786
Module: 114
LineInfo: 28314c961de7d32e
Fields:
Message: Failed to prepare for backing up.
--------------------
Error code: 353
Module: 149
LineInfo: a71592046cb2c5f6
Fields:
Message: Failed to back up the group.
--------------------
Error code: 2
Module: 218
LineInfo: 338a407ad20e0987
Fields:
Message: Error occurred while running the backup and recovery engine.
--------------------
Error code: 1080
Module: 1
LineInfo: 145a191bfe9050d1
Fields:
Message: Failed to execute the operation.
--------------------
Error code: 1005
Module: 1
LineInfo: bb03ce40e9a37f1a
Fields:
Message: Cannot find any disk or volumes to back up. The operation has been terminated.
--------------------'.

Here is the mail server

Backup has failed. Please check the log for additional information.
1 Information 2/23/13 10:00:02 PM Task 'MAIL' changed its state from 'idle' to 'running'.
2 Information 2/23/13 10:00:02 PM Task 'MAIL' was started.
3 Information 2/23/13 10:00:08 PM Backing up VM(s).
4 Information 2/23/13 10:00:08 PM Successfully connected to 'VMware vCenter Server 4.1.0 build-799345'.
5 Information 2/23/13 10:00:09 PM Successfully connected to 'VMware ESX 4.1.0 build-988178' through VMware vCenter Server.
6 Information 2/23/13 10:00:14 PM Successfully connected to 'VMware ESX 4.1.0 build-988178' through VMware vCenter Server.
7 Information 2/23/13 10:00:14 PM Successfully connected to 'VMware ESX 4.1.0 build-988178' through VMware vCenter Server.
8 Information 2/23/13 10:00:23 PM Successfully connected to 'VMware vCenter Server 4.1.0 build-799345'.
9 Information 2/23/13 10:00:24 PM The following virtual machines do not have VMware Tools installed: 'MAIL'. Snapshots of these virtual machines may be inconsistent and source file exclusion is not supported.
Additional info:
--------------------
Error code: 32861
Module: 114
LineInfo: 28314c961de7d314
Fields:
Message: The following virtual machines do not have VMware Tools installed: 'MAIL'. Snapshots of these virtual machines may be inconsistent and source file exclusion is not supported.
--------------------
10 Information 2/23/13 10:00:25 PM Successfully connected to 'VMware vCenter Server 4.1.0 build-799345'.
11 Information 2/23/13 10:00:26 PM Successfully connected to 'VMware ESX 4.1.0 build-988178' through VMware vCenter Server.
12 Information 2/23/13 10:01:00 PM Creating snapshot (2/23/13 10:00:50 PM).
13 Information 2/23/13 10:01:03 PM Load virtual machine 'vm://86E16424-D25B-4E0D-AB44-B3544AC9B64A/52530554-5743-7cc8-3cd0-cb8164da8dce?host=host-1541&type=vmwesx' into the disk subsystem.
14 Information 2/23/13 10:01:04 PM Adding virtual hard disk '[vm2-sas] MAIL/MAIL.vmdk' to '1:1'.
15 Information 2/23/13 10:01:26 PM Adding virtual hard disk '[vm2-sas] MAIL/MAIL_1.vmdk' to '1:2'.
16 Information 2/23/13 10:01:46 PM Analyzing partition 'C:'...
17 Information 2/23/13 10:01:46 PM Analyzing partition 'D:'...
18 Information 2/23/13 10:01:48 PM Preparing for the Microsoft Exchange database validation.
19 Information 2/23/13 10:04:13 PM Detaching hard disk 'SCSI1:2'.
20 Information 2/23/13 10:04:21 PM Detaching hard disk 'SCSI1:1'.
21 Information 2/23/13 10:04:28 PM Remove snapshot (snapshot-8192).
22 Information 2/23/13 10:04:29 PM Task 'MAIL' changed its state from 'running' to 'idle'.
23 Error 2/23/13 10:04:29 PM Task 'MAIL' failed: 'Failed to create a backup.
Additional info:
--------------------
Error code: 3
Module: 435
LineInfo: 555b5abba09501ce
Fields:
Message: Failed to create a backup.
--------------------
Error code: 32786
Module: 114
LineInfo: 28314c961de7d32e
Fields:
Message: Failed to prepare for backing up.
--------------------
Error code: 353
Module: 149
LineInfo: a71592046cb2c5f6
Fields:
Message: Failed to back up the group.
--------------------
Error code: 2
Module: 218
LineInfo: 338a407ad20e0987
Fields:
Message: Error occurred while running the backup and recovery engine.
--------------------
Error code: 368
Module: 149
LineInfo: 4db9605401c15283
Fields:
Message: Failed to prepare for the Microsoft Exchange database validation.
--------------------
Error code: 358
Module: 149
LineInfo: 8e1d384601b2ab4b
Fields:
Message: VSS metadata is missing or corrupt.
--------------------
Error code: 13
Module: 4
LineInfo: 86137b9d60c180c7
Fields:
Message: The file is corrupted.
--------------------'.

I'm going to open a case too because Acronis needs to be aware of these problems.

0 Users found this helpful
frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 22
Comments: 3800

Hi KJSTech,

Concerning the 1st failure - it looks like there were traces left in the virtual appliance from the disks which were attached to it before (for backup purposes). This might happen if for example the default appliance disks (1GB and 2GB) are attached to wrong SCSI slots or something went wrong during the upgrade of the vSphere (i.e. something happened to the state of the virtual appliance). Typically such problems are resolved by rebooting the virtual appliance in order to get rid of the traces.

The Exchange-aware backup failure should be investigated by following the steps from http://kb.acronis.com/content/31347

Thank you.
--
Best regards,
Vasily
Acronis vmProtect Program Manager

Well all the backups last night ran properly. During the day I just went into each job and 'touched it' by just looking at it and clicking save. Its like that "reset" the job or something because now they all completed.

Even the mail server completed, ran from 18:03:50 to 19:20:15.

So it seems every once in awhile you just have to 'touch' the jobs. Maybe we could come up with a script that does that behind the scenes in a future version?

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 22
Comments: 3800

Hi KJSTech,

Even though the jobs went fine over night it would still be worthy to investigate what happened. The editing and saving the jobs should not have affected the results actually. There is more likely some Linux modules (the base OS of vmProtect appliance) state which has changed. As mentioned in
http://forum.acronis.com/forum/40299 we will investigate this case and figure out what went wrong.

Thank you.
--
Best regards,
Vasily
Acronis vmProtect Program Manager