
Guide to Installing DataMgr
January, 2000 Document Number 600922

AMASS, EMASS, DataMgr, FileServ, and VolServ are either trademarks or registered trademarks of ADIC, Advanced Digital Information Corporation. DAS is a trademark of Grau, an ADIC subsidiary. All other product names and identifications are trademarks or registered trademarks of their respective manufacturers.
Copyright © 1996-2000 by ADIC. All rights reserved. This document is the property of ADIC. No part of this document may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any language or computer language in any form or by any means, electronic, mechanical, magnetic, optical, chemical, manual, or otherwise, without the express written permission of:
ADIC 10949 East Peakview Ave. Englewood, CO 80111 USA Phone: 303-792-9700 FAX: 303-792-2465
Use, duplication, or disclosure of either the software or documentation is subject to restrictions set forth by the U.S. Government in FAR 52.227-19(c)(2) and subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 52.227- 7013 and/or in similar or following clauses in the FAR, DoD, or NASA FAR Supplement.
ADIC Technical Assistance Center:
Although the material contained herein has been carefully reviewed, ADIC does not warrant it to be free of errors or omissions. We reserve the right to make corrections, updates, revisions, or changes to the information contained herein.

ADIC includes this Form in an effort to provide the best possible documentation to our customers. Please take a few moments to mail or FAX your response to:
ADIC Software Documentation 10949 East Peakview Ave. Englewood, CO 80111 FAX: 303-792-2465 E-mail: swpubs@adic.com
Is there anything you especially like or dislike about the organization, presentation,
or writing in this manual?


Purpose of This Book P-3 Who Should Read This Book P-3 How This Book is Organized P-4 Conventions P-5 Books P-6
Online Documentation P-6 Related Publications P-7 Contact Publications Department P-7 Secured Web Site P-7
Capacity-based License 1-3
Feature Licenses 1-3
Permanent Authorization Strings 1-3 Temporary Product Key 1-5 Changing Authorization String 1-5 BFS Issues License to Clients 1-7
Registration File Monitors License 1-7
How to Refresh Registration File 1-8 Requirements 1-9
File Pathname Limit 1-9 File System Size & Name 1-9 Large Files 1-10 Shared Libraries 1-10

Disk Space 1-13 Create Installation Directory 1-14 Determine Location for Components 1-14
Summary of Elements 1-15 Create Directories 1-16
Complete Table 1-17 Size Databases 1-18
Size BFS Database 1-18 Size Managed File System Database 1-20 Edit Paths 1-21
man Pages 1-21 Utilities 1-21 GUIs 1-22 Edit Temporary Storage Space 1-23 System Mount Table 1-24
Extract Files From Local CD 2-3 Extract Files From Remote CD 2-4 Install DataMgr 2-6 Startup File 2-12 Startup & Shutdown 2-13
Establish Access for DMFS Clients 3-3 Schedule cron Jobs 3-4
ii Contents

DMFS cron job 3-4 BFS cron job 3-5 Back Up Databases 3-6
Assign a Backup Volume 3-7 Save SSD Logs 3-9
Edit cron File 3-10 Logging 3-12
Logging Hierarchy 3-12 Format of Messages 3-13 Priority Levels 3-13 Modify Logging Characteristics 3-14 Modifiable Variables 3-15 Start Administra- tive GUI 3-19
Start Client GUI 3-19 Change Colors and Fonts 3-20
Deinstall DataMgr 4-3 Reinstall DataMgr 4-4 Remove Load Directory 4-6
Contents iii

iv Contents

Purpose of This Book P-3 Who Should Read This Book P-3 How This Book is Organized P-4 Conventions P-5 Books P-6
Online Documentation P-6 Related Publications P-7 Contact Publications Department P-7 Secured Web Site P-7
Preface

P-2 Preface

This book describes how to install and configure DataMgr on both the server and on clients’ machines.
This book is written for the system administrators who has been assigned the task of installing DataMgr.
The table below lists DataMgr books that a system administrator should read:
Preface · Preface P-3

This book contains the following chapters:
Chapter 1: Prerequisites — Defines system requirements for DataMgr.
Chapter 2: Install DataMgr — Instructions for installing DataMgr as well as special startup & shutdown procedures.
P-4 Preface

The word “library” is a generic way to reference a storage device.
If using HP SunSpot libraries, install patch 1234.
Screen text, file names, program names, and commands are in Courier font.
The root prompt is shown as a number symbol.
What you should type in is shown in Courier bold font.
Site-specific variables are in a Times italics font.
# dmfscntl -p /mfspath
A backward slash ( \ ) denotes the input is continued onto the next line; the printed page is just not wide enough to accommodate the line.
# rsh nodename -n dd if=/dev\
/tapedevicename/bs=20b | tar\ xvfb - 20
Type the entire command without the backward slashes.
Pressing after each command is assumed.
A menu name with an arrow refers to a sequence of menus or options.
Main Menu -—> Edit —>Add-—> Select Policy

