tsmve 7.1 / 7.1.0.2 configuration problems
hello, something is wrong with the tsmve 7.1.0.2 assistant. after configuration with the assistant, backup and restores with the web-gui client is working well. but if i trie to backup a vm like dsmc backup vm xxxthe data is stored under the datamover node, not under the datacenter node. the proxy agent and target relationships seems ok. any ideas? with best regards Stefan Savoric
Re: tsmve 7.1 / 7.1.0.2 configuration problems
Hello You have to load the dsmc with the appropriate NODENAME (datacenter node) So create another dsm.opt with it (e.g dsm_datacenter.opt) and load it as: dsmc -optfile=dsm_datacenter.opt Regards -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of TSM Sent: Thursday, July 10, 2014 10:45 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] tsmve 7.1 / 7.1.0.2 configuration problems hello, something is wrong with the tsmve 7.1.0.2 assistant. after configuration with the assistant, backup and restores with the web-gui client is working well. but if i trie to backup a vm like dsmc backup vm xxxthe data is stored under the datamover node, not under the datacenter node. the proxy agent and target relationships seems ok. any ideas? with best regards Stefan Savoric
Antwort: Re: tsmve 7.1 / 7.1.0.2 configuration problems
Hello Robert, that was my workaround. Is this the only solution? Also i have to define new schedule and cad. thank you. Robert Ouzen rou...@univ.haifa.ac.il Gesendet von: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 10.07.2014 09:52 Bitte antworten an ADSM: Dist Stor Manager An: ADSM-L@VM.MARIST.EDU Kopie: Thema: Re: tsmve 7.1 / 7.1.0.2 configuration problems Hello You have to load the dsmc with the appropriate NODENAME (datacenter node) So create another dsm.opt with it (e.g dsm_datacenter.opt) and load it as: dsmc -optfile=dsm_datacenter.opt Regards -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of TSM Sent: Thursday, July 10, 2014 10:45 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] tsmve 7.1 / 7.1.0.2 configuration problems hello, something is wrong with the tsmve 7.1.0.2 assistant. after configuration with the assistant, backup and restores with the web-gui client is working well. but if i trie to backup a vm like dsmc backup vm xxxthe data is stored under the datamover node, not under the datacenter node. the proxy agent and target relationships seems ok. any ideas? with best regards Stefan Savoric
Re: Antwort: Re: tsmve 7.1 / 7.1.0.2 configuration problems
Hi Stefan I woks that way ... Look the option asnode too Best Regards Robert Haifa University Israel -ORIGINAL MESSAGE- FROM: ADSM: DIST STOR MANAGER [MAILTO:ADSM-L@VM.MARIST.EDU] ON BEHALF OF TSM SENT: THURSDAY, JULY 10, 2014 11:17 AM TO: ADSM-L@VM.MARIST.EDU SUBJECT: [ADSM-L] ANTWORT: RE: TSMVE 7.1 / 7.1.0.2 CONFIGURATION PROBLEMS HELLO ROBERT, THAT WAS MY WORKAROUND. IS THIS THE ONLY SOLUTION? ALSO I HAVE TO DEFINE NEW SCHEDULE AND CAD. THANK YOU. ROBERT OUZEN rou...@univ.haifa.ac.il GESENDET VON: ADSM: DIST STOR MANAGER ADSM-L@VM.MARIST.EDU 10.07.2014 09:52 BITTE ANTWORTEN AN ADSM: DIST STOR MANAGER AN: ADSM-L@VM.MARIST.EDU KOPIE: THEMA: RE: TSMVE 7.1 / 7.1.0.2 CONFIGURATION PROBLEMS HELLO YOU HAVE TO LOAD THE DSMC WITH THE APPROPRIATE NODENAME (DATACENTER NODE) SO CREATE ANOTHER DSM.OPT WITH IT (E.G DSM_DATACENTER.OPT) AND LOAD IT AS: DSMC -OPTFILE=DSM_DATACENTER.OPT REGARDS -ORIGINAL MESSAGE- FROM: ADSM: DIST STOR MANAGER [MAILTO:ADSM-L@VM.MARIST.EDU] ON BEHALF OF TSM SENT: THURSDAY, JULY 10, 2014 10:45 AM TO: ADSM-L@VM.MARIST.EDU SUBJECT: [ADSM-L] TSMVE 7.1 / 7.1.0.2 CONFIGURATION PROBLEMS HELLO, SOMETHING IS WRONG WITH THE TSMVE 7.1.0.2 ASSISTANT. AFTER CONFIGURATION WITH THE ASSISTANT, BACKUP AND RESTORES WITH THE WEB-GUI CLIENT IS WORKING WELL. BUT IF I TRIE TO BACKUP A VM LIKE DSMC BACKUP VM XXXTHE DATA IS STORED UNDER THE DATAMOVER NODE, NOT UNDER THE DATACENTER NODE. THE PROXY AGENT AND TARGET RELATIONSHIPS SEEMS OK. ANY IDEAS? WITH BEST REGARDS STEFAN SAVORIc
Re: APARs fixed in TSM 7.1.0.100
Hi, Missing the issue probably. This interim fix contains no apar fixes seems pretty clear. Also I suspect IBM is blocking google search bots (forcing ppl to use their wonderful search engine) as more and more results on google point to dead links @ ibm. Op 9 jul. 2014 11:55 schreef BEYERS Kurt kurt.bey...@vrt.be: Hello everybody, I'm in the process of upgrading our TSM servers from TSM 6.3.4 to TSM 7.1 because the latter version is a prerequisite for the Oracle T1D tape drives we will start using. I would have preferred to wait for TSM 7.1.1, but that does not fit the into the planning. I've seen that a patch level 7.1.0.100 is available for download. I've tried to find the APAR's that are solved in it, especially for TSM Server, but the only thing I've found so far is for the OC: copy APARs fixed in level 7.1.0.100 This interim fix does not include APAR fixes. It updates Operations Center V7.1.0 so that you can run the Operations Center on Linux on an IBM Power Systems server. /copy I've also checked the README.html included in the bin file, but their they refer only to links towards the Information Center / Knowledge Center. So does anybody knows the URL where you can find the APAR's fixed for TSM 7.1.0.100. If it is restricted towards running the OC in a new environment, I'll skip the upgrade. Although the quest to find the fixed APAR's is taking longer then the actual install itself would consume. IBM is getting worse than Oracle, their MOS website is also a jungle where you get lost easily. :( Thanks for any answers in advance! Best regards, Kurt *** Disclaimer *** Vlaamse Radio- en Televisieomroeporganisatie Auguste Reyerslaan 52, 1043 Brussel nv van publiek recht BTW BE 0244.142.664 RPR Brussel http://www.vrt.be/gebruiksvoorwaarden
TSM and AS/400
Hi, I have been asked to evaluate the possibility to take a backup from AS/400 (Power720 - v6.1) to TSM (I don't know anything about AS/400). I looked on the info and I understand we need something called Backup Recovery and Media Services for iSeries, I have a few questions: 1. Is it supported for all current TSM servers, v7.1 for example ? 2. I understand I need Tivoli Storage Manager Application Programming Interface for IBM i - TSM API for iSeries - but I couldn't find it ? 3. It says BRMS officially supports and tests ONLY IBM Tape Media Libraries, IBM tape drives , IBM Virtual Tape Libraries (VTL), IBM optical drives and Tivoli Storage manager(TSM). Is this for backup direct from the BRMS to the IBM libraries and tapes, or it also includes LAN-free to TSM's libraries and tapes ? 4. And to connect to the previous question (if yes), do you think EMC DataDomain posing as a IBM library (IBM 3584) can fool it ? Regards, Tuncel Değerli görüş ve önerilerinizi internet sayfamızdaki Bize Ulaşın bölümünden iletebilirsiniz. Bu e-posta ve muhtemel eklerinde verilen bilgiler kişiye özel ve gizli olup, yalnızca mesajda belirlenen alıcı ile ilgilidir. Size yanlışlıkla ulaşmışsa lütfen göndericiye bilgi veriniz, mesajı siliniz ve içeriğini başka bir kişiye açıklamayınız, herhangi bir ortama kopyalamayınız. Bu mesaj veya ekleri, aksi sözleşme ile veya mesaj içeriğinde açıkça belirtilmedikçe, herhangi bir işleme ilişkin olarak Bankamız adına herhangi bir teklif, kabul veya teyit amacı taşımamaktadır. Verilen bilgilerin doğru veya eksiksiz olmasına yönelik bir garanti verilmemekte olup, bilgiler önceden bildirilmeksizin değiştirilebilecektir. Bu mesajın içeriği Bankamızın resmi görüşlerini yansıtmayabileceğinden Akbank T.A.Ş. hiçbir hukuki sorumluluğu kabul etmez. Akbank T.A.Ş Sabancı Center 4.Levent, 34330 İstanbul - Ticaret Sicil Memurluğu: İstanbul - Sicil Numarası: 90418 - www.akbank.com You are kindly requested to share your valuable views and opinions to us via the Contact Us section on our website. The information provided in this e-mail and any attachments it may contain is proprietary and confidential, and is only related with the receiver of this message. If it is sent to you by mistake; please inform the sender, delete the message and do not explain its contents to anyone, and do not copy it in any form. Unless otherwise provided by contract, this message is not intended to act as a banking transaction such as an offer, purchase or sale of a financial transaction or confirmation of a remittance. No guarantee is given for the accuracy or integrity of any or all information provided herein and such information may be changed without prior notice. Akbank T.A.Ş. acknowledges no legal responsibility whatsoever as may be related with or arise out of the content of this message as it may not reflect the official policy of our Bank. Akbank T.A.Ş Sabancı Center 4.Levent, 34330 İstanbul - Trade Registry Office: İstanbul - Registration Number: 90418 - www.akbank.com
Re: TSM and AS/400
I have been asked to evaluate the possibility to take a backup from AS/400 (Power720 - v6.1) to TSM (I don't know anything about AS/400). I looked on the info and I understand we need something called Backup Recovery and Media Services for iSeries, I have a few questions: Been there done that. - Yes, you need BRMS, which is a pay-for AS/400 backup application. BRMS will normally write to a local tape drive attached to the AS/400/Iseries/Power box. When you add the TSM API, it isn't really a client, it's more like a driver - it just adds another destination for BRMS. The BRMS person sets up and runs jobs just like before, except now in addition to writing to a local drive, if he specifies TSM as the destination, data can go over the network to TSM. Restores are done through BRMS, and retention is also controlled by BRMS. (If you've ever set up the TSM TDP agent for Oracle, this works much the same way.) Instructions are in the redbook SG24-7031 from www.redbooks.ibm.com. I've never installed BRMS, so I can't help you there, I don't know how good the instructions in the redbook are. But if the AS/400 guy has BRMS working on the AS/400/Iseries/Power already, all you need is Chap. 9 in the redbook to get the TSM connection working. However, a couple of things you need to know: - BRMS uses the TSM API very inefficiently. If you have more than about 500GB per day you need to back up from the AS/400, you are unlikely to be happy with the results. If the AS/400/Iseries/Power is currently writing to fast local tape drives, say LTO5, you probably will be unhappy with performance of the API. If it is currently writing to slower drives, say LTO3, then it may be suitable for you to switch to the API. I've also had success with one customer by having them change their scheduling to run jobs in parallel instead of sequentially so as to get done even with the slower throughput. (If you don't have BRMS already, I suggest you ask your IBM rep for a trial before you buy.) -The TSM API doesn't provide a complete solution. You can use BRMS to back up what I think they call data libraries from the AS/400/Iseries. But you still have to use a local device to create your system backup. (It's sort of like a mksysb to AIX, in that it's your bootable OS recovery method in case you have to go to a DR site and recover on another box.) 1. Is it supported for all current TSM servers, v7.1 for example ? I'm not sure to what degree it's supported. It works, because it's just the client API. (Supported in IBM terms means not only that it works but that they will take problem reports for it. I don't know it they are still doing that.) But I have 1 customer using it on a 6.3.4 server and another on 7.1 server with no issues (but they back up less than 500 GB per day each). 2. I understand I need Tivoli Storage Manager Application Programming Interface for IBM i - TSM API for iSeries - but I couldn't find it ? It's on the FTP site, but you have to know where to look - it hasn't changed since V5 and is listed under OS400. Here's the link to the latest one I know of: ftp://ftp.software.ibm.com/storage/tivoli-storage-management/maintenance/client/v5r5/OS400/v554/5.5.4.0-TIV-TSMBAC-OS400.README_api_enu.htm 3. It says BRMS officially supports and tests ONLY IBM Tape Media Libraries, IBM tape drives , IBM Virtual Tape Libraries (VTL), IBM optical drives and Tivoli Storage manager(TSM). Is this for backup direct from the BRMS to the IBM libraries and tapes, or it also includes LAN-free to TSM's libraries and tapes ? That is for BRMS going direct to a locally attached tape. When you use the TSM API, the data goes from BRMS across the network via TCP/IP to TSM just like any ordinary backup client (windows, linux, etc.), then the TSM server provides the device support for the back end. So you can use any storage device that is attached to your TSM server, and the data can migrate through the TSM hierarchy from disk to tape, etc. There is no LAN_free support from BRMS to TSM. 4. And to connect to the previous question (if yes), do you think EMC DataDomain posing as a IBM library (IBM 3584) can fool it ? Yes, see previous answer. BRMS doesn't know what device the data lands on, it knows only that the TSM server has it. Wanda
VM backup fails with ANS1907E - object merger operation error
TSM4VE 7.1, TSM 6.3.4.300, datamover on a W2K8 VM: ANS1228E Sending of object 'VMUSMOSS10WEB1' failed. ANS1907E An error occurred while trying to perform an object merge operation on the server. All the web hits for ANS1907E seem to be old API issues... The weird thing is that sometimes it works, sometimes it doesn't. Steve STEPHEN STACKWICK | Senior Consultant | 301.518.6352 (m) | stephen.stackw...@icfi.commailto:sstackw...@icfi.com | icfi.comhttp://www.icfi.com/ ICF INTERNATIONAL | 7125 Thomas Edison Dr, Suite 100, Columbia, Md 21046 | 443-573-0524, 443-718-4900 (o)
Re: TSM and AS/400
Hi, Wanda Thanks for the help ! Not having LAN-free capabilities and not being able to backup the system are very serious disadvantages. I also looked around at the FTP site and found Latest maintenance is at ftp://ftp.software.ibm.com/storage/tivoli-storage-management/maintenance/client/v6r1/OS400/v615/ (v6.1.5.0) Latest patch is at ftp://ftp.software.ibm.com/storage/tivoli-storage-management/patches/client/v6r1/OS400/v615/ (v6.1.5.5) Versions 6.1,5.5 and 5.4 are supported, 5.3 is EOS. Best Regards, Tuncel Mutlu -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Prather, Wanda Sent: Thursday, July 10, 2014 6:16 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: TSM and AS/400 I have been asked to evaluate the possibility to take a backup from AS/400 (Power720 - v6.1) to TSM (I don't know anything about AS/400). I looked on the info and I understand we need something called Backup Recovery and Media Services for iSeries, I have a few questions: Been there done that. - Yes, you need BRMS, which is a pay-for AS/400 backup application. BRMS will normally write to a local tape drive attached to the AS/400/Iseries/Power box. When you add the TSM API, it isn't really a client, it's more like a driver - it just adds another destination for BRMS. The BRMS person sets up and runs jobs just like before, except now in addition to writing to a local drive, if he specifies TSM as the destination, data can go over the network to TSM. Restores are done through BRMS, and retention is also controlled by BRMS. (If you've ever set up the TSM TDP agent for Oracle, this works much the same way.) Instructions are in the redbook SG24-7031 from www.redbooks.ibm.com. I've never installed BRMS, so I can't help you there, I don't know how good the instructions in the redbook are. But if the AS/400 guy has BRMS working on the AS/400/Iseries/Power already, all you need is Chap. 9 in the redbook to get the TSM connection working. However, a couple of things you need to know: - BRMS uses the TSM API very inefficiently. If you have more than about 500GB per day you need to back up from the AS/400, you are unlikely to be happy with the results. If the AS/400/Iseries/Power is currently writing to fast local tape drives, say LTO5, you probably will be unhappy with performance of the API. If it is currently writing to slower drives, say LTO3, then it may be suitable for you to switch to the API. I've also had success with one customer by having them change their scheduling to run jobs in parallel instead of sequentially so as to get done even with the slower throughput. (If you don't have BRMS already, I suggest you ask your IBM rep for a trial before you buy.) -The TSM API doesn't provide a complete solution. You can use BRMS to back up what I think they call data libraries from the AS/400/Iseries. But you still have to use a local device to create your system backup. (It's sort of like a mksysb to AIX, in that it's your bootable OS recovery method in case you have to go to a DR site and recover on another box.) 1. Is it supported for all current TSM servers, v7.1 for example ? I'm not sure to what degree it's supported. It works, because it's just the client API. (Supported in IBM terms means not only that it works but that they will take problem reports for it. I don't know it they are still doing that.) But I have 1 customer using it on a 6.3.4 server and another on 7.1 server with no issues (but they back up less than 500 GB per day each). 2. I understand I need Tivoli Storage Manager Application Programming Interface for IBM i - TSM API for iSeries - but I couldn't find it ? It's on the FTP site, but you have to know where to look - it hasn't changed since V5 and is listed under OS400. Here's the link to the latest one I know of: ftp://ftp.software.ibm.com/storage/tivoli-storage-management/maintenance/client/v5r5/OS400/v554/5.5.4.0-TIV-TSMBAC-OS400.README_api_enu.htm 3. It says BRMS officially supports and tests ONLY IBM Tape Media Libraries, IBM tape drives , IBM Virtual Tape Libraries (VTL), IBM optical drives and Tivoli Storage manager(TSM). Is this for backup direct from the BRMS to the IBM libraries and tapes, or it also includes LAN-free to TSM's libraries and tapes ? That is for BRMS going direct to a locally attached tape. When you use the TSM API, the data goes from BRMS across the network via TCP/IP to TSM just like any ordinary backup client (windows, linux, etc.), then the TSM server provides the device support for the back end. So you can use any storage device that is attached to your TSM server, and the data can migrate through the TSM hierarchy from disk to tape, etc. There is no LAN_free support from BRMS to TSM. 4. And to connect to the previous question (if yes), do you think EMC DataDomain posing as a IBM library (IBM 3584) can fool it ? Yes, see
Re: Backup fails with no error message
of314fe45a.773f8b60-on87257d0e.006e2dd7-85257d0e.006f9...@us.ibm.com 73a8ba4a53ee4dcea9852cbfa85a6...@by2pr05mb631.namprd05.prod.outlook.com of6d738e72.2896199c-on87257d11.000d1ce9-85257d11.000ef...@us.ibm.com In-Reply-To: of6d738e72.2896199c-on87257d11.000d1ce9-85257d11.000ef...@us.ibm.com Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [147.140.233.16] x-microsoft-antispam: BCL:0;PCL:0;RULEID: x-forefront-prvs: 0268246AE7 x-forefront-antispam-report: SFV:NSPM;SFS:(6009001)(189002)(199002)(377424004)(51704005)(377454003)(85714005)(479174003)(13464003)(93886003)(77982001)(99286002)(15975445006)(76482001)(20776003)(2171001)(87936001)(2656002)(33646001)(64706001)(105586002)(19580405001)(92566001)(88552001)(15202345003)(79102001)(101416001)(50986999)(66066001)(19580395003)(107886001)(83322001)(76176999)(31966008)(99396002)(83072002)(46102001)(76576001)(85306003)(74662001)(106356001)(74316001)(54356999)(95666004)(19625735002)(81342001)(86362001)(74502001)(551544002)(89122001)(80022001)(21056001)(107046002)(85852003)(81542001)(75432001)(108616002)(567094001)(24736002);DIR:OUT;SFP:;SCL:1;SRVR:BY2PR05MB629;H:BY2PR05MB631.namprd05.prod.outlook.com;FPR:;MLV:sfv;PTR:InfoNoRecords;MX:1;LANG:en; Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: jefferson.edu X-VPM-MSG-ID: e00d0915-4ef0-4ad4-b390-b317d5f556a7 X-VPM-HOST: xvm127.jefferson.edu X-VPM-GROUP-ID: ca56bb30-8f8c-4377-8f9e-1371248b9de3 X-VPM-ENC-REGIME: Plaintext X-VPM-CERT-FLAG: 0 X-VPM-IS-HYBRID: 0 X-Barracuda-Connect: zixgateway01.jefferson.edu[147.140.20.158] X-Barracuda-Start-Time: 1405010793 X-Barracuda-Encrypted: AES256-SHA X-Barracuda-URL: http://148.100.49.28:8000/cgi-mod/mark.cgi X-Virus-Scanned: by bsmtpd at marist.edu X-Barracuda-BRTS-Status: 1 X-Barracuda-Spam-Score: 0.00 X-Barracuda-Spam-Status: No, SCORE=0.00 using global scores of TAG_LEVEL=3.5 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=5.5 tests= X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.3.7405 Rule breakdown below pts rule name description -- -- The error log entries for each day usually include a few messages about files not found or files that changed while TSM was reading them. There is a warning message each day noting that a specific directory is excluded. The directory is named in an 'exclude.dir' statement and is the top level directory for a file system listed in a 'domain' statement. I have asked th= e system vendor for clearance to remove the file system from the domain statement. I have not gotten a response so far. There are no messages that have any evident connection to the exit status of 12 or to stopping the backup prematurely. The file system in which the backup stopped from June 27 to July 7 has about 12.6 GB of free space. The file system in which the backup stopped yesterday has about 6.5 GB of free space. The file system used for TSM logs has about 3.8 GB of free space. Neither of the file systems in which the backup stopped at one time or another has millions of files; a successful backup of the entire resource group early this morning inspected 559,009 files. The backup that got a segmentation fault apparently ran out of stack space; the error report in the output from 'errpt -a' includes the words 'Too many stack elements'. The soft limit on the stack size for root is 65,536 512 by= te blocks. The hard limit is 8,388,608 blocks. Are there any published recommendations for resource limits for the TSM client? I looked over the other error reports in the output from 'errpt -a'. I didn= 't find anything recognizably relevant around the times when 'dsmc' ended with exit status 12, in the interval between the successful /main/UT backup on June 26 and the failed backup on June 27, or in the interval between the success /main/U backup on July 8 and the failed backup on July 9 Thomas Denier Thomas Jefferson University Hospital -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of An= drew Raibeck Sent: Wednesday, July 09, 2014 10:44 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Backup fails with no error message It is a puzzler. Just to verify: you have checked dsmerror.log as well for error messages an= d found nothing? Another thought is to check the TSM server activity log fo= r any tell tale error or warning messages that might provide a hint. The TSM client return codes are derived directly from the severity of the m= essages issued during whatever operation is running. ANSI messages are = RC 0; ANSW are RC 8; and ANSE or ANSS are RC 12. The exceptions= are related to skipped files: these exception messages are ANSE but = the return code handling sets the RC to 4. The highest severity prevails, s= o if, for example, an
Upgrade from 5.5 to 7.1 Extractdb/insertdb seems to pause?
The extractdb and insertdb phase of the upgrade seems to be paused. It's been 40 min and the # bytes read and # records inserted/extracted haven't changed. The disk is being hit hard by the db2syscs process to the database volumes. I've never seen the extract phase do this before. This is my first time for a production upgrade. The source is 30GB at 50% used. During the 3:20 the extract has been running this pause has occurred twice. First time for about 50-min and now fo the past 40-min. Is this normal now for V7.1 upgrades from V5? It's almost like it's doing the update phase during the extract/insert phase. Bill Boyer DSS, Inc. (610) 927-4407 Enjoy life. It has an expiration date. - ??
Re: Backup fails with no error message
Thomas, Neither myself nor a knowledgeable colleague I checked with can think of anything definitive that would cause the client to blow the stack like that (we do not have any specific best practice recommendations in this area). It is conceivable that these issues are all rooted in the same cause. If you still have the SERVICE trace file(s) from the time of the core, you could open a PMR and submit that for us to look at. Maybe we could find something in the trace, like anomalous recursion in the file system, that leads to this. If you go this route, let me know the PMR number. Also, did you happen to run down Matthew Glanville's suggestion from the other day? Maybe something odd is going on with the mount point(s) for the involved file systems. Regards, - Andy Andrew Raibeck | Tivoli Storage Manager Level 3 Technical Lead | stor...@us.ibm.com IBM Tivoli Storage Manager links: Product support: http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/Tivoli_Storage_Manager Online documentation: https://www.ibm.com/developerworks/mydeveloperworks/wikis/home/wiki/Tivoli +Documentation+Central/page/Tivoli+Storage+Manager Product Wiki: https://www.ibm.com/developerworks/mydeveloperworks/wikis/home/wiki/Tivoli +Storage+Manager/page/Home ADSM: Dist Stor Manager ADSM-L@vm.marist.edu wrote on 2014-07-10 12:46:28: From: Thomas Denier thomas.den...@jefferson.edu To: ADSM-L@vm.marist.edu Date: 2014-07-10 12:47 Subject: Re: Backup fails with no error message Sent by: ADSM: Dist Stor Manager ADSM-L@vm.marist.edu The error log entries for each day usually include a few messages about files not found or files that changed while TSM was reading them. There is a warning message each day noting that a specific directory is excluded. The directory is named in an 'exclude.dir' statement and is the top level directory for a file system listed in a 'domain' statement. I have asked th= e system vendor for clearance to remove the file system from the domain statement. I have not gotten a response so far. There are no messages that have any evident connection to the exit status of 12 or to stopping the backup prematurely. The file system in which the backup stopped from June 27 to July 7 has about 12.6 GB of free space. The file system in which the backup stopped yesterday has about 6.5 GB of free space. The file system used for TSM logs has about 3.8 GB of free space. Neither of the file systems in which the backup stopped at one time or another has millions of files; a successful backup of the entire resource group early this morning inspected 559,009 files. The backup that got a segmentation fault apparently ran out of stack space; the error report in the output from 'errpt -a' includes the words 'Too many stack elements'. The soft limit on the stack size for root is 65,536 512 by= te blocks. The hard limit is 8,388,608 blocks. Are there any published recommendations for resource limits for the TSM client? I looked over the other error reports in the output from 'errpt -a'. I didn= 't find anything recognizably relevant around the times when 'dsmc' ended with exit status 12, in the interval between the successful /main/UT backup on June 26 and the failed backup on June 27, or in the interval between the success /main/U backup on July 8 and the failed backup on July 9 Thomas Denier Thomas Jefferson University Hospital -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of An= drew Raibeck Sent: Wednesday, July 09, 2014 10:44 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Backup fails with no error message It is a puzzler. Just to verify: you have checked dsmerror.log as well for error messages an= d found nothing? Another thought is to check the TSM server activity log fo= r any tell tale error or warning messages that might provide a hint. The TSM client return codes are derived directly from the severity of the m= essages issued during whatever operation is running. ANSI messages are = RC 0; ANSW are RC 8; and ANSE or ANSS are RC 12. The exceptions= are related to skipped files: these exception messages are ANSE but = the return code handling sets the RC to 4. The highest severity prevails, s= o if, for example, an ANSW (RC 8) and ANSE (RC 12) are issued, then= the RC will be 12. We have had the odd skipped file message that is not = setting the RC to 4, but those have been fixed via APARs, and in any case I= would still expect some error message in the log. If you inspect the error= log, let me The GlobalRC trace example I showed you illustrates when a non-zero produ= cing message sets the return code. Thus when whatever message is processed = that trips the RC 12, I would expect to see it in the trace. If you have tr= ace files from when the problem did not occur, and the RC was
