Quick Start

System-Managed Storage

ADSM includes the following components:

Server

Provides storage management for client workstations and maintains a database of ADSM information.

Server Storage

Contains files that are backed up, archived, and migrated from workstations. Server storage consists of pools of random and sequential access media.

Administrative client

Provides an interface to the ADSM server.

Backup-archive client

Provides backup and archive services to workstations.

Hierarchical storage management (HSM) client

Provides space management services for workstations on some platforms.

Server Storage Migration

To use your storage resources efficiently, you can arrange server storage into a hierarchy. You can then define when data is migrated from faster, more expensive storage pools (disk, for example) to slower, less expensive storage pools (tape, for example). You can also store data on another ADSM system (see ADSM Administrator's Guide for details).

ADSM Policy

ADSM lets users on workstations do the following tasks:

Backup

Copy files to server storage to prevent loss of data. Copies of multiple versions of a file can be stored.

Archiving

Copy files to server storage for long-term storage.

Hierarchical Storage Management

Free storage space by moving data to server storage. The original file is replaced pointer to the location of the original in server storage. This is also called space management or migration .

Policy is defined by administrators in policy objects: policy domains, policy sets, management classes, and backup and archive copy groups.

The following figure shows how ADSM stores client data.

Figure 10. How ADSM Controls Backup, Archive, and Space Management

(1) An ADSM client backs up, archives, or migrates a file. The file is bound to either the default management class or a management class specified in the client's include-exclude list.

(2) If, according to the management class, the file is eligible for backup, archive, or space management, the client sends the file and file information to the server.

(3) The server checks the management class or copy group to determine where in server storage to store the file initially.

If there is not enough space in the initial storage pool, the server examines the next pool in the hierarchy and places the file there if space is available.

(4) The server stores the file in the appropriate storage pool and stores information about the file in the database.

When files in server storage are migrated from one pool to another, the server updates the file information in the database.

Expiration

Files remain in server storage until they expire and expiration processing occurs. A file expires based on criteria set in ADSM policy. For example, backup policy may specify that up to two backup versions of a file can be kept in server storage. If a third backup version of a file is created, the oldest version in server storage expires. Backup policy may also specify that if a file is deleted from a client file system, it expires after 60 days.

During expiration processing, ADSM deletes from the database those files that have expired.