Fwd: ERROR: ANS1312E Server media mount not possible
Note: forwarded message attached. __ Do you Yahoo!? Yahoo! Mail - You care about security. So do we. http://promotions.yahoo.com/new_mail---BeginMessage--- Note: forwarded message attached. __ Do you Yahoo!? Yahoo! Mail Address AutoComplete - You start. We finish. http://promotions.yahoo.com/new_mail---BeginMessage--- Hi All, I'm using TSM server 5.2 on IBM AIX 5.2 and facing the following MESSEAGE while running backup. ANS1312E Server media mount not possible I'm junor at TSM, so anybody can show me how to debug the things ? Thank you in advance, Tinh __ Do you Yahoo!? Yahoo! Mail is new and improved - Check it out! http://promotions.yahoo.com/new_mail ---End Message--- ---End Message---
Re: Fwd: ERROR: ANS1312E Server media mount not possible
I'm using TSM server 5.2 on IBM AIX 5.2 and facing the following MESSEAGE while running backup. ANS1312E Server media mount not possible I'm junor at TSM, so anybody can show me how to debug the things ? You don't mention that you've looked up that client message, so the first step would be to do that, either in the TSM Messages manual (accessible via http://publib.boulder.ibm.com/tividd/td/tdprodlist.html) or via 'dsmc help'. Beyond that you can refer to cumulative causes of that message I've compiled in http://people.bu.edu/rbs/ADSM.QuickFacts; and you can search the ADSM-L archives for all the prior postings on that frequently posted message number: www.adsm.org is the most commonly used www.marist.edu/htbin/wlvindex?adsm-l yields a primitive file list You can also email the list administrator from this page. (Be aware that its web server is always slow.) www.mail-archive.com/[EMAIL PROTECTED]/ Richard Sims http://people.bu.edu/rbs
ANS1312E Server Media Mount Not Possible
I have some large servers that have their data bound to a management class which directs the data directly to a primary tape pool. This pool has a copystgpool defined. Therefore, when these clients backup at night, their data is simultaneously written to the onsite and offsite tape copy. My library is a 3584 with 12 LTO1 drives. Everything has been working just great for many months, but on Monday I upgraded the version and the OS on my TSM server. I went from 5.1.6.2 to 5.1.7.3 and from AIX 4.3.3ML9 to AIX 5.1.0ML3. All clients are running the 5.1.5 AIX TSM client. They have been for many months. Since the upgrade, I have started getting the ANS1312E Server Media Mount Not Possible. The RESOURCEUTILIZATION parameter was set to 4 on a few of the clients, but was not set on others. The MAXNUMMP for all the clients was set at the default of 2. As I mentioned, it worked just fine this way before the server upgrade. This morning, I read some other emails of people with a similar problem and one said to raise the MAXNUMMP to 4. I did this, and it started working again. Could someone please explain to me why I needed to do this? Each client is still only mounting two tapes (one for onsite and one for offsite). Was it broken before and now it's fixed, or vice-versa? Thanks! This E-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended only for the use of the Individual(s) named above. If you are not the intended recipient of this E-mail, or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any dissemination or copying of this E-mail is strictly prohibited. If you have received this E-mail in error, please immediately notify us at (865) 374-4900 or notify us by E-mail at [EMAIL PROTECTED]
Re: ANS1312E Server Media Mount Not Possible
The same problem occured for me when I went to release 5.1.7. It is a known problem. You have to increase the Maximum Mount Points Allowed to 999. A fix is in the works, but not yet available. With release 5.1.7, the mount points are not being released. Please refer to IC37274. Thanks, Cynthia Leon Systems Programmer Presbyterian Healthcare Services 2501 Buena Vista SE Albuquerque, NM 87106 505-923-6903 -Original Message- From: Thach, Kevin G [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 15, 2003 7:23 AM To: [EMAIL PROTECTED] Subject: ANS1312E Server Media Mount Not Possible I have some large servers that have their data bound to a management class which directs the data directly to a primary tape pool. This pool has a copystgpool defined. Therefore, when these clients backup at night, their data is simultaneously written to the onsite and offsite tape copy. My library is a 3584 with 12 LTO1 drives. Everything has been working just great for many months, but on Monday I upgraded the version and the OS on my TSM server. I went from 5.1.6.2 to 5.1.7.3 and from AIX 4.3.3ML9 to AIX 5.1.0ML3. All clients are running the 5.1.5 AIX TSM client. They have been for many months. Since the upgrade, I have started getting the ANS1312E Server Media Mount Not Possible. The RESOURCEUTILIZATION parameter was set to 4 on a few of the clients, but was not set on others. The MAXNUMMP for all the clients was set at the default of 2. As I mentioned, it worked just fine this way before the server upgrade. This morning, I read some other emails of people with a similar problem and one said to raise the MAXNUMMP to 4. I did this, and it started working again. Could someone please explain to me why I needed to do this? Each client is still only mounting two tapes (one for onsite and one for offsite). Was it broken before and now it's fixed, or vice-versa? Thanks! This E-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended only for the use of the Individual(s) named above. If you are not the intended recipient of this E-mail, or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any dissemination or copying of this E-mail is strictly prohibited. If you have received this E-mail in error, please immediately notify us at (865) 374-4900 or notify us by E-mail at [EMAIL PROTECTED] == --- PRESBYTERIAN HEALTHCARE SERVICES DISCLAIMER --- This message originates from Presbyterian Healthcare Services or one of its affiliated organizations. It contains information, which may be confidential or privileged, and is intended only for the individual or entity named above. It is prohibited for anyone else to disclose, copy, distribute or use the contents of this message. All personal messages express views solely of the sender, which are not to be attributed to Presbyterian Healthcare Services or any of its affiliated organizations, and may not be distributed without this disclaimer. If you received this message in error, please notify us immediately at [EMAIL PROTECTED] ==
Re: ANS1312E Server Media Mount Not Possible
The same problem occured for me when I went to release 5.1.7. It is a known problem. You have to increase the Maximum Mount Points Allowed to 999. A fix is in the works, but not yet available. With release 5.1.7, the mount points are not being released. Please refer to IC37274. Thanks, Cynthia Leon Systems Programmer Presbyterian Healthcare Services 2501 Buena Vista SE Albuquerque, NM 87106 505-923-6903 -Original Message- From: Thach, Kevin G [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 15, 2003 7:23 AM To: [EMAIL PROTECTED] Subject: ANS1312E Server Media Mount Not Possible I have some large servers that have their data bound to a management class which directs the data directly to a primary tape pool. This pool has a copystgpool defined. Therefore, when these clients backup at night, their data is simultaneously written to the onsite and offsite tape copy. My library is a 3584 with 12 LTO1 drives. Everything has been working just great for many months, but on Monday I upgraded the version and the OS on my TSM server. I went from 5.1.6.2 to 5.1.7.3 and from AIX 4.3.3ML9 to AIX 5.1.0ML3. All clients are running the 5.1.5 AIX TSM client. They have been for many months. Since the upgrade, I have started getting the ANS1312E Server Media Mount Not Possible. The RESOURCEUTILIZATION parameter was set to 4 on a few of the clients, but was not set on others. The MAXNUMMP for all the clients was set at the default of 2. As I mentioned, it worked just fine this way before the server upgrade. This morning, I read some other emails of people with a similar problem and one said to raise the MAXNUMMP to 4. I did this, and it started working again. Could someone please explain to me why I needed to do this? Each client is still only mounting two tapes (one for onsite and one for offsite). Was it broken before and now it's fixed, or vice-versa? Thanks! This E-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended only for the use of the Individual(s) named above. If you are not the intended recipient of this E-mail, or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any dissemination or copying of this E-mail is strictly prohibited. If you have received this E-mail in error, please immediately notify us at (865) 374-4900 or notify us by E-mail at [EMAIL PROTECTED] == --- PRESBYTERIAN HEALTHCARE SERVICES DISCLAIMER --- This message originates from Presbyterian Healthcare Services or one of its affiliated organizations. It contains information, which may be confidential or privileged, and is intended only for the individual or entity named above. It is prohibited for anyone else to disclose, copy, distribute or use the contents of this message. All personal messages express views solely of the sender, which are not to be attributed to Presbyterian Healthcare Services or any of its affiliated organizations, and may not be distributed without this disclaimer. If you received this message in error, please notify us immediately at [EMAIL PROTECTED] ==
Re: ANS1312E Server media mount not possible
think this also: this volume may be full and next storage which is most probably a tapepool need a mount point? Which parameter controls how long a backup session will wait for a mount of a secondary storage pool volume after the primary storage pool fills?
Re: ANS1312E Server media mount not possible
the high and low tresholds of any stg pool determines when the data is moved to the next pool. see below options are from my disk pool which goes to a tape pool when it is 90 % full until it is 50 % full High Mig Pct: 90 this is the percent where your data starts to go next pool Low Mig Pct: 50 until this percent NExt Storage Pool The pool where data goes in these limits tsm: TSM01.MBTq stg backuppool Storage Device Estimated Pct Pct High Low Next Stora- Pool Name Class Name Capacity Util Migr Mig Mig ge Pool (MB) Pct Pct --- -- -- - - --- --- BACKUPPOOL DISK 26 000.0 0.0 0.0 90 50 3583POOL [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 21.08.2002 15:47 Please respond to ADSM-L To: [EMAIL PROTECTED] cc: Subject: Re: ANS1312E Server media mount not possible think this also: this volume may be full and next storage which is most probably a tapepool need a mount point? Which parameter controls how long a backup session will wait for a mount of a secondary storage pool volume after the primary storage pool fills?
Re: ANS1312E Server media mount not possible
Mountwait on the device class of the pool. Kelly J. Lipp Storage Solutions Specialists, Inc. PO Box 51313 Colorado Springs, CO 80949 [EMAIL PROTECTED] or [EMAIL PROTECTED] www.storsol.com or www.storserver.com (719)531-5926 Fax: (240)539-7175 -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Burak Demircan Sent: Wednesday, August 21, 2002 6:05 AM To: [EMAIL PROTECTED] Subject: Re: ANS1312E Server media mount not possible the high and low tresholds of any stg pool determines when the data is moved to the next pool. see below options are from my disk pool which goes to a tape pool when it is 90 % full until it is 50 % full High Mig Pct: 90 this is the percent where your data starts to go next pool Low Mig Pct: 50 until this percent NExt Storage Pool The pool where data goes in these limits tsm: TSM01.MBTq stg backuppool Storage Device EstimatedPctPct High Low Next Stora- Pool NameClass NameCapacity Util Migr Mig Mig ge Pool (MB) Pct Pct --- -- -- - - --- --- BACKUPPOOL DISK 26 000.00.00.0 90 50 3583POOL [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 21.08.2002 15:47 Please respond to ADSM-L To:[EMAIL PROTECTED] cc: Subject:Re: ANS1312E Server media mount not possible think this also: this volume may be full and next storage which is most probably a tapepool need a mount point? Which parameter controls how long a backup session will wait for a mount of a secondary storage pool volume after the primary storage pool fills?
ANS1312E Server media mount not possible
I assume that ANS1312E Server media mount not possible Explanation: Server media mount not possible. The server timed out waiting for a mount of an offline volume. refers to mounting a sequential acess media? If my assumption is correct, under what conditions should a backup process request a server media mount? I am getting ANS1312E for a node which goes to a disk storage pool which has a max size threshold of NOLIMIT. I would not expect it ever to request a server media mount. Any ideas? David EHresman
Re: ANS1312E Server media mount not possible
How about disk is full and all drives are busy so backup goes to secondary storage which is tape? Quoting David E Ehresman [EMAIL PROTECTED]: I assume that ANS1312E Server media mount not possible Explanation: Server media mount not possible. The server timed out waiting for a mount of an offline volume. refers to mounting a sequential acess media? If my assumption is correct, under what conditions should a backup process request a server media mount? I am getting ANS1312E for a node which goes to a disk storage pool which has a max size threshold of NOLIMIT. I would not expect it ever to request a server media mount. Any ideas? David EHresman Fred Johanson
Re: ANS1312E Server media mount not possible
Hi Check the status of volumes q vol Use vary on command to make offline volumes online. Regards Raghu S Nivas Consultant - TSM DCM Data Systems Ltd New Delhi India. e-mail: [EMAIL PROTECTED],[EMAIL PROTECTED] David E Ehresman To: [EMAIL PROTECTED] deehre01@LOUIScc: VILLE.EDU Subject: ANS1312E Server media mount not Sent by: ADSM:possible Dist Stor Manager [EMAIL PROTECTED] ST.EDU 08/20/2002 09:42 PM Please respond to ADSM: Dist Stor Manager I assume that ANS1312E Server media mount not possible Explanation: Server media mount not possible. The server timed out waiting for a mount of an offline volume. refers to mounting a sequential acess media? If my assumption is correct, under what conditions should a backup process request a server media mount? I am getting ANS1312E for a node which goes to a disk storage pool which has a max size threshold of NOLIMIT. I would not expect it ever to request a server media mount. Any ideas? David EHresman
Re: ANS1312E Server media mount not possible
think this also: this volume may be full and next storage which is most probably a tapepool need a mount point?? [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 21.08.2002 07:44 Please respond to ADSM-L To: [EMAIL PROTECTED] cc: Subject: Re: ANS1312E Server media mount not possible Hi Check the status of volumes q vol Use vary on command to make offline volumes online. Regards Raghu S Nivas Consultant - TSM DCM Data Systems Ltd New Delhi India. e-mail: [EMAIL PROTECTED],[EMAIL PROTECTED] David E Ehresman To: [EMAIL PROTECTED] deehre01@LOUIS cc: VILLE.EDU Subject: ANS1312E Server media mount not Sent by: ADSM: possible Dist Stor Manager [EMAIL PROTECTED] ST.EDU 08/20/2002 09:42 PM Please respond to ADSM: Dist Stor Manager I assume that ANS1312E Server media mount not possible Explanation: Server media mount not possible. The server timed out waiting for a mount of an offline volume. refers to mounting a sequential acess media? If my assumption is correct, under what conditions should a backup process request a server media mount? I am getting ANS1312E for a node which goes to a disk storage pool which has a max size threshold of NOLIMIT. I would not expect it ever to request a server media mount. Any ideas? David EHresman
ANS1312E Server media mount not possible
I sometimes get the following error message in client schedule logs. I am using copying data to my tape pools only from a migration from my disk pool. Now, I suspect a node option :MAXNUMMP This option is 1 for all of my nodes (35 nodes) Can it be due to MAXNUMMP option? Is it logical to make this value zero (0) and forbid any node to acquire a drive. I am using TSM 4.2.1.15 on AIX 4.3.3 on F80 Clients are Windows NT/2000 and version is 4.2.1.32 I have 3583 LTO library with 3 drives. Regards, Burak 12-04-2002 19:53:37 Data transfer time: 266.04 sec 12-04-2002 19:53:37 Network data transfer rate: 133.33 KB/sec 12-04-2002 19:53:37 Aggregate data transfer rate: 9.69 KB/sec 12-04-2002 19:53:37 Objects compressed by: 0% 12-04-2002 19:53:37 Elapsed processing time: 01:01:00 12-04-2002 19:53:37 --- SCHEDULEREC STATUS END 12-04-2002 19:53:37 ANS1312E Server media mount not possible
Re: ANS1312E Server media mount not possible
Rolf Meyer wrote: Thats Q OPT Hallo in the tsm dsmc client you can use the command SHOW OPT (I didn't find any docs, tip from our support in Germany) and you will get a complete list of all options. Greetings Rolf Meyer On Thursday, 11. October 2001 21:10, you wrote: How do I check to see what my Resourceutilization is currently set to? -Original Message- From: Rolf Meyer [mailto:[EMAIL PROTECTED]] Sent: Thursday, October 11, 2001 1:41 PM To: [EMAIL PROTECTED] Subject: Re: ANS1312E Server media mount not possible On Thursday, 11. October 2001 18:54, you wrote: Hallo, I saw this message very often because I defined MaxMountPoints = 1 and Resourceutilization = 4. Changed Resourceutil. to the default (which is two). Greetings from Hamburg Rolf Meyer I got the following error in the scheduling of our servers this morning: 10/10/2001 19:01:04 Total number of bytes transferred: 5.22 GB 10/10/2001 19:01:04 Data transfer time: 580.46 sec 10/10/2001 19:01:04 Network data transfer rate: 9,432.76 KB/sec 10/10/2001 19:01:04 Aggregate data transfer rate: 3,792.61 KB/sec 10/10/2001 19:01:04 Objects compressed by: 0% 10/10/2001 19:01:04 Elapsed processing time: 00:02:03 10/10/2001 19:01:04 --- SCHEDULER STATUS END 10/10/2001 19:01:04 ANS1312E Server media mount not possible-?? I also saw it yesterday on a couple of other servers. The logs for those servers are fine now. I'm running 4.1 on the TSM server and all the clients involved are also 4.1. We have been running 4.1 for about 3-4 months and this is first time I've seen something like this come up. I looked over the website at http://search.adsm.org/ http://search.adsm.org/ and I didn't see anything helpful. Most of what I saw was in relation to going from version 3.x to version 4.1. We've been 4.1 for awhile now before the error started to show up so I don't see a relationship. We send the data to a diskpool first and then in the morning everything gets sent to tape. Thanks, David Tyree Microcomputer Specialist South Georgia Medical Center 229.333.1155 Confidential Notice: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.
ANS1312E Server media mount not possible
Hi Can somebody help me. A W2K Server TSM Client vers. 4.1.1 TSM server OS/390 4.1.1.0 StorageTek VSM tape library. When I run a backup, I receive the follow error message: ANS1312E Server media mount not possible Can any tell me what the problem is. Regards, Bo Nielsen FDB dataPhone: +45 4386 4671 Roskildevej 65 Fax: +45 4386 4990 DK-2620 AlbertslundE-mail: [EMAIL PROTECTED] Denmark
Antwort: ANS1312E Server media mount not possible
The client tries to write directly into a sequentiel storage pool and on the server the point MAX MOUNT POINTS for the client ist set to zero. __ Da E-Mails leicht unter fremdem Namen erstellt oder manipuliert werden koennen, muessen wir zu Ihrem und unserem Schutz die rechtliche Verbindlichkeit der vorstehenden Erklaerungen ausschliessen. Die fuer die Stadtsparkasse Koeln geltenden Regeln ueber die Verbindlichkeit von rechtsgeschaeftlichen Erklaerungen mit verpflichtendem Inhalt bleiben unberuehrt.
Re: ANS1312E Server media mount not possible
Answer from dsmc: dsmc h 39 Explanation: Server media mount not possible. The server timed out waiting for a mount of an offline volume. System Action: File skipped. User Response: Retry later when server volumes can be mounted. The server couldn't mount a tape and reached a timeout waiting for it. Look at the server log for the reason. Perhaps all drives are in use or you have no scratch volume in the library or not enough scratch volumes in your storage pool. Bo Nielsen schrieb: Hi Can somebody help me. A W2K Server TSM Client vers. 4.1.1 TSM server OS/390 4.1.1.0 StorageTek VSM tape library. When I run a backup, I receive the follow error message: ANS1312E Server media mount not possible Can any tell me what the problem is. Regards, Bo Nielsen FDB dataPhone: +45 4386 4671 Roskildevej 65 Fax: +45 4386 4990 DK-2620 AlbertslundE-mail: [EMAIL PROTECTED] Denmark -- Mit freundlichen Gren Bernhard Unold begin:vcard n:Unold;Bernhard tel;work:+49 7071/29-80130 x-mozilla-html:FALSE adr:;; version:2.1 email;internet:[EMAIL PROTECTED] fn:Bernhard Unold end:vcard
Re: Antwort: ANS1312E Server media mount not possible
That sounds like that is exactly your problem. I was caught by this when we moved our first server to TSM. I believe 3.7 sets these to 0. You will have to make it something other than 0 for it to work. Jack -Original Message- From: Gisbert Schneider [mailto:[EMAIL PROTECTED]] Sent: Monday, March 05, 2001 6:51 AM To: [EMAIL PROTECTED] Subject: Antwort: ANS1312E Server media mount not possible The client tries to write directly into a sequentiel storage pool and on the server the point MAX MOUNT POINTS for the client ist set to zero. __ Da E-Mails leicht unter fremdem Namen erstellt oder manipuliert werden koennen, muessen wir zu Ihrem und unserem Schutz die rechtliche Verbindlichkeit der vorstehenden Erklaerungen ausschliessen. Die fuer die Stadtsparkasse Koeln geltenden Regeln ueber die Verbindlichkeit von rechtsgeschaeftlichen Erklaerungen mit verpflichtendem Inhalt bleiben unberuehrt.
SV: Antwort: ANS1312E Server media mount not possible
Thanks for the advise. MaxMountPoint was set to 0. I set it to 0, and then the backups run. Regards, Bo Nielsen -- Fra: Palmadesso Jack[SMTP:[EMAIL PROTECTED]] Svar til: ADSM: Dist Stor Manager Sendt:5. marts 2001 14:18 Til: [EMAIL PROTECTED] Emne: Re: Antwort: ANS1312E Server media mount not possible That sounds like that is exactly your problem. I was caught by this when we moved our first server to TSM. I believe 3.7 sets these to 0. You will have to make it something other than 0 for it to work. Jack -Original Message- From: Gisbert Schneider [mailto:[EMAIL PROTECTED]] Sent: Monday, March 05, 2001 6:51 AM To: [EMAIL PROTECTED] Subject: Antwort: ANS1312E Server media mount not possible The client tries to write directly into a sequentiel storage pool and on the server the point MAX MOUNT POINTS for the client ist set to zero. __ Da E-Mails leicht unter fremdem Namen erstellt oder manipuliert werden koennen, muessen wir zu Ihrem und unserem Schutz die rechtliche Verbindlichkeit der vorstehenden Erklaerungen ausschliessen. Die fuer die Stadtsparkasse Koeln geltenden Regeln ueber die Verbindlichkeit von rechtsgeschaeftlichen Erklaerungen mit verpflichtendem Inhalt bleiben unberuehrt.
Re: Antwort: ANS1312E Server media mount not possible
Fra: Palmadesso Jack[SMTP:[EMAIL PROTECTED]] That sounds like that is exactly your problem. I was caught by this when we moved our first server to TSM. I believe 3.7 sets these to 0. You will have to make it something other than 0 for it to work. Having just upgraded to the most recent version of TSM, from ADSM 3.1.2.55 on AIX, I decided to look at all the nodes I have. I found that all the nodes I had previously defined before the upgrade were all set to 0. The new ones I created are set to 2. Better make a note in the document everyone got from me to update your nodes. Now that that's fixed I wonder what other things I'll find out about in the future. This is really annoying, I've been involved with delivering software to the government in the past and we had proceedures to follow. In those proceedures were proceedures from past deliveries to make sure the same functions, that worked in the past, still work, not just enhancements. I thought this would be SOP for all companies delivering software to its customers but I guess not. Geoff (I have enough to do without having to go back and fix things from software updates) Gill NT Systems Support Engineer SAIC Computer Systems Group E-Mail: [EMAIL PROTECTED] Phone: (858) 826-4062 Pager: (888) 997-9614
Re: ANS1312E Server media mount not possible
Check drive status and media access property. If drive status is unavailable, update drive following method. ex)update drive libraryname drivenumber online=yes If media access property is readonly, change it to readwrite.. I had the same problem yesterday,now I solved problem .. Good luck.. From South Korea Cddata co.ltd. - Original Message - From: "Bo Nielsen" [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, March 05, 2001 6:17 PM Subject: ANS1312E Server media mount not possible Hi Can somebody help me. A W2K Server TSM Client vers. 4.1.1 TSM server OS/390 4.1.1.0 StorageTek VSM tape library. When I run a backup, I receive the follow error message: ANS1312E Server media mount not possible Can any tell me what the problem is. Regards, Bo Nielsen FDB dataPhone: +45 4386 4671 Roskildevej 65 Fax: +45 4386 4990 DK-2620 AlbertslundE-mail: [EMAIL PROTECTED] Denmark
ANS1312E Server media mount not possible
Hi: Yet another peculiar situation that has popped up since the upgrade to TSM 3.7.2 on the server: Backgound: - the problem only occurs on this node in an SP environment - the node is the control workstation - I can ping the backup (TSM) server from the node with the failure - at the time of the incremental backup - dsmc i - I have checked the drives and mounts and they are online and not in use. - what I get is: [rscws] /home/root/tsmfiles # dsmc Tivoli Storage Manager Command Line Backup Client Interface - Version 3, Release 7, Level 2.0 (C) Copyright IBM Corporation, 1990, 2000, All Rights Reserved. tsm i Node Name: RSCWS Session established with server BACKUP: AIX-RS/6000 Server Version 3, Release 7, Level 2.0 Server date/time: 10/11/00 09:37:28 Last access: 10/11/00 09:24:15 Incremental backup of volume '/' Incremental backup of volume '/usr' Incremental backup of volume '/var' Incremental backup of volume '/home' Incremental backup of volume '/xrsa' Incremental backup of volume '/spdata' Incremental backup of volume '/usr/lpp/sysback/images/all' Incremental backup of volume '/usr/sys/inst.images' ANS1898I * Processed 1,500 files * Normal File--37,888 /TT_DB/property_table.ind [Sent] Normal File--18,432 /TT_DB/property_table.rec [Sent] Normal File--11,264 /TT_DB/property_table.var [Sent] Special File--0 /dev/error more files here, then Normal File--61,440 /etc/objrepos/product.vc [Sent] Normal File-- 128 /etc/security/failedlogin.1 [Sent] Normal File--80 /etc/security/adsm/BACKUP [Sent] Total number of objects inspected:2,356 Total number of objects backed up:0 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: 790.12 KB Data transfer time:1.70 sec Network data transfer rate: 462.54 KB/sec Aggregate data transfer rate: 97.91 KB/sec Objects compressed by:0% Elapsed processing time: 00:00:08 ANS1312E Server media mount not possible Larry Clark NYS Thruway Authority
Re: ANS1312E Server media mount not possible
Hi Richard: - yes, this particular node goes directly to tape, colocated. Nothing looks out of wack. Just to be sure I'm doing a move data on the volume now Volume 000224 in use by node RSCWS. SHOW VOLUMEUSAGE completed. tsm: BACKUPq vol 000224 f=d Volume Name: 000224 Storage Pool Name: AIX3590BACK Device Class Name: 3494ATAPE Estimated Capacity (MB): 12,666.7 Pct Util: 61.2 Volume Status: Filling Access: Read/Write Pct. Reclaimable Space: 41.8 Scratch Volume?: Yes In Error State?: No Number of Writable Sides: 1 Number of Times Mounted: 881 Write Pass Number: 1 Approx. Date Last Written: 10/08/00 06:17:06 Approx. Date Last Read: 10/10/00 17:35:22 Date Became Pending: Number of Write Errors: 0 Number of Read Errors: 0 Volume Location: Last Update by (administrator): Last Update Date/Time: 10/03/99 19:30:37 dsmerror entry: 10/11/00 13:58:52 cuPing: Out of sequence verb: verb: 61 10/11/00 13:58:52 sessOpen: Session state transition error, sessState: sSigned On. 10/11/00 13:58:52 sessOpen: Transitioning: sSignedOn state === sTRANSERR stat e 10/11/00 13:58:52 ANS1312E Server media mount not possible [EMAIL PROTECTED] 10/11/00 01:46PM 10/11/00 12:50:04 ANR0406I Session 7978 started for node RSCWS (AIX) = (Tcp/Ip 129.10.199.10(40421)). 10/11/00 12:50:09 ANR0406I Session 7979 started for node RSCWS (AIX) = (Tcp/Ip 129.10.199.10(40423)). 10/11/00 12:50:10 ANR0403I Session 7979 ended for node RSCWS (AIX). 10/11/00 12:50:11 ANR0480W Session 7978 for node RSCWS (AIX) terminated = - connection with client severed. [EMAIL PROTECTED] 10/11/00 11:33AM ANS1312E Server media mount not possible Larry - That's very interesting...no indication of even trying to mount a volume. Apparently, the server immediately knew that it could not satisfy the request: there was no timeout as indicated in the ANS1312E message description, and MOUNTWait could not be the issue since its unit of measurement is minutes, and the rejection here was in seconds. You didn't say, but I'll assume that you are set up to back up directly to tape. I'll also assume the common collocation choice of "by node". In that case the server would want to append the new data to the end of the tape that it was last filling for that node. Perhaps that volume is in a peculiar state - not bad enough to cause the server to go use a new scratch or, if no scratches left, the end of any other tape. See if you can determine what that tape was, from the prior successful backup for that node reflected in the Activity Log or queries, and then do a Query Volume F=D to see what it's state is; and also check that it is still in the library. If you are backing up to an intermediate disk storage pool, check its status and capacity. Beyond that, see if there is any dsmerror log with further indications. Richard Sims, BU
Re: ANS1312E Server media mount not possible
Hi Richard and list: TSM support cracked this one: The parameter for node RSCWS had its maxmountpoint ( new client parm as of 3.7) set to 0. Do not know how/why, since all other nodes were set to unlimited. That generated the media error. [EMAIL PROTECTED] 10/11/00 01:46PM 10/11/00 12:50:04 ANR0406I Session 7978 started for node RSCWS (AIX) = (Tcp/Ip 129.10.199.10(40421)). 10/11/00 12:50:09 ANR0406I Session 7979 started for node RSCWS (AIX) = (Tcp/Ip 129.10.199.10(40423)). 10/11/00 12:50:10 ANR0403I Session 7979 ended for node RSCWS (AIX). 10/11/00 12:50:11 ANR0480W Session 7978 for node RSCWS (AIX) terminated = - connection with client severed. [EMAIL PROTECTED] 10/11/00 11:33AM ANS1312E Server media mount not possible Larry - That's very interesting...no indication of even trying to mount a volume. Apparently, the server immediately knew that it could not satisfy the request: there was no timeout as indicated in the ANS1312E message description, and MOUNTWait could not be the issue since its unit of measurement is minutes, and the rejection here was in seconds. You didn't say, but I'll assume that you are set up to back up directly to tape. I'll also assume the common collocation choice of "by node". In that case the server would want to append the new data to the end of the tape that it was last filling for that node. Perhaps that volume is in a peculiar state - not bad enough to cause the server to go use a new scratch or, if no scratches left, the end of any other tape. See if you can determine what that tape was, from the prior successful backup for that node reflected in the Activity Log or queries, and then do a Query Volume F=D to see what it's state is; and also check that it is still in the library. If you are backing up to an intermediate disk storage pool, check its status and capacity. Beyond that, see if there is any dsmerror log with further indications. Richard Sims, BU
Re: ANS1312E Server media mount not possible
Larry, check the client on the server and make sure that you do not have mountpoints set to 0 Robert Burton Open System Storage Analyst Royal Bank of Canada 315 Front St West Toronto, On, M5V 3A4 416-348-3849 email: [EMAIL PROTECTED] -Original Message- From: Lawrence Clark [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 11, 2000 11:09 AM To: [EMAIL PROTECTED] Subject: ANS1312E Server media mount not possible Hi: Yet another peculiar situation that has popped up since the upgrade to TSM 3.7.2 on the server: Backgound: - the problem only occurs on this node in an SP environment - the node is the control workstation - I can ping the backup (TSM) server from the node with the failure - at the time of the incremental backup - dsmc i - I have checked the drives and mounts and they are online and not in use. - what I get is: [rscws] /home/root/tsmfiles # dsmc Tivoli Storage Manager Command Line Backup Client Interface - Version 3, Release 7, Level 2.0 (C) Copyright IBM Corporation, 1990, 2000, All Rights Reserved. tsm i Node Name: RSCWS Session established with server BACKUP: AIX-RS/6000 Server Version 3, Release 7, Level 2.0 Server date/time: 10/11/00 09:37:28 Last access: 10/11/00 09:24:15 Incremental backup of volume '/' Incremental backup of volume '/usr' Incremental backup of volume '/var' Incremental backup of volume '/home' Incremental backup of volume '/xrsa' Incremental backup of volume '/spdata' Incremental backup of volume '/usr/lpp/sysback/images/all' Incremental backup of volume '/usr/sys/inst.images' ANS1898I * Processed 1,500 files * Normal File--37,888 /TT_DB/property_table.ind [Sent] Normal File--18,432 /TT_DB/property_table.rec [Sent] Normal File--11,264 /TT_DB/property_table.var [Sent] Special File--0 /dev/error more files here, then Normal File--61,440 /etc/objrepos/product.vc [Sent] Normal File-- 128 /etc/security/failedlogin.1 [Sent] Normal File--80 /etc/security/adsm/BACKUP [Sent] Total number of objects inspected:2,356 Total number of objects backed up:0 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: 790.12 KB Data transfer time:1.70 sec Network data transfer rate: 462.54 KB/sec Aggregate data transfer rate: 97.91 KB/sec Objects compressed by:0% Elapsed processing time: 00:00:08 ANS1312E Server media mount not possible Larry Clark NYS Thruway Authority
Re: ANS1312E Server media mount not possible
If you are on TSM 3.7/4.1 and have migrated from ADSM 3.1, please make sure that the mount point limit for the node is 0 if you are directing data to tape (check your copygroups). In upgrading the data base, the default mount limit for existing nodes is zero, for newly-defined nodes it is two. You can change the limit using upd node * maxnummp=2 or whatever number of drives you'd like the client to use. Joerg Pohlmann Richard Sims [EMAIL PROTECTED] on 2000-10-11 10:46:23 AM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Re: ANS1312E Server media mount not possible 10/11/00 12:50:04 ANR0406I Session 7978 started for node RSCWS (AIX) = (Tcp/Ip 129.10.199.10(40421)). 10/11/00 12:50:09 ANR0406I Session 7979 started for node RSCWS (AIX) = (Tcp/Ip 129.10.199.10(40423)). 10/11/00 12:50:10 ANR0403I Session 7979 ended for node RSCWS (AIX). 10/11/00 12:50:11 ANR0480W Session 7978 for node RSCWS (AIX) terminated = - connection with client severed. [EMAIL PROTECTED] 10/11/00 11:33AM ANS1312E Server media mount not possible Larry - That's very interesting...no indication of even trying to mount a volume. Apparently, the server immediately knew that it could not satisfy the request: there was no timeout as indicated in the ANS1312E message description, and MOUNTWait could not be the issue since its unit of measurement is minutes, and the rejection here was in seconds. You didn't say, but I'll assume that you are set up to back up directly to tape. I'll also assume the common collocation choice of "by node". In that case the server would want to append the new data to the end of the tape that it was last filling for that node. Perhaps that volume is in a peculiar state - not bad enough to cause the server to go use a new scratch or, if no scratches left, the end of any other tape. See if you can determine what that tape was, from the prior successful backup for that node reflected in the Activity Log or queries, and then do a Query Volume F=D to see what it's state is; and also check that it is still in the library. If you are backing up to an intermediate disk storage pool, check its status and capacity. Beyond that, see if there is any dsmerror log with further indications. Richard Sims, BU
Re: ANS1312E Server media mount not possible
Hi Richard and list: TSM support cracked this one: The parameter for node RSCWS had its = maxmountpoint ( new client parm as of 3.7) set to 0. Do not know how/why, = since all other nodes were set to unlimited. Larry - Thanks for the final resolution. I'll make note of that one. It goes to show how little attention the Messages manual receives from Tivoli, that so much customer hassle and Tivoli support time has to go into figuring such things out, all preventable had the development process resulted in the effects of new operands being properly documented. Sigh. Richard
Re: ANS1312E Server media mount not possible
Hi Bob: That was the reason..Don't know how it got changed and never would that thought to look at those client options since they are new. [EMAIL PROTECTED] 10/11/00 11:27AM Larry, check the client on the server and make sure that you do not have mountpoints set to 0 Robert Burton Open System Storage Analyst Royal Bank of Canada 315 Front St West Toronto, On, M5V 3A4 416-348-3849 email: [EMAIL PROTECTED] -Original Message- From: Lawrence Clark [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 11, 2000 11:09 AM To: [EMAIL PROTECTED] Subject: ANS1312E Server media mount not possible Hi: Yet another peculiar situation that has popped up since the upgrade to TSM 3.7.2 on the server: Backgound: - the problem only occurs on this node in an SP environment - the node is the control workstation - I can ping the backup (TSM) server from the node with the failure - at the time of the incremental backup - dsmc i - I have checked the drives and mounts and they are online and not in use. - what I get is: [rscws] /home/root/tsmfiles # dsmc Tivoli Storage Manager Command Line Backup Client Interface - Version 3, Release 7, Level 2.0 (C) Copyright IBM Corporation, 1990, 2000, All Rights Reserved. tsm i Node Name: RSCWS Session established with server BACKUP: AIX-RS/6000 Server Version 3, Release 7, Level 2.0 Server date/time: 10/11/00 09:37:28 Last access: 10/11/00 09:24:15 Incremental backup of volume '/' Incremental backup of volume '/usr' Incremental backup of volume '/var' Incremental backup of volume '/home' Incremental backup of volume '/xrsa' Incremental backup of volume '/spdata' Incremental backup of volume '/usr/lpp/sysback/images/all' Incremental backup of volume '/usr/sys/inst.images' ANS1898I * Processed 1,500 files * Normal File--37,888 /TT_DB/property_table.ind [Sent] Normal File--18,432 /TT_DB/property_table.rec [Sent] Normal File--11,264 /TT_DB/property_table.var [Sent] Special File--0 /dev/error more files here, then Normal File--61,440 /etc/objrepos/product.vc [Sent] Normal File-- 128 /etc/security/failedlogin.1 [Sent] Normal File--80 /etc/security/adsm/BACKUP [Sent] Total number of objects inspected:2,356 Total number of objects backed up:0 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: 790.12 KB Data transfer time:1.70 sec Network data transfer rate: 462.54 KB/sec Aggregate data transfer rate: 97.91 KB/sec Objects compressed by:0% Elapsed processing time: 00:00:08 ANS1312E Server media mount not possible Larry Clark NYS Thruway Authority
