User manual QUANTUM DATAMGR 3.5 CLIENTS GUIDE 01-2000

[. . . ] Client's Guide to Using DataMgrTM DataMgr Version 3. 5 January, 2000 Document Number 600921 Trademark Notice AMASS, EMASS, DataMgr, FileServ, and VolServ are either trademarks or registered trademarks of ADIC, Advanced Digital Information Corporation. All other product names and identifications are trademarks or registered trademarks of their respective manufacturers. Copyright Notice Copyright © 1996-2000 by 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. Government Rights Restricted Use, duplication, or disclosure of either the software or documentation is subject to restrictions set forth by the U. S. [. . . ] However, if a path is a directory, then the entire tree represented by the directory is excluded from migration. Wildcards are not valid and will be ignored. Note Although the . /Migration directory, which contains configuration files and is created by DataMgr, is not explicitly listed in the locklist file it is never migrated. 2-16 View Management Criteria with Commands Client's Guide to Using DataMgr View Blocks & Number of Files Display number of files and blocks for both: · · Migrated files. Shadowed files. For a description of stub and shadowed files, refer to "Managed File Systems" on page 1-13 in DataMgr Overview. Note Can be run as non-root user. The path and options follow: View with Commands /etc/dmfs/usr/bin/dmdf [-b, -f, -h, -t, -u] [managedfs] where: Options no options Description View the total number of 1 KB-sized blocks that have been migrated or shadowed on the client's disk. View just the number of 1 KB-sized blocks that have been both migrated and shadowed. Usage. -b -f -h -t -u View Management Criteria with Commands 2-17 Client's Guide to Using DataMgr Options managedfs NOTE: If this option is not used, DataMgr displays all managed file systems. Description Specify the mount point of a client's managed file system. Separate multiple file systems with a space. View Number of Files & Blocks # dmdf mfspath /techpubs /home The output below is the result of running the command without options: migrated blocks 167021 156090 shadwd blocks 62384 122098 migrtd files 1519 2333 shadwd files 116 254 The output fields are described below: Field Mfspath Migrated Blocks Description List of file systems that DataMgr is currently managing. (The GUI expresses this value in MB. ) Shadowed Blocks Total number of 1 KB-sized blocks that have been shadowed. (The GUI expresses this value in MB. ) Migrated Files Total number of migrated files. 2-18 View Management Criteria with Commands Client's Guide to Using DataMgr Field Shadowed Files Description Total number of shadowed files. For a description of shadowed files, refer to "Shadowed File" on page 1-16 in DataMgr Overview. Using df Command on Managed Files When you interpret the UNIX df output for a managed file system, remember that each migrated file requires only 1 KB of space on your managed file system because this is the amount of space used by the stub file. For a description of stub files, refer to "Stub Files" on page 1-14 in DataMgr Overview. View with Commands View Management Criteria with Commands 2-19 Client's Guide to Using DataMgr View Space Needed for Reloads Display the virtual space usage in KB for either: · · Migrated files. Migrated directories. Virtual space is the logical block count of files; therefore, if a file is migrated, dmdu displays the space that would be used if the file were reloaded. Note Can be run as non-root user. The path and options follow: /etc/dmfs/usr/bin/dmdu [-u] [-a | -a file] [-s | -s directory] where: Options no options Description Display the total amount of virtual space (in 1 KB-sized blocks) required for each directory if the entire directory was reloaded. -u -a file NOTE: If a file is not specified, DataMgr uses the current directory. Display the total amount of virtual space (in 1 KB-sized blocks) required by each file if the file was reloaded. Names descend recursively. 2-20 View Management Criteria with Commands Client's Guide to Using DataMgr Options -s directory NOTE: If a directory is not specified, DataMgr uses the current directory. Description Display the total amount of virtual space (in 1 KB-sized blocks) required by each subdirectory. The output below is the result of running the command with the -a option: # dmdu -a 0 1 1 0 1 1 1 0 5 1184 9 2 1200 . /lost+found . /amass . /xdimod . /Migration/label . /Migration/locklist . /Migration/policy . /Migration/status . /Migration/trans . /Migration . /techpubs . /home . /vmunix . View with Commands View Management Criteria with Commands 2-21 Client's Guide to Using DataMgr The output fields are described below: Field Virtual Space Description Amount of virtual space (in 1 KB-sized blocks) required by each migrated file if the file was reloaded. Files or directory in a file system. File or Directory Name Using du Command on Managed Files The UNIX du command operates unchanged on a managed file system. It reports the number of 1 KB-sized blocks used by each directory encountered as it traverses the directory specified on the command line. When you interpret the UNIX du output for a managed file system, remember that each migrated file requires only 1 KB of space on your migrating file system because this is the amount of space used by the stub file. For a description of stub files, refer to "Stub Files" on page 1-14 in DataMgr Overview. 2-22 View Management Criteria with Commands Client's Guide to Using DataMgr NOTES View with Commands View Management Criteria with Commands 2-23 Client's Guide to Using DataMgr 2-24 View Management Criteria with Commands Task Table . 3-16 3 View Management Criteria with GUI View with GUI Client's Guide to Using DataMgr Roadmap Topic Initial setup tasks prior to using DataMgr. 4 5 A 3 Refer To Chapter 1 2 3-2 View Management Criteria with GUI Client's Guide to Using DataMgr Task Table Task View Migration Criteria View Space Occupied by Files View Policy Parameters View Files Managed by DataMgr View File Excluded From Migration View Blocks & Number of Files View Space Needed for Reloads 2-7 2-10 2-15 2-17 2-20 Command 2-4 GUI 3-4 3-8 3-10 3-13 3-14 Note View with GUI This chapter assumes that a DataMgr client can only view statistics, and cannot edit values that have been previously set by the DataMgr administrator. View Management Criteria with GUI 3-3 Client's Guide to Using DataMgr View Migration Criteria To view the file systems managed by DataMgr, use the Client xdmfs GUI. For the location of the system mount table for your workstation, refer to "System Mount Table" on page 1-7. To run the Client GUI, enter the xdmfs command. # xdmfs Step 2. The Client Main menu appears. [. . . ] · E_DM_NOFILEINFO = Specified file or directory does not exist or can not find in the DataMgr database. · E_DM_NOTRUNNING = DataMgr has been installed but is not currently running. · E_DM_RESOURCE = Unable to allocate enough resources (memory) to get the status of the requested file. API Calls API Calls A-7 Client's Guide to Using DataMgr DM_LockFile() Add the specified file to the DataMgr locklist. The file will not be truly locked from migration until the DM_SyncLock() routine is called. [. . . ]