Re: Idle system fails with Media mount not possible
Query the node with F=d and change Number of Mount points from 0 to at least number of drives you have in library. What happened is stgpool probally filled up and the backup tried to continue on tape, but with Number of Mount points set to 0 said no and it failed. Thanks, Robert Rippy From: Conko, Steven [EMAIL PROTECTED] on 12/17/2002 04:19 PM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Idle system fails with Media mount not possible strange one... and ive looked at everything i can think of. In client dsmerror.log: 12/17/02 15:01:54 ANS1228E Sending of object '/tibco/logs/hawk/log/Hawk4.log' failed 12/17/02 15:01:54 ANS1312E Server media mount not possible 12/17/02 15:01:57 ANS1312E Server media mount not possible In activity log: ANR0535W Transaction failed for session 1356 for node SY00113 (AIX) - insufficient mount points available to satisfy the request. There is NOTHING else running on this TSM server. All 6 drives are online. The backup is going to a 18GB diskpool that is 8% full, there are plenty of scratch tapes, i set max mount points to 2. keep mount point=yes. it starts backing up the system then just fails... always at the same point. the file its trying to back up does not exceed the max size. all drives are empty, online. diskpool is online. i see the sessions start and then just after a minute or 2 just abort. any ideas?
Re: Idle system fails with Media mount not possible
the client was already set to 2 mount points. the storage pool does not fill up. any other suggestions? -Original Message- From: Robert L. Rippy [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 18, 2002 7:47 AM To: [EMAIL PROTECTED] Subject: Re: Idle system fails with Media mount not possible Query the node with F=d and change Number of Mount points from 0 to at least number of drives you have in library. What happened is stgpool probally filled up and the backup tried to continue on tape, but with Number of Mount points set to 0 said no and it failed. Thanks, Robert Rippy From: Conko, Steven [EMAIL PROTECTED] on 12/17/2002 04:19 PM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Idle system fails with Media mount not possible strange one... and ive looked at everything i can think of. In client dsmerror.log: 12/17/02 15:01:54 ANS1228E Sending of object '/tibco/logs/hawk/log/Hawk4.log' failed 12/17/02 15:01:54 ANS1312E Server media mount not possible 12/17/02 15:01:57 ANS1312E Server media mount not possible In activity log: ANR0535W Transaction failed for session 1356 for node SY00113 (AIX) - insufficient mount points available to satisfy the request. There is NOTHING else running on this TSM server. All 6 drives are online. The backup is going to a 18GB diskpool that is 8% full, there are plenty of scratch tapes, i set max mount points to 2. keep mount point=yes. it starts backing up the system then just fails... always at the same point. the file its trying to back up does not exceed the max size. all drives are empty, online. diskpool is online. i see the sessions start and then just after a minute or 2 just abort. any ideas?
Re: Idle system fails with Media mount not possible
yes, its at ML 10. -Original Message- From: David Longo [mailto:[EMAIL PROTECTED]] Sent: Tuesday, December 17, 2002 7:12 PM To: [EMAIL PROTECTED] Subject: Re: Idle system fails with Media mount not possible You didn't mention the Maint Level of AIX 4.3.3. If you have less than ML 10, then I would upgrade to that as one step. David Longo [EMAIL PROTECTED] 12/17/02 05:15PM How strange.. I just went through something similar. Running on AIX 4.3.3, TSM 4.2.1.7. What are you running? The short answer was to reboot the AIX operating system, and everything started working fine.. The long answer follows (well, not really an answer, just my situation, and what I tried to resolve it). Server AIX 4.3.3 TSM 4.2.1.7 Nodes W2K Storage Agent 4.2.1.7 BA Client 4.2.1.32 TDP for SQL 2.2 SQL 2000 and WinNT4 Storage Agent 4.2.1.7 BA Client 4.2.1.15 TDP for SQL 1.1 SQL 6.5 Relevant TSM server storage as follows... diskpool_sql_meta (no next storage pool intended only for the */.../meta/.../* info) diskpool_sql (next storage pool is ltotape_sql, intended for smaller databases) ltotape_sql (collocation of FILESPACE since /stripes=2 backups are kept here) The SQL 2000 server had been having issues over the last few months where backups to ltotape_sql with /stripes=2 of a 265GB database would fail with a server media mount no possible error, but /stripes=1 differential backups would back up fine. Oddly, increasing the Maximum Mount Points for the node by one would allow the /stripes=2 backup to succeed, but the next time a /stripes=2 backup would run, it would fail (until I increased the MMP again). I had 5 drives, all free and unused and 7 MMP for the node when... this new wrinkle occurred. The SQL 6.5 server started having problems backing up certain databases: the smaller system databases; master, model, msdb, pubs, tempdb, with and error message of server media mount not possible. All the DBs on this server have a destination of ltotape_sql. Like you, plenty of room in the storage pool, plenty of scratch. Called support Got level one.. told him a few things.. he didn't even want to try it.. and immediately escalated to level two. While I waited for a call back from level two, the following occurred. I noticed that there are some databases in diskpool_sql that haven't migrated to ltotape_sql. Kicking off a migration gets a similar error message media mount not possible, which, oddly, is the same message I got from the storage agent when backing up tapes to ltotape_sql. I carefully detailed what it took to migrate those 3 files from diskpool_sql to ltotape_sql, which is a whole other chapter by itself, involving changing maxscratch up and down, moving data, and a few other hoops, and I was unable to get some tapes to move with a move data command (tapes that had only one master or msdb or tempdb type database on them). Level two calls back. I go through the entire situation, including the fact of the Max Mount Point having to change every time I did I /stirpes=2 backup (I wasn't sure if that was a related issue or not). She is baffled, and wants to think it over and search databases etc to see what she can come up with. Within 30 mins, she calls back and asks me to reboot the TSM server's OS (uptime reported a whopping 82 days), just to see what would happen. I do. Migrations go. Backups /stripes=1 go. Backups /stripes=2 go (even with MMP set back to 4 for that node, instead of 7 ( with only 5 tape drives remember). This was Friday. Sunday night, the TSM server did something odd (haven't reported this to TSM support yet). It just stopped. It showed link status on the fiber cards, and network cards, but you couldn't ping it, the server console wouldn't wake up, nothing. Even the display on the front was dark, but the power light was on steady like it was operational, not flashing like it would be if you did a proper shutdown. I reset it Monday morning when I found it that way, and then had to do a clean shutdown and power on to get the fiber cards to see the library correctly. Very weird. So, I am taking Monday morning (yesterday) as the start time to see how long it takes until I have to increase my MMP on the one node just to get a /stripes=2 backup. The saga continues... Conko, Steven To: [EMAIL PROTECTED] [EMAIL PROTECTED] cc: M Fax to: Sent by: Subject: Idle system fails with Media mount not possible ADSM: Dist Stor Manager [EMAIL PROTECTED] IST.EDU 12/17/2002 03:19 PM Please respond to ADSM: Dist Stor Manager strange one... and ive looked at everything i can think of. In client dsmerror.log: 12/17/02 15:01:54 ANS1228E
Re: Idle system fails with Media mount not possible
I've also seen this where Unix hasn't released the drives from the OS. TSM seems them as available but not Unix. I have had to delete the drive and redefine so that they can be used. It was a bug in a certain code of TSM but I can't remember which one or even if that is truly your problem. Thanks, Rob. From: Conko, Steven [EMAIL PROTECTED] on 12/18/2002 09:03 AM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Re: Idle system fails with Media mount not possible the client was already set to 2 mount points. the storage pool does not fill up. any other suggestions? -Original Message- From: Robert L. Rippy [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 18, 2002 7:47 AM To: [EMAIL PROTECTED] Subject: Re: Idle system fails with Media mount not possible Query the node with F=d and change Number of Mount points from 0 to at least number of drives you have in library. What happened is stgpool probally filled up and the backup tried to continue on tape, but with Number of Mount points set to 0 said no and it failed. Thanks, Robert Rippy From: Conko, Steven [EMAIL PROTECTED] on 12/17/2002 04:19 PM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Idle system fails with Media mount not possible strange one... and ive looked at everything i can think of. In client dsmerror.log: 12/17/02 15:01:54 ANS1228E Sending of object '/tibco/logs/hawk/log/Hawk4.log' failed 12/17/02 15:01:54 ANS1312E Server media mount not possible 12/17/02 15:01:57 ANS1312E Server media mount not possible In activity log: ANR0535W Transaction failed for session 1356 for node SY00113 (AIX) - insufficient mount points available to satisfy the request. There is NOTHING else running on this TSM server. All 6 drives are online. The backup is going to a 18GB diskpool that is 8% full, there are plenty of scratch tapes, i set max mount points to 2. keep mount point=yes. it starts backing up the system then just fails... always at the same point. the file its trying to back up does not exceed the max size. all drives are empty, online. diskpool is online. i see the sessions start and then just after a minute or 2 just abort. any ideas?
Re: Idle system fails with Media mount not possible
The strange thing as that other clients are backing up fine... these are three very similar, nearly identical clients, all configured exactly the same. the others backup fine, and this incremental keeps failing in the same spot with the media mount not possible. -Original Message- From: Robert L. Rippy [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 18, 2002 9:12 AM To: [EMAIL PROTECTED] Subject: Re: Idle system fails with Media mount not possible I've also seen this where Unix hasn't released the drives from the OS. TSM seems them as available but not Unix. I have had to delete the drive and redefine so that they can be used. It was a bug in a certain code of TSM but I can't remember which one or even if that is truly your problem. Thanks, Rob. From: Conko, Steven [EMAIL PROTECTED] on 12/18/2002 09:03 AM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Re: Idle system fails with Media mount not possible the client was already set to 2 mount points. the storage pool does not fill up. any other suggestions? -Original Message- From: Robert L. Rippy [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 18, 2002 7:47 AM To: [EMAIL PROTECTED] Subject: Re: Idle system fails with Media mount not possible Query the node with F=d and change Number of Mount points from 0 to at least number of drives you have in library. What happened is stgpool probally filled up and the backup tried to continue on tape, but with Number of Mount points set to 0 said no and it failed. Thanks, Robert Rippy From: Conko, Steven [EMAIL PROTECTED] on 12/17/2002 04:19 PM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Idle system fails with Media mount not possible strange one... and ive looked at everything i can think of. In client dsmerror.log: 12/17/02 15:01:54 ANS1228E Sending of object '/tibco/logs/hawk/log/Hawk4.log' failed 12/17/02 15:01:54 ANS1312E Server media mount not possible 12/17/02 15:01:57 ANS1312E Server media mount not possible In activity log: ANR0535W Transaction failed for session 1356 for node SY00113 (AIX) - insufficient mount points available to satisfy the request. There is NOTHING else running on this TSM server. All 6 drives are online. The backup is going to a 18GB diskpool that is 8% full, there are plenty of scratch tapes, i set max mount points to 2. keep mount point=yes. it starts backing up the system then just fails... always at the same point. the file its trying to back up does not exceed the max size. all drives are empty, online. diskpool is online. i see the sessions start and then just after a minute or 2 just abort. any ideas?
Re: Idle system fails with Media mount not possible
Does it fail on the same file or directory every time, and does that file or directory attract a management class which is pointing to a different storage pool Conko, Steven [EMAIL PROTECTED] on 12/18/2002 02:29:12 PM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc:(bcc: John Naylor/HAV/SSE) Subject: Re: Idle system fails with Media mount not possible The strange thing as that other clients are backing up fine... these are three very similar, nearly identical clients, all configured exactly the same. the others backup fine, and this incremental keeps failing in the same spot with the media mount not possible. -Original Message- From: Robert L. Rippy [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 18, 2002 9:12 AM To: [EMAIL PROTECTED] Subject: Re: Idle system fails with Media mount not possible I've also seen this where Unix hasn't released the drives from the OS. TSM seems them as available but not Unix. I have had to delete the drive and redefine so that they can be used. It was a bug in a certain code of TSM but I can't remember which one or even if that is truly your problem. Thanks, Rob. From: Conko, Steven [EMAIL PROTECTED] on 12/18/2002 09:03 AM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Re: Idle system fails with Media mount not possible the client was already set to 2 mount points. the storage pool does not fill up. any other suggestions? -Original Message- From: Robert L. Rippy [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 18, 2002 7:47 AM To: [EMAIL PROTECTED] Subject: Re: Idle system fails with Media mount not possible Query the node with F=d and change Number of Mount points from 0 to at least number of drives you have in library. What happened is stgpool probally filled up and the backup tried to continue on tape, but with Number of Mount points set to 0 said no and it failed. Thanks, Robert Rippy From: Conko, Steven [EMAIL PROTECTED] on 12/17/2002 04:19 PM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Idle system fails with Media mount not possible strange one... and ive looked at everything i can think of. In client dsmerror.log: 12/17/02 15:01:54 ANS1228E Sending of object '/tibco/logs/hawk/log/Hawk4.log' failed 12/17/02 15:01:54 ANS1312E Server media mount not possible 12/17/02 15:01:57 ANS1312E Server media mount not possible In activity log: ANR0535W Transaction failed for session 1356 for node SY00113 (AIX) - insufficient mount points available to satisfy the request. There is NOTHING else running on this TSM server. All 6 drives are online. The backup is going to a 18GB diskpool that is 8% full, there are plenty of scratch tapes, i set max mount points to 2. keep mount point=yes. it starts backing up the system then just fails... always at the same point. the file its trying to back up does not exceed the max size. all drives are empty, online. diskpool is online. i see the sessions start and then just after a minute or 2 just abort. any ideas? ** The information in this E-Mail is confidential and may be legally privileged. It may not represent the views of Scottish and Southern Energy plc. It is intended solely for the addressees. Access to this E-Mail by anyone else is unauthorised. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. Any unauthorised recipient should advise the sender immediately of the error in transmission. Scottish Hydro-Electric, Southern Electric, SWALEC and S+S are trading names of the Scottish and Southern Energy Group. **
Re: Idle system fails with Media mount not possible
yes, it is always failing on the same file(s) in the same directory. how would it attract a different management class? this is using the default management class and we dont have any includes or excludes set up. -Original Message- From: John Naylor [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 18, 2002 9:35 AM To: [EMAIL PROTECTED] Subject: Re: Idle system fails with Media mount not possible Does it fail on the same file or directory every time, and does that file or directory attract a management class which is pointing to a different storage pool Conko, Steven [EMAIL PROTECTED] on 12/18/2002 02:29:12 PM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc:(bcc: John Naylor/HAV/SSE) Subject: Re: Idle system fails with Media mount not possible The strange thing as that other clients are backing up fine... these are three very similar, nearly identical clients, all configured exactly the same. the others backup fine, and this incremental keeps failing in the same spot with the media mount not possible. -Original Message- From: Robert L. Rippy [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 18, 2002 9:12 AM To: [EMAIL PROTECTED] Subject: Re: Idle system fails with Media mount not possible I've also seen this where Unix hasn't released the drives from the OS. TSM seems them as available but not Unix. I have had to delete the drive and redefine so that they can be used. It was a bug in a certain code of TSM but I can't remember which one or even if that is truly your problem. Thanks, Rob. From: Conko, Steven [EMAIL PROTECTED] on 12/18/2002 09:03 AM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Re: Idle system fails with Media mount not possible the client was already set to 2 mount points. the storage pool does not fill up. any other suggestions? -Original Message- From: Robert L. Rippy [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 18, 2002 7:47 AM To: [EMAIL PROTECTED] Subject: Re: Idle system fails with Media mount not possible Query the node with F=d and change Number of Mount points from 0 to at least number of drives you have in library. What happened is stgpool probally filled up and the backup tried to continue on tape, but with Number of Mount points set to 0 said no and it failed. Thanks, Robert Rippy From: Conko, Steven [EMAIL PROTECTED] on 12/17/2002 04:19 PM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Idle system fails with Media mount not possible strange one... and ive looked at everything i can think of. In client dsmerror.log: 12/17/02 15:01:54 ANS1228E Sending of object '/tibco/logs/hawk/log/Hawk4.log' failed 12/17/02 15:01:54 ANS1312E Server media mount not possible 12/17/02 15:01:57 ANS1312E Server media mount not possible In activity log: ANR0535W Transaction failed for session 1356 for node SY00113 (AIX) - insufficient mount points available to satisfy the request. There is NOTHING else running on this TSM server. All 6 drives are online. The backup is going to a 18GB diskpool that is 8% full, there are plenty of scratch tapes, i set max mount points to 2. keep mount point=yes. it starts backing up the system then just fails... always at the same point. the file its trying to back up does not exceed the max size. all drives are empty, online. diskpool is online. i see the sessions start and then just after a minute or 2 just abort. any ideas? ** The information in this E-Mail is confidential and may be legally privileged. It may not represent the views of Scottish and Southern Energy plc. It is intended solely for the addressees. Access to this E-Mail by anyone else is unauthorised. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. Any unauthorised recipient should advise the sender immediately of the error in transmission. Scottish Hydro-Electric, Southern Electric, SWALEC and S+S are trading names of the Scottish and Southern Energy Group. **
Re: Idle system fails with Media mount not possible
On the client, do a 'dsmc show opt' and a 'dsmc q inclexcl' to check for stray management-class bindings that are different from your other working clients. If all your clients don't belong to a common domain, then check the server for missing copygroup definitions, incorrect target pool, target pool with no associated volume, and/or policysets that haven't been 'activate'd. Conko, Steven [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 18-Dec-2002 09:29 Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] To: ADSM-L cc: Subject:Re: Idle system fails with Media mount not possible The strange thing as that other clients are backing up fine... these are three very similar, nearly identical clients, all configured exactly the same. the others backup fine, and this incremental keeps failing in the same spot with the media mount not possible. -Original Message- From: Robert L. Rippy [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 18, 2002 9:12 AM To: [EMAIL PROTECTED] Subject: Re: Idle system fails with Media mount not possible I've also seen this where Unix hasn't released the drives from the OS. TSM seems them as available but not Unix. I have had to delete the drive and redefine so that they can be used. It was a bug in a certain code of TSM but I can't remember which one or even if that is truly your problem. Thanks, Rob. From: Conko, Steven [EMAIL PROTECTED] on 12/18/2002 09:03 AM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Re: Idle system fails with Media mount not possible the client was already set to 2 mount points. the storage pool does not fill up. any other suggestions? -Original Message- From: Robert L. Rippy [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 18, 2002 7:47 AM To: [EMAIL PROTECTED] Subject: Re: Idle system fails with Media mount not possible Query the node with F=d and change Number of Mount points from 0 to at least number of drives you have in library. What happened is stgpool probally filled up and the backup tried to continue on tape, but with Number of Mount points set to 0 said no and it failed. Thanks, Robert Rippy From: Conko, Steven [EMAIL PROTECTED] on 12/17/2002 04:19 PM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Idle system fails with Media mount not possible strange one... and ive looked at everything i can think of. In client dsmerror.log: 12/17/02 15:01:54 ANS1228E Sending of object '/tibco/logs/hawk/log/Hawk4.log' failed 12/17/02 15:01:54 ANS1312E Server media mount not possible 12/17/02 15:01:57 ANS1312E Server media mount not possible In activity log: ANR0535W Transaction failed for session 1356 for node SY00113 (AIX) - insufficient mount points available to satisfy the request. There is NOTHING else running on this TSM server. All 6 drives are online. The backup is going to a 18GB diskpool that is 8% full, there are plenty of scratch tapes, i set max mount points to 2. keep mount point=yes. it starts backing up the system then just fails... always at the same point. the file its trying to back up does not exceed the max size. all drives are empty, online. diskpool is online. i see the sessions start and then just after a minute or 2 just abort. any ideas?
Re: Idle system fails with Media mount not possible
everything checks out so far. now what i have done is a specific backup of just the directory it was failing on... dsmc incr /tibco/logs/ -subdir=yes that ran fine and when i ran the system wide backup again it got further and failed on another subdirectory of /tibco. i then did a backup of THAT directory and it was successful. then the system wide backup got further but failed in ANOTHER /tibco directory. so right now im piecemealing it together. i cant understand why it keeps failing on these subdirectories. some /tibco/... dirs work. some dont. -Original Message- From: Kent Monthei [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 18, 2002 9:59 AM To: [EMAIL PROTECTED] Subject: Re: Idle system fails with Media mount not possible On the client, do a 'dsmc show opt' and a 'dsmc q inclexcl' to check for stray management-class bindings that are different from your other working clients. If all your clients don't belong to a common domain, then check the server for missing copygroup definitions, incorrect target pool, target pool with no associated volume, and/or policysets that haven't been 'activate'd. Conko, Steven [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 18-Dec-2002 09:29 Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] To: ADSM-L cc: Subject:Re: Idle system fails with Media mount not possible The strange thing as that other clients are backing up fine... these are three very similar, nearly identical clients, all configured exactly the same. the others backup fine, and this incremental keeps failing in the same spot with the media mount not possible. -Original Message- From: Robert L. Rippy [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 18, 2002 9:12 AM To: [EMAIL PROTECTED] Subject: Re: Idle system fails with Media mount not possible I've also seen this where Unix hasn't released the drives from the OS. TSM seems them as available but not Unix. I have had to delete the drive and redefine so that they can be used. It was a bug in a certain code of TSM but I can't remember which one or even if that is truly your problem. Thanks, Rob. From: Conko, Steven [EMAIL PROTECTED] on 12/18/2002 09:03 AM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Re: Idle system fails with Media mount not possible the client was already set to 2 mount points. the storage pool does not fill up. any other suggestions? -Original Message- From: Robert L. Rippy [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 18, 2002 7:47 AM To: [EMAIL PROTECTED] Subject: Re: Idle system fails with Media mount not possible Query the node with F=d and change Number of Mount points from 0 to at least number of drives you have in library. What happened is stgpool probally filled up and the backup tried to continue on tape, but with Number of Mount points set to 0 said no and it failed. Thanks, Robert Rippy From: Conko, Steven [EMAIL PROTECTED] on 12/17/2002 04:19 PM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Idle system fails with Media mount not possible strange one... and ive looked at everything i can think of. In client dsmerror.log: 12/17/02 15:01:54 ANS1228E Sending of object '/tibco/logs/hawk/log/Hawk4.log' failed 12/17/02 15:01:54 ANS1312E Server media mount not possible 12/17/02 15:01:57 ANS1312E Server media mount not possible In activity log: ANR0535W Transaction failed for session 1356 for node SY00113 (AIX) - insufficient mount points available to satisfy the request. There is NOTHING else running on this TSM server. All 6 drives are online. The backup is going to a 18GB diskpool that is 8% full, there are plenty of scratch tapes, i set max mount points to 2. keep mount point=yes. it starts backing up the system then just fails... always at the same point. the file its trying to back up does not exceed the max size. all drives are empty, online. diskpool is online. i see the sessions start and then just after a minute or 2 just abort. any ideas?
Re: Idle system fails with Media mount not possible
So are you saying that the management class that the directories are atracting is pointing them to the same disk storage pool which you said had plenty of space. ** The information in this E-Mail is confidential and may be legally privileged. It may not represent the views of Scottish and Southern Energy plc. It is intended solely for the addressees. Access to this E-Mail by anyone else is unauthorised. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. Any unauthorised recipient should advise the sender immediately of the error in transmission. Scottish Hydro-Electric, Southern Electric, SWALEC and S+S are trading names of the Scottish and Southern Energy Group. **
Re: Idle system fails with Media mount not possible
yes, everything is going to the disk storage pool that has pleny of space. these systems dont use multiple management classes. -Original Message- From: John Naylor [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 18, 2002 10:24 AM To: [EMAIL PROTECTED] Subject: Re: Idle system fails with Media mount not possible So are you saying that the management class that the directories are atracting is pointing them to the same disk storage pool which you said had plenty of space. ** The information in this E-Mail is confidential and may be legally privileged. It may not represent the views of Scottish and Southern Energy plc. It is intended solely for the addressees. Access to this E-Mail by anyone else is unauthorised. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. Any unauthorised recipient should advise the sender immediately of the error in transmission. Scottish Hydro-Electric, Southern Electric, SWALEC and S+S are trading names of the Scottish and Southern Energy Group. **
Re: Idle system fails with Media mount not possible
well, by using the piecemeal method of successfully individually backing up everything that failed i have finally been able to run a successfull system wide backup. strange. is it possible with a 1GB filesize limit on the diskpool that several files added up to more than 1 gb? would that cause a problem? -Original Message- From: Kent Monthei [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 18, 2002 9:59 AM To: [EMAIL PROTECTED] Subject: Re: Idle system fails with Media mount not possible On the client, do a 'dsmc show opt' and a 'dsmc q inclexcl' to check for stray management-class bindings that are different from your other working clients. If all your clients don't belong to a common domain, then check the server for missing copygroup definitions, incorrect target pool, target pool with no associated volume, and/or policysets that haven't been 'activate'd. Conko, Steven [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 18-Dec-2002 09:29 Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] To: ADSM-L cc: Subject:Re: Idle system fails with Media mount not possible The strange thing as that other clients are backing up fine... these are three very similar, nearly identical clients, all configured exactly the same. the others backup fine, and this incremental keeps failing in the same spot with the media mount not possible. -Original Message- From: Robert L. Rippy [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 18, 2002 9:12 AM To: [EMAIL PROTECTED] Subject: Re: Idle system fails with Media mount not possible I've also seen this where Unix hasn't released the drives from the OS. TSM seems them as available but not Unix. I have had to delete the drive and redefine so that they can be used. It was a bug in a certain code of TSM but I can't remember which one or even if that is truly your problem. Thanks, Rob. From: Conko, Steven [EMAIL PROTECTED] on 12/18/2002 09:03 AM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Re: Idle system fails with Media mount not possible the client was already set to 2 mount points. the storage pool does not fill up. any other suggestions? -Original Message- From: Robert L. Rippy [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 18, 2002 7:47 AM To: [EMAIL PROTECTED] Subject: Re: Idle system fails with Media mount not possible Query the node with F=d and change Number of Mount points from 0 to at least number of drives you have in library. What happened is stgpool probally filled up and the backup tried to continue on tape, but with Number of Mount points set to 0 said no and it failed. Thanks, Robert Rippy From: Conko, Steven [EMAIL PROTECTED] on 12/17/2002 04:19 PM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Idle system fails with Media mount not possible strange one... and ive looked at everything i can think of. In client dsmerror.log: 12/17/02 15:01:54 ANS1228E Sending of object '/tibco/logs/hawk/log/Hawk4.log' failed 12/17/02 15:01:54 ANS1312E Server media mount not possible 12/17/02 15:01:57 ANS1312E Server media mount not possible In activity log: ANR0535W Transaction failed for session 1356 for node SY00113 (AIX) - insufficient mount points available to satisfy the request. There is NOTHING else running on this TSM server. All 6 drives are online. The backup is going to a 18GB diskpool that is 8% full, there are plenty of scratch tapes, i set max mount points to 2. keep mount point=yes. it starts backing up the system then just fails... always at the same point. the file its trying to back up does not exceed the max size. all drives are empty, online. diskpool is online. i see the sessions start and then just after a minute or 2 just abort. any ideas?
Re: Idle system fails with Media mount not possible
On the TSM Server, what does 'query occupancy' report ? In what pools are your backups of this client vs others ultimately landing ? Conko, Steven [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 18-Dec-2002 10:37 Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] To: ADSM-L cc: Subject:Re: Idle system fails with Media mount not possible well, by using the piecemeal method of successfully individually backing up everything that failed i have finally been able to run a successfull system wide backup. strange. is it possible with a 1GB filesize limit on the diskpool that several files added up to more than 1 gb? would that cause a problem? -Original Message- From: Kent Monthei [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 18, 2002 9:59 AM To: [EMAIL PROTECTED] Subject: Re: Idle system fails with Media mount not possible On the client, do a 'dsmc show opt' and a 'dsmc q inclexcl' to check for stray management-class bindings that are different from your other working clients. If all your clients don't belong to a common domain, then check the server for missing copygroup definitions, incorrect target pool, target pool with no associated volume, and/or policysets that haven't been 'activate'd. Conko, Steven [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 18-Dec-2002 09:29 Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] To: ADSM-L cc: Subject:Re: Idle system fails with Media mount not possible The strange thing as that other clients are backing up fine... these are three very similar, nearly identical clients, all configured exactly the same. the others backup fine, and this incremental keeps failing in the same spot with the media mount not possible. -Original Message- From: Robert L. Rippy [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 18, 2002 9:12 AM To: [EMAIL PROTECTED] Subject: Re: Idle system fails with Media mount not possible I've also seen this where Unix hasn't released the drives from the OS. TSM seems them as available but not Unix. I have had to delete the drive and redefine so that they can be used. It was a bug in a certain code of TSM but I can't remember which one or even if that is truly your problem. Thanks, Rob. From: Conko, Steven [EMAIL PROTECTED] on 12/18/2002 09:03 AM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Re: Idle system fails with Media mount not possible the client was already set to 2 mount points. the storage pool does not fill up. any other suggestions? -Original Message- From: Robert L. Rippy [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 18, 2002 7:47 AM To: [EMAIL PROTECTED] Subject: Re: Idle system fails with Media mount not possible Query the node with F=d and change Number of Mount points from 0 to at least number of drives you have in library. What happened is stgpool probally filled up and the backup tried to continue on tape, but with Number of Mount points set to 0 said no and it failed. Thanks, Robert Rippy From: Conko, Steven [EMAIL PROTECTED] on 12/17/2002 04:19 PM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Idle system fails with Media mount not possible strange one... and ive looked at everything i can think of. In client dsmerror.log: 12/17/02 15:01:54 ANS1228E Sending of object '/tibco/logs/hawk/log/Hawk4.log' failed 12/17/02 15:01:54 ANS1312E Server media mount not possible 12/17/02 15:01:57 ANS1312E Server media mount not possible In activity log: ANR0535W Transaction failed for session 1356 for node SY00113 (AIX) - insufficient mount points available to satisfy the request. There is NOTHING else running on this TSM server. All 6 drives are online. The backup is going to a 18GB diskpool that is 8% full, there are plenty of scratch tapes, i set max mount points to 2. keep mount point=yes. it starts backing up the system then just fails... always at the same point. the file its trying to back up does not exceed the max size. all drives are empty, online. diskpool is online. i see the sessions start and then just after a minute or 2 just abort. any ideas?
Idle system fails with Media mount not possible
strange one... and ive looked at everything i can think of. In client dsmerror.log: 12/17/02 15:01:54 ANS1228E Sending of object '/tibco/logs/hawk/log/Hawk4.log' failed 12/17/02 15:01:54 ANS1312E Server media mount not possible 12/17/02 15:01:57 ANS1312E Server media mount not possible In activity log: ANR0535W Transaction failed for session 1356 for node SY00113 (AIX) - insufficient mount points available to satisfy the request. There is NOTHING else running on this TSM server. All 6 drives are online. The backup is going to a 18GB diskpool that is 8% full, there are plenty of scratch tapes, i set max mount points to 2. keep mount point=yes. it starts backing up the system then just fails... always at the same point. the file its trying to back up does not exceed the max size. all drives are empty, online. diskpool is online. i see the sessions start and then just after a minute or 2 just abort. any ideas?
Re: Idle system fails with Media mount not possible
How strange.. I just went through something similar. Running on AIX 4.3.3, TSM 4.2.1.7. What are you running? The short answer was to reboot the AIX operating system, and everything started working fine.. The long answer follows (well, not really an answer, just my situation, and what I tried to resolve it). Server AIX 4.3.3 TSM 4.2.1.7 Nodes W2K Storage Agent 4.2.1.7 BA Client 4.2.1.32 TDP for SQL 2.2 SQL 2000 and WinNT4 Storage Agent 4.2.1.7 BA Client 4.2.1.15 TDP for SQL 1.1 SQL 6.5 Relevant TSM server storage as follows... diskpool_sql_meta (no next storage pool intended only for the */.../meta/.../* info) diskpool_sql (next storage pool is ltotape_sql, intended for smaller databases) ltotape_sql (collocation of FILESPACE since /stripes=2 backups are kept here) The SQL 2000 server had been having issues over the last few months where backups to ltotape_sql with /stripes=2 of a 265GB database would fail with a server media mount no possible error, but /stripes=1 differential backups would back up fine. Oddly, increasing the Maximum Mount Points for the node by one would allow the /stripes=2 backup to succeed, but the next time a /stripes=2 backup would run, it would fail (until I increased the MMP again). I had 5 drives, all free and unused and 7 MMP for the node when... this new wrinkle occurred. The SQL 6.5 server started having problems backing up certain databases: the smaller system databases; master, model, msdb, pubs, tempdb, with and error message of server media mount not possible. All the DBs on this server have a destination of ltotape_sql. Like you, plenty of room in the storage pool, plenty of scratch. Called support Got level one.. told him a few things.. he didn't even want to try it.. and immediately escalated to level two. While I waited for a call back from level two, the following occurred. I noticed that there are some databases in diskpool_sql that haven't migrated to ltotape_sql. Kicking off a migration gets a similar error message media mount not possible, which, oddly, is the same message I got from the storage agent when backing up tapes to ltotape_sql. I carefully detailed what it took to migrate those 3 files from diskpool_sql to ltotape_sql, which is a whole other chapter by itself, involving changing maxscratch up and down, moving data, and a few other hoops, and I was unable to get some tapes to move with a move data command (tapes that had only one master or msdb or tempdb type database on them). Level two calls back. I go through the entire situation, including the fact of the Max Mount Point having to change every time I did I /stirpes=2 backup (I wasn't sure if that was a related issue or not). She is baffled, and wants to think it over and search databases etc to see what she can come up with. Within 30 mins, she calls back and asks me to reboot the TSM server's OS (uptime reported a whopping 82 days), just to see what would happen. I do. Migrations go. Backups /stripes=1 go. Backups /stripes=2 go (even with MMP set back to 4 for that node, instead of 7 ( with only 5 tape drives remember). This was Friday. Sunday night, the TSM server did something odd (haven't reported this to TSM support yet). It just stopped. It showed link status on the fiber cards, and network cards, but you couldn't ping it, the server console wouldn't wake up, nothing. Even the display on the front was dark, but the power light was on steady like it was operational, not flashing like it would be if you did a proper shutdown. I reset it Monday morning when I found it that way, and then had to do a clean shutdown and power on to get the fiber cards to see the library correctly. Very weird. So, I am taking Monday morning (yesterday) as the start time to see how long it takes until I have to increase my MMP on the one node just to get a /stripes=2 backup. The saga continues... Conko, Steven To: [EMAIL PROTECTED] [EMAIL PROTECTED] cc: M Fax to: Sent by: Subject: Idle system fails with Media mount not possible ADSM: Dist Stor Manager [EMAIL PROTECTED] IST.EDU 12/17/2002 03:19 PM Please respond to ADSM: Dist Stor Manager strange one... and ive looked at everything i can think of. In client dsmerror.log: 12/17/02 15:01:54 ANS1228E Sending of object '/tibco/logs/hawk/log/Hawk4.log' failed 12/17/02 15:01:54 ANS1312E Server media mount not possible 12/17/02 15:01:57 ANS1312E Server media mount not possible In activity log: ANR0535W Transaction failed for session 1356 for node SY00113 (AIX) - insufficient mount points available to satisfy the request. There is NOTHING else running on this TSM server. All 6
Re: Idle system fails with Media mount not possible
ANR0535W Transaction failed for session 1356 for node SY00113 (AIX) - insufficient mount points available to satisfy the request. There is NOTHING else running on this TSM server. All 6 drives are online. Nothing running can itself be an indication of things suspicious... It may be that TSM tried to acquire one drive after another, but none of them could be had - which could well be a problem with the library or network access to it. You haven't told us your hardware type or what diagnostic steps you have taken. An obvious first step, in your AIX system, is 'errpt -a | less' and look for odd stuff. Another obvious step is to perform a manual query or action against the library, as with the 'mtlib' command or equivalent for your library type, to get status and, if that works, to try mounting a tape. Also, try pinging the library from the TSM server system. Do 'SHOW LIBRARY' in TSM and check what it thinks the status of the library and drives are. Use 'lsdev' and the like to check the status of the drives. Stuff like that, to uncover what's awry. Richard Sims, BU
Re: Idle system fails with Media mount not possible
You didn't mention the Maint Level of AIX 4.3.3. If you have less than ML 10, then I would upgrade to that as one step. David Longo [EMAIL PROTECTED] 12/17/02 05:15PM How strange.. I just went through something similar. Running on AIX 4.3.3, TSM 4.2.1.7. What are you running? The short answer was to reboot the AIX operating system, and everything started working fine.. The long answer follows (well, not really an answer, just my situation, and what I tried to resolve it). Server AIX 4.3.3 TSM 4.2.1.7 Nodes W2K Storage Agent 4.2.1.7 BA Client 4.2.1.32 TDP for SQL 2.2 SQL 2000 and WinNT4 Storage Agent 4.2.1.7 BA Client 4.2.1.15 TDP for SQL 1.1 SQL 6.5 Relevant TSM server storage as follows... diskpool_sql_meta (no next storage pool intended only for the */.../meta/.../* info) diskpool_sql (next storage pool is ltotape_sql, intended for smaller databases) ltotape_sql (collocation of FILESPACE since /stripes=2 backups are kept here) The SQL 2000 server had been having issues over the last few months where backups to ltotape_sql with /stripes=2 of a 265GB database would fail with a server media mount no possible error, but /stripes=1 differential backups would back up fine. Oddly, increasing the Maximum Mount Points for the node by one would allow the /stripes=2 backup to succeed, but the next time a /stripes=2 backup would run, it would fail (until I increased the MMP again). I had 5 drives, all free and unused and 7 MMP for the node when... this new wrinkle occurred. The SQL 6.5 server started having problems backing up certain databases: the smaller system databases; master, model, msdb, pubs, tempdb, with and error message of server media mount not possible. All the DBs on this server have a destination of ltotape_sql. Like you, plenty of room in the storage pool, plenty of scratch. Called support Got level one.. told him a few things.. he didn't even want to try it.. and immediately escalated to level two. While I waited for a call back from level two, the following occurred. I noticed that there are some databases in diskpool_sql that haven't migrated to ltotape_sql. Kicking off a migration gets a similar error message media mount not possible, which, oddly, is the same message I got from the storage agent when backing up tapes to ltotape_sql. I carefully detailed what it took to migrate those 3 files from diskpool_sql to ltotape_sql, which is a whole other chapter by itself, involving changing maxscratch up and down, moving data, and a few other hoops, and I was unable to get some tapes to move with a move data command (tapes that had only one master or msdb or tempdb type database on them). Level two calls back. I go through the entire situation, including the fact of the Max Mount Point having to change every time I did I /stirpes=2 backup (I wasn't sure if that was a related issue or not). She is baffled, and wants to think it over and search databases etc to see what she can come up with. Within 30 mins, she calls back and asks me to reboot the TSM server's OS (uptime reported a whopping 82 days), just to see what would happen. I do. Migrations go. Backups /stripes=1 go. Backups /stripes=2 go (even with MMP set back to 4 for that node, instead of 7 ( with only 5 tape drives remember). This was Friday. Sunday night, the TSM server did something odd (haven't reported this to TSM support yet). It just stopped. It showed link status on the fiber cards, and network cards, but you couldn't ping it, the server console wouldn't wake up, nothing. Even the display on the front was dark, but the power light was on steady like it was operational, not flashing like it would be if you did a proper shutdown. I reset it Monday morning when I found it that way, and then had to do a clean shutdown and power on to get the fiber cards to see the library correctly. Very weird. So, I am taking Monday morning (yesterday) as the start time to see how long it takes until I have to increase my MMP on the one node just to get a /stripes=2 backup. The saga continues... Conko, Steven To: [EMAIL PROTECTED] [EMAIL PROTECTED] cc: M Fax to: Sent by: Subject: Idle system fails with Media mount not possible ADSM: Dist Stor Manager [EMAIL PROTECTED] IST.EDU 12/17/2002 03:19 PM Please respond to ADSM: Dist Stor Manager strange one... and ive looked at everything i can think of. In client dsmerror.log: 12/17/02 15:01:54 ANS1228E Sending of object '/tibco/logs/hawk/log/Hawk4.log' failed 12/17/02 15:01:54 ANS1312E Server media mount not possible 12/17/02 15:01:57 ANS1312E Server media mount not possible In activity log: ANR0535W Transaction
