IC96596: PARTIAL INCREMENTAL BACKUP DOES NOT EXPIRE DELETED FILES

APAR status

• Closed as documentation error.

Error description

• While executing an incremental backup if the source path points
  to a subset
  of files via wild card,  then the incremental backup will not
  expire the deleted files from that sub-directory
  
  For example:
  dsmc incremental c:\dir1\*.txt -subdir=yes
  
  This does NOT expire deleted files under the c:\dir1 directory
  branch.
  
  In order to properly expire files from this directory, specify
  the whole directory and not specific group of files
  as follows:
  
  dsmc incremental c:\dir1\ -subdir=yes
  
  Additional Info:
  Depending on your storage management policies, the server might
  keep more than one version of your files in storage.
  The most recently backed up files are active backup versions.
  Older copies of your backed up files are inactive versions.
  However, if you delete a file from your workstation, the next
  full incremental backup causes the active backup version of the
  file to become inactive.
  If you need to restore a file you have deleted, and if a full
  incremental backup has been run since you deleted the file,
  then you need to restore an inactive version of the file
  (assuming that a version still exists on the server).
  The number of inactive versions maintained by the server and how
  long they are retained is governed by the management policies
  defined by your server administrator.
  The purpose of the active versions is to represent which files
  existed on your file system at the time of the backup
  
  
  Tivoli Storage Manager Versions Affected:
  TSM 55 on Windows 2003
  
  
  Initial Impact: Low
  
  
  Additional Keywords:
  incr, incremental, partial incremental, backup, expire
  

Local fix

• Specify the whole directory and not specific group of files as
  follows:
  dsmc incremental c:\dir1\ -subdir=yes
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: IBM Tivoli Storage Manager for               *
  *                 UNIX and Linux                               *
  *                 Backup-Archive Clients                       *
  *                 Installation and User's Guide                *
  *                                                              *
  *                 IBM Tivoli Storage Manager for               *
  *                 Windows                                      *
  *                 Backup-Archive Clients                       *
  *                 Installation and User's Guide                *
  ****************************************************************
  * PROBLEM DESCRIPTION: The documentation incorrectly           *
  *                      describes which files are rebound or    *
  *                      expired mduring an incremental backup.  *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  *
  

Problem conclusion

• Backing up your data >
  Incremental, selective, or incremental-by-date backups >
  Full and partial incremental backup
  
  The following text is incomplete:
  Rebind backup versions if management class assignments
  change. Only objects that have active backup versions are
  bound again. Objects for which only inactive backup
  versions exist are not bound again.
  
  The following text text is added:
  
  During a partial incremental backup operation, objects are
  rebound or expired as follows:
  If the file specification matches all files in a path:
   Rebinding and expiration occurs for all eligible backup
   versions that match the file specification. This is the case
   for an incremental command like
      dsmc incr c:\mydir\* -subdir=yes
  If the file specification does not match all files in a path:
   Rebinding and expiration occurs for all eligible backup
   versions that match the file specification.
   However, eligible backup versions are not expired or rebound
   if they were in a directory that no longer exists on the
   client file system.
   Consider the example command:
      dsmc incr c:\mydir\*.txt -subdir=yes.
   Rebinding and expiration occurs only for files that match the
   *.txt specification whose directories still exist on the
   client file system.
  

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

Applicable component levels