Verified Answers

If an answer to your question is correct, click on "Verify Answer" under the "More" button. The answer will now appear with a checkmark. Please be sure to always mark answers that resolve your issue as verified. Your fellow Community members will appreciate it! Learn more

  • State Suggested Answer
  • Replies replies
    7
  • Answers answer
    1
  • Subscribers subscribers
    12
  • Views views
    1003
  • Users 0 members are here
Related
Options

Backup shows mount request for cleaning tape

Mario Vrablansky

Hello,

I have following problem on my DP server ( v 10.80 )
Tape Library : HP StorageWorks MSL 2024 G3 Series

Backup is configured to use pool sql_pool ( Appendable/Loose and use free pool free_pool)

There is enough media in free_pool
omnimm -list_scratch_media free_pool

Allocation order for pool : free_pool
Nr. Medium Label Location
==============================================================================
1 [FAV973L6] FAV973L6 HP:MSL G3 Series: 14
2 [FAV998L6] FAV998L6 HP:MSL G3 Series: 39
3 [FAV974L6] FAV974L6 HP:MSL G3 Series: 15
4 [FAV997L6] FAV997L6 HP:MSL G3 Series: 38
5 [FAW001L6] FAW001L6 HP:MSL G3 Series: 42
6 [FAV977L6] FAV977L6 HP:MSL G3 Series: 18
7 [FAV978L6] FAV978L6 HP:MSL G3 Series: 19
8 [FAW002L6] FAW002L6 HP:MSL G3 Series: 43
9 [FAV985L6] FAV985L6 HP:MSL G3 Series: 26
10 [FAV980L6] FAV980L6 HP:MSL G3 Series: 21
11 [FAV976L6] FAV976L6 HP:MSL G3 Series: 17
12 [FAV960L6] FAV960L6 HP:MSL G3 Series: 1
13 [FAV986L6] FAV986L6 HP:MSL G3 Series: 27
14 [FAV964L6] FAV964L6 HP:MSL G3 Series: 5


After starting backup i see in GUI that backup is in state Mount request and ask for cleaning tape CLNU00L1 in slot 45.

When i confirm mount request it loads cleaning media and show message "Drive of device "HP:Ultrium 6-SCSI_1" seems to be clean now"
But then ask to mount CLNU00L1 again. Why is backup asking for cleaning tape CLNU00L1 from slot 45 when there is enough tapes in free_pool ?

I tried turn off Detect dirty drive but it didnt help.

Thank you

[Normal] From: BMA@XXXXXXXX "HP:Ultrium 6-SCSI_1" Time: 11/3/2023 9:00:30 PM
STARTING Media Agent "HP:Ultrium 6-SCSI_1"

[Warning] From: BSM@XXXXXXXX "HP:Ultrium 6-SCSI_1" Time: 11/3/2023 9:00:33 PM
___________________________________________________________________
Mount request for any medium (blank or without protection):
Device : HP:Ultrium 6-SCSI_1
Host : XXXXXXXX
Slot : 45
___________________________________________________________________


[Normal] From: BSM@XXXXXXXX "sql_BBCLHIS11" Time: 11/3/2023 10:30:51 PM
Starting the mount request notification script "C:\Program Files\OmniBack\bin\Mount.bat".

[Normal] From: BMA@XXXXXXXX "HP:Ultrium 6-SCSI_1" Time: 11/6/2023 10:19:53 AM
=> UMA@XXXXXXXX@Changer0:0:0:1
Loading medium from slot 45 to device Tape0:0:0:0C

[Normal] From: BMA@XXXXXXXX "HP:Ultrium 6-SCSI_1" Time: 11/6/2023 10:22:04 AM
=> UMA@XXXXXXXX@Changer0:0:0:1
Cleaning Tape detected

[Normal] From: BSM@XXXXXXXX "sql_BBCLHIS11" Time: 11/6/2023 10:22:04 AM
Drive of device "HP:Ultrium 6-SCSI_1" seems to be clean now.

[Normal] From: BMA@XXXXXXXX "HP:Ultrium 6-SCSI_1" Time: 11/6/2023 10:22:04 AM
=> UMA@XXXXXXXX@Changer0:0:0:1
Unloading medium to slot 45 from device Tape0:0:0:0C

[Warning] From: BSM@XXXXXXXX "HP:Ultrium 6-SCSI_1" Time: 11/6/2023 10:23:34 AM
___________________________________________________________________
Mount request for any medium (blank or without protection):
Device : HP:Ultrium 6-SCSI_1
Host : XXXXXXXX
Slot : 45
___________________________________________________________________