Books The books described below are part of the technical documentation set and are shipped on CD along with the DataMgr software:
System Administrator’s Guide to Installing DataMgr Install and configure DataMgr on a UNIX server and on clients’ workstations.
DataMgr Overview An introduction to DataMgr, an hierarchical storage management (HSM) application. Contains a glossary.
System Administrator’s Guide to Using DataMgr Define managed file system criteria with either commands or GUI. Describes DataMgr commands and utilities. Describe backup and restore issues. Provides troubleshooting tools.
Client’s Guide to Using DataMgr View migration criteria; start user-initiated migration and reload; and manage file quota system.
quick reference card Summarizes commands and utilities.
The software CD contains DataMgr book files and Adobe® Acrobat® Reader. The Reader allows you to view and navigate the online documentation files yet preserves the page design and graphics from the printed books.
P-6 Preface

The publications described in the table below are created and distributed on an as-needed basis:
“Release Notes” For each version of DataMgr, the “Release Notes” contain:
“Product Alerts” Informs customers of technical problems and solutions.
“Product Bulletins” Conveys technical information — not problems — to customers.
To make corrections or to comment on DataMgr publications, please contact Software Technical Publications at our email address: swpubs@adic.com.
To receive access to the secured site on our home page containing technical product information (Release Notes, Product Alerts, Product Bulletins, FAQs), send e-mail to swpubs@adic.com and include the items below. In return, we will send you instructions and a password.
Preface · Related Publications Description · Preface P-7

P-8 Preface

Preface · Preface P-9

P-10 Preface

Capacity-based License 1-3 BFS Issues License to Clients 1-7 Requirements 1-9 Create Installation Directory 1-14 Determine Location for Components 1-14 Size Databases 1-18 Edit Paths 1-21 Edit Temporary Storage Space 1-23 System Mount Table 1-24
Prerequisites

Install AMASS before installing DataMgr.
Verify that you have the necessary system requirements.
Install DataMgr. 2
Setup tasks:
Post installation tasks:
Task Refer To · Chapter · 1-2 Prerequisites

ADIC issues a DataMgr license based on the amount of disk space each client machine mounts for management. Capacity-based license levels are described below:
The license is entered when installing the BFS component. The BFS provides the licenses needed by the individual DMFS clients. (For a description of DataMgr components, refer to “Components” on page 1-4 in DataMgr Overview.)
A separate authorization string is needed for the optional features below. For a description of these features, refer to the Storage Policies chapter in DataMgr Overview.
During installation you are asked to enter either:
Authorization strings have the following format: xxxx-xxxx-xxxx-xxxx-xxx. You can enter the authorization string in one of the following ways:
Prerequisites · Permanent Authorization Strings · Prerequisites 1-3

If your Software Certificate does not contain this string, call ADIC at (303) 792-9700 or FAX (303) 792-2465 or email techsup@adic.com and they will issue you an authorization string after you provide them with the required information. How to find this required information is described below:
Serial Number Look at the DataMgr CD and write down the serial number. Enter your Serial Number here
Host ID Determine the host ID with the appropriate command in the table below. Enter your Host ID here
License Information Write down the licenses for each BFS your company purchased.

The generic 30-day temporary product key is: U3QEYUCJ.
The temporary product key does not enable File Replication, Multi-tier, or File Import.
At the end of 30 days, if a permanent Authorization String has not been entered, DataMgr expires, but migrated data will not be lost. If you enter a permanent license after the expiration date, file migration and reload is again enabled through the BFS.
Change the authorization string if any of the following conditions apply:
# cd /etc/bfs/usr/utils # ./bfsmaint -i

Use the bfsmaint -i utility option only when DataMgr is running.
When prompted, enter a new authorization string. Your responses are shown in bold.
License information for host zanzibar:
Temporary license expires in 1 month Okay to overwrite license file? [n] y
Enter your Authorization string for a permanent license:
License information for host zanzibar: Number of level 1: 10 Number of level 2: 1 Number of level 3: 0
License file written · 1-6 Prerequisites

The BFS issues each DMFS client the appropriate license level after receiving information on the amount of disk storage it manages on the client machine. If a license for the appropriate level is not available, the BFS issues the client a license for the next higher level. If all licenses are in use, the request is denied. (For a description of DataMgr components, refer to “Components” on page 1-4 in DataMgr Overview.)
For example, if a client has 3GB of space for management, it needs a Level 1 license. If a Level 1 licenses is not available, the BFS will try to issue a Level 2 license, and if there are none available, it will try to issue a Level 3 license.
If a client attempts to use either file replication or multi-tier migration, but the BFS does not have the appropriate feature license, the operation will fail.
On the BFS, DataMgr maintains a registration file located in /etc/bfs/registered. This file (an example is shown below) monitors all levels of licenses that are authorized and in use at any given time.
Serial number: DM-00539 License installed on Tue Jan 5 17:46:38 1999 Allowed license levels: Number of level 1: 25 Number of level 2: 3 Number of level 3: 1
Current license levels in use: Level 1 checked out: 8 Level 2 checked out: 1 Level 3 checked out: 1
Prerequisites · Prerequisites 1-7

