Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

VMDK のサイズが原因で vSphere Data Protection のバックアップに失敗する (51769)

Last Updated: 11/30/2017Categories: TroubleshootingTotal Views: 1Language:
JapaneseEnglish

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

免責事項：これは英文の記事「vSphere Data Protection backup fails due to VMDK size」の日本語訳です。記事はベストエフォートで翻訳を進めているため、ローカライズ化コンテンツは最新情報ではない可能性があります。最新情報は英語版の記事で参照してください。

Purpose

vSphere Data Protection のバックアップが失敗する

バックアップ ログに、次のようなエントリが記録される。

avvcbimage Error <0000>: [IMG0010] PAX stream append ([datastore] VM_disk_2.vmdk) at sector offset 128 length 128 sectors=65536 failed (32)
avvcbimage Info <9772>: Starting graceful (staged) termination, PAX stream append failed (wrap-up stage)
avvcbimage Info <6688>: Process 7060 (/usr/local/avamarclient/bin/avtar) finished (code 176: fatal signal)
avvcbimage Warning <6690>: CTL workorder "VAULT_Backup-1478606035772" non-zero exit status 'code 176: fatal signal'
avvcbimage Info <40654>: isExitOK()=157
avvcbimage Info <16022>: Cancel detected(miscellaneous error), isExitOK(0).
avvcbimage Info <9746>: bytes submitted was 65536
avvcbimage Error <0000>: [IMG0010] pax_container::endfile(virtdisk-flat.vmdk,65536) returned problem:32
avvcbimage Error <0000>: [IMG0010] pax_container::enddir returned problem:32
avvcbimage Info <40654>: isExitOK()=157
avvcbimage Info <16022>: Cancel detected(miscellaneous error), isExitOK(0).
avvcbimage Info <12032>: backup ([datastore] VM_disk_2.vmdk) terminated 2516582.40 MB
avvcbimage Info <40654>: isExitOK()=157
avvcbimage Error <0000>: [IMG1003] Backup of [datastore] VM_disk_2.vmdk failed
avvcbimage Error <0000>: [IMG0011] Avtar exited with 'code 176: fatal signal'

注：前述のログの引用は単なる例です。日付、時間、および環境変数は、環境によって異なる場合があります。

Cause

この問題は、仮想マシンのいずれかのディスク（VMDK フラット ファイル）のサイズが原因で発生します。ディスクのサイズは、小数点以下の数値のない整数にする必要があります。
例：
ディスクのサイズは 2516583 MB のような整数とし、2516582.40 MB のような整数を使用することはできません。
このエラーは、VDP が仮想マシン上で変更ブロックのトラッキング (CBT) 情報を更新し、ディスクのサイズが 1 MB の倍数ではない場合に発生します。

Resolution

この問題を解決するには、MB 単位のディスクのサイズを整数に変更します。
注：サイズを縮小することはできず、増やすことしかできません。
Web Client を使用して MB 単位のディスクのサイズを整数に変更するには、次の手順を実行します。

インベントリで仮想マシンを右クリックして、[設定の編集] をクリックします。

[仮想ハードウェア] タブで、[ハード ディスク] を展開してディスク オプションを表示します。

[プロビジョニング済みサイズ] テキストボクスに新しい値を入力し、単位に [MB] を選択して、値が MB の整数であることを確認します。

[OK] をクリックします。

注：2 TB を超えるディスクはホット拡張できないため、最初に仮想マシンをシャットダウンする必要があります。

関連する情報

VMware vSphere 6.0 Documentation Center - Change the Virtual Disk Configuration

Increasing the size of a virtual disk (1004047)

Support for virtual machine disks larger than 2 TB in VMware ESXi 5.5 (2058287)

Related Information

vSphere Data Protection backup fails due to VMDK size

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
JapaneseEnglish

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere Data Protection

VMware vSphere

Related Versions:

VMware vSphere Data Protection 6.1.x

Support Assistant