Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Scribd Logo
Upload

Welcome to Scribd!

  • 535 views

    Vmchange Used For Ejection of Tapes

    Uploaded by

    amsreeku
    Running two separate vmchange commands to eject tapes, one with the -abort_ie option, can cause the subsequent vmupdate command to fail with a "Robot busy" error due to a timing issue. Using a single vmchange command with the -single_cycle option eliminates this problem because it does not return until the eject is fully completed.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as PDF, TXT or read online from Scribd

    Vmchange Used For Ejection of Tapes

    Uploaded by

    amsreeku
    535 views4 pages
    Running two separate vmchange commands to eject tapes, one with the -abort_ie option, can cause the subsequent vmupdate command to fail with a "Robot busy" error due to a timing issue. Using a single vmchange command with the -single_cycle option eliminates this problem because it does not return until the eject is fully completed.

    Original Title

    Vmchange Used for Ejection of Tapes

    Copyright

    © Attribution Non-Commercial (BY-NC)

    Available Formats

    PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Running two separate vmchange commands to eject tapes, one with the -abort_ie option, can cause the subsequent vmupdate command to fail with a "Robot busy" error due to a timing issue. Using a single vmchange command with the -single_cycle option eliminates this problem because it does not return until the eject is fully completed.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    535 views4 pages

    Vmchange Used For Ejection of Tapes

    Uploaded by

    amsreeku
    Running two separate vmchange commands to eject tapes, one with the -abort_ie option, can cause the subsequent vmupdate command to fail with a "Robot busy" error due to a timing issue. Using a single vmchange command with the -single_cycle option eliminates this problem because it does not return until the eject is fully completed.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    of 4

    After running vmchange with the -abort_ie option, robot inventory will fail with "Robot busy, cannot

    perf... Page 1 of 4

    Support Home | Supported Products A to Z

    Knowledge Base
    Document ID: 316433 Search
    http://support.veritas.com/docs/316433
    E-Mail this document to a colleague Advanced Search Op
    Other Support Re
    After running vmchange with the -abort_ie option, robot inventory will fail with
     Support Forum
    "Robot busy, cannot perform operation (223)". Ask an expert. J
    product discussi
    Forum communi
    Exact Error Message
     Manage Cases
    Robot Busy, Cannot Perform Operation (223) Submit and man
    cases using MyS
     Contact Techni
    Details: Find the support
    Overview: for your region.
    There are different methods of ejecting tapes when no one is present to remove the tapes
    from the library MAP.
    One method is to run two vmchange commands one after the other. The second Was this article h
    vmchange command uses the -abort_ie option which aborts the move but leaves the j Yes n
    k
    l
    m
    n j No
    k
    l
    m
    ejected tapes sitting in the robotic MAP.
    If any information wa
    information you were
    Example: provided, please let u
    feedback will help us
    # vmchange -res -multi_eject -verbose -rn ROBOT_NUMBER -rt service.
    tld -rh MEDIA_SERVER -ml (Enter comment her
    <media_id>:<media_id> ...:<media_id>
    # /usr/openv/volmgr/bin/vmchange -res -multi_eject - (Optional Email Add
    abort_ie -rt tld -rn <robot number> -rh <robot host>

    The above commands are then immediately followed by a vmupdate command to update
    the inventory. NOTE: Comments e
    NOT receive support
    Example: need Symantec Ente
    # /usr/openv/volmgr/bin/vmupdate -rt tld -rn <robot number> support, please click
    If the vmupdate command is failing with "Robot busy, cannot perform operation (223)",
    there may be a timing issue between the two commands vmchange and vmupdate.

    SOLUTION:
    Use a single vmchange command with the -single_cycle option instead of two
    vmchange commands, one with the -abort_ie option as shown above.
    Example:
    # /usr/openv/volmgr/bin/vmchange -res -multi_eject -rt tld
    -rn <robot number> -rh <robot host> -ml
    <media_id>:<media_id> ...:<media_id> -single_cycle

    Here's an example of the difference in commands:

    TEST 1 using two vmchange commands, one with -abort_ie:

    file://H:\study\netbackup\New Folder\Vmchange+eject.htm 7/6/2010


    After running vmchange with the -abort_ie option, robot inventory will fail with "Robot busy, cannot perf... Page 2 of 4

    # vmchange -res -multi_eject FX0020:FX0023 -rt tld -rn 0 -


    rh rosv240-03
    (This syntax returns immediately but is not actually complete.)

    The next commands are displaying the eject status for the test:
    (Note that the final field in the vmchange -verify_eject output is the eject status for that
    tape where 1=in slot, 2=in progress, 3=waiting removal, 6=eject complete.)

    # vmchange -res -multi_eject FX0020:FX0023 -rt tld -rn 0 -


    rh rosv240-03 -verify_eject
    MAILSLOT_STATUS 4 FX0020 UNKNOWN 1 1 1 <---in slot
    MAILSLOT_STATUS 7 FX0023 UNKNOWN 2 1 1 <-- in slot
    # vmchange -res -multi_eject FX0020:FX0023 -rt tld -rn 0 -
    rh rosv240-03 -verify_eject
    MAILSLOT_STATUS 4 FX0020 UNKNOWN 1 1 2 <-- in progress
    MAILSLOT_STATUS 7 FX0023 UNKNOWN 2 1 1 <-- in slot
    # vmchange -res -multi_eject FX0020:FX0023 -rt tld -rn 0 -
    rh rosv240-03 -verify_eject
    MAILSLOT_STATUS 4 FX0020 UNKNOWN 1 1 3 <-- waiting
    removal
    MAILSLOT_STATUS 7 FX0023 UNKNOWN 2 1 3 <-- waiting
    removal

    The next vmchange command aborts the eject as all the tapes are now in the MAP. If the
    vmchange eject was not aborted and it timed out, all the tapes would be returned to their
    respective slots.

    # vmchange -res -multi_eject FX0020:FX0023 -rt tld -rn 0 -


    rh rosv240-03 -abort_ie

    The eject is now considered complete as shown below:

    # vmchange -res -multi_eject FX0020:FX0023 -rt tld -rn 0 -


    rh rosv240-03 -verify_eject
    MAILSLOT_STATUS 4 FX0020 UNKNOWN 1 1 6 <--eject complete
    MAILSLOT_STATUS 7 FX0023 UNKNOWN 2 1 6 <--eject complete

    TEST 2 using the same tapes and "-single_cycle" syntax. The "-single_cycle" option
    automatically marks the ejected tapes as "complete" as soon as they're all moved to the
    MAP. This eliminates the need to execute the second vmchange -abort_ie command.
    Additionally the "-single_cycle" command option does not complete until the eject is done

    file://H:\study\netbackup\New Folder\Vmchange+eject.htm 7/6/2010


    After running vmchange with the -abort_ie option, robot inventory will fail with "Robot busy, cannot perf... Page 3 of 4

    which eliminates any timing issue when a subsequent vmupdate command is run.

    # vmchange -res -multi_eject -rt tld -rn 0 -rh rosv240-03 -


    single_cycle
    (Note this command does not return until completed)

    # vmchange -res -multi_eject FX0020:FX0023 -rt tld -rn 0 -


    rh rosv240-03 -verify_eject
    MAILSLOT_STATUS 4 FX0020 UNKNOWN 1 1 6 <--eject complete
    MAILSLOT_STATUS 7 FX0023 UNKNOWN 2 1 6 <--eject complete

    Products Applied:
    NetBackup Enterprise Server 6.0, 6.0 MP1,
    6.0 MP2, 6.0 MP3, 6.0 MP4, 6.0 MP5, 6.0
    MP6, 6.0 MP7, 6.5, 6.5.1, 6.5.2, 6.5.3

    Last Updated: January 02 2009 07:48 PM


    GMT
    Expires on: 01-01-2010
    Subscribe to receive critical updates
    about this document
    Subjects:
    NetBackup Enterprise Server
    Equipment: Robotic Hardware
    Solaris
    Application: Device Management

    Languages:
    English (US)

    Operating Systems:
    Solaris
    8.0

    Symantec World Headquarters:


    20330 Stevens Creek Blvd. Cupertino, CA 95014
    World Wide Web: http://www.symantec.com,
    Tech Support Web: http://entsupport.symantec.com,
    E-Mail Support:
    http://seer.entsupport.symantec.com/email_forms,

    file://H:\study\netbackup\New Folder\Vmchange+eject.htm 7/6/2010


    After running vmchange with the -abort_ie option, robot inventory will fail with "Robot busy, cannot perf... Page 4 of 4

    FTP: ftp://ftp.entsupport.symantec.com or
    http://ftp.entsupport.symantec.com

    THE INFORMATION PROVIDED IN THE SYMANTEC SOFTWARE KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY
    OF ANY KIND. SYMANTEC SOFTWARE DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE
    WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL SYMANTEC
    SOFTWARE OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL,
    CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES,EVEN IF SYMANTEC SOFTWARE OR ITS SUPPLIERS
    HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR
    LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT
    APPLY.

    file://H:\study\netbackup\New Folder\Vmchange+eject.htm 7/6/2010

    You might also like