How to Refresh Registration File
If a client goes down while files are being migrated or reloaded, the /etc/bfs/registered file can become out-of-sync with the current client configurations.
To refresh the registered file, refer to “Refresh Registration File” on page 6-39 in System Administrator’s Guide to Using DataMgr.
1-8 Prerequisites

Requirements Make sure you read the DataMgr “Release Notes” to obtain the following information:
Install and start AMASS before installing DataMgr.
DataMgr supports a file pathname limit of 1023 characters for the DataMgr root directory in AMASS. For example, if client files are going under /archive/FMSclients/eureka on AMASS, then the length of this string (26 characters) must be subtracted from 1023 (1023-26=997). Consequently, succeeding file pathnames can be a total of 997 characters in length.
File system size is important. ADIC recommends that your file system not exceed 1 million files. As the number of files approaches 1 million, the system slows considerably. The smaller the file system, the faster most utilities and commands will complete.
The size of a file system name can be a maximum of 24 characters in length.
Prerequisites · Prerequisites 1-9

Large Files If a DMFS client requires DataMgr to manage files larger than 2GB, the BFS must support large files. Large file support is provided on the following operating system:
The tables below list required shared libraries for successful operation of both the Client GUI and the Administrative GUI.
If, for example, your system does not have a libXaw.so.5, but it does have a libXaw.so.4 or libXaw.so, create a symbolic link to the actual library (highest number) with the required library. An example follows:
# cd /usr/openwin/lib; ln -s libXaw.so.4 libXaw.so.5
(actual library) (required library)
X11.base.lib
/usr/lib/libX11.a
X11.base.rte
/usr/lib/libXaw.a
X11.samples.lib.Core
/usr/lib/libXm.a
/usr/lib/libXext.a
Fileset Libraries Included · 1-10 Prerequisites

X11R5-SHLIBS /usr/lib/Motif1.2/libXm.sl
/usr/lib/X115R/libX11.sl
/usr/lib/X11R5/libXt.sl
x_eoe.sw.eoe
/usr/lib/libXaw.so
motif_eoe.sw.eoe
/usr/lib/libXmu.so
/usr/lib/libXt.so
/usr/lib/libX11.so
/usr/lib/libXext.so

X Windows Libraries Included
SUNWmfrun /usr/dt/lib/libXaw.so
/usr/openwin/lib/libXaw.so
/usr/openwin/lib/libXmu.so
/usr/openwin/lib/libXt.so
/usr/openwin/lib/libX11.so
/usr/openwin/lib/libXext.so
Add both /usr/dt/lib and /usr/openwin/lib to the LD_LIBRARY_PATH environment variable.
Solaris · Open Windows · 1-12 Prerequisites

Disk Space The table below shows the amount of disk space required by DataMgr:
System DMFS BFS SLD SSD /etc/dm*
AIX 32MB 14MB 140KB 4MB 8MB BFS Database and Managed File System Database HP-UX 30MB 13MB 66KB 10MB 5MB
Solaris 31MB 10MB 91KB 4MB 5MB
* The /etc/dm/log and /etc/dm/raima/log contain log files so this initial size will grow.
# Use the equations found in “Size Databases” on Page 1-18 to calculate the space for these two databases.
The DataMgr installation script will verify that there is enough space available in the installation directory before proceeding. If there is not enough space, the script asks if you want to attempt the install anyway. Typically, you want to stop the install, make the space available, and continue with the installation.

Create a platform-specific directory to contain the DataMgr files extracted from the CD. The default directory is /usr/dminstall. For instructions on deleting this directory if space is limited, see “Remove Load Directory” on page 4-6.
If, for example, you have extracted Solaris-specific DataMgr files from the CD, your directory hierarchy would look similar to the illustration below:
home/ tmp/ lib/ bin/ usr/
Each DataMgr component (BFS, SSD, SLD, and DMFS) must be installed on a UNIX machine.

The illustration attempts to give you an overview of the DataMgr elements described below.
Bitfile IDs for migrated
RIDs & Bitfiles for migrated files files
Has file systems managed by DataMgr.
Administrative xdmadm GUI.
RID identifies the location of the migrated file under the mount point /archive.
Stub file is left behind after DataMgr migrates a file.
BFS Database correlates BFIDs with RIDs.
Actual migrated files.
Bitfile is a term used to describe the migrated file on AMASS. The bitfiles are located under the corresponding clientmachinename directory.
Client xdmfs GUI.
Bitfile ID is a unique way to identify a migrated file.
Client Transaction Database.
Managed File System Database.
- Administrative xdmadm GUI is on the BFS and used by the System Administrator.
- Client xdmfs GUI is on the DMFS and used by clients as well as the System Administrator.

