Re: upgrading 6.3 to 7.1.x

[Dwight Cook]

The library manager has to be the highest level of TSM for the 
environment...


Dwight E. Cook
Technical Services Prof. Sr. 
TSM Delivery Architect
IBM Cloud
(918) 493-4678



From:   Zoltan Forray 
To: ADSM-L@VM.MARIST.EDU
Date:   04/19/2016 12:11 PM
Subject:Re: upgrading 6.3 to 7.1.x
Sent by:"ADSM: Dist Stor Manager" 



Well, I did my first 6.3.5 to 7.1.3 (plan to jump to 7.1.5.100 next)
upgrade on a discontinued but still functioning server.  After correcting 
a
problem in the startup script, it seems to be running - mostly.

I am getting a strange error on my TS3500 Library Manager server.

4/19/2016 12:01:12 PM ANR0443W Protocol error on session 93137 for node
FIREBALL (Linux/x86_64) - invalid "driveList" field found in "MountVolume"
verb (offset 21).

FIREBALL is the name of the server just upgraded. I can't find anything 
via
Google.

I suspect it has to do with the LM server still being at 6.3.5.1 and needs
to be upgraded first?


On Mon, Apr 18, 2016 at 1:14 PM, Lee, Gary  wrote:

> When I  did it it was backup db, run install of 7.1.x then start server.
>
> However, one caveat, make sure you have sufficient empty space in your
> active log.  Recommendation is double the space you need for the log.
> Had this problem, it will not run the upgrade step if you have
> insufficient log space.
>



--
*Zoltan Forray*
TSM Software & Hardware Administrator
Xymon Monitor Administrator
VMware Administrator (in training)
Virginia Commonwealth University
UCC/Office of Technology Services
www.ucc.vcu.edu
zfor...@vcu.edu - 804-828-4807
Don't be a phishing victim - VCU and other reputable organizations will
never use email to request that you reply with your password, social
security number or confidential personal information. For more details
visit http://infosecurity.vcu.edu/phishing.html

Re: upgrading 6.3 to 7.1.x

[Lee, Gary]

Yes, library manager must be highest server level of the bunch.

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Zoltan 
Forray
Sent: Tuesday, April 19, 2016 1:11 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] upgrading 6.3 to 7.1.x

Well, I did my first 6.3.5 to 7.1.3 (plan to jump to 7.1.5.100 next)
upgrade on a discontinued but still functioning server.  After correcting a
problem in the startup script, it seems to be running - mostly.

I am getting a strange error on my TS3500 Library Manager server.

4/19/2016 12:01:12 PM ANR0443W Protocol error on session 93137 for node
FIREBALL (Linux/x86_64) - invalid "driveList" field found in "MountVolume"
verb (offset 21).

FIREBALL is the name of the server just upgraded. I can't find anything via
Google.

I suspect it has to do with the LM server still being at 6.3.5.1 and needs
to be upgraded first?


On Mon, Apr 18, 2016 at 1:14 PM, Lee, Gary  wrote:

> When I  did it it was backup db, run install of 7.1.x then start server.
>
> However, one caveat, make sure you have sufficient empty space in your
> active log.  Recommendation is double the space you need for the log.
> Had this problem, it will not run the upgrade step if you have
> insufficient log space.
>



--
*Zoltan Forray*
TSM Software & Hardware Administrator
Xymon Monitor Administrator
VMware Administrator (in training)
Virginia Commonwealth University
UCC/Office of Technology Services
www.ucc.vcu.edu
zfor...@vcu.edu - 804-828-4807
Don't be a phishing victim - VCU and other reputable organizations will
never use email to request that you reply with your password, social
security number or confidential personal information. For more details
visit http://infosecurity.vcu.edu/phishing.html

Re: upgrading 6.3 to 7.1.x

[Rhodes, Richard L.]

Yes, that's my understanding.  The LM in a library sharing environment has to 
be upgraded first.
This is where we are - planning our LM instances upgrade to v7.1, then the 
clients.

Rick



-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Zoltan 
Forray
Sent: Tuesday, April 19, 2016 1:11 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: upgrading 6.3 to 7.1.x

