Re: Admin session refused on each new client

[Krzysztof Przygoda]

Hi Eric
Try setting admin schedule running every few minutes "update admin *
sessionsecurity=transitional". Silly, but works...
ps.
For me IBM attitude for handling this issue is kind of silly. Especially
that this sessionsecurity=strict is also pushed to all managed accounts
which you, on your own, cannot update without deleting enterprise
subscription.

Kind Regards
Krzysztof

2018-02-20 17:17 GMT+01:00 Loon, Eric van (ITOPT3) - KLM <
eric-van.l...@klm.com>:

> Hi guys!
> We have always used a script to install the TSM client code on new Linux
> clients. Since the server was upgraded to 7.1.8 (and thus are suffering
> from the new security features) the script fails. The admin session which
> is supposed to define the new node on the TSM server is rejected with the
> message "ANR0404W Session 66 for administrator ADMIN (Linux x86-64) refused
> - client is down-level with this server version.". This can be fixed once
> by a upd admin ADMIN sessionsecurity=transitional at which point the
> certificate is exchanged and the session is working again. But because the
> sessionsecurity is immediately set to strict afterwards by TSM, the next
> time the script is run on a different client, it fails again.
> Has anybody been able to find some work-around for this?
> Kind regards,
> Eric van Loon
> Air France/KLM Storage Engineering
>
> 
> 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
> 
>

Re: Admin session refused on each new client

[Jansen, Jonas]

Hi Eric,
I think you should use the new dsmcert tool to add the server certificate to 
the client trusted certificate store. May bee you can add this step to your 
script.
Best regards,
Jonas Jansen

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Loon, 
Eric van (ITOPT3) - KLM
Sent: Tuesday, February 20, 2018 5:18 PM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] Admin session refused on each new client

Hi guys!
We have always used a script to install the TSM client code on new Linux 
clients. Since the server was upgraded to 7.1.8 (and thus are suffering from 
the new security features) the script fails. The admin session which is 
supposed to define the new node on the TSM server is rejected with the message 
"ANR0404W Session 66 for administrator ADMIN (Linux x86-64) refused - client is 
down-level with this server version.". This can be fixed once by a upd admin 
ADMIN sessionsecurity=transitional at which point the certificate is exchanged 
and the session is working again. But because the sessionsecurity is 
immediately set to strict afterwards by TSM, the next time the script is run on 
a different client, it fails again.
Has anybody been able to find some work-around for this?
Kind regards,
Eric van Loon
Air France/KLM Storage Engineering


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

Admin session refused on each new client

[Loon, Eric van (ITOPT3) - KLM]

Hi guys!
We have always used a script to install the TSM client code on new Linux 
clients. Since the server was upgraded to 7.1.8 (and thus are suffering from 
the new security features) the script fails. The admin session which is 
supposed to define the new node on the TSM server is rejected with the message 
"ANR0404W Session 66 for administrator ADMIN (Linux x86-64) refused - client is 
down-level with this server version.". This can be fixed once by a upd admin 
ADMIN sessionsecurity=transitional at which point the certificate is exchanged 
and the session is working again. But because the sessionsecurity is 
immediately set to strict afterwards by TSM, the next time the script is run on 
a different client, it fails again.
Has anybody been able to find some work-around for this?
Kind regards,
Eric van Loon
Air France/KLM Storage Engineering


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

Re: Don't upgrade TSM client to 7.1.8 on a 6.3 server!

[Erwann SIMON]

Hi Eric,

The same wil happen for every server, on any platform, for version under 
7.1.7.300 if you install a 7.1.8 or 8.1.2 client.

Look at this :
"Interim fix 7.1.7.300 was released to provide compatibility with a future 
release of the Global Security Kit (GSKit)."
No other APAR fixed with this Interim Fix
http://www-01.ibm.com/support/docview.wss?uid=swg21995379

-- 
Best regards / Cordialement / مع تحياتي
Erwann SIMON

- Mail original -
De: "Eric van Loon (ITOPT3) - KLM" 
À: ADSM-L@VM.MARIST.EDU
Envoyé: Mardi 20 Février 2018 14:29:21
Objet: [ADSM-L] Don't upgrade TSM client to 7.1.8 on a 6.3 server!

