ADSM-L
[Top] [All Lists]
<prev [Date] next>
[Advanced]
 <prev [Thread] next>

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

2016-06-03 12:56:55
Subject: Re: [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: Fri, 3 Jun 2016 12:55:23 -0400 
Correct.  Nothing at all in the error log now.  The scheduler log just
shows the backup activity of the first backup then after a few minute gap
the scheduler is restarted by the CAD (since it had terminated
unexpectedly) and tries again until the 1 hour window is up.

That was before clearing out c:\windows\temp.  It has been running for
about 2 hours now without crashing.

On Fri, Jun 3, 2016 at 12:19 PM, David Ehresman <
david.ehresman AT louisville DOT edu> wrote:

> Tom,
>
> I'm asking the obvious, but are you saying there are no entries in the
> dsmerror.log in the baclient folder of the datamover?
>
> David
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf 
> Of
> Tom Alverson
> Sent: Friday, June 03, 2016 11:55 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: [ADSM-L] Strange TSM for VE error
>
> Thanks for that info.  Unfortunately once I forced the exclusion of that
> one server it just crashes on the next server with no errors.  I just
> deleted all of the files in c:\windows\temp (it had thousands of leftover
> TSM for VE temp files in there) and not it has kept going after the first
> server (has not crashed yet) - so maybe the problem was all the files in
> the temp folder.  I won't know for a few  hours.
>
> The only error that is getting logged is windows saying "that service has
> terminated unexpectedly".
>
> On Thu, Jun 2, 2016 at 6:36 PM, Gee, Norman <Norman.Gee AT lc.ca DOT gov> 
> wrote:
>
> > At one point I had exclusion with wildcards in the VM names and all of
> the
> > sudden that
> > stop working after the TDP got updated. My exclusion list now list all of
> > the exact VM
> > names.
> >
> > -----Original Message-----
> > From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On 
> > Behalf Of
> > Tom Alverson
> > Sent: Thursday, June 02, 2016 2:18 PM
> > To: ADSM-L AT VM.MARIST DOT EDU
> > Subject: Re: Strange TSM for VE error
> >
> > OK this is getting weirder and weirder -  the server that was generating
> > the vShield_SVM error was a vshield server that our vmware guys said
> should
> > not be backed up.  The options were set (by an exclusion option) to skip
> > all of the server names that are used for vShield - except the exclusion
> > was not working.  I finally excluded the full specific server name and
> now
> > it goes on to the next server and the scheduler process just quits right
> in
> > the middle of the backup with absolutely no logging of any errors now.
> It
> > did this with TSM for VE 7.1.4.0 and did not change when I put 7.1.4.1 on
> > the VBS server.  I guess the next step is an IBM ticket as I have no clue
> > at this point.  I even excluded the next server it was working on and it
> > just started on the server after that and bombs (with no errors logged).
> > Once it bombs, the scheduler tries again once or twice during the hour
> but
> > the same thing happens each time.
> >
> > Tom
> >
> > On Thu, Jun 2, 2016 at 10:01 AM, Ryder, Michael S <
> > michael_s.ryder AT roche DOT com
> > > wrote:
> >
> > > 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.
> > >
> > >
> https://urldefense.proofpoint.com/v2/url?u=http-3A__www-2D01.ibm.com_support_docview.wss-3Fuid-3Dswg21497028&d=AwIBaQ&c=SgMrq23dbjbGX6e0ZsSHgEZX6A4IAf1SO3AJ2bNrHlk&r=dOGCMY197NTNH1k_wcsrWS3_fxedKW4rpKJ8cHCD2L8&m=l75yczRhK70sB66A2IMMgB-wBs7JyoTRM5qk_FDoXZM&s=h0cYKTE-9lFoY8-a-GjieFJsQBLsyPJI_KaF1fDH1Us&e=
> > >
> > > 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://urldefense.proofpoint.com/v2/url?u=https-3A__forums.veeam.com_vmware-2Dvsphere-2Df24_storage-2Dvmotion-2Dfails-2Dt10000.html&d=AwIBaQ&c=SgMrq23dbjbGX6e0ZsSHgEZX6A4IAf1SO3AJ2bNrHlk&r=dOGCMY197NTNH1k_wcsrWS3_fxedKW4rpKJ8cHCD2L8&m=l75yczRhK70sB66A2IMMgB-wBs7JyoTRM5qk_FDoXZM&s=JTp0X50GwXqd3Iq_PlTS7HGb-GycXV2UG4wD9n4dGnE&e=
> > > >
> > > >
> > > >
> > >
> >
> https://urldefense.proofpoint.com/v2/url?u=https-3A__kb.vmware.com_selfservice_microsites_search.do-3Flanguage-3Den-5FUS-26cmd-3DdisplayKC-26externalId-3D2008957&d=AwIBaQ&c=SgMrq23dbjbGX6e0ZsSHgEZX6A4IAf1SO3AJ2bNrHlk&r=dOGCMY197NTNH1k_wcsrWS3_fxedKW4rpKJ8cHCD2L8&m=l75yczRhK70sB66A2IMMgB-wBs7JyoTRM5qk_FDoXZM&s=3UtZbOWCKpcDBNSrAL4lHPs5HLDKBoPV60VsBCnQ6Aw&e=
> > > >
> > > > 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.
> > > >
> > >
> >
>
[More with this subject...]
<Prev in Thread] Current Thread [Next in Thread>
Previous by Date:  Re: [ADSM-L] Strange TSM for VE error, David Ehresman
Next by Date:  Re: [ADSM-L] removing offsite data for a particular node, Thomas Denier
Previous by Thread:  Re: [ADSM-L] Strange TSM for VE error, David Ehresman
Next by Thread:  Re: [ADSM-L] Strange TSM for VE error, Tom Alverson
Indexes:  [Date] [Thread] [Top] [All Lists]