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 t
Author: Dirk Kastens <Dirk.Kastens AT UNI-OSNABRUECK DOT DE>
Date: Wed, 15 Mar 2006 15:12:59 +0100
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
Author: Dirk Kastens <Dirk.Kastens AT UNI-OSNABRUECK DOT DE>
Date: Wed, 15 Mar 2006 15:17:34 +0100
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
Author: "Kauffman, Tom" <KauffmanT AT NIBCO DOT COM>
Date: Wed, 15 Mar 2006 09:21:37 -0500
What I do during D/R -- which amounts to your situation, restoring on a 'new' platform -- is create the primary DB volumes and log volume, restore the database, and then create mirror volumes for the
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 t
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 an
Author: Dirk Kastens <Dirk.Kastens AT UNI-OSNABRUECK DOT DE>
Date: Wed, 15 Mar 2006 16:59:33 +0100
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
Author: Richard Rhodes <rrhodes AT FIRSTENERGYCORP DOT COM>
Date: Wed, 15 Mar 2006 14:16:43 -0500
We will be doing this later this year. 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 wi
Suggestion: Define a new copy pool. copy -only- the disk pool to it. That way you take care of the years' backlog of data at your leisure. On the occasion of your migration: + Disable sessions + bac
Author: Steven Harris <steve AT STEVENHARRIS DOT INFO>
Date: Thu, 16 Mar 2006 10:21:59 +1000
Hi Richard How about this? Backup your disk stgpool to a separate, distinct copypool (just for ease of restore you could use your regular copypool) When you get to the new system, mark your old volum
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,pat
Author: Dirk Kastens <Dirk.Kastens AT UNI-OSNABRUECK DOT DE>
Date: Thu, 16 Mar 2006 11:34:11 +0100
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"
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? Th
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
Author: Dirk Kastens <Dirk.Kastens AT UNI-OSNABRUECK DOT DE>
Date: Thu, 16 Mar 2006 12:33:01 +0100
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 have been done w
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
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
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 upgr
Hi me again 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