That's exactly what I am expecting too. I assume that you can have a
library SCSI attached as opposed to LAN (as I have). But in my case SCSI
target IDs etc do not matter as I only point to an alias defined in the
ibmatl.conf file. I also will have to change the drives from
/dev/rmt/0stc,1stc to 2
Farren Minns wrote:
I may be missing something here of course.
I also don't see a need for deleting and redefining the paths, drives
and libraries. As I said, I connected our library from the old (AIX5.1)
to the new server (AIX5.3). Although the AIX devices changed from
rmt1-rmt6 to rmt0-rmt5,
Hi me again
>From the points on the list (below) is says to delete and redefine the
lib,drives etc because of possible changed scsi-id's, but the library is
referred to by it's alias in the ibmatl.conf file, and this alias will be
the same on the new server. I know this works as I can use the mtli
Hi there
Thanks for that but I'm still confused.
I have already installed 5.1.6.2 on the new server and restored the dB etc
to make sure that the old and new servers are exactly the same. I then
upgraded to 5.2.2 and then to 5.2.2.7 without any problems (this is all
just a test as the original se
Prior to TSM 5 you could get away with just an inventory, but now it has
become necessary to delete and redefine the paths, which will wipe out
all your libvols. (TSM 4 didn't even have paths.) It is critical to do
the two checkin libvol commands in the order in your list - scratch
first, and then
I guess an interim upgrade to 5.1.10 and the clean-up will be pretty quick
anyway so maybe I'll do it anyway just to make sure all is as clean as
possible. If something's worth doing...
All the best
Farren
|-+---|
| Dirk Kasten
Farren Minns wrote:
So do you think I can be confident that this is OK, or should I
add the 5.1.10 step anyway?
Maybe someone from IBM should answer this. If you have tested the
upgrade before, it should be ok. The cleanup command only took a few
minutes on our old server, so the upgrade could
Hi again
I have just been having a look at the powerpoint presentation and it says
that the 'cleanup backupgroups' job runs as part of an upgrade to 5.2/5.3
anyway but that it can increase the length of time to covert the database.
However, I have already tested going from 5.1.6.2 to 5.2.2.7 on th
Hi Dirk
OK, I'm assuming that in this case I could install 5.1.6.2 on the new
server, restore the dB, upgrade to 5.1.10 and then do the "cleanup
backupgroups" rather than upgrading the old server? The reason being that
as 5.1 is out of support, and as our present server has been running like a
dre
Farren,
Farren Minns schrieb:
TSM 5.1.6.2 on Solaris 2.7 - moving to 5.2.7.0 on Solaris 2.9
One point is missing: you should first update the old server to TSM
5.1.10 and run a "cleanup backupgroups" before you go to version 5.2.x.
Theres a good PowerPoint presentation:
http://www-1.ibm.com/su
TSM 5.1.6.2 on Solaris 2.7 - moving to 5.2.7.0 on Solaris 2.9
Hi all
Regarding Anton's check list below, I have a couple of questions.
1) Do I really need to delete and redefine the drives,libray,paths etc? I
understand that I will need to update the /dev/rmt/??? entry for the drives
to make sur
gt; <[EMAIL PROTECTED]
> DE>
> To
> Sent by: "ADSM: ADSM-L@VM.MARIST.EDU
> Dist Stor
> cc
> Manager"
> <[EMAIL PROTECTED]
> Subject
>
>> On Wed, 15 Mar 2006 14:16:43 -0500, Richard Rhodes <[EMAIL PROTECTED]> said:
> We have a complicating problem - several disk pools using migration delay.
> We do this
> for several applications that use TSM to archive data (deleting it from
> within the application). We
> hold this data in a d
Dist Stor cc
Manager"
<[EMAIL PROTECTED] Subject
.EDU> Re: New TSM Server, DB and STG POOL
question
03/15/2006 10:44
anton walde schrieb:
We changed our Hardware a year ago. We asked support to help us and got a
good hand-out with all the steps to make.
Here is the 'cook book':
I followed the technote that Richard mentioned, and everything worked
fine. I think you should delete the old disk pool volumes befo
Hallo.
We changed our Hardware a year ago. We asked support to help us and got a
good hand-out with all the steps to make.
Here is the 'cook book':
1. you must have the samt TSM-Version on the old and new server.
2. migrate all diskpools to tape
3. backup the TSM-DB on the old server maybe t
Thanks Dirk
Well I set caching to off on the disk pool on the original server and then
migrated down to zero before doing the DB backup. So I'm thinking that if I
now just format the vols I need on the new server, it should be fine. As it
is this is just a test and I'll do the proper upgrade at th
On Mar 15, 2006, at 9:12 AM, Dirk Kastens wrote:
... There's a technote on this topic somewhere on the
Tivoli support side.
1114874 is at least one on the site.
Richard Sims
s used at startup to find the database. All other definitions are stored
in the database.
Tom Kauffman
NIBCO, Inc
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Farren
Minns
Sent: Wednesday, March 15, 2006 8:33 AM
To: ADSM-L@VM.MARIST.EDU
Subject
I wrote:
> I first deleted all disk storage pools on the old server,
CAUTION!!! Of yourse, I only deleted the disk pool volumes, NOT the
storage pools themselves.
--
Regards,
Dirk Kastens
Universitaet Osnabrueck, Rechenzentrum (Computer Center)
Albrechtstr. 28, 49069 Osnabrueck, Germany
Tel.:
Farren,
Farren Minns schrieb:
If moving a TSM server from one machine to another, do you format space for
the backup pools first, then do the restore, or do you restore your DB
first and then format space for the backup pool and archive pool?
I just moved our AIX TSM-Server from one machine t
Hi All
I'm running TSM on Solaris 2.7 and moving to Solaris 2.9 on a new physical
server.
If moving a TSM server from one machine to another, do you format space for
the backup pools first, then do the restore, or do you restore your DB
first and then format space for the backup pool and archive
22 matches
Mail list logo
