![]() |
![]() |
![]() |
![]() |
Managing Storage
The Serval filer enables the quick and easy configuration of storage through a unified view of the filer and the storage.
· the Filer head is where the volume and file system reside. For configuration and management, you will need to manage the volumes.
· the storage is where the data actually resides. The storage can be either disk or tape, and any associated port, typically fibre channel, that connects to the SAN.
Managing Volumes
The Serval Filer uses logical volumes as the way to manage and allocate LUNs to a file system. The logical volume can exist with one or more LUNs. You can display, manage existing volumes, and create new volumes through the Volume display. Figure 27 shows the Volume display.
Figure 27 Volume DisplayThe Volume display shows the settings for all configured volumes. Portions of this display are links to other displays and dialogs where you can configure a new volume or modify a new volume. On the Volume display, you will also notice that you can set file system specific features, such as file sets, snapshots, and NFS share definitions. These options are available because the Agile File System sits on top of one or more logical volumes.
The Volume display can contain multiple volumes. The Volume display shows the number of the volumes that are displayed. You can show different volumes in the Volume display window:
· Click Refresh to redisplay the Volume display after you have added a volume, or if you want to make sure that accurate information is contained in the Volume display.
Viewing Existing Volumes
Step 1: Click the link in the Name field to invoke the Volume Detail display. Figure 28 shows the Volume Detail display.
Figure 28 Storage Volume Detail Display
On the Volume Details display, you can also see the LUN List. This list shows all the LUNs that are associated with a specific volume. Table 17 shows the contents of the LUN List and explains the contents of the list.
Viewing LUN Details
From the Volume Details display, you can click any of the LUNs listed in the WWN:LUN field to invoke the LUN Details display. This display shows more specific information about each LUN than the LUN List on the Volume Details display. Figure 29 shows the LUN Details display.
Figure 29 LUN Details display
Viewing LUN Statistics
From the LUN Details display, you can invoke the LUN Statistics display by clicking the View Stats button. Figure 30 shows the LUN Statistics display.
Figure 30 LUN Stats DisplayTable 19 shows the contents of the LUN Stats display and explains what each field means.
Adding a New Volume
From the Storage Volume display, you can create a new volume by clicking the Add Volume button. This button invokes the Add Volume dialog, where you can create a new logical volume and set the usage quota parameters. These parameters are the conditions that trigger the automatic volume space growth and the associated allocation of LUN space for volume growth. Figure 31 shows the Add Volume dialog. This GUI screen is a dialog because it requires interaction to complete, as opposed to a display which shows configured information and requires no interaction for it to complete.
Figure 31 Add Volume dialogStep 1: In the Name field, enter the name that you wan to apply to the volume. The Name field is a text-entry field that can contain from 1 to 48 alphanumeric characters.
· If you want to configure an absolute maximum limit for the amount, in Kilobytes, of storage that can be consumed by the logical volume in the Name field, select the radio button to the left of the text-entry field.
· After selecting the button, enter the amount, in Kilobytes of the absolute maximum amount of storage space the volume can consume. Enter a numeric string.
· If you do not want to limit the amount of storage space that the volume can consume, select the No Limit button and leave the text entry field blank. No Limit is the default setting.
· If you want to configure an alert threshold, in Kilobytes, that invokes automatic volume space growth and triggers and e-mail notification to the Serval's administrator, click the radio button to the left of the text-entry field.
· After selecting the radio button, enter the amount, in Kilobytes of disk space, that will trigger automatic volume growth and e-mail alerts. The automatic volume growth and e-mail alerts will trigger when the threshold value you set is met or exceeded by the size of the logical volume in the Name field.
· If you do not want to the Serval filer to support automatic volume space growth, select the No Limit button and leave the text entry field blank. No Limit is the default setting.
· If you want to configure the smallest amount, in Kilobytes, that the volume can grow as a result of automatic volume space growth, click the radio button to the left of the text-entry field.
· After selecting the radio button, enter the smallest amount, in Kilobytes of disk space, that the volume will be allowed to automatically grow.
· If you want the volume to grow at no specified minimum amount, select the Any button, and leave the text-entry field blank. Any is the default setting.
Step 5: In the Auto Grow Threshold field, enter the percentage of disk capacity at which the logical volume should grow. When the specified percentage of capacity is reached, the Serval's automatic volume growth feature is activated. Enter a percentage between 1 and 100. Zero (0) percentage is the default, and it causes the feature to be disabled.
Step 6: From the Vendor/Model pulldown listbox, select the type of storage that is connected to the SAN. Choose from:
Step 7: From the RAID Level pulldown listbox, select the level of RAID in use on the storage that is connected to the SAN. Choose from:
· If you want to configure the smallest individual LUN, in Megabytes, that the volume can grow as a result of automatic volume space growth, click the radio button to the left of the text-entry field.
· After selecting the radio button, enter the size, in Megabytes, of the smallest individual LUN that the Serval will take to allocate more volume space through automatic volume space growth.
· If you want the volume to take any individual LUN regardless of its size, select the Any button, and leave the text-entry field blank. Any is the default setting.
· If you want to configure the largest individual LUN, in Megabytes, that the volume can take as a result of automatic volume space growth, click the radio button to the left of the text-entry field.
· After selecting the radio button, enter the size, in Megabytes, of the largest individual LUN that the Serval will take to automatically allocate more volume space.
· If you want the volume to take any individual LUN regardless of its size, select the Any button, and leave the text-entry field blank. Any is the default setting.
Modifying Logical Volumes
After a volume has been created and added to the Volume Display, you can change the volume's name and usage quotas at any time by clicking the modify link in the Volume display. When you click the modify link, the Volume Modify dialog appears. Figure 32 shows the Volume Modify dialog.
Figure 32 Volume Modify DialogStep 1: To configure a new name for the volume, in the New Name field, enter the new name for the volume. Enter an alphanumeric character string from 1 to 48 characters in length.
· If you want to configure an absolute maximum limit for the amount, in Kilobytes, of storage that can be consumed by the logical volume in the New Name field, select the radio button to the left of the text-entry field.
· After selecting the button, enter the amount, in Kilobytes of the absolute maximum amount of storage space the volume can consume. Enter a numeric string.
· If you do not want to change the amount of storage space that the volume can consume, select the No Limit button and leave the text entry field blank. No Limit is the default setting.
· If you want to configure an alert threshold, in Kilobytes, that invokes automatic volume space growth and triggers and e-mail notification to the Serval's administrator, click the radio button to the left of the text-entry field.
· After selecting the radio button, enter the amount, in Kilobytes of disk space, that will trigger automatic volume growth and e-mail alerts. The automatic volume growth and e-mail alerts will trigger when the threshold value you set is met or exceeded by the size of the logical volume in the Name field.
· If you do not want the Serval filer to support automatic volume space growth, select the No Limit button and leave the text entry field blank. No Limit is the default setting.
· If you want to configure the smallest amount, in Kilobytes, that the volume can grow as a result of automatic volume space growth, click the radio button to the left of the text-entry field.
· After selecting the radio button, enter the smallest amount, in Kilobytes of disk space, that the volume will be allowed to automatically grow.
· If you want the volume to grow at no specified minimum amount, select the Any button, and leave the text-entry field blank. Any is the default setting.
Step 5: In the Auto Grow Threshold field, enter the percentage of disk capacity at which the logical volume should grow. When the specified percentage of capacity is reached, the Serval's automatic volume growth feature is activated. Enter a percentage between 1 and 100. Zero (0) percentage is the default, and it causes the feature to be disabled.
Deleting Logical Volumes
At any time after you have created a logical volume, you can delete it by selecting the Delete link on the Volume display. By clicking this link, you invoke the Delete Volume Confirmation dialog. Figure 33 shows this dialog.
Figure 33 Delete Volume Confirmation dialogStep 2: Invoke the Delete Volume Confirmation dialog by selecting
AgileView->Storage->Volume->Delete. The name of the volume is automatically carried to the Delete Volume Confirmation dialog.
Step 3: Click Apply to delete the volume and free any LUNs allocated it, or click Cancel to abort the deletion process.
Managing File Sets
The Serval filer supports file sets through the Volume display. File sets are a software construction that groups files into one logical group. A file set is essentially a special type of directory. File sets must always have their own directory, and they are always the root of that directory. When you create a file set, you are creating a parent level entity into which you are adding individual files. File sets must be created in the same tree, and cannot span across different directory trees. Figure 34 shows the File Sets display.
Figure 34 File Set display
· the Refresh button that automatically redisplays the File Set display after updating any file set information.
Adding a File Set
From the File Set display, you can add a new fileset and configure its parameters by clicking the Add File Set button. This button invokes the FileSet Add dialog. Figure 35 shows the File Set Add dialog.
Figure 35 File Set Add dialogStep 1: From the File Set display, click the Add Fileset button to invoke the File Set Add dialog. You will notice that the Volume Name field is already populated with the name of the volume from the Volume display where you clicked the fileset link.
Step 2: In the File Set Path field enter the path to the file set. Make sure that you reference the path from the root of the volume listed in the Volume field. You must include the (/). Enter an alphanumeric character string.
Monitoring File Set Usage
· file set, which show the aggregate usage of all configured users and groups that are using the file set.
· user, which shows the usage of one or all users using a file set. You can view the usage information by user name or UID.
· group, which shows the usage of one or all groups using a file set. You can view the usage information by group name or GID.
Figure 36 shows the File Set Usage display. This display shows statistics about how much a specific file set has been used by all users and groups that are configured to access it.
Figure 36 File Set Usage displayTable 21 shows the contents of the File Set Usage display and explains what each field means. All of the following fields are tracked automatically by the Serval.
Even though the Serval filer intermittently updates the information contained in this display, you can manually refresh the display at any time by clicking the Refresh button.
To facilitate navigation through the GUI, the menu path in the active window is live. As a result you can click any of the underlined words in the path to link directly to that portion of the GUI instead of repeatedly clicking the browser's Back button.
Monitoring Per-Group Usage of File Sets
You can display the group usage conditions of one or more file sets through the File Sets Group Sage display. This display lists all of the group IDs (GIDs) that are configured to access a file sets. The GIDs are listed in order to facilitate locating a specific GID. Figure 37 shows the File Sets Group Usage display.
Figure 37 File Set Group Usage DisplayTable 22 shows the File Set Group Usage display and explains what each field in the display means.
Even though the Serval filer intermittently updates the information contained in this display, you can manually refresh the display at any time by clicking the Refresh button.
To facilitate navigation through the GUI, the menu path in the active window is live. As a result you can click any of the underlined words in the path to link directly to that portion of the GUI instead of repeatedly clicking the browser's Back button.
Monitoring Per-User Usage of File Sets
You can display the per-user usage conditions of one or more file sets through the File Sets Group Usage display. This display lists all of the user IDs (UIDs) that are configured to access a file sets. The UIDs are listed in order to facilitate locating a specific UID. Figure 38 shows the File Sets User Usage display.
Figure 38 File Set User Usage DisplayTable 23 shows the File Set User Usage display and explains what each field in the display means.
Even though the Serval filer intermittently updates the information contained in this display, you can manually refresh the display at any time by clicking the Refresh button.
To facilitate navigation through the GUI, the menu path in the active window is live. As a result, you can click any of the underlined words in the path to link directly to that portion of the GUI instead of repeatedly clicking the browser's Back button.
Setting Quota Conditions for File Sets
You can set the quota values for particular file sets through the File Set Quota dialog. The Serval filer ensures security on file set by applying the strictest conditions to a file set. Therefore, any quotas you set on a file set are applied in addition to any per-user or per-group quotas. Quotas on file sets apply to all UIDs and GIDs that access the file set. Quotas are applied to either Inodes or file system blocks. Quotas are tracked by three variables you configure:
· a soft limit, which is a typical usage allocation that is normally enforced but can be exceeded for a specified time limit. The soft limit can be applied to inodes or blocks.
· a hard limit, which is the absolute maximum usage limit that can be supported by a user or group, but for only a specified time limit. The hard limit can be applied to inodes or blocks.
· a time limit, which the absolute amount of time that any group or user can consume storage resources that have progressed past the soft limit into the time limit. The time limit can be applied to inodes or blocks.
Setting Quotas on File Sets
Quotas can be configured on specified file sets. When quotas are applied to file sets, all users and groups that access the file set are subject to the quota conditions for the file set as well as any quota conditions configured for the users and groups themselves. Figure 39 shows the File Set Quota dialog.
Figure 39 File Set Quota displayStep 1: In the Soft Quota field, enter the quota settings that are applied to Inodes. Enter a value, in MB of storage space.
Step 2: In the Hard Quota field, enter the quota settings that are applied to Inodes. Enter a value, in MB of storage space.
Step 3: In the Time Limit field, enter the quota settings that are applied to Inodes. Enter a value, in seconds.
Step 4: In the Soft Quota field, enter the quota settings that are applied to the Serval's 8 KB file system blocks. Enter a value, in number of blocks.
Step 5: In the Hard Quota field, enter the quota settings that are applied to the Serval's 8 KB file system blocks. Enter a value, in number of blocks.
Step 6: In the Time Limit field, enter the quota settings that are applied to the Serval's 8 KB file system blocks. Enter a value, in number of blocks in seconds.
Step 7: Click the Save button to send the quotas settings to the config file and automatically update the file set quota parameters.
Monitoring Quotas on Groups
Quotas can be configured on specified groups. When quotas are applied to groups, all users in the group are subject to the group's quota conditions for the group. Also, in situations where quotas are configured on individual users as well as on groups, the Serval filer enforces both quotas. In situations where quotas exist for users, groups, and file sets, the Serval enforces all quotas to provide the strictest control over the usage of the file set. Figure 40 shows the File Set Group Quota dialog.
Figure 40 File Set Group Quota displayTable 24 shows the contents of the File Set Group Quota display, and explains what each field means.
Even though the Serval Filer intermittently refreshes the display, you can manually refresh the display at any time by clicking the Refresh button.
Configuring Quotas on Groups
You can Configure Group Quota parameters through the File Set Group display. ON this display, the Operation field contains a link called "modify" that leads to the Group Quota Modify dialog. This dialog is where you can configure change individual quota parameters for existing quotas. Figure 41 shows the group Quota Modify dialog.
Figure 41 Group Quota Modify dialogThe Group ID field is already filled in based on the group quota that you selected.
Step 1: In the File System Object Soft Quota field, enter the quota settings that are applied to groups that access Inodes. Enter a value, in MB of storage space.
Step 2: In the File System Object Hard Quota field, enter the quota settings that are applied to groups that access Inodes. Enter a value, in MB of storage space.
Step 3: In the File System Object Time Limit field, enter the time limit that a group will be allowed to access an Inode. Enter a value, in seconds.
Step 4: In the Soft Quota field, enter the file system block quotas that will be applied to groups. Enter a value, in number of blocks.
Step 5: In the Hard Quota field, enter the file system block quotas that will be applied to groups. Enter a value, in number of blocks.
Step 6: In the Time Limit field, enter the time limit that a group will be allowed to access file system blocks. Enter a value, in number of blocks in seconds.
Step 7: Click the Save button to send the quotas settings to the config file and automatically update the file set quota parameters.
Configuring Quotas on Users
You can Configure User Quota parameters through the File Set Group display. On this display, the Operation field contains a link called "modify" that leads to the User Quota Modify dialog. This dialog is where you can configure change individual quota parameters for existing quotas. Figure 42 shows the User Quota Modify dialog.
Figure 42 User Quota Modify dialogThe User ID field is already filled in based on the user quota that you selected.
Step 1: In the File System Object Soft Quota field, enter the quota settings that are applied to users that access Inodes. Enter a value, in MB of storage space.
Step 2: In the File System Object Hard Quota field, enter the quota settings that are applied to users that access Inodes. Enter a value, in MB of storage space.
Step 3: In the File System Object Time Limit field, enter the time limit that a user will be allowed to access an Inode. Enter a value, in seconds.
Step 4: In the Soft Quota field, enter the file system block quotas that will be applied to users. Enter a value, in number of blocks.
Step 5: In the Hard Quota field, enter the file system block quotas that will be applied to users. Enter a value, in number of blocks.
Step 6: In the Time Limit field, enter the time limit that a user will be allowed to access file system blocks. Enter a value, in number of blocks in seconds.
Step 7: Click the Save button to send the quotas settings to the config file and automatically update the file set quota parameters.
Configuring Default Quotas
Default quotas act like templates; they enable you to set default usage conditions for a user, group, or file set:
· if quotas are not configured for specific users, then default quotas are enforced. If quotas are configured for specific users, then those quotas are used because they are more specific. Any users not covered by their own quota are covered by the default file set quota.
· if quotas are not configured for specific groups, then default quotas are enforced. If quotas are configured for specific groups, then those quotas are used because they are more specific. Any groups not covered by their own quota are covered by the default file set quota.
· if quotas are not configured for a specific file set, then default quotas are enforced. When you create a default quota for a file set, then the quota is applied to all the file sets that are created under the particular file set.
When you create a default quota, the quota is not automatically enabled.
You can configure Default quotas through the File Set display. On this display, the Quota Details column contains a hyperlink called "Default." By clicking this link, you invoke the Default Quota dialog, which enables you to configure the default quota parameters for file sets, users, and groups. Figure 43 shows the Default Quota dialog.
Figure 43 Default Quota dialogYou do not need to configure all three types of default quotas. You can select any type of default quota that you want. However, configuring all three types of default quotas will not adversely affect performance.
Configuring Default Quotas on File Sets
To configure default quotas for file sets, locate the first of the three sections on the dialog, and follow this procedure:
Step 1: In the File System Object Soft Quota field, enter the quota settings that are applied to applied to Inodes containing the file set. Enter a value, in MB of storage space.
Step 2: In the File System Object Hard Quota field, enter the quota settings that are applied to Inodes containing the file set. Enter a value, in MB of storage space.
Step 3: In the File System Object Time Limit field, enter the time limit that anyone can be allowed to access the Inode containing the file set. Enter a value, in seconds.
Step 4: In the Soft Quota field, enter the file system block quotas that will be applied to file set. Enter a value, in number of blocks.
Step 5: In the Hard Quota field, enter the file system block quotas that will be applied to the file set. Enter a value, in number of blocks.
Step 6: In the Time Limit field, enter the time limit that a user will be allowed to access file system blocks in the file set. Enter a value, in number of blocks in seconds.
Step 7: Click the Save button to send the quotas settings to the config file and automatically update the file set quota parameters.
· If you do not want to configure other default quotas, click a link in the Storage->Volume->File Set->Default Quota path at the top of the active window.
Configuring Default Quotas on Groups
To configure default quotas for groups, locate the second of the three sections on the dialog, and follow this procedure:
Step 1: In the File System Object Soft Quota field, enter the quota settings that are applied to groups that access Inodes. Enter a value, in MB of storage space.
Step 2: In the File System Object Hard Quota field, enter the quota settings that are applied to groups that access Inodes. Enter a value, in MB of storage space.
Step 3: In the File System Object Time Limit field, enter the time limit that a group will be allowed to access an Inode. Enter a value, in seconds.
Step 4: In the Soft Quota field, enter the file system block quotas that will be applied to groups. Enter a value, in number of blocks.
Step 5: In the Hard Quota field, enter the file system block quotas that will be applied to groups. Enter a value, in number of blocks.
Step 6: In the Time Limit field, enter the time limit that a group will be allowed to access file system blocks. Enter a value, in number of blocks in seconds.
Step 7: Click the Save button to send the quotas settings to the config file and automatically update the file set quota parameters.
· If you do not want to configure other default quotas, click a link in the Storage->Volume->File Set->Default Quota path at the top of the active window.
Configuring Default Quotas for Users
To configure default quotas for users, locate the third of the three sections on the dialog, and follow this procedure:
Step 1: In the File System Object Soft Quota field, enter the quota settings that are applied to users that access Inodes. Enter a value, in MB of storage space.
Step 2: In the File System Object Hard Quota field, enter the quota settings that are applied to users that access Inodes. Enter a value, in MB of storage space.
Step 3: In the File System Object Time Limit field, enter the time limit that a user will be allowed to access an Inode. Enter a value, in seconds.
Step 4: In the Soft Quota field, enter the file system block quotas that will be applied to users. Enter a value, in number of blocks.
Step 5: In the Hard Quota field, enter the file system block quotas that will be applied to users. Enter a value, in number of blocks.
Step 6: In the Time Limit field, enter the time limit that a user will be allowed to access file system blocks. Enter a value, in number of blocks in seconds.
Step 7: Click the Save button to send the quotas settings to the config file and automatically update the file set quota parameters.
· If you do not want to configure other default quotas, click a link in the Storage->Volume->File Set->Default Quota path at the top of the active window.
Activating or Deactivating Quota Software
· When the quota software is enabled, quotas apply and users and groups can access file sets with the configured usage conditions. When a quota is enabled, the quota software experiences an initialization stage. During quota initialization, the virtualized disk and tape storage resources are located for each file system. When you create a quota, the SAN Filer requires a short amount of time to apply all the quotas to the virtualized storage resources for a particular file system. However, as soon as the SAN Filer detects a quota and the resource to which it applies, the SAN Filer activates and enforces the quota regardless of whether all virtualized resources have been located and identified. Quota initialization occurs whenever quotas are created, modified, enabled or disabled.
You can enable or disable quota software through the File Set display. On this display, the Operation column contains a hyperlink called "Quota On." By clicking this link, you invoke the Quota Status Confirmation dialog, which enables you to change the state of a quota. Figure 44 shows the Quota Status Confirmation dialog.
Figure 44 Quota Status Confirmation dialogDeleting File Sets
You can delete individual file sets entirely from the Serval filer. When you do so, the file set is no longer available. You can delete file sets through the File Set display. On this display, the Operation column contains a hyperlink called "Delete." By clicking this link, you invoke the Delete File Set Confirmation dialog, which enables you to change the state of a quota. Figure 45 shows the Delete File Set Confirmation dialog.
Figure 45 Delete FileSet ConfirmationManaging Snapshots
Snapshots are static pictures of the Agile File System. They enable many important functions of data protection, such as:
Snapshots provide a glimpse of the file system at a particular point in time. This "point-in-time" view of the file system occurs when the storage administrator manually creates a snapshot, at which time all modify (write) file system transactions are postponed for an instant while the SAN Filer gets the file system information. Read only file system transactions are still permissible when a snapshot is occurring. When the file system information is obtained, the information is written into a snapshots file. The SAN Filer does not automatically take a snapshot at initial boot up.
Scheduled snapshots can be configured to occur either hourly, daily, or weekly. Daily snapshots are taken at midnight, and weekly snapshots are taken at midnight of every Sunday. However, daily and weekly snapshots have the following scheduling considerations:
The SAN Filer supports a default snapshot schedule, as shown in Table 25.
Table 25 Default Snapshot Schedule
Configuring Scheduled Snapshots
You can configure snapshots from the Volume display. On this display, the Operation column has a link called, "Snapshot." By clicking this link, you invoke the Snapshot dialog, where you can configure a snapshot schedule for automatic snapshots, take an on-demand snapshot manually, and display the snapshot list. Figure 46 show the Snapshot Dialog.
Figure 46 Snapshot DialogStep 1: In the Snapshot Reserve field, enter a percentage that indicates how much of the disk space you want reserved for snapshots. Enter a value from 0 to 100.
Step 2: In the Number of Weekly Snapshots to Keep field, enter the maximum number of weekly snapshots you want to keep on the Serval filer. Enter a number between 0 and 4.
Step 3: In the Number of Daily Snapshots to Keep field, enter the maximum number of weekly snapshots you want to keep on the Serval filer. Enter a number between 0 and 7.
Step 4: In the Number of Hourly Snapshots to Keep field, enter the maximum number of weekly snapshots you want to keep on the Serval filer. Enter a number between 0 and 23.
Step 5: In the Schedule for Hourly Snapshots matrix, click the check box(es) that correspond to the hour(s) at which you want the Serval to take automated snapshots. You can click any number of hours throughout the displayed 24-hour grid. By default, the 12 p.m. check box is checked.
Step 6: After you set the appropriate times, click Apply to set the times or Reset to reset the schedule.
The Snapshot List is the bottom section of the Snapshots Dialog. This section applies to on-demand snapshots, and it lists the currently configured on-demand snapshots and the parameters with which they have been set. Table 26 shows the contents of the Snapshots List, and explains what each field means.
Creating an On-Demand Snapshot
On the Snapshots Dialog, you can create an on-demand snapshot by clicking the Create Snapshot button. On-demand snapshots can be taken at any time, and are supplemental to any scheduled snapshots. By clicking this button, you invoke the Create Snapshot dialog. Figure 47 shows the Create Snapshot Dialog.
Figure 47 Create Snapshot dialogStep 1: In the Snapshot Name field, enter the name that you are assigning to the on-demand snapshot you are creating. Enter an alphanumeric character string.
Deleting On-Demand Snapshots
After an on-demand snapshot has been taken, you can permanently remove it from the Snapshot List. One the Snapshot dialog, the Snapshot List contains a link called "delete" in the Operation field. By clicking this link, you invoke the Delete Snapshot Confirmation dialog. Figure 48 shows the Delete Snapshot Confirmation dialog.
Figure 48 Delete Snapshot Confirmation dialogConfiguring NFS Shares
The file system is shared over an IP interface that is connected through the SAN Filer's File Processing NIM. The SAN Filer shares its file system information with IP-connected clients based on conditions that the storage administrator configures. By default, shared file system information is read-only, unless the requesting client is allowed to mount the resource differently. Clients are able to mount resources differently depending on the access permissions they have been granted.
NFS shares are individual definitions of hosts in the IP network that can mount the file system. You can set share definitions that allow different levels of access-for example, read, write, root, and root squash:
· Read-only access enables hosts to access shared resources without the ability to make changes. With read-only access set, the SAN Filer permits resources to be available for viewing only. Resources cannot be modified in any way. The SAN Filer supports configuring up to 255 read-only hosts per share definition and read-only access can be applied to subnets as well as individual hosts.
· Read-write access enables hosts to access shared resources with the ability to make changes. With read-write access set, the SAN Filer permits read-write hosts to not only view resources, but access them for modifying. The SAN Filer supports configuring up to 255 read-write hosts per share definition, and read-write access can be applied to subnets as well as individual hosts.
Root squash access enables the SAN Filer to map UID 0 to a predetermined non-root UID for file system access. A non-root UID is any UID other than 0. With root squash the SAN Filer can accept a pre-configured root user if root squash is not configured, or assign a root user to a different UID. If the SAN Filer assigns the root UID, that UID will always be 99. Root squash interoperates with root access in the following ways:
· If root access is not set for a client requesting to mount a resource, the SAN Filer does not accept the UID 0, and sets the root UID to 99.
By default, root squash exists on share interfaces unless explicitly configured to allow UID 0.
· Root access enables the clients to access shared resources as the root user, UID 0. The SAN Filer supports up to 255 root hosts, and root access can be applied to subnets as well as individual hosts.
Enabling root access on a shared resource does not guarantee that the root user will be granted full access. The permissions assigned on the resource can overwrite the root access. For example, if /usr/local/agile is shared with read-only access, and the root user logs into a client, when the client mounts /usr/local/agile, the root user will only be able to access resources with read only permissions.
Figure 49 Volume Share display
Even thought the Serval Filer manually refreshes its display, you can manually refresh the information in the Volume Share display by clicking the Refresh button.
Adding an NFS Share
On the Volume Share display you can configure an NFS share definition through the Add Share button. By clicking this button, you invoke the Volume Share Add dialog, where you can create new NFS shares, define the volume and path that they will share, and add a new network host. Figure 50 shows the Volume Share Add dialog.
Figure 50 Volume Share Add dialogStep 1: In the Path field, enter the path to the network resources that will be shared. Enter the path from the root of the volume listed in the Volume Name field.
Step 2: In the Share via IP Interface field, enter the IP address of the interface on which the share definition will be exported. Enter the IP interface address in dotted decimal notation, such as 10.101.110.26.
Step 3: Click the Save button to immediately submit this information to the configuration file and the Volume Share display.
Step 4: In the Host/Subnet List section of the dialog, you can enter the information for the following fields, by clicking the Add Host button:
Adding a Network Host
On the Volume Share display, you can add a network host and its NFS share conditions through the Add Host button. By clicking this button, you invoke the Volume Share Add Host dialog, where you can create new NFS shares and define the conditions that they will apply to the network host you specify in the dialog. Figure 51 shows the Volume Share Add Host dialog.
Figure 51 Volume Share Add Host dialogStep 1: In the Host IP Address field, enter the node address of the host that you are adding to the Volume Share display. Enter the host's IP address in dotted decimal notation, and do not include any mask bits, such as 101.102.103.139
Step 2: From the Permission pulldown listbox, select the appropriate access permission for the host. Select either read-only or read-write.
Step 3: From the Root Squash pulldown listbox, select whether you want root squash to change the UID of users who log in as root on the host. Select either Yes, perform root squash, or No, leave root users as UID 0.
Step 4: When parameters have been set, click the Save button to activate changes and save the settings to the config file.
Modifying NFS Shares
On the Volume Share display the Operation column contains a link called, modify. This link invokes the Volume Share Modify dialog where you can change settings on an existing NFS share. This dialog enables you to change parameters in the share definition without having to completely remove then recreate the NFS definition. Figure 52 shows the Volume Share Add Host dialog.
Figure 52 Volume Share Modify dialogStep 1: In the Share via IP Interface field, enter the IP address of the interface on which the share definition will be exported. Enter the IP interface address in dotted decimal notation, such as 10.101.110.26.
Step 2: Click the Save button to immediately submit this information to the configuration file and the Volume Share display.
Step 3: You can add a networked host by clicking the Add Host button. By clicking this button you invoke the Volume Share Add Host dialog. To add a new host, see "Adding a Network Host"
Modifying NFS Share Targets
In the Operation field, you can modify the existing setting by clicking the modify link. This link invokes the Modify Share Target Dialog where you can configure host parameters. Figure 53 shows the Modify Share Target dialog.
Figure 53 Modify Share Target dialogStep 1: In the Host field, enter the IP address of the host for which you are modifying NFS share definitions. Enter the IP address in dotted decimal notation, but do not include any mask bits. For example, 10.101.103.14.
Step 2: From the Permission pulldown listbox, select the access permission that you are changing on the NFS share. Select from read-only or read-write.
Step 3: From the Root Squash pulldown listbox, select whether you want the NFS share to allow root squash to change UID 0 to UID 99 for users who log in to the Serval as root. Select from yes, to enable root squash, or no to allow root UID 0.
Step 4: Click Save to immediately activate changes to the Serval filer, and commit these changes to the config file.
Deleting Hosts
On the Volume Share Modify display, you can completely delete a host from the NFS share definition by clicking the "delete" link in the Operation column. By clicking this link you, invoke the Delete Share Confirmation dialog where you can specify the host IP address that you want to completely remove. Figure 54 shows the Delete Share Confirmation dialog.
Figure 54 Delete Share Confirmation dialogUnsharing an NFS Share
On the Volume Share display, you can unshare a resource by clicking the "unshare" link in the Operation field. By clicking this link, you invoke the Unshare Share Confirmation dialog where you can completely remove the path to the resource that is being shared. Unsharing is different than deleting a host. By unsharing you remove the path to resource, so no hosts can reach the resource. By deleting a host, the path remains intact for all hosts except the one that you are deleting. Figure 55 shows the Unshare Share Confirmation dialog.
Figure 55 Unshare Path Confirmation dialogManaging Disks
The Serval file supports disk drives and disk arrays. The Serval file maintains a list of disks that it knows about. This list is the Storage Disk display. Figure 56 shows the Storage Disk display.
Figure 56 Storage Disk display
Monitoring Used LUNs
In the Storage Disk display's Used column, the amount of used disk space is displayed. The number indicated is a link to the Used LUNs display where you can view specific LUNs that have been assigned to a volume. Figure 57 shows the Used LUNs display.
Figure 57 Used LUNs display
Table 29 Contents of the Used LUNs displayIndicates the ID string of the SCSI controller for the Used LUN. of the LUN.
· Even though the Serval Filer automatically refreshes the Used LUNs display you can automatically refresh this display at any time by clicking the Refresh button.
Monitoring LUN Details
Through the Used LUNs display, you can monitor details about each LUN in the list. On the Used LUNs display, you can view detailed information about each LUN in the list, by clicking the digit string in the WWN:LUN field. This string is a link that invokes the LUN Detail display, where you can view particular details about the LUN. Figure 58 shows the LUN Detail display.
Figure 58 LUN Detail display
Viewing LUN Statistics
From the LUN Details display you can view specific statistics about each LUN in the Used LUNs display by clicking the View Stats button. By clicking this button, you invoke the LUN Stats display where you can view specific performance details about a particular LUN. Figure 59 shows the LUN Stats display.
Figure 59 LUN Stats display
Even though the Serval intermittently refreshes the LUN Stats display, you can manually refresh this display at any time by clicking the Refresh button.
Resetting LUNs
On the Used LUNs display, the Operation column contains a link called "reset." By clicking this link you invoke the Reset LUN Confirmation dialog where you can cause a LUN to be reset. Resetting a LUN causes it to re-initialize so that it can be used again. When you reset a LUN, all existing information about the WWN and LUN ID remain intact. Figure 60 shows the Reset LUN Confirmation dialog.
Figure 60 Reset LUN Confirmation dialogViewing the Free LUNs
Free LUNs are those LUNs that are available to the Serval for assignment to a logical volume, but have not yet been assigned. Free LUNs are part of a storage pool, and they can be assigned out of that pool as needed when the Serval's automatic volume growth software determines that a logical volume needs to more storage space.
The Storage Disk display contains a field called Free. This field displays the amount of disk space that each free LUN has available. This field contains a link to the Free LUNs display where you can view a list of the free LUNs available to the Serval. By clicking this link, you invoke the Free LUNs display, where you can view individual LUNs. Figure 61 shows the Free LUNs display.
Figure 61 Free LUNs display
Table 32 Contents of the Free LUNs displayIndicates the ID string of the SCSI controller for the Free LUN. of the LUN.
Shows the amount of disk space in Kilobytes that the LUN has available.
· Even though the Serval Filer automatically refreshes the Free LUNs display you can automatically refresh this display at any time by clicking the Refresh button.
Viewing Free LUN Details
Through the Free LUNs display, you can monitor details about each free LUN in the list by clicking the digit string in the WWN:LUN name field. This string is a link that invokes the LUN Detail display, where you can view particular details about the LUN. For information about the Free LUN details, see "Viewing LUN Statistics".
Viewing Free LUN Statistics
From the LUN Details display you can view specific statistics about each LUN in the Free LUNs display by clicking the View Stats button. By clicking this button, you invoke the LUN Stats display where you can view specific performance details about a particular LUN. For information about the Free LUN statistics, see "Viewing LUN Statistics".
Resetting Free LUNs
On the Free LUNs display, the Operation column contains a link called "Reset." By clicking this link you invoke the Reset LUN Confirmation dialog where you can cause a LUN to be reset. Resetting a LUN causes it to re-initialize so that it can be used again. When you reset a LUN, all existing information about the WWN and LUN ID remain intact. For information about resetting a free LUN, see "Resetting LUNs".
Monitoring Foreign LUNs
Foreign LUNs are those LUNs that the Serval knows about, but it cannot use. Foreign LUNs do not own an Agile label, a software tag that makes the LUN available to the Serval for assignment to a logical volume, or available to the Serval's automatic volume growth software.
The Storage Disk display contains a field called Foreign. This field displays the amount of disk space that each foreign LUN has available. This field contains a link to the Foreign LUNs display where you can view a list of the foreign LUNs that the Serval knows about. By clicking this link, you invoke the Foreign LUNs display, where you can view individual LUNs. Figure 62 shows the Foreign LUN display.
Figure 62 Foreign LUNs display
· Even though the Serval Filer automatically refreshes the Foreign LUNs display you can automatically refresh this display at any time by clicking the Refresh button.
Labelling Foreign LUNs
Foreign LUNs are those LUNs that do not have an Agile Storage label, so they are not available to the Serval for assignment in a logical volume or allocation out of the storage pool for automatic volume growth. A label is associated with a LUN's WWN and LUN ID. The label is invisible to administrators and end users once it has been assigned to a LUN.
The Foreign LUNs contains a link called "label" that links in the Operation field. By clicking this link you invoke the Label LUN Confirmation dialog where you can apply the Agile label to a LUN. Figure 63 shows the Label LUN Confirmation dialog.
Figure 63 Label LUN Confirmation dialogStep 1: Click the Continue button to assign a label to the LUN indicated in the Controller and LUN fields.
Step 2: Click the Cancel button to abort the LUN labelling procedure and return to the Foreign LUN display.
Resetting Foreign LUNs
On the Foreign LUNs display, the Operation column contains a link called "Reset." By clicking this link you invoke the Reset LUN Confirmation dialog where you can cause a LUN to be reset. Resetting a LUN causes it to re-initialize so that it can be rediscovered again. When you reset a LUN, all existing information about the WWN and LUN ID remain intact. For information about resetting a free LUN, see "Resetting LUNs".
Monitoring Out-of-Cluster LUNs
Out-of-cluster LUNs are those LUNs that a Serval filer is aware of, but belong to another cluster. Because a Serval filer cannot use resources unless they are configured in the same cluster as the Serval filer, the out-of-cluster notation is important. It indicates which LUNs are labelled and assigned to a different Serval.
The Storage Disk display contains a field called Out Cluster. This field displays the amount of disk space that each foreign LUN has available. This field contains a link to the Out-Cluster LUNs display where you can view a list of the out-of-cluster LUNs that the Serval knows about. By clicking this link, you invoke the Out-of-Cluster LUNs display, where you can view LUNs that are not part of the Serval's cluster. Figure 64 shows the Out-of-Cluster LUN display.
Figure 64 Out-of-Cluster LUNs display
· Even though the Serval Filer automatically refreshes the Out-of-Cluster LUNs display you can automatically refresh this display at any time by clicking the Refresh button.
· You can proceed to the first page of the Out-of-Cluster LUNs display by clicking the First button.
Labelling Out-of-Cluster LUNs
The Out-of-Cluster LUNs display contains a link called "label" in the Operation field. By clicking this link you invoke the Label LUN Confirmation dialog where you can apply the Agile label to a LUN. For information about labelling out-of-cluster LUNs, see "Labelling Foreign LUNs".
Resetting Out-of-Cluster LUNs
On the Out-of-Cluster LUNs display, the Operation column contains a link called "Reset." By clicking this link you invoke the Reset LUN Confirmation dialog where you can cause a LUN to be reset. Resetting a LUN causes it to re-initialize so that it can be rediscovered again. When you reset a LUN, all existing information about the WWN and LUN ID remain intact. For information about resetting a free LUN, see "Resetting LUNs".
Creating Volumes
From the Storage Disk display, you can create logical volumes. On this display the Operation column contains the "Create Volume" link. By clicking this link, you invoke the Create Volume dialog, where you can assign a LUN to a volume and create the volume's usage conditions. Figure 65 shows the Create Volume dialog.
Figure 65 Create Volume dialogStep 1: In the Volume Name dialog, enter an alphanumeric character string that identifies the volume that you are creating. Enter a character string from 1 to 48 characters in length.
· If you want to configure the smallest individual LUN, in Megabytes, that the volume can grow as a result of automatic volume space growth, click the radio button to the left of the text-entry field.
· After selecting the radio button, enter the size, in Megabytes, of the smallest individual LUN that the Serval will take to allocate more volume space through automatic volume space growth.
· If you want the volume to take any individual LUN regardless of its size, select the Any button, and leave the text-entry field blank. Any is the default setting.
· If you want to configure the largest individual LUN, in Megabytes, that the volume can take as a result of automatic volume space growth, click the radio button to the left of the text-entry field.
· After selecting the radio button, enter the size, in Megabytes, of the largest individual LUN that the Serval will take to automatically allocate more volume space.
· If you want the volume to take any individual LUN regardless of its size, select the Any button, and leave the text-entry field blank. Any is the default setting.
· If you want to configure an absolute maximum limit for the amount, in Kilobytes, of storage that can be consumed by the logical volume in the Name field, select the radio button to the left of the text-entry field.
· After selecting the button, enter the amount, in Kilobytes of the absolute maximum amount of storage space the volume can consume. Enter a numeric string.
· If you do not want to limit the amount of storage space that the volume can consume, select the No Limit button and leave the text entry field blank. No Limit is the default setting.
· If you want to configure an alert threshold, in Kilobytes, that invokes automatic volume space growth and triggers and e-mail notification to the Serval's administrator, click the radio button to the left of the text-entry field.
· After selecting the radio button, enter the amount, in Kilobytes of disk space, that will trigger automatic volume growth and e-mail alerts. The automatic volume growth and e-mail alerts will trigger when the threshold value you set is met or exceeded by the size of the logical volume in the Name field.
· If you do not want to the Serval filer to support automatic volume space growth, select the No Limit button and leave the text entry field blank. No Limit is the default setting.
· If you want to configure the smallest amount, in Kilobytes, that the volume can grow as a result of automatic volume space growth, click the radio button to the left of the text-entry field.
· After selecting the radio button, enter the smallest amount, in Kilobytes of disk space, that the volume will be allowed to automatically grow.
· If you want the volume to grow at no specified minimum amount, select the Any button, and leave the text-entry field blank. Any is the default setting.
Step 7: In the Auto Grow Threshold field, enter the percentage of disk capacity at which the logical volume should grow. When the specified percentage of capacity is reached, the Serval's automatic volume growth feature is activated. Enter a percentage between 1 and 100. Zero (0) percentage is the default, and it causes the feature to be disabled.
Managing Tape Devices
In addition to disk drives and arrays, the Serval Filer provides intelligent file services for tape drives and tape libraries. This tape storage will be called tape devices in this documentation. Tape devices, like disk devices, are detected automatically at initial boot up or whenever the topology changes due to addition or deletion of storage. The discovery of tape or disk devices occurs through the Serval's SCSI and fibre channel protocols.
The Serval Filer displays its tape devices in the Storage Tape display. This display contains the tape devices that have been discovered and registered as LUNs. Figure 66 shows the tape devices that have registered with the Serval.
Figure 66 Storage Tape display
Even though the Serval filer intermittently refreshes the display, you can manually update the contents of the Storage Tape display by clicking the Refresh button.
Viewing Tape Device Details
Through the Storage Tape display you can monitor details about each tape device in the list by clicking the digit string in the WWN:LUN name field. This string is a link that invokes the Tape Detail display, where you can view particular details about the LUN. Figure 67 shows the Tape Detail display.
Figure 67 Tape Detail displayFor information about the Free LUN details, see "Monitoring LUN Details". The information in the display and the table describing it are the same, except the Tape Detail display shows information about tape devices instead of LUNs.
This display contains the View Stats button that enables you to view performance and operating statistics for the tape devices connected to the Serval filer.
Viewing Tape Statistics
Through the Tape Detail display, you can view operating statistics for the tape drives that the Serval filer knows about through the View Stats button. By clicking this display, you invoke the Tape Stats Detail display. Figure 68 shows the Tape Stats Detail display.
Figure 68 Tape Detail Stats displayFor information about the Tape Detail Stats display, see "Viewing LUN Statistics". The information in this display and the table describing it are the same as in Monitoring LUN Details, except the Tape Detail display shows information about tape devices instead of LUNs.
Even though the Serval filer intermittently refreshes the contents of the Tape Detail Stats display, you can update the contents of this display at any time by issuing the Refresh button.
Resetting Tape Devices
On the Storage Tape display, the Operation column contains a link called "Reset." By clicking this link you invoke the Reset Tape Confirmation dialog where you can cause a tape device to be reset. Resetting a tape causes it to re-initialize so that it can be rediscovered again. When you reset a tape device, all existing information about the WWN and LUN ID remain intact. Figure 70 shows the Reset Tape Confirmation dialog.
Figure 69 Reset Tape Confirmation dialogManaging Storage Ports
The SAN Filer automatically detects LUNs through a storage port. The storage port is the fibre channel, or fibre channel-compliant, transceiver that connects an individual fibre channel slice into the fibre channel topology.
Storage ports interact with physical storage devices to discover LUNs. When physical devices are connected to the SAN Filer through a storage port, SCSI discovery routines learn the device and its characteristics. The discovered device is virtualized and created as a LUN. The SAN Filer supports four storage ports on each Storage Processing NIM.
Figure 70 Storage Port displayTable 36 shows the contents of the Storage Port display, and explains what each field contains.
Even though the Serval intermittently refreshes the contents of the Storage Port display, you can update the contents of the display at any time by clicking the Refresh button.
Viewing Port Details
Through the Storage Port display you can monitor details about each port in the list by clicking the digit string in the Slot/Port name field. This string is a link that invokes the Storage Port Detail display, where you can view particular details about the port. Figure 71 shows the Storage Port Detail display.
Figure 71 Storage Port Detail display
From this display, you can view detailed operating and performance statistics for the storage port by clicking the View Stats button.
Storage Port Detailed Statistics Display Has Changed
In the online help, Figure 69 "Storage Port Stats Display" has been changed. The new display is the Storage Port Stats Details display. The new display is shown in Figure 3.
Figure 3 Storage Ports Stats Detail Display
Even though the Serval intermittently refreshes the contents of the Storage Port display, you can update the contents of the display at any time by clicking the Refresh button.
Enabling Storage Ports
Through the Storage Port display you can manually enable a disabled port. The Operation field of the Storage Port display contains a link called "Enable." By clicking this link, you invoke the Enable Port Confirmation dialog, where you can change the port's state. Figure 72 shows the Enable Port Confirmation display.
Figure 72 Enable Port Confirmation dialogDisabling a Storage Port
Through the Storage Port display you can manually disable an enabled port. The Operation field of the Storage Port display contains a link called "Disable." By clicking this link, you invoke the Disable Port Confirmation dialog, where you can change the port's state. Figure 73 shows the Disable Port Confirmation display.
Figure 73 Disable Port Confirmation dialog
![]() |
![]() |
![]() |
![]() |