IJ47005: MMBACKUP: MIGRATED FILES SHOULD NOT BE COUNTED AS BACKUP CANDIDATES IF --SKIP-MIGRATED IS USED.

APAR status

• Closed as program error.

Error description

• When mmbackup calculates number of backup candidates, it counts
  migrated files as backup candidates. It is incorrect unless
  --backup-migrated is used, because migrated files will not be
  backed up. This incorrect calculation results in mmbackup
  completion with error due to "some skipped files".
  

Local fix

Problem summary

• When mmbackup calculates number of backup candidates, it counts
  migrated files as backup candidates. It is incorrect unless
  --backup-migrated is used, because migrated files will not be
  backed up. This incorrect calculation results in mmbackup
  completion with error due to "some skipped files".
  

Problem conclusion

• This problem is fixed in 5.1.2.12 
  To see all Spectrum Scale APARs and their respective
  Fix solutions refer to page:
  https://public.dhe.ibm.com/storage/spectrumscale/spectrum_scale_
  apars.html
  
  Benefits of the solution:
  Unless there is no other
  error, mmbackup will complete successfully.
  
  Work around:
  None
  
  Problem trigger:
  This problem could occur by mmbackup without --backup-migrated
  option when some of files are migrated.
  
  Symptom: 
  Component Level Outage
  
  Platforms affected:
  All platforms that support mmbackup.
  
  Functional Area affected:
  mmbackup
  
  Customer Impact:
  High Importance
  

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

  SPEC SCALE STD

• Fixed component ID

  5737F33AP

Applicable component levels