Operational Defect Database
BugZero found this defect 427 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
Veeam | kb4380
After Upgrade to Veeam Backup & Replication 12, Storage Rescan of IBM HyperSwap Volume Fails
Last update date:
3/20/2023
Affected products:
Veeam Backup & Replication
Affected releases:
12
Fixed releases:
No fixed releases provided.
Description:
Challenge
After upgrading to Veeam Backup & Replication 12, Storage Rescan fails with: Failed to update information about IBM HyperSwap volumes. Please ensure that volumes on both sides of IBM HyperSwap relationships are included in the rescan scope in the storage properties. See KB4380 for details.
Cause
During the upgrade to Veeam Backup & Replication 12, the configuration upgrade procedure will attempt to associate snapshots with their respective volume on the corresponding IBM HyperSwap relationship. However, in a configuration where only the volume on one side of the relationship was added to the list of volumes to scan for the IBM storage array, the upgrade procedures attempt to correlate snapshots and volumes cannot succeed. In such a scenario, to avoid the removal of snapshots on secondary volume from the database, the v12 rescan process will fail.
Solution
Edit the Storage System within the Veeam Backup & Replication console, and ensure that volumes on both sides of IBM HyperSwap relationships are included in the rescan scope.
More Information
In Veeam Backup & Replication 11, snapshots on both sides of the IBM HyperSwap relationship were returned for the volume. To perform a backup from the secondary side of the relationship, setting the IbmHyperSwapUseSecondary registry value was required. Veeam Backup & Replication 12 can separately query each side of the IBM Hyperswap relationship and return corresponding snapshots only, allowing users to explicitly select within the backup job which side should be used as the backup source. In Veeam Backup & Replication 12, the registry value IbmHyperSwapUseSecondary is deprecated.
