Hi,
We are trying to use TSM BA Client 6.2.2 to do Full VM backups, using the vStorage API.
I have been able to back up a small (4GB) VM OK, but when I try larger VMs (30GB), these fail part way through (e.g. 30% complete), and I see the following error reported in "dsmerror.log":
06/27/2011 17:38:45 ANS9365E VMware vStorage API error.
TSM function name : vddksdkRead
TSM file : vmvddksdk.cpp (2232)
API return code : 1
API error message : Unknown error
06/27/2011 17:38:45 ANS0361I DIAG: ANS1111I VmProcessExtent(): vddksdkRead() rc=-1, startSector=35529216, numSectorsToRead=512
06/27/2011 17:38:49 ANS0238E The sequence of calls is invalid.
06/27/2011 17:38:49 ANS5283E The operation was unsuccessful.
06/27/2011 17:38:49 ANS4047E There is a read error on 'vmxxx'. The file is skipped.
06/27/2011 17:38:49 ANS4148E Full VM backup of Virtual Machine 'vmxxx' failed with RC 152
The VMs concerned are shut down; one was Windows and one was Linux. I have Googled this error and have not found an exact match. I guess there is something about the configuration of our VMs which is causing a problem for TSM, but I don't know what.
Any clues? Thanks.
We are trying to use TSM BA Client 6.2.2 to do Full VM backups, using the vStorage API.
I have been able to back up a small (4GB) VM OK, but when I try larger VMs (30GB), these fail part way through (e.g. 30% complete), and I see the following error reported in "dsmerror.log":
06/27/2011 17:38:45 ANS9365E VMware vStorage API error.
TSM function name : vddksdkRead
TSM file : vmvddksdk.cpp (2232)
API return code : 1
API error message : Unknown error
06/27/2011 17:38:45 ANS0361I DIAG: ANS1111I VmProcessExtent(): vddksdkRead() rc=-1, startSector=35529216, numSectorsToRead=512
06/27/2011 17:38:49 ANS0238E The sequence of calls is invalid.
06/27/2011 17:38:49 ANS5283E The operation was unsuccessful.
06/27/2011 17:38:49 ANS4047E There is a read error on 'vmxxx'. The file is skipped.
06/27/2011 17:38:49 ANS4148E Full VM backup of Virtual Machine 'vmxxx' failed with RC 152
The VMs concerned are shut down; one was Windows and one was Linux. I have Googled this error and have not found an exact match. I guess there is something about the configuration of our VMs which is causing a problem for TSM, but I don't know what.
Any clues? Thanks.