file system manager user’s guide - oracle · file system manager user’s guide part no....

Sun Microsystems, Inc.www.sun.com

Submit comments about this document at: http://www.sun.com/hwdocs/feedback

File System Manager User’s Guide

Part No. 819-5448-10April 2006, Revision 01

PleaseRecycle

Copyright 2006 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, California 95054, U.S.A. All rights reserved.

Sun Microsystems, Inc. has intellectual property rights relating to technology that is described in this document. In particular, and withoutlimitation, these intellectual property rights may include one or more of the U.S. patents listed at http://www.sun.com/patents and one ormore additional patents or pending patent applications in the U.S. and in other countries.

This document and the product to which it pertains are distributed under licenses restricting their use, copying, distribution, anddecompilation. No part of the product or of this document may be reproduced in any form by any means without prior written authorization ofSun and its licensors, if any.

Third-party software, including font technology, is copyrighted and licensed from Sun suppliers.

Parts of the product may be derived from Berkeley BSD systems, licensed from the University of California. UNIX is a registered trademark inthe U.S. and in other countries, exclusively licensed through X/Open Company, Ltd.

Sun, Sun Microsystems, the Sun logo, AnswerBook2, docs.sun.com, Solaris, Java, Solstice DiskSuite, SunPlex, and Sun StorEdge aretrademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and in other countries.

All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. in the U.S. and in othercountries. Products bearing SPARC trademarks are based upon an architecture developed by Sun Microsystems, Inc.

Mozilla is a trademark or registered trademark of Netscape Communications Corporation in the United States and other countries.

The OPEN LOOK and Sun™ Graphical User Interface was developed by Sun Microsystems, Inc. for its users and licensees. Sun acknowledgesthe pioneering efforts of Xerox in researching and developing the concept of visual or graphical user interfaces for the computer industry. Sunholds a non-exclusive license from Xerox to the Xerox Graphical User Interface, which license also covers Sun’s licensees who implement OPENLOOK GUIs and otherwise comply with Sun’s written license agreements.

U.S. Government Rights—Commercial use. Government users are subject to the Sun Microsystems, Inc. standard license agreement andapplicable provisions of the FAR and its supplements.

DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES,INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT,ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID.

Copyright 2006 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, Californie 95054, Etats-Unis. Tous droits réservés.

Sun Microsystems, Inc. a les droits de propriété intellectuels relatants à la technologie qui est décrit dans ce document. En particulier, et sans lalimitation, ces droits de propriété intellectuels peuvent inclure un ou plus des brevets américains énumérés à http://www.sun.com/patents etun ou les brevets plus supplémentaires ou les applications de brevet en attente dans les Etats-Unis et dans les autres pays.

Ce produit ou document est protégé par un copyright et distribué avec des licences qui en restreignent l’utilisation, la copie, la distribution, et ladécompilation. Aucune partie de ce produit ou document ne peut être reproduite sous aucune forme, par quelque moyen que ce soit, sansl’autorisation préalable et écrite de Sun et de ses bailleurs de licence, s’il y en a.

Le logiciel détenu par des tiers, et qui comprend la technologie relative aux polices de caractères, est protégé par un copyright et licencié par desfournisseurs de Sun.

Des parties de ce produit pourront être dérivées des systèmes Berkeley BSD licenciés par l’Université de Californie. UNIX est une marquedéposée aux Etats-Unis et dans d’autres pays et licenciée exclusivement par X/Open Company, Ltd.

Sun, Sun Microsystems, le logo Sun, AnswerBook2, docs.sun.com, Solaris, Java, Solstice DiskSuite, SunPlex, et Sun StorEdge sont des marquesde fabrique ou des marques déposées de Sun Microsystems, Inc. aux Etats-Unis et dans d’autres pays.

Toutes les marques SPARC sont utilisées sous licence et sont des marques de fabrique ou des marques déposées de SPARC International, Inc.aux Etats-Unis et dans d’autres pays. Les produits portant les marques SPARC sont basés sur une architecture développée par SunMicrosystems, Inc.

Mozilla est une marque de Netscape Communications Corporation aux Etats-Unis et à d’autres pays.

L’interface d’utilisation graphique OPEN LOOK et Sun™ a été développée par Sun Microsystems, Inc. pour ses utilisateurs et licenciés. Sunreconnaît les efforts de pionniers de Xerox pour la recherche et le développement du concept des interfaces d’utilisation visuelle ou graphiquepour l’industrie de l’informatique. Sun détient une license non exclusive de Xerox sur l’interface d’utilisation graphique Xerox, cette licencecouvrant également les licenciées de Sun qui mettent en place l’interface d ’utilisation graphique OPEN LOOK et qui en outre se conformentaux licences écrites de Sun.

LA DOCUMENTATION EST FOURNIE "EN L’ÉTAT" ET TOUTES AUTRES CONDITIONS, DECLARATIONS ET GARANTIES EXPRESSESOU TACITES SONT FORMELLEMENT EXCLUES, DANS LA MESURE AUTORISEE PAR LA LOI APPLICABLE, Y COMPRIS NOTAMMENTTOUTE GARANTIE IMPLICITE RELATIVE A LA QUALITE MARCHANDE, A L’APTITUDE A UNE UTILISATION PARTICULIERE OU AL’ABSENCE DE CONTREFAÇON.

Contents

1. Product Overview 1

About the File System Manager Software 1

How the Software Works 2

Assigning Administrative Privileges to Users 3

Logging In to and Out of the Software 5

Setting the Session Timeout Value 6

2. Using the Browser Interface 7

About Interface Elements 7

About the Banner and Content Pane 7

Reference: Banner Elements 9

Reference: Content Pane Navigational Elements 10

Reference: Content Pane Icons and Buttons 11

About Wizards 13

Enabling Pop-Up Windows 13

Changing the Current Server 14

About Report Tables 14

Reference: Report Table Controls 15

Sorting Tables 17

Filtering Tables 17

iii

Using Help 17

3. Getting Started: Task Overview 19

4. Performing Initial Configuration Tasks 21

Task Overview: Configuring a Server 21

Reference: Server Configuration Files 22

Specifying How Configuration Entries Are Saved 23

Adding a Server 24

Removing a Server 26

5. Monitoring the Environment 27

Monitoring Servers 27

Displaying the Configuration of Servers in Your Site 28

Displaying the Configuration of a Server 28

Displaying Software Packages on a Server 28

Displaying Log or Trace Files on a Server 29

Displaying Configuration Files on a Server 29

Displaying Warning Messages in Server Files 30

Displaying the Minimum Server Release Supported by File SystemManager 30

Monitoring File Systems 31

Displaying the Status of a File System 31

Displaying File System Devices 32

Displaying NFS Shared Directories in a File System 32

Displaying File Match Criteria for an Archiving File System 33

Displaying the Status of Metadata Snapshot Activities 33

Displaying the Status of a Restore Process for an Archiving File System 34

Displaying the Metadata Server for a Shared File System 35

Displaying All Hosts in a Shared File System 35

iv File System Manager User’s Guide • April 2006

Monitoring Policies 36

Displaying File Match Criteria in a Policy 36

Displaying File Systems Using Specific File Match Criteria 37

Displaying the Copy Details of a Policy 37

Displaying the VSNs Assigned to a Policy Copy 38

Monitoring Libraries 38

Displaying VSNs for a Library 39

Displaying the Drives in a Library 39

Displaying the Status and State of a Library 40

Displaying Historian Catalog Information 40

Displaying Mount Requests in a Library 41

Monitoring Tape Drives 41

Displaying the VSN for a Tape Drive 41

Displaying the State of a Stand-Alone Tape Drive 42

Monitoring Archiving, Releasing, and Staging Activity 42

Displaying Archiving Activity 43

Displaying Releasing Activity 43

Displaying Staging Activity 44

Monitoring Jobs 44

About Jobs 44

Displaying Jobs 46

Canceling a Job 46

Monitoring Faults 47

About Faults 47

Displaying Faults 48

Acknowledging Faults 49

Deleting Faults 49

Contents v

6. Managing File Systems 51

About File System Management 51

About Discovering Available Devices 52

About File Systems 53

About Supported File Systems 54

About Stand-Alone, Non-archiving File Systems 56

About Archiving File Systems 57

About Shared File Systems 58

About HA-QFS File Systems 59

Administering Stand-Alone, Non-archiving File Systems and Archiving FileSystems 60

Planning a Stand-Alone, Non-archiving or Archiving File System 60

Creating a Stand-Alone, Non-archiving or Archiving File System 61

Growing a Stand-Alone, Non-archiving or Archiving File System 62

Checking a Stand-Alone, Non-archiving or Archiving File System 63

Mounting a Stand-Alone, Non-archiving or Archiving File System 64

Editing Mount Options for a Stand-Alone, Non-archiving or Archiving FileSystem 65

Unmounting a Stand-Alone, Non-archiving or Archiving File System 66

Deleting a Stand-Alone, Non-archiving or Archiving File System 66

About Creating an Archiving File System and VSN Association 67

Managing Policies for Archiving File Systems 68

Removing File Match Criteria From an Archiving File System 68

Adding a Policy to an Archiving File System 69

Adding Existing File Match Criteria to an Archiving File System 69

Reordering File Match Criteria for an Archiving File System 70

Protecting Archiving File System Data 71

About Protecting Archiving File System Data 71

Scheduling and Taking Metadata Snapshots 72

vi File System Manager User’s Guide • April 2006

About Metadata Snapshots 72

Planning Metadata Snapshots 73

Scheduling the Creation of Metadata Snapshots 74

Taking a Metadata Snapshot on Demand 75

Editing a Metadata Snapshot Schedule 75

Removing a Metadata Snapshot Schedule 76

Restoring Archiving File System Data 76

Restoring an Archiving File System 77

About Filtering and Searching Through Metadata Snapshots 79

About Filter and Search File Name Pattern Values 81

Canceling a Metadata Snapshot Search 82

Deleting the Index for a Metadata Snapshot 82

Deleting a Metadata Snapshot 83

Administering Shared File Systems 84

Planning a Shared File System 85

Creating a Shared File System 85

Creating the Shared Hosts File 86

Adding a Client or Potential Metadata Server 87

Deleting a Client or Potential Metadata Server 88

Deleting the Metadata Server 89

Mounting and Unmounting Shared File Systems 90

Mounting a Shared File System 90

Mounting the Metadata Server 91

Mounting a Client or Potential Metadata Server 91

Editing Mount Options for a Shared File System 92

Unmounting a Shared File System 93

Unmounting a Client or Potential Metadata Server 93

Unmounting the Metadata Server 94

Contents vii

Deleting a Shared File System 94

Managing NFS Sharing for File Systems 95

About NFS Sharing 95

Adding an NFS Directory 96

Editing NFS Directory Options 97

Changing the Status of an NFS Directory 98

Removing an NFS Directory 99

7. Managing Archiving 101

About Archive Management 101

About Archiving, Releasing, and Staging 102

About the Sun StorEdge SAM-FS Software 103

About Archiving 104

Planning for Archiving 105

About Continuous Archiving 107

About Associative Archiving 108

About the Releaser 108

About the Stager 109

Controlling Archiving for Archiving File Systems 109

Configuring Archiver Scanning for an Archiving File System 110

Stopping or Idling Archiving for an Archiving File System 110

Running Archiving for an Archiving File System 111

Managing Archive Policies 111

Administering Archive Policies 112

About Archive Policies 112

Reference: Creating a Policy archiver.cmd Example 115

Creating a Policy 116

Creating a No-Archive Policy 116

Editing a Policy 117

viii File System Manager User’s Guide • April 2006

Deleting a Policy 117

Enabling Archiving Options in a Policy 118

Enabling Disk Archiving 118

Enabling Archiving to Tape 119

Enabling Associative Archiving 120

Enabling Continuous Archiving 121

Enabling Archiving to Pools of Disk or Tape VSNs 122

Administering File Match Criteria 123

About File Match Criteria 124

Editing File Match Criteria 124

Adding a File System to a Set of File Match Criteria 125

Removing a File System From a Set of File Match Criteria 126

Planning File Match Criteria 126

Adding File Match Criteria to a Policy 127

Removing File Match Criteria From a Policy 128

Administering Policy Copies 128

About Policy Copies 129

Editing a Policy Copy 129

Modifying VSN Assignments in a Policy Copy 129

Adding a Copy to a Policy 130

Removing a Copy From a Policy 130

Managing VSN Pools for Archiving 131

About VSN Pools 131

Creating a VSN Pool 132

Editing a VSN Pool 132

Deleting a VSN Pool 133

Managing Disk VSNs for Archiving 134

About Archiving to Disk VSNs 134

Contents ix

Creating a Disk VSN 135

Editing the Media Attributes of a Disk VSN 135

Setting Up General Archiving 136

About Archiver Scanning Methods 136

Configuring Global Archiving Values 137

Configuring Global Staging Values 138

Configuring Global Releasing Values 138

Configuring Global Media Type Parameters 139

Configuring the Recycler 140

About the Recycler 140

Running Recycling 141

Configuring Library Recycling Values 142

Configuring Policy Recycling Values 143

Managing Archiving and Staging Activity 144

Controlling Global Archiving Activity 144

Controlling Global Staging Activity 145

Staging a File or Directory on Demand 145

8. Managing Removable Media 147

About Removable Media Management 147

About Removable Media 148

About Supported Libraries and Drives 149

About the Historian 150

Managing Libraries 150

About Libraries 151

Adding a Library 151

Changing the State of a Library 152

Unloading a Library 153

Removing Archiving, Staging, and Recycling Configurations 154

x File System Manager User’s Guide • April 2006

Deleting a Library 155

Managing Library Drives 156

Changing the State of a Library Drive 156

Idling a Drive 156

Unloading a Drive 157

Cleaning a Drive 158

Managing VSNs in a Library 158

Searching for a VSN 159

Importing a VSN 159

Exporting a VSN 160

Loading a VSN Into a Drive in a Library 161

Unloading a VSN From a Drive in a Library 162

Labeling a VSN 162

Reserving a VSN in a Library 163

Unreserving a VSN in a Library 164

Auditing the Slot for a VSN in a Library 165

Editing the Media Attributes for a VSN in a Library 165

Managing Stand-Alone Tape Drives 166

About Stand-Alone Tape Drives 167

Adding a Tape Drive 167

Deleting a Tape Drive 167

Unloading a VSN From a Tape Drive 168

Reserving a VSN in a Tape Drive 169

Unreserving a VSN in a Tape Drive 170

Changing the State of a Tape Drive 170

Editing the Media Attributes for a VSN in a Tape Drive 171

Idling a Tape Drive 172

Auditing a Slot of a Tape Drive 172

Contents xi

9. Performing General Administration Tasks 175

About Notifications 175

Creating a Notification 177

Changing Notification Events for a Recipient 177

Deleting a Notification 178

10. Troubleshooting 179

Using SAMreports 179

About SAMreports 180

Displaying SAMreports 180

Generating SAMreports 181

Incompatible Software Release 181

One Device Displayed Multiple Times 182

Inaccessible Server 183

No Remaining Space for a VSN 184

Damaged or Stale Files in a Metadata Snapshot 184

Existing Fault Conditions Not Displayed 184

Glossary 187

Index 201

xii File System Manager User’s Guide • April 2006

Preface

The File System Manager User’s Guide provides detailed procedures for using the FileSystem Manager browser-based graphical user interface. This document is writtenfor system administrators and users who use File System Manager to configure,control, protect, and monitor one or more file systems in the network from a centrallocation.

Before You Read This DocumentThis document assumes that the management station software and the SunStorEdgeQFS or Sun StorEdge SAM-FS software packages are already installed.

For insatallation procedures, see the Sun StorEdge QFS Software Installation andUpgrade Guide and the Sun StorEdge SAM-FS Software Installation and Upgrade Guide.

Using UNIX CommandsThis document might not contain information about basic UNIX® commands andprocedures such as shutting down the system, booting the system, and configuringdevices. Refer to the following for this information:

■ Software documentation that you received with your system

■ Solaris™ Operating System documentation, which is at:

http://docs.sun.com

xiii

Shell Prompts

Typographic Conventions

Shell Prompt

C shell machine-name%

C shell superuser machine-name#

Bourne shell and Korn shell $

Bourne shell and Korn shell superuser #

Typeface*

* The settings on your browser might differ from these settings.

Meaning Examples

AaBbCc123 The names of commands, files,and directories; on-screencomputer output

Edit your.login file.Use ls -a to list all files.% You have mail.

AaBbCc123 What you type, when contrastedwith on-screen computer output

% su

Password:

AaBbCc123 Book titles, new words or terms,words to be emphasized.Replace command-line variableswith real names or values.

Read Chapter 6 in the User’s Guide.These are called class options.You must be superuser to do this.To delete a file, type rm filename.

xiv File System Manager User’s Guide • April 2006

Related DocumentationThis manual is part of a set of documents that describes the operations of the SunStorEdge QFS and Sun StorEdge SAM-FS software products. TABLE P-1 shows thecomplete release 4U5 documentation set for these products.

If you are configuring a File System Manager file system in a Sun Clusterenvironment, the following additional documents might interest you:

■ Sun Cluster Concepts Guide for Solaris OS

■ Sun Cluster Software Installation Guide for Solaris OS

■ Sun Cluster Data Services Planning and Administration Guide for Solaris OS

■ Sun Cluster Data Service for Oracle Real Application Clusters Guide for Solaris OS

Accessing Sun Documentation OnlineThe File System Manager software distribution includes PDF files that you can viewfrom Sun’s Network Storage documentation web site or from docs.sun.com.

TABLE P-1 Related File System Manager Documentation

Title Part Number

Sun StorEdge QFS Configuration and Administration Guide 819-4332-10

Sun StorEdge SAM-FS File System Configuration and Administration Guide 819-4333-10

Sun StorEdge SAM-FS Storage and Archive Management Guide 819-4329-10

Sun StorEdge SAM-FS Installation and Upgrade Guide 819-4330-10

Sun StorEdge QFS Installation and Upgrade Guide 819-4334-10

Sun StorEdge SAM-FS Troubleshooting Guide 819-4331-10

Sun StorEdge QFS and Sun StorEdge SAM-FS 4.5 Release Notes 819-4335-10

Preface xv

To Access Documentation From docs.sun.comThis web site contains documentation for Solaris and many other Sun softwareproducts.

1. Go to the following URL:

http://docs.sun.com

The docs.sun.com page appears.

2. Find the documentation for your product by searching for File System Manager inthe search box.

To Access Documentation From Sun’s NetworkStorage Documentation Web SiteThis web site contains documentation for Network Storage products.

1. Go to the following URL:

http://www.sun.com/products-n-solutions/hardware/docs/Software/Storage_Software

The Storage Software page appears.

2. Click the Sun StorEdge QFS or Sun StorEdge SAM-FS links.

Third-Party Web SitesSun is not responsible for the availability of third-party web sites mentioned in thisdocument. Sun does not endorse and is not responsible or liable for any content,advertising, products, or other materials that are available on or through such sitesor resources. Sun will not be responsible or liable for any actual or alleged damageor loss caused by or in connection with the use of or reliance on any such content,goods, or services that are available on or through such sites or resources.

xvi File System Manager User’s Guide • April 2006

Sun Welcomes Your CommentsSun is interested in improving its documentation and welcomes your comments andsuggestions. You can submit your comments by going to:

http://www.sun.com/hwdocs/feedback

Please include the title and part number of your document with your feedback:

File System Manager User’s Guide, part number 819-5448-10

Preface xvii

xviii File System Manager User’s Guide • April 2006

CHAPTER 1

Product Overview

This chapter provides an overview of the File System Manager. It contains thefollowing sections:

■ “About the File System Manager Software” on page 1

■ “How the Software Works” on page 2

■ “Assigning Administrative Privileges to Users” on page 3

■ “Logging In to and Out of the Software” on page 5

■ “Setting the Session Timeout Value” on page 6

About the File System ManagerSoftwareThe File System Manager software is a browser-based graphical user interface thatenables you to configure, control, protect, and monitor one or more file systems inyour network from a central location. To access this central location, you can use theweb browser on any host in your network.

The goal of the software is to provide a less complex way than the command line ofperforming the most common tasks associated with these file systems. To configureoptions that are unavailable through the browser interface, use the command-lineinterface, configuration files, and so on, that are associated with the file systems.

Note: If you manually edit configuration files outside of the browser interface, youare responsible for any errors that might occur due to incorrect configuration.

1

How the Software WorksThe File System Manager software is installed on a server called the managementstation. The name of the management station is always displayed in the banner ofthe browser interface.

When you first run the browser interface, you add servers upon which the filesystems that you want to administer will reside. You can add the managementstation to the browser interface to administer file systems on the managementstation.

Note: To add a server to the browser interface, you must install the appropriatepackages locally. For example, if you want to manage archiving file systems throughthe browser interface, you must have the SUNWsamfsr and SUNWsamfsu packagesinstalled locally. For information about Sun StorEdge SAM-FS and Sun StorEdgeQFS software releases that are compatible with the current File System Managerbrowser interface, click a server release on the Servers page or see the README file.

The servers that you add are displayed on the Servers page. By clicking a servername on this page, you can access web pages where you can configure andadminister the file systems on the server. Depending on the packages installedlocally on the server that you select, different web pages, fields, and options aredisplayed in the browser interface.

Each time you perform a configuration action through the browser interface, the FileSystem Manager software edits the appropriate configuration files that are locatedon the server that you are administering. This enables you to configure the filesystems on the server remotely and without using a command-line interface.

When you perform any action in the browser interface, including a refresh of theweb browser window, the latest data is updated. For example, mounting a filesystem updates the browser interface with data about the file system, its drives, andfiles.

Use the Jobs tab to view the progress of user and system processes. For example, toview the archiving status of files, click the Jobs tab and choose a category from theFilter menu. All jobs from the selected category are displayed.

For information about how to perform initial configuration steps, see “TaskOverview: Configuring a Server” on page 21.

For information about installing the management station and about installing theSun StorEdge QFS and Sun StorEdge SAM-FS software packages, see the SunStorEdge QFS Software Installation and Upgrade Guide and the Sun StorEdge SAM-FSSoftware Installation and Upgrade Guide.

2 File System Manager User’s Guide • April 2006

Assigning AdministrativePrivileges to UsersBy default, the root user has privileges to perform all operations available from theFile System Manager software.

You can assign other users full access to all File System Manager operations, oraccess to only a subset of operations. The following table lists the five levels ofprivileges that you can assign to File System Manager users.

These privilege levels and the functions assigned to each level are defined in the/etc/security/auth_attr file.

Caution: For proper system operation, do not make any changes to the/etc/security/auth_attr file.

To add users and assign privileges, complete the following procedure.

1. Outside of the browser interface, log in to the management station server asroot.

2. Use the useradd and passwd commands to add each user.

For example, to add a user with account name bobsmith, type the following:

# /usr/sbin/useradd/useradd bobsmith

# /usr/bin/passwd bobsmith

Each user account that you add in this way has read-only viewing privileges forFile System Manager functions.

TABLE 1-1 Administrative Privileges

Administrative Privilege Level Privileges

com.sun.netstorage.fsmgr.config Unlimited.

com.sun.netstorage.fsmgr.operator.media Import, export and assign VSNs (volume serialnames).

com.sun.netstorage.fsmgr.operator.sam.control Perform operations relating to faults and jobs,generate SAMreports, and start, stop, and idlethe archiving function.

com.sun.netstorage.fsmgr.operator.file Perform staging and restoring operations.

com.sun.netstorage.fsmgr.operator.filesystem Mount and unmount file systems, and checkand repair file systems.

Chapter 1 Product Overview 3

3. (Optional) To specify full or partial configuration privileges for a user, add thefollowing line to the /etc/user_attr file:

account-name::::auths=privilege-level

account-name is the name of the user’s account and privilege-level is the level ofauthorization that you want to assign to the user.

For example, to assign full privileges (privilege levelcom.sun.netstorage.fsmgr.config) for user account bobsmith, add thefollowing line to the /etc/user_attr file:

bobsmith::::auths=com.sun.netstorage.fsmgr.config

To assign bobsmith privileges only for staging and restoring file systems(privilege level com.sun.netstorage.fsmgr.operator.file) and exporting,importing, and assigning VSNs (privilege levelcom.sun.netstorage.operator.media), add the following line to the/etc/user_attr file:

bobsmith::::auths=com.sun.netstorage.fsmgr.operator.file,com.sun.netstorage.fsmgr.operator.media

You can also create an account for multiple users that includes a role with privilegesthat only some of those users can access. To do this:

1. Use the useradd and passwd commands to add the account.

2. Use the roleadd and passwd commands to add the role.

3. Specify the privilege levels in the /etc/user_attr file.

For example, to add a user account called guest for multiple users and a rolecalled admin with special privileges within that account, type the following:

# /usr/sbin/useradd/useradd guest

# /usr/bin/passwd guest

# /usr/sbin/roleadd admin

# /usr/bin/passwd admin

To assign privileges to the admin role to restore and stage file systems, add thefollowing lines to the /etc/user_attr file:

admin::::auths=com.sun.netstorage.fsmgr.operator.file

guest::::type=normal;roles=admin

In this example, when a user logs in as guest, File System Manager prompts theuse to select either No Role or Admin. If users know the Admin role password,they can select Admin, enter the Admin password, and have privileges to restoreand stage file systems. All other users must select No Role and have read-onlyprivileges.


Because multiple users with the same privilege level can be logged in to the softwareconcurrently, there is a risk of one user's changes overwriting another user'sprevious changes. To prevent this, develop policies about who can make changesand how to notify others.

Logging In to and Out of theSoftwareTo log in to the File System Manager software:

1. Open a web browser window and type the following address in the Address field:

https://management-station-name:6789

The Java Web Console is displayed.

2. In the User Name field, type either root or your user name.

Note – If you have upgraded the File System Manager software from an earlierversion, the samadmin user account is still available. You can type samadmin in theUser Name field and then type the samadmin password to gain full access to all FileSystem Manager operations.

3. In the Password field, type the root password or your user password.

If you do not know the password, contact your system administrator.

4. Click Log In.

The Java Web Console displays a list of the software applications that areavailable to you.

5. In the Storage section, click File System Manager.

After logging in to the File System Manager software, perform operations (such asmonitoring) in a single session. Opening multiple sessions could cause theoverwriting of changes made in either session.

To log out of the File System Manager software, click Log Out in the upper rightcorner of the page. If you are using a personal computer and do not log out usingthis method, the session might remain open, and you might not be prompted for auser name the next time you try to log in.

Chapter 1 Product Overview 5

Setting the Session TimeoutValueBy default, a SunJava Web Console session times out after fifteen minutes ofidleness. The File System Manager installation process changes the session timeoutvalue to 60 minutes if File System Manager is the only application registered in theSun Java Web Console environment.

You can change the session timeout value, although for security reasons, a valuegreater than 60 minutes is not recommended.

To change the timeout value:

1. Outside of the browser interface, log on to the management station server asroot.

2. Enter the command /opt/SUNWfsmgr/bin/fsmgr session timeout, wheretimeout is the timeout value in minutes. For example, to set the timeout to 45minutes, enter the following command:

# /opt/SUNWfsmgr/bin/fsmgr session 45


CHAPTER 2

Using the BrowserInterface

This chapter provides information about using the browser interface. It contains thefollowing sections:

■ “About Interface Elements” on page 7

■ “About Wizards” on page 13

■ “Enabling Pop-Up Windows” on page 13

■ “Changing the Current Server” on page 14

■ “About Report Tables” on page 14

■ “Using Help” on page 17

About Interface ElementsThis section provides information about the elements of the browser interface. Itcontains the following subsections:

■ “About the Banner and Content Pane” on page 7

■ “Reference: Banner Elements” on page 9

■ “Reference: Content Pane Navigational Elements” on page 10

■ “Reference: Content Pane Icons and Buttons” on page 11

About the Banner and Content PaneThe File System Manager browser interface pages are divided into two sections:

7

■ Banner

■ Content pane

The banner displays the name of the application and displays other statusinformation, such as the last time data was updated in the browser interface. Thecontent pane displays the Change Server button, navigational tabs, and reports andforms.

FIGURE 2-1 Banner, Navigational Elements, and Content Pane

You can navigate through the File System Manager browser interface as you would atypical web page. Use the navigational tabs in the content pane to move to differentpages throughout the application. Click a link in the content pane to view moredetailed information about that selected item. To return to a previous browserinterface page, click the link that you want in the navigational path that is displayedon the current page, just below the navigational tabs.

In addition, you can place your mouse over a portion of the browser interface todisplay a tooltip, which is a line of text that describes that portion of the page.


Reference: Banner ElementsThe banner spans the top of the application. The following table describes theelements in the banner.

TABLE 2-1 Banner Elements

Button Description

Returns you to the Sun Java Web Console page.

Displays the File System Manager software release and copyrightinformation.

Refreshes the current page.

Sets the option to prompt you to save information to a temporaryfile instead of committing the action while running a wizard. Formore information, see “Enabling Pop-Up Windows” onpage 13.

Logs you out of the Java Web Console and the current application.

Opens the online help in a separate window.

Status Information

Displays the name and role of the user who is currently logged in tothe software.

Chapter 2 Using the Browser Interface 9

Reference: Content Pane NavigationalElementsThe content pane is located below the banner of the application. It displays reportinformation and enables you to enter data on forms. In addition, you can navigatethrough the pages of the application by using the navigational elements.

The following table describes the navigational elements that are displayed in thecontent pane when you are viewing the File Systems Summary page, the page fromwhich you can start managing file systems.

Displays the name of the management station system that is hostingthe File System Manager software.

Displays the latest time that data was retrieved from the file systemsthat you are administering. The latest data is collected anddisplayed each time you refresh the browser window or perform anaction in the browser.

Displays the current number of each type of unacknowledged faulton the server. There are four fault types:

Down, Critical, Major, and Minor.

For more information about faults, see “About Faults” onpage 47.

TABLE 2-2 Navigational Elements

Navigational Element Description

Current Servermenu

Displays the server for which you are currently viewinginformation. To change the current server, select a new serverfrom the drop-down menu.

Add/RemoveServers link

Displays the Servers page, which provides a summary of theservers that you have added to the browser interface. Clickinga server on the Servers page takes you to the File SystemsSummary page, from which you can manage the file systemson that server.

TABLE 2-1 Banner Elements (Continued)

Button Description


* These tabs are displayed only if the current server has the Sun StorEdge SAM-FSsoftware installed locally.

Reference: Content Pane Icons andButtonsThe following table describes icons and buttons that are commonly displayed onreports and forms in the content pane.

File SystemManagement Tab

Displays the File Systems Summary page, which provides asummary of the file systems that are located on the selectedserver. You can create and administer file systems from thispage. Additionally, you can display detailed reports on thedevices and archive policies of each file system, if they exist.

ArchiveManagement Tab*

Displays the Archive Policies Summary page, which providesa list of the current archive policies for the selected server.From this page you can access local tabs that help youconfigure or manage volume serial name (VSN) pools, diskVSNs, general archiving settings, archiving and stagingactivity, and the recycler.

Media ManagementTab*

