Hi Del!
Ok... Hm... I don't think our SQL guys will be very charmed by the work around
(ignoring the error)... And I can't blame them. To my opinion these kind of
bugs should not be fixed in a new (maintenance) release but it should be fixed
through an immediately available fix release...
However, thank you VERY much for your help!
Kind regards,
Eric van Loon
AF/KLM Storage Engineering
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Del Hoobler
Sent: woensdag 7 mei 2014 16:21
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: TDP for SQL server error
Hi Eric,
Yes... this is APAR IC99653.
http://www-01.ibm.com/support/docview.wss?&uid=swg1IC99653
For now, you can remove the "LOCALDSMAGENTNODE" option and ignore the "red X"
saying it isn't configured.
You can still perform the legacy backup operations.
Del
----------------------------------------------------
"ADSM: Dist Stor Manager" <ADSM-L AT vm.marist DOT edu> wrote on 05/07/2014
09:40:57 AM:
> From: "Loon, EJ van (SPLXM) - KLM" <Eric-van.Loon AT KLM DOT COM>
> To: ADSM-L AT vm.marist DOT edu,
> Date: 05/07/2014 09:41 AM
> Subject: Re: TDP for SQL server error
> Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT vm.marist DOT edu>
>
> Hi Del!
> The tdpsql.cfg file indeed contained the LOCALDSMAGENTNODE entry. As
> soon as he removes this line and starts the TDP GUI the wizard starts
> with the message that the TDP client has not been configured.
> And when he configures it through the wizard the LOCALDSMAGENTNODE
> line is added again... The backup method is set to legacy in the
tdpsql.cfg
> Thank you very much for your help!
> Kind regards,
> Eric van Loon
> AF/KLM Storage Engineering
>
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf
> Of Del Hoobler
> Sent: woensdag 7 mei 2014 14:09
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: TDP for SQL server error
>
> Hi Eric,
>
> No. You should just be able to use legacy style backups.
> My guess is that the configuration wizard inadvertently added some
> entries causing this.
>
> Check the tdpsql.cfg file.
>
> 1. Remove the LOCALDSMAGENTNODE entry (if there is one.)
>
> 2. Make sure the BACKUPMETHOD is:
> BACKUPMETHOD LEGACY
>
>
> Del
>
> ----------------------------------------------------
> "ADSM: Dist Stor Manager" <ADSM-L AT vm.marist DOT edu> wrote on 05/07/2014
> 08:00:45 AM:
>
> > From: "Loon, EJ van (SPLXM) - KLM" <Eric-van.Loon AT KLM DOT COM>
> > To: ADSM-L AT vm.marist DOT edu,
> > Date: 05/07/2014 08:01 AM
> > Subject: Re: TDP for SQL server error Sent by: "ADSM: Dist Stor
> > Manager" <ADSM-L AT vm.marist DOT edu>
> >
> > Hi Remco!
> > Has this changed than? We have been using the (older) TDP client for
> > multiple years but I never had to grant the BA client for TDP clients!
> > Kind regards,
> > Eric van Loon
> > AF/KLM Storage Engineering
> >
> > -----Original Message-----
> > From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On
> > Behalf Of Remco Post
> > Sent: woensdag 7 mei 2014 9:27
> > To: ADSM-L AT VM.MARIST DOT EDU
> > Subject: Re: TDP for SQL server error
> >
> > you need to grant proxy rights to the fs client for the sql client
> > (or
> > vv) for VSS based backups to work, legacy backups work without such
> > proxy rights (and without the error message).
> >
> > Op 7 mei 2014, om 09:05 heeft Loon, EJ van (SPLXM) - KLM <Eric-
> > van.Loon AT KLM DOT COM> het volgende geschreven:
> >
> > > Hi TSMers!
> > > Our SQL department is testing the TDP 6.4.1 client on their SQL
> > Server 2012 servers. Backup and restore is working fine, but they
> > keep
> > on receiving the following error:
> > >
> > > ANS1532E: Proxy Rejected: Proxy authority has not been granted to
> > > this
> node
> > >
> > > Like I said, the restore works, but it's a bit annoying and I
> > don't understand where it's coming from, we do not use a fromnode or
> > something...
> > > Thank you very much for your help in advance!
> > > Kind regards,
> > > Eric van Loon
> ********************************************************
> For information, services and offers, please visit our web site:
> http://www.klm.com. This e-mail and any attachment may contain
> confidential and privileged material intended for the addressee only.
> If you are not the addressee, you are notified that no part of the
> e-mail or any attachment may be disclosed, copied or distributed, and
> that any other action related to this e-mail or attachment is strictly
> prohibited, and may be unlawful. If you have received this e-mail by
> error, please notify the sender immediately by return e-mail, and
> delete this message.
>
> Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/ or
> its employees shall not be liable for the incorrect or incomplete
> transmission of this e-mail or any attachments, nor responsible for
> any delay in receipt.
> Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal
> Dutch Airlines) is registered in Amstelveen, The Netherlands, with
> registered number 33014286
> ********************************************************
>
>
********************************************************
For information, services and offers, please visit our web site:
http://www.klm.com. This e-mail and any attachment may contain confidential and
privileged material intended for the addressee only. If you are not the
addressee, you are notified that no part of the e-mail or any attachment may be
disclosed, copied or distributed, and that any other action related to this
e-mail or attachment is strictly prohibited, and may be unlawful. If you have
received this e-mail by error, please notify the sender immediately by return
e-mail, and delete this message.
Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its
employees shall not be liable for the incorrect or incomplete transmission of
this e-mail or any attachments, nor responsible for any delay in receipt.
Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch
Airlines) is registered in Amstelveen, The Netherlands, with registered number
33014286
********************************************************
|
