Chapter 6. Reconfiguring OpenVault
Prev |  | Next

## Chapter 6. Reconfiguring OpenVault

This chapter describes OpenVault methods for reconfiguration and performance tuning. The sections in this chapter include:

- Importing media into different cartridge groups

- Adding (configuring) or deleting (deconfiguring) drives

- Changing the drive group of a drive

- Changing the name of a library

- Adding remote drives, libraries, and applications at a later time

- Establishing OpenVault security after setup with “no security”

- Changing the OpenVault password for applications, libraries, and drives

## Importing Media Into Cartridge Groups

To import media into different cartridge groups, use the `ov_import` command, perhaps automated with input scripts, to import cartridges into cartridge groups specified by the `-g` option. For example, to import four tapes into the DMF cartridge group, and two other tapes into the NetWorker cartridge group, run these commands:

    # ov_import -g dmf -b DLT7000
    test001 DLT7000 vol1 dmf
    test002 DLT7000 vol2 dmf
    test003 DLT7000 vol3 dmf
    test004 DLT7000 vol4 dmf
    Ctrl+D
    # ov_import -g networker -b DLT7000
    test0A DLT7000 volA networker
    test0B DLT7000 volB networker
    Ctrl+D

For more information, see “Simplified Entry of Media Information” in Chapter 3.

## Adding or Deleting Drives

When you add a drive to your system, OpenVault must recognize the drive in order to put it under management. Use the `ov_drive` command with the `-c` option to create an OpenVault record of (and DCP for) the drive. For example, to create drive1 in the xfsdump drive group, enter this command:

    # ov_drive -c drive1 xfsdump false

The `ov_drive` command takes three arguments after `-c`, specifying the drive's name, its drive group, and administrative disabling. The third flag controls whether the drive is temporarily disabled (`temp`), permanently disabled (`perm`), or not disabled (`false`).

To remove a drive from OpenVault management, use the `ov_drive` command with the `-d` (delete) option. For example, to delete drive1, enter this command:

    # ov_drive -d drive1

## Changing the Drive Group of a Drive

To change the drive group of a drive, you must first delete that drive (and its DCP), then create it anew in a different drive group.

To remove a drive from OpenVault management, use the `ov_drive` command with the `-d` (delete) option. For example, to delete drive7, enter this command:

    # ov_drive -d drive7

If the new drive group does not exist, create it with the `ov_drivegroup` command. If that drive group already exists, skip the following step. It is likely that you should associate an application (DMF) with the drive group at this time:

    # ov_drivegroup -c dmf -A DMF

To return the drive to OpenVault management, use the `ov_drive` command with the `-c` (create) option. For example, to create drive7 in drive group DMF, not administratively disabled (`false`) until deleted, enter this command:

    # ov_drive -c drive7 dmf false

## Changing the Name of a Library

To change the name of a library, you must first delete that library (and its associated LCP), then create it anew with a different name. Before changing the name of a library, be sure to stop and restart the OpenVault server to avoid causing confusion:

    # /usr/OpenVault/stop
    # /usr/OpenVault/start

To remove a library from OpenVault management, use the `ov_library` command with `-d` (delete) option. For example, to delete lib2, enter this command:

    # ov_library -d lib2

To return the library to OpenVault management, use the `ov_library` command with `-c` (create) option. For example, to rename this library tapebot, enter this command:

    # ov_library -c tapebot false

The `ov_library` command takes two arguments after `-c`, specifying the library's name, and administrative disabling. The second argument controls whether the drive is temporarily disabled (`temp`), permanently disabled (`perm`), or not disabled (`false`).

## Adding Remote OpenVault Components

To add remote OpenVault components, inform the server about them, then run the `setup` script on the remote client, as documented in Chapter 2, “Installing OpenVault”.

## Establishing OpenVault Security

When you initially configured OpenVault, you probably followed instructions in the documentation and created an installation without security. This implies that the `admin/keys` file, the `dcp/*/config` and `lcp/*/config` files, and the `var/core_keys` file, specify “none” as the security key.

| Note: Perhaps this is obvious, but passwords for specific applications in `admin/keys`, for DCPs in `dcp/*/config`, or for LCPs in `lcp/*/config`, must be the same as the password given in the `var/core_keys` file for that component.

To establish security, become superuser and edit these files, substituting the password of your choice for the word “none” on lines reading key:

    # cd /usr/OpenVault
    # vi admin/keys dcp/*/config lcp/*/config var/core_keys
    ~
    /none

## Changing OpenVault Passwords

OpenVault authorization is aided by passwords specified in the `admin/keys` file, the `dcp/*/config` and `lcp/*/config` files, and `var/core_keys`. These passwords can all be the same, or they can be different from one component to the next. To change passwords, become superuser and edit these files, substituting the password of your choice for old password, either globally, or component by component:

    # cd /usr/OpenVault
    # vi admin/keys dcp/*/config lcp/*/config var/core_keys
    ~
    /key:

## Reconfiguring Server Operation

The `/usr/OpenVault/mlm/config` file contains crucial OpenVault operational parameters, expected to remain fairly static, as shown in Table 6-1. Modify them with utmost care.

Table 6-1. OpenVault Server Parameters

Parameter | What It Controls
--- | ---
`PORTNUM` | TCP/IP port number on which OpenVault listens for connections
`SEMAKEY` | Semaphore key that OpenVault uses for communication between components
`MAXSTARTS` | Maximum number of connections before OpenVault rejects new ones
`BOOTGRACE` | After reboot, number of seconds OpenVault waits before ejecting drives
`TASKRETRY` | Number of seconds OpenVault waits before reevaluating blocked mounts
`MPRETRY` | Number of seconds OpenVault waits before retrying a failed mount

Prev | Table of Contents | Next
Chapter 5. Operating OpenVault |  | Chapter 7. Tertiary Storage Management