Displays the Library Summary page, which provides a list ofthe libraries that are visible to the selected server. From thispage you can create and configure libraries and stand-alonetape drives for archiving.

Jobs Tab Displays the Current Jobs Summary page, which displays thesystem’s current jobs. This page also provides local tabs fromwhich you can view pending jobs and all jobs.

Faults Tab Displays the Fault Summary page, which contains informationabout current fault conditions on the server.

Administration Tab Displays the Server Configuration page.

TABLE 2-3 Icons and Buttons for Reports and Forms

Icon/Button Description

Displays the top of a report or form.

TABLE 2-2 Navigational Elements (Continued)

Navigational Element Description


Displays the part of the report or form thatis indicated by the text next to this icon.

Indicates that the message is an errormessage.

Indicates that the message is a warningmessage.

Indicates that the message is informationalin nature.

Enables you to add the selected object tothe browser interface.

Exits a procedure without applyingchanges.

Closes the selected window or, from theFaults tab, closes the selected faults.

Deletes the selected object from the FileSystem Manager browser interface.

Enables you to modify the selected object.

Creates a new instance of an object.

TABLE 2-3 Icons and Buttons for Reports and Forms (Continued)



About WizardsA wizard is a tool that enables you to perform actions that are composed of multiplesteps, such as creating a policy or file system.

Before you perform an action that opens a wizard, you might want to set preferencesfrom the application window’s banner. For more information, see “Enabling Pop-UpWindows” on page 13.

Enabling Pop-Up WindowsTo use all the functions in the File System Manager application, you must have pop-up windows enabled. By default, the Mozilla web browser blocks pop-up windows.

To enable pop-up windows in the Mozilla web browser:

1. Launch a web browser session.

2. Choose Edit > Preferences.

The Preferences window is displayed.

3. In the Category pane, expand the Privacy & Security node.

Removes the selected object from thebrowser interface.

Sets all page elements to the originalselections that were displayed when thepage was first accessed.

Saves the selections and entries that youhave made.

Applies the sort selections from theAdvanced Sort window to the report table.

TABLE 2-3 Icons and Buttons for Reports and Forms (Continued)



4. In the Privacy & Security expanded list, click Popup Windows.

The Popup Windows settings are displayed in the right pane of the window.

5. Deselect the Block Unrequested Popup Windows check box, and click OK.

6. Close the web browser session and open a new session.

Pop-up windows are enabled in the new browser session.

Changing the Current ServerYou can administer only one server at a time through the browser interface.

To change the current server, do one of the following:

■ From the Servers page, click the name of the server that you want to administer.

The File Systems Summary page is displayed for the newly selected server.

■ From the Site Information page, click the Server Selection tab and click the nameof the server that you want to administer.

The File Systems Summary page is displayed for the newly selected server.

■ From a page other than the Servers or Site Information page, select the server youwant to administer from the Current Server menu.

The information on the page changes to reflect the newly selected server.

About Report TablesCertain reports and forms display report tables. This section provides informationabout how you control the display of tables and sort and filter the information thatis displayed in report tables. It contains the following subsections:

■ “Reference: Report Table Controls” on page 15

■ “Sorting Tables” on page 17

■ “Filtering Tables” on page 17


Reference: Report Table ControlsReport tables have the following controls that enable you to manipulate the displayof the tables and to work with items listed in the tables.

TABLE 2-4 Report Table Controls

Table Control Description

Applies the selected operation to the objects that areselected on the current page of a summary reporttable or to the object displayed on a detailed report.Note: Available operations in this menu vary,depending on the objects that are selected. If you areviewing this from a summary report, and one of theselected objects in the table cannot have a particularoperation applied to it, that operation is disabled inthis menu.

Indicates how many pages are in the report, anddisplays the page you are currently viewing. To viewa different page, type the page number in the Pagefield and click Go.

Enables you to select the entries that you want todisplay. Click the button on the left to display thenext 25 report entries. Click the button on the right todisplay the last 25 report entries.

Enables you to select the entries that you want todisplay. Click the button on the left to display thefirst 25 report entries. Click the button on the right todisplay the previous 25 report entries.

Indicate that the column in the report table is sortedin ascending order. The ascending sort order is bynumber, by uppercase letter, and then by lowercaseletter.A column that has the gray and purple version ofthis icon indicates that this is the table’s currentascending sort order.Click the icon on the left to redisplay the table andre-sort the column in descending order. Click theicon on the right to redisplay the table and changethe table’s current ascending sort order.


Indicate that the column in the report is sorted indescending order. The descending sort order is bylowercase letter, by uppercase letter, and then bynumber.A column that has the gray and purple version ofthis icon indicates that this is the table’s currentdescending sort order.Click the icon on the left to redisplay the table andre-sort the column in ascending order. Click the iconon the right to redisplay the table and change thetable’s current descending sort order.

Enable you to select or deselect all of the check boxeson the current page of the report table. Click the iconon the left to select all of the check boxes. Click theicon on the right to deselect all of the check boxes.

Click to deselect the selected radio button in thereport table.

Opens the Advanced Sort window. Making the tablesort selections and clicking Sort re-sorts the tablewith your selections. The ascending sort order is bynumber, by uppercase letter, and then by lowercaseletter. The descending sort order is by lowercaseletter, by uppercase letter, and then by number.

Enables you to toggle between displaying 1000 tablerows one page at a time, and displaying 25 tablerows one page at a time. When the top icon isdisplayed on a report table, click the icon to pagethrough 1000 rows of data in the table. When thebottom icon is displayed on a report table, click theicon to page through 25 rows of data in the table.

Enables you to display only the information thatinterests you in a report table.

TABLE 2-4 Report Table Controls (Continued)

Table Control Description


Sorting TablesTo sort a report table:

1. Click the Advanced Sort icon ( ) in the table’s banner.

The Advanced Sort window is displayed.

2. Select the columns that you want to sort.

3. Select the sort order you want, and click Sort.

Alternatively, you can sort the information in individual columns in ascending ordescending order by clicking either the purple or white triangle in the columnheading.

Filtering TablesYou can filter the contents of certain report tables so that only the information thatinterests you is displayed.

When filtering tables, keep the following in mind:

■ A filter must have at least one defined criterion.

■ A filter applies to the current server only. You cannot apply a filter to report tablesacross multiple servers.

■ You can use filters with the sorting function to further narrow your results.

To filter a report table, choose the filter criterion from the Filter menu in the table.

Using HelpTo view additional information about the File System Manager software, click Helpin the banner of the File System Manager browser interface. The help windowconsists of a Navigation pane on the left and a Topic pane on the right.


The following table describes the tabs in the help window.

The following table describes the buttons in the help window.

TABLE 2-5 Help Window Tabs

Tab Description

Contents Click a folder icon to display topics and subtopics. Click atopic page icon to display the help page for that topic in theTopic pane.

Index Click the Index tab to display an alphabetized list of subjects.Click an index entry to display the help page for that topic.

Search Type the words for which you want to search in the Searchfield and press Enter or Return. The Navigation pane displaysa list of topics that match your search criteria in order ofrelevancy. Click a topic link to display the help page for thattopic.

TABLE 2-6 Help Window Buttons

Button Description

Click to return to the previous help topic that you wereviewing.

Click to go forward to the next help topic that you viewed inthe current session. This button is enabled only if you haveclicked the Previous button.

Click to print the help topic that is displayed in the right pane.

Click to close the help window.


CHAPTER 3

Getting Started: TaskOverview

The following table provides an overview of the tasks that you can perform to getstarted with the software.

For a brief overview of the software, see “How the Software Works” on page 2.

TABLE 3-1 Getting Started Tasks

Task See This Information

Perform the initial configuration. • “Task Overview: Configuring a Server” on page 21

Monitor the environment. • “Monitoring Servers” on page 27• “Monitoring File Systems” on page 31• “Monitoring Policies” on page 36• “Monitoring Libraries” on page 38• “Monitoring Tape Drives” on page 41• “Monitoring Archiving, Releasing, and Staging Activity” on page 42• “Monitoring Jobs” on page 44• “Monitoring Faults” on page 47

Manage file systems. • “Administering Stand-Alone, Non-archiving File Systems andArchiving File Systems” on page 60

• “Managing Policies for Archiving File Systems” on page 68• “Protecting Archiving File System Data” on page 71• “Administering Shared File Systems” on page 84• “Managing NFS Sharing for File Systems” on page 95

19

Manage libraries (archiving filesystems only).

• “Adding a Library” on page 151• “Changing the State of a Library Drive” on page 156• “Unloading a Library” on page 153• “Deleting a Library” on page 155• “Managing VSNs in a Library” on page 158• “Managing Library Drives” on page 156

Manage stand-alone tape drives(archiving file systems only).

• “Adding a Tape Drive” on page 167• “Reserving a VSN in a Tape Drive” on page 169• “Changing the State of a Tape Drive” on page 170• “Idling a Tape Drive” on page 172• “Auditing a Slot of a Tape Drive” on page 172

Set up and administer archiving(archiving file systems only).

• “Controlling Archiving for Archiving File Systems” on page 109• “Managing VSN Pools for Archiving” on page 131• “Managing Disk VSNs for Archiving” on page 134• “Setting Up General Archiving” on page 136• “Configuring the Recycler” on page 140• “Managing Archiving and Staging Activity” on page 144

Schedule metadata snapshots toprotect file system data.

• “Protecting Archiving File System Data” on page 71• “Scheduling and Taking Metadata Snapshots” on page 72

Perform general configuration ofthe software.

• “Creating a Notification” on page 177

TABLE 3-1 Getting Started Tasks (Continued)

Task See This Information


CHAPTER 4

Performing InitialConfiguration Tasks

This chapter provides information about initial configuration tasks. It contains thefollowing sections:

■ “Task Overview: Configuring a Server” on page 21

■ “Reference: Server Configuration Files” on page 22

■ “Specifying How Configuration Entries Are Saved” on page 23

■ “Adding a Server” on page 24

■ “Removing a Server” on page 26

Task Overview: Configuring aServerWhen you first launch the browser interface, you can add and configure servers forwhich you want to administer file systems. To host and administer archiving filesystems, the servers on which the file systems reside must have the Sun StorEdgeSAM-FS software (SUNWsamfsr and SUNWsamfsu packages) installed locally.Servers with only the Sun StorEdge QFS software (SUNWqfsr and SUNWqfsupackages) installed locally can host and administer only non-archiving file systems.

For information about the file systems that can be managed using the File SystemManager browser interface, see “About Supported File Systems” on page 54.

The following table lists the tasks you must perform to initially configure a serverthrough the browser interface. Complete the configuration tasks in the order listed inthe table.

You must be have the appropriate privileges to perform these tasks.

21

For more information, see “Assigning Administrative Privileges to Users” on page 3.

For information about how these tasks affect the configuration files on a server, see“Reference: Server Configuration Files” on page 22.

Reference: ServerConfiguration FilesWhen you add a server to the browser interface and configure Sun StorEdge QFS filesystems, the File System Manager software creates or edits the appropriate SunStorEdge QFS configuration files on that server. If any file systems are configured to

TABLE 4-1 Initial Configuration Tasks

Task Applicable File System See This Information

1. Add each server to thebrowser interface.

Archiving, non-archiving • “Adding a Server” on page 24

2. If necessary, create a filesystem on each newly addedserver.

Archiving, non-archiving • “About File System Management” on page 51• “About File Systems” on page 53• “Creating a Stand-Alone, Non-archiving or

Archiving File System” on page 61• “Creating a Shared File System” on page 85

3. If you are using libraries,bring the libraries under SunStorEdge SAM-FS softwarecontrol.

Note: This task is notapplicable for sites thatperform disk archiving only.

Archiving • “About Removable Media Management” onpage 147

• “About Supported Libraries and Drives” onpage 149

• “About Archiving” on page 104• “Adding a Library” on page 151

4. (Optional) Create a custompolicy and add the policy’s filematch criteria to the newlycreated archiving file systems.

Archiving • “About Archiving, Releasing, and Staging” onpage 102

• “About Archive Policies” on page 112• “Creating a Policy” on page 116• “Adding Existing File Match Criteria to an

Archiving File System” on page 69

5. Schedule the creation ofmetadata snapshots for anynewly created archiving filesystems.

Archiving • “About Metadata Snapshots” on page 72• “Scheduling the Creation of Metadata

Snapshots” on page 74


be archiving, the File System Manager software also creates or edits the appropriateSun StorEdge SAM-FS configuration files. You can use the command-line interfacefor the file systems to further edit these files later.

The following table describes the browser interface actions that affect the SunStorEdge QFS and Sun StorEdge SAM-FS configuration files on the server.

Specifying How ConfigurationEntries Are SavedYou can specify whether you want to be prompted to save your configuration entriesto a temporary file when performing a procedure through a wizard. When you firstrun a wizard, new configuration files (mcf, samfs.cmd, archiver.cmd) are created

TABLE 4-2 Browser Interface Actions and their Effect on Files and Commands

Browser Interface Action Affected Configuration File or Files Associated Man Commands

Create, edit, grow, or remove a filesystem.

• mcf

• samfs.cmd

• /etc/vfstab

• mcf(4)• samfs.cmd(4)

• vfstab(4)

If you are using libraries, add thelibrary and bring the library underSun StorEdge SAM-FS softwarecontrol or remove the library fromSun StorEdge SAM-FS softwarecontrol.

• mcf

• samst.conf

Note: If the library is a smallcomputer system interface (SCSI)direct-attached library and itstarget number is larger than 6 orits logical unit number (LUN)identifier is larger than 1, thesoftware does not update thesamst.conf file. In this situation,you must manually configure thesamst.conf file.

• mcf(4)

• samst.conf(4)

Create, edit, or delete archivepolicies, and apply a policy to anarchiving file system.

• archiver.cmd

• diskvols.conf

• archiver.cmd(4)

• diskvols.conf(4)

Make configuration changes onthe General Setup page under theArchive Management tab.

• stager.cmd

• recycler.cmd

• releaser.cmd

• stager.cmd(4)

• recycler.cmd(4)

• releaser.cmd(4)

Schedule or take a metadatasnapshot and restore files from thesnapshot.

/var/spool/cron/crontabs/root

crontab(1)

Chapter 4 Performing Initial Configuration Tasks 23

on the selected server. Saving your entries to a temporary file enables you topreserve configuration files that already exist on that server. For example, thisenables you to save comments that might exist in a configuration file.

To set preferences for configuration entries:

1. In the banner, click Preferences.

2. Do one of the following:

■ Select the check box – Wizards will prompt you to save your entries to atemporary file, which enables you to save your entries without committingthem to the configuration. You can choose the directory in which to save thefile.

■ Deselect the check box – While the wizard is running, wizard entries will becommitted to new configuration files on the selected server. You will not beprompted to save your entries to a temporary file.

3. Click Submit.

If you selected the check box and then configure a file system through the browserinterface, information is saved in one or more of the following files, depending onthe wizard you are running:

■ archiver.cmd.dump

■ mcf.dump

■ samfs.cmd.dump

These files are saved in the directory that you choose. You can use them later tomanually edit system configurations.

Adding a ServerAdding a server enables you to administer its file systems, archiving processes,media, and so on, through the browser interface.

To add a server:

1. Outside of the browser interface, use telnet to connect to the server.

2. Log in to the server as root.

3. Use the fsmadm(1M) add command to add the management station (the systemon which the File System Manager software is installed) to the list of hosts thatcan remotely administer the server.

fsmadm add management-station-name:domain-name


Only hosts that are added to the list through this command can remotelyadminister the server.

4. To ensure that the management station has been successfully added, use thefsmadm(1M) list command.

5. Launch a browser window and log in to the File System Manager browserinterface as an administrator user.

6. Perform either of the following:

■ If the Servers page is displayed, click Add.

■ If any other page is displayed, click Add/Remove Servers to go to the Serverspage and click Add.

The Add Server window is displayed.

7. Type the name of the server or type the IP address of the server in the ServerName field or IP Address field.

8. Click OK.

9. If you typed the name or address of a server that is part of a Sun Clusterenvironment, a list of the other nodes in the cluster is displayed. Select the othernodes to also add them as managed servers for a HA (highly available)-QFSconfiguration.

Note: To create an HA-QFS configuration, you must also use the Sun Clustermanagement tool, SunPlex Manager, to configure the devices as part of a SunCluster resource group. File System Manager includes ha in the description of filesystems that are configured on cluster devices even if the devices are not part of aresource group and the file systems are not therefore truly highly-available.

This option is available only if the servers have either of the following packagesinstalled locally:

■ Release 4, update 5, SUNWsamfsr and SUNWsamfsu packages

■ Release 4, update 5, SUNWqfsr and SUNWqfsu packages

When you add a server, the software detects any file systems that are alreadyconfigured on the server. These file systems are automatically displayed on the FileSystems Summary page.

If no file systems have already been created on the server, you can create andconfigure a new file system.

For more information, see “Creating a Stand-Alone, Non-archiving or Archiving FileSystem” on page 61.

Chapter 4 Performing Initial Configuration Tasks 25

Removing a ServerIf you no longer want to administer the file systems on a server through the browserinterface, you can manually remove the server.

Note: Removing a server does not uninstall any software from the server. It onlycauses the server to no longer be displayed in the browser interface.

To remove a server from the browser interface:

1. Perform either of the following:

■ If the Servers page is displayed, select the radio button next to the server thatyou want to remove and click Remove.

■ If any other page is displayed, click Add/Remove Servers to go to the Serverspage, select the radio button next to the server that you want to remove, andclick Remove.

A message box prompts you to confirm the removal.

2. Click OK.

3. If you want to permanently disable remote administration of the server from themanagement station, do the following:

a. Outside of the browser interface, use telnet to connect to the server.

b. Log in to the server as root.

c. Use the fsmadm(1M) remove command to remove the management stationfrom the list of hosts that can remotely manage the server.

fsmadm remove management-station-name.domain-name

d. To verify that the management station has been removed, use the fsmadm(1M)list command.


CHAPTER 5

Monitoring theEnvironment

This chapter provides information about monitoring your environment. It containsthe following sections:

■ “Monitoring Servers” on page 27

■ “Monitoring File Systems” on page 31

■ “Monitoring Policies” on page 36

■ “Monitoring Libraries” on page 38

■ “Monitoring Tape Drives” on page 41

■ “Monitoring Archiving, Releasing, and Staging Activity” on page 42

■ “Monitoring Jobs” on page 44

■ “Monitoring Faults” on page 47

Monitoring ServersThis section provides information about monitoring servers. It contains thefollowing subsections:

■ “Displaying the Configuration of Servers in Your Site” on page 28

■ “Displaying the Configuration of a Server” on page 28

■ “Displaying Software Packages on a Server” on page 28

■ “Displaying Log or Trace Files on a Server” on page 29

■ “Displaying Configuration Files on a Server” on page 29

■ “Displaying Warning Messages in Server Files” on page 30

27

■ “Displaying the Minimum Server Release Supported by File System Manager” onpage 30

Displaying the Configuration of Serversin Your SiteYou can view configuration information about all servers in your site.

If at least one server is hosting archiving file systems, you can view the mediadevices that can be used for archiving.

To display configuration information about the servers in your site:

■ From the Servers page, click the Site Information tab. The Site Information pagelists the servers and their media devices.

Displaying the Configuration of a ServerYou can view configuration information about an individual server, such as its log ortrace files, packages and so on.

To display configuration information about a server:

1. From the Servers page, select the radio button next to the server for which youwant to view configuration information.

2. Click View Configuration.

The Server Configuration page is displayed.

Displaying Software Packages on aServerTo display the software packages that are installed locally on a server:

1. From the Servers page, select the radio button next to the server for which youwant to view its software packages.




3. Scroll down to the Packages section.

The table lists any File System Manager, Sun StorEdge QFS, and Sun StorEdgeSAM-FS software packages that are installed on the server.

Displaying Log or Trace Files on a ServerYou can view the contents of the Sun StorEdge QFS and Sun StorEdge SAM-FS logand trace files on the current server. This is useful when a fault condition occurs andyou want to investigate its cause.

To view the contents of a log or trace file:

1. From the Servers page, select the radio button next to the server for which youwant to view log or trace files.



3. Scroll down to the Log and Trace section and click the path name of the log ortrace file that you want to view.

A window is displayed that enables you to view the contents of the selected file.This window automatically refreshes so that the latest information in the file isdisplayed.

Displaying Configuration Files on aServerYou can view the contents of the Sun StorEdge QFS and Sun StorEdge SAM-FSconfiguration files on the current server.

To view the contents of a configuration file:

1. From the Servers page, select the radio button next to the server for which youwant to view configuration files.

Chapter 5 Monitoring the Environment 29



3. Scroll down to the Configuration Files Status section and click the path name ofthe configuration file that you want to view.

A window is displayed that enables you to view the contents of the selected file.This window automatically refreshes so that the latest information in the file isdisplayed.

Displaying Warning Messages in ServerFilesYou can display warning messages for a server.

If there are warning messages related to a Sun StorEdge QFS or Sun StorEdge SAM-FS configuration file on a server, the configuration file is displayed as a link in thebrowser interface.

To display the warning messages related to a server configuration file:

1. From the Servers page, select the radio button next to the server for which youwant to view configuration file warning messages.



3. Scroll down to the Configuration File Status section and click the configurationstatus of the file that you want.

A window is displayed that lists the warning messages related to theconfiguration file.

Displaying the Minimum Server ReleaseSupported by File System ManagerThe features and functionality supported through the browser interface depend onthe release level of the Sun StorEdge QFS and Sun StorEdge SAM-FS softwareinstalled locally on a server.


To display the minimum server release supported by the browser interface:

■ From the Servers page, click the release and update level in the Release column ofthe table. The File System Manager Release Highlights page is displayed.

This page lists the features and functionality available through the browserinterface.

Monitoring File SystemsThis section provides information about monitoring file systems. It contains thefollowing subsections:

■ “Displaying the Status of a File System” on page 31

■ “Displaying File System Devices” on page 32

■ “Displaying NFS Shared Directories in a File System” on page 32

■ “Displaying File Match Criteria for an Archiving File System” on page 33

■ “Displaying the Status of Metadata Snapshot Activities” on page 33

■ “Displaying the Status of a Restore Process for an Archiving File System” onpage 34

■ “Displaying the Metadata Server for a Shared File System” on page 35

■ “Displaying All Hosts in a Shared File System” on page 35

Displaying the Status of a File SystemTo display the status of a file system:

1. From the Servers page, click the name of the server on which the file system islocated.

The File Systems Summary page is displayed.

2. To display a specific file system, page through the table until the specified filesystem is displayed, or filter the table so that the file system that meets the filtercriteria is displayed.

3. View the information in the columns to determine whether the file system ismounted, whether it is shared, how much space is consumed, and so on.


Displaying File System DevicesTo display the devices on a file system:



2. On the File Systems Summary page, click the name of the file system that containsthe devices you want to view.

The File System Details page is displayed.

3. If you are displaying the device of a UFS file system, review the Device Namefield. Otherwise, click View Devices.

The Devices page for that file system is displayed.

Displaying NFS Shared Directories in aFile SystemYou can display network file system (NFS) directories that are shared out to thenetwork from a local file system.

To display the network file system (NFS) shared directories in a file system:



2. On the File Systems Summary page, select the radio button next to the file systemfor which you want to view NFS directories.

3. From the Operations menu, choose Edit NFS Properties.

The File System NFS Properties page is displayed.

4. Scroll down to the NFS Shared Directories table to view the NFS shareddirectories in the file system.


Displaying File Match Criteria for anArchiving File SystemFile match criteria are defined in a policy and can be applied to an archiving filesystem. When the files in the archiving file system meet the file match criteriadefined in the policy, the files are eligible to be archived.

To display the sets of file match criteria that are applied to an archiving file system:

1. From the Servers page, click the name of the server on which the archiving filesystem is located.


2. Select the radio button next to the archiving file system for which you want toview file match criteria, and click View Policies.

The File System Archive Policies page displays the policy and file match criteriacombinations that apply to this archiving file system.

3. To view details about a set of file match criteria, do the following:

a. Click the name of the policy.

The Policy Details page for the selected policy is displayed.

b. Click the file match criteria that you want to view.

The Policy Criteria Details page is displayed.

Displaying the Status of MetadataSnapshot ActivitiesTo display the status of a metadata snapshot-related activities on a server:

1. From the Servers page, click the name of the server for which you want to displaythe status of a metadata snapshot.

2. Click the Jobs tab.

The Current Jobs Summary page is displayed.


3. From the Filter menu, choose one of the following:

■ Create Metadata Snapshot – When a snapshot is taken on demand, this jobenables you to view the status of the snapshot being created.

■ Create Metadata Snapshot Index – When you want to restore a file fromarchive media, you might need to create a search index for the file, and movethe file onto disk so you can browse through it. This job enables you to viewthe status of these processes.

■ Metadata Snapshot Search – When you want to restore a file, you might needto search through the metadata snapshot file to find the file you want torestore. This job enables you to view the status of the search process.

4. (Optional) To display more detailed information about a metadata snapshot job,click its job ID.

Displaying the Status of a RestoreProcess for an Archiving File SystemIn the event of a disaster, you can restore lost files from archive media to online diskcache of an archiving file system.

To display the status of a restore process for an archiving file system:

1. From the Servers page, click the name of the server for which you want to displaythe status of a file restore process.



3. Choose whether you want to display current, pending, or all restore filesprocesses by clicking the appropriate local tab under the Jobs tab.

4. From the Filter menu, choose Restore.


Displaying the Metadata Server for aShared File SystemTo display the metadata server for a shared file system:

1. From the Servers page, click a server on which the shared file system isconfigured.


2. Click the shared file system for which you want to display the metadata server.



■ If the current server is acting as a client for the shared file system, scroll downto the Server field to view the metadata server.

■ If the current server is acting as a potential metadata server or as the metadataserver, the Participating Hosts table is displayed. Look at the values in the Typecolumn to determine which server is acting as the metadata server.

Displaying All Hosts in a Shared FileSystemTo display all participating hosts in a shared file system:

1. From the Servers page, click the name of the server that is acting as the metadataserver or as the potential metadata server for the shared file system.


2. From the File Systems Summary page, click the name of the shared file system forwhich you want to view hosts.


3. Look at the Participating Hosts table to view all participating hosts in the sharedfile system.


Monitoring PoliciesThis section provides information about monitoring policies. It contains thefollowing subsections:

■ “Displaying File Match Criteria in a Policy” on page 36

■ “Displaying File Systems Using Specific File Match Criteria” on page 37

■ “Displaying the Copy Details of a Policy” on page 37

■ “Displaying the VSNs Assigned to a Policy Copy” on page 38

Displaying File Match Criteria in a PolicyYou can display the details of a specific set of file match criteria that is defined in apolicy. When files meet the file match criteria specified in the policy, the files areeligible for archiving.

To display file match criteria in a policy:

1. From the Servers page, click the name of the server that is configured with thepolicy that you want to view.


2. Click the Archive Management tab.

The Archive Policies Summary page is displayed.

3. Click the name of the policy for which you want to view file match criteria.

The Policy Details page lists the file match criteria that is defined in the policy.

4. If you want to view the details of a specific set of file match criteria, click thename of the set.



Displaying File Systems Using SpecificFile Match CriteriaFile match criteria can be applied to numerous archiving file systems.

To display the archiving file systems to which a selected set of file match criteriaapplies:





3. Click the policy that you want to view.


4. Click the file match criteria that you want to view.


5. Scroll down the page to the File Systems Using Criteria section.

A list of file systems that use the selected file match criteria is displayed.

Displaying the Copy Details of a PolicyTo display the copy details of a policy:





3. Click the name of the policy that you want to view.



4. Scroll down to the Copy Information section and click a copy number.

The Policy Copy (Tape) Details or the Policy Copy (Disk) Details page isdisplayed.

Displaying the VSNs Assigned to aPolicy CopyA policy copy defines the volumes or pool of volumes to which an archive copy of afile can be sent. A volume serial name (VSN) identifies a volume.

To display the VSNs and VSN pools of a policy copy:





3. In the table, click the name of the policy for which you want to display VSNinformation.


4. Scroll down the page to the Copy Information section and click the VSNs listed inthe VSNs Available field for a specified copy.

The Policy Copy VSNs page lists the VSNs in the Available VSNs field.

Monitoring LibrariesThis section provides information about monitoring libraries. It contains thefollowing subsections:

■ “Displaying VSNs for a Library” on page 39

■ “Displaying the Drives in a Library” on page 39

■ “Displaying the Status and State of a Library” on page 40

■ “Displaying Historian Catalog Information” on page 40

■ “Displaying Mount Requests in a Library” on page 41


Displaying VSNs for a LibraryVolume serial names (VSNs) are the named volumes associated with a selectedlibrary.

To display VSN information for a library:

1. From the Servers page, click the name of the server on which the file system thatyou want is located.


2. Click the Media Management tab.

The Library Summary page is displayed.

3. Select the radio button next to the library that you want to view, and click ViewVSNs.

The VSN Summary page for the selected library is displayed.

4. For information about a VSN, click the name of the VSN.

The VSN Details page for the selected VSN is displayed.

Displaying the Drives in a LibraryTo display the drives in a library:

1. From the Servers page, click the name of the server that you want to monitor.




3. Select the radio button next to the library that is configured with the drives thatyou want to view, and click View Drives.

The Drives Summary page for the selected library is displayed.


Displaying the Status and State of aLibraryYou can determine the status and state of libraries through the browser interface.The status indicates whether any fault alarms are present. The state indicateswhether the library is on, off, or unavailable.

To display the status and state of a library:




3. View the State column to see the state of the library.

4. View the Faults column to see the status of the library.

If the library is in a fault condition, click the corresponding fault icon to displaythe Fault Summary page for that library.

Displaying Historian CatalogInformationThe Historian is a catalog that keeps track of volumes that have been exported froman automated library or that have been unloaded from manually loaded devices.

To display the Historian catalog:





3. Click Historian.

The Historian page is displayed.


Displaying Mount Requests in a LibraryTo display mount requests:





3. Choose whether you want to display current, pending, or all media mountrequests by clicking the appropriate local tab under the Jobs tab.

4. To view all media mount request jobs, choose Media Mount Request from theFilter menu.

5. (Optional) To display more detailed information about a media mount requestjob, click its job ID.

Monitoring Tape DrivesThis section provides information about monitoring tape drives. It contains thefollowing subsections:

■ “Displaying the VSN for a Tape Drive” on page 41

■ “Displaying the State of a Stand-Alone Tape Drive” on page 42

Displaying the VSN for a Tape DriveThe media cartridge in a stand-alone tape drive contains a single volume. A volumeserial name (VSN) identifies a volume.

To display the VSN for a tape drive:






3. Click the Stand-Alone Tape Drives local tab.

The Stand-Alone Tape Drives Summary page is displayed. The VSN that isassociated with a tape drive is displayed in the same row as the drive number.

4. To display more details about the VSN, click the VSN name.

The VSN Details page is displayed.

Displaying the State of a Stand-AloneTape DriveYou can display the state of a stand-alone tape drive from the Media Managementtab. The drive states can be on, off, or unavailable.

To display the status of a stand-alone tape drive:

1. From the Servers page, click the name of the server that is configured with thestand-alone tape drive that you want to view.




