Highlighted
mobe_chang
2 Iron

Avamar+DD2500 備份VMDK失敗

转到解答

Dear all:

最近在備份某一台虛擬主機時,總是出現以下錯誤,其他虛擬主機備份皆正常,就這台會出現這樣的情況,

這台主機所在的Datastore也都正常,空間也足夠。

再請各位先進協助看看是甚麼問題~

.......

2015-05-16 06:36:39 avvcbimage Info <16001>: Found 1 disk(s), 0 snapshots, and 1 snapshot files, on the VMs datastore.

2015-05-16 06:36:39 avvcbimage Warning <18652>: Too many extra snapshot files (1) were found on this Windows VMs datastore. This can cause a problem for the backup or restore.

2015-05-16 06:36:39 avvcbimage Info <18678>: Extracted XXX_AP-flat.vmdk base disk from the VMX file

2015-05-16 06:36:39 avvcbimage FATAL <0000>: [IMG0002] The datastore information from VMX '[XXX] XXX...

2015-05-16 06:36:39 avvcbimage Error <0000>: [IMG0009] createSnapshot: snapshot creation failed
2015-...

........


非常感謝

标签 (2)
标记 (2)
0 项奖励
4 条回复4
版主
版主

Re: Avamar+DD2500 備份VMDK失敗

转到解答

Hi Mobe,

这是一个已知的问题,这里有个KB解释了如何解决此问题。

KB地址: https://emc--c.na5.visual.force.com/apex/KB_BreakFix_1?id=kA1700000000W9w

0 项奖励
版主
版主

Re: Avamar+DD2500 備份VMDK失敗

转到解答

Mobe,

担心你打不开链接,我直接把内容贴了出来,你可以看一下下面的内容。

VMWare Image Backups Fail (Code 10056) >> avvcbimage Error <9759>: createSnapshot: Snapshot creation failed

Unable to perform VMware client Image backups and they are failing with Code 10056.

The Snapshot create task fails with the following errors:

Issue #1

avvcbimage Warning <16002>: Too many extra snapshot files (3) were found on the VMs datastore. This can cause a problem for the backup or restore.

avvcbimage FATAL <16018>: The datastore information from VMX '[MLUN] Datastore/TestMachine.vmx' will not permit a restore or backup.

avvcbimage Info <0000>: Starting graceful (staged) termination, Too many pre-existing snapshots on the datastore will not permit a restore or backup. (wrap-up stage)

avvcbimage Error <9759>: createSnapshot: snapshot creation failed

The log shows Avamar did not detect there is Snapshot for this VM initially:

avvcbimage Info <14664>: no snapshots are present on this VM.

However, there are Snapshot files on the Datastore:

2013-01-31 23:37:54 avvcbimage Info <14677>: All VM file Info:
File:'CCHA-00SV0D0SAN-000003-ctk.vmdk                   ' last modified on '07-Dec-2011 15:58'  size=3932672
File:'CCHA-00SV0D0SAN-000003-delta.vmdk                 ' last modified on '07-Dec-2011 15:57'  size=134344704
File:'CCHA-00SV0D0SAN-000003.vmdk                       ' last modified on '07-Dec-2011 15:55'  size=408

Issue #2 The vm has too many existing snapshots (30 or more)

2015-02-20 13:47:23 avvcbimage Info <14665>: 30 snapshots are present on this VM:
   level=1, children=1, ref='snapshot-4223', 'snapshot1':desc='na'
   ...
     *level=30, children=0, ref='snapshot-4252', 'snapshot30':desc='na
​2015-02-20 13:47:23 avvcbimage FATAL <0000>: [IMG0019] The pre-existing snapshots from VMX '[MLUN] Datastore/TestMachine.vmx does not permit a backup.

EMC Software: Avamar 6.1 - 7.1
System: VMWare

For issue #1
If there are Snapshot files in the Virtual Machine directory and vCenter reported less then was discovered by the scan then the backup fails.

When Avamar attempts to backup a Virtual Machine, it must take a snapshot. Before performing it queries vCenter for how many snapshots the Virtual Machine currently contains. Then the Datastore directory is scanned where the Virtual Machine resides.

For Issue #2
VMware ESI will only permit up to 32 before the Snapshot task fails with: Create Virtual Machine Sapshot task fails with a VMware error of: "Snapshot hierarchy is too deep". As described above we need to take a new "Avamar" snapshot (bring Snapshot count to 31). And the end of the backup we need to delete this Snapshot. This delete action causes ESX to create a hidden esx Snapshot called consolidated helper (snapshot count would be 32) and could fail due to the ESX "Snapshot hierarchy is too deep" issue. For this reason the Avamar proxy code will NOT allow Snapshots of a VM that has existing 30 snapshots.

For Issue #1
Snapshot files must be removed from the Virtual Machines Datastore Directory.

Before removing the files there are some checks that must be completed.

  1. Ensure the Virtual Machines are not currently using the snapshot file in question.
  • This can be done by looking into the virtual machines Settings > Hardware tab > select each disk and make sure the "Disk file" is not allocated to a Snapshot file. (Snapshots will have a suffix named of <vm name>-00000#.vmdk
  1. Make sure the Avamar proxies does not have the disk attached to them.
  • In vCenter select a proxy and navigate to the Settings > Hardware tab
  • Each proxy should have two disks, any additional should be removed
  • To remove an extra disk, select the disk and click "Remove" and leave the "Removal Options" selection to "Remove from Virtual Machine"
  • This may be done by EMC TSE Using Proxycp utility using the "--listproxydisk --cleanup" options.
  1. Run a Snapshot Consolidation (ESX / vCenter 5.x and above)
  • In vCenter navigate to the Virtual Machine, then in the tool bar  select > Inventory > Virtual Machine > Snapshot > Consolidate
  • For vCenter 4.x you may take a snapshot of the Virtual Machine, Then go back to Snapshot Manager and select "Delete All" (Warning: This deletes all Snapshot even if they are user created, make sure you do not mind losing your current valid snapshots)
  • Manually remove the Snapshots if the Consolidate does not work - Do not perform this if there are other valid user Snapshots Or if the VM disks are currently using any Snapshot file.
    • Navigate to the Datastore directory of the Virtual Machine
    • Create a new Folder in the VM Directory Called "SS Removal"
    • Drag and drop the offending snapshot files into the new directory created above.
  1. Inspect the Datastore directory for the Virtual Machine in question and verify the Snapshot files still exist.
  2. One removed perform a backup.
  3. If the issue is not resolved please contact EMC Technical Support.

For Issue #2. 
In VMware, delete the existing Snapshot. VMware does not recommend using Snapshots as your only  backup strategy (For example: use product like Avamar ). Have more than a small set of short term Snapshots that introduces latency and high stun times during Snapshot operations.Ideally a VM should not have Snapshot.

0 项奖励
mobe_chang
2 Iron

Re: Avamar+DD2500 備份VMDK失敗

转到解答

Hi leo:

太感謝您的貼心了,目前已參照說明修正。

非常感謝

0 项奖励
版主
版主

Re: Avamar+DD2500 備份VMDK失敗

转到解答

不客气 Mobe。

0 项奖励