Resolving The Problem

Two files are created on the Tivoli Storage Manager server during a Data Protection for SQL backup: Data and Meta data. The DP for SQL GUI/CommandLine uses the SQL Meta data to display information about the object and what can be restored. The Data part of the object is the actual data from the SQL database.

These 2 objects are placed in different filespaces on the Tivoli Storage Manager Server and can be stored in different mgmtclass destinations. It is necessary to ensure that both objects are available for a restore. If only one part exists, a restore is not possible.
Therefore, when configuring the management class retention policy on the Tivoli Storage Manager Server, it is important that the DP for SQL Meta Data and DB data should be configured to the exact same parameters. Note that the Management Class that is used for storing the Meta Data and DB data can have different destinations, but it is critical that the retention be the same amount of time for both objects.
Example:

SQLMeta Management Class:

SQLMETA Copy Group:                
                 Name: STANDARD        
               Number: 1                
            Frequency: 0                
      Ver Data Exists: 10000            
     Ver Data Deleted: 31              
    Retain Extra Vers: 31              
     Retain Only Vers: 31              
          Copy Serial: Shared Static    
            Copy Mode: Modified        
          Destination: SQLMETA          

SQLData Management Class:

SQLDATA Copy Group:            
                 Name: STANDARD        
               Number: 1                
            Frequency: 0                
      Ver Data Exists: 10000            
     Ver Data Deleted: 31              
    Retain Extra Vers: 31              
     Retain Only Vers: 31              
          Copy Serial: Shared Static    
            Copy Mode: Modified        
          Destination: SQLDATA

During a DP SQL backup, there are 2 parts for the object that are saved on the Tivoli Storage Manager Server. Meta and Data. There is a known restriction that you cannot change the management class to separately rebind the meta and the data to different management classes. If this is the very first backup, such that no objects exist on the Tivoli Storage Manager server, then the objects can be placed in the different mgmtclasses. However, after there is data and meta objects already saved on the Tivoli Storage Manager server, it is not possible to rebind these separately. The work around for this would be to create a new node for the DP backups so that no prior backups exist. Or, alternatively to rename the existing filespaces so that the next backup (with the different include statements) are seen a the first backup.

Examples of some include statements are

include ?\...\*\...\diff*? SQLDATA
include ?\...\*\...\full*? SQLDATA
include ?\...\meta\...\diff? SQLMETA
include ?\...\meta\...\full? SQLMETA