ADSM-L

[ADSM-L] Strange TSM for VE error

2016-06-01 18:49:58
Subject: [ADSM-L] Strange TSM for VE error
From: Tom Alverson <tom.alverson AT GMAIL DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Wed, 1 Jun 2016 18:48:30 -0400
I am running TSM for VE  7.1.4.1 on WIndows 2008 and it has been OK until
about 2 weeks ago.  Since then every night the backup job (should be over
100 VM's) just kind of aborts without logging success or failure.  The only
errors in the logs are these (which don't appear in any Google searches)




*06/01/2016 18:15:51 ANS2345W The virtual machine named 'server1
(2cc5bac1-e96f-4b08-ac8b-a7f36f27e6cd)-0' was found to have an old snapshot
'TSM-VM Snapshot Wed Jun 01 18:02:40 2016'. A command was sent to the
vCenter to remove it.*

*06/01/2016 18:16:05 ANS9387W An incremental backup for virtual machine
'server1 (2cc5bac1-e96f-4b08-ac8b-a7f36f27e6cd)-0' is not possible because
changed block information cannot be obtained. A full VM backup is attempted
instead.*

*06/01/2016 18:16:14 ANS9365E VMware vStorage API error for virtual machine
'server1 (2cc5bac1-e96f-4b08-ac8b-a7f36f27e6cd)-0'.*

*   TSM function name : ReconfigVM_USCORETask*

*   TSM file          : ..\..\common\vm\vmvisdk.cpp (6897)*

*   API return code   : 12*

*   API error message : SOAP 1.1 fault: "":ServerFaultCode[no subcode]*

*"The method is disabled by 'vShield_SVM'"*

*Detail:*



*06/01/2016 18:28:12 ANS2345W The virtual machine named 'server2
(17a6690f-9e77-4066-ba92-bcb947aa2216)' was found to have an old snapshot
'TSM-VM Snapshot Wed Jun 01 18:15:43 2016'. A command was sent to the
vCenter to remove it.*

*06/01/2016 18:28:19 ANS9365E VMware vStorage API error for virtual machine
'server1 (2cc5bac1-e96f-4b08-ac8b-a7f36f27e6cd)-0'.*

*   TSM function name : ReconfigVM_USCORETask*

*   TSM file          : ..\..\common\vm\vmvisdk.cpp (6897)*

*   API return code   : 12*

*   API error message : SOAP 1.1 fault: "":ServerFaultCode[no subcode]*

*"The method is disabled by 'vShield_SVM'"*

*Detail:*




Of course there is no detail.  I have asked our Vcenter people if they have
made any changes but the odd thing is I have several other VBS servers
talking to this vcenter and they are not having this problem.  The only
change (made to all the VBS servers) recently was last month's Microsoft
patches.