IC90999: FROMDATE, FROMTIME AND FILEDATA OPTIONS FOR "EXPORT NODE" COMMAND MAY NOT WORK AS EXPECTED FOR VM DATA.

APAR status

• Closed as documentation error.

Error description

• When exporting node, which contains VM data, with FROMDATE,
  FROMTIME option,
  the VM data which had been backed up before the date/time will
  also be exported.
  
  Meanwhile, when using "FILEDATA" options for the node which
  contains VM data,
  the data which does not belongs to target objects may also be
  exported.
  
  These are current limitations and should be notified in the
  manual description.
  
  For example, current manual descriptions are as follows:
  Tivoli Storage Manager for Windows Version 6.3.3 Administrator's
  Reference
  Chapter 1. Administering the server from the command-line
  interface
  P.480 EXPORT NODE-to sequential media
  -------------------------
  FROMDate
  Specifies the earliest date for which files to be exported were
  stored on the
  server. Files that were stored on the server earlier than the
  specified date are
  not exported. This parameter only applies to client file data.
  This parameter
  does not affect other information that might be exported, for
  example, policy.
  Tivoli Storage Manager ignores the FROMDATE parameter when the
  FILEDATA parameter is set to NONE.
  
  Directory processing:
  The FROMDATE parameter does not apply to
  directories. All directories in a file space are processed even
  if the directories
  were not backed up in the specified date range.
  -------------------------
  
  P.478 EXPORT NODE-to sequential media
  -------------------------
  FILEData
  Specifies the type of files that should be exported for all
  nodes being exported
  to the server. This parameter is optional. The default value is
  NONE
  ...
  
  BACKUPActive
  The server exports only active backup versions. These active
  backup
  versions are the active versions in the Tivoli Storage Manager
  database at
  the time that the EXPORT command is issued
  -------------------------
  
  
  Tivoli Storage Manager Versions Affected: All supported versions
  for all platforms.
  
  
  Customer/L2 Diagnostics (If Applicable)
  For example, even in case when FROMDATE option is used with
  02/19/2013 on source server,
  VM data which had been backed up on 02/18/2013 is also exported
  to target server.
  
  (Example of command which is used on source server)
  ---------------
  server> EXPORT NODE sample_node FROMDATE=02/19/2013
  TOSERVER=target_server
  ---------------
  
  (Example of result for "query vm" command on target server)
  ---------------
  tsm> query vm * -ina=yes
    #       Backup Date       Mgmt Class      Type        A/I
  Virtual Machine
  ---       -----------       ----------           ----   ---
  ---------------
    1   2013-02-18 HH:mm:SS   SAMPLE_MGMT     (VSTOR)FULL  I
  sample
    2   2013-02-18 HH:mm:SS   SAMPLE_MGMT     (VSTOR)FULL  I
  sample
    3   2013-02-20 HH:mm:SS   SAMPLE_MGMT     (VSTOR)FULL  A
  sample
  ---------------
  
  Initial Impact: Low
  
  
  Additional Keywords: zz55 zz61 zz62 zz63 vm filedata
  backupactive fromdate
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All Tivoli Storage Manager server users.     *
  ****************************************************************
  * PROBLEM DESCRIPTION: See error description.                  *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The documentation for the EXPORT NODE command will be updated
  with the following note in the FROMDATE option:
  
  Note: If you have group data on the node that you are
  exporting, for example virtual machine data or system state
  backup data, data that was backed up before the designated
  FROMDATE and FROMTIME can also be exported. This export is
  a result of incremental backup processing for the data.
  The incremental backup processing can cause extra files that
  do not meet the filtering criteria to be exported, so that
  there is a consistent image for the backup data.
  
  The documentation for the EXPORT NODE command will be updated
  with the following note in the FROMTIME option:
  
  Note: If you have group data on the node that you are
  exporting, for example virtual machine data or system state
  backup data, data that was backed up before the designated
  FROMDATE and FROMTIME can also be exported. This export is
  a result of incremental backup processing for the data.
  The incremental backup processing can cause extra files that
  do not meet the filtering criteria to be exported, so that
  there is a consistent image for the backup data.
  
  The documentation for the EXPORT NODE command will be updated
  with the following note in the FILEDATA option:
  
  Note: If you have group data, for example virtual machine
  data or system state backup data, on the node that you
  are exporting and you are using the FILEDATA option, data
  that is not a part of the target objects might be exported.
  For example, if FILEDATA=BACKUPACTIVE when the FROMDATE
  or TODATE parameters are specified, it is possible to
  include inactive backup data. The incremental backup
  processing for the data can cause extra files that do
  not meet the filtering criteria to be exported,
  so that there is a consistent image for the backup data.
  

Problem conclusion

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