Hi guys,
I just found out the hard way and I would like to share this knowledge before 
anyone else running this (unsupported) server level runs into the same issue: 
do NOT upgrade the TSM client to 7.1.8 on a 6.3 server. This client contains a 
GSKit version (8.0.50.78) which is not compatible with the 6.3 server. As soon 
as you upgrade the client, you will not be able to back up the TSM database 
(ANR4588E A database backup configuration might be incorrect) and as soon as 
you stop your server, you won't be able to start it anymore (ANR1820E The 
server could not connect to the database manager by using TCP/IP port). After 
downgrading to the GSKit that comes with the 7.1.6.x clients (8.0.50.66) 
everything is working again.
So, now it's logged on the internet. :)
Kind regards,
Eric van Loon
Air France/KLM Storage Engineering

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

Re: Exchange backup speed

[Storer, Raymond]

Tom,

I don't have a large on-premises Exchange environment.  I perform full backups 
daily and log backups hourly.  Things you could test to improve speed:
- test RESOURCEUTILIZATION option in dsm.opt to at least 5 (10 is max, I think) 
to see how it performs in your environment and adjust up or down as needed
- test dsm.opt settings TCPBUFFSIZE to 512, TCPWINDOWSIZE to 63, and 
TXNBYTELIMIT to 25600 and modify them to see what works best in your environment

You could test turning off error checking for the exchange backups.  If you do, 
I strongly recommend testing a restore "occasionally".
You don't need PowerShell to automate your Exchange backups.  You can, as it 
appears you already have, use batch files and tdpexcc.exe to do your backups.  
As someone else already pointed out, VSS will abort multiple simultaneous 
backups; so, stagger them by at least ten minutes (+/-)--it really depends on 
how long it takes for Windows to complete the snapshot in your environment.

Good luck!

Ray
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Tom 
Alverson
Sent: Friday, February 16, 2018 6:56 PM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] Exchange backup speed

>
>
> We are trying to speed up our Exchange backups that are currently only
using about 15% of the network bandwidth.  Our servers are running Windows
2012R2 and Exchange 2013 CU15 with TSM 7.1.0.1 and TDPEXC 7.1.0.1.
Currently we are backing up 15 DAGS per Exchange server (we have multiple 
exchange servers) and we are only backing up on servers that are standby 
replicas.  Currently we are trying a 14 day schedule were we do a full backup 
of a different DAG per day, and incrementals on the rest.  Even doing this we 
are having trouble completing them in 24 hours (before the next day's backup is 
supposed to start).

I saw an old posting from Del saying to increase RESOURCEUTILIZATION on the 
DSMAGENT.  Does that mean the DSM.OPT in the BACLIENT folder?  It was set at 2. 
 Do either the buffers or buffrsize options make any difference?

Also if we want to "parallelize" the backups does that mean separate scheduler 
services for each one?  We currently use 14 different batch files (for the 14 
days of the cycle) with something like this:

[day1.bat]

tdpexcc.exe backup dag1 full
tdpexcc.exe backup dag2,dag3,dag4,dag5 incr tdpexcc.exe backup 
dag6,dag7,dag8,dag9 incr tdpexcc.exe backup dag10,dag11,dag12,dag13 incr 
tcpexcc.exe backup dag14,dag15 incr exit



CONFIDENTIALITY NOTICE: This email and any attachments are for the
exclusive and confidential use of the intended recipient. If you are not
the intended recipient, please do not read, distribute or take action in
reliance upon this message. If you have received this in error, please
notify us immediately by return email and promptly delete this message
and its attachments from your computer system. We do not waive
attorney-client or work product privilege by the transmission of this
message.

Don't upgrade TSM client to 7.1.8 on a 6.3 server!

[Loon, Eric van (ITOPT3) - KLM]

Hi guys,
I just found out the hard way and I would like to share this knowledge before 
anyone else running this (unsupported) server level runs into the same issue: 
do NOT upgrade the TSM client to 7.1.8 on a 6.3 server. This client contains a 
GSKit version (8.0.50.78) which is not compatible with the 6.3 server. As soon 
as you upgrade the client, you will not be able to back up the TSM database 
(ANR4588E A database backup configuration might be incorrect) and as soon as 
you stop your server, you won't be able to start it anymore (ANR1820E The 
server could not connect to the database manager by using TCP/IP port). After 
downgrading to the GSKit that comes with the 7.1.6.x clients (8.0.50.66) 
everything is working again.
So, now it's logged on the internet. :)
Kind regards,
Eric van Loon
Air France/KLM Storage Engineering

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

