Administrator's Guide


Using Virtual Volumes

ADSM lets a server (source server) store the results of database backups, export operations, and storage pool operations on another server (target server). The data is stored as virtual volumes, which appear to be sequential media volumes on the source server but which are actually stored as archive files on a target server. The source server is a client of the target server, and the data for the source server is managed only by the source server. In other words, the source server controls the expiration and deletion of the files that comprise the virtual volumes on the target server.

At the target server, the virtual volumes from the source server are seen as archive data. The source server is registered as a client node (of TYPE=SERVER) at the target server and is assigned to a policy domain. The archive copy group of the default management class of that domain specifies the storage pool for the data from the source server.
Note:If the default management class does not include an archive copy group, data cannot be stored on the target server.

Using virtual volumes can benefit you in the following ways:

Be aware of the following when you use virtual volumes:

Note:When you issue a DEFINE SERVER command, the source server sends a verification code to the target server. When the source server begins a session with the target server, it also sends the verification code. If the code matches what was previously stored on the target, the session is opened in read/write mode. If the verification code is lost at the source server (for example, after a database restore), the code can be reset by issuing an UPDATE SERVER command with the FORCESYNC=YES parameter.


[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]