IT26511: INCREMENTAL INCORRECTLY ADDS NON-AUTOMOUNTED BIND MOUNTS TO DOMAIN ALL-LOCAL

APAR status

• Closed as program error.

Error description

• Linux RHEL7 made change to bind causing command "mount " to
  present  bind directory the same as the local mount point.
  During backup with "domain all-local" setting,  the bind
  directory is backed up as a separated file space, causing data
  under the bind directory to be backed up twice.
  
  
  L2/Customer diagnostics:
  
  1: cat fstab:
  ..
  /dev/export/export /export ext4 defaults 2 2
  /export/data /data none bind
  ..
  
  Note:
  /export is ext4
  /data is a bind to directory /export/data
  .
  2: mount command shows both as ext4:
  ...
  /dev/mapper/export-export on /export type ext4
  (rw,relatime,seclabel,stripe=640,data=ordered)
  /dev/mapper/export-export on /data type ext4
  (rw,relatime,seclabel,stripe=640,data=ordered)
  ..
  3: during incremental backup with domain all-local: both /export
  and /data are processed:
  
  Incremental backup of volume '/'
  
  Incremental backup of volume '/boot'
  
  Incremental backup of volume '/var'
  
  Incremental backup of volume '/export'
  
  Incremental backup of volume '/data'
  ,,..
  
  This cause data under /export/data to be backed up twice but
  stored under two separated filespaces:   /export and /data .
  Local fix:
  

Local fix

• 1: Use domain all-local -/bind_mount_name to exclude the bind
  mounts
  or
  2:Use the operating system automounter instead of a direct bind
  mount to manage the directory, so that the automounted bind
  directory is excluded from "domain all-local" and becomes a part
   of "domain all-auto-lofs" instead.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * IBM Spectrum Protect backup-archive client versions 7.1 and  *
  * 8.1 on all Linux platforms.                                  *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * See ERROR DESCRIPTION.                                       *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Apply fixing level when available. This problem is projected *
  * to be fixed in level 8.1.7 and in the next release of the    *
  * client documentation. Note that this is subject to change at *
  * the discretion of IBM. In the meantime, documentation        *
  * updates for IBM Spectrum Protect Backup-Archive Clients      *
  * Installation and User's Guide V8.1.x are at the following    *
  * website:                                                     *
  * - UNIX and Linux:                                            *
  * http://www-01.ibm.com/support/docview.wss?uid=swg27048955    *
  ****************************************************************
  

Problem conclusion

• Upon the fix, a non-automounted bind mount will be backed up
  under DOMAIN=ALL-LOFS provided the appropriate record exists in
  the '/etc/fstab' system configuration file.
  In the backup-archive client publication, in the DOMAIN option
  description, the following note is added:
  "On Linux, you must configure an appropriate /etc/fstab entry to
  include a bind mount into the all-lofs domain."
  

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

• dsmc     dsmagent
  

Fix information

• Fixed component name

  TSM CLIENT

• Fixed component ID

  5698ISMCL

Applicable component levels

• R81L PSY

     UP