-Protocol violation detected.
Hello all of you ! How do I correct this error :"-Protocol violation detected." I see it in the dsmsched.log of a lot of NT 4.0 servers. And in the actlog. I do not know what to do. Any idears ? Regards Jesper Kjer Denmark
Re: TSM 3.7 Sun Sol Server error
Hello, I also have the same problem. TSM 3.7, Solaris 2.7 on part of an E1, the library is a Sun StorEdge L1000. I've edited the /usr/kernel/drv/mt.conf for the two drives (SCSI id 2, LUN 0 SCSI id 3, LUN 0) and also /usr/kernel/drv/lb.conf for the library (SCSI id 0, LUN 0). add_drv for both mt and lb fail with the same message as Boris. I'm new to both Sun and TSM, so I'd appreciate any help, even something that may seem blatantly obvious to some of you. Michael Gogos Unix Systems Support ANZ Banking Group 227 Toorak Road South Yarra 3141 Victoria, Australia phone: (+613) 9869-6840 fax: (+613) 9869-3447 email: mailto:[EMAIL PROTECTED] -Original Message- From: Boris Feldman (Udi) [mailto:[EMAIL PROTECTED]] Sent: Wednesday, August 09, 2000 4:54 PM To: [EMAIL PROTECTED] Subject: TSM 3.7 Sun Sol Server error Hi All, We are using TSM 3.7 Server on Sun Solaris server (Ultra 60) with AIT2 tapes in QualStar 4440 library. I got the failed installation process (on the mt drive definition point : add_drv ). The error was : the mt drive was successfully added to system but failed to attach. As result of this problem we have not the mt driver files in /dev/rmt/ directory. Any ideas? TNXS. ___ Boris Feldman - Product Manager IBM Storage TSM UDI Millenium Ltd. 1G Yoni Netanyahu Str. Or-Yehuda 60256, ISRAEL Tel : (972)-3-5333555 ext. 357 Fax : (972)-3-5333676 Mobile : (972)-54-929357 E-mail [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] ___
Re: ADSM JOB POSTINGS??
Yes. www.ibm.com Joyce Woods wrote: Hello Everyone: Does anyone know where positions are posted for fellow ADSM'ers looking for a new job??? Thanks !
Re: TSM 3.7 Sun Sol Server error
You're trying to use a 32 bit driver under a 64 bit OS. Before 3.7.3 there were no 64 bit drivers. Try upgrading your server to 3.7.3 or above and it should work okay. On Wed, Aug 09, 2000 at 04:26:51PM +1000, Gogos, Michael wrote: Hello, I also have the same problem. TSM 3.7, Solaris 2.7 on part of an E1, the library is a Sun StorEdge L1000. I've edited the /usr/kernel/drv/mt.conf for the two drives (SCSI id 2, LUN 0 SCSI id 3, LUN 0) and also /usr/kernel/drv/lb.conf for the library (SCSI id 0, LUN 0). add_drv for both mt and lb fail with the same message as Boris. I'm new to both Sun and TSM, so I'd appreciate any help, even something that may seem blatantly obvious to some of you. Michael Gogos Unix Systems Support ANZ Banking Group 227 Toorak Road South Yarra 3141 Victoria, Australia phone: (+613) 9869-6840 fax: (+613) 9869-3447 email: mailto:[EMAIL PROTECTED] -Original Message- From: Boris Feldman (Udi) [mailto:[EMAIL PROTECTED]] Sent: Wednesday, August 09, 2000 4:54 PM To: [EMAIL PROTECTED] Subject: TSM 3.7 Sun Sol Server error Hi All, We are using TSM 3.7 Server on Sun Solaris server (Ultra 60) with AIT2 tapes in QualStar 4440 library. I got the failed installation process (on the mt drive definition point : add_drv ). The error was : the mt drive was successfully added to system but failed to attach. As result of this problem we have not the mt driver files in /dev/rmt/ directory. Any ideas? TNXS. ___ Boris Feldman - Product Manager IBM Storage TSM UDI Millenium Ltd. 1G Yoni Netanyahu Str. Or-Yehuda 60256, ISRAEL Tel : (972)-3-5333555 ext. 357 Fax : (972)-3-5333676 Mobile : (972)-54-929357 E-mail [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] ___
TSM and Lotus Notes Archiving
Hi, does anybody have any experience with the product " IBM Content Manager CommonStore for Lotus" which has an interface to tsm for archiving "Lotus-Notes-Documents". Regards winfried
Re: ADSM Solaris client
We are using Solaris 2.6 backup client to back up our unix servers. Every week or so after having started the dsm scheduler the scheduler crops out saying that "cannot open the dsmsched.log file". You didn't provide us with any information about the operating environment or the context of the problem so that we can better advise, so what we can provide will be limited... Is there a dsmerror.log being produced, with some info in it about this? Did the problem just start happening after months of no problems doing backups? If so, pursue what changed in the environment. Do the permissions on the directory or the log file change over time, as in something altering them? Is the backup being started with the current directory being in a file system with some odd (weekly) housekeeping going on? Is the file system going full at some times of the day? Make sure the file systems are being monitored by some alerting program. Is the process or the system running out of file handles at event time? Use 'lsof' or comparable program to check what files this process has open, and potentially have cron do so hourly to accumulate info to see what's occurring when the problem thresholds. Richard Sims, BU
Scheduler Problems on AIX - SCHEDMODE=PROMPTED???
Hello All, I upgraded my AIX TSM clients to 3.7.2.14 yesterday and now I am having a problem with the TSM scheduler process. The backups were missed for the 6 boxes I upgraded last night. I arrived this morning and thought maybe I had forgotten to restart the scheduler, but the schedulers were all running. I investigated by looking in the activity log and I received the following error for all of the clients - ANR2716E Schedule prompter was not able to contact client client name using type 1 (IP Address 1501). The schedule mode for these clients was set to PROMPTED. I switched the schedule mode to POLLING and the scheduled backups ran. Is there a problem with the TSM scheduler at this level? Any help is appreciated. Thanks, Sean Sean McNamara Senior Analyst PJM Interconnection L.L.C. (610)666-4206
Re: Scheduler Problems on AIX - SCHEDMODE=PROMPTED???
Hi Sean! If you switch from polling to prompted mode, you will have to restart all the scheduler clients. Kindest regards, Eric van Loon -Original Message- From: Sean McNamara [mailto:[EMAIL PROTECTED]] Sent: Wednesday, 09 August, 2000 15:20 To: [EMAIL PROTECTED] Subject: Scheduler Problems on AIX - SCHEDMODE=PROMPTED??? Hello All, I upgraded my AIX TSM clients to 3.7.2.14 yesterday and now I am having a problem with the TSM scheduler process. The backups were missed for the 6 boxes I upgraded last night. I arrived this morning and thought maybe I had forgotten to restart the scheduler, but the schedulers were all running. I investigated by looking in the activity log and I received the following error for all of the clients - ANR2716E Schedule prompter was not able to contact client client name using type 1 (IP Address 1501). The schedule mode for these clients was set to PROMPTED. I switched the schedule mode to POLLING and the scheduled backups ran. Is there a problem with the TSM scheduler at this level? Any help is appreciated. Thanks, Sean Sean McNamara Senior Analyst PJM Interconnection L.L.C. (610)666-4206 ** 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. **
Please Help - Server Down
Has anyone encounter this before??? The server was terminated and can't be brought back up. Messages from log and dsmserv errpt below. The followings are error messages from the log: nohup.out file from "nohup /opt/IBMadsm-s/bin/dsmserv" command: ADSTAR Distributed Storage Manager for Sun Solaris 2.6/7 Version 3, Release 1, Level 2.20 Licensed Materials - Property of IBM 5639-B22 (C) Copyright IBM Corporation 1990, 1998. All rights reserved. U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corporation. ANR7800I DSMSERV generated at 10:46:31 on Mar 26 1999. ANR7801I Subsystem process ID is 4938. ANR0900I Processing options file /opt/IBMadsm-s/bin/dsmserv.opt. ANR0990I ADSM server restart-recovery in progress. ANR0214W Database volume /apps/adsm/db_mirror/mir.db2.dsm is in the offline state - VARY ON required. ANR0215W Recovery log volume /apps/adsm/db_mirror/mir.log2.dsm is in the offline state - VARY ON required. ANR0214W Database volume /apps/adsm/db_mirror/mir.db3.dsm is in the offline state - VARY ON required. ANR0200I Recovery log assigned capacity is 3704 megabytes. ANR0201I Database assigned capacity is 7552 megabytes. ANR0306I Recovery log volume mount in progress. ANR0353I Recovery log analysis pass in progress. ANR0354I Recovery log redo pass in progress. ANR0355I Recovery log undo pass in progress. ANRD logseg.c(493): Log space has been overcommitted (no empty segment found) - base LSN = 164471.0.0. ANR7824S Server operation terminated. ANR7823S Internal error LOGSEG871 detected. ANRD Trace-back of called functions: ANRD 0x0007E43C AbortServer ANRD 0x0007B7E0 pkAbort ANRD 0x0056294C LogAllocSegment ANRD 0x0055C830 ForceLogPages ANRD 0x0055AD50 LogWriterThread ANRD 0x0007E628 StartThread ANRD 0xEF764C40 *UNKNOWN* ANRD 0x0007E550 StartThread output form dsmserv.errl == 08/08/2000 23:14:54 ANR7824S Server operation terminated. 08/08/2000 23:14:54 ANR7823S Internal error LOGSEG871 detected. 08/08/2000 23:14:54 ANRD Trace-back of called functions: 08/08/2000 23:14:54 ANRD 0x0007E43C AbortServer 08/08/2000 23:14:54 ANRD 0x0007B7E0 pkAbort 08/08/2000 23:14:54 ANRD 0x0056294C LogAllocSegment 08/08/2000 23:14:54 ANRD 0x0055C830 ForceLogPages 08/08/2000 23:14:54 ANRD 0x00559F9C LogWriterThread 08/08/2000 23:14:54 ANRD 0x0007E628 StartThread 08/08/2000 23:14:54 ANRD 0xEF764C40 *UNKNOWN* 08/08/2000 23:14:54 ANRD 0x0007E550 StartThread 08/08/2000 23:14:54 ANR7820S ADSM thread 1 terminated in response to program abort. 08/08/2000 23:14:54 ANR7820S ADSM thread 2 terminated in response to program abort. 08/08/2000 23:14:54 ANR7820S ADSM thread 3 terminated in response to program abort. 08/08/2000 23:14:54 ANR7820S ADSM thread 4 terminated in response to program abort. 08/08/2000 23:14:54 ANR7820S ADSM thread 5 terminated in response to program abort. 08/08/2000 23:14:54 ANR7820S ADSM thread 6 terminated in response to program abort. 08/08/2000 23:14:54 ANR7820S ADSM thread 7 terminated in response to program abort. 08/08/2000 23:14:54 ANR7820S ADSM thread 8 terminated in response to program abort. 08/08/2000 23:14:54 ANR7820S ADSM thread 9 terminated in response to program abort. 08/08/2000 23:14:54 ANR7820S ADSM thread 10 terminated in response to program abort. 08/08/2000 23:14:54 ANR7820S ADSM thread 11 terminated in response to program abort. 08/08/2000 23:14:54 ANR7820S ADSM thread 12 terminated in response to program abort. 08/08/2000 23:14:54 ANR7820S ADSM thread 13 terminated in response to program abort. 08/08/2000 23:14:54 ANR7820S ADSM thread 14 terminated in response to program abort. 08/08/2000 23:14:54 ANR7820S ADSM thread 15 terminated in response to program abort. 08/08/2000 23:14:54 ANR7820S ADSM thread 16 terminated in response to program abort. 08/08/2000 23:14:54 ANR7820S ADSM thread 17 terminated in response to program abort. 08/08/2000 23:14:54 ANR7820S ADSM thread 18 terminated in response to program abort. 08/08/2000 23:14:54 ANR7820S ADSM thread 19 terminated in response to program abort. 08/08/2000 23:14:54 ANR7820S ADSM thread 20 terminated in response to program abort. 08/08/2000 23:14:54 ANR7820S ADSM thread 21 terminated in response to program abort. 08/08/2000 23:14:54 ANR7820S ADSM thread 22 terminated in response to program abort. 08/08/2000 23:14:54 ANR7820S ADSM thread 23 terminated in response to program abort. 08/08/2000 23:14:54 ANR7820S ADSM thread 24 terminated in response to program abort. 08/08/2000 23:14:54 ANR7820S ADSM thread 25 terminated in response to program abort. 08/08/2000 23:14:54 ANR7820S ADSM thread 26 terminated in response to program abort. 08/08/2000 23:14:54 ANR7820S ADSM thread 27 terminated in
Re: Scheduler Problems on AIX - SCHEDMODE=PROMPTED???
Just kill shedule and again restart it. "[EMAIL PROTECTED]/P=Internet/A= /C=us" on 08/09/2000 09:43:43 AM Please respond to "[EMAIL PROTECTED]/P=Internet/A= /C=us" @ X400 To: "[EMAIL PROTECTED]/P=Internet/A= /C=us"@X400 cc: Subject: Scheduler Problems on AIX - SCHEDMODE=PROMPTED??? Hello All, I upgraded my AIX TSM clients to 3.7.2.14 yesterday and now I am having a problem with the TSM scheduler process. The backups were missed for the 6 boxes I upgraded last night. I arrived this morning and thought maybe I had forgotten to restart the scheduler, but the schedulers were all running. I investigated by looking in the activity log and I received the following error for all of the clients - ANR2716E Schedule prompter was not able to contact client client name using type 1 (IP Address 1501). The schedule mode for these clients was set to PROMPTED. I switched the schedule mode to POLLING and the scheduled backups ran. Is there a problem with the TSM scheduler at this level? Any help is appreciated. Thanks, Sean Sean McNamara Senior Analyst PJM Interconnection L.L.C. (610)666-4206
Re: Please Help - Server Down
Long, check the availability of your db log files from your operating system... looks like you probably had a volume group go unavailable... also you might have to add to and extend your log to get back up... DSMSERV EXTEND LOG (Emergency Log Extension) Use this command to extend the size of the recovery log when you need additional log space to restart the server. After the server is running, you can do the following: v Back up the database, which frees the recovery log space. v Adjust the size of the recovery log, the database backup trigger full percentage, or both to allow for successful future database backups. Note: Use the DSMFMT utility to format a new recovery log volume. Syntax DSMSERV EXTEND LOG volume_name megabytes Parameters volume_name(Required) Specifies the name of a new, formatted volume available for use as the recovery log extension. megabytes(Required) Specifies the size, in megabytes, of the new volume. The size must be a multiple of 4MB and 1MB less than the size of the volume specified in the volume_name parameter. For example, if the volume is 5MB, specify a value of 4. -- From: Long Nguyen[SMTP:[EMAIL PROTECTED]] Reply To: ADSM: Dist Stor Manager Sent: Wednesday, August 09, 2000 8:43 AM To: [EMAIL PROTECTED] Subject: Please Help - Server Down Has anyone encounter this before??? The server was terminated and can't be brought back up. Messages from log and dsmserv errpt below. The followings are error messages from the log: nohup.out file from "nohup /opt/IBMadsm-s/bin/dsmserv" command: ADSTAR Distributed Storage Manager for Sun Solaris 2.6/7 Version 3, Release 1, Level 2.20 Licensed Materials - Property of IBM 5639-B22 (C) Copyright IBM Corporation 1990, 1998. All rights reserved. U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corporation. ANR7800I DSMSERV generated at 10:46:31 on Mar 26 1999. ANR7801I Subsystem process ID is 4938. ANR0900I Processing options file /opt/IBMadsm-s/bin/dsmserv.opt. ANR0990I ADSM server restart-recovery in progress. ANR0214W Database volume /apps/adsm/db_mirror/mir.db2.dsm is in the offline state - VARY ON required. ANR0215W Recovery log volume /apps/adsm/db_mirror/mir.log2.dsm is in the offline state - VARY ON required. ANR0214W Database volume /apps/adsm/db_mirror/mir.db3.dsm is in the offline state - VARY ON required. ANR0200I Recovery log assigned capacity is 3704 megabytes. ANR0201I Database assigned capacity is 7552 megabytes. ANR0306I Recovery log volume mount in progress. ANR0353I Recovery log analysis pass in progress. ANR0354I Recovery log redo pass in progress. ANR0355I Recovery log undo pass in progress. ANRD logseg.c(493): Log space has been overcommitted (no empty segment found) - base LSN = 164471.0.0. ANR7824S Server operation terminated. ANR7823S Internal error LOGSEG871 detected. ANRD Trace-back of called functions: ANRD 0x0007E43C AbortServer ANRD 0x0007B7E0 pkAbort ANRD 0x0056294C LogAllocSegment ANRD 0x0055C830 ForceLogPages ANRD 0x0055AD50 LogWriterThread ANRD 0x0007E628 StartThread ANRD 0xEF764C40 *UNKNOWN* ANRD 0x0007E550 StartThread output form dsmserv.errl == 08/08/2000 23:14:54 ANR7824S Server operation terminated. 08/08/2000 23:14:54 ANR7823S Internal error LOGSEG871 detected. 08/08/2000 23:14:54 ANRD Trace-back of called functions: 08/08/2000 23:14:54 ANRD 0x0007E43C AbortServer 08/08/2000 23:14:54 ANRD 0x0007B7E0 pkAbort 08/08/2000 23:14:54 ANRD 0x0056294C LogAllocSegment 08/08/2000 23:14:54 ANRD 0x0055C830 ForceLogPages 08/08/2000 23:14:54 ANRD 0x00559F9C LogWriterThread 08/08/2000 23:14:54 ANRD 0x0007E628 StartThread 08/08/2000 23:14:54 ANRD 0xEF764C40 *UNKNOWN* 08/08/2000 23:14:54 ANRD 0x0007E550 StartThread 08/08/2000 23:14:54 ANR7820S ADSM thread 1 terminated in response to program abort. 08/08/2000 23:14:54 ANR7820S ADSM thread 2 terminated in response to program abort. 08/08/2000 23:14:54 ANR7820S ADSM thread 3 terminated in response to program abort. 08/08/2000 23:14:54 ANR7820S ADSM thread 4 terminated in response to program abort. 08/08/2000 23:14:54 ANR7820S ADSM thread 5 terminated in response to program abort. 08/08/2000 23:14:54 ANR7820S ADSM thread 6 terminated in response to program abort. 08/08/2000 23:14:54 ANR7820S ADSM thread 7 terminated in response to program abort. 08/08/2000 23:14:54 ANR7820S ADSM thread 8 terminated in response to program abort. 08/08/2000 23:14:54 ANR7820S ADSM thread 9 terminated in response to program abort. 08/08/2000 23:14:54 ANR7820S ADSM thread 10 terminated in response to program abort. 08/08/2000 23:14:54
Re: What determines what is to be backed up?
Jack, Has some attribute of the file other than the time stamp changed. With the netware client for example ADSM will look at attributes such as file size and trustee rights. If you only want it to consider timestamp then look at the incrbydate option. If you do use incrbydate remember that you should still run full incrementals on a regular basis. If you search through the particular client manual you are interested in, you should be able to find the file attributes ADSM will use to decide if a backup is required. John Palmadesso Jack [EMAIL PROTECTED] on 08/09/2000 02:43:25 PM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc:(bcc: John Naylor/HAV/SSE) Subject: What determines what is to be backed up? Good Morning, What criteria does ADSM use to determine what files are to be backed up incrementally. Does it go just by last date modified or by the actual contents of the file or something else? I have some clients that show they backed up some files last night that have not been modified since 8/2. Why is this happening? Jack ** 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 **
Impatient clients on ADSM with 3494
I've got a funny 'fault' with our system, (3.1.2.40 server with attached four drive 3494), as follows: Clients set restores going, and most of the time there's no problems. But, every so often, we get a restore which needs data on a lot of tapes, (for example 30 or more). Invariably this restore will fail at some point, and the problem appears to be that it thinks that there are no mount points (drives) free. Most of the time this appears to true, although the drives are at status 'idle', (why doesn't it dismount the tapes!?). Other times it appears that the server just cannot load the tape quick enough to satisfy the client - which ends up with the now-dreaded 'data unavailable to server' message. Worst still, on occasion we have drives 0 and 2 free, 1 and 3 in use and the clients regard this as 'no mount points available' - why? Our most consistent workaround appears to be keep an eye on the restore and manually dismount the tape it's just finished with, especially if the restore is using drives 1 or 3. We've tried setting the mountretention's on both drive and library device classes down to five minutes but this doesn't help. Is there some other timeout value, esp. on the client, that I've overlooked? And has anyone seen problems like this with the 3494's? Any assistance greatly welcome, even 'no idea - report to Tivoli/IBM'. Bob Cross. * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * This message is confidential. It may also be privileged or protected by other legal rules. It does not constitute an offer or acceptance of an offer, nor shall it form any part of a legally binding contract. If you have received this communication in error, please let us know by reply then destroy it. You should not use, print, copy the message or disclose its contents to anyone. E-mail is subject to possible data corruption, is not secure, and its content does not necessarily represent the opinion of this Company. No representation or warranty is made as to the accuracy or completeness of the information and no liability can be accepted for any loss arising from its use. This e-mail and any attachments are not guaranteed to be free from so-called computer viruses and it is recommended that you check for such viruses before down-loading it to your computer equipment. This Company has no control over other websites to which there may be hypertext links and no liability can be accepted in relation to those sites. Scottish Newcastle plc Registered in Scotland, Registered Number 16288 Registered Office: 50 East Fettes Avenue, Edinburgh, EH4 1RR * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
Re: Impatient clients on ADSM with 3494
Hello Bob, We also had an issue with the mount retention. At the present time our mount retention is 1 minute. We also made the decision to transfer all data to disk pool first and then to tape pool. Restores from disk are 100 times faster than tape. Have a great day, Debbie Denham Robert Cross [EMAIL PROTECTED] 08/09/00 10:26AM I've got a funny 'fault' with our system, (3.1.2.40 server with attached four drive 3494), as follows: Clients set restores going, and most of the time there's no problems. But, every so often, we get a restore which needs data on a lot of tapes, (for example 30 or more). Invariably this restore will fail at some point, and the problem appears to be that it thinks that there are no mount points (drives) free. Most of the time this appears to true, although the drives are at status 'idle', (why doesn't it dismount the tapes!?). Other times it appears that the server just cannot load the tape quick enough to satisfy the client - which ends up with the now-dreaded 'data unavailable to server' message. Worst still, on occasion we have drives 0 and 2 free, 1 and 3 in use and the clients regard this as 'no mount points available' - why? Our most consistent workaround appears to be keep an eye on the restore and manually dismount the tape it's just finished with, especially if the restore is using drives 1 or 3. We've tried setting the mountretention's on both drive and library device classes down to five minutes but this doesn't help. Is there some other timeout value, esp. on the client, that I've overlooked? And has anyone seen problems like this with the 3494's? Any assistance greatly welcome, even 'no idea - report to Tivoli/IBM'. Bob Cross. * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * This message is confidential. It may also be privileged or protected by other legal rules. It does not constitute an offer or acceptance of an offer, nor shall it form any part of a legally binding contract. If you have received this communication in error, please let us know by reply then destroy it. You should not use, print, copy the message or disclose its contents to anyone. E-mail is subject to possible data corruption, is not secure, and its content does not necessarily represent the opinion of this Company. No representation or warranty is made as to the accuracy or completeness of the information and no liability can be accepted for any loss arising from its use. This e-mail and any attachments are not guaranteed to be free from so-called computer viruses and it is recommended that you check for such viruses before down-loading it to your computer equipment. This Company has no control over other websites to which there may be hypertext links and no liability can be accepted in relation to those sites. Scottish Newcastle plc Registered in Scotland, Registered Number 16288 Registered Office: 50 East Fettes Avenue, Edinburgh, EH4 1RR * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
Re: TSM and Lotus Notes Archiving
We use CommonStore with SAP if that is any help. It is fairly easy to use. -Original Message- From: Winfried Heilmann [mailto:[EMAIL PROTECTED]] Sent: Wednesday, August 09, 2000 7:34 AM To: [EMAIL PROTECTED] Subject: TSM and Lotus Notes Archiving Hi, does anybody have any experience with the product " IBM Content Manager CommonStore for Lotus" which has an interface to tsm for archiving "Lotus-Notes-Documents". Regards winfried
Re: Impatient clients on ADSM with 3494
Robert, Set your mount retention on the storage pool down to 1 minute. Also check the mount limit on the device class of your tapes, if you have this defaulted that is why you are only using 2 of the 4 drives. John Robert Cross [EMAIL PROTECTED] on 08/09/2000 03:26:09 PM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc:(bcc: John Naylor/HAV/SSE) Subject: Impatient clients on ADSM with 3494 I've got a funny 'fault' with our system, (3.1.2.40 server with attached four drive 3494), as follows: Clients set restores going, and most of the time there's no problems. But, every so often, we get a restore which needs data on a lot of tapes, (for example 30 or more). Invariably this restore will fail at some point, and the problem appears to be that it thinks that there are no mount points (drives) free. Most of the time this appears to true, although the drives are at status 'idle', (why doesn't it dismount the tapes!?). Other times it appears that the server just cannot load the tape quick enough to satisfy the client - which ends up with the now-dreaded 'data unavailable to server' message. Worst still, on occasion we have drives 0 and 2 free, 1 and 3 in use and the clients regard this as 'no mount points available' - why? Our most consistent workaround appears to be keep an eye on the restore and manually dismount the tape it's just finished with, especially if the restore is using drives 1 or 3. We've tried setting the mountretention's on both drive and library device classes down to five minutes but this doesn't help. Is there some other timeout value, esp. on the client, that I've overlooked? And has anyone seen problems like this with the 3494's? Any assistance greatly welcome, even 'no idea - report to Tivoli/IBM'. Bob Cross. * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * This message is confidential. It may also be privileged or protected by other legal rules. It does not constitute an offer or acceptance of an offer, nor shall it form any part of a legally binding contract. If you have received this communication in error, please let us know by reply then destroy it. You should not use, print, copy the message or disclose its contents to anyone. E-mail is subject to possible data corruption, is not secure, and its content does not necessarily represent the opinion of this Company. No representation or warranty is made as to the accuracy or completeness of the information and no liability can be accepted for any loss arising from its use. This e-mail and any attachments are not guaranteed to be free from so-called computer viruses and it is recommended that you check for such viruses before down-loading it to your computer equipment. This Company has no control over other websites to which there may be hypertext links and no liability can be accepted in relation to those sites. Scottish Newcastle plc Registered in Scotland, Registered Number 16288 Registered Office: 50 East Fettes Avenue, Edinburgh, EH4 1RR * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * ** 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 **
Re: Help with scheduling ADSM tasks into blocks of time.
Start Oracle hot backups (2 at a time) 6am - 6pm Oracle recommends that hot backups be done during periods of low update activity because updates generate unusually large amounts of redo log data during hot backups. When a database update occurs logging normally records which fields are affected and how the fields are changed. When an update occurs during a hot backup the 'after' version of every block affected by the change is written to the redo logs. This allows the recovery process to bring 'fuzzy' backups of the .dbf files back to a consistent state. The size of a block is between 1024 and 8192 bytes, depending on the configuration. Most of the time you have earmarked for hot backups falls within the normal work day. Are you sure you have the disk space and I/O bandwidth to support the intensive logging associated with hot backups during the work day?
Immediate Backup does not start immediately
I defined an immediate backup, but the node says that the next try to get a schedule will be in 1 hour. What schedule mode do I have to define on the client and on the server? I would like that the server starts the backup and the node would permanently listen. Thank you for any help, Kind regards Werner Nussbaumer
Moving Tapes from AIX to NT
No such thing as a dumb question, Right! If I migrate my server from AIX to NT, I can export import the DB but what happens to the tapes we have accumulated? Can a tape be read by an NT TSM server that was created by an AIX server? No such thing as a dumb
Retrieving limitations
Does anyone know what the limitations are retrieving files across different platforms. Example Archive files on a Novell platform and retrieve the files from a Unix client. Can this be done? Thanks Darren Perry Publishers Printing Co. Email:[EMAIL PROTECTED]
Re: DIRMC not working???
I'm being told by the Unix administrator he is having a problem with "only one" of his clients. Of the 10 clients he has, I have them all in the same domain. In that domain there are 4 management classes so I've asked him to add the line DIRMC to his dsm.sys file. Why? Is this being confused with specifying a management class on an Include statement? A DIRMC in most Unix systems is irrelevant because the directory info is basic and, like an empty file, is recorded in the *SM database, not in a storage pool. ANS1105E The management class for this file does not have a valid backup copy group. This file will not be backed up. The server policy definitions need to be checked out, according to this message. Richard Sims, BU
Restoring files
Someone please enlighten me. I have a Unix Administrator who has root access to all of his computers. He basically wants to give all of his users the right to restore files anytime they want. His reasoning is because he doesn't have access, here is his note to me: Note that we're talking about one pseudo-DBA on the Data Warehouse server. He doesn't have root access. He does have "oracle" access (which I don't) which means he can only restore database related stuff (which I don't have responsibility for). He makes it sound like he can't do this but I get the feeling he just doesn't want to. Someone please help me understand why he couldn't do these restores because of his access. I am trying to limit the number of users that can do restores so this doesn't get out of hand. Thanks, Geoff Gill NT Systems Support Engineer Computer Systems Group E-Mail: [EMAIL PROTECTED] Phone: (858) 826-4062 Pager: (888) 997-9614
TSM Windows 4.1.0 Client Install from Electronic Distribution
Trying to install the Windows 2000 V4.1.0 client I see that the READ1STC.TXT file says, for electronic distribution as when downloading from Internet: "TBD Will try to remain as close to 3.7 structure as possible." I guess the document was still in draft when released. Are there final instructions on how to install? It's not obvious, at least to me. Sorry if this has been discussed, I'm just checking back in after an absence. Rich
Re: Windows 2000 profession B/u issues
I am successfully backing up my W2K laptop to an RS6K TSM server. Unfortunately I cannot help you with your problem because I have not tried to backup shares. -- Joshua S. Bassi Senior Technical Consultant Symatrix Technology, Inc. [EMAIL PROTECTED] -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Robinson, Cris Sent: Wednesday, August 09, 2000 8:41 AM To: [EMAIL PROTECTED] Subject: Windows 2000 profession B/u issues Is anyone out there backing up Windows 2000 professional clients. We are looking to migrate to 2000 but there are issues with user privileges to files and folders. I have gone through the documentation but have not been able to get TSM to see a user share. It will only see the default \\localmachine\C$ admin share. We are looking to "lock down most of the device except 1 folder which we set up a share to. This folder is called "scratch". Not my idea for a name so don't go there ;-) so, we have a domain \\localmachine\scratch in addition to the c$ share. has anyone been able to get this or any other approach to work? Thanks - CR __ Cris Robinson Backup Recovery Engineering Information Technology Support Services Liberty Mutual Insurance Portsmouth, New Hampshire 603.431.8400.54837 mailto:[EMAIL PROTECTED]
Re: Retrieving limitations
Does anyone know what the limitations are retrieving files across different platforms. The file systems must be compatible for cross-platform operations to succeed - even Query's! For example, a FAT file system is common to Windows, DOS, NT, and OS/2, but not to most Unix systems, which prevents interoperation. Richard Sims, BU
Re: NetWare Client Passwords
Joshua, Try adding the option "nwpwfile yes". I used to intermittently see this problem when the scheduler attempted to connect to Netware - I would type in the Netware user id and password again and it would run fine for months. I haven't seen this problem at all since I added this option. Steve Branch Phillips Petroleum e-mail: [EMAIL PROTECTED] "Joshua S. Bassi" [EMAIL PROTECTED]@VM.MARIST.EDU on 08/09/2000 11:52:25 AM Any replies will be addressed to: "ADSM: Dist Stor Manager" [EMAIL PROTECTED] Sent by: "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: NetWare Client Passwords All, I am trying to setup a nightly schedule to backup a NetWare 4.1.1 server. The TSM client is 4.1.0.0 and the server is W2K TSM 3.7.3. When I connect to the server, I am not prompted for a password. I can backup/restore just fine. But when I try to schedule a nightly backup through the scheduler, I get the schedule info displayed, but when the server contacts the client, it requests the password for user .backup. I do not believe it should be doing this due to the fact that I have passwordaccess set to generate! Below is my option file, can somebody please help? -- Joshua S. Bassi Senior Technical Consultant Symatrix Technology, Inc. [EMAIL PROTECTED] cha 0 commm tcp *commmipx compressa n compressi n dom all-local nds errorlogr 10 largecom y maxcmdr 4 nwus .cn=backup.o=whatever passworda generate processor 1000 quiet resour10 retryp10 schedlogr 10 schedmod pr suy tapep n tcpb 31 *tcpb 512 tcps ??? tcpw 64 *txnb 25600 *Use this option when backing up to tape
Hail the power of SQL!
Today I've been learning SQL to help gather info about my ADSM setup, and
I'm absolutely ecstatic it's power and flexibility.
A week ago, a 'SQL for ADSM' cheat sheet would have been indispensible to
me, but I didn't know of one. Does such a thing
exist? If it doesn't, I think I'll write one up and post it to the list,
for the sake of other ADSM newbie admins. ("help select" was somewhat
useful, but doesn't really make the grade).
While we are on the topic, does anyone have any favorite SQL statements
they'd like to share?
Re: Hail the power of SQL!
dsmadmc -id=admin -pa=x 'select stgpool_name,count(*) from volumes group by
stgpool_name'
[EMAIL PROTECTED] 08/09/00 03:15PM
Today I've been learning SQL to help gather info about my ADSM setup, and
I'm absolutely ecstatic it's power and flexibility.
A week ago, a 'SQL for ADSM' cheat sheet would have been indispensible to
me, but I didn't know of one. Does such a thing
exist? If it doesn't, I think I'll write one up and post it to the list,
for the sake of other ADSM newbie admins. ("help select" was somewhat
useful, but doesn't really make the grade).
While we are on the topic, does anyone have any favorite SQL statements
they'd like to share?
Re: Hail the power of SQL!
A week ago, a 'SQL for ADSM' cheat sheet would have been indispensible to me, but I didn't know of one. Does such a thing exist? Daniel - That and much more misc. accumulated tidbits are to be found in my ADSM functional directory at http://people.bu.edu/rbs . Look under "REFERENCES AND OTHER RESOURCES" toward the bottom of the file, and "SQL" therein. There are also various sample SELECT statements sprinkled throughout the categorized file. Richard Sims (just another ADSMer, and compulsive documenter), BU
Re: Retrieving limitations
Richard, So if I have files archived via a Novell client, can I retrieve them with an NT client? Thanks, Keith Higgs Richard Sims [EMAIL PROTECTED] 08/09/00 01:33PM Does anyone know what the limitations are retrieving files across different platforms. The file systems must be compatible for cross-platform operations to succeed - even Query's! For example, a FAT file system is common to Windows, DOS, NT, and OS/2, but not to most Unix systems, which prevents interoperation. Richard Sims, BU
Re: Recommended ADSM hardware
1. Go for an *80, whatever you can afford. Disk (SSA) is more important than RAM. Couldn't justify much more than 256MB on ADSM -- havn't any evidence for TSM. AIX will use the extra so go for a gig or two... 2. Go for a 3494 with at least 3 (pref. 4) 3590-E1A drives. Too much? Buy used from ICC upgrade. Still too much? Buy a new, large capacity, 3575 with at least 4 (pref. 6) 3570C drives. Too much? Buy used from ICC upgrade. Still too much? Go to work for a better company! Does my preference for IBM hardware show? Go browse ADSM-L archives and then review 8mm DLT recording technology and decide for yourself. "Marc D. Taylor" wrote: Hello All, I am tasked with the responsibility of developing a proposal for a new ADSM server. Presently, we have an IBM J40 w/ 256 MB ram, 25 GB of disk storage. We are using dlt2000 drives. What I would like to poll from you all is: What IBM AIX box you would use and what tape technology you would use. I have gotten info on dlt8000's and the ait drives. Are there others I should be considering? What are people using today. Thanks for your input and I have learned a lot from being on this list. I will share the results if anyone is interested. Marc Taylor === Marc D. Taylor Research Programmer Beckman Institute Systems Services Room 1714 Office: 217-244-7373, Fax: 217-333-8206 [EMAIL PROTECTED] www.beckman.uiuc.edu/groups/biss
Re: Hail the power of SQL!
This thread reminds me of a question I've been meaning to ask. I have several SQL queries that run as cron jobs to keep me current on system status. About two months ago the server started crashing every Sunday at the same exact time. The problem was traced to an automated query that runs every day, which has been running for almost two years. Once I modified the statement, the crashes stopped. Support said that it was because of the "group by" portion of the query, and that this is a know issue. My questions are: 1. Why would this start happening when I have been using this script every day for over a year? Well, the crash should not be happening - we would more expect a message like ANR2958E SQL temporary table storage has been exhausted. But SQL queries require workspace, and that comes from the TSM database, and certainly yours has grown, been used, and changed over time. The workspace usually needs to be contiguous, as well, and when things get tight, untoward events can transpire. How TSM is actually servicing some of these queries also plays a part. Your mileage may vary, things change, and all that. Richard Sims, BU
