change TSM server to a new AIX box. What is the way? [Virus checked]
Hi, our TSM Server (Version 5.1.8) is a SP wide node (AIX 5.2_ML02). Now I want change the server to a new pSeries standalone p615. Our TSM-diskstoragepool, the database and the logs are on SSA-Disks. So I think that I must install the new node with the same AIX level and TSM level (mksysb is not so easy, because it is a SP-node). After this I stop the old TSM server. Connect the ssa disks on the new node, import the volumegroups, change the ip configuration on the new node (so that it is the same as on the old server), connect the library, mount filesystems, check that device conf, volhis, database and logs are in right path and than I can start the TSM-Server. Is this the way? Best regards, Frank
3583 library problem
Hi all, My 3583 library don't work today when i execute backup db t=f devclass=3583_MGC, tivoli give me this message: ANR4571E Database backup/restore terminated - = insufficient number of mount points available for removable media. The library always work perfectly and the configuration in tivoli is ok. The number of drives is 1 and the mount limit is set to one. Any ideas? Thanks in advance.
Re: 3583 library problem
I think you need to make more mount point available by increasing the mount limit value -Message d'origine- De : ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] la part de tani Envoyé : mardi 19 octobre 2004 09:09 À : [EMAIL PROTECTED] Objet : 3583 library problem Hi all, My 3583 library don't work today when i execute backup db t=f devclass=3583_MGC, tivoli give me this message: ANR4571E Database backup/restore terminated - = insufficient number of mount points available for removable media. The library always work perfectly and the configuration in tivoli is ok. The number of drives is 1 and the mount limit is set to one. Any ideas? Thanks in advance. === Ce message et toutes les pieces jointes (ci-apres le "message") sont confidentiels et etablis a l'intention exclusive de ses destinataires. Toute utilisation ou diffusion non autorisee est interdite. Tout message electronique est susceptible d'alteration. La SOCIETE GENERALE et ses filiales declinent toute responsabilite au titre de ce message s'il a ete altere, deforme ou falsifie. === This message and any attachments (the "message") are confidential and intended solely for the addressees. Any unauthorized use or dissemination is prohibited. E-mails are susceptible to alteration. Neither SOCIETE GENERALE nor any of its subsidiaries or affiliates shall be liable for the message if altered, changed or falsified. ===
Re: 3583 library problem
But, i think that tivoli does not recommend to define more mount points of the number of drives present in the library Thanks Amhouche Youssef AMHOUCHE Youssef wrote: >I think you need to make more mount point available by increasing the mount >limit value > >-Message d'origine- >De : ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] la part de >tani >Envoyé : mardi 19 octobre 2004 09:09 >À : [EMAIL PROTECTED] >Objet : 3583 library problem > > >Hi all, >My 3583 library don't work today when i execute >backup db t=f devclass=3583_MGC, tivoli give me this message: >ANR4571E Database backup/restore terminated - = insufficient >number of mount points available for removable media. > >The library always work perfectly and the configuration in tivoli is ok. >The number of drives is 1 and the mount limit is set to one. >Any ideas? > >Thanks in advance. > > >=== > >Ce message et toutes les pieces jointes (ci-apres le "message") >sont confidentiels et etablis a l'intention exclusive de ses destinataires. >Toute utilisation ou diffusion non autorisee est interdite. >Tout message electronique est susceptible d'alteration. >La SOCIETE GENERALE et ses filiales declinent toute responsabilite >au titre de ce message s'il a ete altere, deforme ou falsifie. > >=== > >This message and any attachments (the "message") are confidential >and intended solely for the addressees. >Any unauthorized use or dissemination is prohibited. >E-mails are susceptible to alteration. >Neither SOCIETE GENERALE nor any of its subsidiaries or affiliates >shall be liable for the message if altered, changed or falsified. > >=== > > >
Re: 3583 library problem
>The library always work perfectly and the configuration in tivoli is ok. >The number of drives is 1 and the mount limit is set to one. >Any ideas? Hello Execute "q path" and/or "q drive" command and check whether all related devices are online. What is the platform where TSM is installed on ? AIX ? I had a similar problem after some messing with san environment which altered the numbering of "/dev/smcX" and "/dev/rmtX" device files. kind regards Pawel W
Re: 3583 library problem
May be, another tape was mounted in drive? I have this trouble with 3582 & TSM 5.2.3 on W2K. Trouble was in devicetype definition -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of tani Sent: Tuesday, October 19, 2004 1:42 PM To: [EMAIL PROTECTED] Subject: Re: 3583 library problem But, i think that tivoli does not recommend to define more mount points of the number of drives present in the library Thanks Amhouche Youssef AMHOUCHE Youssef wrote: >I think you need to make more mount point available by increasing the >mount limit value > >-Message d'origine- >De : ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] la part de >tani Envoyé : mardi 19 octobre 2004 09:09 À : [EMAIL PROTECTED] >Objet : 3583 library problem > > >Hi all, >My 3583 library don't work today when i execute backup db t=f >devclass=3583_MGC, tivoli give me this message: >ANR4571E Database backup/restore terminated - = insufficient number of >mount points available for removable media. > >The library always work perfectly and the configuration in tivoli is ok. >The number of drives is 1 and the mount limit is set to one. >Any ideas? > >Thanks in advance. > > >=== > >Ce message et toutes les pieces jointes (ci-apres le "message") sont >confidentiels et etablis a l'intention exclusive de ses destinataires. >Toute utilisation ou diffusion non autorisee est interdite. >Tout message electronique est susceptible d'alteration. >La SOCIETE GENERALE et ses filiales declinent toute responsabilite au >titre de ce message s'il a ete altere, deforme ou falsifie. > >=== > >This message and any attachments (the "message") are confidential and >intended solely for the addressees. >Any unauthorized use or dissemination is prohibited. >E-mails are susceptible to alteration. >Neither SOCIETE GENERALE nor any of its subsidiaries or affiliates >shall be liable for the message if altered, changed or falsified. > >=== > > >
Re: RECLAMATION
Generally, I always run at 50%. 2 tapes into 1. I have been known to reclaim at 25% when worrying about tape levels over a weekend... You can run multiple reclamations per storagepool.. but theres a bit of legfowrk involved. Reclamations are really just move-data's, so you could start multiple move-data's based on tape %Util. .. You end up with several tapes you are reclaiming to, and if any of those don't fill past 50% you can reclaim then at the end. I used to reclaim purely using my chosen order of tapes and move-data's, as I didn't used to trust the order in which TSM picked the tapes it was going to reclaim. It seemed to make sense to me to pick the least utilised tapes first. Matt. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Ian Hobbs Sent: Monday, October 18, 2004 9:05 PM To: [EMAIL PROTECTED] Subject: Re: RECLAMATION I would say go as low as you can without impacting other processes. Why waste tape I always say . 65% is not bad. I run at 50%. The trick I have found is to get to a level where the percentage is sustainable. If you can't get there, and tapes are becoming an issue, either get more tapes or drives. Reclamation sure can run a while on todays large tapes. I wonder when multiple reclaims can be run for a single pool at once like migration or backup Also, if you are not getting enough tapes back, make sure expiration is running to completion regularly. On Mon, 18 Oct 2004 15:54:31 -0400, Lepre, James wrote: >What is the IDEAL pct for reclamation, I use 65pct should I go lower > >-Original Message- >From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of >Hart, Charles >Sent: Monday, October 18, 2004 3:51 PM >To: [EMAIL PROTECTED] >Subject: Re: RECLAMATION > >Here's one > >select count(*) from volumes where pct_reclaim>95 and >stgpool_name='TAPE_DR_COPY' > > >-Original Message- >From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of >Richard Hammersley >Sent: Monday, October 18, 2004 2:43 PM >To: [EMAIL PROTECTED] >Subject: Re: RECLAMATION > > >James, > >Do a "query volume" and look at the "pct util" column for the tapes >offsite. Compare that value with the Reclamation Threshold for your >pool. If there are a lot of tapes that meet that threshold and they >don't come back when they should then you should look to make sure the >reclamation is running when it should and if it is running to >completion.Reclamation Threshold > > >Richard > >James Lepre wrote: > >>Hello All, >> >> >> >> I am having problem with reclamation. Tapes are not being recycled as >>they should be. For instance I used get back about 100 tapes per week, >>now I am getting back 16. Any suggestions? >> >> >> Ian Hobbs [EMAIL PROTECTED] === "Never argue with an idiot. They drag you down to their level then beat you with experience." -Dilbert ___ Disclaimer Notice __ This message and any attachments are confidential and should only be read by those to whom they are addressed. If you are not the intended recipient, please contact us, delete the message from your computer and destroy any copies. Any distribution or copying without our prior permission is prohibited. Internet communications are not always secure and therefore Powergen Retail Limited does not accept legal responsibility for this message. The recipient is responsible for verifying its authenticity before acting on the contents. Any views or opinions presented are solely those of the author and do not necessarily represent those of Powergen Retail Limited. Registered addresses: Powergen Retail Limited, Westwood Way, Westwood Business Park, Coventry, CV4 8LG. Registered in England and Wales No: 3407430 Telephone +44 (0) 2476 42 4000 Fax +44 (0) 2476 42 5432
Re: 3583 library problem
Solved. it was a problem in the definition of the route to the drive in tivoli.By some reason tivoli change the state of the drive to nonactive. Recently i update the maintenance level in aix maybe this was the problem. Thanks Pawel. Pawel Wozniczka wrote: >>The library always work perfectly and the configuration in tivoli is ok. >>The number of drives is 1 and the mount limit is set to one. >>Any ideas? >> >> > >Hello > >Execute "q path" and/or "q drive" command and check whether all related >devices are online. > >What is the platform where TSM is installed on ? AIX ? > >I had a similar problem after some messing with san environment which >altered the numbering of "/dev/smcX" and "/dev/rmtX" device files. > >kind regards > >Pawel W > > >
Re: 3583 library problem
Drive is online? Path is online? -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of tani Sent: Tuesday, October 19, 2004 11:09 AM To: [EMAIL PROTECTED] Subject: 3583 library problem Hi all, My 3583 library don't work today when i execute backup db t=f devclass=3583_MGC, tivoli give me this message: ANR4571E Database backup/restore terminated - = insufficient number of mount points available for removable media. The library always work perfectly and the configuration in tivoli is ok. The number of drives is 1 and the mount limit is set to one. Any ideas? Thanks in advance.
Re: Prioritizing a restore ...
Richard,
Thanks for your response. In fact you just confirmed what I thought : my
old TSM server (6H0) must have reached it's limits ! Time to buy some
hardware, our CFO will be pleased hearing this ;-)
Cheers.
Arnaud
**
Panalpina Management Ltd., Basle, Switzerland, CIT Department
Viadukstrasse 42, P.O. Box 4002 Basel/CH
Phone: +41 (61) 226 11 11, FAX: +41 (61) 226 17 01
Direct: +41 (61) 226 19 78
e-mail: [EMAIL PROTECTED]
**
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Richard Sims
Sent: Monday, 18 October, 2004 19:40
To: [EMAIL PROTECTED]
Subject: Re: Prioritizing a restore ...
On Oct 18, 2004, at 12:05 PM, PAC Brion Arnaud wrote:
> I had hard times, couple of days ago, explaining our management why
> the restore of an important informix server took more than 12 hours
> because it was made at the same time (middle of the night) than all
> the nightly backups, and that TSM server seemed to be overflown by all
> that data ...
>
> Therefore my question : is there any way giving a restore process a
> higher prioryty than any other server activity, to ensure a faster
> restore ?
Arnaud - I believe that an Informix restoral would follow the standard
TSM convention where, per the TSM Admin Guide ("Preemption of
Client or Server Operations"), restorals inherently have a high
priority, as the product's raison d'etre. Perhaps you have the
NOPREEMPT server option in effect? If not, check your Activity Log for
what the story is.
Richard Sims
tape status is pending (?)
Hello, has anybody an idea when a tape get this status: Volume Name 86L1 Storage Pool Name COPYPOOL Device Class Name LTOCLASS1 Estimated Capacity (MB) 0.0 Scaled Capacity Applied - Pct Util 0.0 Volume Status PENDING Access READWRITE Pct. Reclaimable Space 0.0 Scratch Volume? NO In Error State? NO If i update this tape, TSM will change it after a few time to pending. Many thanks for any idea. Roland Scharlau >>> Mail is virus-checked by Symantec Mail Security <<<
AW: tape status is pending (?)
Hi, look at storgepool definition "reusedelay" parameter "q stg COPYPOOL f=d" After a volumes comes empty the volume change his status to pending if reuse delay is defined on storagepool. You can delete the volume for reuse. Regards Michael -Ursprüngliche Nachricht- Von: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Im Auftrag von Roland Scharlau Gesendet: Dienstag, 19. Oktober 2004 12:18 An: [EMAIL PROTECTED] Betreff: tape status is pending (?) Hello, has anybody an idea when a tape get this status: Volume Name 86L1 Storage Pool Name COPYPOOL Device Class Name LTOCLASS1 Estimated Capacity (MB) 0.0 Scaled Capacity Applied - Pct Util 0.0 Volume Status PENDING Access READWRITE Pct. Reclaimable Space 0.0 Scratch Volume? NO In Error State? NO If i update this tape, TSM will change it after a few time to pending. Many thanks for any idea. Roland Scharlau >>> Mail is virus-checked by Symantec Mail Security <<<
AW: tape status is pending (?)
Hi Michael, i changed the parameter to 3 days and deleted the volume. Now i define it again. Many thanks for yor answer. Nice day Roland -Ursprüngliche Nachricht- Von: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Im Auftrag von Michael Garnebode Gesendet: Dienstag, 19. Oktober 2004 12:38 An: [EMAIL PROTECTED] Betreff: AW: tape status is pending (?) Hi, look at storgepool definition "reusedelay" parameter "q stg COPYPOOL f=d" After a volumes comes empty the volume change his status to pending if reuse delay is defined on storagepool. You can delete the volume for reuse. Regards Michael -Ursprüngliche Nachricht- Von: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Im Auftrag von Roland Scharlau Gesendet: Dienstag, 19. Oktober 2004 12:18 An: [EMAIL PROTECTED] Betreff: tape status is pending (?) Hello, has anybody an idea when a tape get this status: Volume Name 86L1 Storage Pool Name COPYPOOL Device Class Name LTOCLASS1 Estimated Capacity (MB) 0.0 Scaled Capacity Applied - Pct Util 0.0 Volume Status PENDING Access READWRITE Pct. Reclaimable Space 0.0 Scratch Volume? NO In Error State? NO If i update this tape, TSM will change it after a few time to pending. Many thanks for any idea. Roland Scharlau >>> Mail is virus-checked by Symantec Mail Security <<< >>> Mail is virus-checked by Symantec Mail Security <<<
Question on HSM & TSM.
All, In an environment where you are using HSM to manage disks (say for example Windows drives) after a period of time the file will be migrated to a storage pool within TSM and a stub file is left on the filesystem as a marker. I'm assuming that when this migration happens the TSM backup/archive client identifies the change and only backs up the stub - or does it need to recall the file from HSM and then back it up? If it does only backup the stub the issue is that you do not have a copy of a real file only a stub and no data. Can someone give me an idea as to how they have this type of scenario implemented within their environment? kind regards, Rowan.
Re: Question on HSM & TSM.
On Oct 19, 2004, at 6:58 AM, Rowan O'Donoghue wrote: In an environment where you are using HSM to manage disks (say for example Windows drives) after a period of time the file will be migrated to a storage pool within TSM and a stub file is left on the filesystem as a marker. I'm assuming that when this migration happens the TSM backup/archive client identifies the change and only backs up the stub - or does it need to recall the file from HSM and then back it up? If it does only backup the stub the issue is that you do not have a copy of a real file only a stub and no data. Can someone give me an idea as to how they have this type of scenario implemented within their environment? Rowan - TSM never backs up HSM stub files, as that would be pointless. It backs up the file, either from the file system or directly from the HSM storage pool if migrated and using same server. See the (old) HSM redbook at http://www.redbooks.ibm.com/abstracts/sg244631.html which explains how it all works in different configurations, and advises on restoral methods. Richard Simshttp://people.bu.edu/rbs
Re: Question on HSM & TSM.
Richard, Rowan This is a theoretical scenario only. If the file has been migrated, normally the reason is that it hasnt been updated, modified or accessed within a specified time limit. Therefore, TSM(with it's progressive incremental technology) would never need to backup the file(it hasnt changed). If you where to do a selective backup of all files TSM would retrieve them from HSM storage(or, the HSM software would be the one retrieving them as TSM are trying to access the files). This however isnt true for all HSM products. DX2000(OTG/Legato) can for example co-operate with TSM and only let TSM back up the stub files. There is no reason TSM would backup the HSM migrated files as migrated files normally havent changed. If you where to change an HSM migrated file, it would normally be recalled from HSM storage and therefore no longer be HSM managed. Mvh // Daniel --- Daniel Sparrman Chef Utveckling & Drift Exist i Stockholm AB Propellervägen 6B 183 62 TÄBY Växel: 08 - 754 98 00 Mobil: 070 - 399 27 51 Richard Sims <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 2004-10-19 13:17 Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To [EMAIL PROTECTED] cc Subject Re: Question on HSM & TSM. On Oct 19, 2004, at 6:58 AM, Rowan O'Donoghue wrote: > In an environment where you are using HSM to manage disks (say for > example > Windows drives) after a period of time the file will be migrated > to a > storage pool within TSM and a stub file is left on the filesystem as a > marker. > > I'm assuming that when this migration happens the TSM backup/archive > client > identifies the change and only backs up the stub - or does it need to > recall the file from HSM and then back it up? If it does only backup > the > stub the issue is that you do not have a copy of a real file only a > stub > and no data. > > Can someone give me an idea as to how they have this type of scenario > implemented within their environment? Rowan - TSM never backs up HSM stub files, as that would be pointless. It backs up the file, either from the file system or directly from the HSM storage pool if migrated and using same server. See the (old) HSM redbook at http://www.redbooks.ibm.com/abstracts/sg244631.html which explains how it all works in different configurations, and advises on restoral methods. Richard Simshttp://people.bu.edu/rbs
Re: change TSM server to a new AIX box. What is the way?
That should work, I moved 2 TSM-servers using this method (one with SSA-disks and one with ESS-luns). To be on the safe side, I first migrated all data from disk to tape and made a DB-backup -Original Message- From: Frank Mueller [mailto:[EMAIL PROTECTED] Sent: dinsdag 19 oktober 2004 11:03 To: [EMAIL PROTECTED] Subject: change TSM server to a new AIX box. What is the way? [Virus checked] Hi, our TSM Server (Version 5.1.8) is a SP wide node (AIX 5.2_ML02). Now I want change the server to a new pSeries standalone p615. Our TSM-diskstoragepool, the database and the logs are on SSA-Disks. So I think that I must install the new node with the same AIX level and TSM level (mksysb is not so easy, because it is a SP-node). After this I stop the old TSM server. Connect the ssa disks on the new node, import the volumegroups, change the ip configuration on the new node (so that it is the same as on the old server), connect the library, mount filesystems, check that device conf, volhis, database and logs are in right path and than I can start the TSM-Server. Is this the way? Best regards, Frank
Re: Question on HSM & TSM.
On Oct 19, 2004, at 7:37 AM, Daniel Sparrman wrote: This is a theoretical scenario only. If the file has been migrated, normally the reason is that it hasnt been updated, modified or accessed within a specified time limit. Therefore, TSM(with it's progressive incremental technology) would never need to backup the file(it hasnt changed). ... The primary criterion for TSM backing up a file is whether it yet exists within TSM backup pool storage: if TSM does not yet have it, it wants it in its collection. So, expect a backup, in standard Incremental processing. Whether the file in the HSM-controlled file system migrates is also a control item: the MIGREQUIRESBkup management class parameter governs this. Richard Sims
Antwort: Re: change TSM server to a new AIX box. What is the way? [Virus checked]
Hi, thanks for your answer. Yes I want to migrate all data from disk to our library and start a DB-Backup. So I want test it. Best regards, Frank "Hooft, Jeroen" <[EMAIL PROTECTED]An: [EMAIL PROTECTED] ORIGIN.COM> Kopie: Gesendet von: Thema:Re: change TSM server to a new AIX box. What is the way? [Virus checked] "ADSM: Dist Stor Manager" <[EMAIL PROTECTED] EDU> 19.10.2004 13:55 Bitte antworten an "ADSM: Dist Stor Manager" That should work, I moved 2 TSM-servers using this method (one with SSA-disks and one with ESS-luns). To be on the safe side, I first migrated all data from disk to tape and made a DB-backup -Original Message- From: Frank Mueller [mailto:[EMAIL PROTECTED] Sent: dinsdag 19 oktober 2004 11:03 To: [EMAIL PROTECTED] Subject: change TSM server to a new AIX box. What is the way? [Virus checked] Hi, our TSM Server (Version 5.1.8) is a SP wide node (AIX 5.2_ML02). Now I want change the server to a new pSeries standalone p615. Our TSM-diskstoragepool, the database and the logs are on SSA-Disks. So I think that I must install the new node with the same AIX level and TSM level (mksysb is not so easy, because it is a SP-node). After this I stop the old TSM server. Connect the ssa disks on the new node, import the volumegroups, change the ip configuration on the new node (so that it is the same as on the old server), connect the library, mount filesystems, check that device conf, volhis, database and logs are in right path and than I can start the TSM-Server. Is this the way? Best regards, Frank
Re: Question on HSM & TSM.
Richard, I agree with what you say, and it is pointless in restoring the file to the original filesystem just to back up that file if it is already migrated to tape. I see that there is an option with DiskXtender to do a backup of the file to TSM before it is migrated to tape and any subsequent backups of the file can be ignored if the file size is zero Still reading ;) kind regards, Rowan O'Donoghue Technical Services Manager Unitech Systems Unit 2, First Floor, Bracken Court, Sandyford Industrial Estate, Dublin 18. DDI: + 353 - 1 - 2999357 Tel: + 353 - 1 - 2942300 Fax: + 353 - 1 - 2942319 www.unitech-ie.com |-+---| | Richard Sims <[EMAIL PROTECTED]> | | | Sent by: "ADSM: Dist Stor | | | Manager" | To| | <[EMAIL PROTECTED]>| [EMAIL PROTECTED]| | | M.MARIST| | 19/10/2004 12:17 | .EDU| | | cc| | | | | Please respond to |Subject| | "ADSM: Dist Stor| Re: | | Manager"| Question| | <[EMAIL PROTECTED]> | on HSM &| | | TSM.| | | | | | | | | | | | | | | | | | | |-+---| On Oct 19, 2004, at 6:58 AM, Rowan O'Donoghue wrote: > In an environment where you are using HSM to manage disks (say for > example > Windows drives) after a period of time the file will be migrated > to a > storage pool within TSM and a stub file is left on the filesystem as a > marker. > > I'm assuming that when this migration happens the TSM backup/archive > client > identifies the change and only backs up the stub - or does it need to > recall the file from HSM and then back it up? If it does only backup > the > stub the issue is that you do not have a copy of a real file only a > stub > and no data. > > Can someone give me an idea as to how they have this type of scenario > implemented within their environment? Rowan - TSM never backs up HSM stub files, as that would be pointless. It backs up the file, either from the file system or directly from the HSM storage pool if migrated and using same server. See the (old) HSM redbook at http://www.redbooks.ibm.com/abstracts/sg244631.html which explains how it all works in different configurations, and advises on restoral methods. Richard Sims http://people.bu.edu/rbs ForwardSourceID:NT00015B9E
Re: tape status is pending (?)
Roland, Be aware that your reusedelay parameter should be the same as the number of days back that you keep TSM DB Backups for. This ensures that should you need to restore to a database backup other than the most recent, data will still be where the older DBBackup thinks it is. Matt. _-'-_ -|- -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Roland Scharlau Sent: Tuesday, October 19, 2004 11:44 AM To: [EMAIL PROTECTED] Subject: AW: tape status is pending (?) Hi Michael, i changed the parameter to 3 days and deleted the volume. Now i define it again. Many thanks for yor answer. Nice day Roland -Ursprüngliche Nachricht- Von: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Im Auftrag von Michael Garnebode Gesendet: Dienstag, 19. Oktober 2004 12:38 An: [EMAIL PROTECTED] Betreff: AW: tape status is pending (?) Hi, look at storgepool definition "reusedelay" parameter "q stg COPYPOOL f=d" After a volumes comes empty the volume change his status to pending if reuse delay is defined on storagepool. You can delete the volume for reuse. Regards Michael -Ursprüngliche Nachricht- Von: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Im Auftrag von Roland Scharlau Gesendet: Dienstag, 19. Oktober 2004 12:18 An: [EMAIL PROTECTED] Betreff: tape status is pending (?) Hello, has anybody an idea when a tape get this status: Volume Name 86L1 Storage Pool Name COPYPOOL Device Class Name LTOCLASS1 Estimated Capacity (MB) 0.0 Scaled Capacity Applied - Pct Util 0.0 Volume Status PENDING Access READWRITE Pct. Reclaimable Space 0.0 Scratch Volume? NO In Error State? NO If i update this tape, TSM will change it after a few time to pending. Many thanks for any idea. Roland Scharlau >>> Mail is virus-checked by Symantec Mail Security <<< >>> Mail is virus-checked by Symantec Mail Security <<< ___ Disclaimer Notice __ This message and any attachments are confidential and should only be read by those to whom they are addressed. If you are not the intended recipient, please contact us, delete the message from your computer and destroy any copies. Any distribution or copying without our prior permission is prohibited. Internet communications are not always secure and therefore Powergen Retail Limited does not accept legal responsibility for this message. The recipient is responsible for verifying its authenticity before acting on the contents. Any views or opinions presented are solely those of the author and do not necessarily represent those of Powergen Retail Limited. Registered addresses: Powergen Retail Limited, Westwood Way, Westwood Business Park, Coventry, CV4 8LG. Registered in England and Wales No: 3407430 Telephone +44 (0) 2476 42 4000 Fax +44 (0) 2476 42 5432
Re: Migrating to TSM V5.2 on z?OS
Robert - Both TSM Tech Support and a local consultant recommended that we run the 'cleanup backupgroups' utility before we moved up to 5.2 (btw, mine is a z/OS shop and we recently moved from 5.1.9 to 5.2.3). This utility cleans up orphaned database objects, which will extend your upgradedb run significantly if not cleaned up. My understanding is that the utility only became available with 5.1.73. So, we upgraded from 5.1.65 to 5.1.9 back in June in preparation for the recent upgrade. Then, a few weeks ago, we went to 5.2.3. Incidentally, the upgrade from 5.1.9 to 5.2.3 took quite a while for us - about 11 hours, because of the UPGRADEDB parameter. My TSM DB is about 23 GB. Other TSM Admins have reported quicker upgrade rates, so your time may very well be better. But, as a word of warning, allow a fairly large upgrade window, so you don't have to restore to your previous version - like I did the first time I attempted it. Good luck, Dave. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Klein, Robert (NIH/CIT) Sent: Monday, October 18, 2004 9:27 AM To: [EMAIL PROTECTED] Subject: Migrating to TSM V5.2 on z?OS Believe it or not, we are still running TSM V4.2.2 on OS/390. We are planning to upgrade our OS to z/OS and, along with that, to upgrade to TSM V5.2. I have heard that on some other platforms (e.g. AIX) one cannot go directly from 4.2.2 to V5x. I don't see anything about such a restriction in the V5.2 for z/OS Quick Start manual, but wanted to check whether anyone was aware of this issue for migration to 5.2 on z/OS. Thanks for any input.
Re: Antwort: Re: change TSM server to a new AIX box. What is the way? [Virus checked]
Since you plan to use portability of vg along with SAN. Here is my 2 cents that may help you better. I don't know if you have SSA drives in SAN or directly connected to host, but it would work anyway you plan. AIX5.2ML2 should allow you to make mksysb with any driver necessary to clone your box in any 'chrp' box. So, if you have only 2 copies of mirred rootvg, you can make a 3rd one from ESS and change the bootlist and boot off of it. Then, shutdown the box, move 3rd rootvg copy on ESS to your new box. Let it see or go to SMS to change mutliboot... Viola! Just an idea. Make sure with your network core switches set with the same VLAN or subnet. I don't know if you have HA set on these hosts, but one more thing that you can try with SAN... Gus Jin Bae Chi (Gus) System Administrator Data Center, CSCC 614-287-5270 614-287-5488 Fax [EMAIL PROTECTED] >>> [EMAIL PROTECTED] 10/19/04 8:13 AM >>> Hi, thanks for your answer. Yes I want to migrate all data from disk to our library and start a DB-Backup. So I want test it. Best regards, Frank "Hooft, Jeroen" <[EMAIL PROTECTED]An: [EMAIL PROTECTED] ORIGIN.COM> Kopie: Gesendet von: Thema:Re: change TSM server to a new AIX box. What is the way? [Virus checked] "ADSM: Dist Stor Manager" <[EMAIL PROTECTED] EDU> 19.10.2004 13:55 Bitte antworten an "ADSM: Dist Stor Manager" That should work, I moved 2 TSM-servers using this method (one with SSA-disks and one with ESS-luns). To be on the safe side, I first migrated all data from disk to tape and made a DB-backup -Original Message- From: Frank Mueller [mailto:[EMAIL PROTECTED] Sent: dinsdag 19 oktober 2004 11:03 To: [EMAIL PROTECTED] Subject: change TSM server to a new AIX box. What is the way? [Virus checked] Hi, our TSM Server (Version 5.1.8) is a SP wide node (AIX 5.2_ML02). Now I want change the server to a new pSeries standalone p615. Our TSM-diskstoragepool, the database and the logs are on SSA-Disks. So I think that I must install the new node with the same AIX level and TSM level (mksysb is not so easy, because it is a SP-node). After this I stop the old TSM server. Connect the ssa disks on the new node, import the volumegroups, change the ip configuration on the new node (so that it is the same as on the old server), connect the library, mount filesystems, check that device conf, volhis, database and logs are in right path and than I can start the TSM-Server. Is this the way? Best regards, Frank
Finding huge client files
I'm starting to see more of these: ANR0521W Transaction failed for session 62190 for node - object excluded by size in storage pool SERVERDISKPOOL and all successor pools. ...and I want to be able to contact these end=users to determine what they're trying to back up. But the name of the thing which was too big is nowhere to be found. This leads to an exchange that always goes something like this: ME: You're trying to back up a very, very, very huge file. It isn't working. CLIENT: No I'm not. I have no big files. Prove it - what's it called? ME: Um, I dunno, but you have it. CLIENT: If you can't name it, I don't have it. Go away and stop bothering me. How can I find out the names of these huge files? It doesn't matter whether I plan to take an accomodating or combative approach - I need to know the names of these monster files. Roger Deschner University of Illinois at Chicago [EMAIL PROTECTED]
Re: Finding huge client files
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Roger Deschner >I'm starting to see more of these: > >ANR0521W Transaction failed for session 62190 for node > - object excluded by size in storage pool >SERVERDISKPOOL and all successor pools. > >How can I find out the names of these huge files? It doesn't >matter whether I plan to take an accomodating or combative >approach - I need to know the names of these monster files. Have you looked at the dsmsched.log files for the offending nodes? -- Mark Stapleton ([EMAIL PROTECTED]) Berbee Information Networks Office 262.521.5627
Antwort: Re: Antwort: Re: change TSM server to a new AIX box. What is the way? [Virus checked]
Hi. We have no SAN and no ESS. The storagepools, database and logs are in a simple SSA-loop. Jin Bae Chi <[EMAIL PROTECTED]An: [EMAIL PROTECTED] >Kopie: Gesendet von:Thema:Re: Antwort: Re: change TSM server to a new AIX box. What is the way? "ADSM: Dist Stor [Virus checked] Manager" <[EMAIL PROTECTED] .EDU> 19.10.2004 15:25 Bitte antworten an "ADSM: Dist Stor Manager" Since you plan to use portability of vg along with SAN. Here is my 2 cents that may help you better. I don't know if you have SSA drives in SAN or directly connected to host, but it would work anyway you plan. AIX5.2ML2 should allow you to make mksysb with any driver necessary to clone your box in any 'chrp' box. So, if you have only 2 copies of mirred rootvg, you can make a 3rd one from ESS and change the bootlist and boot off of it. Then, shutdown the box, move 3rd rootvg copy on ESS to your new box. Let it see or go to SMS to change mutliboot... Viola! Just an idea. Make sure with your network core switches set with the same VLAN or subnet. I don't know if you have HA set on these hosts, but one more thing that you can try with SAN... Gus Jin Bae Chi (Gus) System Administrator Data Center, CSCC 614-287-5270 614-287-5488 Fax [EMAIL PROTECTED] >>> [EMAIL PROTECTED] 10/19/04 8:13 AM >>> Hi, thanks for your answer. Yes I want to migrate all data from disk to our library and start a DB-Backup. So I want test it. Best regards, Frank "Hooft, Jeroen" <[EMAIL PROTECTED]An: [EMAIL PROTECTED] ORIGIN.COM> Kopie: Gesendet von: Thema:Re: change TSM server to a new AIX box. What is the way? [Virus checked] "ADSM: Dist Stor Manager" <[EMAIL PROTECTED] EDU> 19.10.2004 13:55 Bitte antworten an "ADSM: Dist Stor Manager" That should work, I moved 2 TSM-servers using this method (one with SSA-disks and one with ESS-luns). To be on the safe side, I first migrated all data from disk to tape and made a DB-backup -Original Message- From: Frank Mueller [mailto:[EMAIL PROTECTED] Sent: dinsdag 19 oktober 2004 11:03 To: [EMAIL PROTECTED] Subject: change TSM server to a new AIX box. What is the way? [Virus checked] Hi, our TSM Server (Version 5.1.8) is a SP wide node (AIX 5.2_ML02). Now I want change the server to a new pSeries standalone p615. Our TSM-diskstoragepool, the database and the logs are on SSA-Disks. So I think that I must install the new node with the same AIX level and TSM level (mksysb is not so easy, because it is a SP-node). After this I stop the old TSM server. Connect the ssa disks on the new node, import the volumegroups, change the ip configuration on the new node (so that it is the same as on the old server), connect the library, mount filesystems, check that device conf, volhis, database and logs are in right path and than I can start the TSM-Server. Is this the way? Best regards, Frank
Re: Migrating to TSM V5.2 on z?OS
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of David Moore >My understanding is that [CLEANUP BACKUPGROUPS] only >became available with 5.1.73. That is incorrect. CLEANUP BACKUPGROUPS became available under later versions of 4.2. -- Mark Stapleton ([EMAIL PROTECTED]) Berbee Information Networks Office 262.521.5627
Re: change TSM server to a new AIX box. What is the way? [Virus checked]
That looks like the correct procedure. We have moved multiple TSM servers between AIX hosts and have had no problems. Just make sure that the server configuration files are all copied over and you should be fine. Ben -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Frank Mueller Sent: Tuesday, October 19, 2004 3:03 AM To: [EMAIL PROTECTED] Subject: change TSM server to a new AIX box. What is the way? [Virus checked] Hi, our TSM Server (Version 5.1.8) is a SP wide node (AIX 5.2_ML02). Now I want change the server to a new pSeries standalone p615. Our TSM-diskstoragepool, the database and the logs are on SSA-Disks. So I think that I must install the new node with the same AIX level and TSM level (mksysb is not so easy, because it is a SP-node). After this I stop the old TSM server. Connect the ssa disks on the new node, import the volumegroups, change the ip configuration on the new node (so that it is the same as on the old server), connect the library, mount filesystems, check that device conf, volhis, database and logs are in right path and than I can start the TSM-Server. Is this the way? Best regards, Frank
AW: tape status is pending (?)
Hi Matt, we make every day a Backup from our TSM DB on disk and once in a week on tape. Is this o.k.? Roland . -Ursprüngliche Nachricht- Von: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Im Auftrag von Warren, Matthew (Retail) Gesendet: Dienstag, 19. Oktober 2004 14:48 An: [EMAIL PROTECTED] Betreff: Re: tape status is pending (?) Roland, Be aware that your reusedelay parameter should be the same as the number of days back that you keep TSM DB Backups for. This ensures that should you need to restore to a database backup other than the most recent, data will still be where the older DBBackup thinks it is. Matt. _-'-_ -|- -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Roland Scharlau Sent: Tuesday, October 19, 2004 11:44 AM To: [EMAIL PROTECTED] Subject: AW: tape status is pending (?) Hi Michael, i changed the parameter to 3 days and deleted the volume. Now i define it again. Many thanks for yor answer. Nice day Roland -Ursprüngliche Nachricht- Von: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Im Auftrag von Michael Garnebode Gesendet: Dienstag, 19. Oktober 2004 12:38 An: [EMAIL PROTECTED] Betreff: AW: tape status is pending (?) Hi, look at storgepool definition "reusedelay" parameter "q stg COPYPOOL f=d" After a volumes comes empty the volume change his status to pending if reuse delay is defined on storagepool. You can delete the volume for reuse. Regards Michael -Ursprüngliche Nachricht- Von: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Im Auftrag von Roland Scharlau Gesendet: Dienstag, 19. Oktober 2004 12:18 An: [EMAIL PROTECTED] Betreff: tape status is pending (?) Hello, has anybody an idea when a tape get this status: Volume Name 86L1 Storage Pool Name COPYPOOL Device Class Name LTOCLASS1 Estimated Capacity (MB) 0.0 Scaled Capacity Applied - Pct Util 0.0 Volume Status PENDING Access READWRITE Pct. Reclaimable Space 0.0 Scratch Volume? NO In Error State? NO If i update this tape, TSM will change it after a few time to pending. Many thanks for any idea. Roland Scharlau >>> Mail is virus-checked by Symantec Mail Security <<< >>> Mail is virus-checked by Symantec Mail Security <<< ___ Disclaimer Notice __ This message and any attachments are confidential and should only be read by those to whom they are addressed. If you are not the intended recipient, please contact us, delete the message from your computer and destroy any copies. Any distribution or copying without our prior permission is prohibited. Internet communications are not always secure and therefore Powergen Retail Limited does not accept legal responsibility for this message. The recipient is responsible for verifying its authenticity before acting on the contents. Any views or opinions presented are solely those of the author and do not necessarily represent those of Powergen Retail Limited. Registered addresses: Powergen Retail Limited, Westwood Way, Westwood Business Park, Coventry, CV4 8LG. Registered in England and Wales No: 3407430 Telephone +44 (0) 2476 42 4000 Fax +44 (0) 2476 42 5432 >>> Mail is virus-checked by Symantec Mail Security <<<
Restoring to different Oracle database
Dear list, Do I need to cater for something if I take backup of Database A using TDP for oracle, and restore it on another machine, with database name B? As far as the intricacies of filespace name, nodename are concerned, these will be the same as were on machine A. Many thanks in advance! Sandra
Question on FC tape drives.
Folks, We are moving from 3590E tape drives to 3592 tape drives. We are also moving from a "direct attach to the TSM server" to a "attachment through a FC switch". I'm sure I'm not the first person to make this change in their environment? Any hints anyone would like to share with me? All my TSM servers are on AIX 5.2 and are using the latest and greatest Atape drivers. As I read the documentation on the Atape drivers: (ftp://ftp.software.ibm.com/storage/devdrvr/Doc/IBM_TotalStorage_tape_IU G.pdf) I see that in this new configuration, I could take advantage of the "Automatic failover" and "Dynamic load balancing" features. As I read through the document (Chapter 6), it looks like upon a path failure, is supposed to fail over transparent to the user, but then has this note that concerns me: 2. The AIX operating system only supports a static configuration of devices, which also applies to the Alternate Pathing and Failover Support. When devices are initially configured at a specific SCSI ID and physical connection (drive port, host bus adapter, and switch number/port, if applicable) and in the Available state, changing the physical device address/connection without either rebooting or unconfiguring and reconfiguring the devices has unpredictable results and is not supported. Also, it looks like when you remove your rmt devices (say, to upgrade the Atape drivers), it looks like the RMT devices may get reconfigured with totally different rmt numbers, requiring a reconfigure of the devices defined to the TSM server. I'm kind of an orderly guy and like to have my rmt devices defined sequentially for ease of troubleshooting, but it sounds like it will take some work on my end to get it to line up nicely like that. I will be starting my testing phase next Monday where I will have 2 FC drives and 2 HBAs attached to the SAN. I am going to configure the FC ports so that both HBAs see both tape drives, so I think I will see 4 new RMT devices when I run a 'cfgmgr'. Anybody else set up in this kind of environment? Any hints/helpful commands they would like to share with me? Thanks, Ben Bullock Micron Technology Boise, Id
Re: Question on FC tape drives.
Running tape through the SAN is great! Whenever there are two or more paths to a drive, do use alternate pathing. The warning you refer to applies to all devices and probably in all computers, if you change something about the device, you had better inform the driver of the change! To deal with the arbitrariness of AIX device names, I use the alternate name feature of the Atape driver. I do this especially for HACMP systems where the names MUST be the same on the HA nodes. I have chosen to build the names as "rmt."+"last 4 hex digits of WWN ." = "path number" Here is a script fragment showing how I construct a name. do WWN=`lsattr -El $d -a ww_name|cut -f2 -d" "|cut -c15-` root=`echo $d|cut -c1-3` new_name=$root.$WWN.0 let "j=0" while [[ -e /dev/$new_name ]] do let "j=j+1" new_name=$root.$WWN.$j done chdev -l $d -a new_name=$new_name done Good Luck! Orville L. Lantto Datatrend Technologies, Inc. (http://www.datatrend.com) IBM Premier Business Partner 121 Cheshire Lane, Suite 700 Minnetonka, MN 55305 Email: [EMAIL PROTECTED] V: 952-931-1203 F: 952-931-1293 CONFIDENTIALITY NOTICE: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. Ben Bullock <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 10/19/2004 04:03 PM Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To [EMAIL PROTECTED] cc Subject Question on FC tape drives. Folks, We are moving from 3590E tape drives to 3592 tape drives. We are also moving from a "direct attach to the TSM server" to a "attachment through a FC switch". I'm sure I'm not the first person to make this change in their environment? Any hints anyone would like to share with me? All my TSM servers are on AIX 5.2 and are using the latest and greatest Atape drivers. As I read the documentation on the Atape drivers: (ftp://ftp.software.ibm.com/storage/devdrvr/Doc/IBM_TotalStorage_tape_IU G.pdf) I see that in this new configuration, I could take advantage of the "Automatic failover" and "Dynamic load balancing" features. As I read through the document (Chapter 6), it looks like upon a path failure, is supposed to fail over transparent to the user, but then has this note that concerns me: 2. The AIX operating system only supports a static configuration of devices, which also applies to the Alternate Pathing and Failover Support. When devices are initially configured at a specific SCSI ID and physical connection (drive port, host bus adapter, and switch number/port, if applicable) and in the Available state, changing the physical device address/connection without either rebooting or unconfiguring and reconfiguring the devices has unpredictable results and is not supported. Also, it looks like when you remove your rmt devices (say, to upgrade the Atape drivers), it looks like the RMT devices may get reconfigured with totally different rmt numbers, requiring a reconfigure of the devices defined to the TSM server. I'm kind of an orderly guy and like to have my rmt devices defined sequentially for ease of troubleshooting, but it sounds like it will take some work on my end to get it to line up nicely like that. I will be starting my testing phase next Monday where I will have 2 FC drives and 2 HBAs attached to the SAN. I am going to configure the FC ports so that both HBAs see both tape drives, so I think I will see 4 new RMT devices when I run a 'cfgmgr'. Anybody else set up in this kind of environment? Any hints/helpful commands they would like to share with me? Thanks, Ben Bullock Micron Technology Boise, Id
Re: Question on FC tape drives.
Excellent, Just the kind of advice I was looking for. I was unaware of the alternate name feature on the Atape driver. I believe I see what the script is doing and should be able to use something similar for my site. Thanks, Ben -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Orville Lantto Sent: Tuesday, October 19, 2004 3:19 PM To: [EMAIL PROTECTED] Subject: Re: Question on FC tape drives. Running tape through the SAN is great! Whenever there are two or more paths to a drive, do use alternate pathing. The warning you refer to applies to all devices and probably in all computers, if you change something about the device, you had better inform the driver of the change! To deal with the arbitrariness of AIX device names, I use the alternate name feature of the Atape driver. I do this especially for HACMP systems where the names MUST be the same on the HA nodes. I have chosen to build the names as "rmt."+"last 4 hex digits of WWN ." = "path number" Here is a script fragment showing how I construct a name. do WWN=`lsattr -El $d -a ww_name|cut -f2 -d" "|cut -c15-` root=`echo $d|cut -c1-3` new_name=$root.$WWN.0 let "j=0" while [[ -e /dev/$new_name ]] do let "j=j+1" new_name=$root.$WWN.$j done chdev -l $d -a new_name=$new_name done Good Luck! Orville L. Lantto Datatrend Technologies, Inc. (http://www.datatrend.com) IBM Premier Business Partner 121 Cheshire Lane, Suite 700 Minnetonka, MN 55305 Email: [EMAIL PROTECTED] V: 952-931-1203 F: 952-931-1293 CONFIDENTIALITY NOTICE: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. Ben Bullock <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 10/19/2004 04:03 PM Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To [EMAIL PROTECTED] cc Subject Question on FC tape drives. Folks, We are moving from 3590E tape drives to 3592 tape drives. We are also moving from a "direct attach to the TSM server" to a "attachment through a FC switch". I'm sure I'm not the first person to make this change in their environment? Any hints anyone would like to share with me? All my TSM servers are on AIX 5.2 and are using the latest and greatest Atape drivers. As I read the documentation on the Atape drivers: (ftp://ftp.software.ibm.com/storage/devdrvr/Doc/IBM_TotalStorage_tape_IU G.pdf) I see that in this new configuration, I could take advantage of the "Automatic failover" and "Dynamic load balancing" features. As I read through the document (Chapter 6), it looks like upon a path failure, is supposed to fail over transparent to the user, but then has this note that concerns me: 2. The AIX operating system only supports a static configuration of devices, which also applies to the Alternate Pathing and Failover Support. When devices are initially configured at a specific SCSI ID and physical connection (drive port, host bus adapter, and switch number/port, if applicable) and in the Available state, changing the physical device address/connection without either rebooting or unconfiguring and reconfiguring the devices has unpredictable results and is not supported. Also, it looks like when you remove your rmt devices (say, to upgrade the Atape drivers), it looks like the RMT devices may get reconfigured with totally different rmt numbers, requiring a reconfigure of the devices defined to the TSM server. I'm kind of an orderly guy and like to have my rmt devices defined sequentially for ease of troubleshooting, but it sounds like it will take some work on my end to get it to line up nicely like that. I will be starting my testing phase next Monday where I will have 2 FC drives and 2 HBAs attached to the SAN. I am going to configure the FC ports so that both HBAs see both tape drives, so I think I will see 4 new RMT devices when I run a 'cfgmgr'. Anybody else set up in this kind of environment? Any hints/helpful commands they would like to share with me? Thanks, Ben Bullock Micron Technology Boise, Id
