TSM Restore Using 349X lib failes.
Hello you guru's. Last weekend we did a migration to a new AIX/box with our TSM 4.2.1.9 server. Everthing was configured, installed. We were unable to test the 3494 library 'cause it was attached to the production environment, and we had no spare available at the location. This is what we did. SOURCE RS/6000 - S70 AIX 4.3.3 TSM 4.2.1.9 1 x 3494 7 x SCSI 3590E 1 x ESS ( 2 x Fibre Channel point to point) TARGET -- RS/6000 - H80 ( New BOX) AIX 4.3.3 ( Cleanly Installed ) TSM 4.2.1.9( Cleanly Installed ) 1 x 3494 (Moved from source) 7 x SCSI 3590E (Moved from source) Seperate ESS ( 2 x Fibre Channel point to point) Library definitions: define library libm libt=349x devi=/dev/magstar (lmcp0) define dev 3590 devt=3590 format=drive mountl=drives define drive libm drive dev=/dev/rmt1 We did these actions before on disaster recovery tests, and it worked fine all the time. BUT NOW, we have preconfigured the whole environment, and started a restore db. We got the message that the library type did not support this action. We defined all settings like we always did. We needed to define a manual tape library to do the restore. Automated restore db's used to work fine. How come it doesn't work now? Could this be a bug? Or did we make a mistake after all? Ilja G. Coolen _ ABP / USZO CIS / BS / TB / Storage Management Telefoon : +31(0)45 579 7938 Fax : +31(0)45 579 3990 Email: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] Intranet : Storage http://intranet/cis_bstb/html_content/sm/index_sm.htm Web _ - Everybody has a photographic memory, some just don't have film. -
Archive and keep last accessed date.
Hi. Do anyone know if it's possible to archive files by the TSM client and NOT changing the last accessed date? If - How? I need it for an archive routine that finds old files (not accessed since long time) in the centralised Netware file servers from where we distribute personal and project libraries to our customers PC's. The intention is, like we always have tried to do in the mainframes, have the date attributes to reflect the customer activities. I.e. have the infrastructure routines to behave transparent from the customers point of view. I'm doing the archiving by a Windows2000 TSM client access via the shares and not by the TSM Netware client to guarantee later access independent from possible file server farm changes in the future. Have someone tried something in this area, please tell me where you found the worst pitfalls. /Lars Lars Danielsson Volvo Information Technology AB Dept 2510, HD2S SE-40508 Gothenburg, Sweden Telephone: +46 31 667479 Telefax: +46 31 662336 mailto:[EMAIL PROTECTED]
Re: Archive and keep last accessed date.
Hej Lars Det är inte TSM klienten som ändrar Last Accessed datumet, utan operativsystemet. Netware, eller Windows för den delen, känner av när filen accessas av en programvara, eller användare, och ändrar därefter datumet. Därför borde denna förändring ligga i operativsystemets inställningar. Jag vet dock inte hur detta hanteras i Netware. Det kanske du kan bättre än mig. Mvh // Daniel Sparrman --- Daniel Sparrman Exist i Stockholm AB Bergkällavägen 31D 192 79 SOLLENTUNA Växel: 08 - 754 98 00 Mobil: 070 - 399 27 51 Danielsson Lars Lars.Danielsson@To: [EMAIL PROTECTED] VOLVO.COM cc: Sent by: ADSM: Subject: Archive and keep last accessed Dist Stordate. Manager [EMAIL PROTECTED] .EDU 2002-02-04 12:34 Please respond to ADSM: Dist Stor Manager Hi. Do anyone know if it's possible to archive files by the TSM client and NOT changing the last accessed date? If - How? I need it for an archive routine that finds old files (not accessed since long time) in the centralised Netware file servers from where we distribute personal and project libraries to our customers PC's. The intention is, like we always have tried to do in the mainframes, have the date attributes to reflect the customer activities. I.e. have the infrastructure routines to behave transparent from the customers point of view. I'm doing the archiving by a Windows2000 TSM client access via the shares and not by the TSM Netware client to guarantee later access independent from possible file server farm changes in the future. Have someone tried something in this area, please tell me where you found the worst pitfalls. /Lars Lars Danielsson Volvo Information Technology AB Dept 2510, HD2S SE-40508 Gothenburg, Sweden Telephone: +46 31 667479 Telefax: +46 31 662336 mailto:[EMAIL PROTECTED]
Re: PRESCHEDULECMD on OS390 unix, rc 127
Unless you're in a Sysplex environment where these users may log on to different systems, I would set my automount timeout to never de-mount the automounted user HFS and then just let TSM backup all mounted HFS's. If a user never logged on, there's no sense in backing up his HFS as it probably never changed. This is the DURATION parameter in the /etc/u.map. If they're logging on to different systems in the Sysplex, then maybe you'll have to live with backing up the HFS files as a whole with DFDSS. Maybe the error you're running into is security, or the filemasking in the /etc/u.map file. The DSNAME of the HFS is determined by incorporating the userid of who is currently logged on. Bill Boyer DSS, Inc. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of MC Matt Cooper (2838) Sent: Friday, February 01, 2002 7:37 AM To: [EMAIL PROTECTED] Subject: PRESCHEDULECMD on OS390 unix, rc 127 Hello all, I am trying to get a PRESCHEDULECMD script that will automount all the users HFSs for backup. I know there is a command for automount but I have to update the list of users automounted daily. We are just getting into this area and it is growing. Anyway, I execut the script successfully from the OS390 Unix environment but when I added to the backup as a PRESCHEDULECMD I got a RC 127. I can not find the interpretation of the message. Anyone know what it is or where I should be looking it up? From the DSMSCHED.LOG ... 02/01/2002 00:00:08 Server Window Start: 00:00:01 on 02/01/2002 02/01/2002 00:00:08 02/01/2002 00:00:08 Executing scheduled command now. 02/01/2002 00:00:08 Executing Operating System command or script: /etc/amnthfs.sh 02/01/2002 00:00:09 Finished command. Return code is: 127 02/01/2002 00:00:09 --- SCHEDULEREC OBJECT BEGIN MVS-DAILY 02/01/2002 00:00:01 There was nothering in the DSMERROR.LOG The DSM.SYS looks like * Top of Data * SERVERNAME MVS1CMF COMMmethod TCPip NODENAME AG04 TCPPort1500 TCPServeraddress 192.168.100.252 SCHEDLOGNAME /var/tsm/dsmsched.log SChEDLOGRETENTION 10 ERRORLOGNAME /var/tsm/dsmerror.log ERRORLOGRETENTION 10 PASSWORDACCESS GENERATE SCHEDMODE PROMPTED INCLEXCL /etc/tsm/inclexcl.txt TCPWindowsize 64 RETRYPERIOD15 MAXCMDRETRIES 10 LARGECOMMBUFFERS YES COMMRESTARTINTERVAL 60 COMMRESTARTDURATION 300 preschedulecmd '/etc/amnthfs.sh' The script looks like.. BROWSE -- /etc/tsm/amnthfs.sh - #!/bin/sh cd /u/MKC$ cd /u/HPZ$ cd /u/CSB$ cd /u/RDH$ cd /u/JEJ$ cd /u/CMR$ cd /u/CD1$
Re: Archive and keep last accessed date.
Sorry, didn't think about the mess getting on the list. Here's a translation: Hi Lars It's not the TSM client that changes the Last Access date, rather the operating system. Netware, or Windows for that mather, senses when the file is changed by an application, or user, and changes the date accordingly. Therefore, this is probably a setting in the operating system. But I don't now how to handle this in Netware, perhaps you know more about this than me. :) Best Regards Daniel Sparrman --- Daniel Sparrman Exist i Stockholm AB Bergkällavägen 31D 192 79 SOLLENTUNA Växel: 08 - 754 98 00 Mobil: 070 - 399 27 51 Salak Juraj j.salak@ASAMTo: [EMAIL PROTECTED] ER.AT cc: Sent by: Subject: Re: Archive and keep last ADSM: Dist accessed date. Stor Manager [EMAIL PROTECTED] RIST.EDU 2002-02-04 15:19 Please respond to ADSM: Dist Stor Manager Hej Daniel, ked sa dohovaras sukromne s Larsom tak je svedstina OK, ale potom mu napis na sukromnu adresu. Ked pises do verejneho fora, tak pouzivaj, prosim Ta, anglictinu Juraj ; -Original Message- From: Daniel Sparrman [mailto:[EMAIL PROTECTED]] Sent: Monday, February 04, 2002 2:15 PM To: [EMAIL PROTECTED] Subject: Re: Archive and keep last accessed date. Hej Lars Det är inte TSM klienten som ändrar Last Accessed datumet, utan operativsystemet. Netware, eller Windows för den delen, känner av när filen accessas av en programvara, eller användare, och ändrar därefter datumet. Därför borde denna förändring ligga i operativsystemets inställningar. Jag vet dock inte hur detta hanteras i Netware. Det kanske du kan bättre än mig. Mvh // Daniel Sparrman --- Daniel Sparrman Exist i Stockholm AB Bergkällavägen 31D 192 79 SOLLENTUNA Växel: 08 - 754 98 00 Mobil: 070 - 399 27 51 Danielsson Lars Lars.Danielsson@To: [EMAIL PROTECTED] VOLVO.COM cc: Sent by: ADSM: Subject: Archive and keep last accessed Dist Stordate. Manager [EMAIL PROTECTED] .EDU 2002-02-04 12:34 Please respond to ADSM: Dist Stor Manager Hi. Do anyone know if it's possible to archive files by the TSM client and NOT changing the last accessed date? If - How? I need it for an archive routine that finds old files (not accessed since long time) in the centralised Netware file servers from where we distribute personal and project libraries to our customers PC's. The intention is, like we always have tried to do in the mainframes, have the date attributes to reflect the customer activities. I.e. have the infrastructure routines to behave transparent from the customers point of view. I'm doing the archiving by a Windows2000 TSM client access via the shares and not by the TSM Netware client to guarantee later access independent from possible file server farm changes in the future. Have someone tried something in this area, please tell me where you found the worst pitfalls. /Lars Lars Danielsson Volvo Information Technology AB Dept 2510, HD2S SE-40508 Gothenburg, Sweden Telephone: +46 31 667479 Telefax: +46 31 662336 mailto:[EMAIL PROTECTED]
Re: Backups failed with new TdP for Exchange client 2.2
after upgrading TdP Exchange from 1.1.1.01 to 2.2, and scheduling the following COMMAND: c:\Program Files\Tivoli\TSM\TDPExchange\excincr.cmd we get RC=1. Using the same script to run incr backup manually, gives RC=0 ! Any idea, cue about why incr fails under Tsm Scheduler (System account) and is successfull when launched manually under a admin user with service account Exchange ? René, Try updating the schedule with the entire command in single quotes or use the short name. The scheduler could be having a problem with the space in the directory name. i.e. c:\Program Files. For example (line may split due to size limitations): UPDATE SCHEDULE domain sched OBJECTS='c:\Program Files\Tivoli\TSM\TDPExchange\excincr.cmd' Thanks, Del Del Hoobler IBM Corporation [EMAIL PROTECTED] Celebrate we will. Life is short but sweet for certain... -- Dave
Re: TDP questions
Managing expiration is the job of the TDP or application software. Ordinarily a new filename is used for every new backup, and TSM hangs onto the file until it is specifically deleted by the TDP. A point of clarification... This is not always true... for example, with TDP for Domino 1.1, TDP for Exchange 2.2 and TDP for SQL 2.2, expiration is controlled by the TSM Server policy settings. The TDP application does not control expiration. Historically speaking... With TDP for SQL 1.1 and TDP for Exchange 1.1 expiration was controlled by running a delete command with the TDP client. That was changed when version 2.2 came out. Thanks, Del Del Hoobler IBM Corporation [EMAIL PROTECTED] Celebrate we will. Life is short but sweet for certain... -- Dave
Re: PRESCHEDULECMD on OS390 unix, rc 127
Hey Bill, I found that my problem causing the RC 127 was I had put the script in /etc/tsm/amnthfs.sh and had a preschedulecmd that was looking for /etc/amnthfs.sh . I had the path wrong. It seems to be interesting working with this. We have a 3 lpar environment so I have to go through the process. I wrote a job that I scheduled to run everyday about an hour before the backups. It has 3 steps. Step1 does an IDCAMS DCOLLECT of the 3 disk volumes that have user HFSs. Step2 is a SAS program that parses the output of the DCOLLECT for all the user HFS's and it writes out a script that will do a CD /U/ (where is the user) for each user HFS, this gets them mounted. Step 3 just copies the script to the /etc/tsm/amnthfs.sh file. Matt -Original Message- From: Bill Boyer [mailto:[EMAIL PROTECTED]] Sent: Monday, February 04, 2002 9:26 AM To: [EMAIL PROTECTED] Subject: Re: PRESCHEDULECMD on OS390 unix, rc 127 Unless you're in a Sysplex environment where these users may log on to different systems, I would set my automount timeout to never de-mount the automounted user HFS and then just let TSM backup all mounted HFS's. If a user never logged on, there's no sense in backing up his HFS as it probably never changed. This is the DURATION parameter in the /etc/u.map. If they're logging on to different systems in the Sysplex, then maybe you'll have to live with backing up the HFS files as a whole with DFDSS. Maybe the error you're running into is security, or the filemasking in the /etc/u.map file. The DSNAME of the HFS is determined by incorporating the userid of who is currently logged on. Bill Boyer DSS, Inc. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of MC Matt Cooper (2838) Sent: Friday, February 01, 2002 7:37 AM To: [EMAIL PROTECTED] Subject: PRESCHEDULECMD on OS390 unix, rc 127 Hello all, I am trying to get a PRESCHEDULECMD script that will automount all the users HFSs for backup. I know there is a command for automount but I have to update the list of users automounted daily. We are just getting into this area and it is growing. Anyway, I execut the script successfully from the OS390 Unix environment but when I added to the backup as a PRESCHEDULECMD I got a RC 127. I can not find the interpretation of the message. Anyone know what it is or where I should be looking it up? From the DSMSCHED.LOG ... 02/01/2002 00:00:08 Server Window Start: 00:00:01 on 02/01/2002 02/01/2002 00:00:08 02/01/2002 00:00:08 Executing scheduled command now. 02/01/2002 00:00:08 Executing Operating System command or script: /etc/amnthfs.sh 02/01/2002 00:00:09 Finished command. Return code is: 127 02/01/2002 00:00:09 --- SCHEDULEREC OBJECT BEGIN MVS-DAILY 02/01/2002 00:00:01 There was nothering in the DSMERROR.LOG The DSM.SYS looks like * Top of Data * SERVERNAME MVS1CMF COMMmethod TCPip NODENAME AG04 TCPPort1500 TCPServeraddress 192.168.100.252 SCHEDLOGNAME /var/tsm/dsmsched.log SChEDLOGRETENTION 10 ERRORLOGNAME /var/tsm/dsmerror.log ERRORLOGRETENTION 10 PASSWORDACCESS GENERATE SCHEDMODE PROMPTED INCLEXCL /etc/tsm/inclexcl.txt TCPWindowsize 64 RETRYPERIOD15 MAXCMDRETRIES 10 LARGECOMMBUFFERS YES COMMRESTARTINTERVAL 60 COMMRESTARTDURATION 300 preschedulecmd '/etc/amnthfs.sh' The script looks like.. BROWSE -- /etc/tsm/amnthfs.sh - #!/bin/sh cd /u/MKC$ cd /u/HPZ$ cd /u/CSB$ cd /u/RDH$ cd /u/JEJ$ cd /u/CMR$ cd /u/CD1$
file permissions AIX
To: Andy Raibeck, et al Where can I find documentation about how TSM 4 deals with files permissions when interacting between client and server machines when each is hosted on AIX ? On the client side, for example, where users share files with others in their group-id, any member of the group can initiate an archive operation for files in that group. The server side, however, seems to ignore group-id info as far as allowing visibility/access to others. Which manual(s) for TSM on AIX discuss handling of file permissions ? - Ray Dmochowski *** This message and any attachments is solely for the intended recipient. If you are not the intended recipient, disclosure, copying, use, or distribution of the information included in this message is prohibited -- please immediately and permanently delete this message.
Re: Archive and keep last accessed date.
Hej Daniel, ked sa dohovaras sukromne s Larsom tak je svedstina OK, ale potom mu napis na sukromnu adresu. Ked pises do verejneho fora, tak pouzivaj, prosim Ta, anglictinu Juraj ; -Original Message- From: Daniel Sparrman [mailto:[EMAIL PROTECTED]] Sent: Monday, February 04, 2002 2:15 PM To: [EMAIL PROTECTED] Subject: Re: Archive and keep last accessed date. Hej Lars Det är inte TSM klienten som ändrar Last Accessed datumet, utan operativsystemet. Netware, eller Windows för den delen, känner av när filen accessas av en programvara, eller användare, och ändrar därefter datumet. Därför borde denna förändring ligga i operativsystemets inställningar. Jag vet dock inte hur detta hanteras i Netware. Det kanske du kan bättre än mig. Mvh // Daniel Sparrman --- Daniel Sparrman Exist i Stockholm AB Bergkällavägen 31D 192 79 SOLLENTUNA Växel: 08 - 754 98 00 Mobil: 070 - 399 27 51 Danielsson Lars Lars.Danielsson@To: [EMAIL PROTECTED] VOLVO.COM cc: Sent by: ADSM: Subject: Archive and keep last accessed Dist Stordate. Manager [EMAIL PROTECTED] .EDU 2002-02-04 12:34 Please respond to ADSM: Dist Stor Manager Hi. Do anyone know if it's possible to archive files by the TSM client and NOT changing the last accessed date? If - How? I need it for an archive routine that finds old files (not accessed since long time) in the centralised Netware file servers from where we distribute personal and project libraries to our customers PC's. The intention is, like we always have tried to do in the mainframes, have the date attributes to reflect the customer activities. I.e. have the infrastructure routines to behave transparent from the customers point of view. I'm doing the archiving by a Windows2000 TSM client access via the shares and not by the TSM Netware client to guarantee later access independent from possible file server farm changes in the future. Have someone tried something in this area, please tell me where you found the worst pitfalls. /Lars Lars Danielsson Volvo Information Technology AB Dept 2510, HD2S SE-40508 Gothenburg, Sweden Telephone: +46 31 667479 Telefax: +46 31 662336 mailto:[EMAIL PROTECTED]
Re: 9840 element addresses.
element 500 - 505 -Original Message- From: Jason Morgan [mailto:[EMAIL PROTECTED]] Sent: Monday, February 04, 2002 9:49 AM To: [EMAIL PROTECTED] Subject: 9840 element addresses. Hi, Would any one be able to confirm what the element addresses for 6 9840 drives in an L700 would be. ? Regards Jason --- Please note my e-mail address has changed to @rbc.com. / Veuillez noter que ma nouvelle adresse courriel est @rbc.com. This e-mail may be privileged and/or confidential, and the sender does not waive any related rights and obligations. Any distribution, use or copying of this e-mail or the information it contains by other than an intended recipient is unauthorized. If you received this e-mail in error, please advise me (by return e-mail or otherwise) immediately. Ce courriel est confidentiel et protégé. L'expéditeur ne renonce pas aux droits et obligations qui s'y rapportent. Toute diffusion, utilisation ou copie de ce message ou des renseignements qu'il contient par une personne autre que le (les) destinataire(s) désigné(s) est interdite. Si vous recevez ce courriel par erreur, veuillez m'en aviser immédiatement, par retour de courriel ou par un autre moyen. ==
Re: TSM Restore Using 349X lib fails.
Did you install atape and atldd? Before using tsm make sure that mtlib can talk to it. You can test that by simply doing an mtlib -l/dev/lmcp0 -qL This will tell you if the machine can talk to the tape library. If it can't make sure that you can ping it and that the /etc/ibmatl.conf is configured properly. Good luck Becky -Original Message- From: Ilja G. Coolen [mailto:[EMAIL PROTECTED]] Sent: Monday, February 04, 2002 3:14 AM To: [EMAIL PROTECTED] Subject: TSM Restore Using 349X lib failes. Hello you guru's. Last weekend we did a migration to a new AIX/box with our TSM 4.2.1.9 server. Everthing was configured, installed. We were unable to test the 3494 library 'cause it was attached to the production environment, and we had no spare available at the location. This is what we did. SOURCE RS/6000 - S70 AIX 4.3.3 TSM 4.2.1.9 1 x 3494 7 x SCSI 3590E 1 x ESS ( 2 x Fibre Channel point to point) TARGET -- RS/6000 - H80 ( New BOX) AIX 4.3.3 ( Cleanly Installed ) TSM 4.2.1.9( Cleanly Installed ) 1 x 3494 (Moved from source) 7 x SCSI 3590E (Moved from source) Seperate ESS ( 2 x Fibre Channel point to point) Library definitions: define library libm libt=349x devi=/dev/magstar (lmcp0) define dev 3590 devt=3590 format=drive mountl=drives define drive libm drive dev=/dev/rmt1 We did these actions before on disaster recovery tests, and it worked fine all the time. BUT NOW, we have preconfigured the whole environment, and started a restore db. We got the message that the library type did not support this action. We defined all settings like we always did. We needed to define a manual tape library to do the restore. Automated restore db's used to work fine. How come it doesn't work now? Could this be a bug? Or did we make a mistake after all? Ilja G. Coolen _ ABP / USZO CIS / BS / TB / Storage Management Telefoon : +31(0)45 579 7938 Fax : +31(0)45 579 3990 Email: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] Intranet : Storage http://intranet/cis_bstb/html_content/sm/index_sm.htm Web _ - Everybody has a photographic memory, some just don't have film. -
Re: 9840 element addresses.
Hi The 9840:s should be placed top down... and the first element adress is 500. For six drives it should look like this from the top of the drive bays: 1st drive 500 2nd drive 501 3rd drive 502 4th drive 503 5th drive 504 6th drive 505 7th empty 8th empty 9th empty 10th empty 11th empty 12th empty The only difference if you have a L700e is that it can hold more drives, and that the element address is between 500-519. Best Regards Daniel Sparrman --- Daniel Sparrman Exist i Stockholm AB Bergkällavägen 31D 192 79 SOLLENTUNA Växel: 08 - 754 98 00 Mobil: 070 - 399 27 51 Jason Morgan jmorga31@CSCTo: [EMAIL PROTECTED] .COMcc: Sent by: Subject: 9840 element addresses. ADSM: Dist Stor Manager [EMAIL PROTECTED] RIST.EDU 2002-02-04 15:49 Please respond to ADSM: Dist Stor Manager Hi, Would any one be able to confirm what the element addresses for 6 9840 drives in an L700 would be. ? Regards Jason
9840 element addresses.
Hi, Would any one be able to confirm what the element addresses for 6 9840 drives in an L700 would be. ? Regards Jason
APAR= IC32379 fixed??
Does anyone know if this has been fixed?? If so, what client level?? I noticed it was closed on 12/26/01 with a recommended workaround. The recommended workaround is not really viable for me since I don't administer the clients I backup. Therefore if they make changes to the local file system and I removed the DOMAIN-ALL Local to implement the temporary fix, then the additions won't get backed up. Thanks, Matt - This message (including any attachments) contains confidential information intended for a specific individual and purpose, and is protected by law. - If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited.
Does the TSM client send the password in clear text ??!
Hello, Does the TSM client send the password in cleartext? Thanks, Keith
Re: 9840 element addresses.
Would drive element address 500 be drive 0 or drive 6 ? Regards Jason Daniel Sparrman [EMAIL PROTECTED]@VM.MARIST.EDU on 04/02/2002 14:52:26 Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Re: 9840 element addresses. Hi The 9840:s should be placed top down... and the first element adress is 500. For six drives it should look like this from the top of the drive bays: 1st drive 500 2nd drive 501 3rd drive 502 4th drive 503 5th drive 504 6th drive 505 7th empty 8th empty 9th empty 10th empty 11th empty 12th empty The only difference if you have a L700e is that it can hold more drives, and that the element address is between 500-519. Best Regards Daniel Sparrman --- Daniel Sparrman Exist i Stockholm AB Bergkällavägen 31D 192 79 SOLLENTUNA Växel: 08 - 754 98 00 Mobil: 070 - 399 27 51 Jason Morgan jmorga31@CSCTo: [EMAIL PROTECTED] .COMcc: Sent by: Subject: 9840 element addresses. ADSM: Dist Stor Manager [EMAIL PROTECTED] RIST.EDU 2002-02-04 15:49 Please respond to ADSM: Dist Stor Manager Hi, Would any one be able to confirm what the element addresses for 6 9840 drives in an L700 would be. ? Regards Jason
HELP Citrix Server Backup
I would like to know what you are using to back up Citrix servers? I was just informed this morning that Tivoli does not support the backup of servers that run Citrix Metaframe!!! Bruce Kamp Network Analyst II Memorial Healthcare System P: (954) 987-2020 x6008 E: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]
Re: Migration and Copypools
If I have defined the following (AIX server, ADSM 3.1): Primary Pool: Arcpool1 Copy Pool:Backuppool1 NextStgpool: Arcpool2 Copy Pool:Backuppool2 Arcpool1 is backed up to Backuppool1. Arcpool2 is the next storage pool, and is backed up to Backuppool2. If I migrate all the data in Arcpool1 to Arcpool2, do the files in Backuppool1 expire? Or do the files get backed up into the second pool, duplicating the data again? If you migrate the data in Arcpool1 to Arcpool2, the files in Backuppool1 do NOT expire. And if you then do a BACKUP STGPOOL from Arcpool2 to Backuppool2, then you are making a SECOND copy pool of your data. Think of it this way: The purpose of the copy pool is make a copy of ALL your primary data, whether it has migrated into your NextStgpool yet or not. What you should do, when you are ready to run your BACKUP STGPOOL, is run it twice: backup stgpool arcpool1 backuppool2 backup stgpool arcpool2 backuppool2 Backup stgpool is incremental; so when you run these commands TSM checks to see if there is any data in arcpool1 that is not ALREADY in backuppool2 and copies it; then does the same with arcpool2. So you don't have to worry about missing any data if you have an extra heavy load one day, and migration from arcpool1 to arcpool2 kicks in before you have a chance to do the backup stgpool to backuppool2. Running both commands makes sure ALL your data is covered in backuppool2. (On the other hand, if all the data is is ALREADY in arcpool2, nothing happens, so you don't get multiple copies of the same data in the same copy pool. TSM is smart that way!) And to get rid of your unneeded copy pool: FIRST run the two commands above to make SURE you have everything represented in backuppool2. Then for EACH VOLUME in backupool1, enter the command: DELETE VOLUME xx DISCARDDATA=YES. (You can do it from the command line or the admin interface, whatever.) That will purge the DB entries for all the data in THAT copy pool, and return all the tapes to 0% used. Then you can just delete the copy pool definition. Hope that helps. Wanda Prather The Johns Hopkins Applied Physics Lab 443-778-8769 [EMAIL PROTECTED] Intelligence has much less practical application than you'd think - Scott Adams/Dilbert
Where Can I Download TDP for Exchange?
Hi all... I need the latest TDP for Exchange version (2.2), but I it is not in tivoli.com. Please, I need a url to download it. Saludos... Jorge Rodrmguez Caracas - Venezuela _ Join the world s largest e-mail service with MSN Hotmail. http://www.hotmail.com
Re: Does the TSM client send the password in clear text ??!
I don't think so, I think it works like Kerberos, where you connect to the server, agree on some hash, then apply that hash to your password, sending only the hashed text as your password. Of course, if it's BASE64 encoded or similar, it may as well be clear text... - Ed Anderson Unix Systems Administrator University of Mississippi Medical Center [EMAIL PROTECTED]
Re: Where Can I Download TDP for Exchange?
TDP's aren't downloadable. You need the CD. Gerald Wichmann 650-625-0436 -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]] On Behalf Of Jorge Rodriguez Sent: Monday, February 04, 2002 10:46 AM To: [EMAIL PROTECTED] Subject: Where Can I Download TDP for Exchange? Hi all... I need the latest TDP for Exchange version (2.2), but I it is not in tivoli.com. Please, I need a url to download it. Saludos... Jorge Rodrmguez Caracas - Venezuela _ Join the world s largest e-mail service with MSN Hotmail. http://www.hotmail.com
Re: Where Can I Download TDP for Exchange?
Hi all... I need the latest TDP for Exchange version (2.2), but I it is not in tivoli.com. Please, I need a url to download it. Jorge, In regards to TDP for Exchange, version 2.2... The GA version is the latest version, i.e. 2.2.0. There is no service for that version right now and thus there is no version available for download. (Unlike the BA client, the TDPs are separately priced and you cannot download the paid in full versions, only service.) If you install from the Paid license CD that you received when you ordered the product, you will have the latest version (i.e. 2.2.0). Thanks, Del Del Hoobler IBM Corporation [EMAIL PROTECTED] Celebrate we will. Life is short but sweet for certain... -- Dave
Re: Where Can I Download TDP for Exchange?
Hello Saludos, here is the ftp site I get my clients from. ftp://ftp.software.ibm.com/storage/tivoli-storage-management/maintenance/ Regards, James W. Brents Jr. Technical Specialist Valero Energy Corporation Phone: 210-592-4441 Email: [EMAIL PROTECTED] -Original Message- From: Jorge Rodriguez [mailto:[EMAIL PROTECTED]] Sent: Monday, February 04, 2002 12:46 PM To: [EMAIL PROTECTED] Subject: Where Can I Download TDP for Exchange? Hi all... I need the latest TDP for Exchange version (2.2), but I it is not in tivoli.com. Please, I need a url to download it. Saludos... Jorge Rodrmguez Caracas - Venezuela _ Join the world s largest e-mail service with MSN Hotmail. http://www.hotmail.com
TSM Authentication
TSM does not send client passwords in the clear. Here's the text from the TSM concepts redbook. Because the storage repository of Tivoli Storage Manager is the place where all the data of an enterprise are stored and managed, security is a very vital aspect for Tivoli Storage Manager. To ensure that data can only be accessed from the owning client or an authorized party, Tivoli Storage Manager implements, for authentication purposes, a mutual suspicion algorithm, which is similar to the methods used by Kerberos authentication. Whenever a client (backup/archive or administrative) wants to communicate with the server, an authentication has to take place. This authentication contains both-sides verification, which means that the client has to authenticate itself to the server, and the server has to authenticate itself to the client. To do this, all clients have a password, which is stored at the server side as well as at the client side. In the authentication dialog these passwords are used to encrypt the communication. The passwords are not sent over the network, to prevent hackers from intercepting them. A communication session will be established only if both sides are able to decrypt the dialog. If the communication has ended, or if a timeout period without activity is passed, the session will be automatically terminated and a new authentication will be necessary. _ William Mansfield Senior Consultant Solution Technology, Inc 630 718 4238
Are Novell file and directory rights are restored by TSM 4.2.x?
I'm sure this has been asked before, but here goes: Does TSM back up (and therefore restore) the user rights of a Novell 5 volume? Is there an option to activate this or is it default behavior? If I restore the files to a new server (i.e. not to the one I orginally backed from) will the rights follow? Thanks for the help Etienne Brodeur
Re: TSM Restore Using 349X lib failes.
Did you install all the 3494/3590 support software/drivers for AIX? -Original Message- From: Ilja G. Coolen [mailto:[EMAIL PROTECTED]] Sent: Monday, February 04, 2002 4:14 AM To: [EMAIL PROTECTED] Subject: TSM Restore Using 349X lib failes. Hello you guru's. Last weekend we did a migration to a new AIX/box with our TSM 4.2.1.9 server. Everthing was configured, installed. We were unable to test the 3494 library 'cause it was attached to the production environment, and we had no spare available at the location. This is what we did. SOURCE RS/6000 - S70 AIX 4.3.3 TSM 4.2.1.9 1 x 3494 7 x SCSI 3590E 1 x ESS ( 2 x Fibre Channel point to point) TARGET -- RS/6000 - H80 ( New BOX) AIX 4.3.3 ( Cleanly Installed ) TSM 4.2.1.9( Cleanly Installed ) 1 x 3494 (Moved from source) 7 x SCSI 3590E (Moved from source) Seperate ESS ( 2 x Fibre Channel point to point) Library definitions: define library libm libt=349x devi=/dev/magstar (lmcp0) define dev 3590 devt=3590 format=drive mountl=drives define drive libm drive dev=/dev/rmt1 We did these actions before on disaster recovery tests, and it worked fine all the time. BUT NOW, we have preconfigured the whole environment, and started a restore db. We got the message that the library type did not support this action. We defined all settings like we always did. We needed to define a manual tape library to do the restore. Automated restore db's used to work fine. How come it doesn't work now? Could this be a bug? Or did we make a mistake after all? Ilja G. Coolen _ ABP / USZO CIS / BS / TB / Storage Management Telefoon : +31(0)45 579 7938 Fax : +31(0)45 579 3990 Email: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] Intranet : Storage http://intranet/cis_bstb/html_content/sm/index_sm.htm Web _ - Everybody has a photographic memory, some just don't have film. -
Re: 9840 element addresses.
Information on element addresses for STK L700 is available @ http://www.tivoli.com/support/storage_mgr/devices/atab94.htm Jason Morgan [EMAIL PROTECTED]To: [EMAIL PROTECTED] cc: Sent by: ADSM: Subject: Re: 9840 element addresses. Dist Stor Manager [EMAIL PROTECTED] .EDU 02/04/2002 08:48 AM Please respond to ADSM: Dist Stor Manager Would drive element address 500 be drive 0 or drive 6 ? Regards Jason Daniel Sparrman [EMAIL PROTECTED]@VM.MARIST.EDU on 04/02/2002 14:52:26 Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Re: 9840 element addresses. Hi The 9840:s should be placed top down... and the first element adress is 500. For six drives it should look like this from the top of the drive bays: 1st drive 500 2nd drive 501 3rd drive 502 4th drive 503 5th drive 504 6th drive 505 7th empty 8th empty 9th empty 10th empty 11th empty 12th empty The only difference if you have a L700e is that it can hold more drives, and that the element address is between 500-519. Best Regards Daniel Sparrman --- Daniel Sparrman Exist i Stockholm AB Bergkällavägen 31D 192 79 SOLLENTUNA Växel: 08 - 754 98 00 Mobil: 070 - 399 27 51 Jason Morgan jmorga31@CSCTo: [EMAIL PROTECTED] .COMcc: Sent by: Subject: 9840 element addresses. ADSM: Dist Stor Manager [EMAIL PROTECTED] RIST.EDU 2002-02-04 15:49 Please respond to ADSM: Dist Stor Manager Hi, Would any one be able to confirm what the element addresses for 6 9840 drives in an L700 would be. ? Regards Jason
Domino TDP
*SMers and Del Hoobler, I need to delete some object from a Domino TDP backup. When I select * from backup etc. I am able to find the OBJECT_IDs for the objects that need deleting. Then to find the tape volume : tsm: DSMSERV3show bfobj O 190937586 Bitfile Object: 0.190937586 Bitfile Object NOT found. However: tsm: DSMSERV3show invo 0 190937586 OBJECT: 0.190937586 (Backup): Node: DOMINOMAIL Filespace: DominoMail.DOMDBS. \MAIL\ 123456.NSF Type: 2 CG: 1 Size: 0.0 HeaderSize: 0 BACKUP OBJECTS ENTRY: State: 1 Type: 2 MC: 1 CG: 1 DominoMail.DOMDBS : \MAIL\ 090178.NSF (MC: DEFAULT) Active, Inserted 02/03/02 01:12:54 EXPIRING OBJECTS ENTRY: Expiring object entry not found. Is it indeed true that there is no bitfile object, as the query inventory indicates the size of this object id is 0.0? Or does TDP store the bitfile object in a container somewhere that I am not looking? Q OCC shows this particular node has 900 files in 170 Gigabytes. Thanks. John Bremer
Migration from ADSM v2.1 (OS/2) to TSM 4.2 (?)
We are still using an ADSM v2.1.16 for OS/2 server. I just realized that end of service was 12/31/01. There was no upgrade for 2.1 on OS/2. We need to migrate to a newer version. It appears there is not a TSM Server for Linux. Is one expected? If we chose to migrate to v4.2 on Windows, does anyone know if are tape pools (created with 2.1 server on os/2) will be usable by the 4.2 server? Is there any documentation on migration? Thanks, Darren
Luuk Kleibrink/D903513/IS/DLVG is niet op zijn/haar kantoor.
Ik ben niet op kantoor vanaf 04-02-2002 tot 06-02-2002.