The Stand-Alone Tape Drives Summary page is displayed.

4. View the State column information for the stand-alone tape drive.

Monitoring Archiving,Releasing, and Staging ActivityIf you are managing a server that is hosting the Sun StorEdge SAM-FS software, youcan monitor the current archiving, staging, and releasing activity for any archivingfile systems on the server. This section provides information on completing thesetasks. It contains the following subsections:

■ “Displaying Archiving Activity” on page 43

■ “Displaying Releasing Activity” on page 43

■ “Displaying Staging Activity” on page 44


Displaying Archiving ActivityYou can view the archiving activity of archiving file systems on the current server.

To display archiving activity:

1. From the Servers page, click the name of the server for which you want to displayarchiving activity.



3. Choose whether you want to display current, pending, or all archiving activity byclicking the appropriate local tab under the Jobs tab.

4. From the Filter menu, choose Archive Copy or Archive Scan to view all jobs ofeither type.

5. (Optional) To display more detailed information about an archive job, click its jobID.

Displaying Releasing ActivityYou can view the releasing activity of archiving file systems on the current server.

To display releasing activity:

1. From the Servers page, click the name of the server for which you want to displayreleasing activity.



3. Choose whether you want to display current, pending, or all releasing activity byclicking the appropriate local tab under the Jobs tab.

4. To view all releasing jobs, choose Release from the Filter menu.

5. (Optional) To display more detailed information on a release job, click its job ID.


Displaying Staging ActivityYou can view the staging activity of archiving file systems on the current server.

To display staging activity:

1. From the Servers page, click the name of the server for which you want to displaystaging activity.



3. Choose whether you want to display current, pending, or all staging activity byclicking the appropriate local tab under the Jobs tab.

4. To view all staging jobs, from the Filter menu, choose Stage.

5. (Optional) To display more detailed information about a stage job, click a job ID.

Monitoring JobsThis section provides information about monitoring jobs. It contains the followingsubsections:

■ “About Jobs” on page 44

■ “Displaying Jobs” on page 46

■ “Canceling a Job” on page 46

About JobsJobs are generated when you perform an action through the browser interface orwhen the server system performs a process. Some jobs are generated and completedso quickly that you might not ever see the job on the Jobs tab.

All jobs in the browser interface, with the exception of the File System Check job, aregenerated only if the current server has the SUNWsamfsr and SUNWsamfsu packagesinstalled locally.


The following table describes the different types of jobs.

The categories by which you can display jobs are as follows:

■ Current – Jobs that are running.

■ Pending – Jobs that are scheduled to run.

■ All – Both current and pending jobs.

TABLE 5-1 Job Types

Job Description

Tape Label A volume is being labeled or relabeled.

Archive Scan The archiver is scanning directories for files to bearchived.

Release The releaser is freeing up disk cache after an archivecopy is made.

Archive Copy The archiver is archiving the file.

File System Check The file system is being checked and repaired.

Stage The stager is copying file data to the disk cache.

Create Metadata Snapshot The software is taking a snapshot of the metadata of anarchiving file system.

Create Metadata SnapshotIndex

The software is performing at least one of the followingactions, as necessary:• Moving the metadata snapshot file from removable

media to online disk• Decompressing the metadata snapshot file• Creating a search index for the metadata snapshot file

Metadata Snapshot Search The software is searching the metadata snapshot file forfiles to restore.

Restore The software is reviewing the pointers to the archivelocations of files or directories on archive media. Inaddition, the files or directories might optionally berestored to online disk, depending on how you initiatedthe restore job.

Media Mount Request You have manually requested that media be mounted.


Displaying JobsTo display jobs:

1. From the Servers page, click the name of the server for which you want to viewjobs.



The Current Jobs Summary page lists all currently running jobs.

3. Choose whether you want to display current, pending, or all jobs by clicking theappropriate local tab under the Jobs tab.

4. (Optional) To display detailed information about a specific job, click its job ID.

The Details page for that job is displayed.

Canceling a JobYou can cancel certain jobs, depending on whether they are current or pending.Some jobs can only be in the current or pending state, not both. This is indicated bythe NA (not applicable) values in the following table.

TABLE 5-2 Job Cancellation Options

Job TypeCan Cancel In CurrentState?

Can Cancel In PendingState?

Archive Copy Yes No

Archive Scan Yes No

Stage Yes Yes

Release No NA

Media Mount Request NA Yes

Create Metadata Snapshot Yes NA

Create Metadata Snapshot Index Yes NA

Metadata Snapshot Search Yes NA

Restore Yes NA


To cancel a job:

1. From the Servers page, click the name of the server for which you want to cancela job.



3. Use the Filter menu or navigate through the table to find the job that you want tocancel.

4. Select the radio button next to the job and click Cancel.

A window is displayed that confirms your cancellation.

5. Click OK.

Monitoring FaultsThis section provides information about monitoring faults. It contains the followingsubsections:

■ “About Faults” on page 47

■ “Displaying Faults” on page 48

■ “Acknowledging Faults” on page 49

■ “Deleting Faults” on page 49

About FaultsFaults are displayed in the browser interface when situations occur that meet thefault criteria defined by the Sun StorEdge QFS and Sun StorEdge SAM-FS softwareinstalled locally on the current server.

File System Check Yes NA

Note: The File System Check job cannot be canceled if the Repair option isspecified when the job is initiated.

Tape Label No NA

TABLE 5-2 Job Cancellation Options (Continued)

Job TypeCan Cancel In CurrentState?

Can Cancel In PendingState?


You can acknowledge and delete all faults on the system at one time by clicking theScroll Through All Data icon on the Fault Summary page. After you click this icon,you can select all faults and then click Acknowledge or Delete.

If a fault condition is discovered more than once by the software, the number oftimes it has been discovered and the initial time it was discovered are displayed inthe browser interface:

No space available. Repeated 3 times since Mon Apr 18, 20052:09 p.m.

The following table describes the fault severities.

Displaying FaultsTo display faults:

1. From the Servers page, click the name of the server for which you want to viewfaults.


2. Click the Faults tab.

The Faults Summary page lists the faults on that server.

TABLE 5-3 Fault Severities

Severity Level Description

Down Indicates that the File System Manager software cannot reach theserver or object. This might be due to a faulty network connection, apower outage, and so on. Down faults are only displayed on theServers page. For more information about possible causes for thisfault condition, see “Inaccessible Server” on page 183.

Critical Indicates a critical fault condition, such as a superblock countmismatch or a library being unavailable. This is a very seriouscondition and requires some administrative action.

Major Indicates a major fault condition, such as a library being full. This isa serious condition and requires some administrative action.

Minor Indicates a minor fault condition, such as a tape drive needing to becleaned, or a library needing to be maintained. This is a seriouscondition, but you can choose whether to perform someadministrative action.


3. (Optional) To display more detailed information about a device that is in a faultcondition, click the device name.

The Device Fault Summary page for that device is lists the faults for that device.

Acknowledging FaultsYou can optionally acknowledge a fault to inform other administrators that you areaddressing the fault condition.

To acknowledge a fault:

1. From the Servers page, click the name of the server for which you want toacknowledge a fault.



The Faults Summary page is displayed.

3. Select the check box next to the fault that you want to acknowledge, and clickAcknowledge.

Acknowledged is displayed in the State field for the fault.

Deleting FaultsFaults are automatically deleted upon reaching a system-defined threshold.However, you can also manually delete faults.

To delete a fault:

1. From the Servers page, click the name of the server for which you want to deletea fault.


The Fault Summary page is displayed.

3. Select the checkbox next to the fault that you want to delete, and click Delete.

A message box prompts you to confirm your choice.

4. Click OK.


CHAPTER 6

Managing File Systems

This chapter provides information about managing file systems. It contains thefollowing sections:

■ “About File System Management” on page 51

■ “About Discovering Available Devices” on page 52

■ “About File Systems” on page 53

■ “Administering Stand-Alone, Non-archiving File Systems and Archiving FileSystems” on page 60

■ “Managing Policies for Archiving File Systems” on page 68

■ “Protecting Archiving File System Data” on page 71

■ “Administering Shared File Systems” on page 84

■ “Managing NFS Sharing for File Systems” on page 95

About File SystemManagementYou can perform the following file system-level operations through the browserinterface:

■ Create Sun StorEdge QFS file systems and configure them to be stand-alone,archiving, or shared.

■ Create non-archiving HA (highly available) shared or stand-alone Sun StorEdgeQFS file systems on nodes within a Sun Cluster configuration.

51


This option is available only if the servers have either of the following packagesinstalled locally:

■ Release 4, update 5, SUNWsamfsr and SUNWsamfsu

■ Release 4, update 5, SUNWqfsr and SUNWqfsu

■ Create Sun StorEdge SAM-FS file systems, which are automatically configured tobe archiving.

■ Create stand-alone UFS file systems.

■ Add clients and potential metadata servers to and remove them from shared filesystems.

■ Grow Sun StorEdge SAM-FS file systems and grow stand-alone and archiving SunStorEdge QFS file systems.

■ Check and repair Sun StorEdge SAM-FS file systems and check and repair stand-alone and archiving Sun StorEdge QFS file systems.

■ Mount and unmount stand-alone, shared, and archiving file systems.

■ Mount and unmount VERITAS file systems (VxFS).

■ Edit the network file system (NFS) properties of file systems that use the NFSservice.

■ Control archiving for archiving file systems.

■ Manage archive policies for archiving file systems.

■ Protect the data of mounted archiving file systems.

If file systems already exist on the current server, they are automatically displayedon the File Systems Summary page.

About Discovering AvailableDevicesWhen you create or grow a file system, the File System Manager software attemptsto discover available devices that can be used in the process.

The software discovers available devices on formatted disks that are properlylabeled. SMI and EFI labels are supported. A device is considered unavailable if itmeets any of the following restrictions:


■ Its size is equal to zero.

■ It is listed in the /etc/vfstab file.

■ It is listed in the selected server’s mcf file.

■ It starts at sector 0. Because of this, s2 is excluded for disks that use the defaultSolaris™ Operating System formatting scheme.

■ It cannot be opened in exclusive-read mode, which eliminates slices or volumesthat are used by mounted file systems.

■ It is used by a Solaris Volume Manager volume or by a metadb process.

■ It is used by a VERITAS Volume Manager volume.

Caution: A device is also unavailable if another host is using the device. However,the browser interface lists such devices as available. You are responsible for knowingwhich shared devices are being used by other hosts.

There might be additional circumstances under which the devices listed as availablein the browser interface are actually unavailable. For example, the browser interfacemay list devices as available because the software expects disks to be partitionedwithout overlapping slices, or because the software was unable to invoke volumemanager commands when performing discovery.

If you need to format a disk, use the format(1M) command outside of the browserinterface. If you use the format(1M) command, you are responsible for determiningwhether devices on the disk are in use.

About File SystemsThis sections provides information about file systems. It contains the followingsubsections:

■ “About Supported File Systems” on page 54

■ “About Stand-Alone, Non-archiving File Systems” on page 56

■ “About Archiving File Systems” on page 57

■ “About Shared File Systems” on page 58

■ “About HA-QFS File Systems” on page 59

Chapter 6 Managing File Systems 53

About Supported File SystemsFile systems can be stand-alone, non-archiving file systems, archiving file systems, orshared file systems. Through the browser interface, stand-alone, non-archiving SunStorEdge QFS file systems can be configured to use storage and archivingmanagement software (Sun StorEdge SAM-FS software) to become archiving filesystems. By default, Sun StorEdge SAM-FS file systems are automatically archivingfile systems through the browser interface.

You can configure Sun StorEdge QFS on Sun Cluster nodes for a stand-alone orshared, non-archiving, HA (highly available) file system. This configuration isavailable if the servers have either of the following packages installed locally:





You can create and administer the following file systems through the browserinterface, based on the packages installed on the server.

TABLE 6-1 Supported File Systems

Packages Product File Systems Archive? Share? Notes

• SUNWsamfsr

• SUNWsamfsu

• Sun StorEdgeQFS

• Sun StorEdgeSAM-FS

Yes Yes, but only SunStorEdge QFS filesystems

Remote or localmanagement ofthese file systemsis supported.

• SUNWqfsr

• SUNWqfsu

Sun StorEdge QFS No Yes Remote or localmanagement ofthis file system issupported.

Either:• UFS software

package, which isincluded in Solaris

• SUNWsamfsr

• SUNWsamfsu

Or:• UFS software

package, which isincluded in Solaris

• SUNWqfsr

• SUNWqfsu

UFS No No

Either:• VERITAS file system

software package• SUNWsamfsr

• SUNWsamfsu

Or:• VERITAS software

package• SUNWqfsr

• SUNWqfsu

VERITAS No No


About Stand-Alone, Non-archiving FileSystemsStand-alone, non-archiving file systems are file systems that are not distributed andthat do not use the storage and archiving software (Sun StorEdge SAM-FS software)to archive files.

The stand-alone, non-archiving file systems that are supported by the browserinterface are the Sun StorEdge QFS, UFS, and VERITAS file systems.

For information about the packages required on a server in order for it to host stand-alone, non-archiving file systems, see “About Supported File Systems” on page 54.

This topic describes the Sun StorEdge QFS file system. For information about theUFS file system or the VERITAS file system, see the product documentation for thosefile systems.

The stand-alone, non-archiving Sun StorEdge QFS file system is a high-performanceUNIX file system that enables you to store metadata on separate devices from filedata.

Advantages of storing metadata on one or more devices separate from file data isthat it reduces device head movement and rotational latency, improves RAID cacheutilization, and enables the mirroring of metadata without the mirroring of file data.

Sun StorEdge QFS file systems are virtually unlimited with regard to file size, thenumber of files that can reside in a file system, and the number of file systems thatyou can create on a server.

These file systems support files up to 263 bytes in length. Such large files can bestriped across many disks or RAID devices, even within a single file system. This isbecause Sun StorEdge QFS file systems use true 64-bit addressing. A typical UFS filesystem is not a true 64-bit file system.

You can configure Sun StorEdge QFS file systems to support multiple RAID devicesby defining striped groups in the file systems. Disk block allocation can beoptimized for a striped group, reducing the overhead for updating the on-diskallocation map. You can assign a file to a striped group.

The number of Sun StorEdge QFS file systems you can configure on a server isunlimited. The volume manager enables each file system to include up to 252 devicepartitions (typically disk). Each partition can include up to 1 terabyte of data.


There is no predefined limit for the number of files on a Sun StorEdge QFS filesystem. This is because the inode space, which holds information about files, isdynamically allocated. Therefore, the maximum number of files is limited only bythe amount of disk storage consumption in the file system.

If you want to configure the file system for archiving, there are guidelines to followso that you don’t overextend your environment.

For more information, see “About Archiving, Releasing, and Staging” on page 102.

For more detailed information about the Sun StorEdge QFS file system, see the SunStorEdge QFS Software Installation and Upgrade Guide.

About Archiving File SystemsArchiving file systems are file systems that use the Sun StorEdge SAM-FS softwareto archive files. You can restore files and the file systems themselves from remotemedia, in the event of a disaster. You can also manage the libraries or stand-alonetape drives that contain archive copies of the files.

The browser interface supports the creation and management of the Sun StorEdgeSAM-FS and the Sun StorEdge QFS file systems as archiving file systems.

For information about the packages required on a server in order for it to hostarchiving file systems, see “About Supported File Systems” on page 54.

You create a Sun StorEdge SAM-FS file system through the browser interface byselecting the Metadata and Data on Same Device option in the New File Systemwizard. By default, this creates an archiving Sun StorEdge SAM-FS file system. Thisfile system stores metadata and file data on the same devices and can never beconfigured as shared. This file system is labeled as “qfs - archiving” in the browserinterface.

You create an archiving Sun StorEdge QFS file system through the browser interfaceby selecting the Metadata and Data on Separate Devices option and the Archive ThisFile System option in the New File System wizard. This automatically configures thefile system to use the Sun StorEdge SAM-FS software for archiving files.

With archiving file systems, the file systems can read and write files directly frommagnetic disk, or can access archive copies of files as if the files were all on primarydisk storage.

When managing archiving file systems through the browser interface, the ArchiveManagement and the Removable Media navigational tabs are displayed. From thesetabs, you can configure how, where, and when to archive files.


For recommendations about configuring archiving based on your environment, see“About Archiving, Releasing, and Staging” on page 102.

For information about the Sun StorEdge SAM-FS and Sun StorEdge QFS file systems,see the Sun StorEdge SAM-FS Software Configuration and Administration Guide and theSun StorEdge QFS Software Configuration and Administration Guide.

About Shared File SystemsShared file systems are file systems that are distributed on multiple hosts. Theadvantage of a shared file system is that file data is passed directly from the FibreChannel disks to the hosts. Data travels by way of local path I/O (direct access I/O).This is in contrast to the network file system (NFS) service, which transfers data overthe network.

The browser interface supports the creation and management of the Sun StorEdgeQFS file system as a shared file system.

For information about the packages required on the server in order for it to hostshared file systems, see “About Supported File Systems” on page 54.

You configure a Sun StorEdge QFS file system to be shared by selecting the Sharedoption in the New File System wizard. When you configure the Sun StorEdge QFSfile system to be shared, you configure it to be a distributed file system that can bemounted on multiple host systems. One host acts as the metadata server for the filesystem, and additional hosts act as clients.

More than one host can be configured as a potential metadata server, but only onehost can be configured as the metadata server at any one time. There is no limit tothe number of shared file system mount points.

Note: When you create a shared file system through the browser interface, thesoftware updates the hosts configuration for the file system. However, the softwaredoes not create or update the hosts.family-set-name file for the file system.

If you want to create the hosts.family-set-name file, see “Creating the Shared HostsFile” on page 86.

The shared file system does not support the following file types:

■ Blocked special files

■ Character special files

■ FIFO (named pipe) special files

Through the browser interface, you can perform the following tasks for a shared filesystem:


■ Create a metadata server for a new file system.

■ Add clients to an existing file system.

■ Add a potential metadata server to an existing file system.

■ Mount or unmount the metadata server and the clients.

■ Change mount options.

■ Delete a client.

■ Delete the metadata server.

All other operations related to shared file systems must be performed outside of thebrowser interface. For more detailed information about the shared Sun StorEdge QFSfile system, see the Sun StorEdge QFS Software Installation and Upgrade Guide.

About HA-QFS File SystemsAn HA-QFS (highly available QFS) file system is a non-archiving HA shared orstand-alone Sun StorEdge QFS file system running on cluster devices and configuredto be part of a Sun Cluster resource group. Using File System Manager, you canconfigure Sun StorEdge QFS on cluster devices. You must use the SunPlex Managertool to configure the devices as part of a Sun Cluster resource group.

Note: File System Manager includes ha in the description of file systems that areconfigured on cluster devices even if the devices are not part of a resource group andthe file systems are therefore not truly highly-available file systems.

For stand-alone HA-QFS, the Sun StorEdge QFS file system is configured on severalSun Cluster nodes. Only one node at a time performs file system input and outputprocessing.

For shared HA-QFS, all hosts within the shared Sun StorEdge QFS configurationmust be nodes within the Sun Cluster environment. The Sun Cluster environmentcontrols metadata server failover.


Administering Stand-Alone,Non-archiving File Systemsand Archiving File SystemsThis section provides information about administering stand-alone, non-archivingfile systems and archiving file systems. It contains the following subsections:

■ “Planning a Stand-Alone, Non-archiving or Archiving File System” on page 60

■ “Creating a Stand-Alone, Non-archiving or Archiving File System” on page 61

■ “Growing a Stand-Alone, Non-archiving or Archiving File System” on page 62

■ “Checking a Stand-Alone, Non-archiving or Archiving File System” on page 63

■ “Mounting a Stand-Alone, Non-archiving or Archiving File System” on page 64

■ “Editing Mount Options for a Stand-Alone, Non-archiving or Archiving FileSystem” on page 65

■ “Unmounting a Stand-Alone, Non-archiving or Archiving File System” onpage 66

■ “Deleting a Stand-Alone, Non-archiving or Archiving File System” on page 66

■ “About Creating an Archiving File System and VSN Association” on page 67

Planning a Stand-Alone, Non-archivingor Archiving File SystemBefore creating a stand-alone, non-archiving file system or an archiving file system,do the following:

■ Decide whether you want the file system to be a stand-alone, non-archiving filesystem or an archiving file system. For information, see “About Stand-Alone,Non-archiving File Systems” on page 56 and “About Archiving File Systems” onpage 57.

■ Make sure the appropriate packages are installed on the server on which thestand-alone, non-archiving file system or archiving file system will reside. Formore information, see “About Supported File Systems” on page 54.

■ If you are creating a Sun StorEdge QFS file system, determine the separate devicesyou want to use for metadata and file data.

■ If you are creating an HA-QFS file system, determine which nodes in the SunCluster environment you want to use for the file system.


■ If you are creating a Sun StorEdge SAM-FS file system, determine the devices youwant to use for both metadata and file data.

■ Determine the disk devices you want to use in the file system.

■ Decide where you want the file system to be mounted on the current server. If themount point is a shared network file system (NFS) directory, you must choose tomount the file system at boot time in the New File System wizard. Otherwise,NFS will automatically share the directory, possibly preventing you frommounting the file system at a later time.

■ Decide the method by which you want files allocated on the file system: by thesingle allocation method or by the dual allocation method. For more information,see the allocation definitions in the Glossary.

The following considerations apply only to archiving file systems:

■ Before creating an archiving file system, determine whether your environmentcan support it. For information about archiving guidelines based on yourenvironment, see “About Archiving, Releasing, and Staging” on page 102.

■ Ensure that there are available volumes to which you can send copies of archivedfiles from the archiving file system. Be aware of the default archive copyconsiderations as described in “Creating a Stand-Alone, Non-archiving orArchiving File System” on page 61.

■ Decide whether you want to create metadata snapshots for the archiving filesystem, and if so, where you want the metadata snapshot files stored. For moreinformation, see “Planning Metadata Snapshots” on page 73.

Creating a Stand-Alone, Non-archivingor Archiving File SystemBefore you create a stand-alone, non-archiving file system or an archiving filesystem, you might want to change how your configuration entries are saved. Formore information, see “Enabling Pop-Up Windows” on page 13.

To create a stand-alone, non-archiving file system or an archiving file system:

1. From the Servers page, click the name of the server on which you want the filesystem to reside.


2. Click New File System.

The New File System wizard is displayed.


3. Specify the type of file system that you want to create. If you are creating a SunStorEdge QFS or Sun StorEdge SAM-FS file system, do the following:

■ To create a Sun StorEdge QFS file system, choose to store metadata and filedata on separate devices.

■ To create a Sun StorEdge SAM-FS file system, choose to store metadata and filedata on the same device.

■ (Optional) If you are creating a Sun StorEdge QFS file system and the serverhas the SUNWsamfsu package installed locally, you can configure the filesystem as archiving by selecting Archive This File System.

■ (Optional) If the server is a node in a Sun Cluster configuration, select HA toconfigure highly available QFS (HA-QFS).


The HA-QFS option is available only if the servers have either of the followingpackages installed locally:



4. Complete the steps in the New File System wizard.

Click the Help tab in the wizard for more information.

Growing a Stand-Alone, Non-archivingor Archiving File SystemWhen you grow a file system, you increase storage capacity by adding disk devices.

Through the browser interface, you can grow only the following file systems:

■ An unmounted Sun StorEdge SAM-FS file system

■ An unmounted, stand-alone, non-archiving Sun StorEdge QFS file system

■ An unmounted, archiving Sun StorEdge QFS file system

To grow a UFS or shared file system, use the command-line interface for that filesystem.


To grow a file system:



2. Select the radio button next to the file system you want to grow, and click Grow.

The Grow File System wizard is displayed.

3. If the file system has metadata and file data on the same device, skip to Step 6.Otherwise, select the metadata devices you want to add to the file system, andclick Next.

Note: The software discovers available devices to the best of its ability. Theremight be circumstances in which the devices displayed are in use. For moreinformation, see “Administering Stand-Alone, Non-archiving File Systems andArchiving File Systems” on page 60.

4. If the file system has striped groups, do the following:

a. Type the number of striped groups that you want to add to the file system andclick Next. The software automatically assigns a name to each striped groupthat you add. A file system cannot contain more than 126 striped groups.

b. For each striped group that you add, select the available devices that you wantas members of the striped group, and click Next. The devices must be the samesize as each other.

5. From the list of available data devices, select the devices you want to add to thefile system, and click Next.

6. (Optional) If you set preferences so that your configuration entries are saved to atemporary file, select Save to File, enter the name of the directory where you wantthe file to be stored, and click Submit.

7. Review the specified information for the new file system. If you are satisfied, clickFinish.

Checking a Stand-Alone, Non-archivingor Archiving File SystemThe file checking process looks for, and optionally repairs, file corruption on the diskpartitions belonging to the selected file system.


You cannot check a UFS or shared file system through the browser interface. Toperform this operation, use the command-line interface for that file system.

To check a stand-alone, non-archiving file system or an archiving file system:



2. Select the radio button next to the file system whose files you want to check.

3. From the Operations menu, choose Check File System.

The Check File System window is displayed.

4. Select an option to either check the file system, or to check the file system andautomatically make repairs.

5. Specify a location to which the file system check report will be sent.

6. Click Submit Job.

Mounting a Stand-Alone, Non-archivingor Archiving File SystemBy mounting a stand-alone, non-archiving file system or an archiving file system,you attach the file system to the file system hierarchy at the specified mount point,which is the path name of a directory. Only an unmounted stand-alone, non-archiving file system or unmounted archiving file system can be mounted.

To mount a stand-alone, non-archiving file system or archiving file system:



2. Select the radio button next to the file system that you want to mount.

3. From the Operations menu, choose Mount.

The file system is redisplayed on the File Systems Summary page with a diskusage value in its Disk Usage (Total) column.


Editing Mount Options for aStand-Alone, Non-archiving orArchiving File SystemThrough the browser interface, you can edit the mount options of a Sun StorEdgeSAM-FS file system, a stand-alone, non-archiving Sun StorEdge QFS file system, oran archiving Sun StorEdge QFS file system.

When you edit mount options, some changes cannot take effect until you unmountand then mount the stand-alone or archiving file system. If the file system iscurrently mounted, some mount options are unavailable for editing.

Follow these additional guidelines when editing mount options:

■ If you want to change a mount option value to the default value, delete theexisting value in the field that you want to change and click Save.

■ If you want to enable or disable mounting of the file system at boot time, youmust manually edit the mount at boot field in the /etc/vfstab file locatedon the current server. For more information about this file, see the Sun StorEdgeQFS Software Installation and Upgrade Guide or the Sun StorEdge SAM-FS SoftwareInstallation and Upgrade Guide.

To edit the mount options of a stand-alone, non-archiving file system or archivingfile system:



2. Select the radio button next to the file system whose mount options you want toedit.

3. From the Operations menu, choose Edit Mount Options.

The File System Edit Mount Options page is displayed.

4. Edit the fields that you want to change and click Save.


Unmounting a Stand-Alone,Non-archiving or Archiving File SystemYou must unmount a stand-alone, non-archiving file system or an archiving filesystem before performing certain operations such as growing the file system,deleting the file system, or upgrading hardware. Before you unmount an archivingfile system, you must idle or stop any archiving operation that is in process.

To unmount a stand-alone, non-archiving file system or archiving file system:



2. Select the radio button next to the file system that you want to unmount.

3. From the Operations menu, choose Unmount.

The file system is redisplayed on the File Systems Summary page with theunmounted value displayed in its Disk Usage (Total) column.

Deleting a Stand-Alone, Non-archivingor Archiving File SystemYou can delete selected stand-alone, non-archiving file systems or archiving filesystems from the server when they are no longer required. Before you can delete anarchiving file system, you must stop archiving, and unmount the archiving filesystem.

Caution: The process of deleting a file system removes all data from the file system.If you want to preserve any of the data on this file system, make sure to copy it toanother file system before proceeding.

Note: You cannot delete an archiving file system if the file system is the last filesystem of a policy or of a policy’s file match criteria. If this is the case, you mustdelete that policy or file match criteria before deleting the file system.


To delete a stand-alone, non-archiving file system or an archiving file system:



2. Select the radio button next to the file system that you want to delete.

3. From the Operations menu, choose Delete.


4. Click OK.

About Creating an Archiving File Systemand VSN AssociationEach archiving file system on a server has a default archive copy that archives allfiles that are not explicitly members of an archive policy. If an archiver.cmd fileexists on the server, there must be a volume association for each file system’s defaultarchive copy. A volume serial name (VSN) identifies a volume.

If an archiver.cmd file already exists on the server when you create an archivingfile system through the browser interface, the File System Manager softwareautomatically creates a VSN association with an available or valid media type for thedefault archive copy.

If an archiver.cmd file does not already exist on the server when you create anarchiving file system, the VSN association is not explicitly created, and the defaultarchiving behavior is retained. In this situation, you can create an archive policyfrom the Archive Management tab and apply the policy to the file system. Thisaction creates the archiver.cmd file and the necessary VSN association for thedefault archive copy of the file system.

To change these default copy definitions, you can manually edit the archiver.cmdfile at a later time.


Managing Policies forArchiving File SystemsThis section provides information about managing policies for an archiving filesystem. It contains the following subsections:

■ “Removing File Match Criteria From an Archiving File System” on page 68

■ “Adding a Policy to an Archiving File System” on page 69

■ “Adding Existing File Match Criteria to an Archiving File System” on page 69

■ “Reordering File Match Criteria for an Archiving File System” on page 70

Removing File Match Criteria From anArchiving File SystemYou can remove the relationship between file match criteria in a policy and anarchiving file system. Removing the relationship between file match criteria and anarchiving file system is not the same as removing the file match criteria from apolicy. When you remove file match criteria from an archiving file system, the filesystem’s files are no longer archived according to the directives defined by that setof criteria. An archiving file system can be associated with more than one set of filematch criteria from several different policies.

File match criteria cannot be removed from an archiving file system if the file systemis the sole file system associated with the file match criteria. In this case, the filematch criteria must be deleted for the association to be removed. If the set of filematch criteria is the sole set of file match criteria in a policy, you must delete thepolicy.

To remove file match criteria from an archiving file system:



2. Select the radio button next to the archiving file system from which you want toremove the file match criteria, and click View Policies.

The File System Archive Policies page is displayed.

3. In the Archive Policy Criteria table, select the radio button next to the policy andfile match criteria combination that you want to remove from the file system.


4. Click Remove.


5. Click OK.

Adding a Policy to an Archiving FileSystemAdding a policy to an archiving file system creates a new policy that is applieddirectly to the selected file system. This enables you to change archiving behavior bydefining new file match criteria and policy copy directives for the file system.

To add a policy to a file system:

1. From the Servers page, click the server on which the file system that you wantresides.


2. Select the radio button next to the file system for which you want to add a newpolicy, and click View Policies.


3. Click Add New Policy.

The New Policy wizard is displayed.

4. Complete the steps in the New Policy wizard as described in the Help tab of thewizard.

Adding Existing File Match Criteria to anArchiving File SystemTo change archiving behavior for a selected archiving file system, you can add oneor more sets of file match criteria from a list of existing file match criteria.