Antwort: Re: TSMVE 8.1.4 installation over webgui, we do not know any of the node passwords now

[Tsm Tsm]

HelloJonas,

seems to be the solution

thank you very much

with best regards
stefan savoric

Re: Command to only backup and clear archive logs

[Hans Christian Riksheim]

Hi,

it takes  1,5 hours for 1,3 TB of database if everything is OK.. Two
streams to tape.  Problem is sometimes that is too long time if the
dbbackup is triggered when the log is 80(?) percent and something is going
on which creates lot of archivelogs. Like reorganization.. I think it was
more convenient with TSM version 5 where "backup incremental" would clear
the log in no time.

Hans Chr.

On Tue, Feb 20, 2018 at 12:53 AM, Harris, Steven <
steven.har...@btfinancialgroup.com> wrote:

> Hans Chr.
>
> What are you backing your DB up to?  Could you use some flash disk or
> tiered disk storage?  Create a special device class just for this
> situation, backup your database to it, then immediately start your normal
> DB backup.  As soon as the normal backup is complete you can delete the
> fast disk backup and return the space.
>
> Cheers
>
> Steve
>
> Steven Harris
> TSM Admin/Consultant
> Canberra Australia
>
>
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
> Remco Post
> Sent: Tuesday, 20 February 2018 2:11 AM
> To: ADSM-L@VM.MARIST.EDU
> Subject: Re: [ADSM-L] Command to only backup and clear archive logs
>
> you need a bigger archive log, or better backup performance (more recent
> versions of TSM allow you to specify the number of parallel sessions in set
> dbrecovery).
>
> > Op 19 feb. 2018, om 10:22 heeft Hans Christian Riksheim <
> bull...@gmail.com> het volgende geschreven:
> >
> > Does TSM/DB2 have that possibility, like Oracle MSSQL?
> >
> > Problem is when the archivelog filesystem goes full we have to wait
> > for the full dbbackup to be finished before archive logs are backed up
> and cleared.
> > Since we have to disable all sessions and other processes(this
> > generates even more logs) we have several hours of outage each time this
> happens.
> >
> >
> >
> > Hans Chr.
>
> --
>
>  Met vriendelijke groeten/Kind Regards,
>
> Remco Post
> r.p...@plcs.nl
> +31 6 248 21 622
>
> This message and any attachment is confidential and may be privileged or
> otherwise protected from disclosure. You should immediately delete the
> message if you are not the intended recipient. If you have received this
> email by mistake please delete it from your system; you should not copy the
> message or disclose its content to anyone.
>
> This electronic communication may contain general financial product advice
> but should not be relied upon or construed as a recommendation of any
> financial product. The information has been prepared without taking into
> account your objectives, financial situation or needs. You should consider
> the Product Disclosure Statement relating to the financial product and
> consult your financial adviser before making a decision about whether to
> acquire, hold or dispose of a financial product.
>
> For further details on the financial product please go to
> http://www.bt.com.au
>
> Past performance is not a reliable indicator of future performance.
>

Re: TSMVE 8.1.4 installation over webgui, we do not know any of the node passwords now

[Jansen, Jonas]

Hello,

since the datacenter node is only accessed via proxy connections, you can 
simply chance the datacenter node password.

Best regards
Jonas Jansen

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Tsm Tsm
Sent: Tuesday, February 20, 2018 8:44 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] TSMVE 8.1.4 installation over webgui, we do not know any of 
the node passwords now

Hello,

our complete new tsm ve installation for vmware 8.1.4  was configured 
completely over the webgui.

so all nodes, etc are registered from the wizard.

so we do not know any of the passwords of the datamovers or the datacenter node 
at all.
and thats the problem.

how can we change the datacenter node password? for example to get the recovery 
agent work?

with which password are the nodes registered?

with best regards
stefan savoric