IT34678: 'BACKUP FAILED: INVALID INDEX' DURING WINDOWS FILE SYSTEM BACKUPS.

APAR status

• Closed as program error.

Error description

• If a reparse point, such as a symbolic link, with meta data
  larger than 1024 bytes is encountered during a Windows
  file system backup, the object is skipped and the backup
  continues.
  
  The job will show as a failed job in the dashboard with the
  message 'Backup failed: invalid index'.
  
  Diagnostics:
  These steps can be taken to confirm the issue is being seen.
  1. View the failing JobLog with the 'Backup failed: invalid
  index' message and save the job number
  reported in the first line.
  
  2. Generate an IBM Spectrum Protect Plus Server log bundle.
  
  3. Extract the bundle to a temporary location.
  
  4. Navigate to the location matching this description:
  
  /logs/application/<Job_Number>/<Faling_VM_IP_Address>/
  
  5.  Search the command.log file for 'WindowsReparse.py', without
  quotes. The text should be near the end of the file.
  
  If 'WindowsReparse.py' is found in the command.log file, it
  indicates a reparse point was encountered.
  
  Initial impact:
  Low
  Versions affected: 10.1.6
  
  Additional keywords: SPP ISPP
  TS004019511
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * IBM Spectrum Protect Plus level 10.1.6 - File System Backup  *
  * on Windows                                                   *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * see ERROR DESCRIPTION                                        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Apply fixing level when available. This problem is currently *
  * projected to be fixed IBM Spectrum Protect Plus levels       *
  * 10.1.7.                                                      *
  * Note that this is subject to change at the discretion of     *
  * IBM.                                                         *
  ****************************************************************
  

Problem conclusion

• The problem has been fixed so that reparse points, such as
  symbolic links, with meta data larger than 1024 bytes are backed
  up successfully.
  

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:

Fix information

• Fixed component name

  SP PLUS

• Fixed component ID

  5737SPLUS

Applicable component levels