- Transaction Database is on each client’s machine.
- Managed File System Database is on each client’s machine. To calculate the size of this database, see “Size Managed File System Database” on page 1-20.
- BFS Database is on BFS. To calculate the size of this Database, see “Size BFS Database” on page 1-18.
- Bitfiles are located under /archive/FMSclients/clientmachinename.
During the installation process, DataMgr creates and writes to the directories listed in the table below. If you do not use the default directories, DataMgr creates the directory names that you enter in the script and the appropriate symbolic links.
Make sure that enough disk space is available for these directories. For space requirements, see “Disk Space” on page 1-13.
Component Default Directory Description
All components /etc/dm Location for DataMgr common files, such as the error log. All machines running a DataMgr component will have this directory.
BFS /etc/bfs Location of BFS executables.
SLD /etc/sld Location of SLD executables.
SSD /etc/ssd Location of SSD executables.
1-16 Prerequisites

Component Default Directory Description
DMFS (clients) /etc/dmfs Location of DMFS executables.
Complete Table Complete the table below when answering the installation questions. If you are installing a DMFS client component on more than one machine, make as many copies of this table as needed. If symbolic links are used, write down the appropriate path for each machine in both the Default Path and Symbolic Link Path columns.
Component Host Name UID GID Default Path Symbolic Link
BFS
SLD
AMASS

The following database are used in DataMgr:
Both the BFS Database and the Managed File System Database must be sized.
DMFS Client BFS & SLD SSD & AMASS
Stub for File A Bitfile ID for
File A RID & Bitfile
File A mation on File A
Managed File System Database
The BFS Database is located under /etc/dm/raima/bfs. This Database contains the bitfile IDs for migrated files. A bitfile ID points to a specific RID (record ID) on AMASS. This is how DataMgr keeps track of where client files have been migrated.
Use the formula below to determine the space required for the BFS Database:
Database size = 64 * Number of files being migrated

If File Replication or Multi-tier Policies are used, then the equation is:
Database size = ((64 + (factor * 16)) * Number of files being migrated
factor = Number of replicated copies or number of tiers.
Example 1: if you have client files using a File Replication policy with 1 primary copy and 1 secondary copy, the equation would look like the following:
Database size = (64 + (1 * 16)) * number of files)
Database size = 80 * number of files
Example 2: if you have client files using a Multi-tier policy with the primary copy and 2 tiers, the equation would look like the following:
Database size = (64 + (2 * 16)) * number of files
Database size = 96 * number of files
A migrated file that is subsequently modified and re-migrated creates a new record in the BFS Database. Also, when a migrated file is removed from a client’s managed file system, it’s record remains in the BFS Database until its retention time expires and the Trashcan is dumped. At that point, the record is available for re-use in the BFS Database.
Prerequisites · Prerequisites 1-19

A BFS Database that is 2GB in size can contain information for 20 million managed files.
The Managed File System Database is located under /etc/dm/raima/dmfs.There is a Managed File System Database for each client’s managed file system. The Database contains all the information on each file in the managed file system and stores information used in generating a list of files to migrate.
Prior to selecting a file system for management, you must determined the size of the Managed File System Database.
Use the formula below to determine the size:
Database size = ((Number of Directories x 250)+(Number of Files x 650))
The values for the Number of Directories and Files are estimates of the maximum number of files and directories that will reside on the client’s file system. This estimate assumes a typical directory and file name length of 20 characters or less. If the file name length is longer, add that length to the estimate.
For example, if the typical file name length is 40 the equation would look like the following:
Database size = ((Number of Directories x 290)+(Number of Files x 650))
1-20 Prerequisites

Edit Paths The following environmental paths are not automatically set up during installation.
man Pages Step 1. To use the man pages, set the following path.
For each c shell environment:
setenv MANPATH ${MANPATH}:/etc/dm/usr/share/man
For each bourne shell environment:
MANPATH=$MANPATH:/etc/dm/usr/share/man export MANPATH
Utilities Step 2. The GUIs use the DataMgr utilities to accomplish a task, for example, changing watermarks uses the dmfscntl utility. Therefore, set the following paths.
For each c shell environment:
set path=($path /etc/dm/usr/utils /etc/dmfs/usr/bin\ /etc/dmfs/usr/utils /etc/bfs/usr/bin /etc/bfs/usr/utils\ /etc/sld/usr/daemons /etc/ssd/usr/daemons /etc/bfs/usr/daemons)
For each bourne shell environment:
PATH=$PATH:/etc/dm/usr/utils:/etc/dmfs/usr/bin:/etc/dmfs/usr/utils:\ /etc/sld/usr/daemons:/etc/ssd/usr/daemons:/etc/bfs/usr/daemons:\ /etc/bfs/usr/
Prerequisites · export PATH · Prerequisites 1-21

GUIs Step 3. To run the Client xdmfs GUI, add /etc/dmfs/usr/bin to your PATH.
# cp /etc/dm/usr/share/gui/xdmfskeysym /usr/lib/X11/XKeysymDB
On Solaris, do the following:
# cp /etc/dm/usr/share/gui/xdmfskeysym /usr/openwin/lib/XKeysymDB
1-22 Prerequisites

The DataMgr dmfsscan command controls migration by bringing space usage levels for a managed file system in line with the values defined by the DataMgr administrator with the low and prestage watermarks.
The dmfsscan command, as a default, uses /usr/tmp for temporary file storage. If you want these files to be directed elsewhere, edit the /etc/dmfs/config/params file and add the "DMFS_TMPDIR=newdir" entry as shown below:
Add this entry to the file.

