Op 18 apr. 2016, om 18:28 heeft Zoltan Forray <[email protected]> het volgende 
geschreven:

> Well, I have been meaning to upgrade my 6.3.5.100 servers to 7.1.5 so this
> pushes the timetable up a little......
> 
> Any gotchas on this upgrade?  Anything I should be concerned with?  Is it
> just a "backup DB/configs... twice - run the installer - everything is
> good"? I have looked through the upgrade docs and it was a bit TL;DR going
> through the DB2 configs, etc.These are all RedHat Linux servers.  Single
> instances of TSM servers so I know how each is configured.  Only one of
> them is a 6.1->6.3 upgrade - the others are all 6.3 installs/migrations.
> 

before the upgrade: reduce the active log to less than 50% of the filespace, 
make sure you have >50% free space in the active log filesystem, then upgrade. 
After the upgrade you can increase the active log to the old size again.

> On Mon, Apr 18, 2016 at 12:12 PM, Skylar Thompson <[email protected]>
> wrote:
> 
>> 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 ([email protected])
>> -- Genome Sciences Department, System Administrator
>> -- Foege Building S046, (206)-685-7354
>> -- University of Washington School of Medicine
>> 
> 
> 
> 
> --
> *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
> [email protected] - 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
  • EoS for T... Schofield, Neil (Storage & Middleware, Backup & Restore)
    • Re: ... Skylar Thompson
      • ... Zoltan Forray
        • ... Remco Post
          • ... Zoltan Forray
      • ... Erwann SIMON
        • ... Del Hoobler
          • ... Erwann SIMON
            • ... Del Hoobler
    • Re: ... Roger Deschner
      • ... Del Hoobler
        • ... Maurice van 't Loo

Reply via email to