Example: Setting up server storage

All the data in four primary storage pools is backed up to one copy storage pool. Active versions of data are stored in an active-data pool.

About this task

Figure 1 shows one way to set up server storage. In this example, the storage that is defined for the server includes:

• Three disk storage pools, which are primary storage pools: ARCHIVE, BACKUP, and HSM
• One primary storage pool that consists of tape cartridges
• One copy storage pool that consists of tape cartridges
• One active-data pool that consists of FILE volumes for fast client restore

Policies that are defined in management classes direct the server to store files from clients in the ARCHIVE, BACKUP, or HSM disk storage pools. An extra policy specifies the following:

• A select group of client nodes that requires fast restore of active backup data
• The active-data pool as the destination for the active-data belonging to these nodes
• The ARCHIVE, BACKUP, or HSM disk storage pools as destinations for archive, backup (active and inactive versions), and space-managed data

For each of the three disk storage pools, the tape primary storage pool is next in the hierarchy. As the disk storage pools fill, the server migrates files to tape to make room for new files. Large files can go directly to tape. For more information about setting up a storage hierarchy, see Storage pool hierarchies.

For more information about backing up primary storage pools, see Backing up primary storage pools.

Figure 1. Example of server storage

To set up this server storage hierarchy, do the following:

1. Define the three disk storage pools, or use the three default storage pools that are defined when you install the server. Add volumes to the disk storage pools if you did not already do so.
   For more information, see

   • Configuring random access volumes on disk devices
   • Configuring random access volumes on disk devices
2. Define policies that direct the server to initially store files from clients in the disk storage pools. To do this, you define or change management classes and copy groups so that they point to the storage pools as destinations. Then, activate the changed policy. See Changing policy for details.

   Define another policy that specifies the active-data pool that you create as the destination for active data.

3. Assign nodes to the domains. Nodes whose active data you want to restore quickly must be assigned to the domain that specifies the active-data pool.
4. Attach one or more tape devices, or a tape library, to your server system.

   To enable the server to use the device, you must enter a series of the following commands:

   
   • DEFINE LIBRARY
   • DEFINE DRIVE
   • DEFINE PATH
   • DEFINE DEVCLASS
   • DEFINE STGPOOL
   For more information, see:

   • Defining storage pools
   • Configuring storage devices
   • Configuring storage devices
5. Update the disk storage pools so that they point to the tape storage pool as the next storage pool in the hierarchy. See Example: Updating storage pools.
6. Define a copy storage pool and an active-data pool. The copy storage pool can use the same tape device or a different tape device as the primary tape storage pool. The active-data pool uses sequential-access disk storage (a FILE-type device class) for fast client restores. See Defining copy storage pools and active-data pools.
7. Set up administrative schedules or a script to back up the disk storage pools and the tape storage pool to the copy storage pool. Use the same or different schedules or scripts to copy active data to the active-data pool. Send the copy storage pool volumes off-site for safekeeping. See Backing up primary storage pools.