Well, I did my first 6.3.5 to 7.1.3 (plan to jump to 7.1.5.100 next)
upgrade on a discontinued but still functioning server.  After correcting a
problem in the startup script, it seems to be running - mostly.

I am getting a strange error on my TS3500 Library Manager server.

4/19/2016 12:01:12 PM ANR0443W Protocol error on session 93137 for node
FIREBALL (Linux/x86_64) - invalid "driveList" field found in "MountVolume"
verb (offset 21).

FIREBALL is the name of the server just upgraded. I can't find anything via
Google.

I suspect it has to do with the LM server still being at 6.3.5.1 and needs
to be upgraded first?


On Mon, Apr 18, 2016 at 1:14 PM, Lee, Gary  wrote:

> When I  did it it was backup db, run install of 7.1.x then start server.
>
> However, one caveat, make sure you have sufficient empty space in your
> active log.  Recommendation is double the space you need for the log.
> Had this problem, it will not run the upgrade step if you have
> insufficient log space.
>



--
*Zoltan Forray*
TSM Software & Hardware Administrator
Xymon Monitor Administrator
VMware Administrator (in training)
Virginia Commonwealth University
UCC/Office of Technology Services
www.ucc.vcu.edu
zfor...@vcu.edu - 804-828-4807
Don't be a phishing victim - VCU and other reputable organizations will
never use email to request that you reply with your password, social
security number or confidential personal information. For more details
visit http://infosecurity.vcu.edu/phishing.html


-
The information contained in this message is intended only for the personal and 
confidential use of the recipient(s) named above. If the reader of this message 
is not the intended recipient or an agent responsible for delivering it to the 
intended recipient, you are hereby notified that you have received this 
document in error and that any review, dissemination, distribution, or copying 
of this message is strictly prohibited. If you have received this communication 
in error, please notify us immediately, and delete the original message.

Re: upgrading 6.3 to 7.1.x

[Zoltan Forray]

Well, I did my first 6.3.5 to 7.1.3 (plan to jump to 7.1.5.100 next)
upgrade on a discontinued but still functioning server.  After correcting a
problem in the startup script, it seems to be running - mostly.

I am getting a strange error on my TS3500 Library Manager server.

4/19/2016 12:01:12 PM ANR0443W Protocol error on session 93137 for node
FIREBALL (Linux/x86_64) - invalid "driveList" field found in "MountVolume"
verb (offset 21).

FIREBALL is the name of the server just upgraded. I can't find anything via
Google.

I suspect it has to do with the LM server still being at 6.3.5.1 and needs
to be upgraded first?


On Mon, Apr 18, 2016 at 1:14 PM, Lee, Gary  wrote:

> When I  did it it was backup db, run install of 7.1.x then start server.
>
> However, one caveat, make sure you have sufficient empty space in your
> active log.  Recommendation is double the space you need for the log.
> Had this problem, it will not run the upgrade step if you have
> insufficient log space.
>



--
*Zoltan Forray*
TSM Software & Hardware Administrator
Xymon Monitor Administrator
VMware Administrator (in training)
Virginia Commonwealth University
UCC/Office of Technology Services
www.ucc.vcu.edu
zfor...@vcu.edu - 804-828-4807
Don't be a phishing victim - VCU and other reputable organizations will
never use email to request that you reply with your password, social
security number or confidential personal information. For more details
visit http://infosecurity.vcu.edu/phishing.html

Re: EoS for TSM 6.3

[Del Hoobler]

Yes, the 6.3.x server will be supported until the 6.4 is EOS.



Del

---


"ADSM: Dist Stor Manager"  wrote on 04/19/2016 
09:42:41 AM:

> From: Erwann SIMON 
> To: ADSM-L@VM.MARIST.EDU
> Date: 04/19/2016 09:44 AM
> Subject: Re: EoS for TSM 6.3
> Sent by: "ADSM: Dist Stor Manager" 
> 
> Hi all, and IBMers particularly,
> 
> Can someone clarify this point ? Will 6.3.3 server be supported 
> along with 6.4 version ?
> 
> -- 
> Best regards / Cordialement / مع تحياتي
> Erwann SIMON
> 
> - Mail original -
> De: "Skylar Thompson" 
> À: ADSM-L@VM.MARIST.EDU
> Envoyé: Lundi 18 Avril 2016 18:12:10
> Objet: Re: [ADSM-L] EoS for TSM 6.3
> 
> Given that the TSM v6.4 "release" shipped the v6.3 server[1], does this
> mean that the v6.3 server will continue to be supported until v6.4 is
> no longer supported?
> 
> [1] http://www-01.ibm.com/support/docview.wss?uid=swg21243309
> 
> On Mon, Apr 18, 2016 at 04:56:16PM +0100, Schofield, Neil (Storage &
> Middleware, Backup & Restore) wrote:
> > In case anyone missed it, IBM last week announced the End-of-
> Support date for TSM 6.3 would be April 30th 2017:
> > http://www.ibm.com/common/ssi/rep_ca/2/897/ENUS916-072/index.html
> 
> --
> -- Skylar Thompson (skyl...@u.washington.edu)
> -- Genome Sciences Department, System Administrator
> -- Foege Building S046, (206)-685-7354
> -- University of Washington School of Medicine
> 

Re: Managed servers out of sync

[Steven Langdale]

Don't forget if you do that, you will loose all of your schedule assoc's,
so will need to re-assoc them.

On Tue, 19 Apr 2016, 14:50 Skylar Thompson, 
wrote:

> The problem is that a domain that has any nodes in it and is out-of-sync
> cannot be fixed; I believe that operation is functionally like a
> delete It's really no big deal to do the temp domain though:
>
> copy domain dom1 temp-dom1
> update node * wheredom=dom1 dom=temp-dom1
> (sync up)
> update node * wheredom=temp-dom1 dom=dom1
> delete domain temp-dom1
>
> The copy domain operation even copies the active policyset and default
> management classes, so there's no risk to having the wrong retention
> policies applied.
>
> On Tue, Apr 19, 2016 at 01:39:54PM +, Kamp, Bruce (Ext) wrote:
> > I have 4 TSM servers running on AIX the library manager/configuration
> manger is now 7.1.4.100 (upgraded from 7.1.0) the other 3 are 7.1.0.
> > About a month ago the server to server communications stopped working
> because of authentication failure.  In working with IBM it was decided that
> I need to upgrade all my servers to a higher version of TSM.  With all the
> changes going on at the moment it will take a while for me to upgrade the
> rest of the servers.
> > I have figured out a temporary work around to get the communications
> working until I can upgrade.  What I found out when I "fixed" the first
> server is that domains have become out of synch.
> >
> > ANR3350W Locally defined domain FS_PROD_DOMAIN_04 contains
> > at least one node and cannot be replaced with a
> > definition from the configuration manager. (SESSION: 4)
> >
> > When I asked IBM how to figure out which nodes are causing this problem
> I was told I had to move all nodes to a temp domain delete the domain run
> notify subscribers & than move the nodes back into the domain.
> >
> > What I am wondering is if anyone knows how I can identify what nodes are
> causing this so I only have to move them out & back?
> >
> >
> > Thanks,
> > Bruce Kamp
> > GIS Backup & Recovery
> > (817) 568-7331
> > e-mail: mailto:bruce.k...@novartis.com
> > Out of Office:
>
> --
> -- Skylar Thompson (skyl...@u.washington.edu)
> -- Genome Sciences Department, System Administrator
> -- Foege Building S046, (206)-685-7354
> -- University of Washington School of Medicine
>

Re: Managed servers out of sync

[Skylar Thompson]

The problem is that a domain that has any nodes in it and is out-of-sync
cannot be fixed; I believe that operation is functionally like a
delete It's really no big deal to do the temp domain though:

copy domain dom1 temp-dom1
update node * wheredom=dom1 dom=temp-dom1
(sync up)
update node * wheredom=temp-dom1 dom=dom1
delete domain temp-dom1