[Normal] From: BMA@XXXXXXXX "HP:Ultrium 6-SCSI_1" Time: 11/6/2023 10:25:19 AM
=> UMA@XXXXXXXX@Changer0:0:0:1
Loading medium from slot 45 to device Tape0:0:0:0C

[Normal] From: BMA@XXXXXXXX "HP:Ultrium 6-SCSI_1" Time: 11/6/2023 10:27:24 AM
=> UMA@XXXXXXXX@Changer0:0:0:1
Cleaning Tape detected

[Normal] From: BSM@XXXXXXXX "sql_BBCLHIS11" Time: 11/6/2023 10:27:24 AM
Drive of device "HP:Ultrium 6-SCSI_1" seems to be clean now.

[Normal] From: BMA@XXXXXXXX "HP:Ultrium 6-SCSI_1" Time: 11/6/2023 10:27:24 AM
=> UMA@XXXXXXXX@Changer0:0:0:1
Unloading medium to slot 45 from device Tape0:0:0:0C

[Warning] From: BSM@XXXXXXXX "HP:Ultrium 6-SCSI_1" Time: 11/6/2023 10:28:55 AM
___________________________________________________________________
Mount request for any medium (blank or without protection):
Device : HP:Ultrium 6-SCSI_1
Host : XXXXXXXX
Slot : 45
___________________________________________________________________


[Normal] From: BMA@XXXXXXXX "HP:Ultrium 6-SCSI_1" Time: 11/6/2023 10:29:32 AM
=> UMA@XXXXXXXX@Changer0:0:0:1
Loading medium from slot 45 to device Tape0:0:0:0C

[Normal] From: BMA@XXXXXXXX "HP:Ultrium 6-SCSI_1" Time: 11/6/2023 10:31:40 AM
=> UMA@XXXXXXXX@Changer0:0:0:1
Cleaning Tape detected

[Normal] From: BSM@XXXXXXXX "sql_BBCLHIS11" Time: 11/6/2023 10:31:40 AM
Drive of device "HP:Ultrium 6-SCSI_1" seems to be clean now.

[Normal] From: BMA@XXXXXXXX "HP:Ultrium 6-SCSI_1" Time: 11/6/2023 10:31:40 AM
=> UMA@XXXXXXXX@Changer0:0:0:1
Unloading medium to slot 45 from device Tape0:0:0:0C

[Warning] From: BSM@XXXXXXXX "HP:Ultrium 6-SCSI_1" Time: 11/6/2023 10:33:10 AM
___________________________________________________________________
Mount request for any medium (blank or without protection):
Device : HP:Ultrium 6-SCSI_1
Host : XXXXXXXX
Slot : 45
___________________________________________________________________


[Normal] From: BSM@XXXXXXXX "sql_BBCLHIS11" Time: 11/6/2023 12:03:29 PM
Starting the mount request notification script "C:\Program Files\OmniBack\bin\Mount.bat".

[Normal] From: BMA@XXXXXXXX "HP:Ultrium 6-SCSI_1" Time: 11/6/2023 12:13:15 PM
=> UMA@XXXXXXXX@Changer0:0:0:1
Loading medium from slot 45 to device Tape0:0:0:0C

[Normal] From: BMA@XXXXXXXX "HP:Ultrium 6-SCSI_1" Time: 11/6/2023 12:15:29 PM
=> UMA@XXXXXXXX@Changer0:0:0:1
Cleaning Tape detected

[Normal] From: BSM@XXXXXXXX "sql_BBCLHIS11" Time: 11/6/2023 12:15:29 PM
Drive of device "HP:Ultrium 6-SCSI_1" seems to be clean now.

[Normal] From: BMA@XXXXXXXX "HP:Ultrium 6-SCSI_1" Time: 11/6/2023 12:15:29 PM
=> UMA@XXXXXXXX@Changer0:0:0:1
Unloading medium to slot 45 from device Tape0:0:0:0C

