APAR status
Closed as program error.
Error description
IBM Spectrum Protect Plus SQL backup fails with the error: ERROR,...,Failed to perform backup of db instance <InstanceName> on application server <host> e=...xsb. commons.XSBException: Failed to setup target volume for backup :Failed to map luns to application server host: The command logs for the SQL Server report the following errors: DEBUG OSVolumeController - Command: [net start msiscsi] DEBUG sqlvdiwrapper - Check whether to block command [appdiscoveryCAL] or not DEBUG sqlvdiwrapper - output dir [c:\ProgramData\SPP\ 055accab-9692-4ddd-b407-2b5a67b4f348], output file [c:\ProgramData\SPP\055accab-9692-4ddd-b407-2b5a67b4f348\ output_sql.json] DEBUG sqlvdiwrapper - [snapshot_lock] lock does not exist, last error [(2, The system cannot find the file specified.)] At the vSnap layer, the individual ZFS volume becomes unmounted but the folder itself remains shared. As a result the log backups written to that volume start going to the root filesystem of the vSnap server. Eventually when the next backup job runs, the vSnap notices the volume has become unmounted and tries to remount it, but now it cannot because the underlying directory on the root filesystem is not empty. The log backups are not lost, they have been redirected to the wrong filesystem. IBM Spectrum Protect Plus Versions Affected: 10.1.2 and 10.1.3 Customer/L2 Diagnostics (If Applicable) N/A Initial Impact: Medium Additional Keywords: TS002082865 SPP ISPP SQL SPPSUP809
Local fix
NA
Problem summary
**************************************************************** * USERS AFFECTED: * * IBM Spectrum Protect Plus version 10.1.2 and 10.1.3 * **************************************************************** * 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.4. Note that this is subject to change at the * * discretion of IBM. * ****************************************************************
Problem conclusion
During a vSnap upgrade, some data services may not be shut down cleanly while updating kernel modules. This can result in ongoing log backups to be written to the root volume of the vSnap instead of to the data pool. It can also result in failed LUN mappings after the upgrade. The problem has been resolved by ensuring that data services are shut down cleanly during an upgrade.
Temporary fix
Comments
APAR Information
APAR number
IT28865
Reported component name
SP PLUS
Reported component ID
5737SPLUS
Reported release
A12
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2019-04-19
Closed date
2019-06-07
Last modified date
2019-06-07
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":"A12","Line of Business":{"code":"LOB26","label":"Storage"}}]
Document Information
Modified date:
30 January 2024