ANR0209E Page address mismatch detected on recovery log
Hello, I'm getting an error when starting TSM Server and the server is not starting We have TSM 5.2.1.0 on an Z/OS. We did an UNLOADDB followed by a LOADFORMAT a LOADDB an AUDITDB. All of them ended ok, but when I try to start the TSM Server I get the messages: ANR0900I Processing options file dsmserv.opt. ANR0990I Server restart-recovery in progress. ANR0200I Recovery log assigned capacity is 1152 megabytes. ANR0201I Database assigned capacity is 26984 megabytes. ANR0306I Recovery log volume mount in progress. ANR0209E Page address mismatch detected on recovery log volume ADSMRE.RCVLOG2A, ANR0209E logical page 0 (physical page 18688); actual: 92160. ANR0209E Page address mismatch detected on recovery log volume ADSMRE.RCVLOG2B, ANR0209E logical page 0 (physical page 18688); actual: 129024. ANR0251E Unable to read recovery log page 0 from any alternate copy. ANRD LOGSEG(772): ThreadId1 Error 3 reading 64 pages from page 0, offset ANRD 256. ANR5963I ADSM server termination complete. The recovery log mode is, and has been forever, NORMAL. Has anyone had this kind of error? What has been the solution Regards AH
Re: ANR0209E Page address mismatch detected on recovery log
Anton - I'm sorry to see you in this situation. The List archives reflect only two instances of people encountering this in the past, and they posted no follow-up resolution. I recommend that you contact TSM Support as your next step. I rue the day that IBM started encouraging customers to take their TSM system out of service and run salvage utilities to reorganize the db, as situations like this inevitably result, particularly as these utilities are not subject to the same development intensity and scrutiny as mainline TSM code. This has been a very poor decision on someone's part in IBM, to foster this kind of risky undertaking in enterprise sites as though it were a casual, risk-free activity. Some vendor thinking is just unfathomable. Richard Simshttp://people.bu.edu/rbs On Mar 30, 2005, at 3:18 AM, Anton Herrero wrote: Hello, I'm getting an error when starting TSM Server and the server is not starting We have TSM 5.2.1.0 on an Z/OS. We did an UNLOADDB followed by a LOADFORMAT a LOADDB an AUDITDB. All of them ended ok, but when I try to start the TSM Server I get the messages: ANR0900I Processing options file dsmserv.opt. ANR0990I Server restart-recovery in progress. ANR0200I Recovery log assigned capacity is 1152 megabytes. ANR0201I Database assigned capacity is 26984 megabytes. ANR0306I Recovery log volume mount in progress. ANR0209E Page address mismatch detected on recovery log volume ADSMRE.RCVLOG2A, ANR0209E logical page 0 (physical page 18688); actual: 92160. ANR0209E Page address mismatch detected on recovery log volume ADSMRE.RCVLOG2B, ANR0209E logical page 0 (physical page 18688); actual: 129024. ANR0251E Unable to read recovery log page 0 from any alternate copy. ANRD LOGSEG(772): ThreadId1 Error 3 reading 64 pages from page 0, offset ANRD 256. ANR5963I ADSM server termination complete. The recovery log mode is, and has been forever, NORMAL. Has anyone had this kind of error? What has been the solution Regards AH
Re: help:Lan-free backup question
Hi Li! It depends. If you are doing LAN-free to a similar device, then you do not have to use separate adapters. However, when you are doing LAN-free to tape or to storage which requires a different device driver, then you will need separate adapters. IBM does not support disk and tape I/O through the same adapter, nor do they support multiple device drivers through one adapter. Kindest regards, Eric van Loon KLM Royal Dutch Airlines -Original Message- From: ming li [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 29, 2005 04:41 To: ADSM-L@VM.MARIST.EDU Subject: help:Lan-free backup question Hi all,somebody told me that for TSM lan-free backup client(store agent?) must need two separate fc adapters to transfer backup data and application data,is this ture?From store agent manual I couldn't find any subject about this.But for Veritas Netbackup a media server only need 1 fc adapter to do this.Who can help me?Thanks! ** For information, services and offers, please visit our web site: http://www.klm.com. 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. **
Re: Tsm TEC trouble
Here's one possibility: If the TEC server is not up or not accessible when the TSM server starts, the Tivoli event logging will be disabled. You can restart it with the BEGIN EVENTLOGGING TIVOLI command. This has been happening to me sporadically because sometimes the TSM server starts before the Tivoli TEC gateway starts (they both run on the same physical machine). Apparently TSM does not try to contact TEC again after the initial failure. Loren Cain Digicon -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Chernyaev Sergey Sent: Monday, January 31, 2005 3:58 AM To: ADSM-L@VM.MARIST.EDU Subject: Tsm TEC trouble Hello, I configure TSM integration with TEC, all work fine, but episodically TSM stop sending events (without any error messages about this). This situation occurred two times: 1. TSM 5.2.2.0 and TEC 3.9FP02 on same mashine with RH 7.3. (After restart TSM all work) 2. TSM 5.2.2.0(or 5.2.3.0, I can't remember) on Windows 2000 SP4 and TEC 3.9FP02 on RH 7.3 Any ideas? Thanks
Re: Preparing a tape storage pool volume for reuse
Rob, I couldn't agree more with Mark. Please read the introduction to TSM. When I look at the name of your copy storage pool (3581_week2) it seems that you are still working in a full/incremental way. This is not how TSM works. This is about the 'progressive backup' in TSM and taken from the TSM Concepts Redbook: [Progressive backup] Saves time and disk space by backing up only new files and modified files. The progressive backup feature uses its own relational database to track data wherever it is stored, delivering direct one-step file restore. This eliminates the need for base-plus-incrementals tapes, commonly used for restore procedures in other storage management products. Furthermore, reclamation isn't something that 'fits' in your backup strategy. It is something that is part of TSM and should be used; it has nothing to do with your backup strategy. Again, please refer to the Redbooks provided by IBM... (http://publib.boulder.ibm.com/infocenter/tivihelp/index.jsp) Regards, Tim -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Rob Berendt Sent: maandag 28 maart 2005 19:12 To: ADSM-L@VM.MARIST.EDU Subject: Re: Preparing a tape storage pool volume for reuse Judging by one of your other emails, is reclaimation a process to merge partial tapes together? If so, that really doesn't interest us. It doesn't fit into our backup strategy. Rob Berendt -- Group Dekko Services, LLC Dept 01.073 PO Box 2000 Dock 108 6928N 400E Kendallville, IN 46755 http://www.dekko.com Mark D. Rodriguez [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 03/25/2005 03:56 PM Please respond to ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU To ADSM-L@VM.MARIST.EDU cc Subject Re: [ADSM-L] Preparing a tape storage pool volume for reuse Rob, Again this is a fundamental concept in TSM as I stated in my previous post I think you will need to develop your skill set in the TSM area. No, you do not want to do DELete VOLume! What you should be doing on some regular basis is running reclamation on that storage pool. Reclamation will then empty the partially used tapes. Please refer to the admin guide where you will find several sections discussing managing storage pools and volumes. -- Regards, Mark D. Rodriguez President MDR Consulting, Inc. === MDR Consulting The very best in Technical Training and Consulting. IBM Advanced Business Partner SAIR Linux and GNU Authorized Center for Education IBM Certified Advanced Technical Expert, CATE AIX Support and Performance Tuning, RS6000 SP, TSM/ADSM and Linux Red Hat Certified Engineer, RHCE === Rob Berendt wrote: Unlike my previous post regarding a BACKUP DB volume, now I have a question about a Copy Storage Pool tape volume. After I used a tape volume for backup stg backuppool lto_3581_week2 I want to reuse it. Do I just: delete volume 12wk2 discarddata=yes wait=no Are there any other steps I need? If I am running TSM 5.2.2 on OS/400 V5R3 under PASE, do I need to INZTAP also? Rob Berendt -- Group Dekko Services, LLC Dept 01.073 PO Box 2000 Dock 108 6928N 400E Kendallville, IN 46755 http://www.dekko.com
Re: Tsm TEC trouble
and things such as an admin sched of BEGIN EVENTLOGGING TIVOLI to run every 24 hours can be very handy... (helps recover from any connectivity problems with your TEC server) Dwight E. Cook Systems Management Integration Professional, Advanced Integrated Storage Management TSM Administration (918) 835-3106 (local Tulsa OK) (877) 625-4186 T/L 349-4361 Loren Cain [EMAIL PROTECTED] ONASP.COM To Sent by: ADSM: ADSM-L@VM.MARIST.EDU Dist Stor cc Manager [EMAIL PROTECTED] Subject .EDU Re: Tsm TEC trouble 03/30/2005 07:56 AM Please respond to ADSM: Dist Stor Manager Here's one possibility: If the TEC server is not up or not accessible when the TSM server starts, the Tivoli event logging will be disabled. You can restart it with the BEGIN EVENTLOGGING TIVOLI command. This has been happening to me sporadically because sometimes the TSM server starts before the Tivoli TEC gateway starts (they both run on the same physical machine). Apparently TSM does not try to contact TEC again after the initial failure. Loren Cain Digicon -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Chernyaev Sergey Sent: Monday, January 31, 2005 3:58 AM To: ADSM-L@VM.MARIST.EDU Subject: Tsm TEC trouble Hello, I configure TSM integration with TEC, all work fine, but episodically TSM stop sending events (without any error messages about this). This situation occurred two times: 1. TSM 5.2.2.0 and TEC 3.9FP02 on same mashine with RH 7.3. (After restart TSM all work) 2. TSM 5.2.2.0(or 5.2.3.0, I can't remember) on Windows 2000 SP4 and TEC 3.9FP02 on RH 7.3 Any ideas? Thanks
ENCRYPTKEY
I have a client that is trying to set up encryption for some files. TSM 5.3 client: ENCRYPTIONTYPE AES128 ENCRYPTKEYSAVE The first time he used the GUI to backup the files he was prompted, but there was no indication that the INCLUDE.ENCRYPT files were encrypted. Is there a way to see from the backup (DSMSCHED.LOG with VERBOSE) that files were encrypted? This client is a bank and he needs to prove to the auditors that files are being encrypted. After the Bank of America tape loss incident, they auditors are understandably nervous. Bill Boyer Growing old is mandatory, growing up is optional - ??
[no subject]
(from the Windows Administrator's Guide, page 201) [When checking in a single volume into an automated library,] a REPLY command is not required if you specify a wait time of zero using the optional WAITTIME parameter on the CHECKIN LIBVOLUME command. The default wait time is 60 minutes. -- Mark Stapleton ([EMAIL PROTECTED]) Office 262.521.5627
Re: 3590 K series
Anybody out there know how long 3590 K series tapes last ( I assume in years). I am trying to figure if our recent batch of tape/drive errors are from tape drives and old tapes. Seem to be older number tapes giving the errors, Would appreciate any knowledge on the subject or direction of where to find the knowledge. Thank You, Bill Rosette Data Center/IS/Papa Johns International WWJD Stapleton, Mark [EMAIL PROTECTED]To: ADSM-L@VM.MARIST.EDU ERBEE.COM cc: Sent by: ADSM: Subject: Dist Stor Manager [EMAIL PROTECTED] .EDU 03/30/2005 09:58 AM Please respond to ADSM: Dist Stor Manager (from the Windows Administrator's Guide, page 201) [When checking in a single volume into an automated library,] a REPLY command is not required if you specify a wait time of zero using the optional WAITTIME parameter on the CHECKIN LIBVOLUME command. The default wait time is 60 minutes. -- Mark Stapleton ([EMAIL PROTECTED]) Office 262.521.5627
Re: ENCRYPTKEY
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of William Boyer I have a client that is trying to set up encryption for some files. TSM 5.3 client: ENCRYPTIONTYPE AES128 ENCRYPTKEYSAVE The first time he used the GUI to backup the files he was prompted, but there was no indication that the INCLUDE.ENCRYPT files were encrypted. Is there a way to see from the backup (DSMSCHED.LOG with VERBOSE) that files were encrypted? This client is a bank and he needs to prove to the auditors that files are being encrypted. After the Bank of America tape loss incident, they auditors are understandably nervous. The easiest way (in fact, the only way I know how) to prove the file is encrypted is to attempt to restore the file to an alternate server; the TSM client will request the encryption key, and will not perform the restore without it. The machine that owns the file has the encryption key embedded in the Windows registry. That is why, when you restore the file to the original machine, the restoration deencryption is transparent. That is also why, when you restore the file to the original machine after it has been rebuilt, that the encryption key is requested. If the transparent restore makes the auditors nervous, have the customer remind the auditors that loss of control of the server console makes any security impossible. It would also behoove all of us to be reminded that, once a TSM client password becomes known to (or is guessed by) malefactors, encryption and data security are greatly compromised. -- Mark Stapleton ([EMAIL PROTECTED]) Office 262.521.5627
Re: Tsm TEC trouble
That's exactly the workaround I was just about to implement. I presume there is no harm in issuing this command multiple times? As far as I can see there is no problem doing that, but you never know. The weirdest problems are the ones that don't manifest themselves until after you've done something a thousand times and only then run out of some resource you never knew you were using... Loren Cain Digicon -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Dwight Cook Sent: Wednesday, March 30, 2005 9:36 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: Tsm TEC trouble and things such as an admin sched of BEGIN EVENTLOGGING TIVOLI to run every 24 hours can be very handy... (helps recover from any connectivity problems with your TEC server) Dwight E. Cook Systems Management Integration Professional, Advanced Integrated Storage Management TSM Administration (918) 835-3106 (local Tulsa OK) (877) 625-4186 T/L 349-4361 Loren Cain [EMAIL PROTECTED] ONASP.COM To Sent by: ADSM: ADSM-L@VM.MARIST.EDU Dist Stor cc Manager [EMAIL PROTECTED] Subject .EDU Re: Tsm TEC trouble 03/30/2005 07:56 AM Please respond to ADSM: Dist Stor Manager Here's one possibility: If the TEC server is not up or not accessible when the TSM server starts, the Tivoli event logging will be disabled. You can restart it with the BEGIN EVENTLOGGING TIVOLI command. This has been happening to me sporadically because sometimes the TSM server starts before the Tivoli TEC gateway starts (they both run on the same physical machine). Apparently TSM does not try to contact TEC again after the initial failure. Loren Cain Digicon -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Chernyaev Sergey Sent: Monday, January 31, 2005 3:58 AM To: ADSM-L@VM.MARIST.EDU Subject: Tsm TEC trouble Hello, I configure TSM integration with TEC, all work fine, but episodically TSM stop sending events (without any error messages about this). This situation occurred two times: 1. TSM 5.2.2.0 and TEC 3.9FP02 on same mashine with RH 7.3. (After restart TSM all work) 2. TSM 5.2.2.0(or 5.2.3.0, I can't remember) on Windows 2000 SP4 and TEC 3.9FP02 on RH 7.3 Any ideas? Thanks
Re: 3590 K series
Oh, sure, blame the media. (old joke :-) In http://www.thic.org/pdf/Oct00/imation.jgoins.001003.pdf Imation says that for the Avanced Metal Particle 1 tape formulation used in 3590 that media life should be expected to be 15 - 30 years, with 5 - 10% magnetization loss after 15 years. The greater issue is how well the tapes were made in their batch, and how they were handled and the atmospheric conditions in which they were used. I've seen some new tapes arrive with ripples because of poor winding during manufacturing. Tape is tape, and being open to the air, lots can happen to them. Richard Sims On Mar 30, 2005, at 9:58 AM, William Rosette wrote: Anybody out there know how long 3590 K series tapes last ( I assume in years). I am trying to figure if our recent batch of tape/drive errors are from tape drives and old tapes. Seem to be older number tapes giving the errors, Would appreciate any knowledge on the subject or direction of where to find the knowledge. Thank You, Bill Rosette Data Center/IS/Papa Johns International WWJD
Re: 3590 K series
I'm sure it really depends on the number of mounts and reads/write cycles that the tape goes through. The problem with the 3590E tapes is that once they are taken out of the library, the number of mounts is lost, so actual mounts per tape is a pure guess if you have offsite copypool tapes that you rotate through. The last time I looked at the tape warranty and on the manufactures web site, I got the impression that the average expected life of a lightly used tape (written once, read only a few times, such as an archive) to be at least 10 years. We typically re-write all our data to new media about every 5 years when we migrate to new tape media, (i.e. 3590A to 3590E, more recently, 3590E to 3592), so I haven't really worried about it too much. Oh ya, we also have copypools of almost everything, so that too takes the worry out of a single reaching it's end of life. Ben -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of William Rosette Sent: Wednesday, March 30, 2005 7:58 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: 3590 K series Anybody out there know how long 3590 K series tapes last ( I assume in years). I am trying to figure if our recent batch of tape/drive errors are from tape drives and old tapes. Seem to be older number tapes giving the errors, Would appreciate any knowledge on the subject or direction of where to find the knowledge. Thank You, Bill Rosette Data Center/IS/Papa Johns International WWJD Stapleton, Mark [EMAIL PROTECTED]To: ADSM-L@VM.MARIST.EDU ERBEE.COM cc: Sent by: ADSM: Subject: Dist Stor Manager [EMAIL PROTECTED] .EDU 03/30/2005 09:58 AM Please respond to ADSM: Dist Stor Manager (from the Windows Administrator's Guide, page 201) [When checking in a single volume into an automated library,] a REPLY command is not required if you specify a wait time of zero using the optional WAITTIME parameter on the CHECKIN LIBVOLUME command. The default wait time is 60 minutes. -- Mark Stapleton ([EMAIL PROTECTED]) Office 262.521.5627
Re: ANR0209E Page address mismatch detected on recovery log
== On Wed, 30 Mar 2005 07:25:17 -0500, Richard Sims [EMAIL PROTECTED] said: I rue the day that IBM started encouraging customers to take their TSM system out of service and run salvage utilities to reorganize the db, as situations like this inevitably result, particularly as these utilities are not subject to the same development intensity and scrutiny as mainline TSM code. This has been a very poor decision on someone's part in IBM, to foster this kind of risky undertaking in enterprise sites as though it were a casual, risk-free activity. Some vendor thinking is just unfathomable. I don't share Richard's tropism away from the offline utilities. However, embarking on any such process without a DB incremental immediately previous is, well, foolhardy. I think of the motorcyclists I sometimes see, on the highway with shorts, a tank-top, flip-flops and sunglasses in leiu of helmet. If you run regular DB fulls, and cut incrementals before you do anything scary, you limit your downside to inconvenience and a setback schedule. I highly recommend the practice. BTW, I've promoted my DB reload procedure to our main site. Thanks greatly to those of you who commented. I continue to solicit experiences of before and after sizes, and comments about behavior before and after. http://open-systems.ufl.edu/services/NSAM/maint_docs/db_un_reload.html - Allen S. Rout
Old tapes
Oh mighty Gurus. Please forgive my naive question.. We are running out of slots in our library and I have examined some of the tapes and have found that some of them haven't been read for 1 1/2 years and some haven't been written to in 3 or 4 years. Can I eject these tapes and store them in a rack? I tried 5 of them and used the following commands: update volume vol loc=shelf checkout libv lib vol checkl=no rem=b Is this kosher? Thanks! DaveZ
DR access to 3494 tapelibrary
Never got a reply to this, so just in case it never got posted: Our DR tests of using a backup TSM server with the exisiting 3494 tape libraries ran into problems. The setup: - both the DR TSM server and the Prod TSM server are connected to the switch and the libraries (lmcp) points and the devices show active. However, the addressing on each server is slightly different. The test: - to test the prod DB is restored to the DR server, which works fine. The problem continues to be accessing the library. - after the last test failure I took an hour during the daily TSM prod cycle and: 1). brought down the PROD TSM and kept it down during the test 2). recycled the DR TSM ( with the hostname and I.P. address of the PROD TSM) so it could establish the addressing from scratch 3). brought up the DR TSM, then brought up TSM. Unfortunately from my previous test I had deleted the library defs and so could not test them coming up automaticly. However, I was able to successfully able to define the library to TSM this time, but then it saw all the volumes in the library as checked out. I was noit able to define this previously when I had not thought it necessary to recycle the DR TSM. Kept getting I/O errors. My thinking is: - if the library and device definitions were in place when I brought up the DR TSM it would have had access to the library and volumes in the library - the recycle of the DR TSM is neccessay after the PROD TSM is down and before bringing up the DR TSM to replace the addressing so that it matches the previous addressing on the PROD TSM ( 1Z-08-02 becomes 1Z-08-01) Any thoughts or experience with the use of a library in this situation? I tried this because I noticed that with both servers connected to the switch that distinct addresses are generated for each set of devices. So restoring the prod TSM DB and bringing it up it appears to see these devices on the DR TSM server as not the same as the devices it used when it was the DB was saved off. However, having the prod TSM server down and recycling DR TSM server prior to starting TSM on the DR server restablishes the addresses on server so they are the primary addresses ( 01) and allows the library and devices to be recognized and defined. At least that's my theory. The limited testing I was able to do suggests that it true. [tsmserv] /home/root # lsdev -Cc tape lmcp0 Available LAN/TTY Library Management Control Point lmcp1 Available LAN/TTY Library Management Control Point rmt0 Available 1H-08-01 IBM 3590 Tape Drive and Medium Changer (FCP) rmt1 Available 1H-08-01 IBM 3590 Tape Drive and Medium Changer (FCP) rmt2 Available 1Z-08-01 IBM 3590 Tape Drive and Medium Changer (FCP) rmt3 Available 1Z-08-01 IBM 3590 Tape Drive and Medium Changer (FCP) rmt4 Available 1Z-08-01 IBM 3590 Tape Drive and Medium Changer (FCP) rmt5 Available 1Z-08-01 IBM 3590 Tape Drive and Medium Changer (FCP) [tsmserv2] /home/root # lsdev -Cc tape lmcp0 Available LAN/TTY Library Management Control Point lmcp1 Available LAN/TTY Library Management Control Point rmt2 Available 1Z-08-02 IBM 3590 Tape Drive and Medium Changer (FCP) rmt3 Available 1Z-08-02 IBM 3590 Tape Drive and Medium Changer (FCP) rmt4 Available 1Z-08-02 IBM 3590 Tape Drive and Medium Changer (FCP) rmt5 Available 1Z-08-02 IBM 3590 Tape Drive and Medium Changer (FCP)
Re: Old tapes
#1, what's your retention for this data if you don't need it reuse the tapes. #2 if they aren't at 100% do move data on them to free up the tapes that way. #3 if your solution calls for long term storage then just check them out and you should be good to go. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Dave Zarnoch Sent: Wednesday, March 30, 2005 10:17 AM To: ADSM-L@VM.MARIST.EDU Subject: Old tapes Oh mighty Gurus. Please forgive my naive question.. We are running out of slots in our library and I have examined some of the tapes and have found that some of them haven't been read for 1 1/2 years and some haven't been written to in 3 or 4 years. Can I eject these tapes and store them in a rack? I tried 5 of them and used the following commands: update volume vol loc=shelf checkout libv lib vol checkl=no rem=b Is this kosher? Thanks! DaveZ
Re: Old tapes
Quick answer. User the query media and move media commands. Query can show you in order, how long tapes have not been used. Move media then allows you to move (er checkout) tapes that haven't been accessed in a certain number of days. If one of these tapes is later needed, TSM will prompt for it. David B. Longo System Administrator Health First, Inc. 3300 Fiske Blvd. Rockledge, FL 32955-4305 PH 321.434.5536 Pager 321.634.8230 Fax:321.434.5509 [EMAIL PROTECTED] [EMAIL PROTECTED] 03/30/2005 11:17:04 AM Oh mighty Gurus. Please forgive my naive question.. We are running out of slots in our library and I have examined some of the tapes and have found that some of them haven't been read for 1 1/2 years and some haven't been written to in 3 or 4 years. Can I eject these tapes and store them in a rack? I tried 5 of them and used the following commands: update volume vol loc=shelf checkout libv lib vol checkl=no rem=b Is this kosher? Thanks! DaveZ ## This message is for the named person's use only. It may contain confidential, proprietary, or legally privileged information. No confidentiality or privilege is waived or lost by any mistransmission. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it, and notify the sender. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. Health First reserves the right to monitor all e-mail communications through its networks. Any views or opinions expressed in this message are solely those of the individual sender, except (1) where the message states such views or opinions are on behalf of a particular entity; and (2) the sender is authorized by the entity to give such views or opinions. ##
Re: Old tapes
Sorry, I think maybe you were also looking for clarification on your checkout command. This is what we use. checkout libvolume library volume checklabel=yes -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Dave Zarnoch Sent: Wednesday, March 30, 2005 10:17 AM To: ADSM-L@VM.MARIST.EDU Subject: Old tapes Oh mighty Gurus. Please forgive my naive question.. We are running out of slots in our library and I have examined some of the tapes and have found that some of them haven't been read for 1 1/2 years and some haven't been written to in 3 or 4 years. Can I eject these tapes and store them in a rack? I tried 5 of them and used the following commands: update volume vol loc=shelf checkout libv lib vol checkl=no rem=b Is this kosher? Thanks! DaveZ
Re: Old tapes
We have had to do this in the past to free up library space. Rather than using the checkout libvol command, I would suggest using the functions within the TSM server to store tapes outside of the library: the move media command. Do a 'help move media' for how it works. Here is an example command I have used that would check tapes out of the library from our I_TAPEPOOL storagepool that have not been touched in 60 days: move media * stg=I_TAPEPOOL wherestate=mountableinlib wherestatus=full day=60 ovflocation='Bldg26 rack' Ben -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Owings, Don Sent: Wednesday, March 30, 2005 9:23 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: Old tapes #1, what's your retention for this data if you don't need it reuse the tapes. #2 if they aren't at 100% do move data on them to free up the tapes that way. #3 if your solution calls for long term storage then just check them out and you should be good to go. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Dave Zarnoch Sent: Wednesday, March 30, 2005 10:17 AM To: ADSM-L@VM.MARIST.EDU Subject: Old tapes Oh mighty Gurus. Please forgive my naive question.. We are running out of slots in our library and I have examined some of the tapes and have found that some of them haven't been read for 1 1/2 years and some haven't been written to in 3 or 4 years. Can I eject these tapes and store them in a rack? I tried 5 of them and used the following commands: update volume vol loc=shelf checkout libv lib vol checkl=no rem=b Is this kosher? Thanks! DaveZ
Re: Preparing a tape storage pool volume for reuse
On Mon, 28 Mar 2005 12:11:38 -0500, Rob Berendt [EMAIL PROTECTED] wrote: Judging by one of your other emails, is reclaimation a process to merge partial tapes together? If so, that really doesn't interest us. It doesn't fit into our backup strategy. May I suggest that perhaps your backup strategy doesn't fit the operational model of TSM? You really can't force TSM into an old-fashioned full-and-incremental strategy, at least not well, and if you're dead-set on trying to do that, then perhaps you should reconsider your choice to use TSM. Kelly
ANR0425W Something or Nothing?
This is for a client Oracle TDP on Solaris 8 with TSM Server W2K, v 5.1.6.3. Simple question, is warning message ANR0425W password has expired anything to worry about? Because I can't seem to make it go away and it doesn't seem to be stopping the backups? The help file shows, System Action: Server operation continues. I have tried update node, changed password exp on server to and 0, removing password file on client side. The TDP documentation stays that the password must be set to generate, which it is. This is from my logs: ANR2017I Administrator ADMIN issued command: SET PASSEXP 0 node=mynode_ora ANR2199I Password expiration period for node MYNODE_ORA set to 0 days. ANR0406I Session 6297 started for node MYNODE_ORA (SUN SOLARIS) (Tcp/Ip 1.1.1.1 (-0)). ANR0425W Session 6297 for node MYNODE_ORA (SUN SOLARIS) refused - password has expired. ANR0406I Session 6300 started for node MYNODE_ORA (TDP Oracle SUN) (Tcp/Ip 1.1.1.1(-0)). ANR0403I Session 6358 ended for node MYNODE_ORA (TDP Oracle SUN). ANR0403I Session 6357 ended for node MYNODE_ORA (TDP Oracle SUN). ANR2507I Schedule NOW_DB for domain DATA_DOMAIN started at 03/30/2005 08:53:57 for node MYNODE_ORA completed successfully at 03/30/2005 09:57:03. ANR0403I Session 6297 ended for node MYNODE_ORA (SUN SOLARIS). ANR0406I Session 6359 started for node MYNODE_ORA (SUN SOLARIS) (Tcp/Ip 1.1.1.1(-0)). ANR0425W Session 6359 for node MYNODE_ORA (SUN SOLARIS) refused - password has expired. ANR0403I Session 6359 ended for node MYNODE_ORA (SUN SOLARIS). Thanks, Mark Bertrand
Archive very, very slow
We recently migrated from a locally attached 3590 E11 tape drive to two 3592 tape drives in a 3494 tape library. We installed TSM 5.2.4.0 on a p5 570 lpar running AIX 5.3. Our data is on an IBM ESS 800. Every day we quiese the application and flash copy it then mount the flash copy volume groups to another system and backup. We were just doing the native backup to the 3590 E11 locally attached drives. Then we mounted the flash copy to the TSM server and did an archive. The four volume groups comprise about 400G of data 95% being in CACHE.DAT files, one which is about 200G in size. The problem is the archive over fibre is taking 12-14 hours to complete. We were backing up to the 3590 local attached tape drives using native commands in about 8 hours. The Aggregate data transfer rate: 10,793.34 KB/sec seems network speed and we are using fibre attached tape drives and ESS storage. The data is mounted to the TSM server so the TSM server is also the client and the data should not be going over the network at all. We have looked at ESS 800 performance of LUNs, software compression, various settings including shmport and commMethod sharedmem and have not been able to come up with anything to make the backup run faster. We have a pmr open at IBM but it has not produced any useful information that would resolve the problem. Has anyone else ever seen anything like this? Ila Z. Miller ___ ___ Health Care Information Systems University of Iowa Hospitals Clinics [EMAIL PROTECTED] Phone: 319.356.0067 FAX: 319.356.3521 Notice: This e-mail (including attachments) is covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is confidential and may be legally privileged. If you are not the intended recipient, you are hereby notified that any retention, dissemination, distribution, or copying of this communication is strictly prohibited. Please reply to the sender that you have received the message in error, then delete it. Thank you.
Re: Archive very, very slow
On Mar 30, 2005, at 2:14 PM, Miller, Ila wrote: ...The data is mounted to the TSM server so the TSM server is also the client and the data should not be going over the network at all. ... Just a minor thought: Your COMMMethod is probably TCPIP, meaning that the I/O would be going through the TCP/IP stack via localhost. You might try COMMMethod SHAREDMEM as a more efficient method for that co-residency situation, and to see if any beneficial impact (which might point to a TCP/IP issue). Beyond that, all the usual tuning values. And someone may be able to contribute based upon similar configuration experience. Richard Sims
Re: Archive very, very slow
We also recently migrated from SCSI attached 3590E drives to SAN attached 3592 drives (both in a 3494 library). Unfortunately, we only saw an increase in the performance with the new tape drives. As Richard mentioned, it may be an issue with the mounting of the data on the host, but I will throw in a few things to perhaps check on the Tape drive configuration. - Are you using the latest and greatest ATAPE and ATLDD drivers? Mine are a little old, but you should at least be at these levels: Atape.driver 9.0.7.0 atldd.driver 5.5.1.0 - Are the drives defined to TSM as a 3592 drives and not Generic or something? Here is a little look at one of mine: tsm: TSMXq drive f=d Library Name: BOITAPELIB1 Drive Name: 3592DRV0 Device Type: 3592 On-Line: Yes Read Formats: 3592C,3592 Write Formats: 3592C,3592 Element: Drive State: LOADED Allocated to: WWN: Serial Number: 07XX5 Last Update by (administrator): BBULLOCK Last Update Date/Time: 02/10/05 12:17:54 Cleaning Frequency (Gigabytes/ASNEEDED/NONE): - On the SAN ports, are you sure that all the drives are linked up as 2GB devices? - If you have multiple FC cards, have you enabled multipathing to take advantage of it? (a nice feature to have, but probably not a contributer to your issues). Ben -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Miller, Ila Sent: Wednesday, March 30, 2005 12:15 PM To: ADSM-L@VM.MARIST.EDU Subject: Archive very, very slow We recently migrated from a locally attached 3590 E11 tape drive to two 3592 tape drives in a 3494 tape library. We installed TSM 5.2.4.0 on a p5 570 lpar running AIX 5.3. Our data is on an IBM ESS 800. Every day we quiese the application and flash copy it then mount the flash copy volume groups to another system and backup. We were just doing the native backup to the 3590 E11 locally attached drives. Then we mounted the flash copy to the TSM server and did an archive. The four volume groups comprise about 400G of data 95% being in CACHE.DAT files, one which is about 200G in size. The problem is the archive over fibre is taking 12-14 hours to complete. We were backing up to the 3590 local attached tape drives using native commands in about 8 hours. The Aggregate data transfer rate: 10,793.34 KB/sec seems network speed and we are using fibre attached tape drives and ESS storage. The data is mounted to the TSM server so the TSM server is also the client and the data should not be going over the network at all. We have looked at ESS 800 performance of LUNs, software compression, various settings including shmport and commMethod sharedmem and have not been able to come up with anything to make the backup run faster. We have a pmr open at IBM but it has not produced any useful information that would resolve the problem. Has anyone else ever seen anything like this? Ila Z. Miller ___ ___ Health Care Information Systems University of Iowa Hospitals Clinics [EMAIL PROTECTED] Phone: 319.356.0067 FAX: 319.356.3521 Notice: This e-mail (including attachments) is covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is confidential and may be legally privileged. If you are not the intended recipient, you are hereby notified that any retention, dissemination, distribution, or copying of this communication is strictly prohibited. Please reply to the sender that you have received the message in error, then delete it. Thank you.
Re: Old tapes SOLVED
Oh mighty ones!! Thank you so much for all your help! I was able to move 100 tapes out of the silo I used the move media command. DaveZ
Re: ANR0425W Something or Nothing?
You are correct Richard, my version's command is tdpoconf password. This prompts you for the existing password and the twice for the new one. I have successfully used this to change the password as with the GUI on the server side and the command line on the server side. I have successfully made it worse, where I was unable to communicate with the server at all. At this point it is working but I still get 0425. I guess I just want to know if I can ignore this if there is not a fix. Thanks -Original Message- From: Richard Sims [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 30, 2005 12:16 PM To: Mark Bertrand Subject: Re: ANR0425W Something or Nothing? Mark - I'm not an Oracle user, but I believe there is a tdpoconf command with that DP, having a password subcommand. Richard Sims On Mar 30, 2005, at 11:45 AM, Mark Bertrand wrote: This is for a client Oracle TDP on Solaris 8 with TSM Server W2K, v 5.1.6.3. Simple question, is warning message ANR0425W password has expired anything to worry about? Because I can't seem to make it go away and it doesn't seem to be stopping the backups? The help file shows, System Action: Server operation continues. I have tried update node, changed password exp on server to and 0, removing password file on client side. The TDP documentation stays that the password must be set to generate, which it is. This is from my logs: ANR2017I Administrator ADMIN issued command: SET PASSEXP 0 node=mynode_ora ANR2199I Password expiration period for node MYNODE_ORA set to 0 days. ANR0406I Session 6297 started for node MYNODE_ORA (SUN SOLARIS) (Tcp/Ip 1.1.1.1 (-0)). ANR0425W Session 6297 for node MYNODE_ORA (SUN SOLARIS) refused - password has expired. ANR0406I Session 6300 started for node MYNODE_ORA (TDP Oracle SUN) (Tcp/Ip 1.1.1.1(-0)). ANR0403I Session 6358 ended for node MYNODE_ORA (TDP Oracle SUN). ANR0403I Session 6357 ended for node MYNODE_ORA (TDP Oracle SUN). ANR2507I Schedule NOW_DB for domain DATA_DOMAIN started at 03/30/2005 08:53:57 for node MYNODE_ORA completed successfully at 03/30/2005 09:57:03. ANR0403I Session 6297 ended for node MYNODE_ORA (SUN SOLARIS). ANR0406I Session 6359 started for node MYNODE_ORA (SUN SOLARIS) (Tcp/Ip 1.1.1.1(-0)). ANR0425W Session 6359 for node MYNODE_ORA (SUN SOLARIS) refused - password has expired. ANR0403I Session 6359 ended for node MYNODE_ORA (SUN SOLARIS). Thanks, Mark Bertrand
Re: Archive very, very slow
COMMMethod is set to SHAREDMEM and has been that way from the start. I'm got tracing turned on now so we will see if that reveals anything. Here is the summary of our archive from last night. Network(FIBER) throughput seems to be ok but the Aggregate is abysmal. Compression is also turned off since we aren't going over ethernet and HW compression is turned on at the tape drive. We are backing up ~32000 file, some in the 50-60G range. Total number of objects inspected: 158,353 Total number of objects archived:31,927 Total number of objects updated: 0 Total number of objects rebound: 0 Total number of objects deleted: 0 Total number of objects expired: 0 Total number of objects failed: 2 Total number of bytes transferred:459.45 GB Data transfer time: 927.99 sec Network data transfer rate:519,159.18 KB/sec Aggregate data transfer rate: 8,740.44 KB/sec Objects compressed by:0% Elapsed processing time: 15:18:40 Gary Galloway ___ ___ Health Care Information Systems University of Iowa Hospitals Clinics -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Richard Sims Sent: Wednesday, March 30, 2005 1:52 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Archive very, very slow On Mar 30, 2005, at 2:14 PM, Miller, Ila wrote: ...The data is mounted to the TSM server so the TSM server is also the client and the data should not be going over the network at all. ... Just a minor thought: Your COMMMethod is probably TCPIP, meaning that the I/O would be going through the TCP/IP stack via localhost. You might try COMMMethod SHAREDMEM as a more efficient method for that co-residency situation, and to see if any beneficial impact (which might point to a TCP/IP issue). Beyond that, all the usual tuning values. And someone may be able to contribute based upon similar configuration experience. Richard Sims
Re: Archive very, very slow
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Galloway, Gary M COMMMethod is set to SHAREDMEM and has been that way from the start. I'm got tracing turned on now so we will see if that reveals anything. Here is the summary of our archive from last night. Network(FIBER) throughput seems to be ok but the Aggregate is abysmal. Compression is also turned off since we aren't going over ethernet and HW compression is turned on at the tape drive. We are backing up ~32000 file, some in the 50-60G range. Total number of objects inspected: 158,353 Total number of objects archived:31,927 Total number of objects updated: 0 Total number of objects rebound: 0 Total number of objects deleted: 0 Total number of objects expired: 0 Total number of objects failed: 2 Total number of bytes transferred:459.45 GB Data transfer time: 927.99 sec Network data transfer rate:519,159.18 KB/sec Aggregate data transfer rate: 8,740.44 KB/sec Objects compressed by:0% Elapsed processing time: 15:18:40 I've got customers that would love to have 8MB/sec aggregates! Note your transfer time (930 seconds); this makes your throughput rate, once data transfer starts, 495MB/sec. You might be having a lot of retries; they run up your total backup time without adding to the amount of data being transfered. See how many retries you see in your dsmsched.log. -- Mark Stapleton ([EMAIL PROTECTED]) IBM Certified Advanced Deployment Professional Tivoli Storage Management Solutions 2005 Office 262.521.5627
Re: VolHistory-Question
Daniel, one can remove last database backup using an undocumented parameter force=yes in the delete volhist command. S pozdravem / Best Regards, Martin Trcka, IT Consultant Tech. Support Department GC System a.s., Spitalka 41, 60200 Brno, Czech Rep. mob: +420 602 452 361 fax: +420 543 537 333 email: [EMAIL PROTECTED] Daniel Sparrman napsal(a): One of the issues with database backups... you cannot remove the last database backup for a particular device class... Best Regards Daniel Sparrman --- Daniel Sparrman Chef Utveckling Drift Exist i Stockholm AB Propellervgen 6B 183 62 TBY Vxel: 08 - 754 98 00 Mobil: 070 - 399 27 51 Christoph Pilgram [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 2005-03-23 11:26 Please respond to ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU To ADSM-L@VM.MARIST.EDU cc Subject VolHistory-Question Hi all, In my VolumeHistory I have an entry for a dbsnapshot to a tape-device-class (for analysing an error by IBM) : Date/Time: 11/25/04 18:12:19 Volume Type: DBSNAPSHOT Backup Series: 1 Backup Operation: 0 Volume Seq: 1 Device Class: 3590DEVCL Volume Name: 000805 Volume Location: Command: I took the tape out of the library some times ago. How can I delete the entry in the Volume-History. I tried 'delete volhist todate=today -4 type=dbsnapshot'. == ANR2467I DELETE VOLHISTORY: 0 sequential volume history entries were successfully deleted. 'delete volhist todate=today -4 type=dbsnapshot devcl=3590devcl' == ANR6978E DELETE VOLHISTORY: Invalid device class 3590DEVCL If I try to delete the volume from GUI, I can not choose devclass=3590DEVCL. Thanks for help Chr. Pilgram Boehringer Ingelheim Pharma GmbH Co.KG IT Department
Re: Archive very, very slow
I turned on tracing and ran an archive with the following command: dsmc archive -traceflag=service,memory -tracefile=/tmp/tsm/trace/dbext_trace.out -tracemax=5000 -verbose -desc=Old IDX Tape Backups for /restore/dbext - 2005Mar30 -filelist=/tmp/tsm/archive_list_dbext_2005Mar30 -archmc=AIX-1YEAR Here is the summary: IBM Tivoli Storage Manager Command Line Backup/Archive Client Interface - Version 5, Release 2, Level 3.0 (c) Copyright by IBM Corporation and other(s) 1990, 2004. All Rights Reserved. Archive function invoked. Node Name: IDX_RESTORE Session established with server TSMNIM01: AIX-RS/6000 Server Version 5, Release 2, Level 4.0 Data compression forced off by the server Server date/time: 03/30/05 14:16:48 Last access: 03/30/05 14:13:11 Total number of objects inspected: 865 Total number of objects archived: 8 Total number of objects updated: 0 Total number of objects rebound: 0 Total number of objects deleted: 0 Total number of objects expired: 0 Total number of objects failed: 0 Total number of bytes transferred:98.15 GB Data transfer time: 323.03 sec Network data transfer rate:318,611.16 KB/sec Aggregate data transfer rate: 31,063.43 KB/sec Objects compressed by:0% Elapsed processing time: 00:55:13 Can someone explain how tuning on tracing would give me increased transfer rate? This is not the same archive we have been having issues with, but this same one took almost 3 ours earlier this week. Gary Galloway ___ ___ Health Care Information Systems University of Iowa Hospitals Clinics [EMAIL PROTECTED] Phone: 319.356.7036 -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Ben Bullock Sent: Wednesday, March 30, 2005 2:01 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Archive very, very slow We also recently migrated from SCSI attached 3590E drives to SAN attached 3592 drives (both in a 3494 library). Unfortunately, we only saw an increase in the performance with the new tape drives. As Richard mentioned, it may be an issue with the mounting of the data on the host, but I will throw in a few things to perhaps check on the Tape drive configuration. - Are you using the latest and greatest ATAPE and ATLDD drivers? Mine are a little old, but you should at least be at these levels: Atape.driver 9.0.7.0 atldd.driver 5.5.1.0 - Are the drives defined to TSM as a 3592 drives and not Generic or something? Here is a little look at one of mine: tsm: TSMXq drive f=d Library Name: BOITAPELIB1 Drive Name: 3592DRV0 Device Type: 3592 On-Line: Yes Read Formats: 3592C,3592 Write Formats: 3592C,3592 Element: Drive State: LOADED Allocated to: WWN: Serial Number: 07XX5 Last Update by (administrator): BBULLOCK Last Update Date/Time: 02/10/05 12:17:54 Cleaning Frequency (Gigabytes/ASNEEDED/NONE): - On the SAN ports, are you sure that all the drives are linked up as 2GB devices? - If you have multiple FC cards, have you enabled multipathing to take advantage of it? (a nice feature to have, but probably not a contributer to your issues). Ben -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Miller, Ila Sent: Wednesday, March 30, 2005 12:15 PM To: ADSM-L@VM.MARIST.EDU Subject: Archive very, very slow We recently migrated from a locally attached 3590 E11 tape drive to two 3592 tape drives in a 3494 tape library. We installed TSM 5.2.4.0 on a p5 570 lpar running AIX 5.3. Our data is on an IBM ESS 800. Every day we quiese the application and flash copy it then mount the flash copy volume groups to another system and backup. We were just doing the native backup to the 3590 E11 locally attached drives. Then we mounted the flash copy to the TSM server and did an archive. The four volume groups comprise about 400G of data 95% being in CACHE.DAT files, one which is about 200G in size. The problem is the archive over fibre is taking 12-14 hours to complete. We were backing up to the 3590 local attached tape drives using native commands in about 8 hours.
ADSM.org URL added to the TSM support website!
Posting at the request of Darrius Plantz ([EMAIL PROTECTED]) ADSM.org URL added to the TSM support website! Please see the IBM Tivoli Storage Manager website at: http://www-306.ibm.com/software/sysmgmt/products/support/IBMTivoliStorag eManager.html Look for the section titled Other resources You will see a link there titled: ADSM.org regards Darrius Plantz Customer Satisfaction Quality Analyst IBM/Tivoli
Re: ANR0209E Page address mismatch detected on recovery log
I want to add a comment. The point to me is that an audit db FAILS to detect and correct the error. Period. And thats is not good since we reley on our db to read our tapes. An unload may discover a corruption and we have the possibilities to audit or dump our db. And when thoose option fails.. somebody wont get happy and you loose data. In Antons case I dont know what the solution is besides a restore from a previus db backup. ANR0209E Page address mismatch detected on recovery log volume ADSMRE.RCVLOG2B, ANR0209E logical page 0 (physical page 18688); actual: 129024. In an other case like this below, is something you DONT want to see. The TSM server starts and you can do backup, restores, migration and reclamation etc. Some backup are sucessfull and some fails with: 15-02-2005 21:15:36 ANR0406I Session 1941 started for node ST-WZ07 (WinNT) (Tcp/Ip 143.97.143.52(1449)). (SESSION: 1941) 15-02-2005 21:15:37 ANR0102E imbkins.c(4103): Error 1 inserting row in table Backup.Objects. (SESSION: 1941) 15-02-2005 21:15:37 ANR0530W Transaction failed for session 1941 for node ST-WZ07 (WinNT) - internal server error detected. (SESSION: 1941) (Cleanup backup groups) Unload DB failed Dump DB ok Load DB failed Audit DB... = restore db later on ANR4177I AUDITDB: Primary backup entry for an object (0.57126454) cannot be found - entry will be deleted. ANR4177I AUDITDB: Primary backup entry for an object (0.57128288) cannot be found - entry will be deleted. ANR4306I AUDITDB: Processed 72911226 database entries (cumulative). ANR4306I AUDITDB: Processed 73139460 database entries (cumulative). ANR4306I AUDITDB: Processed 73325165 database entries (cumulative). ANR4306I AUDITDB: Processed 73441006 database entries (cumulative). ANRD imaudit.c(776): ThreadId0 Audit of one or more secondary tables failed, objRc=0, expRc=0, grpRc=4 Callchain of previous message: 7C59BBF3 RaiseException()+56 - 1000F969 tsmInitializeServer()+8139 - 104E6399 outTextf()+1469 - 10222EBB tsmInitializeServer()+21B68B - ANR4142I AUDITDB: Database audit process terminated in error. Wort a note: Anton used TSM 5.2.1.0 on an Z/OS. In the other was a w2k server with 5.2.2.5 involved. //Henrik [EMAIL PROTECTED] Sent by: To: ADSM-L@VM.MARIST.EDU ADSM: Dist cc: (bcc: Henrik Wahlstedt) Stor ManagerSubject: Re: ANR0209E Page address mismatch detected on recovery log [EMAIL PROTECTED] RIST.EDU 2005-03-30 18:04 Please respond to ADSM: Dist Stor Manager == On Wed, 30 Mar 2005 07:25:17 -0500, Richard Sims [EMAIL PROTECTED] said: I rue the day that IBM started encouraging customers to take their TSM system out of service and run salvage utilities to reorganize the db, as situations like this inevitably result, particularly as these utilities are not subject to the same development intensity and scrutiny as mainline TSM code. This has been a very poor decision on someone's part in IBM, to foster this kind of risky undertaking in enterprise sites as though it were a casual, risk-free activity. Some vendor thinking is just unfathomable. I don't share Richard's tropism away from the offline utilities. However, embarking on any such process without a DB incremental immediately previous is, well, foolhardy. I think of the motorcyclists I sometimes see, on the highway with shorts, a tank-top, flip-flops and sunglasses in leiu of helmet. If you run regular DB fulls, and cut incrementals before you do anything scary, you limit your downside to inconvenience and a setback schedule. I highly recommend the practice. BTW, I've promoted my DB reload procedure to our main site. Thanks greatly to those of you who commented. I continue to solicit experiences of before and after sizes, and comments about behavior before and after. http://open-systems.ufl.edu/services/NSAM/maint_docs/db_un_reload.html - Allen S. Rout --- The information contained in this message may be CONFIDENTIAL and is intended for the addressee only. Any unauthorised use, dissemination of the information or copying of this message is prohibited. If you are not the addressee, please notify the sender immediately by return e-mail and delete this message. Thank you.
