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.

When you add a drive to your system, OpenVault must recognize the drive in order to put it under management. The preferred method to do this is with the ov_admin command, via the Manage DCPs for Locally Attached Drives option. You can use this menu option to create an OpenVault record of (and DCP for) the drive. Alternatively, the ov_drive command provides options to create a drive.

To remove a drive from OpenVault management, use the Manage DCPs for Locally Attached Drives option from the ov_admin command. Alternatively, the ov_drive command provides options to delete a drive.

The preferred method to change the drive group of a drive is with the ov_admin command. The Manage Drive Groups menu selection causes a submenu to display. The item Reassign a drive to Another Drive Group allows you to change the drive group of a drive.

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. The preferred way to do this is with the ov_admin command. The Manage LCPs for Locally Attached Libraries option allows you to delete an LCP. After that step is accomplished, you can use the Manage LCPs for Locally Attached Libraries option again to create the LCP with a new name.

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

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

---

Note: Perhaps this is obvious, but passwords for specific applications in clients/admin/keys, for DCPs in clients/dcp/*/*/config, or for LCPs in clients/lcp/*/*/config, must be the same as the password given in the server/config/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 /var/opt/openvault 
# vi clients/admin/keys clients/dcp/*/*/config clients/lcp/*/*/config\
        server/config/core_keys 
~
/none 

OpenVault authorization is aided by passwords specified in the security files described in “Establishing OpenVault Security”. 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 /var/opt/openvault 
# vi clients/admin/keys clients/dcp/*/*/config lcp/*/*/config \
        server/config/core_keys 
~
/key: 

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