ADSM-L

Re: [ADSM-L] Strange TSM for VE error

2016-06-02 10:04:01
Subject: Re: [ADSM-L] Strange TSM for VE error
From: "Ryder, Michael S" <michael_s.ryder AT ROCHE DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Thu, 2 Jun 2016 10:01:43 -0400
Tom:

I had an extremely similar problem, with this same string in my errors --
"ReconfigVM_USCORETask"

This is the article I read that helped me to solve my problem.

In short... vCenter permissions.

http://www-01.ibm.com/support/docview.wss?uid=swg21497028

Good Luck

Best regards,

Mike Ryder
RMD IT Client Services

On Thu, Jun 2, 2016 at 9:04 AM, Rick Adamson <RickAdamson AT segrocers DOT com>
wrote:

> Tom,
> I think you need to look for the cause in either vCenter or Veeam.
> The message *"The method is disabled by XXXXXXX" refers to vCenter
> blocking backup tasks via the API, and vShield_SVM is specific to Veeam.
>
> There are known issues where a task such as vMotion runs, which sets a
> flag in vCenter so other tasks don't cause conflicts, then when the vMotion
> task finishes the flag does not get removed properly. The result is other
> backup jobs are not able to run.
>
> Referencing these VMware and Veeam threads will help understand:
>
> https://forums.veeam.com/vmware-vsphere-f24/storage-vmotion-fails-t10000.html
>
>
> https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2008957
>
> I know this doesn't provide you with a direct resolution, but hopefully
> will get you going down the right path.
>
> Again, I would start with taking a look at vCenter and Veeam for
> additional information.
>
> Hope this helps.
> Let us know what you find.
>
> -Rick Adamson
>
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf 
> Of
> Tom Alverson
> Sent: Wednesday, June 01, 2016 6:49 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: [ADSM-L] Strange TSM for VE error
>
> 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.
>