268
Symantec™ FileStore Web GUI Administrator's Guide 5.7
Symantec™ FileStore WebGUI Administrator's Guide
5.7
Symantec FileStore Web GUI Administrator’s GuideThe software described in this book is furnished under a license agreement and may be usedonly in accordance with the terms of the agreement.
Product version: 5.7
Document version: 5.7.0
Legal NoticeCopyright © 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 ofSymantec corporation or its affiliates in the U.S. and other countries. Other names may betrademarks of their respective owners.
This Symantec product may contain third party software for which Symantec is requiredto provide attribution to the third party (“Third Party Programs”). Some of the Third PartyPrograms are available under open source or free software licenses. The License Agreementaccompanying the Software does not alter any rights or obligations you may have underthose open source or free software licenses. See the Third-party Legal Notices documentfor 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 documentmay be reproduced in any form by any means without prior written authorization ofSymantec 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 OFMERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT,ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TOBE LEGALLY INVALID. SYMANTEC CORPORATION SHALL NOT BE LIABLE FOR INCIDENTALOR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING,PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE INFORMATION CONTAINEDIN THIS DOCUMENTATION IS SUBJECT TO CHANGE WITHOUT NOTICE.
The Licensed Software and Documentation are deemed to be commercial computer softwareas 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 inCommercial Computer Software or Commercial Computer Software Documentation", asapplicable, 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 Corporation350 Ellis StreetMountain View, CA 94043
http://www.symantec.com
Technical SupportSymantec Technical Support maintains support centers globally. TechnicalSupport’s primary role is to respond to specific queries about product featuresand functionality. The Technical Support group also creates content for our onlineKnowledge Base. The Technical Support group works collaboratively with theother functional areas within Symantec to answer your questions in a timelyfashion. For example, the Technical Support group works with Product Engineeringand Symantec Security Response to provide alerting services and virus definitionupdates.
Symantec’s support offerings include the following:
■ A range of support options that give you the flexibility to select the rightamount of service for any size organization
■ Telephone and/or Web-based support that provides rapid response andup-to-the-minute information
■ Upgrade assurance that delivers software upgrades
■ Global support purchased on a regional business hours or 24 hours a day, 7days a week basis
■ Premium service offerings that include Account Management Services
For information about Symantec’s support offerings, you can visit our Web siteat the following URL:
www.symantec.com/business/support/index.jsp
All support services will be delivered in accordance with your support agreementand the then-current enterprise technical support policy.
Contacting Technical SupportCustomers with a current support agreement may access Technical Supportinformation at the following URL:
www.symantec.com/business/support/contact_techsupp_static.jsp
Before contacting Technical Support, make sure you have satisfied the systemrequirements that are listed in your product documentation. Also, you should beat the computer on which the problem occurred, in case it is necessary to replicatethe problem.
When you contact Technical Support, please have the following informationavailable:
■ 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 registrationIf your Symantec product requires registration or a license key, access our technicalsupport Web page at the following URL:
www.symantec.com/business/support/
Customer serviceCustomer 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 thefollowing 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 resourcesIf you want to contact Symantec regarding an existing support agreement, pleasecontact the support agreement administration team for your region as follows:
[email protected] and Japan
[email protected], Middle-East, and Africa
[email protected] America and Latin America
DocumentationYour feedback on product documentation is important to us. Send suggestionsfor improvements and reports on errors or omissions. Include the title anddocument version (located on the second page), and chapter and section titles ofthe text on which you are reporting. Send feedback to:
About Symantec ConnectSymantec Connect is the peer-to-peer technical community site for Symantec’senterprise customers. Participants can connect and share information with otherproduct users, including creating forum posts, articles, videos, downloads, blogsand suggesting ideas, as well as interact with Symantec product teams andTechnical Support. Content is rated by the community, and members receivereward points for their contributions.
http://www.symantec.com/connect/storage-management
Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Chapter 1 Introducing Symantec FileStore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
About FileStore ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17About FileStore features ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Simple installation .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Active/Active Scalable NFS .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Active/Active CIFS .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19NFS Lock Management (NLM) .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Administration .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Storage tiering .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20High-performance data replication .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Integrated content scanning using Symantec AntiVirus for
FileStore ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20About the core strengths of FileStore ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21FileStore key benefits and other applications .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
High performance scaling and seamless growth .... . . . . . . . . . . . . . . . . . . . . . . . 22High availability ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Consolidating and reducing costs of storage .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Enabling scale-out compute clusters and heterogeneous sharing
of data ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24FileStore on the Web .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Using the FileStore product documentation .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Chapter 2 Understanding Symantec FileStorearchitecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
About FileStore architecture ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27FileStore software components ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Chapter 3 Using the Symantec FileStore ManagementConsole . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
About the FileStore Management Console ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Logging into the FileStore Management Console ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Refreshing the FileStore GUI database ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Contents
Rescanning the GUI database ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31About resuming an operation without losing your data using the Back
button .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32About session timeout issues ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32About screen resolutions for viewing the FileStore Management
Console ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Using the FileStore Management Console ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33About monitoring FileStore from the Management Console
Dashboard .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Monitoring storage and pool consumption summary .... . . . . . . . . . . . . . . . . 34Monitoring the status summary .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Monitoring file systems and associated shares ... . . . . . . . . . . . . . . . . . . . . . . . . . . 36Monitoring pool consumption .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Monitoring the disk status ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Monitoring the share status ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Monitoring the service status ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Monitoring the system load .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
About monitoring FileStore alerts ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Using the alerts panel ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43About selecting a filter ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43Selecting a filter for file systems .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44Using the Enter Filter Text box .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Using the advanced filter settings ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Customizing FileStore tabular displays ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Chapter 4 Creating and maintaining Symantec FileStoreshares . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
About shares ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47About NFS shares ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Adding an NFS share .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Viewing information about NFS shares ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Accessing NFS details ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Modifying an NFS share .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Deleting an NFS share .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
About managing CIFS shares ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Viewing information about a CIFS share ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Accessing details for a CIFS share ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Adding a CIFS share ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Modifying a CIFS share ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60Deleting a CIFS share ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
About managing CIFS home directories ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Contents8
Viewing information about CIFS home directory users andquotas ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Setting up a CIFS home directory .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65Setting a CIFS home directory user ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65Removing a CIFS home directory user ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66Removing a CIFS home directory for all users ... . . . . . . . . . . . . . . . . . . . . . . . . . . . 66Enabling a CIFS home directory user quota ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66Disabling a CIFS home directory user quota ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67Enabling user and group quotas ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67Disabling user and group quotas ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67Enabling a CIFS group quota .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68Disabling a CIFS group quota .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68Setting the default CIFS quota value .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68Modifying the default CIFS quota value .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69Adding a CIFS home directory user quota ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69Modifying a CIFS home directory user quota ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70Setting a CIFS home directory quota for all users ... . . . . . . . . . . . . . . . . . . . . . . 71Adding a CIFS home directory group quota .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72Modifying a CIFS home directory group quota .... . . . . . . . . . . . . . . . . . . . . . . . . . 72Setting a CIFS home directory group quota for all users ... . . . . . . . . . . . . . 73Changing a CIFS home directory quota .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
About FTP .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74Viewing information about FTP settings ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74Aborting an FTP session .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75Uploading an FTP log to a URL .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Chapter 5 Creating and maintaining Symantec FileStore filesystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
About creating and maintaining file systems .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78Creating a file system .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79Viewing information about a file system .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82About the More button .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84Destroying a file system .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87Editing the snapshot quota ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87Placing a file system online .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88Placing a file system offline ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88Growing a file system .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89Shrinking a file system .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89Sharing a file system .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90About NFS export options .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90About CIFS share options .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92Adding a tier to a file system .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
9Contents
Running a tier policy ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95Relocating a directory of a tiered file system .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96Adding a mirror to a tiered file system .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96Removing a mirror from a tiered file system .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97Removing a tier from a file system .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97Creating a tier schedule ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97Removing a tier schedule ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98Modifying a tier policy ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98Removing a tier policy ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99Adding a mirror to a file system .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99Removing a mirror from a file system .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100Setting Fast Resync .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100Removing Fast Resync .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101Checking and repairing the consistency of file systems .... . . . . . . . . . . . . . . . . . . 101Setting file system alerts ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102Setting file system alerts for all file systems .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102Unsetting file system alerts ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103Unsetting file system alerts for all file systems .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103Enabling Symantec AntiVirus for FileStore Auto-Protect for file
systems .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104Disabling Symantec AntiVirus for FileStore Auto-Protect for file
systems .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104Stopping Symantec AntiVirus for FileStore manual scans .... . . . . . . . . . . . . . . 105Starting Symantec AntiVirus for FileStore manual scans .... . . . . . . . . . . . . . . . 105Accessing the file system details ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105Creating a shared file system .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109About snapshot operations .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Creating a snapshot ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111Destroying a snapshot ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112Preserving a snapshot ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112Changing the status of a snapshot to online .... . . . . . . . . . . . . . . . . . . . . . . . . . . . 113Changing the status of a snapshot to offline ... . . . . . . . . . . . . . . . . . . . . . . . . . . . 113Viewing snapshots ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114Managing snapshots ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114Restoring a snapshot ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Chapter 6 Configuring Symantec FileStore storage . . . . . . . . . . . . . . . . . . . . . . 117
About storage provisioning and management ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118About configuring storage pools ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118Creating storage pools ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118Viewing information about storage pools ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119Accessing storage pool details ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Contents10
Adding a disk to a storage pool ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121Moving a disk from one storage pool to another storage pool ... . . . . . . . . . . . 122Removing a disk from a storage pool ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122Destroying a storage pool ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122Renaming a pool ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123Detaching one or more pools from a cluster ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123Attaching a replication storage pool to a cluster ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123Creating a storage pool by selecting disks ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124Adding a disk to a storage pool ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124Running scan bus .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125Viewing information about disks ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125Accessing disk details ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126About I/O fencing .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Creating an I/O fencing operation .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128Enabling I/O fencing .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128Viewing information about I/O fencing .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129Disabling I/O fencing .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129Replacing a coordinator disk .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130Destroying a coordinator disk .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Chapter 7 Managing a Symantec FileStore cluster . . . . . . . . . . . . . . . . . . . . . . . 131
About managing a cluster ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131Installing FileStore software on a node .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132Adding a new node to a cluster ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132Viewing information about a node in a cluster ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132Accessing cluster details ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134Making a service go online .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134Autofixing a service ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135Deleting a node from a cluster ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135Rebooting a node in a cluster ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135Rebooting all the nodes in a cluster ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136Shutting down a node in a cluster ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136Shutting down all the nodes in a cluster ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136Displaying the current load for the cluster ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
Chapter 8 Setting up Symantec FileStore Replication . . . . . . . . . . . . . . . . . . 139
About FileStore file-level replication .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140How FileStore Replication works .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140About setting up FileStore Replication between two
clusters ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141About configuring FileStore Replication using the FileStore
Management Console ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
11Contents
Using the replication GUI wizard .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143Creating a replication job on the source cluster ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146Viewing information about replication jobs on the source
cluster ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147Modifying a replication job on the source cluster ... . . . . . . . . . . . . . . . . . . . . . . . . . . . 148Destroying a replication job on the source cluster ... . . . . . . . . . . . . . . . . . . . . . . . . . . 149Enabling a replication job on the source cluster ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150Disabling a replication job on the source cluster ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150Pausing a replication job on the source cluster ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151Resuming a replication job on the source cluster ... . . . . . . . . . . . . . . . . . . . . . . . . . . . 151Aborting a replication job on the source cluster ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151Triggering a replication job on the source cluster ... . . . . . . . . . . . . . . . . . . . . . . . . . . 152Resynchronizing a replication job .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152About the replication units operations .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Creating replication units for the source cluster on the sourcecluster ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
Creating replication units for the destination cluster on thesource cluster ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Adding a replication unit entry .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156Modifying a replication unit entry .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156Removing a replication unit entry .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157Viewing information about replication units ... . . . . . . . . . . . . . . . . . . . . . . . . . . 158Destroying a replication unit ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
About replication schedule operations .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159Creating a replication schedule on the source cluster ... . . . . . . . . . . . . . . . 159Viewing information about replication schedules on the source
cluster ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161Modifying a replication schedule on the source cluster ... . . . . . . . . . . . . . 161Deleting a replication schedule on the source cluster ... . . . . . . . . . . . . . . . 162
Chapter 9 Setting up Symantec AntiVirus for FileStore . . . . . . . . . . . . . . . 163
About Symantec AntiVirus for FileStore ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164About configuring Symantec AntiVirus for FileStore using the
FileStore Management Console ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165Scheduling a Symantec AntiVirus for FileStore scan job .... . . . . . . . . . . . . . . . . 167Viewing information about Symantec AntiVirus for FileStore scan
jobs ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168Modifying a Symantec AntiVirus for FileStore scan job .... . . . . . . . . . . . . . . . . . 168Deleting a Symantec AntiVirus for FileStore scan job .... . . . . . . . . . . . . . . . . . . . . 169Enabling a Symantec AntiVirus for FileStore scan job .... . . . . . . . . . . . . . . . . . . . 169Disabling a Symantec AntiVirus for FileStore scan job .... . . . . . . . . . . . . . . . . . . . 170Stopping a Symantec AntiVirus for FileStore scan job .... . . . . . . . . . . . . . . . . . . . 170
Contents12
Adding a LiveUpdate server ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170Deleting a LiveUpdate server ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171Initiating LiveUpdate manually ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171Viewing information about LiveUpdate ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172Initiating LiveUpdate by using schedules ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172Modifying a LiveUpdate schedule ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173Deleting a current LiveUpdate server schedule ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174Adding a proxy URL for a LiveUpdate server ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174Deleting a proxy URL for a LiveUpdate server ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175Viewing information about quarantined files ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175Deleting quarantined files ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175Repairing quarantined files ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176Displaying information about quarantined files ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176Restoring quarantined files ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
Chapter 10 Managing Symantec FileStore network settings . . . . . . . . 179
About FileStore settings ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182Starting an NFS server ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185Stopping an NFS server ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185Viewing status information for the NFS server ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186Displaying NFS status information for all the nodes in the
cluster ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186About configuring FileStore for CIFS .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
About configuring CIFS for standalone mode .... . . . . . . . . . . . . . . . . . . . . . . . . . 188Starting a CIFS server ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188Stopping a CIFS server ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188Viewing status information for the CIFS server ... . . . . . . . . . . . . . . . . . . . . . . . 189Configuring a CIFS server ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
About mapping user names for CIFS/NFS sharing .... . . . . . . . . . . . . . . . . . . . . . . . . 191Mapping a CIFS user ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192Removing a mapped CIFS user ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
Adding a CIFS local user ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192Adding a CIFS user to a group .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193Deleting a CIFS local user ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193Changing a CIFS user password .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194Adding a CIFS local group .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194Deleting a CIFS local group .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194Starting the FTP server ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195Stopping the FTP server ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195Viewing status information for the FTP server ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195Configuring the FTP server ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197Adding FTP local user accounts ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
13Contents
Changing a password for an FTP local user ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200Setting user attributes for an FTP local user ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200Deleting an FTP local user account ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201About DNS .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202Configuring DNS settings ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202Enabling DNS services ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202Disabling DNS services ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203Configuring NIS settings ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203Enabling NIS services ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203Disabling NIS services ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204Viewing information about your network configuration and
statistics ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204Adding a bond Ethernet interface ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207Removing a bond Ethernet interface ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207Adding an IP address to a cluster ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208Deleting an IP address from a cluster ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208Modifying an IP address ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209Modifying the status of an IP address to online .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209Modifying the configuration of an Ethernet interface ... . . . . . . . . . . . . . . . . . . . . . 209Adding a new IP route to a cluster ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210Deleting an IP route from a cluster ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211About configuring LDAP settings ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211Configuring LDAP server settings and enabling SSL .... . . . . . . . . . . . . . . . . . . . . . . 212Enabling LDAP .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213Disabling LDAP .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213Enabling SSL for LDAP access ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214Disabling SSL for LDAP access ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214Restoring LDAP default settings ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214About NSS .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214Configuring an NSS lookup order ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215Viewing information about VLAN devices ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215Adding a VLAN device ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216Removing a VLAN device ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216Viewing the clock, setting the NTP server and global cache .... . . . . . . . . . . . . 217Setting the system clock .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218Setting the time zone .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218Modifying the number of NFS daemons .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219Creating or modifying DMP I/O policies ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219Modifying DMP tune attributes ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221Modifying global tune fstab attributes ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222About importing or exporting configuration settings ... . . . . . . . . . . . . . . . . . . . . . 223
Importing configuration settings ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223Exporting configuration settings ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
Contents14
About backup services ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224Viewing backup services ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225Starting backup services ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226Stopping backup services ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226Viewing details about backup services ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226About NetBackup .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227Configuring backup using NetBackup .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228Adding a media server ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229Deleting a media server ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229About the Network Data Management Protocol ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
About NDMP configurations .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230Configuring NDMP policies ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
About SNMP notifications .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233Configuring report settings ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234Deleting an email server ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236Exporting event notifications .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236Adding an SNMP management server ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237Deleting an SNMP management server ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237Adding a syslog server address ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238Deleting a syslog server address ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238Adding an email group .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238Removing an email group .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239Adding a severity/filter ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239Removing a severity/filter ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240Adding an email to an email group .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240Deleting an email from an email group .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241Viewing user accounts ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241Adding new user accounts ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241Removing user accounts ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242Resetting passwords .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242Viewing upgrade settings ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243Upgrading FileStore ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243Uninstalling FileStore up to the specified version .... . . . . . . . . . . . . . . . . . . . . . . . . . 244Syncing nodes ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244Configuring FileStore Replication .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244
Binding a virtual IP address on the source and destinationclusters ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
Unbinding a virtual IP address for the source and destinationclusters ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
Viewing replication status details ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246Starting the replication service for the source and destination
clusters ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
15Contents
Stopping the replication service for source and destinationclusters ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
Exporting keys on the source cluster ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247Importing keys on the destination cluster ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248Exporting keys on the destination cluster ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248Importing keys on the source cluster ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249Creating a link between the source cluster and the destination
cluster ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249Deleting a link between the source cluster and the destination
cluster ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249Deleting import/export keys ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250Checking the link between the source and destination
clusters ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250Adding a loopback link .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
Configuring the Symantec AntiVirus for FileStore service ... . . . . . . . . . . . . . . . 251Starting the Symantec AntiVirus for FileStore service for all the
nodes ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251Stopping the Symantec AntiVirus for FileStore service for all
the nodes ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251Excluding file extensions from Symantec AntiVirus for FileStore
scans .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252Deleting file extensions from Symantec AntiVirus for FileStore
scans .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252Setting the Symantec AntiVirus for FileStore action policy ... . . . . . . . 252
Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259
Contents16
Introducing SymantecFileStore
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 FileStoreFileStore was formerly known as Storage Foundation Scalable File Server.
FileStore is a highly-scalable and highly-available clustered Network AttachedStorage (NAS) software appliance. Based on Storage Foundation Cluster FileSystem technology, FileStore is a complete solution for multi-protocol file serving.FileStore provides an open storage gateway model, including a highly- availableand scalable Network File System (NFS), CIFS, and FTP file serving platform andan 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
1Chapter
■ Active/Active shared data NFS sharing including shared read/write andLDAP/NIS support
■ Simple administration of Fibre Channel Host Bus Adapters (HBAs), file systems,disks, snapshots, and Dynamic Storage Tiering
■ SNMP, syslog, and email notification
■ High-speed asynchronous/episode-based replication for content distributionand data mining
■ Multi-protocol sharing of file systems in a highly-scalable and highly-availablemanner
■ 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 thefile system
■ Seamless upgrade and patch management
■ Support information
■ Online man pages
The components of FileStore include a security-hardened, custom-install SUSELinux Enterprise Server (SLES) 11 SP1 operating system, core Storage Foundationservices including Cluster File System, and the FileStore software platform. Thesecomponents are provided on multiple DVDs or a DVD ISO image.
About FileStore featuresFileStore is designed to provide a full-suite of NAS features, in addition toclass-leading performance and scalability. A partial list of these features isdiscussed in the following sections.
Simple installationA single node in the cluster is booted from a DVD containing the operating systemimage, 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 thecluster nodes are automatically installed with all necessary components. The keyservices are then automatically started to allow the cluster to begin discoveringstorage and creating file shares.
Introducing Symantec FileStoreAbout FileStore features
18
Active/Active Scalable NFSWith FileStore, all nodes in the cluster can serve the same NFS shares as bothread and write. This creates very high aggregated throughput rates, because youcan use sum of the bandwidth of all nodes. Cache-coherency is maintainedthroughout the cluster.
Active/Active CIFSCIFS is active on all nodes within the FileStore cluster. The specific shares areread/write on the node they reside on, but can failover to any other node in thecluster. FileStore supports CIFS home directory shares.
NFS Lock Management (NLM)The NFS Lock Management (NLM) module allows a customer to use NFS advisoryclient locking in parallel with core SFCFS global lock management. The moduleconsists of failing over the locks among FileStore nodes as well as forwarding allNFS client lock requests to a single NFS lock master.
The result is that no data corruption occurs if a user or application needs to useNFS client locking with an FileStore cluster.
AdministrationFileStore contains a role-based administration model consisting of the followingkey 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. Thisinterface provides a single point of administration for the entire cluster. A userlogs in as one of those roles on one of the nodes in the cluster and runs commandsthat perform the same tasks on all nodes in the cluster.
You do not need to have any knowledge of the Veritas Storage Foundationtechnology to install or administer an FileStore cluster. If you are currently familiarwith core SFCFS or Storage Foundation in general, you will be familiar with thebasic management concepts.
19Introducing Symantec FileStoreAbout FileStore features
Storage tieringFileStore's built-in Dynamic Storage Tiering (DST) feature can reduce the cost ofstorage by moving data to lower cost storage. FileStore storage tiering alsofacilitates the moving of data between different drive architectures.
Dynamic Storage Tiering lets you do the following:
■ Create each file in its optimal storage tier, based on pre-defined rules andpolicies.
■ 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 longerneeded.
■ Retain original file access paths to minimize operational disruption, forapplications, 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 replicationIncluded as a standard feature in the Enterprise Edition of FileStore and optionalon the Standard Edition, FileStore Replication provides for high-performancecontent 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 specificfiles that have changed since the last update. With FileStore Replication, thedestination file system can be on-line for reads, and updates to that destinationcan be as frequent as every fifteen minutes. FileStore Replication is ideal forcontent distribution, or for creating hot-standby replicas of a productionenvironment.
Integrated content scanning using Symantec AntiVirus for FileStoreNew to FileStore is the ability for customers to use Symantec AntiVirus forFileStore. Leveraging content-scanning and anti-virus technology similar to thatfound in the Symantec Endpoint Protection range of products, this feature allowsfor scheduled and real-time (on-demand) scanning of files and other data containedwithin the FileStore cluster. When conducted in real-time, this content-scanningcan be used with multiple file access protocols, including CIFS, NFS, FTP, andHTTP. Files can be automatically quarantined and regular virus definition updatescan be obtained by way of the standard Symantec LiveUpdate service.
Introducing Symantec FileStoreAbout FileStore features
20
About the core strengths of FileStoreFileStore leverages all the capabilities and strengths of the Storage Foundationfamily of products.
FileStore contains all the key features of Storage Foundation Cluster File System5.1 SP1PR3 including:
■ Dynamic Multi-Pathing (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 toprovide in-depth failure detection and path failover logic. DMP is compatible withmore hardware than any other similar product, and is a standard componentwithin the FileStore product.
Cluster Volume Manager provides a cluster-wide consistent virtualization layerthat leverages all the strengths of the underlying Veritas Volume Manager (VxVM)technology including online re-layout and resizing of volumes, and online arraymigrations. You can mirror your FileStore file systems across separate physicalframes to ensure maximum availability on the storage tier. This techniqueseamlessly 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 ata file or sub-file level. CFS lets all nodes in the cluster perform metadata or datatransactions. This allows linear scalability in terms of NFS operations per second.
VCS monitors communication, and failover for all nodes in the cluster and theirassociated critical resources. This includes virtual IP addressing failover for allclient connections regardless of the client protocol.
Dynamic Storage Tiering (DST) dynamically and transparently moves files todifferent storage tiers to respond to changing business needs. DST is used inSymantec FileStore as FileStore Storage Tiering.
I/O fencing further helps to guarantee data integrity in the event of a multiplenetwork failure by using the FileStore storage to ensure that cluster membershipcan be determined correctly. This virtually eliminates the chance of a clustersplit-brain from occurring.
21Introducing Symantec FileStoreAbout the core strengths of FileStore
FileStore key benefits and other applicationsFileStore can be used with any application that requires the sharing of files usingthe NFS v3, CIFS, or FTP protocol. Use-cases such as home directories or decisionsupport applications that require sequential shared access, Web pages, andapplications are all ideal for FileStore. FileStore is also applicable when you wantgeneral purpose, high-throughput scale-out processing for your data, togetherwith enterprise-class highly available cluster functionality.
High performance scaling and seamless growthFileStore lets you scale storage and processing independently and seamlessly,online. Because an application may need to scale either storage or processing, orboth, 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. Youcan add processing one node at a time, rather than buying a large, expensiveindependent appliance.
A storage administrator can configure a new array or even add new LUNs froman existing array into the FileStore cluster. FileStore can then scan the storage,automatically see the new LUNs and place them under FileStore control for usein the cluster. All of this is performed online.
At the storage end, resizing of existing file systems can be performed online withno interruption of service. A simple command is used to both add space to anexisting file system and to also reduce (dynamically shrink) the amount of freespace in a specified file system.
The product provides nearly linear scaling in terms of NFS operations per secondand total I/O throughput.
Figure 1-1 depicts this scaling capability.
Introducing Symantec FileStoreFileStore key benefits and other applications
22
Figure 1-1 Example of near-linear performance scaling with FileStore
When using 16-node clusters, extremely high throughput performance numberscan be obtained. This is due to the benefits of near linear FileStore clusterscalability.
High availabilityFileStore has an “always on" file service that provides zero interruption of fileservices for company critical data.
The loss of single or even multiple nodes does not interrupt I/O operations on theclient 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 nodecan act as a failover for any other node.
The FileStore architecture provides transparent failover for other key servicessuch as NFS lock state, CIFS and FTP daemons, reporting, logging, andbackup/restore operations. The console service that provides access to thecentralized menu-driven interface is automatically failed over to another node.
The installation service is also highly available and can seamlessly recover fromthe initially installed node failing during the installation of the remaining nodesin the cluster.
The use of Veritas Cluster Server technology and software within FileStore is keyto the ability of FileStore to provide best-of-breed high availability, in addition toclass-leading scale-out performance.
Consolidating and reducing costs of storageThe value of consolidating several independent islands of NAS appliances intofewer, larger shared pools has many cost benefits.
23Introducing Symantec FileStoreFileStore key benefits and other applications
A typical enterprise uses 30-40% of its storage. This low storage utilization rateresults in excessive spending on new storage when there is more than adequatefree space in the data center.
With FileStore, you can group storage assets into fewer, larger shared pools. Thisincreases the use of backend LUNs and overall storage.
FileStore also has built-in, pre-configured heterogeneous storage tiering. Thislets you use different types of storage in a primary and secondary tierconfiguration. Using simple policies, data can be transparently moved from theprimary storage tier to the secondary tier. This is ideal when mixing drive typesand architectures such as high-speed SAS drives with cheaper storage, such asSATA-based drives. Furthermore, data can be stored initially on the secondarytier 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) becausethere will often be a significant change between the amount of SSD storageavailable, and amount of other storage availability, such as SATA drives. Dataand files that are promoted to the primary tier are transferred back to thesecondary tier in accordance with the configured access time policy.
All of this results in substantially increased efficiency, and it can save you moneybecause you make better use of the storage you already have.
Enabling scale-out compute clusters and heterogeneous sharing ofdata
The trend toward scale-out, or grid computing continues to gain pace. There aresignificant performance and cost advantages of moving applications away fromlarge UNIX Symmetrical Multi-Processing (SMP) or mainframe environments andtowards a farm of commodity computer servers running a distributed application.
One of the key inhibitors to scale-out computing is the requirement to provide ashared storage infrastructure for the compute nodes, and enable you to shareheterogeneously as well as scale up as performance requires. FileStore solves bothof these issues by providing a highly scalable and shared storage platform at thestorage tier and by facilitating heterogeneous sharing on the compute tier.
FileStore can provide the performance and availability you need for a large-scaleNFS compute and storage tier. It provides enough throughput and seamless failoverfor this type of architecture – whether a few dozen compute nodes, or scaling toseveral hundred nodes.
Introducing Symantec FileStoreFileStore key benefits and other applications
24
FileStore on the WebFor comprehensive, up-to-date information about FileStore, visit the SymantecWeb site:
http://www.symantec.com/business/support/overview.jsp?pid=55079
Using the FileStore product documentationFileStore product documentation is available in PDF format on the FileStoreinstallation DVD in the /docs directory:
■ Symantec FileStore Web GUI Administrator’s Guide (sfs_admin_gui.pdf)
■ Symantec FileStore Command-Line Administrator’s Guide (sfs_admin.pdf)
■ Symantec FileStore Installation Guide (sfs_install.pdf)
■ Symantec FileStore Replication Guide (sfs_replication.pdf)
■ Symantec FileStore Troubleshooting Guide (sfs_troubleshoot.pdf)
■ Symantec FileStore Release Notes (sfs_relnotes.pdf)
Find additional information at this location:
http://www.symantec.com/business/support/overview.jsp?pid=55079
25Introducing Symantec FileStoreFileStore on the Web
Introducing Symantec FileStoreUsing the FileStore product documentation
26
Understanding SymantecFileStore architecture
This chapter includes the following topics:
■ About FileStore architecture
■ FileStore software components
About FileStore architectureFileStore can be installed on a variety of readily-available Intel-based servers inrack-mount or other form factors. Architecturally, an FileStore cluster is aNetwork-Attached Storage (NAS) gateway. The servers (nodes) that comprise acluster collaborate to execute client computers' requests to read and write filedata stored on physical disks that are accessible for all nodes.
The FileStore nodes translate clients' Network File System (NFS) or CommonInternet File System (CIFS) file access requests into disk read and write requeststhat the FileStore nodes issue to storage devices (Logical Units, or LUNs, presentedby disk arrays or alternatively, physical disk drives) that contain file data.
Each FileStore cluster node runs a version of the open source Linux operatingsystem that has been hardened by thorough qualification of necessary componentsand elimination of unnecessary ones. Together, the nodes comprise a cluster inwhich all file systems are accessible by (mounted on) all servers simultaneously.
FileStore software uses Veritas Storage Foundation and Cluster Server technologiesto provide its storage management, file services, and high availability features.FileStore software augments these with specialized components that integratethe base capabilities into a high-performing, scalable, easy to administer NFS andCIFS file server.
2Chapter
FileStore software componentsThe principal FileStore-specific software components are the following:
■ The NFS server that provides file access services to UNIX and Linux clientcomputers that use the Network File System (NFS) protocol to access data.
■ The Samba-based CIFS Server that provides file access services to Windowsclient computers that use the Common Internet File System (CIFS) protocolto access data.
■ The Network Lock Manager that provides advisory locking for file systemsaccessed by NFS (locking for CIFS-accessed file systems is integral to the CIFSprotocol) so that multiple clients can access files concurrently withoutcorrupting data.
■ The FileStore console that enables an administrator to configure and managean FileStore cluster using either a simple command-line interface or abrowser-based graphical interface.
Understanding Symantec FileStore architectureFileStore software components
28
Using the SymantecFileStore ManagementConsole
This chapter includes the following topics:
■ About the FileStore Management Console
■ Logging into the FileStore Management Console
■ Refreshing the FileStore GUI database
■ Rescanning the GUI database
■ About resuming an operation without losing your data using the Back button
■ About session timeout issues
■ About screen resolutions for viewing the FileStore Management Console
■ Using the FileStore Management Console
■ About monitoring FileStore from the Management Console Dashboard
■ About monitoring FileStore alerts
■ Using the alerts panel
■ About selecting a filter
■ Selecting a filter for file systems
■ Using the Enter Filter Text box
■ Using the advanced filter settings
3Chapter
■ Customizing FileStore tabular displays
About the FileStore Management ConsoleThe FileStore Management Console is a centralized, Web-based administrationtool used to configure and monitor all the components of FileStore.
FileStore includes both the browser-based graphical user interface (the FileStoreManagement Console) as well as a Command-Line Interface (CLI). For informationon using the CLI, refer to the Symantec FileStore Command-Line Administrator’sGuide.
Logging into the FileStore Management ConsoleTo access the FileStore Management Console, use any of the following URLs:
■ https://CONSOLE-IP:8443/sm
■ https://CONSOLE-IP:8443/sm/Login
You initially log into the FileStore Management Console using the defaultusername/password of master/master. After you have logged in successfully,change your password.
Note: Changing the default password is important for system security. If you donot change the default password, a warning message appears the next time youlog in.
As the administrator, you can add additional users, assigning them the role ofmaster, system-admin, or storage-admin. Each role allows the user access tocertain commands.
Note: The End User License Agreement (EULA) is displayed the first time you login to the FileStore Management Console.
Refreshing the FileStore GUI databaseThere is an on-demand refresh operation that you can use if you find that FileStoreGUI data is not updated or the latest data is not displayed. The Refresh operationdiscovers any changes that occurred to FileStore objects and reports those changesto the database. Using the Refresh operation on the Home > Summary pagediscovers any changes that have occurred to all objects, services, and settings,
Using the Symantec FileStore Management ConsoleAbout the FileStore Management Console
30
and reports those changes to the database, and those updates are reflected in theFileStore GUI displays.
Indicates the Refresh operation that discovers any changes thatoccurred to FileStore objects and reports those changes to the database.
Using the Refresh operation on the File Systems page, discovers any changesrelated to file systems, disks, or pools, and those updates are reflected in theFileStore GUI displays. The Refresh operation updates changes in the database,but it does not recreate the database.
Note: There is a corresponding Support> gui db refresh command that can beexecuted from the FileStore CLI, and any updates are reflected in the databasefor the CLI. See the Symantec FileStore Command-Line Administrator’s Guide formore information about using the CLI.
To refresh the FileStore GUI database from the Home > Summary page
1 To refresh the FileStore GUI database, on the Home > Summary page, clickthe Refresh icon.
There is a Refresh icon for the following FileStore GUI tabs: Shares, Storage,Cluster, Replication, AntiVirus, and Settings.
2 In the Refresh dialog, verify that you want to discover any changes that haveoccurred to FileStore GUI objects, and click OK.
3 In the Result dialog, click OK.
Rescanning the GUI databaseIn certain situations you may need to rescan (rather than refresh) the GUI database.The rescan feature generates a fresh database and updates all the changes in thecluster.
Note: There is a corresponding Support> gui db rescan command that can beexecuted from the FileStore CLI. See the Symantec FileStore Command-LineAdministrator’s Guide for more information about using the CLI.
31Using the Symantec FileStore Management ConsoleRescanning the GUI database
To rescan the GUI database
1 A warning message automatically displays in the GUI when the databaseneeds to be rescanned. When the message displays, click OK.
2 Another message appears to inform you that the Web service will beterminated. Click OK.
3 When the Web service returns, re-login to the GUI.
About resuming anoperationwithout losing your datausing the Back button
Should you perform an operation and receive an error message, you can use theBack button to resume the operation from the Result dialog to the main dialogwithout losing your previously entered data.
The following operations contain Back button functionality:
■ Storage > Create Pool
■ File Systems > Create
■ File Systems > Manage Snapshot
■ File Systems > Create Tier
About session timeout issuesIf you have not actively used the FileStore Management Console within 30 minutes,your FileStore Management Console session will expire, and you will receive asession timeout message.
In some cases, you may experience a session timeout after creating a file systemfor the first time, or when deleting the last file system.
If you reboot the console node or all nodes from the FileStore Management Consoleusing Cluster>RebootNode or Reboot all operations, your session will timeout,and you will be requested to open a new browser window, and re-login to theFileStore Management Console.
About screen resolutions for viewing the FileStoreManagement Console
Refer to Table 3-1 for the best screen resolutions for viewing the FileStoreManagement Console.
Using the Symantec FileStore Management ConsoleAbout resuming an operation without losing your data using the Back button
32
Table 3-1 Screen resolutions for viewing the FileStore Management Console
ViewScreenresolution
Standard1024 x 768
Best View1280 x 800
Best View1440 x 900
Using the FileStore Management ConsoleYou initially log into the Management Console using the user name and thepassword assigned to you by the administrator during the initial softwareconfiguration using the CLI.
Upon the successful login, the FileStore ManagementConsoleHome page displaysthe Dashboard.
Immediately below the console window title bar are seven tabs that correspondto the console pages used to execute the six categories of FileStore tasks.
■ HomeUsed to monitor resources, performance, hardware component status, andalerts. The Dashboard is displayed immediately upon login.
■ SharesProvides support for multi-protocol file sharing where the same file systemcan be exported to both Windows and UNIX users using the CIFS and NFSprotocols.
■ File SystemsCreates, configures, shares, and deletes FileStore file systems.
■ StorageCreates storage pools and disks.
■ ClusterAdds nodes to the cluster.
■ ReplicationProvides high performance, scalable (one-to-many) data replication and isideal for use as a content distribution solution, and for use to create hot standbycopies of important data sets.
■ AntiVirus
33Using the Symantec FileStore Management ConsoleUsing the FileStore Management Console
Provides support for Symantec AntiVirus for FileStore, which allows forscheduled and real-time (on-demand) scanning of files and other data containedwithin the FileStore cluster.
■ SettingsUsed to manage a cluster's network settings.
To perform a task, you click the tab that corresponds to the task's category.
About monitoring FileStore from the ManagementConsole Dashboard
You use the FileStore Management Console's Dashboard panels to monitor yourcluster's performance, component status, and alerts. Alerts are correlated withthe summary displays.
You can use the Management Console Dashboard to monitor the following:
■ Storage summary
■ Pool summary
■ Pool consumption
■ File system consumption and associated shares
■ CPU and Network usage
■ Status of disks, shares, and services
■ Alerts status
Monitoring storage and pool consumption summaryThe Management Console Dashboard's Storage Summary and Pool Summarypanels display the cluster's current capacity and utilization. The utilization ismeasured in gigabytes.
The Dashboard displays storage and pool consumption in two categoriesdistinguished by color:
■ Used Space (green)Displays currently allocated storage and pool capacity.
■ Free Space (blue)Displays unallocated storage and pool capacity.
Using the Symantec FileStore Management ConsoleAbout monitoring FileStore from the Management Console Dashboard
34
Monitoring the status summaryThe Status Summary panel displays the current status of the file systems,snapshots, and nodes.
Table 3-2 Status icons
DescriptionStatus icon
Faulted
Indicates that something is wrong with the file system, snapshot, ornode.
At Risk
The component is functioning, but has reported that it is not withinits normal operating parameters.
Online
Indicates the file system, snapshot, or node are up and running.
Offline
Indicates the file system, snapshot, or node are down or unmounted.
35Using the Symantec FileStore Management ConsoleAbout monitoring FileStore from the Management Console Dashboard
If you click on a number in the FS column, FileStore takes you to the FileSystemstab.
See “Viewing information about a file system” on page 82.
If you click on a number in the Snapshots column, FileStore takes you to theSnapshots window on the File Systems tab.
If you click on a number in the Nodes column, FileStore takes you to the Nodeswindow on the Cluster tab.
See “Viewing information about a node in a cluster” on page 132.
Monitoring file systems and associated sharesThe Most Consumed File Systems panel displays the five file systems that areconsuming the most of their allocated space. The shares that correspond to eachfile system are also listed.
The file consumption states are defined by color:
■ GreenUnder 70% of the pool is in use.
■ OrangeBetween 70% and 90% of the pool is in use.
■ RedThe pool use exceeds 90%. You need to reallocate some of the usage.
Using the Symantec FileStore Management ConsoleAbout monitoring FileStore from the Management Console Dashboard
36
If you click on a file system, FileStore takes you to a window displaying the filesystem details in File Systems tab.
See “Viewing information about a file system” on page 82.
If you click on an NFS or CIFS share, FileStore takes you to a window displayingthe details of the shared files in the Shares tab.
See “Viewing information about NFS shares” on page 51.
See “Viewing information about a CIFS share” on page 55.
Monitoring pool consumptionIn the Most Consumed Pools panel, the pools using the most capacity are listed.The usage is colored-coded to alert you to the status of the usage. The utilizationis measured in megabytes and gigabytes and is measured as a percentage of usage.
The pool consumption states are defined by color:
■ GreenUnder 70% of the pool is in use.
■ OrangeBetween 70% and 90% of the pool is in use.
■ RedThe pool use exceeds 90%. You need to reallocate some of the usage.
37Using the Symantec FileStore Management ConsoleAbout monitoring FileStore from the Management Console Dashboard
If you click on a pool name, FileStore takes you to a window displaying the pooldetails on the Storage tab.
See “Viewing information about storage pools” on page 119.
Monitoring the disk statusThe Disk Status panel displays the disk status on each node that is listed.
Table 3-3 Disk Status icons
DescriptionIcon
Indicates the node.
Indicates the node is up and running (online).
Indicates the node is down or unmounted (offline).
Using the Symantec FileStore Management ConsoleAbout monitoring FileStore from the Management Console Dashboard
38
See “Viewing information about a node in a cluster” on page 132.
See “Viewing information about disks” on page 125.
See “Viewing information about disks” on page 125.
Monitoring the share statusThe Share Status panel displays the status of the NFS and CIFS shares on eachnode that is listed.
If you click on a node, FileStore takes you to the Node Details window on theCluster tab.
See “Viewing information about a node in a cluster” on page 132.
If you click on a number in the NFS Share columns, FileStore takes you to theNFS window on the Shares tab.
See “Viewing information about NFS shares” on page 51.
If you click on a number in the CIFS Share columns, FileStore takes you to theCIFS window on the Shares tab.
See “Viewing information about a CIFS share” on page 55.
Monitoring the service statusThe Service Status panel displays all of the nodes in the cluster (up to four) andthe status of each service running on each node.
The services displayed are the following:
■ NFS - status of the NFS service
■ CIFS - status of the CIFS service
■ FTP - status of the FTP service
39Using the Symantec FileStore Management ConsoleAbout monitoring FileStore from the Management Console Dashboard
■ Console - status of the console IP address
■ BU - status of the NDMP service
■ AV - status of the Symantec AntiVirus for FileStore service
If you click on a node, FileStore takes you to the Node Details window on theCluster tab.
See “Viewing information about a node in a cluster” on page 132.
This panel also displays a list of offline IP addresses.
Monitoring the system loadThe FileStore Management Console's Dashboard's System Load panel displaysthe average calculation of the CPU usage of all of the nodes in the cluster and thetraffic between the network and the cluster or individual node.
You can select one of the following parameters to display:
■ Node - to select an individual node
■ Duration - to select what time span you want to view
■ Device - to select which device to use
Using the Symantec FileStore Management ConsoleAbout monitoring FileStore from the Management Console Dashboard
40
If you click on the View Available Nodes link, FileStore takes you to the Clustertab.
See “Viewing information about a node in a cluster” on page 132.
About monitoring FileStore alertsThe FileStore Management Console Dashboard Alerts panel displays a list ofalerts.
The information provided with the alerts is the following:
■ Severity - Severity level of the alert
■ Time - Time the alert occurred
■ Message - Message associated with the alert
■ Filter - Filter used for sorting the alerts
41Using the Symantec FileStore Management ConsoleAbout monitoring FileStore alerts
If you click on the View All Alerts link, FileStore takes you to the Home > Alertstab where all the alerts are displayed.
Alert levels and definitions are described in Table 3-4.
Note: After an alert is handled, it is removed from the panel. However, it remainsin the syslog.
Table 3-4 Alert levels in precedence order
DefinitionAlert level
There is no icon for this alert.
Indicates that the system is unusable.
Emerg
Indicates that immediate action is required.Alert
Indicates a critical condition.Critical
Indicates an error condition.Error
Using the Symantec FileStore Management ConsoleAbout monitoring FileStore alerts
42
Table 3-4 Alert levels in precedence order (continued)
DefinitionAlert level
Indicates a warning condition.Warning
There is no icon for this alert.
Indicates a normal but significant condition.
Notice
Indicates an informational message.Info
There is no icon for this alert.
Indicates a debugging message.
Debug
Using the alerts panelTo view all of the alerts
1 To view all of the alerts, click on the Alerts tab at the top of the Dashboardwindow.
You can also go to the bottom of the Dashboard window, and click on ViewAll Alerts.
The Alerts window opens.
2 In the Alerts window, you can click on any of the nodes.
By clicking on a node, FileStore takes you to the NodeDetails window on theCluster tab.
About selecting a filterSince the FileStore cluster may include or be connected to hundreds of servers,contain thousands of disks, host hundreds of file systems, and support thousandsof clients, a filtering capability is included to help you isolate specific subsets ofcomponents based on their properties.
43Using the Symantec FileStore Management ConsoleUsing the alerts panel
Table 3-5 Filter definitions
DefinitionFilter type
These filters are a list of parameters in the current main window. Thefilters differ for each tab. For example, in File Systems some of thepredefined filters include NFS and Mirrored.
See “Selecting a filter for file systems” on page 44.
Predefined filters
You can enter a specific text string that is not included in thepredefined filters to sort by.
Note: This feature does not work if the Advanced filter settings arebeing used.
See “Using the Enter Filter Text box” on page 45.
Text Filters
You can specify your own filters by selecting a combination ofparameter values in the drop-down menus. Advanced filters can besaved and invoked by name.
See “Using the advanced filter settings” on page 45.
Advanced filters
Selecting a filter for file systemsTo select a predefined filter
1 Click the Select Filter drop-down menu and select one of the parameters tosort the table.
The table changes automatically.
2 To restore the entire list of file systems, you can click the ClearFilter button,or select All in the drop-down menu.
Using the Symantec FileStore Management ConsoleSelecting a filter for file systems
44
Using the Enter Filter Text boxTo use the enter filter text box
1 You can filter the display by entering a text string.
Type the text (for example, all or part of a file system name or description)in the Enter Filter Text box, and click the Filter button.
2 To restore the entire list of file systems, you can click the ClearFilter button.
Using the advanced filter settingsTo use the advanced filter settings
1 To add new criteria to the current filters or add new filters, click on theAdvanced heading.
2 Select the criteria you want to use to sort the table by selecting items fromthree drop-down menus. Click the Addnewcriteria button. The criteria youselect appears on the screen with an X by it. Click the Apply button, and yourtable is sorted.
3 To save the criteria you select, click the Save button. In the Save Query box,enter a filter name for the criteria, and it is saved under that name in thepredefined list in the Select Filter drop-down menu.
4 Click Save.
5 To delete the criteria you selected, click on the X on the right side of thecriteria.
6 Click on Cancel to end the process.
45Using the Symantec FileStore Management ConsoleUsing the Enter Filter Text box
Customizing FileStore tabular displaysThree graphical icons appear in the upper right corner of each of the tabulardisplays.
By clicking these icons you can display pages from which the following actionscan be performed:
Table 3-6 Table display icons
DefinitionIcon
Customize the displayed table by adding or removing columns,rearranging column order, and filtering the information displayed.
Export table contents either directly to Microsoft Excel, or to a textfile of comma-separated values (CSV) that can be imported into anyspreadsheet application that supports the CSV data format.
Open a browser window containing a printer-friendly version of thetable that can be printed using the browser’s Print command.
Using the Symantec FileStore Management ConsoleCustomizing FileStore tabular displays
46
Creating and maintainingSymantec FileStore shares
This chapter includes the following topics:
■ About shares
■ About NFS shares
■ About managing CIFS shares
■ About managing CIFS home directories
■ About FTP
About sharesFileStore provides support for multi-protocol file sharing where the same filesystem can be exported to both Windows and UNIX users using the CommonInternet File System (CIFS) and Network File System (NFS) protocols. The resultis an efficient use of storage by sharing a single data set across multi-applicationplatforms.
The File Transfer Protocol (FTP) server feature allows clients to access files onthe FileStore servers using the FTP protocol. The FTP service providessecure/non-secure access by FTP to files in the FileStore servers. The FTP serviceruns on all of the nodes in the cluster and provides simultaneous read/write accessto the files. The FTP service also provides configurable anonymous access to thefiler.
4Chapter
Note:When a share is exported over both NFS and CIFS protocols, the applicationsrunning on the NFS and CIFS clients may attempt to concurrently read or writethe same file. This may lead to unexpected results since the locking models usedby these protocols are different. For example, an application reads stale data. Forthis reason, FileStore warns you when the share export is requested over NFS orCIFS and the same share has already been exported over CIFS or NFS, when atleast one of these exports allows write access.
Table 4-1 Protocol definitions
DefinitionProtocol
Network File System (NFS) allows NFS clients to access files onFileStore servers using the NFS protocol.
NFS
Common Internet File System (CIFS) allows CIFS clients to access fileson FileStore servers using the CIFS protocol.
CIFS
File Transfer Protocol (FTP) allows clients to access files on theFileStore servers using the FTP protocol.
FTP
About NFS sharesThe NFS protocol enables the files hosted by an NFS server to be accessed bymultiple UNIX and Linux client systems. Using NFS, a local system can mountand use a disk partition or file system from a remote system (an NFS server), asif it were local. The FileStore NFS server exports a disk partition or file system,with selected permissions and options, and makes it available to NFS clients. Theselected permissions and options can also be updated, to restrict or expand thepermitted use. To remove sharing, unexport the NFS file system. The FileStoreNFS service is clustered. The NFS clients continuously retry during a failovertransition. Even if the TCP connection is broken for a short time, the failover istransparent to NFS clients, and NFS clients regain access transparently as soonas the failover is complete.
Depending on client configuration and the nature of the failure, a client operationmay time out, resulting in an error message.
You use NFS operations to export or unexport your file systems.
Creating and maintaining Symantec FileStore sharesAbout NFS shares
48
Table 4-2 NFS operations
DefinitionOperation
Displays the exported file systems.
See “Viewing information about NFS shares” on page 51.
View
Exports a file system.
See “Adding an NFS share” on page 49.
Add
Unexports a file system.
See “Deleting an NFS share” on page 55.
Delete
Modifies the parameters of an exported file system.
See “Modifying an NFS share” on page 53.
Modify
Adding an NFS shareTo add an NFS share
1 In the FileStore Management Console, click Shares > NFS.
2 Click on the Add button.
The Add NFS Share dialog box displays.
3 In the File System/Directory Path field, specify the file system/directorypath that you want to add (export) starting with the file system name. Thisis a required field.
The directory path starting with the file system name should start with /vx/,and only a-zA-Z0-9_/@+=.:- characters are allowed.
49Creating and maintaining Symantec FileStore sharesAbout NFS shares
4 In the Set Export Options box, select the options you want applied to theshared file system. This is a required field.
Grants read-only permission to the file system. Hosts mountingthis file system are not able to change it.
Read Only(Default)
Grants read and write permission to the file system. Hostsmounting this file system can make changes to the file system.
Read Write
Grants synchronous write access to the file system. Forces theserver to perform a disk write before the request is consideredcomplete.
Synchronous(Default)
Grants asynchronous write access to the file system. Allows theserver to write data to the disk when appropriate.
Async
Grants secure access to the file system. Requires that clientsoriginate from a secure port. A secure port is between 1-1024.
Secure (Default)
Grants insecure access to the file system. Permits client requeststo originate from unauthorized ports (those above 1024).
Insecure
Requires the authorization of all locking requests.Secure Locks(Default)
Some NFS clients do not send credentials with lock requests, andtherefore work incorrectly with Secure Locks, in which case you
Insecure Locks
can only lock world-readable files. If you have such clients, eitherreplace them with better ones, or use the Insecure Locks option.
Prevents the root user on an NFS client from having rootprivileges on an NFS mount.
Root Squash(Default)
This "squashes" the power of the remote root user to the lowestlocal user, preventing remote root users from acting as thoughthey were the root user on the local system.
Disables the Root Squash option. Allows the root users on theNFS client to have root privileges on the NFS server.
No Root Squash
Causes the NFS server to delay writing to the disk if another writerequest is imminent. This can improve performance by reducing
Write Delay(Default)
the number of times the disk must be accessed by separate writecommands, reducing write overhead.
Disables the Write Delay (Wdelay) option.No Write Delay
The No Write Delay option has no effect if Async is also set.
Creating and maintaining Symantec FileStore sharesAbout NFS shares
50
Verifies that the requested file is in an exported subdirectory. Ifthis option is turned off, the only verification is that the file isin an exported file system.
Subtree Check
Sometimes subtree checking can produce problems when arequested file is renamed while the client has the file open. Ifmany such situations are anticipated, it might be better to setNo Subtree Check. One such situation might be the export of the/home directory file system. Most other situations are besthandled by using the Subtree Check option.
No Subtree Check(Default)
This option allows the FileStore administrator to associate aspecific number as fsid with the share.
Fsid
5 In the Specify Client box, select one of the following:
■ Single host - specify a host either by an abbreviated name that isrecognized by the resolver (DNS is the resolver), the fully qualified domainname, or an IP address.
■ Netgroups - netgroups may be given as @group. Only the host part of eachnetgroup member is considered for checking membership.If the client is not given, then the specified file system can be mounted oraccessed by any client. To re-export new options to an existing share, thenew options are updated after the operation is run.
6 Click OK.
7 In the Result dialog, click OK.
Viewing information about NFS sharesTo view information about NFS shares
◆ In the FileStore Management Console, click Shares > NFS.
In the NFS window, you can view the following information about NFS shares:
Lists the NFS shared file systems.Exports
Name of the parent file system or snapshot you want to export.Parent FileSystem/Snapshot
Either file system or snapshot.Parent Type
51Creating and maintaining Symantec FileStore sharesAbout NFS shares
Clients are one of the following:
■ Single host - specify a host either by an abbreviated namethat is recognized by the resolver (DNS is the resolver), thefully qualified domain name, or an IP address.
■ Netgroups - netgroups may be given as @group. Only the hostpart of each netgroup member is considered for checkingmembership.
If the client is not given, then the specified file system is mountedor accessed by any client. To re-export new options to an existingshare, the new options are updated after the command is run.
Clients
Comma-separated list of export options.
Export options include the following:
■ Read Only
■ Read Write
■ Synchronous
■ Async
■ Secure
■ Insecure
■ Secure Locks
■ Insecure Locks
■ Root Squash
■ No Root Squash
■ Write Delay
■ No Write Delay
■ Subtree Check
■ No Subtree Check
■ Fsid
Export options
The NFS share is in faulted state on the nodes that are listed. Youcannot access the share through those nodes.
Offline on Nodes
Accessing NFS detailsTo access NFS details
1 In the FileStore Management Console, click Shares > NFS.
2 In the Exports column, click on the name of the NFS share you want to view.
Creating and maintaining Symantec FileStore sharesAbout NFS shares
52
3 In the Shares > NFS > NFS Details page, you can view the followinginformation for the NFS share:
Directory location for the NFS share.Export
Indicates if the NFS share is offline on the specified nodes.Offline on Nodes
Name of the parent file system/snapshot for the NFS share.
Clicking on the hyperlink takes you to the File Systems > FileSystems > File System Details page.
Parent FileSystem/Snapshot
Indicates the type of parent for the NFS share, for example, filesystem.
Type of Parent
4 In the Export Options table, you can view the following information for theNFS share:
Displays the shared clients with the file system. An asterisk (*)indicates all clients.
Clients
Displays the export options when the file system was shared.
See “Sharing a file system” on page 90.
Export Options
Modifying an NFS shareTo modify an NFS share
1 In the FileStore Management Console, click Shares > NFS.
2 Select an NFS share you want to modify.
3 Right-click the name of the NFS share you want to modify, and click Modify,or click the Modify button.
53Creating and maintaining Symantec FileStore sharesAbout NFS shares
4 In the Modify NFS Share dialog box, select the appropriate options for theModify NFS Options field. This is a required field.
Read-only permission to the file system. Hosts mounting thisfile system are not able to make changes to the client.
Read Only(Default)
Read and write permission to the file system. Hosts mountingthis file system are able to make changes to the clients.
Read Write
Synchronous write access to the file system. Forces the serverto perform a disk write before the request is considered complete.
Synchronous
Secure access to the file system. Requires that clients originatefrom a secure port. A secure port is between 1-1024.
Secure
Prevents the root user on an NFS client from having rootprivileges on an NFS mount.
Root Squash
Causes the NFS server to delay writing to the disk if another writerequest is imminent. This can improve performance by reducingthe number of times the disk must be accessed by separate writecommands, reducing write overhead.
Write Delay
Grants asynchronous write access to the file system. Allows theserver to write data to the disk when appropriate.
Async
Grants insecure access to the file system. Permits client requeststo originate from unauthorized ports (those above 1024).
Insecure
Disables the Root Squash option. Allows the root users on theNFS client to have root privileges on the NFS server.
No Root Squash
Disables the Write Delay option.No Write Delay
Verifies that the requested file is in an exported subdirectory. Ifthis option is turned off, the only verification is that the file isin an exported file system.
Subtree Check
Sometimes subtree checking can produce problems when arequested file is renamed while the client has the file open. Ifmany such situations are anticipated, it might be better to setNo Subtree Check. One such situation might be the export of the/home directory file system. Most other situations are besthandled by using the Subtree Check option.
No Subtree Check(Default)
This option allows the FileStore administrator to associate aspecific number as fsid with the share.
Fsid
Creating and maintaining Symantec FileStore sharesAbout NFS shares
54
5 Click OK.
6 In the Result dialog, click OK.
Deleting an NFS shareTo delete an NFS share
1 In the FileStore Management Console, click Shares > NFS.
2 Select the NFS share you want to delete.
3 Right-click the name of the NFS share you want to delete, and click Delete,or click the Delete button.
4 In the Delete NFS Share dialog box, click OK.
5 In the Result dialog, click OK.
About managing CIFS sharesYou can export FileStore file systems to clients as CIFS shares. When a share iscreated, it is given a name. The share name is different from the file system name.Clients use the share name when importing shares.
In addition to exporting file systems as CIFS shares, you can use FileStore to storeuser home directories. Each of these home directories is called a home directoryshare. Shares that are used to export ordinary file systems (that is, the file systemsthat are not used for home directories), are called ordinary shares to distinguishthem from home directory shares.
Viewing information about a CIFS shareTo view information about a CIFS share
◆ In the FileStore Management Console, click Shares > CIFS.
In the CIFS page, you can view the following information for the CIFS share:
Displays the CIFS clustering mode.Clustering Mode
Displays any CIFS home directory file systems.Home DirectoryFile Systems
Displays the security level for the CIFS share.Security
Displays the idmap type and value for the CIFS share.Idmap Backend
55Creating and maintaining Symantec FileStore sharesAbout managing CIFS shares
Name of the CIFS share.
CIFS share names can consist of the following characters: lowerand uppercase letters "a" - "z" and "A" - "Z," numbers "0" - "9"and special characters: "_" and "-". ( "-" cannot be used as the firstcharacter in a share name).
Note: A share name cannot exceed 256 characters.
Share Name
File system or directory path for the CIFS share.FileSystem/DirPath
Parent file system or snapshot.Parent FileSystem/Snapshot
Indicates the type of parent for the CIFS share, for example, filesystem or snapshot.
Parent Type
Export options for the specific share.
Available values include:
■ RO/RW- grants read-only or read-write permissions to a share
■ Guest - specifies if there is a CIFS guest account
■ Oplocks - specifies if there are opportunistic locks on the filesin a share
■ No Oplocks - No opportunistic locks are used for this share.
■ Owner - By default, the FileStore root owns the root directoryof the exported share. This lets CIFS clients create foldersand files in the share. However, there are some operationswhich require owner privileges; for example, changing theowner itself, and changing permissions of the top-level folder(that is, the root directory in UNIX terms). To enable theseoperations, you can set the owner option to a specific username, and this user can perform the privileged operations.
■ Group - By default, the FileStore root is the primary groupowner of the root directory of the exported share. This letsCIFS clients create folders and files in the share. However,there are some operations that require the group privileges;for example, changing the group itself, and changingpermissions of the top-level folder (that is, the root directoryin UNIX terms). To enable these operations, you can set thegroup option to a specific group name and this group canperform the privileged operations.
■ Virtual IP - FileStore lets you specify a virtual IP address. Thisaddress must be part of the FileStore cluster, and is used bythe system to serve the share internally.
Export Options
Creating and maintaining Symantec FileStore sharesAbout managing CIFS shares
56
Type of share.
Available values include:
■ Normal - indicates a normal share type
■ Split - indicates that the share has been split for readjustinga CIFS workload
Share Type
Indicates if the CIFS share is offline on the specified nodes.Offline on nodes
Accessing details for a CIFS shareTo access details for a CIFS share
1 In the FileStore Management Console, click Shares > CIFS.
2 In the Share Name column, click on the name of the CIFS share you want toview.
3 In the Shares > CIFS > CIFS Details page, you can view the followinginformation for the CIFS share:
Name of the CIFS share.Share Name
Indicates if the CIFS share is offline on the specified nodes.Offline on Nodes
Name of the parent file system/snapshot for the CIFS share.
Clicking on the hyperlink takes you to the File Systems > FileSystems > File System Details page.
Parent FileSystem/Snapshot
Indicates the type of parent for the CIFS share, for example, filesystem or snapshot.
Type of Parent
Displays the export options when the CIFS file system was shared.
See “Sharing a file system” on page 90.
Export Options
Indicates the type of share, Normal or Split.Share Type
Adding a CIFS shareTo add a CIFS share
1 In the FileStore Management Console, click Shares > CIFS.
2 Click the Add button.
The Add CIFS Share dialog box displays.
57Creating and maintaining Symantec FileStore sharesAbout managing CIFS shares
3 In the Select File System drop-down menu, select the file system you areadding the share to. This is a required field.
The given file system must not be currently used for storing home directoryshares.
4 In the ShareName field, enter the name of the CIFS share. This is a requiredfield.
Names of FileStore CIFS shares can consist of the following characters: lowerand upper-case letters "a" - "z" and "A" - "Z," numbers "0" - "9" and specialcharacters: "_" and "-". ("-" cannot be used as the first character in a sharename.)
5 In the SetExportOptions box, select the CIFS export options you want appliedto the selected file system. This is a required field.
Select if you want to grant read-only permission to the exportedshare. Files cannot be created or modified.
Read Only
Select if you want to grant read-write permission to the exportedshare.
Read Write
Select if you want to prevent clients from seeing the existenceof files and directories that are not readable to them.
Hide Unreadable
Select if you want to hide system files (lost+found, quotas,quotas.grp) from displaying when using a CIFS normal share.For example, when adding a CIFS normal share, the default is todisplay the system files. To hide the system files, you must usethe Veto System Files CIFS export option.
Veto System Files
Select if you want FileStore to allow restricted access to the sharewhen no user name or password is provided.
Guest
Select if you wantFileStore to always require the user name andpassword for all of the connections to this share.
No Guest
Select if you want FileStore to support opportunistic locks onthe files in this share.
Oplocks
Select if you want FileStore to not use opportunistic locks forthis share.
Disable oplocks when:
■ A file system is exported over both CIFS and NFS protocols
■ Either CIFS or NFS protocols has read and write access
No Oplocks
Creating and maintaining Symantec FileStore sharesAbout managing CIFS shares
58
Select if you want All Windows Access Control Lists (ACLs).
Note: All Windows Access Control Lists (ACLs) are supportedexcept in the case when you attempt using the Windows Explorerfolder Properties>SecurityGUI to inherit down to a non-emptydirectory hierarchy while denying all access to yourself.
Full ACL
Select if you want to enable No Full Access Control Lists (ACLs).
Some advanced Windows Access Control Lists (ACLs)functionality does not work. For example, if you try to create ACLrules on files saved in a CIFS share using Windows explorer whileallowing some set of file access for user1 and denying file accessfor user2, this is not possible when CIFS shares are exportedusing No Full ACL.
No Full ACL
Select if you want FileStore root to own the root directory ofthe exported share. This is by default. This lets CIFS clients createfolders and files in the share. However, there are some operationsthat require owner privileges; for example, changing the owneritself, and changing permissions of the top-level folder (that is,the root directory). To enable these operations, you can set theowner option to a specific user name, and this user can performthe privileged operations.
Owner
Select if you want FileStore root to be the primary group ownerof the root directory of the exported share. This is by default.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 permissionsof the top-level folder (that is, the root directory). To enablethese operations, you can set the group option to a specific groupname and this group can perform the privileged operations.
Group
FileStore lets you specify a virtual IP address. This address mustbe part of the FileStore cluster, and is used by the system to servethe share internally.
Virtual IP
When a file system is exported by CIFS, its mode is set to anfs_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. Thisvalue is reset to 0755 when the CIFS share is deleted. The defaultis: FS Mode = 1777.
FS Mode
59Creating and maintaining Symantec FileStore sharesAbout managing CIFS shares
When a directory is created under a file system exported by CIFS,the necessary permissions are calculated by mapping DOS modesto UNIX permissions. The resulting UNIX mode is then bit-wise'AND'ed with this parameter. Any bit not set here is removedfrom the modes set on a directory when it is created. The defaultis: Dir Mask = 0755.
Dir Mask
When a file is created under a file system exported by CIFS, thenecessary permissions are calculated by mapping DOS modes toUNIX permission. The resulting UNIX mode is then bit-wise'AND'ed with this parameter. Any bit not set here is removedfrom the modes set on a file when it is created. The default is:Create Mask = 0744.
Create Mask
6 Click OK.
7 In the Result dialog, click OK.
Modifying a CIFS shareTo modify a CIFS share
1 In the FileStore Management Console, click Shares > CIFS.
2 Select a CIFS share for which you want to modify.
3 Right-click the name of the NFS share you want to modify, and click Modify,or click the More button, and then click Modify.
4 In the Modify CIFS Share dialog, select the CIFS export options you want tomodify.
Select if you want to grant read-only permission to the exportedshare. Files cannot be created or modified.
Read Only
Select if you want to grant read-write permission to the exportedshare.
Read Write
Select if you want to prevent clients from seeing the existenceof files and directories that are not readable to them.
Hide Unreadable
Select if you want to hide system files (lost+found, quotas,quotas.grp) from displaying when using a CIFS normal share.For example, when adding a CIFS normal share, the default is todisplay the system files. To hide the system files, you must usethe Veto System Files CIFS export option.
Veto System Files
Creating and maintaining Symantec FileStore sharesAbout managing CIFS shares
60
Select if you want FileStore to allow restricted access to the sharewhen no user name or password is provided.
Guest
Select if you wantFileStore to always require the user name andpassword for all of the connections to this share.
No Guest
Select if you want FileStore to support opportunistic locks onthe files in this share.
Oplocks
Select if you want FileStore to not use opportunistic locks forthis share.
Disable oplocks when:
■ A file system is exported over both CIFS and NFS protocols
■ Either CIFS or NFS protocols has read and write access
No Oplocks
Select if you want to enable All Windows Access Control Lists(ACLs).
Note: All Windows Access Control Lists (ACLs) are supportedexcept in the case when you attempt using the Windows Explorerfolder Properties>SecurityGUI to inherit down to a non-emptydirectory hierarchy while denying all access to yourself.
Full ACL
Select if you want to enable No Full Access Control Lists (ACLs).
Some advanced Windows Access Control Lists (ACLs)functionality does not work. For example, if you try to create ACLrules on files saved in a CIFS share using Windows explorer whileallowing some set of file access for user1 and denying file accessfor user2, this is not possible when CIFS shares are exportedusing No Full ACL.
No Full ACL
Select if you want FileStore root to own the root directory ofthe exported share. This is by default. This lets CIFS clients createfolders and files in the share. However, there are some operationsthat require owner privileges; for example, changing the owneritself, and changing permissions of the top-level folder (that is,the root directory). To enable these operations, you can set theowner option to a specific user name, and this user can performthe privileged operations.
Owner
61Creating and maintaining Symantec FileStore sharesAbout managing CIFS shares
Select if you want FileStore root to be the primary group ownerof the root directory of the exported share. This is by default.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 permissionsof the top-level folder (that is, the root directory). To enablethese operations, you can set the group option to a specific groupname and this group can perform the privileged operations.
Group
FileStore lets you specify a virtual IP address. This address mustbe part of the FileStore cluster, and is used by the system to servethe share internally.
Virtual IP
When a file system is exported by CIFS, its mode is set to anfs_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. Thisvalue is reset to 0755 when the CIFS share is deleted. The defaultis: FS Mode = 1777.
FS Mode
When a directory is created under a file system exported by CIFS,the necessary permissions are calculated by mapping DOS modesto UNIX permissions. The resulting UNIX mode is then bit-wise'AND'ed with this parameter. Any bit not set here is removedfrom the modes set on a directory when it is created. The defaultis: Dir Mask = 0755.
Dir Mask
When a file is created under a file system exported by CIFS, thenecessary permissions are calculated by mapping DOS modes toUNIX permission. The resulting UNIX mode is then bit-wise'AND'ed with this parameter. Any bit not set here is removedfrom the modes set on a file when it is created. The default is:Create Mask = 0744.
Create Mask
5 Click OK.
6 In the Result dialog, click OK.
Deleting a CIFS shareTo delete a CIFS share
1 In the FileStore Management Console, click Shares > CIFS.
2 Select the CIFS share you want to delete.
3 Right-click the name of the CIFS share you want to delete, and click Delete,or click the Delete button.
Creating and maintaining Symantec FileStore sharesAbout managing CIFS shares
62
4 In the Delete CIFS Share dialog, verify that you want to delete the selectedCIFS share, and click OK.
5 In the Result dialog, click OK.
About managing CIFS home directoriesYou can use FileStore to store the home directories of CIFS users.
A home directory share name is identical to a FileStore user name. When FileStorereceives a new CIFS connection request, it checks if the requested share is one ofthe ordinary exported shares. If it is not, FileStore checks if the requested sharename 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 thatthe received connection is for a home directory share.
You can access your home directory share the same way you access a file system'sordinary shares. You can connect only to your own home directory.
Viewing information about CIFS home directory users and quotasYou can use FileStore to store home directories of CIFS users and to configureuser and group quotas.
To view information about CIFS home directories and quotas
1 In the FileStore Management Console, click Shares > CIFS.
2 Click Home Directory User and Quota Details.
From the HomeDirectoryUser table, you can view the following informationfor CIFS home directory users:
Name of the CIFS user.User Name
Active Directory/Windows NT domain associated with the user.The term local indicates a local CIFS user.
Domain
File system where the user's home directory is located.Home DirectoryFile Systems
Amount of disk space that is used by the home directory.Usage
From the Home Directory Quota Status table, you can view the followingstatus information about quotas:
File system where the quota is enabled (or disabled).File System
63Creating and maintaining Symantec FileStore sharesAbout managing CIFS home directories
User quota status for the specified file system.
Valid status includes:
■ Enabled
■ Disabled
User Quota Status
Group quota status for the specified file system.
Valid status includes:
■ Enabled
■ Disabled
Group QuotaStatus
From the DefaultQuotaValue table, you can view the following informationabout default quota values:
The quota type: User or Group.Quota
Soft limit for disk space usage.Soft Space
Hard limit for disk space usage.Hard Space
Soft limit for the number of inodes.Soft Inodes
Hard limit for the number of inodes.Hard Inodes
From the User Quota table, you can view the following information aboutuser quotas:
Name of the user.User Name
Amount of disk space currently being used by the user.Space used
The user's soft limit quota for disk space usage.Soft Space
The user's hard limit quota for disk space usage.Hard Space
The number of inodes currently being used by the user.Inodes Used
The user's soft limit quota for the number of inodes.Soft Inodes
The user's hard limit quota for the number of inodes.Hard Inodes
From the Group Quota table, you can view information about group quotas:
Name of the group.Group Name
Amount of disk space currently being used by the group.Space used
Creating and maintaining Symantec FileStore sharesAbout managing CIFS home directories
64
The group's soft limit quota for disk space usage.Soft Space
The group's hard limit quota for disk space usage.Hard Space
The number of inodes currently being used by the group .Inodes Used
The group's soft limit quota for the number of inodes.Soft Inodes
The group's hard limit quota for the number of inodes.Hard Inodes
Setting up a CIFS home directoryHome directory shares are stored in one or more file systems. A single homedirectory can exist only in one of these file systems, but a number of homedirectories can exist in a single home directory file system.
To set up a CIFS home directory
1 In the FileStore Management Console, click Shares > CIFS.
2 Click the ChangeCIFSSettings link to display the Settings>General >CIFSpage.
3 In the Home directory file system(s) field, enter the home directory filesystems name.
Multiple home directory file systems can be entered with comma separators.
4 Click Save.
The home directory file systems display on the Shares > CIFS > HomeDirectory page.
Setting a CIFS home directory userTo set a CIFS home directory user
1 In the FileStore Management Console, click Shares > CIFS.
2 Click the Home Directory User and Quota Details link.
3 In the Shares>CIFS>HomeDirectoryUser table, click the SetUser button.
4 In the Set Home Directory User dialog, update the appropriate fields:
Enter the name of the CIFS user.User Name
Enter the Active Directory/Windows NT domain name or specifylocal for the FileStore local user.
Domain Name
65Creating and maintaining Symantec FileStore sharesAbout managing CIFS home directories
5 Click OK.
6 In the Result dialog, click OK.
Removing a CIFS home directory userTo remove a CIFS home directory user
1 In the FileStore Management Console, click Shares > CIFS.
2 Click the Home Directory User and Quota Details link.
3 In the Shares > CIFS > Home Directory User table, click the user name thatyou want to remove, and click the Remove User button.
4 In the RemoveUser dialog, verify that you want to remove the selected homedirectory user, and click OK.
5 In the Result dialog, click OK.
Removing a CIFS home directory for all usersTo remove a CIFS home directory for all users
1 In the FileStore Management Console, click Shares > CIFS.
2 Click the Home Directory User and Quota Details link.
3 In the Shares > CIFS > Home Directory User table, click the Remove Allbutton.
4 In the Remove All Home Directory Users dialog, verify that you want toremove the home directory for all users, and click OK.
5 In the Result dialog, click OK.
Enabling a CIFS home directory user quotaTo enable a CIFS home directory quota
1 In the FileStore Management Console, click Shares > CIFS.
2 Click the Home Directory User and Quota Details link.
3 In the Shares > CIFS > Home Directory Quota Status table, click the EnableUser Quota button.
4 In the EnableUserQuota dialog, verify that you want to enable the CIFS userquota, and click OK.
5 In the Result dialog, click OK.
Creating and maintaining Symantec FileStore sharesAbout managing CIFS home directories
66
Disabling a CIFS home directory user quotaTo disable a CIFS home directory user quota
1 In the FileStore Management Console, click Shares > CIFS.
2 Click the Home Directory User and Quota Details link.
3 In the Shares>CIFS>HomeDirectoryQuotaStatus table, click the DisableUser Quota button.
4 In the Disable User Quota dialog, verify that you want to disable the CIFSuser quota, and click OK.
5 In the Result dialog, click OK.
Enabling user and group quotasTo enable user and group quotas
1 In the FileStore Management Console, click Shares > CIFS.
2 Click the Home Directory User and Quota Details link.
3 In the Shares > CIFS > Home Directory Quota Status table, click the Morebutton, and click Enable User & Group Quota.
4 In the Enable User & Group Quota dialog, verify that you want to enable aCIFS user quota and group quota, and click OK.
5 In the Result dialog, click OK.
Disabling user and group quotasTo disable user and group quotas
1 In the FileStore Management Console, click Shares > CIFS.
2 Click the Home Directory User and Quota Details link.
3 In the Shares > CIFS > Home Directory Quota Status table, click the Morebutton, and click Disable User & Group Quota.
4 In the Disable User & Group Quota dialog, verify that you want to disable aCIFS user quota and group quota, and click OK.
5 In the Result dialog, click OK.
67Creating and maintaining Symantec FileStore sharesAbout managing CIFS home directories
Enabling a CIFS group quotaTo enable a CIFS group quota
1 In the FileStore Management Console, click Shares > CIFS.
2 Click the Home Directory User and Quota Details link.
3 In the Shares > CIFS > Home Directory Quota Status table, click the Morebutton, and click the Enable Group Quota option.
4 In the Enable Group Quota dialog, verify that you want to enable the CIFSgroup quota, and click OK.
5 In the Result dialog, click OK.
Disabling a CIFS group quotaTo disable a CIFS group quota
1 In the FileStore Management Console, click Shares > CIFS.
2 Click the Home Directory User and Quota Details link.
3 In the Shares > CIFS > Home Directory Quota Status table, click the Morebutton.
4 Click the Disable Group Quota option.
5 In the Disable Group Quota dialog, verify that you want to disable the CIFSgroup quota, and click OK.
6 In the Result dialog, click OK.
Setting the default CIFS quota valueTo set the default CIFS quota value
1 In the FileStore Management Console, click Shares > CIFS.
2 Click the Home Directory User and Quota Details link.
3 In the Shares>CIFS>DefaultQuotaValue table, click the SetDefaultQuotabutton.
Creating and maintaining Symantec FileStore sharesAbout managing CIFS home directories
68
4 In the Set Default Quota dialog, update the appropriate fields:
Select either User Quota or Group Quota from the drop-downmenu.
Quota Type
Enter the soft limit for the number of inodes.Soft Inodes
Enter the hard limit for the number of inodes.Hard Inodes
Enter the soft limit for disk space usage, for example, 10MB.Soft Space
Enter the hard limit for disk space usage, for example, 10MB.Hard Space
5 Click OK.
6 In the Result dialog, click OK.
Modifying the default CIFS quota valueTo modify the default CIFS quota value
1 In the FileStore Management Console, click Shares > CIFS.
2 Click the Home Directory User and Quota Details link.
3 In the Shares>CIFS>DefaultQuotaValue table, click the default quota thatyou want to modify, and click the Modify Default Quota button.
4 In the Modify Default Quota dialog, update the appropriate fields for thetype of quota you want to modify.
Enter the soft limit for the number of inodes.Soft Inodes
Enter the hard limit for the number of inodes.Hard Inodes
Enter the soft limit for disk space usage, for example, 10MB.Soft Space
Enter the hard limit for disk space usage, for example, 10MB.Hard Space
5 Click OK.
6 In the Result dialog, click OK.
Adding a CIFS home directory user quotaUser quota can be set with hard/soft limits on usage. Usage is dictated by thenumber of blocks and number of files that can be created by the user.
69Creating and maintaining Symantec FileStore sharesAbout managing CIFS home directories
To add a CIFS home directory user quota
1 In the FileStore Management Console, click Shares > CIFS.
2 Click the Home Directory User and Quota Details link.
3 In the Shares > CIFS > User Quota table, click Add User Quota.
4 In the Add User Quota dialog, update the appropriate fields:
Enter the name of the CIFS user.User Name
Enter the Active Directory/Windows NTdomain name or specifylocal for the FileStore local user.
Domain Name
Enter the soft limit for the number of inodes.Soft Inodes
Enter the hard limit for the number of inodes.Hard Inodes
Enter the soft limit for disk space usage, for example, 10MB.Soft Space
Enter the hard limit for disk space usage, for example, 10MB.Hard Space
Check this checkbox if you want to set quota values to be thesame as the quota values set for the user or group quotas.
This checkbox only displays if a default quota is set.
Set Default UserQuota
5 Click OK.
6 In the Result dialog, click OK.
Modifying a CIFS home directory user quotaTo modify a CIFS home directory user quota
1 In the FileStore Management Console, click Shares > CIFS.
2 Click the Home Directory User and Quota Details link.
3 In the Shares > CIFS > User Quota table, click a user name requiringmodifications to the user quota, and click Modify User Quota.
Creating and maintaining Symantec FileStore sharesAbout managing CIFS home directories
70
4 In the Modify User Quota dialog, update the appropriate fields:
This field is pre-filled with the domain name.
Enter or modify the Active Directory/Windows NTdomain nameor specify local for the FileStore local user.
Domain Name
Modify the soft limit for the number of inodes.Soft Inodes
Modify the hard limit for the number of inodes.Hard Inodes
Modify the soft limit for disk space usage, for example, 10MB.Soft Space
Modify the hard limit for disk space usage, for example, 10MB.Hard Space
Check this checkbox if you want to set quota values to be thesame as the quota values set for the user or group quotas.
This checkbox only displays if a default quota is set.
Set Default UserQuota
5 Click OK.
6 In the Result dialog, click OK.
Setting a CIFS home directory quota for all usersTo set a CIFS home directory quota for all users
1 In the FileStore Management Console, click Shares > CIFS.
2 Click the Home Directory User and Quota Details link.
3 In the Shares > CIFS > User Quota table, click Set All User Quota.
4 In the Set User Quota for All Users dialog, update the appropriate fields:
Enter the soft limit for the number of inodes.Soft Inodes
Enter the hard limit for the number of inodes.Hard Inodes
Enter the soft limit for disk space usage, for example, 10M.Soft Space
Enter the hard limit for disk space usage, for example, 10M.Hard Space
Check this checkbox if you want to set quota values to be thesame as the quota values set for the user or group quotas.
This checkbox only displays if a default quota is set.
Set Default UserQuota
5 Click OK.
6 In the Result dialog, click OK.
71Creating and maintaining Symantec FileStore sharesAbout managing CIFS home directories
Adding a CIFS home directory group quotaGroup quota can be set with hard/soft limits on usage. Usage is dictated by thenumber of blocks and number of files that can be created by all the users in thegroup.
To add a CIFS home directory group quota
1 In the FileStore Management Console, click Shares > CIFS.
2 Click the Home Directory User and Quota Details link.
3 In the Shares > CIFS > Group Quota table, click Add Group Quota.
4 In the Add Group Quota dialog, update the appropriate fields:
Enter the CIFS group name.Group Name
Enter the Active Directory/Windows NTdomain name or specifylocal for the FileStore local user.
Domain Name
Enter the soft limit for the number of inodes.Soft Inodes
Enter the hard limit for the number of inodes.Hard Inodes
Enter the soft limit for disk space usage, for example, 10M.Soft Space
Enter the hard limit for disk space usage, for example, 10M.Hard Space
Check this checkbox if you want to set quota values to be thesame as the quota values set for the user or group quotas.
This checkbox only displays if a default quota is set.
Set Default UserQuota
5 Click OK.
6 In the Result dialog, click OK.
Modifying a CIFS home directory group quotaGroup quota must be enabled before being able to modify a group quota.
To modify a CIFS home directory group quota
1 In the FileStore Management Console, click Shares > CIFS.
2 Click the Home Directory User and Quota Details link.
3 In the Shares > CIFS > Group Quota table, click a group name for which youwant to modify, and click Modify Group Quota.
Creating and maintaining Symantec FileStore sharesAbout managing CIFS home directories
72
4 In the Modify Group Quota dialog, update the appropriate fields:
This field is pre-filled with the domain name.
Modify the Active Directory/Windows NT domain name or specifylocal for the FileStore local user.
Domain Name
Modify the soft limit for the number of inodes.Soft Inodes
Modify the hard limit for the number of inodes.Hard Inodes
Modify the soft limit for disk space usage, for example, 10M.Soft Space
Modify the hard limit for disk space usage, for example, 10M.Hard Space
Check this checkbox if you want to set quota values to be thesame as the quota values set for the user or group quotas.
This checkbox only displays if a default quota is set.
Set Default UserQuota
5 Click OK.
6 In the Result dialog, click OK.
Setting a CIFS home directory group quota for all usersTo set a CIFS home directory group quota for all users
1 In the FileStore Management Console, click Shares > CIFS.
2 Click the Home Directory User and Quota Details link.
3 In the Shares > CIFS > Group Quota table, click Set All Group Quota.
4 In the Set Group Quota for All Users dialog, update the appropriate fields:
Enter the soft limit for the number of inodes.Soft Inodes
Enter the hard limit for the number of inodes.Hard Inodes
Enter the soft limit for disk space usage, for example, 10M.Soft Space
Enter the hard limit for disk space usage, for example, 10M.Hard Space
5 Click OK.
6 In the Result dialog, click OK.
73Creating and maintaining Symantec FileStore sharesAbout managing CIFS home directories
Changing a CIFS home directory quotaTo change a CIFS home directory quota
1 In the FileStore Management Console, click Shares > CIFS.
2 Click the Change CIFS Settings link.
3 In the Settings > General > CIFS page, update the Home directory globalquota field for the updated quota amount.
4 Click Save.
About FTPThe File Transfer Protocol (FTP) server feature allows clients to access files onthe FileStore servers using the FTP protocol. The FTP service providessecure/non-secure access by way of FTP to files in the FileStore servers. The FTPservice runs on all of the nodes in the cluster and provides simultaneous read/writeaccess to the files. The FTP service also provides configurable anonymous accessto the filer. The FTP operations are used to configure the FTP server.
Viewing information about FTP settingsTo view information about FTP settings
◆ In the FileStore Management Console, click Shares > FTP.
In the FTP window, you can view the following information:
The IDs of the FTP sessions.Session ID
Displays the name of the user using the FTP session.User
Displays the IP address of the user.Client IP
Displays the IP address of the server the user is connecting to.Server IP
Displays the state of the session.State
Name of the file you are transferring.File
Creating and maintaining Symantec FileStore sharesAbout FTP
74
Aborting an FTP sessionTo abort an FTP session
1 In the FileStore Management Console, click Shares > FTP.
2 Select the session ID you want to abort.
3 Right-click the session ID, and click AbortSession, or click the AbortSessionbutton.
4 In the AbortSession dialog, verify that you want to abort the specified session,and click OK.
5 In the Result dialog, click OK.
Uploading an FTP log to a URLTo upload an FTP log to a URL
1 In the FileStore Management Console, click Shares > FTP.
2 Click Upload to URL.
3 In the Upload to URL dialog, enter the appropriate fields:
Enter the URL where the FTP logs are uploaded. The URLsupports both FTP and SCP. If a node name is specified, only thelogs from that node are uploaded.
The default name for the uploaded file is ftp_log.tar.gz.
Enter URL
Click the SelectNode radio button, and specify the node you wantto select from the drop-down menu.
Select Node
Click the AllNodes radio button if you want to upload logs to allnodes.
All Nodes
4 Click OK.
5 In the Result dialog, click OK.
75Creating and maintaining Symantec FileStore sharesAbout FTP
Creating and maintaining Symantec FileStore sharesAbout FTP
76
Creating and maintainingSymantec FileStore filesystems
This chapter includes the following topics:
■ About creating and maintaining file systems
■ Creating a file system
■ Viewing information about a file system
■ About the More button
■ Destroying a file system
■ Editing the snapshot quota
■ Placing a file system online
■ Placing a file system offline
■ Growing a file system
■ Shrinking a file system
■ Sharing a file system
■ About NFS export options
■ About CIFS share options
■ Adding a tier to a file system
■ Running a tier policy
5Chapter
■ Relocating a directory of a tiered file system
■ Adding a mirror to a tiered file system
■ Removing a mirror from a tiered file system
■ Removing a tier from a file system
■ Creating a tier schedule
■ Removing a tier schedule
■ Modifying a tier policy
■ Removing a tier policy
■ Adding a mirror to a file system
■ Removing a mirror from a file system
■ Setting Fast Resync
■ Removing Fast Resync
■ Checking and repairing the consistency of file systems
■ Setting file system alerts
■ Setting file system alerts for all file systems
■ Unsetting file system alerts
■ Unsetting file system alerts for all file systems
■ Enabling Symantec AntiVirus for FileStore Auto-Protect for file systems
■ Disabling Symantec AntiVirus for FileStore Auto-Protect for file systems
■ Stopping Symantec AntiVirus for FileStore manual scans
■ Starting Symantec AntiVirus for FileStore manual scans
■ Accessing the file system details
■ Creating a shared file system
■ About snapshot operations
About creating and maintaining file systemsFile systems consist of both metadata and file system data.
Creating and maintaining Symantec FileStore file systemsAbout creating and maintaining file systems
78
Metadata contains information such as the following:
■ Last modification date
■ Creation time
■ Permissions
The total amount of space required for the metadata depends on the number offiles in the file system. A file system with many small files requires more spaceto store metadata, and file systems with fewer larger files requires less space forhandling the metadata.
When a file system is created, some space needs to be set aside initially for handlingthe metadata. The space required is generally proportional to the size of the filesystem. The space set aside for handling metadata may grow or shrink as andwhen required. A file system on a 1 GB volume takes around 35 MB (about 3%)initially for storing metadata. Whereas a file system of 10 MB requires about 3.3MB (30%) initially for storing the metadata.
Creating a file systemAfter a file system is created, the file system reserves some space for internallogging. Internal logging provides additional data integrity. Due to the spacereserved for internal logging, the file system may appear to be used just after filesystem creation. The space reserved for internal logging increases with the numberof nodes in the FileStore cluster.
Log file sizes for the file systems are as follows:
Log size = 60 M per node10 G to 100 G
Log size = 100 M per node100 G to 1 T
Log size = 256 MB per node1 T and above
To create a file system
1 From the FileStore Management Console, click File Systems > Create.
2 In the Create File System dialog, enter the file system information in theappropriate fields.
Specifies the name of the file system being created. The filesystem name should be a string. If the file system name alreadyexists, an error message is displayed, and the file system will notbe created.
Name of FileSystem (Required)
79Creating and maintaining Symantec FileStore file systemsCreating a file system
You need to select the type of file system you are creating.
■ Simple - creates a simple file system of a specified size, andyou can specify a block size for the file system. (Default)
■ Mirrored - creates a mirrored file system with a specifiednumber of mirrors along with a list of pools, and online status.Each mirror uses the disks from the corresponding pools aslisted.
■ Striped - creates a striped file system. A striped file systemis a file system that stores its data across multiple disks ratherthan storing the data on just one disk.
■ Striped-mirror - creates a striped-mirror file system with aspecified number of mirrors and stripes.
■ Mirrored-stripe - creates a mirrored-stripe file system witha specified number of columns, mirrors, pools, and protectionoptions.
Select Layout
Specifies the number of mirrors the file system has. You mustenter a positive integer.
This field only displays if you selected Mirrored, Striped-mirror,or Mirrored-stripe radio buttons.
Number of Mirrors
Available values include:
■ Disk (default) - creates mirrors on separate disks
■ Pool - creates mirrors in separate pools. If there is not enoughspace to create the mirrors, an error message is displayed,and the file system is not created.
This field only displays if you selected Mirrored, Striped-mirror,or Mirrored-stripe radio buttons.
Protection
Specifies the number of columns for the striped file system. Thenumber of columns represents the number of disks to stripe theinformation across. If the number of columns exceeds the numberof disks for the entered pools, an error message is displayed. Thismessage indicates that there is not enough space to create thestriped file system.
This field only displays if you selected Striped, Striped-mirror,or Mirrored-stripe radio buttons.
Number ofColumns
Creating and maintaining Symantec FileStore file systemsCreating a file system
80
Specifies a stripe width in kilobytes.
Possible values are the following:
■ 128
■ 256
■ 512 - default
■ 1024
■ 2048
This field only displays if you selected Striped, Striped-mirror,or Mirrored-stripe radio buttons.
Stripe Unit
Specifies the block size for the file system.
Possible values of bytes are the following:
■ 1024 - default
■ 2048
■ 4096
■ 8192
The default block size is determined based on the size of the filesystem when the file system is created. For example, 1 KB is thedefault block size for up to a 2 TB file system size. There are otherdefault block sizes, 2 KB, 4 KB, and 8 KB for different ranges offile system sizes. If you create a 1 TB file system, and thenincrease it to 3 TB, the file system block size remains at 1KB.
Block sizes can affect the file size. For example, to create a filesystem greater then 32 TB, the block size needs to be 8192.
Block Size(Required)
Specifies the size of the new file system.
In order to create a file system, a minimum of 10 MB space isrequired.
Available units are the following:
■ KB
■ MB
■ GB
■ TB
Size of File System(Required)
3 Click Next.
81Creating and maintaining Symantec FileStore file systemsCreating a file system
4 In the Select Pool dialog box, select the pool you are creating the file systemfrom.
Click to expand the list of pools.Expand
Click to reduce the list of pools.Collapse
5 Click Finish.
Viewing information about a file systemOnce you have created a file system, you can view the file system in the main FileSystem window.
To view a file system
◆ From the FileStore Management Console, click File Systems.
In the File Systems page, you can view the following information for the filesystem you created:
Name of the file system.Name
Protocol for the file system.
Valid values include:
■ NFS - Linux file system
■ CIFS - Windows file system
Protocol
Dynamic Storage Tiering (DST) indicates if the file system has asecondary tier in its configuration.
Valid values include:
■ Enabled - indicates the a secondary tier was added to the filesystem
■ Disabled - indicates the secondary tier was removed
DST
Displays the status for the file system.
Valid values include:
■ Online - indicates the file system is online
■ Offline - indicates the file system is offline
Status
Number of snapshots for the parent file system.Number ofSnapshots
Displays the layout of the file system.Layout
Creating and maintaining Symantec FileStore file systemsViewing information about a file system
82
Displays if the fast resync operation is enabled or disabled.Fast Resync
Displays if Symantec AntiVirus for FileStore Auto-Protect hasbeen enabled or disabled.
Valid values include:
■ Disabled
■ Enabled
AntiVirusAuto-Protect
Displays the Symantec AntiVirus for FileStore scan status.AntiVirus ScanStatus
Displays the total space for the file system.Total Space
Displays the used space for the file system as a percentage.Used Space
Percentage of used space on the disk.% Used
Displays the snapshot quota status.
Valid values include:
■ on
■ off
Snapshot Quota
Displays the capacity limit of all the snapshots for a file system.Capacity Limit
Displays the status for checking and repairing the specified filesystem, fsck.
Valid values include:
■ Running
■ Done successfully
■ Failed
■ Unknown
■ Not Running
Full Check Status
Displays the defragmentation status for the specified file system.
Valid values include:
■ Running
■ Done successfully
■ Stopped
■ Failed
■ Not Running
Defrag Status
83Creating and maintaining Symantec FileStore file systemsViewing information about a file system
About the More buttonIn the main FileSystem window, you can use the More button to list the operationsyou can select to configure your file system.
Table 5-1 File system operations
DefinitionVariable
Creates a file system.
See “Creating a file system” on page 79.
Create
Manages snapshots.
See “Managing snapshots” on page 114.
Manage Snapshot
Restores snapshots.
See “Restoring a snapshot” on page 116.
Restore Snapshot
Places a file system offline and releases its storage back to the storagepool. You can only destroy an unshared file system. You must deletethe share before you can destroy the file system.
See “Destroying a file system” on page 87.
Destroy
Changes the configuration of the snapshot quota which you set duringthe creation of the file system.
See “Editing the snapshot quota” on page 87.
Edit SnapshotQuota
Places a file system online.
See “Placing a file system online” on page 88.
Online
Places a file system offline.
See “Placing a file system offline” on page 88.
Offline
Increases the size of a file system by a specified size or to a specifiedsize.
If the file system is not online, an error message is displayed, and noaction is taken.
See “Growing a file system” on page 89.
Grow
Creating and maintaining Symantec FileStore file systemsAbout the More button
84
Table 5-1 File system operations (continued)
DefinitionVariable
Decreases the size of a file system by a specified size or to a specifiedsize.
To decrease the size of the file system, it must be online. If the filesystem is not online, an error message is displayed, and no action istaken.
See “Shrinking a file system” on page 89.
Shrink
Shares the file system using the NFS or CIFS protocols, with theselected export options.
See “Sharing a file system” on page 90.
Share
Creates a secondary tier on the file system.
See “Adding a tier to a file system” on page 94.
Create Tier
Runs a tier policy for a tiered file system.
See “Running a tier policy” on page 95.
Run Tier Policy
Relocates a directory of a tiered file system.
See “Relocating a directory of a tiered file system” on page 96.
Relocate Tier
Adds a mirror to a tiered file system.
See “Adding a mirror to a tiered file system” on page 96.
Add Tier Mirror
Removes a mirror from a tiered file system.
See “Removing a mirror from a tiered file system” on page 97.
Remove TierMirror
Removes a secondary tier from the file system.
See “Removing a tier from a file system” on page 97.
Remove Tier
Creates a tier schedule.
See “Creating a tier schedule” on page 97.
Tier Schedule
Removes a tier schedule.
See “Removing a tier schedule” on page 98.
Remove TierSchedule
Modifies a tier policy.
See “Modifying a tier policy” on page 98.
Modify Tier Policy
Removes a tier policy.
See “Removing a tier policy” on page 99.
Remove Policy
85Creating and maintaining Symantec FileStore file systemsAbout the More button
Table 5-1 File system operations (continued)
DefinitionVariable
Adds a mirror to the file system.
See “Adding a mirror to a file system” on page 99.
Add Mirror
Removes a mirror from the file system.
See “Removing a mirror from a file system” on page 100.
Remove Mirror
The Fast Resync (Fast Mirror Resynchronization) variable keeps themirror in the file system in a consistent state. If the power fails or aswitch fails, mirrors in the file system may not be in a consistent state.
Note: You must have at least two mirrors on the file system to enableFast Resync.
See “Setting Fast Resync” on page 100.
Set FastResync
Disables the Fast Resync operation on the selected file system.
See “Removing Fast Resync” on page 101.
Unset FastResync
Checks the consistency of the file system.
See “Checking and repairing the consistency of file systems”on page 101.
Check File System
Sets file system alerts.
See “Setting file system alerts” on page 102.
Set Alert
Sets file system alerts for all file system.
See “Setting file system alerts for all file systems” on page 102.
Set Alert for All
Unsets file system alerts.
See “Unsetting file system alerts” on page 103.
Unset Alert
Unsets alerts for all file systems.
See “Unsetting file system alerts for all file systems” on page 103.
Unset Alert for All
Enables Symantec AntiVirus for FileStore Auto-Protect (AP) on selectedfile systems
See “Enabling Symantec AntiVirus for FileStore Auto-Protect for filesystems” on page 104.
Enable AVAuto-Protect
Creating and maintaining Symantec FileStore file systemsAbout the More button
86
Table 5-1 File system operations (continued)
DefinitionVariable
Disables Symantec AntiVirus for FileStore Auto-Protect (AP) onselected file systems.
See “Disabling Symantec AntiVirus for FileStore Auto-Protect for filesystems” on page 104.
Disable AVAuto-Protect
Starts the Symantec AntiVirus for FileStore manual scan on selectedfile systems.
See “Starting Symantec AntiVirus for FileStore manual scans”on page 105.
Start AV Scan
Stops the Symantec AntiVirus for FileStore manual scan on selectedfile systems.
See “Stopping Symantec AntiVirus for FileStore manual scans”on page 105.
Stop AV Scan
Destroying a file system
Note: NFS/CIFS shared file systems cannot be destroyed unless you first deletethe share. Also, you must use the Storage> fs destroy CLI command to destroya DAR-enabled file system. You cannot use the FileStore Management Console.
To destroy a file system
1 From the FileStore Management Console, click File Systems.
2 Select the file system that you want to destroy.
3 From the More drop-down menu, select Destroy, or right-click the name ofthe file system, and click Destroy.
4 In the Destroy File System dialog box, click OK.
5 In the Result dialog, click OK.
Editing the snapshot quotaOnce you have edited the snapshot quota, quota information (Quota and CapacityLimit) are displayed on the File Systems table.
87Creating and maintaining Symantec FileStore file systemsDestroying a file system
To edit the snapshot quota
1 From the FileStore Management Console, click File Systems.
2 Select the file system you want to edit the snapshot quota on.
3 From the More drop-down menu, select Edit Snapshot Quota, or right-clickthe name of the file system, and click Edit Snapshot Quota.
4 In the Edit Snapshot Quota dialog box, click on the status of the file system.
5 Enter the new quota in the Quota box.
6 Click OK.
7 In the Result dialog, click OK.
Placing a file system onlineTo place a file system online
1 From the FileStore Management Console, click File Systems.
2 Select a file system that you want to mount (place online).
3 From the More drop-down menu, select Online, or right-click the name ofthe file system, and click Online.
4 In the Online File System dialog box, click OK.
5 In the Result dialog, click OK.
Placing a file system offlineTo place a file system offline
1 From the FileStore Management Console, click File Systems.
2 Select a file system that you want to unmount (place offline).
3 From the More drop-down menu, select Offline, or right-click the name ofthe file system, and click Offline.
4 In the Offline File System dialog box, click OK.
5 In the Result dialog, click OK.
Creating and maintaining Symantec FileStore file systemsPlacing a file system online
88
Growing a file systemTo increase the size of a file system
1 From the FileStore Management Console, click File Systems.
2 Select the file system whose size that you want to increase.
3 From the More drop-down menu, select Grow, or right-click the name of thefile system, and click Grow.
4 In the GrowFile System dialog box, select the appropriate options, and clickOK.
Increases the size of a file system by a specified size (inMegabytes, Gigabytes, or Terabytes).
Grow by Size(Required)
Increases the size of a file system to a specified size (inMegabytes, Gigabytes, or Terabytes).
Grow Size to
Select the disk associated with the file system.Select Disk
Select the pool associated with the file system.Select Pool
Select the type of protection for the file system.
Valid values include:
■ Pool - if Pool is entered, mirrors are created in separate pools.If there is not enough room for creating the mirrors, an errormessage is displayed, and the file system is not created.
■ Disk - if Disk is entered, mirrors are created on separate disks.
Protection
5 In the Result dialog, click OK.
Shrinking a file systemTo decrease the size of a file system
1 From the FileStore Management Console, click File Systems.
2 Select the file system whose size that you want to shrink.
3 From the More drop-down menu, select Shrink, or right-click the name ofthe file system, and click Shrink.
89Creating and maintaining Symantec FileStore file systemsGrowing a file system
4 In the ShrinkFileSystem dialog box, select the appropriate options, and clickOK.
Decrease the size of the file system by an amount (in Megabytes,Gigabytes, or Terabytes).
Shrink by size
Decrease the size of the file system to a specific size (inMegabytes, Gigabytes, or Terabytes).
Shrink to size
5 In the Result dialog, click OK.
Sharing a file systemTo share a file system
1 From the FileStore Management Console, click File Systems.
2 Select the file system you want to share.
3 From the More drop-down menu, select Share, or right-click the name of thefile system, and click Share.
4 In the Share File System dialog box, select the settings for the specified filesystem (for Share Type, select either the radio button for NFS or CIFS).
See “About NFS export options” on page 90.
See “About CIFS share options” on page 92.
5 Click OK.
6 In the Result dialog, click OK.
About NFS export optionsLinux file systems use the Network File System (NFS) protocol.
If you select NFS as the type of shared file system you want to create, you needto provide the following information:
■ Read Only (Default) - Grants read-only permission to the exported share. Filescannot be created or modified. This is the default value.
■ Read Write - Grants read and write permission to the exported share.
■ Synchronous (Default) - Grants synchronous write access to the file system.Forces the server to perform a disk write before the request is consideredcomplete.
Creating and maintaining Symantec FileStore file systemsSharing a file system
90
■ Async - Grants asynchronous write access to the file system. Allows the serverto write data to the disk when appropriate.
■ Secure (Default) - Grants secure access to the file system. Requires that clientsoriginate from a secure port. A secure port is between 1-1024.
■ Insecure - Grants insecure access to the file system. Permits client requeststo originate from unprivileged ports (those above 1024).
■ Secure Locks (Default) - Requires authorization of all locking requests.
■ Insecure Locks - Some NFS clients do not send credentials with lock requests,and therefore work incorrectly with Secure Locks, in which case you can onlylock world-readable files. If you have such clients, either replace them withbetter ones, or use the Insecure Locks option.
■ Root Squash (Default) - Prevents the root user on an NFS client from havingroot privileges on an NFS mount.
■ No Root Squash - Disables the Root Squash option. Allows root users on theNFS client to have root privileges on the NFS server.
■ Write Delay (Default) - Causes the NFS server to delay writing to the disk ifanother write request is imminent. This can improve performance by reducingthe number of times the disk must be accessed by separate write commands,reducing write overhead.
■ No Write Delay - Disables the Write Delay option.
■ Subtree Check - 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 exportedfile system.
■ No Subtree Check (Default) - Sometimes subtree checking can produce problemswhen a requested file is renamed while the client has the file open. If manysuch situations are anticipated, it might be better to set No Subtree Check.One such situation might be the export of the home directory. Most othersituations are best handled with Subtree Check.
■ Fsid - Signals to the NFS server that this export is the root.
Clients may be specified in the following ways:
■ Single host - specify a host either by an abbreviated name that is recognizedby the resolver (DNS is the resolver), the fully-qualified domain name, or anIP address.
■ Netgroups - netgroups may be given as @group. Only the host part of eachnetgroup member is considered for checking membership.
91Creating and maintaining Symantec FileStore file systemsAbout NFS export options
If the client is not given, then the specified file system can be mounted oraccessed by any client. To re-export new options to an existing share, the newoptions will be updated after the command is run.
About CIFS share optionsWindows file systems use the Common Internet File System (CIFS) protocol.
If you select CIFS as the type of shared file system you want to create, you needto provide the following information:
ShareName - The name for the newly-exported CIFS share. Names for the FileStoreCIFS shares 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.) Share Name is a requiredfield.
Choose the export options for the CIFS share from the following list:
■ Read Only (Default) - Grants read-only permission to the exported share. Filescannot be created or modified. This is the default value.
■ Read Write - Grants read and write permission to the exported share.
■ Hide Unreadable - Prevents clients from seeing the existence of files anddirectories that are not readable to them.
■ Veto System Files - Hides system files (lost+found, quotas, quotas.grp) fromdisplaying when using a CIFS normal share. For example, when adding a CIFSnormal share, the default is to display the system files. To hide the systemfiles, you must use the Veto System Files CIFS export option.
■ Guest - FileStore allows restricted access to the share when no user name orpassword is provided.
■ No Guest (Default) - FileStore always requires the user name and passwordfor all of the connections to this share. This is the default value.
■ Oplocks (Default) - FileStore supports opportunistic locks on the files in thisshare. This is the default value.
■ No Oplocks - No opportunistic locks will be used for this share. Disable theoplocks when:1) A file system is exported over both CIFS and NFS protocols.2) Either CIFS or NFS protocol has read and write access.
■ Full ACL - All Windows Access Control Lists (ACLs) are supported except inthe case when you attempt using the Windows Explorer folder Properties >
Creating and maintaining Symantec FileStore file systemsAbout CIFS share options
92
SecurityGUI to inherit down to a non-empty directory hierarchy while denyingall access to yourself.
■ No Full ACL (Default) - Some advanced Windows Access Control Lists (ACLs)functionality does not work. For example, if you try to create ACL rules onfiles saved in a CIFS share using Windows explorer while allowing some setof file access for user1 and denying file access for user2, this is not possiblewhen CIFS shares are exported using the No Full ACL export option.
■ Owner (Default) - By default, the FileStore root owns the root directory of theexported share. This lets CIFS clients create folders and files in the share.However, there are some operations which require owner privileges; forexample, changing the owner itself, and changing permissions of the top-levelfolder (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 performthe privileged operations.
■ Group (Default) - By default, the FileStore root is the primary group owner ofthe root directory of the exported share. This lets CIFS clients create foldersand files in the share. However, there are some operations that require groupprivileges; for example, changing the group itself, and changing permissionsof the top-level folder (that is, the root directory in UNIX terms). To enablethese operations, you can set the group option to a specific group name andthis group can perform the privileged operations.
■ Virtual IP - FileStore lets you specify a virtual IP address. This address mustbe part of the FileStore cluster, and is used by the system to serve the shareinternally.
■ FS Mode (Default) - When a file system is exported by CIFS, its mode is set toan fs_mode value. It is the UNIX access control set on a file system, and CIFSoptions like rw/ro do not take precedence over it. This value is reset to 0755when the CIFS share is deleted. The default is: FS Mode = 1777.
■ Dir Mask (Default) - When a directory is created under a file system exportedby CIFS, the necessary permissions are calculated by mapping DOS modes toUNIX permissions. The resulting UNIX mode is then bit-wise 'AND'ed withthis parameter. Any bit not set here is removed from the modes set on adirectory when it is created. The default is: Dir Mask = 0755.
■ Create Mask (Default) - When a file is created under a file system exported byCIFS, the necessary permissions are calculated by mapping DOS modes toUNIX permission. The resulting UNIX mode is then bit-wise 'AND'ed with thisparameter. Any bit not set here is removed from the modes set on a file whenit is created. The default is: Create Mask = 0744.
93Creating and maintaining Symantec FileStore file systemsAbout CIFS share options
Adding a tier to a file systemFileStore provides two types of tiers, a primary and a secondary tier. Each filesystem that is created includes a primary tier. This tier cannot be removed.Operations like Add Mirror, Grow, and Shrink, are applied to the primary tier.
An additional (secondary) storage tier can be added to the file system. A file systemcan only support a maximum of two storage tiers.
To add a tier to a file system
1 From the FileStore Management Console, click File Systems.
2 Select a file system that you want to add a tier for.
3 From the More drop-down menu, select Add Tier, or right-click the name ofthe file system, and click Add Tier.
4 In the Add Tier dialog box, select the appropriate options, and click Next.
Indicates the name of the file system you selected for adding atier.
Name of FileSystem
You need to select the type of file system you are creating.
■ Simple - creates a simple file system of a specified size, andyou can specify a block size for the file system. (Default)
■ Mirrored - creates a mirrored file system with a specifiednumber of mirrors along with a list of pools. Each mirror usesthe disks from the corresponding pools as listed.
■ Striped - creates a striped file system. A striped file systemis a file system that stores its data across multiple disks ratherthan storing the data on just one disk.
■ Striped-mirror - creates a striped-mirror file system with aspecified number of mirrors and stripes.
■ Mirrored-stripe - creates a mirrored-stripe file system witha specified number of columns, mirrors, pools, and protectionoptions.
Select Layout
Specifies the number of mirrors the file system has. The numberof mirrors entered must be a positive integer.
Number of Mirrors
Creating and maintaining Symantec FileStore file systemsAdding a tier to a file system
94
If not specified, the default for the protection field is "disk."
The available options for this field are:
■ Disk - if "Disk" is selected from the drop-down menu, mirrorsare created on separate disks.
■ Pool - if "Pool" is selected from the drop-down menu, mirrorsare created in separate pools. If there is not enough room forcreating the mirrors, an error message is displayed, and thefile system is not created.
Protection
Specifies the number of columns for the striped file system. Thenumber of columns represents the number of disks to stripe theinformation across. If the number of columns exceeds the numberof disks for the entered pools, an error message is displayed. Thismessage indicates that there is not enough space to create thestriped file system.
Number ofColumns
Specifies a stripe width (in kilobytes).
Possible values are the following:
■ 128
■ 256
■ 512 (default)
■ 1024
■ 2048
Stripe Unit
Specifies the size of the tier.
Available units are the following:
■ KB
■ MB
■ GB
■ TB
Tier Size(Required)
5 In the Select Pool dialog box, select the pool you want the secondary tier toreside on.
6 Click Finish.
Running a tier policyTo run a tier policy for a tiered file system
1 From the FileStore Management Console, click File Systems.
2 Select a tiered file system for which you want to run a tier policy.
95Creating and maintaining Symantec FileStore file systemsRunning a tier policy
3 From the More drop-down menu, select Run Tier Policy, or right-click thename of the tiered file system, and click Run Tier Policy.
4 In the RunTierPolicy dialog, verify that you want to run a tier policy for theselected file system, and click OK.
5 In the Result dialog, click OK.
Relocating a directory of a tiered file systemTo relocate a directory of a tiered file system
1 From the FileStore Management Console, click File Systems.
2 Select a tiered file system for which you want to relocate a directory.
The relocation of the directory is done from the secondary tier to the primarytier.
3 From the More drop-down menu, select Relocate Tier , or right-click thename of the tiered file system, and click Relocate Tier.
4 In the RelocateTier dialog, enter the relative path of the directory you wantto relocate, and click OK.
5 In the Result dialog, click OK.
Adding a mirror to a tiered file systemTo add a mirror to a tiered file system
1 From the FileStore Management Console, click File Systems.
2 Select a tiered file system for which you want to add a mirror.
3 From the More drop-down menu, select Add Tier Mirror , or right-click thename of the tiered file system, and click Add Tier Mirror.
4 In the AddTierMirror dialog, select either Pool or Disk from the drop-downmenu.
This specifies the pool or disk that will be used as a mirror for the specifiedfile system.
If disk is selected for the Protection field, then mirrors are created on separatedisks. The disks may or may not be in the same pool.
The disk needs to be part of the pool, or an error message displays.
5 Click OK.
6 In the Result dialog, click OK.
Creating and maintaining Symantec FileStore file systemsRelocating a directory of a tiered file system
96
Removing a mirror from a tiered file system
Note: For a striped-mirror file system, if any of the disks are bad, this operationdisables 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 filesystem.
To remove a mirror from a tier
1 From the FileStore Management Console, click File Systems.
2 Select a tiered file system for which you want to remove a mirror.
3 From the More drop-down menu, select Remove Tier Mirror , or right-clickthe name of the tiered file system, and click Remove Tier Mirror.
4 In the Remove Tier Mirror dialog, select either to remove the mirror on thepool or the disk, or click OK to remove any one mirror on the tier.
If nothing is selected, one mirror will be removed. FileStore decides whichmirror should be removed.
The FileStore Management Console decides which mirror should be removed.
5 In the Result dialog, click OK.
Removing a tier from a file systemTo remove a tier from a file system
1 From the FileStore Management Console, click File Systems.
2 Select a file system that you want to remove a tier from.
3 From the More drop-down menu, select RemoveTier, or right-click the nameof the file system, and click Remove Tier.
4 In the Remove Tier dialog box, click OK.
5 In the Result dialog, click OK.
Creating a tier scheduleTo create a tier schedule
1 From the FileStore Management Console, click File Systems.
2 Select a file system that you want to create a tier schedule for.
97Creating and maintaining Symantec FileStore file systemsRemoving a mirror from a tiered file system
3 From the More drop-down menu, select Tier Schedule, or right-click thename of the file system, and click Tier Schedule.
4 For the Schedule field, specify the minute, hour, day of the month, day of theweek, and month from the drop-down menus for running the tier schedule.
For the Minute drop-down, an asterisk implies running a schedule everyminute.
For the Hour drop-down, an asterisk implies running a schedule every hour.
For the Dayof theMonth drop-down, an asterisk implies running a scheduleevery day of the month.
For the Day of the Week drop-down, an asterisk implies running a scheduleevery day of the week.
For the Month drop-down, an asterisk implies running a schedule everymonth.
5 Click OK.
6 In the Result dialog, click OK.
Removing a tier scheduleTo remove a tier schedule
1 From the FileStore Management Console, click File Systems.
2 Select a file system that you want to remove a tier schedule for.
3 From the More drop-down menu, select RemoveTierSchedule, or right-clickthe name of the file system, and click Remove Tier Schedule.
4 In the Remove Tier Schedule dialog, verify that you want to remove the tierschedule for the selected file system, and click OK.
5 In the Result dialog, click OK.
Modifying a tier policyTo modify a tier policy
1 From the FileStore Management Console, click File Systems.
2 Select a file system that you want to modify a tier policy for.
3 From the More drop-down menu, select Modify Tier Policy, or right-clickthe name of the file system, and click Modify Tier Policy.
Creating and maintaining Symantec FileStore file systemsRemoving a tier schedule
98
4 In the Modify Tier Policy dialog, update the following fields:
Displays the name of the file system you selected to modify.File System
Select the radio button for the primary or the secondary tier.Create files on
Specify the number of days from which the inactive files movefrom the primary to the secondary tier.
Specify Duration(Required)
Specify the minimum I/O requests for moving files from thesecondary to the primary tier.
If the I/O requests exceed the specified number in the Durationfield, the file is considered active, and the file is moved to theprimary tier.
Min I/O requests(Required)
Specify the number of days used for calculating the I/O requests.Duration(Required)
5 Click OK.
6 In the Result dialog, click OK.
Removing a tier policyTo remove policy options
1 From the FileStore Management Console, click File Systems.
2 Select a file system that you want to remove a tier policy for.
3 From the More drop-down menu, select Remove Policy, or right-click thename of the file system, and click Remove Policy.
4 In the Remove Policy dialog, verify that you want to remove the policy forthe selected file system, and click OK.
5 In the Result dialog, click OK.
Adding a mirror to a file systemTo add a mirror to a file system
1 From the FileStore Management Console, click File Systems.
2 Select a file system you want to add a mirror to.
3 From the More drop-down menu, select AddMirror, or right-click the nameof the file system, and click Add Mirror.
99Creating and maintaining Symantec FileStore file systemsRemoving a tier policy
4 In the Add Mirror dialog box, select the appropriate settings and click OK.
Select the pool you are adding the mirror to.Select Storage
Select the type of protection for the file system.
If not specified, the default for the Protection field is Disk.
Valid values include:
■ Pool - if Pool is entered, mirrors are created in separate pools.If there is not enough room for creating the mirrors, an errormessage is displayed, and the file system is not created.
■ Disk - if Disk is entered, mirrors are created on separate disks.
Protection
5 In the Result dialog, click OK.
Removing a mirror from a file systemTo remove a mirror from a file system
1 From the FileStore Management Console, click File Systems.
2 Select a file system that you want to remove a mirror from.
3 From the More drop-down menu, select Remove Mirror, or right-click thename of the file system, and click Remove Mirror.
4 In the Remove Mirror dialog box, select the appropriate settings and clickOK.
Specifies the pool you want to remove from the mirrored filesystem. If you specify a pool that is not part of the mirrored filesystem , an error message is displayed, and no action is taken.
Select Pool
Specifies the disk to remove from the mirrored file system. If youspecify a pool that is not part of the mirrored file system , anerror message is displayed, and no action is taken.
Select Disk
5 In the Result dialog, click OK.
Setting Fast ResyncTo set Fast Resync
1 From the FileStore Management Console, click File Systems.
2 Select a file system you want to set Fast Resync on.
Creating and maintaining Symantec FileStore file systemsRemoving a mirror from a file system
100
3 From the More drop-down menu, select Set Fast Resync, or right-click thename of the file system, and click Set Fast Resync.
4 In the Set Fast Resync dialog box, select the appropriate settings and clickOK.
Specifies the pool you want to set Fast Resync on.Select Pool
Specifies the disk you want to set Fast Resync on.Select Disk
5 In the Result dialog, click OK.
Removing Fast ResyncTo remove Fast Resync
1 From the FileStore Management Console, click File Systems.
2 Select a file system you want to remove Fast Resync from.
3 From the More drop-down menu, select Unset Fast Resync, or right-clickthe name of the file system, and click Unset Fast Resync.
4 In the Unset Fast Resync dialog box, click OK to remove Fast Resync.
5 In the Result dialog, click OK.
Checking and repairing the consistencyof file systemsThe specified file system must be offline to run the CheckFile System operation.
To check and repair the consistency of file systems
1 From the FileStore Management Console, click File Systems.
2 Select a file system for which you want to check.
3 From the More drop-down menu, select CheckFileSystem, or right-click thename of the file system, and click Check File System.
4 In the Check File System dialog, verify that you want to check the specifiedfile system, and click OK.
5 In the Result dialog, click OK.
101Creating and maintaining Symantec FileStore file systemsRemoving Fast Resync
Setting file system alertsTo set file system alerts
1 From the FileStore Management Console, click File Systems.
2 Select a file system for which you want to set alerts.
3 From the More drop-down menu, select SetAlert, or right-click the name ofthe file system, and click Set Alert.
4 In the Set Alert dialog, update the following fields, and click OK.
Numeric value of used file system space required to generate analert.
Enter the percentage to trigger the alert. By default, the alert isset to 80%.
Used Space(Required -depends onselection)
Numeric value indicating the number of inodes required togenerate an alert.
Enter the numeric value to trigger the alert.
Number of Inodes(Required -depends onselection)
5 In the Result dialog, click OK.
Setting file system alerts for all file systemsTo set file system alerts for all file systems
1 From the FileStore Management Console, click File Systems.
2 From the More drop-down menu, select Set Alert for All, or right-click thename of the file system, and click Set Alert for All.
Creating and maintaining Symantec FileStore file systemsSetting file system alerts
102
3 In the Set Alert for All dialog, update the following fields, and click OK.
Numeric value of used file system space required to generate analert.
Enter the percentage to trigger the alert. By default, the alert isset to 80%.
Used Space(Required -depends onselection)
Numeric value indicating the number of inodes required togenerate an alert.
Enter the numeric value to trigger the alert.
Number of Inodes(Required -depends onselection)
4 In the Result dialog, click OK.
Unsetting file system alertsYou can unset the alerts set on a file system. If you unset an alert on any filesystem, you receive alerts for the file systems based on the default values.
To unset file system alerts
1 From the FileStore Management Console, click File Systems.
2 Select a file system for which you want to unset the alerts.
3 From the More drop-down menu, select UnsetAlert, or right-click the nameof the file system, and click Unset Alert.
4 In the Unset Alert dialog, select either the Used Space radio button or theNumber of Inodes radio button, and click OK.
5 In the Result dialog, click OK.
Unsetting file system alerts for all file systemsTo unset file system alerts for all file systems
1 From the FileStore Management Console, click File Systems.
2 From the More drop-down menu, select Unset Alert for All, or right-clickthe name of the file system, and click Unset Alert for All.
3 In the Unset Alert for All dialog, select either the Used Space radio buttonor the Number of Inodes radio button, and click OK.
4 In the Result dialog, click OK.
103Creating and maintaining Symantec FileStore file systemsUnsetting file system alerts
Enabling Symantec AntiVirus for FileStoreAuto-Protect for file systems
Symantec AntiVirus for FileStore provides two methods for protecting your data:
■ Auto-Protect (AP) scan - protects files and file systems as they are accessed(when a file is opened, modified, or executed).
■ Scheduled scan - scans file systems for viruses when requested or at scheduledintervals. By default, whenever a file system is created, Auto-Protect on thatfile system is in the Disabled state.
To enable Symantec AntiVirus for FileStore Auto-Protect for file systems
1 From the FileStore Management Console, click File Systems.
2 Select a file system or multiple file systems you want to enable for SymantecAntiVirus for FileStore Auto-Protect (AP).
See “About Symantec AntiVirus for FileStore” on page 164.
3 From the More drop-down menu, select EnableAVAutoProtect, or right-clickthe name of the file system or multiple file systems, and click Enable AVAuto Protect.
4 In the Auto Protect Enable dialog, verify that you want to enable the filesystem(s) for Auto-Protect, and click OK.
5 In the Result dialog, click OK.
Disabling Symantec AntiVirus for FileStoreAuto-Protect for file systems
To disable Symantec AntiVirus for FileStore Auto-Protect for file systems
1 From the FileStore Management Console, click File Systems.
2 Select a file system or multiple file systems you want to disable for SymantecAntiVirus for FileStore Auto-Protect (AP).
See “About Symantec AntiVirus for FileStore” on page 164.
3 From the More drop-down menu, select Disable AV Auto Protect, orright-click the name of the file system or multiple file systems, and clickDisable AV Auto Protect.
4 In the Auto Protect Disable dialog, verify that you want to disable the filesystem(s) for Auto-Protect, and click OK.
5 In the Result dialog, click OK.
Creating and maintaining Symantec FileStore file systemsEnabling Symantec AntiVirus for FileStore Auto-Protect for file systems
104
Stopping Symantec AntiVirus for FileStore manualscans
To stop Symantec AntiVirus for FileStore manual scans
1 From the FileStore Management Console, click File Systems.
2 Select a file system that you want to stop running Symantec AntiVirus forFileStore scans for.
See “About Symantec AntiVirus for FileStore” on page 164.
3 From the More drop-down menu, select StopAVScan, or right-click the nameof the file system, and click Stop AV Scan.
4 In the Stop AV Scan dialog, verify that you want to stop the AV scan, andclick OK.
5 In the Result dialog, click OK.
Starting Symantec AntiVirus for FileStore manualscans
You can choose to manually scan files on an as-needed basis or to have automatedscans performed at regular intervals.
To start Symantec AntiVirus for FileStore manual scans
1 From the FileStore Management Console, click File Systems.
2 Select a file system that you want to start running Symantec AntiVirus forFileStore scans for.
See “About Symantec AntiVirus for FileStore” on page 164.
3 From the More drop-down menu, select Start AV Scan, or right-click thename of the file system, and click Start AV Scan.
4 In the Start AV Scan dialog, select the preferred node from the PreferredNode drop-down list, and click OK.
5 In the Result dialog, click OK.
Accessing the file system detailsClick on the name of a file system to view file system details for the selected filesystem.
From the FileSystemsDetails page, you can also perform the following operations:
105Creating and maintaining Symantec FileStore file systemsStopping Symantec AntiVirus for FileStore manual scans
■ Share a file systemSee “Sharing a file system” on page 90.
■ Manage snapshotsSee “Managing snapshots” on page 114.
■ Destroy a file systemSee “Destroying a file system” on page 87.
■ Create a tier for a file systemSee “Adding a tier to a file system” on page 94.
To view a file system
1 From the FileStore Management Console, click File Systems.
2 In the Name column, click on the file system you want to view.
3 In the FileSystemsDetails page, you can view the following information forthe file system:
Name of the file system.Name
Status for the file system, either online or offline.Status
Total space available for the file system.Total Space
Displays which nodes are online for the file system.File System OnlineNodes
Displays which nodes are offline for the file system.File System OfflineNodes
Used space for the file system as a percentage.Used Space
Displays the block size selected during file system creation.Block Size
Protocol for the file system, either CIFS or NFS.
Clicking on the CIFS or the NFS link takes you to the Shares >NFS or the Shares > CIFS page.
Protocol
Displays if the fast resync operation is enabled or disabled.Fast Resync
Number of snapshots for the parent file system.
Clicking on the Manage Snapshot button takes you to theSnapshots detail page.
Snapshots
Lists the snapshot schedules created for this file system.AutomatedSnapshotSchedules
Creating and maintaining Symantec FileStore file systemsAccessing the file system details
106
Displays if Symantec AntiVirus for FileStore Auto-Protect hasbeen enabled or disabled.
AntiVirusAuto-Protect
Displays the Symantec AntiVirus for FileStore scan status.AntiVirus ScanStatus
Displays the number of Symantec AntiVirus for FileStore jobs.AntiVirus Jobs
Displays the value as a percentage to trigger the alert based onthe file system usage. By default, the alert is set at 80%.
Space Alert Value
Displays the current file system used space as a percentage.Current UsedSpace
Displays the value as a percentage to trigger the alert based onthe number of inodes used. By default, the alert is set at 80%.
Number of InodesAlert Value
Displays the current number of files used as a percentage.Current Number ofInodes Used
Displays the status for checking and repairing the specified filesystem, fsck.
Available values include:
■ Running
■ Done successfully
■ Failed
■ Unknown
■ Not Running
Full Check Status
Displays the defragmentation status for the specified file system.
Available values include:
■ Running
■ Done successfully
■ Stopped
■ Failed
■ Not Running
Defrag Status
107Creating and maintaining Symantec FileStore file systemsAccessing the file system details
4 In the TierSummary:PrimaryTier panels, you can view the settings for theprimary tier.
Layout for the file system (simple, mirrored, striped,striped-mirror, or mirrored-stripe).
Layout
Number of mirrors for the file system.Mirrors
Number of columns for the file system.Columns
Displays the stripe-unit size.Stripe Unit
Displays if fast resync is enabled and on which pool it is enabled.Fast Resync
Pools for the file system.Pools
Disks for the file system.Disks
Total space for the file system.FS Size
Specifies the used space for the file system.Used Space
5 Using the TierTasks drop-down menu, you can shrink or grow a file system.
See “Shrinking a file system” on page 89.
See “Growing a file system” on page 89.
Creating and maintaining Symantec FileStore file systemsAccessing the file system details
108
6 In the Tier Summary: Secondary Tier panel, you can view the followinginformation:
Type of layout for the file system.Layout
Number of mirrors for the file system.Mirrors
Number of columns for the file system.Columns
Displays the stripe-unit size.Stripe Unit
Schedule time (or interval).Schedule
Policy for the schedule, when the schedule is run.Policy
Name of the pool associated with the tier.Pools
Size of the secondary tier.Size
Used space for the file system.Used Space
7 Using the Tier Tasks drop-down menu, you can shrink a file system, grow afile system, remove a tier, add tier mirror, remove tier mirror, run tier policy,and relocate a tier.
See “Shrinking a file system” on page 89.
See “Growing a file system” on page 89.
See “Removing a tier from a file system” on page 97.
See “Adding a mirror to a tiered file system” on page 96.
See “Removing a mirror from a tiered file system” on page 97.
See “Running a tier policy” on page 95.
See “Relocating a directory of a tiered file system” on page 96.
Creating a shared file systemTo create a shared file system
1 From the FileStore Management Console, click File Systems.
2 Select the file system for which you would like to create a shared file system,and click More > Share, or right-click the name of the file system, and clickShare.
109Creating and maintaining Symantec FileStore file systemsCreating a shared file system
3 In the Share Creation dialog, select the appropriate options, and click OK.
See “About NFS export options” on page 90.
See “About CIFS share options” on page 92.
4 In the Result dialog, click OK.
About snapshot operationsA snapshot is a virtual image of the entire file system. You can create snapshotsof a parent file system on demand. Physically, it contains only data thatcorresponds to changes made in the parent, and so consumes significantly lessspace than a detachable full mirror.
Snapshots are used to recover from data corruption. If files, or an entire filesystem, are deleted or become corrupted, you can replace them from the latestuncorrupted snapshot. You can mount a snapshot and export it as if it were acomplete 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 thetotal space consumed by snapshots remains above the quota, FileStore rejectsattempts to create additional ones.
The headings on the list of snapshots are defined as follows:
Name of the snapshot.Name
Name of the schedule created for the snapshot.Schedule Name
Name of the file system the snapshot belongs to.Parent File System
Date the snapshot was created.Creation Date
Protocol for the file system.
Valid values include:
■ NFS - Linux file system
■ CIFS - Windows file system
Protocol
Status of the snapshot.Status
When creating a snapshot, you selected whether or not it wasremovable.
Removable
Determines if the snapshot is preserved when all of the automatedsnapshots are destroyed.
Preserved
Creating and maintaining Symantec FileStore file systemsAbout snapshot operations
110
Table 5-2 Snapshot commands
DefinitionCommand
Create a snapshot. A snapshot is a copy of a set of files and directoriesas they were at a particular point in the past. FileStore supports filesystem level snapshots.
FileStore limits the space a snapshot can use. Snapshots use free spacein the file system from which they were taken.
See “Creating a snapshot” on page 111.
Create
Deletes a snapshot.
See “Destroying a snapshot” on page 112.
Destroy
Determines if the snapshot is preserved when all of the automatedsnapshots are destroyed.
See “Preserving a snapshot” on page 112.
Preserve
Changes the status of a snapshot to online.
See “Changing the status of a snapshot to online” on page 113.
Online
Changes the status of a snapshot to offline.
See “Changing the status of a snapshot to offline” on page 113.
Offline
Displays all the snapshots for the specified file system.
See “Viewing snapshots” on page 114.
View
Creates, modifies, deletes, and destroys automated snapshots.
See “Managing snapshots” on page 114.
Manage
Restores the specified snapshot.
See “Restoring a snapshot” on page 116.
Restore
Creating a snapshotTo create a snapshot
1 From the FileStore Management Console, click File Systems > Snapshots >Create.
2 In the Snapshot Creation dialog box, select the appropriate fields to createa snapshot.
Select the name of the file system.File System Name
111Creating and maintaining Symantec FileStore file systemsAbout snapshot operations
Enter a unique name for the snapshot.
Note:The following are reserved words for snapshot name: flags,ctime, and mtime.
Snapshot Name
Click the option to specify if you would like snapshotsautomatically removed if the file system runs out of space.
This is an offline operation.
Valid values are:
■ Yes
■ No
The default value is No.
Removable
3 Click OK.
4 In the Result dialog, click OK.
Destroying a snapshotTo destroy a snapshot
1 From the FileStore Management Console, click File Systems > Snapshots.
2 Select a snapshot that you want to destroy, and click the Destroy button, orright-click the name of the snapshot, and click Destroy.
3 In the Destroy dialog box, click OK to delete the snapshot.
4 In the Result dialog, click OK.
Preserving a snapshotTo preserve a snapshot
1 From the FileStore Management Console, click File Systems > Snapshots.
2 Select the snapshot that you want to preserve.
3 From the More button, click Preserve, or right-click the name of the snapshot,and click Preserve.
4 In the Preserve Snapshot dialog box, click OK to preserve the snapshot
5 In the Result dialog, click OK.
Creating and maintaining Symantec FileStore file systemsAbout snapshot operations
112
Changing the status of a snapshot to onlineTo change the status of a snapshot to online
1 From the FileStore Management Console, click File Systems > Snapshots.
2 Select the snapshot that you want to change the status for.
3 From the More button, click Online, or right-click the name of the snapshot,and click Online.
4 In the Online Snapshot dialog, verify that you want to change the status ofthe selected snapshot to online, and click OK.
5 In the Result dialog, click OK.
Changing the status of a snapshot to offlineTo change the status of a snapshot to offline
1 From the FileStore Management Console, click File Systems > Snapshots.
2 Select the snapshot that you want to change the status for.
3 From the More button, click Offline, or right-click the name of the snapshot,and click Offline.
4 In the Offline Snapshot dialog, verify that you want to change the status ofthe selected snapshot to offline, and click OK.
5 In the Result dialog, click OK.
113Creating and maintaining Symantec FileStore file systemsAbout snapshot operations
Viewing snapshotsTo view snapshots
1 From the FileStore Management Console, click File Systems > Snapshots.
2 Double-click on the name of a snapshot that you want to view.
In the Snapshot Details window, you can view the following information:
Name of the snapshot.Name
Name of the snapshot schedule.Schedule Name
Name of the file system.Parent File System
Date when the snapshot was created.Creation Date
File system protocol, either NFS or CIFS.Protocol
Status of the file system, either online or offline.Status
Displays the setting you selected for the snapshot, either yes orno.
Removable
Displays whether or not you selected the snapshot to bepreserved.
Preserved
Managing snapshotsTo manage snapshots
1 From the FileStore Management Console, click File Systems > Snapshots.
You can also access this operation by navigating to File Systems, selecting afile system, and then by clicking the Manage Snapshot button.
The snapshots must have already been created using FileSystems>Snapshots> Create.
2 In the ManageSnapshot dialog box, select the snapshot operation you wouldlike to perform:
■ Create an instant snapshot
■ Create an automated snapshot schedule
■ Modify an existing automated snapshot schedule
■ Delete an existing automated snapshot schedule
■ Destroy all automated snapshots from a schedule
Creating and maintaining Symantec FileStore file systemsAbout snapshot operations
114
3 If you select Createan instant snapshot, the next dialog box asks you for thefollowing:
Select the name of the file system the snapshot is on.File System Name
Enter the name of the snapshot you want managed.Snapshot name
Click the option to specify if you would like snapshotsautomatically removed if the file system runs out of space.
Valid values are:
■ Yes
■ No
The default value is No.
Removable
4 If you select Create an automated snapshot schedule, the next dialog boxasks you for the following:
Specifies the name of the file system the snapshot was createdon.
Selected FileSystem
Specifies the name of the schedule corresponding to theautomatically created snapshot.
The Schedule Name cannot contain an underscore ('_') as partof its value. For example, sch_1 is not allowed.
Special characters are not allowed for Schedule Name. OnlyEnglish characters and numbers are allowed.
Schedule Name
Specifies the number of snapshots that can be created for a givenfile system and schedule name. This field only accepts numericinput. Entering 0 implies the snapshots can be created on a givenfile system and schedule name without any restriction. Any othervalue would imply that only xnumber of snapshots can be createdfor a given file system and schedule name. If the number ofsnapshots corresponding to the schedule name is equal to orgreater than the value of this field, then snapshots that are morethan an hour old are automatically destroyed until the numberof snapshots is less than the maximum snapshot limit value.
The range allowed for this field is 0-999.
MaximumSnapshot Limit
For Month, select from Jan. - Dec.
For Week, select from Sun - Sat.
For other values, select from the ranges provided using thedrop-down menus.
Set Schedule
115Creating and maintaining Symantec FileStore file systemsAbout snapshot operations
5 If you select Modify an existing automated snapshot schedule, you aremodifying the snapshot schedule of a particular file system. After you selectthis option, click Next. Click on the snapshot schedule name you want tochange. Click Next. In the Create an automated snapshot schedule dialogbox, enter your changes. Click Finish.
6 If you select Delete an existing automated snapshot schedule, you aredeleting the schedule set for automatically creating snapshots for a particularfile system or for a particular schedule. After you select this option, clickNext. In the next dialog box, click on the snapshot schedule name you wantto delete. Click Finish.
7 If you select Destroy all automated snapshots from a schedule, you aredestroying all of the automated snapshots from a schedule. This excludes thepreserved and online snapshots. After you select this option, click Next. Clickon the snapshot schedule name you want to destroy. Click Finish.
Restoring a snapshot
Note: You must use the Storage> snapshot restore CLI command to restore asnapshot that includes a DAR-enabled file system. You cannot use the FileStoreManagement Console.
To restore a snapshot
1 From the FileStore Management Console, click File Systems > Snapshots.
The snapshot must have already been created using FileSystems>Snapshots> Create.
2 Select the snapshot that you want to restore.
3 From the More button, click Restore Snapshot, or right-click the name ofthe snapshot, and click Restore Snapshot.
4 In the Restore Snapshot dialog, verify that you want to restore the selectedsnapshot, and click OK.
5 In the Result dialog, click OK.
Creating and maintaining Symantec FileStore file systemsAbout snapshot operations
116
Configuring SymantecFileStore storage
This chapter includes the following topics:
■ About storage provisioning and management
■ About configuring storage pools
■ Creating storage pools
■ Viewing information about storage pools
■ Accessing storage pool details
■ Adding a disk to a storage pool
■ Moving a disk from one storage pool to another storage pool
■ Removing a disk from a storage pool
■ Destroying a storage pool
■ Renaming a pool
■ Detaching one or more pools from a cluster
■ Attaching a replication storage pool to a cluster
■ Creating a storage pool by selecting disks
■ Adding a disk to a storage pool
■ Running scan bus
■ Viewing information about disks
6Chapter
■ Accessing disk details
■ About I/O fencing
About storage provisioning and managementStorage provisioning in FileStore focuses on the storage pool, which is comprisedof a set of disks.
To provision FileStore storage, verify that the Logical Unit Numbers (LUNs) ormeta-LUNs in your physical storage arrays have been zoned for use with theFileStore cluster. The storage array administrator normally allocates and zonesthis physical storage.
You use the Storage operations to create storage pools using disks (LUNs).
About configuring storage poolsA storage pool is a group of disks from which FileStore allocates capacity whenyou create or expand file systems. Disk discovery and pool assignment are doneonce. FileStore propagates disk information to all cluster nodes.
Creating storage poolsTo create storage pools used to create a file system
1 In the FileStore Management Console, click Storage > Pools.
2 Click Create.
3 In the Create Pool dialog, enter the name of the storage pool.
Pool Name is a required field.
4 Select the disks to include in the storage pool.
Each disk can only belong to one storage pool. If you try to add a disk that isalready in use, an error message displays.
If I/O fencing is enabled, disks must support SCSI-3 PGR registrations.
The minimum size for a disk must be 10 MB.
5 Click OK.
6 In the Result dialog, click OK.
Configuring Symantec FileStore storageAbout storage provisioning and management
118
Viewing information about storage poolsTo view information about storage pools
◆ In the FileStore Management Console, click Storage > Pools.
From the Storage>Pools page, you can view the following information aboutstorage pools:
Name of the storage pool.Name
Number of disks associated with the storage pool.Disks
Size of the storage pool in GB.Pool Size
Used space that is allocated to the storage pool in GB.Used Space
Percentage of the used space that is allocated to the storage pool.%Used
Displays the file systems associated with the storage pool.File Systems onPool
From the Storage>Pools >DetachedPools section of the page, you can alsoview the following information about detached storage poolsets.
Name of the detached storage poolset.Detached PoolName
Name of the cluster from which the poolset was detached.Cluster DetachedFrom
Date when the poolset was detached.Date of Detached
List of disks included in the detached poolset.Detached PoolsetDisks
Names of the pools included in the detached poolset.Detached Pools
List of file systems included in the detached poolset.Detached FileSystems
Accessing storage pool detailsClick on the name of a storage pool to view storage pool details for the selectedstorage pool.
119Configuring Symantec FileStore storageViewing information about storage pools
To access storage pool details
1 In the FileStore Management Console, click Storage > Pools.
2 In the Name column, click on the storage pool you want to view.
3 In the Storage > Pools > Pool Details page, you can view the followinginformation for the storage pool:
Name of the storage pool.Pool Name
Displays the file systems that are associated with the storagepool.
Clicking on the hyperlink takes you to the File Systems > FileSystems page.
Number of FileSystems
Number of the disks associated with the storage pool.Number of Disks
Displays the capacity consumption for the storage pool.
You can view the following values:
■ Used Space - displays currently allocated storage pool capacityin GB
■ Free Space - displays unallocated storage pool capacity in GB
■ Total Space - total space available on the storage pool in GB
CapacityConsumption
Configuring Symantec FileStore storageAccessing storage pool details
120
4 In the Disks table, you can view the following information for the disksassociated with the specified storage pool:
Name of the disk associated with the specified storage pool.Name
Total space available on the disk in GB.Total Space
Allocated space on the disk in GB.Used Space
Percentage of used space on the disk.% Used
Free space on the disk in GB.Free Space
File system associated with the disk.
Clicking on the file system name (hyperlink) takes you tothe FileSystems>FileSystems>FileSystemDetails page.
File Systems on Disks
Displays the node names where the disk is not visible.Not Visible by Node (s)
5 In the Disks table, you can also add a disk to a storage pool, move a disk toanother storage pool, and remove a disk from a storage pool.
See “Adding a disk to a storage pool” on page 121.
See “Moving a disk from one storage pool to another storage pool” on page 122.
See “Removing a disk from a storage pool” on page 122.
Adding a disk to a storage poolTo add a disk to a storage pool
1 In the FileStore Management Console, click Storage > Pools.
2 Select a storage pool to add a disk to, and click Add Disk.
3 In the Add Disk to Pool dialog, select the disks to be added to the storagepool, and click OK.
4 In the Result dialog, click OK.
121Configuring Symantec FileStore storageAdding a disk to a storage pool
Moving a disk from one storage pool to anotherstorage pool
To move a disk from one storage pool to another storage pool
1 In the FileStore Management Console, click Storage > Pools.
2 Select a storage pool to move, and click More.
3 Click Move Disk to Other Pool.
4 In the Move Disk to Other Pool dialog, select the disks to be moved.
5 In the Select Pool drop-down menu, select the pool to move the disks to.
6 Click OK.
7 In the Result dialog, click OK.
Removing a disk from a storage poolTo remove a disk from a storage pool
1 In the FileStore Management Console, click Storage > Pools.
2 Select a storage pool to remove a disk from, and click More.
3 Click Remove Disk.
4 In the Remove Disk dialog, select the disk(s) to be removed.
5 Click OK.
6 In the Result dialog, click OK.
Destroying a storage poolTo destroy a storage pool
1 In the FileStore Management Console, click Storage > Pools.
2 Select a storage pool to delete, and click More.
3 Click Destroy Pool.
4 In the DestroyPool dialog, verify that you want to destroy the selected pool.
5 Click OK.
6 In the Result dialog, click OK.
Configuring Symantec FileStore storageMoving a disk from one storage pool to another storage pool
122
Renaming a poolTo rename a pool
1 In the FileStore Management Console, click Storage > Pools.
2 Select a storage pool to rename, and click More.
3 Click Rename Pool Name.
4 In the Rename Pool Name dialog, enter the new name for the pool.
This is a required field.
5 Click OK.
6 In the Result dialog, click OK.
Detaching one or more pools from a clusterTo detach one or more pools from a cluster
1 In the FileStore Management Console, click Storage > Pools.
2 Select one (or more) storage pools to detach, and click More.
3 Click Detachset Pool.
4 In the Detachset Pool dialog, verify that you want to detach the selectedpools.
5 Enter a new name for the detached pool set.
6 Click OK.
7 In the Result dialog, click OK.
Attaching a replication storage pool to a clusterTo attach a replication storage pool to a cluster
1 In the FileStore Management Console, click Storage > Pools.
2 In the DetachedPools section of the page, select the replication storage poolto attach, and click Attachset Pool.
3 In the Attachset Pool dialog, verify that you want to attach the selectedreplication storage pools.
123Configuring Symantec FileStore storageRenaming a pool
4 If desired, you can rename the pools and file systems by entering acomma-separated list of pool or file system name pairs. Click the checkboxand enter the renaming information. For example,pool2=newpool2,fs3=newfs3.
5 Click OK.
6 In the Result dialog, click OK.
Creating a storage pool by selecting disksTo create a storage pool by selecting disks
1 In the FileStore Management Console, click Storage > Disks.
2 Select a disk name to be associated with the storage pool you are creating,and click Create Pool.
3 In the Create Pool dialog, enter the name of the storage pool you want tocreate.
The Select Disks field is a required field.
Each disk can only belong to one storage pool. If you try to add a disk that isalready in use, an error message displays.
If I/O fencing is enabled, disks must support SCSI-3 PGR registrations.
The minimum size for a disk must be 10 MB.
4 Click OK.
5 In the Result dialog, click OK.
Adding a disk to a storage poolTo add a disk to a storage pool
1 In the FileStore Management Console, click Storage > Disks.
2 Select a disk name to add a storage pool to, and click Add Disk to Pool.
3 In the AddDisk toPool dialog, select the disk to add to the storage pool fromthe drop-down menu.
A disk can belong to only one pool.
The minimum size of the disks required for adding a disk to a pool is 10 MB.
If I/O fencing is enabled, disks must support SCSI-3 PGR registrations.
Configuring Symantec FileStore storageCreating a storage pool by selecting disks
124
4 Click OK.
5 In the Result dialog, click OK.
Running scan busTo run scan bus
1 In the FileStore Management Console, click Storage > Disks.
2 Click Run Scan Bus.
3 In the Run Scan Bus dialog, verify that you want to run scan bus to discovernew disks.
4 Click OK.
5 In the Result dialog, click OK.
Viewing information about disksTo view information about disks
◆ In the FileStore Management Console, click Storage > Disks.
From the Storage>Disks page, you can view the following information aboutdisks:
Name of the disk.Name
Name of the storage pool.Pool Name
Directory path for where the disk is located.Paths
Total space available on the disk.Total Space
Used space that is allocated to the storage pool in MB and GB.Used Space
Percentage of used space on the disk.% Used
Free space on the disk.Free Space
Serial number for the disk.Serial Number
Vendor ID for the disk.Vendor ID
Displays the node names where the disk is not visible.Not Visible byNode(s)
125Configuring Symantec FileStore storageRunning scan bus
Indicates if the disk is used for I/O fencing or not.
Possible values include:
■ NO - this disk is not used for I/O fencing. It can be used tocreate a pool.
■ YES - this disk is used for I/O fencing. It cannot be used tocreate a pool.
Coordinator Disk
Accessing disk detailsClick on the name of the disk to view detailed information for the specified disk.
To access disk details
1 In the FileStore Management Console, click Storage > Disks.
2 In the Name column, click on the disk you want to view.
3 In the Storage > Disks > Disk Details page, you can view the followinginformation for the disk:
Name of the disk.Disk Name
Name of the storage pool that is associated with the disk.
Clicking on the hyperlink for PoolName takes you to the Storage> Pools > Pool Details page.
Pool Name
File systems that are associated with the disk.
Clicking on the hyperlink for File Systems takes you to the FileSystems > File Systems > File System Details page.
File Systems
Indicates if there are any mirrors on the file system.Mirrors
Displays the capacity consumption for the disk.
You can view the following values:
■ Used Space - displays currently allocated disk capacity in GB
■ Free Space - displays unallocated disk capacity in GB
■ Total Space - total space available on the disk in GB
CapacityConsumption
Name of the enclosure.Enclosure
Displays the array name for each disk.Array Name
Displays the array type for each disk.Array Type
Vendor ID for the disk.Vendor ID
Configuring Symantec FileStore storageAccessing disk details
126
Serial number for the disk.Serial No
In the Paths table, you can view the following information for the nodes thatare associated with the specified disk:
Displays the name of the node that is associated with the specifieddisk.
Node Name
Displays the name of the path that is associated with the specifieddisk.
Path Name
Displays the status for the node that is associated with thespecified disk.
Status
4 You can also use the Storage > Disks > Disk Details page to perform thefollowing operations: add a disk to a storage pool, move a disk to anotherstorage pool, and remove a disk.
See “Adding a disk to a storage pool” on page 124.
See “Moving a disk from one storage pool to another storage pool” on page 122.
See “Removing a disk from a storage pool” on page 122.
About I/O fencingIn the FileStore cluster, one method of communication between the nodes isconducted through heartbeats over private links. If two nodes cannot verify eachother's state because they cannot communicate, then neither node can distinguishif 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 otherbut do communicate with the central storage. This condition is referred to as thesplit-brain condition.
I/O fencing (also referred to as disk fencing) protects data integrity if the split-braincondition occurs. I/O fencing determines which nodes are to retain access to theshared storage and which nodes are to be removed from the cluster, to preventpossible data corruption.
To protect the data on the shared disks, each system in the cluster must beconfigured to use I/O fencing by making use of special purpose disks calledcoordinator disks. They are standard disks or LUNs that are set aside for use bythe I/O fencing driver.
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
127Configuring Symantec FileStore storageAbout I/O fencing
from other nodes. A system must eject a peer from the coordinator disks beforeit can fence the peer from the data drives. Racing for control of coordinator disksis how fencing helps prevent split-brain. Coordinator disks cannot be used forany other purpose. You cannot store data on them, or include them in a disk groupfor user data.
To use the I/O fencing feature, you need to create a separate coordinator diskgroup, which contain three coordinator disks. Your minimum configuration mustbe a two-node cluster with FileStore software installed and 3+ disks (three ofwhich are used for the coordinator disk group and the rest of the disks are usedfor storing data).
Creating an I/O fencing operationTo create an I/O fencing operation
1 In the FileStore Management Console, click Storage > Fencing.
2 Click the Create button.
3 In the Create Fencing dialog, select any three disks from the available diskdrop-down menu, and click OK.
4 In the Result dialog, click OK.
When performing this operation, the cluster is rebooted, and Web servicesare terminated. Please re-login to the FileStore Management Console, andclick the Refresh link on the Storage > Fencing page.
Enabling I/O fencingTo enable I/O fencing
1 In the FileStore Management Console, click Storage > Fencing.
2 Click on the Disk Name that you want to enable.
3 Click the Enable button.
The Enable Fencing dialog displays.
If the enable fencing feature is already enabled, a warning message displayssaying that fencing is already enabled.
4 In the Enable Fencing dialog, a warning message displays Are you sure youwant to enable fencing?.
Configuring Symantec FileStore storageAbout I/O fencing
128
5 Click OK.
6 In the Result dialog, click OK.
When performing this operation, the cluster is rebooted, and Web servicesare terminated. Please re-login to the FileStore Management Console, andclick the Refresh link on the Storage > Fencing page.
Viewing information about I/O fencingTo view information about I/O fencing
◆ In the FileStore Management Console, click Storage > Disks.
From the Storage > Fencing page, you can view the following informationfor the coordinator disks:
Name of the coordinator disk.Disk Name
Status of the coordinator disk, enabled or disabled.Disk Status
Disabling I/O fencingTo disable I/O fencing
1 In the FileStore Management Console, click Storage > Fencing.
2 Click on the Disk Name that you want to disable.
3 Click on the Disable button.
The Disable Fencing dialog displays.
4 In the DisableFencing dialog, a warning message displays Areyousureyouwant to disable fencing?.
5 Click OK.
6 In the Result dialog, click OK.
When performing this operation, the cluster is rebooted, and Web servicesare terminated. Please re-login to the FileStore Management Console, andclick the Refresh link on the Storage > Fencing page.
129Configuring Symantec FileStore storageAbout I/O fencing
Replacing a coordinator diskTo replace a coordinator disk
1 In the FileStore Management Console, click Storage > Fencing.
2 Select a disk to replace a coordinator disk for, and click Replace Disk.
The Replace Disk dialog displays.
3 From the Select Disks option, select any disk to replace with the alreadyselected disk.
4 Click OK.
5 In the Result dialog, click OK.
Destroying a coordinator diskTo destroy a coordinator disk
1 In the FileStore Management Console, click Storage > Fencing.
2 Select a disk to destroy, and click Destroy.
The Destroy Fencing dialog displays.
3 In the DestroyFencing dialog, a warning message displays Areyousureyouwant to destroy fencing?.
4 Click OK.
5 In the Result dialog, click OK.
Configuring Symantec FileStore storageAbout I/O fencing
130
Managing a SymantecFileStore cluster
This chapter includes the following topics:
■ About managing a cluster
■ Installing FileStore software on a node
■ Adding a new node to a cluster
■ Viewing information about a node in a cluster
■ Accessing cluster details
■ Making a service go online
■ Autofixing a service
■ Deleting a node from a cluster
■ Rebooting a node in a cluster
■ Rebooting all the nodes in a cluster
■ Shutting down a node in a cluster
■ Shutting down all the nodes in a cluster
■ Displaying the current load for the cluster
About managing a clusterYou can perform the following tasks to manage a cluster:
■ Installing FileStore software on a node.
7Chapter
■ Adding a new node to a cluster
■ Viewing information about a node in a cluster
■ Deleting a node from a cluster
■ Rebooting a single node or all of the nodes in a cluster
■ Shutting down a node or all of the nodes in a cluster
Installing FileStore software on a nodeTo install FileStore software on a node
1 In the FileStore Management Console, click Cluster.
2 In the Need to Install Nodes table, select an IP address for a node and clickthe Install Node button.
3 In the Install Node dialog, verify that you want to install FileStore softwareon the selected node, and click OK.
A confirmation message appears to inform you that the installation may takesome time to complete.
4 Click OK to start the installation.
Adding a new node to a clusterTo add a new node to a cluster
1 In the FileStore Management Console, click Cluster.
2 In the Available Nodes table, select an IP address for a node that is in theInstalled state, and click the Add Nodes button.
You can only add the nodes that are in the Installed state.
3 In the Add Node dialog, verify that you want to add the selected node, andclick OK.
4 In the Result dialog, click OK.
Viewing information about a node in a clusterTo view information about a node in a cluster
◆ In the FileStore Management Console, click Cluster.
Managing a Symantec FileStore clusterInstalling FileStore software on a node
132
In the Nodes table, you can view the following information about the nodesin a cluster:
Name of the nodeNode
State of the node
Available values include:
■ Running
■ Offline
State
Percentage of CPU used by the nodeCPU
Displays the World Wide Name (WWN) information for all of thenodes in the cluster.
HBA
The Available Nodes table displays the following fields:
IP address of the nodeIP Address
Version of the nodeVersion
Install state for the node
Available states include:
■ INSTALLED
■ RUNNING
■ FAULTED
■ EXITED
■ LEAVING
■ UNKNOWN
Install State
The Need to Install Nodes table displays the following fields:
IP address of the node that requires FileStore software to be installedIP address
Index (count) of the node that needs to be installedIndex
133Managing a Symantec FileStore clusterViewing information about a node in a cluster
Accessing cluster detailsTo access cluster details
1 In the FileStore Management Console, click Cluster.
2 In the Node column, click on the name of the node you want to view.
3 In the Cluster > Node Details page, you can view the following informationfor the node:
Name of the node.Node Name
State of the node.
Available states include:
■ RUNNING
■ OFFLINE
State
CPU for the node.CPU
Number of online/offline NFS shares with hyperlinks to the NFSshares.
NFS Shares
Number of online/offline CIFS shares with hyperlinks to the CIFSshares.
CIFS Shares
Indicates the disks that are online/offline.Disks
The Services table displays the following information for all the services forthe selected node:
IP address or name of the service, for example, CIFS, FTP, GUI.Service Name
Name of the node.Node Name
Status of the node (ONLINE or OFFLINE).Status
Making a service go onlineTo make a service go online
1 In the FileStore Management Console, click Cluster.
2 In the Node column, click on the name of the node for which you want tomake the service go online.
You will be at the Cluster > Node Details page.
Managing a Symantec FileStore clusterAccessing cluster details
134
3 In the Services table, select the service name for which you want to go online,and click Online Service.
4 In the Online service dialog, verify that you want to make the service goonline, and click OK.
5 In the Result dialog, click OK.
Autofixing a serviceTo autofix a service
1 In the FileStore Management Console, click Cluster.
2 In the Node column, click on the name of the node for which you want toautofix the service.
You will be at the Cluster > Node Details page.
3 In the Services table, select the service name for which you want to autofix,and click Autofix Service.
4 In the AutofixService dialog, verify that you want to autofix all services, andclick OK.
5 In the Result dialog, click OK.
Deleting a node from a clusterTo delete a node from a cluster
1 In the FileStore Management Console, click Cluster.
2 In the Nodes table, select a node you want to delete.
3 Right-click the name of the node you want to delete, and click Delete Node,or click the Delete Node button.
4 In the Delete Node dialog, verify that you want to delete the selected node,and click OK.
5 In the Result dialog, click OK.
Rebooting a node in a clusterTo reboot a single node or all of the nodes in a cluster
1 In the FileStore Management Console, click Cluster.
2 In the Nodes table, select a node(s) you want to reboot.
135Managing a Symantec FileStore clusterAutofixing a service
3 Right-click the name of the node you want to reboot, and click RebootNode,or click the Reboot Node button.
4 In the Reboot Node dialog, verify that you want to reboot the selected node,and click OK.
5 In the Result dialog, click OK.
Rebooting all the nodes in a clusterTo reboot all the nodes in a cluster
1 In the FileStore Management Console, click Cluster.
2 In the Nodes table, click the More button, and then click Reboot all.
3 In the Reboot All Nodes dialog, verify that you want to reboot all the nodesin the cluster, and click OK.
4 In the Result dialog, click OK.
Shutting down a node in a clusterTo shut down a node in a cluster
1 In the FileStore Management Console, click Cluster.
2 In the Nodes table, select a node you want to shut down.
3 Right-click the name of the node you want to shut down, and click ShutdownNode, or click the More button, and then click Shutdown Node.
4 In the ShutdownNode dialog, verify that you want to shut down the selectednode, and click OK.
5 In the Result dialog, click OK.
Shutting down all the nodes in a clusterTo shut down all the nodes in a cluster
1 In the FileStore Management Console, click Cluster.
2 In the Nodes table, click the More button, and then click Shutdown all.
3 In the Shutdown All Nodes dialog, verify that you want to shut down all thenodes in the cluster, and click OK.
4 In the Result dialog, click OK.
Managing a Symantec FileStore clusterRebooting all the nodes in a cluster
136
Displaying the current load for the clusterTo display the current load for the cluster
1 In the FileStore Management Console, click Cluster.
2 In the Nodes table, select the node that you want to display the current loadfor.
3 In the Nodes table, click the More button, and then click Cluster CurrentLoad.
4 In the Cluster Load dialog, you can view the following information for theselected node:
Name of the node.Node
State of the node.
Available values include:
■ RUNNING
■ OFFLINE
State
CPU usage for the node displayed in the last five seconds.CPU(5 sec)
Indicates the network load for the Public Interface 0 displayedin MBs.
pubeth0 rx
(MB/s)
Indicates the network load for the Public Interface 0 displayedin MBs.
pubeth0 tx (MB/s)
5 Click OK.
6 In the Result dialog, click OK.
137Managing a Symantec FileStore clusterDisplaying the current load for the cluster
Managing a Symantec FileStore clusterDisplaying the current load for the cluster
138
Setting up SymantecFileStore Replication
This chapter includes the following topics:
■ About FileStore file-level replication
■ About configuring FileStore Replication using the FileStore ManagementConsole
■ Using the replication GUI wizard
■ Creating a replication job on the source cluster
■ Viewing information about replication jobs on the source cluster
■ Modifying a replication job on the source cluster
■ Destroying a replication job on the source cluster
■ Enabling a replication job on the source cluster
■ Disabling a replication job on the source cluster
■ Pausing a replication job on the source cluster
■ Resuming a replication job on the source cluster
■ Aborting a replication job on the source cluster
■ Triggering a replication job on the source cluster
■ Resynchronizing a replication job
■ About the replication units operations
■ About replication schedule operations
8Chapter
About FileStore file-level replicationThe FileStore Replication solution provides high performance, scalable(one-to-many) data replication and is ideal for use as a content distributionsolution, and for use to create hot standby copies of important data sets.
FileStore Replication lets you asynchronously replicate a file system from onenode in a source cluster to another node in a destination cluster at regularly timedintervals. This allows for content sharing, replication, and distribution.
The FileStore Replication functionality allows episodic replication with a minimumtimed interval update of fifteen minutes and no set maximum. Unlike manyreplication solutions, FileStore Replication also allows the destination file systemto be online for reads while replication is active.
Major features of FileStore Replication include:
■ Online access (read-only) to replicated data
■ Immediate read/write access to target replicated data in the unlikely eventthat the source file system goes offline for a sustained period of time
■ Load balancing across jobs
■ Highly-available replication service
■ Unlimited simultaneous replication operations
How FileStore Replication worksFileStore Replication is an incremental file-level replication service that runs ontop of the Cluster File System that is used by FileStore which is, in turn, based onthe Veritas File System (VxFS). FileStore Replication uses two file system specificfeatures: File Change Log (FCL) and Storage Checkpoint services, to retrieve filechanges between replication periods.
For a given period, the FCL records every change made to the file system. Byscanning the FCL, FileStore Replication quickly identifies the file(s) that havechanged and generates the modified file list. This avoids the expensive file systemscanning that is normally associated with file-based replication, and whichtypically results in sub-optimal performance.
Next, FileStore Replication uses VxFS Storage Checkpoint's metadata comparisonfeature to retrieve the modified extent list of each changed file. It does not needto access the file data.
The FileStore Replication transport layer works in conjunction with, and interfacesto the well-known rsync remote file synchronization tool. Using this existingnetwork transportation program makes the network configuration much easier
Setting up Symantec FileStore ReplicationAbout FileStore file-level replication
140
in the enterprise domain: the Secure Socket Shell (SSH) port (22) required by rsyncis opened by default on almost all enterprise firewalls. rsync is also a reliablesolution for a low bandwidth or unreliable link environment.
Note: FileStore uses the rsync protocol to provide transportation of FileStoreReplication encapsulated files. The use of rsync is not exposed in FileStore, andcannot be administered outside of the FileStore Replication feature set.
About setting up FileStore Replication between two clustersYou run FileStore Replication between two FileStore clusters which is referredas:
■ Source cluster - where the data is being replicated from
■ Destination cluster - where the data is being replicated to
FileStore Replication requires communication between both clusters. Thiscommunication occurs over TCP/IP Port 22 (SSH) so make sure that Port 22 isopen across the network between the two clusters.
Note:Before you set up your clusters for replication, you must first identify whichis the source cluster and which is the destination cluster. All of the operationsare performed on the source cluster first.
To use FileStore Replication, you must first create an online file system on theFileStore source cluster and an online file system on the destination cluster.
Note:Assign a virtual IP (VIP) address to both the source and destination clusters.The FileStore Replication service requires VIP addresses not already in use forthe two clusters to communicate.
The replication service can only be started after you bind a virtual IP address. Tobind a virtual IP address, go to the Settings > Replication tab, and click the Bindbutton for the specified IP address, and enter the appropriate fields on the BindVIP dialog.
This operation must be run on both the source and destination clusters.
141Setting up Symantec FileStore ReplicationAbout FileStore file-level replication
About configuring FileStore Replication using theFileStore Management Console
Perform the following tasks in the order described in Table 8-1 to configureFileStore Replication using the FileStore Management Console.
You will need to access two tabs, Settings > Replication and Replication toconfigure FileStore Replication using the FileStore Management Console.Alternatively, you can use the ReplicationSteps at the top of the Replication GUIwizard to help you navigate through the replication setup process.
See “Using the replication GUI wizard” on page 143.
Table 8-1 Workflow for configuring FileStore Replication using the FileStoreManagement Console
Link for finding more information about the taskTask
See “Binding a virtual IP address on the source anddestination clusters” on page 245.
Binding a virtual IP addresson the source and destinationclusters
See “Starting the replication service for the source anddestination clusters” on page 247.
Starting the replicationservice for the source anddestination clusters
See “Exporting keys on the source cluster” on page 247.Exporting keys on the sourcecluster
See “Importing keys on the destination cluster” on page 248.Importing keys on thedestination cluster
See “Exporting keys on the destination cluster” on page 248.Exporting keys on thedestination cluster
See “Importing keys on the source cluster” on page 249.Importing keys on the sourcecluster
See “Creating a link between the source cluster and thedestination cluster” on page 249.
Creating a link between thesource cluster and thedestination cluster
See “Checking the link between the source and destinationclusters” on page 250.
Checking the link betweenthe source cluster and thedestination cluster
See “Creating replication units for the source cluster on thesource cluster” on page 154.
Creating replication units forthe source cluster on thesource cluster
Setting up Symantec FileStore ReplicationAbout configuring FileStore Replication using the FileStore Management Console
142
Table 8-1 Workflow for configuring FileStore Replication using the FileStoreManagement Console (continued)
Link for finding more information about the taskTask
See “Creating replication units for the destination clusteron the source cluster” on page 155.
Creating replication units forthe destination cluster on thesource cluster
See “Creating a replication schedule on the source cluster”on page 159.
Creating replicationschedules on the sourcecluster
See “Creating a replication job on the source cluster”on page 146.
Creating replication jobs onthe source cluster
See “Enabling a replication job on the source cluster”on page 150.
Enabling a replication job onthe source cluster
See “Triggering a replication job on the source cluster”on page 152.
Triggering a replication jobon the source cluster
See “Pausing a replication job on the source cluster”on page 151.
Pausing a replication job onthe source cluster
See “Aborting a replication job on the source cluster”on page 151.
Aborting a replication job onthe source cluster
See “Resuming a replication job on the source cluster”on page 151.
Resuming a replication jobon the source cluster
See “Disabling a replication job on the source cluster”on page 150.
Disabling a replication job onthe source cluster
See “Destroying a replication job on the source cluster”on page 149.
Destroying a replication jobon the source cluster
See “Resynchronizing a replication job” on page 152.Resynchronizing areplication job
See “Viewing replication status details” on page 246.Viewing replication statusdetails
Using the replication GUI wizardThe FileStore Management Console includes a replication GUI wizard to helpguide you through the replication setup process.
143Setting up Symantec FileStore ReplicationUsing the replication GUI wizard
Figure 8-1 Replication GUI wizard
The replication GUI wizard includes a list of Replication Steps at the top of thepage. Each of these steps includes a clickable link you can use to navigate throughthe replication interface and perform replication setup tasks. The steps arepresented in order. Follow the steps to set up a replication.
Figure 8-2 Replication steps
Setting up Symantec FileStore ReplicationUsing the replication GUI wizard
144
To use the replication GUI wizard
1 In the FileStore Management Console for the source cluster, click Replication.
A replication page appears with a list of Replication Steps at the top of thepage.
2 To start the replication setup, click the Bind IP link in Replication Steps.
The Settings > Replication page appears.
Use this page to perform the first four replication steps. The following listshows the steps you can perform on this page and includes links for moreinformation about each step.
See “Binding a virtual IP address on the source and destinationclusters” on page 245.
Bind IP
See “Starting the replication service for the source and destinationclusters” on page 247.
Start/StopService
See “Exporting keys on the source cluster” on page 247.
See “Importing keys on the destination cluster” on page 248.
See “Exporting keys on the destination cluster” on page 248.
See “Importing keys on the source cluster” on page 249.
Import/ExportKeys
See “Creating a link between the source cluster and the destinationcluster” on page 249.
See “Checking the link between the source and destinationclusters” on page 250.
Create/Edit Links
145Setting up Symantec FileStore ReplicationUsing the replication GUI wizard
3 After you have finished the first four steps, continue clicking through thelinks to complete the replication.
The following list shows additional replication steps you can perform andincludes links for more information about each step.
See “Creating replication units for the source cluster on the sourcecluster” on page 154.
See “Creating replication units for the destination cluster on thesource cluster” on page 155.
Create/Edit Rep.Units
See “Creating a replication schedule on the source cluster”on page 159.
Create/EditSchedules
See “Creating a replication job on the source cluster” on page 146.
See “Enabling a replication job on the source cluster” on page 150.
Create/ManageJobs
Creating a replication job on the source clusterThe job definition defines what will be copied (replicated), the source cluster, thedestination cluster, and the frequency of the replication. The replication job needsto be created only at the source cluster.
To create a replication job on the source cluster
1 In the FileStore Management Console for the source cluster, click Replication> Jobs.
2 In the Jobs table, click the Create button.
Setting up Symantec FileStore ReplicationCreating a replication job on the source cluster
146
3 In the Create Job dialog, enter information for the following fields:
Enter a name for the job you are creating.Job Name(Required)
Select the source replication unit from the drop-down menu forrunning the replication job.
Source ReplicationUnit (Required)
Select the destination replication unit from the drop-down menufor running the replication job.
DestinationReplication Unit(Required)
Select the link name from the drop-down menu for running thereplication job.
Link Name(Required)
Select the schedule from the drop-down menu for running thereplication job.
If you do not want to use a schedule with this job, keep this fieldempty.
Check the box before Select Schedule to enable the schedule forthe replication job.
Select Schedule
4 Click OK.
Viewing information about replication jobs on thesource cluster
To view information about replication jobs on the source cluster
◆ In the FileStore Management Console for the source cluster, click Replication> Jobs.
From the Jobs page, you can view the following information for FileStoreReplication jobs:
Name of the replication job.
Clicking this link takes you to a Jobs Details page.
Job Name
Name of the schedule.
Clicking this link takes you to the Replication>Schedules page.
Schedule
Source replication unit (where the data is being replicated from).Source ReplicationUnit
147Setting up Symantec FileStore ReplicationViewing information about replication jobs on the source cluster
Destination replication unit (where the data is being replicatedto).
DestinationReplication Unit
Time when the replication job was started.Start Time andDate
Status of the replication job
Available values include:
■ Enabled
■ Disabled
■ Paused
■ Failed
■ Running
■ Trying to Disable
■ Trying to Enable
■ Trying to Pause
■ Trying to Abort
■ Trying to Run
Status
Status message for the replication job.Files/OperationSent
Modifying a replication job on the source clusterTo modify a replication job on the source cluster
1 In the FileStore Management Console for the source cluster, click Replication> Jobs.
2 Select the job you want to modify by clicking the box next to it.
3 Right-click the name of the job you want to modify, and click Modify, or clickthe Modify button.
The job must be in the Disabled state to change the Source Replication Unit,Destination Replication Unit, or Link Name.
You can modify a replication schedule for jobs in the Enabled state.
Setting up Symantec FileStore ReplicationModifying a replication job on the source cluster
148
4 In the Modify Job dialog, enter information for the following fields:
Select a new source replication unit from the drop-downlist. This option modifies the source replication unit of thejob definition.
Source Replication Unit
Select a new destination replication unit from the drop-downlist. This option modifies the destination replication unitin the job definition.
Destination ReplicationUnit
Select a new schedule name from the drop-down list.
Modifies the replication frequency in the job definition.
Schedule Name
Select a link name from the drop-down list.
The link name is a unique identifier/name assigned to theassociation between the source and the destination clusters.Link name is used to identify the link that is establishedbetween the source and destination clusters. You can usethe link name instead of the virtual IP addresses of thesource and destination clusters when using other replicationcommands.
For example:
Pune_Shanghai
Link Name
5 Click OK.
6 In the Result dialog, click OK.
Destroying a replication job on the source clusterA replication job needs to be in the Disabled state prior to the replication job beingdestroyed.
You cannot destroy a job that is in the Enabled state.
To destroy a replication job
1 In the FileStore Management Console for the source cluster, click Replication> Jobs.
2 In the Jobs table, select the job with a status of Disabled that you want todestroy by clicking the box next to it.
3 Right-click the name of the job you want to destroy, and click Destroy, orclick the More button, and click Destroy.
149Setting up Symantec FileStore ReplicationDestroying a replication job on the source cluster
4 In the Destroy Job dialog, verify that you want to destroy the selectedreplication job, and click OK.
5 In the Result dialog, click OK.
Enabling a replication job on the source clusterThe replication job must be in the Disabled state prior to enabling the replicationjob.
Replication of the job starts on the next scheduled date for the job.
To enable a replication job on the source cluster
1 In the FileStore Management Console for the source cluster, click Replication> Jobs.
2 In the Jobs table, select the job with a status of Disabled by clicking the boxnext to it.
3 Right-click the name of the job you want to enable, and click Enable, or clickthe More button, and click Enable.
4 In the EnableJob dialog, verify that you want to enable the selected replicationjob, and click OK.
5 In the Result dialog, click OK.
Disabling a replication job on the source clusterThe replication job must be in the Enabled, Failed, or Paused states prior todisabling the replication job.
To disable a replication job on the source cluster
1 In the FileStore Management Console for the source cluster, click Replication> Jobs.
2 In the Jobs table, select the job with a status of Enabled, Failed, or Pausedthat you want to disable by clicking the box next to it.
3 Right-click the name of the job you want to disable, and click Disable, or clickthe More button, and click Disable.
4 In the Disable Job dialog, verify that you want to disable the selectedreplication job, and click OK.
5 In the Result dialog, click OK.
Setting up Symantec FileStore ReplicationEnabling a replication job on the source cluster
150
Pausing a replication job on the source clusterTo pause a replication job on the source cluster
1 In the FileStore Management Console for the source cluster, click Replication> Jobs.
2 In the Jobs table, select the job with a status of Running that you want topause by clicking the box next to it.
3 Right-click the name of the job you want to pause, and click Pause, or clickthe More button, and click Pause.
4 In the PauseJob dialog, verify that you want to pause the selected replicationjob, and click OK.
5 In the Result dialog, click OK.
Resuming a replication job on the source clusterIf a replication job was paused or is failing because of a minor issue (for example,failing because the source file system is offline, the replication service is down,or the destination file system is full), you can start the job again from the pointit failed.
To resume a replication job on the source cluster
1 In the FileStore Management Console for the source cluster, click Replication> Jobs.
2 In the Jobs table, select the job with a status of either Paused or Failed thatyou want to resume by clicking the box next to it.
3 Right-click the name of the job you want to resume, and click Resume, orclick the More button, and click Resume.
4 In the Resume Job dialog, verify that you want to resume the selectedreplication job, and click OK.
5 In the Result dialog, click OK.
Aborting a replication job on the source clusterYou can abort a replication job. When you abort a replication job, all files replicatedup to the point of aborting the job are destroyed.
151Setting up Symantec FileStore ReplicationPausing a replication job on the source cluster
To abort a replication job on the source cluster
1 In the FileStore Management Console for the source cluster, click Replication> Jobs.
2 In the Jobs table, select the job with a status of Running that you want toabort by clicking the box next to it.
3 Right-click the name of the job you want to abort, and click Abort, or clickthe More button, and click Abort.
4 In the Abort Jobdialog, verify that you want to abort the selected replicationjob, and click OK.
5 In the Result dialog, click OK.
Triggering a replication job on the source clusterThe Trigger operation lets you run a replication job out of the defined sequence.For example, you can trigger a replication job to run immediately.
To trigger a replication job on the source cluster
1 In the FileStore Management Console for the source cluster, click Replication> Jobs.
2 In the Jobs table, select the job with a status of Enabled that you want totrigger by clicking the box next to it.
3 Right-click the name of the job you want to trigger, and click Trigger, or clickthe More button, and click Trigger.
4 In the TriggerJob dialog, verify that you want to abort the selected replicationjob, and click OK.
5 In the Result dialog, click OK.
Resynchronizing a replication jobIn some rare cases, a replication job cannot always reconcile the source anddestination clusters. The Resync operation lets you leverage existing data at thedestination and resume the replication without restarting from scratch.
To resynchronize a replication job
1 In the FileStore Management Console for the source cluster, click Replication> Jobs.
2 In the Jobs table, select the job that you want to resynchronize by clickingthe box next to it.
Setting up Symantec FileStore ReplicationTriggering a replication job on the source cluster
152
3 Right-click the name of the job you want to resynchronize, and click Resync,or click the More button, and click Resync.
4 In the Resync dialog, verify that you want to resynchronize the selectedreplication job, and click OK.
5 In the Result dialog, click OK.
About the replication units operationsThe Replication Units operations let you define the type of data that you willreplicate from the source cluster to the destination cluster. All files and foldersbelonging to a replication unit are replicated together from the source cluster tothe destination cluster.
A single replication unit can span across multiple directories and multiple filesystems.
A replication unit is an ordered set of entries, where each entry is one of thefollowing:
■ A single file system
■ A single subdirectory
■ A single file
FileStore Replication requires that the source and destination replication unitsof a job definition have the same type of ordered entries, that is, every entry pair(one entry from the source and one entry from the destination replication unit)must be of a similar type.
Both can be files, or both can be directories, as shown in the following exampletaken from the FileStore CLI:
Replication> repunit show
Replication unit Name Replication unit Entries
===================== ========================
ru1 fs1,fs2/dir1,fs2/f1
ru2 fs4,fs6/dir2,fs5/f2
The entity is identified by the file system name, optionally followed by a slash '/',followed by the path of the directory or the file inside the file system. Memberentities are ordered inside a replication unit and such ordering information isused to determine the replication entity pair mapping from the source replicationunit to the destination replication unit.
153Setting up Symantec FileStore ReplicationAbout the replication units operations
Note: Make sure that the paths in the destination replication unit exist in thedestination cluster.
Table 8-2 Replication unit operations
DefinitionOperation
Creates a replication unit definition. This operation determines theexact item (such as a file system) that you want to replicate.
create
Destroys a replication unit definition.
Note: Make sure that you first destroy the job that was using thereplication units, or the command fails.
destroy
Adds an entry in an existing replication unit definition.add entry
Changes an entry in an existing replication unit definition.modify entry
Removes an entry in an existing replication unit definition.remove entry
Creating replication units for the source cluster on the source clusterTo create replication units for the source cluster on the source cluster
1 In the FileStore Management Console for the source cluster, click Replication> Replication Units.
2 In the Replication Units table, click the Create button.
3 In the Create Rep Unit dialog, enter information for the following fields:
Define a name for the replication unit, which will be used in thejob definition.
Rep Unit Name
Setting up Symantec FileStore ReplicationAbout the replication units operations
154
Enter the replication unit pattern for the replication unit.
A replication unit pattern can be the following three types:
■ File System Pattern - defines file system(s) as a replicationunit. All the files and directories in the source file system(s)are replicated to destination file system(s) specified by thispattern.
■ Dir Pattern - defines directory or directories in the file systemas a replication unit. All the files in the directory or directoriesare replicated to the destination directory or directoriesspecified by this pattern.
■ File Pattern - defines file(s) as a replication unit. Source file(s)are replicated to destination file(s) specified by this pattern.
The following are source replication unit pattern examples:
■ File System Pattern - [fs1] [fs1,fs2]
■ Dir Pattern - [fs1/dir1] [fs1/dir1,fs1/dir2/dir3]
■ File Pattern - [fs1/file1] [fs1/file2, fs1/dir1/file3]
Content in square brackets applies to input for the Enter FilePath field.
Enter File Path
4 Click the Add Files button.
5 Click OK.
6 In the Result dialog, click OK.
Creating replication units for the destination cluster on the sourcecluster
To create replication units for the destination cluster on the source cluster
1 In the FileStore Management Console on the source cluster, click Replication> Replication Units.
2 In the Replication Units table, click the Create button.
3 In the Create Rep Unit dialog, enter information for the following fields:
Define a name for the replication unit, which will be used in thejob definition.
Rep Unit Name
155Setting up Symantec FileStore ReplicationAbout the replication units operations
Enter the name of the destination file system pattern, destinationdir pattern, or the file pattern.
The following are destination replication unit pattern examples(relative to source replication unit pattern examples):
■ File System Pattern - [fs3] [fs3,fs4]
■ Dir Pattern - [fs3/dir1] [fs3/dir1,fs4/dir3/dir4]
■ File Pattern - [fs3/file1] [fs3/file2, fs4/dir3/file3]
Content in square brackets applies to input for the Enter FilePath field.
Enter File Path
4 Click the Add Files button.
5 Click OK.
6 In the Result dialog, click OK.
Adding a replication unit entryTo add a replication unit entry
1 In the FileStore Management Console, click Replication>ReplicationUnits.
2 Select the rep unit name that you want to add an entry to.
3 Right-click the name of the rep unit you want to add an entry to, and clickAdd Entry, or click the More button, and click Add Entry.
4 In the Add replication unit dialog, enter a rep unit entry, and click OK.
5 In the Result dialog, click OK.
Modifying a replication unit entryTo modify a replication unit entry
1 In the FileStore Management Console, click Replication>ReplicationUnits.
2 Select the rep unit name that you want to modify.
3 Right-click the name of the rep unit you want to modify, and click ModifyEntry, or click the More button, and click Modify Entry.
Setting up Symantec FileStore ReplicationAbout the replication units operations
156
4 In the Modify replication unit dialog, update the appropriate fields:
Displays the name of the rep unit you selected.Rep Unit Name
Select a rep unit entry from the drop-down menu.Rep Unit Entry
Enter a new rep unit entry.New Rep UnitEntry
5 Click OK.
6 In the Result dialog, click OK.
Removing a replication unit entryTo remove a replication unit entry
1 In the FileStore Management Console, click Replication>ReplicationUnits.
2 Select the rep unit name that you want to remove.
3 Right-click the name of the rep unit you want to remove, and click RemoveEntry, or click the More button, and click Remove Entry.
4 In the Remove replication unit dialog, select the rep unit entry to removefrom the drop-down menu, and click OK.
5 In the Result dialog, click OK.
157Setting up Symantec FileStore ReplicationAbout the replication units operations
Viewing information about replication unitsTo view information about replication units
◆ In the FileStore Management Console, click Replication>ReplicationUnits.
From the ReplicationUnits page, you can view the following information forFileStore Replication units:
Name of the replication unit.Replication UnitName
Name of the replication unit entry.
A replication unit is defined as an ordered set of entries, whereeach entry is one of the following: file system, subdirectory, ora single file.
Clicking on a replication unit entry takes you to the File SystemDetails page.
Entries
Name of the replication job.
Clicking this link takes you to the Jobs Details page.
Job Name
Destroying a replication unitThe Replication > Replication Units > Destroy operation destroys a replicationunit definition.
Note:Make sure that you first destroy the job that was using the replication units,or else the Destroy operation will fail.
To destroy a replication unit
1 In the FileStore Management Console, click Replication>ReplicationUnits.
2 Select the rep unit name that you want to destroy.
3 Right-click the name of the rep unit you want to destroy, and click Destroy,or click the Destroy button.
The Destroy Replication Unit dialog displays.
4 In the Destroy Replication Unit dialog, verify that you want to destroy theselected replication unit, and click OK.
5 In the Result dialog, click OK.
Setting up Symantec FileStore ReplicationAbout the replication units operations
158
About replication schedule operationsThe Schedule operation configures the schedules used for one or more jobs.FileStore Replication uses the following parameters to schedule the replicationjobs: minute, hour, day-of-the-month, month, and day-of-the-week.
FileStore Replication supports periodic replications, where the data gets replicatedfrom the source to the destination cluster at regular intervals defined by theschedule.
Table 8-3 Replication schedule operations
DefinitionOperations
Creates a schedule.create
Modifies an existing schedule.
Make sure that the job is first disabled before you modify the schedule.
modify
Deletes a schedule.
Note: Make sure that no currently running job is using this scheduledefinition.
delete
Creating a replication schedule on the source clusterTo create a replication schedule
1 In the FileStore Management Console for the source cluster, click Replication> Schedules.
2 In the Schedules table, click the Create button.
159Setting up Symantec FileStore ReplicationAbout replication schedule operations
3 In the Create Schedules dialog, enter information for the following fields:
Specify the name of the schedule to be created.Schedule Name
Specify the frequency for the schedule.Set Frequency
Select the minutes for running the replication schedule fromthe drop-down menu. Select a numeric value between 0-59,or an asterisk (*), which represents every minute.
Minute
Select the hour for running the replication schedule fromthe drop-down menu. Select a numeric value between 0-23,or an asterisk (*), which represents every hour.
Hour
Schedule the day of the month you want to run the replicationschedule from the drop-down menu. Select a numeric valuebetween 1-31, or an asterisk (*), which represents every dayof the month.
Day of the Month
Schedule the day of the week you want to run the replicationschedule from the drop-down menu. Select a day of the week,or an asterisk (*), which represents every day of the week.
Day of the Week
Schedule the month you want to run the replication schedulefrom the drop-down menu. Select a month, or an asterisk (*),which represents every month.
Month
4 Click OK.
5 In the Result dialog, click OK.
Setting up Symantec FileStore ReplicationAbout replication schedule operations
160
Viewing information about replication schedules on the source clusterTo view information about replication schedules
◆ In the FileStore Management Console on the source cluster, click Replication> Schedules.
From the Schedules page, you can view the following information for FileStoreReplication schedules:
Name of the replication schedule.Schedule Name
Replication jobs associated with the schedule.Associated Jobs
Number of minutes for running the schedule. An asterisk (*)represents running the schedule every minute.
Minute
Number of hours for running the schedule. An asterisk (*)represents running the schedule every hour.
Hour
Day of the month for running the schedule. An asterisk (*)represents running the schedule every day of the month.
Day of the Month
Month for running the schedule. An asterisk (*) representsrunning the schedule every month.
Month
Day of the week for running the schedule. An asterisk (*)represents running the schedule every day of the week.
Weekday
Modifying a replication schedule on the source clusterTo modify a schedule
1 In the FileStore Management Console on the source cluster, click Replication> Schedules.
2 Select the schedule you want to modify by clicking the box next to it.
3 In the Modify Schedule dialog, update information for the following fields:
Change the minute for running the replication schedule.Minute
Change the hour for running the replication schedule.Hour
Change the day of the month for running the replication schedule.Day of the Month
Change the day of the week for running the replication schedule.Day of the Week
Change the month for running the replication schedule.Month
161Setting up Symantec FileStore ReplicationAbout replication schedule operations
4 Click OK.
5 In the Result dialog, click OK.
Deleting a replication schedule on the source clusterTo delete a replication schedule
1 In the FileStore Management Console on the source cluster, click Replication> Schedules.
2 Select the schedule you want to delete by clicking the box next to it.
3 In the Delete Schedule dialog, verify the replication schedule you want todelete, and click OK.
4 In the Result dialog, click OK.
Setting up Symantec FileStore ReplicationAbout replication schedule operations
162
Setting up SymantecAntiVirus for FileStore
This chapter includes the following topics:
■ About Symantec AntiVirus for FileStore
■ About configuring Symantec AntiVirus for FileStore using the FileStoreManagement Console
■ Scheduling a Symantec AntiVirus for FileStore scan job
■ Viewing information about Symantec AntiVirus for FileStore scan jobs
■ Modifying a Symantec AntiVirus for FileStore scan job
■ Deleting a Symantec AntiVirus for FileStore scan job
■ Enabling a Symantec AntiVirus for FileStore scan job
■ Disabling a Symantec AntiVirus for FileStore scan job
■ Stopping a Symantec AntiVirus for FileStore scan job
■ Adding a LiveUpdate server
■ Deleting a LiveUpdate server
■ Initiating LiveUpdate manually
■ Viewing information about LiveUpdate
■ Initiating LiveUpdate by using schedules
■ Modifying a LiveUpdate schedule
■ Deleting a current LiveUpdate server schedule
9Chapter
■ Adding a proxy URL for a LiveUpdate server
■ Deleting a proxy URL for a LiveUpdate server
■ Viewing information about quarantined files
■ Deleting quarantined files
■ Repairing quarantined files
■ Displaying information about quarantined files
■ Restoring quarantined files
About Symantec AntiVirus for FileStoreFileStore includes the ability to enable scheduled and Auto-Protect (on-demand)antivirus scanning within the FileStore cluster and without requiring externalservers.
Symantec AntiVirus for FileStore provides two methods for protecting your 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-demandscanning of NFS, CIFS, or other protocols within FileStore.Symantec AntiVirus for FileStore provides support for the Auto-Protect methodthrough use of Auto-Protect operations provided at the file system level.See “Enabling Symantec AntiVirus for FileStore Auto-Protect for file systems”on page 104.
■ Scheduled scan - scans file systems for viruses when requested or at scheduledintervalsYou can use the Scheduled scan method to have automated scans occur atregular times, or to manually scan file systems on an as-needed basis.Symantec AntiVirus for FileStore provides support for scheduled scans throughuse of the AntiVirus > LiveUpdate and Settings > AntiVirus > Scan Actionsoperations.See “Setting the Symantec AntiVirus for FileStore action policy” on page 252.Manual scan support is provided at the file system level.See “Starting Symantec AntiVirus for FileStore manual scans” on page 105.
Setting up Symantec AntiVirus for FileStoreAbout Symantec AntiVirus for FileStore
164
Figure 9-1 Symantec AntiVirus for FileStore overview
Client Server
1. Client opens a file. 2. Symantec AntiVirus forFileStore scans the file.3. If a virus is found,Symantec AntiVirus forFileStore reacts based on thepolicies.
4. Client is allowed ordenied access to the file.
The client attempts to access a file from the share. A file becomes a candidatefor scanning when it is accessed.
1.
If Auto-Protect (AP) is enabled on the share, Symantec AntiVirus for FileStoreverifies if the file needs to be scanned or not based on parameters, such as fileextensions. If Auto-Protect is not enabled on that share, it lets you access thefile without Symantec AntiVirus for FileStore intervention.
2.
If the file is a candidate to be scanned, Symantec AntiVirus for FileStore scansthe file and takes the specified action, such as delete, quarantine, or clean, basedon the indicated scan action policies.
3.
Based on the scan results, you are allowed or denied access to the file.4.
About configuring Symantec AntiVirus for FileStoreusing the FileStore Management Console
Perform the following tasks in the order described in Table 9-1 to configureSymantec AntiVirus for FileStore using the FileStore Management Console. Youwill need to access multiple tabs, Settings > AntiVirus, AntiVirus, and FileSystems to configure Symantec AntiVirus for FileStore using the FileStoreManagement Console.
Table 9-1 Workflow for configuring Symantec AntiVirus for FileStore usingthe FileStore Management Console
Link for finding more information about the taskTask
See “Starting the Symantec AntiVirus for FileStore servicefor all the nodes” on page 251.
See “Stopping the Symantec AntiVirus for FileStore servicefor all the nodes” on page 251.
Starting or stopping theSymantec AntiVirus forFileStore service
165Setting up Symantec AntiVirus for FileStoreAbout configuring Symantec AntiVirus for FileStore using the FileStore Management Console
Table 9-1 Workflow for configuring Symantec AntiVirus for FileStore usingthe FileStore Management Console (continued)
Link for finding more information about the taskTask
See “Setting the Symantec AntiVirus for FileStore actionpolicy” on page 252.
Setting the SymantecAntiVirus for FileStoreaction policy
See “Excluding file extensions from Symantec AntiVirusfor FileStore scans” on page 252.
Excluding files from beingscanned
See “Adding a LiveUpdate server” on page 170.Adding a LiveUpdate server
See “Initiating LiveUpdate manually” on page 171.Initiating LiveUpdatemanually
See “Initiating LiveUpdate by using schedules” on page 172.Initiating LiveUpdate usingschedules
See “Enabling Symantec AntiVirus for FileStoreAuto-Protect for file systems” on page 104.
Enabling SymantecAntiVirus for FileStoreAuto-Protect for file systems
See “Disabling Symantec AntiVirus for FileStoreAuto-Protect for file systems” on page 104.
Disabling SymantecAntiVirus for FileStoreAuto-Protect for file systems
See “Starting Symantec AntiVirus for FileStore manualscans” on page 105.
Starting Symantec AntiVirusfor FileStore manual scans
See “Stopping Symantec AntiVirus for FileStore manualscans” on page 105.
Stopping SymantecAntiVirus for FileStoremanual scans
See “Scheduling a Symantec AntiVirus for FileStore scanjob” on page 167.
Scheduling a SymantecAntiVirus for FileStore scanjob
See “Viewing information about Symantec AntiVirus forFileStore scan jobs” on page 168.
Viewing information aboutSymantec AntiVirus forFileStore scan jobs
See “Modifying a Symantec AntiVirus for FileStore scanjob” on page 168.
Modifying a SymantecAntiVirus for FileStore scanjob
See “Disabling a Symantec AntiVirus for FileStore scan job”on page 170.
Disabling a SymantecAntiVirus for FileStore scanjob
Setting up Symantec AntiVirus for FileStoreAbout configuring Symantec AntiVirus for FileStore using the FileStore Management Console
166
Table 9-1 Workflow for configuring Symantec AntiVirus for FileStore usingthe FileStore Management Console (continued)
Link for finding more information about the taskTask
See “Viewing information about quarantined files”on page 175.
Viewing information aboutquarantined files
See “Repairing quarantined files” on page 176.Repairing quarantined files
See “Restoring quarantined files” on page 176.Restoring quarantined files
See “Stopping the Symantec AntiVirus for FileStore servicefor all the nodes” on page 251.
Stopping the SymantecAntiVirus for FileStoreservice
Scheduling a Symantec AntiVirus for FileStore scanjob
To schedule a Symantec AntiVirus for FileStore scan job
1 In the FileStore Management Console, click AntiVirus > AntiVirus Jobs.
2 Click the Create button.
3 In the Create Job dialog, enter information for the following fields:
Enter a unique job name for the scan.Job Name
Select the file system you want to have scanned from thedrop-down menu.
Name of FileSystem
Specify the frequency for running the scheduled scan job fromthe drop-down menus for Minute, Hour, Day of the Month, Dayof the Week, and Month.
Set Frequency
Specify the preferred node for running the scan job from thedrop-down menu.
Preferred Node
4 Click OK.
5 In the Result dialog, click OK.
167Setting up Symantec AntiVirus for FileStoreScheduling a Symantec AntiVirus for FileStore scan job
Viewing information about Symantec AntiVirus forFileStore scan jobs
To view Symantec AntiVirus for FileStore scan jobs
◆ In the FileStore Management Console, click AntiVirus > AntiVirus Jobs.
In the AntiVirus Jobs page, you can view the following information:
Name of the scan job.Job Name
Name of the file system where the scan job is run.File System
Number of minutes for running the scan job.Minute
Hour for running the scan job.Hour
Day of the month for running the scan job.Day of the Month
Month for running the scan job.Month
Day of the week for running the scan job.Weekday
State of the scan job.
Available values include:
■ Disable
■ Enable
■ Not Started
■ Scheduled
■ Completed
State
Preferred node for running the scan job.Preferred Node
Modifying a Symantec AntiVirus for FileStore scanjob
To modify a Symantec AntiVirus for FileStore scan job
1 In the FileStore Management Console, click AntiVirus > AntiVirus Jobs.
2 Select the scan job that you want to modify.
3 Click the Modify button.
Setting up Symantec AntiVirus for FileStoreViewing information about Symantec AntiVirus for FileStore scan jobs
168
4 In the Modify Job dialog, enter information for the following fields:
Modify the scan job name.Job Name
Select the file system you want to have scanned from thedrop-down menu.
Name of FileSystem
Specify the frequency for running the scheduled scan job fromthe drop-down menus for Minute, Hour, Day of the Month, Dayof the Week, and Month.
Set Frequency
Specify the preferred node for running the scan job from thedrop-down menu.
Preferred Node
5 Click OK.
6 In the Result dialog, click OK.
Deleting a Symantec AntiVirus for FileStore scan jobTo delete a Symantec AntiVirus for FileStore scan job
1 In the FileStore Management Console, click AntiVirus > AntiVirus Jobs.
2 Select the scan job that you want to delete.
3 Click the More button, and click Delete, or right-click the JobName, and clickDelete.
4 In the Delete Job dialog, verify the name of the scan job you want to delete,and click OK.
5 In the Result dialog, click OK.
Enabling a Symantec AntiVirus for FileStore scan jobTo enable a Symantec AntiVirus for FileStore scan job
1 In the FileStore Management Console, click AntiVirus > AntiVirus Jobs.
2 Select the scan job that you want to enable.
3 Click the More button, and click Enable, or right-click the Job Name, andclick Enable.
4 In the Enable Job dialog, verify the name of the scan job you want to enable,and click OK.
5 In the Result dialog, click OK.
169Setting up Symantec AntiVirus for FileStoreDeleting a Symantec AntiVirus for FileStore scan job
Disabling a Symantec AntiVirus for FileStore scan jobTo disable a Symantec AntiVirus for FileStore scan job
1 In the FileStore Management Console, click AntiVirus > AntiVirus Jobs.
2 Select the scan job that you want to disable.
3 Click the More button, and click Disable, or right-click the Job Name, andclick Disable.
4 In the Disable Job dialog, verify the name of the scan job you want to disable,and click OK.
5 In the Result dialog, click OK.
Stopping a Symantec AntiVirus for FileStore scan jobTo stop a Symantec AntiVirus for FileStore scan job
1 In the FileStore Management Console, click AntiVirus > AntiVirus Jobs.
2 Select the scan job that you want to stop.
3 Click the More button, and click Stop, or right-click the Job Name, and clickStop.
4 In the Stop Job dialog, verify the name of the scan job you want to stop, andclick OK.
5 In the Result dialog, click OK.
Adding a LiveUpdate serverYou can use the LiveUpdate feature to add LiveUpdate servers to SymantecAntiVirus for FileStore for updating virus definitions. You can add a maximumof 10 servers and 1 proxy server to the LiveUpdate server list.
To add a LiveUpdate server
1 In the FileStore Management Console, click AntiVirus > LiveUpdate.
2 Click the Server ID for the LiveUpdate server you want to add, and click theAdd button, or right-click the Server ID, and click Add.
3 In the Add LiveUpdate dialog, update the URL field.
Select either http, ftp, or proxy from the drop-down menu.
Enter a URL, as in sample.com.
Setting up Symantec AntiVirus for FileStoreDisabling a Symantec AntiVirus for FileStore scan job
170
4 Click OK.
5 In the Result dialog, click OK.
Deleting a LiveUpdate serverTo delete a LiveUpdate server
1 In the FileStore Management Console, click AntiVirus > LiveUpdate.
2 Select the LiveUpdate server that you want to delete.
3 Click the Delete button, or right-click the Server ID, and click Delete.
4 In the Delete Server dialog, verify that you want to delete the selectedLiveUpdate server, and click OK.
5 In the Result dialog, click OK.
Initiating LiveUpdate manuallyYou can update virus definitions in two ways, either manually or by usingschedules.
To initiate LiveUpdate manually
1 In the FileStore Management Console, click AntiVirus > LiveUpdate.
2 In the LiveUpdate Servers table, click Start LiveUpdate.
3 In the Start LiveUpdate dialog, verify that you want to start LiveUpdatemanually, and click OK.
4 In the Result dialog, click OK.
171Setting up Symantec AntiVirus for FileStoreDeleting a LiveUpdate server
Viewing information about LiveUpdateTo view information about LiveUpdate
◆ In the FileStore Management Console, click AntiVirus > LiveUpdate.
In the LiveUpdate page, you can view information about LiveUpdate servers,LiveUpdate schedules, virus definition versions, and proxy URLs.
In the LiveUpdate Servers table, you can view the following information.You can also add or delete LiveUpdate servers.
ID of the LiveUpdate server.Server ID
Location of the LiveUpdate server.Server URL
In the LiveUpdate Schedule section, you can view the current LiveUpdateschedule. You can also create, modify, or delete a LiveUpdate schedule.
In the Virus Definition Version section, you can view the current virusdefinition version.
In the Proxy URL section, you can view, add or delete proxy URLs.
Initiating LiveUpdate by using schedulesYou can update virus definitions in two ways, either manually or by usingschedules.
To initiate LiveUpdate by using schedules
1 In the FileStore Management Console, click AntiVirus > LiveUpdate.
2 In the LiveUpdate Schedule section, click Create.
Setting up Symantec AntiVirus for FileStoreViewing information about LiveUpdate
172
3 In the Create Schedule dialog, enter information for the following fields:
Specify the minutes for running the LiveUpdate.
An asterisk indicates running a schedule task every minute.
Minute
Specify the hour for running the LiveUpdate.
An asterisk indicates running a schedule task every hour.
Hour
Specify the day of the month for running the LiveUpdate.
An asterisk indicates running a schedule task every day of themonth.
Day of the Month
Specify the day of the week for running the LiveUpdate.
An asterisk indicates running a schedule task every day of theweek.
Day of the Week
Specify the month for running the LiveUpdate.
An asterisk indicates running a schedule task every month.
Month
4 Click OK.
5 In the Result dialog, click OK.
Modifying a LiveUpdate scheduleTo modify a LiveUpdate schedule task
1 In the FileStore Management Console, click AntiVirus > LiveUpdate.
2 In the LiveUpdate Schedule section, click Modify.
173Setting up Symantec AntiVirus for FileStoreModifying a LiveUpdate schedule
3 In the Modify Schedule dialog, enter information for the following fields:
Specify the minutes for running the LiveUpdate.
An asterisk indicates running a schedule task every minute.
Minute
Specify the hour for running the LiveUpdate.
An asterisk indicates running a schedule task every hour.
Hour
Specify the day of the month for running the LiveUpdate.
An asterisk indicates running a schedule task every day of themonth.
Day of the Month
Specify the day of the week for running the LiveUpdate.
An asterisk indicates running a schedule task every day of theweek.
Day of the Week
Specify the month for running the LiveUpdate.
An asterisk indicates running a schedule task every month.
Month
4 Click OK.
5 In the Result dialog, click OK.
Deleting a current LiveUpdate server scheduleTo delete a current LiveUpdate server schedule
1 In the FileStore Management Console, click AntiVirus > LiveUpdate.
2 In the LiveUpdate Schedule section, click Delete.
3 In the Delete Schedule dialog, verify that you want to delete the LiveUpdateserver schedule, and click OK.
4 In the Result dialog, click OK.
Adding a proxy URL for a LiveUpdate serverTo add a proxy URL
1 In the FileStore Management Console, click AntiVirus > LiveUpdate.
2 In the Proxy URL table, click Add.
Setting up Symantec AntiVirus for FileStoreDeleting a current LiveUpdate server schedule
174
3 In the AddProxyURL dialog, enter a proxy URL, for example, myproxy.com,and click OK.
4 In the Result dialog, click OK.
Deleting a proxy URL for a LiveUpdate serverTo delete a proxy URL for a LiveUpdate server
1 In the FileStore Management Console, click AntiVirus > LiveUpdate.
2 In the Proxy URL table, click Delete to delete the existing proxy URL.
3 In the Delete Proxy URL dialog, verify that you want to delete the specifiedproxy URL, and click OK.
4 In the Result dialog, click OK.
Viewing information about quarantined filesFileStore places scanned files that have not passed the virus protection softwarein quarantine. You can display information about the files placed in quarantine,delete the files, repair the files, or restore quarantined files.
Each quarantined file is associated with an ID. Each node stores quarantined fileslocally. If any node is removed from a cluster, quarantined files on that node arelost.
To view information about quarantined files
◆ In the FileStore Management Console, click AntiVirus > Quarantine.
In the Quarantine page, you can view the following information:
ID for the quarantined file.
For example, 8BA00000.
QID
Full path to the location of the quarantined file.Full Path
Deleting quarantined filesTo delete quarantined files
1 In the FileStore Management Console, click AntiVirus > Quarantine.
2 Select a QID or multiple QIDs you want to delete.
175Setting up Symantec AntiVirus for FileStoreDeleting a proxy URL for a LiveUpdate server
3 Click the Delete button, or right-click the QID or multiple QIDs and clickDelete.
4 In the Delete Quarantine dialog, verify that you want to delete the selectedquarantined file or files, and click OK.
5 In the Result dialog, click OK.
Repairing quarantined filesTo repair quarantined files
1 In the FileStore Management Console, click AntiVirus > Quarantine.
2 Click a QID or multiple QIDs you want to repair.
3 Click the Repair button, or right-click the QID or multiple QIDs, and clickRepair.
4 In the Repair Quarantine dialog, verify that you want to repair the selectedquarantined file or files, and click OK.
5 In the Result dialog, click OK.
Displaying information about quarantined filesTo display information about quarantined files
1 In the FileStore Management Console, click AntiVirus > Quarantine.
2 Click a QID or multiple QIDs you want information about, and either clickthe More button, and select Info, or right-click the QID or multiple QIDs,and click Info.
3 In the Info Job dialog, verify that you want to view information about theselected quarantined file or files, and click OK.
4 In the Result dialog, click OK.
Restoring quarantined filesTo restore quarantined files
1 In the FileStore Management Console, click AntiVirus > Quarantine.
2 Click a QID or multiple QIDs you want to restore.
3 Click the More button, and select Restore, or right-click the QID or multipleQIDs, and click Restore.
Setting up Symantec AntiVirus for FileStoreRepairing quarantined files
176
4 In the Restore Job dialog, verify that you want to restore the selectedquarantined file or files, and click OK.
5 In the Result dialog, click OK.
177Setting up Symantec AntiVirus for FileStoreRestoring quarantined files
Setting up Symantec AntiVirus for FileStoreRestoring quarantined files
178
Managing SymantecFileStore network settings
This chapter includes the following topics:
■ About FileStore settings
■ Starting an NFS server
■ Stopping an NFS server
■ Viewing status information for the NFS server
■ Displaying NFS status information for all the nodes in the cluster
■ About configuring FileStore for CIFS
■ About mapping user names for CIFS/NFS sharing
■ Adding a CIFS local user
■ Adding a CIFS user to a group
■ Deleting a CIFS local user
■ Changing a CIFS user password
■ Adding a CIFS local group
■ Deleting a CIFS local group
■ Starting the FTP server
■ Stopping the FTP server
■ Viewing status information for the FTP server
10Chapter
■ Configuring the FTP server
■ Adding FTP local user accounts
■ Changing a password for an FTP local user
■ Setting user attributes for an FTP local user
■ Deleting an FTP local user account
■ About DNS
■ Configuring DNS settings
■ Enabling DNS services
■ Disabling DNS services
■ Configuring NIS settings
■ Enabling NIS services
■ Disabling NIS services
■ Viewing information about your network configuration and statistics
■ Adding a bond Ethernet interface
■ Removing a bond Ethernet interface
■ Adding an IP address to a cluster
■ Deleting an IP address from a cluster
■ Modifying an IP address
■ Modifying the status of an IP address to online
■ Modifying the configuration of an Ethernet interface
■ Adding a new IP route to a cluster
■ Deleting an IP route from a cluster
■ About configuring LDAP settings
■ Configuring LDAP server settings and enabling SSL
■ Enabling LDAP
■ Disabling LDAP
■ Enabling SSL for LDAP access
Managing Symantec FileStore network settings180
■ Disabling SSL for LDAP access
■ Restoring LDAP default settings
■ About NSS
■ Configuring an NSS lookup order
■ Viewing information about VLAN devices
■ Adding a VLAN device
■ Removing a VLAN device
■ Viewing the clock, setting the NTP server and global cache
■ Setting the system clock
■ Setting the time zone
■ Modifying the number of NFS daemons
■ Creating or modifying DMP I/O policies
■ Modifying DMP tune attributes
■ Modifying global tune fstab attributes
■ About importing or exporting configuration settings
■ About backup services
■ Viewing backup services
■ Starting backup services
■ Stopping backup services
■ Viewing details about backup services
■ About NetBackup
■ Configuring backup using NetBackup
■ Adding a media server
■ Deleting a media server
■ About the Network Data Management Protocol
■ About SNMP notifications
■ Configuring report settings
181Managing Symantec FileStore network settings
■ Deleting an email server
■ Exporting event notifications
■ Adding an SNMP management server
■ Deleting an SNMP management server
■ Adding a syslog server address
■ Deleting a syslog server address
■ Adding an email group
■ Removing an email group
■ Adding a severity/filter
■ Removing a severity/filter
■ Adding an email to an email group
■ Deleting an email from an email group
■ Viewing user accounts
■ Adding new user accounts
■ Removing user accounts
■ Resetting passwords
■ Viewing upgrade settings
■ Upgrading FileStore
■ Uninstalling FileStore up to the specified version
■ Syncing nodes
■ Configuring FileStore Replication
■ Configuring the Symantec AntiVirus for FileStore service
About FileStore settingsYou can use the FileStore Settings page to perform the following tasks as describedin Table 10-1.
Managing Symantec FileStore network settingsAbout FileStore settings
182
Table 10-1 Managing FileStore network settings tasks
Where to find more information about the taskTask
See “Starting an NFS server” on page 185.
See “Stopping an NFS server” on page 185.
See “Viewing status information for the NFS server” on page 186.
Starting, stopping,and viewing statusinformation forthe NFS server
See “Starting a CIFS server” on page 188.
See “Stopping a CIFS server” on page 188.
See “Viewing status information for the CIFS server” on page 189.
Starting, stopping,and viewing statusinformation for aCIFS server
See “Configuring a CIFS server” on page 189.
See “About mapping user names for CIFS/NFS sharing” on page 191.
Configuring a CIFSserver forstandalone mode
Mapping usernames forCIFS/NIFS sharing
See “Adding a CIFS local user” on page 192.
See “Adding a CIFS user to a group” on page 193.
See “Deleting a CIFS local user” on page 193.
See “Changing a CIFS user password” on page 194.
See “Adding a CIFS local group” on page 194.
See “Deleting a CIFS local group” on page 194.
Managing CIFSlocal users andgroups
See “Starting the FTP server” on page 195.
See “Stopping the FTP server” on page 195.
See “Configuring the FTP server” on page 197.
Starting, stopping,and configuringthe FTP server
See “Adding FTP local user accounts” on page 200.
See “Changing a password for an FTP local user” on page 200.
See “Setting user attributes for an FTP local user” on page 200.
Managing FTPlocal users
See “Configuring DNS settings” on page 202.
See “Configuring NIS settings” on page 203.
Configuring DNSand NIS settings
See “Viewing information about your network configuration andstatistics” on page 204.
Viewinginformation aboutyour networkconfiguration andstatistics
183Managing Symantec FileStore network settingsAbout FileStore settings
Table 10-1 Managing FileStore network settings tasks (continued)
Where to find more information about the taskTask
See “Adding a bond Ethernet interface” on page 207.
See “Removing a bond Ethernet interface” on page 207.
Adding orremoving bondEthernetinterfaces
See “Adding an IP address to a cluster” on page 208.
See “Deleting an IP address from a cluster” on page 208.
Adding or deletingIP addresses
See “Modifying an IP address” on page 209.
See “Modifying the status of an IP address to online” on page 209.
Modifying orchanging thestatus of an IPaddress to online
See “Modifying the configuration of an Ethernet interface” on page 209.Modifying andEthernet interfaceconfiguration
See “Adding a new IP route to a cluster” on page 210.
See “Deleting an IP route from a cluster” on page 211.
Adding or deletingan IP route
See “Configuring LDAP server settings and enabling SSL” on page 212.Enabling LDAPand SSL
See “Configuring NIS settings” on page 203.ConfiguringNS-switch settings
See “Adding a VLAN device” on page 216.
See “Removing a VLAN device” on page 216.
Adding orremoving VLANdevices
See “Viewing the clock, setting the NTP server and global cache”on page 217.
Configuring clockand NTP settings
See “Importing configuration settings” on page 223.Importing andexportingconfigurationsettings
See “Configuring backup using NetBackup” on page 228.Configuringbackup
See “Configuring NDMP policies” on page 233.Configuring NDMPpolicies
Managing Symantec FileStore network settingsAbout FileStore settings
184
Table 10-1 Managing FileStore network settings tasks (continued)
Where to find more information about the taskTask
See “Configuring report settings” on page 234.Configuring eventnotifications
See “Adding new user accounts” on page 241.
See “Removing user accounts” on page 242.
See “Resetting passwords” on page 242.
Managing users
See “Upgrading FileStore” on page 243.UpgradingFileStore
See “Configuring FileStore Replication” on page 244.Configuringreplicationsettings
See “Configuring the Symantec AntiVirus for FileStore service”on page 251.
ConfiguringSymantecAntiVirus forFileStore
Starting an NFS serverTo start an NFS server
1 In the FileStore Management Console, click Settings > General > NFS.
2 In the NFS Server Status on Nodes table, select the node name you want tostart, and click the Start Server button.
3 In the Start Server dialog, verify that you want to start the selected NFSserver, and click OK.
4 In the Result dialog, click OK.
Stopping an NFS serverA node must have a status of Online to be stopped.
You receive an error if you try to stop an already stopped NFS server.
To stop an NFS server
1 In the FileStore Management Console, click Settings > General > NFS.
2 In the NFS Server Status on Nodes table, select the node name you want tostop, and click the Stop Server button.
185Managing Symantec FileStore network settingsStarting an NFS server
3 In the StopServer dialog, verify that you want to stop the selected NFS server,and click OK.
4 In the Result dialog, click OK.
Viewing status information for the NFS serverTo view status information for the NFS server
◆ In the FileStore Management Console, click Settings > General > NFS.
From the NFS Server Status on Nodes table, you can view the followinginformation for the NFS server:
Name of the node.Node Name
Status of the node.
Available values are:
■ ONLINE - indicates that the node can serve NFS protocols tothe client.
■ OFFLINE - indicates that NFS services on that node are down.
■ FAULTED - indicates something is wrong with the NFS serviceon the node.
NFS Server Status
Displaying NFS status information for all the nodesin the cluster
To display NFS status information for all nodes in the cluster
1 In the FileStore Management Console, click Settings > General > NFS.
2 Click the NFS Stats button.
3 In the NFS Stats dialog, you see output similar to the following:
test_01
--------------------------------------------------
Server rpc stats:
calls badcalls badauth badclnt xdrcall
0 0 0 0 0
---------------------------------------------------
Managing Symantec FileStore network settingsViewing status information for the NFS server
186
4 Click OK.
5 In the Result dialog, click OK.
About configuring FileStore for CIFSThe 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 otheroperating systems. This chapter describes the initial configuration of the FileStoreCIFS service on three operating modes, and how to reconfigure the FileStore CIFSservice when, some CIFS settings are changed.
FileStore can be integrated into a network that consists of computers runningMicrosoft Windows. You can control and manage the network resources by usingActive Directory (AD) or NT workgroup domain controllers.
Before you use FileStore with CIFS, you must have administrator-level knowledgeof the Microsoft operating systems, Microsoft services, and Microsoft protocols(including AD and NT services and protocols).
See www.microsoft.com for more information.
When serving CIFS clients, you can configure FileStore to operate in one of themodes as described in Table 10-2.
Table 10-2 CIFS modes
DefinitionMode
Information about the user and group accounts is stored locally onFileStore. FileStore also authenticates users locally using the Linuxpassword and group files. This mode of operation is provided forFileStore testing and may be appropriate in other cases, for example,when FileStore is used in a small network and is not a member of aWindows security domain. In this mode of operation, you must createthe local users and groups; they can access the shared resources subjectto authorization control.
Standalone
FileStore becomes a member of an NT4 security domain. The domaincontroller stores user and group account information, and theMicrosoft NTLM or NTLMv2 protocol authenticates.
NT Domain
FileStore becomes a member of an AD security domain and isconfigured to use the services of the AD domain controller, such asDNS, LDAP, and NTP. Kerberos, NTLMv2, or NTLM authenticatesusers.
Active Directory(AD)
187Managing Symantec FileStore network settingsAbout configuring FileStore for CIFS
When FileStore operates in the NT or AD domain mode, it acts as a domain memberserver and not as the domain controller.
About configuring CIFS for standalone modeIf you do not have an Active Directory (AD) server or NT domain controller, youcan use FileStore as a standalone server. FileStore is used in standalone modewhen testing FileStore functionality and when it is not a member of a domain.
Before you configure the CIFS service for standalone mode, do the following:
■ Make sure that the CIFS server is not runningSee “Viewing status information for the CIFS server” on page 189.
■ Set security to userSee “Configuring a CIFS server” on page 189.
■ Start the CIFS serverSee “Starting a CIFS server” on page 188.
Starting a CIFS serverTo start a CIFS server
1 In the FileStore Management Console, click Settings > General > CIFS.
2 In the CIFS Server status on nodes table, select the node you want to start,and click the Start Server button.
3 In the Start Server dialog, verify that you want to start the selected CIFSserver, and click OK.
4 In the Result dialog, click OK.
Stopping a CIFS serverThe node must have a status of Online to be stopped.
To stop a CIFS server
1 In the FileStore Management Console, click Settings > General > CIFS.
2 In the CIFS Server Status on Nodes table, select the node you want to stop,and click the Stop Server button.
3 In the Stop Server dialog, verify that you want to stop the selected CIFSserver, and click OK.
4 In the Result dialog, click OK.
Managing Symantec FileStore network settingsAbout configuring FileStore for CIFS
188
Viewing status information for the CIFS serverTo view status information for the CIFS server
◆ In the FileStore Management Console, click Settings > General > CIFS.
From the CIFS Server Status on Nodes table, you can view the followinginformation for the CIFS server:
Name of the node.Node Name
Status of the node.
Available values are:
■ ONLINE - indicates that the CIFS server is online
■ OFFLINE - indicates that the CIFS server is offline
■ PARTIAL - indicates that some of the underlying services(Veritas Cluster Server resources) are not online in the CIFSgroup. For example, currently FileStore uses SMB, NMB,Winbind, and share resources in the CIFS group. If some ofthe share resources are not online, then the CIFS server statusdisplays a PARTIAL state.
Some of the resources are critical in the group while othersare non- critical. In the last example, SMB, NMB, and Winbindresources are critical. If all of the three resources are notONLINE, then the CIFS server state displays as in theFAULTED/OFFLINE state.
CIFS Server Status
Configuring a CIFS serverTo configure a CIFS server
1 In the FileStore Management Console, click Storage > General > CIFS.
2 In the CIFS Server Status on Nodes table, enter the appropriate options.
CIFS security level.
Enter the CIFS security level from the drop-down menu.
Security
Active Directory (AD) or NT workgroup domain controller.
Enter the IP address or the DNS name for the server.
Domain Controller(Required)
Name of the domain that FileStore will join.
Enter the domain name for which FileStore will join.
Domain Name(Required)
189Managing Symantec FileStore network settingsAbout configuring FileStore for CIFS
Existing NT domain user.
Enter the name of an existing NT domain user who haspermission to perform the join domain operation.
Domain User(Required)
Enter the workgroup name for the AD or NT domain controller.
Though the following symbols $,( ), ', and & are valid charactersfor naming a WORKGROUP, the FileStore CIFS implementationdoes not allow using these symbols.
Workgroup
Enter the Asynchronous I/O (AIO) read/write size.AIO R/W Size
FileStore can be used to store users' home directories.
Enter the home directory file system names.
Home directoryfile system(s)
Enter the CIFS clustering mode from the drop-down menu.Clustering Mode
Select either Yes or No from the drop-down menu to enable ordisable the use of Microsoft NTLM (NT LAN Manager) protocolfor authenticating users.
NTLM Auth
Select either Yes or No from the drop-down menu to enable ActiveDirectory trusted domains.
Allow TrustedDomains
Select either RID or LDAP from the drop-down menu.
Valid values include:
■ RID - configures FileStore to store information about usersand groups locally.
This operation requires that Allow Trusted Domains not beenabled, as the operation is not compatible with trusteddomains.
■ LDAP - configures FileStore to store information about usersand groups in a remote LDAP service. This operation onlyworks when configuring CIFS in the AD domain mode. TheLDAP service can run on the domain controller or it can beexternal to the domain controller. For FileStore to use theLDAP service, the LDAP service must include both RFC 2307and Samba schema extensions. When set to LDAP, you canenable or disable Allow Trusted Domains. You must firstconfigure LDAP settings at the Settings > General > LDAPtab.
Idmap Type
Managing Symantec FileStore network settingsAbout configuring FileStore for CIFS
190
Enter the idmap value.
If IdmapType is RID, then IdmapValue should be 10000:20000,where the range of numbers must be between 10000-1000000000.
If IdmapType is LDAP, then IdmapValue is not required. LDAPneeds to be configured in Settings > General > LDAP.
Idmap Value
Displays the netbios name.Netbios Name
Enter a comma-separated list of netbios alias names.
After setting the netbios alias name(s), you can access the CIFSserver by using the specified alias name(s).
Netbios Aliases
3 Click Save.
About mapping user names for CIFS/NFS sharingThe CIFS server uses user name mapping to translate login names sent by aWindows client to local or remote UNIX user names. The CIFS server uses filelookup for mapping, and this mapping is unidirectional. You can map a CIFS userto 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 singleUNIX user
When user name mapping takes place is dependent on the current securityconfigurations. If security is set to user, mapping is done before authentication,and a password must be provided for the mapped user name. For example, if thereis a mapping between the users CIFSuser1 and NFSuser1. If CIFSuser1 wants toconnect to the FileStore server, then CIFSuser1 needs to provide a passwordforNFSuser1. In this case, NFSuser1 must be the CIFS local user.
The domain you specify for CIFS user name mapping must be the netbios domainname (instead of the Active Directory DNS domain name) for the user. For example,a netbios domain name might be listed as SYMANTECDOMAIN instead ofSYMANTECDOMAIN.COM (without the .COM extension).
To determine the netbios domain name, login to your Active Directory Server andtype the following in a command window:
set | findstr DOMAIN
The results include:
191Managing Symantec FileStore network settingsAbout mapping user names for CIFS/NFS sharing
USERDOMAIN netbios_domain_name
USERDNSDOMAIN Active_Directory_DNS_domain_name
Use the value of the USERDOMAIN (the netbios domain name) when you mapuser names.
Mapping a CIFS userTo map a CIFS user name
1 In the FileStore Management Console, click Settings > General > CIFS.
2 In the Map User table, click the Add button.
3 In the Add CIFS Map User dialog, update the following required fields:
Enter a CIFS user name, for example, CIFSuser1.CIFS User Name(Required)
Enter a domain name, for example, SYMANTECDOMAIN.COM.Domain Name(Required)
Enter an NFS user name, for example, NFSuser1.NFS User Name(Required)
4 Click OK.
5 In the Result dialog, click OK.
Removing a mapped CIFS userTo remove a mapped CIFS user
1 In the FileStore Management Console, click Settings > General > CIFS.
2 In the Map User table, select the CIFS User Name you want to remove, andclick Remove.
In the Remove CIFS Map User dialog, verify that you want to remove theselected CIFS user name, and click OK.
3 In the Result dialog, click OK.
Adding a CIFS local userWhen FileStore is operating in the standalone mode, only the local users andgroups of users can establish CIFS connections and access the home directoriesand ordinary shares. The FileStore local files store the information about these
Managing Symantec FileStore network settingsAdding a CIFS local user
192
user and group accounts. Local procedures authenticate and authorize these usersand groups based on the use of names and passwords.
To add a CIFS local user
1 In the FileStore Management Console, click Settings > General > CIFS.
2 In the CIFS Local User table, click the Add CIFS User button.
3 In the Add CIFS User dialog, update the following fields:
Enter a CIFS user name, for example, CIFSuser1.CIFS User Name(Required)
Enter a comma-separated list of group names, for example:grp2,grp1.
CIFS Group Name
Enter the password.Password(Required)
Re-enter the password.Retype password(Required)
4 Click OK.
5 In the Result dialog, click OK.
Adding a CIFS user to a groupTo add a CIFS user to a group
1 In the FileStore Management Console, click Settings > General > CIFS.
2 In the CIFSLocalUser table, select a CIFS user name to add to the group, andclick Add User to Group.
3 In the Add CIFS User to Group dialog, enter the CIFS group name (forexample, grp1), and click OK.
4 In the Result dialog, click OK.
Deleting a CIFS local userTo delete a CIFS local user
1 In the FileStore Management Console, click Settings > General > CIFS.
2 In the CIFS Local User table, select a CIFS user name to delete, and clickDelete User.
193Managing Symantec FileStore network settingsAdding a CIFS user to a group
3 In the Delete Local User dialog, verify that you want to delete the selectedCIFS local user, and click OK.
4 In the Result dialog, click OK.
Changing a CIFS user passwordTo change a CIFS user password
1 In the FileStore Management Console, click Settings > General > CIFS.
2 In the CIFSLocalUser table, select a CIFS user name you want to change thepassword for, and click Change Password.
3 In the Change CIFS User Password dialog, enter the current CIFS userpassword in the New Password field, and then re-enter the password in theRetype New Password field to verify that the password is correct.
4 Click OK.
5 In the Result dialog, click OK.
Adding a CIFS local groupTo add a CIFS local group
1 In the FileStore Management Console, click Settings > General > CIFS.
2 In the CIFS Local Group table, click the Add Group button.
3 In the AddCIFSGroup dialog, enter the CIFS group name, for example, grp1,and click OK.
4 In the Result dialog, click OK.
Deleting a CIFS local groupTo delete a CIFS local group
1 In the FileStore Management Console, click Settings > General > CIFS.
2 In the CIFS Local Group table, select a CIFS group name that you want todelete, and click Delete Group.
3 In the Delete CIFS Group dialog, verify that you want to delete the selectedCIFS group, and click OK.
4 In the Result dialog, click OK.
Managing Symantec FileStore network settingsChanging a CIFS user password
194
Starting the FTP serverThe File Transfer Protocol (FTP) server feature allows clients to access files onFileStore servers using the FTP protocol. The FTP service providessecure/non-secure access by means of FTP to files in FileStore servers. The FTPservice runs on all of the nodes in the cluster, and provides simultaneousread/write access to the files. The FTP service also provides configurableanonymous access to FileStore.
To start the FTP server
1 In the FileStore Management Console, click Settings > General > FTP.
2 In the FTP Server Status on Nodes table, click Start Server.
3 In the Start Server dialog, verify that you want to start the selected FTPserver, and click OK.
4 In the Result dialog, click OK.
Stopping the FTP serverBy default, the FTP server is OFFLINE. The FTP server starts on the standard FTPport 21.
To stop the FTP server
1 In the FileStore Management Console, click Settings > General > FTP.
2 In the FTP Server Status on Nodes table, click Stop Server.
3 In the StopServer dialog, verify that you want to stop the selected FTP server,and click OK.
4 In the Result dialog, click OK.
Viewing status information for the FTP serverTo view status information for the FTP server
1 In the FileStore Management Console, click Settings > General > FTP.
2 From the FTP Server Status on Nodes table, you can view the followinginformation for the FTP server:
Name of the node.Node Name
195Managing Symantec FileStore network settingsStarting the FTP server
Status of the node.
Available values are:
■ ONLINE - indicates that the node can serve FTP protocols tothe client.
■ OFFLINE - indicates that FTP services on that node are down.
FTP Server Status
Managing Symantec FileStore network settingsViewing status information for the FTP server
196
Configuring the FTP serverTo configure FTP
1 In the FileStore Management Console, click Settings > General > FTP.
197Managing Symantec FileStore network settingsConfiguring the FTP server
2 In the Configure FTP Settings table, enter the appropriate options.
Tells the FTP server whether or not to allow anonymous logons.Anonymous login
By checking this checkbox, you allow anonymous users to log on to the FTP server. By notchecking this checkbox, you do not allow anonymous logons to the FTP server.
For changes to take effect, you need to restart the FTP server.
Specifies whether or not anonymous users have write access in their login directory.Anonymous writeaccess
By checking this checkbox, you allow anonymous users to modify the content of their logindirectory. By not checking this checkbox (default), you do not allow anonymous users to modifythe content of their login directory.
Make sure that the anonymous user (UID:40 GID:49 UNAME:ftp) has the appropriate permissionsto modify files in their login directory.
For the changes to take effect, you need to restart the FTP server.
Specifies the login directory for anonymous users.Anonymous logindirectory
The login directory must start with /vx/. Make sure that the anonymous user (UID:40 GID:49UNAME:ftp) has the appropriate permissions to read files in the login directory.
Specifies the maximum number of simultaneous FTP clients allowed.Maximumconnections limit(Required)
Valid values are from 1-9999. The default value is 2000. The value affects the entire cluster.
For the changes to take effect, you need to restart the FTP server.
Specifies the maximum number of simultaneous FTP connections that are allowed from a singleclient IP address.
Maximumconnections perclient (Required)
Valid values are from 1-999. The default value is 2000.
For the changes to take effect, you need to restart the FTP server.
Specifies the range of port numbers to listen on for passive FTP transfers. The Port Rangedefines a range that is specified with a starting port and an ending port, as in 30000:40000.
Port range(Required)
Valid values for port numbers range from 30000 to 50000. The default value is 30000:40000.
For the changes to take effect, you need to restart the FTP server.
Specifies the port number on which the FTP service listens for connections.Listen on port(Required)
Valid values are from 10-1023. The default value is 21.
For the changes to take effect, you need to restart the FTP server.
Managing Symantec FileStore network settingsConfiguring the FTP server
198
Specifies whether to allow FTP access for users (non-anonymous).
By checking this checkbox (default), you allow user logins to succeed. By not checking thischeckbox, you specify that anonymous logins are allowed, but user logins are not allowed.
For the changes to take effect, you need to restart the FTP server.
User logon
Specifies whether or not to allow non-secure (plain-text) logins into the FTP server.
By checking this checkbox (default), you allow non-secure (plain-text) logins to succeed. By notchecking this checkbox, you allow non-secure (plain-text) logins to fail.
For the changes to take effect, you need to restart the FTP server.
Allow plain textuser login
Specifies whether or not users can delete files on the FTP server.
By checking this checkbox , you allow users to delete files. By not checking this checkbox(default), you do not allow users to delete files.
This setting applies to users. It does not apply to anonymous logins. Anonymous logins arenever allowed to delete files on the FTP server.
For the changes to take effect, you need to restart the FTP server.
Allow user todelete files
Specifies the location of the home 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.
Home directorypath
Specifies the type of users that are allowed to log in to the FTP server.
Select NIS_LDAP to allow users with accounts configured on NIS or LDAP servers to log intothe FTP server.
Select Local (default) to allow users created with FTP User > Add to log into the FTP server.
For the changes to take effect, you need to restart the FTP server.
Security type
Specifies the amount of time in minutes after which an idle connection is disconnected.
Valid values range from 1 to 600 (the default value is 15 minutes).
For the changes to take effect, you need to restart the FTP server.
Idle time out(Required)
3 Click Save.
199Managing Symantec FileStore network settingsConfiguring the FTP server
Adding FTP local user accountsTo add a local user account
1 In the FileStore Management Console, click Settings > General > FTP.
2 In the FTP User section, click Add.
The Add FTP User dialog box displays.
3 Enter the appropriate options:
Enter the account name of the user whose account you want toadd.
FTP User Name(Required)
Enter a password for the user.Password(Required)
4 Enter the Password again for verification purposes.
5 Click OK.
Changing a password for an FTP local userTo change a password for an FTP local user
1 In the FileStore Management Console, click Settings > General > FTP.
2 In the FTPUser section, select the user whose password you want to change.
3 Click Change Password.
The Change FTP User Password dialog box displays.
4 Enter a new password for the user.
5 Enter the Password again for verification purposes.
6 Click OK.
Setting user attributes for an FTP local userTo set user attributes for an FTP local user
1 In the FileStore Management Console, click Settings > General > FTP.
2 In the FTP User section, select a user whose attributes you want to set.
3 Click Set User Attribute.
The Set User Attribute dialog box displays.
Managing Symantec FileStore network settingsAdding FTP local user accounts
200
4 Enter the appropriate options:
Enter a home directory for the local user account. The homedirectory you specify for a local user account is created relativeto the home directory path that is configured for the FTP server.
Changes to this value are applicable for any new connections.Configuring a new home directory location does not migrate anyexisting data in a local user's current home directory to the newhome directory.
Home Directory
Specifies the maximum upload bandwidth (in MB/second) for alocal user account on the FTP server. By default, there is no limiton the upload bandwidth for local users.
Upload Bandwidth
Specifies the maximum download bandwidth (in MB/second) fora local user account on the FTP server. By default, there is nolimit on the download bandwidth for local users.
DownloadBandwidth
Specifies the maximum number of files and directories for a localuser account. By default, there is no limit to the number of filesand directories a local user can have.
Maximum Files
Specifies the maximum amount of disk space available in a localuser home directory. By default, there is no limit to the amountof disk space local users can have for their home directories.
Maximum Usage
Specifies the maximum number of simultaneous connections alocal user can have to the FTP server. By default there is no limitto the number of connections a local user can have.
MaximumConnections perClient
5 Click OK.
Deleting an FTP local user accountTo delete a local user account
1 In the FileStore Management Console, click Settings > General > FTP.
2 In the FTPUser section, select the user account you want to delete, and clickDelete.
3 In the DeleteFTPUser dialog, verify that you want to delete the selected useraccount, and click OK.
4 In the Result dialog, click OK.
201Managing Symantec FileStore network settingsDeleting an FTP local user account
About DNSThe Domain Name System (DNS) service translates between numeric IP addressesand their associated host names.
The DNS operation lets you view or change an FileStore cluster's DNS settings.You can configure an FileStore cluster's DNS lookup service to use up to threeDNS servers. You must enable the FileStore cluster's DNS name service beforeyou specify the DNS servers it is to use for lookups.
Configuring DNS settingsWhen DNS is enabled, the FileStore cluster's DNS service uses the datacenter 'sDNS server(s) to determine the IP addresses of network entities such as SNMP,NTP, LDAP, and NIS servers with which the cluster must communicate.
To configure DNS settings
1 In the FileStore Management Console, click Settings > General > Network.
2 In the DNS Settings table, enter the appropriate options.
The domain name is displayed by default.
The DNS domain name is entered at the time of installation.
Domain Name
Specifies the IP addresses of DNS name servers that are used bythe FileStore DNS lookup service.
Enter the IP addresses of the name servers. The order of the IPaddresses is the order in which the name servers are to be used.Multiple IP addresses can be entered with a space as a separatorfor the IP addresses.
Server Name
3 Click Save.
Enabling DNS servicesTo enable DNS services
1 In the FileStore Management Console, click Settings > General > Network.
2 In the DNS Settings section, click the Enable button.
3 In the EnableDNSService dialog, verify that you want to enable DNS services,and click OK.
Managing Symantec FileStore network settingsAbout DNS
202
Disabling DNS servicesTo disable DNS services
1 In the FileStore Management Console, click Settings > General > Network.
2 In the DNS Settings section, click the Disable button.
3 In the Disable DNS Service dialog, verify that you want to disable DNSservices, and click OK.
Configuring NIS settingsFileStore supports Network Information Service (NIS), implemented in an NISserver, as an authentication authority. You can use NIS to authenticate computers.
You must set the NIS domain name and NIS server name before you can enableNIS.
To configure NIS settings
1 In the FileStore Management Console, click Settings > General > Network.
2 In the NIS Settings table, enter the appropriate options.
Enter the NIS domain name that is set on the FileStore cluster.Domain Name(Required)
Enter the NIS server name that is set on the FileStore cluster.Server Name(Required)
3 Click Save.
Enabling NIS servicesTo enable NIS services
1 In the FileStore Management Console, click Settings > General > Network.
2 In the NIS Settings section, click the Enable button.
3 In the Enable NIS Service dialog, verify that you want to enable NIS clientson the FileStore cluster, and click OK.
203Managing Symantec FileStore network settingsDisabling DNS services
Disabling NIS servicesTo disable NIS services
1 In the FileStore Management Console, click Settings > General > Network.
2 In the NIS Settings section, click the Disable button.
3 In the DisableNISService dialog, verify that you want to disable NIS services,and click OK.
Viewing information about your networkconfiguration and statistics
To view information about your network configuration and statistics
◆ In the FileStore Management Console, click Settings > General > Network.
From the Network page, you can view the following network configurationand statistics:
DNS Settings table
Enable or disable DNS.
Click Enable to enable DNS lookups.
Click Disable to disable DNS lookups.
You must enable DNS before changing Domain Name or ServerName.
DNS status is
The domain name is displayed by default.
The DNS domain name is entered at the time of installation.
Domain Name
Specifies the IP addresses of DNS name servers that are used bythe FileStore DNS lookup service.
Enter the IP addresses of the name servers. The order of the IPaddresses is the order in which the name servers are to be used.Multiple IP addresses can be entered with a space as a separatorfor the IP addresses.
Server Name
NIS Settings table
Enable or disable NIS clients on the FileStore cluster.
Click Enable if you want to enable NIS.
Click Disable if you want to disable NIS.
NIS status is
Managing Symantec FileStore network settingsDisabling NIS services
204
Enter the NIS domain name that is set on the FileStore cluster.Domain Name(Required)
Enter the NIS server name that is set on the FileStore cluster.Server Name(Required)
Network Bond table
Name of the bond configuration.Bond Name
Specifies how the bonded Ethernet interfaces divide the traffic.Bond Mode
Displays the name of the Ethernet interfaces for the NIC bond.Devices
IP Address table
Displays the IP address for the cluster.IP Address
Displays the netmask for the IP address.Netmask
Displays the name of the Ethernet interfaces for the IP address.Device
Displays the node names that are associated with the interface.Node
Displays the type of the IP address: Physical or Virtual.Type
Displays the status of the IP address.
Valid values include:
■ ONLINE
■ OFFLINE
■ FAULTED
A virtual IP can have a FAULTED status if it is already beingused. It can also have a FAULTED status if the correspondingdevice is not working on all nodes in the cluster (for example,a disconnected cable).
Status
Valid values include:
■ Unused - IP address is unused
■ Con (console IP) - IP address is the console IP address
■ NetBackup - IP address that is used for NetBackup
■ Replication - IP address that is used for replication
Tag
IP Link table
205Managing Symantec FileStore network settingsViewing information about your network configuration and statistics
Displays the node name that is associated with the Ethernetinterface.
Node
Displays the name of the Ethernet interface on the node.Device
Displays the status of the interface.
Valid values include:
■ ONLINE
■ OFFLINE
■ FAULTED
Status
Displays the Maximum Transmission Unit (MTU) value that isconfigured for the interface.
MaximumTransmission Unit(MTU)
Displays the Ethernet connection status.
Valid values are:
■ Yes - Ethernet is connected.
■ No - Ethernet is not connected.
Ethernet isconnected
Displays the device speed (in MB per second) for the interface.Device speed(Mb/s)
Displays the hardware (MAC) address that is associated with theinterface.
Hardware Address
IP Route table
Displays the node name that is associated with the route.Node Name
Displays the destination network (or destination host) addressfor which the route is defined.
Destination IP
Displays the Gateway IP address (if any) associated with the route.Gateway IP
Displays the netmask that is associated with the route.Netmask
Displays the flag that is associated with the route.
The flags are as follows:
■ U - Route is up
■ H - Target is a host
■ G - Use gateway
Flag
Displays the largest amount of data, specified in bytes, that theroute can support in a single, unfragmented piece.
MaximumSegment Size
Managing Symantec FileStore network settingsViewing information about your network configuration and statistics
206
Displays the length of the largest single uninterrupted burst ofdata allowed to be transmitted in the upstream path.
Max Data in aSingle Burst
Displays the round-trip time that is associated with the route.Round Trip Time
Specifies which Ethernet interface on the node is associated withthe route.
Device
Adding a bond Ethernet interfaceBonds associate each set of two or more Ethernet interfaces with one IP address.This association improves network performance on each FileStore cluster nodeby increasing the potential bandwidth available on an IP address beyond the limitsof a single Ethernet interface, and by providing redundancy for higher availability.For example, you can bond two 1-gigabit Ethernet interfaces together to provideup to 2 gigabits per second of throughput to a single IP address. Moreover, if oneof the interfaces fails, communication continues using the single Ethernetinterface.
To add a bond Ethernet interface
1 In the FileStore Management Console, click Settings > General > Network.
2 Click the Add Bond button.
3 In the Add Network Bond dialog, enter the appropriate options.
From the drop-down menu, select the mode for distributing trafficamong the bonded interfaces.
Select Mode(Required)
Select the public Ethernet interface to bond.
You must select two public Ethernet interfaces for bonding.
Select NIC(Required)
4 Click OK.
5 In the Result dialog, click OK.
Removing a bond Ethernet interfaceTo remove a bond Ethernet interface
1 In the FileStore Management Console, click Settings > General > Network.
2 Select the bond name you want to remove, and click the RemoveBond button.
207Managing Symantec FileStore network settingsAdding a bond Ethernet interface
3 In the Remove Bond dialog, enter the appropriate options.
From the drop-down menu, select the mode for distributing trafficamong the bonded interfaces.
Select Mode(Required)
Remove the public Ethernet interface for bonding.Select NIC(Required)
4 Click OK.
5 In the Result dialog, click OK.
Adding an IP address to a clusterTo add an IP address to a cluster
1 In the FileStore Management Console, click Settings > General > Network.
2 Click the Add IP button.
3 In the Add IP dialog, enter the appropriate options.
Enter the IP address to be added to the cluster.
Note: Do not use physical IP addresses to access the FileStorecluster. In case of a node failure, physical IP addresses cannotmove between nodes.
IP Address
Enter the netmask for the IP address.Netmask
From the drop-down menu, select the type of IP address, eithera virtual or a physical IP address.
Type
From the drop-down menu, select the Ethernet interface for theIP address.
Device
4 Click OK.
5 In the Result dialog, click OK.
Deleting an IP address from a clusterTo delete an IP address from a cluster
1 In the FileStore Management Console, click Settings > General > Network.
2 Select the IP address you want to remove, and click the Delete IP button.
Managing Symantec FileStore network settingsAdding an IP address to a cluster
208
3 In the Delete IP dialog, click OK.
4 In the Result dialog, click OK.
Modifying an IP addressYou can change the status (Online, Offline) for an IP address by modifying the IPaddress.
To modify an IP address
1 In the FileStore Management Console, click Settings > General > Network.
2 Select the IP address you want to modify, and click the Modify IP button.
3 In the Modify IP dialog, enter the new IP address, and click OK.
4 In the Result dialog, click OK.
Modifying the status of an IP address to onlineTo modify the status of an IP address to online
1 In the FileStore Management Console, click Settings > General > Network.
2 Select the IP address you want to modify the status for, and click the OnlineIP button.
3 In the Online IP dialog, select the node name to online from the drop-downmenu, and click OK.
4 In the Result dialog, click OK.
Modifying the configuration of an Ethernet interfaceTo modify the configuration of an Ethernet Interface
1 In the FileStore Management Console, click Settings > General > Network.
2 Select the Ethernet interface (IP Link) you want to modify, and click the SetIP Link button.
3 In the Set IP Link dialog, enter the appropriate options.
From the drop-down menu, select which node of the cluster toconfigure.
Node Name
From the drop-down menu, select the Ethernet interface toconfigure.
Device
209Managing Symantec FileStore network settingsModifying an IP address
From the drop-down menu, enter one of the following operations:
■ Up - Brings the Ethernet interface online.
■ Down - Brings the Ethernet interface offline.
■ MTU - Specifies the Ethernet interface's MaximumTransmission Unit (MTU) to the value you enter in theOptional Argument field.
Operation
Used only for the MTU operation. Specifies the MTU of theEthernet interface.
Valid MTU values are any integer from 46-9216.
OptionalArgument
4 Click OK.
Adding a new IP route to a clusterTo add an IP route to a cluster
1 In the FileStore Management Console, click Settings > General > Network.
2 Click the Add IP Route button.
3 In the Add IP Route dialog, enter the appropriate options.
From the drop-down menu, select the node that has the routingtable for the route you are adding.
Node Name
Enter the destination IP address.Destination IP
Specify the netmask that is associated with the destination IPaddress.
Netmask
Specify the gateway IP address that is used by the route you areadding. To add a route that does not use an IP address, enter0.0.0.0.
Gateway IP
Specifies which Ethernet interface on the node where the routepath is added.
Valid options include:
■ pubeth0 - Public Ethernet interface 0
■ pubeth1- Public Ethernet interface 1
Device
4 Click OK.
Managing Symantec FileStore network settingsAdding a new IP route to a cluster
210
Deleting an IP route from a clusterTo delete an IP route from a cluster
1 In the FileStore Management Console, click Settings > General > Network.
2 Select the IP route you want to remove, and click the Delete IPRoute button.
3 In the Delete IP Route dialog, click OK.
About configuring LDAP settingsThe Lightweight Directory Access Protocol (LDAP) is the protocol used tocommunicate with LDAP servers. The LDAP servers are the entities that performthe service. In FileStore, the most common use of LDAP is for user authentication.
For sites that use an LDAP server for access or authentication, FileStore providesa simple LDAP client configuration interface.
Before you configure FileStore LDAP settings, obtain the following LDAPconfiguration information your system administrator:
■ IP address or host name of the LDAP server. You also need the port numberof the LDAP server.
■ Base (or root) distinguished name (DN), for example:
cn=employees,c=us
LDAP database searches start here.
■ Bind distinguished name (DN) and password, for example:
ou=engineering,c=us
This allows read access to portions of the LDAP database to search forinformation.
■ 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.
■ Base DN for Netgroups, for example:
211Managing Symantec FileStore network settingsDeleting an IP route from a cluster
ou=netgroups,dc=com
This allows access to the LDAP database, to search for Netgroups.
■ 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 SecureSockets Layer (SSL) protocol to communicate with the LDAP server.
■ Password hash algorithm, for example, md5, if a specific password encryptionmethod is used with your LDAP server.
Configuring LDAP server settings and enabling SSLTo configure LDAP server settings and enable SSL
1 In the FileStore Management Console, click Settings > General > LDAP.
2 In the LDAP Settings panel, enter the appropriate LDAP options:
Click the Disable button to disable LDAP from querying the LDAPdirectory service.
Disable
Click the Enable button to enable LDAP to query the LDAPdirectory service.
Enable
Enter the LDAP server host name or IP address.Server
Enter the LDAP base DN.Base DN
Enter the LDAP groups base DN.Groups base DN
Enter the LDAP bind DN.Bind DN
If you are specifying an LDAP bind DN, you will be prompted fora password. You must use your LDAP server password.
Password
Select either clear, crypt, or md5 from the drop-down list.Entering a password sets the LDAP password hash algorithmthat is used when you set or change the LDAP user's password.
The password is encrypted with the configured hash algorithmbefore it is sent to the LDAP server and stored in the LDAPdirectory.
Password Hash
Managing Symantec FileStore network settingsConfiguring LDAP server settings and enabling SSL
212
3 Enter the appropriate SSL options:
Click the Disable button to disable SSL secure communicationfor LDAP.
Disable
Click the Enable button to enable Secure Sockets Layer (SSL)secure communication for LDAP access and authentication forFileStore.
Enable
Enter the LDAP server port number.
The default LDAP server port number is 389.
Port
Enter the value for the user base DN.User base DN
Enter the value for the Netgroups base DN.Netgroups base DN
Enter the LDAP root bind DN.Root bind DN
If specifying an LDAP root bind DN, you will be prompted tosupply a password. You must use your LDAP server password.
Password
4 Click Save or Cancel.
Enabling LDAPTo enable LDAP
1 In the FileStore Management Console, click Settings > General > LDAP.
2 In the LDAP section of the LDAP Settings panel, click the Enable button.
3 In the LDAP Enable dialog, click OK.
LDAP is enabled to query the LDAP directory service.
Disabling LDAPTo disable LDAP
1 In the FileStore Management Console, click Settings > General > LDAP.
2 In the LDAP section of the LDAP Settings panel, click the Disable button.
3 In the LDAP Disable dialog, click OK.
LDAP is disabled and cannot query the LDAP directory service.
213Managing Symantec FileStore network settingsEnabling LDAP
Enabling SSL for LDAP accessTo enable SSL for LDAP access
1 In the FileStore Management Console, click Settings > General > LDAP.
2 In the SSL section of the LDAP Settings panel, click the Enable button.
3 In the SSL Enable dialog, click OK.
Secure Sockets Layer (SSL) secure communication for LDAP access andauthentication is enabled.
Disabling SSL for LDAP accessTo disable SSL for LDAP access
1 In the FileStore Management Console, click Settings > General > LDAP.
2 In the SSL section of the LDAP Settings panel, click the Disable button.
3 In the SSL Disable dialog, click OK.
Secure Sockets Layer (SSL) secure communication for LDAP access andauthentication is disabled.
Restoring LDAP default settingsTo restore default LDAP settings
1 In the FileStore Management Console, click Settings > General > LDAP.
2 In the LDAP Settings panel, click the Restore Value button.
3 In the Restore LDAP Settings dialog box, click the checkbox for the LDAPsettings you want to restore to default values.
For example, click the Server and Port checkboxes to restore the defaultLDAP server and port settings. The other settings remain unchanged.
4 Click OK.
About NSSName Service Switch (NSS) is an FileStore cluster service that provides a singleconfiguration location to identify the services (such as NIS or LDAP) for networkinformation such as hosts, groups, or passwords.
Managing Symantec FileStore network settingsEnabling SSL for LDAP access
214
For example, host information may be on an NIS server. Group information maybe in an LDAP database.
The NSS configuration specifies which network services the FileStore clustershould use to authenticate hosts, users, groups, and netgroups. The configurationalso specifies the order in which multiple services should be queried.
Configuring an NSS lookup orderTo configure an NSS lookup order
1 In the FileStore Management Console, click Settings>General>NS-Switch.
2 In the NS-Switch Settings panel, select the appropriate options:
Select the radio button for the groups file.
The group file is set by default.
groups
Select the radio button for the hosts file.hosts
Select the radio button for the netgroups file.netgroups
Select the radio button for the password.password
Select the radio button for the shadow file.shadow
3 Click Save.
Viewing information about VLAN devicesThe virtual LAN (VLAN) feature lets you create VLAN devices on the FileStorenodes and administer them as any other VLAN device.
215Managing Symantec FileStore network settingsConfiguring an NSS lookup order
To view information about VLAN devices
◆ In the FileStore Management Console, click Settings > General > VLAN.
From the Virtual LAN table, you can view the following information forvirtual LAN devices:
Name of the VLAN device.Name
Specifies the VLAN device.
Valid values include: pubeth0 or pubeth1.
Device
Specifies the VLAN ID.
Valid values range from 1 to 4095.
ID
Adding a VLAN deviceTo add a VLAN device
1 In the FileStore Management Console, click Settings > General > VLAN.
2 Click Add Device.
3 In the Add Device dialog, enter the appropriate options:
Select either pubeth0 or pubeth1 from the drop-down list.Select DeviceName
Enter the VLAN ID.
Valid values range from 1 to 4095.
Device Id
4 Click OK.
5 In the Result dialog, click OK.
Removing a VLAN deviceTo remove a VLAN device
1 In the FileStore Management Console, click Settings > General > VLAN.
2 Select a device to remove, and click Remove Device.
Managing Symantec FileStore network settingsAdding a VLAN device
216
3 In the Remove Device dialog, verify that you want to remove the selectedVLAN device, and click OK.
4 In the Result dialog, click OK.
Viewing the clock, setting the NTP server and globalcache
System settings enable you to view the system clock, enable an NTP server, andmodify the global inode cache size.
The system clock shows the current date and time on all nodes in the cluster.
To enable an NTP server
1 In the FileStore Management Console, click Settings > General > System.
2 In the NTP Settings panel, enter the appropriate options:
Check the EnableNTP checkbox to enable the NTP server on theFileStore cluster.
Uncheck the EnableNTP checkbox to disable the NTP server onthe FileStore cluster.
Enable NTP
Enter the name of the NTP server or the IP address for the NTPserver.
Server Name
3 Click Save.
To modify the global inode cache size
1 In the FileStore Management Console, click Settings > General > System.
2 In the Options panel for Global Node Cache, change the global inode cachesize.
If your system is caching a large number of metadata transactions, or if thereis significant virtual memory manager usage, modifying some of the variablesmay improve performance. The range for the inode cache size is from 10000to 2097151.
3 Click Save.
After updating the global inode cache size, you need to log out and then logback into the FileStore Management Console.
217Managing Symantec FileStore network settingsViewing the clock, setting the NTP server and global cache
Setting the system clockTo set the system clock
1 In the FileStore Management Console, click Settings > General > System.
2 In the Clock Settings panel, you can view the system date and time.
3 To set the clock, click Set Clock.
The Set System Clock dialog box displays.
4 Enter the appropriate options:
In the Hour, Minute, and Second drop-down menus, select thetime in 24-hour format.
Set Time
Click Calendar to choose a date.Set Day
5 Click OK.
Setting the time zoneTo set the time zone
1 In the FileStore Management Console, click Settings > General > System.
2 To set the time zone, click Set Time Zone.
The Set Time Zone dialog box displays.
3 Enter the appropriate options:
In the Select Region drop-down menu, select the region for thesystem.
Select Region
In the Select Time Zone drop-down menu, select the time zonefor the system. The time zones that are included on this menuare based on the region you selected.
Select Time Zone
To set the time zone based on Greenwich Mean Time (GMT), choose GMTfrom the Select Region menu, then choose a GMT value (for exampleGMT+10), from the Select Time Zone menu.
4 Click OK.
Managing Symantec FileStore network settingsSetting the system clock
218
Modifying the number of NFS daemonsTo modify the number of NFS daemons for a selected node
1 In the FileStore Management Console, click Settings > General > System.
2 In the NFS Daemons panel, select a node you want to modify, and click theModify button.
3 In the ModifyNFSDaemons dialog for the NumberofDaemons field, modifythe number of daemons for the selected node.
The range for the number of daemons you can modify is 16 to 1892.
4 Click OK.
5 In the Result dialog, click OK.
To modify the number of NFS daemons for all of the nodes in the cluster
1 In the FileStore Management Console, click Settings > General > System.
2 In the NFS Daemons panel, click the Modify All button.
3 In the ModifyNFSDaemons dialog for the NumberofDaemons field, modifythe number of daemons.
The range for the number of daemons you can modify is 16 to 1892.
4 Click OK.
5 In the Result dialog, click OK.
Creating or modifying DMP I/O policiesTo create or modify DMP I/O policies
1 In the FileStore Management Console, click Settings > General > System.
2 In the DMP-I/O Policies panel, click the Modify button.
3 In the Modify DMP-I/O Policy dialog, enter the appropriate options:
From the drop-down menu, select one of the following three typesof classes:
■ arrayname
■ arraytype
■ enclosure
Depending on the type you select, you can then enter an arrayname, an array type, or an enclosure name.
Type
219Managing Symantec FileStore network settingsModifying the number of NFS daemons
Name of the array. Two physical array boxes of the same makehave the same array name.
Array Name
A multipathing type of array. From the drop-down menu, selectone 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
Array Type
Name of the enclosure to distinguish between arrays having thesame array name.
Enclosure Name
Managing Symantec FileStore network settingsCreating or modifying DMP I/O policies
220
From the drop-down menu, select one of the following options:
adaptive - In storage area network (SAN) environments, thisoption determines the paths that have the least delays, andschedules the I/O on the paths that are expected to carry a higherload. Priorities are assigned to the paths in proportion to thedelay.
adaptiveminq - The I/O is scheduled according to the length ofthe I/O queue on each path. The path with the shortest queue isassigned the highest priority.
balanced - Takes into consideration the track cache whenbalancing the I/O across paths.
minimumq - Uses a minimum I/O queue policy. The I/O is senton the paths that have the minimum number of I/O requests inthe queue. This policy is suitable for low-end disks or JBODswhere a significant track cache does not exist. This is the defaultpolicy for Active/Active (A/A) arrays.
priority - Assigns the path with the highest load carrying capacityas the priority path. This policy is useful when the paths in a SANhave unequal performances, and you want to enforce loadbalancing manually.
round-robin - Sets a simple round-robin policy for the I/O. Thisis the default policy for Active/Passive (A/P) and AsynchronousActive/Active (A/A-A) arrays.
single active - The I/O is channeled through the single activepath.
I/O Policy
The policy options you enter apply to all nodes in the cluster.
4 Click OK.
5 In the Result dialog, click OK.
Modifying DMP tune attributesTo modify DMP tune attributes
1 In the FileStore Management Console, click Settings > General > System.
2 In the DMP Tune Attributes panel, click the Modify button.
You do not need to select a node before modifying the DMP tune attributes;changes you make apply to all nodes in a cluster.
221Managing Symantec FileStore network settingsModifying DMP tune attributes
3 In the Modify DMP Tune dialog, enter the appropriate options:
Time (in seconds) when an intermittently failing path needs tobe monitored before DMP marks the path as healthy, and DMPattempts to schedule I/O requests for that path.
If you enter a value of 0, DMP is prevented from detectingintermittently failing paths.
dmp path age
Time (in seconds) for which a path must stay healthy. If a path'sstate changes back from enabled to disabled within this timeperiod, DMP marks the path as intermittently failing, and DMPdoes not re-enable the path for I/O until the DMP path ageseconds have elapsed.
If you enter a value of 0, DMP is prevented from detectingintermittently failing paths.
dmp health time
4 Click OK.
5 In the Result dialog, click OK.
Modifying global tune fstab attributesTo modify global tune fstab attributes
1 In the FileStore Management Console, click Settings > General > System.
2 In the Global Tune FSTAB Attributes panel, click the Modify button.
You not need to select a node before modifying the tune FSTAB attributes,changes you make apply to all nodes in a cluster.
3 In the Modify Tune FSTAB dialog box for the Write Throttle field, enter avalue for the write throttle.
The write throttle is useful in situations where a computer system combinesa large amount of memory and slow storage devices. In this configuration,sync operations (such as fsync) may take so long to complete that the systemappears to hang. This behavior occurs because the file system is creatingdirty buffers (in-memory updates) faster than they can be asynchronouslyflushed to disk.
Lowering the value of the write throttle can help prevent system slowdownby limiting the number of buffers per file that a file system generates beforeflushing the buffers to disk.
If you assign a write throttle value of 0, there is no limit on the number ofdirty buffers per file.
Managing Symantec FileStore network settingsModifying global tune fstab attributes
222
4 Click OK.
5 In the Results dialog, click OK.
About importing or exporting configuration settingsYou can import the configuration settings saved in a local file or saved to a remotemachine specified by a URL.
See “Importing configuration settings” on page 223.
You can export the configuration settings saved in a local file or saved to a remotemachine specified by a URL.
See “Exporting configuration settings” on page 224.
Importing configuration settingsImporting configuration settings overwrites all of your existing configurationsettings except for cluster name.
To import configuration settings
1 In the FileStore Management Console, click Settings > General >Configuration.
2 Click the Import button.
3 In the Import Configuration dialog, enter the appropriate options:
Click either the Local or the Remote radio button.
If you select the Remote type, you are required to supply apassword.
Select Type
Enter the name of the saved configuration file.
Specifies the URL of the export file (supported protocols are FTPand SCP).
Filename/URL(Required)
223Managing Symantec FileStore network settingsAbout importing or exporting configuration settings
Select an option from the drop-down menu.
Available values include:
■ All
■ All (except Cluster Specific)
■ CIFS specific
■ NFS specific
■ Admin
■ Network
■ Report
■ System
■ FTP
■ Backup
■ Replication
■ Storage Schedules
■ AntiVirus
Config Type
4 Click OK.
Exporting configuration settingsTo export configuration settings
1 In the FileStore Management Console, click Settings > General >Configuration.
2 Click the Export button.
3 In the Export Configuration dialog, enter the appropriate options:
Click either the Local or the Remote radio button.
If you select the Remote type, you are required to supply apassword.
Select Type
Enter the name of the saved configuration file.
Specifies the URL of the export file (supported protocols are FTPand SCP).
File Name/URL(Required)
4 Click OK.
About backup servicesFileStore provides two options for backup services:
Managing Symantec FileStore network settingsAbout backup services
224
■ FileStore includes built-in client software for Symantec's NetBackup dataprotection suite. If NetBackup is the enterprise's data protection suite of choice,the file systems hosted by FileStore can be backed up to a NetBackup mediaserver.See “About NetBackup” on page 227.
■ FileStore also supports the Network Data Management Protocol (NDMP) fordata backup and recovery. NDMP is an open protocol for transferring databetween the data server and the tape server under the control of a client.See “About the Network Data Management Protocol” on page 229.
Viewing backup servicesThe Settings > Backup > NBU page enables you to view the status of NetBackupand NDMP backup services.
To view backup services
◆ In the FileStore Management Console, click Settings > Backup > NBU.
In the BackupStatusonNodes table, you can view the following informationabout backup services:
The node running the backup service. This node can be an NDMPserver or a NetBackup client.
Node Name
Displays the status of the backup service.
Valid values include:
■ ONLINE
■ OFFLINE
Status
In addition to viewing backup status, you can use the Settings > Backup > NBUpage to configure NetBackup settings.
See “Configuring backup using NetBackup” on page 228.
225Managing Symantec FileStore network settingsViewing backup services
Starting backup servicesTo start backup services
1 In the FileStore Management Console, click Settings > Backup > NBU.
2 In the Backup Status on Nodes table, click the Start Server button.
To start the service on a specific node, select the node first, then click theStart Server button.
3 In the StartServer dialog, confirm that you want to start the backup service,and click OK.
The services that handle backup and restore are started and the virtual IPaddress is brought online.
Stopping backup servicesTo stop backup services
1 In the FileStore Management Console, click Settings > Backup > NBU.
2 In the Backup Status on Nodes table, click the Stop Server button.
3 In the Stop Server dialog, confirm that you want to stop the backup service,and click OK.
The services that handle backup and restore are stopped and the associatedvirtual IP address is taken offline.
Viewing details about backup servicesTo view details about backup services
1 In the FileStore Management Console, click Settings > Backup > NBU.
2 In the Backup Status on Nodes table, click the Status Detail button.
In the Backup Status dialog, you can view details about backup services:
Displays the status of the virtual IP address.
Valid values include:
■ up - The virtual IP is up.
■ down - The virtual IP is down.
■ not configured - The virtual IP is not configured.
Virtual IP state
Managing Symantec FileStore network settingsStarting backup services
226
Displays the status of the NDMP server.
Valid values include:
■ running - The NDMP server is running.
■ stopped - The NDMP server is stopped.
■ working - An NDMP backup or restore job is in progress.
NDMP Server state
Displays the status of the NetBackup client on the node.
Valid values include:
■ running - The NetBackup client is running.
■ stopped - The NetBackup client is stopped.
■ working - A NetBackup backup or restore job is in progress.
NetBackup Clientstate
Displays the status of any ongoing backup or restore jobs.Backup/restorejobs
About NetBackupFileStore includes built-in client software for Symantec's NetBackup dataprotection suite. If NetBackup is the enterprise's data protection suite of choice,the 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 addressesof the NetBackup master and media servers. Backups are scheduled from thoseservers, using NetBackup's administrative console.
Consolidating storage reduces the administrative overhead of backing up andrestoring many separate file systems. With a 2255 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. Allcritical file data can be backed up and restored through the NetBackup clientsoftware that is included with FileStore (separately licensed NetBackup masterand media servers running on separate computers are required), or through anybackup management software that supports NAS systems as data sources.
227Managing Symantec FileStore network settingsAbout NetBackup
Configuring backup using NetBackupTo configure backup using NetBackup
1 In the FileStore Management Console, click Settings > Backup > NBU.
2 In the NetBackup Settings panel, enter the appropriate options:
Enter the host name of the NetBackup master server.
Note: Make sure that the host name for the master server can be resolved through DNS, andthe host name IP address can be resolved back to its host name through the DNS reverse lookupprocess.
FileStore only includes the NetBackup client code on the FileStore nodes. If you want to useFileStore NetBackup to back up your FileStore file systems, you must add an external NetBackupmaster 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 masterserver before 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.
Master ServerName
Enter the host name of the NetBackup Enterprise Media Manager (EMM) server.
You need to add an external EMM server, which can be the same as the NetBackup masterserver, to work with FileStore.
Note: If you want to use NetBackup to backup FileStore file systems, you must add an externalNetBackup EMM server.
EMM Server Name
Enter the virtual IP address to be used with the NetBackup and the NDMP data server installationon the FileStore cluster.
Note: Make sure that the virtual IP address can be resolved back to the host name that isconfigured when entering the Virtual Name field.
Virtual IP
Enter the host name that is used by the NetBackup installation on the FileStore cluster.
Note:Make sure that the host name can be resolved through DNS, and the host name IP addresscan be resolved back to the host name through the DNS reverse lookup process. Also, makesure that the host name resolves to an IP address that is configured when entering the VirtualIP field.
Virtual Name
3 Click Save or Cancel.
Managing Symantec FileStore network settingsConfiguring backup using NetBackup
228
Adding a media serverYou can add an external NetBackup media server, if the NetBackup media serveris not co-located with the NetBackup master server.
Make sure that the host name for the media server can be resolved through DNS,and the host name IP address can be resolved back to its host name through theDNS reverse lookup process.
To add a media server
1 In the FileStore Management Console, click Settings > Backup > NBU.
2 In the Media Server table, enter the server name in the Server Name field,and click the Add button.
After adding the server name, the server name displays in the table.
Deleting a media serverTo delete a media server
1 In the FileStore Management Console, click Settings > Backup > NBU.
2 In the Media Server table, select the server name in the table that you wantto delete, and click the Delete button.
3 In the Delete media server name dialog, verify that you want to delete theselected media server, and click OK.
4 In the Result dialog, click OK.
About the Network Data Management ProtocolThe Network Data Management Protocol (NDMP) is an open protocol fortransferring data between the data server and the tape server under the controlof a client. NDMP is used for data backup and recovery.
NDMP is based on a client-server architecture. The Data Management Applicationis the client and the data and tape services are the servers. The Data ManagementApplication initiates the backup session. A single control connection from theData Management Application to each of the data and tape services and a dataconnection between the tape and the data services creates a backup session.
NDMP provides the following services:
■ Defines a mechanism and protocol for controlling backup, recovery, and othertransfers of data between the data server and the tape server
229Managing Symantec FileStore network settingsAdding a media server
■ Separates the network attached Data Management Application, Data Servers,and Tape Servers participating in archival, recovery, or data migrationoperations
■ Provides low-level control of tape devices and SCSI media changers
Table 10-3 NDMP terminology
DefinitionTerminology
The host computer system that executes the NDMP server application.Data is backed up from the NDMP host to either a local tape drive orto a backup device on a remote NDMP host.
host
The virtual state computer on the NDMP host that is controlled usingthe NDMP protocol. This term is used independently ofimplementation.
There are three types of NDMP services:
■ Data service
■ Tape service
■ SCSI service
service
An instance of one or more distinct NDMP services that is controlledby a single NDMP control connection. Thus a Data/Tape/SCSI Serveris an NDMP server providing data, tape, and SCSI services.
server
The configuration of one client and two NDMP services to perform adata management operation such as a backup or a recovery.
session
The application that controls the NDMP server. Backup and restoreare initiated by the NDMP client. In NDMP version 4, the client is theData Management Application.
client
An application that controls the NDMP session. In NDMP, there is amaster-slave relationship. The Data Management Application is thesession master; the NDMP services are the slaves. In NDMP versions1, 2, and 3, the term NDMP client is used instead of the DataManagement Application.
Data ManagementApplication
The Settings>Backup>NDMP operations configure the default policies that areused during the NDMP backup and restore sessions.
About NDMP configurationsFileStore currently supports the three-way NDMP backup. The data and tapeservices reside on different nodes on a network. The Data Management Application
Managing Symantec FileStore network settingsAbout the Network Data Management Protocol
230
has two control connections, one to each of the data and tape services. There isalso 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 NDMPhost. Backup data is sent over the local network. The tape drives must be inNDMP-type storage units.
Figure 10-1 Illustration of three-way NDMP FileStore backup
Tape Library
ControlFlow
NFS clients
DataFlow
NBU MediaServer withNDMP
Primary Storage Array
NBU / TSM / EMCLegato withNDMP
ControlFlow
FileStore – Cluster– NDMP Server
The NDMP commands configure the default policies that are used during theNDMP backup or restore sessions. The Data Management Application (client)initiating the connection for NDMP backup and restore operations to the NDMPdata/tape server can override these default policies by setting the same policyname as the environment variable and using any suitable value of that environmentvariable.
Table 10-4 lists the NDMP settings you can configure.
The FileStore NDMP server supports MD5 and text authentication. The DataManagement Application that initiates the connection to the server uses masterfor the user name and for the password for the NDMP backup session
231Managing Symantec FileStore network settingsAbout the Network Data Management Protocol
authentication. The password can be changed using the Settings>UserAccountsReset Password operation.
Table 10-4 NDMP settings
DescriptionSetting
Enter the virtual IP address of the NDMP server.Virtual IP
Checks if the file or directory already exists. If it does, it is renamedwith the suffix.#ndmp_old and a new file or directory is created.
Overwrite Policy -Rename Old (Default)
Checks if the file or directory to be restored already exists. If itdoes, the command responds with an error message. A log messageis returned to the Data Management Application. Refer to theData Management Application documentation for the location ofthe NDMP log messages. The file or directory is not overwritten.
Overwrite Policy - NoOverwrite
If the file or directory already exists, it is overwritten. It isrecommended that while doing a restore from incrementalbackups, click the Overwrite Always radio button.
Overwrite Policy -Overwrite Always
File Change Log. FCL can be used to directly get the list of modifiedfiles 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 changescan be recorded in the FCL. In that case, click the Last ModifiedTime radio button.
Backup Method - FileChange Log (FCL)(Default)
Time of last modification. By clicking the Last Modified Timebutton, the time of the last backup can be stored reliably in thefile system, and the time can be used to find all of the modifiedfiles since the last backup. The location where the time of lastbackup is stored is in /etc/ndmp.dumpdates.
Backup Method - LastModified Time
Establishes the continuation of the backup and restore sessioneven if an error condition occurs because a file or directory cannotbe backed up or restored.
Failure resilient
Configures the Dynamic Storage Tiering (DST) restore policy.
During the restore session, the DST policy only applies to the filesystem, but it does not become effective until you run it throughthe storage tier policy operations.
DST restore
Configures the NDMP recursive restore policy to restore thecontents of a directory each time you restore.
Recursive restore
Contains the file system backup information. Thedumpdates fileis located in /etc/ndmp.dumpdates.
Update dumpdates
Managing Symantec FileStore network settingsAbout the Network Data Management Protocol
232
Table 10-4 NDMP settings (continued)
DescriptionSetting
Determines whether or not you want the file history of the backedup data that is sent to the Data Management Application (DMA).
Send history of backedup data to DMA
Lets you bring back previous versions of the files for review or tobe used. A snapshot is a virtual copy of a set of files and directoriestaken at a particular point in time. The NDMP use snapshot policyenables the backup of a point-in-time image of a set of files anddirectories instead of a continuous changing set of files anddirectories.
Take snapshot beforebackup
Configures the masquerade as a third-party policy.
The FileStore NDMP server masquerades as a third-partycompatible device for certain NDMP backup applications.
Configure themasquerade as thirdparty
Configuring NDMP policiesTo configure NDMP
1 In the FileStore Management Console, click Settings > Backup > NDMP.
2 In the NDMP settings, update the appropriate fields.
See Table 10-4 on page 232.
3 Click Save or Cancel.
About SNMP notificationsSimple Network Management Protocol (SNMP) is a network protocol to simplifythe management of remote network-attached devices such as servers and routers.SNMP is an open standard system management interface. Information from theManagement Information Base (MIB) can also be exported.
SNMP messages enable the reporting of a serious condition to a managementstation. The management station is then responsible for initiating furtherinteractions with the managed node to determine the nature and extent of theproblem.
In FileStore, options include specifying the SNMP messages for the event reporting,selecting the types of events to report, and selecting the severity of the occurrencesto report. The SNMP server must be specified during configuration.
233Managing Symantec FileStore network settingsAbout SNMP notifications
Configuring report settingsEvent notifications link applications that generate messages (the events) toapplications that monitor the associated conditions and respond when triggeredby the events.
To configure email settings
1 In the FileStore Management Console, click Settings > Reports.
2 In the Email Settings and Configuration portion of the Reports panel, clickthe checkbox in front of Email Settings and Configuration, and enter theappropriate options.
Enter the external email server you want to use to display details.Email Server
Enter the email user you want to use to display details.Username
Enter the password for the external email server.Password
For deleting the email server, refer to the section listed below.
See “Deleting an email server” on page 236.
To configure event report settings
1 In the FileStore Management Console, click Settings > Reports.
2 In the EventReportSettings portion of the Reports panel, click the checkboxin front of Event Report Settings, and enter the appropriate options.
Enter the time interval (in seconds) for the number of duplicateevents sent for notifications.
The default is 60.
Duplicatefrequency
Enter the number of duplicate events to ignore duringnotifications.
The default is 5.
Duplicate Number
For exporting event notifications, refer to the section listed below.
See “Exporting event notifications” on page 236.
To configure SNMP settings
1 In the FileStore Management Console, click Settings > Reports.
2 In the SNMP Settings panel, click the checkbox in front of SNMP Settings,and enter the appropriate options.
Managing Symantec FileStore network settingsConfiguring report settings
234
Enter the host name or IP address of the SNMP ManagementServer.
SNMPManagementServer
Select the filter for SNMP notifications from the drop-downmenu.
Valid values include:
■ Network - if an alert is for a networking event, then selectingthe Network filter triggers that alert. If you select theNetwork filter only, and an alert is for a storage-related event,the Network alert will not be sent.
■ Storage - is for storage-related events, for example, filesystems, snapshots, disks, and pools
■ All
The default filter is All.
Filter
Each group can have its own severity definition. You can definethe lowest level of a severity that triggers all other severitieshigher than it.
The default severity is Info.
Valid values include:
■ Emerg - indicates that the system is unusable
■ Alert - indicates that immediate action is required
■ Crit - indicates a critical condition
■ Err - indicates an error condition
■ Warning - indicates a warning condition
■ Notice - indicates a normal but significant condition
■ Info - indicates an informational message
Severity
For deleting SNMP settings, refer to the section listed below.
See “Deleting an SNMP management server” on page 237.
235Managing Symantec FileStore network settingsConfiguring report settings
To enable system log settings
1 In the FileStore Management Console, click Settings > Reports.
2 In the System Log Settings panel, click the checkbox in front of System LogSettings, and enter the appropriate options.
Enter the host name or IP address of the external syslog server.Syslog serveraddress
Enter the filter value for the syslog server.Syslog filter
Enter the severity for the syslog server.Syslog Severity
For deleting syslog settings, refer to the section listed below.
See “Deleting a syslog server address” on page 238.
3 Click Save.
Deleting an email server
Note: Deleting an email server causes the user name and password settingsassociated with that server to be deleted also.
To delete an email server
1 In the FileStore Management Console, click Settings > Reports.
2 In the EmailSettingsandConfiguration panel, click the DeleteEmailServerbutton.
3 In the Delete Email Server dialog, click OK to confirm the deletion.
4 In the Result dialog, click OK.
Exporting event notificationsTo export event notifications
1 In the FileStore Management Console, click Settings > Reports.
2 In the Event Report Settings panel, after having configured Event ReportSettings, click the Export Event button.
See “Configuring report settings” on page 234.
Managing Symantec FileStore network settingsDeleting an email server
236
3 In the Export Event dialog, update the appropriate options:
Select either the Event or Audit radio button.Select Type
Select either ftp or scp from the drop-down menu, and enter theURL where the events will be exported.
Enter URL(Required)
Enter the password for either the ftp or the scp server forexporting the events.
Password(Required)
4 Click OK.
5 In the Result dialog, click OK.
Adding an SNMP management serverTo add an SNMP management server
1 In the FileStore Management Console, click Settings > Reports.
2 In the SNMP Settings panel, after having configured SNMP Settings, entera valid server name in the SNMP Management Server field.
Enter a valid host name or IP address. For example:
mgmtserv1.company.com
See “Configuring report settings” on page 234.
3 Click the Add button.
After the page refreshes, a new server name displays in the list box.
You can enter multiple server names using this procedure.
Deleting an SNMP management serverTo delete an SNMP management server
1 In the FileStore Management Console, click Settings > Reports.
2 In the SNMP Settings panel, after having configured SNMP Settings, selectone server name in the SNMP Management Server list box to delete.
See “Configuring report settings” on page 234.
3 Click the Delete button.
237Managing Symantec FileStore network settingsAdding an SNMP management server
Adding a syslog server addressTo add a syslog server address
1 In the FileStore Management Console, click Settings > Reports.
2 In the System Log Settings panel, after having configured System LogSettings, enter a valid server name in the Syslog Server Address list box.
See “Configuring report settings” on page 234.
3 Click the Add button.
Deleting a syslog server addressTo delete a syslog server address
1 In the FileStore Management Console, click Settings > Reports.
2 In the System Log Settings panel, after having configured System LogSettings, select one server name in the Syslog Server Address list box todelete.
See “Configuring report settings” on page 234.
3 Click the Delete button.
Adding an email groupWhen adding an email group, an email group can only contain the followingcharacters: alpha characters, numbers, hyphens, or underscores.
To add an email group
1 In the FileStore Management Console, click Settings > Reports.
2 Click the Add Group button.
3 In the Add Email Group dialog, enter the name of the email group.
Email groups enable you to collect multiple email addresses into one entity.The email group is used as the destination of the FileStore email notification.
Note: After you add an email group, you can use the Add Severity/Filterbutton to configure email notification properties for the group. By default,the filter is set to All and the severity is set to Info.
Managing Symantec FileStore network settingsAdding a syslog server address
238
4 Click OK.
5 In the Result dialog, click OK.
Removing an email groupTo remove an email group
1 In the FileStore Management Console, click Settings > Reports.
2 Select an email group to remove by placing a check next to it.
3 Click the Remove Group button.
4 In the RemoveEmailGroup dialog, verify that you want to delete the selectedemail group, and click OK.
5 In the Result dialog, click OK.
Adding a severity/filterTo add a severity/filter
1 In the FileStore Management Console, click Settings > Reports.
2 Select an email group to add a severity/filter to by placing a check next to it.
3 Click the Add Severity/Filter button.
4 In the AddSeverity/Filter dialog, select the severity/filter from the drop-downmenu.
Select the filter from the drop-down menu to add to the emailgroup.
Available values include:
■ Storage
■ Network
■ All (default)
Select Filter
239Managing Symantec FileStore network settingsRemoving an email group
Select the severity from the drop-down menu to add to the emailgroup.
Available values include:
■ Alert
■ Info (default)
■ Critical
■ Warning
■ Error
■ Emerg
■ Notice
■ Debug
Select Severity
5 Click OK.
6 In the Result dialog, click OK.
Removing a severity/filterTo remove a severity/filter
1 In the FileStore Management Console, click Settings > Reports.
2 Select an email group to remove a severity/filter from by placing a check nextto it.
3 Click the Remove Severity/Filter button.
4 In the Remove Severity/Filter dialog, select the severity/filter to removefrom the drop-down menu, and click OK.
5 In the Result dialog, click OK.
Adding an email to an email groupTo add an email to an email group
1 In the FileStore Management Console, click Settings > Reports.
2 Select an email group to add the email to by placing a check next to it.
3 Click the Add Email button.
Managing Symantec FileStore network settingsRemoving a severity/filter
240
4 In the Add Email to Group dialog, enter the email ID for the email that youwant to add to the email group, and click OK.
Email ID is a required field.
5 In the Result dialog, click OK.
Deleting an email from an email groupTo delete an email address from an email group
1 In the FileStore Management Console, click Settings > Reports.
2 Place a check next to the email group that contains the email address youwant to delete.
3 Click the Delete Email button.
4 In the Delete Email from Group dialog, choose the email address you wantto delete from the Email ID drop-down menu, and click OK.
5 In the Result dialog, click OK.
Viewing user accountsTo view user accounts
1 In the FileStore Management Console, click Settings > User Accounts.
2 From the User Accounts table, you can view the following information forexisting user accounts:
Name of the user.User Name
Role of the user, either: Master, System Administrator, or StorageAdministrator.
Role
Adding new user accountsTo add new user accounts
1 In the FileStore Management Console, click Settings > User Accounts.
2 Click the Add User button
3 In the Add User dialog, enter the user name for the new user.
User Name is a required field.
241Managing Symantec FileStore network settingsDeleting an email from an email group
4 In the Role drop-down, select either: Master, System Administrator, or StorageAdministrator as the role for the new user.
5 Click OK.
6 In the Result dialog, click OK.
Removing user accountsTo remove user accounts
1 In the FileStore Management Console, click Settings > User Accounts.
2 Select a user account you want to remove, and click the RemoveUser button.
3 In the RemoveUser dialog, verify that you want to remove the selected user.
4 Click OK.
5 In the Result dialog, click OK.
Resetting passwordsTo reset passwords
1 In the FileStore Management Console, click Settings > User Accounts.
2 Select a user account you want to reset a password for, and click the ResetPassword button.
3 In the Reset Password dialog, enter a new password in the New Passwordfield.
4 Click OK.
5 In the Result dialog, click OK.
Managing Symantec FileStore network settingsRemoving user accounts
242
Viewing upgrade settingsTo view upgrade settings
1 In the FileStore Management Console, click Settings > Upgrade.
2 From the Product Version table, you can view the following information:
Displays the current version of the product, either for thestandard or the enterprise version.
Current Version
Displays the FileStore installation date.Install Date
Displays the date that FileStore was released.Release Date
3 From the Major Upgrades table, you can view the following information:
Displays the date when FileStore was upgraded.Installation Date
Displays the patch version.Patch
Displays the date the major upgrade was released.Release Date
Displays the base version that the upgrade is based on.Base
Upgrading FileStoreTo upgrade to the latest version of FileStore
1 In the FileStore Management Console, click Settings > Upgrade.
2 For UpgradeProduct, click Upgrade to download the latest software patches.
3 In the Upgrade FileStore dialog, enter the appropriate fields:
Enter the URL from where you can download software patches.
For example:
scp://[email protected]/patches/nasgw1.0_patch1.tar.gz
Note: http, ftp, or scp protocols are supported.
URL
Enter the password for the scp or ftp protocols.Password
243Managing Symantec FileStore network settingsViewing upgrade settings
4 Click OK.
5 In the Result dialog, click OK.
Uninstalling FileStore up to the specified versionTo uninstall FileStore up to the specified version
1 In the FileStore Management Console, click Settings > Upgrade.
2 In the Uninstall Product Version table, click Uninstall.
3 In the Uninstall FileStore dialog, enter the version number that you want touninstall up to.
4 Click OK.
5 In the Result dialog, click OK.
Syncing nodesTo sync nodes
1 In the FileStore Management Console, click Settings > Upgrade.
2 For Sync Node, click Sync.
3 In the SyncNode dialog, select the node from the drop-down menu that needsto be synchronized to bring it up to the currently installed software versionof the rest of the nodes in the cluster.
4 Click OK.
5 In the Result dialog, click OK.
Configuring FileStore ReplicationYou need to set up communication between your source and destination clusters.
Make sure that you already created an online file system on the FileStore sourcecluster and an online file system on the FileStore destination cluster.
FileStore Replication makes use of encrypted keys to authenticate the source anddestination cluster. This section provides a walk-through for the creation andimport/export of these encrypted keys for both the source and destination cluster.
In this release of FileStore Replication, it is possible to provide a third-partydestination to act as an intermediary between nodes for the transfer of theencrypted keys.
Managing Symantec FileStore network settingsUninstalling FileStore up to the specified version
244
Note: Without the correct authentication of source/destination encryption keys,FileStore Replication will not function correctly.
For more information on configuring FileStore Replication using the FileStoreManagement Console, see the link below.
See “About configuring FileStore Replication using the FileStore ManagementConsole” on page 142.
For more information on FileStore Replication, see the Symantec FileStoreReplication Guide.
Binding a virtual IP address on the source and destination clustersThe FileStore Replication service requires extra virtual IP addresses at the samenetwork range as for the console virtual IP addresses that are used for the cluster.Reserve at least one virtual IP address for the FileStore Replication service oneach cluster.
To bind a virtual IP address for the source and destination clusters
1 In the FileStore Management Console for both the source and destinationclusters, click Settings > Replication.
2 In the Replication window, click Bind.
3 In the BindVIP dialog, for the Virtual IP field, enter a virtual IP address, andclick OK.
The Virtual IP field is a required field.
4 In the Result dialog, click OK.
Unbinding a virtual IP address for the source and destination clustersTo unbind a virtual IP for the source and destination clusters
1 In the FileStore Management Console for both the source and destinationclusters, click Settings > Replication.
2 In the Replication window, click Unbind.
3 In the Unbind VIP dialog, verify that you want to unbind the virtual IPaddress, and click OK.
4 In the Result dialog, click OK.
245Managing Symantec FileStore network settingsConfiguring FileStore Replication
Viewing replication status detailsTo view replication status details
1 In the FileStore Management Console for both the source and destinationclusters, click Settings > Replication.
2 In the Replication window, click Status Details.
3 In the Replication Status Details dialog, you can view details about thereplication.
Device that the replication service is currently using.Replication Device
Cluster node on which the replication service is currentlyrunning.
Online on Node
Version number that is associated with the replication protocol.The replication protocol version is used to track changes in sourceand destination interactions and to ensure replicationcompatibility across FileStore installations.
ReplicationProtocol Version
Confirms the IP address is up and running. For example,10.10.10.10.
OFFLINE - indicates the address is not available.
VIP Status
Status of the replication daemon.
Available values are:
■ ONLINE - indicates that the replication daemon is running.
■ OFFLINE - indicates that the replication daemon is notrunning.
Daemon Status
Status of the database on the console node.
Available values are:
■ ONLINE - indicates that the database is active.
■ OFFLINE - indicates that the database is not available.
Console Node DBStatus
Status of the database on the replication node.
Available values are:
■ ONLINE - indicates that the database is active.
■ OFFLINE - indicates that the database is not available.
Replication NodeDB Status
4 When you have finished viewing replication status details, click OK.
Managing Symantec FileStore network settingsConfiguring FileStore Replication
246
Starting the replication service for the source and destination clustersTo start the replication service for the source and destination clusters
1 In the FileStore Management Console for both the source and destinationclusters, click Settings > Replication.
2 In the Replication Service Status area, click the Start button.
3 In the StartService dialog, verify that you want to start the replication service,and click OK.
4 In the Result dialog, click OK.
Stopping the replication service for source and destination clustersTo stop the replication service for source and destination clusters
1 In the FileStore Management Console for both the source and destinationclusters, click Settings > Replication.
2 In the Replication Service Status area, click the Stop button.
3 In the StopService dialog, verify that you want to stop the replication service,and click OK.
Exporting keys on the source clusterThe FileStore Replication service needs to identify the source and destinationclusters when performing replication operations. The source cluster is the clusterwhere the file or directory is copied from, and the destination cluster is the clusterwhere the file or directory is copied to. The source cluster needs to export keysthat will be imported by the destination cluster.
To configure export keys on the source cluster
1 In the FileStore Management Console for the source cluster, click Settings> Replication.
2 In the Export Keys area, enter the appropriate information:
Enter the URL where to save the key file, for example:
scp://username@hostname:/path/to/save/keyfile
URL (Required)
Enter the password for logging into the hostname where thekeyfile is saved.
Password
3 Click the Export button to export the URL.
247Managing Symantec FileStore network settingsConfiguring FileStore Replication
Importing keys on the destination clusterTo configure import for the destination cluster
1 In the FileStore Management Console for the destination cluster, clickSettings > Replication.
2 In the Import Keys area, enter the appropriate information:
Enter the URL where the key file is saved, for example:
scp://username@hostname:/path/to/save/keyfile
URL (Required)
Enter the password for logging into the hostname where thekeyfile is saved.
Password
3 Click the Import button to import the URL.
Exporting keys on the destination clusterTo configure export keys on the destination cluster
1 In the FileStore Management Console for the destination cluster, clickSettings > Replication.
2 In the Export Keys area, enter the appropriate information:
Enter the URL where the key file is saved, for example:
scp://username@hostname:/path/to/save/keyfile
URL (Required)
Enter the password for logging into the hostname where thekeyfile is saved.
Password
3 Click the Export button to export the URL.
Managing Symantec FileStore network settingsConfiguring FileStore Replication
248
Importing keys on the source clusterTo configure import keys on the source cluster
1 In the FileStore Management Console for the source cluster, click Settings> Replication.
2 In the Import Keys area, enter the appropriate information:
Enter the URL where to save the key file, for example:
scp://username@hostname:/path/to/save/keyfile
URL (Required)
Enter the password for logging into the hostname where thekeyfile is saved.
Password
3 Click the Import button to import the URL.
Creating a link between the source cluster and the destination clusterTo create a link between the source and the destination clusters
1 In the FileStore Management Console for the destination cluster, click Settings> Replication.
2 In the Remote Links table, enable the checkbox on the row for the recentlyadded remote cluster, and click the Authenticate button.
3 In the Authenticate dialog, for the Link Name field, enter the link name.
Link Name is a required field.
4 Click OK.
5 In the Result dialog, click OK.
Deleting a link between the source cluster and the destination clusterTo delete a link between the source cluster and the destination cluster
1 In the FileStore Management Console, click Settings > Replication.
2 In the Remote Links table, select the link name you want to delete the linkfor by clicking the box next to it.
3 Click the Deauthenticate button.
4 In the Deauthenticate dialog, verify that you want to delete the link for thespecified cluster IP address, and click OK.
5 In the Result dialog, click OK.
249Managing Symantec FileStore network settingsConfiguring FileStore Replication
Deleting import/export keysTo delete import/export keys
1 In the FileStore Management Console, click Settings > Replication.
2 In the Remote Links table, select the link name you want to delete the keyfor by clicking the box next to it.
3 Click the Delete Key button.
4 In the Delete Key dialog, verify that you want to delete the key associatedwith the link name, and click OK.
5 In the Result dialog, click OK.
Checking the link between the source and destination clustersTo check the link between the source and destination clusters
1 In the FileStore Management Console for the destination cluster, click Settings> Replication.
2 In the Remote Links table, enable the checkbox on the row for the recentlycreated link, and click the Check Link button.
3 Click the Check Link button.
4 In the Check Link dialog, verify that you want to check the status for theselected link name, and click OK.
5 In the Result dialog, click OK.
Adding a loopback linkFor local replication initialization, you need to create a link using the IP addressof the local console cluster. This link acts as a local link and is used for localsynchronization. For more information on local replication initialization, see theSymantec FileStore Replication Guide.
To add a loopback link
1 In the FileStore Management Console for the source cluster, click Settings >Replication.
2 In the Remote Links table, click the Add Loopback Link button.
The Add Loopback Link dialog displays.
3 In the Link Name field, enter a name for the loopback link, and click OK.
4 In the Result dialog, click OK.
Managing Symantec FileStore network settingsConfiguring FileStore Replication
250
Configuring the Symantec AntiVirus for FileStoreservice
You must configure the Symantec AntiVirus for FileStore service using Settings> AntiVirus before being able to use the AntiVirus operations.
For additional information on configuring Symantec AntiVirus for FileStore usingthe FileStore Management Console, refer to the section listed below.
See “About configuring Symantec AntiVirus for FileStore using the FileStoreManagement Console” on page 165.
The Start Service operation starts the Symantec AntiVirus for FileStore serviceon all of the nodes in a cluster. By default, the Symantec AntiVirus for FileStoreservice is OFFLINE. If the Symantec AntiVirus for FileStore service is alreadystarted, Symantec AntiVirus for FileStore clears the faults (if any), and then ittries to start the Symantec AntiVirus for FileStore service.
The Stop Service operation stops the Symantec AntiVirus for FileStore serviceon all of the nodes in a cluster.
See “About Symantec AntiVirus for FileStore” on page 164.
Starting the Symantec AntiVirus for FileStore service for all the nodesTo start the Symantec AntiVirus for FileStore service for all the nodes
1 In the FileStore Management Console, click Settings > AntiVirus.
2 In the AntiVirus Service status on nodes table, click Start Service.
3 In the Start Service dialog, verify that you want to start the SymantecAntiVirus for FileStore service for all the nodes, and click OK.
4 In the Result dialog, click OK.
Stopping the Symantec AntiVirus for FileStore service for all the nodesYou receive an error if you try to stop an already stopped (OFFLINE) SymantecAntiVirus for FileStore service.
You can stop the Symantec AntiVirus for FileStore service at any time.
To stop the Symantec AntiVirus for FileStore service for all the nodes
1 In the FileStore Management Console, click Settings > AntiVirus.
2 In the AntiVirus Service status on nodes table, click Stop Service.
251Managing Symantec FileStore network settingsConfiguring the Symantec AntiVirus for FileStore service
3 In the Stop Service dialog, verify that you want to stop the SymantecAntiVirus for FileStore service for all the nodes, and click OK.
4 In the Result dialog, click OK.
Excluding file extensions from Symantec AntiVirus for FileStore scansYou can remove given file extensions from Symantec AntiVirus for FileStorescans. Once the file extension is added to the exclude extension list, SymantecAntiVirus for FileStore will not scan files having the specified file extension. Bydefault, Symantec AntiVirus for FileStore scans all the files.
File extensions are case-sensitive.
To exclude file extensions from Symantec AntiVirus for FileStore scans
1 In the FileStore Management Console, click Settings > AntiVirus.
2 In the File Extensions table, click the Add button.
3 In the Add exclude file extension dialog, for File extension, enter txt, DOC,or com. Multiple file extensions are separated by commas.
4 Click OK.
5 In the Result dialog, click OK.
Deleting file extensions from Symantec AntiVirus for FileStore scansYou can delete file extensions from the Symantec AntiVirus for FileStoreconfiguration file. After the file extensions are deleted from the configurationfile, they are scanned by Symantec AntiVirus for FileStore.
To delete file extensions from Symantec AntiVirus for FileStore scans
1 In the FileStore Management Console, click Settings > AntiVirus.
2 In the File Extensions table, click the Delete button.
3 In the Deleteexclude fileextension dialog, verify that you want to delete thespecified file extension, and click OK.
4 In the Result dialog, click OK.
Setting the Symantec AntiVirus for FileStore action policySymantec AntiVirus for FileStore lets you set a primary and secondary actionpolicy for handling virus-infected files. By default, Clean is the primary action,and Quarantine is the secondary action.
The following are Symantec AntiVirus for FileStore action policies:
Managing Symantec FileStore network settingsConfiguring the Symantec AntiVirus for FileStore service
252
■ Delete - deletes the virus-infected file if a virus is found.
■ Quarantine - quarantines the virus-infected file if a virus is found. Quarantinedfiles are stored on local storage.
■ Clean - attempts to clean the virus from the file if a virus is found.
■ Leave - leaves the virus-infected file as is. Symantec AntiVirus for FileStoredoes not take any action if a virus is found.
For example, if Symantec AntiVirus for FileStore detects a virus in a file, SymantecAntiVirus for FileStore first tries to clean the virus from the infected file (theprimary action). If the clean action fails, Symantec AntiVirus for FileStorequarantines the infected file (the secondary action).
Note: You can configure a single scan action by setting the same action for boththe primary and secondary scan.
To set the Symantec AntiVirus for FileStore action policy
1 In the FileStore Management Console, click Settings > AntiVirus.
2 In the Scan Actions table, click the Set button.
3 In the SetScanAction dialog, select the primary and secondary action policiesfrom the drop-down menus, and click OK.
4 In the Result dialog, click OK.
253Managing Symantec FileStore network settingsConfiguring the Symantec AntiVirus for FileStore service
Managing Symantec FileStore network settingsConfiguring the Symantec AntiVirus for FileStore service
254
CIFS See Common Internet File System.
Clustered Trivial
Database
A cluster implementation of the TDB (Trivial database) based on the Berkeleydatabase API.
Common Internet File
System
A network protocol that provides the foundation for Windows-based file sharingand other network utilities. FileStore supports Common Internet File Systemsharing.
console IP address A virtual IP address that is configured for administrative access to the FileStorecluster management console.
coordinator disks In FileStore, three or more LUNs designated to function as part of the I/O fencingmechanism. You cannot use coordinator disks to store user data.
CTDB See Clustered Trivial Database.
DAR See Data Archive and Retention.
data archive and
retention
Combined Enterprise Vault and FileStore feature that supports both write onceread many (WORM) and non-WORM archives. DAR-enabled file systems areprotected against accidental or deliberate file removal and tampering.
data connection The connection between the two NDMP servers that carry the data stream. Thedata connection in NDMP is either an NDMP interprocess communicationmechanism (for local operations) or a TCP/IP connection (for 3-way operations).
data management An application that controls the NDMP session. In NDMP there is a master-slaverelationship. The data management application is the session master; the NDMPservices are the slaves. In NDMP versions 1, 2, and 3 the term "NDMP client" isused instead of data management application.
data master A node that contains the authoritative copy of a Trivial database (TDB) record.
data service An NDMP service that transfers data between primary storage and the dataconnection.
datastore A database that integrates data from multiple sources such as fibre channel, iSCSILUNs, or NAS volumes.
deduplication database A database that stores the mapping of the data fingerprints to one or more datasegments.
Glossary
deduplication
percentage
A measure of freed storage as a result of deduplication. It is another way ofrepresenting the deduplication ratio. For example, if deduplicating 1 TB frees up800 GB, the deduplication percentage is 80%.
deduplication ratio The ratio of logical to physical storage. In other words, a deduplication ratio of5:1 denotes that 200 GB of allocated storage actually accounts for 1 TB of data.
DM See data master.
DST See Dynamic Storage Tiering.
fingerprint block size The data size on which a fingerprint is calculated for detecting duplicates. Thesmaller the granularities, the better the match detection. It cannot be less thanthe file system block size.
guest operating system An operating system installed on a virtual machine.
mirrored file system A file system that is constructed and managed by a technique for automaticallymaintaining one or more copies of the file system, using separate underlyingstorage for each copy. If a storage failure occurs, then access is maintained throughthe remaining accessible mirrors.
NDMP Network data management protocol. NDMP is a widely used protocol throughwhich an NDMP-compliant backup application can control the backups and restoresfor an NDMP host. NetBackup requires the NetBackup for NDMP separately-pricedoption to support NDMP.
NDMP client An application that controls the NDMP session. See also data managementapplication.
NDMP host The host computer system that executes the NDMP server application. Data isbacked up from the NDMP host to either a local tape drive or to a backup deviceon a remote NDMP host.
NDMP server An instance of one or more distinct NDMP services controlled by a single NDMPcontrol connection. Thus a data/tape/SCSI server is an NDMP server providingdata, tape, or SCSI services.
NDMP service The state computer on the NDMP host accessed with the Internet protocol andcontrolled using the NDMP protocol. This term is used independently ofimplementation. The three types of NDMP services are: data service, tape service,and SCSI service.
NDMP session The configuration of one data management application and two NDMP servicesto perform a data management operation such as a backup or a recovery.
Netbackup Pure Disk The deduplication engine for NetBackup, enabling efficient, storage-optimizeddata protection for the data center, remote office, and virtual environments.NetBackup PureDisk is a software-based deduplication solution that is tightly
Glossary256
integrated with NetBackup. PureDisk is ideal for unique environments that requirehigh performance and scalability.
Network Attached
Storage
A file-level computer data storage that is connected to a network that providesdata access to network-capable clients.
Network File System A protocol that lets the user on a client computer access files over a network. Tothe client's applications the files appear as if they resided on one of the localdevices.
Network Time Protocol A protocol for synchronizing computer system clocks over packet-switched,variable-latency data networks.
NFS See Network File System.
NFS lock management A feature that lets a customer use the Network File System (NFS) advisory clientlocking feature in parallel with core Cluster File System (CFS) global lockmanagement.
no_root_squash An NFS sharing option. Does not map requests from the UID 0. This option is onby default.
NTP See Network Time Protocol.
oplocks A file-locking mechanism that is designed to improve performance by controllingthe caching of files on the client.
private interconnect An internal IP network that is used by the Scalable File Server to facilitatecommunications between the Scalable File Server server nodes.
recovery master A node that contains fcntl-locks on distributed file systems and initiates therecovery process.
RM See recovery master.
round-robin DNS A technique in which a DNS server, not a dedicated computer, performs the loadbalancing.
Samba An open-source implementation of the SMB file sharing protocol. It provides fileand print services to SMB/CIFS clients.
share A specification of a file system or proper subset of a file system, which supportsshared access to a file system through an NFS or CIFS server. The specificationdefines the folder or directory that represents the file system along with accesscharacteristics and limitations.
shared extent An extent shared by multiple files. A shared extent is freed only when there areno more references to it in any file.
soft limit A file system quota for inode and block consumption that can be established forindividual users or groups. If a user exceeds the soft limit, there is a grace period,
257Glossary
during which the quota can be exceeded. After the grace period has expired, nomore inodes or data blocks can be allocated.
snapshot A point-in-time image or replica of a file system that looks identical to the filesystem from which the snapshot was taken.
storage pool A logical construct that contains one or more LUNs from which file systems canbe created.
Symantec NetBackup A Symantec software product that backs up, archives, and restores files, directories,or raw partitions that reside on a client system.
syslog A standard for forwarding log messages in an IP network. The term refers to boththe syslog protocol and the application sending the syslog messages.
tape service An NDMP service that transfers data between secondary storage and the dataconnection and allows the data management application to manipulate and accessthe secondary storage.
vCenter plug-in One or more components extending collective capabilities of the vSphere Clientand the vCenter Server.
Virtual Machine Disk One or more files underlying the physical image of a virtual machine.
VMware vCenter Server A management server from VMware allowing management of ESX servers andVMware VDI.
VMware vSphere Client A Windows-based GUI for accessing vCenter Server capabilities.
World Wide Name A 64-bit identifier that is used in Fibre Channel networks to uniquely identifyeach element in the network (nodes and ports).
WWN See World Wide Name.
Glossary258
Aaborting
FTP server session 75replication job on the source cluster 151
aboutbackup services 224creating file systems 78FileStore file-level replication 140maintaining file systems 78Management Console 30More button 84NDMP configurations 230NFS shares 48selecting a filter 43shares 47snapshot operations 110
accessingcluster details 134details for a CIFS share 57disk details 126file system details 105FileStore product documentation 25NFS server details 52
addinga tier to a file system 94an IP address to a cluster 208an IP route to a cluster 210bond Ethernet interface 207CIFS home directory group quota 72CIFS home directory user quota 69CIFS local group 194CIFS local user 192CIFS share 57CIFS user to a group 193disk to a storage pool 121, 124email group 238email to an email group 240FTP local user 200LiveUpdate server 170loopback link 250mirror to a tiered file system 96
adding (continued)mirrors to a file system 99new node to a cluster 132new user accounts 241NFS share 49proxy URL for LiveUpdate server 174replication unit entry 156severity or filter 239SNMP management server 237syslog server address 238VLAN device 216
advanced filter settingsusing 45
alertsalerts panel using 43monitoring 41
associated sharesmonitoring 36
attachingstorage pools 123
autofixinga service 135
BBack button
using to resume an operation without losingdata 32
backup servicesabout 224starting 226stopping 226viewing 225
backup status detailsviewing 226
bindingvirtual IP addresses for source and destination
clusters 245bond Ethernet interface
adding 207removing 207
Index
Cchanging
CIFS user password 194FTP local user password 200
checkinglink between source and destination clusters 250
checking and repairingconsistency of file systems 101
CIFSabout configuring for FileStore 187adding a CIFS home directory group quota 72adding a CIFS home directory user quota 69changing a CIFS home directory quota 74changing user password 194configuring for standalone mode 188disabling a CIFS group quota 68disabling CIFS home directory user and group
quotas 67disabling CIFS home directory user quota 67enabling a CIFS group quota 68enabling CIFS home directory user and group
quotas 67enabling CIFS home directory user quota 66managing CIFS home directories 63mapping to a user name 192modifying CIFS home directory group quota 72modifying default CIFS quota value 69modifying home directory user quota 70setting CIFS home directory group quota for all
users 73setting CIFS home directory quota for all
users 71setting the default CIFS quota value 68setting up CIFS home directory 65
CIFS home directoryviewing information 63
CIFS local groupadding 194deleting 194
CIFS local useradding 192deleting 193
CIFS serverconfiguring 189starting 188stopping 188viewing status information about 189
CIFS shareaccessing details for 57
CIFS share (continued)adding 57deleting 62managing 55modifying 60viewing 55
CIFS share optionsabout 92
CIFS useradding to a group 193
clusteraccessing details for 134adding a new node 132deleting a node from 135displaying the current load for 137installing software on a node 132managing 131rebooting a node 135rebooting all the nodes in a cluster 136shutting down a node 136shutting down all the nodes in a cluster 136viewing information about 132
cluster nodesobtaining NFS status information for 186
configuration settingsexporting 223–224importing 223
configuringCIFS for FileStore 187CIFS for standalone mode 188CIFS server 189DNS settings 202export keys on the destination cluster 248export keys on the source cluster 247FTP server 197import keys on the destination cluster 248import keys on the source cluster 249NDMP policies 233NetBackup 228NIS settings 203replication 244replication using the FileStore Management
Console 142replication using the replication GUI wizard 143report settings 234storage pools about 118Symantec AntiVirus for FileStore service 251Symantec AntiVirus for FileStore using the
FileStore Management Console 165
Index260
coordinator diskdestroying 130replacing 130
core strengthsFileStore 21
creatingfile systems 79file systems about 78I/O fencing operation 128link between source cluster and destination
cluster 249replication job on the source cluster 146replication schedule 159replication units on destination cluster 155replication units on source cluster 154shared file systems 109snapshots 111storage pools 118storage pools by selecting disks 124tier schedule 97
customizing tabular displays 46
Ddeleting
an IP route from a cluster 211CIFS local group 194CIFS local user 193CIFS share 62current LiveUpdate server schedule 174email from an email group 241email server 236export keys 250FTP local user 201import keys 250link between the source cluster and the
destination cluster 249LiveUpdate server 171NFS share 55node from a cluster 135proxy URL for LiveUpdate server 175quarantined files 175replication schedule 162SNMP management server 237Symantec AntiVirus for FileStore scan jobs 169syslog server address 238
description of FileStore Replication 140destroying
coordinator disk 130file system 87
destroying (continued)replication job on the source cluster 149replication unit 158snapshot 112storage pools 122
detachingstorage pools 123
disablingCIFS group quota 68CIFS home directory user and group quotas 67CIFS home directory user quota 67DNS settings 203I/O fencing 129NIS settings 204replication job on the source cluster 150Symantec AntiVirus for FileStore Auto Protect
for file systems 104Symantec AntiVirus for FileStore scan jobs 170
disksaccessing details about 126monitoring status 38viewing information about 125
displayingcurrent load for the cluster 137information about quarantined files 176
DMP I/O policiesmodifying 219
DMP tune attributesmodifying 221
DNS serviceabout 202
DNS settingsconfiguring 202disabling 203enabling 202
Eediting
snapshot quota 87email
adding to an email group 240deleting from an email group 241
email groupadding 238removing 239
email serverdeleting 236
enablingCIFS group quota 68
261Index
enabling (continued)CIFS home directory user and group quotas 67CIFS home directory user quota 66DNS settings 202I/O fencing 128NIS settings 203NTP server 217replication job on the source cluster 150Symantec AntiVirus for FileStore Auto Protect
for file systems 104Symantec AntiVirus for FileStore scan jobs 169
Enter Filter Text boxusing 45
Ethernet interfacemodifying the configuration 209
event notificationsexporting 236
export keysdeleting 250
exportingconfiguration settings 223–224event notifications 236
Ffast resync
removing 101setting up 100
file extensionsdeleting from Symantec AntiVirus for FileStore
scans 252excluding from Symantec AntiVirus for FileStore
scans 252file systems
accessing details for 105adding a mirror to a tiered file system 96adding a tier to 94adding mirrors to 99checking and repairing the consistency of 101creating 79creating shared 109destroying 87growing 89monitoring 36placing offline 88placing online 88relocating a directory of a tiered file system 96removing a mirror from a tiered file system 97removing mirrors from 100removing tier from 97
file systems (continued)running a tier policy 95setting alerts for 102setting for all file systems 102sharing 90shrinking 89unsetting file system alerts 103unsetting file system alerts for all file
systems 103viewing information about 82
FileStoreabout 17core strengths of 21key features 17product documentation 25uninstalling up to the specified version 244upgrading 243Web resources 25
FileStore Replicationadding a loopback link 250checking the link between the source and
destination clusters 250configuring export keys on the destination
cluster 248configuring export keys on the source
cluster 247configuring import keys on the destination
cluster 248configuring import keys on the source
cluster 249creating a link between the source and
destination clusters 249deleting the link between source and destination
clusters 249description of feature 140file-level about 140setting up between two clusters 141
filters for file systemsselecting 44
FTP local useradding 200deleting 201
FTP local user attributessetting 200
FTP local user passwordchanging 200
FTP serveraborting session 75about 74
Index262
FTP server (continued)configuring 197settings viewing information about 74starting 195stopping 195uploading log to a URL 75viewing status information for the FTP
server 195
Gglobal inode cache size
modifying 217global tune fstab attributes
modifying 222growing
file system 89GUI database
refreshing 30rescanning 31
Hhome directory
changing a CIFS home directory quota 74removing for all users 66users removing 66
home directory userssetting 65
II/O fencing
about 127creating 128disabling 129enabling 128viewing information about 129
import keysdeleting 250
importingconfiguration settings 223
installingsoftware on a node 132
IP addressadding to a cluster 208modifying 209modifying the status to online 209removing from a cluster 208
IP routeadding to a cluster 210
IP route (continued)deleting from a cluster 211
LLDAP
before configuring 211configuring server settings 212disabling 213enabling 213enabling or disabling 212restoring default settings 214
LiveUpdateinitiating manually 171viewing information about 172
LiveUpdate serveradding 170adding proxy URL 174creating schedule 172deleting 171deleting proxy URL 175deleting schedule 174modifying schedule 173
logging intoManagement Console 30
lookup orderconfiguring NSS 215
Mmaintaining
file systems about 78Management Console
about 30logging into 30monitoring Dashboard 34session timeout issues 32using 33
managingCIFS home directories 63CIFS shares 55cluster 131snapshots 114
manually updating LiveUpdate virus definitions 171mapping
CIFS user name 192removing CIFS user 192user names for CIFS/NIFS sharing 191
media serveradding 229
263Index
media server (continued)deleting 229
modifyingan IP address in a cluster 209CIFS home directory group quota 72CIFS home directory user quota 70CIFS share 60configuration of an Ethernet interface 209default CIFS quota value 69DMP I/O policies 219DMP tune attributes 221global inode cache size 217Global tune fstab attributes 222NFS share 53number of NFS daemons 219replication job on the source cluster 148replication schedule 161replication unit entry 156Symantec AntiVirus for FileStore scan jobs 168tier policy 98
monitoringalerts 41associated shares 36disk status 38file systems 36FileStore Management Console Dashboard 34pool consumption 37pool consumption summary 34service status 39share status 39status summary 35storage consumption summary 34system load 40
More buttonabout 84
movingdisk from one storage pool to another storage
pool 122
NNDMP
about 229about configurations 230configuring policies for 233
NetBackupabout 227adding a media server 229configuring 228deleting a media server 229
network configuration and statisticsviewing information about 204
NFSmodifying number of NFS daemons 219
NFS export optionsabout 90
NFS serveraccessing details about 52starting 185stopping 185viewing status information 186
NFS shareabout 48adding 49deleting 55modifying 53viewing 51
NFS status informationobtaining for nodes in the cluster 186
NIS settingsconfiguring 203disabling 204enabling 203
nodessyncing for upgrade 244
NSSabout 214configuring lookup order 215
NTP serverenabling 217
Oonline
making a service 134modifying status to 209
Ppasswords
resetting 242pausing
replication job on the source cluster 151placing
file system offline 88file system online 88
pool consumptionmonitoring 37monitoring summary 34
Index264
preservingsnapshot 112
proxy URL for LiveUpdate serveradding 174deleting 175
Qquarantined files
deleting 175displaying information about 176repairing 176restoring 176viewing information about 175
Rrebooting
all the nodes in a cluster 136single node in a cluster 135
refreshingGUI database 30
relocatingdirectory of a tiered file system 96
removingan IP address from a cluster 208bond Ethernet interface 207disk from a storage pool 122email group 239fast resync 101home directory for all users 66home directory users 66mapped CIFS user 192mirror from a tiered file system 97mirrors from a file system 100replication unit entry 157severity or filter 240tier from file system 97tier policy 99tier schedule 98user accounts 242VLAN device 216
renamingstorage pools 123
repairingquarantined files 176
replacingcoordinator disk 130
replicationabout 140
replication (continued)binding a virtual IP address for source and
destination clusters 245configuring 244configuring using the FileStore Management
Console 142configuring using the replication GUI
wizard 143unbinding a virtual IP address for source and
destination clusters 245viewing status details 246
replication jobaborting on the source cluster 151creating on the source cluster 146destroying on the source cluster 149disabling on the source cluster 150enabling on the source cluster 150modifying on the source cluster 148pausing on the source cluster 151resuming on the source cluster 151resynchronizing 152triggering on the source cluster 152viewing information about 147
replication schedulecreating 159deleting 162modifying 161operations about 159viewing information about 161
replication servicestarting for source and destination clusters 247stopping for source and destination clusters 247
replication unitcreating on destination cluster 155creating on source cluster 154destroying 158operations 153viewing information about 158
replication unit entryadding 156modifying 156removing 157
report settingsconfiguring 234
rescanningGUI database 31
resettingpasswords 242
265Index
restoringquarantined files 176snapshots 116
resumingoperation without losing data 32replication job on the source cluster 151
resynchronizingreplication job 152
runningscan bus to discover new disks 125tier policy 95
Sscan bus
running to discover new disks 125schedule
creating LiveUpdate server 172modifying LiveUpdate server 173
schedulingSymantec AntiVirus for FileStore scan jobs 167
screen resolutionviewing the FileStore Management Console 32
selectingabout filters 43filter for file systems 44
serviceautofixing a service 135making go online 134
service statusmonitoring 39
session timeoutabout 32
settingCIFS home directory group quota for all users 73CIFS home directory quota for all users 71default CIFS quota value 68file system 102file system alerts for all file systems 102FTP local user attributes 200home directory user 65prior to configuring LDAP 211Symantec AntiVirus for FileStore action
policy 252system clock 218time zone 218
setting upCIFS home directory 65fast resync 100FileStore Replication between two clusters 141
severity or filteradding 239removing 240
sharesabout 47monitoring status 39
sharinga file system 90
shrinkingfile system 89
shutting downall the nodes in a cluster 136node in a cluster 136
snapshot quotaediting 87
snapshotschanging status to offline 113changing status to online 113creating 111destroying 112managing 114operations about 110preserving 112restoring 116viewing 114
SNMP management serveradding 237deleting 237
SNMP notificationsabout 233
SSLdisabling 214enabling 214enabling or disabling 212
startingbackup services 226CIFS server 188FTP server 195NFS server 185replication service for source and destination
clusters 247Symantec AntiVirus for FileStore scans 105Symantec AntiVirus for FileStore service for all
the nodes 251status summary
monitoring 35stopping
backup services 226CIFS server 188
Index266
stopping (continued)FTP server 195NFS server 185replication service for source and destination
clusters 247Symantec AntiVirus for FileStore scan jobs 170Symantec AntiVirus for FileStore scans 105Symantec AntiVirus for FileStore service for all
the nodes 251storage consumption summary
monitoring 34storage pools
about 118accessing details about a particular storage
pool 119adding a disk to 121, 124attaching 123creating 118creating by selecting disks 124destroying 122detaching 123moving a disk from one storage pool to
another 122removing a disk from 122renaming a pool 123viewing information about 119
storage provisioning and managementabout 118
Symantec AntiVirus for FileStoreabout 164configuring using the FileStore Management
Console 165Symantec AntiVirus for FileStore action policy
setting 252Symantec AntiVirus for FileStore Auto Protect for
file systemsdisabling 104enabling 104
Symantec AntiVirus for FileStore scan jobsdeleting 169disabling 170enabling 169modifying 168scheduling 167stopping 170viewing information about 168
Symantec AntiVirus for FileStore scansdeleting file extensions from 252excluding file extensions from 252
Symantec AntiVirus for FileStore scans (continued)starting 105stopping 105
Symantec AntiVirus for FileStore serviceconfiguring 251starting for all the nodes 251stopping for all the nodes 251
syncingnodes for upgrade 244
syslogadding server address 238deleting server address 238
system clocksetting 218
system loadmonitoring 40
Ttabular displays
customizing 46tier policy
modifying 98removing 99
tier schedulecreating 97removing 98
time zonesetting 218
triggeringreplication job on the source cluster 152
Uunbinding
virtual IP address for source and destinationclusters 245
uninstallingFileStore up to the specified version 244
unsettingfile system alerts 103
upgrade settingsviewing 243
upgradingFileStore 243
uploadingFTP log to a URL 75
user accountsadding 241removing 242
267Index
user accounts (continued)viewing 241
user names for CIFS/NIFS sharingmapping 191
usingadvanced filter settings 45alerts panel 43Enter Filter Text box 45Management Console 33
Vviewing
backup services 225backup status details 226CIFS home directory information 63information about 158, 215information about a node in a cluster 132information about CIFS shares 55information about disks 125information about file systems 82information about FTP settings 74information about I/O fencing 129information about LiveUpdate 172information about NFS server status 186information about NFS shares 51information about quarantined files 175information about replication job on the source
cluster 147information about replication schedules 161information about storage pools 119information about Symantec AntiVirus for
FileStore scan jobs 168information about the FTP server 195screen resolutions for the FileStore Management
Console 32snapshots 114status information for the CIFS server 189storage pool details 119upgrade settings 243user accounts 241
virtual IP addressbinding for source and destination clusters 245unbinding for source and destination
clusters 245VLAN device
adding 216removing 216viewing information about 215
WWeb resources for FileStore 25
Index268