When you add file match criteria to an archiving file system, the files in that filesystem will be archived according to the archiving directives defined by the filematch criteria.


To add existing file match criteria to an archiving file system:



2. Select the radio button next to the archiving file system to which you want to addfile match criteria, and click View Policies.


3. In the Archive Policy Criteria table, click Add Existing Criteria.

The Available Criteria window is displayed.

4. From the list of available file match criteria, select the file match criteria you wantto add to the file system, and click Add.

Reordering File Match Criteria for anArchiving File SystemYou can reorder file match criteria associated with an archiving file system so thatthe file match criteria archive directives are applied in a new sequence.

To reorder file match criteria for an archiving file system:



2. Select the radio button next to the archiving file system for which you want toreorder file match criteria, and click View Policies.


3. In the Archive Policy Criteria table, click Reorder.

The Reorder Match Criteria window is displayed.

4. Select the file match criteria that you want, and click either Move Up or MoveDown to change the order of the file match criteria in the list.

Repeat this step until all of the file match criteria are in the order you want.


5. (Optional) If the Preferences option is enabled, do one of the following:

■ If you want to save your changes to a temporary file instead of committing thechanges to the configuration, select the Save in directory option and type thedirectory in which you want to save the temporary file.

■ If you want to commit the reordering changes to the configuration, select theReorder policy criteria option.

6. Click Submit.

Protecting Archiving FileSystem DataYou can protect the files of an archiving file system by regularly creating metadatasnapshots and by using media. This section provides information about protectingfileson an archiving file system. It contains the following subsections:

■ “About Protecting Archiving File System Data” on page 71

■ “Scheduling and Taking Metadata Snapshots” on page 72

■ “Restoring Archiving File System Data” on page 76

About Protecting Archiving File SystemDataTo protect the data on archiving file systems, you can schedule metadata snapshotsfor the file systems and you can archive copies of files from the file systems toarchive media.

File data consists of the actual files and directories of a file system. Metadata consistsof information about that file data. In particular, metadata is data about files, filepaths, the inodes for files, directories, access control limits, symbolic links,removable media, segmented files, and the indexes of segmented files. Before lostfile data can be retrieved from archive media, metadata must be restored.

When a metadata snapshot is created through the browser interface, it contains allthe metadata for the file system, which includes pointers to the archive locations foreach file. By using this metadata, the File System Manager software can recover filedata. You should store metadata snapshots separately from the file system to ensurethat they are available if the file system is lost.


With archiving file systems, the archiver, which is a component of the Sun StorEdgeSAM-FS software, can copy file data to archive media. This protects the data becauseit enables you to retrieve the data from the archive media at a later time, as long asthe media onto which archive copies are written is not erased and as long as FileSystem Manager can access the metadata snapshot.

Scheduling and Taking MetadataSnapshotsThis section provides information about scheduling and taking metadata snapshotsfor an archiving file system. It contains the following subsections:

■ “About Metadata Snapshots” on page 72

■ “Planning Metadata Snapshots” on page 73

■ “Scheduling the Creation of Metadata Snapshots” on page 74

■ “Taking a Metadata Snapshot on Demand” on page 75

■ “Editing a Metadata Snapshot Schedule” on page 75

■ “Removing a Metadata Snapshot Schedule” on page 76

About Metadata SnapshotsYou can schedule metadata snapshots for the archiving file systems on the server.

Scheduling a metadata snapshot through the browser interface is the equivalent ofcreating an entry in root’s crontab(1) to automate the Sun StorEdge SAM-FSsoftware samfsdump(1M) process. This process enables you to back up metadataseparate from the file data of an archiving file system. A metadata snapshot containsall the metadata for a complete archiving file system at a single point in time.

Note: Files written to an archiving file system after the creation of a metadatasnapshot starts might not be archived, and archive copies on cartridges might not bereflected in the metadata snapshot. Because of this, the files might not be known tothe system if the metadata snapshot is used to restore the archiving file system. Fileswritten to the archiving file system or archived after the metadata snapshot is takenwill be included in the next metadata snapshot.

Metadata snapshots can be run only on mounted, archiving file systems. A metadatasnapshot does the following:

■ Saves the relative path for each file.


■ Contains all information required for restoring an archiving file system, such asthe inode for each file, directory information, and symbolic links.

■ Enables you to restore an entire archiving file system, a directory hierarchy, or asingle file. See “Restoring an Archiving File System” on page 77 for moreinformation about the restore process.

Planning Metadata SnapshotsThe following table provides planning recommendations that can help you protectthe data of an archiving file system.

TABLE 6-2 Recommendations for Planning Metadata Snapshots

Recommendation Reason

Keep data from each archiving file system on its ownunique set of tapes or other archive media, and donot mix data from multiple file systems.

The path names of the files on archive media do notinclude the originating file system’s name, and thismight cause inconsistencies when you restore files.For more information, see the Sun StorEdge SAM-FSTroubleshooting Guide.

Make sure the archiving file system for which youwant to schedule metadata snapshots is mounted.

Metadata snapshots cannot be scheduled forunmounted file systems.

Store metadata snapshots for each file system in aseparate directory

Keeping the snapshots in separate files helps youlocate the snapshot you need to use to restore a filesystem more easily.

Schedule metadata snapshots for a time when filesare not being created or modified.

Taking a metadata snapshot when files are not beingcreated or modified will help ensure that the file databeing captured is not stale and will minimize thecreation of damaged files.

Archive your files regularly, and schedule metadatasnapshots at least once a day.

To ensure that files can be restored, configurearchiver scan intervals so that files are archivedbefore a metadata snapshot is created.

Make sure that the location on which you arecreating and storing metadata snapshot files hassufficient storage space for these files.

Metadata snapshot files can be quite large,depending on the number of files being stored on thearchiving file system.

Periodically check the metadata snapshot log file toensure that snapshots are being taken without anyerrors.

Checking the log file for issues can prevent thecreation of snapshots that contain damaged files. Youspecify the location of the metadata snapshot on theSchedule Metadata Snapshot page.


Scheduling the Creation of Metadata SnapshotsBy default, archiving file systems do not have metadata snapshots scheduled. Forinformation about planning for metadata snapshots, see “Planning MetadataSnapshots” on page 73.

To schedule the creation of metadata snapshots:

1. From the Servers page, click the server on which the archiving file system islocated.


2. Select the radio button next to the mounted archiving file system for which youwant to schedule a metadata snapshot.

3. From the Operations menu, choose Schedule Metadata Snapshots.

The Schedule Metadata Snapshot page is displayed.

4. Specify the appropriate values, and click Save.

In anticipation of taking a metadata snapshot ondemand, determine in advance the approximatelength of time it will take to create the metadatasnapshot and the approximate size of the snapshotfile.

Determining the length of time and the size of thefile can help you decide whether to wait for thescheduled metadata snapshot creation. You can usethe following values to make this determination:• Length of time = 5 to 10 Gbytes of data per hour• Snapshot file size = 666 * number of files on the

file systemThese values will vary, depending on the disktransfer and seek speeds of the systems being used.

Decide on a retention period for your metadatasnapshots.

Retaining all metadata snapshots indefinitely usesup space on your system. You can specify aretention period on the Schedule Metadata Snapshotspage. For example, you can specify that each time ametadata snapshot is taken, all snapshots older thantwo days (48 hours) should be deleted.

Determine who should receive notifications ofmetadata snapshot errors.

Metadata snapshots are critical in maintaining areliable restore capability of the file system. If ametadata snapshot fails, system administratorsshould be notified. You can specify addresses towhich you want error notifications sent on theNotifications Summary page, which is accessiblefrom the Schedule Metadata Snapshots page.

TABLE 6-2 Recommendations for Planning Metadata Snapshots (Continued)



After metadata snapshot files have been created, periodically check the snapshotlog file to ensure that snapshots are being created without errors or damagedfiles.

Taking a Metadata Snapshot on DemandYou might want to manually take a metadata snapshot instead of taking a snapshotat the regularly scheduled time in order to capture the metadata from an archivingfile system at a specific point in time.

To take a metadata snapshot on demand:



2. Select the radio button next to the mounted archiving file system for which youwant to take a metadata snapshot.

3. From the Operations menu, choose Take Snapshot.

The Take Metadata Snapshot window is displayed.

4. In the Fully Qualified Snapshot File Name field, type the path and the name ofthe snapshot file that you want to create.

5. Click Submit.

For information about how long it might take to create a metadata snapshot whentaken on demand, see “Planning Metadata Snapshots” on page 73.

Editing a Metadata Snapshot ScheduleTo edit the metadata snapshot schedule for an archiving file system:



2. Select the radio button next to the mounted archiving file system for which youwant to edit the metadata snapshot schedule.

3. From the Operations menu, choose Schedule Metadata Snapshots.

The Schedule Metadata Snapshots page is displayed.

4. Edit the fields that you want to change, and click Save.


Removing a Metadata Snapshot ScheduleRemoving a metadata snapshot schedule from an archiving file system does notremove the existing metadata snapshot files from the current server.

If the server has Release 4, Update 4, of the SUNWsamfsr and SUNWsamfsu orSUNWqfsr and SUNWqfsu packages installed locally, you must manually removeexisting metadata snapshots outside of the browser interface.

If the server has Release 4, Update 5, of the SUNWsamfsr and SUNWsamfsu orSUNWqfsr and SUNWqfsu packages installed locally, you can remove metadatasnapshots using the Delete Snapshot button on the Restore File System page. Formore information, see “Deleting a Metadata Snapshot” on page 83.

To remove a metadata snapshot schedule from an archiving file system:



2. Select the radio button next to the mounted archiving file system for which youwant to remove the metadata snapshot schedule.

3. From the Operations menu, choose Remove Snapshot Schedule.


4. Click OK.

Restoring Archiving File System DataThis section provides information about restoring data for an archiving file system.It contains the following subsections:

■ “Restoring an Archiving File System” on page 77

■ “About Filtering and Searching Through Metadata Snapshots” on page 79

■ “About Filter and Search File Name Pattern Values” on page 81

■ “Canceling a Metadata Snapshot Search” on page 82

■ “Deleting the Index for a Metadata Snapshot” on page 82

■ “Deleting a Metadata Snapshot” on page 83


Restoring an Archiving File SystemWith archiving file systems, you can configure the archiver to write copies of files toarchive media. After files are archived, information about the files can be captured ina metadata snapshot. In the event of a disaster, you can then use the metadatasnapshot to restore the files or the file system itself.

The restore process capabilities differ depending on whether the server has update 4or update 5 of the Release 4 SUNWsamfsr and SUNWsamfsu or SUNWqfsr andSUNWqfsu packages installed locally.

With update 4, you can restore file systems only from snapshot files that werecreated using File System Manager through a metadata snapshot schedule process.

With update 5, you can restore file systems using any metadata snapshot, includingsnapshots generated by other file systems, as long as the file data from the filesystem is accessible.

With update 5, you can also use multiple metadata snapshots to restore files into asingle file system. Conversely, you can use a single metadata snapshot to restore filedata into multiple file systems. For example, you could restore directory dir1 frommetadata snapshot file snapshot1 into file system mysam, and also restore directorydir2 from snapshot2 into the same file system (mysam). You could also restoredirectory dira from snapshot file snapshot3 into file system sam1 and directorydirb from the same snapshot file (snapshot3) to a different file system, forexample sam2.

For information about planning metadata snapshots, see “Planning MetadataSnapshots” on page 73.

To restore a file system:



2. Select the radio button next to the mounted archiving file system for which youwant to restore files, and choose Restore from the Operations menu.

The Restore File System page is displayed with a Metadata Snapshot Summarytable listing the metadata snapshots available in the current directory.

3. (Optional) If the server has Release 4, update 5 of the SUNWsamfsr andSUNWsamfsu or SUNWqfsr and SUNWqfsu packages installed locally, you canclick Browse to select a different directory from which to display the MetadataSnapshot Summary table.

4. If the metadata snapshot file is not displayed as a link in the Metadata SnapshotSummary table, follow these steps to bring the snapshot file online for browsing:


a. Select the radio button next to the metadata snapshot.

b. Click Create Index.

An index file is created. If the metadata snapshot was compressed using thecompress utility, a new decompressed version of the metadata snapshot willalso be created. The original version of the metadata snapshot remains on theserver. Files compressed with gzip do not requiring decompressing.

Note: If the metadata snapshot is a headerless snapshot created using the SunStorEdge SAM-FS samfsdump(1M) command with the -H option, the systemcannot index the snapshot, and you cannot restore the file system using thatsnapshot.

5. When the metadata snapshot is displayed as a link in the Metadata SnapshotSummary table, do one of the following:

■ Click the metadata snapshot file to browse its contents.

■ Select the radio button next to the metadata snapshot file and click ShowContents.

The Restore File System page is refreshed, and the top-level items in the selectedmetadata snapshot are displayed in the Metadata Snapshot Entries table.

Note: Top-level items are displayed unless you previously selected a metadatasnapshot and the directory that was displayed from that snapshot is found in thenewly selected metadata snapshot. In this situation, the same directory continuesto be displayed.

6. Do one or more of the following to find the files that you want to restore:

■ Navigate through the snapshot by clicking directories and by using the Up OneLevel or Go to Directory buttons.

■ Click Filter to limit the items in the table so that only the information thatinterests you is displayed. For more information, see “About Filtering andSearching Through Metadata Snapshots” on page 79.

■ Click Search Snapshot to search the whole snapshot file and display resultsbased on your search criteria.

■ Type a value in the Maximum Snapshot Entries Retrieved field to limit the totalnumber of items that are read from the snapshot file.

7. To restore the whole file system, select the Entire File System option in the Restoresection of the page. Alternatively, to restore a file or directory, follow these steps:

a. Select the radio button next to the file or directory in the Metadata SnapshotEntries table.

The file or directory that you select is displayed in the File or Directory toRestore field.


b. Specify the location to which you want to restore the file or directory. Bydefault, the location is the path of the original file or directory, relative to themount point of the file system. You can specify a different path relative to themount point, or you can specify an absolute path on any archiving file system.

c. If the server has the Release 4, Update 4 versions of the SUNWsamfsr andSUNWsamfsu or SUNWqfsr and SUNWqfsu packages installed locally, and a fileor directory already exists in the location to which you are restoring files, therestore operation fails. To restore that file or directory, either specify a differentlocation or rename the file or directory that already exists in the restorelocation before starting the restore process.

If the server has the Release 5, update 5 versions of the SUNWsamfsr andSUNWsamfsu or SUNWqfsr and SUNWqfsu packages installed locally, specifywhat action you want the system to take if the file already exists in the locationto which you are restoring files.

8. From the Online Status After Restoring menu, choose the actions that you wantthe file system to take after completing the restore process.

9. Click Restore.

About Filtering and Searching Through MetadataSnapshotsYou can control which files and directories in a metadata snapshot are displayed inthe browser interface. Filtering a metadata snapshot displays the files and directoriesthat meet the filter criteria in a hierarchical fashion and enables you to navigatethrough the hierarchy.

If you want to restore a specific file for an archiving file system and you know onlypart of the file’s name, you might want to search the metadata snapshot for that file.Searching a metadata snapshot enables the software to scan the entire metadatasnapshot file and to display all files or directories that meet the search criteria on oneflat level. Search results are displayed as static full path names rather than asdirectories through which you can navigate.

When filtering the contents of a metadata snapshot file, be aware of the following:

■ You must choose at least one filter criterion.

■ A filter applies to the contents of the selected metadata snapshot file only, not tomultiple metadata snapshot files.


■ A filter remains in effect as you navigate into directories and subdirectories of ametadata snapshot. For example, you might find a directory named user byspecifying *us as a filter criterion. When you navigate through the userdirectory, the filter is still applied, and so not all files are displayed. To view allfiles in that directory, reset or remove the filter criterion.

■ To remove filter criteria from the table, click the Clear Filter button on the RestoreFile System Page.

■ Specifying multiple values in the Filter Snapshot window is the equivalent ofusing AND in a search.

The following table describes the filter and search values that you can specify.

TABLE 6-3 Filter Values

Filter Value Description

File Name Pattern field Type a value to filter for files and directories with the specified name. Formore information about wildcard characters that you can use in this field,see “About Filter and Search File Name Pattern Values” on page 81.

File Size greater than or equalto

Type a value to filter for files that are larger than the specified size.

File Size less than or equal to Type a value to filter for files that are smaller than the specified size.

File Date Choose to filter for files that are created or that are modified during thespecified time frame.

Owner ID Type a value to filter for files that are owned by the specified user, asdefined on the server from which the files originated.

Group ID Type a value to filter for files that are owned by users who are members ofthe specified group, as defined on the server from which the files originated.

Is Damaged Choose to filter for files that are damaged.This option is available only if the server has either of the followingpackages installed locally:• Release 4, update 5, SUNWsamfsr and SUNWsamfsu

• Release 4, update 5, SUNWqfsr and SUNWqfsu

Is Online Choose to filter for files that are online and available for browsing.This option is available only if the server has either of the followingpackages installed locally:• Release 4, update 5, SUNWsamfsr and SUNWsamfsu

• Release 4, update 5, SUNWqfsr and SUNWqfsu


About Filter and Search File Name Pattern ValuesWhen you filter or search through a metadata snapshot, you can filter or search forfiles and directories based on the file or directory name. You do this by typing avalue in the File Name Pattern field in the Filter Snapshot or Search Snapshotwindow. For more information about the patterns, see the fnmatch(3c) man page.

The following are valid wildcard characters that you can type in the File NamePattern field.

TABLE 6-4 File Name Wildcards

Wildcard Description

? Enables you to filter for files that contain any character in place ofthe question mark. For example, a?d returns files named aad, abd,acd, and so on.

* Enables you to filter for files that contain any number of charactersin place of the asterisk. For example, *a*d returns files named ad,abcd, efabcd, aaaad, and adddd.

[] Enables you to filter for files that contain one of the alternativesspecified within the brackets. For example, a[bc] returns filesnamed ab or ac.

““ Enables you to filter for files that contain only the specifiedcharacters. For example, “abc” returns only files named abc.