The copy domain operation even copies the active policyset and default
management classes, so there's no risk to having the wrong retention policies 
applied.

On Tue, Apr 19, 2016 at 01:39:54PM +, Kamp, Bruce (Ext) wrote:
> I have 4 TSM servers running on AIX the library manager/configuration manger 
> is now 7.1.4.100 (upgraded from 7.1.0) the other 3 are 7.1.0.
> About a month ago the server to server communications stopped working because 
> of authentication failure.  In working with IBM it was decided that I need to 
> upgrade all my servers to a higher version of TSM.  With all the changes 
> going on at the moment it will take a while for me to upgrade the rest of the 
> servers.
> I have figured out a temporary work around to get the communications working 
> until I can upgrade.  What I found out when I "fixed" the first server is 
> that domains have become out of synch.
>
> ANR3350W Locally defined domain FS_PROD_DOMAIN_04 contains
> at least one node and cannot be replaced with a
> definition from the configuration manager. (SESSION: 4)
>
> When I asked IBM how to figure out which nodes are causing this problem I was 
> told I had to move all nodes to a temp domain delete the domain run notify 
> subscribers & than move the nodes back into the domain.
>
> What I am wondering is if anyone knows how I can identify what nodes are 
> causing this so I only have to move them out & back?
>
>
> Thanks,
> Bruce Kamp
> GIS Backup & Recovery
> (817) 568-7331
> e-mail: mailto:bruce.k...@novartis.com
> Out of Office:

--
-- Skylar Thompson (skyl...@u.washington.edu)
-- Genome Sciences Department, System Administrator
-- Foege Building S046, (206)-685-7354
-- University of Washington School of Medicine

Re: EoS for TSM 6.3

[Erwann SIMON]

Hi all, and IBMers particularly,

Can someone clarify this point ? Will 6.3.3 server be supported along with 6.4 
version ?

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

- Mail original -
De: "Skylar Thompson" 
À: ADSM-L@VM.MARIST.EDU
Envoyé: Lundi 18 Avril 2016 18:12:10
Objet: Re: [ADSM-L] EoS for TSM 6.3

Given that the TSM v6.4 "release" shipped the v6.3 server[1], does this
mean that the v6.3 server will continue to be supported until v6.4 is
no longer supported?

[1] http://www-01.ibm.com/support/docview.wss?uid=swg21243309

On Mon, Apr 18, 2016 at 04:56:16PM +0100, Schofield, Neil (Storage & 
Middleware, Backup & Restore) wrote:
> In case anyone missed it, IBM last week announced the End-of-Support date for 
> TSM 6.3 would be April 30th 2017:
> http://www.ibm.com/common/ssi/rep_ca/2/897/ENUS916-072/index.html

--
-- Skylar Thompson (skyl...@u.washington.edu)
-- Genome Sciences Department, System Administrator
-- Foege Building S046, (206)-685-7354
-- University of Washington School of Medicine

Managed servers out of sync

[Kamp, Bruce (Ext)]

I have 4 TSM servers running on AIX the library manager/configuration manger is 
now 7.1.4.100 (upgraded from 7.1.0) the other 3 are 7.1.0.
About a month ago the server to server communications stopped working because 
of authentication failure.  In working with IBM it was decided that I need to 
upgrade all my servers to a higher version of TSM.  With all the changes going 
on at the moment it will take a while for me to upgrade the rest of the servers.
I have figured out a temporary work around to get the communications working 
until I can upgrade.  What I found out when I "fixed" the first server is that 
domains have become out of synch.

ANR3350W Locally defined domain FS_PROD_DOMAIN_04 contains
at least one node and cannot be replaced with a
definition from the configuration manager. (SESSION: 4)

When I asked IBM how to figure out which nodes are causing this problem I was 
told I had to move all nodes to a temp domain delete the domain run notify 
subscribers & than move the nodes back into the domain.

What I am wondering is if anyone knows how I can identify what nodes are 
causing this so I only have to move them out & back?


Thanks,
Bruce Kamp
GIS Backup & Recovery
(817) 568-7331
e-mail: mailto:bruce.k...@novartis.com
Out of Office: