Re: SAN error
Thanks, TSM run as root. My question is : how can I know which is the device that HBAAPI can't manage ? I have lot of drives and HBA so I wondered which one return this message ? All the HBA are compatible with HBAAPI... The drives too... So the message can indicate a potential problem which is not already logged elsewhere (errlog, ...) Or a configuration mismatch ! Regards Pierre > -Message d'origine- > De : ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] De > la part de Fred Johanson > Envoyé : vendredi 23 novembre 2007 16:02 > À : ADSM-L@VM.MARIST.EDU > Objet : Re: [ADSM-L] SAN error > > I wondered about messages like that when I turned > SANDISCOVERY on. I found that TSM must run as root (in AIX) > to access the devices at the OS level. > > > > From: ADSM: Dist Stor Manager on behalf of CAYE PIERRE > Sent: Fri 11/23/2007 6:48 AM > To: ADSM-L@VM.MARIST.EDU > Subject: [ADSM-L] SAN error > > > > Hi, > > I went ot turn on SANDiscovery on a new server and I get the message : > > ANR1789W Get HBA target mapping failed. > > How can I know which device is involved ? > > I run TSM 5.3.4.2 (old I know) on AIX 5.3 > > Regards, > > Pierre CAYE >
Re: SAN error
I wondered about messages like that when I turned SANDISCOVERY on. I found that TSM must run as root (in AIX) to access the devices at the OS level. From: ADSM: Dist Stor Manager on behalf of CAYE PIERRE Sent: Fri 11/23/2007 6:48 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] SAN error Hi, I went ot turn on SANDiscovery on a new server and I get the message : ANR1789W Get HBA target mapping failed. How can I know which device is involved ? I run TSM 5.3.4.2 (old I know) on AIX 5.3 Regards, Pierre CAYE
SAN error
Hi, I went ot turn on SANDiscovery on a new server and I get the message : ANR1789W Get HBA target mapping failed. How can I know which device is involved ? I run TSM 5.3.4.2 (old I know) on AIX 5.3 Regards, Pierre CAYE
Re: TSM STA Paths
The library manager need an access to the cartridge to validate, at least, the label when mounting and dismounting the tape. > -Message d'origine- > De : ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] De > la part de Ian-IT Smith > Envoyé : vendredi 23 novembre 2007 11:54 > À : ADSM-L@VM.MARIST.EDU > Objet : Re: [ADSM-L] TSM STA Paths > > I thought the Library manager would be able to mount the > drive off the element and serial number info in the drive statrement. > > Then informthe STA to send data to its SCSI device defined in > the path associated with that drive. > > Although, if the TSM Library manager actually needs the SCSI > device to mount the tape, then yes I guess the TSM Library > Manager->Drive path must be configured in addition to the > STA->Drive path. > > > Ian Smith > > > > > CAYE PIERRE <[EMAIL PROTECTED]> Sent by: "ADSM: > Dist Stor Manager" > 23/11/2007 10:47 > Please respond to > "ADSM: Dist Stor Manager" > > > To > ADSM-L@VM.MARIST.EDU > cc > > Subject > Re: [ADSM-L] TSM STA Paths > > > > > > > The library manager, as it is said, is the library manager. > When STA need cartridges, it ask the library manager for it. > The library manager ask the library to mount a tape, then, > when it know > the drive where it is mounted, it will check the label of the > cartridge, > so an access (ie a path) to the drive is needed for the > library manager. > Then, knowing the drive, it find the path of the drive on STA > side so it > can tell the STA where the cartridge is mounted and address (ie the > special file) of the tape. > When you look at drives activity on the library manager, you > can see that, > during mount process of cartridge, the cartridge and the > mount point are > owned by the library manager. Therefore the ownership is > transfered to the > STA. > A select on drives table (allocated_to) during mount process > can show you > all that. > > Regards > > Pierre > > > -Message d'origine- > > De : ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] De > > la part de Ian-IT Smith > > Envoyé : vendredi 23 novembre 2007 10:47 > > À : ADSM-L@VM.MARIST.EDU > > Objet : [ADSM-L] TSM STA Paths > > > > I have a question regarding paths for drives in a storage agent > > environment: > > > > If drives are in a library, can they be defined on the > > Library Manager as drive, but ONLY have paths to the storage agent? > > > > Or must all drives need to be pathed to the library manager > > as well as the storage agents? > > > > I was sure that the TSM Library Manager did not require a > > path to the drive > > > > > > Ian Smith > > > > > > > > --- > > > > This e-mail may contain confidential and/or privileged > > information. If you are not the intended recipient (or have > > received this e-mail in error) please notify the sender > > immediately and delete this e-mail. Any unauthorized copying, > > disclosure or distribution of the material in this e-mail is > > strictly forbidden. > > > > Please refer to > > http://www.db.com/en/content/eu_disclosures.htm for > > additional EU corporate and regulatory disclosures. > > > > > > --- > > This e-mail may contain confidential and/or privileged > information. If you are not the intended recipient (or have > received this e-mail in error) please notify the sender > immediately and delete this e-mail. Any unauthorized copying, > disclosure or distribution of the material in this e-mail is > strictly forbidden. > > Please refer to > http://www.db.com/en/content/eu_disclosures.htm for > additional EU corporate and regulatory disclosures. >
SV: [ADSM-L] Windows TSM server upgrade advice
Hello, Can you install the TSM code on another disk? If so upgrade the OS to 2003 with sp2, after that uninstall TSM and reinstall and upgrade TSM on the other disk. Regards/Micke Från: ADSM: Dist Stor Manager genom Chris McKay Skickat: on 2007-11-21 17:27 Till: ADSM-L@VM.MARIST.EDU Ämne: [ADSM-L] Windows TSM server upgrade advice Hello, I'm looking for some advice if possible on upgrading a Windows TSM server. The current server is built on Windows 2000, running TSM version 5.3. I have very limited system partition space available (approx 2GB free), which houses the OS and TSM server files. I would like to upgrade the OS to Windows 2003 server, and also upgrade the version of TSM to version 5.5. I am a little concerned with the space available on the system partition, as most likely it would be easier to upgrade the OS first, then upgrade the version of TSM after. I have a second TSM server that is also at level 5.3, but on a Windows 2003 OS. Any advice would be appreciated. Take care, Chris
Re: TSM STA Paths
I thought the Library manager would be able to mount the drive off the element and serial number info in the drive statrement. Then informthe STA to send data to its SCSI device defined in the path associated with that drive. Although, if the TSM Library manager actually needs the SCSI device to mount the tape, then yes I guess the TSM Library Manager->Drive path must be configured in addition to the STA->Drive path. Ian Smith CAYE PIERRE <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" 23/11/2007 10:47 Please respond to "ADSM: Dist Stor Manager" To ADSM-L@VM.MARIST.EDU cc Subject Re: [ADSM-L] TSM STA Paths The library manager, as it is said, is the library manager. When STA need cartridges, it ask the library manager for it. The library manager ask the library to mount a tape, then, when it know the drive where it is mounted, it will check the label of the cartridge, so an access (ie a path) to the drive is needed for the library manager. Then, knowing the drive, it find the path of the drive on STA side so it can tell the STA where the cartridge is mounted and address (ie the special file) of the tape. When you look at drives activity on the library manager, you can see that, during mount process of cartridge, the cartridge and the mount point are owned by the library manager. Therefore the ownership is transfered to the STA. A select on drives table (allocated_to) during mount process can show you all that. Regards Pierre > -Message d'origine- > De : ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] De > la part de Ian-IT Smith > Envoyé : vendredi 23 novembre 2007 10:47 > À : ADSM-L@VM.MARIST.EDU > Objet : [ADSM-L] TSM STA Paths > > I have a question regarding paths for drives in a storage agent > environment: > > If drives are in a library, can they be defined on the > Library Manager as drive, but ONLY have paths to the storage agent? > > Or must all drives need to be pathed to the library manager > as well as the storage agents? > > I was sure that the TSM Library Manager did not require a > path to the drive > > > Ian Smith > > > > --- > > This e-mail may contain confidential and/or privileged > information. If you are not the intended recipient (or have > received this e-mail in error) please notify the sender > immediately and delete this e-mail. Any unauthorized copying, > disclosure or distribution of the material in this e-mail is > strictly forbidden. > > Please refer to > http://www.db.com/en/content/eu_disclosures.htm for > additional EU corporate and regulatory disclosures. > --- This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and delete this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. Please refer to http://www.db.com/en/content/eu_disclosures.htm for additional EU corporate and regulatory disclosures.
Compare TSM and veritas Netbackup
Hello, I search for comparaison between TSM ans netbackup solutions in LINUX environements. Thank you for help.
Re: TSM STA Paths
The library manager, as it is said, is the library manager. When STA need cartridges, it ask the library manager for it. The library manager ask the library to mount a tape, then, when it know the drive where it is mounted, it will check the label of the cartridge, so an access (ie a path) to the drive is needed for the library manager. Then, knowing the drive, it find the path of the drive on STA side so it can tell the STA where the cartridge is mounted and address (ie the special file) of the tape. When you look at drives activity on the library manager, you can see that, during mount process of cartridge, the cartridge and the mount point are owned by the library manager. Therefore the ownership is transfered to the STA. A select on drives table (allocated_to) during mount process can show you all that. Regards Pierre > -Message d'origine- > De : ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] De > la part de Ian-IT Smith > Envoyé : vendredi 23 novembre 2007 10:47 > À : ADSM-L@VM.MARIST.EDU > Objet : [ADSM-L] TSM STA Paths > > I have a question regarding paths for drives in a storage agent > environment: > > If drives are in a library, can they be defined on the > Library Manager as drive, but ONLY have paths to the storage agent? > > Or must all drives need to be pathed to the library manager > as well as the storage agents? > > I was sure that the TSM Library Manager did not require a > path to the drive > > > Ian Smith > > > > --- > > This e-mail may contain confidential and/or privileged > information. If you are not the intended recipient (or have > received this e-mail in error) please notify the sender > immediately and delete this e-mail. Any unauthorized copying, > disclosure or distribution of the material in this e-mail is > strictly forbidden. > > Please refer to > http://www.db.com/en/content/eu_disclosures.htm for > additional EU corporate and regulatory disclosures. >
TSM STA Paths
I have a question regarding paths for drives in a storage agent environment: If drives are in a library, can they be defined on the Library Manager as drive, but ONLY have paths to the storage agent? Or must all drives need to be pathed to the library manager as well as the storage agents? I was sure that the TSM Library Manager did not require a path to the drive Ian Smith --- This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and delete this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. Please refer to http://www.db.com/en/content/eu_disclosures.htm for additional EU corporate and regulatory disclosures.