[Warning] From: BSM@XXXXXXXX "HP:Ultrium 6-SCSI_1" Time: 11/6/2023 12:16:59 PM
___________________________________________________________________
Mount request for any medium (blank or without protection):
Device : HP:Ultrium 6-SCSI_1
Host : XXXXXXXX

  • 0  

    Hello Mario

    Does it happen at the begin of session or mount request happen in the middle of backup?

    Please provide output for command omnimm -show_pool_alloc "poolname"

    Best Regards

  • 0 in reply to   

    Hello,

    Thank you for quick reply. It's in the beginning of session. Here is the output.

    omnimm -show_pool_alloc sql_pool

    Allocation order for pool : sql_pool
    Nr. Medium Label Location
    ==============================================================================
    1 [FAV962L6] FAV962L6 HP:MSL G3 Series: 3
    ===============================================================================
    Available for allocation : 0 [KB]

    omnimm -show_pool_alloc free_pool

    Allocation order for pool : free_pool
    Nr. Medium Label Location
    ==============================================================================
    1 [FAV973L6] FAV973L6 HP:MSL G3 Series: 14
    2 [FAV998L6] FAV998L6 HP:MSL G3 Series: 39
    3 [FAV974L6] FAV974L6 HP:MSL G3 Series: 15
    4 [FAV997L6] FAV997L6 HP:MSL G3 Series: 38
    5 [FAW001L6] FAW001L6 HP:MSL G3 Series: 42
    6 [FAV977L6] FAV977L6 HP:MSL G3 Series: 18
    7 [FAV978L6] FAV978L6 HP:MSL G3 Series: 19
    8 [FAW002L6] FAW002L6 HP:MSL G3 Series: 43
    9 [FAV985L6] FAV985L6 HP:MSL G3 Series: 26
    10 [FAV980L6] FAV980L6 HP:MSL G3 Series: 21
    11 [FAV976L6] FAV976L6 HP:MSL G3 Series: 17
    12 [FAV960L6] FAV960L6 HP:MSL G3 Series: 1
    13 [FAV986L6] FAV986L6 HP:MSL G3 Series: 27
    14 [FAV964L6] FAV964L6 HP:MSL G3 Series: 5
    ===============================================================================
    Available for allocation : 115379643136 [KB]

  • 0  

    The cleaning operation seems to be succesful. The question is why there is a second mount request seen, right? The second mount request seems to be "for any medium (blank or without protection)", not for the cleaning tape anymore. At first sight, this looks like a bug. Disclaimer: I did not say it is a bug, only it looks like that at first sight.

    As you are running an unsupported version, you would not be able to log a case for this. Now, I'm assuming you saw this once and cannot reproduce it anymore as you should not see cleaning requests that often. Is that indeed the case? If you see cleaning requests regularly then I would have the device checked from a hardware point of view first of all. Just my 2 cents ...

    Koen Verbelen

    Although I am an OpenText employee, I am speaking for myself and not for OpenText.
    If you found this post useful, give it a “Like” or click on "Verify Answer" under the "More" button.
    You may also be interested in my Data Protector Support Tips listed per category

  • 0  

    Also, if there is a cleaning slot configured then there should not be a need for the cleaning tape mount request in the first place. Is there a cleaning slot configured? And is there a cleaning tape loaded in that slot?

    You can check the cleaning slot config in the GUI (Repository tab in the library properties) or with: omnidownload -library LibraryName

    You can check the slot contents in the GUI or with : omnimm -repository LibraryName

    Koen Verbelen

    Although I am an OpenText employee, I am speaking for myself and not for OpenText.
    If you found this post useful, give it a “Like” or click on "Verify Answer" under the "More" button.
    You may also be interested in my Data Protector Support Tips listed per category

  • 0 in reply to   

    Yes exaclty. Library has barcode reader and it's enabled in DP GUI for library. According to documentation cleaning process should be fully automatic. Just enable "Dirty drive detection" and DP should take care about cleaning with libraries which have barcode reader. It should not ask for manual mount. 

    I think DP somehow thinks there are no free tapes and always ask for cleaning tape CLNU00L1 in slot 45. 

    All tapes on free_pool are listed as Protection : Expired which should be fine. 


    omnidownload -library "HP:MSL G3 Series"
    NAME "HP:MSL G3 Series"
    DESCRIPTION "HP StorageWorks MSL 2024 G3 Series"
    HOST XXXXXXXX
    POLICY SCSI-II
    TYPE LTO-Ultrium
    BARCODEREADER
    SANSTABLEADDR
    IOCTLSERIAL "DEC44905UW"
    CONTROL "Changer0:0:0:1"
    REPOSITORY
    "1"
    "2"
    "3"
    "4"
    "5"
    "6"
    "7"
    "8"
    "9"
    "10"
    "11"
    "12"
    "13"
    "14"
    "15"
    "16"
    "17"
    "18"
    "19"
    "20"
    "21"
    "22"
    "23"
    "24"
    "25"
    "26"
    "27"
    "28"
    "29"
    "30"
    "31"
    "32"
    "33"
    "34"
    "35"
    "36"
    "37"
    "38"
    "39"
    "40"
    "41"
    "42"
    "43"
    "44"
    "45"
    MULTIPATH
    "XXXXXXXX";"Changer0:0:0:1"
    "XXXXXXXX";"scsi2:0:0:1"

    omnimm -repository "HP:MSL G3 Series"

    Slot [side] Medium Medium Label (ID)
    ===============================================================================
    1 Data Protector [FAV960L6] FAV960L6
    2 Data Protector [FAV961L6] FAV961L6
    3 Data Protector [FAV962L6] FAV962L6
    4 Data Protector [FAV963L6] FAV963L6
    5 Data Protector [FAV964L6] FAV964L6
    6 Data Protector [FAV965L6] FAV965L6
    7 Data Protector [FAV966L6] FAV966L6
    8 Data Protector [FAV967L6] FAV967L6
    9 Data Protector [FAV968L6] FAV968L6
    10 Data Protector [FAV969L6] FAV969L6
    11 Data Protector [FAV970L6] FAV970L6
    12 Data Protector [FAV971L6] FAV971L6
    13 Data Protector [FAV972L6] FAV972L6
    14 Data Protector [FAV973L6] FAV973L6
    15 Data Protector [FAV974L6] FAV974L6
    16 Data Protector [FAV975L6] FAV975L6
    17 Data Protector [FAV976L6] FAV976L6
    18 Data Protector [FAV977L6] FAV977L6
    19 Data Protector [FAV978L6] FAV978L6
    20 Data Protector [FAV979L6] FAV979L6
    21 Data Protector [FAV980L6] FAV980L6
    22 Data Protector [FAV981L6] FAV981L6
    23 Data Protector [FAV982L6] FAV982L6
    24 Data Protector [FAV983L6] FAV983L6
    25 Data Protector [FAV984L6] FAV984L6
    26 Data Protector [FAV985L6] FAV985L6
    27 Data Protector [FAV986L6] FAV986L6
    28 Data Protector [FAV987L6] FAV987L6
    29 Data Protector [FAV988L6] FAV988L6
    30 Data Protector [FAV989L6] FAV989L6
    31 Data Protector [FAV990L6] FAV990L6
    32 Data Protector [FAV991L6] FAV991L6
    33 Data Protector [FAV992L6] FAV992L6
    34 Data Protector [FAV993L6] FAV993L6
    35 Data Protector [FAV994L6] FAV994L6
    36 Data Protector [FAV995L6] FAV995L6
    37 Data Protector [FAV996L6] FAV996L6
    38 Data Protector [FAV997L6] FAV997L6
    39 Data Protector [FAV998L6] FAV998L6
    40 Data Protector [FAV999L6] FAV999L6
    41 Data Protector [FAW000L6] FAW000L6
    42 Data Protector [FAW001L6] FAW001L6
    43 Data Protector [FAW002L6] FAW002L6
    44 Data Protector [FAW003L6] FAW003L6
    45 Cleaning tape [CLNU00L1]

  • Suggested Answer

    0   in reply to 

    OK, I do see the cleaning tape in slot 45, I do not see the cleaning slot configuration. But I checked and that's actually not required. That option seems to be there for libraries without barcode support.

    Now, after taking a closer look again (only), I realized that there's never a dirty drive detected and you're only seeing a mount request for a blank or unprotected tape all the time!The most plausible explanation would be that at the time of this mount request there was indeed no tape available. Is that possible? That would also explain why the mount request is issued for the cleaning slot ... because all other slots were occupied with protected tapes at that time.

    Please double check the backup spec, is it specifying a pool? If not then it is the default pool for the device that will be used. So please double check which pool exactly is used for this backup. Next make sure that pool is indeed using the freepool. And when all this is confirmed, think about the possibility there may not have been tapes available at the time of the mount request. The media.log file may possibly help to anayse the situation and understand when tapes became available.

    Otherwise, if you really believe tapes were available then the problem would still be reproducible, right? That would mean you could generate debugs. But the question is again whether it would make sense, as you won't get any lab support (so nothing would get fixed) anymore for 10.80. It may be time to upgrade to a more recent version. It's still pretty new, but I'm hearing positive feedback about our latest version 23.4, I did not hear about any critical issues at all and this version is supported until October 2026. Maybe something to think about.

    Koen Verbelen

    Although I am an OpenText employee, I am speaking for myself and not for OpenText.
    If you found this post useful, give it a “Like” or click on "Verify Answer" under the "More" button.
    You may also be interested in my Data Protector Support Tips listed per category

  • 0   in reply to   

    Has this been resolved? Would you mind sharing the outcome? Thanks.

    Koen Verbelen

    Although I am an OpenText employee, I am speaking for myself and not for OpenText.
    If you found this post useful, give it a “Like” or click on "Verify Answer" under the "More" button.
    You may also be interested in my Data Protector Support Tips listed per category

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Cookies Preferences
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.