Symantec™ FileStore Command-Line Administrator's Guide

Symantec FileStore Command-Line Administrator's Guide
5.6
Symantec FileStore Command-Line Administrators Guide

The software described in this book is furnished under a license agreement and may be used only in accordance with the terms of the agreement. Product version: 5.6 Document version: 5.6.0
Legal Notice
Copyright 2011 Symantec Corporation. All rights reserved. Symantec, the Symantec logo, Veritas, Veritas Storage Foundation, CommandCentral, NetBackup, Enterprise Vault, and LiveUpdate are trademarks or registered trademarks of Symantec corporation or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners. This Symantec product may contain third party software for which Symantec is required to provide attribution to the third party (Third Party Programs). Some of the Third Party Programs are available under open source or free software licenses. The License Agreement accompanying the Software does not alter any rights or obligations you may have under those open source or free software licenses. See the Third-party Legal Notices document for this product, which is available online or included in the base release media. The product described in this document is distributed under licenses restricting its use, copying, distribution, and decompilation/reverse engineering. No part of this document may be reproduced in any form by any means without prior written authorization of Symantec Corporation and its licensors, if any. THE 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. SYMANTEC CORPORATION SHALL NOT BE LIABLE FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING, PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE INFORMATION CONTAINED IN THIS DOCUMENTATION IS SUBJECT TO CHANGE WITHOUT NOTICE. The Licensed Software and Documentation are deemed to be commercial computer software as defined in FAR 12.212 and subject to restricted rights as defined in FAR Section 52.227-19 "Commercial Computer Software - Restricted Rights" and DFARS 227.7202, "Rights in Commercial Computer Software or Commercial Computer Software Documentation", as applicable, and any successor regulations. Any use, modification, reproduction release, performance, display or disclosure of the Licensed Software and Documentation by the U.S. Government shall be solely in accordance with the terms of this Agreement.
Symantec Corporation 350 Ellis Street Mountain View, CA 94043 http://www.symantec.com
Technical Support
Symantec Technical Support maintains support centers globally. Technical Supports primary role is to respond to specific queries about product features and functionality. The Technical Support group also creates content for our online Knowledge Base. The Technical Support group works collaboratively with the other functional areas within Symantec to answer your questions in a timely fashion. For example, the Technical Support group works with Product Engineering and Symantec Security Response to provide alerting services and virus definition updates. Symantecs support offerings include the following:
A range of support options that give you the flexibility to select the right amount of service for any size organization Telephone and/or Web-based support that provides rapid response and up-to-the-minute information Upgrade assurance that delivers software upgrades Global support purchased on a regional business hours or 24 hours a day, 7 days a week basis Premium service offerings that include Account Management Services
For information about Symantecs support offerings, you can visit our Web site at the following URL: www.symantec.com/business/support/index.jsp All support services will be delivered in accordance with your support agreement and the then-current enterprise technical support policy.
Contacting Technical Support

Customers with a current support agreement may access Technical Support information at the following URL: www.symantec.com/business/support/contact_techsupp_static.jsp Before contacting Technical Support, make sure you have satisfied the system requirements that are listed in your product documentation. Also, you should be at the computer on which the problem occurred, in case it is necessary to replicate the problem. When you contact Technical Support, please have the following information available:
Product release level
Hardware information Available memory, disk space, and NIC information Operating system Version and patch level Network topology Router, gateway, and IP address information Problem description:

Error messages and log files Troubleshooting that was performed before contacting Symantec Recent software configuration changes and network changes
Licensing and registration

If your Symantec product requires registration or a license key, access our technical support Web page at the following URL: www.symantec.com/business/support/
Customer service
Customer service information is available at the following URL: www.symantec.com/business/support/ Customer Service is available to assist with non-technical questions, such as the following types of issues:

Questions regarding product licensing or serialization Product registration updates, such as address or name changes General product information (features, language availability, local dealers) Latest information about product updates and upgrades Information about upgrade assurance and support contracts Information about the Symantec Buying Programs Advice about Symantec's technical support options Nontechnical presales questions Issues that are related to CD-ROMs or manuals
Support agreement resources

If you want to contact Symantec regarding an existing support agreement, please contact the support agreement administration team for your region as follows:
Asia-Pacific and Japan Europe, Middle-East, and Africa North America and Latin America customercare_apac@symantec.com semea@symantec.com supportsolutions@symantec.com
Documentation
Product guides are available on the media in PDF format. Make sure that you are using the current version of the documentation.The document version appears on page 2 of each guide. The latest product documentation is available on the Symantec website. http://www.symantec.com/business/support/overview.jsp?pid=15107 Your feedback on product documentation is important to us. Send suggestions for improvements and reports on errors or omissions. Include the title and document version (located on the second page), and chapter and section titles of the text on which you are reporting. Send feedback to: docs@symantec.com
About Symantec Connect

Symantec Connect is the peer-to-peer technical community site for Symantecs enterprise customers. Participants can connect and share information with other product users, including creating forum posts, articles, videos, downloads, blogs and suggesting ideas, as well as interact with Symantec product teams and Technical Support. Content is rated by the community, and members receive reward points for their contributions. http://www.symantec.com/connect/storage-management
Additional enterprise services

Symantec offers a comprehensive set of services that allow you to maximize your investment in Symantec products and to develop your knowledge, expertise, and global insight, which enable you to manage your business risks proactively. Enterprise services that are available include the following:
Managed Services These services remove the burden of managing and monitoring security devices and events, ensuring rapid response to real threats.
Consulting Services
Symantec Consulting Services provide on-site technical expertise from Symantec and its trusted partners. Symantec Consulting Services offer a variety of prepackaged and customizable options that include assessment, design, implementation, monitoring, and management capabilities. Each is focused on establishing and maintaining the integrity and availability of your IT resources. Education Services provide a full array of technical training, security education, security certification, and awareness communication programs.
Education Services
To access more information about enterprise services, please visit our Web site at the following URL: www.symantec.com/business/services/ Select your country or language from the site index.
Contents
Technical Support ............................................................................................... 4 Chapter 1 Introducing Symantec FileStore ....................................... 21

About FileStore ............................................................................ About FileStore features ................................................................ Simple installation ................................................................. Active/Active Scalable NFS ...................................................... Active/Active CIFS ................................................................. NFS Lock Management (NLM) ................................................... Administration ...................................................................... Storage tiering ...................................................................... High-performance data replication ............................................ Integrated content scanning using Symantec AntiVirus for FileStore ......................................................................... About the core strengths of FileStore ............................................... FileStore key benefits and other applications .................................... High performance scaling and seamless growth ........................... High availability .................................................................... Consolidating and reducing costs of storage ................................ Enabling scale-out compute clusters and heterogeneous sharing of data ........................................................................... FileStore on the Web .................................................................... Using the FileStore product documentation ...................................... 21 22 22 23 23 23 23 24 24 24 25 26 26 27 27 28 29 29
Chapter 2
Creating users based on roles .......................................... 31

About user roles and privileges ....................................................... About the naming requirements for adding new users ........................ About using the FileStore command-line interface ............................. Logging in to the FileStore CLI ........................................................ About accessing the online man pages ............................................. About creating Master, System Administrator, and Storage Administrator users ............................................................... Creating Master, System Administrator, and Storage Administrator users .................................................................................... About the support user .................................................................. 31 32 33 33 40 41 42 45
10
Contents
Configuring the support user account .............................................. 46 Displaying the command history ..................................................... 47
Chapter 3
Displaying and adding nodes to a cluster ...................... 49

About the cluster commands .......................................................... About FileStore installation states and conditions .............................. Displaying the nodes in the cluster .................................................. About adding a new node to the cluster ............................................ Installing the FileStore software onto a new node .............................. Adding a node to the cluster ........................................................... Deleting a node from the cluster ..................................................... Shutting down the cluster nodes ..................................................... Rebooting the nodes in the cluster ................................................... 49 50 52 54 54 56 57 58 59
Chapter 4
Configuring storage ............................................................ 61

About storage provisioning and management ................................... About configuring storage pools ..................................................... Configuring storage pools .............................................................. About configuring disks ................................................................ Configuring disks ......................................................................... About performing local replication initialization ............................... Detaching one or more pools from the FileStore cluster as a detached pool set ................................................................................ Displaying detached pools ............................................................. Attaching a replication storage pool to a FileStore cluster .................... About displaying information for all disk devices ............................... Displaying information for all disk devices associated with nodes in a cluster ............................................................................... Increasing the storage capacity of a LUN .......................................... Formatting/reinitializing a disk ...................................................... Printing WWN information ............................................................ Initiating FileStore host discovery of LUNs ...................................... Importing pools forcefully ............................................................. About I/O fencing ......................................................................... Configuring I/O fencing ................................................................. About quotas for file systems ......................................................... Using quota commands for enabling, disabling, and displaying file system quotas ....................................................................... Using quota commands for setting and displaying file system quotas .................................................................................. About quotas for CIFS home directories ........................................... Using quotas for CIFS home directories ............................................ 62 64 66 69 70 72 74 75 75 76 77 80 81 81 81 82 82 84 87 89 91 96 98
Contents
11
Displaying the quota values for CIFS home directories ...................... About iSCSI ............................................................................... Configuring the iSCSI initiator ................................................ Configuring the iSCSI initiator name ........................................ Configuring the iSCSI device .................................................. Configuring discovery on iSCSI ............................................... About configuring the iSCSI targets ............................................... Configuring the iSCSI targets ....................................................... About data archive and retention (DAR) .......................................... How DAR interacts with other FileStore applications ........................ Configuring data archive and retention ..........................................
105 107 108 109 110 111 114 116 119 121 123
Chapter 5
Configuring Symantec FileStore network settings .......................................................................... 127

About network mode commands ................................................... Displaying the network configuration and statistics .......................... About bonding Ethernet interfaces ................................................ Bonding Ethernet interfaces ......................................................... About DNS ................................................................................ Configuring DNS settings ............................................................. About IP commands .................................................................... About configuring IP addresses ..................................................... Configuring IP addresses ............................................................. About configuring Ethernet interfaces ........................................... Displaying current Ethernet interfaces and states ............................ Configuring Ethernet interfaces .................................................... About configuring routing tables ................................................... Configuring routing tables ........................................................... About LDAP .............................................................................. Before configuring LDAP settings .................................................. About configuring LDAP server settings ......................................... Configuring LDAP server settings .................................................. About administering FileStore cluster's LDAP client ......................... Administering the FileStore cluster's LDAP client ............................ About NIS ................................................................................. Configuring the NIS-related commands .......................................... About NSS ................................................................................. Configuring NSS lookup order ...................................................... About VLAN interfaces ................................................................ Configuring VLAN interfaces ........................................................ 128 129 130 132 133 135 137 137 139 143 144 145 146 148 151 151 152 154 158 159 160 161 163 164 165 166
12
Contents
Chapter 6
Configuring your NFS server ........................................... 169

About NFS server commands ........................................................ Accessing the NFS server ............................................................. Displaying NFS statistics ............................................................. Displaying file systems and snapshots that can be exported ............... 169 170 172 173
Chapter 7
Creating and maintaining NFS shares
......................... 175 175 176 177 181 184 184
About NFS file sharing ................................................................ Displaying exported directories ..................................................... Adding an NFS share .................................................................. Sharing directories using CIFS and NFS protocols ............................ Exporting an NFS snapshot .......................................................... Unexporting a directory or deleting NFS options ..............................
Chapter 8
Creating and maintaining file systems
........................ 187 188 191 191 192 195 197 198 199 201 202 202 204 204 205 206 208 209 211 213 215 215 217 219 220 221 221
About creating and maintaining file systems ................................... Listing all file systems and associated information ........................... About creating file systems .......................................................... Creating a file system ................................................................. Adding or removing a mirror to a file system ................................... Configuring FastResync for a file system ........................................ Disabling the FastResync option for a file system ............................. Increasing the size of a file system ................................................. Decreasing the size of a file system ................................................ Checking and repairing a file system .............................................. Changing the status of a file system ............................................... Defragmenting a file system ......................................................... Destroying a file system .............................................................. About snapshots ........................................................................ Creating snapshots ............................................................... Displaying snapshots ............................................................ Configuring snapshots .......................................................... About snapshot schedules ...................................................... Creating snapshot schedules .................................................. Displaying snapshot schedules ................................................ Configuring snapshot schedules .............................................. About instant rollbacks ............................................................... Creating a FileStore space-optimized rollback ............................ Creating a full-sized rollback .................................................. Listing FileStore instant rollbacks ........................................... Restoring a file system from an instant rollback .........................
Contents
13
Refreshing an instant rollback from a file system ....................... Making an instant rollback go online ........................................ Making an instant rollback go offline ....................................... Destroying an instant rollback ................................................ Creating a shared cache object for a FileStore instant rollback ........................................................................ Listing cache objects for a FileStore instant rollback ................... Destroying a cache object of a FileStore instant rollback .............. About setting up file system alerts for file system usage .................... Setting file system alerts ....................................................... Unsetting file system alerts .................................................... Displaying file system alerts ................................................... About the Partition Secure Notification (PSN) feature ....................... Enabling the Partition Secure Notification (PSN) feature ............. Disabling the Partition Secure Notification (PSN) feature ............. Listing the online file systems that have the Partition Secure Notification (PSN) feature enabled .....................................
222 223 223 224 225 226 227 227 227 229 229 230 231 231 232
Chapter 9
Using Symantec FileStore as a CIFS server .................. 233

About configuring FileStore for CIFS .............................................. About configuring CIFS for standalone mode ................................... Configuring CIFS server status for standalone mode ......................... About configuring CIFS for NT domain mode ................................... Configuring CIFS for the NT domain mode ...................................... About leaving an NT domain ........................................................ Changing NT domain settings ....................................................... Changing security settings ........................................................... Changing security settings after the CIFS server is stopped ................ About Active Directory (AD) ......................................................... Configuring entries for NTP for authenticating to Active Directory (AD) ............................................................... Configuring entries for FileStore DNS for authenticating to Active Directory (AD) ............................................................... Joining FileStore to Active Directory (AD) ................................. Verifying that FileStore has joined Active Directory (AD) successfully ................................................................... About configuring CIFS for Active Directory (AD) domain mode .......... Configuring CIFS for the AD domain mode ................................ Using multi-domain controller support in CIFS .......................... About leaving an AD domain .................................................. Changing domain settings for AD domain mode ......................... Removing the AD interface .................................................... 234 236 237 240 242 245 245 247 247 247 248 248 251 253 253 255 258 258 259 262
14
Contents
About setting NTLM .................................................................... Setting NTLM ............................................................................ About setting trusted domains ...................................................... Allowing trusted domains access to CIFS when setting an LDAP IDMAP backend to rid ..................................................... Allowing trusted domains access to CIFS when setting an LDAP IDMAP backend to ldap ................................................... Allowing trusted domains access to CIF when setting an LDAP IDMAP backend to hash ................................................... About configuring Windows Active Directory as an LDAP IDMAP backend for FileStore for CIFS .......................................... Configuring the Active Directory schema with CIFS-schema extensions ..................................................................... Configuring LDAP as an IDMAP backend using the FileStore CLI ............................................................................... Configuring the CIFS server with the LDAP backend ................... Setting Active Directory trusted domains .................................. About storing account information ................................................ Storing user and group accounts ................................................... About reconfiguring the CIFS service ............................................. Reconfiguring the CIFS service ..................................................... About managing CIFS shares ........................................................ About the CIFS export options ................................................ Setting share properties ........................................................ Displaying CIFS share properties ............................................. Allowing specified users and groups access to the CIFS share ............................................................................ Denying specified users and groups access to the CIFS share ............................................................................ Modifying an existing CIFS share ............................................ Modifying an existing CIFS share with different CIFS options ......................................................................... Exporting a CIFS snapshot ..................................................... Deleting a CIFS share ............................................................ Sharing file systems using CIFS and NFS protocols ........................... About mapping user names for CIFS/NFS sharing ............................ About load balancing for the normal clustering mode ........................ About load balancing for the ctdb clustering mode ........................... Splitting a CIFS share .................................................................. About managing home directories ................................................. Setting the home directory file systems .................................... Setting up home directories .................................................... Displaying home directory usage information ............................
262 264 265 265 266 267 268 269 274 274 275 276 278 279 280 282 284 286 288 289 290 291 292 292 293 294 297 298 300 300 302 303 305 307
Contents
15
Deleting home directories and disabling creation of home directories ..................................................................... About ctdb clustering modes ........................................................ Exporting a directory as a CIFS share ............................................ Exporting the same file system/directory as a different CIFS share .................................................................................. About switching the clustering mode ............................................. Switching from normal to ctdb clustering mode ......................... Switching from ctdb to normal clustering mode ......................... About migrating CIFS shares and home directories ........................... Migrating CIFS shares and home directories from normal to ctdb clustering mode ............................................................. Migrating CIFS shares and home directories from ctdb to normal clustering mode ............................................................. Setting the aio_fork option ........................................................... Setting the netbios aliases for the CIFS server .................................. About managing local users and groups .......................................... Creating a local CIFS user ...................................................... About configuring local groups ............................................... Configuring a local group .......................................................
308 309 310 312 313 313 316 317 319 321 324 325 326 327 329 330
Chapter 10
Configuring your FTP server ............................................ 333

About FTP ................................................................................. Displaying FTP server ................................................................. About FTP server commands ........................................................ Using the FTP server commands ................................................... About FTP set commands ............................................................. Using the FTP set commands ........................................................ Implementing all of the FTP> set command changes ........................ About FTP session commands ....................................................... Using the FTP session commands .................................................. Using the FTP logupload command ................................................ About FTP local user commands .................................................... Using the FTP local user commands ............................................... About FTP local user set commands ............................................... Using the FTP local user set commands .......................................... 333 335 335 336 337 341 345 346 346 348 348 350 351 353
Chapter 11
Configuring your HTTP server ......................................... 359

About configuring your HTTP server for accessing FileStore data ................................................................................... 359 About using the HTTP server commands ........................................ 360 Starting the HTTP server ....................................................... 360
16
Contents
Stopping the HTTP server ...................................................... Displaying the status for the HTTP server ................................. About HTTP set commands .......................................................... Displaying the current HTTP sessions on each node ................... Setting the minimum number of idle threads for handling request spikes ........................................................................... Setting the maximum number of idle threads for handling request spikes ........................................................................... Setting the maximum number of threads to be created ................ Setting the initial number of server threads .............................. Setting the maximum number of threads in each server process ......................................................................... Displaying the list of all configurable HTTP options and their values .......................................................................... About HTTP alias commands ........................................................ Adding a mapping from a virtualPath to a realPath ..................... Deleting a mapping that is visible to clients as a virtualPath ......... Displaying all the aliases configured on the server ...................... About HTTP document root mapping commands .............................. Setting the root directory for the HTTP server ........................... Displaying the current root directory for the HTTP server ...........
361 361 361 363 363 363 364 364 364 365 365 366 367 367 367 368 368
Chapter 12
Configuring event notifications and audit logs ........... 369

About configuring event notifications and audit logs ........................ About severity levels and filters .................................................... About email groups ..................................................................... Configuring an email group .......................................................... About syslog event logging ........................................................... Configuring a syslog server .......................................................... Displaying events on the console ................................................... About SNMP notifications ............................................................ Configuring an SNMP management server ...................................... Configuring events for event reporting ........................................... Exporting events in syslog format to a given URL ............................. About audit logs ......................................................................... Configuring audit logs ................................................................. Disabling the audit log for a file system .......................................... 370 371 371 373 378 379 381 381 382 385 386 387 389 391
Chapter 13
Configuring backup ........................................................... 393

About backup ............................................................................ 394 About NetBackup ....................................................................... 395 About the NetBackup snapshot client ............................................. 396
Contents
17
About NetBackup snapshot methods .............................................. About NetBackup instant recovery ................................................ About Fibre Transport ................................................................. About SAN clients ...................................................................... About FT media servers ............................................................... About the FT Service Manager ...................................................... About zoning the SAN for Fibre Transport ...................................... About HBAs for SAN clients and FT media servers ............................ About connecting the fiber for SAN Client ....................................... Adding a NetBackup master server to work with FileStore ................. Configuring or changing the virtual IP address used by NetBackup and NDMP data server installation .......................................... Configuring the virtual name of NetBackup ..................................... About Network Data Management Protocol ..................................... About NDMP supported configurations .................................... About the NDMP policies ....................................................... Configuring the NDMP policies ............................................... Displaying all NDMP policies .................................................. About retrieving the NDMP data ............................................. Retrieving the NDMP data ...................................................... Restoring the default NDMP policies ........................................ About backup configurations ........................................................ Configuring backup .................................................................... Configuring backups using NetBackup or other third-party backup applications ........................................................................
396 397 397 397 398 398 398 399 399 400 402 403 403 405 406 407 412 413 414 416 417 418 420
Chapter 14
Configuring Symantec FileStore Dynamic Storage Tiering ............................................................................ 421

About FileStore Dynamic Storage Tiering (DST) ............................... How FileStore uses Dynamic Storage Tiering ................................... About policies ............................................................................ About adding tiers to file systems .................................................. Adding tiers to a file system ......................................................... Removing a tier from a file system ................................................. About configuring a mirror on the tier of a file system ...................... Configuring a mirror to a tier of a file system .................................. Listing all of the files on the specified tier ....................................... Displaying a list of DST file systems ............................................... Displaying the tier location of a specified file ................................... About configuring the policy of each tiered file system ...................... Configuring the policy of each tiered file system .............................. Relocating a file or directory of a tiered file system ........................... 422 425 426 426 427 428 429 429 431 432 432 432 434 438
18
Contents
About configuring schedules for all tiered file systems ...................... Configuring schedules for all tiered file systems ............................... Displaying files that will be moved and/or pruned by running a policy ................................................................................. Allowing metadata information on the file system to be written on the secondary tier ................................................................. Restricting metadata information to the primary tier only .................
438 439 440 441 442
Chapter 15
Configuring system information .................................... 443

About system commands ............................................................. About setting the clock commands ................................................ Setting the clock commands ......................................................... About configuring the locally saved configuration files ..................... Configuring the locally saved configuration files .............................. Using the more command ............................................................ About coordinating cluster nodes to work with NTP servers ............... Coordinating cluster nodes to work with NTP servers ........................ Displaying the system statistics .................................................... Using the swap command ............................................................ About the option commands ......................................................... Using the option commands ......................................................... 443 444 445 448 449 453 453 454 455 456 457 459
Chapter 16
Upgrading Symantec FileStore ....................................... 465

About upgrading patches or drivers ............................................... Displaying the current version of FileStore ..................................... About installing patches .............................................................. About types of patches ................................................................ Installing patches ....................................................................... Uninstalling patches ................................................................... Synchronizing software upgrades on a node .................................... Uninstalling driver updates .......................................................... 465 467 468 469 470 471 472 472
Chapter 17
Using Symantec AntiVirus for FileStore ....................... 475

About Symantec AntiVirus for FileStore ........................................ About Symantec AntiVirus for FileStore licensing ............................ About Symantec AntiVirus for FileStore commands .......................... Displaying Symantec AntiVirus for FileStore configurations .............. About configuring Symantec AntiVirus for FileStore on all the nodes in the cluster ....................................................................... Configuring Symantec AntiVirus for FileStore on the cluster's nodes ................................................................................. 476 477 477 478 479 480
Contents
19
About configuring Auto-Protect on FileStore file systems .................. Configuring Auto-Protect on FileStore file systems ........................... About excluding file extensions ..................................................... Configuring file extensions for the Symantec AntiVirus for FileStore configuration file ................................................................. About Symantec AntiVirus for FileStore LiveUpdate ......................... Using Symantec AntiVirus for FileStore with LiveUpdate .................. About using Symantec AntiVirus for FileStore quarantine commands .......................................................................... Using Symantec AntiVirus for FileStore quarantine commands .......... Setting the Symantec AntiVirus for FileStore action policy ................ About using Symantec AntiVirus for FileStore manual scan commands .......................................................................... Using Symantec AntiVirus for FileStore manual scan commands .......................................................................... About scheduling a Symantec AntiVirus for FileStore scan job ............ Scheduling a Symantec AntiVirus for FileStore scan job ....................
481 482 482 483 484 486 490 491 493 494 495 496 498
Chapter 18
Troubleshooting ................................................................. 503

About troubleshooting commands ................................................. Setting the CIFS log level ............................................................. Retrieving and sending debugging information ................................ Updating FileStore GUI-related operations ..................................... About the iostat command ........................................................... Generating CPU and device utilization reports ................................. Displaying license information for the cluster ................................. About excluding the PCI ID prior to the FileStore installation ............ Excluding the PCI IDs from the cluster ........................................... Testing network connectivity ....................................................... About the services command ........................................................ Using the services command ........................................................ Using the support login ............................................................... About network traffic details ........................................................ Exporting and displaying the network traffic details ......................... Accessing processor activity ......................................................... Using the traceroute command ..................................................... Recovering from a non-graceful shutdown ...................................... 504 505 506 507 507 508 509 510 511 513 513 515 517 517 518 519 520 521
Glossary ............................................................................................................. 523 Index ................................................................................................................... 527
20
Contents
Chapter
Introducing Symantec FileStore

This chapter includes the following topics:

About FileStore About FileStore features About the core strengths of FileStore FileStore key benefits and other applications FileStore on the Web Using the FileStore product documentation
About FileStore
FileStore was formerly known as Storage Foundation Scalable File Server. FileStore is a highly-scalable and highly-available clustered Network Attached Storage (NAS) software appliance. Based on Storage Foundation Cluster File System technology, FileStore is a complete solution for multi-protocol file serving. FileStore provides an open storage gateway model, including a highly- available and scalable Network File System (NFS), CIFS, and FTP file serving platform and an easy-to-use administrative interface. The product includes the following key features:

Backup operations using both NDMP and/or the built-in NetBackup client Active/Active CIFS, including integration with Active Directory operations Simple administration through a single GUI and/or CLI interface
22
Introducing Symantec FileStore About FileStore features
Active/Active shared data NFS sharing including shared read/write and LDAP/NIS support Simple administration of Fibre Channel Host Bus Adapters (HBAs), file systems, disks, snapshots, and Dynamic Storage Tiering (DST) SNMP, syslog, and email notification High-speed asynchronous/episode-based replication for content distribution and data mining Multi-protocol sharing of file systems in a highly-scalable and highly-available manner Support for single-node FileStore clusters Create a snapshot schedule that stores the values by minutes, hour, day-of-the-month, month, and day-of-the-week along with the name of the file system Seamless upgrade and patch management Support information Online man pages
The components of FileStore include a security-hardened, custom-install SLES 10 SP3 operating system, core Storage Foundation services including Cluster File System, and the FileStore software platform. These components are provided on a single DVD or DVD ISO image.
About FileStore features

FileStore is designed to provide a full-suite of NAS features, in addition to class-leading performance and scalability. A partial list of these features is discussed in the following sections.
Simple installation
A single node in the cluster is booted from a DVD containing the operating system image, core Storage Foundation, and FileStore modules. While the node boots, the other nodes are defined using IP addresses. After you install FileStore and the first node is up and running, the rest of the cluster nodes are automatically installed with all necessary components. The key services are then automatically started to allow the cluster to begin discovering storage and creating file shares.
23
Active/Active Scalable NFS

With FileStore, all nodes in the cluster can serve the same NFS shares as both read and write. This creates very high aggregated throughput rates, because you can use sum of the bandwidth of all nodes. Cache-coherency is maintained throughout the cluster.
Active/Active CIFS
CIFS is active on all nodes within the FileStore cluster. The specific shares are read/write on the node they reside on, but can failover to any other node in the cluster. FileStore supports CIFS home directory shares.
NFS Lock Management (NLM)

The NFS Lock Management (NLM) module allows a customer to use NFS advisory client locking in parallel with core SFCFS global lock management. The module consists of failing over the locks among FileStore nodes as well as forwarding all NFS client lock requests to a single NFS lock master. The result is that no data corruption occurs if a user or application needs to use NFS client locking with an FileStore cluster.
Administration
FileStore contains a role-based administration model consisting of the following key roles:

Storage Master System
These roles are consistent with the operational roles in many data centers. For each role, the administrator uses a simple menu-driven text interface. This interface provides a single point of administration for the entire cluster. A user logs in as one of those roles on one of the nodes in the cluster and runs commands that perform the same tasks on all nodes in the cluster. You do not need to have any knowledge of the Veritas Storage Foundation technology to install or administer an FileStore cluster. If you are currently familiar with core SFCFS or Storage Foundation in general, you will be familiar with the basic management concepts.
24
Storage tiering
FileStore's built-in Dynamic Storage Tiering (DST) feature can reduce the cost of storage by moving data to lower cost storage. FileStore storage tiering also facilitates the moving of data between different drive architectures. DST lets you do the following:
Create each file in its optimal storage tier, based on pre-defined rules and policies. Relocate files between storage tiers automatically as optimal storage changes, to take advantage of storage economies. Prune files on secondary tiers automatically as files age and are no longer needed. Retain original file access paths to minimize operational disruption, for applications, backup procedures, and other custom scripts. Handle millions of files that are typical in large data centers. Automate these features quickly and accurately.
High-performance data replication

Included as a standard feature in the Enterprise Edition of FileStore and optional on the Standard Edition, FileStore Replication provides for high-performance content distribution across multiple clusters. FileStore Replication is asynchronous (sometimes called episodic) and provides for file-based replication between clusters, together with the advantage of being able to only transfer blocks within specific files that have changed since the last update. With FileStore Replication, the destination file system can be on-line for reads, and updates to that destination can be as frequent as every fifteen minutes. FileStore Replication is ideal for content distribution, or for creating hot-standby replicas of a production environment.
Integrated content scanning using Symantec AntiVirus for FileStore

New to FileStore is the ability for customers to use Symantec AntiVirus for FileStore. Leveraging content-scanning and anti-virus technology similar to that found in the Symantec Endpoint Protection range of products, this feature allows for scheduled and real-time (on-demand) scanning of files and other data contained within the FileStore cluster. When conducted in real-time, this content-scanning can be used with multiple file access protocols, including CIFS, NFS, FTP, and HTTP. Files can be automatically quarantined and regular virus definition updates can be obtained by way of the standard Symantec LiveUpdate service.
Introducing Symantec FileStore About the core strengths of FileStore
25
About the core strengths of FileStore

FileStore leverages all the capabilities and strengths of the Storage Foundation family of products. FileStore contains all the key features of Storage Foundation Cluster File System 5.0 MP4 including:

Dynamic Multipathing (DMP) Cluster Volume Manager Cluster File System (CFS) Veritas Cluster Server (VCS) Dynamic Storage Tiering (DST) I/O Fencing
DMP provides load balancing policies and tight integration with array vendors to provide in-depth failure detection and path failover logic. DMP is compatible with more hardware than any other similar product, and is a standard component within the FileStore product. Cluster Volume Manager provides a cluster-wide consistent virtualization layer that leverages all the strengths of the underlying Veritas Volume Manager (VxVM) technology including online re-layout and resizing of volumes, and online array migrations. You can mirror your FileStore file systems across separate physical frames to ensure maximum availability on the storage tier. This technique seamlessly adds or removes new storage, whether single drives or entire arrays. Cluster File System complies with the Portable Operating System Interface (POSIX) standard. It also provides full cache consistency and global lock management at a file or sub-file level. CFS lets all nodes in the cluster perform metadata or data transactions. This allows linear scalability in terms of NFS operations per second. VCS monitors communication, and failover for all nodes in the cluster and their associated critical resources. This includes virtual IP addressing failover for all client connections regardless of the client protocol. DST dynamically and transparently moves files to different storage tiers to respond to changing business needs. DST is used in Symantec FileStore as FileStore Storage Tiering. I/O fencing further helps to guarantee data integrity in the event of a multiple network failure by using the FileStore storage to ensure that cluster membership can be determined correctly. This virtually eliminates the chance of a cluster split-brain from occurring.
26
Introducing Symantec FileStore FileStore key benefits and other applications
FileStore key benefits and other applications

FileStore can be used with any application that requires the sharing of files using the NFS v3, CIFS, or FTP protocol. Use-cases such as home directories or decision support applications that require sequential shared access, Web pages, and applications are all ideal for FileStore. FileStore is also applicable when you want general purpose, high-throughput scale-out processing for your data, together with enterprise-class highly available cluster functionality.
High performance scaling and seamless growth

FileStore lets you scale storage and processing independently and seamlessly, online. Because an application may need to scale either storage or processing, or both, this capability gives you a lot of flexibility. FileStore automates the installation of new nodes into the running cluster, configures those nodes, and adds the nodes' capacity into the processing tier. FileStore can scale from 1 to 16 nodes with near linear performance scaling. You can add processing one node at a time, rather than buying a large, expensive independent appliance. A storage administrator can configure a new array or even add new LUNs from an existing array into the FileStore cluster. FileStore can then scan the storage, automatically see the new LUNs and place them under FileStore control for use in the cluster. All of this is performed online. At the storage end, resizing of existing file systems can be performed online with no interruption of service. A simple command is used to both add space to an existing file system and to also reduce (dynamically shrink) the amount of free space in a specified file system. The product provides nearly linear scaling in terms of NFS operations per second and total I/O throughput. Figure 1-1 depicts this scaling capability.
27
Figure 1-1
Example of near-linear performance scaling with FileStore
When using 16-node clusters, extremely high throughput performance numbers can be obtained. This is due to the benefits of near linear FileStore cluster scalability.
High availability
FileStore has an always on" file service that provides zero interruption of file services for company critical data. The loss of single or even multiple nodes does not interrupt I/O operations on the client tier. This is in contrast to the traditional active/passive failover paradigm. Further, with FileStore's modular N-to-N approach to clustered NAS, any node can act as a failover for any other node. The FileStore architecture provides transparent failover for other key services such as NFS lock state, CIFS and FTP daemons, reporting, logging, and backup/restore operations. The console service that provides access to the centralized menu-driven interface is automatically failed over to another node. The installation service is also highly available and can seamlessly recover from the initially installed node failing during the installation of the remaining nodes in the cluster. The use of Veritas Cluster Server technology and software within FileStore is key to the ability of FileStore to provide best-of-breed high availability, in addition to class-leading scale-out performance.
Consolidating and reducing costs of storage

The value of consolidating several independent islands of NAS appliances into fewer, larger shared pools has many cost benefits.
28
A typical enterprise uses 30-40% of its storage. This low storage utilization rate results in excessive spending on new storage when there is more than adequate free space in the data center. With FileStore, you can group storage assets into fewer, larger shared pools. This increases the use of backend LUNs and overall storage. FileStore also has built-in, pre-configured heterogeneous storage tiering. This lets you use different types of storage in a primary and secondary tier configuration. Using simple policies, data can be transparently moved from the primary storage tier to the secondary tier. This is ideal when mixing drive types and architectures such as high-speed SAS drives with cheaper storage, such as SATA-based drives. Furthermore, data can be stored initially on the secondary tier and then promoted to the primary tier dynamically based on a pattern of I/O. This creates an optimal scenario when you use Solid State Disks (SSDs) because there will often be a significant change between the amount of SSD storage available, and amount of other storage availability, such as SATA drives. Data and files that are promoted to the primary tier are transferred back to the secondary tier in accordance with the configured access time policy. All of this results in substantially increased efficiency, and it can save you money because you make better use of the storage you already have.
Enabling scale-out compute clusters and heterogeneous sharing of data

The trend toward scale-out, or grid computing continues to gain pace. There are significant performance and cost advantages of moving applications away from large UNIX Symmetrical Multi-Processing (SMP) or mainframe environments and towards a farm of commodity computer servers running a distributed application. One of the key inhibitors to scale-out computing is the requirement to provide a shared storage infrastructure for the compute nodes, and enable you to share heterogeneously as well as scale up as performance requires. FileStore solves both of these issues by providing a highly scalable and shared storage platform at the storage tier and by facilitating heterogeneous sharing on the compute tier. FileStore can provide the performance and availability you need for a large-scale NFS compute and storage tier. It provides enough throughput and seamless failover for this type of architecture whether a few dozen compute nodes, or scaling to several hundred nodes.
Introducing Symantec FileStore FileStore on the Web
29
FileStore on the Web

For comprehensive, up-to-date information about FileStore, visit the Symantec Web site: http://www.symantec.com/business/support/overview.jsp?pid=55079
Using the FileStore product documentation

FileStore product documentation is available in PDF format on the FileStore installation DVD in the /docs directory:

Symantec FileStore Web GUI Administrators Guide (sfs_admin_gui.pdf) Symantec FileStore Command-Line Administrators Guide (sfs_admin.pdf) Symantec FileStore Installation Guide (sfs_install.pdf) Symantec FileStore Replication Guide (sfs_replication.pdf) Symantec FileStore Release Notes (sfs_relnotes.pdf)
Find additional information at this location: http://www.symantec.com/business/support/overview.jsp?pid=55079
30
Introducing Symantec FileStore Using the FileStore product documentation
Chapter
Creating users based on roles


About user roles and privileges About the naming requirements for adding new users About using the FileStore command-line interface Logging in to the FileStore CLI About accessing the online man pages About creating Master, System Administrator, and Storage Administrator users Creating Master, System Administrator, and Storage Administrator users About the support user Configuring the support user account Displaying the command history
About user roles and privileges

Your privileges within Symantec FileStore (FileStore) are based on what user role (Master, System Administrator, or Storage Administrator) you have been assigned. The following table provides an overview of the user roles within FileStore.
32
Creating users based on roles About the naming requirements for adding new users
Table 2-1 User role

Master
User roles within FileStore Description

Masters are responsible for adding or deleting users, displaying users, and managing passwords. Only the Masters can add or delete other administrators. System Administrators are responsible for configuring and maintaining the file system, NFS sharing, networking, clustering, setting the current date/time, and creating reports. Storage Administrators are responsible for provisioning storage and exporting and reviewing reports.
System Administrator
Storage Administrator
The Support account is reserved for Technical Support use only, and it cannot be created by administrators. See Using the support login on page 517.
About the naming requirements for adding new users

The following table provides the naming requirements for adding new FileStore users. Table 2-2 Guideline
Starts with
Naming requirements for adding new users Description

Letter or an underscore (_) Must begin with an alphabetic character and the rest of the string should be from the following POSIX portable character set: ([A-Za-z_][A-Za-z0-9_-.]*[A-Za-z0-9_-.$]).
Length
Can be up to 31 characters. If user names are greater than 31 characters, you will receive the error, "Invalid user name." FileStore CLI commands are case-insensitive (for example, the user command is the same as the USER command). However, user-provided variables are case-sensitive (for example, the username Master1 is not the same as the username MASTER1). Hyphens (-) and underscores (_) are allowed.
Case
Can contain
Creating users based on roles About using the FileStore command-line interface
33
Table 2-2 Guideline

Valid syntax
Naming requirements for adding new users (continued) Description

Valid user names include:

Name: a.b a_b ______-
See Creating Master, System Administrator, and Storage Administrator users on page 42.
About using the FileStore command-line interface

You can enter FileStore commands on the system console or from any host that can access FileStore through a session using Secure Socket Shell (SSH) . FileStore provides the following features to help you when you enter commands on the command line:

Command-line help by typing a command and then a question mark (?) Command-line manual (man) pages by typing man and the name of the command you are trying to find Conventions used in the FileStore online command-line man pages Description
Indicates you must choose one of elements on either side of the pipe. Indicates that the element inside the brackets is optional. Indicates that the element inside the braces is part of a group. Indicates a variable for which you need to supply a value. Variables are indicated in italics in the man pages.
Table 2-3 Symbol

| (pipe) [ ] (brackets) { } (braces) <>
Logging in to the FileStore CLI

When you first log in to the FileStore CLI, use the default username/password of master/master. After you have logged in successfully, change your password.
34
Creating users based on roles Logging in to the FileStore CLI
Note: Changing the default password is important for system security. If you do not change the default password, a warning message appears the next time you log in. See Creating Master, System Administrator, and Storage Administrator users on page 42. By default, the initial password for any user is the same as the username. For example, if you logged in as user1, your default password would also be user1. To use any of the CLI commands, first log in by using the user role you have been assigned. Then enter the correct mode. These two steps must be performed before you can use any of the commands. Note: The End User License Agreement (EULA) is displayed the first time you log in to the FileStore CLI. To log in to the FileStore CLI
1 2
Log in to FileStore using the appropriate user role, System Admin, Storage Admin, or Master. Enter the name of the mode you want to enter. For example, to enter the admin mode, you would enter the following:
admin
You can tell you are in the admin mode because you will see the following:
Admin>
The following tables describe all the available modes, commands associated with that mode, and what roles to use depending on which operation you are performing. Table 2-4 Admin mode commands System Admin
X X
Admin mode commands

passwd show supportuser user
Storage Admin
X X
Master
X X X X
35
Table 2-5
Antivirus mode commands System Admin

X X X X X X X X X
Antivirus mode commands

autoprotect excludeextension job liveupdate quarantine scanaction scan service show
Storage Admin
Master
X X X X X X X X X
Table 2-6
Backup mode commands System Admin

X X X X X X X X
Backup mode commands

ndmp netbackup show start status stop virtual-ip virtual-name
Storage Admin
Master
X X X X X X X X
Table 2-7
CIFS mode commands System Admin

X
CIFS mode commands

homedir
Storage Admin
Master
X
36
Table 2-7
CIFS mode commands (continued) System Admin

X X X X X X
CIFS mode commands

local server set share show split
Storage Admin
Master
X X X X X X
Table 2-8
Cluster mode commands System Admin

X X X X X
Cluster mode commands

add delete reboot show shutdown
Storage Admin
Master
X X X X X
Table 2-9
FTP mode commands System Admin

X X X X X X
FTP mode commands

local logupload server session set show
Storage Admin
Master
X X X X X X
37
Table 2-10
History mode commands System Admin

X
History mode commands

history
Storage Admin
X
Master
X
Table 2-11
Network mode commands System Admin

X X X X X X X X X
Network mode commands

bond dns ip ldap nis nsswitch ping show vlan
Storage Admin
Master
X X X X X X X X X
Table 2-12
NFS mode commands System Admin

X X X X
NFS mode commands

server share show fs stat
Storage Admin
Master
X X X X
Table 2-13
Report mode commands System Admin

X X
Report mode commands

audit email
Storage Admin
Master
X X
38
Table 2-13
Report mode commands (continued) System Admin

X X X X X X X
Report mode commands

event exportevents showevents snmp syslog
Storage Admin
Master
X X X X X
Table 2-14
Storage mode commands System Admin

X X X X X X X X X X X X X X X X X X X X
Storage mode commands

dar disk grow disk list disk format fencing fs hba iscsi pool quota rollback scanbus snapshot tier
Storage Admin
Master
X X X X X X X X X X X X X X
39
Table 2-15
Support mode commands System Admin Storage Admin Master

X X X X X X X X X
Support mode commands

debuginfo gui iostat license pciexclusion services tethereal top traceroute
Table 2-16
System mode commands System Admin

X X X X X X X
System mode commands

clock config more ntp option stat swap
Storage Admin
Master
X X X X X X X
Table 2-17
Upgrade mode commands System Admin

X X
Upgrade mode commands

patch show
Storage Admin
Master
X X
40
Creating users based on roles About accessing the online man pages
About accessing the online man pages

You access the online man pages by typing man name_of_command at the command line. The example shows the result of entering the Network> man ldap command.
Network> man ldap NAME ldap - configure LDAP client for authentication SYNOPSIS ldap ldap ldap ldap
enable disable show [users|groups|netgroups] set {server|port|basedn|binddn|ssl|rootbinddn|users-basedn| groups-basedn|netgroups-basedn|password-hash} value ldap get {server|port|basedn|binddn|ssl|rootbinddn| users-basedn|groups-basedn|netgroups-basedn|password-hash}
You can also type a question mark (?) at the prompt for a list of all the commands that are available for the command mode that you are in. For example, if you are within the admin mode, if you type a question mark (?), you will see a list of the available commands for the admin mode.
sfs> admin ? Entering admin mode... sfs.Admin> exit logout man passwd show supportuser user --return to the previous menus --logout of the current CLI session --display on-line reference manuals --change the administrator password --show the administrator details --enable or disable the support user --add or delete an administrator
To exit the command mode, enter the following: exit. For example:
sfs.Admin> exit sfs>
To exit the system console, enter the following: logout.
Creating users based on roles About creating Master, System Administrator, and Storage Administrator users
41
For example:
sfs> logout
About creating Master, System Administrator, and Storage Administrator users

The admin> user commands add or delete a user, display user settings, and rename the password. Note: By default, the password of the new user is the same as the username. Table 2-18 Command
user add
Creating users Definition

Creates the different levels of administrator. You must have master privilege. A user can be a Master user who has all the permissions, including add and deleting users. A Storage Administrator has access to only storage commands and is responsible for upgrading the cluster and applying the patches. A System Administrator is responsible for configuring the NFS server and exporting the file system, adding and deleting new nodes to the cluster, and configuring other network parameters such as DNS and NIS. See Creating Master, System Administrator, and Storage Administrator users on page 42.
passwd
Creates a password. Passwords can be any length. By default, the initial password for any user is the same as the username. For example, if you logged in as user1, your default password would also be user1. You will not be prompted to supply the old password. See Creating Master, System Administrator, and Storage Administrator users on page 42.
show
Displays a list of current users, or you can specify a particular username and display both the username and its associated privilege. See Creating Master, System Administrator, and Storage Administrator users on page 42.
42
Creating users based on roles Creating Master, System Administrator, and Storage Administrator users
Table 2-18 Command

user delete
Creating users (continued) Definition

Deletes a user. See Creating Master, System Administrator, and Storage Administrator users on page 42.
Creating Master, System Administrator, and Storage Administrator users

To create the different levels of administrator, you must have master privilege. To create a Master user
To create a Master user, enter the following:

Admin> user add username master
For example:
Admin> user add master1 master Creating Master: master1 Success: User master1 created successfully
To create a System Administrator user
To create a System Administrator user, enter the following:

Admin> user add username system-admin
For example:
Admin> user add systemadmin1 system-admin Creating System Admin: systemadmin1 Success: User systemadmin1 created successfully
43
To create a Storage Administrator user
To create a Storage Administrator user, enter the following:

Admin> user add username storage-admin
For example:
Admin> user add storageadmin1 storage-admin Creating Storage Admin: storageadmin1 Success: User storageadmin1 created successfully
To change a user's password
To change the password for the current user, enter the following command:
Admin> passwd
You will be prompted to enter the new password for the current user.
To change the password for a user other than the current user, enter the following command:
Admin> passwd [username]
You will be prompted to enter the new password for the user.
44
To display a list of current users
To display the current user, enter the following:

Admin> show [username]
To display a list of all the current users, enter the following:

Admin> show
For example:
Admin> show List of Users ------------master user1 user2
To display the details of the administrator with the username master, enter the following:
Admin> show master Username : master Privileges : Master Admin>
To delete a user from FileStore
If you want to display the list of all the current users prior to deleting a user, enter the following:
Admin> show
To delete a user from FileStore, enter the following:

Admin> user delete username
For example:
Admin> user delete user1 Deleting User: user1 Success: User user1 deleted successfully
Creating users based on roles About the support user
45
About the support user

The supportuser commands are used to enable, disable, or view the status of the support user. Only an administrator logged in as master has the privilege to enable, disable, change the password, or check the status of the support user. You log into the system console and enter the Admin> mode to access the commands. See About using the FileStore command-line interface on page 33. Table 2-19 Command
supportuser enable
Support user commands Definition

Enables the support user for the tracing and debugging of any node. The enable command lets the support user login remotely. See Configuring the support user account on page 46.
supportuser password
Changes the support user password. The password can be changed at any time. See Configuring the support user account on page 46.
supportuser status Checks the status of the support user (whether it is enabled or disabled).
Note: You must have master privilege to use this command.

See Configuring the support user account on page 46. supportuser disable Disables the support user without permanently removing it from the system. By default, the support user is in disable mode when FileStore is installed. See Configuring the support user account on page 46.
46
Creating users based on roles Configuring the support user account
Configuring the support user account

To enable the support user account
If you want to enable the support user, enter the following:

Admin> supportuser enable
For example:
Admin> supportuser enable Enabling support user. support user enabled. Admin>
To change the support user password
If you want to change the support user password, enter the following:
Admin> supportuser password
For example:
Admin> supportuser password Changing password for support. New password: Re-enter new password: Password changed Admin>
To check the support user status
If you want to check the status of the support user, enter the following:
Admin> supportuser status
For example:
Admin> supportuser status support user status : Enabled Admin>
Creating users based on roles Displaying the command history
47
To disable the support user account
If you want to disable the support user, enter the following:

Admin> supportuser disable
For example:
Admin> supportuser disable Disabling support user. support user disabled. Admin>
Displaying the command history

The history command displays the commands that you have executed. You can also view commands executed by another user. You must be logged in to the system to view the command history. See About using the FileStore command-line interface on page 33.
48
Creating users based on roles Displaying the command history
To display command history
To display the command history, enter the following:

SFS> history [username] [number_of_lines] username number_of_lines Displays the command history for a particular user. Displays the number of lines of history you want to view.
For example:
SFS> history master 7 Username : master Privileges : Master Time Status 02-12-2009 11:09 Success 02-12-2009 11:10 Success 02-12-2009 11:19 Success 02-12-2009 11:28 Success 02-12-2009 15:00 SUCCESS 02-12-2009 15:31 Success 02-12-2009 15:49 Success SFS>
Message NFS> server status NFS> server start NFS> server stop NFS> fs show Disk list stats completed Network shows success Network shows success
Command (server status) (server start ) (server stop ) (show fs ) (disk list ) (show ) (show )
The information displayed from using the history command is:

Time Status Message Command Displays the time stamp as MM-DD-YYYY HH:MM Displays the status of the command as Success, Error, or Warning. Displays the command description. Displays the actual commands that were executed by you or another user.
Chapter
Displaying and adding nodes to a cluster


About the cluster commands About FileStore installation states and conditions Displaying the nodes in the cluster About adding a new node to the cluster Installing the FileStore software onto a new node Adding a node to the cluster Deleting a node from the cluster Shutting down the cluster nodes Rebooting the nodes in the cluster
About the cluster commands

This chapter discusses the FileStore cluster commands. You use these commands to add or delete nodes to your cluster. The cluster commands are defined in Table 3-1. To access the commands, log into the administrative console (for master or system-admin) and enter Cluster> mode. See About using the FileStore command-line interface on page 33.
50
Displaying and adding nodes to a cluster About FileStore installation states and conditions
Table 3-1 Commands

cluster> show
Cluster mode commands Definition

Displays the nodes in the FileStore cluster, their states, CPU load, and network load during the past 15 minutes. See Displaying the nodes in the cluster on page 52.
network> ip addr add cluster> add
Installs the FileStore software onto the new node. See Installing the FileStore software onto a new node on page 54. Adds a new node to the FileStore cluster. See Adding a node to the cluster on page 56.
cluster> delete
Deletes a node from the FileStore cluster. See Deleting a node from the cluster on page 57.
cluster> shutdown Shuts down one or all of the nodes in the FileStore cluster. See Shutting down the cluster nodes on page 58. cluster> reboot Reboots a single node or all of the nodes in the FileStore cluster. Use the nodename(s) that is displayed in the show command. See Rebooting the nodes in the cluster on page 59.
About FileStore installation states and conditions

Table 3-2 describes FileStore installation states. Table 3-2 FileStore installation states
Installation state Description

INSTALLING FileStore installation is in progress on the new node. The stage of installation is also shown. FileStore has been successfully installed on this node and the node is ready to be added to the cluster. Node is part of the cluster and FileStore processes are running on it. Node is down and/or FileStore processes are not running on it. Node is leaving the cluster gracefully Node has exited the cluster gracefully
INSTALLED
RUNNING FAULTED LEAVING EXITED
Displaying and adding nodes to a cluster About FileStore installation states and conditions
51
Table 3-2
FileStore installation states (continued)
Installation state Description

UNKNOWN Exact state of the node cannot be determined
Depending on the cluster condition as described in Table 3-3, output for the Cluster> show command changes. Table 3-3 Condition Cluster conditions and states Description
If the node is configured and State displays as FAULTED, and there is no installation state part of the cluster, but the or network statistics. node is powered off. If the node is configured and State displays as FAULTED, and there is no installation state part of the cluster, but the or network statistics. node is physically removed from the cluster. If the node is configured and State changes from LEAVING to EXITED. part of the cluster, but the node is shutdown using the Cluster> shutdown command. If the node is configured and Node gets deleted from the cluster, and the node is shown part of the cluster, and you under the installed node list. issue the Cluster> delete command. If the node is installed, but If the system is powered off, the node displays in the not part of the cluster, and is installed node list for 2-3 minutes, but attempting to add powered off. the node to the cluster will not work, as the system is in a powered-off state. After 2-3 minutes has expired, the node is deleted from the installed node list. If the system is powered on, the node appears in the installed node list. If the node is installed, but Same behavior as above. not part of the cluster, and is physically removed.
52
Displaying and adding nodes to a cluster Displaying the nodes in the cluster
Displaying the nodes in the cluster

You can display all the nodes in the cluster, their states, CPU load, and network load during the past 15 minutes. If you use the Cluster> show currentload option, you can display the CPU and network loads collected from now to the next five seconds.
Displaying and adding nodes to a cluster Displaying the nodes in the cluster
53
To display a list of nodes in the cluster
To display a list of nodes that are part of a cluster, and the systems that are available to add to the cluster, enter the following:
Cluster> show
For nodes already in the cluster, the following is displayed:

Node -----sfs_01 sfs_02 State ------RUNNING RUNNING CPU(15 min) pubeth0(15 min) pubeth1(15 min) % rx(MB/s) tx(MB/s) rx(MB/s) tx(MB/s) ----------- -------- -------- -------- -------1.35 0.00 0.00 0.00 0.00 1.96 0.00 0.00 0.00 0.00
For the nodes not yet added to the cluster, they are displayed with unique identifiers.
Node ---4dd5a565-de6c-4904-aa27-3645cf557119 bafd13c1-536a-411a-b3ab-3e3253006209 State ----INSTALLED 5.0SP2(172.16.113.118) INSTALLING-Stage-4-of-4
Node
Displays the node name if the node has already been added to the cluster. Displays the unique identifier for the node if it has not been added to the cluster. Example: node_01 or 35557d4c-6c05-4718-8691-a2224b621920
State
Displays the state of the node or the installation state of the system along with an IP address of the system if it is installed. See About FileStore installation states and conditions on page 50.
CPU pubeth0 pubeth1
Indicates the CPU load Indicates the network load for the Public Interface 0 Indicates the network load for the Public Interface 1
54
Displaying and adding nodes to a cluster About adding a new node to the cluster
To display the CPU and network loads collected from now to the next five seconds, enter the following:
Cluster> show currentload
Example output:
Node ---sfs_01 sfs_02 sfs_03 State ----RUNNING RUNNING RUNNING CPU(5 sec) % ---------0.26 0.87 10.78 pubeth0(5 sec) pubeth1(5 sec) rx(MB/s) tx(MB/s) rx(MB/s) tx(MB/s) -------- -------- -------- -------0.01 0.00 0.01 0.00 0.01 0.00 0.01 0.00 27.83 12.54 0.01 0.00
About adding a new node to the cluster

After you have installed the first node of the cluster, you need to complete two separate procedures to install additional nodes and add them to the cluster. Procedures to install and add additional nodes:

You first need to install the FileStore software binaries on the node. You then add the node to your existing cluster. After the FileStore software has been installed, the node enters the INSTALLED state. It can then be added to the cluster and become operational.
Note: Before proceeding, make sure that all of the nodes are physically connected to the private and public networks. Software installation can run concurrently on multiple new nodes. See the Symantec FileStore Installation Guide for more information.
Installing the FileStore software onto a new node

To install the FileStore software onto the new node
Log in to the master account through the FileStore console and access the network mode. To log in to the FileStore console:
Use ssh master@consoleipaddr where consoleipaddr is the console IP address.
Displaying and adding nodes to a cluster Installing the FileStore software onto a new node
55
For the password, enter the default password for the master account, master. You can change the password later by using the Admin> password command. Note: Changing the default password is important for system security. If you do not change the default password, a warning message appears the next time you log in.
If the nodes have not been preconfigured, you need to preconfigure them. To preconfigure nodes:
Obtain the IP address ranges, as described in the Symantec FileStore Installation Guide, for the public network interfaces of the nodes to be installed. Add each IP address using the following command:
Network> ip addr add ipaddr netmask type
IP is a protocol that allows addresses to be attached to an Ethernet interface. Each Ethernet interface must have at least one address to use the protocol. Several different addresses can be attached to one Ethernet interface. Add the ipaddr and the netmask. And type is the type of IP address (virtual or physical).
Press F12 (or an equivalent key) for each new node for a network reboot. The FileStore software is automatically installed on all of the nodes.
Enter Cluster> show to display the status of the node installation as it progresses.
Cluster> show
The following are the four stages when installing a node:

INSTALLING (Stage 1 of 4: Installing Linux) INSTALLING (Stage 2 of 4: Copying SFS installation sources) INSTALLING (Stage 3 of 4: First Boot) INSTALLING (Stage 4 of 4: Installing SFS)
The installing state also contains a unique identifier, as in:

Node ---State -----
56
Displaying and adding nodes to a cluster Adding a node to the cluster
4dd5a565-de6c-4904-aa27-3645cf557119 INSTALLED 5.0SP2(172.16.113.118) bafd13c1-536a-411a-b3ab-3e3253006209 INSTALLING-Stage-4-of-4
Adding a node to the cluster

After the FileStore software is installed on a new node, the node is assigned a temporary IP address. The address is displayed in the State field in the output for Cluster> show. For example, the temporary IP address shown above is 172.16.113.118. The temporary IP address is only used to add the node to the cluster. Only the nodes in the INSTALLED state can be added to the cluster. See Installing the FileStore software onto a new node on page 54. Note: This command is not supported in a single-node cluster. The coordinator disks must be visible on the newly added node as a prerequisite for I/O fencing to be configured successfully. Without the coordinator disks, I/O fencing will not load properly and the node will not be able to obtain cluster membership. See About I/O fencing on page 82. If a problem occurs while you are adding a node to a cluster (for example, if the node is temporarily disconnected from the network), do the following to fix the problem: To recover the node:

Power off the node. Use the Cluster > delete nodename command to delete the node from the cluster. Power on the node. Use the Cluster > add nodeip command to add the node to the cluster.
Displaying and adding nodes to a cluster Deleting a node from the cluster
57
To add the new node to the cluster
1 2 3
Log in to FileStore using the master user role. Enter the cluster mode. To add the new node to the cluster, enter the following:
Cluster> add nodeip
where nodeip is the IP address assigned to the INSTALLED node. For example:
Cluster> add 172.16.113.118 Checking ssh communication with 172.16.113.118 ...done Configuring the new node .....done Adding node to the cluster.........done Node added to the cluster New node's name is: sfs_01
Deleting a node from the cluster

This command deletes a node from the cluster. Use the nodename that is displayed in the Cluster> show command. Note: This command is not supported in a single-node cluster. If the deleted node was in the RUNNING state prior to deletion, that node would be assigned an IP address that can be used to add the node back to the cluster. See About adding a new node to the cluster on page 54. If the deleted node was not in the RUNNING state prior to deletion, reboot the deleted node to assign it an IP address which can be used to add the node back into the cluster. You must first reinstall the operating system FileStore software (using the PXE installation) onto the node before adding it to the cluster. Refer to Symantec FileStore Installation Guide. After the node is deleted from the cluster, that node's IP address is free for use by the cluster for new nodes. Note: When using the Cluster> shutdown or Cluster> delete commands, you cannot use unique identifiers for node names; these commands only work with node names.
58
Displaying and adding nodes to a cluster Shutting down the cluster nodes
To delete a node from the cluster
To show the current state of all nodes in the cluster, enter the following:
Cluster> show
To delete a node from a cluster, enter the following:

Cluster> delete nodename
where nodename is the nodename that appeared in the listing from the show command. For example:
Cluster> delete sfs_01 Stopping Cluster processes on sfs_01 ...........done deleting sfs_1's configuration from the cluster .....done Node sfs_1 deleted from the cluster
If you try to delete a node that is unreachable, you will receive the following warning message:
This SFS node is not reachable, you have to re-install the SFS software via PXE boot after deleting it. Do you want to delete it now? (y/n)
Shutting down the cluster nodes

You can shut down a single node or all of the nodes in the cluster. Use the nodename(s) that is displayed in the Cluster> show command. Note: When using the Cluster> shutdown or Cluster> delete commands, you cannot use unique identifiers for node names; these commands only work with node names.
Displaying and adding nodes to a cluster Rebooting the nodes in the cluster
59
To shut down a node or all the nodes in a cluster
To shut down a node, enter the following:

Cluster> shutdown nodename
nodename indicates the name of the node you want to shut down. For example:
Cluster> shutdown sfsfiler_04 Stopping Cluster processes on sfsfiler_04 Sent shutdown command to sfsfiler_04. SSH sessions to sfsfiler_04 may terminate.
To shut down all of the nodes in the cluster, enter the following:
Cluster> shutdown all
Use all as the nodename if you want to shut down all of the nodes in the cluster. For example:
Cluster> shutdown all Stopping Cluster processes on all SSH sessions to all nodes may terminate. Sent shutdown command to sfsfiler_02 Sent shutdown command to sfsfiler_03 Sent shutdown command to sfsfiler_04 Sent shutdown command to sfsfiler_01
Rebooting the nodes in the cluster

You can reboot a single node or all of the nodes in the cluster. Use the nodename(s) that is displayed in the Cluster> show command.
60
Displaying and adding nodes to a cluster Rebooting the nodes in the cluster
To reboot a node
To reboot a node, enter the following:

Cluster> reboot nodename
nodename indicates the name of the node you want to reboot. For example:
Cluster> reboot sfsfiler_04 Stopping Cluster processes on sfsfiler_04 Sent reboot command to sfsfiler_04. SSH sessions to sfsfiler_4 may terminate.
To reboot all of the nodes in the cluster, enter the following:

Cluster> reboot all
Use all as the nodename if you want to reboot all of the nodes in the cluster. For example:
Cluster> reboot all Stopping Cluster processes on all SSH sessions to all nodes may terminate. Sent reboot command to sfsfiler_02 Sent reboot command to sfsfiler_03 Sent reboot command to sfsfiler_04 Sent reboot command to sfsfiler_01
Chapter
Configuring storage

About storage provisioning and management About configuring storage pools Configuring storage pools About configuring disks Configuring disks About performing local replication initialization Detaching one or more pools from the FileStore cluster as a detached pool set Displaying detached pools Attaching a replication storage pool to a FileStore cluster About displaying information for all disk devices Displaying information for all disk devices associated with nodes in a cluster Increasing the storage capacity of a LUN Formatting/reinitializing a disk Printing WWN information Initiating FileStore host discovery of LUNs Importing pools forcefully About I/O fencing Configuring I/O fencing
62
Configuring storage About storage provisioning and management
About quotas for file systems Using quota commands for enabling, disabling, and displaying file system quotas Using quota commands for setting and displaying file system quotas About quotas for CIFS home directories Using quotas for CIFS home directories Displaying the quota values for CIFS home directories About iSCSI About configuring the iSCSI targets Configuring the iSCSI targets About data archive and retention (DAR) How DAR interacts with other FileStore applications Configuring data archive and retention
About storage provisioning and management

Storage provisioning in FileStore focuses on the storage pool, which is comprised of a set of disks. The file system commands accept a set of pools as an argument. For example, creating a file system takes one or more pools, and creates a file system over some or all of the pools. A mirrored file system takes multiple pools as an argument and creates a file system such that each copy of the data resides on a different pool. To provision FileStore storage, verify that the Logical Unit Numbers (LUNS) or meta-LUNS in your physical storage arrays have been zoned for use with the FileStore cluster. The storage array administrator normally allocates and zones this physical storage. Use the FileStore Storage> pool commands to create storage pools using disks (the named LUNS). Each disk can only belong to one storage pool. If you try to add a disk that is already in use, an error message is displayed. With these storage pools, use the Storage> fs commands to create file systems with different layouts (for example mirrored, striped, striped-mirror). The storage commands are defined in Table 4-1.
Configuring storage About storage provisioning and management
63
To access the commands, log into the administrative console (master, system-admin, or storage-admin) and enter the Storage> mode. See About using the FileStore command-line interface on page 33. Table 4-1 Command
disk grow
Storage mode commands Definition

Grows a selected disk if it is resized on the storage array. See Increasing the storage capacity of a LUN on page 80.
disk list
Lists all of the available disks, and identifies which ones you want to assign to which pools. See About displaying information for all disk devices on page 76.
disk format
Formats/reinitializes a disk forcefully to reinstate it. See Formatting/reinitializing a disk on page 81.
dar
Enables file systems for data archive and retention (DAR). See Configuring data archive and retention on page 123.
fencing
Protects the data integrity if the split-brain condition occurs. See About I/O fencing on page 82.
hba
Prints the World Wide Name (WWN) information for all of the nodes in the cluster. See Printing WWN information on page 81.
iscsi
Links data storage facilities. See About iSCSI on page 107.
pool
Configures storage pools. See About configuring storage pools on page 64.
pool adddisk, pool mvdisk, pool rmdisk pool detachset, pool showdetached, pool attachset
Configures the disk(s) in the pool. See About configuring disks on page 69. Configures local replication initialization. See About performing local replication initialization on page 72.
64
Configuring storage About configuring storage pools
Table 4-1 Command

scanbus
Storage mode commands (continued) Definition

Scans all of the SCSI devices connected to all of the nodes in the cluster. See Initiating FileStore host discovery of LUNs on page 81.
quota
Sets a limit on disk quota to restrict certain aspects of the file system usage. See About quotas for file systems on page 87.
About configuring storage pools

Storage provisioning in FileStore focuses on the concept of pools. Pools are more a logical construct rather than an architectural component. Pools are loosely collections of disks. In the FileStore context, a disk is a LUN provisioned from a storage array. Each LUN should be provisioned to all FileStore nodes. Disks must be added to pools prior to use. During the initial configuration, you use the Storage> commands to create storage pools, to discover disks, and to assign them to pools. Disk discovery and pool assignment are done once. FileStore propagates disk information to all cluster nodes. You must first create storage pools that can be used to build file systems on. Disks and pools can be specified in the same command provided the disks are part of an existing storage pool. The pool and disk specified first are allocated space before other pools and disks. If the specified disk is larger than the space allocated, the remainder of the space is still utilized when another file system is created spanning the same disk.
Configuring storage About configuring storage pools
65
Table 4-2 Command

pool create
Configure storage pool commands Definition

Creates storage pools. You can build file systems on top of them.
Note: Disks being used for the Storage> pool create command
must support SCSI-3 PGR registrations if I/O fencing is enabled.
Note: The minimum size of disks required for creating a pool or adding
a disk to the pool is 10 MB. See Configuring storage pools on page 66. pool list Displays the pools and associated disks. A storage pool is a collection of disks from shared storage; the pool is used as the source for adding file system capacity as needed. See Configuring storage pools on page 66. pool rename Renames a pool. See Configuring storage pools on page 66. pool destroy Destroys storage pools used to create file systems. Destroying a pool does not delete the data on the disks that make up the storage pool. See Configuring storage pools on page 66. pool free Lists the free space in each of the pools. Free space information includes:

Disk name Free space Total space Use %
See Configuring storage pools on page 66.
66
Configuring storage Configuring storage pools
Configuring storage pools

To create the storage pool used to create a file system
List all of the available disks, and identify which ones you want to assign to which pools.
Storage> disk list Disk sfs_01 ==== ======== disk1 OK
To create a storage pool, enter the following:

Storage> pool create pool_name disk1[,disk2,...] pool_name Specifies what the created storage pool will be named. The storage pool name should be a string. Specifies the disks to include in the storage pool. If the specified disk does not exist, an error message is displayed. Use the Storage> disk list command to view the available disks. Each disk can only belong to one storage pool. If you try to add a disk that is already in use, an error message is displayed. To specify additional disks to be part of the storage pool, use a comma with no space in between.
disk1, disk2,...
For example:
Storage> pool create pool1 Disk_0,Disk_1 SFS pool Success V-288-1015 Pool pool1 created successfully 100% [#] Creating pool pool1
67
To list your pools
To list your pools, enter the following:

Storage> pool list
For example:
Storage> pool list Pool List of disks --------------------pool1 Disk_0 Disk_1 pool2 Disk_2 Disk_3 pool3 Disk_4 Disk_5
To rename a pool
To rename a pool, enter the following:

Storage> pool rename old_name new_name old_name Specifies the name for the existing pool that will be changed. If the old name is not the name of an existing pool, an error message is displayed. Specifies the new name for the pool. If the specified new name for the pool is already being used by another pool, an error message is displayed.
new_name
For example:
Storage> pool rename pool1 p01 SFS pool Success V-288-0 Disk(s) Pool rename successful.
68
To destroy a storage pool
To destroy a storage pool, enter the following:

Storage> pool destroy pool_name
where pool_name specifies the storage pool to delete. If the specified pool_name is not an existing storage pool, an error message is displayed. For example:
Storage> pool destroy pool1 SFS pool Success V-288-988 Pool pool1 is destroyed.
Because you cannot destroy an Unallocated storage pool, you need to remove the disk from the storage pool using the Storage> pool rmdisk command prior to trying to destroy the storage pool. See Configuring disks on page 70. If you want to move the disk from the unallocated pool to another existing pool, you can use the Storage> pool mvdisk command. See Configuring disks on page 70. To list free space for pools
To list free space for your pool, enter the following:

Storage> pool free [pool_name]
where pool_name specifies the pool for which you want to display free space information. If a specified pool does not exist, an error message is displayed. If pool_name is omitted, the free space for every pool is displayed, but information for specific disks is not displayed. For example:
Storage> pool free Pool Free Space ==== ========== pool_1 0 KB pool_2 0 KB pool_3 57.46M
Total Space =========== 165.49M 165.49M 165.49M
Use% ==== 100% 100% 65%
Configuring storage About configuring disks
69
About configuring disks

Disks and pools can be specified in the same command provided the disks are part of an existing storage pool. The pool and disk that are specified first are allocated space before other pools and disks. If the specified disk is larger than the space allocated, the remainder of the space is still utilized when another file system is created spanning the same disk. Table 4-3 Command
pool adddisk
Configure disks commands Definition

You can add a new disk to an existing pool. A disk can belong to only one pool. The minimum size of disks required for creating a pool or adding a disk to the pool is 10 MB.
Note: Disks being used for the pool adddisk command must support
SCSI-3 PGR registrations if I/O fencing is enabled. See Configuring disks on page 70. pool mvdisk You can move disks from one storage pool to another.
Note: You cannot move a disk from one storage pool to another if the
disk has data on it. See Configuring disks on page 70. pool rmdisk You can remove a disk from a pool.
Note: You cannot remove a disk from a pool if the disk has data on
it. See Configuring disks on page 70. If a specified disk does not exist, an error message is displayed. If one of the disks does not exist, then none of the disks are removed. A pool cannot exist if there are no disks assigned to it. If a disk specified to be removed is the only disk for that pool, the pool is removed as well as the assigned disk. If the specified disk to be removed is being used by a file system, then that disk will not be removed.
70
Configuring storage Configuring disks
Configuring disks
To add a disk
To add a new disk to an existing pool, enter the following:

Storage> pool adddisk pool_name disk1[,disk2,...] pool_name Specifies the pool to be added to the disk. If the specified pool name is not an existing pool, an error message is displayed. Specifies the disks to be added to the pool. To add additional disks, use a comma with no spaces between. A disk can only be added to one pool, so if the entered disk is already in the pool, an error message is displayed.
disk1,disk2,...
For example:
Storage> pool adddisk pool2 Disk_2 SFS pool Success V-288-0 Disk(s) Disk_2 are added to pool2 successfully.
Configuring storage Configuring disks
71
To move disks from one pool to another
To move a disk from one pool to another, or from an unallocated pool to an existing pool, enter the following:
Storage> pool mvdisk src_pool dest_pool disk1[,disk2,...] src_pool Specifies the source pool to move the disks from. If the specified source pool does not exist, an error message is displayed. Specifies the destination pool to move the disks to. If the specified destination pool does not exist, a new pool is created with the specified name. The disk is moved to that pool. Specifies the disks to be moved. To specify multiple disks to be moved, use a comma with no space in between. If a specified disk is not part of the source pool or does not exist, an error message is displayed. If one of the disks to be moved does not exist, all of the specified disks to be moved will not be moved. If all of the disks for the pool are moved, the pool is removed (deleted from the system), since there are no disks associated with the pool.
dest_pool
disk1,disk2,...
For example:
Storage> pool mvdisk p01 pool2 Disk_0 SFS pool Success V-288-0 Disk(s) moved successfully.
72
Configuring storage About performing local replication initialization
To remove a disk
To remove a disk from a pool, enter the following:

Storage> pool rmdisk disk1[,disk2,...]
where disk1,disk2 specifies the disk(s) to be removed from the pool. An unallocated pool is a reserved pool for holding disks that are removed from other pools. For example:
Storage> pool list Pool Name List of disks ----------------------pool1 Disk_0 Disk_1 pool2 Disk_2 Disk_5 pool3 Disk_3 Disk_4 Unallocated Disk_6 Storage> pool rmdisk Disk_6 SFS pool Success V-288-987 Disk(s) Disk_6 are removed successfully. Storage> pool list Pool Name List of disks ---------------------pool1 Disk_0 Disk_1 pool2 Disk_2 Disk_5 pool3 Disk_3 Disk_4
The Disk_6 disk no longer appears in the output.
To remove additional disks, use a comma with no spaces in between. For example:
Storage> pool rmdisk disk1,disk2
About performing local replication initialization

Local replication initialization allows you to initialize replication locally to some locally-attached disk array, then physically transport the disk array to the location of the destination file server, and then resume replication over a network link once the replication is configured correctly. Given that replicating an existing dataset can require delivering many terabytes of data to a remote site, physically transporting the disk array to a new location,
Configuring storage About performing local replication initialization
73
then resuming the replication can save significant set up time and network costs. For details on local replication initialization, see the Symantec FileStore Replication Guide. The following operations need to occur to perform replication local synchronization:
Define a set of disk, pools, and file systems that can be removed from the local FileStore cluster. Copy files between a set of file systems or directories and a second set of file systems or directories, so that when the second set of file systems are moved from a local system to a remote system, efficient periodic copying can be resumed without a full second copy operation over the network. Attach a removed (detached) set of disks, pools, and file systems to a second (remote) FileStore cluster one-time after they have been removed from the first (local) FileStore cluster.
Table 4-4 lists the Storage> pool commands you use for local replication initialization. Note: The Storage> pool attachset, detachset, and showdetached commands should be used for local replication initialization only and not for other purposes. Table 4-4 Command
pool detachset
Local replication initialization commands Definition

Detaches one or more pools from the FileStore cluster as a detached pool set. See Detaching one or more pools from the FileStore cluster as a detached pool set on page 74.
pool showdetached Displays the detached pools. See Displaying detached pools on page 75. pool attachset Attaches a detached pool set to the FileStore cluster. See Attaching a replication storage pool to a FileStore cluster on page 75.
74
Configuring storage Detaching one or more pools from the FileStore cluster as a detached pool set
Detaching one or more pools from the FileStore cluster as a detached pool set
The Storage> pool detachset command detaches one or more pools from the FileStore cluster as a detached pool set. You can provide a new name for the detached pool set. This operation unmounts the file systems, creating a separated disk group from the named pools, and deports that disk group. Once detached, the storage for those pools can be physically removed from the cluster. To detach one or more pools from the FileStore cluster
To detach one or more pools from the FileStore cluster, enter the following:
Storage> pool detachset pool1[,pool2,...] detach_poolset_name pool1, pool2, ... Specifies one or more pools to detach from the cluster. To specify multiple pools to detach, use a comma to separate the pool names with no space in between the pool names. detach_poolset_name Indicates the new name for the detached pool set.
For example:
Storage> pool detachset pool1 detached_pool1 SFS Storage SUCCESS V-288-1655 Pool detachset completed successfully.
Configuring storage Displaying detached pools
75
Displaying detached pools

To display detached pools
To display detached pools, enter the following

Storage> pool showdetached [detach_poolset_name]
where detach_poolset_name is the name of the detached pool set you want to display. For example:
Storage> pool showdetached DETACHED_POOLSETNAME ==================== detached_pool2 DETACHED_POOLSET_DISKS ======================= ams_wms0_34,ams_wms0_35 Storage> pool showdetached detached_pool2 Detached_poolsetname : detached_pool2 Poolsetid : 1276181004.41.src_01 Detached from Cluster : src Date : 2010.06.10 20:13:15 IST All detached fsnames : tgt_fs Detached filesystem : tgt_fs, Associated pools : pool2 Associated repunit : tgt_ru All detached pools : pool2 Detached pool : pool2, Disks : ams_wms0_34 ams_wms0_35 POOLSET_ID ========== 1276181004.41.src_01 DETACHED_POOLS ============== pool2
Attaching a replication storage pool to a FileStore cluster

The Storage> pool attachset command allows you to attach replication storage pool(s) to a FileStore cluster. At the time the replication storage pool is attached, the file systems or pools that are part of the replication storage poolset, can be renamed by using the pattern newname=oldname.
76
Configuring storage About displaying information for all disk devices
Several file systems or replication storage pools can be renamed by listing several such rename patterns in a comma-separated list, as in:
pool attachset poolset1 newfs1=tgt_fs,newpool2=pool2
To attach a replication storage pool to a FileStore cluster
To attach a replication storage pool(s) to a FileStore cluster, enter the following:

Storage> pool attachset poolset_name [name_mapping] poolset_name name_mapping Indicates the name of the pool set to attach. Specifies a comma-separated list of pools or file system name pairs in the form of new_name=old_name that you want to rename.
For example:
Storage> pool attachset poolset1 Mount Point is being added... SFS Storage SUCCESS V-288-1653 Pool attachset completed successfully.
About displaying information for all disk devices

The Storage> disk list command displays the aggregated information of the disk devices connected to all of the nodes in the cluster. Table 4-5 Command
disk list stats (default)
Disk devices commands Definition

Displays a list of disks and nodes in tabular form. Each row corresponds to a disk, and each column corresponds to a node. If an OK appears in the table, it indicates that the disk that corresponds to that row is accessible by the node that corresponds to that column. If an ERR appears in the table, it indicates that the disk that corresponds to that row is inaccessible by the node that corresponds to that column. This list does not include the internal disks of each node.
See Displaying information for all disk devices associated with nodes in a cluster on page 77.
Configuring storage Displaying information for all disk devices associated with nodes in a cluster
77
Table 4-5 Command

disk list detail
Disk devices commands (continued) Definition

Displays the disk information, including a list of disks and their properties. If the console server is unable to access any disk, but if any other node in the cluster is able to access that disk, then that disk is shown as "---." See Displaying information for all disk devices associated with nodes in a cluster on page 77.
disk list paths
Displays the list of multiple paths of disks connected to all of the nodes in the cluster. It also shows the status of each path on each node in the cluster. See Displaying information for all disk devices associated with nodes in a cluster on page 77.
disk list types
Displays the enclosure name, array name, and array type for a particular disk that is present on all of the nodes in the cluster. See Displaying information for all disk devices associated with nodes in a cluster on page 77.
Displaying information for all disk devices associated with nodes in a cluster
Depending on which command variable you use, the column headings will differ.
Disk Serial Number Enclosure Size Use% Indicates the disk name. Indicates the serial number for the disk. Indicates the type of storage enclosure. Indicates the size of the disk. Indicates the percentage of the disk that is being used.
78
ID
ID column consists of the following four fields. A ":" separates these fields.
VendorID - Specifies the name of the storage vendor, for example, HITACHI, IBM, EMC, HP, and so on.
ProductID - Specifies the ProductID based on vendor. Each vendor manufactures different products. For example, HITACHI has HDS5700, HDS5800, and HDS9200 products. These products have ProductIDs such as DF350, DF400, and DF500. TargetID - Specifies the TargetID. Each port of an array is a target. Two different arrays or two ports of the same array have different TargetIDs. TargetIDs start from 0. LunID - Specifies the ID of the LUN. This should not be confused with the LUN serial number. LUN serial numbers uniquely identify a LUN in a target. Whereas a LunID uniquely identifies a LUN in an initiator group (or host group). Two LUNS in the same initiator group cannot have the same LunID. For example, if a LUN is assigned to two clusters, then the LunID of that LUN can be different in different clusters, but the serial number is the same.
Enclosure
Name of the enclosure to distinguish between arrays having the same array name. Indicates the name of the storage array. Indicates the type of storage array and can contain any one of the three values: Disk for JBODs, Active-Active, and Active-Passive.
Array Name Array Type
To display a list of disks and nodes in tabular form
To display a list of disks and nodes in tabular form, enter the following:
Storage> disk list stats Disk ==== fas2700_13 fas2700_14 fas2700_15 fas2700_16 fas2700_17 dev_01 ======== OK OK OK OK OK dev_02 ======== OK OK OK OK OK
79
To display the disk information
To display the disk information, enter the following:

Storage> disk list detail Disk ==== fas2701_4 fas2701_5 fas2701_6 fas2701_7 Pool ==== pool2 pool1 pool2 pool1 Enclosure ========== fas2701 fas2701 fas2701 fas2701 Size ==== 1.0G 10.0G 1.0G 1.0G Use% ==== 47.3% 44.2% 4.3% 100.0%
ID ========================== NETAPP:LUN%5F311170011:0:1 NETAPP:LUN%5F311170011:0:2 NETAPP:LUN%5F311170011:0:3 NETAPP:LUN%5F311170011:0:4
Serial Number ============= hpasKJZRKpHK hpasKJZRKpaT hpasKJZRKppB hpasKJZRKqKx
To display the disk list paths
To display the disks multiple paths, enter the following:

Storage> disk list paths Disk Paths dev_01 dev_02 ==== ====== ======================== ======================== fas2700_13 Path 1 secondary,enabled,active secondary,enabled,active fas2700_14 Path 1 secondary,enabled,active secondary,enabled,active fas2700_15 Path 1 secondary,enabled,active secondary,enabled,active fas2700_16 Path 1 secondary,enabled,active secondary,enabled,active fas2700_17 Path 1 secondary,enabled,active secondary,enabled,active fas2700_18 Path 1 secondary,enabled,active secondary,enabled,active
80
Configuring storage Increasing the storage capacity of a LUN
To display information for all disk devices associated with nodes in a cluster
To display information for all of the disk devices connected to all of the nodes in a cluster, enter the following:
Storage> disk list types Disk ==== fas2700_13 fas2700_14 fas2700_15 fas2700_16 fas2700_17 fas2700_18 fas2700_19 Enclosure ========= fas2700 fas2700 fas2700 fas2700 fas2700 fas2700 fas2700 Array Name ========== FAS270 FAS270 FAS270 FAS270 FAS270 FAS270 FAS270 Array Type ========== A/P-C-NETAPP A/P-C-NETAPP A/P-C-NETAPP A/P-C-NETAPP A/P-C-NETAPP A/P-C-NETAPP A/P-C-NETAPP
Increasing the storage capacity of a LUN

The Storage> disk grow command lets you increase the storage capacity of a previously created LUN on a storage array disk. Warning: When increasing the storage capacity of a disk, make sure that the storage array does not reformat it. This will destroy the data. For help, contact your Storage Administrator. To increase the storage capacity of a LUN
1 2
Increase the storage capacity of the disk on your storage array. Contact your Storage Administrator for assistance. Run the FileStore Storage> scanbus command to make sure that the disk is connected to the FileStore cluster. See Initiating FileStore host discovery of LUNs on page 81.
To increase the storage capacity of the LUN, enter the following:

Storage> disk grow disk_name
where disk_name is the name of the disk. For example:

Storage> disk grow Disk_0 SFS disk SUCCESS V-288-0 disk grow Disk_0 completed successfully
Configuring storage Formatting/reinitializing a disk
81
Formatting/reinitializing a disk
If the disk does not belong to any group, the Storage> disk format command erases the first 100M space on the disk(s). You can specify more than one disk for formatting by using a comma to separate the disks. To reformat/reinitialize a disk
To reformat/reinitialize a disk, enter the following:

Storage> disk format disk1 [,disk2,...]
where disk1 is the disk that you want to format/reinitialize.
Printing WWN information

The Storage> hba (host bus adapter) command prints World Wide Name (WWN) information for all of the nodes in the cluster. If you want to find the WWN information for a particular node, specify the node name. To print WWN information
To print the WWN information, enter the following:

Storage> hba [host_name]
where you can use the host_name variable if you want to find WWN information for a particular node. Example output:
Storage> hba Node ==== sfs_01 sfs_02 sfs_03
Host Initiator HBA WWNs ======================= 21:00:00:e0:8b:9d:85:27, 21:01:00:e0:8b:bd:85:27 21:00:00:e0:8b:9d:65:1c, 21:01:00:e0:8b:bd:65:1c 21:00:00:e0:8b:9d:88:27, 21:01:00:e0:8b:bd:88:27
There are two WWNs on each row that represent the two HBAs for each node.
Initiating FileStore host discovery of LUNs

The Storage> scanbus command scans all of the SCSI devices connected to all of the nodes in the cluster. When you add new storage to your devices, you must scan for new SCSI devices. You only need to issue the command once and all of the nodes discover the newly added disks. And the command updates the device
82
Configuring storage Importing pools forcefully
configurations without interrupting the existing I/O activity. The scan does not inform you if there is a change in the storage configuration. You can see the latest storage configuration using the Storage> disk list command. You do not need to reboot after scanbus has completed. To scan SCSI devices
To scan the SCSI devices connected to all of the nodes in the cluster, enter the following:
Storage> scanbus
For example:
Storage> scanbus 100% [#] Scanning the bus for disks
Importing pools forcefully

The Storage> scanbus force command tries to import pools forcefully. This may help when using Storage> scanbus alone does not work. To import pools forcefully
To import pools forcefully, enter the following:

Storage> scanbus [force]
About I/O fencing

In the FileStore cluster, one method of communication between the nodes is conducted through heartbeats over private links. If two nodes cannot verify each other's state because they cannot communicate, then neither node can distinguish if the failed communication is because of a failed link or a failed partner node. The network breaks into two networks that cannot communicate with each other but do communicate with the central storage. This condition is referred to as the "split-brain" condition. I/O fencing (also referred to as disk fencing) protects data integrity if the split-brain condition occurs. I/O fencing determines which nodes are to retain access to the shared storage and which nodes are to be removed from the cluster, to prevent possible data corruption. To protect the data on the shared disks, each system in the cluster must be configured to use I/O fencing by making use of special purpose disks called
Configuring storage About I/O fencing
83
coordinator disks. They are standard disks or LUNs that are set aside for use by the I/O fencing driver. You can specify three disks as coordinator disks. The coordinator disks act as a global lock device during a cluster reconfiguration. This lock mechanism determines which node is allowed to fence off data drives from other nodes. A system must eject a peer from the coordinator disks before it can fence the peer from the data drives. Racing for control of coordinator disks is how fencing helps prevent split-brain. Coordinator disks cannot be used for any other purpose. You cannot store data on them. To use the I/O fencing feature, specify the disks that will be used as coordinator disks; you need three coordinator disks. Your minimum configuration must be a two-node cluster with FileStore software installed and 3+ disks (three of which will be used for the coordinator disk group and the rest of the disks will be used for storing data). See Table 4-6 on page 83. Table 4-6 Command
fencing status
I/O fencing commands Definition

Checks the status of I/O fencing. It shows whether the coordinator disk group is currently enabled or disabled. It also shows the status of the individual coordinator disks. See Configuring I/O fencing on page 84.
fencing on
Checks if the coordinator disk group has three disks. If not, you will need to add disks to the coordinator disk pool until three are present. The minimum LUN size is 10MB. See Configuring I/O fencing on page 84.
fencing replace
Replaces a coordinator disk with another disk. The command first checks the whether the replacement disks is in failed state or not. If its in the failed state, then an error appears. After the command verifies that the replacement disk is not in a failed state, it checks whether the replacement disk is already being used by an existing pool (storage or coordinator). If it is not being used by any pool, the original disk is replaced.
Note: If the disk being replaced is in a failed state, then it is mandatory

to delete the disk from the array. This is required because if the failed disk comes up and works properly, it can lead to an even number of fencing disks, and this affects the functionality. See Configuring I/O fencing on page 84.
84
Configuring storage Configuring I/O fencing
Table 4-6 Command

fencing off
I/O fencing commands (continued) Definition

Disables I/O fencing on all of the nodes. This command does not free up the coordinator disks. See Configuring I/O fencing on page 84.
fencing destroy
Destroys the coordinator pool if I/O fencing is disabled.
Note: This command is not supported for a single-node cluster.

See Configuring I/O fencing on page 84.
Configuring I/O fencing

To check the status of I/O fencing
To check the status of I/O fencing, enter the following:

Storage> fencing status
In the following example, I/O fencing is configured on the three disks Disk_0,Disk_1 and Disk_4 and the column header Coord Flag On indicates that the coordinator disk group is in an imported state and these disks are in good condition. If you check the Storage> disk list output, it will be in the OK state.
IO Fencing Status ============================ Disabled Disk Name ============== Disk_0 Disk_1 Disk_2 Coord Flag On ============== Yes Yes Yes
85
To add disks to coordinator disk group
To add disks to the coordinator disk group, enter the following:

Storage> fencing on [disk1,disk2,disk3]
The three disks are optional arguments and are required only if the coordinator pool does not contain any disks. You may still provide three disks for fencing with the coordinator pool already containing three disks. This will however remove the three disks previously used for fencing from the coordinator pool and configure I/O fencing on the new disks. For example:
Storage> fencing on SFS fencing Success V-288-0 IO Fencing feature now Enabled 100% [#] Enabling fencing Storage> fencing status IO Fencing Status ================= Enabled Disk Name ============== Disk_0 Disk_1 Disk_2 Coord Flag On ============== Yes Yes Yes
86
To replace an existing coordinator disk
To replace the existing coordinator disk, enter the following:

Storage> fencing replace src_disk dest_disk
where src_disk is the source disk and dest_disk is the destination disk. For example:
Storage> fencing replace Disk_2 Disk_3 SFS fencing Success V-288-0 Replaced disk Disk_2 with Disk_3 successfully. 100% [#] Replacing disk Disk_2 with Disk_3 Storage> fencing status IO Fencing Status ================= Enabled Disk Name ============== Disk_0 Disk_1 Disk_3 Coord Flag On ============== Yes Yes Yes
To disable I/O fencing
To disable I/O fencing, enter the following:

Storage> fencing off
For example, to disable fencing if it's already enabled:

Storage> fencing off SFS fencing Success V-288-0 IO Fencing feature now Disabled 100% [#] Disabling fencing
To destroy the coordinator pool
To destroy the coordinator pool, enter the following:

Storage> fencing destroy
Configuring storage About quotas for file systems
87
About quotas for file systems

You use Storage > quota commands for configuring disk quotas on file systems for users and groups. Users and groups visible through different sources of name service lookup (nsswitch), local users, LDAP, NIS, and Windows users can be configured for files systems or CIFS home directory quotas. There are two types of disk quotas:
Usage quota (numspace) - limits the amount of disk space that can be used on a file system Inode quota (numinodes) - limits the number of inodes that can be created on a file system
An inode is a data structure in a UNIX or UNIX-like file system that describes the location of some or all of the disk blocks allocated to the file. In addition to setting a limit on disk quotas, you can also define a warning level, or soft quota, whereby the FileStore administrator is informed that they are nearing their limit, which is less than the effective limit, or hard quota. Hard quota limits can be set so that a user is strictly not allowed to cross quota limits. A soft quota limit must be less than a hard quota limit for any type of quota. Table 4-7 Command
quota fs enable
File system quota commands Definition

Enables the quota on a specified file system. If the file system name is not specified, the quota is enabled for all of the online file systems. See Using quota commands for enabling, disabling, and displaying file system quotas on page 89.
quota fs disable
Disables the quota on a specified file system. If a file system name is not specified, the quota is disabled on all of the online file systems. See Using quota commands for enabling, disabling, and displaying file system quotas on page 89.
quota fs status
Displays the quota status of the specified file system. If a file system name is not specified, the command displays the quota status for all of the online file systems. This command only displays whether or not the quota is enabled. See Using quota commands for enabling, disabling, and displaying file system quotas on page 89.
88
Configuring storage About quotas for file systems
Table 4-7 Command

quota fs set
File system quota commands (continued) Definition

Sets the quota for the user or group on the specified file system. If a file system name is not specified, the quota for the user name or group name applies to all of the online file systems. This command does not set the quota for the CIFS home directories. See Using quota commands for setting and displaying file system quotas on page 91.
quota fs setall
Sets the quota value for all the users and groups for whom the quota has already been set with set commands. Other users and groups (for whom the quota has not been set previously) will not be affected. See Using quota commands for setting and displaying file system quotas on page 91.
quota fs show
Displays the quota values that are already set for user or group. See Using quota commands for setting and displaying file system quotas on page 91.
quota fs setdefault Changes the default value used for setting future quotas. Existing user/group quotas are not changed. If a file system name is not specified, then the default is set for all of the online file systems except the CIFS home directories. See Using quota commands for setting and displaying file system quotas on page 91. quota fs showdefault Displays the default quota values for user or group. See Using quota commands for setting and displaying file system quotas on page 91.
Configuring storage Using quota commands for enabling, disabling, and displaying file system quotas
89
Using quota commands for enabling, disabling, and displaying file system quotas
To enable a file system quota
To enable a file system quota, enter the following:

Storage> quota fs enable [fs_name] [{userquota | groupquota}] fs_name userquota File system name you want to set the quota for. User quota can be set with hard/soft limits on usage. Usage is dictated by the number of blocks and number of inodes that can be created by the user. Group quota can be set with hard/soft limits on usage. Usage is dictated by the number of blocks and number of inodes that can be created by all the users in the group.
groupquota
For example, to enable a quota (user and group) for file system fs1:
Storage> quota fs enable fs1 OK Completed
To disable a file system quota
To disable a file system quota, enter the following:

Storage> quota fs disable [fs_name] [{userquota | groupquota}] fs_name userquota File system name you want to set the quota for. User quota can be set with hard/soft limits on usage. Usage is dictated by the number of blocks and number of inodes that can be created by the user. Group quota can be set with hard/soft limits on usage. Usage is dictated by the number of blocks and number of inodes that can be created by all the users in the group.
groupquota
For example, to disable the user quota for file system fs1:
Storage> quota fs disable fs1 userquota OK Completed
90
Configuring storage Using quota commands for enabling, disabling, and displaying file system quotas
To display the status of a file system quota
To display the status of a file system quota, enter the following:

Storage> quota fs status [fs_name] [{userquota | groupquota}] fs_name userquota File system name you want to set the quota for. User quota can be set with hard/soft limits on usage. Usage is dictated by the number of blocks and number of inodes that can be created by the user. Group quota can be set with hard/soft limits on usage. Usage is dictated by the number of blocks and number of inodes that can be created by all the users in the group.
groupquota
For example, to display the status of a file system quota (enabled or disabled):
Storage> quota fs status FS name User Quota ======= ========== fsmirror Disabled quotafs Enabled striped1 Enabled fs1 Disabled OK Completed
Group Quota ========== Disabled Enabled Enabled Enabled
Configuring storage Using quota commands for setting and displaying file system quotas
91
Using quota commands for setting and displaying file system quotas
To set the quota value
To set the quota value for a file system, enter the following:
Storage> quota fs set [{userquota | groupquota}] user_or_group_names [hardlimit | softlimit] [numinodes | numspace] [value] [fs_name]
For example, to set the user quota (hardlimit and numinodes) of user qtuser on file system fs1:
Storage> quota fs set userquota qtuser hardlimit numinodes 957 fs1 OK Completed Storage> quota fs show fs1 userquota qtuser User Quota Details for filesystem fs1: User Space Soft Hard Inodes Soft Name Used Space Space Used Inodes ===== ===== ===== ===== ===== ===== qtuser 0 0 0 0 0 OK Completed
Hard Inodes ==== 957
userquota
User quota can be set with hard/soft limits on usage. Usage is dictated by the number of blocks and number of inodes that can be created by the user. Group quota can be set with hard/soft limits on usage. Usage is dictated by the number of blocks and number of inodes that can be created by all the users in the group.
groupquota
user_or_group_name Name of the user or the name of the group for which a quota value is set. You can specify a comma-separated list of user or group names. To delete quota values for a user, you have to set all the user quota entries to 0. A user with a UID of 0 is not allowed in a Storage> quota fs set command. A 0 indicates there is no limitation on the file system. hardlimit Hard quota limits (hardlimit) can also be set so that you are not allowed to exceed the quota limits. A quota limit can be set as a soft quota limit (soflimit) where you are warned against exceeding the quota limits, and there is a grace period during which you are allowed to exceed the quota limits. After the grace period is over, you will not be allowed to exceed the quota limits. The soflimit has to be less than the hardlimit for any type of quota.
softlimit
92
numinodes numspace value
Inode quota for the file system. Usage quota (numspace) for the file system. Quota value for the users or groups on a file system. If a value is not provided, the default value set from using the Storage> quota fs setdefault command is used. If Storage> quota fs setdefault is set for particular file systems, then that default value has precedence.
fs_name
File system name you want to set the quota for.
To set all quota values
To set all of the quota values, enter the following:

Storage> quota fs setall [{userquota | groupquota}] [hardlimit | softlimit] [numinodes | numspace] [value] [fs_name]
For example, to set all existing user quotas to default values:

Storage> quota fs show User Quota Details for User Space Soft Name Used Space ===== ===== ====== a1 0 0 qtuser 0 0 qtuser2 0 1000K fs1 filesystem fs1: Hard Inodes Space Used ====== ===== 10G 0 0 0 0 0
Soft Inodes ====== 1000 0 0
Hard Inodes ===== 10000 957 0
Storage> quota fs setall userquota OK Completed Storage> quota fs show fs1 User Quota Details for filesystem fs1: User Space Soft Hard Inodes Name Used Space Space Used ======= ===== ===== ===== ==== a1 0 0 10G 0 qtuser 0 0 0 0 qtuser2 0 1000K 0 0
Soft Inodes ==== 1000 0 0
Hard Inodes ===== 1000 1000 1000
userquota
User quota can be set with hard/soft limits on usage. Usage is dictated by the number of blocks and number of inodes that can be created by the user.
93
groupquota
Group quota can be set with hard/soft limits on usage. Usage is dictated by the number of blocks and number of inodes that can be created by all the users in the group. Hard quota limit. Soft quota limit. Inode quota for the file system. Usage quota for the file system. Quota value for the users or groups on a file system. If a value is not provided, the default value set from using the Storage> quota fs setdefault command is used. If Storage> quota fs setdefault is set for particular file systems, then that default value has precedence. If a value is 0 is entered, it is treated as an unlimited quota. If all values for a user or group quota are 0, the user or group is automatically deleted from the quota settings, which means that the Storage> quota fs status command will not show this user's or group's settings, as all quota values are treated as an unlimited quota.
hardlimit softlimit numinodes numspace value
94
To display the file system settings
To display the file system settings, enter the following:

Storage> quota fs show [fs_name] [{userquota | groupquota}] [user_or_group_names]
For example, to display quota values for the file system:

Storage> quota fs show User Quota Details for filesystem quotafs: User Space Soft Hard Files Soft Name Used Space Space Used Files ========== ===== ====== ======= ===== ===== quotauser 10M 1M 20M 1 5 quotauser 9M 1M 10M 1 0 qtuser 10M 10M 20M 9 5 qtuser2 19M 5M 20M 1 0 User Quota Details for filesystem fs1: User Space Soft Hard Files Name Used Space Space Used ====== ====== ===== ===== ===== a1 0 0 10G 0 qtuser 0 0 0 0 qtuser2 0 1000K 0 0
Hard Files ====== 1000 0 1000 1000
Soft Files ===== 1000 0 0
Hard Files ===== 1000 1000 1000
User Quota Details for filesystem longfilesystemnameforqt: User Space Name Used ====== ===== qtuser 0 OK Completed Soft Space ===== 0 Hard Space ===== 0 Files Used ===== 0 Soft Files ==== 901 Hard Files ===== 1000
fs_name userquota
File system name you want to set the quota for. User quota can be set with hard/soft limits on usage. Usage is dictated by the number of blocks and number of inodes that can be created by the user. Group quota can be set with hard/soft limits on usage. Usage is dictated by the number of blocks and number of inodes that can be created by all the users in the group.
groupquota
95
user_or_group_names
Name of the user or the name of the group for which a quota value is set. You can specify a comma-separated list of user or group names. To delete quota values for a user, you will have to set all the user quota entries to 0. A user with a UID of 0 is not allowed in a Storage> quota fs set command.
To set the default quota values
To set the default quota values, enter the following:

Storage> quota fs setdefault [{userquota | groupquota}] hardlimit | softlimit numinodes | numspace [value] [fs_name]
userquota
User quota can be set with hard/soft limits on usage. Usage is dictated by the number of blocks and number of inodes that can be created by the user. Group quota can be set with hard/soft limits on usage. Usage is dictated by the number of blocks and number of inodes that can be created by all the users in the group. Hard quota limit. Soft quota limit. Inode quota for the file system. Usage quota for the file system. Quota value for the users or groups on a file system. If a value is not provided, the default value set from using the Storage> quota fs setdefault command is used. If Storage> quota fs setdefault is set for particular file systems, then that default value has precedence. If a value is 0 is entered, it is treated as an unlimited quota. If all values for a user or group quota are 0, the user or group is automatically deleted from the quota settings, which means that the Storage> quota fs status command will not show this user's or group's settings, as all quota values are treated as an unlimited quota.
groupquota
fs_name
File system name you want to set the quota for.
For example, to set the default group quota value:

Storage> quota fs setdefault groupquota hardlimit numspace 1T OK Completed
96
Configuring storage About quotas for CIFS home directories
To display the default values
To display the default values, enter the following:

Storage> quota fs showdefault [fs_name] [{userquota | groupquota}] fs_name userquota File system name you want to set the quota for. User quota can be set with hard/soft limits on usage. Usage is dictated by the number of blocks and number of inodes that can be created by the user. Group quota can be set with hard/soft limits on usage. Usage is dictated by the number of blocks and number of inodes that can be created by all the users in the group.
groupquota
For example, to display the default quota values:

Storage> quota fs showdefault Default Quota values: ===================== Title User/Group Soft Quota Space ===== =========== ====== Default Quota User Quota Default Quota Group Quota Per FS default Quota values: ======================================== FS User/Group Soft Hard Name Quota Space Space ===== ============= ===== ===== fs1 User Quota OK Completed Soft Files ===== Hard Files ===== 1000
Hard Space ====== 1T
Soft Hard Files Files ====== ===== 1000 -
About quotas for CIFS home directories

You use Storage> quota cifshomedir commands to configure quotas for CIFS home directories. Users and groups visible through different sources of name service lookup (nsswitch), local users, LDAP, NIS, and Windows users can be configured for CIFS home directory quotas. Default values are entered in a configuration file only. The actual application of the quota is done with the set and setall commands using the default values provided.
Configuring storage About quotas for CIFS home directories
97
Table 4-8 Command
CIFS home directory quota commands Definition
quota cifshomedir Changes the default value that will be used for setting future quotas setdefault on the CIFS home directories. Existing user/group quotas are not effected. See Using quotas for CIFS home directories on page 98. quota cifshomedir Displays the default values for the CIFS home directories. showdefault See Using quotas for CIFS home directories on page 98. quota cifshomedir Sets the quota value for the users or groups for the CIFS home set directories. See Using quotas for CIFS home directories on page 98. quota cifshomedir Sets the quota value for all users and groups for whom the quota has setall already been set with set commands. See Using quotas for CIFS home directories on page 98. quota cifshomedir Enables the quota of the CIFS home directories. enable See Using quotas for CIFS home directories on page 98. quota cifshomedir Disables the quota of the CIFS home directories. disable See Using quotas for CIFS home directories on page 98. quota cifshomedir Displays the status of the quota of the CIFS home directories. This status command only displays whether or not the quota is enabled. See Using quotas for CIFS home directories on page 98. quota cifshomedir Displays the general quota values on the CIFS home directories per show user or group. This command also displays the consumed (used space) quota for users or groups. See Displaying the quota values for CIFS home directories on page 105. quota cifshomedir Displays the detailed quota values already set on each file system for showdetail CIFS home directories. This command also displays the consumed (used space) quota for users or groups on each file system for the CIFS home directories. See Displaying the quota values for CIFS home directories on page 105.
98
Configuring storage Using quotas for CIFS home directories
Using quotas for CIFS home directories

To set the default value used for quota limits for CIFS home directories
To set the default value used for quota limits for CIFS home directories, enter the following:
Storage> quota cifshomedir setdefault userquota | groupquota hardlimit | softlimit numinodes | numspace [value] userquota User quota can be set with hard/soft limits on usage. Usage is dictated by the number of blocks and number of inodes that can be created by the user. Group quota can be set with hard/soft limits on usage. Usage is dictated by the number of blocks and number of inodes that can be created by all the users in the group. Hard quota limit. Soft quota limit. Inode quota for the file system. Usage quota for the file system. Quota value for the users or groups on a file system. If a value is not specified, then the value is 0. If Storage> quota fs setdefault is set for particular file systems, then that default value has precedence. If a value is 0 is entered, it is treated as an unlimited quota. If all values for a user or group quota are 0, the user or group is automatically deleted from the quota settings, which means that the Storage> quota fs show command will not show this user's or group's settings, as all quota values are treated as an unlimited quota.
groupquota
For example, to set the default CIFS home directory user quota value:
Storage> quota cifshomedir setdefault userquota hardlimit numspace 2T OK Completed
99
To display default quota values for CIFS home directories
To display the default quota values of the CIFS home directories, enter the following:
Storage> quota cifshomedir showdefault [userquota | groupquota] userquota User quota can be set with hard/soft limits on usage. Usage is dictated by the number of blocks and number of inodes that can be created by the user. Group quota can be set with hard/soft limits on usage. Usage is dictated by the number of blocks and number of inodes that can be created by all the users in the group.
groupquota
For example, to display the default CIFS home directory quota values:
Storage> quota cifshomedir showdefault CIFS homedir default Quota values: ============================================== User/Group Quota Soft Space Hard Space Soft Inodes ================ ========== ========== =========== User Quota 2T Group Quota OK Completed
Hard Inodes =========== -
100
To set a quota for CIFS home directories
To set a quota for the user or group for CIFS home directories, enter the following:
Storage> quota cifshomedir set userquota | groupquota user_or_group_names [domainname] [hardlimit | softlimit] [numinodes | numspace] [value]
For example, to set the user quota (hardlimit and numinodes) of user qtuser on CIFS home directories:
Storage> quota cifshomedir set userquota qtuser qtdomain hardlimit numinodes 6549 Storage> quota cifshomedir show User Quota Details for CIFS homedirfs: User Space Name Used ======== ===== qtuser 0 OK Completed Soft Space ===== 20M Hard Space ====== 100M Inodes Used ===== 0 Soft Inodes ====== 1000 Hard Indoes ====== 6549
userquota
User quota can be set with hard/soft limits on usage. Usage is dictated by the number of blocks and number of inodes that can be created by the user. Group quota can be set with hard/soft limits on usage. Usage is dictated by the number of blocks and number of inodes that can be created by all the users in the group. Name of the user or the name of the group for which a quota value is set. You can specify a comma-separated list of user or group names. To delete quota values for a user, you will have to set all the user quota entries to 0. A user with a UID of 0 is not allowed in a Storage> quota fs set command.
groupquota
user_or_group_names
domainname
Domain name is the first section of the domain. For example, in symantec.filestore.com the domain name is symantec.
hardlimit softlimit
Hard quota limit. Soft quota limit.
101
numinodes numspace value
Inode quota for the file system. Usage quota for the file system. Quota value for the CIFS home directories. If a value is not provided, the default value set from using the Storage> quota fs setdefault command is used. If Storage> quota fs setdefault is set for particular file systems, then that default value has precedence. If a value is 0 is entered, it is treated as an unlimited quota. If all values for a user or group quota are 0, the user or group is automatically deleted from the quota settings, which means that the Storage> quota fs status command will not show this user's or group's settings, as all quota values are treated as an unlimited quota.
102
To set the quota value for all users and groups
To set the quota value for all users and groups for whom the quota has already been set with the set commands, enter the following:
Storage> quota cifshomedir setall userquota | groupquota [hardlimit | softlimit] [numinodes | numspace] [value]
Other users and groups (for whom quota has not been set previously) will not be affected. For example, to set all existing user quotas for CIFS home directories:
Storage> quota cifshomedir show User Quota Details for CIFS homedirfs: User Space Name Used ======= ====== qtuser 0 OK Completed Soft Space ====== 20M Hard Space ===== 100M Inodes Used ===== 0 Soft Inodes ====== 1000 Hard Inodes ====== 6549
Storage> quota cifshomedir setall userquota softlimit numinodes 198 OK Completed Storage> quota cifshomedir show User Quota Details for CIFS homedirfs: User Space Name Used ===== ===== qtuser 0 OK Completed Soft Space ====== 20M Hard Space ====== 100M Inodes Used ===== 0 Soft Inodes ====== 198 Hard Inodes ====== 6549
userquota
User quota can be set with hard/soft limits on usage. Usage is dictated by the number of blocks and number of inodes that can be created by the user. Group quota can be set with hard/soft limits on usage. Usage is dictated by the number of blocks and number of inodes that can be created by all the users in the group. Hard quota limit. Soft quota limit. Inode quota for the file system.
groupquota
hardlimit softlimit numinodes
103
numspace value
Usage quota for the file system. Quota value for CIFS home directories for whom the quota has already been set with set commands. If a value is not provided, the default value set from using the Storage> quota fs setdefault command is used. If Storage> quota fs setdefault is set for particular file systems, then that default value has precedence. If a value is 0 is entered, it is treated as an unlimited quota. If all values for a user or group quota are 0, the user or group is automatically deleted from the quota settings, which means that the Storage> quota fs status command will not show this user's or group's settings, as all quota values are treated as an unlimited quota.
To enable the quota for CIFS home directories
To enable the quota for CIFS home directories, enter the following:
Storage> quota cifshomedir enable [userquota | groupquota] userquota User quota can be set with hard/soft limits on usage. Usage is dictated by the number of blocks and number of inodes that can be created by the user. Group quota can be set with hard/soft limits on usage. Usage is dictated by the number of blocks and number of inodes that can be created by all the users in the group.
groupquota
For example, to enable quotas (user and group quotas) for CIFS home directories:
Storage> quota cifshomedir enable OK Completed
104
To disable the quota for CIFS home directories
To disable the quota for the CIFS home directories, enter the following:
Storage> quota cifshomedir disable [userquota | groupquota] userquota User quota can be set with hard/soft limits on usage. Usage is dictated by the number of blocks and number of inodes that can be created by the user. Group quota can be set with hard/soft limits on usage. Usage is dictated by the number of blocks and number of inodes that can be created by all the users in the group.
groupquota
For example, to disable the group quota for CIFS home directories:
Storage> quota cifshomedir disable groupquota OK Completed
To display the status of the quota for CIFS home directories
To display the quota status of the CIFS home directories, enter the following:
Storage> quota cifshomedir status [userquota | groupquota]
Displays only if the quota is enabled or disabled.

userquota User quota can be set with hard/soft limits on usage. Usage is dictated by the number of blocks and number of inodes that can be created by the user. Group quota can be set with hard/soft limits on usage. Usage is dictated by the number of blocks and number of inodes that can be created by all the users in the group.
groupquota
For example, to display the status of a CIFS home directory quota (enabled or disabled):
Storage> quota cifshomedir status FS name User Quota ======= ========== CIFS homedirectories OK Completed Enabled
Group Quota ========== Disabled
Configuring storage Displaying the quota values for CIFS home directories
105
Displaying the quota values for CIFS home directories

To display the quotas for CIFS home directories
To display the quotas for the CIFS home directories, enter the following:
Storage> quota cifshomedir show [userquota | groupquota] [user_or_group_names]
userquota
groupquota
user_or_group_names Name of the user or the name of the group for which a quota value is set. You can specify a comma-separated list of user or group names. To delete quota values for a user, you will have to set all the user quota entries to 0. A user with a UID of 0 is not allowed in a Storage> quota fs set command.
For example, to display general quota information for a CIFS home directory for both userquota and group quota:
Storage> quota cifshomedir show User Quota Details for CIFS homedirfs: User Name Space Used Soft Space Hard Space Inodes Used Soft Inodes Hard Inodes ========= ========== ========== ========== =========== =========== =========== user06 0 30M 50M 0 0 0 user07 0 0 0 0 300 500 Group Quota Details for CIFS homedirfs: Group Name Space Used Soft Space Hard Space Inodes Used Soft Inodes Hard Inodes ========= ========== ========== ========= =========== =========== =========== group01 0 400M 600M 0 0 0 group02 0 0 0 0 60000 80000 OK Completed
The Storage> quota cifshomedir show command does not display the file system name in the output.
106
Configuring storage Displaying the quota values for CIFS home directories
To display the quota values that are already set on each file system for the CIFS home directories
To display the quota values that are already set on each file system for the CIFS home directories, enter the following:
Storage> quota cifshomedir showdetail [userquota | groupquota] [user_or_group_names]
userquota
groupquota
user_or_group_names Name of the user or the name of the group for which a quota value is set. You can specify a comma-separated list of user or group names. To delete quota values for a user, you will have to set all the user quota entries to 0. A user with a UID of 0 is not allowed in a Storage> quota fs set command.
For example, to display quota information on CIFS home directory file systems fs1 and fs2 for both userquota and groupquota:
Storage> quota cifshomedir showdetail User Quota Details for filesystem fs1: User Name Space Used Soft Space Hard Space Inodes Used Soft Inodes Hard Inodes ========== ========== ========== ========== ========== ========== ========== user06 0 30M 50M 0 0 0 user07 0 0 0 0 300 500 User Quota Details for filesystem fs2: User Name Space Used Soft Space Hard Space Inodes Used Soft Inodes Hard Inodes ========== ========== ========== ========== ========== ========== ========== user06 0 30M 50M 0 0 0 user07 0 0 0 0 300 500 Group Quota Details for filesystem fs1: Group Name Space Used Soft Space Hard Space Inodes Used Soft Inodes Hard Inodes ========== ========== ========== ========== ========== ========== ========== group01 0 400M 600M 0 0 0 group02 0 0 0 0 60000 80000 Group Quota Details for filesystem fs2: Group Name Space Used Soft Space Hard Space Inodes Used Soft Inodes Hard Inodes ========== ========== ========== ========== ========== ========== ========== group01 0 400M 600M 0 0 0 group02 0 0 0 0 60000 80000 OK Completed
Configuring storage About iSCSI
107
The file system name displays in the output for the Storage> quota cifshomedir showdetail command.
About iSCSI
The Internet Small Computer System Interface (iSCSI) is an Internet protocol-based storage networking standard that links data storage facilities. By carrying SCSI commands over IP networks, iSCSI facilitates data transfers over Intranets and manages storage over long distances. The iSCSI feature allows FileStore servers to use iSCSI disks as shared storage. Table 4-9 Command
iscsi status
iSCSI commands Definition

Displays the status of the iSCSI initiator service. See Configuring the iSCSI initiator on page 108.
iscsi start
Starts the iSCSI initiator service. See Configuring the iSCSI initiator on page 108.
iscsi stop
Stops the iSCSI initiator service. See Configuring the iSCSI initiator on page 108.
iscsi device add
Adds a device for use with the iSCSI initiator. iSCSI initiator connections use this device to connect to the target. If there are any existing targets, then the iSCSI initiator initiates a connection to all targets by way of device. See Configuring the iSCSI initiator on page 108.
iscsi device del
Deletes a device from the iSCSI configuration. Any existing connections by way of the device to targets is terminated. If device is the last device in the iSCSI initiator configuration, and there are existing targets, then the device cannot be deleted from the configuration. See Configuring the iSCSI initiator on page 108.
iscsi device list
Lists the devices used by the iSCSI initiator. See Configuring the iSCSI initiator on page 108.
108
Table 4-9 Command
iSCSI commands (continued) Definition
iscsi discovery add Adds a discovery address to the iSCSI initiator configuration. If no TCP port is specified with the discovery-address, then the default port 3260 is used. Any targets discovered at discovery-address are automatically logged in. See Configuring the iSCSI initiator on page 108. iscsi discovery del Deletes a discovery address from the iSCSI initiator configuration. Any targets discovered using discovery-address are also deleted from the configuration. See Configuring the iSCSI initiator on page 108. iscsi discovery rediscover Performs discovery of changes in targets or LUNs at discovery-address. Any LUNs or targets that have been removed at discovery-address will be automatically removed from the configuration. New LUNs or targets discovered at discovery-address will be automatically added and logged into. See Configuring the iSCSI initiator on page 108. iscsi discovery list Lists the discovery address present in the iSCSI initiator configuration. See Configuring the iSCSI initiator on page 108. iscsi initiator name setprefix Sets the prefix used to generate initiator names. Initiator names are generated as initiator-name-prefix followed by the node number of the node. See Configuring the iSCSI initiator name on page 109. iscsi initiator name list Lists the initiator names for all nodes in the cluster. See Configuring the iSCSI device on page 110.
Configuring the iSCSI initiator

To display the iSCSI initiator service
To display the status of the iSCSI initiator server, enter the following:
Storage> iscsi status
For example:
iSCSI Initiator Status on sfs_01 : ONLINE iSCSI Initiator Status on sfs_02 : ONLINE
109
To start the iSCSI initiator service
To start the iSCSI initiator service, enter the following:

Storage> iscsi start
For example:
Storage> iscsi start Storage> iscsi status iSCSI Initiator Status on sfs_01 : ONLINE iSCSI Initiator Status on sfs_02 : ONLINE
To stop the iSCSI initiator service
To stop the iSCSI initiator service, enter the following:

Storage> iscsi stop
For example:
Storage> iscsi stop Storage> iscsi status iSCSI Initiator Status on sfs_01 : OFFLINE iSCSI Initiator Status on sfs_02 : OFFLINE
Configuring the iSCSI initiator name

To display the iSCSI initiator names
To display the iSCSI initiator names, enter the following:

Storage> iscsi initiator name list
For example:
Storage> iscsi initiator name list Node Initiator Name ----------------sfs_01 iqn.2009-05.com.test:test.1 sfs_02 iqn.2009-05.com.test:test.2
110
To configure the iSCSI initiator name
To configure the iSCSI initiator name, enter the following:

Storage> iscsi initiator name setprefix initiatorname-prefix
where initiatorname-prefix is a name that conforms to the naming rules for initiator and target names as specified in RFC3721. Initiator names for nodes in the cluster are generated by appending the node number to this prefix. For example:
Storage> iscsi initiator name setprefix iqn.2009-05.com.test:test
Configuring the iSCSI device

The iSCSI initiator contains a list of devices from which connections are made to targets. To display the list of devices
To display the list of devices, enter the following:

Storage> iscsi device list
For example:
Storage> iscsi device list Device -----pubeth0 pubeth1
To add an iSCSI device
To add an iSCSI device, enter the following:

Storage> iscsi device add device
where device is the device where the operation takes place. For example:
Storage> iscsi device add pubeth1 Storage> iscsi device list Device -----pubeth0 pubeth1
111
To delete an iSCSI device
To delete an iSCSI device, enter the following:

Storage> iscsi device delete device
where device is the device where the operation takes place. For example:
Storage> iscsi device add pubeth1 Storage> iscsi device list Device -----pubeth0
Configuring discovery on iSCSI

The iSCSI initiator contains a list of discovery addresses. To display the iSCSI discovery addresses
To display the iSCSI discovery addresses, enter the following:

Storage> iscsi discovery list
For example:
Storage> iscsi discovery list Discovery Address ----------------192.168.2.14:3260 192.168.2.15:3260
112
To add a discovery address to the iSCSI initiator
To add a discovery address to the iSCSI initiator, enter the following:

Storage> iscsi discovery add discovery-address
where discovery-address is the target address at which an initiator can request a list of targets using a SendTargets text request as specified in iSCSI protocol of RFC3720. If no port is specified with the discovery address, default port 3260 is used. For example:
Storage> iscsi discovery add 192.168.2.15:3260 Discovery CHAP credentials for sfs_1: Outgoing CHAP Username : root Outgoing CHAP Password : ******** Incoming CHAP Username : Authentication succeeded. Discovered Targets -----------------iqn.2001-04.com.example:storage.disk2.sys3.xyz iqn.2001-04.com.example:storage.disk3.sys3.xyz iqn.2001-04.com.example:storage.disk4.sys3.xyz iqn.2001-04.com.example:storage.disk5.sys3.xyz Logging into target iqn.2001-04.com.example:storage.disk2.sys3.xyz Logging into target iqn.2001-04.com.example:storage.disk3.sys3.xyz Logging into target iqn.2001-04.com.example:storage.disk4.sys3.xyz Logging into target iqn.2001-04.com.example:storage.disk5.sys3.xyz Storage> iscsi discovery list Discovery Address ----------------192.168.2.14:3260 192.168.2.15:3260
113
To delete an iSCSI discovery address
To delete the targets discovered using this discovery address, enter the following:
Storage> iscsi discovery del discovery-address
Storage> iscsi discovery del 192.168.2.15:3260 Storage> iscsi discovery list Discovery Address ----------------192.168.2.14:3260
To rediscover an iSCSI discovery address
To rediscover an iSCSI discovery address, enter the following:

Storage> iscsi discovery rediscover discovery-address
Storage> iscsi discovery rediscover 192.168.2.15:3260 Deleted targets ----------------iqn.2001-04.com.example:storage.disk5.sys3.xyz New targets ----------------iqn.2001-04.com.example:storage.disk6.sys3.new.xyz Logging into target iqn.2001-04.com.example:storage.disk6.sys3.new.xyz
114
Configuring storage About configuring the iSCSI targets
About configuring the iSCSI targets

iSCSI target commands allow you to view or manipulate targets discovered using the iscsi discovery add command, or statically added targets using the iscsi target add command. The iscsi target list command lists all the targets visible to the iSCSI initiator. To get detailed information about a target, use the iscsi target listdetail targetname command. Table 4-10 Command
iscsi target add
iSCSI target commands Definition

Adds a static target-portal combination to the iSCSI initiator configuration. The portal-address cannot be the same as any discovery-address present in the iSCSI initiator configuration. Connections to portal-address are made for target-name, but no discovery is done for any other targets available at portal-address. If no portal tag is specified with portal-address, the default portal tag of 1 is used. See Configuring the iSCSI targets on page 116.
iscsi target del
Deletes a target target-name from the iSCSI initiator configuration. Any existing connections to target-name are terminated. discovery-address or portal-address is the address through which the target becomes visible to the initiator. A target that was discovered at a discovery-address once deleted from an iSCSI initiator configuration will again be visible to an iSCSI initiator if re-discovery is done either through isci discovery rediscover or scanbus commands. See Configuring the iSCSI targets on page 116.
iscsi target login
Allows login to a target target-name from an iSCSI initiator. Connections to target-name are made from all devices present in an iSCSI initiator configuration. discovery-address or portal-address is the address through which the target becomes visible to the initiator. A target once logged out by the iSCSI initiator is not logged in until iscsi target login is requested. See Configuring the iSCSI targets on page 116.
Configuring storage About configuring the iSCSI targets
115
Table 4-10 Command
iSCSI target commands (continued) Definition
iscsi target logout Allows logout from connections to target-name from the iSCSI initiator. discovery-address or portal-address is the address through which the target becomes visible to the initiator. A target once logged out by the iSCSI initiator is not logged in until iscsi target login is requested. See Configuring the iSCSI targets on page 116. iscsi target list Lists the targets visible to the iSCSI initiator. See Configuring the iSCSI targets on page 116. iscsi target listdetail Lists detailed information about the target. See Configuring the iSCSI targets on page 116.
116
Configuring storage Configuring the iSCSI targets
Configuring the iSCSI targets

To display the iSCSI targets
To display the iSCSI targets, enter the following:

Storage> iscsi target list
For example:
Storage> iscsi target list Target -----iqn.2001-04.com.example:storage.disk2.sys3.xyz iqn.2001-04.com.example:storage.disk4.sys3.xyz iqn.2001-04.com.example:storage.disk5.sys3.xyz iqn.2001-04.com.example:storage.disk3.sys3.xyz iqn.2001-04.com.example2:storage.disk2.sys3.xyz iqn.2001-04.com.example2:storage.disk3.sys3.xyz iqn.2001-04.com.example2:storage.disk4.sys3.xyz iqn.2001-04.com.example2:storage.disk5.sys3.xyz Discovery Address -----------------192.168.2.14:3260 192.168.2.14:3260 192.168.2.14:3260 192.168.2.14:3260 192.168.2.15:3260 192.168.2.15:3260 192.168.2.15:3260 192.168.2.15:3260 State Disk ----- ----ONLINE disk_0 ONLINE disk_2 ONLINE disk_3 ONLINE ONLINE ONLINE ONLINE ONLINE disk_1 disk_4 disk_5 disk_6 disk_7
117
To display the iSCSI target details
To display the iSCSI target details, enter the following:

Storage> iscsi target listdetail target
where target is the name of the node you want to display the details for. For example:
Storage> iscsi target listdetail iqn.2001-04.com.example: storage.disk2.sys3.xyz Discovery Address : 192.168.2.14:3260 Connections =========== Portal Address sfs_01 sfs_02 ---------------------192.168.2.14:3260,1 2 2
To add an iSCSI target
To add an iSCSI target, enter the following:

Storage> iscsi target add target-name portal-address target-name Name of the iSCSI target at which SCSI LUNs are available. target-name should conform to the naming rules defined in RFC3721. The location where the target is accessible.
portal-address
For example:
Storage> iscsi target add iqn.2001-04.com.example: storage.disk2.sys1.xyz 192.168.2.14:3260 Logging into target iqn.2001-04.com.example: storage.disk2.sys1.xyz Storage> iscsi target listdetail iqn.2001-04.com.example: storage.disk2.sys1.xyz Connections =========== Portal Address sfs55_01 --------------------192.168.2.14:3260,1 1
sfs55_02 -------1
118
To delete an iSCSI target
To delete an iSCSI target, enter the following:

Storage> iscsi target del target-name {discovery-address|portal-address} target-name Name of the iSCSI target at which SCSI LUNs are available. target-name should conform to the naming rules defined in RFC3721.
discovery-address Target address at which an initiator can request a list of targets using a SendTargets text request as specified in iSCSI protocol of RFC3720. If no port is specified with the discovery address, default port 3260 is used. portal-address The location where the target is accessible.
For example:
Storage> iscsi target del iqn.2001-04.com.example: storage.disk2.sys3.xyz
To login to an iSCSI target
To login to an iSCSI target, enter the following:

Storage> iscsi target login target-name {discovery-address | portal-address} target-name Name of the iSCSI target at which SCSI LUNs are available. target-name should conform to the naming rules defined in RFC3721.
For example:
Storage> iscsi target login iqn.2001-04.com.example: storage.disk2.sys3.xyz
Configuring storage About data archive and retention (DAR)
119
To logout from an iSCSI target
To logout from an iSCSI target, enter the following:

Storage> iscsi target logout target-name {discovery-address | portal-address} target-name Name of the iSCSI target at which SCSI LUNs are available. target-name should conform to the naming rules defined in RFC3721.
For example:
Storage> iscsi target logout iqn.2001-04.com.example: storage.disk2.sys3.xyz
About data archive and retention (DAR)

The FileStore data archive and retention feature enables you to create WORM (write once, read many)-enabled file systems for data archiving. DAR-enabled file systems are protected against accidental or deliberate file removal and tampering. This feature is important for installations that must meet corporate requirements to ensure that data is archived reliably and securely over a long period of time. Once a file system is created in FileStore, you can use the Storage> dar command to mark the file system as DAR-enabled and specify the minimum, maximum, and default retention times for WORM files in the archive. After a file system is DAR-enabled, you can use Symantec Enterprise Vault to configure a file as WORM and specify a specific retention time. Marking a file system as DAR-enabled and setting the range of retention times is controlled by FileStore. Marking a file as a WORM file and choosing a retention time for the file are controlled by the Enterprise Vault. Retention times set for the file must be compatible with the minimum and maximum retention times configured by the Storage> dar enable command. If no retention time is set, the default FileStore retention time is used.
120
Configuring storage About data archive and retention (DAR)
FileStore enforces the immutability of WORM files until their retention date is reached. Once their retention dates have passed, these files can be deleted or the retention date extended. Otherwise, no other operations are allowed on the files. To use the data archive and retention feature:
You must purchase a FileStore license for the feature. The license is based on the amount of disk space you plan to use for data archive and retention. After you purchase a license, use the Storage> dar licenseset command to specify the amount of disk space you are licensed to use. Currently, DAR is only supported for Symantec Enterprise Vault environments. When you configure Enterprise Vault to work with FileStore make sure you configure Enterprise Vault to be the only "user" of the exported DAR-enabled shares. You must have an Network Time Protocol (NTP) server enabled and configured. See About coordinating cluster nodes to work with NTP servers on page 453. When you use the CIFS> share add command to add a CIFS share for a DAR-enabled file system, make sure you include the no_full_acl export option. If you do not set this option, you cannot change a file to WORM through CIFS. See About the CIFS export options on page 284.
You can use Report > audit commands to configure audit logs for DAR-enabled file systems. See About audit logs on page 387. System and audit log entries for DAR-related operations can include (but are not limited to) the following:

Attempts to modify the data (or metadata) of a WORM file Attempts to increment (or decrement) the retention date Attempts to delete a DAR-enabled file system Attempts to modify the system clock DAR commands Definition
Sets the licensed disk space capacity for all DAR-enabled file systems. See Configuring data archive and retention on page 123.
Table 4-11 Command

dar licenseset
Configuring storage How DAR interacts with other FileStore applications
121
Table 4-11 Command

dar show
DAR commands (continued) Definition

Shows the licensed disk space capacity for all DAR-enabled file systems. This includes the amount of currently-used disk space and the amount of available disk space. See Configuring data archive and retention on page 123.
dar enable
Marks a file system as DAR-enabled and sets the minimum, maximum, and default retention times for files in the archive. See Configuring data archive and retention on page 123.
dar list
Displays a list of DAR-enabled file systems, associated retention times, and retention options. See Configuring data archive and retention on page 123.
How DAR interacts with other FileStore applications

The FileStore data archive and retention feature is designed and optimized to work with Enterprise Vault. It supports the current version of Enterprise Vault and is compatible with earlier versions of Enterprise Vault. In general, other FileStore features and applications preserve both the WORM data and metadata when accessing and performing operations on files in a DAR-enabled file system, but there are some exceptions. See Table 4-12 for details. Note: For the latest information on how DAR interacts with other applications, see the Symantec FileStore Release Notes. Table 4-12 Feature or Application
AntiVirus
Application support for data archive and retention Description

AntiVirus can overwrite DAR protection. If a file is suspected to be infected, AntiVirus can remove the file even if the file is marked WORM.
122
Configuring storage How DAR interacts with other FileStore applications
Table 4-12 Feature or Application

Backup
Application support for data archive and retention (continued) Description

Data archive and retention works with the NDMP client and NetBackup. The NDMP client preserves both the WORM data and metadata when accessing and performing backup operations on files in a DAR-enabled file system. For NetBackup client, use pathname /_vxfs_private_/fs_name (instead of /vx/fs_name) to restore DAR-enabled files.
CIFS
DAR-enabled file systems can be accessed over CIFS. However, DAR-enabled files systems cannot be used for CIFS home directories. Currently, commands and operations to create and manage DAR-enabled file systems are available in the FileStore CLI, but not in the FileStore Management Console. Transfer of files between the storage tiers works as expected (transparent to DAR). DST removal policies cannot remove WORM files. The FTP service cannot be used on DAR-enabled file systems. Currently, DAR-enabled files systems cannot be accessed over NFS. You must have an Network Time Protocol (NTP) server enabled and configured to use data archive and retention. DAR-enabled file systems are supported as a replication source, but not as a replication target. Data from a normal (not DAR-enabled) share cannot be promoted or migrated into an existing or new DAR-enabled share. Snapshots can be mounted and promoted for DAR-enabled file systems: A warning message appears when a snapshot of a DAR-enabled file system is mounted. You can restore a snapshot of a DAR-enabled file system, but you may lose data stored after the snapshot was taken. A warning message appears before the restore occurs. Snapshot-based backups that use the NetBackup client type VxFS_Checkpoint do not work with DAR-enabled file systems.
CLI and Management Console DST
FTP NFS NTP
Replication
Snapshot
Configuring storage Configuring data archive and retention
123
Configuring data archive and retention

To license a DAR-enabled file system
To set the licensed disk capacity for all DAR-enabled file systems, enter the following:
Storage> dar licenseset disk_size
where disk_size is the amount of disk space you have licensed. Disk capacity can be specified as T (terabyte), G (gigabytes), or M (megabytes). For example:
Storage> dar licenseset 10G
To show the licensed disk capacity for a DAR-enabled file system
To show the licensed disk capacity for all DAR-enabled file systems, enter the following:
Storage> dar show Licensed: 10G Used: 5.1G Available: 4.90G Used%: 51%
To create a DAR-enabled file system
Use the Storage> fs create command to create an empty file system. You can create a new file system and then enable it for data archive and retention. For example:
Storage> fs create simple fs1 1G pool1 100% [#] Creating simple file system
Use the Storage> dar enable command to enable the file system for data archive and retention.
Storage> dar enable fs_name [def_retent] [min_retent] [max_retent] [retent_opt] fs_name Name of the file system you want to enable for data archive and retention. Once a file system is marked DAR-enabled, you can not remove this setting.
124
def_retent
Specifies the default data retention time (in days) for files in a DAR-enabled file system. Retention times are measured relative to the time the value was set. Valid values are:

number - the number of days inf - infinite retention time
If you do not specify a default data retention time, the default is 365 days (1 year). min_retent Specifies the minium data retention time for files in a DAR-enabled file system. Retention times are measured relative to the time the value was set. Valid values are:

If you do not specify a minimum data retention time, the default is 0 days. max_retent Specifies the maximum data retention time for files in a DAR-enabled file system. Retention times are measured relative to the time the value was set. Valid values are:

If you do not specify a maximum data retention time, the default is 10950 days (30 years). retent_opt Specifies optional retention values. Choices include: incret | noincret If the option is incret, you can increase (increment) data retention times. If the option is noincret, you cannot increase data retention times. decret | nodecret If the option is decret, you can decrease (decrement) data retention times. If the option is nodecret, you cannot decrease data retention times.
To enter more than one retention option, use a comma to separate the values. For example, incret,decret. By default, the options are incret,nodecret.
125
For example:
Storage> dar enable fs1 95 1 365 incret,decret
Note: An error message appears, if you try to use the Storage> dar enable command on a file system in any of the following states: NFS shared, CIFS shared, FTP shared, or Non-empty. Listing DAR-enabled file systems
Storage> dar list DAR Enabled FS STATUS ============== ====== fs1 fs3 fs4
To list DAR-enabled files systems, enter the following:
DEF RETENTION =============
MIN RETENTION ============= 1 days 0 days
MAX RETENTION ============= 365 days 10950 days
RETENTION OPTIONS ================= INC_RETN,DEC_RETN INC_RETN
Online 95 days Offline Online 365 days
To delete a DAR-enabled file system
To delete a DAR-enabled file system, enter the following:

Storage> fs destroy fs_name
where fs_name is the name of the file system you want to delete. For example:
Storage> fs destroy fs1 SFS FS WARNING V-288-0 fs1 is DAR enabled SFS FS WARNING V-288-0 Are you sure you want to destroy? (yes/no)
You must use the Storage> fs destroy CLI command to delete a DAR-enabled file system. You cannot use the Destroy option on the File System page of the FileStore Management Console.
126
Chapter
Configuring Symantec FileStore network settings


About network mode commands Displaying the network configuration and statistics About bonding Ethernet interfaces Bonding Ethernet interfaces About DNS Configuring DNS settings About IP commands About configuring IP addresses Configuring IP addresses About configuring Ethernet interfaces Displaying current Ethernet interfaces and states Configuring Ethernet interfaces About configuring routing tables Configuring routing tables About LDAP Before configuring LDAP settings
128
Configuring Symantec FileStore network settings About network mode commands
About configuring LDAP server settings Configuring LDAP server settings About administering FileStore cluster's LDAP client Administering the FileStore cluster's LDAP client About NIS Configuring the NIS-related commands About NSS Configuring NSS lookup order About VLAN interfaces Configuring VLAN interfaces
About network mode commands

FileStore network-mode commands let you specify and check the status of network parameters for the FileStore cluster. Note: Before you use FileStore network mode commands, you must have a general understanding of IP addresses and networking. If you are not familiar with the terms or output, contact your Network Administrator for help. As shown in Table 5-1, network node commands are organized into functional groups or submodes. To access the commands, log into your administrative console (master, system-admin, or storage-admin) and enter Network> mode. See About using the FileStore command-line interface on page 33. Table 5-1 Network submode
Bond
Network submodes Function

Creates a logical association between two or more Ethernet interfaces. See About bonding Ethernet interfaces on page 130.
DNS
Identifies the DNS parameters that the FileStore cluster can use. See About DNS on page 133.
Configuring Symantec FileStore network settings Displaying the network configuration and statistics
129
Table 5-1 Network submode

IP
Network submodes (continued) Function

Manages the FileStore cluster IP addresses. See About IP commands on page 137.
LDAP
Identifies the LDAP parameters that the FileStore cluster can use. See About LDAP on page 151.
NIS
Identifies the NIS parameters that the FileStore cluster can use. See About NIS on page 160.
NSS
Provides a single configuration location to identify the services (such as NIS or LDAP) for network information such as hosts, groups, or passwords. See About NSS on page 163.
VLAN
Views, adds, or deletes VLAN interfaces. See About VLAN interfaces on page 165.
Displaying the network configuration and statistics

You can use the Network> show command to display the current cluster configuration and related statistics of the cluster network configuration.
130
Configuring Symantec FileStore network settings About bonding Ethernet interfaces
To display the network configuration and statistics
To display the cluster's network configuration and statistics, enter the following:
Network> show Interface Statistics -------------------sfs_01 ------------Interfaces MTU Metric lo 16436 1 priveth0 1500 1 priveth1 1500 1 pubeth0 1500 1 pubeth1 1500 1 TX-OK 13766 953273 506641 152817 673 TX-DROP 0 0 0 0 0 TX-ERR 0 0 0 0 0
RX-OK 13766 452390 325940 25806318 25755262 Flag LRU BMR BMRU BMRU BMRU
RX-DROP 0 0 0 0 0
RX-ERR 0 0 0 0 0
RX-FRAME 0 0 0 0 0
TX-CAR 0 0 0 0 0
Routing Table ------------sfs_01 ------------Destination Gateway 172.27.75.0 0.0.0.0 10.182.96.0 0.0.0.0 10.182.96.0 0.0.0.0 127.0.0.0 0.0.0.0 0.0.0.0 10.182.96.1 Genmask 255.255.255.0 255.255.240.0 255.255.240.0 255.0.0.0 0.0.0.0 Flags MSS Window irtt Iface U 0 0 0 priveth0 U 0 0 0 pubeth0 U 0 0 0 pubeth1 U 0 0 0 lo UG 0 0 0 pubeth0
See Configuring routing tables on page 148.
About bonding Ethernet interfaces

Bond commands associate each set of two or more Ethernet interfaces with one IP address. This association improves network performance on each FileStore cluster node by increasing the potential bandwidth available on an IP address beyond the limits of a single Ethernet interface and by providing redundancy for higher availability. For example, you can bond two 1-gigabit Ethernet interfaces
Configuring Symantec FileStore network settings About bonding Ethernet interfaces
131
together to provide up to 2 gigabits per second of throughput to a single IP address. Moreover, if one of the interfaces fails, communication continues using the single Ethernet interface. Bond commands let you create, remove, and display a cluster's bonds. When you create or delete a bond, it affects the corresponding Ethernet interfaces on the FileStore cluster nodes. You can only bond public Ethernet interfaces. Note: When you create or remove a bond, SSH connections with Ethernet interfaces involved in that bond may be dropped. When the operation is complete, you must restore the SSH connections. Table 5-2 Command
show
Bond commands Definition

Displays a bond and its type used to distribute traffic among the bonded interfaces. See Bonding Ethernet interfaces on page 132.
create
Creates a bond between sets of two or more named Ethernet interfaces on all FileStore cluster nodes. See Bonding Ethernet interfaces on page 132.
remove
Removes a bond between two or more named Ethernet interfaces on all FileStore cluster nodes. See Bonding Ethernet interfaces on page 132.
132
Configuring Symantec FileStore network settings Bonding Ethernet interfaces
Bonding Ethernet interfaces

To display a bond
To display a bond and the algorithm used to distribute traffic among the bonded interfaces, enter the following:
Network> bond show
In this example, DEVICES refers to Ethernet interfaces.

Network> bond show BONDNAME -------bond0 MODE ---active-backup DEVICES ------pubeth1 pubeth2
To create a bond
To create a bond between sets of two or more Ethernet interfaces on all FileStore cluster nodes, enter the following:
Network> bond create interfacelist mode interfacelist Specifies a comma-separated list of public Ethernet interfaces to bond. Specifies how the bonded Ethernet interfaces divide the traffic.
mode
For example:
Network> bond create pubeth1,pubeth2 broadcast 100% [#] Bonding interfaces. Please wait... bond created, the bond name is: bond0
You can specify a mode either as a number or a character string, as follows:

0 balance-rr This mode provides fault tolerance and load balancing. It transmits packets in order from the first available slave through the last. Only one slave in the bond is active. If the active slave fails, a different slave becomes active. To avoid confusing the switch, the bond's MAC address is externally visible on only one port (network adapter).
active-backup
Configuring Symantec FileStore network settings About DNS
133
balance-xor
Transmits based on the selected transmit hash policy. The default policy is a simple. This mode provides load balancing and fault tolerance. You can use the xmit_hash_policy option to select alternate transmit policies.
broadcast
Transmits everything on all slave interfaces and provides fault tolerance. Creates aggregation groups with the same speed and duplex settings. It uses all slaves in the active aggregator based on the 802.3ad specification. Provides channel bonding that does not require special switch support. The outgoing traffic is distributed according to the current load (computed relative to the speed) on each slave. The current slave receives incoming traffic. If the receiving slave fails, another slave takes over its MAC address. Includes balance-tlb plus Receive Load Balancing (RLB) for IPV4 traffic. This mode does not require any special switch support. ARP negotiation load balances the receive.
802.3ad
balance-tlb
balance-alb
To remove a bond
To remove a bond from all of the nodes in a cluster, enter the following:
Network> bond remove bondname
where bondname is the name of the bond configuration. For example:

Network> bond remove bond0 100% [#] Removing Bond bond0. Please wait... bond removed : bond0
About DNS
The Domain Name System (DNS) service translates between numeric IP addresses and their associated host names. The DNS commands let you view or change a FileStore cluster's DNS settings. You can configure a FileStore cluster's DNS lookup service to use up to three DNS
134
Configuring Symantec FileStore network settings About DNS
servers. You must enable the FileStore cluster's DNS name service before you specify the DNS servers to use for lookups. Table 5-3 Command
dns show
DNS commands Definition

Displays the current settings of the FileStore cluster's DNS lookup service. See Configuring DNS settings on page 135.
dns enable
Enables FileStore to perform DNS lookups. When DNS is enabled, the FileStore cluster's DNS service uses the data center's DNS server(s) to determine the IP addresses of network entities such as SNMP, NTP, LDAP, and NIS servers with which the cluster must communicate. See Configuring DNS settings on page 135.
dns disable
Disables DNS lookups. See Configuring DNS settings on page 135.
dns set nameservers
Specifies the IP addresses of DNS name servers to be used by the FileStore DNS lookup service. The order of the IP addresses is the order in which the name servers are to be used. Enter the IP addresses of the name servers. The order of the IP addresses is the order in which the name servers are to be used. See Configuring DNS settings on page 135.
dns clear nameservers
Removes the IP addresses of DNS name servers from the cluster's DNS lookup service database. See Configuring DNS settings on page 135.
dns set domainname
Enter the domain name that the FileStore cluster will be in. For the required information, contact your Network Administrator. This command clears any previously set domain name. Before you use this procedure, you must enable the DNS server. See Configuring DNS settings on page 135.
dns clear domainname
Removes the DNS domain name. See Configuring DNS settings on page 135.
Configuring Symantec FileStore network settings Configuring DNS settings
135
Configuring DNS settings

To display DNS settings
To display DNS settings, enter the following:

Network> dns show DNS Status : Disabled nameserver : 172.16.113.118 domain : symantec.com
To enable DNS settings
To enable DNS settings to allow FileStore hosts to do lookups and verify the results, enter the following commands:
Network> dns enable Network> Network> dns show DNS Status : Enabled domain : cluster1.com nameserver : 10.216.50.132
To disable DNS settings
To disable DNS settings, enter the following:

Network> dns disable Network> Network> dns show DNS Status : Disabled Old Settings -----------domain : cluster1.com nameserver : 10.216.50.132
136
Configuring Symantec FileStore network settings Configuring DNS settings
To specify IP addresses of DNS name servers
To specify the IP addresses of DNS name servers to be used by the FileStore DNS service and verify the results, enter the following commands:
Network> dns set nameservers nameserver1 [nameserver2] [nameserver3]
For example:
Network> dns set nameservers 10.216.50.199 10.216.50.200 Network> Network> dns show DNS Status : Enabled nameserver : 10.216.50.199 nameserver : 10.216.50.200
To remove name servers list used by DNS
To remove the name servers list used by DNS and verify the results, enter the following commands:
Network> dns clear nameservers Network> Network> dns show DNS Status : Enabled
To set the domain name for the DNS server
To set the domain name for the DNS server, enter the following:
Network> dns set domainname domainname
where domainname is the domain name for the DNS server. For example:
Network> dns set domainname example.com Network> Network> dns show DNS Status : Enabled domain : example.com nameserver : 10.216.50.132
Configuring Symantec FileStore network settings About IP commands
137
To remove domain name used by DNS
To remove the domain name used by DNS, enter the following:

Network> dns clear domainname Network> Network> dsn show DNS Status : Enabled nameserver : 10.216.50.132
About IP commands
Internet Protocol (IP) commands configure your routing tables, Ethernet interfaces, and IP addresses, and display the settings. The following sections describe how to configure the IP commands:

See About configuring IP addresses on page 137. See About configuring Ethernet interfaces on page 143. See About configuring routing tables on page 146.
About configuring IP addresses

Each Ethernet interface must have a physical IP address associated with it. These are usually supplied when the FileStore software is installed. Each Ethernet interface also requires one or more virtual IP addresses to communicate with other cluster nodes and with the rest of the network. Table 5-4 lists the commands you can use to configure your IP addresses. Table 5-4 Command
ip addr show
IP commands Definition
Displays the IP addresses, the devices (Ethernet interfaces) they are assigned to, and their attributes.
Note: Any Ethernet interfaces excluded during the initial FileStore

installation will not be displayed. See Configuring IP addresses on page 139.
138
Configuring Symantec FileStore network settings About configuring IP addresses
Table 5-4 Command

ip addr add
IP commands (continued) Definition

Adds a virtual or physical IP address to the FileStore cluster. FileStore assigns the newly added IP address to an Ethernet interface or one of its nodes. Virtual IP addresses are used for communication among cluster nodes and with clients on the enterprise network. By default, this command does not use VLAN Ethernet interfaces unless they are specified in the device option. FileStore determines the node to which the IP address will be assigned. After you add a virtual IP address, it takes a few seconds for it to come online. If you enter an IP address that is already used in the cluster, an error message is displayed. You cannot enter an invalid IP address (one that is not four bytes or has a byte value greater than 255).
Note: An IP address that does not go online may indicate a problem

with the FileStore cluster. For help, use the Support> services command, or contact Symantec Technical Support. See Using the services command on page 515. See Configuring IP addresses on page 139. ip addr online Brings an IP address online on any running node in the cluster. The IP address does not need to be in the offline mode for this command to work. You can use this command to switch the IP address from an online node to another specified node. You can change an IP address to the online mode if it is in the OFFLINE/FAULTED state. This command also displays any faults for the IP address on the specified node.
Note: An IP address that does not go online may indicate a problem

with the FileStore cluster. For help, use the Support> services command, or contact Symantec Technical Support. See Using the services command on page 515. See Configuring IP addresses on page 139. ip addr modify Modifies an IP protocol address used by the cluster. You can change both the physical IP addresses and virtual IP addresses. If you change the virtual IP address it terminates the NFS connection on oldipaddr. See Configuring IP addresses on page 139.
Configuring Symantec FileStore network settings Configuring IP addresses
139
Table 5-4 Command

ip addr del
IP commands (continued) Definition

Deletes an IP protocol address from the cluster. You can delete physical IP addresses only if they are not being used by any interface of the cluster. You can also delete virtual IP addresses, except for the console IP address. When you add or delete an IP address from the cluster, the cluster automatically evens out the number of virtual IP addresses on each node. See Configuring IP addresses on page 139.
Configuring IP addresses
To configure your IP addresses, perform the following commands. To display all the IP addresses for the cluster
To display all of a cluster's IP addresses, enter the following:

Network> ip addr show IP Netmask -------10.182.107.53 255.255.240.0 10.182.107.54 255.255.240.0 10.182.107.55 255.255.240.0 10.182.107.56 255.255.240.0 10.182.107.65 255.255.240.0 10.182.107.201 255.255.240.0 10.182.107.202 255.255.240.0 10.182.107.203 255.255.240.0 10.182.107.204 255.255.240.0
Device -----pubeth0 pubeth1 pubeth0 pubeth1 pubeth0 pubeth0 pubeth0 pubeth1 pubeth1
Node ---sfs_1 sfs_1 sfs_2 sfs_2 sfs_1 sfs_2 sfs_1 sfs_2 sfs_1
Type ---Physical Physical Physical Physical Virtual Virtual Virtual Virtual Virtual
Status ------
ONLINE (Con IP) ONLINE ONLINE ONLINE ONLINE
The output headings are:

IP Netmask Device Node Type Displays the IP addresses for the cluster. Displays the netmask for the IP address. Displays the name of the Ethernet interface for the IP address. Displays the node name associated with the interface. Displays the type of the IP address: physical or virtual.
140
Status
Displays the status of the IP addresses:

ONLINE ONLINE (console IP) OFFLINE FAULTED
A virtual IP can be in the FAULTED state if it is already being used. It can also be in the FAULTED state if the corresponding device is not working on all nodes in the cluster (for example, a disconnected cable).
141
To add an IP address to a cluster
To add an IP address to a cluster, enter the following:

Network> ip addr add ipaddr netmask type [device] ipaddr Specifies the IP address to add to the cluster. Do not use physical IP addresses to access the FileStore cluster. In case of failure, the IP addresses cannot move between nodes. A failure could be either a node failure, an Ethernet interface failure, or storage failure. netmask type device Specifies the netmask for the IP address. Specifies the IP type, either virtual or physical. Only use this option if you entered virtual for the type.
For example, to add a virtual IP address on a normal device, enter the following:
Network> ip addr add 10.10.10.10 255.255.255.0 virtual pubeth0 SFS ip addr Success V-288-0 ip addr add successful.
For example, to add a virtual IP address on a bond device, enter the following:
Network> ip addr add 10.10.10.10 255.255.255.0 virtual bond0 SFS ip addr Success V-288-0 ip addr add successful.
For example, to add a virtual IP address on a VLAN device created over a normal device with VLAN ID 3, enter the following:
Network> ip addr add 10.10.10.10 255.255.255.0 virtual pubeth0.3 SFS ip addr Success V-288-0 ip addr add successful.
For example, to add a virtual IP address on a VLAN device created over a bond device with VLAN ID 3, enter the following:
Network> ip addr add 10.10.10.10 255.255.255.0 virtual bond0.3 SFS ip addr Success V-288-0 ip addr add successful.
142
To change an IP address to the online mode on a specified node
To change an IP address to the online mode on a specified node, enter the following:
Network> ip addr online ipaddr nodename ipaddr nodename Specifies the IP address that needs to be brought online. Specifies the nodename on which the IP address needs to be brought online. If you do not want to enter a specific nodename, enter any with the IP address.
For example:
Network> ip addr online 10.10.10.15 node5_2 Network> ip addr show IP Netmask Device Node ---------------10.216.114.212 255.255.248.0 pubeth0 node5_1 10.216.114.213 255.255.248.0 pubeth1 node5_1 10.216.114.214 255.255.248.0 pubeth0 node5_2 10.216.114.215 255.255.248.0 pubeth1 node5_2 10.216.114.217 255.255.248.0 pubeth0 node5_1 10.10.10.10 255.255.248.0 pubeth0 node5_1 10.10.10.11 255.255.248.0 pubeth1 node5_1 10.10.10.12 255.255.248.0 pubeth0 node5_2 10.10.10.13 255.255.248.0 pubeth1 node5_2 10.10.10.15 255.255.248.0 pubeth0 node5_2
Type ---Physical Physical Physical Physical Virtual Virtual Virtual Virtual Virtual Virtual
Status ------
ONLINE (Con IP) ONLINE ONLINE ONLINE ONLINE ONLINE
Configuring Symantec FileStore network settings About configuring Ethernet interfaces
143
To modify an IP address
To modify an IP address, enter the following:

Network> ip addr modify oldipaddr newipaddr netmask oldipaddr newipaddr netmask Specifies the old IP address to be modified. Specifies what the new IP address will be. Specifies the netmask for the new IP address.
If the specified oldipaddr is not assigned to the cluster, an error message is displayed. If you enter an invalid IP address (one that is not four bytes or has a byte value greater than 255), an error message is displayed. If the new IP address is already being used, an error message is displayed. For example:
Network> ip addr modify 10.10.10.15 10.10.10.16 255.255.240.0 SFS ip addr Success V-288-0 ip addr modify successful.
To remove an IP address from the cluster
To remove an IP address from the cluster, enter the following:

Network> ip addr del ipaddr
where ipaddr is the IP address to remove from the cluster. For example:
Network> ip addr del 10.10.10.15 SFS ip addr Success V-288-0 ip addr del successful.
About configuring Ethernet interfaces

You can display and change the public Ethernet interfaces (for example, pubeth0 and pubeth1) whether a link is up or down, and the Ethernet interface's Maximum Transmission Unit (MTU) value.
144
Configuring Symantec FileStore network settings Displaying current Ethernet interfaces and states
Table 5-5 Command

ip link show
Ethernet interface commands Definition

Displays each Ethernet interface's (device) status, if it connected to each node in the cluster, the speed, MTU, and MAC address.
Note: Any Ethernet interfaces excluded during the initial FileStore

installation are not displayed. See Displaying current Ethernet interfaces and states on page 144. ip link set Changes the network Ethernet interface's attributes or states. See Configuring Ethernet interfaces on page 145.
Displaying current Ethernet interfaces and states

To display current Ethernet interfaces and states
To display current configurations, enter the following:

Network> ip link show [nodename] [device] nodename Specifies which node of the cluster to display the attributes. Enter all to display all IP links. device Specifies which Ethernet interface on the node to display the attributes.
Network> ip link show sfs_1 pubeth0 Nodename -------sfs_01 Device Status ------ -----pubeth0 UP MTU Detect --- -----1500 yes Speed HWaddr ------ -----100Mb/s 00:0c:29:a8:9d:f3
To display all configurations, enter the following:

Network> ip link show Nodename -------sfs_01 sfs_01 sfs_02 sfs_02 Device Status ------ -----pubeth0 UP pubeth1 UP pubeth0 UP pubeth1 UP MTU Detect --- -----1500 yes 1500 yes 1500 yes 1500 yes Speed -----100Mb/s 100Mb/s 100Mb/s 100Mb/s HWaddr -----00:0c:29:a8:9d:f3 00:0c:29:a8:9d:fd 00:0c:29:da:c9:e2 00:0c:29:da:c9:ec
Configuring Symantec FileStore network settings Configuring Ethernet interfaces
145
Configuring Ethernet interfaces

To change an Ethernet interface
To change an Ethernet interface's configuration, enter the following:

Network> ip link set nodename device operation [argument] nodename Specifies which node of the cluster to configure. If the node specified is not part of the cluster, then an error message is displayed. To configure all nodes at once, use the all option in the nodename field. device Specifies the Ethernet interface to configure. If you enter an Ethernet interface that cannot be configured, an error message is displayed. operation Enter one of the following operations:

up - Brings the Ethernet interface online. down - Brings the Ethernet interface offline. mtu MTU - Changes the Ethernet interface's Maximum Transmission Unit (MTU) to the value that is specified in the argument field.
argument
The argument field is used only when you enter mtu in the operation field. Setting the incorrect MTU value causes the console IP to become unavailable. The argument field specifies what the MTU of the specified Ethernet interface on the specified node should be changed to. The MTU value must be an unsigned integer between 46 and 9216. If you enter the argument field, but do not enter an MTU in the operation field, the argument is ignored.
Network> ip link set all pubeth0 mtu 1600 sfs_01 : mtu updated on pubeth0 sfs_02 : mtu updated on pubeth0 Network> ip link show
146
Configuring Symantec FileStore network settings About configuring routing tables
Nodename -------sfs_01 sfs_01 sfs_02 sfs_02
Device Status ------ -----pubeth0 UP pubeth1 UP pubeth0 UP pubeth1 UP
MTU Detect --- -----1600 yes 1500 yes 1600 yes 1500 yes
Speed -----100Mb/s 100Mb/s 100Mb/s 100Mb/s
HWaddr -----00:0c:29:a8:9d:f3 00:0c:29:a8:9d:fd 00:0c:29:da:c9:e2 00:0c:29:da:c9:ec
About configuring routing tables

Sometimes an FileStore cluster must communicate with network services (for example, LDAP) using specific gateways in the public network. In these cases, you must define routing table entries. These entries consist of the following:

The target network node's IP address and accompanying netmask. Gateways IP address. Optionally, a specific Ethernet interface via which to communicate with the target. This is useful, for example, if the demands of multiple remote clients are likely to exceed a single gateways throughput capacity.
You add or remove routing table entries using the Network> mode ip route command. Table 5-6 lists the commands used to configure the routing tables of the nodes in the cluster. Table 5-6 Command
route show
Routing table commands Definition

Displays the routing table of the nodes in the cluster. You can enter a specific nodename or use all to display the routing tables for all nodes in the cluster. See Configuring routing tables on page 148.
Configuring Symantec FileStore network settings About configuring routing tables
147
Table 5-6 Command

route add
Routing table commands (continued) Definition

Adds a new route for the cluster. The routing table contains information about paths to other networked nodes. You can make routing table changes on each node of the cluster. Use all for the nodename to add the route to all of the nodes in the cluster. Use a netmask value of 255.255.255.255 for the netmask to add a host route to ipaddr. Use a value of 0.0.0.0 for the gateway to add a route that does not use any gateway. The dev device is an optional argument. Use any of the public Ethernet interfaces for the device, for example, pubeth0, pubeth1, or any. See Configuring routing tables on page 148.
route del
Deletes a route used by the cluster. Use all for nodename to delete the route from all of the nodes in the cluster. The combination of ipaddr and netmask specifies the network or host for which the route is deleted. Use a value of 255.255.255.255 for the netmask to delete a host route to ipaddr. See Configuring routing tables on page 148.
148
Configuring Symantec FileStore network settings Configuring routing tables
Configuring routing tables

To display the routing tables of the nodes in the cluster
To display the routing tables of the nodes in the cluster, enter the following:
Network> ip route show [nodename]
where nodename is the node whose routing tables you want to display. To see the routing table for all of the nodes in the cluster, enter all. For example:
Network> ip route show all sfs_01 ------------Destination Gateway 172.27.75.0 0.0.0.0 10.182.96.0 0.0.0.0 10.182.96.0 0.0.0.0 127.0.0.0 0.0.0.0 0.0.0.0 10.182.96.1 sfs_02 ------------Destination Gateway 172.27.75.0 0.0.0.0 10.182.96.0 0.0.0.0 10.182.96.0 0.0.0.0 127.0.0.0 0.0.0.0 0.0.0.0 10.182.96.1
Genmask 255.255.255.0 255.255.240.0 255.255.240.0 255.0.0.0 0.0.0.0
Flags MSS Window irtt Iface U 0 0 0 priveth0 U 0 0 0 pubeth0 U 0 0 0 pubeth1 U 0 0 0 lo UG 0 0 0 pubeth0
Genmask 255.255.255.0 255.255.240.0 255.255.240.0 255.0.0.0 0.0.0.0
Flags MSS Window irtt Iface U 0 0 0 priveth0 U 0 0 0 pubeth0 U 0 0 0 pubeth1 U 0 0 0 lo UG 0 0 0 pubeth0
Destination
Displays the destination network or destination host for which the route is defined. Displays a network node equipped for interfacing with another network. Displays the netmask.
Gateway
Genmask
149
Flags
The flags are as follows: U - Route is up H - Target is a host G - Use gateway
MSS
Displays maximum segment size. The default is 0. You cannot modify this attribute. Displays the maximum amount of data the system accepts in a single burst from the remote host. The default is 0. You cannot modify this attribute. Displays the initial round trip time with which TCP connections start. The default is 0. You cannot modify this attribute. Displays the interface. On UNIX systems, the device name lo refers to the loopback interface.
Window
irtt
Iface
To add to the route table
To add a route entry to the routing table of nodes in the cluster, enter the following:
Network> ip route add nodename ipaddr netmask via gateway [dev device] nodename Specifies the node to whose routing table the route is to be added. To add a route path to all the nodes, use all in the nodename field. If you enter a node that is not a part of the cluster, an error message is displayed. ipaddr Specifies the destination of the IP address. If you enter an invalid IP address, then a message notifies you before you fill in other fields. netmask Specifies the netmask associated with the IP address that is entered for the ipaddr field. Use a netmask value of 255.255.255.255 for the netmask to add a host route to ipaddr. via This is a required field. You must type in the word.
150
gateway
Specifies the gateway IP address used for the route. If you enter an invalid gateway IP address, then an error message is displayed. To add a route that does not use a gateway, enter a value of 0.0.0.0.
dev dev device
Specifies the route device option. You must type in the word. Specifies which Ethernet interface on the node the route path is added to. This variable is optional. You can specify the following values:

any - Default pubeth0 - Public Ethernet interface pubeth1 - Public Ethernet interface
The Ethernet interface field is required only when you specify dev in the dev field. If you omit the dev and device fields, FileStore uses a default Ethernet interface.
For example:
Network> ip route add sfs_01 10.10.10.10 255.255.255.255 via 0.0.0.0 dev pubeth0 sfs_01: Route added successfully
Configuring Symantec FileStore network settings About LDAP
151
To delete route entries from the routing tables of nodes in the cluster
To delete route entries from the routing tables of nodes in the cluster, enter the following:
Network> ip route del nodename ipaddr netmask nodename Specify the node from which the node is deleted. To delete the route entry from all nodes, use the all option in this field. ipaddr Specifies the destination IP address of the route entry to be deleted. If you enter an invalid IP address a message notifies you before you enter other fields. netmask Specifies the IP address to be used.
For example:
Network> ip route del sfs_01 10.216.128.0 255.255.255.255 sfs_01: Route deleted successfully
About LDAP
The Lightweight Directory Access Protocol (LDAP) is the protocol used to communicate with LDAP servers. The LDAP servers are the entities that perform the service. In FileStore the most common use of LDAP is user authentication. For sites that use an LDAP server for access or authentication, FileStore provides a simple LDAP client configuration interface.
Before configuring LDAP settings

Before you configure FileStore LDAP settings, obtain the following LDAP configuration information from your system administrator:
IP address or host name of the LDAP server. You also need the port number of the LDAP server. Base (or root) distinguished name (DN), for example, cn=employees,c=us. LDAP database searches start here.
152
Configuring Symantec FileStore network settings About configuring LDAP server settings
Bind distinguished name (DN) and password, for example, ou=engineering,c=us. This allows read access to portions of the LDAP database to search for information. Base DN for users, for example, ou=users,dc=com. This allows access to the LDAP directory to search for and authenticate users. Base DN for groups, for example, ou=groups,dc=com. This allows access to the LDAP database, to search for groups. Root bind DN and password. This allows write access to the LDAP database, to modify information, such as changing a user's password. Secure Sockets Layer (SSL). Configures an FileStore cluster to use the Secure Sockets Layer (SSL) protocol to communicate with the LDAP server. Password hash algorithm, for example md5, if a specific password encryption method is used with your LDAP server.
The following sections describe how to configure LDAP:

See Configuring LDAP server settings on page 154. See Administering the FileStore cluster's LDAP client on page 159.
About configuring LDAP server settings

Table 5-7 lists the LDAP commands used to configure the LDAP server settings. Table 5-7 Command
set basedn
LDAP commands Definition

Sets the base DN value for the LDAP server.
Note: Setting the base DN for the LDAP server is required.

See Configuring LDAP server settings on page 154. set server Sets the hostname or IP address for the LDAP server. See Configuring LDAP server settings on page 154. set port Sets the port number for the LDAP server. See Configuring LDAP server settings on page 154.
Configuring Symantec FileStore network settings About configuring LDAP server settings
153
Table 5-7 Command

set ssl
LDAP commands (continued) Definition

Configures an FileStore cluster to use the Secure Sockets Layer (SSL) protocol to communicate with the LDAP server. If your LDAP server does not use SSL for authentication, sets this value to off (the default value). Consult your system administrator for confirmation. If your LDAP server supports SSL, you must set SSL to on. This setting is mandatory. The certificates that are required for SSL are auto-negotiated with the LDAP server when the session is established. See Configuring LDAP server settings on page 154.
set binddn
Sets the bind Distinguished Name (DN) and its password for the LDAP server. This DN is used to bind with the LDAP server for read access. For LDAP authentication, most attributes need read access.
Note: Use the LDAP server password. Contact your Network

Administrator for assistance. See Configuring LDAP server settings on page 154. set rootbinddn Sets the LDAP root bind DN and its password. This DN is used to bind with the LDAP server for write access to the LDAP directory. This setting is not required for authentication. To change some attributes of an LDAP entry, the root bind DN is required. For example, if a root user wants to change a user's password, the root user must have administrative privileges to write to the LDAP directory.
Note: Use the LDAP server password. Contact your Network

Administrator for assistance. See Configuring LDAP server settings on page 154. set users-basedn set groups-basedn Sets the LDAP users, groups, and netgroups base Distinguished Name (DN). PAM/NSS uses this DN to search LDAP groups.
Note: You must set the LDAP users, groups, and netgroups base DN.
set See Configuring LDAP server settings on page 154. netgroups-basedn
154
Configuring Symantec FileStore network settings Configuring LDAP server settings
Table 5-7 Command
LDAP commands (continued) Definition
set password-hash Sets the LDAP password hash algorithm used when you set or change the LDAP user's password. The password is encrypted with the configured hash algorithm before it is sent to the LDAP server and stored in the LDAP directory.
Note: Setting the LDAP password hash algorithm is optional.

See Configuring LDAP server settings on page 154. get Displays the configured LDAP settings. See Configuring LDAP server settings on page 154. clear Clears a configured setting. See Configuring LDAP server settings on page 154.
Configuring LDAP server settings

You can set the LDAP base Distinguished Name (base DN). LDAP records are structured in a hierarchical tree. You access records through a particular path, in this case, a Distinguished Name, or DN. The base DN indicates where in the LDAP directory hierarchy you want to start your search. Note: For FileStore to access an LDAP directory service, you must specify the LDAP server DNS name or IP address. To set the base DN for the LDAP server
To set the base DN for the LDAP server, enter the following:
Network> ldap set basedn value
where value is the LDAP base DN in the following format:

dc=yourorg,dc=com
For example:
Network> ldap set basedn dc=example,dc=com OK Completed
155
To set the LDAP server hostname or IP address
To set the LDAP server hostname or IP address, enter the following:

Network> ldap set server value
where value is the LDAP server hostname or IP address. For example:

Network> ldap set server ldap-server.example.com OK Completed
For example, if you enter an IP address for the value you get the following message:
Network> ldap set server 10.10.10.10 OK Completed
To set the LDAP server port number
To set the LDAP server port number, enter the following:

Network> ldap set port value
where value is the LDAP server port number. For example:

Network> ldap set port 555 OK Completed
To set FileStore to use LDAP over SSL
To set FileStore to use LDAP over SSL, enter the following:

Network> ldap set ssl {on|off}
For example:
Network> ldap set ssl on OK Completed
156
To set the bind DN for the LDAP server
To set the bind DN for the LDAP server, enter the following:
Network> ldap set binddn value
where value is the LDAP bind DN in the following format:

cn=binduser,dc=yourorg,dc=com
The value setting is mandatory. You are prompted to supply a password. You must use your LDAP server password. For example:
Network> ldap set binddn cn Enter password for 'cn': *** OK Completed
To set the root bind DN for the LDAP server
To set the root bind DN for the LDAP server, enter the following:
Network> ldap set rootbinddn value
where value is the LDAP root bind DN in the following format:

cn=admin,dc=yourorg,dc=com
You are prompted to supply a password. You must use your LDAP server password. For example:
Network> ldap set rootbinddn dc Enter password for 'dc': *** OK Completed
157
To set the LDAP users, groups, or netgroups base DN
To set the LDAP users, groups, or netgroups base DN, enter the following:
Network> ldap set users-basedn value Network> ldap set groups-basedn value Network> ldap set netgroups-basedn value users-basedn value Specifies the value for the users-basedn. For example: ou=users,dc=example,dc=com (default)
groups-basedn value
Specifies the value for the groups-basedn. For example: ou=groups,dc=example,dc=com (default)
netgroups-basedn Specifies the value for the netgroups-basedn. For example: value ou=netgroups,dc=example,dc=com (default)
For example:
Network> ldap set users-basedn ou=Users,dc=example,dc=com OK Completed
To set the password hash algorithm
To set the password hash algorithm, enter the following:

Network> ldap set password-hash {clear|crypt|md5}
For example:
Network> ldap set password-hash clear OK Completed
158
Configuring Symantec FileStore network settings About administering FileStore cluster's LDAP client
To display the LDAP configured settings
To display the LDAP configured settings, enter the following:

Network> ldap get {server|port|basedn|binddn|ssl|rootbinddn| users-basedn|groups-basedn|netgroups-basedn|password-hash}
For example:
Network> ldap get server LDAP server: ldap-server.example.com OK Completed
To clear the LDAP setting
To clear the previously configured LDAP setting, enter the following:

Network> ldap clear {server|port|basedn|binddn|ssl|rootbinddn| users-basedn|groups-basedn|netgroups-basedn|password-hash}
For example:
Network> ldap clear binddn OK Completed
About administering FileStore cluster's LDAP client

You can display the Lightweight Directory Access Protocol (LDAP) client configurations. LDAP clients use the LDAPv3 protocol to communicate with the server. Table 5-8 Command
ldap show
LDAP client commands Definition

Displays the FileStore cluster's LDAP client configuration. See Administering the FileStore cluster's LDAP client on page 159.
ldap enable
Enables the LDAP client configuration. See Administering the FileStore cluster's LDAP client on page 159.
ldap disable
Disables the LDAP client configuration. This command stops FileStore from querying the LDAP service. See Administering the FileStore cluster's LDAP client on page 159.
Configuring Symantec FileStore network settings Administering the FileStore cluster's LDAP client
159
Administering the FileStore cluster's LDAP client

To display the LDAP client configuration
To display the LDAP client configuration, enter the following:

Network> ldap show [users|groups|netgroups] users Displays the LDAP users that are available in the Name Service Switch (NSS) database. Displays the LDAP groups that are available in the NSS database. Displays the LDAP netgroups that are available in the NSS database.
groups netgroups
If you do not include one of the optional variables, the command displays all the configured settings for the LDAP client. For example:
Network> ldap show LDAP client is enabled. ======================= LDAP server: LDAP port: LDAP base DN: LDAP over SSL: LDAP bind DN: LDAP root bind DN: LDAP password hash: LDAP users base DN: LDAP groups base DN: LDAP netgroups base DN: OK Completed
ldap_server 389 (default) dc=example,dc=com on cn=binduser,dc=example,dc=com cn=admin,dc=example,dc=com md5 ou=Users,dc=example,dc=com ou=Groups,dc=example,dc=com ou=Netgroups,dc=example,dc=com
160
Configuring Symantec FileStore network settings About NIS
To enable the LDAP client configuration
To enable the LDAP client configuration, enter the following:

Network> ldap enable
For example:
Network> ldap enable
LDAP clients use the LDAPv3 protocol for communicating with the server. Enabling the LDAP client configures the Pluggable Authentication Module (PAM) files to use LDAP. PAM is the standard authentication framework for Linux. To disable the LDAP client configuration
To disable the LDAP client configuration, enter the following:

Network> ldap disable
For example:
Network> ldap disable
LDAP clients use the LDAPv3 protocol for communicating with the server. This command configures the PAM configuration files so that they do not use LDAP.
About NIS
FileStore supports Network Information Service (NIS), implemented in a NIS server, as an authentication authority. You can use NIS to authenticate computers. If your environment uses NIS, enable the NIS-based authentication on the FileStore cluster. Table 5-9 Command
nis show
NIS commands Definition

Displays the NIS server name, domain name, the NIS users, groups, and netgroups that are available in the NIS database. See Configuring the NIS-related commands on page 161.
nis set domainname
Sets the NIS domain name in the FileStore cluster. See Configuring the NIS-related commands on page 161.
Configuring Symantec FileStore network settings Configuring the NIS-related commands
161
Table 5-9 Command
NIS commands (continued) Definition
nis set servername Sets the NIS server name in the FileStore cluster. See Configuring the NIS-related commands on page 161. nis enable Enables the NIS clients in the FileStore cluster. You must set the NIS domain name and NIS server name before you can enable NIS. See Configuring the NIS-related commands on page 161. nis disable Disables the NIS clients in the FileStore cluster. See Configuring the NIS-related commands on page 161.
Configuring the NIS-related commands

To display NIS-related settings
To display NIS-related settings, enter the following:

Network> nis show [users|groups|netgroups] users Displays the NIS users that are available in the FileStore cluster's NIS database. Displays the NIS groups that are available in the FileStore cluster's NIS database. Displays the NIS netgroups that are available in the FileStore cluster's NIS database.
groups
netgroups
For example:
Network> nis show NIS Status : Disabled domain : NIS Server :
162
Configuring Symantec FileStore network settings Configuring the NIS-related commands
To set the NIS domain name on all nodes in the cluster
To set the NIS domain name on the cluster nodes, enter the following:
Network> nis set domainname [domainname]
where domainname is the domain name. For example:

Network> nis domainname domain_1 Setting domainname: "domain_1"
To set NIS server name on all nodes in the cluster
To set the NIS server name on all cluster nodes, enter the following:
Network> nis set servername servername
where servername is the NIS server name. You can use the server's name or IP address. For example:
Network> nis servername 10.10.10.10 Setting NIS Server "10.10.10.10"
To enable NIS clients
To enable NIS clients, enter the following:

Network> nis enable
For example:
Network> nis enable Enabling NIS Client on all the nodes..... Done. Please enable NIS in nsswitch settings for required services.
To view the new settings, enter the following:

Network> nis show NIS Status : Enabled domain : domain_1 NIS Server : 10.10.10.10
Configuring Symantec FileStore network settings About NSS
163
To disable NIS clients
To disable NIS clients, enter the following:

Network> nis disable
For example:
Network> nis disable Disabling NIS Client on all nodes Please disable NIS in nsswitch settings for required services.
About NSS
Name Service Switch (NSS) is an FileStore cluster service which provides a single configuration location to identify the services (such as NIS or LDAP) for network information such as hosts, groups, or passwords. For example, host information may be on an NIS server. Group information may be in an LDAP database. The NSS configuration specifies which network services the FileStore cluster should use to authenticate hosts, users, groups, and netgroups. The configuration also specifies the order in which multiple services should be queried. Table 5-10 Command
nsswitch show
NSS commands Definition

Displays the NSS configuration. See Configuring NSS lookup order on page 164.
nsswitch conf
Configures the order of the NSS services. See Configuring NSS lookup order on page 164.
164
Configuring Symantec FileStore network settings Configuring NSS lookup order
Configuring NSS lookup order

To display the NSS configuration
To display the NSS configuration, enter the following:

Network> nsswitch group: hosts: netgroup: passwd: shadow: show files nis files nis nis files nis files winbind
winbind dns winbind
ldap
ldap
To configure the NSS lookup order
To configure the NSS lookup order, enter the following:

Network> nsswitch conf {group|hosts|netgroups|passed|shadow} value1 [[value2]] [[value3]] [[value4]] group hosts netgroups passed shadow value Selects the group file. Selects the hosts file. Selects the netgroups file. Selects the password. Selects the shadow file. Specifies the following NSS lookup order with the following values:

value1 (required)- { files/nis/winbind/ldap } value2 (optional) - { files/nis/winbind/ldap } value3 (optional) - { files/nis/winbind/ldap } value4 (optional) - { files/nis/winbind/ldap }
For example:
Network> nsswitch conf shadow files ldap Network> nsswitch show group: files nis winbind hosts: files nis dns netgroup: nis passwd: files nis winbind shadow: files ldap
ldap
ldap
Configuring Symantec FileStore network settings About VLAN interfaces
165
To select DNS, you must use the following command:

Network> nsswitch conf hosts nsswitch conf hosts <value1> [value2] [value3] --select hosts file value1 value2 value3 : Choose the type (files) (files) : Type the type (files/nis/dns) [] : Type the type (files/nis/dns) []
About VLAN interfaces

The virtual LAN (VLAN) feature lets you create VLAN interfaces on the FileStore nodes and administer them as any other VLAN interfaces. The VLAN interfaces are created using Linux support for VLAN interfaces. The Network> vlan commands view, add, or delete VLAN interfaces. Table 5-11 Command
vlan show
VLAN commands Definition

Displays the VLAN interfaces. See Configuring VLAN interfaces on page 166.
vlan add
Adds a VLAN interface. See Configuring VLAN interfaces on page 166.
vlan del
Deletes a VLAN interface. See Configuring VLAN interfaces on page 166.
166
Configuring Symantec FileStore network settings Configuring VLAN interfaces
Configuring VLAN interfaces

To display the VLAN interfaces
To display the VLAN interfaces, enter the following:

Network> vlan show
For example:
VLAN ----pubeth0.2 DEVICE -----pubeth0 VLAN id ------2
To add a VLAN interface
To add a VLAN interface, enter the following:

Network> vlan add device vlan_id device Specifies the VLAN interface on which the VLAN interfaces will be added. Specifies the VLAN ID which the new VLAN interface uses. Valid values range from 1 to 4095.
vlan_id
For example:
Network> vlan add pubeth1 2 Network> vlan show VLAN ----pubeth0.2 pubeth1.2 DEVICE -----pubeth0 pubeth1 VLAN id ------2 2
167
To delete a VLAN interface
To delete a VLAN interface, enter the following:

Network> vlan del vlan_device
where the vlan_device is the VLAN name from the Network> vlan show command. For example:
Network> vlan del pubeth0.2 Network> vlan show VLAN ----pubeth1.2 DEVICE -----pubeth1 VLAN id ------2
168
Chapter
Configuring your NFS server


About NFS server commands Accessing the NFS server Displaying NFS statistics Displaying file systems and snapshots that can be exported
About NFS server commands

The clustered NFS Server provides file access services to UNIX and Linux client computers via the Network File System (NFS) protocol. You use the NFS commands to start and stop your NFS server. See Table 6-1 on page 169. Note: For the NFS> share commands, see the section referenced below. See About NFS file sharing on page 175. To access the commands, log into the administrative console (for master, system-admin, or storage-admin) and enter NFS> mode. See About using the FileStore command-line interface on page 33. Table 6-1 Command
server status
NFS mode commands Definition

Displays the status of the NFS server. See Accessing the NFS server on page 170.
170
Configuring your NFS server Accessing the NFS server
Table 6-1 Command

server start
NFS mode commands (continued) Definition

Starts the NFS server. See Accessing the NFS server on page 170.
server stop
Stops the NFS server. See Accessing the NFS server on page 170.
stat
Prints the NFS statistics. See Displaying NFS statistics on page 172.
show fs
Displays all of the online file systems and snapshots that can be exported. See Displaying file systems and snapshots that can be exported on page 173.
Accessing the NFS server

To check on the NFS server status
Prior to starting the NFS server, check on the status of the server by entering:
NFS> server status
For example:
NFS> server status NFS Status on sfs_01 : OFFLINE NFS Status on sfs_02 : OFFLINE
The states (ONLINE, OFFLINE, and FAULTED) correspond to each FileStore node identified by the node name. The states of the node may vary depending on the situation for that particular node. The possible states of the NFS> server status command are:
ONLINE OFFLINE FAULTED Indicates that the node can serve NFS protocols to the client. Indicates the NFS services on that node are down. Indicates something is wrong with the NFS service on the node.
You can run the NFS> server start command to restart the NFS services, and only the nodes where NFS services have problems, will be restarted.
Configuring your NFS server Accessing the NFS server
171
To start the NFS server
To start the NFS server, enter the following:

NFS> server start
You can use the NFS> server start command to clear an OFFLINE state from the NFS> server status output by only restarting the services that are offline. You can run the NFS> server start command multiple times without it affecting the already-started NFS server. For example:
NFS> server start ..Success.
Run the NFS> server status command again to confirm the change.
NFS> server status NFS Status on sfs_01 : ONLINE NFS Status on sfs_02 : ONLINE
To stop the NFS server
To stop the NFS server, enter the following:

NFS> server stop
For example:
NFS> server stop ..Success.
You will receive an error if you try to stop an already stopped NFS server.
172
Configuring your NFS server Displaying NFS statistics
Displaying NFS statistics

To display statistics for all the nodes in the cluster on the NFS server
To display NFS statistics, enter the following:

NFS> stat [nodename]
where nodename specifies the node name for which you are trying to obtain the statistical information. If the nodename is not specified, statistics for all the nodes in the cluster are displayed. For example:
NFS> stat sfs_01 sfs_01 ---------------Server rpc stats: calls badcalls 52517 0 Server nfs v2: null getattr 10 100% 0 0% read wrcache 0 0% 0 0% link symlink 0 0% 0 0% Server null 11 read 4138 remove 0 fsstat 0 nfs v3: getattr 0% 17973 35% write 8% 4137 8% rmdir 0% 1 0% fsinfo 0% 2 0%
badauth 0
badclnt 0
xdrcall 0
setattr 0 0% write 0 0% mkdir 0 0%
root 0 0% create 0 0% rmdir 0 0%
lookup 0 0% remove 0 0% readdir 0 0%
readlink 0 0% rename 0 0% fsstat 0 0%
setattr 0 0% create 3251 6% rename 0 0% pathconf 0 0%
lookup 5951 11% mkdir 1255 2% link 0 0% commit 3067 6%
access 6997 13% symlink 1034 2% readdir 0 0%
readlink 1034 2% mknod 0 0% readdirplus 1361 2%
Configuring your NFS server Displaying file systems and snapshots that can be exported
173
Displaying file systems and snapshots that can be exported

To display a file system and snapshots that can be exported
To display online file systems and the snapshots that can be exported, enter the following:
NFS> show fs
For example:
NFS> show fs FS/Snapshot =========== fs1
174
Configuring your NFS server Displaying file systems and snapshots that can be exported
Chapter
Creating and maintaining NFS shares


About NFS file sharing Displaying exported directories Adding an NFS share Sharing directories using CIFS and NFS protocols Exporting an NFS snapshot Unexporting a directory or deleting NFS options
About NFS file sharing

The Network File System (NFS) protocol enables exported directories (including all files under the directory that reside on the exported directory's file system) hosted by an NFS server to be accessed by multiple UNIX and Linux client systems. Using NFS, a local system can mount and use a disk partition or file system from a remote system (an NFS server), as if it were local. The FileStore NFS server exports a directory , with selected permissions and options, and makes it available to NFS clients. The selected permissions and options can also be updated, to restrict or expand the permitted use. To remove sharing, unexport the NFS directory. The FileStore NFS service is clustered. The NFS clients continuously retry during a failover transition. Even if the TCP connection is broken for a short time, the
176
Creating and maintaining NFS shares Displaying exported directories
failover is transparent to NFS clients, and NFS clients regain access transparently as soon as the failover is complete. However, depending on client configuration and the nature of the failure, a client operation may time out, resulting in an error message such as: NFS server not responding, still trying. You use NFS commands to export or unexport your directories. The NFS> share commands are defined in Table 7-1. To access the commands, log into the administrative console (for master, system-admin, or storage-admin) and enter the NFS> mode. See About using the FileStore command-line interface on page 33. Table 7-1 Command
share show
NFS mode commands Definition

Display exported directories. See Displaying exported directories on page 176.
share add
Export a directory. See Adding an NFS share on page 177.
share delete
Unexport a directory. See Unexporting a directory or deleting NFS options on page 184.
Displaying exported directories

You can display the exported directories and the NFS options that are specified when the directory was exported.
Creating and maintaining NFS shares Adding an NFS share
177
To display exported directories
To display exported directories, enter the following:

NFS> share show
For example:
NFS> share show /vx/fs2 /vx/fs3
* (sync) * (secure,ro,no_root_squash)
The command output displays two columns.

Left-hand column Displays the directory that was exported. For example: /vx/fs2
Right-hand column
Displays the system that the directory is exported to, and the NFS options with which the directory was exported. For example: * (secure,ro,no_root_squash)
Adding an NFS share

You can export an NFS share with the specified NFS options that can then be accessed by one or more client systems. The new NFS options are updated after the command is run. If you add a directory that has already been exported with a different NFS option (rw, ro, async, or secure, for example), FileStore provides a warning message saying that the directory has already been exported. FileStore updates (overwrite) the old NFS options with the new NFS options. Directory options appear in parentheses. If a client was not specified when the NFS> share add command was used, then * is displayed as the system to be exported to, indicating that all clients can access the directory. Directories that have been exported to different clients appear as different entries. Directories that are exported to <world> and other specific clients also appear as different entries.
178
For example: Consider the following set of exported directories where only the client (1.1.1.1) has read-write access to directory (fs2), while all other clients have read access only.
/vx/fs2 /vx/fs2 * (ro) 1.1.1.1 (rw)
When sharing a directory, FileStore does not check whether the client exists or not. If you add a share for an unknown client, then an entry appears in the NFS> show command output. If the directory (including the underlying file system) does not exist, you will not be able to export to any client. FileStore gives the following error:
SFS nfs ERROR V-288-1697 Directory /vx/fs1/export does not exist
You cannot export a non-existent directory. The NFS> show fs command displays the list of exportable file systems. Valid NFS options include the following:
rw Grants read and write permission to the directory (including all files under the directory that reside on the exported directory's file system). Hosts mounting this directory will be able to make changes to the directory. Grants read-only permission to the directory. Hosts mounting this directory will not be able to change it. Grants synchronous write access to the directory. Forces the server to perform a disk write before the request is considered complete. Grants asynchronous write access to the directory. Allows the server to write data to the disk when appropriate. Grants secure access to the directory. Requires that clients originate from a secure port. A secure port is between 1-1024. Grants insecure access to the directory. Permits client requests to originate from unprivileged ports (those above 1024). Requires authorization of all locking requests.
ro (Default)
sync (Default)
async
secure (Default)
insecure
secure_locks (Default)
179
insecure_locks
Some NFS clients do not send credentials with lock requests, and therefore work incorrectly with secure_locks, in which case you can only lock world-readable files. If you have such clients, either replace them with better ones, or use the insecure_locks option. Prevents the root user on an NFS client from having root privileges on an NFS mount. This effectively "squashes" the power of the remote root user to the lowest local user, preventing remote root users from acting as though they were the root user on the local system.
root_squash (Default)
no_root_squash
Disables the root_squash option. Allows root users on the NFS client to have root privileges on the NFS server. Causes the NFS server to delay writing to the disk if another write request is imminent. This can improve performance by reducing the number of times the disk must be accessed by separate write commands, reducing write overhead. Disables the wdelay option. Verifies that the requested file is in an exported subdirectory. If this option is turned off, the only verification is that the file is in an exported file system. Sometimes subtree checking can produce problems when a requested file is renamed while the client has the file open. If many such situations are anticipated, it might be better to set no_subtree_check. One such situation might be the export of the home directory. Most other situations are best handled with subtree_check. This option allows the FileStore administrator to associate a specific number as fsid with the share.
wdelay (Default)
no_wdelay subtree_check (Default)
no_subtree_check
fsid (Default)
For example, you could issue the following commands:

NFS> share add rw,async /vx/fs2 NFS> share add rw,sync,secure,root_squash /vx/fs3 10.10.10.10
Note: With root_squash, the root user can access the share, but with 'nobody' permissions.
180
To export a directory/file system
To see your exportable online file systems and snapshots, enter the following:
NFS> show fs
For example:
NFS> show fs FS/Snapshot =========== fs2 fs3
To see your NFS share options, enter the following:

NFS> share show
For example:
To export a directory, enter the following command:

NFS> share add nfsoptions export_dir [client] nfsoptions export_dir Comma-separated list of export options from the set. Specifies the name of the directory you want to export. The directory name should start with /vx, and only a-zA-Z0-9_/@+=.:- characters are allowed for export_dir.
Creating and maintaining NFS shares Sharing directories using CIFS and NFS protocols
181
client
Clients may be specified in the following ways:
Single host - specify a host either by an abbreviated name that is recognized by the resolver (DNS is the resolver), the fully qualified domain name, or an IP address.
Netgroups - netgroups may be given as @group. Only the host part of each netgroup member is considered for checking membership. IP networks - you can also simultaneously export directories to all hosts on an IP sub-network. This is done by specifying an IP address and netmask pair as address/netmask where the netmask can be specified as a contiguous mask length.
If the client is not given, then the specified directory can be mounted or accessed by any client. To re-export new options to an existing share, the new options will be updated after the command is run.
Example using NFS options:

NFS> share add async /vx/fs1 Exporting *:/vx/fs1 with options async ..Success.
Sharing directories using CIFS and NFS protocols

FileStore provides support for multi-protocol file sharing where the same directory (including all files under the directory that reside on the exported directory's file system) can be exported to both Windows and UNIX users using the CIFS and NFS protocols. The result is an efficient use of storage by sharing a single data set across multi-application platforms. Figure 7-1 shows how the directory sharing for the two protocols works.
182
Figure 7-1
Exporting and/or sharing CIFS and NFS directories
Shared Storage File System FS1
2-node FileStore cluster Data access by CIFS protocol Data access by NFS protocol
Windows user
UNIX user
Note: When a share is exported over both NFS and CIFS protocols, the applications running on the NFS and CIFS clients may attempt to concurrently read or write the same file. This may lead to unexpected results since the locking models used by these protocols are different. For example, an application reads stale data. For this reason, FileStore warns you when the share export is requested over NFS or CIFS and the same share has already been exported over CIFS or NFS, when at least one of these exports allows write access.
183
To export a directory to Windows and UNIX users
To export a directory to Windows and UNIX users with read-only and read-write permission respectively, go to CIFS mode and enter the following commands:
CIFS> show Name Value ---- ----netbios name mycluster ntlm auth yes allow trusted domains no homedirfs idmap backend rid:10000-1000000 workgroup SYMANTECDOMAIN security ads Domain SYMANTECDOMAIN.COM Domain user administrator Domain Controller SYMSERVER CIFS> share add fs1 share1 ro Exporting CIFS filesystem : share1... CIFS> share show ShareName FileSystem ShareOptions share1 fs1 owner=root,group=root,ro
Enter the NFS mode and enter the following commands:

CIFS> exit > nfs Entering share mode... NFS> share add rw fs1 SFS nfs WARNING V-288-0 Filesystem (fs1) is already shared over CIFS with 'ro' permission. Do you want to proceed (y/n): y Exporting *:/vx/fs1 with options rw ..Success. NFS> share show /vx/fs1 * (rw)
184
Creating and maintaining NFS shares Exporting an NFS snapshot
Exporting an NFS snapshot

To export an NFS snapshot
To create an NFS snapshot, enter the following for example:

Storage> snapshot create fs5sp1 FS5
See About snapshots on page 205.
To export the NFS snapshot, enter the following for example:

NFS> share add rw /vx/FS5:fs5sp1
See Adding an NFS share on page 177.
Unexporting a directory or deleting NFS options

You can unexport the share of the exported directory. Note: You will receive an error message if you try to remove a directory that does not exist. To unexport a directory or delete NFS options
To see your existing exported resources, enter the following command:

NFS> share show
Only the directories that are displayed can be unexported. For example:
To delete a directory from the export path, enter the following command:
NFS> share delete export_dir [client]
For example:
NFS> share delete /vx/fs3 Removing export path *:/vx/fs3 ..Success.
Creating and maintaining NFS shares Unexporting a directory or deleting NFS options
185
export_dir
Specifies the name of the directory you want to delete. The directory name should start with /vx, and only a-zA-Z0-9_/@+=.:- characters are allowed in export_dir. You cannot include single or double quotes that do not enclose characters. NFS> share delete "*:/vx/example" You cannot use one single quote or one double quote, as in the following example: NFS> share delete ' "filesystem
client
Clients may be specified in the following ways: Single host - specify a host either by an abbreviated name that is recognized by the resolver (DNS is the resolver), the fully qualified domain name, or an IP address. Netgroups - netgroups may be given as @group. Only the host part of each netgroup member is considered for checking membership. IP networks - you can also simultaneously export directories to all hosts on an IP sub-network. This is done by specifying an IP address and netmask pair as address/netmask where the netmask can be specified as a contiguous mask length.
If client is included, the directory is removed from the export path that was directed at the client. If a directory is being exported to a specific client, the NFS> share delete command must specify the client to remove that export path. If the client is not specified, then the specified directory can be mounted or accessed by any client.
186
Creating and maintaining NFS shares Unexporting a directory or deleting NFS options
Chapter
Creating and maintaining file systems


About creating and maintaining file systems Listing all file systems and associated information About creating file systems Creating a file system Adding or removing a mirror to a file system Configuring FastResync for a file system Disabling the FastResync option for a file system Increasing the size of a file system Decreasing the size of a file system Checking and repairing a file system Changing the status of a file system Defragmenting a file system Destroying a file system About snapshots About instant rollbacks About setting up file system alerts for file system usage
188
Creating and maintaining file systems About creating and maintaining file systems
About the Partition Secure Notification (PSN) feature
About creating and maintaining file systems

This chapter discusses the FileStore file system commands. You use these commands to configure your file system. For more information on the Storage> fs commands, see Table 8-1. File systems consist of both metadata and file system data. Metadata contains information such as the last modification date, creation time, permissions, and so on. The total amount of space required for the metadata depends on the number of files in the file system. A file system with many small files requires more space to store metadata. A file system with fewer larger files requires less space for handling the metadata. When you create a file system, you need to set aside some space for handling the metadata. The space required is generally proportional to the size of the file system. For this reason, after you create the file system with the Storage> fs list command the output includes non-zero percentages. The space set aside for handling metadata may increase or decrease as needed. For example, a file system on a 1 GB volume takes approximately 35 MB (about 3%) initially for storing metadata. In contrast, a file system of 10 MB requires approximately 3.3 MB (30%) initially for storing the metadata. File systems can be increased or decreased in size. Dynamic Storage Tiering (DST) functionality is also provided at the file system level. See About FileStore Dynamic Storage Tiering (DST) on page 422. To access the commands, log into the administrative console (as a master, system-admin, or storage-admin) and enter Storage> mode. See About using the FileStore command-line interface on page 33. Table 8-1 Command
fs list

Lists all file systems and associated information. See Listing all file systems and associated information on page 191.
fs create
Creates a file system. See About creating file systems on page 191.
fs addmirror
Adds a mirror to a file system. See Adding or removing a mirror to a file system on page 195.
189
Table 8-1 Command

fs rmmirror

Removes a mirror from a file system. See Adding or removing a mirror to a file system on page 195.
fs setfastresync
Keeps the mirrors in the file system in a consistent state. See Configuring FastResync for a file system on page 197.
fs unsetfastresync Disables the FastResync option for a file system. See Disabling the FastResync option for a file system on page 198. fs growto Increases the size of a file system to a specified size. See Increasing the size of a file system on page 199. fs growby Increases the size of a file system by a specified size. See Increasing the size of a file system on page 199. fs shrinkto Decreases the size of a file system to a specified size. See Decreasing the size of a file system on page 201. fs shrinkby Decreases the size of a file system by a specified size. See Decreasing the size of a file system on page 201. fs fsck Checks and repair a file system. See Checking and repairing a file system on page 202. fs alert Sets and unsets alerts by file system usage and displays current disk usage and alert values. See About setting up file system alerts for file system usage on page 227. fs online Mounts (places online) a file system. See Changing the status of a file system on page 202. fs offline Unmounts (places offline) a file system. See Changing the status of a file system on page 202. fs destroy Destroys a file system. See Destroying a file system on page 204.
190
Table 8-1 Command

snapshot

Copies a set of files and directories as they were at a particular point in the past. See About snapshots on page 205.
snapshot schedule Creates or remove a snapshot. See About snapshot schedules on page 211.
Creating and maintaining file systems Listing all file systems and associated information
191
Listing all file systems and associated information

To list all file systems and associated information
To list all file systems and associated information, enter the following:
Storage> fs list [fs_name]
where fs_name is optional. If you enter a file system that does not exist, an error message is displayed. If you do not enter a specified file system, a list of file systems is displayed. For example:
Storage> fs list General Info: =============== Block Size: sfsman4_01: sfsman4_02: Primary Tier ============ clus_01: clus_02: Size: Use%: Layout: Mirrors: Columns: Stripe Unit: FastResync: Mirror 1: List of pools: List of disks: dev
1024 Bytes online online
online online 1.00G simple 0.00 K Disabled
pool1 disk_0 disk_2
About creating file systems

The Storage> fs commands manage file system operations.
192
Creating and maintaining file systems Creating a file system
Table 8-2 Command

fs create simple
Create file systems commands Definition

Creates a simple file system of a specified size. You can specify a block size for the file system. The default block size is determined based on the size of the file system when the file system is created. For example, 1 KB is the default block size for up to a 2 TB file system size. There are other default block sizes, 2 KB, 4 KB, and 8 KB for different ranges of file system sizes. If you create a 1 TB file system, and then increase it to 3 TB, the file system block size remains at 1KB. See Creating a file system on page 192.
fs create mirrored Creates a mirrored file system with a specified number of mirrors, a list of pools, and online status. Each mirror uses the disks from the corresponding pools as listed. See Creating a file system on page 192. fs create mirrored-stripe Creates a mirrored-stripe file system with a specified number of columns, mirrors, pools, and protection options. See Creating a file system on page 192. fs create striped-mirror Creates a striped-mirror file system with a specified number of mirrors and stripes. See Creating a file system on page 192. fs create striped Creates a striped file system. A striped file system is a file system that stores its data across multiple disks rather than storing the data on one disk. See Creating a file system on page 192.
Creating a file system

After a file system is created, the file system reserves some space for internal logging. Internal logging provides additional data integrity. Due to the space reserved for internal logging, the file system may appear to be used just after file system creation. The space reserved for internal logging increases with the number of nodes in the FileStore cluster. Log file sizes for the file systems are as follows:
10 G to 100 G Log size = 60 M per node
193
100 G to 1 T 1 T and above
Log size = 100 M per node Log size = 256 MB per node
To create a simple file system of a specified size
To create a simple file system with a specified size, enter the following:
Storage> fs create simple fs_name size pool1[,disk1,...] [blksize=bytes]
For example:
Storage> fs create simple fs2 10m sda 100% [#] Creating simple filesystem
To create a mirrored file system
To create a mirrored file system, enter the following:

Storage> fs create mirrored fs_name size nmirrors pool1[,disk1,...] [protection=disk|pool] [blksize=bytes]
For example:
Storage> fs create mirrored fs1 100M 2 pool1,pool2 100% [#] Creating mirrored filesystem
To create a mirrored-stripe file system
To create a mirrored-stripe file system, enter the following:

Storage> fs create mirrored-stripe fs_name size nmirrors ncolumns pool1[,disk1,...] [protection=disk|pool] [stripeunit=kilobytes] [blksize=bytes]
To create a striped-mirror file system
To create a striped-mirror file system, enter the following:

Storage> fs create striped-mirror fs_name size nmirrors ncolumns pool1[,disk1,...] [protection=disk|pool] [stripeunit=kilobytes] [blksize=bytes]
To create a striped file system
To create a striped file system, enter the following:
194
Storage> fs create striped fs_name size ncolumns pool1[,disk1,...] [stripeunit=kilobytes] [blksize=bytes] fs_name Specifies the name of the file system being created. The file system name should be a string. If you enter a file that already exists, you receive an error message and the file system is not created. Specifies the size of a file system. To create a file system, you need at least 10 MB of space. Available units are the following:

size
MB GB TB
You can enter the units with either uppercase (10M) or lowercase (10m) letters. To see how much space is available on a pool, use the Storage> pool free command. See About configuring storage pools on page 64. nmirrors Specifies the number of mirrors for the file system. You must enter a positive integer. Specifies the number of columns for the striped file system. The number of columns represents the number of disks to stripe the information across. If the number of columns exceeds the number of disks for the entered pools, an error message is displayed. This message indicates that there is not enough space to create the striped file system. Specifies the pool(s) or disk(s) for the file system. If you specify a pool or disk that does not exist, you receive an error message. Specify more than one pool or disk by separating the name with a comma; however, do not include a space between the comma and the name. To find a list of pools and disks, use the Storage> pool list command. To find a list of disks, use the Storage> disk list command. The disk must be part of the pool or an error message is displayed.
ncolumns
pool1[,disk1,...]
Creating and maintaining file systems Adding or removing a mirror to a file system
195
protection
If you do not specify a protection option, the default is "disk." The available options for this field are:

disk - Creates mirrors on separate disks. pool - Creates mirrors in separate pools. If there is not enough space to create the mirrors, an error message is displayed, and the file system is not created.
stripeunit=kilobytes Specifies a stripe width (in kilobytes). Possible values are the following:

128 256 512 (default) 1024 2048
blksize=bytes
Specifies the block size for the file system. Possible values of bytes are the following:

1024 (default) 2048 4096 8192
Block sizes can affect the file size. For example, to create a file system greater then 32 TB, the block size needs to be 8192.
Adding or removing a mirror to a file system

A mirrored file system is one that has copies of itself on other disks or pools. To add a mirror to a file system
To add a mirror to a file system, enter the following:

Storage> fs addmirror fs_name pool1[,disk1,...] [protection=disk|pool] fs_name Specifies which file system to add the mirror. If the specified file system does not exist, an error message is displayed.
196
Creating and maintaining file systems Adding or removing a mirror to a file system
pool1[,disk1,...]
Specifies the pool(s) or disk(s) to use for the file system. If the specified pool or disk does not exist, an error message is displayed, and the file system is not created. You can specify more than one pool or disk by separating the name with a comma, but do not include a space between the comma and the name. To find a list of existing pools and disks, use the Storage> pool list command. See About configuring storage pools on page 64. To find a list of the existing disks, use the Storage> disk list command. See About displaying information for all disk devices on page 76. The disk needs to be part of the pool or an error message is displayed.
protection
The default value for the protection field is disk. Available options are: disk - if the protection is set to disk, then mirrors will be created on separate disks. This flag only works for file systems of type mirrored, mirrored-striped, and striped-mirror. The disks may or may not be in the same pool. pool - if the protection is set to pool, then mirrors will be created in separate pools. This flag only works for file systems of type mirrored, mirrored-striped, and striped-mirror. If not enough space is available, then the file system creation operation fails.
For example:
Storage> fs addmirror fs1 pool3,pool4
Creating and maintaining file systems Configuring FastResync for a file system
197
To remove a mirror from a file system
To remove a mirror from a file system, enter the following:

Storage> fs rmmirror fs_name [pool_or_disk_name] fs_name Specifies the file system from which to remove the mirror. If you specify a file system that does not exist, an error message is displayed. Specifies the pool or disk name to remove from the mirrored file system that is spanning on the specified pools/disks. If a pool name is the same as the disk name, then the mirror present on the pool is deleted.
pool_or_disk_name
For a striped-mirror file system, if any of the disks are bad, the Storage> fs rmmirror command disables the mirrors on the disks that have failed. If no disks have failed, FileStore chooses a mirror to remove. For example:
Storage> fs rmmirror fs1 AMS_WMS0_0
Configuring FastResync for a file system

If the power fails or a switch fails mirrors in a file system may not be in a consistent state. The Storage> fs setfastresync (Fast Mirror Resynchronization (FastResync)) command keeps the mirrors in the file system in a consistent state. Note: You must have at least two mirrors on the file system to enable FastResync. The setfastresync command is enabled by default.
198
Creating and maintaining file systems Disabling the FastResync option for a file system
To enable the FastResync option
To enable FastResync, enter the following:

Storage> fs setfastresync fs_name [pool_or_disk_name] fs_name Specifies the name of the file system for which to enable FastResync. If you specify a file system that does not exist, an error message is displayed. If the FastResync on the specified file system already has FastResync enabled, an error message is displayed, and no action is taken. Specifies the pool or disk name to resynchronize from the mirrored file system that is spanning the specified pool or disk. If you specify a pool or disk that is not part of the mirrored file system, an error message is displayed, and no action is taken.
pool_or_disk_name
For example, to enable for a file system, enter the following :

Storage> fs setfastresync fs6
Disabling the FastResync option for a file system

You can disable the FastResync option for a file system. Note: When instant rollbacks exist for a volume, you cannot disable the FastResync option for a file system. To disable the FastResync option
To disable the FastResync option, enter the following:

Storage> fs unsetfastresync fs_name
where fs_name specifies the name of the file system for which to disable FastResync. If you specify a file system does not exist, an error message is displayed. For example:
Storage> fs unsetfastresync fs6
Creating and maintaining file systems Increasing the size of a file system
199
Increasing the size of a file system

To increase the size of a file system, it must be online. If the file system is not online, an error message is displayed, and no action is taken. To increase the size of a file system to a specified size
To increase the size of a file system to a specified size, enter the following:
Storage> fs growto {primary|secondary} fs_name new_length [pool1[,disk1,...]] [protection=disk|pool]
For example:
Storage> fs growto primary fs1 1G
If no pool is specified with the command, the disks for growing the file system can be taken from any available pool. The protection flag takes the default value of disk in this case. The value of the protection field cannot be set to pool when no pool is specified with the command. This operation may convert the layout of the file system if the command determines that the new file system is too large for the original layout. To increase the size of a file system by a specified size
To increase the size of a file system by a specified size, enter the following:
Storage> fs growby {primary|secondary} fs_name length_change [pool1[,disk1,...]] [protection=disk|pool]
For example:
Storage> fs growby primary fs1 50M
If no pool is specified with the command, the disks for growing the file system can be taken from any available pool. The protection flag takes the default value of disk in this case. The value of the protection field cannot be set to pool when no pool is specified with the command. This operation may convert the layout of the file system if the command determines that the new file system is too large for the original layout.
primary |secondary Specifies the primary or the secondary tier.
200
Creating and maintaining file systems Increasing the size of a file system
fs_name
Specifies the file system whose size will be increased. If you specify a file system that does not exist, an error message is displayed. Expands the file system to a specified size. The size specified must be a positive number, and it must be bigger than the size of the existing file system. If the new file system is not larger than the size of the existing file system, an error message is displayed, and no action is taken. This variable is used with the Storage> fs growto command.
new_length
length_change
Expands the file system by a specified size. The size specified must be a positive number, and it must be lesser than the available space. If it exceeds the available space, an error message is displayed, and no action is taken. This variable is used with the Storage> fs growby command.
pool1[,disk1,...]
Specifies the pool(s) or disk(s) to use for the file system. If you specify a pool or disk that does not exist, an error message is displayed, and the file system is not resized. You can specify more than one pool or disk by separating the name with a comma; however, do not include a space between the comma and the name. To find a list of existing pools and disks, use the Storage> pool list command. See About configuring storage pools on page 64. To find a list of the existing disks, use the Storage> disk list command. See About displaying information for all disk devices on page 76. The disk needs to be part of the pool or an error message displays.
protection
The default value for the protection field is disk. Available options are: disk - if the protection is set to disk, then mirrors will be created on separate disks. This flag only works for file systems of type mirrored, mirrored-striped, and striped-mirror. The disks may or may not be in the same pool. pool - if the protection is set to pool, then mirrors will be created in separate pools. This flag only works for file systems of type mirrored, mirrored-striped, and striped-mirror. If not enough space is available, then the file system creation operation fails.
Creating and maintaining file systems Decreasing the size of a file system
201
Decreasing the size of a file system

You can decrease the size of the file system. To decrease the size of the file system, it must be online. If the file system is not online, an error message is displayed, and no action is taken. To decrease the size of a file system to a specified size
To decrease the size of a file system, enter the following:

Storage> fs shrinkto {primary|secondary} fs_name new_length
For example:
Storage> fs shrinkto primary fs1 10M
To decrease the size of a file system by a specified size
To decrease the size of a file system, enter the following:

Storage> fs shrinkby {primary|secondary} fs_name length_change
For example:
Storage> fs shrinkby primary fs1 10M primary | secondary fs_name Specifies the primary or secondary tier. Specifies the file system whose size will decrease. If you specify a file system that does not exist, an error message is displayed. Specifies the size to decrease the file system to. The size specified must be a positive number, and it must be smaller than the size of the existing file system. If the new file system size is not smaller than the size of the existing file system, an error message is displayed, and no action is taken. Decreases the file system by a specified size. The size specified must be a positive number, and it must be smaller than the size of the existing file system. If the new file system size is not smaller than the size of the existing file system, an error message is displayed, and no action is taken.
new_length
length_change
202
Creating and maintaining file systems Checking and repairing a file system
Checking and repairing a file system

The Storage> fs fsck command lets you check and repair a file system. Warning: Using the Storage> fs fsck command on an online file system can damage the data on the file system. Only use the Storage> fs fsck command on a file system that is offline. To check and repair a file system
To check and repair a file system, enter the following:

Storage> fs fsck fs_name
where fs_name specifies the file system for which to check and repair. For example:
Storage> fs fsck fs1 SFS fs ERROR V-288-693 fs1 must be offline to perform fsck.
Changing the status of a file system

The Storage> fs online or Storage> fs offline command lets you mount (online) or unmount (offline) a file system. You cannot access an offline file system from a client.
Creating and maintaining file systems Changing the status of a file system
203
To change the status of a file system
To change the status of a file system, enter one of the following, depending on which status you are using:
Storage> fs online fs_name Storage> fs offline fs_name
where fs_name specifies the name of the file system that you want to mount (online) or unmount (offline). If you specify a file system that does not exist, an error message is displayed. For example, to bring a file system online:
Storage> fs list FS STATUS SIZE === ====== ==== fs1 online 5.00G fs2 offline 10.00M NFS SHARED ======= no no CIFS SHARED ======= no no
LAYOUT ====== simple simple
MIRRORS ======= -
COLUMNS ======= -
USE% ==== 10% -
SECONDARY TIER ========= no no
Storage> fs online fs2 100% [#] Online filesystem Storage> fs list FS STATUS SIZE === ====== ==== fs1 online 5.00G fs2 online 10.00M NFS SHARED ======= no no LAYOUT ====== simple simple MIRRORS ======= COLUMNS ======= USE% ==== 10% 100%
CIFS SECONDARY SHARED TIER ======= ========= no no no no
For example, to place a file system offline:

Storage> fs offline fs1 100% [#] Offline filesystem
204
Creating and maintaining file systems Defragmenting a file system
Defragmenting a file system

To defragment a file system
To defragment a file system, enter the following:

Storage> fs defrag fs_name
where fs_name is the name of the file system that you want to defragment. The specified file system must be online prior to attempting to defragment the file system. See Changing the status of a file system on page 202. For example:
Storage> fs defrag fs1 It will take some time to do the defragmentation Do you want to continue? yes|no yes Defragmentation in progress... If you want to stop defragmentation, you can press ctrl+c... Defragmentation completed successfully for fs1 Storage> fs defrag fs2 SFS fs ERROR V-288-646 File system fs2 does not exist. Storage> fs defrag fs22 It will take some time to do the defragmentation Do you want to continue? yes|no no Defragmentation cancelled for fs22
Destroying a file system

The Storage> fs destroy command unmounts a file system and releases its storage back to the storage pool. You can destroy only those file systems that are not shared by CIFS or NFS.
Creating and maintaining file systems About snapshots
205
To destroy a file system
To destroy a file system, enter the following:

Storage> fs destroy fs_name
where fs_name specifies the name of the file system that you want to destroy. For example:
Storage> fs destroy fs1 100% [#] Destroy filesystem
About snapshots
A snapshot is a virtual image of the entire file system. You can create snapshots of a parent file system on demand. Physically, it contains only data that corresponds to changes made in the parent, and so consumes significantly less space than a detachable full mirror. Snapshots are used to recover from data corruption. If files, or an entire file system, are deleted or become corrupted, you can replace them from the latest uncorrupted snapshot. You can mount a snapshot and export it as if it were a complete file system. Users can then recover their own deleted or corrupted files. You can limit the space consumed by snapshots by setting a quota on them. If the total space consumed by snapshots remains above the quota, FileStore rejects attempts to create additional ones. You can create a snapshot by either using the snapshot create command or by creating a schedule that calls the snapshot create command depending on the values entered for the number of hours or minutes after which this command should run. This method automatically creates the snapshot by storing the following values in the crontab: minutes, hour, day-of-month, month, and day-of-week. Table 8-3 Command
snapshot create
Snapshot commands Definition

A storage snapshot is a copy of a set of files and directories as they were at a particular point in the past. FileStore supports file system level snapshots. FileStore limits the space a snapshot can use. Snapshots use free space in the file system from which they were taken. See Creating snapshots on page 206.
206
Table 8-3 Command

snapshot list
Snapshot commands (continued) Definition

Lists all the snapshots for the specified file system. If you do not specify a file system, snapshots of all the file systems are displayed. See Displaying snapshots on page 208.
snapshot destroy
Deletes a snapshot. See Configuring snapshots on page 209.
snapshot online
Mounts a snapshot. See Configuring snapshots on page 209.
snapshot offline
Unmounts a snapshot. See Configuring snapshots on page 209.
snapshot quota list Displays snapshot information for all the file systems. See Configuring snapshots on page 209. snapshot quota on Disables the creation of snapshots on the given file system when the space used by all of the snapshots of that file system exceeds a given capacity. The space used by the snapshots is restricted. See Configuring snapshots on page 209. snapshot quota off Enables the creation of snapshots on the given file system when the space used by all of the snapshots of that file system exceeds a given capacity. The space used by the snapshots is not restricted. See Configuring snapshots on page 209. snapshot restore Restore the given file system by a given snapshot. See Configuring snapshots on page 209.
Creating snapshots
To create a snapshot
To create a snapshot, enter the following:

Storage> snapshot create snapshot_name fs_name [removable]
207
snapshot_name
Specifies the name for the snapshot.
Note: The following are reserved words for snapshot name:

flags, ctime, and mtime. fs_name removable Specifies the name for the file system. Valid values are:

yes no
If the removable attribute is yes, and the file system is offline, the snapshot is removed automatically if the file system runs out of space. The default value is removable=no.
For example:
Storage> snapshot create snapshot1 fs1 100% [#] Create snapshot
208
Displaying snapshots
To display snapshots
To display snapshots, enter the following:

Storage> snapshot list [fs_name] [schedule_name]
fs_name
Displays all of the snapshots of the specified file system. If you do not specify a file system, snapshots of all of the file systems are displayed.
schedule_name Displays the schedule name. If you do not specify a schedule name, then snapshots created under fs_name are displayed.
Storage> snapshot list Snapshot =================================== snap2 sc1_24_Jul_2009_21_34_01_IST sc1_24_Jul_2009_19_34_02_IST presnap_sc1_24_Jul_2009_18_34_02_IST sc1_24_Jul_2009_17_34_02_IST ctime ==================== 2009.Jul.27.02:40:43 2009.Jul.24.21:34:03 2009.Jul.24.19:34:04 2009.Jul.24.18:34:04 2009.Jul.24.17:34:04
FS == fs1 fs1 fs1 fs1 fs1
Status ====== offline offline offline offline offline Removable ========= no yes yes yes yes Preserved ========= No No No Yes No Size ==== 190.0M 900.0M 7.0G 125M 0K
mtime ==================== 2009.Jul.27.02:40:57 2009.Jul.24.21:34:03 2009.Jul.24.19:34:04 2009.Jul.24.18:34:04 2009.Jul.24.17:34:04
Snapshot FS Status ctime mtime Removable
Displays the name of the created snapshots. Displays the file systems that correspond to each created snapshots. Displays whether or not the snapshot is mounted (that is, online or offline). Displays the time the snapshot was created. Displays the time the snapshot was modified. Determines if the snapshot should be automatically removes in case the underlying file system runs out of space. You entered either yes or no in the snapshot create snapshot_name fs_name [removable] Determines if the snapshot is preserved when all of the automated snapshots are destroyed.
Preserved
209
Size
Displays the size of the snapshot.
Configuring snapshots
To destroy a snapshot
To destroy a snapshot, enter the following:

Storage> snapshot destroy snapshot_name fs_name snapshot_name fs_name Specifies the name of the snapshot to be destroyed. Specifies the name of the file system to be destroyed.
For example:
Storage> snapshot destroy snapshot1 fs1 100% [#] Destroy snapshot
To mount or unmount snapshots
To mount or unmount snapshots, enter one of the following commands, depending on which operation you want to perform:
Storage> snapshot online|offline snapshot_name fs_name snapshot_name fs_name Specifies the name of the snapshot. Specifies the name of the file system.
For example, to bring a snapshot online, enter the following:

Storage> snapshot online snapshot1 fs1 100% [#] Online snapshot
For example, to place snapshot offline, enter the following:

Storage> snapshot offline snapshot fs1 100% [#] Offline snapshot
210
To display snapshot quotas
To display snapshot quotas, enter the following:

Storage> snapshot quota list FS Quota Capacity Limit == ===== ============== fs1 on 1G fs2 off 0 fs3 off 0
To enable or disable a quota limit
To enable or disable a quota limit, enter the following:

Storage> snapshot quota on fs_name [capacity_limit] Storage> snapshot quota off [fs_name] on Enables the quota limit, which disallows creation of snapshots on the given file system when the space used by all the snapshots of that file system exceeds a given capacity limit. Specifies the name of the file system. You can specify a capacity limit on the number of blocks used by all the snapshots for a specified file system. Enter a number that needs to be followed by K, M, G, or T (for kilo, mega, giga, or terabyte). Disables the quota capacity limit for the specified file system.
fs_name capacity_limit
off
For example, to enable the snapshot quota, enter the following:

Storage> snapshot quota on fs1 1024K Storage> snapshot quota list FS Quota Capacity Limit == ===== ============== fs1 ON 1024K
For example, to disable the snapshot quota, enter the following:

Storage> snapshot quota off fs1
211
To restore a snapshot
To restore a snapshot, enter the following:

Storage> snapshot restore snapshot_name fs_name snapshot_name fs_name Specifies the name of the snapshot to be destroyed. Specifies the name of the file system to be destroyed.
For example:
Storage> snapshot restore snapshot0 fs0 SFS snapshot WARNING V-288-0 Snapshot created after snapshot0 will be deleted SFS snapshot WARNING V-288-0 Are you sure to restore file system fs0 with snapshot ssss? (yes/no) yes SFS snapshot SUCCESS V-288-0 File System fs0 restored successfully by snapshot snapshot0.
About snapshot schedules

The Storage> snapshot schedule commands let you automatically create or remove a snapshot that stores the values for minutes, hour, day-of-the-month, month, and day-of-the-week in the crontab along with the name of the file system. To distinguish the automated snapshots, a time stamp corresponding to their time of creation is appended to the schedule name. For example, if a snapshot is created using the name schedule1 on February 27, 2009 at 11:00 AM, the name becomes: schedule1_Feb_27_2009_11_00_01_IST. The crontab interprets the numeric values in a different manner when compared to the manner in which FileStore interprets the same values. For example, snapshot schedule create schedule1 fs1 30 2 * * * automatically creates a snapshot every day at 2:30 AM, and does not create snapshots every two and a half hours. If you wanted to create a snapshot every two and a half hours with at most 50 snapshots per schedule name, then run snapshot schedule create schedule1 fs1 50 */30 */2 * * *, where the value */2 implies that the schedule runs every two hours. You can also specify a step value for the other parameters, such as day-of-month or month and day-of-week as well, and you can use a range along with a step value. Specifying a range in addition to the numeric_value implies the number of times the crontab skips for a given parameter.
212
Note: A best practice is to create only one snapshot schedule for a specified file system. Otherwise, when running the Storage> snapshot schedule destroyall command, it might take a while to complete.
Note: If the master node is being rebooted, snapshot schedules will be missed if scheduled during the reboot of the master node. Table 8-4 Command Snapshot schedule commands Definition
snapshot schedule Creates a schedule to automatically create a snapshot of a particular create file system. See Creating snapshot schedules on page 213. snapshot schedule Modifies the snapshot schedule of a particular filesystem. modify See Configuring snapshot schedules on page 215. snapshot schedule Creates a schedule to destroy all of the automated snapshots. This destroyall excludes the preserved and online snapshots. See Configuring snapshot schedules on page 215. snapshot schedule Preserves a limited number of snapshots corresponding to an existing preserve schedule and specific file system name. These snapshots are not removed as part of the snapshot schedule autoremove command. See Configuring snapshot schedules on page 215. snapshot schedule Displays all schedules that have been set for automatically creating show snapshots. See Configuring snapshot schedules on page 215. snapshot schedule Deletes the schedule set for automatically creating snapshots for a delete particular file system or for a particular schedule. See Configuring snapshot schedules on page 215.
213
Creating snapshot schedules

To create a snapshot schedule
To create a snapshot schedule, enter the following:

Storage> snapshot schedule create schedule_name fs_name max_snapshot_limit minute [hour] [day_of_the_month] [month] [day_of_the_week]
For example, to create a schedule for an automated snapshot creation of a given file system at 3:00 am every day, enter the following:
Storage> snapshot schedule create schedule1 fs1 100 0 3 * * *
When an automated snapshot is created, the entire date value is appended, including the time zone.
schedule_name Specifies the name of the schedule corresponding to the automatically created snapshot. The schedule_name cannot contain an underscore ('_') as part of its value. For example, sch_1 is not allowed. fs_name Specifies the name of the file system. The file system name should be a string.
max_snapshot_limit Specifies the number of snapshots that can be created for a given file system and schedule name. This field only accepts numeric input. Entering 0 implies the snapshots can be created on a given file system and schedule name without any restriction.
Note: Avoid entering a value of 0 for max_snapshot_limit, as it is not recommended to

create an unlimited number of automatic snapshots. Any other value would imply that only x number of snapshots can be created for a given file system and schedule name. If the number of snapshots corresponding to the schedule name is equal to or greater than the value of this field, then snapshots that are more than an hour old are automatically destroyed until the number of snapshots is less than the maximum snapshot limit value. The range allowed for this parameter is 0-999. minute This parameter may contain either an asterisk like '*/15'', which implies every 15 minutes, or a numeric value between 0-59.
Note: If you are using the '*/xx' format, the smallest value for 'xx' is 15.
You can enter */(15-59) or a range such as 23-43. An asterisk (*) is not allowed. hour This parameter may contain either an asterisk, (*), which implies "run every hour," or a number value between 0-23. You can enter */(0-23), a range such as 12-21, or just the *.
214
day_of_the_month This parameter may contain either an asterisk, (*), which implies "run every day of the month," or a number value between 1-31. You can enter */(1-31), a range such ass 3-22, or just the *. month This parameter may contain either an asterisk, (*), which implies "run every month," or a number value between 1-12. You can enter */(1-12), a range such as 1-5, or just the *. You can also enter the first three letters of any month (must use lowercase letters). day_of_the_week This parameter may contain either an asterisk (*), which implies "run every day of the week," or a numeric value between 0-6. Crontab interprets 0 as Sunday. You can also enter the first three letters of the week (must use lowercase letters).
For example, to create a schedule for automated snapshot creation of a given file system every 3 hours on a daily basis, and only 30 snapshots can be maintained for a given snapshot schedule, enter the following:
Storage> snapshot schedule create schedule1 fs1 30 0 */3 * * *
215
Displaying snapshot schedules

To display a snapshot schedule
To display all of the schedules for automated snapshots, enter the following:
Storage> snapshot schedule show [fs_name] [schedule_name] fs_name Displays all of the schedules of the specified file system. If no file system is specified, schedules of all of the file systems are displayed. Displays the schedule name. If no schedule name is specified, then all of the schedules created under fs_name are displayed.
schedule_name
For example, to display all of the schedules for creating or removing snapshots to an existing file system, enter the following:
Storage> snapshot schedule show fs3 FS Schedule Name Max Snapshot Minute === ============= ============ ====== fs3 sched1 30 */20 fs3 sched2 20 */45
Hour ==== * *
Day === * *
Month ===== * *
WeekDay ======= * *
For example, to list the automated snapshot schedules for all file systems, enter the following:
Storage> snapshot schedule show FS Schedule Name Max Snapshot === fs6 fs1 ============= sc1 sc1 ============ 10 10
Minute ====== */50 */25
Hour ==== * *
Day === * *
Month ===== * *
WeekDay ======= * *
Configuring snapshot schedules

In some instances, snapshots may skip scheduled runs. This may happen because of the following two reasons:
When a scheduled snapshot is set to trigger, the snapshot needs to gain a lock to begin the operation. If any command is issued from the CLI or is running through schedules, and if the command holds a lock, the triggered snapshot schedule is not able to obtain the lock, and the scheduled snapshot fails. When a scheduled snapshot is set to trigger, the snapshot checks if there is any instance of a snapshot creation process running. If there is a snapshot
216
creation process running, the scheduled snapshot aborts, and a snapshot is not created. To modify a snapshot schedule
To modify a snapshot schedule, enter the following:

Storage> snapshot schedule modify schedule_name fs_name max_snapshot_limit minute [hour] [day_of_the_month] [month] [day_of_the_week]
For example, to modify the existing schedule so that a snapshot is created at 2:00 am on the first day of the week, enter the following:
Storage> snapshot schedule modify schedule1 fs1 *2**1
To remove all snapshots
To automatically remove all of the snapshots created under a given schedule and file system name (excluding the preserved and online snapshots), enter the following:
Storage> snapshot schedule destroyall schedule_name fs_name
Example 1: If you try to destroy all automated snapshots when two of the automated snapshots are still mounted, FileStore returns an appropriate error, and other automated snapshots under the given schedule and file system are destroyed.
Storage> snapshot schedule destroyall schedule1 fs1 SFS snapshot ERROR V-288-1074 Cannot destroy snapshot(s) schedule1_7_Dec_2009_17_58_02_UTC schedule1_7_Dec_2009_16_58_02_UTC in online state.
Example 2: If you try to destroy all automated snapshots (which are in an offline state), the operation completes successfully.
Storage> snapshot schedule destroyall schedule2 fs1 100% [#] Destroy automated snapshots
Creating and maintaining file systems About instant rollbacks
217
To preserve snapshots
To preserve a number of snapshots corresponding to an existing schedule and specific file system name, enter the following:
Storage> snapshot schedule preserve schedule_name fs_name snapshot_name
For example, to preserve a snapshot created according to a given schedule and file system name, enter the following:
Storage> snapshot schedule preserve schedule fs1 schedule1_Feb_27_16_42_IST
To delete a snapshot schedule
To delete a snapshot schedule, enter the following:

Storage> snapshot schedule delete fs_name [schedule_name]
For example:
Storage> snapshot schedule delete fs1
About instant rollbacks

The Storage> rollback commands manage volume-level snapshots. All rollback commands take a file system name as an argument and perform operations on the underlying volume of that file system. Both space-optimized and full-sized rollbacks are supported by FileStore. Space-optimized rollbacks use a storage cache, and do not need a complete copy of the original volume's storage space. However, space-optimized rollbacks are not suitable for write-intensive volumes, because the copy-on-write mechanism may degrade the performance of the volume. Full-sized rollbacks use more storage, but that has little impact on write performance after synchronization is completed. Both space-optimized rollbacks and full-sized rollbacks can be used instantly after operations such as create, restore, or refresh. Note: When instant rollbacks exist for a volume, you cannot disable the FastResync option for a file system.
218
Table 8-5 Command
Rollback snapshot commands Definition

Creates a shared cache object. See Creating a shared cache object for a FileStore instant rollback on page 225.
rollback cache create
rollback cache destroy
Destroys a shared cache object. See Destroying a cache object of a FileStore instant rollback on page 227.
rollback cache list
Displays a list of shared cache objects. See Listing cache objects for a FileStore instant rollback on page 226.
rollback create space-optimized
Creates a space-optimized instant rollback for a specified file system. See Creating a FileStore space-optimized rollback on page 219.
rollback create full-sized rollback destroy
Creates a full-sized instant rollback for a specified file system. See Creating a full-sized rollback on page 220. Destroys an instant rollback. See Destroying an instant rollback on page 224.
rollback list
Displays a list of instant rollbacks. See Listing FileStore instant rollbacks on page 221.
rollback refresh
Refreshes instant rollback data. See Refreshing an instant rollback from a file system on page 222.
rollback restore
Restores instant rollback data. See Restoring a file system from an instant rollback on page 221.
rollback online
Mounts an instant rollback so that it will be available for read/write access. See Making an instant rollback go online on page 223.
rollback offline
Unmounts an instant rollback. See Making an instant rollback go offline on page 223.
When creating instant rollbacks for volumes bigger than 1T, there may be error messages such as the following:
219
SFS instant_snapshot ERROR V-288-1487 Volume prepare for full-fs1-1 failed.
An error message may occur because the default amount of memory allocated for a Data Change Object (DO) may not be large enough for such big volumes. You can use the vxtune command to change the value. The default value is 6M, which is the memory required for a 1T volume. To change it to 15M, use the following command:
vxtune volpagemod_max_memsz èxpr 15 \* 1024 \* 1024`
Creating a FileStore space-optimized rollback

To create a FileStore space-optimized rollback
To create a FileStore space-optimized rollback for a specified file system, enter the following:
Storage> rollback create space-optimized rollback_name fs_name [cacheobj] rollback_name fs_name Indicates the name of the rollback. Indicates the name of the file system for where to create the space-optimized rollback. Indicates the cache object name. If the cache object is specified, then the shared cache object is used. Or FileStore automatically creates a cache object for the rollback.
cacheobj
For example:
Storage> rollback create space-optimized snap4 fs4 100%[#] Create rollback
220
Creating a full-sized rollback

To create a full-sized rollback for a specified file system
To create a FileStore space-optimized rollback for a specified file system, enter the following:
Storage> rollback create full-sized rollback_name fs_name pool rollback_name fs_name Indicates the name of the rollback. Indicates the name of the file system for where to create the full-sized rollback. Indicates the name of the pool for where to create the full-sized rollback. The disks used for the rollback are allocated from the specified pool.
pool
For example:
Storage> rollback create full-sized snap5 fs4 pool1 100%[#] Create rollback
221
Listing FileStore instant rollbacks

To list FileStore instant rollbacks
To list FileStore instant rollbacks, enter the following:

Storage> rollback list [fs_name]
where fs_name is the name of the file system where you want to list the instant rollbacks. If no file system is specified, instant rollbacks are displayed for all the file systems. For example:
Storage> rollback list NAME TYPE roll5 fullinst roll1 spaceopt
FILESYSTEM fs4 bigfs
SNAPDATE 2010/10/15 20:04 2010/10/15 17:03
Storage> rollback list fs4 NAME TYPE SNAPDATE roll5 fullinst 2010/10/15 20:04
CHANGED_DATA SYNCED_DATA 640K(0.1%) 800M(100%)
Restoring a file system from an instant rollback

Prior to restoring a file system by a specified rollback, the file system should be offline. See Making an instant rollback go offline on page 223.
222
To restore a file system from an instant rollback
To restore a file system from an instant rollback, enter the following:

Storage> rollback restore rollback_name fs_name rollback_name fs_name Indicates the name of the rollback that you want to restore. Indicates the name of the file system that you want to restore.
For example:
Storage> rollback restore fs4 snap4
Re-online the file system. See Making an instant rollback go online on page 223. Re-onlining a file system may take some time depending on the size of the file system.
Refreshing an instant rollback from a file system

To refresh an instant rollback from a file system
To refresh an instant rollback from a file system, enter the following:

Storage> rollback refresh fs_name rollback_name fs_name Indicates the name of the file system that you want to refresh. Indicates the name of the rollback that you want to refresh.
rollback_name
For example:
Storage> rollback refresh roll5 fs4 SFS rollback WARNING V-288-0 rollback roll5 will be refreshed to filesystem fs4 SFS rollback WARNING V-288-0 Are you sure to refresh rollback roll5 with filesystem fs4? (yes/no) yes 100% [#] Refresh rollback SFS rollback SUCCESS V-288-0 snapshot roll5 refreshed successfully from fs fs4
223
Making an instant rollback go online

You can choose to online an instant rollback and use it as a live file system. If the original file system is offline for some reason, the instant rollback can be used as a backup. When a instant rollback is mounted and written to with new data, the instant rollback may no longer be suitable for use in restoring the contents of the original volume. If you chose to write to an instant rollback, create another instant rollback as a backup of the original file system. Making an instant rollback go online
To make an instant rollback go online, enter the following:

Storage> rollback online rollback_name fs_name rollback_name fs_name Indicates the name of the rollback that you want to go online. Indicates the name of the file system that you want to go online.
For example:
Storage> rollback online snap1 Online the filesystem of rollback "snap1"
The instant rollback is available for read/write access just as the file system.
Making an instant rollback go offline

Making an instant rollback go offline
To make an instant rollback go offline, enter the following:

Storage> rollback offline rollback_name fs_name rollback_name fs_name Indicates the name of the rollback that you want to go offline. Indicates the name of the file system that you want to go offline.
For example:
Storage> rollback offline snap1 fs1 Offline the filesystem of snapshot "snap1"
224
Destroying an instant rollback

The instant rollback must be in the offline state before it can be destroyed. See Making an instant rollback go offline on page 223. To destroy an instant rollback
To destroy an instant rollback, enter the following:

Storage> rollback destroy rollback_name fs_name rollback_name fs_name Indicates the name of the rollback that you want to destroy. Indicates the name of the file system that you want to destroy.
For example:
Storage> rollback destroy snap1 myfs2 Destroy the snapshot "snap1" of filesystem "myfs2"
225
Creating a shared cache object for a FileStore instant rollback

To create a shared cache object for a FileStore instant rollback
To create a shared cache object for a FileStore instant rollback, enter the following:
Storage> rollback cache create cache_name cache_size pool cache_name Indicates the name of the cache you want to create for the instant rollback. Indicates the cache size for the instant rollback. Cache size can be specified in any units, such as M, G, or T. The size of the shared cache object should be sufficient to record changes to the file system during intervals between instant rollback refreshes. By default, the size of the cache object for an instant rollback is 20% of the total size of the parent file system. The size of the cache object is dependent on your environment. pool Indicates the pool for storing the cache object for the instant rollback. For better performance, the pool used for the space-optimized rollback should be different from the pool used by the file system.
cache_size
For example:
Storage> rollback cache create mycache 500m pool1 Create a shared cache object "mycache" with the disks from "pool1", the size is 500m
226
Listing cache objects for a FileStore instant rollback

To list cache objects for a FileStore instant rollback
To list cache objects for a FileStore instant rollback, enter the following:
Storage> rollback cache create cache_name cache_size pool
cache_name cache_size
Indicates the name of the cache you want to display for the instant rollback. Indicates the cache size for the instant rollback. Cache size can be specified in any units, such as M, G, or T. The size of the shared cache object should be sufficient to record changes to the file system during intervals between instant rollback refreshes. By default, the size of the cache object for an instant rollback is 20% of the total size of the parent file system. The size of the cache object is dependent on your environment.
pool
Indicates the pool for storing the cache object for the instant rollback. For better performance, the pool used for the space-optimized rollback should be different from the pool used by the file system.
For example:
Storage> rollback cache list CACHE NAME TOTAL(Mb) USED(Mb) (%) AVAIL(Mb) (%) SDCNT SNAP-fs1_tier1-C01 200 5 (2) 195 (97) 1 SNAP-fs1_tier2-C01 200 4 (2) 196 (98) 1
SDCNT is the number of subdisks that have been created on the cache object. If you did not assign a cache object, a cache object is internally created for the instant rollback.
Creating and maintaining file systems About setting up file system alerts for file system usage
227
Destroying a cache object of a FileStore instant rollback

To destroy a cache object of a FileStore instant rollback
To destroy a cache object of a FileStore instant rollback, enter the following:

Storage> rollback cache destroy cache_name
where cache_name is the name of the cache object that you want to destroy. For example:
Storage> rollback cache destroy mycache
You can only destroy the cache object if there is no instant rollback that is using this cache object.
About setting up file system alerts for file system usage

The Storage> fs alert commands allow you to set, unset alerts by file system usage and display current disk usage and alert values. You can set alerts based on the number of inodes used or the file system space used. Table 8-6 Command
fs alert set
File system alerts commands Description

Sets file system alerts based on file system usage. See Setting file system alerts on page 227.
fs alert unset
Unsets file system alerts. See Unsetting file system alerts on page 229.
fs alert show
Displays the current disk space usage and the alert value. See Displaying file system alerts on page 229.
Setting file system alerts

You can set file system alerts based on usage. You can either set the alert based on the number of inodes used or the file system space used. File system alerts can be displayed by using the Report> showevents command.
228
To set file system alerts
To set file system alerts, enter the following:

Storage> fs alert set numinodes | numspace value [fs_name]
where fs_name is the name of the file system for which you want to set the file system alerts. fs_name is optional. When setting the alert for numspace, value is the percentage you want to set to trigger the alert. By default, the alert is sent at 80%. The default value can be modified by not specifying a file system name in the command. When setting the alert for numinodes, value is the number of inodes used. The default alert value for numinodes is set at 0. An alert will not be sent until you set it to a different value. Examples of alerts: NUMSPACE alerts in Report> showevents
2011 Nov 14 23:55:02 [CLUS_01,alert,master] [[fs alert]] numspace set at 70(%) crossed for File System fs1, current usage 98(%)
NUMINODES alert in Report> showevents

2011 Nov 15 00:05:22 [CLUS_01,alert,master] [[fs alert]] numinodes set at 2000 crossed for File System fs1, current usage 7768
Examples for setting alerts that are file-system specific:

Storage> fs alert set numinodes 2M fs1 SFS fs SUCCESS V-288-663 Alert of type [ numinodes ] set to 2M on the file system fs1 Storage> fs alert set numinodes 2M SFS fs SUCCESS V-288-663 Default Alert on the file systems of type [ numinodes ] set to 2M
Examples for default alerts:

Storage> fs alert set numspace 80 fs1 SFS fs SUCCESS V-288-663 Alert of type [ numspace ] set to 80 on the file system fs1 Storage> fs alert set numspace 60 SFS fs SUCCESS V-288-663 Default Alert on the file systems of type [ numspace ] set to 60
229
Unsetting file system alerts

You can unset the alerts set on a file system. If you unset an alert on any file system, you receive alerts for the file systems based on the default values. To unset file system alerts
To unset file system alerts, enter the following:

Storage> fs alert unset numinodes | numspace [fs_name]
where fs_name is the name of the file system for which you want to unset the file system alert. fs_name is optional. Examples for unsetting alerts that are file-system specific:
Storage> fs alert unset numinodes fs1 SFS fs SUCCESS V-288-663 Alert of type [ numinodes ] set to DEFAULT value on the file system fs1 Storage> fs alert unset numspace fs1 SFS fs SUCCESS V-288-663 Alert of type [ numspace ] set to DEFAULT value on the file system fs1
Examples of default alerts for unsetting alerts:

Storage> fs alert unset numinodes SFS fs SUCCESS V-288-663 Alert of type [ numinodes ] set to Default value 0 Storage> fs alert unset numspace SFS fs SUCCESS V-288-663 Alert of type [ numspace ] set to Default value 80 (%)
Displaying file system alerts

You can display the current disk space usage and the set alert value. A D beside the value indicates that the value is the default value used throughout the system.
230
Creating and maintaining file systems About the Partition Secure Notification (PSN) feature
To display file system alerts
To display file system alerts, enter the following:

Storage> fs alert show
For example:
Storage> fs alert show File System Alert Type =========== ========== fs0 numspace fs0 numinodes fs1 numspace fs1 numinodes fs4 numspace fs4 numinodes
Value ========= 80% (D) 6500 80% (D) 8000 80(D)% 2000000 (D)
Current Usage ============= 2% 1000 2% 10000 3% 4
About the Partition Secure Notification (PSN) feature

FileStore is integrated with Symantec Enterprise Vault, a data archiving application, such that FileStore can be used as a backend data store for non-WORM and WORM files for Enterprise Vault. Enterprise Vault can be configured to retain original items that have been archived until the vault store partition has been backed up. Enterprise Vault provides a safety copy setting for each vault store for the above purpose. The safety copy setting can be set to various values like Immediately After Archive or After backup. To support the After backup option, the vault store, for example, in this case, FileStore has to provide a notification to Enterprise Vault after it has successfully made a redundant copy of the data. Enterprise Vault can then remove the safety copies. Enterprise Vault also creates shortcuts and placeholders at this time, if Enterprise Vault is configured to do so. For more information about Enterprise Vault, refer to the Symantec Enterprise Vault Administrator's Guide. Note: To configure Enterprise Vault to work with partitions supported by FileStore, when the Enterprise Vault Administration Console (VAC) asks you to input the Location for the new Vault Store Partition, enter the following as an example: \\10.209.105.101\myshare_myfs1\test\. The final backslash (\) needs to be entered to add the partition. The Partition Secure Notification (PSN) feature refers to the FileStore feature that provides the above-mentioned notifications to Enterprise Vault. This feature is supported when either an NDMP backup or the FileStore replication service is
231
used. After each NDMP backup or replication session is completed, PSN finds the list of all Enterprise Vault partitions in PSN-enabled file systems, and notifies Enterprise Vault by creating an .xml file in the partition roots in an Enterprise Vault-specified format.
Enabling the Partition Secure Notification (PSN) feature

The Storage> fs evpsn enable command enables the Enterprise Vault (EV) Partition Secure Notification (PSN) feature on the specified file system. The specified file system must be online to enable this feature. To enable the Partition Secure Notification (PSN) feature
To enable the PSN feature, enter the following:

Storage> fs evpsn enable fs_name
where fs_name is the specified file system where you want to enable the PSN feature. For example:
Storage> fs evpsn enable fs1 SFS fs SUCCESS V-288-650 evpsn enabled on fs1 successfully.
Disabling the Partition Secure Notification (PSN) feature

The Storage > evpsn disable command disables the Enterprise Vault (EV) Partition Secure Notification (PSN) feature on the specified file system. The specified file must be online to disable this feature. To disable the Partition Secure Notification (PSN) feature
To disable the PSN feature, enter the following:

Storage> fs evpsn disable fs_name
where fs_name is the specified file system where you want to disable the PSN feature. For example:
Storage> fs evpsn disable fs1 SFS fs SUCCESS V-288-652 evpsn disabled on fs1 successfully.
232
Listing the online file systems that have the Partition Secure Notification (PSN) feature enabled
The Storage> fs evpsn list command displays the list of online file systems that have the Enterprise Vault (EV) Partition Secure Notification (PSN) feature enabled. To list the online file systems that have the Partition Secure Notification (PSN) feature enabled
To list the online file systems that have the Partition Secure Notification (PSN) feature enabled, enter the following:
Storage> fs evpsn list
For example:
Storage> fs evpsn FS ============ fs1 list
Chapter
Using Symantec FileStore as a CIFS server


About configuring FileStore for CIFS About configuring CIFS for standalone mode Configuring CIFS server status for standalone mode About configuring CIFS for NT domain mode Configuring CIFS for the NT domain mode About leaving an NT domain Changing NT domain settings Changing security settings Changing security settings after the CIFS server is stopped About Active Directory (AD) About configuring CIFS for Active Directory (AD) domain mode About setting NTLM Setting NTLM About setting trusted domains About storing account information Storing user and group accounts
234
Using Symantec FileStore as a CIFS server About configuring FileStore for CIFS
About reconfiguring the CIFS service Reconfiguring the CIFS service About managing CIFS shares Sharing file systems using CIFS and NFS protocols About mapping user names for CIFS/NFS sharing About load balancing for the normal clustering mode About load balancing for the ctdb clustering mode Splitting a CIFS share About managing home directories About ctdb clustering modes Exporting a directory as a CIFS share Exporting the same file system/directory as a different CIFS share About switching the clustering mode About migrating CIFS shares and home directories Setting the aio_fork option Setting the netbios aliases for the CIFS server About managing local users and groups
About configuring FileStore for CIFS

The Common Internet File System (CIFS), also known as the Server Message Block (SMB), is a network file sharing protocol that is widely used on Microsoft and other operating systems. This chapter describes the initial configuration of the FileStore CIFS service on two clustering modes and three operating modes, and how to reconfigure the FileStore CIFS service when, some CIFS settings are changed. The following clustering modes are supported by FileStore:

Normal Clustered Trivial Database (CTDB) - a cluster implementation of the TDB (Trivial database) based on the Berkeley database API
The following operating modes are supported by FileStore:
Using Symantec FileStore as a CIFS server About configuring FileStore for CIFS
235
User Domain ADS
Each clustering mode supports all of the three operating modes. The ctdb clustering mode is a different clustered implementation of FileStore CIFS, which supports almost all of the features that are supported by normal clustering mode as well as some additional features. Additional features supported in ctdb clustering mode:

Directory-level share support Multi-instance share export of a file system/directory Simultaneous access of a share from multiple nodes and therefore better load balancing
See About ctdb clustering modes on page 309. FileStore can be integrated into a network that consists of machines running Microsoft Windows. You can control and manage the network resources by using Active Directory or NT workgroup domain controllers. Before you use FileStore with CIFS, you must have administrator-level knowledge of the Microsoft operating systems, Microsoft services, and Microsoft protocols (including Active Directory and NT services and protocols). You can find more information about them at: www.microsoft.com. To access the commands, log into your administrative console (master, system-admin, or storage-admin) and enter CIFS> mode. See About using the FileStore command-line interface on page 33. When serving the CIFS clients, FileStore can be configured to operate in one of the operating mode environments described in Table 9-1. Table 9-1 Mode
Standalone
CIFS operating mode environments Definition

Information about the user and group accounts is stored locally on FileStore. FileStore also authenticates users locally using the Linux password and group files. This mode of operation is provided for FileStore testing and may be appropriate in other cases, for example, when FileStore is used in a small network and is not a member of a Windows security domain. In this mode of operation, you must create the local users and groups; they can access the shared resources subject to authorization control.
236
Using Symantec FileStore as a CIFS server About configuring CIFS for standalone mode
Table 9-1 Mode

NT Domain
CIFS operating mode environments (continued) Definition

FileStore becomes a member of an NT4 security domain. The domain controller (DC) stores user and group account information, and the Microsoft NTLM or NTLMv2 protocol authenticates. FileStore becomes a member of an AD security domain and is configured to use the services of the AD domain controller, such as DNS, LDAP, and NTP. Kerberos, NTLMv2, or NTLM authenticate users.
Active Directory
When FileStore operates in the NT or AD domain mode, it acts as a domain member server and not as the domain controller.
About configuring CIFS for standalone mode

If you do not have an AD server or NT domain controller, you can use FileStore as a standalone server. FileStore is used in standalone mode when testing FileStore functionality and when it is not a member of a domain. Before you configure the CIFS service for the standalone mode, do the following:

Make sure that the CIFS server is not running. Set security to user. Start the CIFS server.
To make sure that the configuration has changed, do the following:

Check the server status. Display the server settings. Configure CIFS for standalone mode commands Definition
Checks the status of the CIFS server. See Configuring CIFS server status for standalone mode on page 237.
Table 9-2 Command

server status
server stop
Stops the CIFS server if it is running. See Configuring CIFS server status for standalone mode on page 237.
show
Checks the security setting. See Configuring CIFS server status for standalone mode on page 237.
Using Symantec FileStore as a CIFS server Configuring CIFS server status for standalone mode
237
Table 9-2 Command

set security user
Configure CIFS for standalone mode commands (continued) Definition

Sets security to user. This is the default value. In standalone mode you do not need to set the domaincontroller, domainuser, or domain. See Configuring CIFS server status for standalone mode on page 237.
server start
Starts the service in standalone mode. See Configuring CIFS server status for standalone mode on page 237.
Configuring CIFS server status for standalone mode

To check the CIFS server status
To check the status of the CIFS server, enter the following:

CIFS> server status
Be default, security is set to user, the required setting for standalone mode. The following example shows that security was previously set to ads. For example:
CIFS> server status CIFS Status on sfs_01 : ONLINE CIFS Status on sfs_02 : ONLINE Homedirfs Security Domain membership status Domain Domain Controller Domain User Clustering Mode : : : : : : : fs1 ads Disabled SYMANTECDOMAIN.COM SYMSERVER administrator normal
If the server is running, enter the following:

CIFS> server stop Stopping CIFS Server.....Success.
238
To check the security setting
Check the current settings before setting security, enter the following:
CIFS> show
For example:
Name ---netbios name netbios aliases ntlm auth allow trusted domains homedirfs aio size idmap backend workgroup security Domain Domain user Domain Controller Clustering Mode Value ----ctdb yes no 1024 rid:10000-1000000 SYMANTECDOMAIN ads SYMANTECDOMAIN.COM administrator SYMSERVER normal
To set security to user, enter the following:

CIFS> set security user Global option updated. Note: Restart the CIFS server.
239
To start the CIFS service in standalone mode
To start the service in standalone mode, enter the following:

CIFS: server start Starting CIFS Server.....Success.
To display the new settings, enter the following:

CIFS> show
For example:
Name ---netbios name netbios aliases ntlm auth allow trusted domains homedirfs aio size idmap backend workgroup security Domain Domain user Domain Controller Clustering Mode Value ----mycluster yes no 1024 rid:10000-1000000 SYMANTECDOMAIN user SYMANTECDOMAIN.COM administrator SYMSERVER normal
To make sure that the server is running in standalone mode, enter the following:
CIFS> server status
For example:
CIFS> server status CIFS Status on sfs_01 : ONLINE CIFS Status on sfs_02 : ONLINE Homedirfs Security Clustering Mode : fs1 : user : normal
The CIFS service is now running in standalone mode.
240
Using Symantec FileStore as a CIFS server About configuring CIFS for NT domain mode
See About managing local users and groups on page 326. See About managing CIFS shares on page 282.
About configuring CIFS for NT domain mode

Before you configure the CIFS service for the NT domain mode, do the following:

Make sure that an NT domain has already been configured. Make sure that FileStore can communicate with the domain controller (DC) over the network. Make sure that the CIFS server is stopped. Set the domain user, domain, and domain controller. Set the security to domain. Start the CIFS server.
To make sure that the configuration has changed, do the following:

Check the server status. Display the server settings. Configuring CIFS for NT domain mode commands Definition
Sets the name of the domain user. The credentials of the domain user will be used at the domain controller while joining the domain. Therefore the domain user should be an existing NT domain user who has permission to perform the join domain operation. See Configuring CIFS for the NT domain mode on page 242.
Table 9-3 Command

set domainuser
set domain
Sets the name for the NT domain that you would like FileStore to join and become a member. See Configuring CIFS for the NT domain mode on page 242.
Using Symantec FileStore as a CIFS server About configuring CIFS for NT domain mode
241
Table 9-3 Command
Configuring CIFS for NT domain mode commands (continued) Definition

Sets the domain controller server names. You can pass a comma-separated list of primary and backup domain controller server names.
set domaincontroller
Note: If security is set to domain, you can use both the AD server
and the Windows NT 4.0 domain controller as domain controllers. However, if you use the Windows NT 4.0 domain controller, you can only use the netbios name of the domain controller to set the domaincontroller parameter. See Configuring CIFS for the NT domain mode on page 242. set security Before you set the security for the domain, you must set the domaincontroller, domainuser, and domain. See Configuring CIFS for the NT domain mode on page 242. set workgroup Sets the workgroup name. If the name of the WORKGROUP or NETBIOS domain name is different from the domain name, use this command to set the WORKGROUP name. See Configuring CIFS for the NT domain mode on page 242. server start The server joins the NT domain only when the server is started after issuing the CIFS> set security command. See Configuring CIFS for the NT domain mode on page 242.
242
Using Symantec FileStore as a CIFS server Configuring CIFS for the NT domain mode
Configuring CIFS for the NT domain mode

To set the domain user name for NT mode
To verify that the CIFS server is stopped, enter the following:

CIFS> server status
If the server is running, stop the server. enter the following:

CIFS> server stop
To set the user name, enter the following:

CIFS> set domainuser username
where username is an existing NT domain user who has permission to perform the join domain operation. For example:
CIFS> set domainuser administrator Global option updated. Note: Restart the CIFS server.
To set the domain for the NT domain node
To set the domain, enter the following:

CIFS> set domain domainname
where domainname is the name of the domain that FileStore will join. For example:
CIFS> set domain SYMANTECDOMAIN.COM Global option updated. Note: Restart the CIFS server.
243
To set the domain controller server names for the NT domain mode
To set the domain controller server names, enter the following:

CIFS> set domaincontroller servernames
where servernames is a comma-separated list of primary and backup domain controller server names. The server name is the netbios name if it is a Windows NT 4.0 domain controller. For example, if the domain controller is a Windows NT 4.0 domain controller, enter the server name SYMSERVER:
CIFS> set domaincontroller SYMSERVER Global option updated. Note: Restart the CIFS server.
To set security to domain for the NT domain mode
To set security to domain, enter the following:

CIFS> set security security
Enter domain for security.

CIFS> set security domain Global option updated. Note: Restart the CIFS server.
To set the workgroup name for the NT domain mode
To set the workgroup name if the WORKGROUP or NetBIOS domain name is different from the domain name, enter the following:
CIFS> set workgroup workgroup
where workgroup sets the WORKGROUP name. If the name of the WORKGROUP or NetBIOS domain name is different from the domain name, use this command to set the WORKGROUP name. For example, if SIMPLE is the name of the WORKGROUP you want to set, you would enter the following:
CIFS> set workgroup SIMPLE
Though the following symbols $,( ), ', and & are valid characters for naming a WORKGROUP, the FileStore CIFS implementation does not allow using these symbols.
244
To start the CIFS server for the NT domain mode
To start the CIFS server, enter the following:

CIFS> server start
You are prompted for a domainuser password by:

CIFS> server start Trying to become a member in domain SYMANTECDOMAIN.COM ... Enter password for user 'administrator':
When you enter the correct password, the following messages appear:
Joined domain SYMANTECDOMAIN.COM OK Starting CIFS Server.....Success.
To find the current settings for the domain name, domain controller name, and domain user name, enter the following:
CIFS> show
To make sure that the service is running as a member of the NT domain, enter the following:
CIFS> server status
For example:
CIFS> server status CIFS Status on sfs_01 : ONLINE CIFS Status on sfs_02 : ONLINE Homedirfs Security Domain membership status Domain Domain Controller Domain User Clustering Mode : : : : : : : fs1 domain Enabled SYMANTECDOMAIN.COM SYMSERVER administrator normal
The CIFS service is now running in the NT domain mode. You can export the shares, and domain users can access the shares subject to authentication and authorization control.
Using Symantec FileStore as a CIFS server About leaving an NT domain
245
About leaving an NT domain

There is no FileStore command that lets you leave an NT domain. It happens automatically when the security or domain settings change, and then starts or stops the CIFS server. Thus, FileStore provides the domain leave operation depending on existing security and domain settings and new administrative commands. However, the leave operation requires the credentials of the old domains user. See Changing NT domain settings on page 245. Table 9-4 Command
set domain
Change NT domain settings commands Definition

Sets the domain. When you change any of the domain settings and you restart the CIFS server, the CIFS server leaves the old domain. Thus, when a change is made to either one or more of the domain, domain controller, or domain user settings, and the next time the CIFS server is started, the CIFS server first attempts to leave the existing join, and then joins the NT domain with the new settings. See Changing NT domain settings on page 245.
set security user
Sets the security user. When you change the security setting, and you start or stop the CIFS server, the CIFS server leaves the existing NT domain. For example, if you change the security setting from domain to user and you stop or restart the CIFS server, it leaves the NT domain. See Changing security settings on page 247. If the CIFS server is already stopped, and you change the security to a value other than domain, FileStore leaves the domain. This method of leaving the domain is provided so that if a CIFS server is already stopped, and may not be restarted soon, you have a way to leave an existing join to the NT domain. See Changing security settings after the CIFS server is stopped on page 247.
Changing NT domain settings

Each case assumes that the FileStore cluster is part of an NT domain.
246
Using Symantec FileStore as a CIFS server Changing NT domain settings
To verify if cluster is part of NT domain
To verify if your cluster is part of the NT domain, enter the following:

CIFS> server status CIFS Status on sfs_01 : ONLINE CIFS Status on sfs_02 : ONLINE Homedirfs Security Domain membership status Domain Domain Controller Domain User Clustering Mode : : : : : : : fs1 domain Enabled SYMANTECDOMAIN.COM SYMSERVER administrator normal
To change domain settings
To stop the CIFS server, enter the following:

To change the domain, enter the following:

CIFS> set domain newdomain.com Global option updated. Note: Restart the CIFS server.
where newdomain.com is the new domain name. When you start the CIFS server, the CIFS server tries to leave the existing domain. This requires the old domainuser to enter their password. After the password is supplied, and the domain leave operation succeeds, the CIFS server joins an NT domain with the new settings.

CIFS> server start Disabling membership in existing domain SYMANTECDOMAIN.COM Enter password for user 'administrator' of domain SYMANTECDOMAIN.COM : Left domain SYMANTECDOMAIN.COM Trying to become a member in domain NEWDOMAIN.COM Enter password for user 'administrator':
Using Symantec FileStore as a CIFS server Changing security settings
247
Changing security settings

To change security settings
To set the security to user, enter the following:

To stop the CIFS server:

CIFS> server stop Disabling membership in existing domain SYMANTECDOMAIN.COM Enter password for user 'administrator' of domain SYMANTECDOMAIN.COM : Stopping CIFS Server.....Success. Left domain SYMANTECDOMAIN.COM
Changing security settings after the CIFS server is stopped

To change security settings for a CIFS server that has been stopped
To set security to a value other than domain, enter the following:

CIFS> set security user Disabling membership in existing domain SYMANTECDOMAIN.COM Enter password for user 'administrator' of domain SYMANTECDOMAIN.COM : Left domain SYMANTECDOMAIN.COM Global option updated. Note: Restart the CIFS server.
If the server is stopped, then changing the security mode will disable the membership of the existing domain.
About Active Directory (AD)

In order to provide CIFS services, FileStore must be able to authenticate within the Windows environment. Active Directory (AD) is a technology created by Microsoft that provides a variety of network services including LDAP directory services, Kerberos-based
248
Using Symantec FileStore as a CIFS server About Active Directory (AD)
authentication, Domain Name System (DNS) naming, secure access to resources, and more.
Configuring entries for NTP for authenticating to Active Directory (AD)

FileStore will not join the AD domain if its clock is excessively out-of-sync with the clock on the AD domain controller. Ensure that Network Time Protocol (NTP) is configured on FileStore, preferably on the same NTP server as the AD domain controller. To configure NTP on FileStore for authenticating to Active Directory
To set the NTP server on all of the nodes in the cluster, enter the following command:
System> ntp servername server-name
where server-name specifies the server name or the IP address you want to set. Ensure that the NTP service is enabled with the correct IP address of the NTP server. For example:
System> ntp servername 10.182.128.180
To enable the NTP server on all of the nodes in the cluster, enter the following command:
System> ntp enable
To display the NTP server on all of the nodes in the cluster, enter the following command:
System> ntp show
To check the FileStore clock, enter the following command:

System> clock show
Configuring entries for FileStore DNS for authenticating to Active Directory (AD)
Name resolution must be configured correctly on FileStore. Domain Name System (DNS) is usually used for name resolution.
249
To configure entries for FileStore DNS for authenticating to Active Directory
Create an entry for the FileStore cluster name. The cluster name is chosen at the time of installation, and it cannot be reset afterwards. It is also the NetBios name of the cluster, hence it must resolve to an IP address.
Configure the FileStore cluster name in DNS so that queries to it return the Virtual IP Addresses (VIPs) associated with the FileStore cluster in a round-robin fashion. This is done by creating separate A records that map the cluster name to each VIP. So, if there are four VIPs associated with the FileStore cluster (not including special VIPs for backup, replication, Symantec AntiVirus for FileStore, and so on), then there must be four A records mapping the cluster name to the four VIPs.
250
Verify that the DNS server has correct entries for FileStore by querying from a client:
myclient:~ # nslookup myfilestore Server: 10.182.108.75 Address: 10.182.108.75#53 Name: myfilestore.sfstest-ad2.local Address: 10.182.96.31 Name: myfilestore.sfstest-ad2.local Address: 10.182.96.30 Name: myfilestore.sfstest-ad2.local Address: 10.182.96.29 Name: myfilestore.sfstest-ad2.local Address: 10.182.96.28
In the above scenario, the DNS server at 10.182.108.75, with domain name sfstest-ad2.local, has been configured so that queries for myfilestore.sfstest-ad2.local rotate in a round-robin manner among IP addresses ranging from 10.182.96.28 through 10.182.96.31. All of these are VIPs associated with the FileStore cluster named myfilestore. After configuring the DNS server correctly, FileStore must be configured as a DNS client. This is done during installation, but may be modified by using the following commands:
Network> dns set domainname sfstest-ad2.local Network> dns set nameservers 10.182.108.75 Network> dns enable
251
Verify that DNS client parameters are set correctly by entering the following command:
Network> dns show
Ensure host resolution is querying DNS by checking nsswitch:

Network> nsswitch show hosts: files dns
In the above scenario, host resolution first looks at files, and then DNS. Configuring name resolution correctly is critical in order to successfully join FileStore to Active Directory.
Joining FileStore to Active Directory (AD)

To join FileStore to Active Directory (AD)
To stop the CIFS server, enter the following command.

CIFS> server stop
To set the domain, enter the following command:

CIFS> set domain sfstest-ad2.local
In this example, it is the same as the DNS domain name. This is the domain name of Active Directory.
To set the domain controller, enter the following command:

CIFS> set domaincontroller 10.182.108.75
In this example, it is the same as the DNS server that was configured earlier. This is the IP address of the Active Directory Domain Controller. However, this is not a requirement . The DNS server and Active Directory can run on different servers, and hence this IP address may be different from the IP address of the DNS server.
To set the domain user, enter the following command:

CIFS> set domainuser newuser
This is a user whose credentials are used to join the Active Directory domain. The domainuser must have Domain Join privilege into the Active Directory domain. The domainuser need not be Administrator.
252
To set the security style, enter the following command:

CIFS> set security ads
The other two supported security styles are user for local users and domain for NT Domains. For authenticating to Active Directory, use the ads security style.
To start the CIFS server, enter the following command:

CIFS> server start
FileStore displays the time on the cluster as well as the time on the Active Directory Domain Controller. If NTP has been configured correctly, then there will be no time skew. Otherwise, you will need to reconfigure NTP correctly. See Configuring entries for NTP for authenticating to Active Directory (AD) on page 248. You will be prompted to enter the password of domainuser.
Using Symantec FileStore as a CIFS server About configuring CIFS for Active Directory (AD) domain mode
253
Verifying that FileStore has joined Active Directory (AD) successfully

To verify that FileStore has joined Active Directory (AD) successfully
To verify that FileStore has joined Active Directory successfully, enter the following command:
CIFS> server status
For example:
CIFS> server status CIFS Status on ctdb_01 : ONLINE CIFS Status on ctdb_02 : ONLINE Homedirfs Security Domain membership status Domain Workgroup Domain Controller Domain User Clustering Mode : : : : : : : : fs2,fs6 ads Enabled SYMANTECDOMAIN.COM SYMANTECDOMAIN SYMSERVER administrator normal
Refer to the Domain membership status line of the output to verify that the FileStore cluster has joined the domain (displays as Enabled) if the join is successful. If the cluster did not join the domain, an informative error message is provided indicating why the FileStore cluster cannot join the domain.
About configuring CIFS for Active Directory (AD) domain mode

This section assumes that an Active Directory (AD) domain has already been configured and that FileStore can communicate with the AD domain controller (DC) over the network. The AD domain controller is also referred to as the AD server.
254
Table 9-5 Command

set domainuser
Configure CIFS for AD domain mode commands Definition

Sets the name of the domain user. The domain user's credentials will be used at the domain controller while joining the domain. Therefore, the domain user should be an existing AD user who has the permission to perform the join domain operation. See Configuring CIFS for the AD domain mode on page 255.
set domain
Sets the name of the domain for the AD domain mode that FileStore will join. See Configuring CIFS for the AD domain mode on page 255.
Sets the domain controller server name. See Configuring CIFS for the AD domain mode on page 255.
set security
Sets security for the domain. You must first set the domaincontroller, domainuser, and domain. See Configuring CIFS for the AD domain mode on page 255.
set workgroup
Sets the workgroup name. If the name of the WORKGROUP or NETBIOS domain name is different from the domain name, use this command to set the WORKGROUP name. See Configuring CIFS for the AD domain mode on page 255.
server start
Starts the server. The CIFS server joins the Active Directory domain only when the server is started after issuing the CIFS> set security command. See Configuring CIFS for the AD domain mode on page 255.
255
Configuring CIFS for the AD domain mode

To set the domain user for AD domain mode

CIFS> server status
If the server is running, stop the server. enter the following:

CIFS> server stop
To set the domain user, enter the following:

where username is the name of an existing AD domain user who has permission to perform the join domain operation. For example:
To set the domain for AD domain mode
To set the domain for AD domain mode, enter the following:

where domainname is the name of the domain. For example:

CIFS> set domain SYMANTECDOMAIN.COM Global option updated. Note: Restart the CIFS server.
256
To set the domain controller for AD domain mode
To set the domain controller, enter the following:

CIFS> set domaincontroller servername
where servername is the server's IP address or DNS name. For example, if the server SYMSERVER has an IP address of 172.16.113.118, you can specify one of the following:
CIFS> set domaincontroller 172.16.113.118 Global option updated. Note: Restart the CIFS server.
or
To set security to ads
To set security to ads, enter the following:

CIFS> set security security
Enter ads for security.

CIFS> set security ads Global option updated. Note: Restart the CIFS server.
To set the workgroup
To set the workgroup name if the WORKGROUP or NetBIOS domain name is different from the domain name, enter the following:
CIFS> set workgroup workgroup
where workgroup sets the WORKGROUP name. If the name of the WORKGROUP OR NetBIOS domain name is different from the domain name, use this command to set the WORKGROUP name. For example, if SIMPLE is the name of the WORKGROUP you want to set, you would enter the following:
CIFS> set workgroup SIMPLE
Though the following symbols $,( ), ', and & are valid characters for naming a WORKGROUP, the FileStore CIFS implementation does not allow using these symbols.
257
To start the CIFS server

CIFS> server start The skew of the system clock with respect to Domain controller is: -17 seconds Time on Domain controller : Thu Dec 4 05:21:47 2008 Time on this system : Thu Dec 4 05:22:04 PST 2008 If the above clock skew is greater than that allowed by the server, then the system won't be able to join the AD domain Trying to become a member in AD domain SYMANTECDOMAIN.COM ... Enter password for user 'administrator':
After you enter the correct password for the user administrator belonging to AD domain SYMANTECDOMAIN.COM, the following message appears:
Joined domain SYMANTECDOMAIN.COM OK Starting CIFS Server.....Success.
To make sure that the service is running, enter the following:

CIFS> server status CIFS Status on sfs_01 : ONLINE CIFS Status on sfs_02 : ONLINE Homedirfs Security Domain membership status Domain Domain Controller Domain User Clustering Mode : : : : : : : fs1 ads Enabled SYMANTECDOMAIN.COM SYMSERVER administrator normal
The CIFS server is now running in the AD domain mode. You can export the shares, and the domain users can access the shares subject to the AD authentication and authorization control.
258
Using multi-domain controller support in CIFS

FileStore allows you to set a comma-separated list of primary and backup domain controllers for the given domain. For example:
CIFS> set domaincontroller SYMSERVER1,SYMSERVER2,SYMSERVER3 Global option updated. Note: Restart the CIFS server.
You will need to stop and start the CIF server. See Reconfiguring the CIFS service on page 280. To display the list of domain controllers
To display the list of domain controllers, enter the following:

CIFS> show Name ---netbios name ntlm auth allow trusted domains homedirfs aio size idmap backend rid workgroup security Domain Domain user Domain Controller Clustering Mode Value ----sfs yes no 1024 10000-1000000 SYMANTECDOMAIN ads SYMANTECDOMAIN.COM administrator SYMSERVER1 SYMSERVER2 SYMSERVER3 normal
If the primary domain controller goes down, the CIFS server tries the next domain controller in the list until it receives a response. You should always point FileStore to the trusted domain controllers to avoid any security issues. FileStore will not perform list reduction or reordering, instead it will use the list as it is. So, avoid entering the redundant name for the same domain controller.
About leaving an AD domain

There is no FileStore command that lets you leave an AD domain. It happens automatically as a part of change in security or domain settings, and then starts or stops the CIFS server. Thus, FileStore provides the domain leave operation
259
depending on existing security and domain settings and new administrative commands. However, the leave operation requires the credentials of the old domains user. All of the cases for a domain leave operation have been documented in Table 9-6. Table 9-6 Command
set domain
Change AD domain mode settings commands Definition

Sets the domain. When you change any of the domain settings and you restart the CIFS server, the CIFS server leaves the old domain. Thus, when a change is made to either one or more of domain, domain controller, or domain user settings, and the next time the CIFS server is started, the CIFS server first attempts to leave the existing join and then joins the AD domain with the new settings. See Changing domain settings for AD domain mode on page 259.
set security user
Sets the security user. If you change the security setting from ads to user and you stop or restart the CIFS server, it leaves the AD domain. When you change the security setting, and you stop or restart the CIFS server, the CIFS server leaves the existing AD domain. For example, the CIFS server leaves the existing AD domain if the existing security is ads, and the new security is changed to user, and the CIFS server is either stopped, or started again. See Changing domain settings for AD domain mode on page 259. If the CIFS server is already stopped, changing the security to a value other than ads causes FileStore to leave the domain. Both the methods mentioned earlier require either stopping or starting the CIFS server. This method of leaving the domain is provided so that if a CIFS server is already stopped, and may not be restarted in near future, you should have some way of leaving an existing join to AD domain. See Changing domain settings for AD domain mode on page 259.
Changing domain settings for AD domain mode

Each case assumes that the FileStore cluster is part of an AD domain.
260
To verify cluster is part of an AD domain
To verify that you cluster is part of an AD domain, enter the following:

CIFS> server status CIFS Status on SFS_01 : ONLINE CIFS Status on SFS_02 : ONLINE Homedirfs Security Domain membership status Domain Domain Controller Domain User Clustering Mode : : : : : : : fs1 ads Enabled SYMANTECDOMAIN.COM SYMSERVER administrator normal
261
To change domain settings for AD domain mode
To stop the CIFS server, enter the following:

To change the domain, enter the following:

CIFS> set domain newdomain.com
When you start the CIFS server, it tries to leave the existing domain. This requires the old domainuser to enter its password. After the password is supplied, and the domain leave operation succeeds, the CIFS server joins an AD domain with the new settings.

CIFS> server start Disabling membership in existing AD domain SYMANTECDOMAIN.COM Enter password for user 'administrator' of domain SYMANTECDOMAIN.COM : Left domain SYMANTECDOMAIN.COM The skew of the system clock with respect to Domain controller is: -18 seconds Time on this system: Thu Dec 4 05:21:47 2008 Time on this system : Thu Dec 4 05:22:04 PST 2008 If the above clock skew is greater than that allowed by the server, then the system won't be able to join the AD domain Trying to become a member in AD domain NEWDOMAIN.COM... Enter password for user 'administrator':
262
Using Symantec FileStore as a CIFS server About setting NTLM
To change the security settings for the AD domain mode
To set the security to user, enter the following:

To stop the CIFS server:

CIFS> server stop Disabling membership in existing AD domain SYMANTECDOMAIN.COM Enter password for user 'administrator' of domain SYMANTECDOMAIN.COM : Stopping CIFS Server.....Success. Left AD domain SYMANTECDOMAIN.COM
Changing security settings with stopped server on the AD domain mode
To set security to a value other than ads, enter the following:

CIFS> set security user Disabling membership in existing AD domain SYMANTECDOMAIN.COM Enter password for user 'administrator': Left AD domain SYMANTECDOMAIN.COM Global option updated. Note: Restart the CIFS server.
Removing the AD interface

You can remove the FileStore cluster from the AD domain by using the Active Directory interface. To remove the FileStore cluster
1 2 3
Open the interface Active Directory Users and Computers. In the domain hierarchy tree, click on Computers. In the details pane, right-click the computer entry corresponding to FileStore (this can be identified by the FileStore cluster name) and click Delete.
About setting NTLM

When you use FileStore in NT or AD domain mode, there is an optional configuration step that can be done. You can disable the use of Microsoft NTLM (NT LAN Manager) protocol for authenticating users.
Using Symantec FileStore as a CIFS server About setting NTLM
263
When FileStore CIFS service is running in the standalone mode (with security set to user) some versions of the Windows clients require NTLM authentication to be enabled. You can do this by setting CIFS> set ntlm_auth to yes. When NTLM is disabled and you use FileStore in the NT domain mode, the only protocol available for user authentication is Microsoft NTLMv2. When NTLM is disabled and you use FileStore in AD domain mode, the available authentication protocols is Kerberos and NTLMv2. The one used depends on the capabilities of both the FileStore clients, and domain controller. If no special action is taken, FileStore allows the NTLM protocol to be used. For any specific CIFS connection, all the participants, that is the client machine, FileStore and domain controller select the protocol that they all support and that provides the highest security. In the AD domain mode, Kerberos provides the highest security. In the NT domain mode, NTLMv2 provides the highest security. Table 9-7 Command
set ntlm_auth no
Set NTLM commands Definition

Disables NTLM. See Setting NTLM on page 264.
set ntlm_auth yes Enables NTLM. See Setting NTLM on page 264.
264
Using Symantec FileStore as a CIFS server Setting NTLM
Setting NTLM
To disable NTLM

To disable NTLM, enter the following:

CIFS> set ntlm_auth no
For example:
CIFS> set ntlm_auth no Global option updated. Note: Restart the CIFS server.
To start the CIFS service, enter the following:

CIFS> server start Starting CIFS Server.....Success.
To enable NTLM

To enable the NTLM protocol, enter the following:

CIFS> set ntlm_auth yes
For example:
CIFS> set ntlm_auth yes Global option updated. Note: Restart the CIFS server.
To start the CIFS service, enter the following:

Using Symantec FileStore as a CIFS server About setting trusted domains
265
About setting trusted domains

The Microsoft Active Directory supports the concept of trusted domains. When you authenticate users, you can configure domain controllers in one domain to trust the domain controllers in another domain. This establishes the trust relation between the two domains. When FileStore is a member in an AD domain, both FileStore and the domain controller are involved in authenticating the clients. You can configure FileStore to support or not support trusted domains. Table 9-8 Command Set trusted domains commands Definition
set Enables the use of trusted domains in the AD domain mode. allow_trusted_domains Note: If the security mode is user, it is not possible to enable yes AD trusted domains. All the IDMAP backend methods (rid, ldap, and hash) are able to support trusted domains. See Setting Active Directory trusted domains on page 275. set Disables the use of trusted domains in the AD domain mode. allow_trusted_domains See Setting Active Directory trusted domains on page 275. no
Allowing trusted domains access to CIFS when setting an LDAP IDMAP backend to rid
To allow trusted domains access to CIFS when setting LDAP IDMAP backend to rid
If the CIFS server is running, enter the following:

To set the idmap_backend to rid, enter the following:

CIFS> set idmap_backend rid Global option updated. Note: Restart the CIFS server.
To set allow_trusted_domains to yes, enter the following:

CIFS> set allow_trusted_domains yes Global option updated. Note: Restart the CIFS server.
266
To start the CIF server again, enter the following:

To verify the CIFS server status when there are trusted domains, enter the following:
CIFS> server status CIFS Status on SFS_01 CIFS Status on SFS_02
: ONLINE : ONLINE
Homedirfs : homefs Security : ads Domain membership status : Enabled Domain : SYMANTECDOMAIN.COM Workgroup : SYMANTECDOMAIN Domain Controller : SYMSERVER Domain User : administrator Clustering Mode : normal Trusted Domains : SYMANTECDOMAIN1 [SYMANTECDOMAIN2] SYMANTECDOMAIN3
Domain names containing square brackets indicate that the domain used to be a trusted domain, but the domain is currently obsolete.
Allowing trusted domains access to CIFS when setting an LDAP IDMAP backend to ldap
To allow trusted domains access to CIFS when setting an LDAP IDMAP backend to ldap
To configure AD as an LDAP IDMAP backend, follow the steps provided at: See About configuring Windows Active Directory as an LDAP IDMAP backend for FileStore for CIFS on page 268.

To set idmap_backend to ldap, enter the following:

CIFS> set idmap_backend ldap Global option updated. Note: Restart the CIFS server.
267

To restart the CIFS server again, enter the following:

: ONLINE : ONLINE
Homedirfs : homefs Security : ads Domain membership status : Enabled Domain : SYMANTECDOMAIN.COM Workgroup : SYMANTECDOMAIN Domain Controller : SYMSERVER Domain User : administrator Clustering Mode : normal Trusted Domains : SYMANTECDOMAIN1 SYMANTECDOMAIN2 SYMANTECDOMAIN3
Allowing trusted domains access to CIF when setting an LDAP IDMAP backend to hash
To allow trusted domains access to CIF when setting an LDAP IDMAP backend to hash

To set idmap_backend to hash, enter the following:

CIFS> set idmap_backend hash Global option updated. Note: Restart the CIFS server.
268

: ONLINE : ONLINE
Homedirfs : homefs Security : ads Domain membership status : Enabled Domain : SYMANTECDOMAIN.COM Workgroup : SYMANTECDOMAIN Domain Controller : SYMSERVER Domain User : administrator Clustering Mode : normal Trusted Domains : SYMANTECDOMAIN1 SYMANTECDOMAIN2 SYMANTECDOMAIN3
About configuring Windows Active Directory as an LDAP IDMAP backend for FileStore for CIFS
The FileStore CIFS server requires equivalent UNIX identities for Windows accounts to service requests from Windows clients. In the case of trusted domains, FileStore has to store the mapped UNIX identities (IDMAP) in a centralized database that is accessible from each of the cluster nodes. Active Directory (AD), as with any LDAP V3 compliant directory service, can function as the backend for FileStore CIFS IDMAP backend storage. When the FileStore CIFS server joins a Windows Active Directory Domain as a member server, and you want to use LDAP as an IDMAP backend, then it is necessary to create an Active Directory application partition for the IDMAP database. To support the creation of an Active Directory application partition, Windows 2003 R2 and above version is required. Active Directory application partition provides the ability to control the scope of replication and allow the placement of replicas in a manner more suitable for dynamic data. As a result, the application directory partition provides the capability of hosting dynamic data in the Active Directory server, thus allowing ADSI/LDAP access to it.
269
By extending the AD schema with the necessary CIFS-schema extensions, and creating an AD application partition, it is possible to store CIFS IDMAP data entries in AD, using one or more domain controllers as IDMAP LDAP backend servers. Also, it is possible to replicate this information in a simple and controlled manner to a subset of AD domain controllers located either in the same domain or in different domains in the AD forest. Note: A single domain user account is used, for example, cifsuser for setting application partition Access Control List (ACL) settings. Make sure the selected user naming context has no space key inside (for example, CN=cifsuser1,CN=Users,DC=example,DC=com). A sample AD server is used, for example, adserver.example.com. Use relevant values when configuring your AD server.
Configuring the Active Directory schema with CIFS-schema extensions

To extend the Active Directory schema with the necessary CIFS-schema extensions
1 2
Login with Schema Admins privileges on the Active Directory Forest Schema Master domain controller. Download ADCIFSSchema.zip from the FileStore server (/opt/VRTSnasgw/install/ADCIFSSchema.zip) with software such as WinSCP.exe. Unzip the file and open each .ldf file to perform a search and replace of the string dc=example,dc=com, replacing the string with the top-level domain component (that is, dc=yourdomain,dc=com) values for the AD forest. Install the schema extensions by executing the schemaupdate.bat file from the command prompt.
To validate the schema extensions
1 2 3 4
Execute regsvr32 schmmgmt.dll in a command prompt window to install the Active Directory Schema Snap-In on the AD server. Enter mmc in Run. On the File menu, click Add/Remove Snapin. In Available snap-ins, click Active Directory Schema, and then click Add.
270
5 6
Click OK. Click Attributes in the left frame, and try to find uidNumber and gidNumber in the right frame. Validate that the uidNumber and gidNumber attributes have no minimum or maximum value setting by viewing the properties of the attribute objects.
To create an application partition
1 2 3
Open a command prompt window on the domain controller that will hold the first replica of the application partition. Enter ntdsutil in the command prompt window. At the ntdsutil command prompt, enter the following:
domain management
If you are using Windows 2008, change this command to the following:
partition management
At the domain management command prompt, enter the following:

connection
At the connection command prompt, enter the following:

connect to server adserver.example.com
At the connection command prompt, enter the following:

quit
271
At the domain management command prompt, enter the following such as:
create nc dc=idmap,dc=example,dc=com null
Example settings:
C:\>ntdsutil ntdsutil: domain management domain management: connection server connections: connect to server adserver.example.com Binding to adserver.example.com ... Connected to adserver.si2m.com using credentials of locally logged on user. server connections: quit domain management: create nc dc=idmap,dc=example,dc=com NULL adding object dc=idmap,dc=example,dc=com domain management: quit ntdsutil: quit Disconnecting from adserver.example.com...
272
Once the application partition has been created, open ADSIedit.msc fromRun, then right-click on ADSI Edit in the left frame, and click connect to ... to connect to the application partition using the settings as indicated:
Name Connection Point Enter Domain. Select or enter a Distinguished Name or Naming Context, as in: dc=idmap,dc=example,dc=com
Computer
Select or enter a domain or server, as in: adserver.example.com
273
Once connected, select the top-level application partition (for example, dc=idmap,dc=example,dc=com) node in the left panel, and right-click to select New then Object from the list, and then select SambaUnixIdPool.
When prompted, enter the following values:

OU attribute uidNumber gidNumber cifsidmap 10000 10000
10 Click Finish to complete the configuration. 11 Once the ou=cifsidmap,dc=idmap,dc=example,dc=com container has been
created, right-click the object, and select properties.
12 On the Security tab, click Add, and proceed to add the cifsuser user account,
and grant the account Read, Write, Create All Child Objects, and Delete All Child Objects permissions.
274
Configuring LDAP as an IDMAP backend using the FileStore CLI

To configure LDAP as an IDMAP backend using the FileStore CLI
1 2
Log into the FileStore cluster CLI using the master account. Configure Network> ldap settings. Example settings:
Network> Network> Network> Network> Network> ldap ldap ldap ldap ldap set basedn dc=idmap,dc=example,dc=com set binddn cn=cifsuser,dc=example,dc=com set rootbinddn cn=cifsuser,cn=users,dc=example,dc=com set server adserver.example.com enable
Configuring the CIFS server with the LDAP backend

To configure the CIFS server with the LDAP backend
1 2 3 4
Log into the FileStore cluster CLI using the master account. Set the domain, domaincontroller, and domainuser. Set security to ads. Set idmap_backend to ldap, and specify idmap OU as cifsidmap. Example settings:
CIFS> CIFS> CIFS> CIFS> CIFS> CIFS> set domain example.com set domainuser administrator set domaincontroller adserver.example.com set security ads set idmap_backend ldap cifsidmap server start
Start the CIFS server. The CIFS server will take some time to import all the users from the joined domain and trusted domain(s) to the application partition. Wait for at least ten minutes before trying to access the shares from Windows clients after starting the CIFS server. To validate that IDMAP entries are being entered correctly in the Active Directory application partition, connect to the Active Directory application partition using an LDAP administration tool, for example, LDP or ADSIEdit. Expand the IDMAP container (ou=cifsidmap). There should be numerous entries.
275
Setting Active Directory trusted domains

To enable Active Directory (AD) trusted domains

To enable trusted domains, enter the following:

CIFS> set allow_trusted_domains yes
For example:

To disable trusted domains

To disable trusted domains, enter the following:

CIFS> set allow_trusted_domains no
For example:
CIFS> set allow_trusted_domains no Global option updated. Note: Restart the CIFS server.

276
Using Symantec FileStore as a CIFS server About storing account information
About storing account information

FileStore maps between the domain users and groups (their identifiers) and local representation of these users and groups. Information about these mappings can be stored locally on FileStore or remotely using the DC directory service. FileStore uses the idmap_backend configuration option to decide where this information is stored. This option can be set to one of the following:
rid Maps SIDs for domain users and groups by deriving UID and GID from RID on the FileStore CIFS server. Stores the user and group information in the LDAP directory service. Maps SIDs for domain users and groups to 31-bit UID and GID by the implemented hashing algorithm on the FileStore CIFS server.
ldap hash
Note: SID/RID are Microsoft Windows concepts that can be found at: http://msdn.microsoft.com/en-us/library/aa379602(VS.85).aspx. The rid and hash values can be used in any of the following modes of operation:

Standalone NT domain AD domain
rid is the default value for idmap_backend in all of these operational modes. The ldap value can be used if the AD domain mode is used.
Using Symantec FileStore as a CIFS server About storing account information
277
Table 9-9 Command
Store account information commands Definition
set idmap_backend Configures FileStore to store information about users and groups rid locally. Trusted domains are allowed if allow_trusted_domains is set to yes. The uid_range is set to 10000-1000000 by default. Change the default range in cases where it is not appropriate to accommodate local FileStore cluster users, Active Directory, or trusted domain users. Do not attempt to modify LOW_RANGE_ID (10000) if user data has already been created or copied on the CIFS server. This may lead to data access denied issues since the UID changes. See Storing user and group accounts on page 278. set idmap_backend Allows you to obtain the unique SID to UID/GID mappings by the hash implemented hashing algorithm. Trusted domains are allowed if allow_trusted_domains is set to yes. The uid_range is set to 10000-1000000 by default. See Storing user and group accounts on page 278. set idmap_backend Configures FileStore to store information about users and groups in ldap a remote LDAP service. You can only use this command when FileStore is operating in the AD domain mode. The LDAP service can run on the domain controller or it can be external to the domain controller.
Note: For FileStore to use the LDAP service, the LDAP service must
include both RFC 2307 and proper schema extensions. See Configuring LDAP as an IDMAP backend using the FileStore CLI on page 274. This option tells the CIFS server to obtain SID to UID/GID mappings from a common LDAP backend. This option is compatible with multiple domain environments. So allow_trusted_domains can be set to yes. If idmap_backend is set to ldap, you must first configure the FileStore LDAP options using the Network> ldap commands. See About LDAP on page 151. See Storing user and group accounts on page 278.
278
Using Symantec FileStore as a CIFS server Storing user and group accounts
Storing user and group accounts

To set idmap_backend to rid

To store information about user and group accounts locally, enter the following:
CIFS> set idmap_backend rid [uid_range]
where uid_range represents the range of identifiers that are used by FileStore when mapping domain users and groups to local users and groups. The default range is 10000-1000000.

To set idmap_backend to LDAP
To make sure that you have first configured LDAP, enter the following:
Network> ldap show

To use the remote LDAP store for information about the user and group accounts, enter the following:
CIFS> set idmap_backend ldap [idmap_ou]
where idmap_ou represents the CIFS idmap Organizational Unit Name (OU) configured on the LDAP server, which is used by FileStore when mapping users and groups to local users and groups. The default value is cifsidmap.

Using Symantec FileStore as a CIFS server About reconfiguring the CIFS service
279
To set idmap_backend to a hash algorithm

To store information about user and group accounts locally, enter the following:
CIFS> set idmap_backend hash [uid_range]
where the uid_range represents the range of identifiers that are used by FileStore. The default range is 10000-1000000.

About reconfiguring the CIFS service

Sometime after you have configured the CIFS service, and used it for awhile, you need to change some of the settings. For example, you may want to allow the use of trusted domains or you need to move FileStore from one security domain to another. To carry out these changes, set the new settings and then start the CIFS server. As a general rule, you should stop the CIFS service before making the changes. An example where FileStore is moved to a new security domain (while the mode of operation stays unchanged as, AD domain) is referenced in the section below. See Reconfiguring the CIFS service on page 280. This example deals with reconfiguring CIFS. So make sure that if any of the other AD services like DNS or NTP are being used by FileStore, that FileStore has already been configured to use these services from the AD server belonging to the new domain. Make sure that the DNS service, NTP service and, if used as an ID mapping store, also the LDAP service, are configured as required for the new domain. To reconfigure the CIFS service, do the following:

Make sure that the server is not running. Set the domain user, domain, and domain controller. Start the CIFS server.
280
Using Symantec FileStore as a CIFS server Reconfiguring the CIFS service
Table 9-10 Command

set domainuser
Reconfigure the CIFS service commands Definition

Changes the configuration option to reflect the values appropriate for the new domain. See Reconfiguring the CIFS service on page 280.
set domain
server start
Starts the server and causes it to leave the old domain and join the new Active Directory domain. You can only issue this command after you enter the CIFS> set security command. See Reconfiguring the CIFS service on page 280.
Reconfiguring the CIFS service

To set the user name for the AD

CIFS> server status
If the server is running, stop the server, and enter the following:
CIFS> server stop
To set the user name for the AD, enter the following:
where username is the name of an existing AD domain user who has permission to perform the join domain operation. For example:
Using Symantec FileStore as a CIFS server Reconfiguring the CIFS service
281
To set the AD domain
To set the AD domain, enter the following:

where domainname is the name of the domain. This command also sets the system workgroup. For example:
CIFS> set domain NEWDOMAIN.COM Global option updated. Note: Restart the CIFS server.
To set the AD server
To set the AD server, enter the following:

CIFS> set domaincontroller servername
where servername is the AD server IP address or DNS name. For example, if the AD server SYMSERVER has an IP address of 172.16.113.118, you can specify one of the following:
CIFS> set domaincontroller 172.16.113.118 Global option updated. Note: Restart the CIFS server.
or
If you use the AD server name, you must configure FileStore to use a DNS server that can resolve this name.
282
Using Symantec FileStore as a CIFS server About managing CIFS shares
To start the CIFS server

CIFS> server start The skew of the system clock with respect to Domain controller is: 3 seconds Time on Domain controller : Fri May 30 06:00:03 2008 Time on this system : Fri May 30 06:00:00 PDT 2008 If the above clock skew is greater than that allowed by the server, then the system wont be able to join the AD domain Enter password for user 'administrator': Trying to become a member in AD domain SYMANTECDOMAIN.COM ... Joined domain SYMANTECDOMAIN.COM OK Starting CIFS Server..
To make sure that the service is running, enter the following:

CIFS> server status
To find the current settings, enter the following:

CIFS> show
About managing CIFS shares

You can export the FileStore file systems to the clients as CIFS shares. When a share is created, it is given a name. The name is different from the file system name. Clients use the share name when they import the share. You create and export a share with one command. The same command binds the share to a file system, and you can also use it to specify share properties. In addition to exporting file systems as CIFS share, you can use FileStore to store the users' home directories. Each of these home directories is called a home directory share. Shares which are used to export ordinary file systems (that is, file systems which are not used for home directories), are called ordinary shares to distinguish them from the home directory shares.
283
Table 9-11 Command

share show
Manage the CIFS shares commands Definition

Displays information on one or all exported shares. The information is displayed for a specific share includes the name of the file system which is being exported and the values of the share options. See Setting share properties on page 286.
share add
Exports a file system with the given sharename or re-export new options to an existing share. The new options are updated after this command is run. This CIFS command, which creates and exports a share, takes as input the name of the file system which is being exported, the share name, and optional attributes. You can use the same command for a share that is already exported. You can do this if it is required to modify the attributes of the exported share. A file system used for storing users home directories cannot be exported as a CIFS share, and a file system that is exported as a CIFS share cannot be used for storing users' home directories. See Setting share properties on page 286.
share delete
Stops the associated file system from being exported. Any files and directories which may have been created in this file system remain intact; they are not deleted as a result of this operation. See Setting share properties on page 286.
share allow
Allows only the specified users and groups to access the share. If all is specified, then default access restrictions are restored on the share. By default, all users and groups are allowed to access the share. See Setting share properties on page 286.
share deny
Denies the specified users and groups access to the share. If all is specified, then all the users and groups are not able to access the share. By default, none of the users or groups are denied access to the share.
Note: If a user or group is present in both the share allow and

share deny list, then access is denied to that user or group. See Setting share properties on page 286. share modify Allows you to modify any CIFS share. See Setting share properties on page 286.
284
About the CIFS export options

The following are the CIFS export options. Table 9-12 CIFS export option
rw
CIFS export options Definition

There is a share option which specifies if the files in the share will be read-only or if both read and write access will be possible, subject to the authentication and authorization checks when a specific access is attempted. This share option can be given one of these values, either rw or ro. Grants read and write permission to the exported share.
ro (Default)
Grants read-only permission to the exported share. Files cannot be created or modified. Another configuration option specifies if a user trying to establish a CIFS connection with the share must always provide the user name and password, or if they can connect without it. In this case, only restricted access to the share will be allowed. The same kind of access is allowed to anonymous or guest user accounts. This share option can have one of the following values, either guest or noguest. FileStore allows restricted access to the share when no user name or password is provided.
guest
noguest (Default)
FileStore always requires the user name and password for all of the connections to this share. All Windows Access Control Lists (ACLs) are supported except in the case when you attempt using the Windows Explorer folder Properties > Security GUI to inherit down to a non-empty directory hierarchy while denying all access to yourself. Some advanced Windows Access Control Lists (ACLs) functionality does not work. For example, if you try to create ACL rules on files saved in a CIFS share using Windows explorer while allowing some set of file access for user1 and denying file access for user2, this is not possible when CIFS shares are exported using no_full_acl. When a file system or directory is exported by CIFS, its mode is set to an fs_mode value. It is the UNIX access control set on a file system, and CIFS options like rw/ro do not take precedence over it. This value is reset to 0755 when the CIFS share is deleted. The default is: fs_mode = 1777.
full_acl
no_full_acl (Default)
fs_mode
285
Table 9-12 CIFS export option

dir_mask
CIFS export options (continued) Definition

When a directory is created under a file system or directory exported by CIFS, the necessary permissions are calculated by mapping DOS modes to UNIX permissions. The resulting UNIX mode is then bit-wise 'AND'ed with this parameter. Any bit not set here is removed from the modes set on a directory when it is created. The default is: dir_mask = 0755.
create_mask
When a file is created under a file system or directory exported by CIFS, the necessary permissions are calculated by mapping DOS modes to UNIX permissions. The resulting UNIX mode is then bit-wise 'AND'ed with this parameter. Any bit not set here is removed from the modes set on a file when it is created. The default is: create_mask = 0744.
oplocks (Default)
FileStore supports the CIFS opportunistic locks. You can enable or disable them for a specific share. The opportunistic locks improve performance for some workloads, and there is a share configuration option which can be given one of the following values, either oplocks or nooplocks. FileStore supports opportunistic locks on the files in this share.
nooplocks
No opportunistic locks will be used for this share. Disable the oplocks when:

1) A file system is exported over both CIFS and NFS protocols. 2) Either CIFS or NFS protocol has read and write access.
owner
There are more share configuration options that can be used to specify the user and group who own the share. If you do not specify these options for a share, FileStore uses the current values as default values for these options. You may want to change the default values to allow a specific user or group to be the share owner. Irrespective of who are owner and group of the exported share, any CIFS clients can create folders and files in the share. However, there are some operations that require owner privileges; for example, changing the owner itself, and changing permissions of the top-level folder (that is, the root directory in UNIX terms). To enable these operations, you can set the owner option to a specific user name, and this user can perform the privileged operations.
286
Table 9-12 CIFS export option

group
CIFS export options (continued) Definition

By default, the current group is the primary group owner of the root directory of the exported share. This lets CIFS clients create folders and files in the share. However, there are some operations that require group privileges; for example, changing the group itself, and changing permissions of the top-level folder (that is, the root directory in UNIX terms). To enable these operations, you can set the group option to a specific group name, and this group can perform the privileged operations. FileStore lets you specify a virtual IP address. This address must be part of the FileStore cluster, and is used by the system to serve the share internally.
ip
Note: ip is not a valid CIFS option when using the ctdb clustering
mode. See About ctdb clustering modes on page 309.
Setting share properties

After a file system is exported as a CIFS share, you can decide to change one or more share options. This is done using the same share add command, giving the name of an existing share and the name of the file system exported with this share. FileStore will realize the given share has already been exported and that it is only required to change the values of the share options. For example, to export the file system fs1 with the name share1, enter the following:
CIFS> share add fs1 share1 "owner=administrator,group=domain users,rw" Exporting CIFS filesystem : share1 ... CIFS> share show ShareName FileSystem ShareOptions share1 fs1 owner=administrator,group=domain users,rw
287
To export a file system
To export a file system, enter the following:

CIFS> share add filesystem sharename [cifsoptions] filesystem An FileStore file system that you want to export as a CIFS share. The given file system must not be currently used for storing the home directory shares. The file system or directory path should always start with the file system name, not with the file system mount point /vx. sharename The name for the newly exported share. Names of the FileStore shares are case- sensitive and can consist of the following characters: lower and uppercase letters "a" - "z" and "A" - "Z," numbers "0" - "9" and special characters: "_" and "-". ( "-", cannot be used as the first character in a share name). A comma-separated list of CIFS export options. This part of the command is optional. If a CIFS export option is not provided, FileStore uses the default value. See About the CIFS export options on page 284.
cifsoptions
For example, an existing file system called FSA being exported as a share called ABC:
CIFS> share add FSA ABC rw,guest,owner=john,group=abcdev
288
Displaying CIFS share properties

To display share properties
To display the information about all of the exported shares, enter the following:
CIFS> share show
For example:
CIFS> share show ShareName FileSystem share1 fs1
ShareOptions owner=root,group=root
To display the information about one specific share, enter the following:
CIFS> share show sharename
For example:
CIFS> share show share1 ShareName VIP Address share1 10.10.10.10
289
Allowing specified users and groups access to the CIFS share

To allow specified users and groups access to the CIFS share
To allow specified users and groups access to the CIFS share, enter the following:
CIFS> share allow sharename @group1 [,@group2,user1,user2,...]
sharename
Name of the CIFS share for which you want to allow specified users and groups access. Names of the FileStore shares are case- sensitive and can consist of the following characters: lower and uppercase letters "a" - "z" and "A" - "Z," numbers "0" - "9" and special characters: "_" and "-". ( "-", cannot be used as the first character in a share name).
group
If the CIFS server joined a domain, and there is a space in the user or group name, the user or group name needs to be entered with double quotes (for example, "@domain users"). By default, all groups are allowed to access the shares. In the case where a CIFS share has joined a domain, and the domain contains trusted domains, and allow_trusted_domains is set to yes on the CIFS server, if you want to allow/deny users or groups from the trusted domains, the user or group needs to be prefixed with the trusted domain name. Separate the domain and user/group with a double backslash. For example: CIFS> share allow sharename "@domain name\\group name"
user
Name of the CIFS user allowed access to the CIFS share. By default, all users are allowed to access the shares.
If all is specified, then default access restrictions are restored on the CIFS share.
CIFS> share allow share1 user1,@group1 Warning: Modifying an already existing share. .........Done
290
Denying specified users and groups access to the CIFS share

To deny specified users and groups access to the CIFS share
To deny specified users and groups access to the CIFS share, enter the following:
CIFS> share deny sharename @group1[,@group2,user1,user2,...]
sharename
Name of the CIFS share for which you want to deny specified users and groups access. Names of the FileStore shares are case- sensitive and can consist of the following characters: lower and uppercase letters "a" - "z" and "A" - "Z," numbers "0" - "9" and special characters: "_" and "-". ( "-", cannot be used as the first character in a share name).
group
If the CIFS server joined a domain, and there is a space in the user or group name, the user or group name needs to be entered with double quotes (for example, "@domain users"). By default, all groups are allowed to access the shares. In the case where a CIFS share has joined a domain, and the domain contains trusted domains, and CIFS is set to trusted domains as true, if you want to allow/deny users or groups from the trusted domains, the user or group needs to be prefixed with the trusted domain name. Separate the domain and user/group with a double backslash. For example: CIFS> share deny sharename "@domain name\\user name"
user
Name of the CIFS user denied access to the CIFS share. By default, all users are allowed to access the shares.
If all is specified, then all the users and groups are not able to access the share.
CIFS> share deny share1 user1,@group1 Warning: Modifying an already existing share. .........Done
291
Modifying an existing CIFS share

To modify an existing CIFS share
To modify an existing CIFS share, enter the following:

CIFS> share modify sharename [cifsoptions] sharename Name of the CIFS share you want to modify. Names of the FileStore shares are case- sensitive and can consist of the following characters: lower and uppercase letters "a" - "z" and "A" - "Z," numbers "0" - "9" and special characters: "_" and "-". ( "-", cannot be used as the first character in a share name). cifsoptions A comma-separated list of CIFS export options. This part of the command is optional.
For example:
CIFS> share modify share1 ro Warning: Modifying an already existing share. Done
292
Modifying an existing CIFS share with different CIFS options

To modify an existing CIFS share with different CIFS options
To modify an existing CIFS share with different CIFS options, enter the following:
CIFS> share show ShareName FileSystem share3 fs3 share4 fs4
ShareOptions owner=root,group=root,fs_mode=1777 owner=root,group=root,fs_mode=1777,rw
To modify the CIFS share, enter the following:

CIFS> share modify share4 rw,full_acl,oplocks Warning: Modifying an already existing share. ..Done
The CIFS> share modify command overwrites the previous value for cifsoptions. See About the CIFS export options on page 284.
To list the CIFS shares, enter the following:

CIFS> share show ShareName FileSystem share3 fs3 share4 fs4 full_acl,oplocks
ShareOptions owner=root,group=root,fs_mode=1777 owner=root,group=root,fs_mode=1777,rw,
Exporting a CIFS snapshot

To export a CIFS snapshot
To create a CIFS snapshot, enter the following for example:

Storage> snapshot create cf11sp1 CF11
See About snapshots on page 205.
To export the CIFS snapshot, enter the following for example:

CIFS> share add CF11:cf11sp1 cf11sp1 rw,guest
See Adding an NFS share on page 177. A client can access the CIFS snapshot by the CIFS share name, cf11sp1.
293
Deleting a CIFS share

To delete a CIFS share
To delete a share, enter the following:

CIFS> share delete sharename
where sharename is the name of the share you want to delete. For example:
CIFS> share delete share1 Unexporting CIFS filesystem : share1 ..
To confirm the share is no longer exported, enter the following:

CIFS> share show ShareName FileSystem share2 fs2
ShareOptions owner=root,group=root
In the case of any remanent sessions (sessions that are not closed while deleting a CIFS share), FileStore displays the following output:
CIFS> share delete share2 Unexporting CIFS share : share2 ....Success. SFS cifs WARNING V-288-0 There are following remanent sessions. Clients may still access 'share4' unless the relevant processes are killed. Remanent Sessions pid nodename ----------------13966 sfsnode_01 14130 sfsnode_02
This is a rare situation, and it occurs if the following conditions are met:

CIFS server is online CIFS share that is being deleted is ONLINE There are some existing client connections with that CIFS share While deleting the share, some remanent sessions are left
If any condition is failed above, then the CIFS> share delete command output displays as usual.
CIFS> share delete share2 Unexporting CIFS share : share2 ....Success.
294
Using Symantec FileStore as a CIFS server Sharing file systems using CIFS and NFS protocols
Sharing file systems using CIFS and NFS protocols

FileStore provides support for multi-protocol file sharing, where the same file system can be exported to both Windows and UNIX users using the CIFS and NFS (Network File System) protocols. The result is an efficient use of storage by sharing a single data set across multi-application platforms. Figure 9-1 shows how file system sharing for the two protocols works. Figure 9-1 Exporting files systems
Shared Storage File System FS1
2-node FileStore cluster Data access by CIFS protocol Data access by NFS protocol
Windows user
UNIX user
It is recommended that you disable the oplocks option when the following occurs:

A file system is exported over both the CIFS and NFS protocols. Either the CIFS and NFS protocol is set with read and write permission.
295
See Setting share properties on page 286. Note: When a share is exported over both NFS and CIFS protocols, the applications running on the NFS and CIFS clients may attempt to concurrently read or write the same file. This may lead to unexpected results since the locking models used by these protocols are different. For example, an application reads stale data. For this reason, FileStore warns you when the share export is requested over NFS or CIFS and the same share has already been exported over CIFS or NFS, when at least one of these exports allows write access.
296
To export a file system to Windows and UNIX users
Go to the NFS mode and enter the following commands:

NFS> share add ro /vx/fs1 Exporting *:/vx/fs1 with options ro ..Success. NFS> share show /vx/fs1 *(ro)
To export a file system to Windows and UNIX users with read-only permission, go to CIFS mode, and enter the following commands:
CIFS> show Name ---netbios name netbios aliases ntlm auth allow trusted domains homedirfs aio size idmap backend workgroup security Domain Domain user Domain Controller Clustering Mode Value ----mycluster yes no 1024 rid:10000-1000000 SYMANTECDOMAIN ads SYMANTECDOMAIN.COM administrator SYMSERVER normal
CIFS> share add fs1 share1 rw SFS cifs WARNING V-288-0 Filesystem (fs1) is already shared over NFS with 'ro' permission. Do you want to proceed (y/n): y Exporting CIFS filesystem : share1 .. CIFS> share show ShareName share1
FileSystem fs1
ShareOptions owner=root,group=root,rw
When the file system in CIFS is set to homedirfs, the FileStore software assumes that the file system is exported to CIFS users in read and write mode. FileStore does not allow you to export the same file system as an CIFS share and a home
Using Symantec FileStore as a CIFS server About mapping user names for CIFS/NFS sharing
297
directory file system (homedirfs). For example, if the file system fs1 is already exported as a CIFS share, then you cannot set it as homedirfs. To export a file system set as homedirfs
To request that a file system be used for home directories, you need to export the file system. Go to the CIFS mode and enter the following:
CIFS> share show ShareName FileSystem ShareOptions share1 fs1 owner=root,group=root,rw CIFS> set homedirfs fs1 SFS cifs ERROR V-288-615 Filesystem (fs1) is already exported by another CIFS share.
About mapping user names for CIFS/NFS sharing

The CIFS server uses user name mapping to translate login names sent by a Windows client to local or remote UNIX user names. The CIFS server uses file lookup for mapping, and this mapping is unidirectional. You can map a CIFS user to an NFS user, but the reverse operation is not possible. This functionality can be used for the following purposes:

CIFS and NFS sharing by mapping CIFS users to NFS users File sharing among CIFS users by mapping multiple CIFS users to a single UNIX user Mapping between two UNIX users by using the CIFS> mapuser add <CIFSusername> LOCAL <NFSusername> command, where both the CIFS user and the NFS user are UNIX users
User name mapping is stored in a configuration file. When user name mapping takes place is dependent on the current security configurations. If security is set to user, mapping is done prior to authentication, and a password must be provided for the mapped user name. For example, if there is a mapping between the users CIFSuser1 and NFSuser1. If CIFSuser1 wants to connect to the FileStore server, then CIFSuser1 needs to provide a password for NFSuser1. In this case, NFSuser1 must be the CIFS local user. If security is set to either ads or domain, user name mapping is done after authentication with the domain controller. This means, the actual password must be supplied for the login user CIFSuser1 in the example cited above. In this case, NFSuser1 may not be the CIFS local user.
298
Using Symantec FileStore as a CIFS server About load balancing for the normal clustering mode
For example, to map a CIFS user to an NFS user:

CIFS> mapuser add CIFSuser1 SYMANTECDOMAIN.COM NFSuser1
For example, to show the mapping between a CIFS user and an NFS user:
CIFS> mapuser show CIFSUserName DomainName NFSUserName CIFSuser1 SYMANTECDOMAIN NFSuser1
For example, to remove the mapping between a CIFS user and an NFS user:
CIFS> mapuser remove CIFSuser1 SYMANTECDOMAIN.COM
The domain you specify for CIFS user name mapping must be the netbios domain name (instead of the Active Directory DNS domain name) for the user. For example, a netbios domain name might be listed as SYMANTECDOMAIN instead of SYMANTECDOMAIN.COM (without the .com extension). To determine the netbios domain name, login to your Active Directory Server and type the following in a command window:
set | findstr DOMAIN
The results will include:

USERDOMAIN netbios_domain_name USERDNSDOMAIN Active_Directory_DNS_domain_name
Use the value of USERDOMAIN (the netbios domain name) when you map user names. Note: When setting quotas on home directories and using user name mapping, make sure to set the quota on the home directory using the user name to which the original name is mapped.
Note: For mapped Active Directory users to access their home directory CIFS shares, use the following convention: \\filestore\realADuser instead of \\filestore\homes.
About load balancing for the normal clustering mode

In normal clustering mode, a CIFS share is served from a single node. CIFS users can access an exported share on any FileStore node. All of the nodes can
Using Symantec FileStore as a CIFS server About load balancing for the normal clustering mode
299
concurrently perform file operations. All of the file systems are mounted on every node. The exported shares are also exported from every node. The following restriction exists for normal clustering mode: only one node at a time can perform file operations on a single share in normal clustering mode. The decision which node is currently allowed to perform the file operations for a specific share is made by the FileStore software and is transparent to the CIFS users. Other issues pertaining to normal clustering mode:
There is a tie up between a virtual IP address and a share. If a virtual IP address that is serving a share is deleted, then the virtual IP address is needed to reschedule that share on another virtual IP address. You can only export the root file system in normal clustering mode. A file system cannot be exported as a different share. Load balancing is provided at the directory level by using the CIFS> split command.
When a CIFS share is accessed by a node that is not the owner of that share, FileStore transparently redirects the access to the node that is the owner of that share. So, all of the processing for a CIFS share is performed by the node that is designated as the owner of that share. If the FileStore work load is found to be too high on a node that owns a share, you can "split" the share by using the CIFS> split command. By splitting a share:
Each share's top-level directories is treated as a single share. Each top-level directory becomes like a root of a new share and only one node at a time can perform the file operations on this new share. The ownership of different top-level directories is assigned to different nodes in the FileStore cluster, balancing the CIFS-related workload.
Caution: You cannot specify which node owns the split share. If the node getting the ownership already has a heavy load, the new load distribution may worsen your situation. Use the CIFS> share show command to view which virtual IP address is assigned to a share. Use the Network> ip addr show command to view which node is assigned a virtual IP address. This shows which node is the current owner of the exported CIFS shares.
300
Using Symantec FileStore as a CIFS server About load balancing for the ctdb clustering mode
About load balancing for the ctdb clustering mode

The ctdb-based clustering mode provides a guarantee of data integrity and consistent locking among FileStore nodes. A CIFS share can be served from multiple nodes simultaneously and therefore provides better load balancing. A CIFS share can be served from multiple virtual IP addresses (VIPs) simultaneously. There will not be any tie up between a VIP and a CIFS share. No redistribution of the CIFS share is required while deleting the VIP. A newly-added VIP can be easily used to serve the CIFS share without any administrator intervention.
Splitting a CIFS share

You can split an exported share with the CIFS> split command. This changes the way a CIFS-related workload is allocated to the FileStore nodes. Note: The CIFS> split command is not supported in ctdb clustering mode. See About ctdb clustering modes on page 309. The purpose of the CIFS> split command is to have multiple nodes serving a large share. Although the command can balance the subdirectory share in a round-robin fashion, the split is not based on the actual load. Restrictions for the CIFS> split command include the following:

You cannot split a sharename more than once. You cannot delete the subdirectory share of a split share. You cannot undo the effects of the CIFS> split command.
Using Symantec FileStore as a CIFS server Splitting a CIFS share
301
To split a CIFS share
To split a CIFS share, enter the following:

CIFS> split sharename [DirName] sharename The name of the share you want to split. It distributes the top-level directories of a file system across the FileStore nodes. You must first split the share before you can enter a directory name. After you have split the share, enter CIFS> share show split share name for a list of directories. The name of the new top-level share directory in the split share. This optional variable adds a top-level directory to a file system, whose corresponding share may or may not have been split.
DirName
For example:
CIFS> split share1 Splitting share splitshare : .........Success.
To display the list of all of the CIFS shares, enter the following command. The output, the asterisk and the word split indicate that a share is split.
CIFS> share show ShareName FileSystem share1* fs3 share2 fs2 share3 fs3
ShareOptions split,rw rw,guest ro,oplocks
To display the details of a CIFS share name, enter the following:

CIFS> share show share1 DirName VIP Address Finan 172.16.113.116 HR 172.16.113.117 Mark 172.16.113.118 Prod 172.16.113.119
302
Using Symantec FileStore as a CIFS server About managing home directories
To create a new top-level directory in a split CIFS share, enter the following command. To create a new top-level directory called newdir in an already split share called share1, enter the following:
CIFS> split share1 newdir Creating directory: newdir Success: Directory 'newdir' created
About managing home directories

You can use FileStore to store the home directories of CIFS users. The home directory share name is identical to the FileStore user name. When FileStore receives a new CIFS connection request, it checks if the requested share is one of the ordinary exported shares. If it is not, FileStore checks if the requested share name is the name of an existing FileStore user (either local user or domain user, depending on the current mode of operation). If a match is found, it means that the received connection request is for a home directory share. You can access your home directory share the same way you access the file system ordinary shares. A user can connect only to his or her own home directory. Note: The internal directories structure of home directory file systems is maintained by FileStore. It is recommended not to use a file system as a homedirfs that has been used by a normal share in the past or vice versa. Table 9-13 Command
set homedirfs
Home directory commands Definition

Specifies one or more file systems to be used for home directories. See Setting the home directory file systems on page 303.
homedir quota
Enables use of quotas on home directory file systems. See Using quotas for CIFS home directories on page 98.
homedir set
Sets the home directory for the specified user. If the home directory does not exist for the specified user, this command creates that user's home directory. See Setting up home directories on page 305.
homedir show
Displays information about home directories. See Displaying home directory usage information on page 307.
303
Table 9-13 Command

homedir delete
Home directory commands (continued) Definition

Deletes a home directory share. See Deleting home directories and disabling creation of home directories on page 308.
homedir deleteall
Deletes the home directories. See Deleting home directories and disabling creation of home directories on page 308.
Setting the home directory file systems

Home directory shares are stored in one or more file systems. A single home directory can exist only in one of these file systems, but a number of home directories can exist in a single home directory file system. File systems that are to be used for home directories are specified using the CIFS> set homedirfs command. When a file system is exported as a homedirfs, its mode is set to a 0755 value. This takes place when you start the CIFS server after setting the homedirfs list. Note: Snapshots cannot be shared as home directory file systems.
304
To specify one or more file systems as the home directories
To reserve one or more file systems for home directories, enter the following:
CIFS> set homedirfs [filesystemlist]
where filesystemlist is a comma-separated list of names of the file systems which are used for the home directories. For example:
CIFS> set homedirfs fs1,fs2,fs3 Global option updated. Note: Restart the CIFS server.
If you want to remove the file systems you previously set up, enter the command again, without any file systems:
CIFS> set homedirfs
To find which file systems (if any) are currently used for home directories, enter the following:
CIFS> show
After you select one or more of the file systems to be used in this way, you cannot export the same file systems as ordinary CIFS shares. If you want to change the current selection, for example, to add an additional file system to the list of home directory file systems or to specify that no file system should be used for home directories, you have to use the same CIFS> set homedirfs command. In each case you must enter the entire new list of home directory file systems, which may be an empty list when no home directory file systems are required. FileStore treats home directories differently from ordinary shares. The differences are as follows:
An ordinary share is used to export a file system, while a number of home directories can be stored in a single file system. The file systems used for home directories cannot be exported as ordinary shares. The CIFS> split command can be used for an ordinary share but not for a home directory share. Exporting a home directory share is done differently than exporting ordinary share. Also, removing these two kinds of shares is done differently.
305
The configuration options you specify for an ordinary share (such as read-only or use of opportunistic locks) are different from the ones you specify for a home directory share.
Setting up home directories

You can set the home directory for the specified user with the CIFS> homedir set command. If the home directory does not exist for the specified user, the CIFS> homedir set command creates that user's home directory. Use the Storage> quota cifshomedir set command to set the quota value for the specified user. Otherwise, the value set from the Storage> quota cifshomedir setdefault command is used to configure the quota limit. If either the user or default quota is not set, 0 is used as the default value for the unlimited quota. Once the global quota value is specified, the value applies to the automatically created homedir. For example, if you set the global quota value to Storage> quota cifshomedir setdefault 100M and you then create a new homedir in Windows, then the 100M quota value is assigned to that homedir.
306
To set the home directory for the specified user
To set the home directory for the specified user, enter the following:
CIFS> homedir set username [domainname] username The name of the CIFS user. If a CIFS user name includes a space, enter the user name with double quotes. For example: CIFS> homedir set "test user" SYMANTECDOMAIN
domainname
The domain for the new home directory.
To find the current settings for a home directory, enter the following:
CIFS> homedir show [username] [domainname] username The name of the CIFS user. If a CIFS user name includes a space, enter the user name with double quotes. For example: CIFS> homedir show "test user" SYMANTECDOMAIN UserName DomainName Usage test user SYMANTECDOMAIN 0
domainname
The Active Directory/Windows NT domain name or specify local for the FileStore local user local.
307
To find the current settings for all home directories, enter the following:
CIFS> homedir show
When you connect to your home directory for the first time, and if the home directory has not already been created, FileStore selects one of the available home directory file systems and creates the home directory there. The file system is selected in a way that tries to keep the number of home directories balanced across all available home directory file systems. The automatic creation of a home directory does not require any commands, and is transparent to both the users and the FileStore administrators. The quota limits the amount of disk space you can allocate for the files in a home directory. You can set the same quota value for all home directories using the Storage> quota cifshomedir setall command. See Using quotas for CIFS home directories on page 98.
Displaying home directory usage information

You can display information about home directories using the CIFS> homedir show command. Note: Information about home directory quotas is up-to-date only when you enable the use of quotas for the home directory file systems.
308
To display information about home directories
To display information about a specific user's home directory, enter the following:
CIFS> homedir show [username] [domainname] username The name of the CIFS user. If a CIFS user name includes a space, enter the user name with double quotes. For example: CIFS> homedir show "test user" SYMANTECDOMAIN UserName DomainName Filesystem Usage test user SYMANTECDOMAIN /vx/fs3 0
domainname
The domain where the home directory is located.
To display information about all home directories, enter the following:

CIFS> homedir show
Deleting home directories and disabling creation of home directories

You can delete a home directory share. This also deletes the files and sub-directories in the share. After a home directory is deleted, if you try to access the same home directory again, a new home directory will automatically be created. If you have an open file when the home directory is deleted, and you try to save the file, a warning appears:
Warning: Make sure the path or filename is correct. Save dialog?
Click on the Save button which saves the file to a new home directory.
Using Symantec FileStore as a CIFS server About ctdb clustering modes
309
To delete a home directory share
To delete the home directory of a specific user, enter the following:

CIFS> homedir delete username [domainname] Do you want to delete homedir for username(y/n): username The name of the CIFS user. If a CIFS user name includes a space, enter the user name with double quotes. Respond with y(es) or n(o) to confirm the deletion. domainname The domain it is located in.
You can delete all of the home directory shares with the CIFS> homedir deleteall command. This also deletes all files and subdirectories in these shares. After you delete the existing home directories, you can again create the home directories manually or automatically. To delete the home directories
To delete all home directories, enter the following:

CIFS> homedir deleteall Do you want to delete all home directories (y/n):
Respond with y(es) or n(o) to confirm the deletion. After you delete the home directories, you can stop FileStore serving home directories by using the CIFS> set homedirfs command. To disable creation of home directories
To specify that there are no home directory file systems, enter the following:
CIFS> set homedirfs
After these steps, FileStore does not serve home directories.
About ctdb clustering modes

The following clustering modes are supported by FileStore:

Normal Clustered Trivial Database (CTDB) - a cluster implementation of the TDB (Trivial database) based on the Berkeley database API
The following operating modes are supported by FileStore:
310
Using Symantec FileStore as a CIFS server Exporting a directory as a CIFS share
User Domain ADS
Each clustering mode supports all of the three operating modes. The ctdb clustering mode is a different clustered implementation of FileStore CIFS, which supports almost all of the features that are supported by normal clustering mode as well as some additional features. Additional features supported in ctdb clustering mode:

Directory-level share support Multi-instance share export of a file system/directory Simultaneous access of a share from multiple nodes and therefore better load balancing
Exporting a directory as a CIFS share

Directory-level share support is available only in the ctdb clustering mode. If you want to export a directory as a CIFS share, you must first switch to the ctdb clustering mode. See About ctdb clustering modes on page 309. See Switching from normal to ctdb clustering mode on page 313. Note: This feature is only supported in the ctdb clustering mode.
Using Symantec FileStore as a CIFS server Exporting a directory as a CIFS share
311
To check the status of the CIFS server to confirm that the clustering mode is set to ctdb
To check the status of the CIFS server to confirm that the clustering mode is set to ctdb, enter the following:
CIFS> server status CIFS Status on ctdb_01 : ONLINE CIFS Status on ctdb_02 : ONLINE Homedirfs : fs1 Security : ads Domain membership status : Enabled Domain : SYMANTECDOMAIN.COM Workgroup : SYMANTECDOMAIN Domain Controller : SYMSERVER Domain User : administrator Clustering Mode : ctdb
To export a directory as a CIFS share
To export a directory as a CIFS share, enter the following:

CIFS> share add fs1/FileStore share1 rw,full_acl Exporting CIFS filesystem : share1 ..Success.
To list the shares, enter the following:

CIFS> share show ShareName FileSystem ShareOptions share1 fs1/FileStore owner=root,group=root,fs_mode=755,rw,full_acl
If the directory name contains a space, enter the directory name with double quotes (" "). For example:
CIFS> share add "fs1/Symantec FileStore" share2 rw Exporting CIFS filesystem : share2 ..Success.
To list the CIFS shares, enter the following:

CIFS> share show ShareName FileSystem ShareOptions share2 fs1/FileStore owner=root,group=root,fs_mode=755,rw share1 fs1/FileStore owner=root,group=root,fs_mode=755,rw, full_acl
312
Using Symantec FileStore as a CIFS server Exporting the same file system/directory as a different CIFS share
Exporting the same file system/directory as a different CIFS share

In ctdb clustering mode, you can export the same file system or directory as a different CIFS share with different available CIFS options. This features allows you more granular control over CIFS shares for different sets of users. If the same file system is exported as different shares in ctdb clustering mode, then after switching to normal clustering mode only one share out of these is available, because multi-instance share export is not supported in normal clustering mode. Note: If the same file system or directory is exported as different shares, then the fs_mode value is the same for all of these shares; that is, the last modified fs_mode value is applicable for all of those shares.
Note: This feature is only supported in the ctdb clustering mode. To export a directory with read access to everyone, but write access to the limited set of users who need to be authenticated
To export a directory with read access to everyone, but write access to the limited set of users who need to be authenticated, enter the following:
CIFS> share add "fs1/Symantec FileStore" share1 rw,noguest Exporting CIFS filesystem : share1 ..Success. CIFS> share add "fs1/Symantec FileStore" share2 ro,guest Exporting CIFS filesystem : share21 ..Success. CIFS> share show ShareName FileSystem ShareOptions share1 fs1/FileStore owner=root,group=root,fs_mode=755,rw,noguest share2 fs1/FileStore owner=root,group=root,fs_mode=755,ro,guest
The above example illustrates that the same directory is exported as a different CIFS share for guest and noquest users with different sets of permissions.
Using Symantec FileStore as a CIFS server About switching the clustering mode
313
About switching the clustering mode

You can switch from normal to ctdb clustering mode or from ctdb to normal clustering mode. You must stop the CIFS server prior to switching to any cluster mode. See About ctdb clustering modes on page 309. See Switching from normal to ctdb clustering mode on page 313. See Switching from ctdb to normal clustering mode on page 316.
Switching from normal to ctdb clustering mode

You must stop the CIFS server prior to switching to any clustering mode by issuing the CIFS> server stop command. In ctdb clustering mode, if the FileStore cluster is joined to the domain, then stopping the CIFS server always results in leaving the join. This is a special case that applies to ctdb clustering mode; this behavior does not occur with normal clustering mode. To switch from normal to ctdb clustering mode
To check the status of the CIFS server prior to switching from normal to ctdb clustering mode, enter the following:
CIFS> server status CIFS Status on ctdb_01 : ONLINE CIFS Status on ctdb_02 : ONLINE Homedirfs : fs1 Security : ads Domain membership status : Enabled Domain : SYMANTECDOMAIN.COM Workgroup : SYMANTECDOMAIN Domain Controller : SYMSERVER Domain User : administrator Clustering Mode : normal

CIFS> server stop Stopping CIFS Server .....Success.
314
To set the CIFS clustering mode to ctdb, enter the following:

CIFS> set clustering_mode ctdb Global option updated. Note: Restart the CIFS server.
315

CIFS> server start Disabling membership in AD domain SYMANTECDOMAIN.COM Enter password for user àdministrator': Left AD domain SYMANTECDOMAIN.COM Uninstalling `normal' Clustering Mode ......Success. Installing `ctdb' Clustering Mode .......Success. Starting CIFS Server .... The skew of the system clock with respect to Domain controller SYMSERVER (10.209.110.210) is: 8 seconds Time on Domain Controller : Thu Aug 19 15:04:22 2010 Time on this system : Thu Aug 19 15:04:14 IST 2010 If the above clock skew is greater than that allowed by the server, then the system won't be able to join the AD domain Trying to become a member in AD domain SYMANTECDOMAIN.COM ... Enter password for user àdministrator': Joined domain SYMANTECDOMAIN.COM OK ..Success.

316
Switching from ctdb to normal clustering mode

You must stop the CIFS server prior to switching to any clustering mode by issuing the CIFS> server stop command. Note: Domain membership is disabled while stopping the CIFS server in ctdb clustering mode. To switch from ctdb to normal clustering mode
To check the status of the CIFS server prior to switching from ctdb to normal clustering mode, enter the following:

CIFS> server stop Disabling membership in AD domain SYMANTECDOMAIN.COM Enter password for user àdministrator': Left AD domain SYMANTECDOMAIN.COM Stopping CIFS Server ......Success.
To set the CIFS clustering mode to normal, enter the following:

CIFS> set clustering_mode normal Global option updated. Note: Restart the CIFS server.
Using Symantec FileStore as a CIFS server About migrating CIFS shares and home directories
317

CIFS> server start Uninstalling `ctdb' Clustering Mode........Success. Installing `normal' Clustering Mode........Success. The skew of the system clock with respect to Domain controller SYMSERVER (10.209.110.210) is: 8 seconds Time on Domain Controller : Thu Aug 19 15:47:47 2010 Time on this system : Thu Aug 19 15:47:39 IST 2010 If the above clock skew is greater than that allowed by the server, then the system won't be able to join the AD domain Trying to become a member in AD domain SYMANTECDOMAIN.COM ... Enter a password for user àdministrator' Joined domain SYMANTECDOMAIN.COM OK Starting CIFS Server.....Success.

About migrating CIFS shares and home directories

You can migrate CIFS shares and home directories from normal to ctdb clustering mode and from ctdb to normal clustering mode. FileStore automatically migrates all CIFS shares and home directories while switching from one clustering mode to another. However, it is not possible to
318
migrate directory-level shares in the normal clustering mode, because directory-level sharing is not supported in normal clustering mode. Automatic migration of the content of users (that is, users' home directories) from one file system to another file system while switching home directories is not supported. So, if a FileStore administrator changes home directories from fs1 to fs2, then users' home directories are not migrated from fs1 to fs2 automatically. While migrating from normal to ctdb clustering mode, a simple share is created for each split share, because splitting shares is not supported in ctdb clustering mode. See Migrating CIFS shares and home directories from normal to ctdb clustering mode on page 319. See Migrating CIFS shares and home directories from ctdb to normal clustering mode on page 321.
319
Migrating CIFS shares and home directories from normal to ctdb clustering mode
To migrate CIFS shares and home directories from normal to ctdb clustering mode
To check the CIFS server status to confirm that the current cluster mode is set to normal, enter the following:
To list the CIFS shares and home directories, enter the following:
CIFS> share show ShareName FileSystem ShareOptions share1* fs1 split,owner=root,group=root,fs_mode=1777, rw,full_acl share3 share4 fs3 fs4 owner=root,group=root,fs_mode=1777 owner=root,group=root,fs_mode=1777,rw
CIFS> homedir show UserName DomainName test Local administrator SYMANTECDOMAIN
Usage -
To stop the CIFS server before changing the clustering mode to ctdb, enter the following:
CIFS> server stop Stopping CIFS Server.....Success. CIFS> set clustering_mode ctdb Global option updated. Note: Restart the CIFS server.
320
To start the CIFS server in ctdb clustering mode and check the CIFS server status, enter the following:
CIFS> server start Disabling membership in AD domain SYMANTECDOMAIN.COM Enter a password for user àdministrator' Left AD domain SYMANTECDOMAIN.COM Uninstalling `normal' Clustering Mode........Success. Installing `ctdb' Clustering Mode........Success. Starting CIFS Server.... The skew of the system clock with respect to Domain controller sfsqa_ad.sfsqa.com (10.209.110.210) is: 9 seconds Time on Domain Controller : Thu Aug 19 17:07:19 2010 Time on this system : Thu Aug 19 17:07:10 IST 2010 If the above clock skew is greater than that allowed by the server, then the system won't be able to join the AD domain Trying to become a member in AD domain SYMANTECDOMAIN.COM ... Enter a password for user àdministrator' Joined domain SYMANTECDOMAIN.COM OK ..Success. CIFS> server status CIFS Status on ctdb_01 : ONLINE CIFS Status on ctdb_02 : ONLINE Homedirfs : fs1 Security : ads Domain membership status : Enabled Domain : SYMANTECDOMAIN.COM Workgroup : SYMANTECDOMAIN Domain Controller : SYMSERVER Domain User : administrator Clustering Mode : ctdb
321
To verify that all the CIFS shares and home directories are properly migrated to the ctdb clustering mode, enter the following:
CIFS> share show ShareName FileSystem share1 fs1 share3 fs3 share4 fs4
ShareOptions owner=root,group=root,fs_mode=1777,rw,full_acl owner=root,group=root,fs_mode=1777 owner=root,group=root,fs_mode=1777,rw
Usage -
Migrating CIFS shares and home directories from ctdb to normal clustering mode
If a file system is exported as multiple CIFS shares in ctdb clustering mode, then while migrating to normal clustering mode, FileStore creates only one CIFS share, whichever comes first in the list.
322
To migrate a CIFS share and home directory from ctdb to normal clustering mode

To list the CIFS shares and home directories, enter the following:
CIFS> share show ShareName FileSystem share1 fs1/FileStore share2 fs1/FileStore share3 fs3 share4 fs4 CIFS> homedir show UserName test administrator DomainName Local SYMANTECDOMAIN Usage -
ShareOptions owner=root,group=root,fs_mode=755,rw,noguest owner=root,group=root,fs_mode=755,ro,guest owner=root,group=root,fs_mode=1777 owner=root,group=root,fs_mode=1777,rw
To stop the CIFS server to switch the clustering mode to normal, enter the following:
CIFS> server stop Disabling membership in AD domain SYMANTECDOMAIN.COM Enter password for user àdministrator': Left AD domain SYMANTECDOMAIN.COM Stopping CIFS Server ......Success. CIFS> set clustering_mode normal Global option updated. Note: Restart the CIFS server.
323
To start the CIFS server in normal clustering mode, enter the following:
CIFS> server start Uninstalling `ctdb' Clustering Mode.........Success. Installing `normal' Clustering Mode.........Success. The skew of the system clock with respect to Domain controller SYMSERVER (10.209.110.210) is: 9 seconds Time on Domain Controller : Thu Aug 19 16:54:03 2010 Time on this system : Thu Aug 19 16:53:54 IST 2010 If the above clock skew is greater than that allowed by the server, then the system won't be able to join the AD domain Trying to become a member in AD domain SYMANTECDOMAIN.COM ... Enter a password for user àdministrator' Joined domain SYMANTECDOMAIN.COM OK SFS cifs WARNING V-288-0 Migration of following shares are not supported in normal clustering mode Clustering mode Sharename FS Name share1 fs1/Symantec FileStore share2 fs1/Symantec FileStore Starting CIFS Server......Success.
The warning message indicates that FileStore was unable to migrate the directory-level share to normal clustering mode. The rest of the CIFS share and home directory were migrated.
To list the CIFS shares and home directories after migrating to normal clustering mode, enter the following:
CIFS> share show ShareName FileSystem share3 fs3 share4 fs4
ShareOptions owner=root,group=root,fs_mode=1777 owner=root,group=root,fs_mode=1777,rw
Usage -
324
Using Symantec FileStore as a CIFS server Setting the aio_fork option
Setting the aio_fork option

The CIFS> set aio_size option allows you to set an Asynchronous I/O (AIO) read/write size with an unsigned integer. To set the aio_fork option
To set the aio_fork option, enter the following:

CIFS> set aio_size size
where size is the AIO read/write size. If size is not set to 0, then enable the aio_fork option, and set it as an AIO read/write size. If size is set to 0, then disable the aio_fork option, and set 0 to an AIO read/write size. For example:
CIFS> set aio_size set aio_size <size> --set aio_fork read/write size. size : Unsigned integer or 0 to disable aio
CIFS> set aio_size 0 Global option updated. Note: Restart the CIFS server. CIFS> set aio_size 1024 Global option updated. Note: Restart the CIFS server.
Using Symantec FileStore as a CIFS server Setting the netbios aliases for the CIFS server
325
Setting the netbios aliases for the CIFS server

To set the netbios aliases for the CIFS server
To set the netbios aliases for the CIFS server, enter the following:
CIFS> set alias [aliaslist]
where aliaslist is either empty (no netbios alias was specified) or a comma-separated list of netbios alias names. After setting the netbios alias names, you can access the CIFS server by using these alias names. For example, if you want to set an empty alias, you would enter the following:
CIFS> set alias Global option updated. Note: Restart the CIFS server.
For example, if you want to set one or multiple netbios alias names, you would enter the following:
CIFS> set alias A1,A2,A3 Global option updated. Note: Restart the CIFS server. CIFS> show Name ---netbios name netbios aliases ntlm auth allow trusted domains homedirfs aio size idmap backend workgroup security Domain Domain user Domain Controller Clustering Mode Value ----sfs4 A1 A2 A3 yes no fs1,fs3 0 rid:10000-1000000 SYMANTECDOMAIN ads SYMANTECDOMAIN.COM administrator SYMSERVER ctdb
326
Using Symantec FileStore as a CIFS server About managing local users and groups
About managing local users and groups

When FileStore is operating in the standalone mode, only the local users and groups of users can establish CIFS connections and access the home directories and ordinary shares. The FileStore local files store the information about these user and group accounts. Local procedures authenticate and authorize these users and groups based on the use of names and passwords. You can manage the local users and groups as described in the rest of this topic. Accounts for local users can be created, deleted, and information about them can be displayed using the CIFS> local user commands. Table 9-14 Command
local user add
Manage local users and groups commands Definition

Adds a new user to CIFS. You can add the user to a local group, by entering the group name in the optional grouplist variable. Before you add the user to a grouplist, you must create the grouplist. When you create a local user, FileStore assigns a default password to the new account. The default password is the same as the user name. For example, if you enter usr1 for the user name, the default password is also usr1. See Creating a local CIFS user on page 327.
local password
The default password for a newly-created account is the same as the user name. You can change the default password using the CIFS> local password command. The maximum password length is eight characters. See Creating a local CIFS user on page 327.
local user delete
Deletes local user accounts. See Creating a local CIFS user on page 327.
local user show
Displays the user ID and lists the groups to which the user belongs. If you do not enter an optional username, the command lists all CIFS existing users. See Creating a local CIFS user on page 327.
local user members
Adds a user to one or more groups. For existing users, this command changes a user's group membership. See Creating a local CIFS user on page 327.
327
Creating a local CIFS user

To create the new local CIFS user
To create a local CIFS user, enter the following:

CIFS> local user add username [grouplist]
where username is the name of the user. The grouplist is a comma-separated list of group names. For example:
CIFS> local user add usr1 grp1,grp2 Adding USER : usr1 Success: User usr1 created successfully
To set the local user password
To set the local password, enter the following:

CIFS> local password username
where username is the name of the user whose password you are changing. For example, to reset the local user password for usr1, enter the following:
CIFS> local password usr1 Changing password for usr1 New password:***** Re-enter new password:***** Password changed for user: 'usr1'
328
To display the local CIFS user(s)
To display local CIFS users, enter the following:

CIFS> local user show [username]
where username is the name of the user. For example, to list all local users:
CIFS> local user show List of Users ------------usr1 usr2 usr3
To display one local user, enter the following:

CIFS> local user show usr1 Username : usr1 UID : 1000 Groups : grp1
To delete the local CIFS user
To delete a local CIFS user, enter the following:

CIFS> local user delete username
where username is the name of the local user you want to delete. For example:
CIFS> local user delete usr1 Deleting User: usr1 Success: User usr1 deleted successfully
329
To change a user's group membership
To change a user's group membership, enter the following:

CIFS> local user members username grouplist
where username is the local user name being added to the grouplist. Group names in the grouplist must be separated by commas. For example:
CIFS> local user members usr3 grp1,grp2 Success: usr3's group modified successfully
About configuring local groups

A local user can be a member of one or more local groups. This group membership is used in the standalone mode to determine if the given user can perform some file operations on an exported share. You can create, delete, and display information about local groups using the CIFS> local group command. Table 9-15 Command
local group add
Configure local groups commands Definition

Creates a local CIFS group. See Configuring a local group on page 330.
local group show
Displays the list of available local groups you created. See Configuring a local group on page 330.
local group delete Deletes a local CIFS group. See Configuring a local group on page 330.
330
Configuring a local group

To create a local group
To create a local group, enter the following:

CIFS> local group add groupname
where groupname is the name of the local group. For example:

CIFS> local group add grp1 Adding GROUP: grp1 Success: Group grp1 created successfully
To list all local groups
To list all existing local groups, enter the following:

CIFS> local group show [groupname]
where groupname lists all of the users that belong to that specific group. For example:
CIFS> local group show List of groups ------------grp1 grp2 grp3
For example:
CIFS> local group show grp1 GroupName UsersList ----------------grp1 usr1, usr2, usr3, urs4
331
To delete the local CIFS groups
To delete the local CIFS group, enter the following:

CIFS> local group delete groupname
where groupname is the name of the local CIFS group. For example:
CIFS> local group delete grp1 Deleting Group: grp1 Success: Group grp1 deleted successfully
332
Chapter
10
Configuring your FTP server


About FTP Displaying FTP server About FTP server commands Using the FTP server commands About FTP set commands Using the FTP set commands Implementing all of the FTP> set command changes About FTP session commands Using the FTP session commands Using the FTP logupload command About FTP local user commands Using the FTP local user commands About FTP local user set commands Using the FTP local user set commands
About FTP
The File Transfer Protocol (FTP) server feature allows clients to access files on the FileStore servers using the FTP protocol. The FTP service provides secure/non-secure access via FTP to files in the FileStore servers. The FTP service runs on all of the nodes in the cluster and provides simultaneous read/write access
334
Configuring your FTP server About FTP
to the files. The FTP service also provides configurable anonymous access to the filer. The FTP commands are used to configure the FTP server. By default, the FTP server is not running. You can start the FTP server using the FTP> server start command. The FTP server starts on the standard FTP port 21. FTP mode commands are listed in Table 10-1. To access the commands, log into the administrative console (master, system-admin, or storage-admin) and enter FTP> mode. See About using the FileStore command-line interface on page 33. Table 10-1 Command
show
FTP mode commands Definition

Displays the FTP server settings. See Displaying FTP server on page 335.
server
Starts, stops, and displays the status of the FTP server. See About FTP server commands on page 335.
set
Configures the FTP server. See About FTP set commands on page 337.
session
Displays and terminates the FTP sessions. See About FTP session commands on page 346.
logupload
Uploads the FTP logs to a URL. See Using the FTP logupload command on page 348.
local
Adds, deletes and displays local user accounts. Configures local user settings. See About FTP local user commands on page 348.
Configuring your FTP server Displaying FTP server
335
Displaying FTP server

To display the FTP settings
To display the FTP settings, enter the following:

FTP> show Parameter --------listen_port max_connections max_conn_per_client passive_port_range allow_non_ssl idle_timeout anonymous_logon anonymous_write anonymous_login_dir user_logon homedir_path allow_delete security Current Value ------------21 2000 2000 30000:40000 yes 15 minutes no no /vx/ yes /vx/ no nis_ldap
About FTP server commands

The FTP> server commands start, stop, and display the status of the FTP server. Note: All configuration changes made using the FTP> set commands come into effect only when the FTP server is restarted. Table 10-2 Command
server status
FTP server commands Definition

Displays the status of the FTP server. See Using the FTP server commands on page 336.
server start
Starts the FTP server on all nodes. If the FTP server is already started, the FileStore software clears any faults and tries to start the FTP server. See Using the FTP server commands on page 336.
336
Configuring your FTP server Using the FTP server commands
Table 10-2 Command

server stop
FTP server commands (continued) Definition

Stops the FTP server and terminates any existing FTP sessions. By default, the FTP server is not running. See Using the FTP server commands on page 336.
Using the FTP server commands

To display the FTP server status
To display the FTP server status, enter

FTP> server status FTP Status on sfs_01 : OFFLINE FTP Status on sfs_02 : OFFLINE
To start the FTP server
To start the FTP server, enter the following:

FTP> server start
To check server status, enter the following:

FTP> server status FTP Status on sfs_01 : ONLINE FTP Status on sfs_02 : ONLINE
To stop the FTP server
To stop the FTP server, enter the following:

FTP> server stop
To check the server status, enter the following:

FTP> server status FTP Status on sfs_01 : OFFLINE FTP Status on sfs_02 : OFFLINE
Configuring your FTP server About FTP set commands
337
About FTP set commands

The FTP> set commands let you set various configurable options for the FTP server. Table 10-3 Command
set anonymous_logon
FTP set commands Definition

Tells the FTP server whether or not to allow anonymous logons. Enter yes to allow anonymous users to log on to the FTP server. Enter no (default) to not allow anonymous logons. For the changes to take effect you will need to restart the FTP server. Enter FTP> server stop followed by FTP> server start. See Using the FTP set commands on page 341.
set anonymous_login_dir
Specifies the login directory for anonymous users. Valid values of this parameter start with /vx/. Make sure that the anonymous user (UID:40 GID:49 UNAME:ftp) has the appropriate permissions to read files in login_directory. For the changes to take effect, you need to restart the FTP server. Enter FTP> server stop followed by FTP> server start. See Using the FTP set commands on page 341.
set anonymous_write
Specifies whether or not anonymous users have the [write] value in their login_directory. Enter yes to allow anonymous users to modify contents of their login_directory. Enter no (default) to not allow anonymous users to modify the contents of their login_directory. Make sure that the anonymous user (UID:40 GID:49 UNAME:ftp) has the appropriate permissions to modify files in their login_directory. For the changes to take effect, you need to restart the FTP server. Enter FTP> server stop followed by FTP> server start. See Using the FTP set commands on page 341.
338
Table 10-3 Command

set allow_delete
FTP set commands (continued) Definition

Specifies whether or not to allow users to delete files on the FTP server. This option only applies to users. It does not apply to anonymous logins. Anonymous logins are never allowed to delete files. Enter yes (default) to allow users to delete files on the FTP server. Enter no to prevent users from deleting files on the FTP server. For the changes to take effect you need to restart the FTP server. Enter FTP> server stop followed by FTP> server start. See Using the FTP set commands on page 341.
set allow_non_ssl
Specifies whether or not to allow non-secure (plain-text) logins into the FTP server. Enter yes (default) to allow non-secure (plain-text) logins to succeed. Enter no to allow non-secure (plain-text) logins to fail. For the changes to take effect you need to restart the FTP server. Enter FTP> server stop followed by FTP> server start. See Using the FTP set commands on page 341.
set homedir_path
Specifies the location of the login directory for users. Valid values include any path that starts with /vx/. For the changes to take effect you need to restart the FTP server. Enter FTP> server stop followed by FTP> server start. See Using the FTP set commands on page 341.
set idle_timeout
Specifies the amount of time in minutes after which an idle connection is disconnected. Valid values for time_in_minutes range from 1 to 600 (default value is 15 minutes). For the changes to take effect, you need to restart the FTP server. Enter FTP> server stop followed by FTP> server start. See Using the FTP set commands on page 341.
339
Table 10-3 Command

set listen_port

Specifies the port number on which the FTP service listens for connections. Valid values for this parameter range from 10-1023. The default value is 21. For the changes to take effect you need to restart the FTP server. Enter FTP> server stop followed by FTP> server start. See Using the FTP set commands on page 341.
set max_connections
Specifies the maximum number of simultaneous FTP clients allowed. Valid values for this parameter range from 1-9999. The default value is 2000. For the changes to take effect, you need to restart the FTP server. Enter FTP> server stop followed by FTP> server start. See Using the FTP set commands on page 341.
set max_conn_per_client
Specifies the maximum number of simultaneous FTP connections allowed from a single client IP address. Valid values for this parameter range from 1-9999. The default value is 2000. For the changes to take effect, you need to restart the FTP server. Enter FTP> server stop followed by FTP> server start. See Using the FTP set commands on page 341.
set passive_port_range
Specifies the range of port numbers to listen on for passive FTP transfers. The port_range defines a range specified as startingport:endingport. A port_range of 30000:40000 specifies that port numbers starting from 30000 to 40000 can be used for passive FTP. Valid values for port numbers range from 30000 to 50000. The default value of this option is 30000:40000. For the changes to take effect, you need to restart the FTP server. Enter FTP> server stop followed by FTP> server start. See Using the FTP set commands on page 341.
340
Table 10-3 Command

set security

Specifies the type of users allowed to log in to the FTP server. Enter nis_ldap (default) to allow users with accounts configured on NIS or LDAP servers to log in to the FTP server. Users created with the FTP > local user add command cannot log in. Enter local to allow users with accounts created with the FTP> local user add command to log in to the FTP server. NIS and LDAP users cannot log in. For the changes to take effect, you need to restart the FTP server. Enter FTP> server stop followed by FTP> server start. See Using the FTP set commands on page 341.
Configuring your FTP server Using the FTP set commands
341
Using the FTP set commands

To set anonymous logons
To enable anonymous logons, enter the following:

FTP> set anonymous_logon yes|no yes no (default) Allows anonymous users to log on to the FTP server. Does not allow anonymous logons.
You need to stop and then start the server for the new setting to take affect.
FTP> set anonymous_logon FTP> show Parameter --------listen_port max_connections max_conn_per_client passive_port_range allow_non_ssl idle_timeout anonymous_logon anonymous_write ... FTP> server stop FTP> server start FTP> show Parameter --------listen_port max_connections max_conn_per_client passive_port_range allow_non_ssl idle_timeout anonymous_logon anonymous_write ... yes Current Value ------------21 2000 2000 30000:40000 yes 15 minutes no no New Value ---------
yes
Current Value ------------21 2000 2000 30000:40000 yes 15 minutes yes no
342
To set anonymous logins
To set anonymous logins, enter the following:

FTP> set anonymous_login_dir login_directory
where the login_directory is the login directory of the anonymous users on the FTP server. To set anonymous write access
To set anonymous write access, enter the following:

FTP> set anonymous_write yes|no yes Allows anonymous users to modify the contents of their login_directory. Does not allow anonymous users to modify the contents of their login_directory.
no (default)
FTP> set anonymous_write yes
To allow users to delete files
To set whether or not to allow users to delete files on the FTP server, enter the following:
FTP> set allow_delete yes|no yes (default) Allows users to delete files on the FTP server. This setting does not apply to anonymous logins. Anonymous logins are never allowed to delete files. Prevents users from deleting files on the FTP server.
no
FTP> set allow_delete no
To set non-secure logins
To set non-secure login access to the FTP server, enter the following:
FTP> set allow_non_ssl yes|no yes (default) no Allows non-secure (plain-text) logins to succeed. Allows non-secure (plain-text) logins to fail.
FTP> set allow_non_ssl no
343
To set the home directory path
To set the location of the login directory for users, enter the following:
FTP> set homedir_path path
where path is the location of the login directory. Valid values include any path that starts with /vx/.
FTP> set homedir_path /vx/home
To set idle timeout
To set the amount of time a connection can stay idle before disconnecting, enter the following:
FTP> set idle_timeout time_in_minutes
where time_in_minutes is the amount of time you want the connection to stay idle before disconnecting.
FTP> set idle_timeout 30
To set the listen port
To set the port number on which the FTP service listens for connections, enter the following:
FTP> set listen_port port_number
where port_number is the port on which the FTP service listens for connections.
FTP> set listen_port 24
To set maximum connections
To set the maximum number of allowed simultaneous FTP clients, enter the following:
FTP> set max_connections connections_number
where connections_number is the number of concurrent FTP connections allowed on the FTP server.
FTP> set max_connections 3000
344
To set maximum connections per client
To set the maximum number of simultaneous FTP connections allowed from a single client IP address, enter the following:
FTP> set max_conn_per_client connections_number
where connections_number is the number of concurrent connections allowed from a single client.
FTP> set max_conn_per_client 1000
To set range of port numbers
To set the range of port numbers to listen on for passive FTP transfers, enter the following:
FTP> set passive_port_range port_range
where port_range is the range of port numbers to listen on for passive FTP transfers.
FTP> set passive_port_range 35000:45000
To set security
To set the type of users allowed to log in to the FTP server, enter the following:
FTP> set security nis_ldap|local nis_ldap Allows users with accounts configured on NIS or LDAP servers to log in to the FTP server. Allows users with accounts configured with the FTP> local user add command to log in to the FTP server.
local
FTP> set security local
Configuring your FTP server Implementing all of the FTP> set command changes
345
Implementing all of the FTP> set command changes

To implement FTP> set command changes
To view all of the FTP> set command changes, enter the following:
FTP> show Parameter --------listen_port max_connections max_conn_per_client passive_port_range allow_non_ssl idle_timeout anonymous_logon anonymous_write anonymous_login_dir user_logon homedir_path allow_delete security
Current Value ------------21 2000 2000 30000:40000 yes 15 minutes no no /vx/ no /vx/ no nis_ldap
New Value --------24 3000 1500 35000:45000 no 30 minutes yes yes /vx/anon/ yes /vx/usr yes local
To implement the new changes, enter the following:

FTP> server stop FTP> server start
To view the new command settings, enter the following:

FTP> show listen_port max_connections max_conn_per_client passive_port_range allow_non_ssl idle_timeout anonymous_logon anonymous_write anonymous_login_dir user_logon homedir_path allow_delete security
24 3000 1500 35000:45000 no 30 minutes yes yes /vx/anon/ yes /vx/usr yes local
346
Configuring your FTP server About FTP session commands
About FTP session commands

The FTP> session commands allow you to view or terminate the FTP sessions that are currently active. Table 10-4 Command
session show
FTP session Commands Definition

Displays the number of current FTP sessions to each node. See Using the FTP session commands on page 346.
session showdetail Displays the details of each session that matches the filter_options criteria. If no filter_options are specified, all sessions are displayed. If multiple filter options are provided then sessions matching all of the filter options are displayed. Filter options can be combined by using ','. The details displayed include: Session ID, User, Client IP, Server IP, State (UL for uploading; DL for downloading, or IDLE), and File (the name of the files that appear are either being uploaded or downloaded). If an '?' appears under User, the session is not yet authenticated. See Using the FTP session commands on page 346. session terminate Terminates the session entered for the session_id variable. What you enter is the same session displayed under Session ID with the FTP> session showdetail command. See Using the FTP session commands on page 346.
Using the FTP session commands

To display the current FTP sessions
To display the current FTP sessions, enter the following:

FTP> session show Max Sessions : 2000 Nodename Current Sessions -------- ---------------sfs_01 4 sfs_02 2
Configuring your FTP server Using the FTP session commands
347
To display the FTP session details
To display the details in the FTP sessions, enter the following:

FTP> session showdetail [filter_options]
where filter_options display the details of the sessions under specific headings. Filter options can be combined by using ','. If multiple filter options are used, sessions matching all of the filter options are displayed. For example, to display all of the session details, enter the following:
FTP> session showdetail Session ID User Client IP ---------- -----------sfs_01.1111 user1 10.209.105.219 sfs_01.1112 user2 10.209.106.11 sfs_02.1113 user3 10.209.107.21 sfs_01.1117 user4 10.209.105.219 sfs_02.1118 user1 10.209.105.219 sfs_01.1121 user5 10.209.111.219
Server IP --------10.209.105.111 10.209.105.111 10.209.105.112 10.209.105.111 10.209.105.111 10.209.105.112
State ----IDLE IDLE IDLE DL UL IDLE
File ----
file123 file345
For example, to display the details of the current FTP sessions to the Server IP (10.209.105.112), originating from the Client IP (10.209.107.21), enter the following:
FTP> session showdetail server_ip=10.209.105.112, client_ip=10.209.107.21 Session ID User Client IP Server IP ---------- ---sfs_02.1113 user3 --------10.209.107.21 --------10.209.105.112
State ----IDLE
File ----
To terminate an FTP session
To terminate one of the FTP sessions displayed in the FTP> session showdetail command, enter the following:
FTP> session terminate session_id
where session_id is the unique identifier for each FTP session displayed in the FTP> session showdetail output.
FTP> session terminate sfs_02.1113 Session sfs_02.1113 terminated
348
Configuring your FTP server Using the FTP logupload command
Using the FTP logupload command

The FTP> logupload command allows you to upload the FTP server logs to a specified URL. To upload the FTP server logs
To upload the FTP server logs to a specified URL, enter the following:
FTP> logupload url [nodename] url The URL where the FTP logs will be uploaded. The URL supports both FTP and SCP (secure copy protocol). If a nodename is specified, only the logs from that node are uploaded. The default name for the uploaded file is ftp_log.tar.gz. Passwords added directly to the URL are not supported. nodename The node on which the operation occurs. Enter the value all for the operation to occur on all of the nodes in the cluster. Use the password you already set up on the node to which you are uploading the logs.
password
For example, to upload the logs from all of the nodes to an SCP-based URL:
FTP> logupload scp://user@host:/path/to/directory all Password: Collecting FTP logs, please wait..... Uploading the logs to scp://root@host:/path/to/directory, please wait...done
For example, to upload the logs from sfs_1 to an FTP-based URL:

FTP> logupload ftp://user@host:/path/to/directory sfs_1 Password: Collecting FTP logs, please wait..... Uploading the logs to ftp://root@host:/path/to/directory, please wait...done
About FTP local user commands

The FTP> local user commands let you create and manage local user accounts on the FTP server.
Configuring your FTP server About FTP local user commands
349
When you add a local user account, the user's home directory is created automatically on the FTP server. User home directories on the FTP server are specified by path/username where path is the home directory path configured by the FTP > set homedir_path command. Table 10-5 Command
local user add
FTP local user Commands Definition

Adds a local user account to the FTP server. See Using the FTP local user commands on page 350.
local user password local user delete
Changes the password for a local user account on the FTP server. See Using the FTP local user commands on page 350. Removes a local user account from the FTP server. See Using the FTP local user commands on page 350.
local user show
Shows a list of local user accounts and associated information. See Using the FTP local user commands on page 350.
350
Configuring your FTP server Using the FTP local user commands
Using the FTP local user commands

To add a local user account
To add a local user account, enter the following:

FTP> local user add username
where username is the name of the user whose account you want to add.
2 3
When the password prompt appears, enter a password for the local user. Type the password again for verification. For example:
FTP > local user add user1 Input password for user1. Enter password: Re-enter password: Success.
When you add a local user, a home directory for the local user is created based on the username of the account and the home directory path specified for users. For example, /vx/home/user1. All users are limited to their home directories and are not allowed to access files on the FTP server beyond their home directories. To change a password for a local user
To change a password for a local user, enter the following:

FTP> local user passwd username
where username is the name of the user whose password you want to change.
When the password prompt appears, enter a new password, then type the password again for verification. For example:
FTP > local user passwd user1 Enter password: Re-enter password: Success.
Configuring your FTP server About FTP local user set commands
351
To delete a local user account
To delete a local user account, enter the following:

FTP> local user delete username
where username is the name of the user whose account you want to delete. For example:
FTP > local user delete user1 Success.
When you delete a local user account, the local user's home directory is not deleted. To show local user accounts
To show local user accounts (and account settings) configured on the FTP server, enter the following:
FTP> local user show USER HOMEDIR ---------localftp1 /localftp1 localftp2 /localftp2 localftp3 /test/asfta localftp4 /localftp4 test /test test2 /test2
UPLOAD -----20 MB/s 103 MB/s -
DOWNLOAD -------10 MB/s 203 MB/s -
MAX_FILES --------1000 -
MAX_USAGE --------10.00 MB 103.00 MB -
MAX_CONN -------20 10003 -
About FTP local user set commands

By default, local user accounts on the FTP server have no limits for the following:

Upload bandwidth Download bandwidth Number of files and directories in a home directory The amount of disk space available for files in a home directory Number of simultaneous connections
To configure limits for these options, use the FTP> user local set commands.
352
Configuring your FTP server About FTP local user set commands
You can also use the FTP> local user set command specify home directories for local users accounts. Local user changes are effective immediately for new connections. You do not need to restart the FTP server. Table 10-6 Command
set upload_bandwidth
FTP local user set commands Definition

Specifies the maximum upload bandwidth (in MB/second) for a local user account on the FTP server. By default, there is no limit on the upload bandwidth for local users. See Using the FTP local user set commands on page 353.
set download_bandwidth
Specifies the maximum download bandwidth (in MB/second) for a local user account on the FTP server. By default, there is no limit on the download bandwidth for local users. See Using the FTP local user set commands on page 353.
set max_files
Specifies the maximum number of files and directories for a local user account on the FTP server. By default, there is no limit on the upload bandwidth for local users. See Using the FTP local user set commands on page 353.
set max_usage
Specifies the maximum amount of disk space available in a local user home directory. By default, there is no limit to the amount of disk space local users can have for their home directories. Values can be specified as M (megabytes), G (gigabytes) or T (terabytes). For example, 200G. See Using the FTP local user set commands on page 353.
set max_connections
Specifies the maximum number of simultaneous connections a local user can have to each node in the cluster. By default there is no limit to the number of connections a local user can have to the FTP server. See Using the FTP local user set commands on page 353.
Configuring your FTP server Using the FTP local user set commands
353
Table 10-6 Command

set homedir
FTP local user set commands (continued) Definition

Specifies the home directory for a local user account. The home directory you configure for a local user account is created relative to the home directory path configured by the FTP > set homedir_path command. The default home directory value for local user accounts is username where username is the login name for the local user account. For example, if the home directory path is set to /vx/fs1/ftp_home and the username is user1, the default home directory for user1 is /vx/fs1/ftp_home/user1 Changes to this value are applicable for any new connections. Configuring a new home directory location does not migrate any existing data in a local user's current home directory to the new home directory. See Using the FTP local user set commands on page 353.
Using the FTP local user set commands

Note: Quota values for MAX_FILES and MAX_USAGE are enforced during the commit of the FTP transaction. The transfer might show the status as 100% transferred, but the final commit might fail if the quota is exceeded.
150 Accepted data connection 100% *****************************************************| 2791 MB 106.58 MB/s 00:00 ETA 553-Quota exceeded: largefile.iso won't be saved
354
To show local user settings
To show the current settings for local user accounts, enter the following:
FTP> local user show USER HOMEDIR ---------localftp1 /localftp1 localftp2 /localftp2 localftp3 /test/asfta localftp4 /localftp4 test /test test2 /test2
UPLOAD -----20 MB/s 103 MB/s -
DOWNLOAD -------10 MB/s 203 MB/s -
MAX_FILES --------1000 -
MAX_USAGE --------10.00 MB 103.00 MB -
MAX_CONN -------20 10003 -
To set upload bandwidth
To set the maximum upload bandwidth for a local user account, enter the following:
FTP> local user set upload_bandwidth username max_value username max_value Specifies the name of a user account. Specifies the maximum upload bandwidth value (measured in MB/second) for the user's account.
For example:
FTP > local user set upload_bandwidth user2 40000 Success.
355
To set download bandwidth
To set the maximum download bandwidth for a local user account, enter the following:
FTP> local user set download_bandwidth username max_value username max_value Specifies the name of a user account. Specifies the maximum download bandwidth value (measured in MB/second) for the user's account.
For example:
FTP > local user set download_bandwidth user2 80000 Success.
To set maximum files
To set the maximum number of files and directories for a local user account, enter the following:
FTP> local user set max_files username number username max_value Specifies the name of a user account. Specifies the maximum number of files and directories allowed in the user's home directory.
For example:
FTP> local user set max_files user2 5000 Success.
356
To set maximum disk space usage
To set the maximum amount of disk space allowed for a local user account, enter the following:
FTP> local user set max_usage username number username number Specifies the name of a user account. Specifies the maximum amount of disk space available for files stored in the user's home directory. Values can be specified as M (megabytes), G (gigabytes), or T (terabytes). For example, 200G.
For example:
FTP> local user set max_usage user2 10T Success.
To set maximum connections
To set the maximum number of simultaneous connections a local user can have to the FTP server, enter the following:
FTP> local user set max_connections username number username number Specifies the name of a user account. Specifies the maximum number of simultaneous connects a user can have to the FTP server.
For example:
FTP> local user set max_connections user2 1000 Success.
357
To set the home directory
To set the home directory for a local user account, enter the following:
FTP> local user set homedir username dir_name username dir_name Specifies that name of a user account. Specifies the name of the home directory for the local user account.
For example:
FTP> local user set homedir user2 home Success.
The home directory you configure for a local user account is created relative to the home directory path configured by the FTP> set homedir_path command. Changes to this value are applicable for any new connections. Configuring a new home directory location does not migrate any existing data in a local user's current home directory to the new home directory.
358
Chapter
11
Configuring your HTTP server


About configuring your HTTP server for accessing FileStore data About using the HTTP server commands About HTTP set commands About HTTP alias commands About HTTP document root mapping commands
About configuring your HTTP server for accessing FileStore data

In addition to CIFS, FTP, and NFS, you can access FileStore file data by way of the Hypertext Transfer (HTTP) protocol using a standard HTTP server. You specify the document root directory of the HTTP server to access data within one or more FileStore file systems. These files can then be accessed and downloaded by way of the HTTP protocol. Note: If you are monitoring HTTP downloads, Internet Explorer may display an incorrect percentage of the amount of a file downloaded by HTTP. Occasionally, Internet Explorer might display the percentage downloaded as more than 100%. In addition, Internet Explorer may sometimes only partially download a file, without displaying an error message for the partial download.
360
Configuring your HTTP server About using the HTTP server commands
About using the HTTP server commands

You use the HTTP> server commands to configure a Hypertext Transfer (HTTP) server. The HTTP server allows files to be accessed using the HTTP protocol. The HTTP server is started on the standard HTTP port 80. By default, the HTTP server is not running. Table 11-1 Command
server start
HTTP server commands Definition

Starts the HTTP server. By default, the HTTP server is not running. See Starting the HTTP server on page 360.
server stop
Stops any existing HTTP sessions. See Stopping the HTTP server on page 361.
server status
Displays the status for the HTTP server. See Displaying the status for the HTTP server on page 361.
Starting the HTTP server

To start the HTTP server
To start the HTTP server, enter the following:

HTTP> server start
For example:
HTTP> server start Success.
Configuring your HTTP server About HTTP set commands
361
Stopping the HTTP server

To stop the HTTP server
To stop the HTTP server, enter the following:

HTTP> server stop
For example:
HTTP> server stop Success.
Displaying the status for the HTTP server

To display the status for the HTTP server
To display the status for the HTTP server, enter the following:
HTTP> server status
For example:
HTTP> server status HTTP Status on sfs_01 : ONLINE HTTP Status on sfs_02 : ONLINE
About HTTP set commands

You use the HTTP> set commands to set various configurable options for the HTTP server. You can view the current HTTP sessions using the HTTP> session show command. You can also display the list of all HTTP configurable options and their values using the HTTP> show command. Table 11-2 Command
session show
HTTP set commands Definition

Displays the current HTTP sessions on each node. See Displaying the current HTTP sessions on each node on page 363.
362
Table 11-2 Command
HTTP set commands (continued) Definition

Sets the minimum number of threads that need to be kept idle to handle sudden bursts of requests. If there is a sudden burst of requests, the HTTP server attempts to use these spare threads, and tries to start other new spare threads in the background. See Setting the minimum number of idle threads for handling request spikes on page 363.
set MinSpareThreads
set MaxSpareThreads
Sets the maximum number of idle threads to handle request spikes. If there are more than MaxSpareThreads idle, then those threads are terminated. See Setting the maximum number of idle threads for handling request spikes on page 363.
set MaxThreads
Sets the maximum number of threads that will be created. If all MaxThreads are busy, new incoming requests may be blocked or discarded. See Setting the maximum number of threads to be created on page 364.
set StartThreads
Sets the initial number of server threads to start with. If this value is less than MinSpareThreads, the HTTP server initially starts with the StartThreads value, and more threads are created until there are at least MinSpareThreads idle. See Setting the initial number of server threads on page 364.
set ThreadsPerProc
Sets the maximum number of threads in each server process. See Setting the maximum number of threads in each server process on page 364.
show
Displays the list of all configurable HTTP options and their values. See Displaying the list of all configurable HTTP options and their values on page 365.
363
Displaying the current HTTP sessions on each node

To display the current HTTP sessions on each node
To display the current HTTP sessions on each node, enter the following:
HTTP> session show
For example:
HTTP> session show Max Sessions: 2000 Nodename -------sfs_01 sfs_02 Current Sessions ---------------4 2
Setting the minimum number of idle threads for handling request spikes
To set the minimum number of idle threads for handling request spikes
To set the minimum number of idle threads for handling request spikes, enter the following:
HTTP> set MinSpareThreads value
where value is the minimum number of idle threads. value has to be less than MaxSpareThreads.
Setting the maximum number of idle threads for handling request spikes
To set the maximum number of idle threads to handle request spikes
To set the maximum number of idle threads to handle request spikes, enter the following:
HTTP> set MaxSpareThreads value
where value is the maximum number of idle threads. For example:

HTTP> set MaxSpareThreads 10 Success.
364
Setting the maximum number of threads to be created

To set the maximum number of threads to be created
To set the maximum number of threads to be created, enter the following:

HTTP> set MaxThreads value
where value is the maximum number of threads to be created.
Setting the initial number of server threads

To set the initial number of server threads
To set the initial number of server threads, enter the following:

HTTP> set StartThreads value
where value is the initial number of server threads.
Setting the maximum number of threads in each server process

To set the maximum number of threads in each server process
To set the maximum number of threads in each server process, enter the following:
HTTP> set ThreadsPerProc value
where value is the maximum number of threads in each server process.
Configuring your HTTP server About HTTP alias commands
365
Displaying the list of all configurable HTTP options and their values
To display the list of all configurable HTTP options and their values
To display the list of all configurable HTTP options and their values, enter the following:
HTTP> show
For example:
HTTP> show DocumentRoot Parameter --------MinSpareThreads MaxSpareThreads MaxThreads StartThreads ThreadsPerProc Virtual Path -----------/fs_str0
/vx/fs_str Current Value -------------7 9 100 8 4 Real Path ---------/vx/fs_str
About HTTP alias commands

You use the HTTP> alias commands to configure HTTP aliases that provide mappings of physical directories (realPath) to virtual paths (virtualPath). Changes are visible to new HTTP connections. Existing HTTP connections still use the old HTTP mappings. Table 11-3 Command
alias add
HTTP alias commands Definition

Adds a mapping from a virtualPath to a realPath. When clients try to access a virtualPath, they will be accessing the realPath instead. realPath needs to be an existing directory. If a virtualPath ends with a slash (/), then the realPath should also end with a slash (/). If a virtualPath does not end with a slash (/), then the realPath should also not end with a slash (/). See Adding a mapping from a virtualPath to a realPath on page 366.
366
Configuring your HTTP server About HTTP alias commands
Table 11-3 Command

alias del
HTTP alias commands (continued) Definition

Deletes a mapping that is visible from clients as a virtualPath. See Deleting a mapping that is visible to clients as a virtualPath on page 367.
alias show
Displays all the aliases configured on the server. See Displaying all the aliases configured on the server on page 367.
Adding a mapping from a virtualPath to a realPath

To add a mapping from a virtualPath to a realPath
To add a mapping from a virtualPath to a realPath, enter the following:

HTTP> alias add virtualPath realPath virtualPath Virtual path visible from the HTTP server. For example: /fs_str0. realPath Existing physical directory location. realPath needs to be an existing directory, and it needs to belong to the /vx directory. For example: /vx/fs_str.
For example:
HTTP> alias add /new/vx/fs_new Success. Virtual Path -----------/fs_str0 /new Real Path --------/vx/fs_str /vx_fs_new
Configuring your HTTP server About HTTP document root mapping commands
367
Deleting a mapping that is visible to clients as a virtualPath

To delete a mapping that is visible to clients as a virtualPath
To delete a mapping that is visible to clients as a virtualPath, enter the following:

HTTP> alias del virtualPath
where virtualPath is the virtual directory path you created. For example:
HTTP> alias del /new Success. HTTP> alias show Virtual Path -----------/fs_str0 Real Path --------/vs/fs_str
Displaying all the aliases configured on the server

To display all the aliases configured on the server
To display all the aliases configured on the server, enter the following:
HTTP> alias show
For example:
HTTP> alias show Virtual Path -----------/fs_str0 /new Real Path --------/vx/fs_str /vx/fs_new
About HTTP document root mapping commands

You use the HTTP> documentRoot commands to specify and then to display the root directory for the HTTP server.
368
Configuring your HTTP server About HTTP document root mapping commands
Table 11-4 Command

documentRoot set
HTTP document root mapping commands Definition

Specifies the root directory for the HTTP server. This is represented by '/' for Web serving. See Setting the root directory for the HTTP server on page 368.
documentRoot show
Displays the root directory for the HTTP server. See Displaying the current root directory for the HTTP server on page 368.
Setting the root directory for the HTTP server

To set the root directory for the HTTP server
To set the root directory for the HTTP server, enter the following:
HTTP> documentRoot set document_root_dir
where document_root_dir is the root directory for the HTTP server. For example:
HTTP> documentRoot set /vx/test_fs/http_dir Success.
Displaying the current root directory for the HTTP server

To display the current root directory for the HTTP server
To display the current root directory for the HTTP server, enter the following:
HTTP> documentRoot show
For example:
HTTP> documentRoot show DocumentRoot /vx/test_fs/http_dir
Chapter
12
Configuring event notifications and audit logs


About configuring event notifications and audit logs About severity levels and filters About email groups Configuring an email group About syslog event logging Configuring a syslog server Displaying events on the console About SNMP notifications Configuring an SNMP management server Configuring events for event reporting Exporting events in syslog format to a given URL About audit logs Configuring audit logs Disabling the audit log for a file system
370
Configuring event notifications and audit logs About configuring event notifications and audit logs
About configuring event notifications and audit logs

FileStore monitors the status and health of various network and storage components, and generates events to notify the administrator. FileStore provides a mechanism to send these events to external event monitoring applications like syslog server, SNMP trap logger, and email servers. This section explains how to configure FileStore so that external event monitoring applications are notified of events on the FileStore cluster. This chapter discusses the FileStore report commands. The Report commands are defined in Table 12-1. To access the commands, log into the administrative console (for master, system-admin, or storage-admin) and enter Report> mode. See About using the FileStore command-line interface on page 33. Table 12-1 Command
event
Report mode commands Definition

Configures events for event reporting. See Configuring events for event reporting on page 385.
exportevents
Exports events in syslog format to a given URL. See Exporting events in syslog format to a given URL on page 386.
email
Configures an email group. See Configuring an email group on page 373.
syslog
Configures a syslog server. See Configuring a syslog server on page 379.
snmp
Configures an SNMP management server. See Configuring an SNMP management server on page 382.
showevents
Displays events. See Displaying events on the console on page 381.
audit
Configures audit logs to record file system activity on file systems that are enabled for data archive and retention (DAR).See Configuring audit logs on page 389.
Configuring event notifications and audit logs About severity levels and filters
371
About severity levels and filters

FileStore monitors events of different severity levels. Setting the severity to a particular level informs FileStore to stop notifications about lower-level events. Notifications are sent for events having the same or higher severity. Table 12-2 describes the valid FileStore severity levels in descending order of severity. Table 12-2 Valid value
emerg alert crit err warning notice info debug
Severity levels Description

Indicates that the system is unusable Indicates that immediate action is required Indicates a critical condition Indicates an error condition Indicates a warning condition Indicates a normal but significant condition Indicates an informational message Indicates a debugging message
FileStore classifies event notifications by area. Setting the event filter to a specific level filters out other areas. Notifications are sent for events matching the given filter. The following filters are configurable:
Network - if an alert is for a networking event, then selecting the network filter triggers that alert. If you select the network filter only, and an alert is for a storage-related event, the network alert is not sent. Storage - is for storage-related events, for example, file systems, snapshots, disks, and pools All
About email groups

The Report> email commands configure the email notifications of events. These commands support the following:
372
Configuring event notifications and audit logs About email groups
Adding email groups Adding filters to the group Adding email addresses to the email group Adding event severity to the group Configuring an external email server for sending event notification emails Email group commands Definition
Displays an existing email group or details for the email group. See Configuring an email group on page 373.
Table 12-3 Command

email show
email add group
Uses email groups to group multiple email addresses into one entity; the email group is used as the destination of the FileStore email notification. Email notification properties can be configured for each email group. When an email group is added initially, it has the all default filter. When a group is added initially, the default severity is info. See Configuring an email group on page 373.
email add email-address
Adds an email address to a group. See Configuring an email group on page 373.
email add severity Adds a severity level to an email group. See Configuring an email group on page 373. email add filter Adds a filter to a group. See Configuring an email group on page 373. email del email-address email del filter Deletes an email address. See Configuring an email group on page 373. Deletes a filter from a specified group. See Configuring an email group on page 373. email del group Deletes an email group. See Configuring an email group on page 373. email del severity Deletes a severity from a specified group. See Configuring an email group on page 373.
Configuring event notifications and audit logs Configuring an email group
373
Table 12-3 Command

email get
Email group commands (continued) Definition

Displays the details of the configured email server. Obtain the following information:

Name of the configured email server Email user's name Email user's password
See Configuring an email group on page 373. email set Displays details for the configured email server and the email user. See Configuring an email group on page 373. email set Deletes the configured email server by specifying the command without any options to delete the email server. See Configuring an email group on page 373.
Configuring an email group

FileStore can be configured to send email messages to users or groups of users through an external SMTP server. To display attributes of an email group
To display attributes of an email group, enter the following:

Report> email show [group]
where group is optional, and it specifies the group for which to display the attributes. If the specified group does not exist, an error message is displayed. For example:
Report> email show root Group Name: root Severity of the events: info,debug Filter of the events: all,storage Email addresses in the group: adminuser@localhost OK Completed
To add a new email group
To add a new email group, enter the following:

Report> email add group group
374
where group specifies the name of the new email group and can only contain the following characters:

Alpha characters Numbers Hyphens Underscores
Entering invalid characters results in an error message. If the entered group already exists, then no error message is displayed. For example:
Report> email add group alert-grp OK Completed
Multiple email groups can be defined, each with their own email addresses, event severity, and filter. To add an email address to an existing group
To add an email address to an existing group, enter the following:

Report> email add email-address group email-address
For example:
Report> email add email-address alert-grp username@company.com OK Completed group Specifies the group to which the email address is being added. If the email group specified does not exist, then an error message is displayed. Specifies the email address to be added to the group. If the email address is not a valid email address, for example, name@symantecexample.com, a message is displayed. If the email address has already been added to the specified group, a message is displayed.
email-address
375
To add a severity level to an existing email group
To add a severity level to an existing email group, enter the following:

Report> email add severity group severity
For example:
Report> email add severity alert-grp alert OK Completed group Specifies the email group for which to add the severity. If the email group specified does not exist, an error message is displayed. Indicates the severity level to add to the email group. See About severity levels and filters on page 371. Entering an invalid severity results in an error message, prompting you to enter a valid severity. Only one severity level is allowed at one time. You can have two different groups with the same severity levels and filters. Each group can have its own severity definition. You can define the lowest level of the severity that will trigger all other severities higher than it.
severity
376
To add a filter to an existing group
To add a filter to an existing group, enter the following:

Report> email add filter group filter group Specifies the email group for which to apply the filter. If the specified email group does not exist, an error message is displayed. Specifies the filter for which to apply to the group. See About severity levels and filters on page 371. The default filter is all. A group can have more than one filter, but there may not be any duplicate filters for the group.
filter
For example:
Report> email add filter root storage OK Completed
To delete an email address from an existing group
To delete an email address from an existing group, enter the following:

Report> email del email-address group email-address group Specifies the group from which to delete the email address. If the entered group does not exist, an error message is displayed. Specifies the email address from which to delete from the group. If the email address entered does not exist for the group, an error message is displayed.
email-address
For example, to delete an existing email address from the email group, enter the following:
Report> email del email-address root testuser@localhost
377
To delete a filter from an existing group
To delete a filter from an existing group, enter the following:

Report> email del filter group filter group Specifies the group to remove the filter from. If the entered email group does not exist, an error message is displayed. Specifies the filter to be removed from the group. See About severity levels and filters on page 371. The default filter is all. If the specified filter is not in the specified group, an error message is displayed.
filter
To delete an existing email group
To delete an existing email group, enter the following:

Report> email del group group
where group specifies the name of the email group to be deleted. If the email group specified does not exist, an error message is displayed. To delete a severity from a specified group
To delete a severity from a specified group, enter the following:

Report> email del severity group severity group Specifies the name of the email group from which the severity is to be deleted. If the specified email group does not exist, an error message is displayed. Specifies the severity to delete from the specified group. See About severity levels and filters on page 371. A severity cannot be deleted from a group if it does not exist for that group. If this occurs, an error message is displayed.
severity
378
Configuring event notifications and audit logs About syslog event logging
To display email server settings
To display email server settings, enter the following:

Report> email get E-Mail Server: smtp.symantec.com E-Mail Username: adminuser E-mail User's Password: ******** OK Completed
To add an email server and user account
To add an email server and user account from which email notifications are sent out, enter the following:
Report> email set [email-server] [email-user] email-server Specifies the external email server from which email notifications are sent out. Specifies the user account from which email notifications are sent out. If email-user is specified, then the password for that user on the SMTP server is required.
email-user
For example:
Report> email set smtp.symantec.com adminuser Enter password for user 'adminuser': ********
To delete the email server from sending email messages
To delete the email server from sending email messages, enter the following command without any options:
Report> email set
About syslog event logging

FileStore can be configured to send system log messages to syslog servers based on severity and filter. In FileStore, options include specifying the external system log (syslog) server for event reporting, and setting the filter and/or severity levels for events. Event
Configuring event notifications and audit logs Configuring a syslog server
379
notifications matching configured severity levels and filters are logged to those external syslog servers. See About severity levels and filters on page 371. Table 12-4 Commands
syslog show
Syslog commands Definition

Displays the list of syslog servers. See Configuring a syslog server on page 379.
syslog add
Adds a syslog server See Configuring a syslog server on page 379.
syslog set severity Sets the severity for the syslog server. See Configuring a syslog server on page 379. syslog set filter Sets the syslog server filter. See Configuring a syslog server on page 379. syslog get filter Displays the values of the configured syslog server. See Configuring a syslog server on page 379. syslog delete Deletes a syslog server. See Configuring a syslog server on page 379.
Configuring a syslog server

FileStore can be configured to send syslog messages to syslog servers based on set severities and filters. To display the list of syslog servers
To display the list of syslog servers, enter the following:

Report> syslog show
To add a syslog server to receive event notifications
To add a syslog server to receive event notifications, enter the following:

Report> syslog add syslog-server-ipaddr
where syslog-server-ipaddr specifies the hostname or the IP address of the external syslog server.
380
Configuring event notifications and audit logs Configuring a syslog server
To set the severity of syslog messages
To set the severity of syslog messages to be sent, enter the following:

Report> syslog set severity value
where value indicates the severity of syslog messages to be sent. For example:
Report> syslog set severity warning
See About severity levels and filters on page 371. To set the filter level of syslog messages
To set the filter level of syslog messages to be sent, enter the following:
Report> syslog set filter value
where value indicates the filter level of syslog messages to be sent. For example:
Report> sylog set filter storage OK Completed
See About severity levels and filters on page 371. To display the values of the configured filter/severity level settings
To display the values of the configured filter/severity level settings, enter the following:
Report> syslog get filter|severity
For example:
Report> syslog get severity Severity of the events: err OK Completed
To delete a syslog server from receiving message notifications
To delete a syslog server from receiving message notifications, enter the following:
Report> syslog delete syslog-server-ipaddr
syslog-server-ipaddr specifies the hostname or the IP address of the syslog server.
Configuring event notifications and audit logs Displaying events on the console
381
Displaying events on the console

To display events on the console
To display events on the console, enter the following:

Report> showevents [number_of_events]
where number_of_events specifies the number of events that you want to display. If you leave number_of_events blank, or if you enter 0, FileStore displays all of the events in the system.
About SNMP notifications

Simple Network Management Protocol (SNMP) is a network protocol to simplify the management of remote network-attached devices such as servers and routers. SNMP is an open standard system management interface. Information from the Management Information Base (MIB) can also be exported. SNMP traps enable the reporting of a serious condition to a management station. The management station is then responsible for initiating further interactions with the managed node to determine the nature and extent of the problem. In FileStore, options include specifying the SNMP server to receive traps from the FileStore cluster, and selecting the severity of the occurrences to report. See About severity levels and filters on page 371. Table 12-5 Command
snmp add
SNMP commands Definition

Adds an SNMP management server. See Configuring an SNMP management server on page 382.
snmp show
Displays the current list of SNMP management servers. See Configuring an SNMP management server on page 382.
snmp delete
Deletes an already configured SNMP management server. See Configuring an SNMP management server on page 382.
snmp set severity
Sets the severity for SNMP notifications. See Configuring an SNMP management server on page 382.
snmp set filter
Sets the filter for SNMP notifications. See Configuring an SNMP management server on page 382.
382
Configuring event notifications and audit logs Configuring an SNMP management server
Table 12-5 Command

snmp get filter|severity snmp exportmib
SNMP commands (continued) Definition

Displays the values of the configured SNMP notifications. See Configuring an SNMP management server on page 382. Uploads the SNMP Management Information Base (MIB) file to the given URL. The URLs support FTP and SCP. If the url specifies a remote directory, the default filename is sfsfs_mib.txt. See Configuring an SNMP management server on page 382.
Configuring an SNMP management server

To add an SNMP management server to receive SNMP traps
To add an SNMP management server to receive SNMP traps, enter the following:
Report> snmp add snmp-mgmtserver-ipaddr
snmp-mgmtserver-ipaddr specifies the host name or the IP address of the SNMP management server. For example, if using the IP address, enter the following:
Report> snmp add 10.10.10.10 OK Completed
For example, if using the host name, enter the following:

Report> snmp add mgmtserv1.symantec.com OK Completed
SNMP traps can be sent to multiple SNMP management servers. To display the current list of SNMP management servers
To display the current list of SNMP management servers, enter the following:
Report> snmp show Configured SNMP management servers: 10.10.10.10,mgmtserv1.symantec.com OK Completed
383
To delete an already configured SNMP management server from receiving SNMP traps
To delete an already configured SNMP management server from receiving SNMP traps, enter the following:
Report> snmp delete snmp-mgmtserver-ipaddr
specifies the host name or the IP address of the SNMP management server. For example:
Report> snmp delete 10.10.10.10 OK Completed
If you input an incorrect value for snmp-mgmtserver-ipaddr, an error message displays. For example:
Report> snmp delete mgmtserv22.symantec.com SFS snmp delete ERROR V-288-26 Cannot delete SNMP management server, it doesn't exist.
To set the severity for SNMP traps to be sent
To set the severity for SNMP traps to be sent, enter the following:
Report> snmp set severity value
where value indicates the severity for the SNMP trap to be sent. For example:
Report> snmp set severity warning OK Completed
See About severity levels and filters on page 371.
384
To set the filter level of SNMP traps
To set the filter level for SNMP traps, enter the following:
Report> snmp set filter value
where value indicates the filter. For example:

Report> snmp set filter network OK Completed
See About severity levels and filters on page 371. To display the filter or severity levels of SNMP traps to be sent
To display the filter or severity levels of SNMP traps to be sent, enter the following:
Report> snmp get filter|severity
For example:
Report> snmp get severity Severity of the events: warning OK Completed Report> snmp get filter Filter for the events: network OK Completed
To export the SNMP MIB file to a given URL
To export the SNMP MIB file to a given URL, enter the following:
Report> snmp exportmib url
where url specifies the location the SNMP MIB file is exported to. FTP and SCP URLs are supported. For example:
Report> snmp exportmib scp://admin@server1.symantec.com:/tmp/sfsfs_mib.txt Password: ***** OK Completed
If the url specifies a remote directory, the default filename is sfsfs_mib.txt.
Configuring event notifications and audit logs Configuring events for event reporting
385
Configuring events for event reporting

To reduce duplicate events
To reduce the number of duplicate events sent for notifications, enter the following:
Report> event set dup-frequency number
where number indicates time (in seconds) in which only one event (of duplicate events) is sent for notifications. For example:
Report> event set dup-frequency 120 OK Completed
where number indicates the number of duplicate events to ignore.

Report> event set dup-number number
For example:
Report> event set dup-number 10 OK Completed
To display the time interval or the number of duplicate events sent for notifications
To display the time interval, enter the following:

Report> event get dup-frequency
For example:
Report> event get dup-frequency Duplicate events frequency (in seconds): 120 OK Completed
To set the number of duplicate events sent for notifications, enter the following:
Report> event get dup-number
For example:
Report> event get dup-number Duplicate number of events: 10 OK Completed
386
Configuring event notifications and audit logs Exporting events in syslog format to a given URL
Exporting events in syslog format to a given URL

You can export events in syslog format to a given URL. Supported URLs for upload include:

FTP SCP
To export events in syslog format to a given URL
To export events in syslog format to a given URL, enter the following:

Report> exportevents url
url specifies the location to which the events in syslog format are exported to. For example:
Report> exportevents scp://root@server1.symantecexample.com: /exportevents/event.1 Password: ****** OK Completed
If the URL specifies a remote directory, the default filename is sfsfs_event.log. To export audit events in syslog format to a given URL
To export audit events in syslog format to a given URL, enter the following:
Report> exportevents url [audit]
url specifies the location to which the audit events in syslog format are exported to. For example:
Report> exportevents scp://root@server1.symantecexample.com: /exportauditevents/auditevent.1 Password: ****** OK Completed
If the URL specifies a remote directory, the default filename is sfsfs_audit.log.
Configuring event notifications and audit logs About audit logs
387
About audit logs

Use Report> audit commands to configure audit logs for DAR-enabled file systems. When enabled, the audit log feature tracks file system activity and stores the results in log files. To configure an audit log:
Specify the file system to be logged. Only DAR-enabled file system can be configured for audit logs. Choose which activities (operations) on the file system are included in the log. Only the activities you specify are logged, no other operations are logged.
Note: When audit logs are configured for a DAR-enabled file system, that file system cannot be taken offline or destroyed. Table 12-6 Command
audit fs enable
Audit commands Definition

Enables audit logs on a DAR-enabled file system. See Configuring audit logs on page 389.
audit fs list
Displays the set of operations (and WORM-only settings) enabled for audit logs. See Configuring audit logs on page 389.
audit fs show
Shows audit logs for a file systems. See Configuring audit logs on page 389.
audit fs disable
Disables audit logs for a file system. Disabling audit logs does not delete current audit log records. See Configuring audit logs on page 389.
Table 12-7 lists the file system operations you can include in audit logs. Table 12-7 Operation
all all_metadata (default)
File system operations in audit logs Definition

All file system operations. All metadata operations.
388
Configuring event notifications and audit logs About audit logs
Table 12-7 Operation

all_create
File system operations in audit logs (continued) Definition

All file create operations. This includes the create, mkdir, link, and symlink operations. All delete file operations. This includes the delete, unlink, and rmdir operations. All set extended attribute operations. This includes setattr and setxattr operations. All open file operations. All close file operations. All file write operations. All file read operations. All file rename operations. All file create operations. All make directory operations. All file link operations. All symbolic link operations for files. All unlink operations. All remove directory operations. All file rename operations. All file set attribute operations. All file set extended attribute operations. All file remove attribute operations. All file get attribute operations. All file get extended attribute operations. All file-related list extended attribute operations.
all_delete
all_setxattr
open close write read rename create mkdir link symlink unlink rmdir rename setattr setxattr removeattr getattr getxattr list_xattr
Configuring event notifications and audit logs Configuring audit logs
389
Configuring audit logs

To enable an audit log
To configure an audit log for a DAR-enabled file system, enter the following:
Report> audit fs enable fs_name [operations] [wormonly=yes|no] fs_name Specifies the name of the file system you want to audit. You can only audit DAR-enabled file systems. A comma-separated list of operations to audit. Only the operations you specify are logged. See About audit logs on page 387. wormonly Valid inputs for the wormonly option are wormonly=yes or wormonly=no. If you specify wormonly=yes, only operations done on WORM files are audited. If you specify wormonly=no, all files (WORM and non-WORM) are audited. The default is wormonly=yes. Report> audit fs enable fs1 read,write wormonly=no
operations
To list operations tracked by an audit log
To list which operations are tracked by an audit log, enter the following:
Report> audit fs list [fs_name]
where fs_name is the name of the file system. If fs_name is not specified, a list of audit log operations for all DAR-enabled file systems is displayed.
Report> audit fs list File system: fs1 Operations: read,write Wormonly: wormonly=no File system: fs2 Operations: all Wormonly: wormonly=yes
390
Configuring event notifications and audit logs Configuring audit logs
To show audit results for a DAR-enabled file system
To show audit log entries for a file system, enter the following:
Report> audit fs show fs_name [operations] [maxlines] fs_name Specifies the name of the file system whose audit log you want to view. A comma-separated list of operations to display in the log. Only log entries for the operations you specify will be displayed. By default all_metadata operations are displayed. See About audit logs on page 387. maxlines The maximum number of lines shown for an audit log. If you specify zero (0), all lines in the log are shown. The default is 10 lines.
operations
Report> audit fs show fs1 all 0 Filename ======== /vx/fs1/file2 /vx/fs1/file2 /vx/fs1/file2 /vx/fs1/file2 /vx/fs1/file1 /vx/fs1/file1 /vx/fs1/file1 /vx/fs1/file1 /vx/fs1/file1 /vx/fs1/file1 /vx/fs1/file1 /vx/fs1/file1 /vx/fs1/file1 /vx/fs1/file1 Operation ========= write write setattr create setattr create write write setxattr setattr setattr create unlink create UID === 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Timestamp ========= Aug 18 13:19:04 Aug 18 13:19:04 Aug 18 13:16:50 Aug 18 13:16:50 Aug 18 13:16:22 Aug 18 13:16:22 Aug 18 10:37:10 Aug 18 10:37:10 Aug 18 10:31:26 Aug 18 10:30:59 Aug 18 10:30:57 Aug 18 10:30:57 Aug 18 10:30:26 Aug 18 10:29:00 Success ======= Success Success Success Success Success Success Success Success Success Success Success Success Success Success
2010 2010 2010 2010 2010 2010 2010 2010 2010 2010 2010 2010 2010 2010
Configuring event notifications and audit logs Disabling the audit log for a file system
391
Disabling the audit log for a file system

To disable the audit log for a file system
To disable the audit log for a file system, enter the following:
Report> audit fs disable fs_name
where fs_name is the name of the file system. When you disable an audit log, the current audit log records are not deleted.
Report> audit fs disable fs1
392
Configuring event notifications and audit logs Disabling the audit log for a file system
Chapter
13
Configuring backup

About backup About NetBackup About the NetBackup snapshot client About NetBackup snapshot methods About NetBackup instant recovery About Fibre Transport About SAN clients About FT media servers About the FT Service Manager About zoning the SAN for Fibre Transport About HBAs for SAN clients and FT media servers About connecting the fiber for SAN Client Adding a NetBackup master server to work with FileStore Configuring or changing the virtual IP address used by NetBackup and NDMP data server installation Configuring the virtual name of NetBackup About Network Data Management Protocol About backup configurations Configuring backup
394
Configuring backup About backup
Configuring backups using NetBackup or other third-party backup applications
About backup
The Backup commands are defined in Table 13-1. To access the commands, log into the administrative console (for master, system-admin, or storage-admin) and enter the Backup> mode. See About using the FileStore command-line interface on page 33. Table 13-1 Command
netbackup
Backup mode commands Definition

Configures the local NetBackup installation of FileStore to use an external NetBackup master server, Enterprise Media Manager (EMM) server, or media server. See About NetBackup on page 395.
virtual-ip
Configures the NetBackup and NDMP data server installation on FileStore nodes to use ipaddr as its virtual IP address. See Configuring or changing the virtual IP address used by NetBackup and NDMP data server installation on page 402.
virtual-name
Configures the NetBackup installation on FileStore nodes to use name as its hostname. See Configuring the virtual name of NetBackup on page 403.
ndmp
Transfers data between the data server and the tape server under the control of a client. The Network Data Management Protocol (NDMP) is used for data backup and recovery. See About Network Data Management Protocol on page 403.
show
Displays settings of the configured servers. See About backup configurations on page 417.
status
Displays status of configured servers. See About backup configurations on page 417.
start
Starts the configured servers. See About backup configurations on page 417.
stop
Stops the configured servers. See About backup configurations on page 417.
Configuring backup About NetBackup
395
About NetBackup
FileStore includes built-in client software for Symantecs NetBackup data protection suite. If NetBackup is the enterprises data protection suite of choice, file systems hosted by FileStore can be backed up to a NetBackup media server. To configure the built-in NetBackup client, you need the names and IP addresses of the NetBackup master and media servers. Backups are scheduled from those servers, using NetBackups administrative console. Consolidating storage reduces the administrative overhead of backing up and restoring many separate file systems. With a 256 TB maximum file system size, FileStore makes it possible to collapse file storage into fewer administrative units, thus reducing the number of backup interfaces and operations necessary. All critical file data can be backed up and restored through the NetBackup client software included with FileStore (separately licensed NetBackup master and media servers running on separate computers are required), or through any backup management software that supports NAS systems as data sources. Table 13-2 Command
netbackup master-server
Netbackup commands Definition

Provides a functioning external NetBackup master server to work with FileStore. FileStore only includes the NetBackup client code on the FileStore nodes. If you want to use NetBackup to back up your FileStore file systems, you must add an external NetBackup master server. For NetBackup clients to be compliant with the NetBackup End-User License Agreement (EULA), you must have purchased and entered valid license keys on the external NetBackup master server prior to configuring NetBackup to work with FileStore. For more information on entering NetBackup license keys on the NetBackup master server, refer to the Symantec NetBackup Installation Guide, Release 7.0.1. See Adding a NetBackup master server to work with FileStore on page 400.
netbackup emm-server
Adds an external NetBackup Enterprise Media Manager (EMM) server (which can be the same as the NetBackup master server) to work with FileStore.
Note: If you want to use NetBackup to backup FileStore file systems,

you must add an external NetBackup EMM server. See Adding a NetBackup master server to work with FileStore on page 400.
396
Configuring backup About the NetBackup snapshot client
Table 13-2 Command

netbackup media-server add
Netbackup commands (continued) Definition

Adds an external NetBackup media server (if the NetBackup media server is not co-located with the NetBackup master server).
Note: Adding an external NetBackup media server is optional. If you

do not add one, then FileStore uses the NetBackup master server as the NetBackup media server. See Adding a NetBackup master server to work with FileStore on page 400. netbackup media-server delete Deletes an already configured NetBackup media server. See Adding a NetBackup master server to work with FileStore on page 400.
About the NetBackup snapshot client

A snapshot is a point-in-time, read-only, disk-based copy of a client volume. After the snapshot is created, NetBackup backs up data from the snapshot, not directly from the clients primary or original volume. Users and client operations can access the primary data without interruption while data on the snapshot volume is being backed up. The contents of the snapshot volume are cataloged as if the backup was produced directly from the primary volume. After the backup is complete, the snapshot-based backup image on storage media is indistinguishable from a backup image produced by a traditional, non-snapshot backup.
About NetBackup snapshot methods

NetBackup can create different types of snapshots. Each snapshot type that you configure in NetBackup is called a snapshot method. Snapshot methods enable NetBackup to create snapshots within the storage stack (such as the file system, volume manager, or disk array) where the data resides. If the data resides in a logical volume, NetBackup can use a volume snapshot method to create the snapshot. If the data resides in a file system, NetBackup can use a file system method, depending on the client operating system and the file system type. You select the snapshot method in the backup policy as explained under Selecting the snapshot method in the Symantec NetBackup 7.0.1 Snapshot Client Administrator's Guide.
Configuring backup About NetBackup instant recovery
397
Note: When using FileStore with NetBackup, select the VxFS_Checkpoint snapshot method.
About NetBackup instant recovery

This feature makes backups available for quick recovery from disk. Instant Recovery combines snapshot technologythe image is created with minimal interruption of user access to datawith the ability to do rapid snapshot-based restores. The snapshot is retained on disk as a full backup image.
About Fibre Transport

NetBackup Fibre Transport is a method of data transfer. It uses Fibre Channel and a subset of the SCSI command protocol for data movement over a SAN rather than TCP/IP over a LAN. It provides a high-performance transport mechanism between NetBackup clients and NetBackup media servers. Fibre Transport supports multiple, concurrent logical connections. The NetBackup systems that support Fibre Transport contain Fibre Channel HBAs that are dedicated to FT communication. The NetBackup Fibre Transport service is active on both the SAN clients and the NetBackup media servers that connect to the storage. Throughout this documentation, Fibre Transport connections between NetBackup clients and NetBackup servers are referred to as FT pipes.
About SAN clients

A NetBackup SAN client is a NetBackup client on which the Fibre Transport service is activated. The SAN client is similar to the NetBackup SAN media server that is used for the Shared Storage Option; it backs up its own data. However, the SAN client is based on the smaller NetBackup client installation package, so it has fewer administration requirements and uses fewer system resources. Usually, a SAN client contains critical data that requires high bandwidth for backups. It connects to a NetBackup media server over Fibre Channel. The NetBackup SAN Client Fibre Transport Service manages the connectivity and the data transfers for the FT pipe on the SAN clients. The SAN client FT service also discovers FT target mode devices on the NetBackup media servers and notifies the FT Service Manager about them.
398
Configuring backup About FT media servers
About FT media servers

A NetBackup FT media server is a NetBackup media server on which the Fibre Transport services are activated. NetBackup FT media servers accept connections from SAN clients and send data to the disk storage. The host bus adapters (HBAs) that accept connections from the SAN clients use a special NetBackup target mode driver to process FT traffic. The media server FT service controls data flow, processes SCSI commands, and manages data buffers for the server side of the FT pipe. It also manages the target mode driver for the host bus adaptors. Requires the SAN Client license.
About the FT Service Manager

The FT Service Manager (FSM) resides on the NetBackup server that hosts the NetBackup Enterprise Media Manager service. FSM interacts with the FT services that run on SAN clients and on FT media servers. FSM discovers, configures, and monitors FT resources and events. FSM runs in the same process as EMM.
About zoning the SAN for Fibre Transport

Before you can configure and use the NetBackup Fibre Transport mechanism, the SAN must be configured and operational. Instructions for how to configure and manage a SAN are beyond the scope of the NetBackup documentation. However, the following explains what is required for the SAN so that the SAN is prepared to work with the FT mechanism. Symantec Corporation recommends that you create the following zones:
An FT traffic zone that includes only the SAN clients and the NetBackup FT media servers HBA ports that connect to the SAN clients. To promote multistream throughput, each SAN client should detect all target mode devices of the media server HBA ports in the zone. The NetBackup SAN clients should detect only the HBA ports that are in target mode on the NetBackup media servers. They should not detect HBA ports in initiator mode on the NetBackup media servers. They should not detect HBAs on other hosts. Without zoning, each NetBackup SAN client host bus adapter (HBA) port detects all HBA ports from all hosts on the SAN. The potentially large number of devices may exceed the number that the operating system supports.
Configuring backup About HBAs for SAN clients and FT media servers
399
If the storage is connected to a SAN, a backup storage zone that includes the storage and the FT media server HBA ports that connect to the storage.
These zones prevent SAN Client traffic from using the bandwidth that may be required for other SAN activity. Note: You must use physical port ID or World Wide Port Name (WWPN) to specify the media server HBA ports that connect to the SAN clients.
About HBAs for SAN clients and FT media servers

The Fibre Channel host bus adapter (HBA) and driver requirements differ on the SAN clients and on the NetBackup FT media servers, as follows:
HBAs on SAN clients The HBAs on the SAN clients can be any supported Fibre Channel HBA. The HBA ports must operate in the default initiator mode. For the HBAs on the SAN client systems, do the following:

Install the drivers for the HBA. Install the utilities for the HBA. Although not required for NetBackup operation, the utilities may help to troubleshoot connectivity problems.
HBAs on NetBackup FT media servers
The NetBackup media servers that host Fibre Transport require the following:
For the connections to the SAN clients, use a QLogic HBA that NetBackup supports for Fibre Transport. For these HBAs, you must configure them to use the NetBackup target mode driver.
If you use SAN attached storage, you can use any supported Fibre Channel HBA to connect to the storage. For these HBAs, you should install the QLogic driver and utilities. The HBA ports that connect to the storage must remain in the default initiator mode. The HBAs and their drivers must support 256K size buffers for data transfer.
For information about supported HBAs, see the NetBackup Release Notes.
About connecting the fiber for SAN Client

NetBackup supports the following configurations for Fibre Transport:
400
Configuring backup Adding a NetBackup master server to work with FileStore
Node port (N_Port) switched Connect the NetBackup media servers and SAN clients to a configuration SAN switch as follows:
Connect the HBA port on the NetBackup FT media server to a Fibre Channel switch port.
Connect each SAN client HBA port to ports on the same Fibre Channel switch. Define the zones on the switch so that the client(s) and server(s) are in the same zone. Be aware of the following: You must define the NetBackup FT media server target ports by physical port ID or World Wide Port Name (WWPN). The target mode driver WWPNs are not unique because they are derived from the Fibre Channel HBA WWPN. You can define SAN clients by either port ID or WWPN. However, if you use one method only, zone definition and management is easier.
Direct connect Fibre Channel Use Fibre Channel arbitrated loop (FC-AL) to connect a arbitrated loop (FC-AL) NetBackup media server HBA port directly to a NetBackup configuration SAN client HBA port.
Note: FC-AL hubs are not supported.
Adding a NetBackup master server to work with FileStore

To add an external NetBackup master server
To add an external NetBackup master server, enter the following:

Backup> netbackup master-server server
where server is the hostname of the NetBackup master server. Make sure that server can be resolved through DNS, and its IP address can be resolved back to server through the DNS reverse lookup. For example:
Backup> netbackup master-server nbumaster.symantecexample.com Ok Completed
Configuring backup Adding a NetBackup master server to work with FileStore
401
To add a NetBackup EMM server
To add the external NetBackup EMM server, enter the following:

Backup> netbackup emm-server server
where server is the hostname of the NetBackup EMM server. Make sure that server can be resolved through DNS, and its IP address can be resolved back to server through the DNS reverse lookup. For example:
Backup> netbackup emm-server nbumedia.symantecexample.com OK Completed
To add a NetBackup media server
To add an NetBackup media server, enter the following:

Backup> netbackup media-server add server
where server is the hostname of the NetBackup media server. Make sure that server can be resolved through DNS, and its IP address can be resolved back to server through the DNS reverse lookup. For example:
Backup> netbackup media-server add nbumedia.symantecexample.com OK Completed
To delete an already configured NetBackup media server
To delete an already configured NetBackup media server, enter the following:

Backup> netbackup media-server delete server
where server is the hostname of the NetBackup media server you want to delete. For example:
Backup> netbackup media-server delete nbumedia.symantecexample.com OK Completed
402
Configuring backup Configuring or changing the virtual IP address used by NetBackup and NDMP data server installation
Configuring or changing the virtual IP address used by NetBackup and NDMP data server installation
You can configure or change the virtual IP address used by NetBackup and the NDMP data server installation on FileStore nodes. This is a highly available virtual IP address in the cluster. For information about the Symantec NetBackup 7.0.1 client capability, refer to the Symantec NetBackup 7.0.1 product documentation set. Note: If you are using NetBackup and the NDMP data server installation on FileStore nodes, configure the virtual IP address using the Backup> virtual-ip command so that it is different from all of the virtual IP addresses, including the console server IP address and the physical IP addresses used to install FileStore. To configure or change the virtual IP address used by NetBackup and NDMP data server installation
To configure or change the virtual IP address used by NetBackup and the NDMP data server installation on FileStore nodes, enter the following:
Backup> virtual-ip ipaddr [device] ipaddr The virtual IP address to be used with the NetBackup and the NDMP data server installation on the FileStore nodes. Make sure that ipaddr can be resolved back to the hostname that is configured by using the Backup> virtual-name command. The Ethernet interface for the virtual IP address.
device
For example:
Backup> virtual-ip 10.10.10.10 pubeth1 OK Completed
See Configuring the virtual name of NetBackup on page 403.
Configuring backup Configuring the virtual name of NetBackup
403
Configuring the virtual name of NetBackup

To configure or change the NetBackup hostname
To configure the NetBackup installation on FileStore nodes to use name as its hostname, enter the following:
Backup> virtual-name name
where name is the hostname to be used by the NetBackup installation on FileStore nodes.
Backup> virtual-name nbuclient.symantecexample.com
Make sure that name can be resolved through DNS, and its IP address can be resolved back to name through the DNS reverse lookup. Also, make sure that name resolves to an IP address configured by using the Backup> virtual-ip command. For example:
Backup> virtual-name nbuclient.symantecexample.com OK Completed
See Configuring or changing the virtual IP address used by NetBackup and NDMP data server installation on page 402.
About Network Data Management Protocol

The Network Data Management Protocol (NDMP) is an open protocol for transferring data between the data server and the tape server under the control of a client. NDMP is used for data backup and recovery. NDMP is based on a client-server architecture. The Data Management Application is the client and the data and tape services are the servers. The Data Management Application initiates the backup session. A single control connection from the Data Management Application to each of the data and tape services and a data connection between the tape and the data services creates a backup session. Note: The information in this section assumes you have the correct backup infrastructure in place that will support the NDMP environment. NDMP provides the following services:
Defines a mechanism and protocol for controlling backup, recovery, and other transfers of data between the data server and the tape server.
404
Configuring backup About Network Data Management Protocol
Separates the network attached Data Management Application, Data Servers, and Tape Servers participating in archival, recovery, or data migration operations. Provides low-level control of tape devices and SCSI media changers. NDMP terminology Definition
The host computer system that executes the NDMP server application. Data is backed up from the NDMP host to either a local tape drive or to a backup device on a remote NDMP host. The virtual state machine on the NDMP host that is controlled using the NDMP protocol. This term is used independently of implementation. There are three types of NDMP services: data service, tape service, and SCSI service. An instance of one or more distinct NDMP services controlled by a single NDMP control connection. Thus a Data/Tape/SCSI Server is an NDMP server providing data, tape, and SCSI services. The configuration of one client and two NDMP services to perform a data management operation such as a backup or a recovery. The application that controls the NDMP server. Backup and restore are initiated by the NDMP client. In NDMP version 4, the client is the Data Management Application.
Table 13-3 Terminology

host
service
server
session
client
Data Management An application that controls the NDMP session. In NDMP there is a Application master-slave relationship. The Data Management Application is the session master; the NDMP services are the slaves. In NDMP versions 1, 2, and 3 the term "NDMP client" is used instead of the Data Management Application.
The Backup> ndmp commands configure the default policies that will be used during the NDMP backup and restore sessions. In FileStore, NDMP supports the following commands:
setenv commands. The set environment commands let you configure the
variables that make up the NDMP backup policies for your environment.
getenv commands. The get environment commands display what you have
set up with the setenv commands or the default values of all of the NDMP environment variables.
showenv command. The show environment command displays all of the NDMP
policies.
405
restoredefaultenv command. The restore default environment command
restores the NDMP policies back to their default values.
About NDMP supported configurations

FileStore currently supports the three-way NDMP backup. The data and tape services reside on different nodes on a network. The Data Management Application has two control connections, one to each of the data and tape services. There is also a data connection between the data and the tape services. Data travels from the disk on an NDMP host to a tape device on another NDMP host. Backup data is sent over the local network. The tape drives must be in NDMP-type storage units. Figure 13-1 Illustration of three-way NDMP FileStore backup
NFS clients NBU / TSM / EMC Legato with Control NDMP Flow
Control Flow
Data Flow FileStore Cluster NDMP Server NBU Media Server with NDMP
Tape Library
Primary Storage Array
The NDMP commands configure the default policies that are used during the NDMP backup or restore sessions. The Data Management Application (client) initiating the connection for NDMP backup and restore operations to the NDMP data/tape server can override these default policies by setting the same policy
406
name as environment variable and using any suitable value of that environment variable. The FileStore NDMP server supports MD5 and text authentication. The Data Management Application that initiates the connection to the server uses master for the username and for the password for the NDMP backup session authentication. The password can be changed using the Admin> passwd command. See Creating Master, System Administrator, and Storage Administrator users on page 42.
About the NDMP policies

The Backup> ndmp commands configure the default policies which will be used during the NDMP backup/restore sessions. The DMA (NDMP client) initiating the connection for the NDMP backup/restore operation to the FileStore NDMP data server can override these default policies by setting the same policy name as environment variable and using any suitable value of that environment variable. Table 13-4 Command
ndmp setenv overwrite_policy
NDMP set commands Definition

Defines how new data is recorded over old data. There are three options available to configure this command: See Configuring the NDMP policies on page 407.
ndmp setenv failure_resilient Continues the backup and restore session even if an error condition occurs. During a backup or restore session, if a file or directory cannot be backed up or restored, setting value to yes lets the session continue with the remaining specified files and directories in the list. A log message is sent to the Data Management Application about the error. Refer to the Data Management Application documentation for the location of the NDMP logs. Some conditions, such as an I/O error, will not let the command continue the backup and restore session. See Configuring the NDMP policies on page 407.
407
Table 13-4 Command
NDMP set commands (continued) Definition

Configures the dynamic storage tiering (DST) restore policy.
ndmp setenv restore_dst
Note: During the restore session, the DST policy only

applies to the file system, but it does not become effective until you run it through the storage tier policy commands. See Configuring the NDMP policies on page 407. ndmp setenv recursive_restore Configures the NDMP recursive restore policy to restore the contents of a directory each time you restore. See Configuring the NDMP policies on page 407. ndmp setenv update_dumpdates Contains the file system backup information for the backup command. In the FileStore NDMP environment, the dumpdates file is /etc/ndmp.dumpdates. See Configuring the NDMP policies on page 407. ndmp setenv send_history States whether or not you want the file history of the backed up data to be sent to the Data Management Application. See Configuring the NDMP policies on page 407. ndmp setenv use_snapshot Lets you bring back previous versions of the files for review or to be used. A snapshot is a virtual copy of a set of files and directories taken at a particular point in time. The NDMP use snapshot policy enables the backup of a point-in-time image of a set of files and directories instead of a continuous changing set of files and directories. See Configuring the NDMP policies on page 407. ndmp setenv backup_method Enables the configuration of the NDMP backup method policy. This policy enables an incremental backup. See Configuring the NDMP policies on page 407. ndmp setenv masquerade_as_thirdparty Configures the masquerade as a third-party policy. See Configuring the NDMP policies on page 407.
Configuring the NDMP policies

Caution: No checks are made when overwriting the directory with the file or vice versa. The destination path being overwritten is removed recursively.
408
To configure the overwrite policy
To configure the overwrite policy, enter the following:

Backup> ndmp setenv overwrite_policy value
where the variables for value are listed in the following table.
no_overwrite Checks if the file or directory to be restored already exists. If it does, the command responds with an error message. A log message is returned to the Data Management Application. Refer to the Data Management Application documentation for the location of the NDMP log messages. The file or directory is not overwritten. Checks if the file or directory already exists. If it does, it is renamed with the suffix .#ndmp_old and a new file or directory is created. If the file or directory already exists, it will be overwritten. It is recommended that while doing a restore from incremental backups, the value is set to overwrite_always. No checks are made when overwriting a directory with files. The destination path being overwritten is removed recursively.
rename_old (default)
overwrite_always
For example:
Backup> ndmp setenv overwrite_policy rename_old Ok Completed
To configure the failure resilient policy
To configure the failure resilient policy, enter the following:

Backup> ndmp setenv failure_resilient value
where the variables for value are yes or no.

yes (default) The backup and restore session continues even if an error condition is encountered. However some conditions, such as the I/O error, will cause the backup and restore session to stop. The backup and restore session terminates immediately when it encounters any error condition.
no
409
To configure the restore DST policy
To configure the restore DST policy, enter the following:

Backup> ndmp setenv restore_dst value

yes (default) During the backup session, if the specified directory set up for backup is a directory in the file system mount point, then the DST policy will be backed up. During the restore session, if the DST policy exists in the backup stream, the DST policy that was backed up will be applied to the restore destination path if that path is a mount point (full file system restore). The DST policy will not be restored if the secondary tier does not exist on the destination path. If the DST policy could not be restored, a log message is returned to the Data Management Application (refer to the Data Management Application documentation for the location of the NDMP logs). During the restore, the DST policy will only be applied to the file system, but it will not be effective until you run it through the Storage> tier policy commands. no The DST policy is not applied even if all of the other conditions are met.
To configure the recursive restore policy
To configure the recursive restore policy, enter the following:

Backup> ndmp setenv recursive_restore value

yes (default) If the name list (names of the files and directories to be restored from the backup) specifies a directory, the contents of that directory will be restored recursively. Restores the directory, but not the contents of the directory.
no
410
To configure the update dumpdates policy
To configure the update dumpdates policy, enter the following:

Backup> ndmp setenv update_dumpdates value
where the variables for value are yes or no. If NetBackup is being used for backup by way of NDMP, use set UPDATE = No in NetBackup to disable updating dumpdates. Or use set UPDATE = "" to stop NetBackup from using a default value of yes.
yes (default) Updates the dumpdates files by the FileStore NDMP data server with the details of the current backup which includes the time at which the backup was taken, the directory that was backed up, and the level of the backup. This information can be later used for the next backup session for the incremental and differential backups. The dumpdates files will not be updated.
no
To configure the send history policy
To configure the send history policy, enter the following:

Backup> ndmp setenv send_history value

yes (default) Sends the history of the backed up data to the Data Management Application. The history includes information for every file and directory that was backed up, such as name, stat, positioning data (used for DAR restore), and inode information. The file history information will not be sent to the Data Management Application.
no
411
To configure the use snapshot policy
To configure the use snapshot policy, enter the following:

Backup> ndmp setenv use_snapshot value

yes (default) The backup session will first take the snapshot of the file system which is being backed up. The snapshot will also be taken if any directory of the file system is being backed up. The snapshot taken uses the same storage space as that of the main file system. The backup session takes the backup of only the live file system.
no
To configure the backup method policy
To configure the backup method policy, enter the following:

Backup> ndmp setenv backup_method value
where the variables for value are fcl or mtime.

FCL (default) File Change Log. FCL can be used to directly get the list of modified files in the file system and they can then be backed up. However, since FCL is finite in size, it is possible that not all of the changes could be recorded in the FCL. In that case, use the mtime backup method. Time of last modification. By checking the mtimes of the files in the file system, the time of last backup can be stored reliably somewhere in the file system, and the time can be used to find all of the modified files since last backup. The location where the 'time of last backup' is stored is /etc/ndmp.dumpdates. The filename is mentioned when you configure the update_dumpdates command.
mtime
For example:
Backup> ndmp setenv backup_method mtime OK Completed
412
To configure the masquerade as a third-party policy
To configure the masquerade as a third-party policy, enter the following:

Backup> ndmp setenv masquerade_as_thirdparty value

yes The FileStore NDMP server masquerades as a third-party compatible device for certain NDMP backup applications. The FileStore NDMP server does not masquerade as a third-party compatible device.
no (default)
For example:
Backup> ndmp setenv masquerade_as_thirdparty yes OK Completed Backup>
Displaying all NDMP policies

To display all of the NDMP policies
To display the NDMP policies, enter the following:

Backup> ndmp showenv
For example:
Backup> ndmp showenv Overwrite policy: Failure Resilient: Restore DST policies: Recursive restore: Update dumpdates: Send history: Use snapshot: Backup method: Masquerade as thirdparty: OK Completed
Rename old yes yes yes yes yes yes fcl yes
413
About retrieving the NDMP data

Table 13-5 Command
ndmp getenv overwrite_policy
NDMP get commands Definition

Defines how new data is recorded over old data. To retrieve the settings for the policy that you set up, use the ndmp getenv overwrite_policy command. See Retrieving the NDMP data on page 414.
ndmp getenv failure_resilient
Enables the continuation of the backup and restore session even if an error condition occurs because a file or directory cannot be backed up or restored. To retrieve the settings for the policy that you set up, use the ndmp getenv failure_resilient command. See Retrieving the NDMP data on page 414.
ndmp getenv restore_dst
Configures the dynamic storage tiering (DST) restore policy. To retrieve the settings for the policy that you set up, use the ndmp getenv restore_dst command. See Retrieving the NDMP data on page 414.
ndmp getenv recursive_restore
Enables the configuration of the restore session to restore the contents of a directory. To retrieve the settings for the policy that you set up, use the ndmp getenv recursive_restore command. See Retrieving the NDMP data on page 414.
ndmp getenv update_dumpdates
Enables the configuration of the dumpdates file. To retrieve the settings for the policy that you set up, use the ndmp getenv update_dumpdates command. See Retrieving the NDMP data on page 414.
ndmp getenv send_history
States whether or not you want the file history of the backed up data to be sent to the Data Management Application. To retrieve the settings for the policy that you set up, use the ndmp getenv send_history command. See Retrieving the NDMP data on page 414.
ndmp getenv use_snapshot
Enables how much of the files and directories you want to copy during the back up session. To retrieve the settings for the policy that you set up, use the ndmp getenv use_snapshot command. See Retrieving the NDMP data on page 414.
414
Table 13-5 Command
NDMP get commands (continued) Definition
ndmp getenv backup_method Enables the configuration of the method to back up the file system. To retrieve the settings for the policy that you set up, use the ndmp getenv backup_method command. See Retrieving the NDMP data on page 414. ndmp getenv masquerade_as_thirdparty Configures the NDMP server to masquerade as a third-party compatible device for certain NDMP backup applications. See Retrieving the NDMP data on page 414.
Retrieving the NDMP data

To retrieve the overwrite backup data
To retrieve the overwrite backup data, enter the following:

Backup> ndmp getenv overwrite_policy
For example:
Backup> ndmp getenv overwrite_policy Overwrite policy: Rename old OK Completed
To retrieve the failure resilient backup data
To retrieve the failure resilient data, enter the following:

Backup> ndmp getenv failure_resilient
For example:
Backup> ndmp getenv failure_resilient Failure Resilient: yes OK Completed
415
To retrieve the restore DST data
To retrieve the restore DST data, enter the following:

Backup> ndmp getenv restore_dst
For example:
Backup> ndmp getenv restore_dst Restore DST policies: no OK Completed
To retrieve the recursive restore data
To retrieve the recursive restore data, enter the following:

Backup> ndmp getenv recursive_restore
For example:
Backup> ndmp getenv recursive_restore Recursive restore: yes OK Completed
To retrieve the update dumpdates data
To retrieve the update dumpdates data, enter the following:

Backup> ndmp getenv update_dumpdates
For example:
Backup> ndmp getenv update_dumpdates Update dumpdates: yes OK Completed
To retrieve the send history data
To retrieve the send history data, enter the following:

Backup> ndmp getenv send_history
For example:
Backup> ndmp getenv send_history Send history: no OK Completed
416
To retrieve the NDMP use snapshot data
To retrieve the send history data, enter the following:

Backup> ndmp getenv use_snapshot
For example:
Backup> ndmp getenv use_snapshot Use snapshot: yes OK Completed
To retrieve the NDMP backup method
To retrieve the configured backup method policy, enter the following:

Backup> ndmp getenv backup_method
For example:
Backup> ndmp getenv backup_method Backup Method: fcl OK Completed
To retrieve the masquerade as a third-party policy
To retrieve the configured masquerade as a third-party policy, enter the following:

Backup> ndmp getenv masquerade_as_thirdparty
For example:
Backup> ndmp getenv masquerade_as_thirdparty Masquerade as thirdparty: yes OK Completed
Restoring the default NDMP policies

To restore the NDMP policies to default values
To restore the NDMP policies to default values, enter the following:

Backup> ndmp restoredefaultenv
Configuring backup About backup configurations
417
About backup configurations

Table 13-6 Command
show
Backup configuration commands Definition

Displays the NetBackup configured settings. If the settings were configured while backup and restore services were running, then they may not be currently in use by the FileStore nodes. To display all of the configured settings, first run the backup> stop command, then run the backup> start command. See Configuring backup on page 418.
status
Displays if the NetBackup and the NDMP data server has started or stopped on the FileStore nodes. If the NetBackup and the NDMP data server has currently started and is running, then Backup> status displays any on-going backup or restore jobs. See Configuring the virtual name of NetBackup on page 403. See Configuring backup on page 418.
start
Starts processes that handle backup and restore. You can also change the status of a virtual IP address to online after it has been configured using the Backup> virtual-ip command. This applies to any currently active node in the cluster that handles backup and restore jobs. The Backup> start command does nothing if the backup and restore processes are already running. See Configuring backup on page 418.
stop
Enables the processes that handle backup and restore. You can also change the status of a virtual IP address to offline after it has been configured using the Backup> virtual-ip command. The Backup> stop command does nothing if backup jobs are running that involve FileStore file systems. See Configuring backup on page 418.
418
Configuring backup Configuring backup
Configuring backup
To display NetBackup configurations
To display NetBackup configurations, enter the following:

Backup> show
For example:
Backup> show Virtual name: Virtual IP: NetBackup Master Server: NetBackup EMM Server: NetBackup Media Server(s): Backup Device: Ok Completed
nbuclient.symantec.com 10.10.10.10 nbumaster.symantec.com nbumaster.symantec.com not configured pubeth1
Configuring backup Configuring backup
419
To display the status of backup services
To display the status of backup services, enter the following:

Backup> status
An example of the status command when no backup services are running:

Backup> status Virtual IP state Backup service online node NDMP Server state NetBackup Client state
: : : :
up node_01 running running
No backup/restore jobs running. OK Completed
An example of the status command when the backup jobs that are running involve file systems using NDMP.
: : : :
up node_01 working running
Following filesystems are currently busy in backup/restore jobs by NDMP: myfs1 OK Completed
An example of the status command when the backup jobs that are running involve file systems using the NetBackup client.
: : : :
up node_01 running working
Some filesystems are busy in backup/restore jobs by NetBackup Client OK Completed
420
Configuring backup Configuring backups using NetBackup or other third-party backup applications
To start backup services
To start backup processes, enter the following:

Backup> start [nodename]
where the optional nodename specifies the node where backup services are started. For example:
Backup> start OK Completed
To stop backup services
To stop backup services, enter the following:

Backup> stop
For example:
Backup> stop SFS backup ERROR V-288-0 Cannot stop, some backup jobs are running.
Configuring backups using NetBackup or other third-party backup applications

You can backup FileStore using the Symantec NetBackup 7.0.1 client capability, or other third-party backup applications that use the standard NFS mount to backup over the network. The FileStore ISO image includes the Symantec Netbackup 7.0.1 FileStore client code. For information about the Symantec NetBackup 7.0.1 client capability, refer to the Symantec NetBackup 7.0.1 product documentation set. The Backup> netbackup commands configure the local NetBackup installation of FileStore to use an external NetBackup master server, Enterprise Media Manager (EMM) server, or media server. When NetBackup is installed on FileStore, it acts as a NetBackup client to perform IP-based backups of FileStore file systems. Note: A new public IP address, not an IP address that is currently used, is required for configuring the NetBackup client. Use the Backup> virtual-ip and Backup> virtual-name commands to configure the NetBackup client.
Chapter
14
Configuring Symantec FileStore Dynamic Storage Tiering


About FileStore Dynamic Storage Tiering (DST) How FileStore uses Dynamic Storage Tiering About policies About adding tiers to file systems Adding tiers to a file system Removing a tier from a file system About configuring a mirror on the tier of a file system Configuring a mirror to a tier of a file system Listing all of the files on the specified tier Displaying a list of DST file systems Displaying the tier location of a specified file About configuring the policy of each tiered file system Configuring the policy of each tiered file system Relocating a file or directory of a tiered file system About configuring schedules for all tiered file systems
422
Configuring Symantec FileStore Dynamic Storage Tiering About FileStore Dynamic Storage Tiering (DST)
Configuring schedules for all tiered file systems Displaying files that will be moved and/or pruned by running a policy Allowing metadata information on the file system to be written on the secondary tier Restricting metadata information to the primary tier only
About FileStore Dynamic Storage Tiering (DST)

The FileStore Dynamic Storage Tiering (DST) feature makes it possible to allocate two tiers of storage to a file system. The following features are part of the FileStore Dynamic Storage Tiering Solution:
Relocate files between primary and secondary tiers automatically as files age and become less business critical. Prune files on secondary tiers automatically as files age and are no longer needed. Promote files from a secondary storage tier to a primary storage tier based on I/O temperature. Retain original file access paths to eliminate operational disruption, for applications, backup procedures, and other custom scripts. Allow you to manually move folders/files and other data between storage tiers. Enforce policies that automatically scan the file system and relocate files that match the appropriate tiering policy.
In FileStore, there are two predefined tiers for storage:

Current active tier 1 (primary) storage. Tier 2 (secondary) storage for aged or older data.
To configure FileStore DST, add tier 2 (secondary) storage to the configuration. Specify where the archival storage will reside (storage pool) and the total size. Files can be moved from the active storage after they have aged for a specified number of days, depending on the policy selected. The number of days for files to age (not accessed) before relocation can be changed at any time. Note: An aged file is a file that exists without being accessed. Figure 14-1 depicts the features of FileStore and how it maintains application transparency.
423
Figure 14-1
Dynamic Storage Tiering

/one-file-system
/sales
/financial /sales
/development /sales
/current
/forecast
/current /2007
/forecast /2008
/current /new
/forecast /history
storage
Primary Tier
Secondary Tier
mirrored RAID5
If you are familiar with Veritas Volume Manager (VxVM), every FileStore file system is a multi-volume file system (one file system resides on two volumes). The DST tiers are predefined to simplify the interface. When an administrator wants to add storage tiering, a second volume is added to the volume set, and the existing file system is encapsulated around all of the volumes in the file system. This chapter discusses the FileStore storage commands. You use these commands to configure tiers on your file systems. The Storage commands are defined in Table 14-1. You log into the administrative console (for master, system-admin, or storage-admin) and enter Storage> mode to access the commands.
424
See About using the FileStore command-line interface on page 33. Table 14-1 Command
tier add

Adds different types of storage tier to the file system. See About adding tiers to file systems on page 426.
tier remove
Removes a tier from a file system. See Removing a tier from a file system on page 428.
tier addmirror
Adds a mirror to a tier of a file system. See About configuring a mirror on the tier of a file system on page 429.
tier rmmirror
Removes a mirror from a tier of a file system. See About configuring a mirror on the tier of a file system on page 429.
tier listfiles
Lists all of the files on the specified tier. See Listing all of the files on the specified tier on page 431.
tier mapfile
Displays the tier location of a specified file. See Displaying the tier location of a specified file on page 432.
tier policy
Configures the policy of each tiered file system. See About configuring the policy of each tiered file system on page 432.
tier relocate
Relocates a file or directory. See Relocating a file or directory of a tiered file system on page 438.
tier schedule
Creates schedules for all tiered file systems. See About configuring schedules for all tiered file systems on page 438.
tier query
Displays a list of files that will be moved and/or pruned by running a policy. See Displaying files that will be moved and/or pruned by running a policy on page 440.
Configuring Symantec FileStore Dynamic Storage Tiering How FileStore uses Dynamic Storage Tiering
425
Table 14-1 Command
tier allowmetadata Allows the metadata information on the file system to be written on yes the secondary tier. See Allowing metadata information on the file system to be written on the secondary tier on page 441. tier allowmetadata Restricts the metadata information to the primary tier only. no See Restricting metadata information to the primary tier only on page 442.
How FileStore uses Dynamic Storage Tiering

FileStore provides two types of tiers:

Primary tier Secondary tier
Each newly created file system has only one primary tier initially. This tier cannot be removed. For example, the following operations are applied to the primary tier:
Storage> fs addmirror Storage> fs growto Storage> fs shrinkto
The Storage> tier commands manage file system DST tiers. All Storage> tier commands take a file system name as an argument and perform operations on the combined construct of that file system. The FileStore file system default is to have a single storage tier. An additional storage tier can be added to enable storage tiering. A file system can only support a maximum of two storage tiers.
Storage> tier commands can be used to perform the following:

Adding/removing/modifying the secondary tier Setting policies Scheduling policies Locating tier locations of files
426
Configuring Symantec FileStore Dynamic Storage Tiering About policies
Listing files that are located on the primary or secondary tier Moving files from the secondary tier to the primary tier Allowing metadata information on the file system to be written on the secondary tier Restricting metadata information to the primary tier only
About policies
Each tier can be assigned a policy. The policies include:

Specify on which tier (primary or secondary) the new files get created. Relocate files from the primary tier to the secondary tier based on any number of days of inactivity of a file. Relocate files from the secondary tier to the primary tier based on the Access Temperature of the file. Prune files on the secondary tier based on any number of days of inactivity of a file.
About adding tiers to file systems

You can add different types of tiers to file systems. Table 14-2 Command
tier add simple
Tier add commands Definition

Adds a second tier to a file system. The storage type of the second tier is independent of the protection level of the first tier. See Adding tiers to a file system on page 427.
tier add mirrored
Adds a mirrored second tier to a file system. See Adding tiers to a file system on page 427.
tier add striped
Adds a striped second tier to a file system. See Adding tiers to a file system on page 427.
tier add mirrored-stripe
Adds a mirrored-striped second tier to a file system. See Adding tiers to a file system on page 427.
Configuring Symantec FileStore Dynamic Storage Tiering Adding tiers to a file system
427
Table 14-2 Command

tier add striped-mirror
Tier add commands (continued) Definition

Adds a striped-mirror second tier to a file system. See Adding tiers to a file system on page 427.
Adding tiers to a file system

To add a second tier to a file system
To add a tier to a file system where the volume layout is "simple" (concatenated), enter the following:
Storage> tier add simple fs_name size pool1[,disk1,...]
To add a mirrored tier to a file system
To add a mirrored tier to a file system, enter the following:

Storage> tier add mirrored fs_name size nmirrors pool1[,disk1,...] [protection=disk|pool]
For example:
Storage> tier add mirrored fs1 100M 2 pool3,pool4 100% [#] Creating mirrored secondary tier of filesystem
To add a striped tier to a file system
To add a striped tier to a file system, enter the following:

Storage> tier add striped fs_name size ncolumns pool1[,disk1,...] [stripeunit=kilobytes]
To add a mirrored-striped tier to a file system
To add a mirrored-striped tier to a file system, enter the following:

Storage> tier add mirrored-stripe fs_name size nmirrors ncolumns pool1[,disk1,...] [protection=disk|pool] [stripeunit=kilobytes]
To add a striped-mirror tier to a file system
To add a striped-mirror tier to a file system, enter the following:
428
Configuring Symantec FileStore Dynamic Storage Tiering Removing a tier from a file system
Storage> tier add striped-mirror fs_name size nmirrors ncolumns pool1[,disk1,...] [protection=disk|pool] [stripeunit=kilobytes] fs_name Specifies the name of the file system to which the mirrored tier will be added. If the specified file system does not exist, an error message is displayed. Specifies the size of the tier to be added to the file system, for example, 10m, 10M, 25g, 100G. Specifies the numbers of columns to add to the striped tiered file system. Specifies the number of mirrors to be added to the tier for the specified file system. Specifies the pool(s) or disk(s) that will be used for the specified tiered file system. If the specified pool or disk does not exist, an error message is displayed. You can specify more than one pool or disk by separating the pool or disk name with a comma, but do not include a space between the comma and the name. The disk needs to be part of the pool or an error message is displayed. protection If no protection level is specified, disk is the default protection level. The protection level of the second tier is independent of the protection level of the first tier. Available options are: disk - If disk is entered for the protection field, then mirrors will be created on separate disks. The disks may or may not be in the same pool. pool - If pool is entered for the protection field, then mirrors will be created in separate pools. If not enough space is available, then the file system will not be created.
size
ncolumns
nmirrors
pool1[,disk1,...]
stripeunit=kilobytes Specifies a stripe width of either 128K, 256k, 512K, 1M, or 2M. The default stripe width is 512K.
Removing a tier from a file system

The Storage> tier remove command removes a tier from the file system and releases the storage used by the file system back to the storage pool. This command
Configuring Symantec FileStore Dynamic Storage Tiering About configuring a mirror on the tier of a file system
429
requires that the file system be online, and that no data resides on the secondary tier. If the storage tier to be removed contains any data residing on it, then the tier cannot be removed from the file system. To remove a tier from a file system
To remove a tier from a file system, enter the following:

Storage> tier remove fs_name
where fs_name specifies the name of the tiered file system that you want to remove. For example:
Storage> tier remove fs1
About configuring a mirror on the tier of a file system

These commands add or remove mirrors to the tier of the file system. Table 14-3 Command
tier addmirror
Tier mirror commands Definition

Adds a mirror to a tier of a file system. See Configuring a mirror to a tier of a file system on page 429.
tier rmmirror
Removes a mirror from a tier of a file system.
Note: For a striped-mirror file system, if any of the disks are bad, this
command disables the mirrors from the tiered file system for which the disks have failed. If no disks have failed, FileStore chooses a mirror to remove from the tiered file system. See Configuring a mirror to a tier of a file system on page 429.
Configuring a mirror to a tier of a file system

To add a mirror to a tier of a file system
To add a mirror to a tier of a file system, enter the following:

Storage> tier addmirror fs_name pool1[,disk1,...] [protection=disk|pool]
430
Configuring Symantec FileStore Dynamic Storage Tiering Configuring a mirror to a tier of a file system
fs_name
Specifies the file system to which the a mirror will be added. If the specified file system does not exist, an error message is displayed. Specifies the pool(s) or disk(s) that will be used as a mirror for the specified tiered file system. You can specify more than one pool or disk by separating the name with a comma. But do not include a space between the comma and the name. The disk needs to be part of the pool or an error message is displayed.
pool1[,disk1,...]
protection
If no protection level is specified, disk is the default protection level. Available options are: disk - If disk is entered for the protection field, then mirrors will be created on separate disks. The disks may or may not be in the same pool. pool - If pool is entered for the protection field, then mirrors will be created in separate pools. If not enough space is available, then the file system will not be created.
For example:
Storage> tier addmirror fs1 pool5 100% [#] Adding mirror to secondary tier of filesystem
To remove a mirror from a tier of a file system
To remove a mirror from a tier of a file system, enter the following:

Storage> tier rmmirror fs_name
where fs_name specifies the name of the tiered file system from which you want to remove a mirror. For example:
Storage> tier rmmirror fs1
This command provides another level of detail for the remove mirror operation. You can use the command to specify which mirror you want to remove by specifying the pool name or disk name. The disk must be part of a specified pool.
Configuring Symantec FileStore Dynamic Storage Tiering Listing all of the files on the specified tier
431
To remove a mirror from a tier spanning a specified pool or disk
To remove a mirror from a tier that spans a specified pool or disk, enter the following:
Storage> tier rmmirror fs_name [pool_or_disk_name] fs_name Specifies the name of the file system from which to remove a mirror. If the specified file system does not exist, an error message is displayed.
pool_or disk_name Specifies the pool or disk from which the mirror of the tiered file system spans.
The syntax for the Storage> tier rmmirror command is the same for both pool and disk. If you try to remove a mirror using Storage> fs rmmirror fs1 abc, FileStore first checks for the pool with the name abc, then FileStore removes the mirror spanning on that pool. If there is no pool with the name abc, then FileStore removes the mirror that is on the abc disk. If there is no disk with the name abc, then an error message is displayed.
Listing all of the files on the specified tier

You can list all of the files that reside on either the primary tier or the secondary tier. Note: If the tier contains a large number of files, it may take some time before the output of this command is displayed. To list all of the files on the specified tier
To list all of the files on the specified tier, enter the following:
Storage> tier listfiles fs_name {primary|secondary}
where fs_name indicates the name of the tiered file system from which you want to list the files. You can specify to list files from either the primary or secondary tier. For example:
Storage> tier listfiles fs1 secondary
432
Configuring Symantec FileStore Dynamic Storage Tiering Displaying a list of DST file systems
Displaying a list of DST file systems

You can display a list of DST file systems using the Storage> fs list command. See Listing all file systems and associated information on page 191.
Displaying the tier location of a specified file

To display the tier location of a specified file
To display the tier location of a specified file, enter the following:

Storage> tier mapfile fs_name file_path fs_name Specifies the name of the file system for which the specified file on the tiered file system resides. If the specified file system does not exist, an error message is displayed. Specifies the tier location of the specified file. The path of the file is relative to the file system.
file_path
For example, to show the location of a.txt, which is in the root directory of the fs1 file system, enter the following:
tier mapfile fs1 /a.txt Tier Extent Type ==== =========== Primary Data
File Offset =========== 0 Bytes
Extent Size =========== 1.00 KB
About configuring the policy of each tiered file system

You can configure the policy of each tiered file system. Table 14-4 Command
tier policy list
Tier policy commands Definition

Displays the policy for each tiered file system. You can have one policy for each tiered file system. See Configuring the policy of each tiered file system on page 434.
Configuring Symantec FileStore Dynamic Storage Tiering About configuring the policy of each tiered file system
433
Table 14-4 Command

tier policy modify
Tier policy commands (continued) Definition

Modifies the policy of a tiered file system. The new files are created on the primary tier. If a file has not been accessed for more than seven days, the files are moved from the primary tier to the secondary tier. If the access temperature of the files in the secondary tier is more than five, these files are moved from the secondary tier to the primary tier. The access temperature is calculated over a 3-day period. See Configuring the policy of each tiered file system on page 434.
tier policy prune
Specifies the prune policy of a tiered file system. Once files have aged on the secondary tier, the prune policy can be set up to delete those aged files automatically. There are three sub-commands under this command:

tier policy prune list tier policy prune modify tier policy prune remove
See Configuring the policy of each tiered file system on page 434. tier policy run Runs the policy of a tiered file system. See Configuring the policy of each tiered file system on page 434. tier policy remove Removes the policy of a tiered file system. See Configuring the policy of each tiered file system on page 434.
434
Configuring Symantec FileStore Dynamic Storage Tiering Configuring the policy of each tiered file system
Configuring the policy of each tiered file system

To display the policy of each tiered file system
To display the policy of each tiered file system, enter the following:
Storage> tier policy list
For example:
Storage> tier policy list FS Create on Days MinAccess Temp == ========= ==== ============== fs1 primary 2 3
PERIOD ====== 4
Each tier can be assigned a policy. A policy assigned to a file system has three parts:
file creation inactive files Specifies on which tier the new files are created. Indicates when a file has to be moved from the primary tier to the secondary tier. For example, if the days option of the tier is set to 10, and if a file has not been accessed for more than 10 days, then it is moved from the primary tier of the file system to the secondary tier. Measures the number of I/O requests to the file during the period designated by the period. In other words, it is the number of read or write requests made to a file over a specified number of 24-hour periods divided by the number of periods. If the access temperature of a file exceeds minacctemp (where the access temperature is calculated over a period of time previously specified) then this file is moved from the secondary tier to the primary tier.
access temperature
435
To modify the policy of a tiered file system
To modify the policy of a tiered file system, enter the following:

Storage> tier policy modify fs_name {primary|secondary} days minacctemp period fs_name The name of the tiered file system from which you want to modify a policy. Causes new files to be created on the primary or secondary tier. You need to input either primary or secondary. Number of days from which the inactive files move from the primary to the secondary tier. The minimum access temperature value for moving files from the secondary to the primary tier. The number of past days used for calculating the access temperature.
tier
days
minacctemp
period
For example:
Storage> tier policy modify fs1 primary 6 5 3 SFS fs SUCCESS V-288-0 Successfully modifies tiering policy for File system fs1
To display the prune policy of a tiered file system
To display the prune policy of a tiered file system, enter the following:
Storage> tier policy prune list
For example:
Storage> tier policy prune list FS Delete After =============== ============ fs1 200 fs2 disabled
The default prune policy status of a tiered file system is disabled. The delete_after indicates the number of days after which the files can be deleted.
436
To modify the prune policy of a tiered file system
To modify the prune policy of a tiered file system, enter the following:
Storage> tier policy prune modify fs_name delete_after fs_name Name of the tiered file system from which you want to modify the prune policy. Number of days from which the inactive files will be deleted.
delete_after
For example:
Storage> tier policy prune modify fs0 180 You have set the Prune policy to file system , system will automatically delete the inactive files on secondary tier. Do you want to continue with setting the Tier Prune policy? (y/n) Y SFS fs SUCCESS V-288-0 Successfully modified the Prune policy for File system fs0
To remove the prune policy of a tiered file system
To remove the prune policy of a tiered file system, enter the following:
Storage> tier policy prune remove fs_name
where fs_name is the name of the tiered file system from which you want to remove the prune policy. For example:
Storage> tier policy prune remove fs1 SFS fs SUCCESS V-288-0 Successfully removed the Prune policy for File system fs1
437
To run the policy of a tiered file system
To run the policy of a tiered file system, enter the following:

Storage> tier policy run fs_name
where fs_name indicates the name of the tiered file system for which you want to run a policy. For example:
Storage> tier policy run fs1 SFS fs INFO V-288-1221 The command may take some time to execute, pressing CTRL + C, will abort the command. SFS fs SUCCESS V-288-1275 Successfully ran tiering policy for File system fs1
To remove the policy of a tiered file system
To remove the policy of a tiered file system, enter the following:

Storage> tier policy remove fs_name
where fs_name indicates the name of the tiered file system from which you want to remove a policy. For example:
Storage> tier policy remove fs1 SFS fs SUCCESS V-288-0 Successfully removed tiering policy for File system fs1
You can run the policy of a tiered file system, which would be similar to scheduling a job to run your policies, except in this case running the policy is initiated manually. The Storage> tier policy run command moves the older files from the primary tier to the secondary tier, and/or prunes the inactive files on the secondary tier, according to the policy setting.
438
Configuring Symantec FileStore Dynamic Storage Tiering Relocating a file or directory of a tiered file system
Relocating a file or directory of a tiered file system

To relocate a file or directory
To relocate a file or directory, enter the following:

Storage> tier relocate fs_name dirPath fs_name The name of the tiered file system from which you want to relocate a file or directory. The relocation of the file or directory is done from the secondary tier to the primary tier. Enter the relative path of the directory (dirPath) you want to relocate. Or enter the relative path of the file (FilePath) that you want to relocate.
dirPath
About configuring schedules for all tiered file systems

The tier schedule commands display, modify, and remove the tiered file systems. Table 14-5 Command
tier schedule modify tier schedule list
Tier schedule commands Definition

Modifies the schedule of a tiered file system. See Configuring schedules for all tiered file systems on page 439. Displays the schedules for all tiered file systems. You can have one schedule for each tiered file system. You cannot create a schedule for a non-existent or a non-tiered file system. See Configuring schedules for all tiered file systems on page 439.
tier schedule remove
Removes the schedule of a tiered file system. See Configuring schedules for all tiered file systems on page 439.
Configuring Symantec FileStore Dynamic Storage Tiering Configuring schedules for all tiered file systems
439
Configuring schedules for all tiered file systems

To modify the schedule of a tiered file system
To modify the schedule of a tiered file system, enter the following:

Storage> tier schedule modify fs_name minute hour day_of_the_month month day_of_the_week
For example, enter the following:

Storage> tier schedule modify fs1 1 1 1 * * * SFS fs SUCCESS V-288-0 Command 'tier schedule modify' executed successfully for fs1 fs_name Specifies the file system where the schedule of the tiered file system resides. If the specified file system does not exist, an error message is displayed. This parameter may contain either an asterisk, (*), which implies "every minute," or a numeric value between 0-59. You can enter */(0-59), a range such as 23-43, or just the *. hour This parameter may contain either an asterisk, (*), which implies "run every hour," or a number value between 0-23. You can enter */(0-23), a range such as 12-21, or just the *. day_of_the_month This parameter may contain either an asterisk, (*), which implies "run every day of the month," or a number value between 1-31. You can enter */(1-31), a range such ass 3-22, or just the *. month This parameter may contain either an asterisk, (*), which implies "run every month," or a number value between 1-12. You can enter */(1-12), a range such as 1-5, or just the *. You can also enter the first three letters of any month (must use lowercase letters). day_of_the_week This parameter may contain either an asterisk (*), which implies "run every day of the week," or a numeric value between 0-6. Crontab interprets 0 as Sunday. You can also enter the first three letters of the week (must use lowercase letters).
minute
440
Configuring Symantec FileStore Dynamic Storage Tiering Displaying files that will be moved and/or pruned by running a policy
To display schedules for all tiered file systems
To display schedules for all tiered file systems, enter the following:
Storage> tier schedule list [fs_name]
where fs_name indicates the name of the tiered file system for which you want to run a policy. For example:
Storage> tier schedule list FS Minute Hour Day === ====== ==== === fs1 1 1 1
Month ===== *
WeekDay ======= *
To remove the schedule of a tiered file system
To remove the schedule of a tiered file system, enter the following:

Storage> tier schedule remove fs_name
where fs_name is the name of the tiered file system from which you want to remove a schedule. For example:
Storage> tier schedule remove fs1 SFS fs SUCCESS V-288-0 Command tier schedule remove executed successfully for fs1
Displaying files that will be moved and/or pruned by running a policy

You can display the list of files that will be moved and/or pruned by running a policy. This is very useful as a "what if" type of analysis. The command does not physically move any file blocks.
Configuring Symantec FileStore Dynamic Storage Tiering Allowing metadata information on the file system to be written on the secondary tier
441
To display a list of files that will be moved and/or pruned by running a policy
To display a list of files that will be moved and/or pruned by running a policy, enter the following:
Storage> tier query fs_name
where fs_name is the name of the tiered file system for which you want to display a list of files that will be moved and/or pruned by running a policy. For example:
Storage> tier query fs1 Are you sure, this command may take a long time to execute and extensively use the system resources, enter yes/no Continuing with the command, you can press CTRL+C to abort the command Yes /a.txt /b.txt /c.txt /d.txt
Allowing metadata information on the file system to be written on the secondary tier
The Storage> tier allowmetadata yes command allows the metadata information on the specified file system to be written on the secondary tier as well. By default, the secondary tier is not configured for storing metadata information on the file system. Tiers configured with this option show metaOK in the column SECONDARY TIER of the Storage> fs list command output.
442
Configuring Symantec FileStore Dynamic Storage Tiering Restricting metadata information to the primary tier only
To allow metadata information on the file system to be written on the secondary tier
To allow metadata information on the file system to be written on the secondary tier, enter the following:
Storage> tier allowmetadata yes fs_name
where fs_name is the name of the file system where metadata information can be written on the secondary tier. For example:
Storage> tier allowmetadata yes fs1 SFS fs SUCCESS V-288-0 Configured the secondary tier for storing metadata information.
Restricting metadata information to the primary tier only

The Storage> tier allowmetadata no command restricts the metadata information to the primary tier only. If the primary tier gets full, the writes to the secondary tier will not be served as the metadata updates are restricted to the primary tier only. To restrict metadata information to the primary tier only
To restrict metadata information to the primary tier only, enter the following:
Storage> tier allowmetadata no fs_name
where fs_name is the name of the file system where the metadata information is restricted to the primary tier only. For example:
Storage> tier allowmetadata no fs1 SFS fs SUCCESS V-288-0 Configured the secondary tier for storing no metadata information.
Chapter
15
Configuring system information


About system commands About setting the clock commands Setting the clock commands About configuring the locally saved configuration files Configuring the locally saved configuration files Using the more command About coordinating cluster nodes to work with NTP servers Coordinating cluster nodes to work with NTP servers Displaying the system statistics Using the swap command About the option commands Using the option commands
About system commands

The system commands set or show the date and time of the system, and start, stop, or check the status of the NTP server. The system command class also allows you to display cluster-wide performance statistics, swap network interfaces, and enable or disable the more filter on output of the administrative console. It also
444
Configuring system information About setting the clock commands
contains option command displays and configures the tunable parameters. The system commands are listed in Table 15-1. To access the commands, log into the administrative console (for master, system-admin, or storage-admin) and enter the System> mode. See About using the FileStore command-line interface on page 33. Table 15-1 Command
clock
System mode commands Definition

Sets or shows the date and time of the system, including setting time zones and displaying the list of regions. See About setting the clock commands on page 444.
config
Imports or exports the FileStore configuration settings. See About configuring the locally saved configuration files on page 448.
more
Enables, disables, or checks the status of the more filter. See Using the more command on page 453.
ntp
Sets the Network Time Protocol (NTP) server on all of the nodes in the cluster. See About coordinating cluster nodes to work with NTP servers on page 453.
stat
Displays the system, Dynamic Multipathing (DMP), and process-related node wide statistics. See Displaying the system statistics on page 455.
swap
Swaps two network interfaces in a cluster. See Using the swap command on page 456.
option
Adjusts a variety of tunable variables that affect the cluster-wide FileStore settings. See Using the option commands on page 459.
About setting the clock commands

These commands set or show the date and time of the system, including setting time zones and displaying the list of regions.
Configuring system information Setting the clock commands
445
Table 15-2 Command

clock show
Clock commands Definition

Displays the current system date and time. See Setting the clock commands on page 445.
clock set
Sets the system date and time. See Setting the clock commands on page 445.
clock timezone
Sets the time zone for the system.
Note: This command only accepts the name of a city or GMT

(Greenwich Mean Time). See Setting the clock commands on page 445. clock regions Sets the region for the system. See Setting the clock commands on page 445.
Setting the clock commands

To display the current date and time of the system
To display the current system date and time, enter the following:
System> clock show
For example:
System> clock show Fri Feb 20 12:16:30 PST 2009
446
To set the system date and time
To set the system date and time, enter the following:

System> clock set time day month year time HH:MM:SS using a 24-hour clock Pacific Daylight Time (PDT) is the time zone used for the system. Greenwich Mean Time (GMT) is the time zone used for the BIOS. day month 1..31 January, February, March, April, May, June, July, August, September, October, November, December YYYY
year
For example:
System> clock set 12:00:00 17 July 2009 .Done. Fri Jul 17 12:00:00 PDT 2009
447
To set the time zone and region for the system
To set the time zone for the system, enter the following:
System> clock timezone timezone
To reset the time zone on your system, enter the following:

System> clock timezone region
The system will reset to the time zone for that specific region. For example:
System> clock show Thu Apr 3 09:40:26 PDT 2008 System> clock timezone GMT Setting time zone to: GMT ..Done. Thu Apr 3 16:40:37 GMT 2008 System> clock show Thu Apr 3 16:40:47 GMT 2008 System> clock timezone Los_Angeles Setting time zone to: Los_Angeles ..Done. Thu Apr 3 09:41:06 PDT 2008
System> clock show Thu Apr 3 09:41:13 PDT 2008
To display the region for the system
To display the region for the system, enter the following:

System> clock regions [region]
448
Configuring system information About configuring the locally saved configuration files
region
Specifies the region for the system. Valid values include:

Africa America Asia Australia Canada Europe GMT-offset - (this includes GMT, GMT +1, GMT +2) Pacific US
For example:
System> clock regions US
The software responds with the areas included in the US region.

System> clock regions US Alaska Aleutian Arizona Central East-Indiana Eastern Hawaii Indiana-Starke Michigan Mountain Pacific Samoa
About configuring the locally saved configuration files

Table 15-3 Command
config list
Configuration commands Definition

Views locally saved configuration files. See Configuring the locally saved configuration files on page 449.
Configuring system information Configuring the locally saved configuration files
449
Table 15-3 Command
Configuration commands (continued) Definition
config export local Exports configuration settings locally. See Configuring the locally saved configuration files on page 449. config export remote Exports configuration settings remotely. See Configuring the locally saved configuration files on page 449.
config import local Imports configuration settings locally.
Warning: Running the system> config import command

overwrites all of your existing configuration settings except cluster name. See Configuring the locally saved configuration files on page 449. config import remote Imports configuration settings remotely.
Warning: Running the system> config import command

overwrites all of your existing configuration settings except cluster name. See Configuring the locally saved configuration files on page 449.
config delete
Deletes the locally saved configuration file. See Configuring the locally saved configuration files on page 449.
Configuring the locally saved configuration files

To list configuration settings
To view locally saved configuration files, enter the following:

System> config list
450
To export configuration settings either locally or remotely
To export configuration settings locally, enter the following:

System> config export local file_name
For example:
System> config export local 2007_July_20
To export configuration settings remotely, enter the following:

System> config export remote URL
For example:
System> config export remote ftp://admin@ftp.docserver.symantec.com/configs/config1.tar.gz Password: ******* file_name URL Specifies the saved configuration file. Specifies the URL of the export file (supported protocols are FTP and SCP).
To import configuration settings either locally or remotely
To import configuration settings locally, enter the following:

file_name Specifies the name of the configuration file to be imported saved in a local file. Specifies the type of configuration to import. This is an optional parameter. If config_type is left blank, config_type defaults to all. System> config import local file_name [config_type] {network|admin|all|report|system|cluster_specific| all_except_cluster_specific|nfs|cifs|ftp|http|backup|replication| storage_schedules|antivirus}
config_type
For example:
System> config import local 2007_July_20 network Backup of current configuration was saved as 200907150515 network configuration was imported Configuration files are replicated to all the nodes
451
where 200907150515 is the date (20090715 = July 15, 2009) and the time (0515 = hour 5 and 15 minutes). To import configuration settings remotely, enter the following:
System> config import remote URL [config_type] {network|admin|all|report|system|cluster_specific| all_except_cluster_specific|nfs|cifs|ftp|http|backup|replication| storage_schedules|antivirus}
For example:
System> config import remote ftp://user1@server.com/home/user1/ 2008_July_20.tar.gz report Password: ******* file_name URL Specifies the saved configuration file. Specifies the saved configuration at a remote machine specified by a URL.
452
config_type
Specifies the type of configuration to import. This is an optional parameter. If config_type is left blank, config_type defaults to all. Available import configuration options are: network - Imports DNS, LDAP, NIS, nsswitch settings (does not include IP). admin - Imports list of users, passwords. This includes cifs local users and groups. all - Imports all configuration information.

report - Imports report settings. system - Imports NTP settings.
cluster_specific - Imports public IP addresses, virtual IP addresses, and console IP addresses. Be careful before using this import option. The network connection to the console server will be lost after performing an import. You need to reconnect to the console server after importing the configuration option. all_except_cluster_specific - Imports all configuration information except for cluster-specific information. nfs - Imports NFS settings.
cifs - Imports CIFS settings.
Note: To import cifs local users and groups you have to

import the admin the module also.

ftp - Imports the FTP setting. http - Imports HTTP settings.
backup - Imports the NBU client and NDMP configuration, excluding the virtual-name and virtual-ip. replication - Imports replication settings. storage_schedules - Imports dynamic storage tiering (DST) and automated snapshot schedules. antivirus - Imports antivirus settings.
You can import the configuration settings saved in a local file or saved to a remote machine specified by a URL. To delete the locally saved configuration file
To delete the locally saved configuration file, enter the following:

System> config delete file_name
file_name specifies the locally saved configuration file for which to delete.
Configuring system information Using the more command
453
Using the more command

The System> more command enables, disables, or checks the status of the more filter. The default setting is enable, which lets you page through the text one screen at a time. To modify and view the more filter setting
To modify and view the more filter setting, enter the following:
System> more enable|disable|status enable disable status Enables the more filter on all of the nodes in the cluster. Disables the more filter on all of the nodes in the cluster. Displays the status of the more filter.
For example:
System> more status Status : Enabled System> more disable SFS more Success V-288-748 more deactivated on console System> more enable SFS more Success V-288-751 more activated on console
About coordinating cluster nodes to work with NTP servers

You can set the Network Time Protocol (NTP) server on all of the nodes in the cluster. Table 15-4 Command
ntp servername
NTP commands Definition

Sets the NTP server on all of the nodes in the cluster. See Coordinating cluster nodes to work with NTP servers on page 454.
ntp show
Displays NTP status and server name. See Coordinating cluster nodes to work with NTP servers on page 454.
454
Configuring system information Coordinating cluster nodes to work with NTP servers
Table 15-4 Command

ntp enable
NTP commands (continued) Definition

Enables the NTP server on all of the nodes in the cluster. See Coordinating cluster nodes to work with NTP servers on page 454.
ntp disable
Disables the NTP server on all of the nodes in the cluster. See Coordinating cluster nodes to work with NTP servers on page 454.
Coordinating cluster nodes to work with NTP servers

To set the NTP server on all of the nodes in the cluster
To set the NTP server on all of the nodes in the cluster, enter the following:
System> ntp servername server-name
where server-name specifies the name of the server or IP address you want to set. For example:
System> ntp servername ntp.symantec.com Setting NTP server = ntp.symantec.com ..Done.
Use 127.127.1.0 as the IP address for selecting the local clock as the time source for the NTP server. To display the status of the NTP server
To display NTP status and server name, enter the following:

System> ntp show
Example output:
System> ntp show Status: Enabled Server Name: ntp.symantec.com
Configuring system information Displaying the system statistics
455
To enable the NTP server
To enable the NTP server on all of the nodes in the cluster, enter the following:
System> ntp enable
For example:
System> ntp enable Enabling ntp server: ntp.symantec.com ..Done.
To disable the NTP server
To disable the NTP server on all of the nodes in the cluster, enter the following:
System> ntp disable
For example:
System> ntp disable Disabling ntp server:..Done. System> ntp show Status : Disabled Server Name: ntp.symantec.com
Displaying the system statistics

The System> stat command displays the system, Dynamic Multipathing (DMP), and process-related node-wide statistics. The load in the displayed output is the load from the last 1, 5, and 15 minutes.
456
Configuring system information Using the swap command
To display the system statistics
To display cluster wide or node wide statistics, enter the following:

System> stat sys|dmp|all|cluster [node] sys dmp cluster Displays the system-related statistics. Displays the DMP-related statistics. Displays the aggregate of the I/O and network performances from each node and averages out the number of nodes in the cluster to show the statistics at the cluster level. The variable node does not apply to this option. Displays the system and DMP-related statistics of one node at a time in the cluster or all of the nodes in the cluster. The name of the node in the cluster.
all
node
To view the cluster-wide network and I/O throughput, enter the following:
System> stat cluster Gathering statistics... Cluster wide statistics:::: ======================================= IO throughput :: 0 Network throughput :: 1.205
Using the swap command

If you set up a single-node cluster, and you were not able to ping the gateway through the private or public interface, then the cables may have been attached incorrectly. To correct this problem, you first need to switch the cables back to the correct connectors. You then need to run the System> swap command. For example, if the public switch is 'priveth0' and the private switch is 'pubeth0,' the System> swap command switches the MAC addresses for 'priveth0' and 'pubeth0.' After running the System> swap command, all Secure Shell (SSH) connections hosted on the input interfaces will terminate. You can check the status of the System> swap command using the history command. The System> swap command works only on a single-node cluster. No other service should be running.
Configuring system information About the option commands
457
Note: Do not use this command if you have exported CIFS/NFS shares. To use the swap command
To use the System> swap command, enter the following:

System> swap interface1 interface2
For example:
System> swap pubeth0 priveth0 All ssh connection(s) need to start again after this command. Do you want to continue [Enter "y/yes" to continue]... Check status of this command in history. Wait.......
About the option commands

The option commands were created to allow you to adjust a variety of tunable variables that affect the global FileStore settings. The tunable variables that can be changed or displayed are listed in Table 15-5. Note: Only system administrators with advanced knowledge of Dynamic Multipathing (DMP) I/O policies should use the DMP-related commands under the System> option. For assistance, contact Symantec Technical Support. Table 15-5 Command
option show nfsd
Option commands Definition

Displays the number of Network File System (NFS) daemons for each node in the cluster. See Using the option commands on page 459.
option modify nfsd Modifies the number of Network File System (NFS) daemons on all of the nodes in the cluster. The range for the number of daemons you can modify is 1 to 512.
Warning: The option modify nfsd command overwrites the

existing configuration settings. See Using the option commands on page 459.
458
Configuring system information About the option commands
Table 15-5 Command
Option commands (continued) Definition
option show dmpio Displays the type of Dynamic Multipathing (DMP) I/O policy corresponding to enclosure, arrayname, and arraytype for each node in a cluster. See Using the option commands on page 459. option modify dmpio Modifies the Dynamic Multipathing (DMP) I/O policy, corresponding to the enclosure, arrayname, and arraytype.
Warning: Check the sequence before modifying the I/O policy. The
policies need to be applied in following sequence: arraytype, arrayname, and enclosure. The enclosure-based modification of the I/O policy overwrites the I/O policy set using the arrayname and the arraytype for that particular enclosure. In turn, the arrayname-based modification of the I/O policy overwrites the I/O policy set using the arraytype for that particular arrayname. See Using the option commands on page 459. option reset dmpio Resets the Dynamic Multipathing (DMP) I/O policy setting for the given input (enclosure, arrayname, and arraytype). Use this command when you want to change the I/O policy from the previously set enclosure to arrayname. The settings hierarchy is enclosure, arrayname, and arraytype, so to modify the I/O policy to arraytype, you need to reset arrayname and enclosure.
Note: This command does not set the default I/O policy.
See Using the option commands on page 459. option show ninodes option modify ninodes Displays the ninodes cache size in the cluster. See Using the option commands on page 459. Changes the cache size of the global inodes. If your system is caching a large number of metadata transactions, or if there is significant virtual memory manager usage, tuning this parameter may improve performance. The range for the inode cache size is from 10000 to 2097151.
Warning: The option modify ninodes command requires a

cluster-wide reboot. See Using the option commands on page 459. option show tunefstab Displays the global value of the write_throttle parameter. See Using the option commands on page 459.
Configuring system information Using the option commands
459
Table 15-5 Command

option modify tunefstab
Option commands (continued) Definition

Modifies the global write_throttle parameter for all the mounted file systems. The write_throttle parameter is useful in situations where a computer system combines a large amount of memory and slow storage devices. In this configuration, sync operations (such as fsync()) may take so long to complete that a system appears to hang. This behavior occurs because the file system is creating dirty buffers (in-memory updates) faster than they can be asynchronously flushed to disk without slowing system performance. Lowering the value of write_throttle limits the number of dirty buffers per file that a file system generates before flushing the buffers to disk. After the number of dirty buffers for a file reaches the write_throttle threshold, the file system starts flushing buffers to disk even if free memory is available. The default value of write_throttle is zero, which puts no limit on the number of dirty buffers per file. See Using the option commands on page 459.
option show dmptune option modify dmptune
Displays the value of the dmptune attribute. See Using the option commands on page 459. Modifies the value for either the dmp_path_age or the dmp_health_time attributes. See Using the option commands on page 459.
Using the option commands

To display the NFS daemons
To display the number of NFS daemons, enter the following:

System> option show nfsd
For example:
System> option show nfsd NODENAME NUMBER_DAEMONS --------------------sfs_01 96 sfs_02 96
460
To change the NFS daemons
To change the number of NFS daemons, enter the following:

System> option modify nfsd number [nodename]
For example:
System> option modify nfsd 97
To display the DMP I/O policy
To display the dmpio policy, enter the following:

System> option show dmpio
For example:
NODENAME --------sfs_01 sfs_01
TYPE --------arrayname enclosure
ENCLR/ARRAY ----------disk disk
IOPOLICY -------balanced minimumq
If you want to view your current enclosure names, use the following command:
Storage> disk list detail
For example:
Storage> Disk ===== sda_01 disk list detail Pool Enclosure ==== ========== p1 OTHER_DISKS
Size ==== 10.00G Serial Number ============= -
ID == VMware%2C:VMware%20Virtual%20S:0:0
461
To change the DMP I/O policy
To change the DMP I/O policy, enter the following:

System> option modify dmpio {enclosure enclr_name|arrayname array_name|arraytype {A/A|A/P|...}} iopolicy={adaptive|adaptiveminq|balanced|minimumq|priority| round-robin|singleactive}
The dmpio policy variables are the following:

enclosure enclr_name Name of the enclosure to distinguish between arrays having the same array name. Name of the array. Two physical array boxes of the same make will have the same array name. A multipathing type of array. Use one of the following: active-active, active-active-A, active-active-A-HDS, active-active-A-HP, APdisk, active-passive, active-passive-C, active-passiveF-VERITAS, active-passiveF-T3PLUS, active-passiveF-LSI, active-passiveG, active-passiveG-C, Disk, CLR-A-P, CLR-A-PF
arrayname
array_name
arraytype
array_type
462
iopolicy
adaptive
In storage area network (SAN) environments, this option determines the paths that have the least delays, and schedules the I/O on paths that are expected to carry a higher load. Priorities are assigned to the paths in proportion to the delay.
adaptiveminq The I/O is scheduled according to the length of the I/O queue on each path. The path with the shortest queue is assigned the highest priority. balanced Takes into consideration the track cache when balancing the I/O across paths. Uses a minimum I/O queue policy. The I/O is sent on paths that have the minimum number of I/O requests in the queue. This policy is suitable for low-end disks or JBODs where a significant track cache does not exist. This is the default policy for Active/Active (A/A) arrays. Assigns the path with the highest load carrying capacity as the priority path. This policy is useful when the paths in a SAN have unequal performances, and you want to enforce load balancing manually. Sets a simple round-robin policy for the I/O. This is the default policy for Active/Passive (A/P) and Asynchronous Active/Active (A/A-A) arrays. The I/O is channeled through the single active path.
minimumq
priority
round-robin
singleactive
To reset the DMP I/O policy
To reset the DMP I/O policy, enter the following:

System> option reset dmpio {enclosure enclr_name|arrayname array_name|arraytype {A/A|A/P|...}}
To display the ninodes cache size
To display the ninodes cache size, enter the following:

System> option show ninodes
For example:
System> option show ninodes INODE_CACHE_SIZE ---------------2000343
463
To change the ninodes cache size
To change the ninodes cache size, enter the following:

System> option modify ninodes number
For example:
System> option modify ninodes 2000343 SFS option WARNING V-288-0 This will require cluster wide reboot. Do you want to continue (y/n)?
To display the tunefstab parameter
To display the tunefstab parameter, enter the following:

System> option show tunefstab
For example:
System> option NODENAME -------sfs_01 show tunefstab ATTRIBUTE --------write_throttle
VALUE ----0
To modify the tunefstab parameter
To modify the tunefstab parameter, enter the following:

System> option modify tunefstab write_throttle value
where value is the number you are assigning to the write_throttle parameter. For example:
System> option System> option NODENAME -------sfs_01 sfs_02 modify tunefstab write_throttle 20003 show tunefstab ATTRIBUTE VALUE ------------write_throttle 20003 write_throttle 20003
464
To display the value of the dmptune attribute
To display the value of the dmptune attribute, enter the following:

System> option show dmptune
For example:
System> option show dmptune NODENAME ATTRIBUTE ---------------sfs_01 dmp_path_age sfs_01 dmp_health_time
VALUE ----57 44
To modify the value of the dmp_path_age and dmp_health_time attributes
To modify the value of the dmp_path_age and dmp_health_time attributes, enter the following:
System> option modify dmptune {dmp_path_age value | dmp_health_time value} dmp_path_age value Modify the value of dmp_health_time. This attribute sets the time in seconds for which a path must stay healthy. If a paths state changes back from enabled to disabled within this time period, DMP marks the path as intermittently failing, and does not re-enable the path for I/O until dmp_path_age seconds elapse. The default value of dmp_health_time is 60 seconds. A value of 0 prevents DMP from detecting intermittently failing paths. Sets the time in seconds for which a path must stay healthy. If a path's state changes back from enabled to disabled within this time period, DMP marks the path as intermittently failing, and DMP does not re-enable the path for I/O until the dmp_path_age seconds have elapsed. The default value of dmp_health_time is 60 seconds. A value of 0 prevents DMP from detecting intermittently failing paths.
dmp_health_time value
For example:
System> option modify dmptune dmp_path_age 40 System> option modify dmptune dmp_health_time 50
Chapter
16
Upgrading Symantec FileStore


About upgrading patches or drivers Displaying the current version of FileStore About installing patches About types of patches Installing patches Uninstalling patches Synchronizing software upgrades on a node Uninstalling driver updates
About upgrading patches or drivers

The upgrade commands install or uninstall upgrades to the FileStore software. The upgrades can be patches or drivers. The software is installed or uninstalled on all of the nodes. The upgrade commands are defined in Table 16-1. To access the commands, log into the administrative console (for master, system-admin, or storage-admin) and enter the Upgrade> mode. See About using the FileStore command-line interface on page 33.
466
Upgrading Symantec FileStore About upgrading patches or drivers
Note: The Upgrade> patch install command can also be used for DUD upgrades in case the new node you want to add into the cluster has a separate set of driver requirements compared to the first node.
Note: To avoid potential upgrade issues, stop all workloads from clients, and then re-initiate the upgrade. Table 16-1 Command
show
Upgrade mode commands Definition

Displays the current version of FileStore, the patch level, and the DUD upgrade(s). The Upgrade> show detail command displays information about major upgrades. Error messages are displayed if any of the nodes in the cluster do not have matching software versions, operating system packages installed, or any DUD upgrade(s) installed. See Displaying the current version of FileStore on page 467.
patch install
Downloads the patch from the specified URL and installs it on all of the nodes. See About installing patches on page 468.
patch uninstall-upto
Uninstalls the software upgrade from all of the nodes up to the specified version. See About installing patches on page 468.
patch sync
Synchronizes the specified node. See About installing patches on page 468.
patch duduninstall Removes all of the driver updates previously added to the cluster and reverts back to the original driver update image. See About installing patches on page 468.
Upgrading Symantec FileStore Displaying the current version of FileStore
467
Displaying the current version of FileStore

To display the current version of FileStore
To display the current version of FileStore and the patch level, enter the following:
Upgrade> show
For example:
Upgrade> show 5.5 ENTERPRISE EDITION (Mon Aug 17 16:12:40 2009), Installed on Mon Aug 10 09:23:28 EST 2009
To display the current version of FileStore, the DUD upgrades, the patch level, and major upgrades, enter the following:
Upgrade> show detail
For example:
Upgrade> show detail 6.0SP1 ENTERPRISE EDITION (Tue Dec 15 08:40:23 2010) 6.0 ENTERPRISE EDITION (Tue Aug 11 08:40:23 2010), Installed on Tue Aug 11 17:21:18 EDT 2010 6.0SP1 ENTERPRISE EDITION (Tue Dec 15 08:40:23 2010), Installed on Tue Dec 15 19:19:54 EDT 2010 Major Upgrade(s) ================ Upgraded from 5.5 to 6.0 (Tue Aug 11 08:40:23 2010) on Tue Aug 11 17:21:18 EDT 2010
468
Upgrading Symantec FileStore About installing patches
About installing patches

Table 16-2 Command
patch install
Patch commands Definition

Downloads the patch from a specified URL and install it on all of the nodes. The Upgrade> patch install command first synchronizes the nodes that have different software versions compared to the other nodes. If the remaining nodes (nodes other than the first node added into the cluster) have a different set of driver requirements, then you can also use the same patch install command to add drivers in the driver update image present in the install server. The driver update image present in the install server acts as a Driver Update Disk (DUD) image during the installation for any node using the PXE boot. To use the same patch install interface for the DUD update process, along with the URL path of the DUD patch (the DUD ISO), you have to specify the list of drivers you want to add.
Note: After you have installed, uninstalled, or synchronized a new

FileStore patch into your cluster, the list of available commands may have changed. Please re-login to the CLI to access the updated features. See Installing patches on page 470. patch uninstall-upto Uninstalls the software upgrade from all of the nodes up to the specified version. You must specify the versions of software up to the version that you want to uninstall. This command first synchronizes the nodes that have different software versions compared to other nodes in the cluster. See Installing patches on page 470. patch sync Forcefully synchronizes the specified node, bringing it up to the currently installed software version of the remaining nodes in the cluster. You only need to install the patch on one node, and then run the Upgrade> patch sync command to synchronize all of the nodes. See Installing patches on page 470. patch duduninstall Removes all of the driver updates previously added to the cluster and reverts back to the original driver update image. This process does not remove the drivers that were added during the installation of the first node. The DUD uninstall process is not incremental, unlike the DUD upgrade process where you can add different drivers by using the patch install commands multiple times. See Installing patches on page 470.
Upgrading Symantec FileStore About types of patches
469
About types of patches

FileStore patches can be divided into two types based on if a patch requires a reboot of the cluster or not:
1) Patches that do not require a cluster reboot. This patch upgrades only FileStore-related binaries and any operating system RPMs that do not require a reboot after applying the patch. Type 1 patches do not require a cluster reboot, so the direct upgrade process can be used. The direct upgrade process does not bring down any nodes/resources while applying a patch, and the upgrade applies the patch on all the nodes in parallel. The cluster remains in a running state serving clients while the upgrade process is running. 2) Patches that require a cluster reboot. This patch upgrades operating system RPMs and FileStore binaries that require a reboot of the cluster. These patches require a one-time cluster reboot. Type 2 patches require a one-time cluster reboot, so use the phased upgrade process to minimize downtime. In a phased upgrade, the upgrade process selects one node called the first-stage node, and stops all services/resources on the first-stage node. (No resources failover to other nodes, so clients connected to the first-stage node virtual IP (VIP) will be interrupted.) The first-stage node is upgraded first. While the upgrade process is running on the first-stage node, the remaining nodes (second-stage nodes) continue serving clients. Once the first-stage node has been upgraded, the upgrade process stops the services/resources on the remaining nodes, and reboots the first-stage node (complete cluster shutdown). When the first-stage node comes up, the phased upgrade starts the patch upgrade process on the remaining nodes. After completion of the patch upgrade on the remaining nodes, all services/resources are online and serving clients. In the case of a phased upgrade, you will be prompted with a message such as the following:
Applying this patch requires reboot of cluster node(s) and uses a phased upgrade mechanism. In phased upgrade method, the patch will be applied on one of the cluster nodes in first phase and then on rest of the nodes in second phase. There will be a downtime of service between these two phases. Do you want to continue with phased installation of this patch? [y|n]
Also, in the case if a phased upgrade fails, the patch synchronization process will not bring a node back to the same level as for the console node. Failed nodes should be added back to the cluster using a PXE installation.
470
Upgrading Symantec FileStore Installing patches
Note: An uninstall is not supported for phased-upgrade patches.
Note: FileStore does not support rollback if the patch upgrades any RPMs.
Installing patches
To install the latest patches on your system
To install the latest patches, enter the following:

Upgrade> patch install URL [driver_list]
For example, you can download a DUD ISO from an HTTP server with authentication and install it. The following output shows the update of the driver update image (on all of the nodes present in the cluster) with the tg3 driver of version 3.71b and the megaraid-sas.ko driver of version 00.00.03.16.
http://admin@docserver.symantec.com/DRIVER_UPDATES/SFS_DUD.iso tg3.ko:3.71b,megaraid_sas.ko:00.00.03.16 Enter password for user 'admin': ********** Please wait. Upgrade is in progress... Patch upgraded on all nodes of cluster.
URL
The URL of the location from where you can download the software patch. The URL supports HTTP, FTP, and SCP protocols for download. The username and password for the HTTP and FTP protocols are supported.
Upgrading Symantec FileStore Uninstalling patches
471
driver_list
An optional variable that you can use for DUD upgrades. Enter a list of comma-separated [drivername:versionnumber] pairs when you want to apply the DUD upgrade. You can exit the patch DUD upgrade process by entering no/no at the prompt. For example: Upgrade> patch install scp:// support@10.209.106.101:/home/support/SFS.iso Enter password for user 'support':******** No input driver given... List of drivers present in DUD:: Drivername:Versionnumber ************************** e1000.ko:7.6.9.1 tg3.ko:3.71b megaraid_sas.ko:00.00.03.16 Please enter driver list you want to add [Enter "No" to exit from here]:: no Sorry...Patch driverupgrade process is terminated by you. The following is an example driver name: tg3.ko
Uninstalling patches
To uninstall patches
To uninstall the software upgrades, enter the following:

Upgrade> patch uninstall-upto version
where version specifies the versions of software up to the version that you want to uninstall. For example:
Upgrade> patch uninstall-upto 5.5RP1 OK Completed
472
Upgrading Symantec FileStore Synchronizing software upgrades on a node
Synchronizing software upgrades on a node

The Upgrade> patch sync command checks that all the nodes are on the same patch level or not. If not, FileStore brings the nodes that are on different patch levels to the same patch level as for the console node. To forcefully synchronize software upgrades on a node
To forcefully synchronize software upgrades on a node, enter the following:

Upgrade> patch sync nodename
where nodename specifies the node that needs to be synchronized to the same software version as the one currently installed in the cluster. For example:
Upgrade> patch sync node2 ............... Syncing software upgrades on node2... SFS patch SUCCESS V-288-122 Patch sync completed.
Uninstalling driver updates

This command lists all of the drivers updated on the cluster and asks you to confirm the uninstall on each one by entering y or yes. If you decide not to uninstall the drivers, press any key other than y or yes to exit the uninstall process.
Upgrading Symantec FileStore Uninstalling driver updates
473
To uninstall driver updates
To uninstall the driver updates, enter the following:

Upgrade> patch duduninstall
You will be asked to confirm the uninstallation of the drivers. For example:
Upgrade> patch duduninstall patch duduninstall DUD updated with following drivers :: ===================================== tg3.ko:3.71b megaraid_sas.ko:00.00.03.16 Do you really want to continue with uninstallation [Enter "y/yes" to continue]:: y Uninstalling DUD... DUD uninstall completed successfully.
474
Upgrading Symantec FileStore Uninstalling driver updates
Chapter
17
Using Symantec AntiVirus for FileStore


About Symantec AntiVirus for FileStore About Symantec AntiVirus for FileStore licensing About Symantec AntiVirus for FileStore commands Displaying Symantec AntiVirus for FileStore configurations About configuring Symantec AntiVirus for FileStore on all the nodes in the cluster Configuring Symantec AntiVirus for FileStore on the cluster's nodes About configuring Auto-Protect on FileStore file systems Configuring Auto-Protect on FileStore file systems About excluding file extensions Configuring file extensions for the Symantec AntiVirus for FileStore configuration file About Symantec AntiVirus for FileStore LiveUpdate Using Symantec AntiVirus for FileStore with LiveUpdate About using Symantec AntiVirus for FileStore quarantine commands Using Symantec AntiVirus for FileStore quarantine commands Setting the Symantec AntiVirus for FileStore action policy
476
Using Symantec AntiVirus for FileStore About Symantec AntiVirus for FileStore
About using Symantec AntiVirus for FileStore manual scan commands Using Symantec AntiVirus for FileStore manual scan commands About scheduling a Symantec AntiVirus for FileStore scan job Scheduling a Symantec AntiVirus for FileStore scan job
About Symantec AntiVirus for FileStore

FileStore software lets you access data through numerous protocols including NFS, CIFS, and FTP. You are able to store your data on the network-attached storage. Symantec AntiVirus for FileStore provides on-access virus protection for data that can be accessed through FileStore. Symantec AntiVirus for FileStore detects and prevents the spread of malicious virus code before your data is compromised. Symantec AntiVirus for FileStore provides two methods for protecting data:
Auto-Protect (AP) scan - protects files and file systems as they are accessed (when a file is opened, modified, or executed) You can use the Auto-Protect method to conduct client access on-demand scanning of NFS, CIFS, or other protocols within FileStore. Symantec AntiVirus for FileStore provides support for the Auto-Protect method through use of the autoprotect commands. See About configuring Auto-Protect on FileStore file systems on page 481. Scheduled scan - scans file systems for viruses when requested or at scheduled intervals You can use the Scheduled scan method to have automated scans occur at regular times, or to manually scan file systems on an as-needed basis. Symantec AntiVirus for FileStore provides support for Scheduled scans through use of the job and scan commands. See About scheduling a Symantec AntiVirus for FileStore scan job on page 496. See About using Symantec AntiVirus for FileStore manual scan commands on page 494.
Note: Symantec AntiVirus for FileStore is based on Symantec Endpoint Protection technology and is an optional component of the FileStore product. Symantec AntiVirus for FileStore requires you to have a valid Symantec Endpoint Protection maintenance agreement in order for the product feature to be licensed correctly.
Using Symantec AntiVirus for FileStore About Symantec AntiVirus for FileStore licensing
477
Figure 17-1
Symantec AntiVirus for FileStore overview
1. Client opens a file.
2. Symantec AntiVirus for FileStore scans the file. 3. If a virus is found, Symantec AntiVirus for FileStore reacts based on the policies.
Client
4. Client is allowed or Server denied access to the file.
1.
The client attempts to access a file from the share. A file becomes a candidate for scanning when it is accessed. If Auto-Protect (AP) is enabled on the share, Symantec AntiVirus for FileStore verifies if the file needs to be scanned or not based on parameters, such as file extensions. If Auto-Protect is not enabled on that share, it allows you to access the file without Symantec AntiVirus for FileStore intervention. If the file is a candidate to be scanned, Symantec AntiVirus for FileStore scans the file and takes the specified action, such as delete, quarantine, or clean, based on the indicated scan action policies. Based on the scan results, you are allowed or denied access to the file.
2.
3.
4.
About Symantec AntiVirus for FileStore licensing

FileStore includes the ability to enable scheduled and Auto-Protect (on-demand) antivirus scanning within the FileStore cluster and without requiring external servers. If you use the Symantec AntiVirus for FileStore antivirus feature, to comply with the Symantec Endpoint Protection End-User License Agreement (EULA), you must have purchased the appropriate number of licenses. Contact your Symantec account representative or channel partner representative for more information on licensing Symantec AntiVirus for FileStore.
About Symantec AntiVirus for FileStore commands

To access the commands, log into your administrative console (master, system-admin, or storage-admin) and enter Antivirus> mode. See About using the FileStore command-line interface on page 33.
478
Using Symantec AntiVirus for FileStore Displaying Symantec AntiVirus for FileStore configurations
Table 17-1 Commands

autoprotect excludeextension
Symantec AntiVirus for FileStore commands Definitions

Enables or disables Auto-Protect (AP) on specified file systems. Adds or deletes file extensions to/from the Symantec AntiVirus for FileStore configuration file. Symantec AntiVirus for FileStoreskips scanning the files whose file extensions are in the excluded list. By default, Symantec AntiVirus for FileStore scans all the files. Creates and configures the scan task identified by a unique job_name. Adds, updates, views, and schedules LiveUpdates to Symantec AntiVirus for FileStore for updating virus definitions. Lists, deletes, repairs, and provides information about quarantined items. Manually starts, stops, and gives status of the file systems. Sets the Symantec AntiVirus for FileStore action policy. Symantec AntiVirus for FileStore takes action according to action policies when a virus is detected in a file. Available action policies are delete, quarantine, clean, and leave. Starts or stops Symantec AntiVirus for FileStore on specified file systems. The command also displays the status of Symantec AntiVirus for FileStore on each node. By default, Symantec AntiVirus for FileStore is stopped on all of the nodes. Displays all of the configuration details of Symantec AntiVirus for FileStore. For example, list of file extensions (doc, exe, zip) and scan action details (clean, delete).
job liveupdate
quarantine
scan scanaction
service
show
Displaying Symantec AntiVirus for FileStore configurations

The show command displays the Symantec AntiVirus for FileStore logs and configuration details.
Using Symantec AntiVirus for FileStore About configuring Symantec AntiVirus for FileStore on all the nodes in the cluster
479
To display Symantec AntiVirus for FileStore configurations
To display Symantec AntiVirus for FileStore logs configuration details, enter the following:
Antivirus> show logs [number_of_jobs]
where number_of_jobs is the number of scan jobs. You can enter a 0 to display all scan logs. For example:
Antivirus> show logs 2 JOB NAME -------MANUALSCAN job1 FS NAME ------fs1 fs1 SCAN START TIME ------------------2009/06/04 04:03:02 2009/06/03 05:12:01 NODE NAME --------cluster_01 cluster_02 SCAN END TIME -----------------2009/06/02 04:08:03 2009/06/03 05:22:02 TIME TO SCAN -----------5 Mins 10 Mins TOTAL THREATS ------------0 3
FILES OMITTED ------------0 0
FILES SCANNED ------------100 500
THREAT NAME ---------------------EICAR Test String EICAR Test String Quarantine succeeded. EICAR Test String
FILE NAME ACTION TAKEN --------------------------------------/vx/fs1/eicar.com Quarantine succeeded. /vx/fs1/eicarcom2.zip>>eicar_com.zip>>eicar.com /vx/fs1/eicarcom2.zip /vx/fs1/eicar.com.txt Quarantine succeeded. Quarantine succeeded.
About configuring Symantec AntiVirus for FileStore on all the nodes in the cluster
The service command enables, disables, or displays status for the Symantec AntiVirus for FileStore service on all of the nodes in the cluster.
480
Using Symantec AntiVirus for FileStore Configuring Symantec AntiVirus for FileStore on the cluster's nodes
Table 17-2
Symantec AntiVirus for FileStore cluster node configuration commands Definition

Starts Symantec AntiVirus for FileStore on all of the nodes in a cluster. By default, Symantec AntiVirus for FileStore is disabled on all of the nodes in the cluster. See Configuring Symantec AntiVirus for FileStore on the cluster's nodes on page 480.
Command
service start
service stop
Stops Symantec AntiVirus for FileStore on all of the nodes in the cluster. See Configuring Symantec AntiVirus for FileStore on the cluster's nodes on page 480.
service status
Displays the status of the Symantec AntiVirus for FileStore service on each node. See Configuring Symantec AntiVirus for FileStore on the cluster's nodes on page 480.
Configuring Symantec AntiVirus for FileStore on the cluster's nodes

To start Symantec AntiVirus for FileStore on all nodes in the cluster
To start Symantec AntiVirus for FileStore on all of the nodes in a cluster, enter the following:
Antivirus> service start
By default, the Symantec AntiVirus for FileStore service will be offline. If the Symantec AntiVirus for FileStore service is already started, Symantec AntiVirus for FileStore clears the faults (if any), and then tries to start the Symantec AntiVirus for FileStore service. For example:
Antivirus> service start
Using Symantec AntiVirus for FileStore About configuring Auto-Protect on FileStore file systems
481
To stop Symantec AntiVirus for FileStore on all nodes in the cluster
To stop Symantec AntiVirus for FileStore on all nodes in a cluster, enter the following:
Antivirus> service stop
You will receive an error if you try to stop an already stopped Symantec AntiVirus for FileStore service. For example:
Antivirus> service stop
To display Symantec AntiVirus for FileStore status on all nodes in the cluster
To display the status of the Symantec AntiVirus for FileStore service on all the nodes in the cluster, enter the following:
Antivirus> service status
For example:
Antivirus> service status
About configuring Auto-Protect on FileStore file systems

The autoprotect command enables or disables Auto-Protect (AP) antivirus protection on specified file system(s) or on all of the FileStore file systems. The default option enables Auto-Protect on all FileStore file systems. Table 17-3 Command autoprotect commands Definition
autoprotect enable Enables Auto-Protect on a specified file system(s) or all of the file systems. See Configuring Auto-Protect on FileStore file systems on page 482. autoprotect disable Disables Auto-Protect on a specified file system(s) or all of the file systems. See Configuring Auto-Protect on FileStore file systems on page 482.
482
Using Symantec AntiVirus for FileStore Configuring Auto-Protect on FileStore file systems
Configuring Auto-Protect on FileStore file systems

To enable Auto-Protect on FileStore file systems
To enable automatic antivirus protection on individual file systems, enter the following:
Antivirus> autoprotect enable fs_name1,fs_name2
where fs_name1 and fs_name2 are the names of the file systems. For example, to enable Auto-Protect on specified file systems, enter the following:
Antivirus> autoprotect enable fs1,fs2
By default, Auto-Protect is disabled on newly created file systems. If you issue the autoprotect enable command without any options, Auto-Protect is enabled on all the file systems in the cluster. For example, to enable Auto-Protect on all the file systems in the cluster, enter the following:
Antivirus> autoprotect enable
To disable Auto-Protect on FileStore file systems
To disable Auto-Protect on FileStore file systems, enter the following:

Antivirus> autoprotect disable fs_name1,fs_name2
where fs_name1 and fs_name2 are the names of the file systems for which Auto-Protect should be disabled. For example:
Antivirus> autoprotect disable fs1,fs2
About excluding file extensions

The excludeextension command lets you exclude file extensions so they are not included in the Symantec AntiVirus for FileStore scan. Note: File extensions are case-sensitive.
Using Symantec AntiVirus for FileStore Configuring file extensions for the Symantec AntiVirus for FileStore configuration file
483
Table 17-4 Command

excludeextension add
File extension exclusion commands Definition

Adds file extensions to the Symantec AntiVirus for FileStore configuration file. The files contained in this configuration file are not scanned by the Symantec AntiVirus for FileStore software. See Configuring file extensions for the Symantec AntiVirus for FileStore configuration file on page 483.
excludeextension delete
Deletes files extensions from the Symantec AntiVirus for FileStore configuration file. After the files are deleted from the configuration file, they are scanned by the Symantec AntiVirus for FileStore software. See Configuring file extensions for the Symantec AntiVirus for FileStore configuration file on page 483.
excludeextension list
Displays the list of file extensions currently in the Symantec AntiVirus for FileStore configuration file. See Configuring file extensions for the Symantec AntiVirus for FileStore configuration file on page 483.
Configuring file extensions for the Symantec AntiVirus for FileStore configuration file
To add file extensions to the Symantec AntiVirus for FileStore configuration file
To add file extensions to the Symantec AntiVirus for FileStore configuration file and eliminate the files from being scanned, enter the following:
Antivirus> excludeextension add file_extension1,file_extension2
where file_extension1,file_extension2 are the names of the file extensions you want to add to the Symantec AntiVirus for FileStore configuration file. For example:
Antivirus> excludeextension add txt,DOC SFS antivirus SUCCESS V-288-1128 File extension txt,DOC added
484
Using Symantec AntiVirus for FileStore About Symantec AntiVirus for FileStore LiveUpdate
To delete file extensions from the Symantec AntiVirus for FileStore configuration file
To delete file extensions from the Symantec AntiVirus for FileStore configuration file and include the files in the Symantec AntiVirus for FileStore scan, enter the following:
Antivirus> excludeextension delete file_extension1,file_extension2
where file_extension1,file_extension2 are the names of the file extensions you want to delete from the Symantec AntiVirus for FileStore configuration file. For example:
Antivirus> excludeextension delete txt SFS antivirus SUCCESS V-288-1128 File extension txt deleted
To display the list of file extensions in the Symantec AntiVirus for FileStore configuration file
To display the list of file extensions in the Symantec AntiVirus for FileStore configuration file, enter the following:
Antivirus> excludeextension list
For example:
Antivirus> excludeextension list Parameter ---------------------------------File excluded extension list
Value ----DOC
About Symantec AntiVirus for FileStore LiveUpdate

The liveupdate feature is used to add LiveUpdate servers to Symantec AntiVirus for FileStore for updating virus definitions. Table 17-5 Command
liveupdate serveradd
Symantec AntiVirus for FileStore liveupdate commands Definition

Adds LiveUpdate servers to Symantec AntiVirus for FileStore for updating virus definitions. See Using Symantec AntiVirus for FileStore with LiveUpdate on page 486.
Using Symantec AntiVirus for FileStore About Symantec AntiVirus for FileStore LiveUpdate
485
Table 17-5 Command

liveupdate serverdelete
Symantec AntiVirus for FileStore liveupdate commands (continued) Definition

Deletes a Symantec AntiVirus for FileStore LiveUpdate server or proxy from the LiveUpdate servers list. See Using Symantec AntiVirus for FileStore with LiveUpdate on page 486.
liveupdate start
Runs a LiveUpdate of the virus definitions immediately. See Using Symantec AntiVirus for FileStore with LiveUpdate on page 486.
liveupdate schedule create
Creates a schedule for the LiveUpdate. See Using Symantec AntiVirus for FileStore with LiveUpdate on page 486. Modifies a schedule for the LiveUpdate. See Using Symantec AntiVirus for FileStore with LiveUpdate on page 486. Deletes the schedule of the LiveUpdate. See Using Symantec AntiVirus for FileStore with LiveUpdate on page 486. Displays the LiveUpdate schedule. See Using Symantec AntiVirus for FileStore with LiveUpdate on page 486.
liveupdate schedule modify
liveupdate schedule delete
liveupdate schedule show
486
Using Symantec AntiVirus for FileStore Using Symantec AntiVirus for FileStore with LiveUpdate
Using Symantec AntiVirus for FileStore with LiveUpdate

To add the LiveUpdate servers to Symantec AntiVirus for FileStore
To add the LiveUpdate servers to Symantec AntiVirus for FileStore, enter the following:
Antivirus> liveupdate serveradd url
where url is either an HTTP, FTP, or proxy server URL. For example:
Antivirus> liveupdate server add http://sample.com SFS antivirus SUCCESS V-288-1263 Server added to liveupdate server database.
The master node assigns a server ID to the given input. You can add a maximum of 10 servers and 1 proxy server to the LiveUpdate server list. To delete the server or proxy from the LiveUpdate servers list
To delete the server or proxy from the LiveUpdate servers list, enter the following:
Antivirus> liveupdate serverdelete serverid | proxy serverid Specifies the ID of the server to be deleted from the LiveUpdate server list. Specifies the proxy server to be deleted from the LiveUpdate server list.
proxy
For example, this command deletes the proxy server from the LiveUpdate servers list, if the proxy server exists.
Antivirus> liveupdate serverdelete proxy SFS antivirus SUCCESS V-288-1274 Successfully proxy server deleted from liveupdate server database.
For example, this command deletes the server associated with server ID 3.
Antivirus> liveupdate serverdelete 3 SFS antivirus SUCCESS V-288-1278 Successfully server with id 3 deleted from liveupdate server database.
487
To run LiveUpdate on Symantec AntiVirus for FileStore
To immediately run LiveUpdate on Symantec AntiVirus for FileStore, enter the following:
Antivirus> liveupdate start
For example, this command runs LiveUpdate immediately.

Antivirus> liveupdate start Please wait liveupdate in progress SFS antivirus SUCCESS V-288-1108 Done
488
To create a new schedule for LiveUpdate on Symantec AntiVirus for FileStore
To create a schedule for LiveUpdate on Symantec AntiVirus for FileStore, enter the following:
Antivirus> liveupdate schedule create minute hour day_of_the_month month day_of_the_week minute Specifies the minutes for the LiveUpdate. This field may contain either an asterisk '*', which implies 'every minute' or a numeric value between the range of 0-59. hour Specifies the hour for the LiveUpdate. This field may contain either an asterisk '*', which implies running every hour, or a numeric value between the range of 0-23. day_of_the_month Specifies the day of the month for the LiveUpdate. This field may contain either an asterisk '*', which implies running every day of the month, or a numeric value between the range of 1-31. month Specifies the month for the LiveUpdate. This field may contain either an asterisk '*', which implies running every month, or a numeric value between the range of 1-12. In addition to the numeric values, this field can also accept names of month as an argument, with the first three letters of the month (case-insensitive) serving as input for the given parameter. day_of_the_week Specifies the day of the week for the LiveUpdate. This field may contain either an asterisk '*', which implies running every day of the week, or a numeric value between the range of 0-7, with both 0 and 7 being interpreted as Sunday by crontab. In addition, this parameter can also accept names, with the first three letters of the month (case-insensitive) serving as an input value.
You can only create one LiveUpdate schedule. For example, this command invokes LiveUpdate every Monday.
Antivirus> liveupdate schedule create * * * * 1 SFS antivirus SUCCESS V-288-1255 Scheduled liveupdate successfully created
489
To modify the LiveUpdate schedule
To modify a schedule for LiveUpdate on Symantec AntiVirus for FileStore, enter the following:
Antivirus> liveupdate schedule modify minute hour day_of_the_month month day_of_the_week minute Modify the minutes for the LiveUpdate. This field may contain either an asterisk '*', which implies 'every minute' or a numeric value between the range of 0-59. hour Modify the hour for the LiveUpdate. This field may contain either an asterisk '*', which implies running every hour, or a numeric value between the range of 0-23. day_of_the_month Modify the day of the month for the LiveUpdate. This field may contain either an asterisk '*', which implies running every day of the month, or a numeric value between the range of 1-31. month Modify the month for the LiveUpdate. This field may contain either an asterisk '*', which implies running every month, or a numeric value between the range of 1-12. In addition to the numeric values, this field can also accept names of month as an argument, with the first three letters of the month (case-insensitive) serving as input for the given parameter. day_of_the_week Modify the day of the week for the LiveUpdate. This field may contain either an asterisk '*', which implies running every day of the week, or a numeric value between the range of 0-7, with both 0 and 7 being interpreted as Sunday by crontab. In addition, this parameter can also accept names, with the first three letters of the month (case-insensitive) serving as an input value.
For example, this command modifies the LiveUpdate schedule.

Antivirus> liveupdate schedule modify 0 1 * * * SFS antivirus SUCCESS V-288-1255 Scheduled liveupdate successfully modified
490
Using Symantec AntiVirus for FileStore About using Symantec AntiVirus for FileStore quarantine commands
To delete the current LiveUpdate schedule
To delete the current LiveUpdate schedule, enter the following:

Antivirus> liveupdate schedule delete
For example, this command deletes the LiveUpdate schedule.

Antivirus> liveupdate schedule delete SFS antivirus SUCCESS V-288-1255 Scheduled liveupdate successfully deleted
To display the current LiveUpdate schedule
To display the current LiveUpdate schedule, enter the following:

Antivirus> liveupdate schedule show
For example, this command displays the current LiveUpdate schedule.

Antivirus> liveupdate schedule show Liveupdate scheduled on 0 1 * * *
About using Symantec AntiVirus for FileStore quarantine commands

Symantec AntiVirus for FileStore places scanned files that have not passed the virus protection software in quarantine. The quarantine commands let you display information about these files, delete the files, repair the files, or restore the quarantined files. Table 17-6 Command
quarantine list
Symantec AntiVirus for FileStore quarantine commands Definition

Lists all of the files that have been quarantined. See Using Symantec AntiVirus for FileStore quarantine commands on page 491.
quarantine delete
Deletes the quarantined files. See Using Symantec AntiVirus for FileStore quarantine commands on page 491.
Using Symantec AntiVirus for FileStore Using Symantec AntiVirus for FileStore quarantine commands
491
Table 17-6 Command

quarantine repair
Symantec AntiVirus for FileStore quarantine commands (continued) Definition

Repairs quarantined files. See Using Symantec AntiVirus for FileStore quarantine commands on page 491.
quarantine restore Restores quarantined files. See Using Symantec AntiVirus for FileStore quarantine commands on page 491. quarantine info Displays information about quarantined files. See Using Symantec AntiVirus for FileStore quarantine commands on page 491.
Using Symantec AntiVirus for FileStore quarantine commands

To list all of the quarantined files
To list all of the files that have been quarantined, enter the following:
Antivirus> quarantine list
For example:
Antivirus> quarantine list QID Quarantine file ----------------sfs_01_5BA00000 /vx/fs2/eicar.com sfs_01_5BA00001 /vx/fs1/eicarcom2.zip sfs_02_5BA00002 /vx/fs1/eicar.com.txt
Each quarantined file is associated with an ID. Each node stores quarantined files locally. If any node is removed from a cluster, quarantined files on that node are lost. For example:
sfs_01_5BA00000 is the ID of the /vx/fs2/eicar.com quarantined file.
492
Using Symantec AntiVirus for FileStore Using Symantec AntiVirus for FileStore quarantine commands
To delete the quarantined files
To delete the quarantined files, enter the following:

Antivirus> quarantine delete [id]
where id is the specified quarantined file to be deleted. Each quarantined file has an ID. If no ID is entered, all of the quarantined files are deleted. For example:
Antivirus> quarantine delete sfs_01_5BA00000 Please wait ... It will take some time ... SFS antivirus SUCCESS V-288-1108 Done
To repair a quarantined file
To repair a quarantined file, enter the following:

Antivirus> quarantine repair [id]
where id is the specified quarantined file to be repaired. Each quarantined file has an ID. If no ID is entered, all of the quarantined files are repaired. For example:
Antivirus> quarantine repair sfs_01_5BA00000, sfs_02_6BA00000 Please wait ... It will take some time ... SFS antivirus SUCCESS V-288-1108 Done
To restore a quarantined file
To restore a quarantined file, enter the following:

Antivirus> quarantine restore [id]
where id is the specified quarantined file to be restored. Each quarantined file has an ID. If no ID is entered, all of the quarantined files are restored. For example:
Antivirus> quarantine restore sfs_01_5BA00000, sfs_01_6BA00000
Using Symantec AntiVirus for FileStore Setting the Symantec AntiVirus for FileStore action policy
493
To display information about quarantined files
To display information about specified quarantined files, enter the following:

Antivirus> quarantine info [id]
where id is the specified file you want information about. For example:
Antivirus> quarantine info sfs_01_5BA00000 Item: 5BA00000 Description: /vx/fs1/eicar.com Full Path: /vx/fs1/eicar.com Log Line: 270502050402,5,1,1,sfs_01,root,EICAR Test String, /vx/fs1/eicar.com,1,5,1,256,33570852,"",1243933471,, Flags: INFECTED Quarantined: Tue Jun 2 05:04:02 2009 Created: Tue Jun 2 05:04:02 2009 Last Accessed: Tue Jun 2 05:04:02 2009 Last Modified: Tue Jun 2 05:02:47 2009
Setting the Symantec AntiVirus for FileStore action policy

The scanaction command sets the Symantec AntiVirus for FileStore action policy. Based on this policy, Symantec AntiVirus for FileStore takes action when a virus is detected in a file.
494
Using Symantec AntiVirus for FileStore About using Symantec AntiVirus for FileStore manual scan commands
To set the Symantec AntiVirus for FileStore action policy
To set the Symantec AntiVirus for FileStore action policy, so that Symantec AntiVirus for FileStore reacts when a virus is detected in a file, enter the following:
Antivirus> scanaction primary_action secondary_action
where primary_action secondary_action are the names of the policies you want the Symantec AntiVirus for FileStore policy to take action on. These polices are:
delete quarantine Deletes the virus-infected file if a virus is found. Quarantines the virus-infected file if a virus is found. Quarantined files are stored on local storage. Attempts to clean the virus from the file if a virus is found. Leaves the virus-infected file as is. Symantec AntiVirus for FileStore does not take any action if a virus is found.
clean leave
For example, if Symantec AntiVirus for FileStore detects a virus in a file, Symantec AntiVirus for FileStore first tries to clean the virus from the infected file (primary_action). If the clean action fails, Symantec AntiVirus for FileStore quarantines the infected file (secondary_action).
Antivirus> scanaction clean quarantine SFS antivirus SUCCESS V-288-1050 Antivirus configuration updated with given scan actions.
About using Symantec AntiVirus for FileStore manual scan commands

The scan command lets you scan specific file systems for viruses, instead of the entire node. Table 17-7 Command
scan start
Symantec AntiVirus for FileStore manual scan commands Definition

Starts the manual scan on the file systems. See Using Symantec AntiVirus for FileStore manual scan commands on page 495.
Using Symantec AntiVirus for FileStore Using Symantec AntiVirus for FileStore manual scan commands
495
Table 17-7
Symantec AntiVirus for FileStore manual scan commands (continued) Definition

Displays the manual scan status , which shows if the scan is in progress or done. See Using Symantec AntiVirus for FileStore manual scan commands on page 495.
Command
scan status
scan stop
Stops the manual scan. See Using Symantec AntiVirus for FileStore manual scan commands on page 495.
Using Symantec AntiVirus for FileStore manual scan commands

To start the manual scan
To start the manual scan on the specified file systems on the preferred node, enter the following:
Antivirus> scan start fs_name1,fs_name2 [preferred_node]
where fs_name1,fs_name2, preferred_node are the file system names for performing a manual scan. If a preferred_node is not specified, the master node determines the node for running the scan. For example:
Antivirus> scan start fs1,fs2,fs3 SFS antivirus SUCCESS V-288-1187 Manual scan started on fs1,fs2,fs3.
496
Using Symantec AntiVirus for FileStore About scheduling a Symantec AntiVirus for FileStore scan job
To display the scan status from a manual scan
To display the manual scan status (if the scan is in progress or done), enter the following:
Antivirus> scan status
For example:
Antivirus> scan status SFS antivirus SUCCESS V-288-1185 Manual scan is in progress on fs1,fs2,fs3.
To stop the manual scan
To stop the manual scan if there are any manual scans running in the background, enter the following:
Antivirus> scan stop
For example:
Antivirus> scan stop SFS antivirus SUCCESS V-288-1188 Manual scan stopped successfully.
About scheduling a Symantec AntiVirus for FileStore scan job

Use the job command to schedule a Symantec AntiVirus for FileStore scan job. The specified job_name must be unique. Table 17-8 Definition
job create
Scan scheduling commands Command

Creates a schedule for a scan that is identified by the job_name. See Scheduling a Symantec AntiVirus for FileStore scan job on page 498.
job modify
Modifies the schedule for a scan that is identified by the job_name. See Scheduling a Symantec AntiVirus for FileStore scan job on page 498.
Using Symantec AntiVirus for FileStore About scheduling a Symantec AntiVirus for FileStore scan job
497
Table 17-8 Definition

job enable
Scan scheduling commands (continued) Command

Enables the given job_name scan schedule. See Scheduling a Symantec AntiVirus for FileStore scan job on page 498.
job disable
Disables the given job_name scan schedule. See Scheduling a Symantec AntiVirus for FileStore scan job on page 498.
job show
Displays information about the given job_name. See Scheduling a Symantec AntiVirus for FileStore scan job on page 498.
job stop
Stops the given job_name from running. See Scheduling a Symantec AntiVirus for FileStore scan job on page 498.
job delete
Deletes the given job_name. See Scheduling a Symantec AntiVirus for FileStore scan job on page 498.
498
Using Symantec AntiVirus for FileStore Scheduling a Symantec AntiVirus for FileStore scan job
Scheduling a Symantec AntiVirus for FileStore scan job

To create a schedule for running a scan job
To create a schedule for running a scan job identified by the assigned job name, enter the following:
Antivirus> job create job_name fs_name1,fs_name2 minute hour day_of_the_month month day_of_the_week [preferred_node] job_name fs_name minute hour day_of_the_month month day_of_the_week preferred_node (optional) Enter a unique job name for the scan. Enter the name of the file system you want to scan. Enter the minutes for scheduling the scan. Enter the hour for scheduling the scan. Enter the day of the month for scheduling the scan. Enter the month for scheduling the scan. Enter the day of the week for scheduling the scan. Enter the preferred node for running the scan job. If no node name appears, the master node selects a node from the cluster and assigns the scheduled scan on that node.
For example, to create a schedule for scanning the file systems fs1 and fs2 every Sunday, you would enter the following:
Antivirus> job create job1 fs1,fs2 0 0 * * 0 SFS antivirus SUCCESS V-288-1169 Job job1 successfully created
499
To modify the schedule for a scan job
To modify the already created scan job, enter the following:

Antivirus> job modify job_name fs_name1,fs_name2 minute hour day_of_the_month month day_of_the_week [preferred_node] job_name fs_name minute hour day_of_the_month month day_of_the_week preferred_node (optional) Modify the unique job name for the scan. Modify the name of the file system you want to scan. Modify the minutes for scheduling the scan. Modify the hour for scheduling the scan. Modify the day of the month for scheduling the scan. Modify the month for scheduling the scan. Modify the day of the week for scheduling the scan. Modify the preferred node for running the scan job. If no node name appears, the master node selects a node from the cluster and assigns the scheduled scan on that node.
For example, to modify job1 for scanning the file system fs3 on the sfs_02 node on the first day of every month, you would enter the following:
Antivirus> job modify job1 fs3 0 0 1 * * sfs_02 SFS antivirus SUCCESS V-288-1168 Job job1 modified.
To enable the scan schedule
To enable the scheduled scan job, enter the following:

Antivirus> job enable job_name
where job_name is the unique name for the scan. For example:
Antivirus> job enable job1 SFS antivirus SUCCESS V-288-1168 Job job1 enabled.
500
To disable the scan schedule
To disable the scheduled scan, enter the following:

Antivirus> job disable job_name
Antivirus> job disable job1 SFS antivirus SUCCESS V-288-1168 Job job1 disabled.
To display information about the scan schedule
To display information about the scheduled scan job, enter the following:
Antivirus> job show job_name
Antivirus> job show job1 Jobname FS State ======= == ===== job1 fs1 DISABLED Preferrednode ============= *
Minute Hour Day Month Week ====== ==== ==== ===== ===== * * * *
To stop the scan schedule
To stop the scheduled scan from running, enter the following:

Antivirus> job stop job_name is
Antivirus> job stop job1 SFS antivirus ERROR V-288-1042 job1 job is not running.
501
To delete the scan schedule
To delete the scheduled scan, enter the following:

Antivirus> job delete job_name
Antivirus> job delete job1 SFS antivirus SUCCESS V-288-1167 Job job1 deleted.
502
Chapter
18
Troubleshooting

About troubleshooting commands Setting the CIFS log level Retrieving and sending debugging information Updating FileStore GUI-related operations About the iostat command Generating CPU and device utilization reports Displaying license information for the cluster About excluding the PCI ID prior to the FileStore installation Excluding the PCI IDs from the cluster Testing network connectivity About the services command Using the services command Using the support login About network traffic details Exporting and displaying the network traffic details Accessing processor activity Using the traceroute command Recovering from a non-graceful shutdown
504
Troubleshooting About troubleshooting commands
About troubleshooting commands

This chapter discusses the FileStore troubleshooting commands. You use these commands to check the status of the nodes and the FileStore cluster. The troubleshooting mode commands are in Table 18-1. To access a particular troubleshooting submode command, log into the administrative console (for master, system-admin, or storage-admin) and enter the appropriate mode. See About using the FileStore command-line interface on page 33. Table 18-1 Command
debuginfo
Support mode commands Definition

Sets CIFS-related log levels for the FileStore cluster. See Setting the CIFS log level on page 505. Retrieves FileStore debugging information from a FileStore node and sends the information to a server using an external FTP or SCP server. See Retrieving and sending debugging information on page 506.
gui
Updates FileStore GUI-related operations. See Updating FileStore GUI-related operations on page 507.
iostat
Generates CPU statistical information. Generates the device utilization report. See About the iostat command on page 507.
license
Displays the licensing information for the cluster. The licensing information includes the total count of CPUs in the cluster and the type of edition (Enterprise edition or Standard edition) that the cluster is running. See Displaying license information for the cluster on page 509.
pciexclusion
Excludes the Peripheral Component Interconnect (PCI) IDs from the nodes in a cluster prior to installing the FileStore software. The PCI IDs must be excluded prior to the PXE boot. See About excluding the PCI ID prior to the FileStore installation on page 510.
network> ping
Tests whether a particular host or gateway is reachable across an IP network. See Testing network connectivity on page 513.
Troubleshooting Setting the CIFS log level
505
Table 18-1 Command

services
Support mode commands (continued) Definition

Brings services that are OFFLINE or FAULTED back into the ONLINE state. See Using the services command on page 515.
support login
Reports FileStore technical support issues. See Using the support login on page 517.
tethereal
Exports the network traffic details to the specified location. Displays captured packet data from a live network. See About network traffic details on page 517.
top
Displays the dynamic real-time view of currently running tasks. See Accessing processor activity on page 519.
traceroute
Displays all of the intermediate nodes on a route between two nodes. See Using the traceroute command on page 520.
Setting the CIFS log level

You can set the CIFS log level for the FileStore cluster. To set the CIFS log level
To set the CIFS-related log level for the FileStore cluster, enter the following:
Support> debuginfo setlog loglevel
A valid loglevel ranges from 0 to 10, 10 being the most detailed log level. It is recommended to increase the CIFS log level, reproduce the CIFS issue, and then upload debugging information for the CIFS issue. The default log level is 2. For example, to set the CIFS log level to 10 for the FileStore cluster:
Support> debuginfo setlog 10
See Retrieving and sending debugging information on page 506.
506
Troubleshooting Retrieving and sending debugging information
Retrieving and sending debugging information

You can retrieve FileStore debugging information from a FileStore node and send the information to a server using an external FTP or SCP server. To upload debugging information from a specified node to an external server
To upload debugging information from a specified node to an external server, enter the following:
Support> debuginfo upload nodename debug-URL module
For example, to upload all debugging information to an FTP server:

Support> debuginfo upload node1_1 ftp://admin@ftp.docserver.company.com/patches/ all
For example, to upload CIFS-related debugging information to an SCP server:

Support> debuginfo upload node1_1 scp://root@server.company.com:/tmp/node1_1-cifs-debuginfo.tar.gz nodename Specifies the nodename from which to collect the debugging information. Specifies the remote file or directory for uploading debugging information. Depending on the type of server from which you are uploading debugging information, use one of the following example URL formats: ftp://admin@ftp.docserver.company.com/ patches/ scp://root@server.company.com:/tmp/ If debug-URL specifies a remote file, the debuginfo file is saved by that name. If debug-URL specifies a remote directory, the debuginfo file name displays as the following: sfsfs_debuginfo_nodename_modulename_timestamp.tar.gz
debug-URL
module
Specifies the values for module. Supported module values are the following:

generic - use to collect Symantec FileStore configurations cifs - use to collect CIFS-related debugging information all - use to collect all information for debugging
Troubleshooting Updating FileStore GUI-related operations
507
Updating FileStore GUI-related operations

You use the Support> gui server commands to start, stop, or display status information for FileStore GUI resources. You use the Support> gui db commands to refresh or rescan the database for the FileStore GUI. To access the FileStore GUI, use any of the following URLs:

https://<CONSOLE-IP>:8443/sm https://<CONSOLE-IP>:8443/sm/Login
To start, stop, or display the status for the FileStore GUI
To start, stop, or display the status for the FileStore GUI, enter the following depending on which action you are performing:
Support> gui server [start|stop|status]
To rescan the FileStore GUI database
To rescan the FileStore GUI database, enter the following:

Support> gui db rescan
The rescan command rescans the database for the FileStore GUI; it generates the fresh database and updates all the changes in the cluster. To refresh the FileStore GUI database
To refresh the FileStore GUI database, enter the following:

Support> gui db refresh [all|filesystem|share|storage|cluster |replication|antivirus|settings|alert|user]
The refresh command only updates the latest changes in the database. It will not recreate the database file.
About the iostat command

The iostat commands display the CPU and I/O statistics.
508
Troubleshooting Generating CPU and device utilization reports
Table 18-2 Command

iostat cpu
iostat commands Definition

Generates CPU statistical information. When the command is used for the first time, it contains information since the system was booted. Each subsequent report shows the details since the last report. See Generating CPU and device utilization reports on page 508.
iostat device
Generates the device utilization report. This information can be used to balance the load among the physical disks by modifying the system configuration. When this command is executed for the first time, it contains information since the system was booted. Each subsequent report shows the details since the last report. There are two options for this command. See Generating CPU and device utilization reports on page 508.
Generating CPU and device utilization reports

To use the iostat command
To use the iostat cpu command, enter the following:

Support> iostat cpu [nodename] [interval] [count] nodename The name of the node from where the report will be generated. The default is console for the Management Console. The duration between each report in seconds. The default is 2 seconds. The number of reports generated at the interval entered in seconds. The default is one report.
interval
count
where the nodename option asks for the name of the node from where the report will be generated. The default is console for the FileStore Management Console. For example, to generate the CPU utilization report of the console node, enter the following:
Support> iostat cpu sfs_01 Linux 2.6.16.60-0.21-smp (sfs_01) avg-cpu: %user 1.86 %nice 0.07 %system 4.53
07/09/09 %iowait 0.13 %steal 0.00 %idle 93.40
Troubleshooting Displaying license information for the cluster
509
To use the iostat device command
To use the iostat device command, enter the following:

Support> iostat device [nodename] [dataunit] [interval] [count] nodename The nodename option asks for the name of the node from where the report will be generated. The default is console for the Management Console. The dataunit option lets you generate the report in block(s) or kilobytes(s). The default is block(s). The duration between each report in seconds. The default is two seconds. The number of reports generated at the interval entered in seconds. The default is one report.
dataunit
interval
count
For example, to generate a device utilization report of a node, enter the following:
Support> iostat device sfs_01 Blk Linux 2.6.16.60-0.21-smp (sfs_01) Device: hda sda hdc tps 4.82 1.95 0.00 Blk_read/s 97.81 16.83 0.01
07/09/09 Blk_read 1410626 242712 136 Blk_wrtn 1241992 58342 0
Blk_wrtn/s 86.11 4.05 0.00
Displaying license information for the cluster

The Support> license show command allows you to display license information for the cluster. The licensing information includes the total count of CPUs in the cluster, and the type of edition (Enterprise or Standard) that the cluster is running. FileStore provides two types of licenses:
Enterprise Edition - The Enterprise Edition of FileStore uses per CPU licenses. Users require as many licenses as there are CPUs in the cluster. Standard Edition - The Standard Edition of FileStore is licensed for a maximum of two CPUs per cluster.
510
Troubleshooting About excluding the PCI ID prior to the FileStore installation
To display license information for the cluster
To display license information for the cluster, enter the following:

Support> license show
For example:
Support> license show There are 4 CPUs in this 2 node FileStore cluster. You are running the Enterprise Edition of FileStore and are using 4 per CPU licenses.
About excluding the PCI ID prior to the FileStore installation

During the initial FileStore software installation, you excluded certain PCI IDs in your cluster to reserve them for future use. This action applies only to the first node. Exclusion also applies to subsequent nodes when they are added if the exclusion criteria is met. Use the commands in this section to exclude additional PCI IDs from the second node or subsequent nodes before you install FileStore software on the second or subsequent nodes. Note: The initial PCI exclusion applies to the first and subsequent nodes that meet the criteria. Once the initial PCI exclusion is in effect, it cannot be deleted without re-creating the FileStore cluster. Table 18-3 Command PCI exclusion commands Definition
pciexclusion show Displays the list of PCI IDs that have been excluded during the initial FileStore installation. The status of the PCI IDs is designated by a y (yes) or n (no). The yes option means they have been excluded. The no option means they have not yet been excluded. See Excluding the PCI IDs from the cluster on page 511. pciexclusion add Allows you to add specific PCI IDs for exclusion. You must enter the values in this command before the PXE boot installation for the PCI IDs to be excluded from the second node installation. See Excluding the PCI IDs from the cluster on page 511.
Troubleshooting Excluding the PCI IDs from the cluster
511
Table 18-3 Command
PCI exclusion commands (continued) Definition
pciexclusion delete Deletes a specified PCI ID from being excluded. You must perform this command prior to a PXE boot installation. See Excluding the PCI IDs from the cluster on page 511.
Excluding the PCI IDs from the cluster

To display the list of excluded PCI IDs
To display the list of PCI IDs that you excluded during the FileStore installation, enter the following:
Support> pciexclusion show PCI ID -----0000:0e:00.0 0000:0e:00.0 0000:04:00:1 PCI ID EXCLUDED -------y y n NODENAME/UUID ------------sfs_01 a79a7f43-9fe2-4eeb-aa1f-27a70e7a0820
The PCI IDs you entered to be excluded during the initial FileStore installation. The PCI ID is made up of the following: [ [<domain>] : ] [ [ <bus> ] : ] [ <slot > ] [ . [ <func> ] ]
EXCLUDED
(y) means the PCI ID has been excluded. (n) means the PCI ID has not been excluded.
NODENAME UUID
The node names corresponding to the PCI IDs. The ID of the node which is in the installed state but not yet added into the cluster.
512
Troubleshooting Excluding the PCI IDs from the cluster
To add a PCI ID for exclusion
To add a PCI ID for exclusion, enter the following:

Support> pciexclusion add pci_list
where pci_list is a comma-separated list of PCI IDs. The format of the PCI ID is in hexadecimal bits (XXXX:XX:XX.X). For example:
Support> pciexclusion add 0000:00:09.8 Support> pciexclusion show PCI ID EXCLUDED NODENAME/UUID ------------------------0000:0e:00.0 y sfs_01 0000:0e:00.0 y a79a7f43-9fe2-4eeb-aa1f-27a70e7a0820 0000:04:00:1 n 0000:00:09.0 n
To delete a PCI ID
To delete a PCI ID that you excluded, enter the following:

Support> pciexclusion delete pci
where pci is the PCI ID in hexadecimal bits. For example: XXXX:XX:XX.X. This command must be used prior to performing a PXE boot installation to take effect. You can only delete a PCI ID exclusion that was not already used on any of the nodes in the cluster. In the following example, you cannot delete PCI IDs with the NODENAME/UUID sfs_1 or a79a7f43-9fe2-4eeb-aa1f-27a70e7a0820. For example:
Support> pciexclusion delete 0000:04:00:1 Support> pciexclusion show PCI ID EXCLUDED NODENAME/UUID ------------------------0000:0e:00.0 y sfs_01 0000:0e:00.0 y a79a7f43-9fe2-4eeb-aa1f-27a70e7a0820 0000:00:09.0 n
Troubleshooting Testing network connectivity
513
Testing network connectivity

You can test whether a particular host or gateway is reachable across an IP network. To use the ping command
To use the ping command, enter the following:

Network> ping destination [nodename] [devicename] [packets]
For example, you can ping host1 using node1:

Network> ping host1 node1 destination Specifies the host or gateway to send the information to. The destination field can contain either a DNS name or an IP address. nodename Specifies the nodename to ping from. To ping from any node, use any in the nodename field. The nodename field is an optional field, and if omitted, any node is chosen to ping from. Specifies the device through which you will ping. To ping from any device in the cluster, use the any variable in the devicename field. Specifies the number of packets that should be sent to the destination. If the packets field is omitted, five packets are sent to the destination by default. The packets field must contain an unsigned integer.
devicename
packets
About the services command

The Support> services command lets you bring services that are OFFLINE or FAULTED back into the ONLINE state. Note: If after using the services command, a service is still offline or faulted, you need to contact Technical Support. These services include:
NFS server
514
Troubleshooting About the services command
CIFS server FTP HTTP GUI Console service Backup NIC information FS manager IP addresses Symantec AntiVirus for FileStore Services commands Definition
Attempts to fix any service that is offline or faulted, running on all of the nodes in the cluster. See Using the services command on page 515.
Table 18-4 Command

services autofix
services online
Fixes a specific service. Enter the servicename and this option will attempt to bring the service back online. If the servicename is already online, no action is taken. If the servername is a parallel service, an attempt is made to online the service on all nodes. If the servicename is a failover service, an attempt is made to online the service on any of the running nodes of the cluster. See Using the services command on page 515.
services show
Lists the state of all of the services. The state of the IPs and file systems are only shown if they are not online. See Using the services command on page 515.
services showall
Lists the state of all of the services including the state of the IPs and the file systems. See Using the services command on page 515.
Troubleshooting Using the services command
515
Using the services command

To display the state of the services
To display the important services running on the nodes, enter the following:
Support> services show Service ------nfs cifs ftp http iSCSIInitiator gui console nic_pubeth0 nic_pubeth1 fs_manager antivirus sfs 01 02 -------- -------ONLINE ONLINE ONLINE ONLINE ONLINE ONLINE ONLINE ONLINE OFFLINE OFFLINE ONLINE ONLINE ONLINE ONLINE ONLINE ONLINE ONLINE ONLINE ONLINE ONLINE ONLINE ONLINE
516
Troubleshooting Using the services command
To display the state of all of the services
To display all of the services running on the nodes, enter the following:
Support> services showall sfs Service 01 02 -------------- -------nfs ONLINE ONLINE cifs ONLINE ONLINE ftp ONLINE ONLINE http ONLINE ONLINE iSCSIInitiator OFFLINE OFFLINE console ONLINE ONLINE gui ONLINE ONLINE nic_pubeth0 ONLINE ONLINE nic_pubeth1 ONLINE ONLINE fs_manager ONLINE ONLINE 10.182.107.201 ONLINE ONLINE 10.182.107.202 ONLINE ONLINE 10.182.107.203 ONLINE ONLINE 10.182.107.204 ONLINE ONLINE /vx/fs1 ONLINE ONLINE antivirus ONLINE ONLINE
To fix any service fault
To fix any service fault, enter the following:

Support> services autofix Attempting to fix service faults...........done
To bring a service online
To bring a service online on the nodes, enter the following:

Support> services online servicename
where servicename is the name of the service you want to bring online. For example:
Support> services online 10.182.107.203
Troubleshooting Using the support login
517
Using the support login

There is a support login used for reporting FileStore technical support issues. Note: The support account is intended for Technical Support use only. It cannot be created by administrators. To use the support login
Log in to the CLI as the support account by entering:

support
and then entering:

symantec
For example,
login as: support Password: Last login: Fri Dec 14 12:09:49 2007 from 172.16.113.118 sfs_01:~ #
After having logged in as the support account, it is recommended that you change your password. See Creating Master, System Administrator, and Storage Administrator users on page 42.
To use the supportuser commands refer to: See About the support user on page 45.
About network traffic details

The tethereal command exports and displays network traffic data. Table 18-5 Command
tethereal export
Tethereal commands Definition

Exports the network traffic details to the specified location. See Exporting and displaying the network traffic details on page 518.
518
Troubleshooting Exporting and displaying the network traffic details
Table 18-5 Command

tethereal show
Tethereal commands (continued) Definition

Displays captured packet data from a live network. See Exporting and displaying the network traffic details on page 518.
Exporting and displaying the network traffic details

To use the tethereal command
To use the tethereal export command, enter the following:

Support> tethereal export url [nodename] [interface] [count] [source] url Provides the location to export the network traffic details. The default filename tethereal.log is used if a filename is not specified in the url. The name of the node from where the traffic details are generated. Unless a name is enter, the default is console for the Management Console. Specifies the network interface for the packet capture. Specifies the maximum number of packets to read. The maximum allowed file size to capture the network traffic details is 128 MB. For a very large 'count' value, if the file size exceeds 128 MB, then the command stops capturing the network traffic details. source Specifies the node to filter the packets.
nodename
interface count
For example, to export the network traffic details, enter the following:
Support> tethereal export scp://user1@172.31.168.140:/ Password: ******* Capturing on pubeth0 ... Uploading network traffic details to scp://user1@172.31.168.140:/ is completed.
Troubleshooting Accessing processor activity
519
To use the tethereal show command
To use the tethereal show command, enter the following:

Support> tethereal show [nodename] [interface] [count] [source] nodename The name of the node from where the traffic details are displayed. The default is console for the Management Console. Specifies the network interface for the packet capture. Specifies the maximum number of packets to read. If you do not specify a count value, the network traffic continues to be displayed until you interrupt it. source Specifies the node to filter the packets.
interface count
For example, the traffic details for five packets, for the Management Console on the pubeth0 interface are:
Support> tethereal show 0.000000 172.31.168.140 0.000276 10.209.105.147 0.000473 10.209.105.147 packet len=112 0.000492 10.209.105.147 packet len=112 sfs_01 pubeth0 5 172.31.168.140 -> 10.209.105.147 ICMP Echo (ping) request -> 172.31.168.140 ICMP Echo (ping) reply -> 172.31.168.140 SSH Encrypted response -> 172.31.168.140 SSH Encrypted response
Accessing processor activity

The top command displays the dynamic real-time view of currently running tasks. It shows the resources being consumed by users and processes at a given time for a specified node.
520
Troubleshooting Using the traceroute command
To use the top command
To use the top command, enter the following:

Support> top [nodename] [iterations] [delay] nodename Displays the resources and processes at a given time for the specified node. Specifies the number of iterations you want to run. The default is three. Specifies the delay between screen updates that you want to see. The default is five seconds.
iterations
delay
For example, to show the dynamic real-time view of tasks running on the node sfs_01, enter the following:
Support> top sfs_01 1 1 top - 16:28:27 up 1 day, 3:32, 4 users, load average: 1.00, 1.00, 1.00 Tasks: 336 total, 1 running, 335 sleeping, 0 stopped, 0 zombie Cpu(s): 0.1% us, 0.1% sy, 0.0% ni, 99.7% id, 0.0% wa, 0.0% hi, 0.0% si Mem: 16405964k total, 1110288k used, 15295676k free, 183908k buffers Swap: 1052248k total, 0k used, 1052248k free, 344468k cached PID 6314 1 USER root root PR 15 16 NI 0 0 VIRT 5340 640 RES 1296 260 SHR 792 216 S R S %CPU 3.9 0.0 %MEM 0.0 0.0 TIME+ 0:00.02 0:04.86 COMMAND top init
Using the traceroute command

The traceroute command displays all of the intermediate nodes on a route between two nodes.
Troubleshooting Recovering from a non-graceful shutdown
521
To use the traceroute command
To use the traceroute command, enter the following:

Support> traceroute destination [source] [maxttl] destination The target node. To display all of the intermediate nodes located between two nodes on a network, enter the destination node. Specifies the source node name from where you want to begin the trace. Specifies the maximum number of hops. The default is seven hops.
source
maxttl
For example, to trace the route to the network host, enter the following:
Support> traceroute www.symantec.com sfs_01 10 traceroute to www.symantec.com (8.14.104.56), 10 hops max, 40 byte packets 1 10.209.104.2 0.337 ms 0.263 ms 0.252 ms 2 10.209.186.14 0.370 ms 0.340 ms 0.326 ms 3 puna-spi-core-b02-vlan105hsrp.net.symantec.com (143.127.185.130) 0.713 ms 0.525 ms 0.533 ms 4 143.127.185.197 0.712 ms 0.550 ms 0.564 ms 5 10.212.252.50 0.696 ms 0.600 ms 78.719 ms
Recovering from a non-graceful shutdown

In some cases, when a non-graceful shutdown of a node occurs (for example, during an unexpected system halt or power failure), you may receive an error message on the local node asking you to use the LINUX fsck (file system check) command to repair files on the node. Attempting to use the fsck command to repair the node is not recommended (and may not be possible). Instead, use a healthy node in the cluster to re-install FileStore software on the damaged node.
522
Troubleshooting Recovering from a non-graceful shutdown
To recover a node
1 2
Use the master account to log in to FileStore. Delete the failed node from the cluster. To delete the node, enter the following:
Cluster> delete nodename
where nodename is the name of the failed node. For example:

Cluster > delete sfs_01 This SFS node is not reachable, you have to re-install the SFS software via PXE boot after deleting it. Do you want to delete it now? (y/n)?
Enter y to confirm the deletion. After the node is deleted, you can use the PXE boot utility to re-install FileStore software on the node.
While you are physically at the node you want to recover, power it up and press F12 (or an equivalent key) to initiate a network boot. The FileStore software automatically installs on the node. For more information, see "Installing FileStore on a preconfigured node" in the Symantec FileStore Installation Guide.
Glossary
CFS (cluster file system) A file system that can be simultaneously mounted on multiple nodes. CFS is used
as the underlying file system within the Scalable File Server.

CIFS (Common Internet A network protocol that provides the foundation for Windows-based file sharing File System) console IP address
and other network utilities. The Scalable File Server supports CIFS file sharing. A virtual IP address that is configured for administrative access to the Scalable File Server cluster management console. Three or more LUNs designated to function as part of the I/O fencing mechanism of the Scalable File Server. Coordinator disks cannot be used to store user data. database API. Combined Enterprise Vault and FileStore feature to support for both WORM (write once, read many) and non-WORM archives. DAR-enabled file systems are protected against accidental or deliberate file removal and tampering. data connection in NDMP is either an NDMP interprocess communication mechanism (for local operations) or a TCP/IP connection (for 3-way operations).
coordinator disks
CTDB (Clustered Trivial A cluster implementation of the TDB (Trivial database) based on the Berkeley Database) DAR (Data Archive and Retention)
data connection (NDMP) The connection between the two NDMP servers that carry the data stream. The
data service (NDMP)
An NDMP service that transfers data between primary storage and the data connection. A unidirectional byte stream of data that flows over a data connection between two peer NDMP services in an NDMP session. For example, in a backup, the data stream is generated by the data service and consumed by the tape service. The data stream can be backup data, recovered data, etc. An application that controls the NDMP session. In NDMP there is a master-slave relationship. The data management application is the session master; the NDMP services are the slaves. In NDMP versions 1, 2, and 3 the term "NDMP client" is used instead of data management application. A node that contains the authoritative copy of a TDB (Trivial database) record. An enhancement technique that provides the load balancing and path failover to disks that are connected to the Scalable File Server cluster nodes.
data stream (NDMP)
data management application (NDMP)
DM (Data Master) DMP (Dynamic Multipathing)
524
Glossary
DST (Dynamic Storage Tiering)
A feature that allows the files and directories to be automatically and seamlessly transferred to different types of storage technology that may originate from different hardware vendors. An ISO image or media that contains one or more additional drivers that are needed to install the Scalable File Server on specific hardware, if the base Scalable File Server installer did not include the necessary drivers. The capability to have the service of a failed computer resource made available automatically with little or no interruption. With the Scalable File Server configured as a cluster, the services provided by any failed node are automatically provided by the remainder of functioning nodes. A file system quota for inode and block consumption that can be established for individual users or groups. When the hard limit is reached no further inodes or blocks can be allocated. An optional Scalable File Server feature that configures a specific group of LUNs with (to have) an additional layer of data protection. This extra protection prevents data loss from occurring in the rare case that the redundant cluster interconnect and public low-priority interconnect fails. A NetBackup server that provides storage within a master and a media server cluster. See also NetBackup. A file system that is constructed and managed by a technique for automatically maintaining one or more copies of the file system, using separate underlying storage for each copy. If a storage failure occurs, then access is maintained through the remaining accessible mirrors. data access to network-capable clients. An open standard protocol that is used to control the data backup and the recovery communications between primary and secondary storage in a heterogeneous network environment. NDMP specifies a common architecture for the backup of network file servers. It enables the creation of a common agent which a centralized program can use to back up the data on file servers that run on different platforms. An application that controls the NDMP session. See also data management application. The host computer system that executes the NDMP server application. Data is backed up from the NDMP host to either a local tape drive or to a backup device on a remote NDMP host. An instance of one or more distinct NDMP services controlled by a single NDMP control connection. Thus a data/tape/SCSI server is an NDMP server providing data, tape, or SCSI services.
DUD (Driver Update Disk)
failover
hard limit
I/O fencing
media server
mirrored file system
NAS (Network Attached A file-level computer data storage that is connected to a network that provides Storage) NDMP (Network Data Management Protocol)
NDMP client
NDMP host
NDMP server
Glossary
525
NDMP service
The state computer on the NDMP host accessed with the Internet protocol and controlled using the NDMP protocol. This term is used independently of implementation. The three types of NDMP services are: data service, tape service, and SCSI service. The configuration of one data management application and two NDMP services to perform a data management operation such as a backup or a recovery. A Veritas software product that backs up, archives, and restores files, directories, or raw partitions that reside on a client system. A protocol that lets the user on a client computer access files over a network. To the client's applications the files appear as if they resided on one of the local devices. A feature that lets a customer use the Network File System (NFS) advisory client locking feature in parallel with core Cluster File System (CFS) global lock management. An NFS sharing option. Does not map requests from the UID 0. This option is on by default. A protocol for synchronizing computer system clocks over packet-switched, variable-latency data networks. A file-locking mechanism that is designed to improve performance by controlling the caching of files on the client. An internal IP network that is used by the Scalable File Server to facilitate communications between the Scalable File Server server nodes. available data storage devices (such as hard disks) or installed operating systems. A node that contains fcntl-locks on distributed file systems and initiates the recovery process. A technique in which a DNS server, not a dedicated computer, performs the load balancing. An open-source implementation of the SMB file sharing protocol. It provides file and print services to SMB/CIFS clients. A specification of a file system or proper subset of a file system, which supports shared access to a file system through an NFS or CIFS server. The specification defines the folder or directory that represents the file system along with access characteristics and limitations. A point-in-time image or replica of a file system that looks identical to the file system from which the snapshot was taken.
NDMP session
NetBackup
NFS (Network File System)
NFS lock management
no root_squash
NTP (Network Time Protocol) oplocks
private interconnect
PXE (Pre-boot eXecution An environment to boot computers using a network interface independent of Environment) RM (Recovery Master)
round robin DNS
Samba
share
snapshot
526
Glossary
soft limit
A file system quota for inode and block consumption that can be established for individual users or groups. If a user exceeds the soft limit, there is a grace period, during which the quota can be exceeded. After the grace period has expired, no more inodes or data blocks can be allocated. A logical construct that contains one or more LUNs from which file systems can be created. The granularity at which data is stored on one drive of the array before subsequent data is stored on the next drive of the array. A standard for forwarding log messages in an IP network. The term refers to both the syslog protocol and the application sending the syslog messages. An NDMP service that transfers data between secondary storage and the data connection and allows the data management application to manipulate and access the secondary storage. A 64-bit identifier that is used in Fibre Channel networks to uniquely identify each element in the network (i.e., nodes and ports).
storage pool
stripe unit
syslog
tape service (NDMP)
WWN (World Wide Name)
Index
A
about Active Directory (AD) 247 administering FileStore cluster's LDAP client 158 backup configurations 417 bonding Ethernet interfaces 130 changing share properties 286 configuring CIFS for AD domain mode 253 configuring disks 69 configuring Ethernet interfaces 143 configuring FileStore for CIFS 234 configuring IP addresses 137 configuring iSCSI targets 114 configuring locally saved configuration files 448 configuring routing tables 146 configuring storage pools 64 creating and maintaining file systems 188 creating file systems 191 data archive and retention 119 disk lists 76 DNS 133 excluding file extensions from Symantec AntiVirus for FileStore scans 482 FTP 333 FTP local user 348 FTP local user set 351 FTP server 335 FTP session 346 FTP set 337 I/O fencing 82 installing patches 468 iostat 507 IP commands 137 iSCSI 107 LDAP 151 leaving AD domain 258 leaving NT domain 245 load balancing for the normal clustering mode 298 local replication initialization 72
about (continued) managing CIFS shares 282 managing home directories 302 NDMP policies 406 NDMP supported configurations 405 Network Data Management Protocol 403 network services 128 network traffic details 517 NFS file sharing 175 NIS 160 option commands 457 reconfiguring CIFS service 279 retrieving the NDMP data 413 scheduling a Symantec AntiVirus for FileStore scan job 496 services command 513 setting NTLM 262 setting trusted domains 265 setting up file system alerts 227 snapshot schedules 211 snapshots 205 storage provisioning and management 62 storing account information 276 support user 45 Symantec AntiVirus for FileStore 476 Symantec AntiVirus for FileStore commands 477 Symantec AntiVirus for FileStore LiveUpdate 484 Symantec AntiVirus for FileStore manual scan commands 494 Symantec AntiVirus for FileStore quarantine commands 490 troubleshooting 504 types of patches 469 VLAN interfaces 165 accessing FileStore product documentation 29 man pages 40 processor activity 519 Active Directory setting the trusted domains for 275
528
Index
Active Directory (AD) about 247 configuring FileStore to authenticate to an AD domain controller 248 joining FileStore to 251 verifying FileStore has joined successfully 253 AD domain mode changing domain settings 259 configuring CIFS 253 security settings 259 setting domain 255 setting domain user 255 setting security 255 starting CIFS server 255 AD interface using 262 AD trusted domains disabling 275 add local user FTP 350 adding a severity level to an email group 373 a syslog server 379 an email address to a group 373 an email group 373 CIFS share 286 disks 70 external NetBackup master server to work with FileStore 400 filter to a group 373 IP address to a cluster 139 mapping from a virtualPath to a realPath 366 mirror to a file system 195 mirror to a tier of a file system 429 mirrored tier to a file system 427 mirrored-striped tier to a file system 427 NetBackup Enterprise Media Manager (EMM) server 400 NetBackup media server 400 new nodes to the cluster 54 NFS share 177 second tier to a file system 427 SNMP management server 382 striped tier to a file system 427 striped-mirror tier to a file system 427 users naming requirements for 32 VLAN interfaces 166
administering FileStore cluster's LDAP client about 158 aio_fork option setting 324 alerts file system unsetting 229 aliases displaying configured on the server 367 allowing metadata information to be written on the secondary tier 441 specified users and groups access to the CIFS share 289 attaching replication storage pool to a FileStore cluster 75 audit logs about 387 configuring 389 disabling for a file system 391 Auto-Protect configuring on file systems 481482
B
backup configurations about 417 backup services displaying the status of 418 starting 418 stopping 418 bind distinguished name setting for LDAP server 154 bonding Ethernet interfaces 132 bonding Ethernet interfaces about 130
C
cache object destroying for an instant rollback 227 changing an IP address to online on any running node 139 configuration of an Ethernet interface 145 DMP I/O policy 459 domain settings 245 domain settings for AD domain mode 259 local CIFS user password 327 NFS daemons 459
Index
529
changing (continued) ninodes cache size 459 security settings 247 security settings after CIFS server is stopped 247 share properties about 286 status of a file system 202 support user password 46 checking and repairing a file system 202 I/O fencing status 84 on the status of the NFS server 170 support user status 46 CIFS allowing specified users and groups access to the CIFS share 289 configuring schema extensions 269 denying specified users and groups access to the CIFS share 290 export options 284 modifying an existing CIFS share 291 setting the log level 505 standalone mode 236 using multi-domain controller support 258 CIFS and NFS protocols share directories 181 sharing file systems 294 CIFS clustering modes about 234 switching from ctdb to normal 316 switching from normal to ctdb 313 CIFS home directories displaying the quota values for 105 quotas 96 using quotas for 98 CIFS operating modes about 234 CIFS server changing security settings after stopped 247 configuring with the LDAP backend 274 starting 280 CIFS server status standalone mode 237 CIFS service standalone mode 237 CIFS share adding 286 deleting 293 exporting as a directory 310
CIFS share (continued) exporting the same file system/directory as a different CIFS share 312 modifying existing 292 splitting 300 CIFS share and home directory migrating from ctdb to normal clustering mode 321 CIFS shares and home directories migrating from ctdb clustering modes 317 migrating from normal to ctdb clustering mode 319 CIFS snapshot exporting 292 CIFS/NFS sharing mapping user names 297 clearing DNS domain names 135 DNS name servers 135 LDAP configured settings 154 CLI logging in to 33 client configurations displaying 159 LDAP server 159 cluster adding an IP address to 139 adding new nodes 54 adding the new node to 56 changing an IP address to online for any running node 139 deleting a node from 57 displaying a list of nodes 52 displaying all the IP addresses for 139 rebooting a nodes or all nodes 59 shutting down a node or all nodes in a cluster 58 clustering modes ctdb 309 command history displaying 47 Command-Line Interface (CLI) how to use 33 commands HTTP alias 365 HTTP document root mapping 367 HTTP server 360 configurable list of all HTTP options and their values 365
530
Index
configuration of an Ethernet interface changing 145 configuration files deleting the locally saved 449 viewing locally saved 449 configuration settings exporting either locally or remotely 449 importing either locally or remotely 449 configuring AD schema with CIFS-schema extensions 269 audit logs 389 Auto-Protect on file systems 481482 backup using NetBackup 420 CIFS for standalone mode 236 CIFS server with the LDAP backend 274 data archive and retention 123 email groups 371 file extensions in Symantec AntiVirus for FileStore configuration file 483 FileStore for CIFS 234 FileStore to authenticate to an AD domain controller 248 HTTP server 359 IP routing 148 iSCSI device 110 iSCSI discovery 111 iSCSI initiator 108 iSCSI initiator name 109 iSCSI targets 116 masquerade as third-party policy 407 NDMP backup method policy 407 NDMP failure resilient policy 407 NDMP overwrite policy 407 NDMP recursive restore policy 407 NDMP restore DST policy 407 NDMP send history policy 407 NDMP update dumpdates policy 407 NDMP use snapshot policy 407 NetBackup virtual IP address 402 NetBackup virtual name 403 NSS 163 NSS lookup order 164 Symantec AntiVirus for FileStore on all the nodes in the cluster 479 Symantec AntiVirus for FileStore on the cluster's nodes 480 VLAN interfaces 166
configuring (continued) Windows Active Directory as an LDAP IDMAP backend 268 configuring CIFS NT domain mode 240 configuring disks about 69 configuring Ethernet interfaces about 143 configuring IP addresses about 137 configuring iSCSI targets about 114 configuring locally saved configuration files about 448 configuring routing tables about 146 configuring storage pools about 64 coordinating cluster nodes to work with NTP servers 454 coordinator disks replacing 84 core strengths FileStore 25 CPU utilization report generating 508 creating full-sized rollback 220 local CIFS group 330 local CIFS user 327 Master, System Administrator, and Storage Administrator users 42 mirrored file systems 192 mirrored-stripe file systems 192 shared cache object 225 simple file systems 192 snapshot schedules 213 snapshots 206 space-optimized instant rollbacks 219 storage pools 66 striped file systems 192 striped-mirror file systems 192 users 42 creating and maintaining file systems about 188 creating file systems about 191
Index
531
ctdb clustering mode about 309 directory-level share support 310 load balancing 300 switching the clustering mode 313 current Ethernet interfaces and states displaying 144 current users displaying list 42
D
data archive and retention about 119 configuring 123 interaction with other applications 121 debugging information retrieving and sending 506 decreasing size of a file system 201 default passwords resetting Master, System Administrator, and Storage Administrator users 42 defragmenting file systems 204 delete local user FTP 350 deleting a node from the cluster 57 already configured SNMP management server 382 CIFS share 293 configured email server 373 configured NetBackup media server 400 email address from a specified group 373 email groups 373 filter from a specified group 373 home directories 308 home directory of given user 308 local CIFS group 330 local CIFS user 327 locally saved configuration file 449 mapping that is visible to clients as a virtualPath 367 NFS options 184 route entries from routing tables of nodes in cluster 148 severity from a specified group 373 snapshot schedules 215
deleting (continued) syslog server 379 users 42 VLAN interfaces 166 denying specified users and groups access to the CIFS share 290 destroying a file system 204 cache object of an instant rollback 227 I/O fencing 84 instant rollbacks 224 snapshots 209 storage pools 66 detached pool set renaming 74 detached pools displaying 75 device utilization report generating 508 directories displaying exported 176 unexporting the share 184 directory-level share support ctdb clustering mode 310 disabling AD trusted domains 275 audit logs for a file system 391 creation of home directories 308 DNS settings 135 FastResync option 198 I/O fencing 84 LDAP clients configurations 159 NIS clients 161 NTLM 264 NTP server 454 Partition Secure Notification (PSN) feature 231 quota limits used by snapshots 209 support user account 46 disk formatting 81 disk lists about 76 disks adding 70 removing 70 displaying all the aliases configured on the server 367
532
Index
displaying (continued) all the IP addresses for cluster 139 command history 47 current Ethernet interfaces and states 144 current HTTP sessions on each node 363 current list of SNMP management servers 382 current root directory for the HTTP server 368 current version 467 detached pools 75 DMP I/O policy 459 DNS settings 135 events on the console 381 existing email groups or details 373 exported directories 176 file system 229 file systems that can be exported 173 files moved and/or pruned by running a policy 440 FTP server settings 335 home directory usage information 307 information for all disk devices for nodes in a cluster 77 LDAP client configurations 159 LDAP configured settings 154 license information 509 list of all configurable HTTP options and their values 365 list of current users 42 list of DST file systems 432 list of nodes in a cluster 52 list of syslog servers 379 local CIFS group 330 local CIFS user 327 NDMP backup method 414 NDMP failure resilient data 414 NDMP masquerade as third-party 414 NDMP overwrite data 414 NDMP recursive restore data 414 NDMP restore DST data 414 NDMP send history data 414 NDMP update dumpdates data 414 NDMP use snapshot data 414 NDMP variables 412 NetBackup configurations 418 network configuration and statistics 129 NFS daemons 459 NFS statistics 172 ninodes cache size 459 NIS-related commands 161
displaying (continued) node-specific network traffic details 518 NSS configuration 164 option tunefstab 459 policy of each tiered file system 434 routing tables of the nodes in the cluster 148 schedules for all tiered file systems 439 share properties 288 snapshot quotes 209 snapshot schedules 215 snapshots 208 snapshots that can be exported 173 status of backup services 418 status of the NTP server 454 Symantec AntiVirus for FileStore configuration 478 Symantec AntiVirus for FileStore logs 478 Symantec AntiVirus for FileStore stats 478 system date and time 445 system statistics 455 tier location of a specified file 432 time interval or number of duplicate events for notifications 385 values of the configured SNMP notifications 382 values of the configured syslog server 379 VLAN interfaces 166 DMP I/O policy changing 459 displaying 459 resetting 459 DNS about 133 domain names clearing 135 name servers clearing 135 specifying 135 settings disabling 135 displaying 135 enabling 135 domain setting 280 setting user name 280 domain controller setting 280 domain name for the DNS server setting 135
Index
533
domain settings changing 245 domain user NT domain mode 242 drivers upgrading 465 DUD driver updates uninstalling 472
exporting (continued) configuration settings 449 directory as a CIFS share 310 events in syslog format to a given URL 386 network traffic details 518 NFS snapshot 184 same file system/directory as a different CIFS share 312 SNMP MIB file to a given URL 382
E
email address adding to a group 373 deleting from a specified group 373 email groups about 371 adding 373 deleting 373 displaying existing and details 373 email server deleting the configured email server 373 obtaining details for 373 setting the details of external 373 enabling DNS settings 135 FastResync for a file system 197 I/O fencing 84 LDAP client configurations 159 NIS clients 161 NTLM 264 NTP server 454 Partition Secure Notification (PSN) feature 231 quota limits used by snapshots 209 support user account 46 Ethernet interfaces bonding 132 changing configuration of 145 event notifications displaying time interval for 385 event reporting setting events for 385 events displaying on the console 381 excluding PCI IDs 510511 export options CIFS 284 exporting audit events in syslog format to a given URL 386 CIFS snapshot 292
F
file data accessing by way of the HTTP server 359 file extensions configuring in Symantec AntiVirus for FileStore configuration file 483 excluding from Symantec AntiVirus for FileStore scans 482 file system alerts about setting up 227 displaying 229 setting 227 unsetting 229 file system quotas for enabling, disabling, and displaying 89 setting and displaying 91 file systems adding a mirror to 195 changing the status of 202 checking and repairing 202 creating 192 decreasing the size of 201 defragmenting 204 destroying 204 disabling FastResync option 198 DST displaying 432 enabling FastResync 197 increasing the size of 199 listing with associated information 191 quotas 87 removing a mirror from 195 restoring from an instant rollback 221 that can be exported displayed 173 FileStore about 21 core strengths of 25 key features 21
534
Index
FileStore (continued) product documentation 29 Web resources 29 FileStore Dynamic Storage Tiering (DST) about 422 FileStore software installing onto a new node 54 filter about 371 adding to a group 373 deleting from a specified group 373 forcefully importing pools 82 formatting a disk 81 FTP about 333 add local user 350 delete local user 350 implementing command changes 345 local user password 350 local user set download bandwidth 353 local user set home directory 353 local user set maximum connections 353 local user set maximum disk usage 353 local user set maximum files 353 local user set upload bandwidth 353 logupload 348 server start 336 server status 336 server stop 336 session show 346 session showdetail 346 session terminate 346 set allow delete 341 set anonymous login 341 set anonymous logon 341 set anonymous write 341 set home directory path 341 set listen port 341 set maximum connections per client 341 set non-secure logins 341 set security 341 show local users 350 FTP local user about 348 FTP local user set about 351
FTP server about 335 settings displaying 335 FTP session about 346 FTP set about 337
G
generating CPU utilization report 508 device utilization report 508 group membership managing 327 GUI-related operations updating 507
H
history command using 47 home directories setting up 305 home directory file systems setting 303 home directory of given user deleting 308 home directory usage information displaying 307 hostname or IP address setting for LDAP server 154 how to use Command-Line Interface (CLI) 33 HTTP alias commands 365 HTTP server commands about 360 configuring for accessing file data 359 displaying the current root directory for 368 displaying the status for 361 document root mapping commands 367 set commands about 361 setting the root directory 368 starting 360 stopping 361 HTTP sessions displaying on each node 363
Index
535
I
I/O fencing about 82 checking status 84 destroying 84 disabling 84 enabling 84 idle threads setting the maximum number for handling request spikes 363 setting the minimum number for request spikes 363 implementing FTP command changes 345 importing configuration settings 449 pools forcefully 82 increasing LUN storage capacity 80 size of a file system 199 initiating host discovery of LUNs 81 installation states and conditions about 50 installing patches 470 about 468 instant recovery NetBackup 397 instant rollbacks about 217 creating a shared cache object 225 creating full-sized 220 creating space-optimized 219 destroying 224 listing 221 listing cache objects 226 making go offline 223 making go online 223 refreshing from a file system 222 restoring a file system from 221 iostat about 507 IP addresses adding to a cluster 139 displaying for the cluster 139 modifying 139 removing from the cluster 139 IP commands about 137
IP routing configuring 148 iSCSI about 107 iSCSI device configuring 110 iSCSI discovery configuring 111 iSCSI initiator configuring 108 iSCSI initiator name configuring 109 iSCSI targets configuring 116
J
joining FileStore to Active Directory (AD) 251
L
LDAP about 151 before configuring settings 151 configuring server settings 152 setting up as an IDMAP backend using the FileStore CLI 274 LDAP password hash algorithm setting password for 154 LDAP server clearing configured settings 154 disabling client configurations 159 displaying client configurations 159 displaying configured settings 154 enabling client configurations 159 setting over SSL 154 setting port number 154 setting the base distinguished name 154 setting the bind distinguished name 154 setting the hostname or IP address 154 setting the password hash algorithm 154 setting the root bind DN 154 setting the users, groups, and netgroups base DN 154 leaving AD domain 258 NT domain 245 license information displaying 509
536
Index
licensing Symantec AntiVirus for FileStore 477 list of DST file systems displaying 432 list of nodes displaying in a cluster 52 listing all file systems and associated information 191 all of the files on the specified tier 431 cache objects for instant rollbacks 226 free space for storage pools 66 instant rollbacks 221 Partition Secure Notification (PSN) online file systems that have this feature enabled 232 storage pools 66 load balancing ctdb clustering mode 300 local CIFS groups creating 330 deleting 330 displaying 330 managing 329 local CIFS user creating 327 deleting 327 displaying 327 local CIFS user password changing 327 local replication initialization 72 local user and groups managing 326 local user password FTP 350 local user set download bandwidth FTP 353 local user set home directory FTP 353 local user set maximum connections FTP 353 local user set maximum disk usage FTP 353 local user set maximum files FTP 353 local user set upload bandwidth FTP 353 logging in to CLI 33 login Technical Support 517
logupload FTP 348 LUN storage capacity increasing 80 LUNs initiating host discovery 81
M
man pages how to access 40 managing CIFS shares 282 group membership 327 home directories 302 local CIFS groups 329 local users and groups 326 mapping deleting that is visible to clients as a virtualPath 367 from a virtualPath to a realPath 366 masquerade as third-party policy configuring 407 Master, System Administrator, and Storage Administrator users creating 42 metadata information allowing to be written on the secondary tier 441 restricting to the primary tier only 442 migrating CIFS share and home directory from ctdb to normal clustering mode 321 CIFS shares and home directories 317 CIFS shares and home directories from normal to ctdb clustering mode 319 mirrored file systems creating 192 mirrored tier adding to a file system 427 mirrored-stripe file systems creating 192 mirrored-striped tier adding to a file system 427 modifying an existing CIFS share 291 an IP address 139 existing CIFS share 292 option tunefstab 459 policy of a tiered file system 434 schedule of a tiered file system 439
Index
537
modifying (continued) snapshot schedules 215 more command using 453 mounting snapshots 209 moving disks from one storage pool to another 70
N
naming requirements for adding users 32 NDMP backup method displaying 414 NDMP backup method policy configuring 407 NDMP failure resilient data displaying 414 NDMP failure resilient policy configuring 407 NDMP masquerade as third-party displaying 414 NDMP overwrite data displaying 414 NDMP overwrite policy configuring 407 NDMP policies about 406 restoring 416 NDMP recursive restore data displaying 414 NDMP recursive restore policy configuring 407 NDMP restore DST data displaying 414 NDMP restore DST policy configuring 407 NDMP send history data displaying 414 NDMP send history policy configuring 407 NDMP supported configurations about 405 NDMP update dumpdates data displaying 414 NDMP update dumpdates policy configuring 407 NDMP use snapshot data displaying 414
NDMP use snapshot policy configuring 407 NDMP variables displaying 412 NetBackup about 395 configuring NetBackup virtual IP address 402 configuring virtual name 403 displaying configurations 418 instant recovery 397 snapshot client 396 snapshot methods 396 NetBackup EMM server. See NetBackup Enterprise Media Manager (EMM) server NetBackup Enterprise Media Manager (EMM) server adding to work with FileStore 400 NetBackup master server configuring to work with FileStore 400 NetBackup media server adding 400 deleting 400 netbios aliases for the CIFS server setting 325 network configuration and statistics 129 testing connectivity 513 Network Data Management Protocol about 403 network services about 128 network traffic details about 517 exporting 518 NFS daemons changing 459 displaying 459 NFS file sharing about 175 NFS options deleting 184 NFS server checking on the status 170 starting 170 stopping 170 NFS share adding 177 NFS snapshot exporting 184
538
Index
NFS statistics displaying 172 ninodes cache size changing 459 displaying 459 NIS about 160 clients disabling 161 enabling 161 domain name setting on all the nodes of cluster 161 related commands displaying 161 server name setting on all the nodes of cluster 161 node adding to the cluster 54, 56 in a cluster displaying information for all disk devices 77 installing FileStore software onto 54 node-specific network traffic details displaying 518 normal clustering mode load balancing 298 NSS configuring 163 displaying configuration 164 lookup order configuring 164 NT domain mode configuring CIFS 240 domain user 242 setting domain 242 setting domain controller 242 setting security 242 setting the workgroup name 242 starting CIFS server 242 NTLM disabling 264 enabling 264 NTP server coordinating cluster nodes to work with 454 disabling 454 displaying the status of 454 enabling 454
O
obtaining details of the configured email server 373 offline making an instant rollback go offline 223 online making an instant rollback go 223 option commands about 457 option tunefstab displaying 459 modifying 459
P
Partition Secure Notification (PSN) feature about 230 disabling 231 enabling 231 listing the online file systems that have this feature enabled 232 password changing a user's password 42 patch level displaying current versions of 467 patches installing 470 synchronizing 472 types of 469 uninstalling 471 upgrading 465 PCI excluding IDs 511 exclusion 510 policies about 426 displaying files moved and/or pruned by running 440 displaying for each tiered file system 434 modifying for a tiered file system 434 relocating from a tiered file system 438 removing from a tiered file system 434 running for a tiered file system 434 preserving snapshot schedules 215 printing WWN information 81 privileges about 31 processor activity accessing 519
Index
539
Q
quota commands enabling, disabling, and displaying file system quotas 89 for setting and displaying file system quotas 91 quota limits enabling or disabling snapshot 209 quotas CIFS home directories 96 displaying the quota values for CIFS home directories 105 for file systems 87 using for CIFS home directories 98
R
rebooting a node or all nodes in cluster 59 reconfiguring CIFS service about 279 recovering from a non-gracefule shutdown 521 refreshing instant rollbacks from a file system 222 regions and time zones setting 445 relocating policy of a tiered file system 438 removing disks 70 IP address from the cluster 139 mirror from a file system 195 mirror from a tier spanning a specified disk 429 mirror from a tier spanning a specified pool 429 mirror from a tiered file system 429 policy of a tiered file system 434 schedule of a tiered file system 439 snapshot schedules 215 tier from a file system 428 renaming detached pool set 74 storage pools 66 replacing coordinator disks 84 replication storage pool attaching 75 resetting default passwords Master, System Administrator, and Storage Administrator users 42
resetting (continued) DMP I/O policy 459 restoring a file system from an instant rollback 221 ndmp policies 416 restricting metadata information to the primary tier only 442 retrieving debugging information 506 retrieving the NDMP data about 413 roles about 31 root directory setting for the HTTP server 368 route entries deleting from routing tables 148 routing tables of the nodes in the cluster displaying 148 running policy of a tiered file system 434
S
schedule displaying for all tiered file systems 439 modifying for a tiered file system 439 removing from a tiered file system 439 scheduling Symantec AntiVirus for FileStore scan jobs 496, 498 second tier adding to a file system 427 security standalone mode 237 security settings AD domain mode 259 changing 247 sending debugging information 506 server start FTP 336 server status FTP 336 server stop FTP 336 server threads setting the initial number 364
540
Index
server threads (continued) setting the maximum number in each server process 364 servers adding LiveUpdate servers 486 services command about 513 using 515 session show FTP 346 session showdetail FTP 346 session terminate FTP 346 set allow delete FTP 341 set anonymous login FTP 341 set anonymous logon FTP 341 set anonymous write FTP 341 set commands HTTP server 361 set home directory path FTP 341 set listen port FTP 341 set maximum connections per client FTP 341 set non-secure logins FTP 341 set security FTP 341 setting AD domain mode 255 aio_fork option 324 base distinguished name for the LDAP server 154 bind distinguished name for LDAP server 154 CIFS log level 505 details of the external email server 373 domain 280 domain controller 280 domain name for the DNS server 135 domain user name 280 events for event reporting 385 file system alerts 227 filter of the syslog server 379
setting (continued) home directory file systems 303 initial number of server threads 364 LDAP as an IDMAP backend using the FileStore CLI 274 LDAP IDMAP backend to hash for accessing CIFS 267 LDAP IDMAP backend to ldap for trusted domain access to CIFS 266 LDAP IDMAP backend to rid for access to CIFS 265 LDAP password hash algorithm 154 LDAP server hostname or IP address 154 LDAP server over SSL 154 LDAP server port number 154 LDAP users, groups, and netgroups base DN 154 maximum number of idle threads for handling request spikes 363 maximum number of threads in each server process 364 maximum number to be created 364 minimum number of idle threads for request spikes 363 netbios aliases for the CIFS server 325 NIS domain name on all the nodes of cluster 161 NT domain mode 242 NT domain mode domain controller 242 NTLM 262 regions and time zones 445 root bind DN for the LDAP server 154 severity of the syslog server 379 SNMP filter notifications 382 SNMP severity notifications 382 Symantec AntiVirus for FileStore action policy 493 system date and time 445 the NIS server name on all the nodes of cluster 161 trusted domains 265 trusted domains for the Active Directory 275 workgroup name 242 setting domain user AD domain mode 255 setting security AD domain mode 255 NT domain mode 242 setting up home directories 305
Index
541
severity levels about 371 adding to an email group 373 severity notifications setting 382 share directories CIFS and NFS protocols 181 share properties displaying 288 shared cache object creating 225 sharing file systems using CIFS and NFS protocols 294 show local users FTP 350 showing snapshot schedules 215 shutdown recovering from a non-graceful 521 shutting down node or all nodes in a cluster 58 snapshot methods NetBackup 396 snapshot schedules about 211 creating 213 deleting 215 displaying 215 modifying 215 preserving 215 removing 215 showing 215 snapshots about 205 creating 206 destroying 209 displaying 208 displaying quotas 209 enabling or disabling quota limits 209 mounting 209 that can be exported displayed 173 unmounting 209 SNMP filter notifications setting 382 management server adding 382 deleting configured 382
SNMP (continued) management server (continued) displaying current list of 382 MIB file exporting to a given URL 382 notifications displaying the values of 382 server setting severity notifications 382 specified group deleting a severity from 373 specifying DNS name servers 135 splitting a CIFS share 300 SSL setting the LDAP server for 154 standalone mode CIFS server status 237 CIFS service 237 security 237 starting backup services 418 CIFS server 280 HTTP server 360 NFS server 170 starting CIFS server AD domain mode 255 NT domain mode 242 status displaying for the HTTP server 361 stopping backup services 418 HTTP server 361 NFS server 170 storage pools creating 66 destroying 66 listing 66 listing free space 66 moving disks from one to another 70 renaming 66 storage provisioning and management about 62 storing account information 276 user and group accounts in LDAP 278 user and group accounts locally 278 striped file systems creating 192
542
Index
striped tier adding to a file system 427 striped-mirror file systems creating 192 striped-mirror tier adding to a file system 427 support user about 45 support user account disabling 46 enabling 46 support user password changing 46 support user status checking 46 swap command using 456 switching CIFS clustering modes from normal to ctdb 313 ctdb clustering mode 313 from ctdb to normal clustering mode 316 Symantec AntiVirus for FileStore about 476 commands about 477 configuring on the cluster's nodes 480 displaying configuration 478 displaying logs 478 displaying stats 478 licensing 477 manual scan commands 494 quarantine commands about 490 scheduling scan jobs 498 setting action policies 493 using manual scan commands 495 using quarantine commands 491 Symantec AntiVirus for FileStore LiveUpdate about 484 adding LiveUpdate servers 486 Symantec Enterprise Vault Partition Secure Notification (PSN) 230 synchronizing patches 472 syslog event logging about 378 syslog format exporting audit events to a given URL 386 exporting events to a given URL 386 syslog server adding 379 deleting 379
syslog server (continued) displaying the list of 379 displaying the values of 379 setting the filter of 379 setting the severity of 379 system date and time displaying 445 setting 445 system statistics displaying 455
T
technical support login 517 testing network connectivity 513 threads setting the maximum number to be created 364 tier adding a tier to a file system 429 displaying location of a specified file 432 listing all of the specified files on 431 removing a mirror from 429 removing a mirror spanning a specified pool 429 removing from a file system 428 removing from a tier spanning a specified disk 429 traceroute command using 520 troubleshooting about 504 trusted domains allowing access to CIF when setting an LDAP IDMAP backend to hash 267 allowing access to CIFS when setting an LDAP IDMAP backend to ldap 266 allowing access to CIFS when setting an LDAP IDMAP backend to rid 265
U
unexporting share of exported directory 184 uninstalling DUD driver updates 472 patches 471 unmounting snapshots 209 updating GUI-related operations 507
Index
543
upgrading patches or drivers 465 user and group accounts in LDAP storing 278 user and group accounts locally storing 278 user names mapping for CIFS/NFS sharing 297 user roles and privileges about 31 users adding new 32 changing passwords 42 creating 42 deleting 42 using AD interface 262 history command 47 more command 453 multi-domain controller support in CIFS 258 services command 515 swap command 456 Symantec AntiVirus for FileStore manual scan commands 495 Symantec AntiVirus for FileStore quarantine commands 491 traceroute command 520
WWN information printing 81
V
verifying FileStore has joined Active Directory (AD) 253 viewing list of locally saved configuration files 449 virtual IP address configuring or changing for NetBackup 402 virtual name configuring for NetBackup 403 VLAN about interfaces 165 adding interfaces 166 configuring interfaces 166 deleting interfaces 166 displaying interfaces 166
W
Web resources for FileStore 29 Windows Active Directory configuring as an LDAP IDMAP backend 268

Symantec™ FileStore Command-Line Administrator&#39;s Guide

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Symantec™ FileStore Command-Line Administrator&#39;s Guide

Hochgeladen von

Copyright:

Verfügbare Formate

Symantec FileStore Command-Line Administrator's Guide

Symantec FileStore Command-Line Administrators Guide

Symantec Corporation 350 Ellis Street Mountain View, CA 94043 http://www.symantec.com

Contacting Technical Support

Product release level

Licensing and registration

Support agreement resources

About Symantec Connect

Additional enterprise services

Technical Support ............................................................................................... 4 Chapter 1 Introducing Symantec FileStore ....................................... 21

Creating users based on roles .......................................... 31

Displaying and adding nodes to a cluster ...................... 49

Configuring storage ............................................................ 61

Configuring Symantec FileStore network settings .......................................................................... 127

Configuring your NFS server ........................................... 169

Creating and maintaining NFS shares

......................... 175 175 176 177 181 184 184

Creating and maintaining file systems

Using Symantec FileStore as a CIFS server .................. 233

Configuring your FTP server ............................................ 333

Configuring your HTTP server ......................................... 359

Configuring event notifications and audit logs ........... 369

Configuring backup ........................................................... 393

Configuring Symantec FileStore Dynamic Storage Tiering ............................................................................ 421

438 439 440 441 442

Configuring system information .................................... 443

Upgrading Symantec FileStore ....................................... 465

Using Symantec AntiVirus for FileStore ....................... 475

Troubleshooting ................................................................. 503

Glossary ............................................................................................................. 523 Index ................................................................................................................... 527

Introducing Symantec FileStore

Introducing Symantec FileStore About FileStore features

About FileStore features

Introducing Symantec FileStore About FileStore features

Active/Active Scalable NFS

NFS Lock Management (NLM)

Storage Master System

Introducing Symantec FileStore About FileStore features

High-performance data replication

Integrated content scanning using Symantec AntiVirus for FileStore

Introducing Symantec FileStore About the core strengths of FileStore

About the core strengths of FileStore

Introducing Symantec FileStore FileStore key benefits and other applications

FileStore key benefits and other applications

High performance scaling and seamless growth

Introducing Symantec FileStore FileStore key benefits and other applications

Example of near-linear performance scaling with FileStore

Consolidating and reducing costs of storage

Introducing Symantec FileStore FileStore key benefits and other applications

Enabling scale-out compute clusters and heterogeneous sharing of data

Introducing Symantec FileStore FileStore on the Web

FileStore on the Web

Using the FileStore product documentation

Find additional information at this location: http://www.symantec.com/business/support/overview.jsp?pid=55079

Introducing Symantec FileStore Using the FileStore product documentation

Creating users based on roles

About user roles and privileges

Table 2-1 User role

User roles within FileStore Description

About the naming requirements for adding new users

Naming requirements for adding new users Description

Table 2-2 Guideline

Naming requirements for adding new users (continued) Description

Symantec™ FileStore Command-Line Administrator's Guide

Symantec™ FileStore Command-Line Administrator's Guide