Nachtwey
Gesendet: Donnerstag, 23. Dezember 2021 17:43
An: ADSM-L@VM.MARIST.EDU
Betreff: [ADSM-L] Problems installing OC-Patch 8.1.13-100 after 8.1.13 upgrade
==> solved!
Hi all,
OK, I fixed it, before sending the question, but perhaps it's interesting for
anyone:
the "install.sh
Hi all,
OK, I fixed it, before sending the question, but perhaps it's
interesting for anyone:
the "install.sh" script uses "#!/bin/sh" in the beginning, replacing
this line by "#!/bin/bash" makes it work :-)
but why did I run in a this problem?
I just updated my server running the Operation
Sarav
+65 9857 8665
On 24 Sep 2020, at 12:12 AM, Sasa Drnjevic wrote:
Hi Sarav and all,
I forgot to inform you earlier, but I have solved the problem with HUNG
or more precisely EXTREMELY slow replication.
Linux nodees were ALL replicating as before the upgrade, without any
problems.
The main
or the past 3 weeks.
>> Regards
>> Sarav
>> +65 9857 8665
>>>> On 24 Sep 2020, at 12:12 AM, Sasa Drnjevic wrote:
>>>
>>> Hi Sarav and all,
>>>
>>> I forgot to inform you earlier, but I have solved the problem with HUNG
>>>
"ADSM: Dist Stor Manager" wrote on 12/15/2020
> 04:15:55 PM:
>
> > From: Zoltan Forray
> > To: ADSM-L@VM.MARIST.EDU
> > Date: 12/15/2020 04:16 PM
> > Subject: [EXTERNAL] Re: Issues with Spectrum Protect+ reports after
> > upgrade to 10.1.7
> &
04:16 PM
> Subject: [EXTERNAL] Re: Issues with Spectrum Protect+ reports after
> upgrade to 10.1.7
> Sent by: "ADSM: Dist Stor Manager"
>
> >>>1. What report are you trying to open?
> VM Backup History - the same one we can't run if we choose "Failed&qu
. Do you
> want to open it anyway?"
>
> 3. Does clicking "yes" to open the file let you proceed?
>
>
> Del
>
>
>
> "ADSM: Dist Stor Manager" wrote on 12/15/2020
> 08:23:42 AM:
>
> > From: Zol
ssues with Spectrum Protect+ reports after
> upgrade to 10.1.7
> Sent by: "ADSM: Dist Stor Manager"
>
> Just discovered another, possibly related issue. We decided to try the
> reporting option to create/send as Excel XLS but the resultant .xls file
> can't be opened by Ex
st Stor Manager" wrote on 12/14/2020
> 11:35:59 AM:
>
> > From: Zoltan Forray
> > To: ADSM-L@VM.MARIST.EDU
> > Date: 12/14/2020 11:36 AM
> > Subject: [EXTERNAL] Issues with Spectrum Protect+ reports after
> > upgrade to 10.1.7
> > Sent by: "ADSM: Dist Stor
e: 12/14/2020 11:36 AM
> > Subject: [EXTERNAL] Issues with Spectrum Protect+ reports after
> > upgrade to 10.1.7
> > Sent by: "ADSM: Dist Stor Manager"
> >
> > Not sure if this is the right place for SP+ questions but here goes.
> >
> > We had a d
Forray
> To: ADSM-L@VM.MARIST.EDU
> Date: 12/14/2020 11:36 AM
> Subject: [EXTERNAL] Issues with Spectrum Protect+ reports after
> upgrade to 10.1.7
> Sent by: "ADSM: Dist Stor Manager"
>
> Not sure if this is the right place for SP+ questions but here goes.
Not sure if this is the right place for SP+ questions but here goes.
We had a daily scheduled "VM Backups History - Failed Backups" report that
was running fine until everything was upgraded to 10.1.7. Then we noticed
the report started showing nothing eventhough the dashboard showed failed
backu
Drnjevic wrote:
Hi Sarav and all,
I forgot to inform you earlier, but I have solved the problem with HUNG
or more precisely EXTREMELY slow replication.
Linux nodees were ALL replicating as before the upgrade, without any
problems.
The main culprit was Windows Systemstate. Ordinary NTFS filespaces
+65 9857 8665
> On 24 Sep 2020, at 12:12 AM, Sasa Drnjevic wrote:
>
> Hi Sarav and all,
>
> I forgot to inform you earlier, but I have solved the problem with HUNG
> or more precisely EXTREMELY slow replication.
>
> Linux nodees were ALL replicating as before
Hi Sarav and all,
I forgot to inform you earlier, but I have solved the problem with HUNG
or more precisely EXTREMELY slow replication.
Linux nodees were ALL replicating as before the upgrade, without any
problems.
The main culprit was Windows Systemstate. Ordinary NTFS filespaces
replicated
node
> replication was going without any problems from source v8.1.1.000 to
> target v8.1.10.100. Both servers are RHEL 7.8.
>
> So, this morning I took my chances and upgraded my source server to
> v8.1.10.100. The upgrade went fine.
>
> But, replication hangs :-(
>
> I
all.
Last week I have upgraded my target server to v8.1.10.100, and node
replication was going without any problems from source v8.1.1.000 to
target v8.1.10.100. Both servers are RHEL 7.8.
So, this morning I took my chances and upgraded my source server to
v8.1.10.100. The upgrade went fine.
Manager On Behalf Of Saravanan
> Palanisamy
> Sent: maandag 31 augustus 2020 23:10
> To: ADSM-L@VM.MARIST.EDU
> Subject: Re: Replication Hung after upgrade to v8.1.10
>
> Hi Eric
>
> Thanks. I have gone through v8.1.10.100 APAR details but I don’t find my
> issue h
3:10
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Replication Hung after upgrade to v8.1.10
Hi Eric
Thanks. I have gone through v8.1.10.100 APAR details but I don’t find my issue
here. I am still waiting for IBM on my case.
Regards
Sarav
+65 9857 8665
> On 31 Aug 2020, at 3:00 PM, Loon, Eric va
amy
> Sent: donderdag 20 augustus 2020 17:42
> To: ADSM-L@VM.MARIST.EDU
> Subject: Re: Replication Hung after upgrade to v8.1.10
>
> IT33437
>
> Regards
> Sarav
> +65 9857 8665
>
>
>> On 20 Aug 2020, at 11:05 PM, Loon, Eric van (ITOP NS) - KLM
>&g
rdag 20 augustus 2020 17:42
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Replication Hung after upgrade to v8.1.10
IT33437
Regards
Sarav
+65 9857 8665
> On 20 Aug 2020, at 11:05 PM, Loon, Eric van (ITOP NS) - KLM
> wrote:
>
> Hi Sarav,
>
> You stated " There is also one
8.1 server
versions.
Starting after the upgrade to 8.1.10, the checkout command (launched by move
drmedia) now behaves as if we were using a remove=no option : tapes stay in
their storage slots and are not move to the bulk (as they should
The curent workaround is to checkin (search=yes) those tapes
lve it?
>>>
>>> Thank you!
>>>
>>> Regards,
>>>
>>> --
>>> Sasa Drnjevic
>>> www.srce.unizg.hr/en/
>>>
>>>
>>>
>>>
>>>> On 20.8.2020. 16:58, Saravanan Palanisamy wrote:
>
;>
>>> We are still facing intermittent hang and no progress on our case. If it’s
>>> one server then we could say it’s environment issue but 3 different pair
>>> and all are in different countries as well. We are holding upgrade for rest
>>> of countries until fi
d say it’s environment issue but 3 different pair and
>> all are in different countries as well. We are holding upgrade for rest of
>> countries until find out root cause.
>>
>> There is also one more issue on v8.1.10 where server will crash abruptly if
>> you use
nt countries as well. We are holding upgrade for rest of
> countries until find out root cause.
>
> There is also one more issue on v8.1.10 where server will crash abruptly if
> you use directory container. It appears to be known issue and we have got
> efix to address it.
&g
Hi Sarav,
Thanks!
Kind regards,
Eric van Loon
Air France/KLM Storage & Backup
-Original Message-
From: ADSM: Dist Stor Manager On Behalf Of Saravanan
Palanisamy
Sent: donderdag 20 augustus 2020 17:42
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Replication Hung after upgrade to v8.
>
> -Original Message-
> From: ADSM: Dist Stor Manager On Behalf Of Saravanan
> Palanisamy
> Sent: donderdag 20 augustus 2020 16:58
> To: ADSM-L@VM.MARIST.EDU
> Subject: Re: Replication Hung after upgrade to v8.1.10
>
> Thanks Erwann for the update.
>
>
ning this level. Do you have an APAR number?
Kind regards,
Eric van Loon
Air France/KLM Storage & Backup
-Original Message-
From: ADSM: Dist Stor Manager On Behalf Of Saravanan
Palanisamy
Sent: donderdag 20 augustus 2020 16:58
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Replication Hu
Thanks Erwann for the update.
We are still facing intermittent hang and no progress on our case. If it’s one
server then we could say it’s environment issue but 3 different pair and all
are in different countries as well. We are holding upgrade for rest of
countries until find out root cause
00:37:41
Objet: [ADSM-L] Replication Hung after upgrade to v8.1.10
Dear Team
Is there anyone facing intermittent replication hung issue after upgrade to
v8.1.10?
We have upgraded TSM server from 8.1.9.300 to 8.1.10 and replication process is
hung intermittently on all 3 servers. Just want to see
Dear Team
Is there anyone facing intermittent replication hung issue after upgrade to
v8.1.10?
We have upgraded TSM server from 8.1.9.300 to 8.1.10 and replication process is
hung intermittently on all 3 servers. Just want to see whether anyone else
impacted.
Once restart TSM instance then
Has anybody done OS upgrade from Red Hat Enterprise Linux Server release
6.10 (Santiago) to
Red Hat Enterprise Linux Server release 7.7 (Maipo) with Spectrum Protect
8.1.8 ?
If so did you encounter any problem ? How did you resolve it
Thank you
Genet Begashaw
Sent: donderdag 23 januari 2020 19:16
To: ADSM-L@VM.MARIST.EDU
Subject: Re: tdpoconf showenv no longer working after upgrade to 8.1.9.0
Check here:
https://www.ibm.com/support/knowledgecenter/SSER7G_8.1.9/db.common/r_techchg_db_orc.html
Del
"ADSM: Dist Stor Manager" wrote on 01
03:38 AM
> Subject: [EXTERNAL] tdpoconf showenv no longer working after upgradeto
8.1.9.0
> Sent by: "ADSM: Dist Stor Manager"
>
> Hi guys,
>
> We discovered that tdpoconf showenv is no longer working for the
> oracle user after the upgrade to DP for Oracle 8.1.
Hi guys,
We discovered that tdpoconf showenv is no longer working for the oracle user
after the upgrade to DP for Oracle 8.1.9.0. It is working OK for root.
The cause of this issue is the fact that the random encryption key file TSM.sth
is not accessible for the oracle user. I think this file
We are performing lots of upgrade scenarios on a test server to find
compatibility errors/issues.
After upgrading from 7.1.9 to 8.1.2.000, started seeing these errors in the
actlog:
2018-11-05, 08:41:08 ANR0150E Failed to open Node T-ISILON-TS-CONSULTANTS.
There was an error decrypting the Node
On 2018-11-01 18:19, Michaud, Luc [Analyste principal - environnement
AIX] wrote:
> We want to upgrade our AIX-based TSM servers from 7.1.7.000 to
> 8.1.x.yyy
>
> The official IBM server upgrade process does not worry us by itself.
>
> However, on this list, over the last
We want to upgrade our AIX-based TSM servers from 7.1.7.000 to 8.1.x.yyy
The official IBM server upgrade process does not worry us by itself.
However, on this list, over the last year, I did notice issues with
SESSIONSECURITY, Web Client, as well as some regressions.
So, here are my questions
> Date: 2018-10-25 16:57
> Subject: Core Dumps After Upgrade
> Sent by: "ADSM: Dist Stor Manager"
>
> Hi All,
>
> We've recently upgraded all of our servers from 7.1.7.300 to 7.1.7.400.
> Since then we've been getting intermittent core dumps when we r
:57
> Subject: Core Dumps After Upgrade
> Sent by: "ADSM: Dist Stor Manager"
>
> Hi All,
>
> We've recently upgraded all of our servers from 7.1.7.300 to 7.1.7.400.
> Since then we've been getting intermittent core dumps when we restart the
> servers after p
Hi All,
We've recently upgraded all of our servers from 7.1.7.300 to 7.1.7.400.
Since then we've been getting intermittent core dumps when we restart the
servers after patching. A couple times this actually caused TSM not to
start, due the home directory to becoming completely full. All of our
ser
: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
Harris, Steven
Sent: woensdag 7 maart 2018 2:57
To: ADSM-L@VM.MARIST.EDU
Subject: Re: v7.1.8/8.1.2 SSL Upgrade: Rethinking servers first or clients first
Eric
Really old-school...
Schedule a one time admin schedule to run a script that
ADSM-L@VM.MARIST.EDU
Subject: Re: v7.1.8/8.1.2 SSL Upgrade: Rethinking servers first or clients first
Eric
Really old-school...
Schedule a one time admin schedule to run a script that as the last step
schedules itself again some time in the future
e.g
def scr reset_fred
upd scr reset_
] On Behalf Of Loon,
Eric van (ITOPT3) - KLM
Sent: Wednesday, 7 March 2018 2:00 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] v7.1.8/8.1.2 SSL Upgrade: Rethinking servers first or
clients first
Hi Krzysztof,
Agreed, it will work but it sure aint pretty. And again, we are trying to find
a fi
Krzysztof Przygoda
Sent: dinsdag 6 maart 2018 15:40
To: ADSM-L@VM.MARIST.EDU
Subject: Re: v7.1.8/8.1.2 SSL Upgrade: Rethinking servers first or clients first
Hi Eric
Solution for admin schedule to run more often without crontabs is to have
several of them starting at different moment of each hour
essage-
> From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
> Deschner, Roger Douglas
> Sent: vrijdag 2 maart 2018 2:00
> To: ADSM-L@VM.MARIST.EDU
> Subject: v7.1.8/8.1.2 SSL Upgrade: Rethinking servers first or clients
> first
>
> I've been usin
maart 2018 2:00
To: ADSM-L@VM.MARIST.EDU
Subject: v7.1.8/8.1.2 SSL Upgrade: Rethinking servers first or clients first
I've been using our test setup for further testing, and I'm thinking of
reversing my strategy. I may want to upgrade clients first, and then servers.
The basic issue is still
tegy. I may want to upgrade clients first, and then
> servers.
>
> The basic issue is still how to overcome the roadblock of having an
> Administrator ID automatically switched from TRANSITIONAL to STRICT upon
> first login from a 7.1.8/8.1.2+ dsmadmc client. IBM seems to think we ca
>Then once the operation of these clients was stabilized, upgrade
>our 4 servers one at a time. As each server is upgraded,
>the already-updated client would cause certificates to be
>exchanged and that Admin ID to be switched to STRICT, which
>would be OK since all of the cli
I've been using our test setup for further testing, and I'm thinking of
reversing my strategy. I may want to upgrade clients first, and then servers.
The basic issue is still how to overcome the roadblock of having an
Administrator ID automatically switched from TRANSITIONAL to S
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
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
évrier 2018 10:40:02
Objet: Re: [ADSM-L] No more client sessions after server upgrade.
Hi Eric,
The default certificate (indicated by a * on the left) on older version is
MD5-signed. TLS 1.2 need a SHA-signed certificatee to be the default.
The update/upgrade process should change the defaul
Hi Eric,
The default certificate (indicated by a * on the left) on older version is
MD5-signed. TLS 1.2 need a SHA-signed certificatee to be the default.
The update/upgrade process should change the default certificate but it seems
that it does not.
Here are the commands to verify the default
Hi guys,
To answer my own question so everybody else will be able to find it though
ADSM-L. The solution was to generate a new certificate. During server startup I
noticed the following message:
ANR3336W Default certificate labeled TSM Server SelfSigned Key in key data base
is down level.
The
é: Mardi 6 Février 2018 11:08:37
Objet: Re: [ADSM-L] No more client sessions after server upgrade.
Hi Zoltan,
The server is a Linux box, but the client is Windows...
Kind regards,
Eric van Loon
Air France/KLM Storage Engineering
-Original Message-
From: ADSM: Dist Stor Manager [mai
@VM.MARIST.EDU
Subject: Re: No more client sessions after server upgrade.
If this is a Linux box, did you run the utility to convert the cert/keys file?
https://www.ibm.com/support/knowledgecenter/en/SSEQVQ_8.1.0/srv.admin/t_ssl_config_ca.html
On Mon, Feb 5, 2018 at 10:52 AM, Loon, Eric van (ITOPT3
If this is a Linux box, did you run the utility to convert the cert/keys
file?
https://www.ibm.com/support/knowledgecenter/en/SSEQVQ_8.1.0/srv.admin/t_ssl_config_ca.html
On Mon, Feb 5, 2018 at 10:52 AM, Loon, Eric van (ITOPT3) - KLM <
eric-van.l...@klm.com> wrote:
> Hi guys!
>
> I just upgraded
Hi guys!
I just upgraded our engineering server from 7.1.7 to 7.1.8 and clients cannot
connect anymore. The only session that is working is the one from the server
itself. I opened an admin console through it and when I try to establish and
admins session from my pc, it's rejected with the mess
Hi Zoltan,
When you upgrade the server, the updated clients will be allowed to
connect the first time (trust on first use) and automatically exchange the
certificates.
Del
"ADSM: Dist Stor Manager" wrote on 01/05/2018
1
Del,
Glad to here there should be no issue in upgrading the clients to 7.1.8 or
8.1.2 before the servers are upgraded.
So, what can I expect when I upgrade the servers to 7.1.8 / 8.1.2/4 as for
the certificates? I realize I have to run the utility to convert the
server cert.kdb file to cert256
Hi Zoltan,
It's fine to upgrade the clients first... you won't see warnings because
the clients know they are talking to a back-level server and will speak
the right "language". The best practice is to upgrade the servers first so
all the certificates are there and i
46 AM
> Subject: Re: Should I upgrade to 7.1.8.x ??? (on the client end only)
> Sent by: "ADSM: Dist Stor Manager"
>
> In fact a q server f=d shows Session Security: Transitional, but
> each time I log on to the server using the admin command line, my
> admin u
gards,
Eric van Loon
Air France/KLM Storage Engineering
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Zoltan
Forray
Sent: donderdag 4 januari 2018 15:03
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Should I upgrade to 7.1.8.x ??? (on the client end
4/2018 08:46 AM
> Subject: Re: Should I upgrade to 7.1.8.x ??? (on the client end only)
> Sent by: "ADSM: Dist Stor Manager"
>
> Hi Del,
> Well, not really... I'm currently installing a 7.1.8 server and
> noticed that I could no longer use a 7.1.7 admin commandline:
ed us
from going to the 7.1.8 client everywhere.
It seems that the BA client was more tolerant of the SSL changes than the
admin client, though; I don't remember any client backup problems after the
server upgrade.
On Thu, Jan 04, 2018 at 01:42:50PM +, Loon, Eric van (ITOPT3) - KLM wrote:
&
Del,
Thanks for the info. Some of it is useful and I have seen most of it.
I have a question about the reverse i.e. clients who have upgraded to
8.1.2+ and 7.1.8.There was this dire warning in the 8.1.2 upgrade docs
about upgrading your servers before installing 8.1.2 clients or your
backups
rotocol. A q admin f=d showed that
> sessionsecurity was again set to strict! I'm lost...
> Kind regards,
> Eric van Loon
> Air France/KLM Storage Engineering
>
>
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
>
--Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Del
Hoobler
Sent: donderdag 4 januari 2018 13:45
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Should I upgrade to 7.1.8.x ??? (on the client end only)
Here are a few links that might help:
https://www.ibm.c
e on 01/04/2018
03:37:53 AM:
> From: "Loon, Eric van (ITOPT3) - KLM"
> To: ADSM-L@VM.MARIST.EDU
> Date: 01/04/2018 03:40 AM
> Subject: Re: Should I upgrade to 7.1.8.x ??? (on the client end only)
> Sent by: "ADSM: Dist Stor Manager"
>
> I too read all
ishing.vcu.edu
On Jan 4, 2018 3:39 AM, "Loon, Eric van (ITOPT3) - KLM" <
eric-van.l...@klm.com> wrote:
I too read all the previous posts, but I still don't know what to do. Your
mail also indicates that your upgrade planning is based on several
assumptions and I think it i
I too read all the previous posts, but I still don't know what to do. Your mail
also indicates that your upgrade planning is based on several assumptions and I
think it is really time for IBM to jump in here. I think someone from
development should explain a little bit about the new sec
l. We also know
there will be library sharing gotchas.
We're actually going to do the backup servers first - after thorough testing.
We think we can minimize the risk to things like admin IDS if we upgrade the
servers with NO clients yet on 7.1.8. I think that having 7.1.8 clients around
wi
I too am looking to upgrade all of my servers from 7.1.7.300, soon. I went
through the documents in your link (IBM - one of them 404's). My first
concern would be upgrading the offsite replica server. While there is
documentation about library manager/client server levels/compatibility
(p
Content preview: I believe the incompatibility arises if you set
SESSIONSECURITY
to STRICT for your nodes. The default is TRANSITIONAL so you should be fine;
IIRC the only communication problems we had when upgrading our servers to
v7.1.8 was with library sharing. [...]
Content ana
Thanks for that link, I am more worried about any "gotcha's" caused by
upgrading the client to 7.1.8 or 8.1.2 before the storage servers get
upgraded (and start using the new authentication). What I had not
realized until I saw the chart is that the new clients are NOT backward
compatible with ol
There's pretty wide version compatibility between clients and servers; we
didn't go v7 server-side until pretty recently but have been running the v7
client for a while. IBM has a matrix published here:
http://www-01.ibm.com/support/docview.wss?uid=swg21053218
For basic backups and restores I thi
Our TSM storage servers were all upgraded last year to 7.1.7.2 (before this
new security update came out). Now I am wondering if I should start using
the updated client or not? If the servers stay at 7.1.7.2 for now is
there any harm in using the newer client? I would have to use 7.1.8.0 on
an
>>> "Licensing files need to be updated with the 8.1.0.x packages."
>>>
>>> Which/whose "Licensing files"? Client, server or OC? In which case
>>> (upgrade to 8.1.2.0 or 8.1.3.0?
>>>
>>>
>>> THNX!
>>>
>
gt; > "Licensing files need to be updated with the 8.1.0.x packages."
> >
> > Which/whose "Licensing files"? Client, server or OC? In which case
> > (upgrade to 8.1.2.0 or 8.1.3.0?
> >
> >
> > THNX!
> >
> > --
> > Sasa Drnjevic
ank you so much for all the info!
>
> Can you please just clarify the following:
>
> "Licensing files need to be updated with the 8.1.0.x packages."
>
> Which/whose "Licensing files"? Client, server or OC? In which case
> (upgrade to 8.1.2.0 or
First of all thank you so much for all the info!
Can you please just clarify the following:
"Licensing files need to be updated with the 8.1.0.x packages."
Which/whose "Licensing files"? Client, server or OC? In which case
(upgrade to 8.1.2.0 or 8.1.3.0?
THN
One thing I forgot to mention... if you use 3rd party CA certs anywhere,
you'll want to store the password hash prior to performing the upgrade:
TSM:> q sslkeyringpw
Copy the password to clipboard
In instance directory:
gsk8capicmd_64 -keydb -stashpw -db cert.kdb
Paste password when
I wanted to update this email thread with some of the gotchas that we have
or are experiencing due to our upgrade from 7.1.7 to 8.1.3:
- Watch out when using configuration management or a library manager. I
don't have it documented very carefully, but if you're in a configuration
Hi John,
I would recommend to upgrade existing hw to desired version, backup SP DB,
set up new system and restore DB. There might be additional challenges to
migrate existing backup data on different volumes (disk, files, tapes) but
for the DB this is an easy way to go.
Cheers
Markus
John,
You may find some useful information at this link:
https://www.ibm.com/support/knowledgecenter/SSGSG7_7.1.0/com.ibm.itsm.srv.install.doc/t_srv_upgrade.html
Andrew
>>> John Keyes 2017-10-19 6:15 AM >>>
Hello,
im planning to upgrade a clients TSM 6.3 server
Thank you, thats what I needed to know.
Best Regards,
John
> Gesendet: Donnerstag, 19. Oktober 2017 um 12:56 Uhr
> Von: "Marc Lanteigne"
> An: ADSM-L@VM.MARIST.EDU
> Betreff: Re: [ADSM-L] TSM 6 to 7 Upgrade questions
>
> Just to clarify this statement: “Depending o
Just to clarify this statement: “Depending on old OS and new OS, you may want
to upgrade before or after the move.”
You will want to move from v6 to v6, then upgrade to v7
Or upgrade to v7, and move from v7.
I have seen cases where the new OS didn’t support v6, so they upgrade on the
Hi John,
You are actually doing two separate tasks. Moving to a different machine and
upgrading the software. You have to do one before the other. Depending on old
OS and new OS, you may want to upgrade before or after the move.
The actual move is very similar to a DR exercise. At a
Hello,
im planning to upgrade a clients TSM 6.3 server to TSM 7.1 on new hardware.
However the documentation I found
(https://www.ibm.com/support/knowledgecenter/SSGSG7_7.1.3/srv.install/t_srv_upgrade63_71.html)
only provides a way to make an in-place upgrade. But I need to move to new
1.2 client. I'm not sure if that factored into
> the negotiation.
>
> So far, I think we're in good shape to have this pushed out in the next two
> weeks to production. We'll be upgrading the servers first and the ops
> center shortly thereafter. Then we'll be
ave this pushed out in the next two
weeks to production. We'll be upgrading the servers first and the ops
center shortly thereafter. Then we'll be recommending that all clients
start the upgrade process (providing SSL guidance where necessary).
Therefore, most of our admins and nodes wi
ly care about a
non-disruptive upgrade of both server and client code, does anybody know if
this can be done? So can one upgrade and disable TLS or any other (for me non
vital) new security feature?
Kind regards,
Eric van Loon
For informatio
36:13PM -0500, Roger Deschner wrote:
> > > This difficulty comes up while there are open, now-published security
> > > vulnerabilities out there inviting exploits, and making our Security
> > > people very nervous. But the considerations described in
> > > http:
n, now-published security
> > vulnerabilities out there inviting exploits, and making our Security
> > people very nervous. But the considerations described in
> > http://www-01.ibm.com/support/docview.wss?uid=swg22004844 make it very
> > difficult and risky to proceed with 7.
iderations described in
> http://www-01.ibm.com/support/docview.wss?uid=swg22004844 make it very
> difficult and risky to proceed with 7.1.8/8.1.3 as though it was just a
> patch. It's a major upgrade, requiring major research and planning, with
> the threat of an exploit constant
duct Wiki:
> https://www.ibm.com/developerworks/community/wikis/home/wiki/Tivoli%
> 20Storage%20Manager
>
> "ADSM: Dist Stor Manager" wrote on 2017-10-06
> 15:30:56:
>
> > From: Zoltan Forray
> > To: ADSM-L@VM.MARIST.EDU
> > Date: 2017-10-06 15:32
>
i_storage_manager
>
> Online documentation:
> http://www.ibm.com/support/knowledgecenter/SSGSG7/
> landing/welcome_ssgsg7.html
>
> Product Wiki:
> https://www.ibm.com/developerworks/community/wikis/home/wiki/Tivoli%
> 20Storage%20Manager
>
> "ADSM: Dist Stor Manager&qu
ARIST.EDU
> Date: 2017-10-06 15:32
> Subject: Re: 7.1.8/8.1.3 Security Upgrade Install Issues
> Sent by: "ADSM: Dist Stor Manager"
>
> Well, my testing of upgrading to 8.1.2/3 is not going well. Sure glad I
am
> doing this on a test server, since it doesn't bode
1 - 100 of 1772 matches
Mail list logo
