You are right Becky!

My mountpoints were set to zero (0).

I have no idea how they were reset to 0.

You are a backup saver!

Thank you very much!!!!!!!!!!!!!!




(Embedded image moved to file: pic28253.pcx)



                    "Davidson,
                    Becky"                To:     [EMAIL PROTECTED]
                    <Becky.Davidson       cc:
                    @SLBG.COM>            Subject:     Re: "Server media mount not 
possible" error condition
                    Sent by: "ADSM:
                    Dist Stor
                    Manager"
                    <[EMAIL PROTECTED]
                    ST.EDU>


                    01/18/2002
                    11:34 AM
                    Please respond
                    to "ADSM: Dist
                    Stor Manager"






Ken
Try a q node f=d to check to make sure that you have mount points greater
then 0
Becky

-----Original Message-----
From: Ken Sedlacek [mailto:[EMAIL PROTECTED]]
Sent: Friday, January 18, 2002 10:25 AM
To: [EMAIL PROTECTED]
Subject: "Server media mount not possible" error condition



Hi ALL:

I have a situation here as follows:

One TSM server 3.7.3
Two RS/6000 H70s at 4.3.3,
Two TSM clients 3.7.3
One shared Magstar 3570 20-cartridge library.

This configuration has been running well for many moons.

We only backup our Oracle dbs + AIX server environments with TSM.

I started getting the "ANS1312E Server media mount not possible" errors  a
few days ago.

Actual dsmerror.log:

01/17/02   03:27:56 ANS1312E Server media mount not possible

01/17/02   03:27:56 ANS1512E Scheduled event 'RS6000H70' failed.  Return
code =
4.
# castor :/ ==>

The dsmsched.log shows the same "ANS1312E Server media mount not possible"
error and the failed return code

The activity log reports:

01/16/02 23:30:01     ANR2561I Schedule prompter contacting POLLUXMUX
(session
                       191) to start a scheduled operation.

01/16/02 23:30:03     ANR0406I Session 192 started for node POLLUXMUX (AIX)

                       (Tcp/Ip 177.66.32.30(41946)).

01/16/02 23:30:09     ANR0406I Session 193 started for node POLLUXMUX (AIX)

                       (Tcp/Ip 177.66.32.30(41949)).

01/16/02 23:30:10     ANR0403I Session 193 ended for node POLLUXMUX (AIX).

01/17/02 00:00:01     ANR2562I Automatic event record deletion started.

01/17/02 00:00:01     ANR2102I Activity log pruning started: removing
entries
                       prior to 01/14/02 00:00:00.

01/17/02 00:00:01     ANR2565I 0 schedules for immediate client actions
have
                       been deleted.

01/17/02 00:00:01     ANR2563I Removing event records dated prior to
01/07/02
                       00:00:00.

01/17/02 00:00:01     ANR2564I Automatic event record deletion ended - 8
records
                       deleted.

01/17/02 00:00:02     ANR2103I Activity log pruning completed: 281 records

                       removed.

01/17/02 00:30:44     ANR0481W Session 192 for node POLLUXMUX (AIX)
terminated -
                       client did not respond within 3600 seconds.


01/17/02 03:30:01     ANR2561I Schedule prompter contacting CASTOROIL
(session
                       194) to start a scheduled operation.

01/17/02 03:30:03     ANR0406I Session 195 started for node CASTOROIL (AIX)

                       (Tcp/Ip 177.66.32.33(50501)).

01/17/02 03:30:21     ANR0406I Session 196 started for node CASTOROIL (AIX)

                       (Tcp/Ip 177.66.32.33(50506)).

01/17/02 03:30:22     ANR0403I Session 196 ended for node CASTOROIL (AIX).



01/17/02 04:30:45     ANR0481W Session 195 for node CASTOROIL (AIX)
terminated -
                       client did not respond within 3600 seconds.


The automated schedules each give the same error.

When I try and do a manual incremental or selective backups, the same error
occurs (ANS1312E Server media mount not possible).

I can manually do TSM db backups in the Magstar 3570 library with no
problems.

Audit library 3570lib runs without a problem.

I have restarted the TSM server and restarted each of the clients
schedulers to no avail.

I have checked the AIX errpt for any rmt1/2 errors. None reported!

This is a real stumper!!

Anyone have any ideas on this??

ps-I am thinking of upgrading to TSM v4.1 in-order to get TSM Tech support
availability.



(Embedded image moved to file: pic09894.pcx)


Attachment: pic28253.pcx
Description: Binary data

Reply via email to