The TSM Client of the same release is supported on NetWare, macOS, AIX, HP-UX, Linux, z/OS, Solaris, and Windows 32/64-bit.
The 5.5 release of the TSM Server is supported on AIX, HP-UX, Linux, Solaris, Windows Server, and z/OS. Duplicate copies (Backupsets or Copy Storage Pools) of any subset of data may be created on sequential media for redundancy or off-site management. Additionally, emulated tape from a Virtual Tape Library or EMC Centera WORM archival device is supported. This database may generally be queried via an emulated SQL-98 compliant interface, or through undocumented SHOW, CREATE or DELETE commands.Īctual user data is managed via a cascading hierarchy of storage media (Primary Storage Pools) presented as raw devices (UNIX), filesystem containers (Windows and Linux), streaming tape or optical media. Shallow directory structures use less TSM DB space than deeper paths. On average, 20GB of space is consumed for every 25 million objects. v5.5 DB pages are always 4KB, and partitions every 4MB. TSM maintains a relational database (limit 534GB through TSM v5.5, 4TB with TSM v6.3.3+) and recovery log (aka transaction log, limit 13 GB through TSM v5.5, 128GB with TSM v6.1+) for logging, configuration, statistical information, and object metadata. Starting with TSM 6.1, released in May 2009, TSM uses a Db2 instance as its database (thus eliminating the architectural limitations of the previous TSM database). The TSM database (through release 5.5) was a bespoke B+ tree database although the TSM database uses many of the same underlying technologies as IBM's Db2, has a SQL engine (for read-only use), and supports access through ODBC, the database has an architectural limit of approximately 530 GB, and 13 GB of log space.
Photo of an IBM Technical Award from 1991 given to the original Workstation Data Save Facility (WDSF) team at the IBM Almaden Research Center in San Jose, CA, USA.
0 kommentar(er)
