q backup
I am trying to perform a restore from a remote node without success. I am running the command res -fromnode=server1 t:\ e:\(restore location) -subdir=yes -repl=no I keep getting the msg no files backed up for t:\. Yet when I issue q backup t:\ on server1 I get a list of files backed up but only the ones backed up using the GUI. I don't see a list of files backed up when I used WINAT to schedule the job. Does anyone have any insight into how this can be resolved. Many Thanks Toni
TSM 4.1.2, SUN Solaris, StorEdge L20
Hi all, can anybody help me with following problem: TSM device driver (lb) cannot identify library contrloler on tape library SUN StorEdge L20 (2 drives, 20 tapes). TSM tape device driver (mt) works fine on both DLT 7000 drives. Veritas NetBackup BusinesServer 3.3 software installed on the same machine uses library robot and drives without failures. CONFIGURATION: Hardware: SUN Ultra5, 256MB RAM, 16GB HDD SUN StorEdge L20, 2x DLT7000 Software: Solaris 2.7, 64bit TSM server 4.1.2 Thank you. Viliam Varga
Re: ADSM and Legato compatibility
Thanks Ray for the information. I will bear that in mind. -Original Message- From: Ray Pratts [SMTP:[EMAIL PROTECTED]] Sent: Friday, January 12, 2001 10:06 PM To: [EMAIL PROTECTED] Subject: Re: ADSM and Legato compatibility My memory is of a project about three years ago. A client was migrating from Legato to ADSM and left Legato on the systems for a while, until they got used to ADSM. What I remenber is, Legato changed attribute flags every time it ran, this caused ADSM to backup files which had not actually changed. It's been a while, but I seem to remember that ADSM back everything up after each Legato backup because "Sharp, Neil (London)" wrote: Does anybody have any experience of running ADSM and Legato concurrently on a RS6000 running AIX? I have already thought about the contention issues with the drives and the processor. What I need to know about is there any known issues with the O/S? Thanks for your time Neil Sharp Merrill Lynch ADSM/TSM Administrator Work : 020-7573-0469 Mobile : 07769-741612 Pager : 01893-038277 e-mail : [EMAIL PROTECTED]
Re: Restoring a 3.7.3 database to a 4.1.2 server
Hi John, Does not work like that on an upgrade. You do not restore the database, unlless you are are aborting the upgrade and going back to your old version. You would just start with the "upgradedb" parameter. Simple process, should all be explained in the quick start manual you should get with your software upgrade. John O'Neall [EMAIL PROTECTED] on 01/13/2001 07:34:41 AM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc:(bcc: John Naylor/HAV/SSE) Subject: Re: Restoring a 3.7.3 database to a 4.1.2 server Am I missing something? Is there some doubt that one can restore a backed-up, say, ADSM 3.1.2 data base to TSM 4.1? That would be catastrophic for us! How else could we migrate? John O'Neall -- Centre de Calcul de l'IN2P3 "Kelly J. Lipp" wrote: I think it will work. Give it a whirl. What have you got to lose? Kelly J. Lipp Storage Solutions Specialists, Inc. PO Box 51313 Colorado Springs CO 80949-1313 (719) 531-5926 Fax: (240) 539-7175 Email: [EMAIL PROTECTED] or [EMAIL PROTECTED] www.storsol.com www.storserver.com -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Jerry Caupain Sent: Friday, January 12, 2001 4:01 AM To: [EMAIL PROTECTED] Subject: Restoring a 3.7.3 database to a 4.1.2 server Hello everyone. I have a TSM 3.7.3 database backup and I want to restore thaht backup to a 4.1.2 server. Is this possible? I want to do this because I don't have the 3.7. software on CD anymore. Thanx, Jerry Caupain ** The information in this E-Mail is confidential and may be legally privileged. It may not represent the views of Scottish and Southern Energy plc. It is intended solely for the addressees. Access to this E-Mail by anyone else is unauthorised. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. Any unauthorised recipient should advise the sender immediately of the error in transmission. Scottish Hydro-Electric and Southern Electric are trading names of Scottish and Southern Energy Group. **
No Subject
I'm wondering if anyone has successfully restored using RMAN from a different TSM server. One of our DBA's is attempting to do this. Environment :- Oracle 8.1.6. TDP for Oracle V.2.1.9 (no we wont use V2.1.10 because it core dumps on any TSM client with cloptsets). TSM server version 4.1.2.0 Solaris 2.07 The scenario is as follows : - Location A contains TSM server xx . Oracle DB yy and DMSO_NODE zz So yy backs up to server xx , via TSM client zz ( using dsm.optora to point to server xx in the dsm.sys file) Location B contain TSM server aa. Oracle DB bb and DSMO_NODE cc aa backs up to server bb , via TSM client cc ( using dsm.optora to point to server cc in the dsm.sys file) To restore yy to Node in Location B, my intention for him (DBA) is to :- export DSMO_NODE=zz (as known in location A) export DSMI_CONFIG=/home/oracle/dsm.optorarest This opt file points to server xx (location A) in dsm.sys stanza. We've set up TDPO.zz password file. Will this work or, is there anything else required? We want to get a handle on this to perform cross server/cross client restores, as we have a local TSM server per tech suite (of which there are several), and DBA's want to restore Oracle DB's between locations for BCP purposes. LONDON Tel: +44(0) 207 547 4917 Fax+44(0) 207 650 7917 Mobile+44(0) 468 361-885 email:[EMAIL PROTECTED] -- 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 destroy this e-mail. Any unauthorised copying, disclosure or distribution of the material in this e-mail is strictly forbidden.
TDP for ORACLE restores
Sorry, a subject might help... -- Forwarded by Bruce Mitchell on 15/01/2001 09:47 --- From: Bruce Mitchell on 15/01/2001 09:39 To: [EMAIL PROTECTED] cc: Subject: I'm wondering if anyone has successfully restored using RMAN from a different TSM server. One of our DBA's is attempting to do this. Environment :- Oracle 8.1.6. TDP for Oracle V.2.1.9 (no we wont use V2.1.10 because it core dumps on any TSM client with cloptsets). TSM server version 4.1.2.0 Solaris 2.07 The scenario is as follows : - Location A contains TSM server xx . Oracle DB yy and DMSO_NODE zz So yy backs up to server xx , via TSM client zz ( using dsm.optora to point to server xx in the dsm.sys file) Location B contain TSM server aa. Oracle DB bb and DSMO_NODE cc aa backs up to server bb , via TSM client cc ( using dsm.optora to point to server cc in the dsm.sys file) To restore yy to Node in Location B, my intention for him (DBA) is to :- export DSMO_NODE=zz (as known in location A) export DSMI_CONFIG=/home/oracle/dsm.optorarest This opt file points to server xx (location A) in dsm.sys stanza. We've set up TDPO.zz password file. Will this work or, is there anything else required? We want to get a handle on this to perform cross server/cross client restores, as we have a local TSM server per tech suite (of which there are several), and DBA's want to restore Oracle DB's between locations for BCP purposes. LONDON Tel: +44(0) 207 547 4917 Fax+44(0) 207 650 7917 Mobile+44(0) 468 361-885 email:[EMAIL PROTECTED] -- 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 destroy this e-mail. Any unauthorised copying, disclosure or distribution of the material in this e-mail is strictly forbidden.
q backup 2
I am trying to perform a restore from a remote node without success.
I am running the command res -fromnode=server1 t:\ e:\(restore location)
-subdir=yes -repl=no
I then tried res -fromnode=server1 {"\\server1\d$\"}\* -subdir=yes -repl=no
I keep getting the msg no files backed up for t:\. Yet when I issue q backup t:\
on server1 I get a list of files backed up but only the ones backed up using the
GUI. I don't see a list of files backed up when I used WINAT to schedule the
job.
Does anyone have any insight into how this can be resolved.
Many Thanks
Forgot to say, I am working on an NT box.
Toni
Re: backup 2
Managed to figure it out. Used nodename. Toni
volhist file
Hello all, I am running TSM 3.7.3.8 on AIX 4.3.3. In looking at my volhist.txt file I noticed it is rather large. After further inspection I see that all the volume history is stored in this file back to the day when we first turned ADSM. Most of this data is useless. Is there a setting or a way to clear this file? Thanks in advance. Ray Baughman Engineering Systems Administrator TSM Administrator National Machinery Co. Phone: 419-443-2257 Fax: 419-443-2376 Email: [EMAIL PROTECTED]
Re: volhist file
Ray Use 'del volhist' command I hope that this helps -Original Message- From: Ray Baughman [SMTP:[EMAIL PROTECTED]] Sent: Monday, January 15, 2001 1:21 PM To: [EMAIL PROTECTED] Subject: volhist file Hello all, I am running TSM 3.7.3.8 on AIX 4.3.3. In looking at my volhist.txt file I noticed it is rather large. After further inspection I see that all the volume history is stored in this file back to the day when we first turned ADSM. Most of this data is useless. Is there a setting or a way to clear this file? Thanks in advance. Ray Baughman Engineering Systems Administrator TSM Administrator National Machinery Co. Phone: 419-443-2257 Fax: 419-443-2376 Email: [EMAIL PROTECTED]
Anthony S Colletti/Poughkeepsie/IBM is out of the office.
I will be out of the office starting January 15, 2001 and will not return until January 18, 2001. I will be out of the office beginning Monday, January 15, 2001 and Returning to the office on Thursday, January 18,2001.. Please contact my backup Indy Parmar at Tie Line 351 1913for immediate assistance
Re: volhist file
Hi Ray! Checkout the DELETE VOLHIST command. Kindest regards, Eric van Loon -Original Message- From: Ray Baughman [mailto:[EMAIL PROTECTED]] Sent: Monday, January 15, 2001 14:21 To: [EMAIL PROTECTED] Subject: volhist file Hello all, I am running TSM 3.7.3.8 on AIX 4.3.3. In looking at my volhist.txt file I noticed it is rather large. After further inspection I see that all the volume history is stored in this file back to the day when we first turned ADSM. Most of this data is useless. Is there a setting or a way to clear this file? Thanks in advance. Ray Baughman Engineering Systems Administrator TSM Administrator National Machinery Co. Phone: 419-443-2257 Fax: 419-443-2376 Email: [EMAIL PROTECTED] ** This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. **
Howto resolve ANR2362E without rebooting the server?
Hi all, due to missing DB backups, our recovery log exeeded 95%. As a result, some records of the log got compressed, which prevent a DB backup to occur. The process stops with the following error: ANR2362E command: DATABASE BACKUP IS NOT CURRENTLY POSSIBLE - COMPRESSED LOG RECORDS EXIST IN THE CURRENT TRANSACTION CHECKPOINT. Regarding the help, I should issue the command at a later time, however I was waiting for hours, and had to increase the log to prevent the server from crashing; but the only way to perform a DB backup was: Rebooting the server: Does anybody know a way to force the backup, or may be a way to "uncompress" the compressed part after adding some space to the log? We are (still) using ADSM 3.1.2.20 on AIX 4.2.1.0. Thanks in advanced.
Re: q backup
use virtualnodename .. shekhar Toni Banire [EMAIL PROTECTED]@VM.MARIST.EDU on 01/15/2001 03:49:31 AM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] Sent by: "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: q backup I am trying to perform a restore from a remote node without success. I am running the command res -fromnode=server1 t:\ e:\(restore location) -subdir=yes -repl=no I keep getting the msg no files backed up for t:\. Yet when I issue q backup t:\ on server1 I get a list of files backed up but only the ones backed up using the GUI. I don't see a list of files backed up when I used WINAT to schedule the job. Does anyone have any insight into how this can be resolved. Many Thanks Toni $RFC822.eml
Re: Restoring a 3.7.3 database to a 4.1.2 server
"Braich, Raminder" wrote: John, Here is an interesting scenario. What if you took the database backup of 3.7, something bad happened and you had to blow away the server, say you reloaded WIN NT on the server. What an awful thought. ;-) Now you upgrade to 4.1.2 and try to restore 3.7 database, it does not work. It would work perhaps if you have 3.7 CD and load it first and then do an upgrade and then migrate the database. I dont see any workaround if you do not have the 3.7 CD. That's just it: I don't have it. I ordered 4.1 directly! But thanks for your comments. I find this situation exceptionally (even for IBM, or Tivoli, or whoever) time-consuming. Our method of upgrading has always been to install the new version on a new machine, test it thoroughly, then to backup the DB on the old machine and restore it on the new one. This has the _enormous_ advantage that if anything goes wrong, we have only to turn the old machine back on and we're in business again, with a minimal loss of time. If now we can no longer do this, but must updgrade ADSM/TSM itself directly on the production machine, it can _only_ take longer, especially if we are obliged to return to the original system. This is _not_ what I consider a Good Thing! D#*n. John -Original Message- From: John Naylor [SMTP:[EMAIL PROTECTED]] Sent: Monday, January 15, 2001 4:20 AM To: [EMAIL PROTECTED] Subject: Re: Restoring a 3.7.3 database to a 4.1.2 server Hi John, Does not work like that on an upgrade. You do not restore the database, unlless you are are aborting the upgrade and going back to your old version. You would just start with the "upgradedb" parameter. Simple process, should all be explained in the quick start manual you should get with your software upgrade. -- | John O'Neall | | | Centre de Calcul de l'IN2P3 | tel: +33 (0)4 78 93 08 80 | | Villeurbanne, France | fax: +33 (0)4 72 69 41 70 |
Re: Restoring a 3.7.3 database to a 4.1.2 server
John, Here is an interesting scenario. What if you took the database backup of 3.7, something bad happened and you had to blow away the server, say you reloaded WIN NT on the server. Now you upgrade to 4.1.2 and try to restore 3.7 database, it does not work. It would work perhaps if you have 3.7 CD and load it first and then do an upgrade and then migrate the database. I dont see any workaround if you do not have the 3.7 CD. -Original Message- From: John Naylor [SMTP:[EMAIL PROTECTED]] Sent: Monday, January 15, 2001 4:20 AM To: [EMAIL PROTECTED] Subject: Re: Restoring a 3.7.3 database to a 4.1.2 server Hi John, Does not work like that on an upgrade. You do not restore the database, unlless you are are aborting the upgrade and going back to your old version. You would just start with the "upgradedb" parameter. Simple process, should all be explained in the quick start manual you should get with your software upgrade. John O'Neall [EMAIL PROTECTED] on 01/13/2001 07:34:41 AM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc:(bcc: John Naylor/HAV/SSE) Subject: Re: Restoring a 3.7.3 database to a 4.1.2 server Am I missing something? Is there some doubt that one can restore a backed-up, say, ADSM 3.1.2 data base to TSM 4.1? That would be catastrophic for us! How else could we migrate? John O'Neall -- Centre de Calcul de l'IN2P3 "Kelly J. Lipp" wrote: I think it will work. Give it a whirl. What have you got to lose? Kelly J. Lipp Storage Solutions Specialists, Inc. PO Box 51313 Colorado Springs CO 80949-1313 (719) 531-5926 Fax: (240) 539-7175 Email: [EMAIL PROTECTED] or [EMAIL PROTECTED] www.storsol.com www.storserver.com -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Jerry Caupain Sent: Friday, January 12, 2001 4:01 AM To: [EMAIL PROTECTED] Subject: Restoring a 3.7.3 database to a 4.1.2 server Hello everyone. I have a TSM 3.7.3 database backup and I want to restore thaht backup to a 4.1.2 server. Is this possible? I want to do this because I don't have the 3.7. software on CD anymore. Thanx, Jerry Caupain ** The information in this E-Mail is confidential and may be legally privileged. It may not represent the views of Scottish and Southern Energy plc. It is intended solely for the addressees. Access to this E-Mail by anyone else is unauthorised. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. Any unauthorised recipient should advise the sender immediately of the error in transmission. Scottish Hydro-Electric and Southern Electric are trading names of Scottish and Southern Energy Group. **
st.conf TSM device driver
System: Solaris 2.6 / TSM 3.7.3.0 Should I set the parameters for the tape drives in the st.conf file? Have the parameters in the st.conf any effects for the TSM device drivers? Thanks. Dave - Get personalized e-mail and a web address or your own free e-mail at http://www.networksolutions.com.
Re: deleting rman data
You should verify the state of the objects. After the deletion of the files via RMAN the state should change from active to inactive. Be sure your RetO value is set to 0 otherwise the files will be kept for some time depending your settings in the managementclass. When the files become inactive, the retention is set to 0 and the expiration on the server has run the files should disappear. Hope this helps, Michel "James healy" [EMAIL PROTECTED] on 01/12/2001 10:49:32 PM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc:(bcc: Michel Engels/BE/Devoteam) Subject: deleting rman data i have a question about verifying the deletion of rman data. i'd like to know how anyone verifies that old versions of rman files are getting deleted. My DBAs say they are running the commands to expire old versions but I don't see it happening Are there any commands that I could erify this with. I've checked q occ and the number of files does not decrease for that rman client.
Re: Restoring a 3.7.3 database to a 4.1.2 server
...Our method of upgrading has always been to install the new version on a new machine, test it thoroughly, then to backup the DB on the old machine and restore it on the new one. This has the _enormous_ advantage that if anything goes wrong, we have only to turn the old machine back on and we're in business again, with a minimal loss of time. John - Proceeding carefully on a new machine is an excellent approach. Given that the approach requires the same amount of db,log space on both systems, an alternative to TSM db backup/restore would be to configure the db,log space on the two systems to be equivalent, and then do a physical copy of the db,log space to the other system, where the dsmserv start-up on the new machine will upgrade the db. This should be much faster than a logical db backup/restore, and a 3.7 CD would not be an issue. Richard Sims, BU
Re: Restoring a 3.7.3 database to a 4.1.2 server
Dear John, If you need the 3.7 version you could try to get the demo version. For as far as I know it is fully functional but expires. You could try to load the demo version furst and then upgrade to 4.1. The only problem I see in this is that it may take some time to get the demo version. With regards, Wolter van de Kolk -Oorspronkelijk bericht- Van: John O'Neall [mailto:[EMAIL PROTECTED]] Verzonden: maandag 15 januari 2001 15:16 Aan: [EMAIL PROTECTED] Onderwerp: Re: Restoring a 3.7.3 database to a 4.1.2 server "Braich, Raminder" wrote: John, Here is an interesting scenario. What if you took the database backup of 3.7, something bad happened and you had to blow away the server, say you reloaded WIN NT on the server. What an awful thought. ;-) Now you upgrade to 4.1.2 and try to restore 3.7 database, it does not work. It would work perhaps if you have 3.7 CD and load it first and then do an upgrade and then migrate the database. I dont see any workaround if you do not have the 3.7 CD. That's just it: I don't have it. I ordered 4.1 directly! But thanks for your comments. I find this situation exceptionally (even for IBM, or Tivoli, or whoever) time-consuming. Our method of upgrading has always been to install the new version on a new machine, test it thoroughly, then to backup the DB on the old machine and restore it on the new one. This has the _enormous_ advantage that if anything goes wrong, we have only to turn the old machine back on and we're in business again, with a minimal loss of time. If now we can no longer do this, but must updgrade ADSM/TSM itself directly on the production machine, it can _only_ take longer, especially if we are obliged to return to the original system. This is _not_ what I consider a Good Thing! D#*n. John -Original Message- From: John Naylor [SMTP:[EMAIL PROTECTED]] Sent: Monday, January 15, 2001 4:20 AM To: [EMAIL PROTECTED] Subject: Re: Restoring a 3.7.3 database to a 4.1.2 server Hi John, Does not work like that on an upgrade. You do not restore the database, unlless you are are aborting the upgrade and going back to your old version. You would just start with the "upgradedb" parameter. Simple process, should all be explained in the quick start manual you should get with your software upgrade. -- | John O'Neall | | | Centre de Calcul de l'IN2P3 | tel: +33 (0)4 78 93 08 80 | | Villeurbanne, France | fax: +33 (0)4 72 69 41 70 |
Re: Restoring a 3.7.3 database to a 4.1.2 server
Now _there_ is a good idea. Thanks once again, Richard. John Richard Sims wrote: ...Our method of upgrading has always been to install the new version on a new machine, test it thoroughly, then to backup the DB on the old machine and restore it on the new one. This has the _enormous_ advantage that if anything goes wrong, we have only to turn the old machine back on and we're in business again, with a minimal loss of time. John - Proceeding carefully on a new machine is an excellent approach. Given that the approach requires the same amount of db,log space on both systems, an alternative to TSM db backup/restore would be to configure the db,log space on the two systems to be equivalent, and then do a physical copy of the db,log space to the other system, where the dsmserv start-up on the new machine will upgrade the db. This should be much faster than a logical db backup/restore, and a 3.7 CD would not be an issue. Richard Sims, BU -- | John O'Neall | | | Centre de Calcul de l'IN2P3 | tel: +33 (0)4 78 93 08 80 | | Villeurbanne, France | fax: +33 (0)4 72 69 41 70 |
TSM and LTO
Hi, does anybody know when TSM (on Unix) or LegatoNetworker comes with LTO-Support? (Ultrium)drives and (Exabyte or StorageTek) autoloader and libraries. mfg / regards andreas rensch / rz-qs tel : +49(0)6171 66 3692 / fax : +49(0)6171 66 7500 3692 / mobil : +49(0)172 6649 016 / mailto:[EMAIL PROTECTED] Alte Leipziger Lebensversicherung aG - Alte Leipziger Platz 1 - D 61440 Oberursel - http://www.alte-leipziger.de Two rules for success in life. 1. Don't tell people everything you know. 2.
Re: TSM and LTO
TSM 4.1 has support for IBM LTO drives at least on AIX and NT with the latest Atape driver. -- Shawn Raymond Sr. Technical Consultant Synergy, INC. 518-782-3457 Andreas Rensch RenschA@ALTE-LEITo: [EMAIL PROTECTED] PZIGER.DE cc: Sent by: "ADSM: Subject: TSM and LTO Dist Stor Manager" [EMAIL PROTECTED] .EDU 01/15/01 10:56 AM Please respond to "ADSM: Dist Stor Manager" Hi, does anybody know when TSM (on Unix) or LegatoNetworker comes with LTO-Support? (Ultrium)drives and (Exabyte or StorageTek) autoloader and libraries. mfg / regards andreas rensch / rz-qs tel : +49(0)6171 66 3692 / fax : +49(0)6171 66 7500 3692 / mobil : +49(0)172 6649 016 / mailto:[EMAIL PROTECTED] Alte Leipziger Lebensversicherung aG - Alte Leipziger Platz 1 - D 61440 Oberursel - http://www.alte-leipziger.de Two rules for success in life. 1. Don't tell people everything you know. 2.
tcpwindowsize
Lg In TSM reference the following is stated: "To improve backup performance, increase the TCPWINDOWSIZE on the server." We have installed TSM4.1 Level0.0 on a S/390 Server. But during startup we get the following messages: ANR0902W Unsupported keyword found in file dsmserv.opt. ANR0906I Line No. : 143 ANR0907I Statement : tcpwindowsize 2048 ANR0908W Error : .|.. Is this a valid parameter for S/390 ??? same applies to TCPNODELAY !! Ruud van Ruler, Shell Services International BV - ISES/32 Our Data Storage Management home page: http://sww2.shell.com/os390/ Room 0C/G06 Dokter van Zeelandstraat 1, 2285 BD Leidschendam NL Tel : +31 (0)70 - 3034644, Fax 4011, Mobile +31 (0)6-55127646 Email Internet: [EMAIL PROTECTED] [EMAIL PROTECTED] R.vanRuler
Re: tcpwindowsize
Shouldn't that be in dsm.opt ?
Re: Using FIXEDIOBUFSIZE and TAPEIOBUFS
Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] Sent by:"ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject:Using FIXEDIOBUFSIZE and TAPEIOBUFS Hi Ramon, From my understanding, FIXEDIOBUFSIZE was disabled at the 3.7.4 level and has not been reactivated. DO NOT use that parameter at the 3.7.3.0 level. I haven't used TAPEIOBUFS - so I can't comment on that one. Glen Smith ---Ramon Colet wrote - Hi *Smers, I'm using TSM 3.7.3 in OS/390 2.7. I know there was a problem with the FIXEDIOBUFSIZE parameter but i'm not suer if it was solved and it's safe to use it now. I'm also thinking about using the TAPEIOBUFS to improve my Tape throughput (especially in Backup Storage Pool and Reclamation). Does any of tou have any warnings or advices about it?. Thanks Ramon Colet Aigües de Barcelona __ FREE Personalized Email at Mail.com Sign up at http://www.mail.com/?sr=signup
tivoli os390 4.1.2 license problem
i dont think that i am that blind ,but i can't seem to get the register license command to work like the manal says since upgrading to 4.1.2 from 3.7 on os390. my licenses are not valid, i know that i have to register them but the register command fails.. this is the syntax as described in the admin reference quide REGISTER LIC MANAGEDSYSLAN NUMBER=45 Error message: ANR2020E REGISTER LICENSE: Invalid parameter - MANAGEDSYSLAN. tim brown begin:vcard n:Brown;Tim tel;fax:845-486-5921 tel;work:845-486-5643 x-mozilla-html:FALSE adr:;; version:2.1 email;internet:[EMAIL PROTECTED] title:Systems Specialist x-mozilla-cpt:;9264 fn:Tim Brown end:vcard
Re: tivoli os390 4.1.2 license problem
Hello Tim, I had the same problem. The correct syntax is: REGISTER LIC MANAGEDSYSLAN 45 /Tomas Norberg Tim Brown [EMAIL PROTECTED]@VM.MARIST.EDU on 2001-01-15 19:02:56 Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] Sent by: "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: tivoli os390 4.1.2 license problem i dont think that i am that blind ,but i can't seem to get the register license command to work like the manal says since upgrading to 4.1.2 from 3.7 on os390. my licenses are not valid, i know that i have to register them but the register command fails.. this is the syntax as described in the admin reference quide REGISTER LIC MANAGEDSYSLAN NUMBER=45 Error message: ANR2020E REGISTER LICENSE: Invalid parameter - MANAGEDSYSLAN. tim brown (See attached file: tbrown.vcf) tbrown.vcf
Re: tivoli os390 4.1.2 license problem
Just use REGISTER LIC MANAGEDSYSLAN 45 The syntax was changed after the manuals were published and documented in the readme file. David Bohm TSM server development (520) 799-5082 T/L 321-5082 email - [EMAIL PROTECTED] Tim Brown [EMAIL PROTECTED]@VM.MARIST.EDU on 01/15/2001 11:02:56 AM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] Sent by: "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: tivoli os390 4.1.2 license problem i dont think that i am that blind ,but i can't seem to get the register license command to work like the manal says since upgrading to 4.1.2 from 3.7 on os390. my licenses are not valid, i know that i have to register them but the register command fails.. this is the syntax as described in the admin reference quide REGISTER LIC MANAGEDSYSLAN NUMBER=45 Error message: ANR2020E REGISTER LICENSE: Invalid parameter - MANAGEDSYSLAN. tim brown (See attached file: tbrown.vcf) tbrown.vcf
Multiple client nodes on one AIX server
Hello all, I'm running TSM 3.7.3.8 on AIX 4.3.3. I have a server which I'd like to backup as several different nodes. So far I've had no luck getting more than one node on the server. I've searched the archives with no luck, probably not searching the right keywords. Anyway, can someone lead me to documentation on how this can be accomplished? Thanks in advance. Ray Baughman Engineering Systems Administrator TSM Administrator National Machinery Co. Phone: 419-443-2257 Fax: 419-443-2376 Email: [EMAIL PROTECTED]
Re: Restoring a 3.7.3 database to a 4.1.2 server
Hey everyone, I'm the one who originally posted this subject. I installed 4.1 and applied the 4.1.2 patch. Then I restored the 3.7.2.database. My TSM server would't start. I ran an AUDITDB with FIX=NO and got the following message: ANR6646I AUDITDB: Auditing disaster recovery manager definitions. ANR4210I AUDITDB: Auditing physical volume repository definitions. ANRD tb.c(775): Column count mismatch for table MMS.Drives - expected 21, found 16 ANR0101E pvraudit.c(233): Error 18 opening table "MMS.Drives". ANR4142I AUDITDB: Database audit process terminated in error. I then tried the FIX=YES option and it still didn't work. As a last resort I did a DSMSERV UPGRADEDB.. It works fine now!! Thanx everyone, Jerry Caupain [EMAIL PROTECTED] 01/15/01 04:25pm Now _there_ is a good idea. Thanks once again, Richard. John Richard Sims wrote: ...Our method of upgrading has always been to install the new version on a new machine, test it thoroughly, then to backup the DB on the old machine and restore it on the new one. This has the _enormous_ advantage that if anything goes wrong, we have only to turn the old machine back on and we're in business again, with a minimal loss of time. John - Proceeding carefully on a new machine is an excellent approach. Given that the approach requires the same amount of db,log space on both systems, an alternative to TSM db backup/restore would be to configure the db,log space on the two systems to be equivalent, and then do a physical copy of the db,log space to the other system, where the dsmserv start-up on the new machine will upgrade the db. This should be much faster than a logical db backup/restore, and a 3.7 CD would not be an issue. Richard Sims, BU -- | John O'Neall | | | Centre de Calcul de l'IN2P3 | tel: +33 (0)4 78 93 08 80 | | Villeurbanne, France | fax: +33 (0)4 72 69 41 70 |
Re: q backup
Keep in mind that drive letters c: d: e: get converted to UNC naming convention. For example you have Server1 that has done backups of the t: drive. On the TSM server you will get a filespace of \\Server1\t$ for example. Now you go to a machine called Restore2. You try to restore the t: drive of Server1 to the c: drive of Restore2. If you execute the command restore t:\dir c:\dir this gets translated to restore \\Restore2\t$ \\Restore2\c$, so what you really need to do is specify explicitly the UNC naming. Restore \\Server1\t$ \\Restore2\c$. James ThompsonA From: Shekhar Dhotre <[EMAIL PROTECTED]> Reply-To: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: Re: q backup Date: Mon, 15 Jan 2001 09:00:29 -0500 use virtualnodename .. shekhar Toni Banire <[EMAIL PROTECTED]>@VM.MARIST.EDU on 01/15/2001 03:49:31 AM Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Subject: q backup I am trying to perform a restore from a remote node without success. I am running the command res -fromnode=server1 t:\ e:\(restore location) -subdir=yes -repl=no I keep getting the msg no files backed up for t:\. Yet when I issue q backup t:\ on server1 I get a list of files backed up but only the ones backed up using the GUI. I don't see a list of files backed up when I used WINAT to schedule the job. Does anyone have any insight into how this can be resolved. Many Thanks Toni $RFC822.eml Get your FREE download of MSN Explorer at http://explorer.msn.com
Skip files on backup restore
With the 3.1 back/rest client there was a "skip" button that was handy for skipping files as the process was running. Does this feature not exist with 3.7 or 4.1 GUI, or am I just unable to find it. When in the GUI the skip button is discussed under help. Thanks, Rod Hroblak __ Do You Yahoo!? Get email at your own domain with Yahoo! Mail. http://personal.mail.yahoo.com/
Re: TDP for ORACLE restores
Hi Bruce, I believe that is all, Our DBAs have done this before. Have you got a problem ? Regards Stephen Mackereth -Original Message- From: Bruce Mitchell [mailto:[EMAIL PROTECTED]] Sent: Monday, 15 January 2001 20:47 To: [EMAIL PROTECTED] Subject: TDP for ORACLE restores Sorry, a subject might help... -- Forwarded by Bruce Mitchell on 15/01/2001 09:47 --- From: Bruce Mitchell on 15/01/2001 09:39 To: [EMAIL PROTECTED] cc: Subject: I'm wondering if anyone has successfully restored using RMAN from a different TSM server. One of our DBA's is attempting to do this. Environment :- Oracle 8.1.6. TDP for Oracle V.2.1.9 (no we wont use V2.1.10 because it core dumps on any TSM client with cloptsets). TSM server version 4.1.2.0 Solaris 2.07 The scenario is as follows : - Location A contains TSM server xx . Oracle DB yy and DMSO_NODE zz So yy backs up to server xx , via TSM client zz ( using dsm.optora to point to server xx in the dsm.sys file) Location B contain TSM server aa. Oracle DB bb and DSMO_NODE cc aa backs up to server bb , via TSM client cc ( using dsm.optora to point to server cc in the dsm.sys file) To restore yy to Node in Location B, my intention for him (DBA) is to :- export DSMO_NODE=zz (as known in location A) export DSMI_CONFIG=/home/oracle/dsm.optorarest This opt file points to server xx (location A) in dsm.sys stanza. We've set up TDPO.zz password file. Will this work or, is there anything else required? We want to get a handle on this to perform cross server/cross client restores, as we have a local TSM server per tech suite (of which there are several), and DBA's want to restore Oracle DB's between locations for BCP purposes. LONDON Tel: +44(0) 207 547 4917 Fax+44(0) 207 650 7917 Mobile+44(0) 468 361-885 email:[EMAIL PROTECTED] -- 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 destroy this e-mail. Any unauthorised copying, disclosure or distribution of the material in this e-mail is strictly forbidden. This email and any attachments may contain privileged and confidential information and are intended for the named addressee only. If you have received this e-mail in error, please notify the sender and delete this e-mail immediately. Any confidentiality, privilege or copyright is not waived or lost because this e-mail has been sent to you in error. It is your responsibility to check this e-mail and any attachments for viruses.
Re: TSM 4.1.2, SUN Solaris, StorEdge L20
Viliam Varga wrote: TSM device driver (lb) cannot identify library contrloler on tape library SUN StorEdge L20 (2 drives, 20 tapes). TSM tape device driver (mt) works fine on both DLT 7000 drives. Veritas NetBackup BusinesServer 3.3 software installed on the same machine uses library robot and drives without failures. This sounds remarkably similar to the problem I had with my StorageTek L20 - I assume it's the same thing, since the description matches. I was trying to use it with TSM 3.7.3, and it didn't work until I upgraded the code to 3.7.4. (I posted to the list about it at the time, so you should be able to find details in the list archive if you want them.) But the other thing I did was re-install the OS in 32-bit mode. It could be worth a try - and if you contact Tivoli about it, they will very likely suggest doing it. If that doesn't work, my suggestion is to log a call with Tivoli. They made some kind of change between 3.7.3 and 3.7.4 that made it work for me - so it's possible you might need the same change at the 4.1 level. CONFIGURATION: Hardware: SUN Ultra5, 256MB RAM, 16GB HDD SUN StorEdge L20, 2x DLT7000 Software: Solaris 2.7, 64bit TSM server 4.1.2 Thank you. Viliam Varga
Re: Multiple client nodes on one AIX server
Hi Ray, This dsm.sys is from a test solaris box that has multiple clients Client version is 3.7.0 server is aix 3.1.2.50 identical copies of this dsm.sys reside on two boxes (qhsu007 and 8) that are Veritas clustered and the application acc-ora-ottr and its IP address swap between them. It looks like the servername must be different for each stanza, which has security ramifications as the encrypted password is stored under the server name. SErvername QHSU007 nodename qhsu007 COMMmethod TCPip TCPPort1500 TCPServeraddress 10.86.2.155 COMPressionYes PasswordAccess generate errorlogname /var/log/dsmerror.log errorlogretention 7 schedlogname /var/log/dsmsched.log schedlogretention 7 schedmode prompted tcpclientaddress 10.86.4.60 SErvername QHSU008 nodename qhsu008 COMMmethod TCPip TCPPort1500 TCPServeraddress 10.86.2.155 COMPressionYes PasswordAccess generate errorlogname /var/log/dsmerror.log errorlogretention 7 schedlogname /var/log/dsmsched.log schedlogretention 7 schedmode prompted tcpclientaddress 10.86.4.61 * This stanza is used by the second dsmc sched process and the opt * file in /p01/app/tsm/acc-ora-ottr to backup the acceptance ottr * data SErvername ACC-ORA-OTTR nodename acc-ora-ottr COMMmethod TCPip TCPPort1500 TCPServeraddress 10.86.2.155 TCPWIndowsize 1024 COMPressionYes PasswordAccess generate schedmode prompted tcpclientaddress 10.86.4.50 errorlogname /p01/app/tsm/dsmerror.log errorlogretention 7 schedlogname /p01/app/tsm/dsmsched.log schedlogretention 7 postschedulecmd"scp -Q -B /p01/app/tsm/dsmsched.log qhsu009:/dct/tsm/logs/acc-ora-ottr_dsmsched.log" SErvernameQHADSM2O nodename tdo-test COMMmethod TCPip TCPPort1500 TCPServeraddress 10.86.2.155 COMPressionYes PASSWORDAccess prompt include /ottra1/.../* rman include /ottra2/.../* rman Ray Baughman [EMAIL PROTECTED] 16/01/2001 4:40:12 Hello all, I'm running TSM 3.7.3.8 on AIX 4.3.3. I have a server which I'd like to backup as several different nodes. So far I've had no luck getting more than one node on the server. I've searched the archives with no luck, probably not searching the right keywords. Anyway, can someone lead me to documentation on how this can be accomplished? Thanks in advance. Ray Baughman Engineering Systems Administrator TSM Administrator National Machinery Co. Phone: 419-443-2257 Fax: 419-443-2376 Email: [EMAIL PROTECTED]
Re: Running TSM server as a WIN2000 Service
Firstly, review the doc - mainly, readme files for server install and quick start book (on the CD and Tivoli web site). On Win2K, the install procedure should create the service; all you gotta do is configure it (Auto start, run as service, use local system account, etc.) either thru the AdminTools-Services applet, or the TSM Server Utilities. If you're using 4.1 or later, you might need to create the service with dsmcutil; more typically, Server Utilities, initial configuration, helps a lot with addressing this and other issues that arise in a Win2K environment. -Original Message- From: Mary Manthata [mailto:[EMAIL PROTECTED]] Sent: Sunday, January 14, 2001 9:54 PM To: [EMAIL PROTECTED] Subject:Running TSM server as a WIN2000 Service Hi There... Does anyone know how to install and start the TSM server as a WIN2000 Service. I do not intend on using the TSM Server Utilities. I want to put the TSM server initialization into a script. Tks in advance!! GOD Bless Clarence Beukes IT Specialist (Tivoli Certified) Tivoli Storage Manager IBM Intergrated Technology Services Tel : +2711 302 6622 Fax : +2711 302 8806 Mobile : +27 82 745 3852 "A computer is almost human - except that it does not blame its mistakes on another computer. "
Re: TSM and LTO
TSM 4.1 also has support for IBM LTO libraries (3581,3583 and 3584). The next PTF should include the support for a few LTO libraries, i.e. Plasmon FTA, Exabyte 110L, ... --- Shawn Raymond [EMAIL PROTECTED] wrote: TSM 4.1 has support for IBM LTO drives at least on AIX and NT with the latest Atape driver. -- Shawn Raymond Sr. Technical Consultant Synergy, INC. 518-782-3457 Andreas Rensch RenschA@ALTE-LEITo: [EMAIL PROTECTED] PZIGER.DE cc: Sent by: "ADSM: Subject: TSM and LTO Dist Stor Manager" [EMAIL PROTECTED] .EDU 01/15/01 10:56 AM Please respond to "ADSM: Dist Stor Manager" Hi, does anybody know when TSM (on Unix) or LegatoNetworker comes with LTO-Support? (Ultrium)drives and (Exabyte or StorageTek) autoloader and libraries. mfg / regards andreas rensch / rz-qs tel : +49(0)6171 66 3692 / fax : +49(0)6171 66 7500 3692 / mobil : +49(0)172 6649 016 / mailto:[EMAIL PROTECTED] Alte Leipziger Lebensversicherung aG - Alte Leipziger Platz 1 - D 61440 Oberursel - http://www.alte-leipziger.de Two rules for success in life. 1. Don't tell people everything you know. 2. __ Do You Yahoo!? Get email at your own domain with Yahoo! Mail. http://personal.mail.yahoo.com/
Backup Exec
Can Backup Exec be setup in such a way that it sends data off to TSM without having a storage device locally attached to the server it's running on? I.e. TSM handles the backup device (library) as well as manage all the volumes. Any comments will be greatly appreciated Jacques Butcher.
Archiving
Hy everyone, we are discussing the possibilities of archiving data with TSM or other products (from NT,UNIX). Our requirements are to archive data for about 30 years. TSM is in discussion because we use it already for backup ( and in some cases we use the archive-command ). The policy domains for the clients for archiving will be (from my point of view) totally different to those for backup. Can anybody share his good (or bad) experience in long term archiving with whatever kind of library in the background (DVD or tape). Thanks a lot Christoph
