TSM Server Upgrade from 5.5.5.2 to 6.3.2
I am planning on upgrading our TSM server from v5.5.5.2 to v6.3.2 this weekend. I have checked and all of the prerequisites are in place and I think I am ready. My only question is, we currently have the v5 database in several directories that have several .DSM files in them but also have lots of free space in them, more than enough to house the V6 DB even if it doubles in size. . According to the upgrade manual, the new directories for the v6 server must be empty but I was hoping to be able to use the same directories where the current v5 database files live since they have more than enough space and then I would eventually delete the old DSM files from the v5 database once the upgrade is complete. When I go to do the upgrade/migration, will it let me use the same directories even though they have one or two files in them already? I realize it might slow the process down but I am limited on SAN space right now.
Re: TSM Server Upgrade from 5.5.5.2 to 6.3.2
With my upgrades I never did test the theory, but I think the directory you specify must be empty. You might try something like this: /tsmdb/v6 instead of /tsmdb Again this is a theory I did not test, but somewhere I saw an example of the DB location that was not on the root of the file system. Please post if this works, I am sure others would be interested. Andy Huebner -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Dury, John C. Sent: Friday, August 17, 2012 11:06 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] TSM Server Upgrade from 5.5.5.2 to 6.3.2 I am planning on upgrading our TSM server from v5.5.5.2 to v6.3.2 this weekend. I have checked and all of the prerequisites are in place and I think I am ready. My only question is, we currently have the v5 database in several directories that have several .DSM files in them but also have lots of free space in them, more than enough to house the V6 DB even if it doubles in size. . According to the upgrade manual, the new directories for the v6 server must be empty but I was hoping to be able to use the same directories where the current v5 database files live since they have more than enough space and then I would eventually delete the old DSM files from the v5 database once the upgrade is complete. When I go to do the upgrade/migration, will it let me use the same directories even though they have one or two files in them already? I realize it might slow the process down but I am limited on SAN space right now. This e-mail (including any attachments) is confidential and may be legally privileged. If you are not an intended recipient or an authorized representative of an intended recipient, you are prohibited from using, copying or distributing the information in this e-mail or its attachments. If you have received this e-mail in error, please notify the sender immediately by return e-mail and delete all copies of this message and any attachments. Thank you.
Re: TSM Server Upgrade from 5.5.5.2 to 6.3.2
I did the upgrade and for the most part it went smoothly. The upgrade wizard did insist on the directories being empty but I was able to create a subdirectory under my target directory and use that so I didn't have to have as much SAN space since I could reuse some directories. John With my upgrades I never did test the theory, but I think the directory you specify must be empty. You might try something like this: /tsmdb/v6 instead of /tsmdb Again this is a theory I did not test, but somewhere I saw an example of the DB location that was not on the root of the file system. Please post if this works, I am sure others would be interested. Andy Huebner -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of Dury, John C. Sent: Friday, August 17, 2012 11:06 AM To: ADSM-L AT VM.MARIST DOT EDU Subject: [ADSM-L] TSM Server Upgrade from 5.5.5.2 to 6.3.2 I am planning on upgrading our TSM server from v5.5.5.2 to v6.3.2 this weekend. I have checked and all of the prerequisites are in place and I think I am ready. My only question is, we currently have the v5 database in several directories that have several .DSM files in them but also have lots of free space in them, more than enough to house the V6 DB even if it doubles in size. . According to the upgrade manual, the new directories for the v6 server must be empty but I was hoping to be able to use the same directories where the current v5 database files live since they have more than enough space and then I would eventually delete the old DSM files from the v5 database once the upgrade is complete. When I go to do the upgrade/migration, will it let me use the same directories even though they have one or two files in them already? I realize it might slow the process down but I am limited on SAN space right now. This e-mail (including any attachments) is confidential and may be legally privileged. If you are not an intended recipient or an authorized representative of an intended recipient, you are prohibited from using, copying or distributing the information in this e-mail or its attachments. If you have received this e-mail in error, please notify the sender immediately by return e-mail and delete all copies of this message and any attachments. Thank you.
Re: TSM Server Upgrade from 5.5.5.2 to 6.3.2
On 08/20/2012 03:12 PM, Dury, John C. wrote: I did the upgrade and for the most part it went smoothly. The upgrade wizard did insist on the directories being empty but I was able to create a subdirectory under my target directory and use that so I didn't have to have as much SAN space since I could reuse some directories. So a little context on this; I once got a yellow belt in DB2. :) http://www.ibm.com/developerworks/data/library/techarticle/0212wieser/index.html DB2 stores data for a "Database" in a series of "Tablespaces". We're handing over the directories entirely to DB2 as "SMS Tablespaces"; System Managed Space. One of the implications of this is that it's a directory in which DB2 thinks it owns _everything_. So you don't want to hand it a directory that has other things in it. and you don't want to accidentally confuse DB2 about its tablespaces. I would recommend a separate filesystem/'disk' per LUN, and I'd always put your stuff in a subdirectory on the volume. That way you can, at need, make a /volumes/tablespace02/tmp parallel to /volumes/tablespace02/containers or such. - Allen S. Rout
