Forum Discussion

Casey_King's avatar
Casey_King
Level 6
19 years ago

PEND-TLD status on Drive

I have an LTO1 drive shared between two AIX servers, one AIX server 1, the drive status was PEND-TLD, and on AIX server 2, the status was up.

From Admin Console:

I downed the drive on both servers, reset the drive, and then UP'ed the drive. The status showed up, so to test the drive I kicked off a backup from my master server. The policy I used required AIX server 1. Once the server attempted to access the drive, the status changed to PEND-TLD.

From Server 1

changed to /usr/openv/volmgr/bin/

stopped NB by running ./stopltid
ran ps -ef to ensure the process was in fact stopped
started NB by running ./ltid args

Once again I went back to the NB Admin Console on the Master Server, and downed, reset, and up'd drive....same problem.

Seeing no change, I went back to my putty session and looked at the drive status on the server itself with ./tpconfig -l

The drive in question showed status down.

Ran the following command:

tpconfig -update -drive 4 -drstatus UP


The status of the drive now shows up, but the Admin Console does not reflect this status. I cannot remember what to do at this point. I know I need to execute a 'scan' from the master server so it will go out and see the new drive status on the server, but I do not remember the command to execute. Any help please?
7.1.x and Earlier
Backup and Recovery
NetBackup

8 Replies

Sort By
  • Stumpr2's avatar
    Stumpr2
    Level 6
    19 years ago
    try
    vmoprcmd -crawlreleasebyname

    here is a technote to read:
    The following list describes the current drive status field descriptions for drives within a VERITAS NetBackup (tm) configuration.
    http://support.veritas.com/docs/266700Message was edited by:
    Bob Stump
  • Dennis_Strom's avatar
    Dennis_Strom
    Level 6
    19 years ago
    http://support.veritas.com/docs/250534
    Drives go into "PEND-TLD" mode


    252419: Device Monitor or vmoprcmd output shows that the drive is in PEND status.
    http://support.veritas.com/docs/252419Message was edited by:
    Dennis Strom
  • Casey_King's avatar
    Casey_King
    Level 6
    19 years ago
    I read through each link you guys sent for my problem and followed instructions, but still had problems. I ended up rebooting the server and cleaning the drive. I have not had any problems since then. I don't like the idea of needing to reboot the server to fix the problem though.
  • Stumpr2's avatar
    Stumpr2
    Level 6
    19 years ago
    Casey,
    I had this problem this morning. A tape drive had a tape in it but it was not assigned to any server according to the scan_host. I removed the drive and then ran vmoprcmd -SSOdownbyname $drivename and then I ran crawlreleasebyname and finally -SSOupbyname. This seemed to fix the problem but then the first time a server attempted to use the tapedrive it failed and I had to force eject the tape. Now I need to call Sun (STK) to come in and look at the tapedrive because it obviously has something wrong.
  • Casey_King's avatar
    Casey_King
    Level 6
    19 years ago
    I think I will do the same thing if this problems arises on the same drive again. Did the drive show the same status on all media servers it is shared with or was it just on one?
  • Rakesh_Khandelw's avatar
    Rakesh_Khandelw
    Level 6
    19 years ago
    run tpautoconf -report_disc

    and see if it reports any descripancies with drive/s in question.
  • Stumpr2's avatar
    Stumpr2
    Level 6
    19 years ago
    Only the one that tried to use it :-)

    ...meaning whichever server initially attempted to use the tapedrive it would go down on that server. The other servers would get a reservation conflict and would not attempt using it as it goes into a pending state.

    Can be kind of deceiving, no?
  • Casey_King's avatar
    Casey_King
    Level 6
    19 years ago
    Bob,

    Let me know what STK says about this. I would be extremely interested in the "fix." I am tired of playing games with this drive, but since it is currently "working" I have no issue.

    thanks

    Casey