FULLVM backup instead of INCR after VMware Storage Vmotion

Technote (troubleshooting)


Problem(Abstract)

After a VMware Storage VMotion of a virtual machine, a Tivoli Storage Manager FULLVM backup is done instead of an INCREMENTAL.

Symptom

ANS9385W Error returned from VMware vStorage API for
virtual machine 'VM1' in vSphere API function __ns2__QueryChangedDiskAreas. RC=12, Detail message: SOAP 1.1 fault: "":ServerFaultCode[no subcode] "Error caused by file
/vmfs/volumes/5101ffa1-9221d4d9-1986-0010186b18f0/VM1/VM1.vmdk"


Environment

Windows or Linux VStorage backup server.

Resolving the problem

This problem has been shown to be caused by a known VMware problem that is being investigated.

http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&externalId=2035976

INCREMENTAL VM backups should continue after the FULLVM backup.

Product Alias/Synonym

TSM

Rate this page:

(0 users)Average rating

Document information


More support for:

Tivoli Storage Manager for Virtual Environments
Data Protection for VMware

Software version:

6.3, 6.4

Operating system(s):

Linux, Windows

Reference #:

1624296

Modified date:

2014-01-21

Translate my page

Machine Translation

Content navigation