What were some of the most common commands and their syntax?

Common commands included `BACKUP`, `ARCHIVE`, `RETRIEVE`, `RESTORE`, and `QUERY`. For example, `BACKUP /path/to/file` would back up a file. Configuration was managed through client options files and server-side configuration.

How did the client and server components communicate?

The product used a client-server architecture. Clients communicated with the ADSM server using a proprietary protocol over TCP/IP. The server managed storage and data movement.

What database or storage mechanisms were used?

ADSM utilized a database, typically DB2, to store metadata about backed-up and archived files. This database was crucial for managing file versions, locations, and other relevant information.

What administrative interfaces were available?

Administrative interfaces included a command-line interface (CLI) and potentially a graphical user interface (GUI) on some platforms. Configuration was primarily done through configuration files and the CLI.

What business value did Tivoli ADSM offer?

Tivoli ADSM provided a centralized backup and archive solution, reducing the risk of data loss and improving data availability. The HSM feature optimized storage costs by automatically moving less frequently accessed data.

How did Tivoli ADSM improve operational efficiency?

By automating the backup and archive processes, ADSM reduced the manual effort required for data protection. This automation improved efficiency and reduced the potential for human error.

How did the HSM feature contribute to storage cost optimization?

The HSM feature helped organizations manage storage costs by automatically moving data to the most appropriate storage tier based on access frequency. This ensured that frequently accessed data was readily available while less frequently accessed data was stored more economically.

What authentication methods were supported?

Authentication methods included user IDs and passwords, which were managed within the ADSM system or integrated with external authentication services. Access control was managed through user groups and permissions.

What access control model was used?

Access control was typically managed using a role-based access control (RBAC) model, where users were assigned to groups, and permissions were granted to those groups. This allowed administrators to manage access efficiently.

What encryption and audit capabilities were available?

Data encryption was available, particularly for data stored on tape. Encryption was used to protect data at rest. Audit logging tracked user activities and system events.

What were the primary methods for administering Tivoli ADSM?

Administration was primarily performed through the command-line interface (CLI). Administrators could manage users, configure storage pools, and monitor system performance using various commands.

How was user management handled?

User management involved creating, modifying, and deleting user accounts. Administrators could assign users to groups and manage their access permissions through the CLI.

What monitoring and logging capabilities were available?

Monitoring capabilities included tracking storage utilization, backup and archive job status, and system performance metrics. Logging provided detailed information about system events and user activities.

Share Your Product Experience

Help the community by sharing your experience with mainframe products. Your insights help others make informed decisions.

Share Your Experience

Tivoli ADSM

Name: Tivoli ADSM
Availability: InStock

IBM Not Supported z/OS z/VM

Archive Automation UNIX and Windows Backup and Restore Files and Datasets

Vendor

IBM

Product Overview

The architecture of Tivoli ADSM comprised several key components. The client software, installed on workstations (MS-DOS, Macintosh, OS/2, AIX), initiated backup and archive operations. The server component, running on the mainframe, managed storage, data movement, and metadata.

Communication between clients and the server used a proprietary protocol over TCP/IP. A database, typically DB2, stored metadata about backed-up and archived files. The HSM feature automatically moved inactive files to lower-cost storage tiers.

The CLI provided administrative control, including user management and configuration. The system supported authentication via user IDs and passwords, with RBAC for access control. The product is no longer supported; therefore, organizations should migrate to a supported solution like IBM Spectrum Protect, which offers a similar architecture with enhanced features.

Frequently Asked Questions

What was the primary function of Tivoli ADSM?

Tivoli ADSM was designed to back up workstation files to mainframe storage. It offered an optional Hierarchical Storage Management (HSM) feature to automatically archive inactive files. The product supported clients including MS-DOS, Macintosh, OS/2, and AIX.

What were the different names used for Tivoli ADSM over time?

Tivoli ADSM was initially released as Workstation Data Save Facility (WDSF) for z/VM. It was later renamed to Data Facility Distributed Storage Manager, then ADSTAR Distributed Storage Manager (ADSM), and finally Tivoli ADSM. The product was renamed to Tivoli Storage Manager in 1999.

Which operating systems were supported by the workstation clients?

Tivoli ADSM supported various workstation clients, including MS-DOS, Macintosh, OS/2, and AIX. These clients allowed users to back up their files from their workstations to the mainframe storage managed by ADSM.

What was the purpose of the Hierarchical Storage Management (HSM) feature?

The Hierarchical Storage Management (HSM) feature automatically archived inactive files to less expensive storage tiers, optimizing storage utilization and cost. This feature was a key component of ADSM's functionality.

Help Improve This Directory

Notice outdated information? Have insights about this product? Help the mainframe community stay informed with accurate, current data.

Report Issue Suggest Product Share Event

Are You a Vendor? Claim Your Listing

Take control of your product listings. Add verified information, showcase updates, and unlock a Claimed Vendor badge across the directory.

Claim Your Listing Now

Share Your Product Experience

Tivoli ADSM

Product Overview

Frequently Asked Questions

What was the primary function of Tivoli ADSM?

What were the different names used for Tivoli ADSM over time?

Which operating systems were supported by the workstation clients?

What was the purpose of the Hierarchical Storage Management (HSM) feature?

What were some of the most common commands and their syntax?

How did the client and server components communicate?

What database or storage mechanisms were used?

What administrative interfaces were available?

What business value did Tivoli ADSM offer?

How did Tivoli ADSM improve operational efficiency?

How did the HSM feature contribute to storage cost optimization?

What authentication methods were supported?

What access control model was used?

What encryption and audit capabilities were available?

What were the primary methods for administering Tivoli ADSM?

How was user management handled?

What monitoring and logging capabilities were available?

Related Products

More from IBM

Access 1

ACF/NCP

ACF/SSP

ACO SolutionPac

Ada/370

ADF II

Similar Products

_beta access monitor

$avers

3770Link

3780Link

ABARS/Assist

ACC

Help Improve This Directory

Are You a Vendor? Claim Your Listing