Design Item
| Considerations
|
Session control
|
Understand and follow these conditions of session control:
- The node name should be unique for an application.
- The owner name should be consistent across a backup and restore
procedure.
- The passwordaccess option affects the use of the TCA child
process (UNIX and OS/400 only), node name, session owner name, and password
management.
- Sessions for data movement should end as soon as the task completes so
that devices on the server are freed for use by other sessions.
- To permit LAN-free data transfer, use the dsmSetUp function
call with the multithread flag set to on.
|
Object naming convention
| When naming objects, consider the following:
- A filespace is a grouping category for the server. Limit the number
of unique filespaces to help performance because several filespace queries are
performed.
- The high-level and low-level object names are the specific object
names. If a unique identifier, such as a date stamp, is included in the
name, then backup objects always will be active. They will expire only
when they are intentionally marked inactive by the dsmDeleteObj
function call.
- Consider how you want the application to restore objects. This will
determine how to format the name for easy queries. If you plan to use a
partial object restore (POR), you cannot use compression. To suppress
compression, use dsmSendObj objAttr objCompressed=bTrue.
|
Object handling
| Do not store objectID values to use for future restores. They are
not guaranteed to be persistent during the life of the object.
|
Management class
| Consider how much control the application wants over the management class
that is associated with its objects. You can define Include statements,
or you can specify a name on the dsmSendObj function call.
|
Object size
| Tivoli Storage Manager needs to know a size estimate for each
object. Consider how your application will do this.
|