The system mount table defines the file systems and disk partitions that are mounted at boot time.
The file system name defined to DataMgr in the /etc/dmfs/config/dmfstab file must match an entry in this system mount file.
The location and format of this table varies by system architecture.The table below shows the location of this file on the various supported platforms:
System System Mount Table Man Page*
* For more information, refer to this man page.

Prerequisites · Prerequisites 1-25

1-26 Prerequisites


Extract Files From Local CD 2-3 Extract Files From Remote CD 2-4 Install DataMgr 2-6 Startup File 2-12 Startup & Shutdown 2-13

Install AMASS before installing DataMgr.
Verify that you have the necessary system requirements.
Install DataMgr. 2
Setup tasks:
Post installation tasks:
Task Refer To · Chapter · 2-2 Installation

To install DataMgr from CD on a local host, perform the following procedure:
# tar -xmvf/cdrompath/datamgr/platform.TAR
where:
cdrompath Enter the pathname where the CD has been mounted. For example, /cdrom/DATAMGR.
platform.TAR Enter the applicable operating system version. For example, sol26.TAR.
Installation · Option Description · Installation 2-3

To install DataMgr from CD on a remote host, perform the following procedure:
# rsh nodename -n dd
if=/cdrompath/datamgr/platform.TAR bs=20b | tar xmvBf -
where:
nodename Enter the remote host name of the machine where the tape device is attached. Make sure the node name is included in the /.rhosts file.
cdrompath Enter the pathname where the CD has been mounted. For example, /cdrom/DATAMGR.
platform.TAR Enter the applicable operating system version. For example, sol26.TAR.
Option Description · 2-4 Installation

Installation · Installation 2-5

If the various components are going to be installed on different machines, the installation sequence is as follows:
The SLD component should be installed first and must be running when the DMFS is installed. This only applies if the two components are located on different machines.
ADIC recommends that each component be started before the next component is installed. This will ensure that each component can talk to the others correctly.
The installation script inserts entries into various system files. These entries are encapsulated between special tags. A typical tag will appear like %CDVSTART_dmfs%. Do not alter or remove these tag lines.
From each machine listed in “Complete Table” on Page 1-17, perform the installations steps below:
If you are upgrading DataMgr, make sure you have a successful current backup of your BFS Database.
2-6 Installation

For example, the commands below go to the hpux directory and runs the DataMgr script.
# cd /usr/dminstall/hpux1020 # ./install_dm
a) DMFS - Data Manager File System (provides migrating file systems)
b) BFS - Bitfile Server (requires installed SSD)
c) SLD - Service Locator Daemon (must be one per network)
d) SSD - Storage Server Daemon (provides local SSD; requires AMASS)
e) ALL - All of the above
Please enter a, b, c, d, e, or a list (eg, ab):
You can select — one, all, or a combination — of components. For example, to install all four components on this machine, enter “e” as shown below:
Please enter a, b, c, d, e, or a list (eg, ab): e
Do you have a current full BFS Database Backup? (y | n) [y]
Installation · Installation 2-7

Please enter the numeric user ID (uid) for the dmfs account: 357
Please enter the base group ID (gid) for the dmfs account: 86
When you install the DMFS component, you need to know the AMASS UID and GID.
If you have previously installed DataMgr, the installation script asks if you want to replace the entries found in root’s crontab with defaults. The crontab contains administrative tasks, For additional information, see “Schedule cron Jobs” on page 3-4. If you answer NO, the script moves on to the next question. You will not be given the chance to select specific entries or configure values.
2-8 Installation