\ Removes the wildcard distinction from any wildcard character thatyou use with the backslash. For example, “*\(\?” returns fileswith (? in their names. To filter for files that have a backslash intheir name, type two backslashes \\.

/ Enables you to filter for files in a pathname. The slash character ina pathname must be explicitly matched by one or more slashes inthe File Name Patter field (for example, /var). It cannot bematched by an asterisk, question mark, or bracket. Slashes in theFile Name Pattern field are identified before brackets. This meansthat, for example, a[b/c]d does not return files named abd ora/d. It will return only a file named a[b/c]d.


The following table shows examples of different File Name Pattern values andwhether they return files or directories named abc.

Canceling a Metadata Snapshot SearchYou might want to cancel a search through a metadata snapshot if the search istaking too long to complete.

To cancel a metadata snapshot search:

1. From the Servers page, click the server on which the archiving file system thatyou want to restore is located.




3. From the Filter menu, choose Metadata Snapshot Search.

The metadata snapshot search job is displayed in the Current Jobs table.

4. Select the radio button next to the metadata snapshot search job, and click Cancel.

Deleting the Index for a Metadata SnapshotIf you used a metadata snapshot file to restore a file system, an index file wascreated for the metadata snapshot. If the metadata snapshot was compressed usingthe compress utility, a new decompressed version of the metadata snapshot will

TABLE 6-5 File Name Patterns

File Name Pattern Some Possible Files or Directories Returned

abc abc, abcd, gabc

“abc” abc

a?c abc, accd, gabc, gagc

a*c abbc, afilenamec, gabc, abc, gaggc

“a?c” a?c

a\*c a*c

*/var abc/var, path/var


have also been created. (A decompressed version of the file is not necessary if it wascompressed using gzip.) Because these files can be large, you might want to deletethem after the restore process is finished.

Deleting the index and, if applicable, the decompressed version of a metadatasnapshot does not delete the original metadata snapshot.

If the server has Release 4, update 4, of the SUNWsamfsr and SUNWsamfsu orSUNWqfsr and SUNWqfsu packages installed locally, you must manually removeexisting metadata snapshots outside of the browser interface.

If the server has Release 4, update 5, of the SUNWsamfsr and SUNWsamfsu orSUNWqfsr and SUNWqfsu packages installed locally, you can remove metadatasnapshots using the Delete Snapshot button on the Restore File System page. Formore information, see “Deleting a Metadata Snapshot” on page 83.

To delete the index and the decompressed version of a metadata snapshot:

1. From the Servers page, click the name of the server on which the archiving filesystem that you restored is located.


2. Select the radio button next to the mounted archiving file system for which youhave restored files, and choose Restore from the Operations menu.

The Restore File System page is displayed.

3. Select the radio button next to the metadata snapshot file for which you manuallycreated an index.

4. Click Delete Index.


5. Click OK.

The index file is deleted. If the metadata snapshot had a decompressed version ofitself created by the index creation process, the decompressed version of thesnapshot is also deleted. The original metadata snapshot remains on the server.

Deleting a Metadata SnapshotIf the server has Release 4, Update 4, of the SUNWsamfsr and SUNWsamfsu orSUNWqfsr and SUNWqfsu packages installed locally, you must manually removeexisting metadata snapshots outside of the browser interface. If the server hasRelease 4, update 5, of the SUNWsamfsr and SUNWsamfsu or SUNWqfsr andSUNWqfsu packages installed locally, use the following procedure to delete ametadata snapshot.


To delete a metadata snapshot file:

1. From the Servers page, click the name of the server on which the archiving filesystem that you restored is located.


2. Select the radio button next to the mounted archiving file system for which youhave restored files, and choose Restore from the Operations menu.

The Restore File System page is displayed.

3. Select the radio button next to the metadata snapshot file you want to delete.

4. Click Delete Snapshot.


5. Click OK.

The metadata snapshot file is deleted. Any associated index or decompressed filesare also deleted.

Administering Shared FileSystemsThis section provides information about administering shared file systems. Itcontains the following subsections:

■ “Planning a Shared File System” on page 85

■ “Creating a Shared File System” on page 85

■ “Creating the Shared Hosts File” on page 86

■ “Adding a Client or Potential Metadata Server” on page 87

■ “Deleting a Client or Potential Metadata Server” on page 88

■ “Deleting the Metadata Server” on page 89

■ “Mounting and Unmounting Shared File Systems” on page 90

■ “Deleting a Shared File System” on page 94


Planning a Shared File SystemBefore you can create, add a client to, or add a potential metadata server to a sharedfile system, the following prerequisites must be met:

■ All participating hosts must have either of the following packages installedlocally:

■ SUNWqfsr and SUNWqfsu

■ SUNWsamfsr and SUNWsamfsu

■ All Sun StorEdge QFS and Sun StorEdge SAM-FS software packages installed onthe participating hosts must be at the same release level.

■ All participating hosts must be added to the File System Manager browserinterface, as described in “Adding a Server” on page 24.

■ The File System Manager service, fsmgmtd, must be running and available oneach host that will participate in the shared file system. For more informationabout the fsmgmtd service, see the Sun StorEdge QFS Software Installation andUpgrade Guide.

Consider the following before creating a shared file system:

■ Determine the devices you want to use for metadata and file data in the filesystem. Metadata devices must be accessible from every host that is a potentialmetadata server in the file system. Data devices must be accessible from everyhost in the file system (clients, metadata server, and potential metadata servers).

■ Decide where you want the file system to be mounted on the current server. If themount point is a shared network file system (NFS) directory, you must choose tomount the file system at boot time in the New File System wizard. Otherwise,NFS will automatically share the directory, possibly preventing you frommounting the file system at a later time.

■ Decide the method by which you want files allocated on the file system: by thesingle allocation method or by the dual allocation method. For more information,see the allocation definitions in the Glossary.

Creating a Shared File SystemBefore you can create a shared file system, you must have prepared yourconfiguration as described in “Planning a Shared File System” on page 85.

You might also want to change how your configuration entries are saved. For moreinformation, see “Enabling Pop-Up Windows” on page 13.


To create a shared file system:

1. From the Servers page, click the name of the server on which you want the sharedfile system to reside.


2. Click New File System.

The New File System wizard is displayed.

3. Specify the Sun StorEdge QFS file system as the type of file system you want tocreate, and do the following:

■ Choose to store metadata and file data on separate devices or on the samedevice.

Note: For general purpose workloads, storing metadata and file data on the samedevice provides better system performance.

■ Select the Shared option.

■ (Optional) If the server is a node in a Sun Cluster configuration, select HA toconfigure HA (highly available) - QFS.


4. Complete the steps in the New File System wizard.


Creating the Shared Hosts FileIf you want to modify the host configuration of a shared file system outside of thebrowser interface, you can create the shared hosts file (hosts.family-set-name) forthe file system and then edit the file manually with the new hosts. You might wantto do this in order to add Linux clients to the shared file system.

The procedure in this topic describes how to create the shared hosts file. Forinformation about how to edit the file, see “To Change the Shared Hosts FileInformation on an Unmounted File System” in the Sun StorEdge QFS SoftwareConfiguration and Administration Guide.

To create the shared hosts file for a shared file system:


1. Use telnet to connect to the metadata server of the shared file system, and login as root.

2. Navigate to the /etc/opt/SUNWsamfs directory.

3. Use the samsharefs(1M) -R command to create the shared hosts file:

# samsharefs -R shared-file-system-name > hosts.family-set-name

Adding a Client or Potential MetadataServerBefore you can add a client or potential metadata server to an existing shared filesystem, you must have prepared your configuration as described in “Planning aShared File System” on page 85.

After you add a potential metadata server to the shared file system, the File SystemManager software automatically updates the hosts file on the potential metadataserver system.

To add a client or potential metadata server to a shared file system:

1. From the Servers page, click a server that is acting as the metadata server or as thepotential metadata server for the shared file system.


2. Scroll through the table and click the shared file system.


3. Click Add.

The Add a Potential Metadata Server or a Shared Client window is displayed.

4. Choose the type of host you want to add:

■ If you want to add a client to the shared file system, choose Shared Client.

■ If you want to add a potential metadata server to the shared file system, choosePotential Metadata Server.

5. From the Host Name menu, choose the host that you want to add to the sharedfile system.

The menu lists hosts that have been added to the browser interface, that have thesame Sun StorEdge QFS and Sun StorEdge SAM-FS release levels as the metadataserver, and that have the Sun StorEdge QFS package installed locally.


6. If you are adding a potential metadata server, select or deselect the Read Onlycheck box as follows:

■ If you want the client to have full access to data in the file system, deselect it.

■ If you want the client to have read-only access to data in the file system, selectit.

7. In the Mount Point field, type the full directory path to which you want the filesystem attached (mounted) within your system’s directory tree. Use the followingsyntax:

/directory-name/file-system-name

Note: If the directory that you specify already exists, be aware that you can accessexisting files in that directory only when the file system is unmounted.

8. If you want to create the mount point that you specified or you want the filesystem to be mounted at boot time, select the appropriate check boxes.


■ To create and mount the file system, select the After Addition, Mount option.This option is displayed only if the metadata server for the shared file systemis mounted.

■ To create the file system without mounting it, select the After Addition, Do NotMount option.

10. Click OK.

Deleting a Client or Potential MetadataServerBefore you can delete a client or potential metadata server from a shared file system,the shared file system must be unmounted on all participating hosts. Forinformation about unmounting a shared file system, see “Unmounting a Shared FileSystem” on page 93.

To delete a client or potential metadata server:






3. Select the radio button next to the client or potential metadata server that youwant to delete, and click Delete.

A message box prompts you to confirm the deletion.

4. Click OK.

Deleting the Metadata ServerBefore you can delete the metadata server of a shared file system, you must performthe following tasks:

1. Unmount the clients and potential metadata servers, as described in“Unmounting a Client or Potential Metadata Server” on page 93.

2. Unmount the metadata server, as described in “Unmounting the MetadataServer” on page 94.

3. Delete the clients and potential metadata servers, as described in “Deleting aClient or Potential Metadata Server” on page 88.

To delete the metadata server:

1. From the Servers page, click the name of the server that is acting as the metadataserver for the shared file system.




3. Select the radio button next to the metadata server that you want to delete, andclick Delete.


4. Click OK.


Mounting and Unmounting Shared FileSystemsThis section provides information about mounting shared file systems. It containsthe following subsections:

■ “Mounting a Shared File System” on page 90

■ “Mounting the Metadata Server” on page 91

■ “Mounting a Client or Potential Metadata Server” on page 91

■ “Editing Mount Options for a Shared File System” on page 92

■ “Unmounting a Shared File System” on page 93

■ “Unmounting a Client or Potential Metadata Server” on page 93

■ “Unmounting the Metadata Server” on page 94

Mounting a Shared File SystemBy mounting a shared file system, you attach the shared file system to the file systemhierarchy at the specified mount point, which is the full path name of a directory(/directory-name/file-system-name).

To mount a shared file system:

1. Ensure that the fsmgmtd daemon is running and available on the metadataserver:

a. On the metadata server, use the fsmadm(1M) status command to checkwhether the daemon is running.

b. If it is not, manually restart the daemon by typing the following:

/opt/SUNWsamfs/sbin/fsmadm restart

2. Return to the File System Manager interface.



4. Scroll through the table and click the shared file system for which you want tomount the metadata server.



5. Select the radio button next to the metadata server that you want to mount, andchoose Mount from the Operations menu.

The metadata server is redisplayed with the mounted value in its Mount Statecolumn.

6. Select the radio button next to the client or potential metadata server that youwant to mount, and choose Mount from the Operations menu.

The client or potential metadata server is redisplayed with the mounted value inits Mount State column.

Mounting the Metadata ServerBefore you can mount the metadata server of a shared file system, the fsmgmtddaemon must be running and available on the metadata server. For moreinformation about this daemon, see the Sun StorEdge QFS Software Installation andUpgrade Guide.

To mount the metadata server:



2. Scroll through the table and click the shared file system for which you want tomount the metadata server.


3. Select the radio button next to the metadata server that you want to mount.


The metadata server is redisplayed with the mounted value in its Mount Statecolumn.

Mounting a Client or Potential Metadata ServerBefore you can mount a client or potential metadata server of a shared file system,the fsmgmtd service must running and available on the metadata server and on theclient or potential metadata server that you are mounting. Additionally, themetadata server must be mounted.


To mount a client or potential metadata server:



2. Scroll through the table and click the shared file system for which you want tomount a client or potential metadata server.


3. Select the radio button next to the client or potential metadata server that youwant to mount.


The client or potential metadata server is redisplayed with the mounted value inits Mount State column.

Editing Mount Options for a Shared File SystemTo edit the mount options for a shared file system, you must edit mount options onits metadata server. When you make changes to the mount options on the metadataserver, the changes are propagated to all the participating hosts in the file system.This synchronizes the hosts’s mount options, unless a client host is flagged as read-only.

To edit a shared file system’s mount options:



2. Scroll through the table and click the shared file system for which you want toedit mount options.


3. Select the radio button next to the metadata server on which you want to editmount options.

4. From the Operations menu, choose Edit Mount Options.

The File System Edit Mount Options page is displayed.



Unmounting a Shared File SystemYou must unmount a shared file system before upgrading hardware.

Note: The main reason to unmount a shared file system is to validate itsconfiguration or to upgrade hardware. You cannot grow a shared file systemthrough the browser interface.

To unmount a shared file system:



2. Scroll through the table and click the shared file system that you want tounmount.


3. For each client or potential metadata server participating in the shared filesystem, do the following:

a. Select the radio button next to the client or potential metadata server.

b. From the Operations menu, choose Unmount.

The client or potential metadata server is redisplayed with the unmountedvalue in the Mount State column.

4. Select the radio button next to the metadata server, and choose Unmount from theOperations menu.

Every metadata server is redisplayed with the unmounted value in the MountState column.

Unmounting a Client or Potential Metadata ServerYou must unmount a shared file system before upgrading hardware. Before youunmount a file system, you must idle or stop any archiving operation that is inprocess.

To unmount a client or potential metadata server in a shared file system:




2. Scroll through the table and click the shared file system for which you want tounmount a client or potential metadata server that you want to unmount.


3. Select the radio button next to the client or potential metadata server.


The client or potential metadata server is redisplayed with the unmounted valuein its Mount State column.

Unmounting the Metadata ServerYou must unmount a shared file system before upgrading hardware. Before youunmount a file system, you must idle or stop any archiving operation that is inprocess.

Note: Before you can unmount the metadata server for a shared file system, youmust unmount each client and potential metadata server that is participating in theshared file system.

To unmount a metadata server for a shared file system:



2. Scroll through the table and click the shared file system for which you want tounmount its metadata server.


3. Select the radio button next to the metadata server that you want to unmount.


The metadata server is redisplayed with the unmounted value in its Mount Statecolumn.

Deleting a Shared File SystemBefore you delete a shared file system, you must perform the following tasks:

1. Unmount all clients and potential metadata servers, as described in “Unmountinga Client or Potential Metadata Server” on page 93.


2. Unmount the metadata server, as described in “Unmounting the MetadataServer” on page 94.

3. Delete all clients and potential metadata servers, as described in “Deleting aClient or Potential Metadata Server” on page 88.

4. Delete the metadata server, as described in “Deleting the Metadata Server” onpage 89.

To delete the shared file system:

1. From the Servers page, click the name of the server on which the shared filesystem resides.


2. Scroll through the table and select the radio button next to the shared file systemthat you want to delete.



4. Click OK.

Managing NFS Sharing for FileSystemsThis section provides information about sharing file systems and editing networkfile system (NFS) properties. It contains the following subsections:

■ “About NFS Sharing” on page 95

■ “Adding an NFS Directory” on page 96

■ “Editing NFS Directory Options” on page 97

■ “Changing the Status of an NFS Directory” on page 98

■ “Removing an NFS Directory” on page 99

About NFS SharingYou can manage network file system (NFS) directories in file systems.


If at least part of a stand-alone, archiving, or shared file system is shared with theNFS service, the Description column on the File Systems Summary page displays thenfs-shared value. For more information about the NFS service, see the NFSdocumentation.

For a whole file system to be NFS shared, the mount point of a file system must be ashared NFS directory. For part of a file system to be NFS shared, a subdirectory of itsmount point must be a shared NFS directory.

Note: If you create a file system and you specify a shared NFS directory as themount point, you must choose to mount the file system at boot time in the New FileSystem wizard. Otherwise, NFS will automatically share the directory, possiblypreventing you from mounting the file system at a later time.

When a file system is NFS shared, remote servers in the network can mount the NFSdirectories on the file system, assuming the servers have the NFS service enabled.This is the equivalent of using the mount_nfs command. For more information, seethe mount_nfs(1M) man page.

The browser interface supports the addition and removal of NFS directories to andfrom file systems. In addition, the browser interface supports the ability to changethe options of the NFS directories and change the status of the directories to sharedor unshared.

The browser interface does not support the NFS automount feature (autofs). Formore information, see the NFS automount(1M) man page.

Adding an NFS DirectoryYou can add a network file system (NFS) directory to a mounted local file system. Ifyou add a NFS directory and choose to share it, other remote servers in the networkcan mount the NFS directory.

Before adding a NFS directory to a file system, the NFS service must be enabled onthe server where the file system is located. For more information, see the NFSdocumentation.

To add a NFS directory:

1. From the Servers page, click the server on which the file system that you want toadminister resides.


2. Select the radio button next to the file system to which you want to add a NFSdirectory.



The File System NFS Details page is displayed.

4. In the NFS Shared Directories table, click Add.

The Add Directory window is displayed.

5. Click Browse to find the directory that you want.

The Browse window is displayed.

6. Use the fields and buttons on the Browse window to navigate through thedirectories on the server and do one of the following:

■ Upon finding the directory that you want, click Choose Folder.

■ If you cannot find a directory that you want, type a name in the Folder Namefield and click Create Folder.

The Browse window is closed and the directory name that you specified isdisplayed on the Add Directory window.

7. To immediately share the directory, click Save. If you do not want to share thedirectory, deselect the Share now check box and click Save.

Editing NFS Directory OptionsYou can edit network file system (NFS) directory options for a local file system thathas the NFS service enabled. Some NFS options that you can edit include the readand write permissions of a NFS directory. Editing these permissions controlswhether remote servers have read-only, read and write, or root access to the sharedNFS directory.

To edit NFS directory options for a file system:



2. Select the radio button next to the file system for which you want to edit NFSdirectory options.



4. Select the radio button next to the directory that you want to edit and click Edit.

The NFS Options window is displayed.


5. Specify one or more of the following:

■ Read only – Select to enable read-only access to this directory. In the AccessList field, optionally specify which servers have read-only access by typing theserver or network group names, separated by a colon. If you leave the AccessList field blank, all servers have read-only access.

■ Read/Write – Select to enable read and write access to this directory. In theAccess List field, optionally specify which servers have read and write accessby typing the server or network group names, separated by a colon. If youleave the Access List field blank, all servers have read and write access.

■ Root – Select to enable executive privileges on this directory. In the Access Listfield, specify which servers have executive privileges by typing the server ornetwork group names, separated by a colon.

6. Click Save.

Changing the Status of an NFS DirectoryYou can change the status of a network file system (NFS) directory to shared orunshared. When you change the status of a NFS directory to unshared, any remotefile system that has mounted the NFS directory can no longer access the files orsubdirectories in the file system.

Note: Changing the status of a NFS directory to unshared does not permanentlydisable the sharing of the NFS directory. Instead, it changes the status of the NFSdirectory to inactive. To permanently disable sharing, you must remove the NFSdirectory. For more information, see “Removing an NFS Directory” on page 99.

To change the status of a NFS directory:



2. Select the radio button next to the file system for which you want to change thestatus of a NFS directory.



4. In the NFS Shared Directories table, select the radio button next to the directoryfor which you want to change status.

5. From the Operations menu, choose Share or Unshare.


The directory is redisplayed with the newly changed status value in its CurrentStatus column.

Removing an NFS DirectoryYou can remove a network file system (NFS) directory from a local file system.Removing a NFS directory does not delete the directory from the server on which itresides. Instead, the NFS directory is permanently unshared and is removed fromthe NFS /etc/dfs/dtstab configuration file.

To remove a network file system (NFS) directory from a file system:



2. Select the radio button next to the file system from which you want to remove aNFS directory.



4. Select the radio button next to the directory that you want to remove, and clickRemove.


5. Click OK.


CHAPTER 7

Managing Archiving

This chapter provides information about managing archiving. It contains thefollowing sections:

■ “About Archive Management” on page 101

■ “About Archiving, Releasing, and Staging” on page 102

■ “Controlling Archiving for Archiving File Systems” on page 109

■ “Managing Archive Policies” on page 111

■ “Managing VSN Pools for Archiving” on page 131

■ “Managing Disk VSNs for Archiving” on page 134

■ “Setting Up General Archiving” on page 136

■ “Configuring the Recycler” on page 140

■ “Managing Archiving and Staging Activity” on page 144

About Archive ManagementIf you are managing a server that has the Sun StorEdge SAM-FS software(SUNWsamfsr and SUNWsamfsu packages) installed locally, you can create SunStorEdge SAM-FS and Sun StorEdge QFS file systems on the server that arearchiving. Otherwise, the Archive Management tab is not displayed in the browserinterface and you cannot perform archiving options.

If the current server has the SUNWsamfsr and SUNWsamfsu packages installedlocally, you can perform the following procedures:

■ Create a stand-alone, non-archiving Sun StorEdge QFS file system and configureit to be archiving.

■ Create a Sun StorEdge SAM-FS file system that is automatically configured to bearchiving.

101

■ Create an archive policy, which is a collection of file system directives, copydirectives, copy parameters, and volume associations that determines how groupsof files can be archived.

■ Perform disk archiving by creating a policy and selecting Disk as your media typein one of the copies in the policy. You can specify several disk volumes, or youcan choose a pool of disk volumes to be used for archiving.

■ Add file match criteria and policy copies to a policy and remove them from apolicy.

■ Apply file match criteria in a policy to a file system. This defines how and whengroups of files in the file system are archived.

■ Remove file match criteria in a policy from a file system, which stops thearchiving of files in the file system, but does not delete the file match criteria fromthe configuration (archiver.cmd file).

■ Delete a policy from the configuration (archiver.cmd file).

■ Configure continuous archiving on a global basis by choosing No Scan on theGeneral Archiving Setup page.

■ Configure continuous archiving on a file system basis by choosing No Scan on theFile System Archive Policies page.

■ Configure metadata archiving by editing the policy settings that are defined in thedefault policy for a file system.

■ Create a no-archive policy, which enables groups of files to never be archived.

■ Create, edit, and delete pools of disk or media volumes.

■ Configure global archiving directives.

About Archiving, Releasing,and StagingThis section provides information about archiving, staging, and releasing. It containsthe following subsections:

■ “About the Sun StorEdge SAM-FS Software” on page 103

■ “About Archiving” on page 104

■ “Planning for Archiving” on page 105

■ “About Continuous Archiving” on page 107

■ “About Associative Archiving” on page 108

■ “About the Releaser” on page 108

■ “About the Stager” on page 109


About the Sun StorEdge SAM-FSSoftwareThe Sun StorEdge SAM-FS software enables you to archive copies of files to andretrieve copies from remote media or partitions of another file system.

The following table describes the components of the Sun StorEdge SAM-FS software.

When you create a file system through the browser interface and you select theArchive This File System option, the File System Manager software configures thefile system to use the Sun StorEdge SAM-FS software that is installed locally on thecurrent server.

TABLE 7-1 Components of Sun StorEdge SAM-FS Software

Component Description

Archiver Software that automatically copies online disk cache files to archivemedia, such as to a disk or a tape.

Releaser Software that automatically maintains the online disk cache of anarchiving file system by freeing disk blocks occupied by eligiblearchived files. The software determines when to release disk blocksby using the High Water Mark and Low Water Mark thresholdvalues that you define when you create an archiving file system.You can edit these values on the Edit Mount Options page for thefile system.

Stager Software that restores files to online disk cache. When a user orprocess requests file data that has been released from disk cache,the stager automatically copies the file data back to the online diskcache.

Recycler Software that clears archive volumes of expired copies and makesvolumes available for reuse.

Chapter 7 Managing Archiving 103

About ArchivingArchiving is the process of copying a file from a file system to a volume that islocated on a removable media cartridge or on a disk partition of another file system.The archiver, a component of the Sun StorEdge SAM-FS software, is software thatautomatically performs this copying of online disk cache files to archive media,unless you use a no-archive policy to configure it to do otherwise.

Before the archive process is initiated, the archiver searches for archiving directivesthat are defined in archive policies. An archive policy is a collection of file systemdirectives, copy directives, copy parameters, and volume associations thatdetermines how groups of files can be archived. Several archive policies can beassociated with an archiving file system. For more information about policies, see“About Archive Policies” on page 112.

Based on the directives defined in the default policy for a file system, the archiverautomatically creates one archive copy of all files and sends the copy to archivemedia. You can configure the archiver to create up to four archive copies on a varietyof archive media by modifying the default policy for the file system or by creating acustom policy and applying it to the file system.

Before a file is considered a candidate for archiving, the data in the file must bemodified. A file is not archived if it is only accessed. A file is selected for archivingbased on its archive age, which is the amount of time since the file's lastmodification. The archive age can be defined for each archive copy in an archivepolicy.

If a large file is segmented into smaller pieces, each segment is treated as a file, andeach segment is archived separately.


Planning for ArchivingThe following table provides general planning recommendations that can helpimprove archiving performance.

TABLE 7-2 Archiving Recommendations


Save archive log files. The archive log files provide information that isessential to recovering data. Store the log files in asafe place in the case of a disaster or in case the SunStorEdge SAM-FS software is unavailable. You canconfigure global archive log files on the GeneralSetup page. You can also configure individual logfiles for each archiving file system on the File SystemArchive Policies page for the file system.

Specify volume ranges in archivecopies, rather than specificvolume names.

Let the software place files on many differentvolumes. Volume ranges enable the system to runcontinuously. Typing specific volume names inarchive copies can rapidly fill a volume, causingundue workflow problems as you remove a piece ofmedia and replace it with another. For informationabout creating archive copies, see “Adding a Copyto a Policy” on page 130.

Base archive intervals on howoften files are created andmodified, and whether you wantto save all modification copies.

The archive interval is the time between file systemscans. A very short archive interval keeps thearchiver scanning almost continuously.

Consider the number of filesystems you are using.

Multiple small archiving file systems result in betterarchiver performance than a single large archivingfile system. The archiver uses a separate process foreach file system. Multiple file systems can bescanned in considerably less time than a single largefile system. For information about the number of filesystems to create based on your environment, see“Planning for Archiving” on page 105.

Use directory structures toorganize files in an archiving filesystem as you would a UNIX filesystem.

For performance considerations, do not place morethan 10,000 files in a directory. For informationabout other archiving configuration guidelines, see“Planning for Archiving” on page 105.


If you are managing a server that has the Sun StorEdge SAM-FS software(SUNWsamfsr and SUNWsamfsu packages) installed locally and you are configuringfile systems on the server to be archiving, it is recommended that you have at leastone tape library associated with the current server.

The following table describes archiving configuration guidelines, on a per-tape-library basis, that can prevent you from over-extending your environment.

Always make a minimum of twofile copies on two separatevolumes.

Placing data on a single media type puts your data atrisk if physical problems with the media occur. Donot rely on a single archive copy. For informationabout creating archive copies, see “Adding a Copyto a Policy” on page 130.

Schedule metadata snapshots tooccur on a regular basis.

You can use the information stored in a metadatasnapshot to recover an archiving file system in theevent of a disaster. Make sure that files are archivedbefore the snapshot is created. For moreinformation, see “About Protecting Archiving FileSystem Data” on page 71.

TABLE 7-3 Archiving Configuration Guidelines

Number of TapeDrives

Number ofCustom Policiesto Create

Maximum Numberof File Systems toCreate

Maximum Numberof Files in EachFile System Library Recycler Values

2–3 1 4 6 million • Minimum Gain - 90%• VSN Limit (#) - 2• High Water Mark - 50%• Size Limit - 30 Gbytes




TABLE 7-2 Archiving Recommendations (Continued)



About Continuous ArchivingContinuous archiving eliminates the need for the archiver to periodically scan anarchiving file system. With continuous archiving, the archiving file system notifiesthe archiver when files have changed and the archiver determines how and when toschedule archiving based on the Start Age, Start Count, and Start Size values definedin the copies of the policy associated with those files.

To enable continuous archiving for all archiving file systems on the current server,choose the No Scan scan method on the General Setup page. To enable continuousarchiving for an individual archiving file system, choose the No Scan method on theFile System Archive Policies page for that file system. Any setting that you make onthe File System Archive Policies page overrides the equivalent setting on the GeneralSetup page.

To specify Start Age, Start Count, and Start Size values for all archiving file systemson the current server, edit the values in the copies of the configurable defaults(allsets) archive policy. To override the settings in the configurable defaults policy,specify Start Age, Start Count, and Start Size values in the individual copies of anyother archive policy. You do this on the Advanced Copy Options page of an archivepolicy.

The following examples describe how the policy copy values affect continuousarchiving:

■ Start Age – If it takes one hour to create files that must be archived together, youcan create a policy copy and can define the Start Age value in the copy to be 1hour. This ensures that all necessary files are created before archiving begins.

■ Start Size – If you want the archiver to wait until a specific amount of data isready to be archived, you can create a policy copy and specify the Start Size valueto be 150 Gbytes, for example. This directs the archiver to wait until 150 Gbytes ofdata are ready to be archived.

■ Start Count – If you know that 3000 files will be generated for archival, you cancreate a policy copy and specify the Start Count value to be 3000. This ensuresthat all 3000 files will be archived together.


About Associative ArchivingAssociative archiving is useful if you want to archive an entire directory to onevolume and if all the contents in that directory will fit on a single archive volume.You can enable associative archiving by selecting the Force files in a directory to bearchived together check box in an archive policy copy.

When files are archived, they are grouped together in one or more archive files toefficiently pack the volume. Subsequently, when accessing files from the samedirectory, you can experience delays as the stage process repositions through avolume to read the next file. To alleviate delays, you can archive files from the samedirectory paths contiguously within an archive file. The process of associativearchiving overrides the space efficiency algorithm to keep files from the samedirectory together. You can specify that these files are to be archived contiguouslywithin a copy of an archive policy.

Associative archiving is useful when the file content does not change and youalways want to access the group of files together at the same time. For example, youmight use associative archiving at a hospital for accessing medical images. Imagesassociated with a single patient can be kept in a single directory, enabling a doctor toaccess those images together at one time.

However, because associative archiving specifies that all files from the samedirectory be archived on a single volume, it is possible that a group of files might notfit on any available volume. In this case, the files are not archived until morevolumes are assigned to the archive policy. Another issue is that the group of files tobe archived might be so large that it can never fit on a single volume. In such a case,the files are never archived.

An alternative to associative archiving is the sorting of files by path. Sorting keepsfiles together, but does not force the files to be archived together. You can specifysorting in the copy of an archive policy.

About the ReleaserThe releaser is a component of the Sun StorEdge SAM-FS software. After a file isarchived, it becomes eligible to be released. The releaser frees primary (disk) storagethat is used by the archived file's data. Two threshold values, High Water Mark andLow Water Mark, manage online disk cache free space. You can define thesethresholds values when you create an archiving file system or when you edit themount options of an archiving file system.


When online disk consumption exceeds the High Water Mark threshold, the systemautomatically begins releasing the disk space occupied by eligible archived files.Disk space occupied by archived file data is released until the Low Water Markthreshold is reached. Files are selected for release depending on file size and age.

Optionally, the first portion of a file can be retained on disk for speedy access and formasking staging delays. If a file has been archived in segments, portions of the filecan be released individually.

About the StagerThe stager is a component of the Sun StorEdge SAM-FS software. When a file whosedata blocks have been released is accessed, the stager automatically stages the file orfile segment data block back to online disk cache. The read operation tracks alongdirectly behind the staging operation, allowing the file to be immediately availableto the application before the entire file is completely staged.

The Sun StorEdge SAM-FS software processes stage request errors automatically. If astage error is returned, the system attempts to find the next available archive copy ofthe file. Stage errors that can be automatically processed include media errors,unavailability of media, and unavailability of an automated library, among others.

Controlling Archiving forArchiving File SystemsThis section provides information about configuring archiver scanning, and aboutstopping, idling, and running archiving for archiving file systems. It contains thefollowing subsections:

■ “Configuring Archiver Scanning for an Archiving File System” on page 110

■ “Stopping or Idling Archiving for an Archiving File System” on page 110

■ “Running Archiving for an Archiving File System” on page 111


Configuring Archiver Scanning for anArchiving File SystemIf you are administering an archiving file system, you can configure the archiverscan method, scan interval, and log file location for the file system. This controlswhen the software scans for files on the file system to be archived.

To configure archiver scanning for a file system:

1. From the Servers page, click the name of the server that you want to configure.


2. Click the radio button next to the file system for which you want to configurearchiving values.

3. Click View Policies.


4. Specify the following:

■ Scan Method – Choose how the archiver scans for files in the file system to bearchived. For more information, see “About Archiver Scanning Methods” onpage 136.

■ Interval – Choose how often the archiver log file is updated.

■ Log File – Type the location of the archiver log file.

5. Click Save.

Stopping or Idling Archiving for anArchiving File SystemWhen you stop archiving, all archiving immediately stops on the selected archivingfile system. If you want to stop archiving at a logical point in the process, choose toidle archiving instead.

To stop archiving for a file system:




2. Select the radio button next to the file system for which you want to stoparchiving.

3. From the Operations menu, do one of the following:

■ To immediately stop archiving, choose Stop Archive.

■ To stop archiving at a logical point in the process, choose Idle Archive.

Running Archiving for an Archiving FileSystemTo run archiving for an archiving file system:



2. Select the radio button next to the file system on which you want to runarchiving.

3. From the Operations menu, choose Run Archive.

Managing Archive PoliciesThis section provides information about managing archive policies. It contains thefollowing subsections:

■ “Administering Archive Policies” on page 112

■ “Enabling Archiving Options in a Policy” on page 118

■ “Administering File Match Criteria” on page 123

■ “Administering Policy Copies” on page 128


Administering Archive PoliciesThis section provides information about administering archive policies. It containsthe following subsections:

■ “About Archive Policies” on page 112

■ “Reference: Creating a Policy archiver.cmd Example” on page 115

■ “Creating a Policy” on page 116

■ “Creating a No-Archive Policy” on page 116

■ “Editing a Policy” on page 117

■ “Deleting a Policy” on page 117

About Archive PoliciesAn archive policy is a collection of file system directives, copy directives, copyparameters, and volume associations that determine how groups of files can bearchived. When the documentation refers to a policy, it is referring to a custompolicy unless otherwise specified.

The following table describes the types of archive policies.

TABLE 7-4 Archive Policy Types

Policy Type Description

File system default A policy that is automatically created when you create anarchiving file system. It archives the metadata for thearchiving file system and archives all files that do not meetany file match criteria defined in any custom or no-archivepolicies that are applied to the archiving file system. Each filesystem default policy has the same name as its archiving filesystem.You can edit this type of policy, but you cannot delete it. It isautomatically deleted when you delete its archiving filesystem. You cannot edit the file match criteria in this policyand you cannot apply the policy to other archiving filesystems.


A policy consists of the following attributes:

■ A policy name

■ One or more sets of file match criteria that can contain:

■ A starting directory, which is a path relative to the mount point of the filesystem

■ Optional search criteria based on the following options:

File name that uses pattern matching

User name and/or group name

Custom A policy that you can create for the purpose of archiving agroup of files according to a different set of rules and,optionally, to different archive media than those specified inthe file system default policy. You define the name of thepolicy and one or more sets of file match criteria thatdetermine which files can be archived.You can edit and delete a custom policy, and the file matchcriteria of a custom policy can be applied to more than onearchiving file system.Note: When the documentation refers to a policy, it is referringto a custom policy unless otherwise specified.

No-archive A policy that you can create for the purpose of preventing filesfrom being archived. There can be only one no-archive policyon a server at a time, and the policy always has the name ofno_archive. This policy does not have any copies, but youcan add file match criteria to the policy to prevent moregroups of files from being archived. The file match criteria inthis policy can be applied to numerous archiving file systems.You can edit and delete the no-archive policy.

Configurabledefaults

A policy that always exists and has the name of allsets.This policy enables you to set default values for advancedcopy options and volume serial name (VSN) assignments.These default values are applied to all custom and file systemdefault policies on the current server.For example, if you set a value in copy 1 of the configurabledefaults policy, this value is set in copy 1 of all the custom andfile system default policies on the server.In addition to having copies 1 through 4, the configurabledefaults policy has an allsets copy. The settings in theallsets copy apply to all other copies on the server.However, any setting in a specific policy overrides the valuesin the configurable defaults policy.You cannot delete this policy.

TABLE 7-4 Archive Policy Types (Continued)

Policy Type Description


Minimum and/or maximum file size

Access age

■ Release or stage attributes

■ Archive age for each copy

■ Unarchive age and release options for each copy

■ At least one file system (no maximum limit) to which the set of match criteria isapplied

■ From one to four archiving copies of the files from the member file systems thatmatch the file match criteria specified in the policy

When you create an archive policy, you must specify whether each copy to be madewill be made to disk or to tape.


Reference: Creating a Policy archiver.cmdExampleAfter you create an archive policy through the browser interface and you associatethe policy with file systems, the system adds additional lines to the archiver.cmdfile on the selected server. In the following example, the policy policy1 isassociated with the file systems samfs1 and samfs2.

...## File System Directives#...fs = samfs1policy1 dir1 -minsize 10k -maxsize 10M

1 4m 7d2 4m 7d

...fs = samfs2policy1 dir1 -minsize 10k -maxsize 10M

1 4m 7d2 4m 7d

## Copy Parameters Directives#paramspolicy1.1 -join pathpolicy1.1 -startage 301mpolicy1.1 -startsize 7Mpolicy1.2 -bufsize 9policy1.2 -drives 2policy1.2 -ovflmin 2M...endparams...## VSN Directives#vsns...policy1.1 lt BL794[2-4]policy1.2 lt BL7942 -pool pool2...endvsns


Creating a PolicyTo create a policy:

1. From the Servers page, click the name of the server for which you want to createa policy.




3. Click New.

The New Archive Policy wizard is displayed.

4. Complete the steps in the New Archive Policy wizard.


Creating a No-Archive PolicyWith a no-archive policy, you create a policy that does not contain any policy copies.Files that meet the file match criteria defined in the no-archive policy are neverarchived. This set of file match criteria in the policy maps directly to theno_archive set, which you can define by using the Sun StorEdge SAM-FScommand-line interface.

Only one no-archive policy can exist on a server at a time. If one already exists, youcannot create a new one without first deleting the existing one. Alternatively, youcan add additional file match criteria to the existing policy if you want to preventthe archiving of additional files.

To create a no-archive policy, follow the directions in “Creating a Policy” onpage 116, and choose to prevent files from being archived in the first step of the NewArchive Policy wizard. Upon creation, the no-archive policy is displayed on theArchive Policies Summary page.


Editing a PolicyTo edit a policy:

1. From the Servers page, click the name of the server where the policy that youwant to edit is configured.




3. Click the policy that you want to edit.

The Policy Details Page is displayed.


■ To add a set of file match criteria to the policy, click Add in the Archive Criteriatable, and then follow the steps in the New Criteria wizard.

■ To add a policy copy to the policy, click Add in the Copy Information table,and follow the steps in the New Copy wizard.

■ To edit an existing set of file match criteria, select the radio button next to thefile match criteria that you want, click Edit, and make your changes.

■ To edit an existing policy copy, click Edit Advance Options in the CopyInformation table and edit the fields that you want to change.

Deleting a PolicyDeleting a policy deletes the policy from the server’s configuration (archiver.cmdfile). This is different from removing the relationship between a file match criteria setand a file system.

To delete a policy:

1. From the Servers page, click the name of the server for which you want to deletea policy.




3. Select the radio button next to the policy that you want to delete, and click Delete.


4. Click OK.


Enabling Archiving Options in a PolicyThis section provides information about enabling archiving options in a policy. Itcontains the following subsections:

■ “Enabling Disk Archiving” on page 118

■ “Enabling Archiving to Tape” on page 119

■ “Enabling Associative Archiving” on page 120

■ “Enabling Continuous Archiving” on page 121

■ “Enabling Archiving to Pools of Disk or Tape VSNs” on page 122

Enabling Disk ArchivingWhen you create an archive policy, you can specify archiving to disk for one or morecopies of that archive policy. The File System Manager software will automaticallyadd the appropriate information in the diskvols.conf file, which enables diskarchiving for that copy or copies.

The File System Manager software can only add information to the diskvols.conffile. It does not edit previously written data, even if you attempt to edit the policythrough the browser interface.

You can enable disk archiving under the circumstances described in the followingsections:

■ “For a New Policy” on page 118

■ “For an Existing Copy in an Existing Policy” on page 119

■ “For a New Copy in an Existing Policy” on page 119

For a New Policy

To enable disk archiving for a new policy:

1. Follow the instructions in “Creating a Policy” on page 116.

2. When you configure media parameters for a copy in the New Archive Policywizard, choose Disk from the Media Type menu.

3. Continue through the wizard and click Finish.


For an Existing Copy in an Existing Policy

To enable disk archiving for an existing copy in an existing policy:

1. If you want to archive to a new disk volume, follow the instructions in “Creatinga Disk VSN” on page 135.

2. Navigate to the Policy Copy VSNs page for the copy in which you want to enabledisk archiving.

3. Choose Disk from the Media Type menu.

4. Specify the disk volume serial names (VSNs) that you want to use for archiving.

5. Click Save.

If you are managing a server that has the release 4, update 3, SUNWsamfsr andSUNWsamfsu packages installed locally, follow these steps to enable disk archivingfor an existing copy in an existing policy:


2. Choose Disk from the Media Type menu.

3. Specify the disk VSNs that you want to use for archiving.

4. Click Save.

For a New Copy in an Existing Policy

To enable disk archiving for a new copy in an existing policy, perform the following:

1. Follow the instructions in “Adding a Copy to a Policy” on page 130.

2. When you configure media parameters for the copy in the New Copy wizard,choose Disk from the Media Type menu.


Enabling Archiving to TapeWhen you create an archive policy, you can specify archiving to tape for one or morecopies of that archive policy.

You can enable archiving to tape under the circumstances described in the followingsections:





For a New Policy

To enable archiving to tape for a new policy:

1. Follow the instructions in “Creating a Policy” on page 116.

2. When you configure media parameters for a copy in the New Archive Policywizard, choose one of the tapes listed in the Media Type menu.



To enable archiving to tape for an existing copy in an existing policy:


2. Choose one of the tapes listed in the Media Type menu.

3. Specify the tape VSNs that you want to use for archiving.

4. Click Save.


To enable archiving to tape for a new copy in an existing policy:

1. Follow the instructions in “Adding a Copy to a Policy” on page 130.

2. When you configure media parameters for the copy, choose one of the tapes listedin the Media Type menu.


Enabling Associative ArchivingAfter you have created a policy, you can specify associative archiving for one ormore copies of that policy.


To enable associative archiving for a policy:

1. From the Servers page, click the name of the server where the policy that youwant to edit is configured.






4. In the Copy Information table, click the copy that you want to edit.

The Copy Details page is displayed.

5. In the Archive Organization section, select the Force files in a directory to bearchived together check box.

6. Click Save.

Enabling Continuous ArchivingYou can enable continuous archiving for all archiving file systems on the currentserver or for a specific file system.

To enable continuous archiving:

1. Do either of the following:

■ To enable continuous archiving for all archiving file systems on the currentserver, navigate to the General Setup page under the Archive Management tab,and choose No Scan as the scan method.

■ To enable continuous archiving for a specific file system, navigate to the FileSystem Archive Policies page for that file system and choose No Scan as thescan method.

2. Set the Start Age, Start Count, or Start Size values in the appropriate policy:

a. From the Servers page, click the name of the server that you want to configure.


b. Click the Archive Management tab.


c. Do either of the following:


i. To set values for all archiving file systems on the current server, click theconfigurable defaults policy.

The Policy Details page is displayed.

ii. To set values for a specific file system, click the file system default policy forthat file system.


d. In the Copy Information table, click the copy for which you want to enablecontinuous archiving.

The Policy Copy (Tape) Details or the Policy Copy (Disk) Details page isdisplayed.

e. Edit the values in one or more of the following fields:

Start Age

Start Count

Start Size

f. Click Save.

Archiving is scheduled according to the specified values.

Enabling Archiving to Pools of Disk or Tape VSNsYou can enable archiving to pools of disk or tape volume serial names (VSNs).

You can enable archiving to pools of disk or tape VSNs under the circumstancesdescribed in the following sections:




For a New Policy

To enable archiving to pools of disk or tape volumes in a new policy, follow thedirections in “Creating a Policy” on page 116, and do one of the following in theNew Archive Policy wizard:

■ On the Copy x - Media Parameters step, choose a VSN pool from the VSN Poolmenu.

■ On the Copy x - Media Parameters step, specify a range of VSNs or type acomma-separated list of VSNs in the Specify VSNs section.



To enable archiving to pools of disk or tape volumes in an existing copy of anexisting policy, follow steps 1 through 5 in “Modifying VSN Assignments in a PolicyCopy” on page 129 and then do one of the following:

■ Choose a VSN pool from the VSN Pool menu, and click Save.

■ Specify a range of VSNs, or type a comma-separated list of VSNs in the SpecifyVSNs section, and click Save.


To enable archiving to pools of disk or tape volumes in a new copy of an existingpolicy, follow the directions in “Adding a Copy to a Policy” on page 130, and do oneof the following in the New Copy wizard:

■ On the Copy Media Parameters step, choose a VSN pool from the From the VSNPool menu.

■ On the Copy Media Parameters step, specify a range of VSNs or type a comma-separated list of VSNs in the Specify VSNs section.

Administering File Match CriteriaPolicies consist of policy copies and sets of file match criteria. The sets of file matchcriteria define archiving directives for the files that meet the criteria.

This section provides information about file match criteria. It contains the followingsubsections:

■ “About File Match Criteria” on page 124

■ “Editing File Match Criteria” on page 124

■ “Adding a File System to a Set of File Match Criteria” on page 125

■ “Removing a File System From a Set of File Match Criteria” on page 126

■ “Planning File Match Criteria” on page 126

■ “Adding File Match Criteria to a Policy” on page 127

■ “Removing File Match Criteria From a Policy” on page 128


About File Match CriteriaWhen you create a policy, you define a single set of file match criteria that identifiesgroups of files to be archived. After you create the policy, you can add additionalsets of file match criteria to the policy to further identify groups of files to bearchived.

File match criteria can be based on file size, ownership, group, and directorylocation. Once a set of criteria is defined, you can associate it with archiving filesystems. When files on the associated archiving file systems meet the criteria definedin a policy, the files are copied to the volumes that are defined in the copies of thepolicy.

You can add a set of file match criteria to or remove it from an existing policy.However, a policy must have at least one set of file match criteria at any time. If apolicy has only one set of file match criteria, the criteria cannot be removed from thepolicy. You must delete the policy itself.

You can add and remove the relationship between an archiving file system and a setof file match criteria. However, a set of file match criteria cannot exist without atleast one member file system. You cannot remove a relationship between anarchiving file system and a set of file match criteria if the file system is the solerelationship with the set of criteria. In this case, you must delete the set of file matchcriteria itself.

Additionally, an archiving file system cannot be deleted if it is the only archiving filesystem associated with an existing set of file match criteria. In this case, you mustremove the set of file match criteria from the policy and then you can delete thearchiving file system.

Editing File Match CriteriaTo edit file match criteria:

1. From the Servers page, click the name of the server with the policy that you wantto edit.




3. Click the policy that contains the file match criteria set that you want to edit.


4. Select the radio button next to the file match criteria set that you want and clickEdit.




Adding a File System to a Set of File MatchCriteriaAdding an archiving file system to a set of file match criteria enables the files in thatfile system to be archived according to the archiving directives defined in the set. Allfiles that match the defined file match criteria will be archived.

By default, when you add an archiving file system to a set of file match criteria, theset of file match criteria is placed at the bottom of the list of criteria that are alreadyapplied to the file system. For information about reordering file match criteria for anarchiving file system, see “Reordering File Match Criteria for an Archiving FileSystem” on page 70.

To add an archiving file system to a set of file match criteria:

1. From the Servers page, click the name of the server on which the set of file matchcriteria is defined.




3. Click the policy that contains the file match criteria for which you want to add afile system.


4. Click the radio button next to the file match criteria that you want and click Edit.


5. Scroll down to the File Systems Using Criteria table and click Add.

The Apply Criteria to File Systems window is displayed.

6. Select the file system that you want to add to the file match criteria, and clickSubmit.


Removing a File System From a Set of File MatchCriteriaRemoving an archiving file system from a set of file match criteria does not deletethe archiving file system or the file match criteria set. Instead, it removes therelationship between the file system and the file match criteria set. Once thisrelationship is removed, files in the file system are no longer archived according tothe archiving directives defined in the set of file match criteria.

To remove an archiving file system from a set of file match criteria:





3. Click the policy that contains the file match criteria that you want to edit.


4. Click the radio button next to the set of file match criteria that you want, and clickEdit.


5. In the File Systems Using Criteria table, select the radio button next to the filesystem that you want to remove, and click Remove.


6. Click OK.

Planning File Match CriteriaThe New Criteria wizard guides you through the process of adding file matchcriteria to an existing policy. See “Adding File Match Criteria to a Policy” onpage 127 for instructions on accessing the New Criteria wizard.

The wizard requires that you enter the following information, which you shouldplan before you begin the process of adding file match criteria:

■ The name of the directory, relative to the mount point of the file system, to whichthis set of file match criteria should be applied. All files and subdirectories in thisdirectory will be archived according to the directives defined in this set of filematch criteria.


■ A regular expression that identifies a file as a member of this archive policy. Forexample, if you want all .gif files to be archived according to the directives inthis archive policy, .gif would be the value of the regular expression.

■ The user name of the owner of the files that you want archived.

■ The group to which the owner of the files belongs.

■ The smallest size that an archive file can be in order to be archived.

■ The largest size that an archive file can be in order to be archived.

■ The length of time during which a file must be accessed for it to meet the filematch criteria.

■ Whether you want to stage when files are accessed, and if so, whether you wantall files in the policy to be staged, to stage only when files are accessed directlyfrom archive media, or to reset all files to the default staging configuration.

■ When you want to release a file from disk cache. You can choose not to release thefile, to free up online disk cache after the first archive copy is made, or to releasea file after all archive copies are made.

■ When a file should be unarchived, based on the last time the file was modified orthe last time the file was accessed.

Adding File Match Criteria to a PolicyTo add a set of file match criteria to an existing policy:







4. In the Archive Criteria table, click Add.

The New Criteria wizard is displayed.

5. Complete the steps in the New Criteria wizard.



Removing File Match Criteria From a PolicyRemoving a set of file match criteria removes the criteria from the policy. This isdifferent from removing the file match criteria association with a file system.

A policy must have at least one set of file match criteria at any time. You cannotdelete a set of file match criteria if it is the only remaining set in a policy. Instead,you must delete the policy itself.

To remove a set of file match criteria from a policy:







4. In the Archive Criteria table, select the radio button next to the set of file matchcriteria that you want to remove, and click Remove.


5. Click OK.

Administering Policy CopiesThis section provides information about administering policy copies. It contains thefollowing subsections:

■ “About Policy Copies” on page 129

■ “Editing a Policy Copy” on page 129

■ “Modifying VSN Assignments in a Policy Copy” on page 129

■ “Adding a Copy to a Policy” on page 130

■ “Removing a Copy From a Policy” on page 130


About Policy CopiesA policy must have between one and four archiving copies. When a file meets thefile match criteria defined in a policy, the file is archived to the media defined in thepolicy copy.

The values in the Start Age, Start Count, and Start Size fields in a policy copy arevery important in determining the way in which the software copies files to archivemedia. For more information, see “About Continuous Archiving” on page 107.

Editing a Policy CopyTo edit an existing copy in a policy:







4. In the Copy Information table, click the copy that you want to edit.

The Policy Copy Details page for that copy is displayed.


Modifying VSN Assignments in a Policy CopyYou can change the volume serial names (VSNs) that are assigned to a policy copyfor archiving.

To modify the VSN assignments in a policy copy:








4. In the Copy Information table, select the radio button next to the policy copy thatyou want to edit, and click Modify VSN Assignments.

The Policy Copy VSNs page is displayed.


Adding a Copy to a PolicyTo add a new copy to an existing policy:







4. In the Copy Information table, click Add.

The New Copy wizard is displayed.

5. Complete the steps in the New Copy wizard.


Removing a Copy From a PolicyDeleting a copy removes the copy from the policy.

A policy must have at least one copy. You cannot delete a copy if it is the onlyremaining copy in a policy. Instead, you must delete the policy itself.

To remove a copy from a policy:








4. In the Copy Information table, select the radio button next to the copy that youwant to remove, and click Remove.


5. Click OK.

Managing VSN Pools forArchivingThis section provides information about managing volume serial name (VSN) pools.It contains the following subsections:

■ “About VSN Pools” on page 131

■ “Creating a VSN Pool” on page 132

■ “Editing a VSN Pool” on page 132

■ “Deleting a VSN Pool” on page 133

About VSN PoolsA volume serial name (VSN) pool specifies a collection of individual VSNs, orvolumes. This collection is used as archive media for an archive policy. As such, VSNpools provide a useful method for assigning VSNs and reserving VSNs to archivepolicies.

You can use VSN pools to define separate groups of VSNs for use by departmentswithin an organization, users within a group, data types, and other groupings. Thepool is assigned a name, media type, and a set of VSNs. A scratch pool is a set ofvolumes used when specific volumes in a VSN association are exhausted or whenanother VSN pool is exhausted.

If a VSN is reserved, it is no longer available to the pool in which it originated.Therefore, the number of VSNs within a named pool changes as VSNs are used.

A VSN pool definition requires at least three fields: the pool name, the media type,and at least one VSN.


Creating a VSN PoolTo create a volume serial name (VSN) pool:

1. From the Servers page, click the name of the server on which you want to create aVSN pool.




3. Click VSN Pools.

The VSN Pool Summary Page is displayed.

4. Click New.

The New VSN Pool window is displayed.

5. Enter a name for the new pool.

6. Select a media type from the Media Type menu.

7. Select one of the following VSN options, and enter the information for thatoption.

■ Start – To specify a single range of VSNs, type the name of a VSN in the Startfield and type the name of a VSN in the End field.

■ Range of VSNs – To specify more than one range of VSNs, type a range ofVSNs separated by a comma or type individual VSN names separated by acomma. Use the following syntax:

EW4276-EW4288,KQ7086,FV8434

8. Click Save.

Editing a VSN PoolTo edit a volume serial name (VSN) pool:

1. From the Servers page, click the name of the server with the VSN pool that youwant to edit.





3. Click VSN Pools.


4. Select the radio button next to the VSN pool that you want to edit.

5. Click Edit.

The the Edit VSN Pool window is displayed.

6. (Optional) From the Media Type menu, choose a different media type.

7. (Optional) In the Specify VSNs section, choose one of the following:

■ Start – To specify a new range of VSNs, type a new name of a VSN in the Startfield and type a new name of a VSN in the End field.

■ Range of VSNs – To specify more than one new range of VSNs, type a newrange of VSNs separated by a comma or type new individual VSN namesseparated by a comma. Use the following syntax:

EW4276-EW4288,KQ7086,FV8434

8. Click Save.

Deleting a VSN PoolA volume serial name (VSN) pool can be deleted only if its member VSNs are notbeing used by a policy. If a VSN pool has a member that is being used by a policy,the Delete button is unavailable.

To delete a VSN pool:

1. From the Servers page, click the name of the server with the VSN pool that youwant to delete.




3. Click VSN Pools.



4. Select the radio button next to the VSN pool that you want to delete, and clickDelete.


5. Click OK.

Managing Disk VSNs forArchivingThis section provides information about managing disk volume serial names (VSNs)for archiving. It containst the following subsections:

■ “About Archiving to Disk VSNs” on page 134

■ “Creating a Disk VSN” on page 135

■ “Editing the Media Attributes of a Disk VSN” on page 135

About Archiving to Disk VSNsIn an archive policy, you can choose to send archive copies of your files to diskvolume serial names (VSNs). Disk VSNs are directories in a mounted file system thathave been assigned volume names. The disk VSNs that you specify in the policy canbe located on a file system on the current server or on a different server. The filesystem on which the disk VSNs are located can be any UNIX file system. However,if the file system is located on a server other than the current server, there must be atleast one archiving file system configured on that other server.

There are no restrictions on the location of disk VSNs on a file system, but it isrecommended that disk VSNs reside on a disk other than where the original filesthat you are archiving reside. It is also recommended that you make more than onecopy in a policy and write to more than one type of archive media. For example, thefirst copy in a policy could be written to disk, the second copy could be written totape, and so on.

The Disk VSNs tab is displayed under the Archive Management tab in theapplication. From the Disk VSNs tab, you can create disk VSNs and can edit themedia attributes of a disk VSN through the browser interface.


Creating a Disk VSNTo create a disk volume serial name (VSN):

1. From the Servers page, click the server for which you want to create a disk VSN.




3. Click the Disk VSNs local tab.

The Disk VSNs page is displayed.

4. Click New.

The New Disk VSN window is displayed.

5. Specify the following:

■ Name – Type the name of the new disk VSN. This can be from one to sixcharacters from the following categories:

Uppercase letters from A to Z

Numerals from 0 (zero) to 9

The following special characters: ! “ % & ‘ ( ) * + , . / : ; < > = ? _

■ Host – Choose the server on which the file system that will contain the diskVSN.

■ Path – Type the full path to the directory in which you want to store archivecopies. If you do not know the path, click Browse to find it.

6. Click Submit.

Editing the Media Attributes of a DiskVSNTo edit the media attributes for a disk volume serial name (VSN):

1. From the Servers page, click the server for which you want to create a disk VSN.





3. Click the Disk VSNs local tab.

The Disk VSNs page is displayed.

4. Select the disk VSN that you want to edit and click Edit Media Flags.

The Edit Disk Media Flags window is displayed.

5. Select the check boxes next to the attributes that you want for the media on whicha disk volume is located, and click Submit.

Setting Up General ArchivingThis section provides information about setting up general archiving. It contains thefollowing subsections:

■ “About Archiver Scanning Methods” on page 136

■ “Configuring Global Archiving Values” on page 137

■ “Configuring Global Staging Values” on page 138

■ “Configuring Global Releasing Values” on page 138

■ “Configuring Global Media Type Parameters” on page 139

About Archiver Scanning MethodsIf you are managing a server that has the Sun StorEdge SAM-FS package installedlocally, you can define how the software scans the archiving file systems on thecurrent server for archiving. Each scanning method determines which files on thearchiving file systems need to be archived and determines the archiving schedule.Scanning occurs at the time intervals that you specify on the General Setup page oron the File System Archive Policies page.

Scanning methods defined on the General Setup page are overridden by thescanning method defined on the File System Archive Policies page for a file system.


You can choose the scanning methods described in the following table.

Configuring Global Archiving ValuesIf you are managing a server that has the Sun StorEdge SAM-FS package installedlocally, you can configure global archiving values for all archiving file systems on thecurrent server. When you configure global archiving values, the archiver.cmd fileis updated.

To configure global archiving values:



TABLE 7-5 Scanning Methods

Scan Method Description

Traditional Scan The software performs several scans of each file system on the current server. Thefirst file system scan descends recursively through the directory tree. Each file isexamined, and files that do not need to be archived are flagged. During successivescans, the .inodes file is examined. The software examines only the inodes that arenot flagged. Upon scan completion, the software sends the archive requests to thearchiver daemon to be scheduled for file copying to media.

Scan Directories The software performs a directory scan of each file system on the current server. Thedirectory scan descends recursively through the directory tree of each file system.Files that do not need to be archived are flagged. The software assumes that allremaining files need archiving. Upon scan completion, the software generates archiverequests based on its finding and sends the requests to the archiver daemon to bescheduled for file copying to media. This method might be useful if the majority ofyour files always need to be archived.

Scan inodes The software scans the .inodes file. All inodes that are not flagged are examined. Afile is flagged if it does not need to be archived. Upon scan completion, the softwaregenerates archive requests based on its findings. This method might be useful if youknow which files are changed on a regular basis. This scan method will examine onlythose files, without performing a larger scan.

No Scan The software does not scan the file systems on the current server to determine thefiles to be archived. Instead, the software works with the file system to determinewhat files need to be archived. The archiver determines when to begin archiving byusing the Start Age, Start Count, and Start Size values that you define in your policycopies. This is the default archiving method, otherwise known as continuousarchiving.


2. Click the Archive Management tab, and then click the General Setup tab.

The General Setup page is displayed.

3. Edit the archiver-specific fields that you want to change, and click Save.

Configuring Global Staging ValuesIf you are managing a server that has the Sun StorEdge SAM-FS package installedlocally, you can configure global staging values for all archiving file systems on thecurrent server. The stager restores file data to the disk cache. When a user or processrequests file data that has been released from the disk cache, the stager automaticallycopies the file data back to the online disk cache.

When you configure global staging values, the stager.cmd file is updated.

To configure the stager:

1. From the Servers page, click the name of the server for which you want toconfigure the stager.


2. Click the Archive Management tab and click the General Setup local tab.


3. Edit the stager-specific fields that you want to change, and click Save.

Configuring Global Releasing ValuesIf you are managing a server that has the Sun StorEdge SAM-FS package installedlocally, you can configure global releasing values for all archiving file systems on thecurrent server. Releasing is the process of freeing primary (disk) storage that is usedby an archived file’s data. Files are selected for release according to criteria such asage.

When you configure global releasing values, the releaser.cmd file is updated.


To configure the releaser:

1. From the Servers page, click the name of the server for which you want toconfigure the releaser.


2. Click the Archive Management tab, and click then the General Setup tab.


3. Edit the releaser-specific fields that you want to change, and click Save.

Configuring Global Media TypeParametersIf you are managing a server that has the Sun StorEdge SAM-FS package installedlocally, you can configure global archiving and staging parameters for each availablemedia type that is associated with the current server. When you configure globalarchiving and staging parameters, the archiver.cmd and the stager.cmd files areupdated.

To configure media type parameters:



2. Click the Archive Management tab, and then click the General Setup tab.


3. Edit the fields that you want to change in the Media Type Parameters and DriveLimits section of the page, and click Save.


Configuring the RecyclerThis section provides information about the recycler. It contains the followingsubsections:

■ “About the Recycler” on page 140

■ “Running Recycling” on page 141

■ “Configuring Library Recycling Values” on page 142

■ “Configuring Policy Recycling Values” on page 143

About the RecyclerThe recycler is a component of the Sun StorEdge SAM-FS software that prevents youfrom overextending the archive disk volumes or removable media in yourenvironment. It does this by freeing up space on volumes that contain expiredarchive copies.

As users modify files on archiving file systems, archive copies associated with theold versions of these files are considered to be expired on their archive disk volumesor removable media. These copies can be purged from the system to make room fornew copies.

The recycler attempts to purge the expired copies first by selecting volumes that areeligible to be recycled and then by recycling the eligible volumes.

Selecting Eligible Volumes

The recycler selects volumes for recycling based on the amount of space used byexpired archive copies as a percentage of total space on the volume. The volumeswith the highest percentages of expired copies are selected to bring the storage usagebelow the configured High Water Mark threshold.

After the volumes are selected, the recycler determines whether the volumes wouldgain enough space after recycling to warrant the operation. The recycler determinesthis by examining the value in the Minimum Gain field either on the Recycler page(for volumes in a library) or in the archive copy (for volumes associated with apolicy). If the selected volumes do not meet this criterion, they are not recycled.


Recycling Volumes

If the selected volumes are considered eligible for recycling, the recycler starts therecycling process. Volumes are recycled differently, depending on whether thevolume is a disk volume or whether it is a removable cartridge in a library:

■ When a disk volume is selected for recycling, additional archive copies can still bewritten to it. However, expired archive copies on the disk volume are identifiedand removed. Valid archive copies are left alone.

■ When a tape or magneto-optical volume is selected for recycling, the systemprevents additional archive copies from being written to it. If you are recycling tocartridges in a library, all files with active archive copies in volumes on thecartridge are marked to be rearchived. The archiver moves these copies to othervolumes. In subsequent runs, the recycler checks these volumes to ensure that allvalid archive copies have been relocated.

The recycler then determines wether there are volumes that contain only expiredarchive copies. If it finds a volume in this condition, the recycler performs one ofthe following actions, according to the user-defined recycler settings:

■ Relabels the volume for immediate reuse.

■ Exports the volume from the library (ejects the cartridge from the library,which makes the that slot available for a new volume). The volume can then bemoved to offsite storage. A historical record of file changes in the volume ispreserved in the Historian.

You define library recycling directives on the Recycler page, which controls recyclingfor all volumes in the library. Alternatively, you can define archive policy-basedrecycling for disk or tape volumes in the Archive Policy Based Recycling section ofan archive policy copy. Archive policy-based recycling is the only way to recycledisk volumes.

For information about recommended recycler settings for libraries, see “AboutArchiving, Releasing, and Staging” on page 102.

Running RecyclingIf you are managing a server that has the SUNWsamfsr and SUNWsamfsu packagesinstalled locally, you can automatically run recycling at off-peak hours by logging into the current server as root and specifying a schedule in the crontab(1) file. Formore information, see the crontab(1) man page. You can also run recycling ondemand at any time.


When you run recycling, the recycler looks in the recycler.cmd(1M) and thearchiver.cmd(1M) files for recycling directives. The recycler.cmd(1M) filespecifies recycling directives for the libraries associated with the server you areadministering.

To define recycler settings for libraries in the browser interface, go to the Recyclerpage. The values you specify are reflected in the recycler.cmd(1M) file.

The archiver.cmd(1M) file specifies recycling directives for the volumes that areassociated with archive policies. To define recycler settings for volumes associatedwith archive policies in the browser interface, go to the Archive Policy BasedRecycling section of an archive policy copy. The values you specify are reflected inthe archiver.cmd(1M) file.

To run recycling on demand, perform the following:

1. Log in to the server for which you want to run recycling.

2. At the command line, type the following:

sam-recycler

3. Log out of the server.

Configuring Library Recycling ValuesThe recycler clears volume serial names (VSNs) in a library of expired archive copiesand makes the volumes available for reuse. For information about recyclerconfiguration guidelines for a library, see “Planning for Archiving” on page 105.

If you are managing a server that has the SUNWsamfsr and SUNWsamfsu packagesinstalled locally, you can configure the recycler for volumes in a library.

To configure the recycler for volumes in a library:

1. From the Servers page, click the name of the server for which you want toconfigure the recycler.


2. Click the Archive Management tab, and then click the Recycler tab.

The Recycler page is displayed.


3. Configure recycling values for each library listed on this page, and click Save.

Note: If you configure the recycler to automatically export a volume after recyclingit, it is recommended that you manually move the exported volume to offsitestorage. This ensures that old data is maintained in the event of a disaster.

Configuring Policy Recycling ValuesThe recycler clears expired archive copies from disk or tape volumes that areassociated with archive policies. Archive policy-based recycling is the only way torecycle disk volumes.

If you are managing a server that has the SUNWsamfsr and SUNWsamfsu packagesinstalled locally, you can configure values for volumes associated with an archivepolicy.

To configure recycling values for volumes associated with an archive policy:







4. In the Copy Information table, click the name of the policy copy that you want toedit.

The Policy Copy Options page is displayed.

5. Edit the recycling-related fields that you want to change in the Archive PolicyBased Recycling section, and click Save.


Managing Archiving andStaging ActivityThis section provides information about controlling archiving and staging activityfor all archiving file systems on the current server. It contains the followingsubsections:

■ “Controlling Global Archiving Activity” on page 144

■ “Controlling Global Staging Activity” on page 145

■ “Staging a File or Directory on Demand” on page 145

Controlling Global Archiving ActivityYou can control archiving activity for all archiving file systems on the current server.

To control archiving activity:

1. From the Servers page, click the name of the server for which you want to controlarchiving activity.


2. Click the Archive Management tab and then click the Activity Management tab.

The Activity Management page is displayed.

3. In the Archiving section of the page, select the radio button next to the option thatyou want to control and click Submit Job.

To view the progress of the archiving activity, click the Jobs tab and look for the jobthat you submitted.


Controlling Global Staging ActivityYou can control staging activity for all archiving file systems on the current server.

To control staging activity:

1. From the Servers page, click the name of the server for which you want to controlstaging activity.


2. Click the Archive Management tab and then click the Activity Management tab.

The Activity Management page is displayed.

3. In the Staging section of the page, select the radio button next to the option thatyou want to control and click Submit Job.

To view the progress of the staging activity, click the Jobs tab and look for the jobthat you submitted.

Staging a File or Directory on DemandThe system automatically stages files and directories when you access them, butlarge files or sets of files may require a great deal of time to come online. You canavoid waiting for the system to stage files or directories by explicitly staging them.

This feature is available only if the server has either of the following packagesinstalled locally:



To stage a file or directory:

1. From the Servers page, click the name of the server for which you want to stagethe file or directory.


2. Select the radio button next to the file system for which you want to stage the fileor directory, and choose Stage from the Operations menu.

The Stage File Page page is displayed.


3. (Optional) In Maximum Files/Directories, specify the maximum number of filesor directories you want to retrieve, and click Apply.

A list of files and directories is displayed.

4. (Optional) To see a list of files within a directory, click the directory name.

5. Select the radio button next to the file or directory that you want to stage.

The Stage File window is displayed.

6. From the drop-down menu, choose the copy of the file or directory that you wantto stage.

7. (Optional) To recursively stage all files within a directory, select Recursively StageFiles in this Directory.

8. Click Submit.

The system displays a message indicating that the file or directory has beensuccessfully staged. Depending on the available system resources, the stagingprocess may take some time.


CHAPTER 8

Managing RemovableMedia

This chapter provides information about managing removable media. It contains thefollowing sections:

■ “About Removable Media Management” on page 147

■ “About Removable Media” on page 148

■ “About Supported Libraries and Drives” on page 149

■ “About the Historian” on page 150

■ “Managing Libraries” on page 150

■ “Managing Stand-Alone Tape Drives” on page 166

About Removable MediaManagementIf you are managing a server that has the SUNWsamfsr and SUNWsamfsu packagesinstalled locally, you can associate removable media with the archiving file systemson the server. Otherwise, the Media Management tab is not displayed in the browserinterface, and you cannot configure removable media.

If the current server does have the SUNWsamfsr and SUNWsamfsu packagesinstalled locally, you can bring stand-alone tape drives and automated librariesunder the control of Sun StorEdge SAM-FS software by adding the tape drives andlibraries to the browser interface. Adding libraries to the browser interfaceautomates the drive ordering of certain libraries. For more information, see “AboutSupported Libraries and Drives” on page 149.

147

In addition, when you add libraries to the browser interface, the libraries areautomatically added to the mcf file on the current server. The order in which librarydevices are listed in the mcf file on the server is the order in which the devices areused by the library.

Note: If a library is added to the mcf file before being added to the browserinterface, the library is not be displayed in the browser interface. In this case, youmust delete the library entry from the mcf file and then add the library to thebrowser interface.

After removable media devices are added to the mcf file, you can use the browserinterface to view the status of the removable media, view the details of libraries(drives and catalogs), and search for volume serial names (VSNs) across multiplelibraries. You can also load and unload a VSN, import and export a VSN, andmodify VSN media attributes.

When you perform any removable media operation, the software displays a messagetelling you whether the operation was started successfully. Some operations take along time to complete. To view the status of these operations, refresh the LibraryDetails or the Drive Details page.

About Removable MediaIf you want the archiving file systems on the current server to be archived toremovable media devices, you must have at least one available removable mediadevice, either an automated library with multiple drives or a stand-alone tape drive.For information about guidelines for archiving to a library, see “About Archiving,Releasing, and Staging” on page 102.

An automated library can be attached directly to a server through a small computersystem interface (SCSI) cable or Fibre Channel, or it can be attached through thenetwork. Devices from vendors such as Sony, Fujitsu, and IBM that attach to thenetwork require third-party software tools.

One or more library catalogs are associated with each automated library. The librarycatalog tracks the movement of removable media devices within the library. Forlibraries that are directly attached, a record of the volume serial names (VSNs) in thelibrary is maintained. There is one catalog for each automated library, and there isone Historian for all automated libraries at a site. All media recorded in a librarycatalog must be of the same media type, such as IBM 3570 or SONY AIT.

Stand-alone tape drives require that you load the removable media manually. Eachmanually loaded drive has its own one-slot library catalog.


Archive media devices that you intend to use must be attached to and recognized bythe current server. For more information, see the Sun StorEdge SAM-FS SoftwareInstallation and Upgrade Guide.

About Supported Libraries andDrivesWhen you add a library or drive to the browser interface, you bring the library ordrive under the control of the Sun StorEdge SAM-FS software. A library or drivecannot be listed in the Sun StorEdge SAM-FS mcf file on the current server beforebeing added to the browser interface.

Using the File System Manager interface, you can support bringing the followingtypes of libraries and drives under the control of Sun StorEdge SAM-FS software:

■ Small computer system interface (SCSI) direct attached libraries – The FileSystem Manager software can discover and display the tape libraries with thecorrect drive ordering after the library is attached to, and recognized by, thecurrent server. The libraries must meet the following criteria:

■ The target must be less than or equal to 6, and the library must have no LUNIDs (logical unit number identifiers) or have just one LUN ID.

■ If the target is larger than 6, or the library has more than one LUN ID, youmust configure the library properly so that it is attached to, and recognized by,the current server. This involves manually updating the samst.conf file onthe current server and then adding the library to the browser interface. Formore information, see the Sun StorEdge SAM-FS Software Installation andUpgrade Guide.

■ Fibre Channel direct attached libraries – The File System Manager software candiscover and display the tape libraries with the correct drive ordering after thelibrary is attached to, and recognized by, the current server. In addition, thesoftware updates the samst.conf file for the server with the World Wide Name(WWN), if the WWN does not already exist in the samst.conf file.

■ Network attached libraries – You can enter the name, type, and parameter filelocation of this library type. You are responsible for correctly ordering the drivesin the mcf file on the server, which you do by editing the parameter file of thelibrary. The following libraries of this type are supported:

■ IBM 3494

■ Sony PetaSite

■ STK ACSLS (Available only if the server has either of the following packagesinstalled locally: Release 4, update 5, SUNWsamfsr and SUNWsamfsu; orRelease 4, update 5, SUNWqfsr and SUNWqfsu.)

Chapter 8 Managing Removable Media 149

■ Fujitsu

■ ADIC and Grau

■ Stand-alone drives – The File System Manager software can discover and displaydrives that are left in the /dev/rmt location on the current server and that do notbelong to any of the libraries mentioned in this topic.

About the HistorianThe Historian is a catalog that keeps track of cartridges exported from an automatedlibrary or unloaded from manually loaded devices. The Historian is similar to thecatalog of an automated library but has no defined hardware devices associated withit.

Like an automated library, the Historian is configured in the mcf file, records entriesfor all cartridges associated with it, can import and export cartridges, and isdisplayed in the browser interface as an automated library.

By default, the Historian is created with 32 entries and can grow to be larger. Eachtime the catalog becomes full, 32 new entries of approximately 200 bytes each areadded. Given this, make sure that the file system on which the Historian resides hasenough storage space to support this potential growth.

Managing LibrariesThis section provides information about managing libraries:

■ “About Libraries” on page 151

■ “Adding a Library” on page 151

■ “Changing the State of a Library” on page 152

■ “Unloading a Library” on page 153

■ “Removing Archiving, Staging, and Recycling Configurations” on page 154

■ “Deleting a Library” on page 155

■ “Managing Library Drives” on page 156

■ “Managing VSNs in a Library” on page 158


About LibrariesLibraries are also known as media changers, jukeboxes, robots, automated libraries,or media libraries. The File System Manager software enables you to manage certainlibraries, assuming the current server has the SUNWsamfsr and SUNWsamfsupackages installed locally. For information about the types of libraries that aresupported, see “About Removable Media Management” on page 147.

Libraries are robotically controlled devices designed to load (import) and unload(export) removable cartridges without operator intervention. A library contains arobotic arm that is used to transport cartridges, slots in which to store cartridges,and one or more drives on which to mount cartridges.

Each cartridge in a library has one or more volumes. A volume is a named area on acartridge that is used for storing data. Double-sided cartridges have two volumes,one on each side. A volume serial name (VSN) identifies a volume.

You can use the File System Manager software to add libraries to or remove librariesfrom the archiving file system configuration. Archive policies for the site determinewhich libraries and drives to use for archiving and staging.

Adding a LibraryBefore adding a library to the browser interface, you must connect the librarydirectly either to the current server, or through the network. For more information,see the Sun StorEdge SAM-FS Software Installation and Upgrade Guide.

For information about the types of libraries that you can add to the configuration,see “About Supported Libraries and Drives” on page 149.

Before you can add a network-attached library through this wizard, you must ensurethat the parameter file for the library exists and that the drives are ordered correctlyin the parameter file.

Note: If you are adding one or more STK ACSLS (StorageTek Automated CartridgeSystem Library Software) libraries and are also adding one or more libraries that areattached directly to the current server, complete this procedure first for the STKACSLS libraries and then go back and complete the procedure for the directlyattached libraries. This sequence is necessary for proper operation of the system.


To add a library:

1. From the Servers page, click the name of the server to which you want to add alibrary.




3. Click Add.

The Add Library wizard is displayed.

4. Specify the type of library you want to add and click Next.

■ Select Direct Attached if the library is attached directly to the current server.

■ Select STK ACSLS if the library is an ACSLS library. This option is availableonly if the server has either of the following packages installed locally:

Release 4, update 5, SUNWsamfsr and SUNWsamfsu

Release 4, update 5, SUNWqfsr and SUNWqfsu

■ Select Network Attached if the library is attached to the server through thenetwork.

5. Enter information about the library as requested by the wizard. (The informationrequested varies depending on which type of library you select.)

6. If the Preferences option on the banner of the software is enabled, you areprompted to commit these changes or to save them to a file in a specifieddirectory without committing them. Make your selection and click Next.

7. Review the specified information for the new library. If you are satisfied, clickFinish. Otherwise, click Previous to make changes.

Changing the State of a LibraryA library can be in a state of On, Off, or Unavailable.

■ When a library is On, it is under the control of the Sun StorEdge SAM-FSsoftware. This enables the Sun StorEdge SAM-FS software to perform thefollowing actions:

■ Discover the internal state of the library, such as the location of tapes, whetherbarcodes are used, and so on.

■ Update the library catalog and other internal structures.


■ When a library is Off, it is no longer under the control of the Sun StorEdge SAM-FS software, which stops I/O operations and the automatic movement ofcartridges. The drives in the library continue to be in the On state.

You might want to turn off a library for the following reasons:

■ To stop Sun StorEdge SAM-FS operations for this library only.

■ To power down the automated library.

■ When a library is Unavailable, you can reconfigure the library, such asconfiguring its cartridges.

To change the state of a library:

1. From the Servers page, click the name of the server that you want to administer.




3. Select the radio button next to the library whose state you want to change.

4. From the Operations menu, choose Change State.

The Change State window is displayed.

5. Select the state that you want, and click Submit.

Unloading a LibraryWhen you unload a library, all the volume serial names (VSNs) in the library areremoved and placed into the Historian catalog. This changes the state of the libraryto Off.

You can import the VSNs from the Historian catalog back into the library at a latertime.

To unload a library:





3. Select the radio button next to the library that you want to unload.


4. From the Operations menu, choose Unload.

A message box prompts you to confirm the unloading.

5. Click OK.

Removing Archiving, Staging, andRecycling ConfigurationsA library cannot be deleted if you have changed the default values to configurearchiving, staging, and recycling for the library. Before deleting the library, you mustremove these configurations.

Removing Archiving and Staging Configurations

To remove the archiving and staging configuration settings for a library:





3. Click the General Archiving Setup local tab.

The General Archiving Setup page is displayed.

4. In the Drive Limits table, delete the values in the Maximum Drives for Archivingand the Maximum Drives for Staging columns for the library that you want todelete. These columns must be left blank.

5. Click Save.

The default drive count values for the library are displayed in the columns thatyou just edited. This can be ignored.

Removing Recycling Configurations

To remove recycling configuration settings for a library:




2. Click the Archive Management tab, and then click the Recycler tab.

The Recycler page is displayed.

3. In the Recycling Characteristics table, delete all of the values for the library. Forexample, clear the check box, delete all values in the text fields, and choose - -from the Size Limit menu.

4. Click Save.

The default recycling parameters for the library are displayed in the table. Thesevalues can be ignored.

Deleting a LibraryDeleting a library logically removes it from the server to which it is attached. Datacontained in the library is no longer accessible to the archiving file systemsassociated with the library, but the data itself is not destroyed.

If you have not configured archiving, staging, and recycling for the library, you canimmediately delete the library. Otherwise, you must first remove theseconfigurations. For instructions, see “Removing Archiving, Staging, and RecyclingConfigurations” on page 154.

To delete a library:





3. Select the radio button next to the name of the library you want to delete.

4. From the Operations menu, choose Delete from the list of commands.


5. Click OK.


Managing Library DrivesThis section provides information about managing drives in a library. It contains thefollowing subsections:

■ “Changing the State of a Library Drive” on page 156

■ “Idling a Drive” on page 156

■ “Unloading a Drive” on page 157

■ “Cleaning a Drive” on page 158

Changing the State of a Library DriveYou might want to change the state of a drive in a library. For example, if a cartridgebecomes lodged in the drive, turn the state of the drive to Off before addressing thesituation.

To change the state of a library drive:





3. Select the radio button next to the library on which the drive that you want tochange is located, and click View Drives.

The Drives Summary page is displayed.

4. Select the radio button next to the row in which the drive that you want to changeis located, and click Change State.


5. Select the drive state that you want, and click Submit.

Idling a DriveIdling a drive stops any archiving or staging activity that is in process. You mightidle drives in a library if you wanted to manually manipulate cartridges in a librarywithout disturbing archiving or staging operations.


To idle a drive:





3. Click the name of the library on which the drive that you want to idle is located.

The Library Details page is displayed.

4. In the Additional Information table, click Drives Summary.

The Drives Summary of a Library page is displayed.

5. Select the radio button next to the row in which the drive that you want to idle islocated, and click Idle.

To restart archiving again after idling a drive, click Restart in the Archiving sectionof the Activity Management page. For more information, see “Controlling GlobalArchiving Activity” on page 144.

Unloading a DriveIf a volume is no longer needed, its cartridge is automatically unloaded. However,you can also manually unload a drive. When you unload a drive, the mountedcartridge is removed from the drive and placed in its storage slot.

Before unloading a drive, you must idle the drive. For more information, see “Idlinga Drive” on page 156.

To unload a drive:





3. Click the name of the library on which the drive that you want to unload islocated.





5. Select the radio button next to the row in which the drive that you want to unloadis located, and click Unload.

To load a different cartridge containing a new volume into a drive, see “Loading aVSN Into a Drive in a Library” on page 161.

Cleaning a DriveYou can clean the read/write heads of a tape drive by mounting a cleaning tape onthe drive and running it.

To clean a drive:





3. Click the name of the library on which the drive that you want to clean is located.




5. Select the radio button next to the row in which the drive that you want to cleanis located, and click Clean.

Managing VSNs in a LibraryThis section provides information about managing volume serial names (VSNs) in alibrary. It contains the following subsections:

■ “Searching for a VSN” on page 159

■ “Importing a VSN” on page 159

■ “Exporting a VSN” on page 160

■ “Loading a VSN Into a Drive in a Library” on page 161

■ “Unloading a VSN From a Drive in a Library” on page 162

■ “Labeling a VSN” on page 162

■ “Reserving a VSN in a Library” on page 163


■ “Unreserving a VSN in a Library” on page 164

■ “Auditing the Slot for a VSN in a Library” on page 165

■ “Editing the Media Attributes for a VSN in a Library” on page 165

Searching for a VSNYou can search for a specific volume serial name (VSN) from any of three differentpages in the browser interface:

■ Library Summary page – Initiates a search across all libraries listed on the LibrarySummary page.

■ Historian page – Initiates a search within the Historian.

■ VSN Summary page – Initiates a search within the selected library.

This topic provides an example of how to search for a VSN from the LibrarySummary page.

To search for a VSN:

1. From the Servers page, click the name of the server for which you want to searchfor a VSN.




3. Click Search for VSN.

The Search VSNs page is displayed.

4. Type the VSN number you want to find, and click Search VSN.

If an exact match is found, the VSN Details page for that VSN is displayed. Ifseveral matches are found, the Search Results page is displayed.

Importing a VSNWhen you import a volume serial name (VSN), the cartridge is brought into thelibrary and placed in the first available slot.

For a direct attached library with mail slots, the File System Manager softwareautomatically imports one VSN at a time or imports all the VSNs at one time,depending on the library. If you import one VSN, then you must repeat thisprocedure for each of the remaining VSNs.


Note: If you import a VSN for a network-attached library, and the VSN isunavailable, the software imports the VSN to the Historian instead. For informationabout when the software considers a VSN unavailable, see “Administering Stand-Alone, Non-archiving File Systems and Archiving File Systems” on page 60.

To import a VSN:

1. From the Servers page, click the name of the server for which you want to importa VSN.




3. Select the radio button next to the name of the library into which you want toimport the VSN, and click Import.

Depending on the library driver configured with the system, one of the followingoccurs:

■ SAMST – The appropriate VSN is automatically imported.

■ ACSLS – The Specify VSN Name window is displayed if the server has eitherof the following packages installed locally: Release 4, update 4, SUNWsamfsrand SUNWsamfsu; or Release 4, update 4, SUNWqfsr and SUNWqfsu.

Specify either a starting VSN and an ending VSN, or enter one VSN name, andclick Submit.

The Import VSNs page is displayed if the server has either of the followingpackages installed locally: Release 4, update 5, SUNWsamfsr and SUNWsamfsupackages; or Release 4, update 5, SUNWqfsr and SUNWqfsu packages. TheImport VSNs page provides advanced filtering options for importing VSNs.

■ Other – This is a library driver other than SAMST or ACSLS. The Specify VSNName window is displayed.

Either specify a starting VSN and an ending VSN, or enter one VSN name, andclick Submit.

Exporting a VSNExporting a volume serial name (VSN) removes the cartridge containing the selectedvolume from the library and places it in the Historian. For direct attached libraries,at least one mail slot is needed for a VSN to be exported.


To export a VSN:

1. From the Servers page, click the name of the server for which you want to exporta VSN.




3. Select the radio button next to the library from which you want to export theVSN, and click View VSNs.

The VSN Summary page is displayed.

4. Select the radio button next to the slot that contains the VSN you want to export.

5. From the Operations menu, choose Export.

The cartridge is ejected from the library device.

Loading a VSN Into a Drive in a LibraryWhen a volume serial name (VSN) is requested for archiving or staging, a cartridgecontaining the volume is automatically loaded into a drive in the library. You canalso manually perform this operation. The software determines the drive into whichthe VSN is loaded.

To load a VSN into a drive in a library:





3. Select the radio button next to the library into which you want to load, and clickView VSNs.

The VSN Summary page is displayed.

4. Select the radio button next to the slot for the VSN you want to load.

5. From the Operations menu, choose Load.

The cartridge is drawn into the drive unit.


Unloading a VSN From a Drive in a LibraryWhen a volume serial name (VSN) is no longer needed, its cartridge is automaticallyremoved (unloaded) from the drive in the library and placed in its storage slot. Youcan also manually perform this operation.

To unload a VSN from a drive in a library:





3. Select the radio button next to the library that you want, and click View Drives.

The Library Drives Summary page is displayed.

4. Select the radio button next to the VSN that you want to unload, and clickUnload.

A message tells you whether the unload operation is issued successfully.

Labeling a VSNLabeling a volume serial name (VSN) enables you to name it for the first time. Youcan also relabel a volume that already has data on it.

If you have volumes in stand-alone tape drives, or in a library that has no bar codereader, you must label the volumes to name them for the first time.

Caution: If you are relabeling a volume, all data on the volume is renderedinaccessible. To preserve the data in this volume, make a copy of it beforeproceeding.

To label a VSN:

1. Outside of the browser interface, make a copy of the volume to preserve its data.

2. From the Servers page, click the name of the server that you want.





4. Select the radio button next to the library where the VSN you want to label islocated, and click View VSNs.

The Library VSN Summary page is displayed.

5. Select the radio button next to the row in which the VSN you want to label islocated, and click Label.

The Label Tape window is displayed.

6. Provide the following information, and click Submit.

■ Label Type – Select to Label (name for the first time) or Relabel the volume.

■ Label Name – Type a VSN name from one to six characters from the followingcategories:

Uppercase letters from A to Z

Numerals from 0 to 9

The following special characters: ! “ % & ‘ ( ) * + , . / : ; < > = ? _

■ Block Size – Select a block size from the list. The block size determines thebasic unit of online storage for the volume.

A message box prompts you to confirm the label operation.

7. Click OK.

A message tells you whether the label operation was issued successfully. If it was,a tape label job is created, which you can view from the Jobs tab. After the job iscompleted, the VSN is updated with the new label.

Reserving a VSN in a LibraryYou can reserve a specific volume serial name (VSN) to be used for archiving ofdesignated files.

To reserve a VSN:





3. Select the radio button next to the library where the VSN you want to reserve islocated, and click View VSNs.



4. Select the radio button next to the row where the VSN you want to reserve islocated, and click Reserve VSN.

The Reserve VSN wizard is displayed.

5. Select one or more reservation methods, as prompted, and click Next:

■ File System – You want the VSN reserved for archiving files from a specific filesystem.

■ Archive Policy – You want the VSN reserved for archiving files that areassociated with a specific archive policy.

■ Owner – You want the VSN reserved for archiving files that are owned by aspecific user, that reside in a specific directory path, or that are owned by auser in a specific group.

6. Depending on the options you selected in the previous step, provide thefollowing information as prompted, and click Next.

■ File System Name – Select a file system from the list.

■ Archive Policy – Select an archive policy from the list.

■ Owner – Select Owner, Group, or Directory, and type the user name, ownername, or the directory path in the field next to the option you selected.

7. Review the specified information for the reservation method. If you are satisfied,click Finish.

Unreserving a VSN in a LibraryUnreserving a volume serial name (VSN) removes its reserved status.

To unreserve a VSN:





3. Select the radio button next to the library where the VSN you want to unreserveis located and click View VSNs.


4. Select the radio button next to the row where the VSN you want to unreserve islocated, and click Unreserve VSN.


Auditing the Slot for a VSN in a LibraryOccasionally, the reported space remaining on a tape or magneto-optical cartridgemight need to be updated in the library catalog. When you audit a slot in a library,the cartridge containing the VSN is loaded, the label of the volume is read, and thelibrary catalog is updated with the slot capacity information.

To audit the slot for a volume in a library:





3. Select the radio button next to the library whose slot you want to audit and clickView VSNs.


4. Select the radio button next to the slot that you want to audit.

5. From the Operations menu, choose Audit.

The library catalog is updated with the slot capacity information.

Editing the Media Attributes for a VSN in aLibraryYou can edit various attributes for the media on which a volume serial name (VSN)is located.

To edit the media attributes for a VSN:





3. Select the radio button next to the library where the VSN you want to edit islocated, and click View VSNs.



4. Select the radio button next to the row in which the VSN you want to edit islocated, and click Edit Media Attributes.

The Edit Media Attributes window is displayed.

5. Select or deselect the check boxes next to the listed attributes, as desired, and clickOK:

■ Damaged Media – Indicates that the VSN might be damaged.

■ Duplicate VSN – Indicates that another VSN exists with the same name.

■ Read-only – Indicates that the VSN is read-only.

■ Write-protected – Indicates that the VSN is write-protected.

■ Foreign media – Indicates that the VSN is foreign, that is, it is not created in aSun StorEdge SAM-FS or Sun StorEdge QFS environment.

■ Recycle – Specifies if the VSN will be recycled.

■ Volume is Full – Indicates that the VSN has no space available for storage.

■ Unavailable – Indicates that the VSN is not available for storage use.

■ Need Audit – Indicates that the library catalog needs to be updated with theslot capacity information of the VSN.

Managing Stand-Alone TapeDrivesThis section provides information about managing stand-alone tape drives. Itcontains the following subsections:

■ “About Stand-Alone Tape Drives” on page 167

■ “Adding a Tape Drive” on page 167

■ “Deleting a Tape Drive” on page 167

■ “Unloading a VSN From a Tape Drive” on page 168

■ “Reserving a VSN in a Tape Drive” on page 169

■ “Unreserving a VSN in a Tape Drive” on page 170

■ “Changing the State of a Tape Drive” on page 170

■ “Editing the Media Attributes for a VSN in a Tape Drive” on page 171

■ “Idling a Tape Drive” on page 172

■ “Auditing a Slot of a Tape Drive” on page 172


About Stand-Alone Tape DrivesStand-alone tape drives differ from automated libraries in that manual interventionis required to load media into, and remove it from, the drive. Most operationsperformed with an automated library pertain to stand-alone tape drives. Theseoperations include adding tape drives to and deleting them from the file system,performing operations involving volume serial names (VSNs), and changing thestate of a drive.

Exported media devices are tracked by the catalog. Each stand-alone tape drive hasits own one-slot library catalog.

Adding a Tape DriveYou can add a stand-alone tape drive to and remove it from a file system. Drives canbe connected to the current server on which the file system is located either directlyor through the network.

To add a tape drive:

1. From the Servers page, click the name of the server to which you want to add atape drive.


2. Click the Media Management tab, and click the Stand-Alone Tape Drives tab.


3. Click Add.

The Add Tape Drive wizard is displayed.

4. Follow the steps in the wizard.

Deleting a Tape DriveDeleting a tape drive logically removes it from the file system to which it isconfigured. No data is destroyed by this procedure.


To delete a tape drive:

1. From the Servers page, click the name of the server from which you want toremove a tape drive.






4. Click the radio button in the row that displays the tape drive that you want todelete.



6. Click OK.

Unloading a VSN From a Tape DriveWhen a volume serial name (VSN) is no longer needed, you can remove its cartridgefrom its stand-alone tape drive and place it in the tape drive’s storage slot.

To unload a VSN from a stand-alone tape drive:





3. Select the radio button next to the row in which the VSN that you want to unloadis located, and choose Unload from the Operations menu.

A message is displayed that tells you whether the unload operation is issuedsuccessfully.


Reserving a VSN in a Tape DriveYou can reserve a specific volume serial name (VSN) to be used for archiving ofdesignated files.

To reserve a VSN:





3. Click the VSN that you want to reserve.


4. Select the radio button in the row that displays the VSN you want to reserve, andclick Reserve VSN.

The Reserve VSN wizard is displayed.

5. Select one or more reservation methods, as prompted, and click Next:

■ File System – You want the VSN reserved for archiving files from a specific filesystem.

■ Archive Policy – You want the VSN reserved for archiving files that areassociated with a specific archive policy.

■ Owner – You want the VSN reserved for archiving files that are owned by aspecific user, that reside in a specific directory path, or that are owned by auser in a specific group.

6. Depending on the options you selected in the previous step, provide thefollowing information as prompted, and click Next.

■ File System Name – Select a file system from the list.

■ Archive Policy – Select an archive policy from the list.

■ Owner – Select Owner, Group, or Directory, and type the user name, ownername, or the directory path in the field next to the option you selected.

7. Review the specified information for the reservation method. If you are satisfied,click Finish.


Unreserving a VSN in a Tape DriveUnreserving a volume serial name (VSN) removes its reserved status.

To unreserve a VSN:







4. Click the VSN that you want to unreserve.


5. Select the radio button in the row that displays the VSN you want to unreserveand click Unreserve VSN.

Changing the State of a Tape DriveA tape drive can be in a state of On, Off, or Unavailable.

To change the state of a tape drive:







4. Select the radio button in the row that displays the tape drive that you want tochange, and click Change State.



5. Select the state into which you want to place the tape drive, and click Submit.

Editing the Media Attributes for a VSNin a Tape DriveYou can edit various attributes for the media on which a volume serial name (VSN)is located.

To edit the media attributes for a volume in a tape drive:







4. Click the VSN whose media attributes you want to edit.


5. Select the radio button in the row that displays the VSN that you want to edit,and click Edit Media Attributes.

The Edit Media Attributes window is displayed.

6. Select or deselect the attributes listed, as desired, and click OK:

■ Damaged Media – Indicates that the VSN might be damaged.

■ Duplicate VSN – Indicates that another VSN exists with the same name.

■ Read-only – Indicates that the VSN is read-only.

■ Write-protected – Indicates that the VSN is write-protected.

■ Foreign media – Indicates that the VSN is foreign; that is, it is not created in aSun StorEdge SAM-FS or Sun StorEdge QFS environment.

■ Recycle – Specifies if the VSN will be recycled.

■ Volume is Full – Indicates that the VSN has no space available for storage.

■ Unavailable – Indicates that the VSN is not available for storage use.

■ Need Audit – Indicates that the library catalog needs to be updated with theslot capacity information of the VSN.


Idling a Tape DriveIdling a tape drive stops any archiving or staging activity that is in process.

To idle a tape drive:







4. Click the radio button in the row that displays the tape drive that you want toidle.

5. From the Operations menu, choose Idle.

Archiving or staging activity stops at a logical point in the process.

Auditing a Slot of a Tape DriveAuditing reads the information on the media in a tape drive’s slot, and updates thelibrary catalog entry for the slot.

To audit a slot of a tape drive:







4. Click the drive whose slot you want to audit.

The Drives Details page is displayed.


5. Select the radio button next to the slot that you want to audit.

6. From the Operations menu, choose Audit.


CHAPTER 9

Performing GeneralAdministration Tasks

This chapter provides information about performing general administration tasks. Itcontains the following sections:

■ “About Notifications” on page 175

■ “Creating a Notification” on page 177

■ “Changing Notification Events for a Recipient” on page 177

■ “Deleting a Notification” on page 178

About NotificationsNotifications are available only to servers that have the SUNWsamfsr andSUNWsamfsu packages installed locally.

A notification is a mechanism by which the system informs a user of certain eventsor conditions by generating a message and sending it to the user’s email address.

You can configure the File System Manager software to automatically send emailnotifications to recipients when certain events occur. When you create a notification,you must provide an email address for the intended recipient of the notification.Every event that triggers a notification, except for the file system overflow event,applies to archiving file systems.

175

You can set up the system so that one or more of the events described in thefollowing table triggers a notification.

TABLE 9-1 Events

Event Description

Device down One or more devices are unusable by the file system.

Archiver operationsinterrupted

The software is unable to complete archiving operations. An email message is sent ifthe archiver is interrupted for any of the following reasons:• No volumes that are associated with the policy are available.• A file being archived is too large for volume overflow on the remaining volumes

that are associated with the policy.• A file being archived is too large for any remaining volume that is associated with

the policy.• Joined files being archived are too large for any remaining volume that is

associated with the policy.

Media required forarchiving/staging

Media devices need to be imported or manually loaded to support archiving orstaging.

Recycling completes The recycler has identified one or more tape volumes that contain large proportionsof expired archive copies. The recycler has finished removing the expired copies fromthe volumes. You can now either export or relabel the tape volume.

Metadata snaphsotsinterrupted

The metadata snapshot for a file system was interrupted. An email message is sent ifthe metadata snapshot fails or for any of the following reasons:• The software attempts to run a disaster recovery script before taking the metadata

snapshot and the software encounters the following conditions:• It cannot find the specified script.• The script does not contain any content.• The script does not have root executable permissions.• The file system for which a snapshot is scheduled is not mounted.• The snapshot file itself does not contain any content.• The snapshot file size is truncated. This occurs when the percentage of content

change in the current snapshot is less than 10 percent, when compared against thethree previous snapshots.

• The compression or indexing of the snapshot file fails.

File system overflow The file system is full. There is no space available for storage use.


Note: If you have the SUNWsamfsr and SUNWsamfsu packages installed locally on aserver, and you wish to enable notifications through the browser interface, be awarethat the software automatically defines the following value in the notify=filename directive of the archiver.cmd file:

/etc/opt/SUNWsamfs/scripts/archiver.sh

If you manually change this value, the browser interface cannot send archiver-related notifications.

Creating a NotificationTo create a notification:

1. From the Servers page, click the name of the server for which you want to createa notification.


2. Click the Administration tab and then click the Notifications tab.

The Notifications Summary page is displayed.

3. Click New.

The Notification Setup window is displayed.

4. Select the check boxes next to the events that you want to trigger notifications.

For information about these events, see “About Notifications” on page 175.

5. In the Notify e-mail address field, type the email address of the recipient that youwant notified.

6. Click Save.

Changing Notification Eventsfor a RecipientYou can change the types of events that will send notifications to a specific recipient.

Note: If you want to change the recipient who receives the notifications, you mustcreate a new notification and specify the new recipient’s email address.

Chapter 9 Performing General Administration Tasks 177

To change notification events for a recipient:

1. From the Servers page, click the name of the server for which you want to changenotification events.




3. Select the radio button next to the recipient for whom you want to change events.

4. Click Edit.

The Notification Setup window is displayed.

5. Select or deselect the check boxes next to the events that will automatically sendnotifications to this recipient.

6. Click Save.

Deleting a NotificationTo delete a notification:

1. From the Servers page, click the name of the server for which you want to deletea notification.




3. Select the radio button next to the notification that you want to delete, and clickDelete.


4. Click OK.


CHAPTER 10

Troubleshooting

This chapter provides information about troubleshooting the File System Managersoftware. It contains the following sections:

■ “Using SAMreports” on page 179

■ “Incompatible Software Release” on page 181

■ “One Device Displayed Multiple Times” on page 182

■ “Inaccessible Server” on page 183

■ “No Remaining Space for a VSN” on page 184

■ “Damaged or Stale Files in a Metadata Snapshot” on page 184

■ “Existing Fault Conditions Not Displayed” on page 184

Using SAMreportsThis section provides information about using SAMreports. It contains the followingsubsections:

■ “About SAMreports” on page 180

■ “Displaying SAMreports” on page 180

■ “Generating SAMreports” on page 181

179

About SAMreportsThe Sun StorEdge QFS and Sun StorEdge SAM-FS SAM Explorer feature collectsinformation from a SAM-QFS environment and writes it to file /tmp/SAMreport.The information contained in the SAMreport is an important aid to diagnosingcomplex problems, and it is needed by an engineer in the event of an escalation.

The SAMreport includes the following information:

■ Packaging, revision levels, and licensing information

■ Configuration files (mcf(4), archiver.cmd(4), recycler.cmd(4),inquiry.conf(4), defaults.conf(4))

■ Log files (sam-log, messages, archiver.log, recycler.log,releaser.log, trace files)

■ Memory dump information

If log files are not routinely collected, an important source of diagnostic informationis missing from the SAMreport. It is important to ensure that sites implement acomprehensive logging policy as part of their standard system administrationprocedures.

It is recommended that you generate a SAMreport in the following circumstances:

■ Whenever there is a system panic, core dump, crash, hang, or stall

■ As close to any system event as possible

Displaying SAMreportsYou can view the contents of an existing SAMreport as long as the server has eitherof the following packages installed locally:



To view the contents of a SAMreport:

1. From the Servers page, select the radio button next to the server for which youwant to view SAMreports.




3. Scroll down to the SAM Explorer section and click the path name of theSAMreport that you want to view.

A window is displayed that enables you to view the contents of the selected file.Click the Next and Previous buttons to page through the report, or enter a linenumber in the Jump To box and click Go to navigate directory to a specific line.

Generating SAMreportsYou can generate new SAMreports as long as the server has either of the followingpackages installed locally:



To generate a SAMreport:

1. From the Servers page, select the radio button next to the server for which youwant to generate a SAMreport.



3. Scroll down to the SAM Explorer section and click Generate Report.

The Run SAM Explorer page is displayed.

4. Select the directory where you want to store the SAMreport and the number oflines from each log file that should be included in the SAMreport.

5. Click Run.

The system generates the SAMreport in the directory you specified. The currentdate and time are appended to the file name.

Incompatible Software ReleaseThe File System Manager management station can collect or discover data from anyserver that has the corresponding or prior update of the following packages installedlocally:

■ SUNWsamfsr and SUNWsamfsu

■ SUNWqfsr and SUNWqfsu

Chapter 10 Troubleshooting 181

For example, the File System Manager release 2.1 software was released at the sametime as the Sun StorEdge QFS and Sun StorEdge SAM-FS release 4, update 5,software. Therefore, the File System Manager release 2.1 browser interface candiscover data from a server that has either of the following installed locally:

■ Release 4, update 5, or release 4, update 4, SUNWsamfsr and SUNWsamfsupackages

■ Release 4, update 5, or release 4, update 4, SUNWqfsr and SUNWqfsu packages

If the server has an older release level of the packages installed, “Not Supported” isdisplayed in the Release column on the Servers page.

If the server has a newer release level of the packages installed, a Down icon isdisplayed on the Servers page.

In either of these situations, do the following to obtain compatible release levels:

1. On the management station and on the server, use the pkginfo(1M) -l (the letterell) command to verify the package release on the system.

2. Depending on the results of the pkginfo(1M) -l command, do the following:

■ If the packages on the management station and server are not compatible,upgrade the system that has the older release.

■ If the packages on the management station and server are compatible, use theshowrev(1M) -p command on both the management station and server toview the patch release levels.

■ For example:

For more information about compatible software and patch release levels, see theREADME document.

One Device Displayed MultipleTimesIf a virtual device is exported from a storage box on two different ports, the currentserver might view this device as two separate devices. If it does, the File SystemManager browser interface will display the device two times.

To address this situation, you must install multipathing software on the server andthen click Refresh in the browser interface.

showrev -p /usr/xpg4/bin/grep -E ‘SUNWsam|SUNWqfs’


Inaccessible ServerIf the File System Manager software cannot communicate with a server, a Down iconis displayed next to the server in the browser interface. There are several reasons thismight occur:

■ The SUNWqfsr and SUNWqfsu packages or the SUNWsamfsr and SUNWsamfsupackages might not be installed on the server or they might be at incompatiblerelease levels. Search for these packages on the server to verify that they areinstalled. For information about compatible release levels, see the “IncompatibleSoftware Release” on page 181.

■ The File System Manager daemon (fsmgmtd) might not be running on the server.Do the following:

a. On the server, use the fsmadm(1M) status command to check whether thedaemon is running.

b. If it is not, manually restart the daemon by typing the following:

/opt/SUNWsamfs/sbin/fsmadm restart

You can configure the daemon to start automatically by using the fsmadm(1M)config -a command on the server.

■ The rpcbind process might not be running on the server. Do the following:

a. Log in to the server as root.

b. Restart the rpcbind process by typing the following:

/usr/sbin/rpcbind &

■ The management station might not be able to remotely administer the server. Allhosts that are listed in /opt/SUNWsamfs/sbin/fsmadm on the server canremotely administer the server. To add the management station to the list, log into the server as root and use the fsmadm(1M) add management-station-name.domain-name command.

■ The server is unavailable, it is not connected to the network, or the network itselfis unavailable. Check the server’s cabling and investigate any possiblenetworking issues.


No Remaining Space for a VSNIf you receive a notification that there is no space available for archiving on avolume (VSN), do one of the following:

■ Add more VSNs to the copies of the appropriate archive policy. The appropriatearchive policy is the policy that is applied to the files being archived to that VSN.For information about how to perform this procedure, see “Modifying VSNAssignments in a Policy Copy” on page 129.

■ Recycle the expired archive copies on the VSN by running the recycler. For moreinformation, see “Running Recycling” on page 141.

Damaged or Stale Files in aMetadata SnapshotIf you encounter either of the following situations, you must archive the specifiedfiles and then take another metadata snapshot of the archiving file system:

■ You review the metadata snapshot log file and you find a message that says a fileis damaged and cannot be restored with the specified metadata snapshot.

■ You receive an email notification that a stale files exists and that the file cannot berestored using the specified metadata snapshot.

Existing Fault Conditions NotDisplayedIf you are aware that a server is in a fault condition, but there is no indicator of thisfault condition in the browser interface, you might need to restart the Solarissysevent daemon (syseventd) on the server.

The reason this might occur is that /opt might not be part of the root file system onthe server. If this is the case, the Solaris sysevent daemon (syseventd) starts before/opt is available when the server is rebooted. Because /opt is unavailable to thedaemon upon rebooting, the daemon cannot find some of the SUNWsamfs binariesthat are required for the File System Manager software to report recent faultconditions or to send Snapshot Interrupted or File System Overflow notifications.

To address this issue, perform the following:

1. After rebooting the server, log in to the server as root.


2. Type the following at the command prompt:

# pkill -HUP syseventd

The Solaris sysevent daemon is restarted. The daemon can now find the requiredSUNWsamfs binaries.


Glossary

Definitions obtained from the Storage Networking Industry Association (SNIA)Dictionary are indicated with “(SNIA)” at the end. For the complete SNIADictionary, go to www.snia.org/education/dictionary.

Aallocation scheme The method by which files are allocated to disk. There are two file allocation

schemes: dual allocation and single allocation.

archive age The amount of time since a file’s last modification.

archive files Files that are copied by the archiver to archive media. Archive files arecompatible with the standard UNIX tar(1) format. This compatibility ensuresdata compatibility with the Sun Solaris Operating System and other UNIXsystems. The file format of archive files includes the file access data (inode) andthe path to the file. If a complete loss of the Sun StorEdge SAM-FSenvironment occurs, the tar(1) format enables file recovery using standardUNIX tools and commands.

archive interval The amount of time between complete archiving processes.

archive media device The media device to which an archive file is written. Archive media can beremovable tape or magneto-optical cartridges in a library. In addition, archivemedia can be a mount point on another file system.

archive policy See policy.

archiver A program that automatically copies files from online disk to offline storage,such as a disk or tape.

archive set A group of files to be archived. The groups can be defined across any group offile systems. Files in an archive set share common criteria that pertain to size,ownership, group, and directory location. The archive set controls the

Glossary 187

destination of the archive copy, the length of time for which the archive copy iskept, and the length of time the system waits before archiving the data. All filesin an archive set are copied to the volumes associated with the archive set. Afile in a file system can be a member of only one archive set. In the browserinterface, archive sets are called archive policies.

archive storage Copies of file data that have been created on archive media.

archiving file system A file system that uses the Sun StorEdge SAM-FS software for storage andarchive management of its files. The Sun StorEdge SAM-FS software controlsaccess to all files stored and all devices configured in the master configurationfile (mcf).

associative staging A file attribute that you can define in a policy. When this attribute is set, allfiles to which the policy is applied are staged.

audit The process of loading of cartridges to verify their volume serial numbers(VSNs). For magneto-optical cartridges, the capacity and space information isdetermined and entered into the automated library’s catalog.

automated library A robotically controlled device designed to load and unload removable mediacartridges without operator intervention. Cartridges are imported to andexported from the library and they are loaded and unloaded automatically. Thearchiving and staging processes use a site-defined scheme for allocating thenumber of drives to be used.

Bblock size See disk allocation unit.

Ccapacity The total amount of space available for storage on a file system, device, or

object.

cartridge A physical entity that contains a media device for recording data, such as atape or optical disk.

catalog A record of the VSN pools in an automated library. There is one catalog foreach automated library, and at a site, there is one Historian for all automatedlibraries.


client-server The model of interaction in a distributed file system in which a program at onesite sends a request to a program at another site and awaits a response. Therequesting program is called the client. The program satisfying the request iscalled the server.

connection The path between two protocol modules that provides reliable stream deliveryservice. A TCP connection extends from a TCP module on one machine to aTCP module on another machine.

continuous archiving A scheduled archiving process based on the Start Age, Start Size, and StartCount values in a policy copy. When a file meets the specified criteria, it isscheduled to be archived.

critical fault A severe error condition. For more information about the different conditionsthat can cause a critical fault to occur in the browser interface, see the/opt/SUNWsamfs/mibs/SUN-SAM-MIB.mib file on the server on which thefault condition occurred.

current job A File System Manager, Sun StorEdge QFS, or Sun StorEdge SAM-FS processthat is currently running or is attempting to run.

current managementstation The management station that is hosting the current session of the File System

Manager software. The name of the current management station is displayed inthe banner of the File System Manager browser interface.

current server The system for which you are monitoring and administering file systemsthrough the browser interface. This server’s name is displayed next to theChange Server button above the global navigational tabs in the browserinterface.

Ddata device A device or group of devices upon which file data is stored.

DAU See disk allocation unit.

direct access A file staging option (stage never) designating that a file can be accesseddirectly from the archive media and need not be retrieved to disk cache.

direct attached library An automated library connected directly to a server through a simplecomputer system interface (SCSI) interface. A SCSI attached library iscontrolled directly by the Sun StorEdge SAM-FS software using the SCSIstandard for automated libraries.

Glossary 189

direct copy method An offline copy method that copies files directly from the offline volume to thearchive volume without using the cache. For this copy method, the sourcevolume and the destination volume must be different, and two drives must beavailable.

disk A nonvolatile, randomly addressable, rewriteable data storage device. Thisdefinition includes both rotating magnetic disks, optical disks, and solid-statedisks, or nonvolatile electronic storage elements. (SNIA)

disk allocation unit(DAU) The basic unit of online storage. The Sun StorEdge QFS file system uses an

adjustable DAU. You can use this configurable DAU to tune the file system tothe physical disk storage device. For Sun StorEdge QFS file systems that usethe dual allocation scheme, the DAU is 16, 32, or 64 Kbytes. For Sun StorEdgeQFS file systems that use the single allocation scheme, the DAU is a multiple of8 Kbytes within the range of 16 Kbytes and 64 Mbytes.

disk archiving The process of archiving of data to disk volumes on another file system.

disk cache The disk-resident portion of an archiving file system. Disk cache is used tocreate and manage data files between an online disk and archive media.Individual disk partitions or an entire disk can be used as disk cache.

disk space threshold An administrator-defined range of disk space that is available to a user. Thehigh threshold indicates the maximum level of disk cache utilization. The lowthreshold indicates the minimum level of disk cache utilization. The releasercontrols disk cache utilization according to these predefined disk spacethresholds.

disk striping The process of recording a file across several disks, thereby improving accessperformance and increasing overall storage capacity. See also striping.

down fault An indicator that the File System Manager software is unable to communicatewith a server or object, for any reason. For information about the types ofconditions that can generate faults in the browser interface, see the/opt/SUNWsamfs/mibs/SUN-SAM-MIB.mib file on the management station.

drive A device that transfers data to and from a removable media volume.

dual allocation A method by which you define a small and large allocation sizes for files beingallocated to storage devices. When a file is created on a storage device, thesystem allocates the first eight addresses of the file in the small allocation. Ifmore space is needed, the file system uses one or more large disk allocationunits (DAUs) to expand the file. For Sun StorEdge QFS file systems, the smallallocation size is 4 Kbytes and the large allocation size is the DAU, which canbe 16, 32, or 64 Kbytes.


Eeq See equipment ordinal number.

equipment ordinalnumber The status code for a removable media device.

export The unloading of removable cartridges from a library.

Ffailover The process of moving metadata server control to a host other than the primary

metadata server that is associated with a shared file system.

family set A storage device that is represented by a group of independent physicaldevices, such as a collection of disks or the drives within an automated library.

fault An error condition on the current server.

file system A software component that imposes structure on the address space of one ormore logical or physical disks so that applications can deal more convenientlywith abstract named data objects of variable size (files). (SNIA)

file system resources Sun StorEdge SAM-FS software components, volumes, or disks that areassociated with a file system. The Sun StorEdge SAM-FS resources include thearchiver, stager, releaser, and recycler.

Gglobal directives Archiver and releaser directives that apply to all file systems on the current

server.

Hhard limit For disk quotas, a maximum limit on file system resources that users cannot

exceed.

Glossary 191

high water mark When defined as a mount option for an archiving file system, a threshold thattriggers the release of disk space occupied by eligible archived files on the filesystem. When defined in a policy copy or on the Recycler page, a thresholdthat triggers recycling, expressed as a percentage of the total capacity of thevolumes associated with a policy or an automated library.

Historian A catalog that keeps track of cartridges exported from an automated library ora manually mounted device. The Historian records entries for all cartridgesassociated with it, and can import and export cartridges. There is one Historianfor all automated libraries at a site.

Iimport The loading of removable cartridges into a library.

inode (index node) A 512-block of information that describes the characteristics of a file ordirectory. This information is allocated dynamically within the Sun StorEdgeQFS file system.

involuntary failover An operation in which, when the current metadata server of a shared filesystem becomes inaccessible, metadata server control is switched from theinaccessible metadata server to the potential metadata server. Involuntaryfailover is performed from the potential metadata server.

Jjob A process from a user or from the File System Manager, Sun StorEdge QFS, or

Sun StorEdge SAM-FS software.

Llast update The most recent time that the browser interface was updated with data.

library See automated library.

library catalog See catalog.


Mmajor fault An error condition that requires some administrator action. For more

information about the different conditions that can cause a major fault to occurin the browser interface, see the /opt/SUNWsamfs/mibs/SUN-SAM-MIB.mibfile on the server on which the fault condition occurred.

management station The fully qualified host name of the system on which the File System Managersoftware is installed locally. You can connect to this system’s File SystemManager browser interface from other hosts in the network. From the FileSystem Manager browser interface, you can configure and administer filesystems that are located on other servers in the network.

master configurationfile (mcf) The file, read at initialization time, that defines the relationships between

devices within a Sun StorEdge SAM-FS or Sun StorEdge QFS environment.

mcf See master configuration file.

media In the Sun StorEdge SAM-FS environment, tape or optical disk cartridges.

media type The type of tape or optical disk cartridge, such as, SONY AIT or IBM 3570.

metadata Data about data. In the Sun StorEdge SAM-FS or Sun StorEdge QFSenvironments, metadata is the index information needed to locate the exactdata position of a file on a disk. Metadata consists of information about files,directories, access control lists, symbolic links, removable media, segmentedfiles, and the indexes of segmented files. Metadata must be protected, becauseif the data is lost, the metadata that locates the data must be restored before thelost data can be retrieved.

metadata archiving An archiving process in which metadata is archived but file data is not. In anarchiving file system, the file system default policy archives the metadata forthe archiving file system.

metadata device A device, such as a solid-state disk or mirrored device, upon which a SunStorEdge QFS file system’s metadata is stored, separate from the system’s filedata. Separating file data from metadata can increase performance.

metadata server A host system in a shared file system that is used by the file system formetadata, the .inodes file, and file data. The metadata server also controlsstorage and archive management operations for the shared file system, if theshared file system is configured to be archiving.

metadata snapshot A file that captures all the metadata for a complete archiving file system at asingle point in time. This file can be used by the File System Manager softwareto recover lost file data in the event of a disaster.

Glossary 193

metadata snapshotschedule The automatic creation of metadata snapshot files for archiving file systems. It

is recommended that metadata snapshots are taken at least once a day.

minor faults An error condition that is not as severe as a critical error condition, but that ismore severe than a minor error condition. For information about the differentconditions that cause minor faults to occur, see the/opt/SUNWsamfs/mibs/SUN-SAM-MIB.mib file on the server on which thefault condition occurred.

mount point (1) A method used to attach a file system to the hierarchy at a path namelocation directory. (2) The directory on which a file system is mounted.

Nnetwork-attached

library A library, such as IBM or Sony, controlled through a software package that issupplied by the vendor, IBM or Sony. The Sun StorEdge SAM-FS file systeminterfaces with the vendor software using a Sun StorEdge SAM-FS mediachanger daemon designed specifically for the library.

none copy method An offline copy method that stages files as needed for each archive file beforecopying to the archive volume.

NFS (network filesystem) shared

directories Network file system directories in a file system that enable you to share filesacross servers that are connected to the network. Through the browserinterface, you can manipulate the read and write permissions of these shareddirectories, and can control whether the directories are shared or unshared.

notification A mechanism by which an email message is sent to the specified recipientwhen a certain condition is detected by the File System Manager software.

Ooffline storage Storage that requires operator intervention for loading.

online storage Storage that is immediately available upon request, such as, disk cache storage.


Ppartition A portion of a device or a side of a magneto-optical cartridge.

policy A mechanism that indicates how and when files in an archiving file system arearchived to remote media. When the documentation refers to a policy, it isreferring to a custom policy unless otherwise specified.

pool A collection of disks or virtual disks that can be carved into volumes.

port A connection point on a host system through which connected devices passdata into and out of the host.

potential metadataserver A host system that has the ability to become the metadata server for a shared

file system.

primary metadataserver The original, preferred host system for a shared file system’s metadata,

.inodes file, and file data. The primary metadata server also controls thestorage and archive management operations for the shared file system, if theshared file system is configured for archiving. When you create a shared filesystem, the server that you are managing at the time automatically becomesthe primary metadata server for the shared file system.

Qquota The amount of system resources that a user is allowed to consume. Quotas are

not supported for removable media or disk archive resources.

Rrecycler A utility that inspects all archive files that are on offline storage and

determines which of these are no longer needed. Upon completing itsassessment, the recycler utility enables you to reuse the space on the media.

releaser A software component that identifies archived files and releases their diskcache copies, thus making more disk cache space available. The releaserautomatically regulates the amount of online disk storage between specifiedhigh and low thresholds.

Glossary 195

report The result of a File System Manager query. Reports are built from the results ofthe most recent update of discovered data.

restore The process of recovering lost files or an archiving file system itself fromarchive media.

robot The portion of an automated library that moves cartridges between storageslots and drives. Also called a transport.

round-robin A data access method in which entire files are written to logical disks in asequential fashion. The entire first file is written to the first logical disk, thesecond file is written to the next logical disk, and so on. The size of each filedetermines the size of the I/O.

In Sun StorEdge QFS file systems, files are round-robined if round-robin accessis specified or if the file system contains mismatched striped groups.

SSCSI See small computer system interface.

segment A section of a large files that has been divided into smaller pieces.

server (1) A system that is hosting the file systems that you are managing through thebrowser interface. (2). As displayed in the browser interface’s banner, themanagement station.

severity level An indicator of the seriousness of a fault condition.

single allocation A method by which you define one allocation size for files that are beingallocated to storage devices. The allocation size is the disk allocation unit(DAU) value, which can be a multiple of 8 Kbytes within the range of 16Kbytes and 64 Mbytes. Only stand-alone Sun StorEdge QFS file systems canuse the single-allocation scheme.

small computer systeminterface (SCSI) A collection of ANSI standards and proposed standards which define I/O

buses primarily intended for connecting storage subsystems or devices to hoststhrough host bus adapters. Originally intended primarily for use with small(desktop and desk-side workstation) computers, SCSI has been extended toserve most computing needs, and is arguably the most widely implementedI/O bus in use today. (SNIA)

SNMP communityname The name of the simple network management protocol (SNMP) community

within which the management station system and the SNMP host system aremembers.


SNMP port The port number of the SNMP host.

soft limit For disk quotas, a threshold limit on file system resources that you cantemporarily exceed. Exceeding the soft limit starts a timer. When you exceedthe soft limit for the specified time (the default is one week), no further systemresources can be allocated until you reduce file system to a level below the softlimit.

stage ahead method An offline copy method that stages the next archive file as the current archivefile is written to the destination. For stage ahead copying, two drives must beavailable and space must be available in cache for all files in one archive file.

stage all method An offline copy method that stages all files before archiving. For stage allcopying, one drive must be available, and space must be available in cache forall files.

stager A software component that copies files from offline storage back to online diskas they are needed.

staging The process of copying an offline file from archive storage back to onlinestorage.

stand-alone tapedrive A device that is similar to an automated library but that requires manual

intervention for loading media into, and removal of media from, its drive.

storage area network(SAN) A network whose primary purpose is the transfer of data between computer

systems and storage elements, and among storage elements. A SAN consists ofa communication infrastructure, which provides physical connections, and amanagement layer, which organizes the connections, storage elements, andcomputer systems so that data transfer is secure and robust. (SNIA)

storage slots Locations inside an automated library in which cartridges are stored when theyare not being used in a drive. If the library is direct attached, the contents ofthe storage slots are kept in the automated library’s catalog.

striped group A collection of devices within a Sun StorEdge QFS file system that are definedin the mcf file as one or more (usually two) gXXX devices. Striped groups aretreated as one logical device and are always striped with a size equal to thedisk allocation unit. You can specify up to 128 striped groups within a filesystem, but you can specify no more than 252 total devices. Files can beallocated across the striped groups.

stripe size The specified number of disk allocation units (DAUs) to be allocated beforeallocation to the next device of a stripe.

striping A data access method in which files are simultaneously written to logical disksin an interlaced fashion. In a Sun StorEdge QFS environment you can declareeither striped or round-robin access for each file system, and you can declarestriped groups within each file system.

Glossary 197

Sun StorEdge QFS filesystem A high-speed UNIX file system that can store file data and metadata on the

same device or on separate devices. The Sun StorEdge QFS software controlsaccess to all files stored and all devices configured in the master configurationfile (mcf).

Sun StorEdge SAM-FSsoftware Software that can be configured with a file system to provide storage, archive

management, and archive retrieval capabilities. This software archives files bycopying the files from online disk to archive media.

Tthreshold A mechanism that defines the desirable available storage window for online

storage. Thresholds set the storage goals for the releaser. Also see disk spacethreshold.

Uunarchiving The process of deleting archive entries for one or more files or directories.

Vvolume A named area on a cartridge or a disk for sharing data. A cartridge has one or

more volumes. Double-sided cartridges have two volumes, one on each side.

volume overflow The spanning of a single file over multiple volumes. Volume overflow is usefulfor sites that use very large files that exceed the capacity of their individualcartridges.

volume serial name(VSN) In the context of archiving to removable media cartridges, a logical identifier

for magnetic tape and optical disk that is written in the volume label. In thecontext of archiving to disk cache, the unique name for the disk archive set. Anindividual volume is identified by media type and VSN.

voluntary failover An operation in which, when the primary metadata server is running andavailable, the metadata server control is switched from the primary metadataserver to a potential metadata server.


VSN See volume serial name.

WWorld Wide Name

(WWN) A 16-digit, hexadecimal number that uniquely identifies a peripheral device,such as a switch or a fabric.

WWN See worldwide name.

Glossary 199

Index

Aactivity

archiving, displaying, 43global archiving, controlling, 143global staging, controlling, 144metadata snapshot, displaying status of, 33releasing, displaying, 43staging, displaying, 44

administrative privileges, assigning, 3archive policies

about, 112adding file match criteria to, 127adding to file systems, 69administering, 112archiver.cmd file for, 115archiving options for, enabling, 118copies of

about, 129adding, 130administering, 128editing, 129removing, 130VSN assignments to, 38, 129

creating, 116deleting, 117editing, 117file match criteria in, displaying, 36managing, 68, 111monitoring, 36no-archive type

about, 104, 113creating, 102, 116

removing file match criteria from, 128

archiver.cmd file, 115archiving

about, 101, 102, 104activity, 42, 43, 143administering policies for, 112associative

about, 108enabling, 120

configuring global values for, 137continuous


controlling, 109to disk VSNs, 134to disk, enabling, 118file systems. See archiving file systemsgeneral, setting up, 136global activity for, controlling, 143idling for a file system, 110planning for, 105to pools of VSNs, enabling, 122running for a file system, 111scan methods, about, 136stopping for a file system, 110to tape, 119

archiving file systemsabout, 57adding policies to, 69administering, 60archiver scanning, configuring for, 110archiving for, controlling, 109checking, 63configuring scanning for, 110

201

creating, 61deleting, 66file match criteria for, 68, 69, 70growing, 62idling archiving for, 110mount options for, editing, 65mounting, 64planning, 60protecting data in, 71restoring, 76, 77running archiving for, 111unmounting, 66VSN association for, creating, 67

associative archivingabout, 108enabling, 120

auditingslots for VSNs in a library, 165slots of tape drives, 172

Bbanner elements, 9banner pane, 7browser

banner and content panes in, 7navigating through, 8overview of, 7

Ccatalog, displaying for Historian, 40cleaning drives, 158clients

adding, 87deleting, 88mounting, 91unmounting, 93

configuration filesoverview of, 22server, displaying, 29

content pane, 10continuous archiving


controls, report table, 15conventions, typographic, xivcopies of archive policies. See archive policies, copies

of

current server, changing, 14

Ddamaged files in metadata snapshot,

troubleshooting, 184devices, discovering available, 52directories, displaying NFS, 32discovering available devices, 52disk archiving, enabling, 118disk VSNs

archiving to, 134archiving to pools of, 122creating, 135editing the media attributes of, 135

documentationaccessing online, xvrelated, xvwhere to submit comments about, xvi

drives. See tape drives

Eexplorer files or reports, SAM. See SAMreports

Ffault conditions not displayed, troubleshooting, 184faults

about, 47acknowledging, 49deleting, 49displaying, 48monitoring, 47

file match criteriaabout, 124adding existing to archiving file systems, 69adding file systems to, 125adding to a policy, 127administering, 123defined in a policy, displaying, 36displaying for a file system, 33editing, 124removing file systems from, 126removing from archiving file system, 68removing from policy, 128reordering for archiving file systems, 70using to display file systems, 37

file name patterns, 81file systems


about, 53adding file match criteria to, 125adding NFS directories to, 96archiving. See archiving file systemsdevices on, displaying, 32file match criteria for, displaying, 33file match criteria, displaying using, 37HA-QFS. See highly-available QFS (HA-QFS) file

systemsmanaging, 51NFS directories for, displaying, 32protecting data on, 71removing file match criteria from, 126restore files process for, displaying, 34shared. See shared file systemsstand-alone, non-archiving. See stand-alone,

non-archiving file systemsstatus, displaying, 31

filter and search file name patterns, 81filtering

metadata snapshot content, 79tables, 17

Ggeneral archiving, setting up, 136getting started, 19

Hhelp, using, 17highly-available QFS (HA-QFS) file systems, 59

about, 59adding servers for, 25creating, 51, 60

Historianabout, 150displaying catalog information for, 40

host file, shared, creating, 86hosts, displaying for a shared file system, 35

Iincompatible software version message,

troubleshooting, 181initial configuration tasks, 21installation, of File System Manager software, 2

Jjobs

about, 44canceling, 46displaying, 46monitoring, 44using to view progress of processes, 2

Llabeling a VSN, 162libraries

about, 151adding, 151auditing slots for VSNs in, 165changing drive states, 156changing the state of, 152deleting, 155managing, 150managing VSNs in, 158media attributes of VSNs in, editing, 165monitoring, 38mount requests in, displaying, 41status and state, displaying, 40supported, 149unloading, 153unloading VSNs from drives in, 162unreserving VSNs in, 164VSNs associated with, displaying, 39

log and trace files on servers, displaying, 29logging in and out, 5

Mmanagement station, software installed on, 2media attributes, editing for disk VSNs, 135media type parameters, configuring global, 139media, removable, managing, 147metadata servers

adding, 87deleting, 88, 89displaying for a shared file system, 35mounting, 91unmounting, 93, 94

metadata snapshotsabout, 72canceling searches of, 82damaged or stale files in, troubleshooting, 184displaying status of activities for, 33editing schedules for, 75filtering content of, 79

Index 203

planning for, 73removing schedules for, 76scheduling, 72, 74searching content of, 79taking on demand, 75

minimum server release, displaying, 30monitoring

archiving activity, 42environment, 19faults, 47file systems, 31jobs, 44libraries, 38policies, 36releasing activity, 42servers, 27staging activity, 42tape drives, 41

mount optionsediting, 65, 92

mount requests, displaying for a library, 41mounting

archiving file systems, 64clients, 91media, requests, 41metadata servers, 91requests in a library, displaying, 41shared file systems, 90stand-alone, non-archiving file systems, 64user privileges to perform, 3

Nnavigational elements, 10network file system (NFS) directories

about, 95adding, 96changing the status of, 98displaying for a file system, 32editing options for, 97removing, 99

notificationsabout, 175changing events for a recipient of, 177creating, 177deleting, 178

Oonline help, using, 17

Ppasswords, entering, 5planning

archiving, 105archiving file systems, 60file match criteria, 126metadata snapshots, 73shared file systems, 85stand-alone, non-archiving file systems, 60

policies, archive. See archive policiespools

archiving to, 122pop-up windows, overview of, 13potential metadata servers

adding, 87deleting, 88mounting, 91unmounting, 93

privileges, assigning user, 3product overview, 1

Rrecycler

about, 140configuring, 139configuring library recycling values for, 142configuring policy recycling values for, 142running, 141

related documentation, xvreleaser

about, 108configuring global values for, 138

releasingabout, 102displaying activity of, 43monitoring activity of, 42

removable mediaabout, 148managing, 147

report icons, 11report tables, 14, 15reserving a VSN, 163restoring


displaying status of process, 34file system data, 76file systems, 77

SSAM explorer files or reports. See SAMreportsSAMreports

about, 180displaying, 180generating, 181troubleshooting with, 179

scanning methods, archiver, 136searching

canceling for metadata snapshots, 82metadata snapshot content, 79for a VSN, 159

securitylimiting user privileges for, 3setting timeout value for, 6through protecting system data, 71

serversadding, 21, 24changing current, 14configuration files on

displaying, 29overview of, 22

configuration of, displaying, 28configuring, 21file warning messages for, displaying, 30inaccessible, troubleshooting, 183log and trace files installed on, displaying, 29minimum release supported for, displaying, 30monitoring, 27removing, 26software packages on, displaying, 28

session timeout value, setting, 6shared file systems

about, 58administering, 84creating, 85deleting, 94editing mount options for, 92hosts in, displaying, 35metadata server for, displaying, 35mounting and unmounting, 90, 93planning, 85

shared hosts file, creating, 86

software version, incompatible message,troubleshooting, 181

sofware packages installed on server, displaying, 28sorting tables, 17stager

about, 109configuring global values for, 138

stagingabout, 102controlling global activity for, 144displaying activity of, 44file or directory on demand, 144managing activity for, 143monitoring activity of, 42

stand-alone tape drives. See tape drives, stand-alonestand-alone, non-archiving file systems

about, 56administering, 60checking, 63creating, 61deleting, 66editing mount options for, 65growing, 62mounting, 64planning, 60unmounting, 66

status and statechanging for a library drive, 156of file systems, 31of libraries, displaying, 40of library, changing, 152of metadata snapshot activities, 33of NFS directories, changing, 98of restore processes, 34of stand-alone tape drives, 42of tape drives, changing, 170

STK ACSLS (StorageTek Automated CartridgeSystem Library Software), adding libraryfor, 149, 151, 152

Sun Cluster environmentadding servers that are part of, 25as relates to HA-QFS file systems, 51, 59, 60

Sun StorEdge SAM-FS software, about, 103supported release levels, 30

Ttables

Index 205

controls, 15filtering, 17sorting, 17

tape archiving, enabling, 119tape drives

adding, 167auditing slots for, 172changing state of, 170cleaning, 158deleting, 167displaying VSN for, 41editing VSN media attributes for, 171idling, 156, 172in library, displaying, 39in library, managing, 156monitoring, 41reserving VSN in, 169stand-alone

about, 167managing, 166state of, displaying, 42

supported, 149unloading, 157unreserving VSN in, 170VSN for, displaying, 41

task overviewfor configuring servers, 21getting started, 19

timeout value, settting, 6trace files on a server, displaying, 29troubleshooting

damaged or stale files in metadata snapshot, 184of device displayed multiple times, 182of fault conditions not displayed, 184of inaccessible server, 183of incompatible software version message, 181using SAMreports, 179VSNs with no available space, 184

typographic conventions, xiv

UUNIX commands, using, xiiiunloading

drives, 157libraries, 151, 153VSNs from drives of a library, 148, 162, 168

unmounting

archiving file systems, 66clients, 93metadata servers, 93, 94shared file systems, 90, 93stand-alone, non-archiving file systems, 66user privileges to perform, 3

unreservingVSNs, 164

user privileges, assigning, 3

Vvolume serial names (VSNs)

about creating associations with archiving filesystems, 67

assigned to policy copies, displaying, 38auditing slots in a library for, 165creating disk, 135disk or tape, enabling archiving to, 122editing attributes for, 165exporting, 160importing, 159in a library, managing, 158labeling, 162library, displaying, 39loading into a library, 161managing disk for archiving, 134modifying in policy copies, 129no available space on, troubleshooting, 184pools

about, 131creating, 132deleting, 133editing, 132managing for archiving, 131

reserving, 163searching, 159for tape drives, displaying, 41unloading from drives of a library, 162unreserving, 164

Wwarning messages in server files, displaying, 30wizards, 13


file system manager user’s guide - oracle · file system manager user’s guide part no....

Documents