| Sun StorEdge SAM-FS Storage and Archive Management Guide |    
|
| Sun StorEdge SAM-FS Storage and Archive Management Guide |
|
| C H A P T E R 1 |
|
Overview |
The Sun StorEdge SAM-FS environment provides a configurable file system with storage, archive management, and retrieval capabilities. The Sun StorEdge SAM-FS software archives files by copying the files from online disk cache to archive media. The archive media can consist of disk slices in another file system or it can consist of removable tape or magneto-optical cartridges in automated or manually loaded storage devices. The Sun StorEdge SAM-FS software automatically maintains online disk space at site-specified usage thresholds. It releases disk space associated with archived file data and restores the files to online disk when they are needed.
This chapter provides a technical overview of the Sun StorEdge SAM-FS components. It contains the following sections:
The Sun StorEdge SAM-FS storage and archive management software includes a high-performance UNIX file system that resides in the server's disk cache. For more information about the file system itself, see the Sun StorEdge SAM-FS File System Configuration and Administration Guide.
The other components that reside in the Sun StorEdge SAM-FS environment are as follows:
For more information about the archiver, see Archiving. For more information about segmented files, see Using Segmented Files.
Releasing is the process of freeing primary (disk) storage that is used by an archived file's data. Two threshold values, the high water mark and the low water mark, both expressed as a percentage of total disk space, are used to manage online disk cache free space. When online disk consumption exceeds the high water mark, the system automatically begins releasing the disk space occupied by eligible archived files. Disk space occupied by archived file data is released until the low water mark is reached. Files are selected for release depending on their size and age. The first portion of a file can be retained on disk for speedy access and for masking staging delays. If a file has been archived in segments, portions of the file can be released individually. For more information about the releaser, see Releasing.
When a file whose data blocks have been released is accessed, the stager automatically stages the file or file segment data back to online disk cache. The read operation tracks along directly behind the staging operation, allowing the file to be immediately available to an application before the entire file is completely staged.
The Sun StorEdge SAM-FS software processes stage request errors automatically. If a stage error is returned, the system attempts to find the next available archive copy of the file. Stage errors that can be automatically processed include media errors, unavailability of media, unavailability of an automated library, and others. For more information about staging, see Staging.
As users modify files, archive copies associated with the old versions of these files are considered to be expired on their archive media. Such copies are no longer needed, so they can be purged from the system. The recycler identifies the archive volumes with the largest proportions of expired archive copies and preserves the unexpired copies by moving them to separate volumes.
If a removable media volume contains only expired copies, you can take one of the following actions:
The recycling process is transparent to end users. For more information about recycling, see Recycling.
The Sun StorEdge SAM-FS environment supports a wide variety of tape storage and magneto-optical devices. The automated libraries that Sun StorEdge SAM-FS supports can be divided into the following groups, depending on how they are attached to the environment:
TABLE 1-1 shows the daemons specific to various automated libraries.
For a list of supported storage devices, contact your Sun Microsystems sales representative or your authorized service provider (ASP).
The relationships between the devices managed within the Sun StorEdge SAM-FS environment are defined in the master configuration file, /etc/opt/SUNWsamfs/mcf. The mcf file specifies the removable media devices, libraries, and file systems included in the Sun StorEdge SAM-FS environment. Each piece of equipment is assigned a unique equipment identifier in the mcf file. Entries in the mcf file also define manually mounted archiving devices and automated library catalog files.
When possible, the system uses the standard Solaris disk and tape device drivers. For devices not directly supported in the Solaris Operating System (OS), such as certain library and optical disk devices, the Sun StorEdge SAM-FS software packages include special device drivers.
Sun SAM-Remote software is a client/server implementation that enables libraries and other removable media devices to be shared between Sun StorEdge SAM-FS host systems. Sun SAM-Remote software enables you to configure multiple storage clients that archive and stage files from a centralized tape library or magneto-optical library. For example, if you have host systems on a network that spans a large geographical area, files created in one city can be archived to cartridges in a library located miles away.
For more information see Using the Sun SAM-Remote Software.
The File System Manager software is a browser-based graphical user interface that enables you to configure and control one or more Sun StorEdge QFS or Sun StorEdge SAM-QFS servers from a central location. To access this central location, you can use the web browser on any host in your network.
The goal of the software is to provide an easy-to-use interface for performing the most common tasks associated with Sun StorEdge QFS or Sun StorEdge SAM-QFS servers. To further configure or administer a server, use the server's command-line interface, scripts, configuration files, and so on. For more information, and instructions for installing File System Manager, see the Sun StorEdge SAM-FS Installation and Upgrade Guide.
1. Log in to the management station web server.
2. In a web browser, go to the following URL:
For hostname, type the name of the host where File System Manager is installed. If you need to specify a domain name in addition to the host name, specify the hostname in this format: hostname.domainname.
Note that this URL begins with https, not http.
The Sun Java Web Console login screen appears.
3. At the User Name prompt, enter root or another valid user name.
4. At the Password prompt, enter the password.
You are now logged in to File System Manager.
The Sun Web Console framework has a default session timeout of 15 minutes. If File System Manger is the only application registered in the Sun Web Console, the File System Manager installation program changes the session timeout to 60 minutes. You can change the session timeout to a different value, but it is recommended that you not set it to a value greater than 60 minutes in order to preserve security.
To change the session timeout value, enter the following command on the management station:
/opt/SUNWfsmgr/bin/fsmgr session timeout-in-minutes
For example, to change the timeout value to 45 minutes, type:
/opt/SUNWfsmgr/bin/fsmgr session 45
You can create additional administrator and guest accounts at any time after the initial File System Manager configuration. These guest accounts are local to the management station.
If you remove the File System Manager software, the removal scripts do not remove any additional accounts that you created manually.
Use the following procedures to create additional accounts.
1. Outside of the browser interface, log in to the management station server as root.
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
Each user account that you add in this way has read-only viewing privileges for File System Manager functions. To add additional privileges see the following section, Assigning Privilege Levels.
You can assign users full or partial access to File System Manager functions. The following table lists the five levels of privileges you can assign to File System Manager users.
To specify full or partial configuration privileges for a user, add the following 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 of authorization that you want to assign to the user.
For example, to assign full privileges (privilege level com.sun.netstorage.fsmgr.config) for user account bobsmith, add the following 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 level com.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 create a generic File System Manager account that can be used by multiple users, and then add a role with privileges that only some of those users can access.
1. Use the useradd and passwd commands to add the account.
For example, to add a user account called guest for multiple users, type the following:
# /usr/sbin/useradd/useradd guest
2. Use the roleadd and passwd commands to add the role.
To create a role called admin with special privileges within the guest account, type the following:
3. Specify the privilege levels in the /etc/user_attr file.
To assign the admin role privileges to restore and stage file systems, add the following 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 the user 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 restore and stage file systems. All other users must select No Role and have read-only privileges.
Because multiple users with the same privilege level can be logged in to the software concurrently, there is a risk of one user's changes overwriting another user's previous changes. To prevent this, develop policies about who can make changes and how to notify others.
By default, File System Manager is set up to manage the server on which it is installed. It can also be used to manage other servers running Sun StorEdge QFS or Sun StorEdge SAM-FS software, but those additional servers must first be configured to enable File System Manager access. Once these servers are configured, you can administer their file systems, archiving processes, and media through the browser interface.
1. Outside of the browser interface, use Telnet to connect to the server you want to add. Login as root.
2. Use the fsmadm(1M) add command to add the management station (the system on which the File System Manager software is installed) to the list of hosts that can remotely administer this server.
All hosts that are added to the list through this command can remotely administer the server.
For example:
# fsmadm add management-station-name.domain-name
To ensure that the management station is successfully added, use the fsmadm(1M) list command and verify that the management station is listed in the output.
3. Log in to the File System Manager browser interface as an administrator user.
4. From the Servers page, click Add.
The Add Server window is displayed.
5. Type the name of the server or the IP address of the server into the Server Name or IP Address field, respectively.
| Sun StorEdge SAM-FS Storage and Archive Management Guide | 819-4329-10 |
|
Copyright © 2006, Sun Microsystems, Inc. All Rights Reserved.
To Invoke the File System Manager