Do not locate the /etc/dm/raima files on a managed file system. Make sure the /etc/dm/raima directory does not reside in the /etc/dmfs/config/dmfstab file.
Enter actual DataMgr home location [/install/datamgr/dm]:
Append logging entries to /etc/syslog.conf? (y | n) [n]:
Enter actual SLD (Service Locator Daemon home location [/etc/sld]:
Enter actual DMFS (DataMgr FileSystem) home location [/etc/dmfs]:
Enter actual BFS (Bitfile Server) home location [/etc/bfs]:
Enter actual Raima database journal home location [/etc/dm/raima/journal]:
Enter actual Raima database home location [/etc/dm/raima]:
Enter actual SSD (Storage Server Daemon) home location [default is /etc/ssd]:
Installation · Installation 2-9

Please enter the hostname of the Storage Server to be used for storing database backups:
However, if you want DataMgr to create another directory, enter a new path.
Enter actual Storage Server Archive directory location [/archive/FMSclients]:
Enter actual DataMgr database backup directory location [/archive/BFSDB_Backup]:
Could not read symbolic link /dev/bd.off
Please do a full backup of your BFS Database before using any migrating file systems. Press return to continue.
2-10 Installation

IRIX only: An error message similar to the following may appear before the reboot but may be ignored:
Installation · Installation 2-11

SSD (on AMASS server) ssd
DMFS (on all clients) dmfsd
The table below lists the system startup files modified by DataMgr during installation. After modification, these system startup files run the /etc/rc.dm script, which contains the DataMgr startup commands.
Operating System Startup File
HP-UX /sbin/init.d
/etc/init.d

Although the command to automatically start DataMgr at bootup is added to the system startup file during installation, a special startup is required, for example, after the system administrator performs system maintenance.
# /etc/dm/usr/utils/killdmfs · Installation · Installation 2-13

2-14 Installation

Installation · Installation 2-15

2-16 Installation

Establish Access for DMFS Clients 3-3 Schedule cron Jobs 3-4
DMFS cron job 3-4 BFS cron job 3-5 Back Up Databases 3-6 Save SSD Logs 3-9 Logging 3-12
Logging Hierarchy 3-12 Format of Messages 3-13 Priority Levels 3-13 Modify Logging Characteristics 3-14 Modifiable Variables 3-15 Start Administra-tive GUI 3-19
Start Client GUI 3-19 Change Colors and Fonts 3-20
Setup Tasks

Install AMASS before installing DataMgr.
Verify that you have the necessary system requirements.
Install DataMgr. 2
Setup tasks:
Post installation tasks:
Task Refer To · Chapter · 3-2 Setup Tasks

Therefore, give clients root access if you want them to be able to add file systems and edit migration criteria. For information on file permission, refer to the chmod manual page.
Setup Tasks · Setup Tasks 3-3

During installation, DataMgr puts entries in the root crontab that perform the tasks described below. If the default schedule does not suit your site’s needs, edit the cron file. For more information, see “Edit cron File” on page 3-10.
DMFS cron job On all DMFS Clients, the crontab performs the following jobs:
3-4 Setup Tasks

BFS cron job On the BFS, the crontab performs the following jobs:
For more information, see “Assign a Backup Volume” on page 3-7. For more information, refer to the Utility Reference chapter in System Administrator’s Guide to Using DataMgr.
Setup Tasks · Setup Tasks 3-5

To effectively and efficiently manage your clients’ file systems, coordinate the execution of the following utilities by scheduling them as cron jobs:
ADIC recommends that you schedule these administrative tasks after the backup of a client’s managed file systems has completed. Therefore, the sequence of execution should be as follows:
While the BFS database is being backed up, the database is locked to prevent any modifications to the database until the backup is complete. Successful backups are sent to /etc/dm/raima/log/ bfsdb_backup.completed.
3-6 Setup Tasks

If this nightly backup fails, DataMgr sends a mail message to root notifying the system administrator the status of the bfsdb_backup. Failed backups are sent to /etc/dm/raima/log/ bfsdb_backup.logfilename.
You can recover a previous backup version of the database by using the /etc/bfs/usr/utils/bfsdb_restore utility that allows you to either restore the most recent backup or restore a specified version. For more information, refer to the Utility Reference chapter in System Administrator’s Guide to Using DataMgr.
Assign a Backup Volume
Do not use volume group 0 (zero) for the BFS Database backups.
Setup Tasks · Setup Tasks 3-7

# setvolgrp /archive/BFSDB_Backup 600
# cd /archive/BFSDB_Backup · # vgroot 600 · 3-8 Setup Tasks

Save SSD Logs DataMgr saves all file movement by the SSD to the /etc/dm/log/ssd/transfile log file. The log files are named transfile.x, where “x” is an age-related counter with the smaller number being the most current.
At installation, DataMgr schedules a nightly cron job that backs up the SSD log and saves the current transfile log to a transfile.x file and then creates a new file called transfile. However, the old transfile.x files are never deleted.
The format of this transfile.x is as follows:
hhmmss:MMDDYYYY type blocks copy BFID ftoken bfsserver logid errors filepath
where:
hhmmss Time of SSD log entry.
MMDDYYYY Date of SSD log entry.
type Creat = File was created in AMASS.
Delet = File was deleted in AMASS.
Renam = File was renamed in AMASS.
blocks Number of 512-byte blocks. Valid only for Creat type.
copy File replication copy number. Valid only for Creat type.
BFID Bitfile ID identifies a file that has been archived to the AMASS file system. Valid for Creat type. and Delet type.
For Renam types, this is the original bitfile name.
Field Description · Setup Tasks · Setup Tasks 3-9

ftoken AMASS RID (record ID).
bfsserver BFS server name. Valid only for Creat type.
logid Internal log ID number used by DataMgr.
errors Zero indicates success; non-zero indicates failure.
filepath Path name to file. For Renam type, this is the new filename.
To review these files in case of system errors, ADIC recommends that you do not delete these “old” transfile.x files, but place them in one of the following areas:
Edit cron File If the default schedule does not suit your site’s needs, edit the cron file:
In the crontab on all DMFS clients:
0 2 * * * /etc/dmfs/usr/utils/dmfsscan -aP
0 1 * * 0 /etc/dmfs/usr/utils/dmfsaudit -av
Field Description · 3-10 Setup Tasks

In the crontab on the BFS:
0 2 * * * /etc/bfs/usr/utils/bfsmaint -v -d 1 -m 0 4 * * 0-5 /etc/bfs/usr/utils/bfsdb_backup -v -n 0 4 * * 6 /etc/bfs/usr/utils/bfsdb_backup -v -n -f
The -n option of bfsdb_backup causes bfsdb_notify to send a mail message to root notifying the system administrator of any bfsdb_backup failure.
In the crontab on all DataMgr components:
0 1 * * 0 /etc/dm/scripts/clean_emasslogs 0 4 * * 0-5 /etc/bfs/usr/utils/bfsdb_backup -v -n 0 4 * * 6 /etc/bfs/usr/utils/bfsdb_backup -v -n -f
Setup Tasks · Setup Tasks 3-11

The figure below illustrates the logging hierarchy with the customer-specific parms/ directory annotated.

The format of a system log message is illustrated below:
Aug 14 1:16:12 nserv dataMgr dmfsd[1001]: E0006 (5) Message.
Actual Text.
Host name.
Transaction number, always 00000. Product name, DataMgr in this case.
Process that logs message.
Priority level, in parentheses.
Log number, begins with “E.”
Month, day, time message was generated.
Message destination PID in brackets [ ].
Priority Levels All messages are contained within a single file for easy reading and problem solving. This file is located in the /etc/dm/emasslogs/parms directory.
Priority levels for the messages are described in the following tables:
0 EMERGENCY: system panic.
1 ALERTS: startup, shutdown, and crash.
2 CRITICAL: system runs but in a degraded mode.
3 ERROR: unsuccessful operation.
4 WARNING: system resources are running short.
5 NOTICE: general system information.
6 INFORMATION: confirms a successful operation.

7 DEBUG: messages.
8 ADIC technical support trace message.
Several characteristics of a system log message can be modified with environment variables in the /usr/dm/emasslogs/emasslog_parms file that is created at install time.
When the emasslog_parms file is modified, run the reload_dmlog script, or stop and start the DMFS to activate the new options.
The /etc/dm/scripts/reload_dmlog script allows system administrator to specify which processes to reload with the new logging levels in the emasslog_parms file.
An example of the emasslog_parms file follows:
# This file contains all the environment variables
Comment lines begin with a number sign ( # ).
# EL_SYSLOG_OPTIONS indicates the format of each message to syslog
Each environment variable name starts in column one.
# EL_PERF_MASK enables the performance logging EL_PERF_ASK=ud;
Equal symbol ( = ) is followed by a value and ends with a semicolon (;).

The environment variables listed in the table below can be modified if required:
Identifies the UNIX user-definable logging process that sends DataMgr messages to the system log. The options are listed below:
(DataMgr defaults to 1)
(AMASS defaults to 2)
1 = LOG_LOCAL1
2 = LOG_LOCAL2
3 = LOG_LOCAL3
4 = LOG_LOCAL4
5 = LOG_LOCAL5
6 = LOG_LOCAL6
7 = LOG_LOCAL7
EL_SYSLOG_OPTIONS
Indicates message destination. Use one, all, or any combination of options. Options are:
p = use LOG_ PID.
c = use LOG_CONS to log messages to console too.
d = use LOG_NDELAY to log messages without delay.

The log mask used for priority 0-7 messages that are directed to the syslog. From the options available use one option or any option combined with “u.”
(defaults to ud)
Options are:
a = use LOG_ALERT for priority level 1
e = use LOG_EMERG for priority level 0.
c = use LOG_CRIT for priority level 2
i = use LOG_INFO for priority level 6
n = use LOG_NOTICE for priority level 5
r = use LOG_ERR for priority level 3
u = use LOG_UPTO() to log all priority levels up to ().
w= use LOG_WARNING for priority level 4
Logging that shows which commands have been run, the time it ran, and whether or not the command succeeded are located in /etc/dm/emasslogs/history/el_hist_00.

The clean_emasslogs script will be added to the user’s cron file upon installation. When this script is run it moves the current set of logs to a file in the same directory with the same name, but appended with a timestamp.Shown below is an example of a moved logs with the timestamp applied.
el_hist_00 el_hist_00.1999:11:28:01:00:00
el_hist_00.1999:11:25:01:00:00 el_hist_00.1999:11:29:01:00:00
el_hist_00.1999:11:26:01:00:00 el_hist_00.1999:11:30:01:00:00
el_hist_00.1999:11:27:01:00:00 el_hist_00.1999:11:30:15:04:08
In addition to the current log, the default script saves up to seven old log files per log type,. To change this default, edit the MAX_COPY parameter in the clean_emasslogs script.
There are two ways to save all log files without deleting the old files:
In both cases a directory must be created prior to modifying the clean_emasslogs script. The clean_emasslogs script does not create the directory.
Be aware that as files accumlate, the disk space is reduced.
# ls /etc/dm/emasslogs/history · Setup Tasks · Setup Tasks 3-17

In our example, we are turning on logging level nine.
-u Usage.
-a Reload all DataMgr processes running.
-p process Specify a single process ID.
-n name Specify a single process name. If multiple processes have the same (e.g. dmfsd), then -n dmfsd will affect each process.
EL_SYSLOG_MASK=ud; · Option Description · 3-18 Setup Tasks

To display help, select Help-->General Help.
To quit, select Services-->Exit.

Start Client GUI Step 1. To run the Client GUI, enter the xdmfs command.

To quit, select File-->Exit. To display help, select Help-->General Help.

When you start both GUIs, they will use default colors and fonts. To change the defaults file, follow the steps below:
3-20 Setup Tasks

DO NOT CHANGE any other text in this file.
Setup Tasks · Setup Tasks 3-21

3-22 Setup Tasks

Deinstall DataMgr 4-3 Reinstall DataMgr 4-4 Remove the Installation Directory 4-6
Tasks
Post Installation

Install AMASS before installing DataMgr.
Verify that you have the necessary system requirements.
Install DataMgr. 2
Setup tasks:
Post installation tasks:
4-2 Post Installation Tasks
Task Refer To · Chapter

If you no longer want to run DataMgr, you can deinstall it from your system by running the deinstallation script. It will remove all DataMgr directories and files.
Do not run deinstall_dm before upgrading or reinstalling DataMgr because it will totally remove all DataMgr files from your system. On the other hand, the install_dm script will remove just the files it needs to before reinstalling DataMgr.
Post Installation Tasks 4-3
# /etc/dm/usr/utils/killdmfs · # /etc/dm/scripts/deinstall_dm · Post Installation

If you upgrade a machine’s operating system, you must reinstall DataMgr.
4-4 Post Installation Tasks
# /etc/dm/usr/utils/killdmfs

Post Installation Tasks 4-5
# /etc/dm/scripts/install_dm · Post Installation

After the installation is complete, if space is limited you may want to remove the extracted DataMgr files from the machine where they were loaded.
home/ tmp/ lib/ bin/ usr/
# cd /usr/dminstall
# rm -r solaris
where:
solaris The name of your platform-specific load directory.
4-6 Post Installation Tasks

Post Installation Tasks 4-7
Post Installation

4-8 Post Installation Tasks


support for large 1-10 transfile 3-9 File system
BFS 2-10 DNS 3-3 managed file system illustration. 1-16 NIS 3-3 Deinstall DataMgr 4-3 deinstall_dm script 4-3 Directory
name length 1-9 size 1-9
Group ID 2-8 GUI 1-15
/archive/FMSclients 1-16 /etc/bfs 1-16 /etc/dm 1-16 /etc/dmfs 1-17 /etc/sld 1-16 /etc/ssd 1-16 defaults 1-16 Disk Space
administrative 3-19 client 3-19 customize 3-20 set up 1-22
Host ID 1-4
requirements 1-13 DMFS 1-15, 2-6, 2-9, 2-11
cron jobs 3-4 establish access 3-3 dmfsaudit utility 3-4, 3-10 dmfsscan utility 3-4, 3-6, 3-10 dmfstab 1-24 DNS database 3-3 Documentation set P-6
complete table 1-17 create directory 1-14 steps 2-6 install_dm script 2-7, 4-5
Journal 2-9
K
killdmfs script 2-13, 4-3, 4-4
/etc/bfs/registered 1-7, 1-8 /etc/hosts 3-3 cron 3-4 dmfstab 1-24 extract from CD 2-3, 2-4 registration 1-8
Large files 1-10 License 1-4, 2-11
capacity-based 1-3

features 1-3 issued to clients 1-7 Load directory
Registration file 1-7
refresh 1-8 Reinstall DataMgr 4-4 Release notes P-7, 1-9 Requirements 1-9
remove 4-6 Logs 3-4, 3-9
clear 3-9
disk space 1-13 shared libraries 1-10
S
backup 3-6 man pages 1-21 Mount point 2-10 Mount table
clearlog 3-4 deinstall_dm 4-3 install_dm 2-7, 4-5 killdmfs 2-13, 4-3, 4-4 rc.dlm 2-13 Serial number 1-4 Shared libraries 1-10 Shutdown
system 1-24
NIS database 3-3
special 2-13 SLD 1-14, 2-6, 2-9 SSD 1-14, 2-6, 2-9 SSD logs 3-4, 3-9 Startup
Online books P-6
Pathname limit 1-9 Paths 1-21 Product
daemons 2-12 special 2-13 Startup file
alerts P-7 bulletins P-7 Product key 1-5 Publications dept
location 2-12 Storage space
edit 1-23 syslog function 2-8 System logs
e-mail address P-7
3-4 System mount table 1-24
Raima 2-9 rc.dm script 2-13
Maintenance · Script · Index INX-3

user completes prior to install. . . 1-17 transfile 3-9
User ID 2-8 Utility
bfsd_backup 3-11 bfsdb_backup 3-5 bfsmaint 3-5, 3-6, 3-11 dmfsaudit 3-4, 3-10 dmfsscan 3-4, 3-6, 3-10 set up path to 1-21
secured site P-7
xdmadm command 3-19 xdmfs command 3-19
Table · Web · INX-4 Index
Eigenaren en ons team reageren doorgaans binnen een dag — en uw vraag helpt ook de volgende persoon.
Stel als eerste een vraag — andere eigenaren of ons team geven antwoord.