IBM’s TSM (Tivoli Spirit Software) is a popular and widely accepted backup software with a series of enterprise-class IT divisions for near about a span of 15 years. In the early 90s, it was introduced and built mainly on the concepts Mainframe Data-Storage Management.
There are a number of relevant aspects which needs due consideration in context to deployment of a TSM backup environment. Apart from the elemental requirements of backup software such as network bandwidth, recovery requirements and capacity, some other specific requirements are due to the architecture of this particular software. Some of the widely accepted practices in context to implementation items and infrastructure design of TSM are hereby discussed.
Disaster Recovery Manager
Disaster Recovery Manager module of TSM must be configured in accordance to all the ‘instructions’ files properly maintained and documented. When the TSM software ‘prepare’ process runs, then the Disaster Recovery Module produces a file of TSM recovery plan which comprises of all relevant TSM configuration information. It also provides a list of database backup volumes and offsite tapes. Moreover, the Disaster Recovery Module plan file should be sent offsite on a regular basis with database backup and storage pool tapes.
Backup Data Retention and Change Rate
The rate of data changes and the duration of the retention of backup data are two significant factors to be considered for maintaining the Proper Efficiency and Adequacy of Tivoli Storage Manager capacity planning. The data change rate always has an explicit impact on the volume of regular backup data which dictates the network bandwidth and overall performance required for the backup infrastructure. Nonetheless, the backup copies kept or versions and the duration of their retention has an explicit influence on the capacity of the backup data storage (tape, disk or VTL). Retention and versioning can be described based on the business recovery requirements. Thus, the best process is to define the prudent retention settings first and then increase as per the necessity.
Customer Option Sets
The TSM backup software clients can enjoy the advantage of numerous options and settings which reflects the site’s specific backup policies and norms or application of it in specific systems. TSM clients mainly depend on the local options file for basic settings like TSM server’s IP address. Thus, it is good to create such beneficial client options sets on TSM server for a group or system of specific configuration options. In case of a large environment of a wide number of TSM nodes (clients), managing the client option sets in a centralized manner is easier as compared to the numerous individual files being spread across the environment.
Thus, with the help of this potentially equipped and easily manageable TSM Backup software one can cluster the files in ‘packages’ which will be bearing a descriptor and time stamp thereby enabling to restore the data for a specified and longer period of time.