IT41107: INCREMENTAL BACKUP FORCED TO BASE BACKUP FOR GUESTS INCLUDING '&' IN THEIR NAME

APAR status

• Closed as program error.

Error description

• Protecting with IBM Spectrum Protect Plus VMware guests that
  contain the ampersand character ('&'), results in full base
  backups instead of the expected incremental backups.
  The cause for switching from incremental to base backup is seen
  in the virgo log found in the job log bundle.
  
  Example with VMware guest name ?VM_1 & Co? :
  
  INFO .. Vm VM_1 & Co running incremental
  
  INFO .. Flags for cbt backup for vm: VM_1 & Co .. backup type:
          incremental
  
  INFO .. Checking volumes for VM VM_1 & Co -> <datastore>
  INFO .. Getting volume with groupId <GroupID>
  INFO .. destVolume <vSnapVolName>
  INFO .. Vsnap Call https://<vSnapHost>:8900/api/volume/
          <vSnapVolId>/path?path=<vSnapFolder>/VM_1 & Co.
          vm-<MobId> method GET
  ...
  INFO .. VSnap Call GET https://<vSnapHost>:8900/api/volume/
          <vSnapVolId>/path?path=<vSnapFolder>/VM_1 & Co.
          vm-<MobId> time Taken 188 ms
  INFO .. reason : org.springframework.web.client.
          HttpClientErrorException: 404 NOT FOUND
  INFO .. Status: :: 404
  INFO .. Vsnap object not found exception
  INFO .. volumeInfo : 2102.volume.<vSnapVolId> group <GroupID>
  INFO .. VM: VM_1 & Co will be run as forced base backup
  
  The reason not finding the previous restore point on the vSnap
  is found in the vsnap.log also present in the job log bundle :
  
  INFO pid-3021 vsnap.api    API request started: GET /volume/
                             <vSnapVolId>/path?path=<vSnapFolder>
                             /VM_1%20&%20Co.vm-<MobId> |
                             Body: None
  ERROR pid-3021 vsnap.api    Traceback (most recent call last):
        ...
        vsnap.common.errors.PathNotFoundError:
        Path <vSnapFolder>/VM_1 not found
  
  The last error message displays the incorrect search argument
  for the path as the guest name was truncated at the '&'
  position from ?VM_1 & Co? to ?VM_1?.
  The backup data is stored in the expected vSnap path :
  /vsnap/vpool<PoolId>/fs<VolId>/<vSnapFolder>/VM_1 & Co.
  vm-<MobId>
  
  This does not affect protection for Hyper-V guests.
  
  IBM Spectrum Protect Plus Versions Affected:
  IBM Spectrum Protect Plus 10.1.x
  
  Additional Keywords: SPP, SPPLUS, TS009427987
  

Local fix

• Avoid using '&' in the guest names.
  If encountering the issue, migrate the VM to a new name.
  Only renaming the VM is not sufficient as the VM files and
  folder on the datastore still will have the original name that
  includes '&'.
  

Problem summary

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

Problem conclusion

• The fix for this issue was to properly encode VM names with & in
  them.
  

Temporary fix

Comments

APAR Information

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

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

Modules/Macros

• Hypervis
  

Fix information

• Fixed component name

  SP PLUS

• Fixed component ID

  5737SPLUS

Applicable component levels