IBM Support

IT42631: VSNAP ENCRYPTION SHOWS AS DISABLED/POOL DOES NOT COME ONLINE, AFTER RUNNING VSNAP REPAIR

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • After vsnap repair create is run, the vSnap pool Encryption
    enabled shows as no. However, the disks that make up the vSnap
    pool show as encrypted.
    
    Example:
    
    vsnap repair create --async
    
    The vsnap repair completed successfully
    
    ID: 1
    NAME: primary
    POOL TYPE: raid6
    STATUS: ONLINE
    PLICATION: Yes
    DEDUPLICATION RATIO: 1.80
    ENCRYPTION:
    ENABLED: No
    
    Vsnap disk show:
    
    6005076400810 | SCSI | 10.00TB  | crypto_LUKS   | sdb   |
    /dev/sdb
    
    This is evident per the crypto_LUKS
    
    Additionally, if the vSnap server is rebooted after the repair
    is run, the pool fails to come online. This is due to the
    encryption key not having the correct name.
    
    To resolve this portion of the apar, see the local fix.
    
    Versions affected: 10.1.5 and later
    
    Keywords: TS011117995
    

Local fix

  • Review the repair.log file on the vsnap server.
    
    
    Find message similar to this:  Started repair. Entering
    repair mode.
    Below this message will be a message like:  Renaming pool 2 to
    1 in the db
    
    This shows the pool was changed from pool id 2 to pool id 1.
    
    Run the following commands to rename the encryption key:
    
    sudo mv /etc/vsnap/keys/vsnap.enckey.2
    /etc/vsnap/keys/vsnap.enckey.1
    sudo systemctl restart vsnap
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * IBM Spectrum Protect Plus levels 10.1.5 to 10.1.13           *
    ****************************************************************
    * 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.14. Note that this is subject to change at the          *
    * discretion of IBM.                                           *
    ****************************************************************
    

Problem conclusion

  • Implemented code fixes to ensure that the repair process
    correctly updates pool IDs in the internal database and renames
    the pool encryption keys correctly. Note that the fixes
    implemented will take effect for new repair operations performed
    after updating to the fix level. For existing systems that are
    in failed state, apply the local fix or retry the repair
    operation after updating to the fix level.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT42631

  • Reported component name

    SP PLUS

  • Reported component ID

    5737SPLUS

  • Reported release

    A1A

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2022-12-05

  • Closed date

    2023-01-31

  • Last modified date

    2023-01-31

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

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

Modules/Macros

  • vSnap
    

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":"A1A","Line of Business":{"code":"LOB26","label":"Storage"}}]

Document Information

Modified date:
01 February 2024