IBM Support

IT45103: STARTING WITH VERSION 10.1.15, VM BACKUPS FAIL TO CLEAN UP HOTADDED GUEST DISKS FROM THE VADP HOST

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • The VMware guest protection using IBM Storage Protect Plus and
    the HotAdd VMware transport method can successfully complete but
    leave the protected guest hotadded disks still connected to
    the vADP host.
    In the /var/log/messages file of the vADP host,
    a crash + automatic restart of the vADP process can be observed
    when the backup job was active.
    
    The crash message can vary and the following were observed :
    
    <timestamp> <hostname> systemd[1]: Started Process Core Dump
                           (PID 19207/UID 0).
    <timestamp> <hostname> systemd-coredump[19208]: Process 16886
                           (vmdkbackup) of user 0 dumped core.
    Stack trace of thread 16896:
         #0  .. runtime.raise.abi0 (vmdkbackup)
         #1  .. runtime.raisebadsignal (vmdkbackup)
         #2  .. runtime.badsignal (vmdkbackup)
         #3  .. runtime.sigtrampgo (vmdkbackup)
         #4  .. runtime.sigtramp.abi0 (vmdkbackup)
         #5  .. __restore_rt (libpthread.so.0)
         #6  .. pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
         #7  .. n/a (libvmacore.so)
         #8  .. n/a (libvmacore.so)
         #9  .. n/a (libvmacore.so)
         #10 .. start_thread (libpthread.so.0)
         #11 .. __clone (libc.so.6)
    Stack trace of thread 17576:
         #0  .. runtime.futex.abi0 (vmdkbackup)
         #1  .. runtime.futexsleep (vmdkbackup)
         #2  .. runtime.notesleep (vmdkbackup)
         #3  .. runtime.mPark (vmdkbackup)
         #4  .. runtime.stopm (vmdkbackup)
         #5  .. runtime.findRunnable (vmdkbackup)
         #6  .. runtime.schedule (vmdkbackup)
         #7  .. runtime.park_m (vmdkbackup)
         #8  .. runtime.mcall (vmdkbackup)
         #9  .. n/a (n/a)
    
    or
    
    <timestamp> <hostname> systemd[1]: Started Process Core Dump
                           (PID 46581/UID 0).
    <timestamp> <hostname> systemd-coredump[46596]: Process 97523
                           (vmdkbackup) of user 0 dumped core.
    Stack trace of thread 97529:
       #0  .. runtime.raise.abi0 (vmdkbackup)
       #1  .. runtime.dieFromSignal (vmdkbackup)
       #2  .. runtime.sigfwdgo (vmdkbackup)
       #3  .. runtime.sigtrampgo (vmdkbackup)
       #4  .. runtime.sigtramp.abi0 (vmdkbackup)
       #5  .. __restore_rt (libpthread.so.0)
       #6  .. runtime.raise.abi0 (vmdkbackup)
       #7  .. runtime.dieFromSignal (vmdkbackup)
       #8  .. runtime.crash (vmdkbackup)
       #9  .. runtime.fatalthrow.func1 (vmdkbackup)
       #10 .. runtime.fatalthrow (vmdkbackup)
       #11 .. runtime.throw (vmdkbackup)
       #12 .. runtime.sigpanic (vmdkbackup)
       #13 .. n/a (libdiskLibPlugin.so)
       #14 .. n/a (libdiskLibPlugin.so)
       #15 .. n/a (libdiskLibPlugin.so)
       #16 .. n/a (libdiskLibPlugin.so)
       #17 .. n/a (libdiskLibPlugin.so)
       #18 .. n/a (libdiskLibPlugin.so)
       #19 .. n/a (libdiskLibPlugin.so)
       #20 .. n/a (libdiskLibPlugin.so)
       #21 .. n/a (libvixDiskLib.so.7.0.1)
       #22 .. VixDiskLib_Open (libvixDiskLib.so.7.0.1)
       #23 .. Vix_Open (vmdkbackup)
       #24 .. runtime.asmcgocall.abi0 (vmdkbackup)
       #25 .. runtime.park_m (vmdkbackup)
       #26 .. n/a (n/a)
    
    
    | MDVREGR  10.1.14.2 5737SPLUS |
    
    IBM Storage Protect Plus Versions Affected:
    IBM Storage Protect Plus 10.1.15 and later
    
    Additional Keywords: SPP, SPPLUS, crash, dump, TS013706671
    

Local fix

  • Update the vADP transport selection option to use NBD or NBDSSL
    instead.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * IBM Spectrum Protect Plus level 10.1.15.                     *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See ERROR DESCRIPTION                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Apply fixing level when available. This problem is currently *
    * projected to be fixed in IBM Spectrum Protect Plus level     *
    * 10.1.16. Note that this is subject to change at the          *
    * discretion of IBM                                            *
    ****************************************************************
    

Problem conclusion

  • This problem has been fixed so that when open disk timeout is
    encountered in VMware backup of hot-add transport mode, the
    backup disks will not be left behind.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT45103

  • Reported component name

    SP PLUS

  • Reported component ID

    5737SPLUS

  • Reported release

    A1F

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2023-12-07

  • Closed date

    2023-12-18

  • Last modified date

    2023-12-18

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    SP PLUS

  • Fixed component ID

    5737SPLUS

Applicable component levels

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSNQFQ","label":"IBM Spectrum Protect Plus"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"A1F","Line of Business":{"code":"LOB26","label":"Storage"}}]

Document Information

Modified date:
18 December 2023