Page 1 Administrator Guide GuardianOS v6.0 For GuardianOS-powered SnapServers and Expansion Arrays www.overlandstorage.com 10400272-001...
Page 3 COPYRIGHT Copyright © 2010, Overland Storage, Inc. All rights reserved. Information in this document is subject to change without notice and does not represent a commitment on the part of Overland Storage or any of its subsidiaries. The software described in this document is furnished under a license agreement.
Page 4 END USER LICENSE AGREEMENT (EULA) FOR USE OF OVERLAND STORAGE STORAGE SOLUTIONS AND RELATED INSTALLATION UTILITIES SNAP IP, ASSIST, AND SNAPSERVER MANAGER (“INSTALLATION UTILITIES”); THE SYSTEM SOFTWARE EMBEDDED IN THE SNAPSERVER STORAGE SOLUTION (“EMBEDDED SOFTWARE”); SOFTWARE MARKETED BY OVERLAND STORAGE OR THAT IS EMBEDDED IN OR OTHERWISE CONSTITUTES A PART OF OVERLAND STORAGE COMPUTER HARDWARE PRODUCT(S) (SOMETIMES REFERRED TO COLLECTIVELY HEREIN, TOGETHER WITH THE INSTALLATION UTILITIES AND THE EMBEDDED SOFTWARE, AS THE “LICENSED SOFTWARE”), EXCEPT WHERE EXPRESSLY PROVIDED...
Page 5 for backup or archival purposes, you may not copy any documentation pertaining to the Licensed Software. You agree that your use and possession of the Licensed Software is permitted only in accordance with the terms and conditions of this Agreement. Ownership of Restricted Software.
Page 6 COMPUTER ASSOCIATES INTERNATIONAL, INC. ("CA") END USER LIMITED LICENSE AGREEMENT (THE "AGREEMENT") CAREFULLY READ THE FOLLOWING TERMS AND CONDITIONS REGARDING YOUR USE OF ETRUST ANTIVIRUS, INCLUDING ITS CODE AND DOCUMENTATION (THE "PROGRAM") BEFORE USING THE PROGRAM. CA PROVIDES YOU WITH ONE COPY OF THE PROGRAM AND LICENSES THE PROGRAM TO YOU PURSUANT TO THE TERMS OF THIS AGREEMENT.
Page 7: Table Of Contents
Preface ... xiii Chapter 1 Administrative Overview ...1 GuardianOS Specifications ... 2 What’s New in GuardianOS ... 6 SnapServer Manager... 12 Connecting to the Server for the First Time ... 14 Using the Initial Setup Wizard ... 16 Determining Capacity ... 17 Scheduling Data Protection Tasks...
Page 8 Apple Networking Configuration ...34 FTP/FTPS Access...36 HTTP/HTTPS Access ...37 DHCP Server ...39 Print Server ...39 Chapter 3 User & Group Management ... 43 Default User and Group Settings ...44 UID and GID Assignments ...44 Local Users and Groups ...45 NIS Domain ...47 Chapter 4 Storage Configuration and Expansion ...
Page 9 Chapter 6 Share and File Access ...95 Configuring Share and Folder Security Overview... 96 Components and Options... 99 SnapTrees and Security Models ID Mapping ... 102 Shares ... 103 Configuring Share Access ... 105 Creating Home Directories ... 106 Windows ACLs ... 107 Security Guides ...
Page 10 Chapter 9 CA eTrust Antivirus Software ... 125 Antivirus Dependencies ...126 Launching the CA eTrust Antivirus GUI ...127 The Local Scanner View...127 Scan Job Configuration and Scheduling ...128 Signature Updates ...131 Alert Options...135 The Move Directory...136 Log View...137 Chapter 10 Unicode ... 139 What is Unicode? ...139 Converting to Unicode...139 Unicode and Protocol Interaction...141...
Page 11 Appendix C Troubleshooting SnapServers ...181 The Meaning of LED Indicators ... 182 System Reset Options ... 203 Networking Issues ... 205 Miscellaneous Issues ... 208 Phone Home Support ... 210 Appendix D GuardianOS Ports ...213 Glossary ...217 Index...229 SnapServer Administrator Guide...
Page 12 SnapServer Administrator Guide...
Page 13: Preface
Audience and Purpose This guide is intended for system and network administrators charged with installing and maintaining SnapServers on their network. We assume the administrator is familiar with the basic concepts and tasks of multiplatform network administration. This guide provides information on the installation, configuration, security, and maintenance of SnapServers.
Page 14: Typographical Conventions
Typographical Conventions Convention Italic Arial Bold Arial Courier Italic Courier Bold Right-Click SnapServer Administrator Guide Usage • Emphasis • The introduction of new terms • File names • Settings you select or enter in the Administration Tool Navigational paths, command buttons, and navigational links.
Page 15: Finding More Information
Finding More Information Product documentation related to GuardianOS SnapServers and expansion arrays are listed below. The current versions of all these documents are always available from http://www.snapserver.com/support. Source and Location Quick Start Guide Product Packaging and Web SnapServer Administrator Guide User CD and Web SnapServer Online Help Administration Tool...
Page 16 SnapServer Administrator Guide...
Page 17: Chapter 1 Administrative Overview
Administrative Overview SnapServers are designed as flexible, low-maintenance network file servers optimized for performance and efficiency. SnapServers run the GuardianOS, built to maximize file I/O throughput across multinetwork protocols. To this end, all unnecessary system control and processing functions that are associated with a general-purpose server have been removed.
Page 18: Guardianos Specifications
GuardianOS Specifications Snap Unit Description SnapServer EXP The SnapServer EXP E2000 is a 2U expansion array with E2000 up to 4 to 12 hot-swappable SATA II or SAS disk drives. It can be used to expand the capacity of the SnapServer NAS N2000.
Page 19 Feature Server Emulation Network Security Data Protection Specification Windows 2000/2003/2008/NT 4 AppleShare 6.0 Network File System (NFS) 2/3/4 Windows Print Server IPP Print Server CA eTrust Antivirus software Microsoft Active Directory Service (ADS) (member server) Windows NT Domain (member server) UNIX Network Information Service (NIS) File and Folder Access Control List (ACL) Security for Users and Groups...
Page 20 GuardianOS Specifications Feature System Management SnapServer Administrator Guide Specification Browser-based Administration Tool for remote system administration SnapCLI for volume system deployment SnapServer Manager utility (platform independent) SNMP (MIB II and Host Resource MIB) User disk quotas for Windows, UNIX/Linux, Mac, FTP/ FTPS Group disk quotas for UNIX/Linux Environmental monitoring...
Page 21 Feature RAID Options DHCP Support Specification RAID 0 (drive striping): Large virtual drive with data striped across all drives of the array to provide maximum performance with no loss in usable capacity. Does not provide data protection. RAID 1 (drive mirroring): One or more drives duplicate one drive for maximum data protection.
Page 22: What's New In Guardianos
What’s New in GuardianOS What’s New in GuardianOS The following tables list the new and changed features since GuardianOS v3.2. What’s New in GuardianOS v6.0 GuardianOS 6.0 has the following new features and functionality: Feature Support for Multiple Ethernet Ports Write Cache Option Email Authentication and Encryption Capability...
Page 23 Feature User Interface Enhancements The User Interface now comes in three color schemes: Windows 2008 Domain Support Support for 128-bit SMB Encryption File Security Viewing Root Filesystem Check What’s New in GuardianOS v5.1 GuardianOS 5.1 has the following new features and functionality: Feature Web root capability Automatic software update...
Page 24 What’s New in GuardianOS What’s New in GuardianOS v5.0 GuardianOS 5.0 has the following new features and functionality Feature Improved system performance Enhanced Windows security and permissions compatibility Improved User Interface RAID 6 and RAID 10 support NFS v4 support Expanded CLI Dynamic Home Directories Switch-side Load Balancing...
Page 25 What’s New in GuardianOS v4.4 GuardianOS 4.4 has the following new features and functionality Feature Data Migration utility Command Line Interface Enhanced Disaster Recovery Support for recovering Snap EDR Management Console Enhanced iSCSI support New OS and browser support Support has been added for Windows Vista, Internet USB tape drive support Improved share name support...
Page 26 What’s New in GuardianOS What’s New in GuardianOS v4.3/4.2 GuardianOS 4.3/4.2 contains the following new functionality: Feature Enhanced NFS client support in Unicode mode Upgrade of NetVault Bakbone NetVault Bakbone has been upgraded from v7.1.1 to v7.4 Improved Snap EDR support Improved UPS support Improved Quotas design Auto-refresh feature...
Page 27 What’s New in GuardianOS v4.0 Starting with GuardianOS v4.0, Backup Express is no longer supported. Note GuardianOS v4.0 introduced the following notable changes to the web admnistration interface: Feature (pre-4.0) Add-on Features Changing the Admin User Password Windows Networking View all disks (formerly from Storage >...
Page 28: Snapserver Manager
SnapServer Manager SnapServer Manager SnapServer Manager (SSM) is a Java-based, platform-independent, multiserver administrative application that runs on all major platforms. SSM provides a single interface from which administrators can discover, configure, and monitor all GuardianOS SnapServers on their network. With SSM, administrators can compare, copy, and configure settings for groups of GuardianOS SnapServers in a single operation.
Page 29: Multiserver Administration
Launching SnapServer Manager Launch SSM using one of the methods described in the following table: Operating System Microsoft Windows NT/XP/ 2000/2003/Vista/2008/7 Macintosh v10.2 or higher UNIX/Linux Multiserver Administration Multiserver administration is available only for GuardianOS SnapServers. • Simultaneous application of settings to server groups — You can organize GuardianOS servers into functional groups and apply settings to all servers in the group simultaneously.
Page 30: Ssm Feature Licensing
Connecting to the Server for the First Time SSM Feature Licensing Use the SSM Feature Licensing menu to apply SnapExtension license keys to one or more servers. There is no limit to the number of licenses that can be entered using this dialogue box.
Page 31 The server number is a unique, numeric-only string that appears on a label affixed to the chassis. • On the SnapServer 410 and N2000, the server label is located on the top of the chassis in the left front corner. •...
Page 32: Using The Initial Setup Wizard
Using the Initial Setup Wizard Using the Initial Setup Wizard The first time you connect to a SnapServer via the browser-based Administration Tool, the Initial Setup Wizard runs. The Initial Setup Wizard consists of several screens that allow you to change the server name, set the date and time, set the administrator password, configure TCP/IP settings for the primary Ethernet port (by default Ethernet1), and reclaim the snapshot space that is by default allotted on the volume.
Page 33: Determining Capacity
Determining Capacity • The default gateway IP address • The DNS IP address • WINS server(s) IP address(es) Keeping or Reclaiming the Snapshot Space A Snapshot is a point-in-time image of your volume. This image can be used for backup or recovery purposes. See “Snapshots” on page 111 for detailed information.
Page 34: Scheduling Data Protection Tasks
Scheduling Data Protection Tasks For example, to calculate the capacity of a SnapServer 520 with 1 TB total capacity in its default state, consider both the hardware and software configuration: • The four 250 GB disk drives each provide 240 GB of formatted capacity. •...
Page 35: Migrating Data From Legacy Servers To The Snapserver
Migrating Data from Legacy Servers to the SnapServer The Data Migration utility can be used to copy or move data from any computer supporting CIFS/SMB or NFS (v2 and v3) directly to a SnapServer. Access the utility by selecting Maintenance > Data Migration Migration”...
Page 36: Snapextensions
SnapExtensions SnapExtensions SnapExtensions are software applications, agents, and utilities that extend the capabilities of a SnapServer. Some SnapExtensions are fully functional out-of-the- box; others may require a download and/or the purchase of a license for full operation. For up-to-date information on feature availability, contact Overland Storage.
Page 37: Chapter 2 Network Access To The Server
Network Access to the Server SnapServers are preconfigured to use DHCP, autonegotiate network settings, and allow access to the server for Windows (CIFS/SMB), Unix (NFS), Macintosh (AFP), FTP/FTPS, and HTTP/HTTPS clients. Discussed next are the options for configuring TCP/IP addressing, network bonding, and access protocols.
Page 38: Viewing Current Network Settings
Viewing Current Network Settings Viewing Current Network Settings The Network > Information screen displays the server's current network settings. One column appears for each Ethernet port. Field definitions are given in the following table: Ethernet Interface Information Port Name Enabled TCP/IP Settings Obtained from IP Address...
Page 39: Tcp/Ip Options
DNS Information Domain Name Primary DNS Secondary DNS #1 Secondary DNS #2 TCP/IP Options GuardianOS SnapServers ship with one or more Gigabit Ethernet (GbE) ports. The following table describes TCP/IP options; default settings appear in italics. Option Setting TCP/IP DHCP Addressing Static Network...
Page 40 TCP/IP Options Option Setting Switch Trunking Link Aggregation (802.3ad) Enable Checked Ethernet Unchecked Speed/ Auto duplex Fixed Primary Interface SnapServer Administrator Guide Description This mode groups multiple physical Ethernet links to create one logical interface. Provides high fault tolerance and fast performance between switches, routers, and servers.
Page 41: Configuring Tcp/Ip Settings
Configuring TCP/IP Settings TCP/IP settings are configured on the Administration Tool. This screen displays information about the server’s Ethernet ports, including: Column Description Port/Bond A list of the Ethernet Ports or Bonds. Click a port or bond to display or modify configuration details.
Page 42: Issues In Tcp/Ip Configuration
Configuring TCP/IP Settings Column Description • Link Aggregation (802.3ad)—Like Switch Trunking, this mode groups multiple physical Ethernet interfaces to create one logical interface, and provides high fault tolerance and fast performance between switches, routers, and servers. Uses Link Aggregation Control Protocol (LACP) to autonegotiate trunk settings.
Page 43 Connect the SnapServer to the Network via a Switch While it is possible to connect a SnapServer to the network via a hub, this configuration unduly restricts the performance of the server for the following reasons: • Hubs do not support full-duplex. You can employ full-duplex only when the SnapServer is connected to a switch.
Page 44: Default Network Protocol Settings
Default Network Protocol Settings Default Network Protocol Settings SnapServers are preconfigured to allow multiplatform access in heterogeneous Windows, UNIX/Linux, and Macintosh environments. The following table summarizes the SnapServer’s default network protocol access configuration. Protocol Default Windows (CIFS/ Enabled SMB) UNIX (NFS) Enabled Apple (AFP) Enabled...
Page 45: Windows Networking Configuration
Windows Networking Configuration Windows Networking Configuration Windows SMB and security settings are configured on the Network > Windows screen of the Administration Tool. Topics include: • Support for Windows Networking (SMB) • Support for Windows Network Authentication Support for Windows Networking (SMB) The default settings make the SnapServer available to SMB clients in the workgroup named Workgroup.
Page 46: Support For Windows Network Authentication
Windows Networking Configuration still see these shares. To completely hide shares from visibility from any protocols, Security > Shares share option that hides a share from SMB, AFP, HTTP, HTTPS, and FTP clients (However, shares are not hidden from NFS clients, which cannot connect to shares that aren't visible.
Page 47 Kerberos Authentication Kerberos is a secure method for authenticating a request for a service in a network. Kerberos lets a user request an encrypted “ticket” from an authentication process that can then be used to request a service from a server. The user credentials are always encrypted before they are transmitted over the network.
Page 48 Windows Networking Configuration Connecting from a Windows Client Windows clients can connect to the SnapServer using either the server name or IP address. To navigate to the server using Windows Explorer, use one of these procedures: • For Microsoft Windows Vista, 2008, and 7 clients, navigate to server_name.
Page 49: Nfs Access
Select a share (called a volume on the Mac) to mount on your desktop. If “guest” is enabled for SMB or if your default log on is a valid SMB user, you will be presented with a share selection dialog box. Choose the share to connect to or click should appear on your desktop for the share.
Page 50: Support For Nfs
Apple Networking Configuration Support for NFS Consider the following technical information when configuring access for your NFS clients. Supported Protocols SnapServers support these versions of the NFS protocol: Protocol Version 2.0, 3.0, 4.0* Mount 1.0, 2.0, 3.0 Lockd 1.0, 4.0 * NFS v4 ACLs are not supported.
Page 51: Afp Configuration Guidelines
AFP Configuration Guidelines Consider the following when configuring access for your AFP clients. Terminology Some SnapServer terms may cause confusion for those familiar with Apple terminology. Term Definitions Share A SnapServer share appears as a Macintosh volume that can be accessed through the Chooser.
Page 52: Ftp/Ftps Access
FTP/FTPS Access Supported AFP Clients The SnapServer supports MacOS 9.x and 10.x clients. FTP/FTPS Access FTP and FTPS settings are configured on the Administration Tool. FTPS adds encryption to FTP for increased security. By default, FTP and FTPS clients can access the server using the anonymous user account, which is mapped to the SnapServer's guest user account and AllUsers group account.
Page 53: Http/Https Access
HTTP/HTTPS Access HTTP and HTTPS are used for browser-based access to the server via Web View, Web Root, or the Administration UI. HTTPS enhances security by encrypting communications between client and server, and cannot be disabled. You can, however, disable HTTP access on the Tool.
Page 54: Web View
HTTP/HTTPS Access Accessing the Admin Tool when Web Root is Enabled By default, when you connect to a SnapServer with web root enabled, the browser will load the user-defined HTML page or present a directory listing of the Web Root. To access the Administation Tool (e.g., to perform administrative functions, change a password, etc.), enter the following in the browser address field: http://[servername or ip address]/config You will be prompted for your User ID and password, then you will be placed into...
Page 55: Dhcp Server
DHCP Server DHCP server settings are configured on the Administration Tool. To configure the SnapServer as a DHCP server, it must have a static IP address. The DHCP server automatically uses the subnet of the IP address you set up. Ensure that the network has no other active DHCP servers.
Page 56: Adding The Network Printer To The Client
Print Server Adding the Network Printer to the Client The SnapServer supports both Windows SMB and IPP printing protocols. To make printer drivers easily accessible to users, copy them to a share that Note everyone can access on the SnapServer. The SnapServer cannot be configured to automatically provide printer drivers to clients.
Page 57: Monitoring Print Jobs Using The Administration Tool
Adding the Network Printer to a Linux Client Add a printer using your usual method. If you are using SMB, you will need to know the SnapServer name. If you are using IPP, enter the exact path as follows in the URL field: http://servername:631/printers/sharename where servername is the name or IP address of your SnapServer and sharename is the...
Page 58 Print Server SnapServer Administrator Guide...
Page 59: Chapter 3 User & Group Management
User & Group Management Authentication validates a user’s identity by requiring the user to provide a registered login name and corresponding password. SnapServers ship with predefined local users and groups that allow administrative and guest user access to the server via all protocols. Administrators may choose to join the SnapServer to a traditional Windows NT or Active Directory domain, and Windows clients can then authenticate to the server using their domain credentials.
Page 60: Default User And Group Settings
Default User and Group Settings Default User and Group Settings SnapServer default security configuration provides one share to the entire volume. All network protocols for the share are enabled, and all users are granted read-write permission to the share via the guest account. A local user or group is one defined locally on a SnapServer using the Administration Tool.
Page 61: Local Users And Groups
• When the server automatically generates UIDs or GIDs for imported Windows domain users or groups, UIDs or GIDs that are already in use by local and NIS users will be skipped. • When NIS domain users and groups are imported, the SnapServer will discard any that are less than 101 or are in conflict with UIDs already in use by local or Windows domain users and groups.
Page 62 Local Users and Groups Changing Local UIDs or GIDs The SnapServer automatically assigns and manages UIDs and GIDs. Because you may need to assign a specific ID to a local user or group in order to match your existing UID/GID assignments, the SnapServer makes these fields editable. Password Policies To provide additional authentication security, set password character requirements, password expiration dates, and lockout rules for local users.
Page 63: Nis Domain
NIS Domain NIS Domain NIS domains are configured on the screen of the Administration Tool. Network > NIS The SnapServer can join an NIS domain and function as an NIS client. It can then read the users and groups maintained by the NIS domain. Thus, you must use the NIS server to make modifications.
Page 64 NIS Domain SnapServer Administrator Guide...
Page 65: Chapter 4 Storage Configuration And Expansion
Storage Configuration and Expansion Much of the configuration discussion presented here is not applicable to Note SnapServers with fewer than four (4) drives. For SnapServer 110 and 210, see the User’s Guide for SnapServer 110 and 210 for storage configuration guidelines. SnapServers with four to eight drives are preconfigured as a single RAID 5, SnapServers with twelve drives are preconfigured with a single RAID 6, and SnapServer 110 and 210 are preconfigured with a single RAID 0.
Page 66: Default Storage Configuration
Default Storage Configuration Default Storage Configuration The default storage configuration for all SnapServer and exapnsion models is shown in the table below. Each server’s disk space has a single volume, and a single share pointing to the volume. The share access settings of the default share grant access to all users and groups over all protocols.
Page 67: Changing The Default Storage Configuration
Changing the Default Storage Configuration The SnapServer’s flexible storage architecture allows for a wide variety of implementations to suit many different storage needs. In some cases, administrators may change the default configuration to increase capacity by modifying the configuration of the SnapServer, or attaching one or more expansion arrays. When a backup scheme does not require backing up from a snapshot, or when a backup window can be used while files are not active, the snapshot space can be reclaimed for storage on the data volume.
Page 68 RAIDs drives as a hot spare. The following table summarizes the advantages and disadvantages of each type of RAID. Features Data Loss Risk Write Access Speeds Usable Capacity Disks Required Supports Hot Spares To reduce exposure to double-drive disk failures on RAID 5, use no more Caution than eight drives in a single RAID set and group smaller RAID sets together.
Page 69 Item Description Identifying Hot spares are identified on the Storage > Disks/Units screen using the following icons: Each icon will be associated with a disk in the RAID, identifying that disk as either a local hot spare or a global hot spare. Interaction When a drive in a RAID fails, the system looks for a hot spare in the following order:...
Page 70: Raid Groups
RAIDs The background disk scan is enabled by default. To disable the background disk scan, go to the Storage > RAID Sets Notes • If the background disk scan is disabled, it will still initiate a scan on a RAID if problems are detected on one of the RAID drives.
Page 71 RAIDs Also consider the following: Adding an Expansion Array In a common scenario, a four-drive SnapServer configured as a RAID 5 is nearing full utilization. The administrator decides to add an expansion array. The administrator creates a RAID 5 on the expansion array, groups it with the existing RAID on the SnapServer, and then expands the size of the original volumes using the new storage from the expansion array.
Page 72: Volumes
Volumes Volumes Volumes are created, viewed, edited, and deleted from the of the Administration Tool. The default volume organizes the SnapServer’s storage capacity into a single volume with a single file system. If you need separate file systems on the same server, you can delete the default volume and create two or more smaller volumes in its place.
Page 73 a RAID or the volume. To reconfigure the antivirus software, click Antivirus To reactivate Snap EDR functionality after creating a new volume, download the Snap EDR package from the SnapServer web site and install it on the server using the OS Update feature. Then click the and click the button.
Page 74: Checking Filesystems
Volumes them). The security model determines the file-level security scheme that will apply to files and folders within the volume or SnapTree directory. Configuring Write Cache Not related to write cache on iSCSI disks. For information about configuring Note write cache on iSCSI disks, see “Write-Cache Options with iSCSI Disks” on page 89. By default, write cache is enabled on all volumes.
Page 75 Volume Management Tools The SnapServer offers several tools for monitoring and controlling how storage space on a volume is used. Function Ongoing Maintenance Email Notification Volume Usage Quotas You can view volume status from the To Check the Root Filesystem Checking the root filesystem requires a reboot of the server.
Page 76: Quotas
Quotas To start the filesystem check, select the level and click progress of the filesystem check will be displayed while it runs. You can view a log of the filesystem check by clicking Quotas Quotas are configured in the Assigning quotas ensures that no one user or group consumes a disproportionate amount of volume capacity.
Page 77: Data Migration
Data Migration Use the Data Migration feature to migrate data from a legacy SnapServer or other computer that supports CIFS or NFS (v2 or v3) to a new SnapServer. The Data Migration (DM) feature can be used to copy or move files and folders from a server on the network (source) to a SnapServer (target).
Page 78 Data Migration that are unknown on the target server will be retained but not enforced. This includes permissions for: • Local users on the source machine. • Domain users for domains unknown to the SnapServer (e.g., trusted domains, if the SnapServer is not configured to support trusted domains). •...
Page 79: Expansion Arrays
• If your source server uses a UNIX SnapTree and has permissions assigned to local or NIS users, use an NFS connection for migration. Local users that have UNIX permissions on the source will not be created Note on the target with the same UIDs. Migrating from a SnapOS Server When migrating from a SnapOS Server to a GuardianOS server, permissions will not be correctly retained.
Page 80 Expansion Arrays Snap Expansion S50 The Snap Expansion S50 storage subsystem is a 2U expansion array with up to twelve SAS or SATA II disk drives, or a combination of SAS and SATA disk drives up to a maximum of 12. It ships as a set of unassigned disks with no RAID configuration.
Page 81 Expansion Arrays Managing Expansion Array Storage Disk drives on expansion arrays are not preconfigured, but are shipped as unassigned disk drives, allowing administrators to configure the array as appropriate. screen displays the head unit and any expansion arrays Storage > Disks/Units attached to the head unit.
Page 82 Expansion Arrays multiple drive failures in a single RAID. See “RAID Groups” on page 54 for information on how to avoid this. Cautions • Host server disk drives and expansion array disk drives are logically interchangeable, but they are not physically interchangeable. That is, you cannot physically take a disk drive from an expansion array and place it in a host SnapServer.
Page 83: Disks And Units
Disks and Units The Disks/Units screen is a graphic representation of RAID configuration and disk status on your server. The legend explains the meaning of each icon. • Move the mouse over a RAID set name to highlight all disks within the RAID set. •...
Page 84 Disks and Units Adding Disk Drives to a RAID This section describes how to safely add drives to an existing RAID 1, 5, 6, or 10. On SnapServers, after a fresh drive is inserted into a drive bay, you must use the Administration Tool to add it to a RAID.
Page 85 Unsupported Disk Drive Combinations To Add New Disk Drives to Increase Capacity on a SnapServer N2000 or E2000 Review the Recommended Disk Drive Configurations and Unsupported Disk Drive Combinations, and determine which drive slots to populate with new disk drives. Remove the bezel by pressing the latch on the left side of the bezel (as you face it) and gently pulling to release the left side from the chassis.
Page 86: Hot Swapping Disk Drives
Disks and Units Hot Swapping Disk Drives The term hot swap refers to the ability to remove and add components to a system without the need to turn off the server or interrupt client access to files. When to Hot Swap Disk Drives When available storage space is not at a premium, most administrators prefer to configure a RAID with a hot spare that automatically takes the place of a failed drive.
Page 87 Press the latch on the right side of the disk drive to release the front lever. Grasp the lever and pull to remove the drive from the chassis. With the drive carrier lever open, slide the new drive into the chassis. Once the drive is pushed all the way into the chassis, close the drive carrier lever and press until it locks into place.
Page 88 Disks and Units Replacing a Disk Drive on a SnapServer 410 When the status LED is amber and the activity LED is off, the drive has failed or is not working properly. Remove the front bezel by pressing in the latches on each side of the bezel and pulling the bezel away from the chassis.
Page 89 Replacing a Disk Drive on a SnapServer 510, 520, 550, 620, 650, or Snap Expansion S50 When the status LED is amber and the activity LED is off, the drive has failed or is not working properly. Remove the front bezel (if applicable) by pressing in the latches on each side of the bezel and pulling the bezel away from the chassis.
Page 90 Disks and Units Replacing a Disk Drive on the SnapServer 4200, 4500, or Snap Disk 10 When the drive’s power LED is amber and the activity LED is off, the disk drive has failed or is not working correctly. Remove the front bezel. With a hand on each latch, slide both latches on the front bezel toward the center.
Page 91 Release the latch on the new disk drive and open its handle. The handle must be open for you to insert the disk drive all the way into its bay. Insert the new disk drive into the empty drive bay, pushing it all the way forward before you close the handle.
Page 92 Disks and Units Grasp the handle and remove the failed disk drive by pulling it towards you. To insert a new disk drive, release the carrier handle by pressing the latch and insert the carrier all the way into the enclosure. Once the carrier is in the enclosure, close the handle until you hear a click.
Page 93: Chapter 5 Iscsi Disks
iSCSI Disks Internet SCSI (iSCSI) is a standard that defines the encapsulation of SCSI packets in Transmission Control Protocol (TCP) and their transmission via IP. On SnapServers, an iSCSI disk is based on an expandable, RAID-protected volume, but appears to a client machine as a local SCSI drive. This storage virtualization frees the administrator from the physical limitations of direct-attached storage media and allows capacity to be expanded easily as needed.
Page 94: Configuring Iscsi Initiators
Configuring iSCSI Initiators • The SANSurfer iSCSI HBA CLI Application Users Guide: This document is available for download on the QLogic web site at support/drivers_software.asp. • The RedHat or Novell (SuSE Linux) web sites: Information on configuring the Linux in-box initiators can be found by searching for iSCSI on the RedHat or Novell web sites.
Page 95 iSCSI Configuration for Microsoft Windows using MS Initiator Installation and configuration information is included with the MS Initiator download (uguide.doc). It can also be downloaded from the Microsoft web site. Before implementing iSCSI using MS Initiator, please consider the following: •...
Page 96 Configuring iSCSI Initiators box to make this a persistent target, then click system reboots SnapServer target. Use the Disk Administrator to configure all volumes on top of the disks. From the Bound Volumes/Devices tab on the Property dialog box, click to allow the iSCSI service to configure the list of persistent volumes.
Page 97 Configuring Shares to iSCSI Disks When using the Microsoft initiator, shares to iSCSI disks may not automatically reconnect when the Windows system hosting the shares is rebooted. There are two methods to resolve this issue: • Share an iSCSI target that has an assigned drive letter. This method requires changes to the Windows registry and is described in article #870964.
Page 98 Configuring iSCSI Initiators Configuring Dynamic Disks to Persistently Reconnect On pre-Vista operating systems, when iSCSI targets are configured as dynamic disks, the Microsoft iSCSI initiator connecting to the dynamic disk may fail to connect properly during system boot. Using dynamic disks for iSCSI targets on pre- Vista operating systems is not supported by Microsoft.
Page 99 Verify that you have additional space available on the SnapServer to expand an existing volume • Open the browser-based Administration Tool for the SnapServer from a client on the network. • Navigate to Storage > iSCSI • Select the iSCSI disk you intend to expand. If you have not disconnected from the iSCSI disk at the host, you will be Note unable to proceed to the configuration page.
Page 100 Configuring iSCSI Initiators Identify the specific volume you are expanding. Enter: select disk n where n is the disk number that Diskpart indicated from the list command. Enter: select Volume n where n is the volume number that Diskpart indicated from the list command. Enter extend size=n where n is the number of megabytes you want to expand the disk.
Page 101 iSCSI Configuration for Linux and UNIX Before implementing iSCSI on Linux or UNIX systems, consider the following: • The QLogic QLA4010/4050/4052c hardware initiator supports Red Hat Enterprise Linux 3, QU5; Red Hat Enterprise Linux 4, QU1; and SuSE Linux Enterprise Server 9, SP3. This initiator provides CHAP authentication and can connect to multiple targets simultaneously.
Page 102: Iscsi Configuration For Vmware
Configuring iSCSI Initiators In System B's /etc/iscsi.conf DiscoveryAddress=192.3.2.193 Username=b Password=PasswordForB System A and B can connect to their own iSCSI disks on the same SnapServer (IP address 192.3.2.193) without the possibility of data corruption caused by sharing the same iSCSI disk. iSCSI Configuration for Novell NetWare Consider the following information before implementing iSCSI on NetWare servers:...
Page 103 Static Discovery, allowing you to enter the IP addresses of only those targets you want the VMware initiator to access. For more information regarding installation and configuration of required VMware components, refer to the documentation included with the VMware Server installation.
Page 104: Iscsi Configuration On The Snapserver
iSCSI Configuration on the SnapServer iSCSI Configuration on the SnapServer iSCSI disks are created on the Before setting up iSCSI disks on your SnapServer, carefully review the following information. Isolate iSCSI Disks from Other Resources for Backup Purposes It is important to isolate iSCSI disks from other resources on the SnapServer for two reasons: •...
Page 105 iSCSI Configuration on the SnapServer iSCSI Multi-Initiator Support The Support Multi-Initiator check box allows two or more initiators to simultaneously access a single iSCSI target. Multi-Initiator Support is designed for use with applications or environments in which clients coordinate with one another to properly write and store data on the target disk.
Page 106 iSCSI Configuration on the SnapServer the significant increase in write performance that write-cache provides, can disable this feature for individual iSCSI disks. Notes • Write-cache can be disabled on an iSCSI-disk-by-iSCSI-disk basis. Disabling write-cache for an iSCSI disk does not disable write-cache for any other iSCSI disk or any other resources on the SnapServer.
Page 107: Creating Iscsi Disks
iqn.[servername].[iscsidiskname] • The format of IQN names for VSS-based iSCSI disks on the SnapServer is: iqn.1997-10.com.snapserver:[servername]:[diskname].[nnn] where [servername] is the name of the SnapServer, [diskname] is the name of the iSCSI disk on the target SnapServer, and [nnn] is a sequential number starting from 000.
Page 108 Creating iSCSI Disks To View iSCSI Disk Status Information You can view iSCSI disk status information from the Label iSCSI Disk Name Volume Status Active Client Authentication Size To Configure iSNS Go to the Network > iSNS To Edit an iSCSI Disk Click an iSCSI disk name.
Page 109: Configuring Vss/Vds For Iscsi Disks
Configuring VSS/VDS for iSCSI Disks GuardianOS provides VSS and VDS hardware providers to support Microsoft Volume Shadow Copy Services (VSS) and Virtual Disk Service (VDS) for iSCSI disks. VSS/VDS operations are supported on iSCSI disks created using GuardianOS Note v5.2 and later. •...
Page 110 Configuring VSS/VDS for iSCSI Disks SnapServer Administrator Guide...
Page 111: Chapter 6 Share And File Access
Share and File Access SnapServer has implemented features to accommodate the disparate methods used by the SMB and NFS protocols for sharing data. At the share level, administrators can assign read-write or read-only share access to individual Windows (and local) users and groups. Administrators can also edit the NFS exports file to control how shares are exported to NFS client machines.
Page 112: Configuring Share And Folder Security Overview
Configuring Share and Folder Security Overview Configuring Share and Folder Security Overview SnapServers support file access in Windows, UNIX, and Apple networks, as well as access via FTP and HTTP. Although the GuardianOS runs on an optimized Linux kernel and has many Linux characteristics, the cross-platform features make it very different than a pure Linux distribution.
Page 113: Where To Place Shares
• Disable individual protocol access to certain shares by navigating to Security > Shares > Create Share > Advanced Share Properties disabling specific protocols, or by selecting a share, clicking to expand , and enabling/disabling specific protocols. Share Properties File and Directory Permissions GuardianOS supports two “personalities”...
Page 114 Configuring Share and Folder Security Overview event that permissions on a child directory are inadvertently altered to disallow administrative access, access from the root share is not affected. This also allows one root share to be targeted when performing backups of the server. If it is necessary to have the root of the volume accessible, using the Hidden option helps ensure only those that need access to that share can access it.
Page 115: Components And Options
Components and Options Shares are created and share access is granted using the Administration Tool. File- level permissions are configured from a Windows or UNIX/Linux workstation. The following table summarizes the components, options, and tools available for setting up share and file security on SnapServers. Component Options Security Models...
Page 116: Snaptrees And Security Models
SnapTrees and Security Models Component Options Share Access Share-level access allows users/groups/clients to connect to a share and is configured from the Security > Share Access screen. Users and groups known to the system can be given Full Access or Read Only (R) access to the share.
Page 117 SnapTree Functionality The following table describes the behavior of SnapTrees and Security Models. Function Description SnapTree Default ownership differs according to the method used to create the Directory SnapTree directory: Ownership • From the client — For UNIX personality directories, the owner and owning group will be according to the logged-in user.
Page 118: Id Mapping
ID Mapping Function Description SnapTree File Security model and permissions differ according to the method used to System create the SnapTree directory: Permissions • From the client: If SMB, permissions will either be according to ACL inheritance (if the parent volume root directory has the Windows security model) or Full Access to the owning user only.
Page 119: Shares
example, if you enter ‘abc’ as your search criterion, all users and groups containing ‘abc’ in the name will be identified. Shares Shares are created, viewed, edited, and deleted from the the Administration Tool. The shares table lists all of the shares on the SnapServer, and describes the share properties.
Page 120 Shares or group that has access to the root of a volume will have access to EVERY file and subdirectory on that volume unless there is a specific ACL in place precluding that access. In general, access to a share at the root of a volume should only be granted to a system administrator or backup operator.
Page 121: Configuring Share Access
Configuring Share Access The GuardianOS supports share-level as well as file- and directory-level permissions (see “Windows ACLs” on page 107) for all local and Windows domain users and groups. Share Access Behaviors Administrators tasked with devising security policies for the SnapServer will find the following share access behaviors of interest: •...
Page 122: Creating Home Directories
Creating Home Directories Example B: More restrictive share-level access trumps more permissive file-level access. Share Level File Level Read-only Full control to FileB Read-only access to all directories and files in Setting User-based Share Access Permissions Share permissions for Windows, Apple, FTP, and HTTP users are configured from by clicking the link in the Security >...
Page 123: Windows Acls
Home directories are supported for SMB, NFS, AFP, HTTP/HTTPS, and FTP/FTPS. They are accessed by clients in the following manner: • For SMB, AFP, and HTTP/HTTPS, users are presented with a virtual share named after the username. The virtual share is visible and accessible only to the user.
Page 124 Windows ACLs Windows personality file or directory (or deletes and recreates it), the personality will change to UNIX with the UNIX permissions specified by the client. Group membership of NFS clients is established by configuring the local Note client’s user account or the NIS domain. Group membership of SnapServer local users or users ID-mapped to domain users is not observed by NFS clients.
Page 125: Security Guides
To Set File and Directory Permissions and Inheritance (Windows) Using a Windows NT 4.0, 2000, 2003, XP, Vista, 2008, or 7 client, map a drive to the SnapServer, logging in as a user with change permissions for the target file or directory.
Page 126 Security Guides The SnapServer will need the name of your Windows domain, and the name and password of an administrative user within your Windows domain. For more information about Windows domains and other Microsoft networking settings, see “Support for Windows Networking (SMB)” on page 29 and “Support for Windows Network Authentication”...
Page 127: Chapter 7 Snapshots
Snapshots A snapshot is a consistent, stable, point-in-time image of a volume that can be backed up independent of activity on the live volume. Snapshots can also satisfy short-term backup situations such as recovering a file deleted in error, or even restoring an entire file system, without resorting to tape.
Page 128: Snapshot Management And Usage
Snapshot Management and Usage Snapshot Management and Usage This section describes snapshot components and dependencies. The Snapshot Pool Snapshot data are stored on a RAID in a snapshot pool, or space reserved within the RAID for this purpose. Each RAID on the system contains only one snapshot pool. This pool contains all snapshot data for all volumes on the RAID.
Page 129: Estimating Snapshot Pool Requirements
Snapshots and iSCSI Disks Running a GuardianOS snapshot on a volume containing an iSCSI Disk will abruptly disconnect any clients attempting to write to the iSCSI Disk and the resulting snapshot may contain inconsistent data. Do not use GuardianOS snapshots on a volume containing an iSCSI Disk. To create a native snapshot of an iSCSI disk on Windows systems, use the VSS feature described in “Configuring VSS/VDS for iSCSI Disks”...
Page 130: Adjusting Snapshot Pool Size
Adjusting Snapshot Pool Size Adjusting Snapshot Pool Size The current size of the snapshot pool for each RAID (or RAID group) can be viewed by navigating to the Storage > Snapshots button, then clicking the Raid Set. On the screen that opens, you can adjust the size of the pool as necessary.
Page 131: Coordinating Snapshot And Backup Operations
read-only), a snapshot share inherits access privileges from its associated live- volume share. The same folders appear on the Web View screen when you connect to the Note SnapServer using a Web browser; however, the snapshot share folder does not provide access to the snapshot;...
Page 132 Coordinating Snapshot and Backup Operations backup packages to include this information. If the volume needs to be restored from tape, or the entire system needs to be recreated from scratch on a different server, this information may be required to restore all rights and quota information.
Page 133: Chapter 8 Disaster Recovery
Disaster Recovery Disaster recovery entails creating the files you need to recover a SnapServer’s configuration information, such as network and RAID configurations, as well as volume-specific information, such as ACLs and quota settings. It also includes what to do if all access to the data on a SnapServer is cut off due to a hardware or software failure.
Page 134: The Snapdrimage File And The Volume Files
Backing Up Server and Volume Settings The SnapDRImage File and the Volume Files Details on the SnapServer disaster recovery files and the information they contain are as follows: • SnapDRImage — The SnapServer disaster recovery image saves server-specific settings such as network, RAID, volume and share configuration, local user and group lists, and EDR Management Console settings (if applicable).
Page 135: Rejoining The Server To A Windows Domain
• You have devised and implemented a data backup strategy. It is recommended that you make a backup of your system regularly, from the root of the share for each volume, and store it in an off-server location. This ensures that the most current data is backed up and available for use with a disaster recovery.
Page 136: Backing Up The Netvault Database Directory
Backing Up the NetVault Database Directory Backing Up the NetVault Database Directory This section details the use of the NetVault Database plug-in and offers various tips for its use. Backup Recommendations It is important to note that the NetVault Database can be backed up at any time as long as no other NetVault jobs controlled by this server are running.
Page 137: Recovering The Netvault Database
Recovering the NetVault Database This section summarizes the procedure necessary for recovering the NetVault Database (NVDB) from tape. For instructional details, see the NetVault documentation that shipped with your SnapServer. Pre-Restore Requirements Before restoring the database, perform the following steps on the SnapServer acting as the NetVault Server: Completely reinstall and configure the same version of the GuardianOS that the server was running.
Page 138 Recovering the NetVault Database Restore Procedure Access the Restore window from the NetVault GUI by clicking the button in the command toolbar. Double-click the NetVault Server open it. Plug-ins (and APMs) used to conduct successful backups on the selected client will be displayed.
Page 139: Disaster Recovery Procedural Overview
Disaster Recovery Procedural Overview The procedure described in this section for responding to a catastrophic event is general in nature and may result in the loss of data. Should such an event actually occur, the exact procedure to follow will vary according to environmental conditions.
Page 140: Cloning A Server
Cloning a Server Now you can replace your data from tape backup. If the backup doesn’t retain permission and ownership settings, you can restore these by selecting Volume Security Settings If you are restoring from any backup other than NetVault, you will need to Note recover the volume settings.
Page 141: Chapter 9 Ca Etrust Antivirus Software
CA eTrust Antivirus Software The CA eTrust Antivirus software is preinstalled on all GuardianOS SnapServers. By default, the software is enabled on most SnapServers, but no scan jobs or signature updates have been scheduled. (The server will, however, check for signature updates whenever the server boots.) These and other antivirus configuration and management tasks are performed using the CA eTrust Antivirus GUI, accessed from the screen of the Administration Tool.
Page 142: Antivirus Dependencies
Antivirus Dependencies Antivirus Dependencies The SnapServer implementation of CA eTrust Antivirus software includes the following features: HTTP Access and Antivirus Configuration To access the CA eTrust Antivirus configuration interface, HTTP must be enabled on the Network > Web Re-enabling the Antivirus Software The antivirus software is enabled by default.
Page 143: Launching The Ca Etrust Antivirus Gui
Launching the CA eTrust Antivirus GUI The CA eTrust Antivirus software is enabled by default. Some situations, such as deleting a volume or performing an upgrade procedure, may require you to re- enable the software. To learn how the antivirus software interacts with other GuardianOS software components, see “Antivirus Dependencies”...
Page 144: Scan Job Configuration And Scheduling
Scan Job Configuration and Scheduling Component Root Directory Move Folder Scheduled Scan Jobs Scan Job Configuration and Scheduling You can run scan jobs on demand or you can configure scan jobs to run periodically. This section outlines the process of configuring and running manual and scheduled scans.
Page 145 Choosing an Infection Treatment (Scan Tab) You can instruct the software to perform one of the following file actions when an infected file is found: File Actions Description Report Only (Default) Reports when an infection is found. Delete File Deletes an infected file. Rename File Renames an infected file with an AVB extension.
Page 146: Running A Manual Scan Job
Scan Job Configuration and Scheduling Running a Manual Scan Job Before running a local scan job, confirm that the scanner options are correctly configured as described in the previous section. In Local Scanner View, select the folders you want to scan. The left-hand pane displays the directory structure of the SnapServer.
Page 147: Signature Updates
Signature Updates Signature updates contain the latest versions of the signature files that recognize the latest infections. They also contain the latest engine versions, which do the work of looking for infections. Signature updates are made available on a regular basis by Computer Associates.
Page 148 Signature Updates Updating SnapServers that have Internet Access If your SnapServers have direct access to the Internet, you only need to schedule the downloads to set up automatic signature updates. If access to the Internet is routed through a proxy server, you may also need to specify the name of the proxy server. Both procedures are explained below: To Schedule Signature Update Downloads Choose...
Page 149 In the Path field, enter the path to the directory on the server on which the update file resides. If you are using a SnapServer, the path would be similar to the following: /shares/SHARE1/sigfiles where SHARE1/sigfiles is the share path to the directory containing the signature update files.
Page 150 Signature Updates Enter the path to the SnapServer (or Windows/SMB server) to which the update files have been downloaded (see previous procedure) using the following format: \\server_name\share_name where server_name is the name of the server, and share_name is the name of the share providing access to the files.
Page 151: Verifying Download Events
Verifying Download Events Use the following procedure to verify download and distribution events. Select View > Log Viewer In the left-hand pane, select the upper right-hand pane in chronological order. Select a distribution event. The details of the distribution event display in the lower pane.
Page 152: The Move Directory
The Move Directory The Move Directory You can configure scans to move infected files to the move folder ( options). To view infected files, click the Scanner pane of the Local Scanner View. To manage a moved file, right-click the file and select from the following options: Option Restore...
Page 153: Log View
Log View The Log View provides easy access to detailed information on scan, distribution, and other events. To access this view select Option Local Scanner RealTime Scanner Scheduled Scanner General Events Distribution Events from the View menu. Log View Description Displays summary information about scan jobs that have run.
Page 154 Log View SnapServer Administrator Guide...
Page 155: Chapter 10 Unicode
Unicode This section details how the GuardianOS SnapServer operates when Unicode is enabled. Topics in Unicode • What is Unicode? • Converting to Unicode • Unicode and Protocol Interaction • How Snapshots Interact with Unicode • Backing Up Unicode Servers •...
Page 156 Converting to Unicode Step 2: Back up your system Back up your system as you normally would. For more information about backing up your server, please see “Backing Up Server and Volume Settings” on page 117. Step 3: Convert to Unicode Navigate to Server >...
Page 157: Unicode And Protocol Interaction
Unicode and Protocol Interaction Step 4: Make a new DRImage Once your system has been converted to unicode, make a new DRImage. The procedures are the same as before (see “Disaster Recovery Procedural Overview” on page 123 for more details). Step 5: Back up the system with Unicode enabled backup applications Back up your system with a Unicode compliant backup application.
Page 158 Unicode and Protocol Interaction for example, you might see {!^AB in a file name. MacOSX clients can edit such files, and the names will be retained in their original form when written back to the file system. MacOS 9 and lower are not Unicode-compliant, and use the MacRoman code page to represent extended characters.
Page 159: How Snapshots Interact With Unicode
HTTP HTTP integrates easily with Unicode and the SnapServer. If invalid UTF8 characters are encountered on the file system, the characters will be returned with an escape sequence. Escape sequences begin with {!^. The following two characters are the hexidecimal value of the characters in the file name; for example, you might see {!^AB in a file name.
Page 160 Backing Up Unicode Servers The following table gives an overview of how Unicode interacts with backup applications: Officially Supports Unicode UI Displays Correct Filenames Backups and Restores Unicode data 1. The UI displays garbage but the data is intact. Backing Up Using Unicode-Enabled Windows Clients When backing up using a Unicode-enabled Windows client, connect and backup using SMB.
Page 161: Unicode And Expansion Arrays
Unicode and Expansion Arrays Backing Up Using Unicode-Enabled UNIX Clients Most Unicode-enabled UNIX clients run one of three language codes: 8859-1 (US), 8859-15 (Europe), or EUC-JP (Japan). In each of these situations, it is important to backup via the UNIX client with a language compliant backup application. Mixing languages (example: having a Japanese UNIX server and a Chinese backup application) will lead to data corruption.
Page 162 Unicode and Expansion Arrays Unicode Converted Head Units When a SnapServer is converted to Unicode, it stays converted to Unicode. If a non- Unicode expansion array is attached to a Unicode-converted SnapServer, the expansion array will be automatically converted to Unicode when it is incorporated with the SnapServer.
Page 163: Appendix A Backup And Replication Solutions
Backup and Replication Solutions GuardianOS supports several backup methods, including third-party off-the-shelf backup applications and applications that have been customized and integrated with the GuardianOS on the SnapServer. Enabling Unicode on the server will limit some backup applications’ ability to Note function with the SnapServer.
Page 164: Integrated Backup Solutions For The Snapserver
Integrated Backup Solutions for the SnapServer Integrated Backup Solutions for the SnapServer The following backup solutions are preinstalled and/or customized for the SnapServer: BakBone Netvault BakBone Netvault is a scalable, enterprise-wide backup solution for GuardianOS, Windows, Linux, and UNIX operating systems with the following functionality: •...
Page 165: Snap Enterprise Data Replicator (Snap Edr)
You can add multiple workstations by completing the fields and repeatedly selecting the button. This should only be done when management of your NetVault implementation MUST be managed from more than one workstation. Each client added in this way consumes a NetVault node license. Other NetVault Clients can be added using the NetVault Management GUI.
Page 166 Integrated Backup Solutions for the SnapServer Configuring Snap EDR for GuardianOS To configure the SnapServer as a Management Console or an Agent, do the following: Click the Snap EDR Select either the Configure as the Management Console button. If you are configuring the server as an Agent, you must provide the server Note name or IP Address of the Management Console.
Page 167: Off-The-Shelf Backup Solutions For The Snapserver
Off-the-Shelf Backup Solutions for the SnapServer These backup packages do not support the backup of Windows ACLs or Note legacy POSIX ACLs. If you use one of these packages, Overland Storage strongly recommends you create a SnapServer disaster recovery image (see page 118) before you perform a backup.
Page 168: Preinstallation Tasks
Off-the-Shelf Backup Solutions for the SnapServer • Location of the SnapServer backup and restore path — Backup servers often request the path for backup and restore operations on the SnapServer. When you configure a backup server to see the agent or client running on the SnapServer, use the following path: /shares/sharename where sharename is the name of the share to be backed up.
Page 169 Copy the agent/backup files to the agent directory. Using a method appropriate to your environment, copy the agent/client files to the directory you just created for this purpose. Installing the CA BrightStor ARCserve Agent This section explains how to install the CA BrightStor ARCserve Agent versions 11.5 and 12.0.
Page 170 Off-the-Shelf Backup Solutions for the SnapServer To unpack the tar file to get the agent files, type the following command and press Enter: tar -zxvf Linux.tar.Z If you later delete the volume this directory is on, you will need to reinstall Note the agent.
Page 171 Close the SSH client and return to the Admnistration Tool. To start the newly installed backup agent, navigate to the and click Restart Delete the agent files you copied to the SnapServer because they are no longer needed. To verify the success of the installation, use your backup management software to configure and run a test backup.
Page 172: Installing The Symantec Backup Exec Ralus Agent
Off-the-Shelf Backup Solutions for the SnapServer Installing the Symantec Backup Exec RALUS Agent To install the Backup Exec RALUS agent, do the following: Prepare the SnapServer Connect to the server over SSH. SSH v2 is required. If you fail to connect to the server, ensure that your SSH Note client is configured to connect via SSH v2.
Page 173 If CA Antivirus has been installed, you will have an /opt directory. If it has not been installed, create an /opt directory: mkdir /opt Create the following symbolic links from the new directories in ralus to the /opt directory: ln -s /hd/[volumename]/ralus/VRTS /opt ln -s /hd/[volumename]/ralus/VRTSralus /opt ln -s /hd/[volumename]/ralus/VRTSvxms /opt where [volumename] is the name of the volume with the most available space.
Page 174 Off-the-Shelf Backup Solutions for the SnapServer cli group member add group-name=beoper user-name=root If using a local Snap user account other than root or admin, and if password Note policies are enabled, configure the user to be exempt from password expiration. See “To Set Password Policy for Local Users”...
Page 175 Installing the Symantec NetBackup v6.5 Client This procedure assumes that you are using the default SnapServer Note configuration; and you have created a directory called agent (to which to copy your agent/client files) on the default share (SHARE1), such that the path to the directory is /shares/SHARE1/agent.
Page 176 Off-the-Shelf Backup Solutions for the SnapServer Create a “symbolic” link to the openv directory in the /usr/ directory: ln -s hd/[volumename]/openv /usr/ where [volumename] is the name of the volume with the most available space. Use the host file editor ( NetBackup servers to the NetBackup server.
Page 177 Remove the NetBackup services by deleting the files for in the bpjava-msvc /etc/xinetd.d rm -rf /etc/xinetd.d/bpcd rm -rf /etc/xinetd.d/vnetd rm -rf /etc/xinetd.d/vopied rm -rf /etc/xinetd.d/bpjava-msc Restart the SnapServer services by either rebooting or typing: /etc/rc.d/init.d/xinetd reload Installing the EMC Legato NetWorker Client This procedure assumes that you are using the default SnapServer Note configuration;...
Page 178 Off-the-Shelf Backup Solutions for the SnapServer Select a volume on which to put a directory called networker. If you later delete the volume the networker directory is on, you will need to Note reinstall the agent. cd /hd [lists all the volumes] [shows volume usage] df -h Determine which volume has the most available space by looking at the...
Page 179 copy the backup to the original using the command and then edit the file again. etc/profile To implement the changes, enter the following command: source /etc/profile Install the EMC Legato Networker Client Connect to the SnapServer via SSH, and log in as admin, using your admin user password.
Page 180 Off-the-Shelf Backup Solutions for the SnapServer To verify the success of the installation, use your backup management software to configure and run a test backup. Backup and Restore Operations with the EMC Legato NetWorker Client This section describes special procedures EMC Legato NetWorker users must use in order to perform backup and restore operations on the SnapServer.
Page 181 Use either the or the recover more details on these commands, see the EMC Legato Networker Command Reference. Connect to the SnapServer via SSH, and log in using the admin user name and password. SSH v2 is required. If you fail to connect to the server, ensure that your SSH Note client is configured to connect via SSH v2.
Page 182: Backup Of Iscsi Disks
Backup of iSCSI Disks Backup of iSCSI Disks iSCSI disks can be backed up from iSCSI clients using any standard backup application on the client operating system. These backups run independently of the SnapServer since the client backs up the contents of the iSCSI disk as if the iSCSI disk were a local hard disk.
Page 183: Appendix B Command Line Interface
Command Line Interface GuardianOS includes a command line interface (SnapCLI) accessible through SSH. Using the CLI, users can access information about most of the SnapServer configuration parameters and perform configuration and maintenance functions without using the GuardianOS web interface or SSM. Some administrative tasks must still be performed using the Administration Note Tool.
Page 184 SnapCLI Syntax For example, to see a list of available commands once you have logged into SnapCLI, type at the prompt. To see a description of a specific command, type the command name (e.g., date) + help or ?: date help Command Arguments and Options date...
Page 185 Suppose, instead of , you entered the command date available, one with options: Command Arguments and Options set [OPTIONS] - require-webview-auth=(yes|no) - non-secure-http=(yes|no) Thus, the following command string: web set require-webview-auth=yes non-secure-http=no sets HTTP/HTTPs properties on the SnapServer to require clients to authenticate in order to access the server and to disable non-secure HTTP access.
Page 186: Snapcli Commands
SnapCLI Commands SnapCLI Commands The following table presents a list of the available SnapCLI commands and a brief description of the function of each. Command activeusers apple get apple set date get date set date timezones dhcp get dhcp set diskunits domain get domain list...
Page 187 Command Description group create Create a local group group delete Delete a local group group get Get available groups with their associated information group list List available groups group set Change the properties of a local group group member add Add a group member to a local group group member delete Delete a group member from a local group...
Page 188 SnapCLI Commands Command iscsi delete iscsi get iscsi set isns get isns set jumboframe get jumboframe list jumboframe set name get name set netinfo nfs get nfs set nis get nis set ntp get ntp set ntp_server get ntp_server set openfiles osupdate get osupdate load...
Page 189 Command Description quota group set Set volume quota limit & usage for a specific group quota user get Get volume quota limit & usage for a specific user quota user set Set volume quota limit & usage for a specific user raid list List available raids raid create...
Page 190 SnapCLI Commands Command share nfsaccess delete shutdown slidingwindow get slidingwindow set slidingwindow list snapex snapshot create later snapshot get snapshot set snapshot list snapshot create now snapshot delete snapshot sched delete snapshot sched get snapshot sched set snapshot sched list snapshot pool get snapshot pool set snapshot pool list...
Page 191 Command Description syslog s2s Create a tar file of S2Sv2 logs syslog syswrapper Create a tar file of syswrapper only systemstatus Get system status information for the server tape list List the SCSI tape devices tape settings get Display current SCSI tape device settings tape settings set Update SCSI tape device settings tcpip get...
Page 192 SnapCLI Commands Command volume get volume create volume edit volume delete volume fscheck volume fscheck-root volume write-cache vxxaccess list vxxaccess add vxxaccess delete web get web set windows get windows set clear exit history less Quit SnapServer Administrator Guide Description Get a specific volume’s properties Create a new logical volume Edit an existing logical volume...
Page 193: Scripts In Snapcli
Scripts in SnapCLI Administrative tasks can be automated with shell scripts that call SnapCLI commands. Running a SnapCLI Script Create the script and put it in a share on the local server. Notes • Be sure to use an application that is compatible with the standard UNIX text file format (e.g., vi).
Page 194: Sample Script
Scripts in SnapCLI Sample Script Following is an example script that can be used to create and remove users, groups, and shares: #!/bin/sh ########################################################## # Copyright 2003-2007 Overland Storage, Inc. All rights reserved. # # Permision is granted to use this code provided that it # # retains the above copyright notice.
Page 195: Create A Share
# if both the user and the group exist add the user as a member of this group if $CLI user get user-name="$1" > /dev/null 2>&1; then if $CLI group get group-name="$2" > /dev/null 2>&1; then echo "Adding user '$1' to group '$2' ..." $CLI group member add user-name="$1"...
Page 196 Scripts in SnapCLI $CLI group delete group-name="$1" > /dev/null 2>&1 if [ $? -ne 0 ]; then echo "Deletion of group '$1' failed." return 1 else echo "Group '$1P' does not exist." return 0 # usage: 'rmshare <share_name>' rmshare() # if the share exists delete it if $CLI share get share-name="$1"...
Page 197: Appendix C Troubleshooting Snapservers
Troubleshooting SnapServers Basic techniques for identifying and resolving common hardware and networking issues are described here. Topics in Troubleshooting SnapServers • The Meaning of LED Indicators • System Reset Options • Networking Issues • Miscellaneous Issues • Phone Home Support Additional Resources Resource Description...
Page 198: The Meaning Of Led Indicators
The Meaning of LED Indicators The Meaning of LED Indicators LED indicators provide information on the status of basic connectivity, disk drives, fan modules, and power supply modules. • SnapServer NAS N2000 and EXP E2000 Status and Drive Light Behavior •...
Page 199 System LED Solid green The unit is powered on but GuardianOS is not running. Blinking green (N2000 only) GuardianOS is booted and operating normally. Network LEDs (N2000 only) Solid green The server is active and connected to the network. The port is disconnected or the Ethernet cable is not connected or linked to an active switch.
Page 200 The Meaning of LED Indicators Disk LEDs Top LED Off (SATA drive) Solid Blue (SAS drive) Blinking Blue Bottom LED Solid Red All Drive LEDs Blinking simultaneously (E2000 only) Power Supply Module Indicator Lights The LED on a SnapServer N2000 and E2000 power module is identified in the following illustration.
Page 201 The Meaning of LED Indicators SnapServer 110/210 Status and Drive Light Behavior The server has two status lights, one network light, and one disk light, as shown in the following illustration: Power Status Network Disk Power and System LEDs These status lights are located to the right of the power button. Looking at the server from the front, the lights appear in the following order, from left to right: Power LED, Status LED, Network LED, and Disk LED.
Page 202 The Meaning of LED Indicators The LEDs operate as described in the following tables: Power LED Solid green Status LED Blinking green Blinking amber Blinking amber and green Network LED Solid green Disk LED Blinking green Solid amber SnapServer 410 Status and Drive Light Behavior The server has two status lights, two network lights, and two lights for each of the four disk drives, as shown in the following illustration: SnapServer Administrator Guide...
Page 203 Overland Storage recommends that you become familiar with the operation of these lights. Power, System, and LAN LEDs These status lights are located to the right of the power button. Looking at the server from the front, the lights appear in the following order, from left to right: power LED, system LED, LAN 1 (Ethernet1) LED, and LAN 2 (Ethernet2) LED.
Page 204 The Meaning of LED Indicators SnapServer 500/600 Series Status and Drive Light Behavior The server has two status lights, two network lights, two lights for each of the four disk drives, and an identification light, as shown in the following illustration: Overland Storage recommends that you become familiar with the operation of these lights.
Page 205 The LEDs operate as described in the following tables: Power LED Solid green The server is powered on. The server is powered off. System LED Double-blink green The server is booting up. Triple-blink green The server is shutting down. Solid or blinking A problem was detected.
Page 206 The Meaning of LED Indicators Status LED (left) Activity LED (right) Solid amber Power Supply Module Indicator Lights The LED on a 500/600 Series power module is identified in the following illustration. Status LED Power Solid green Blinking green Solid amber SnapServer Administrator Guide Disk drive installed, but not working correctly...
Page 207 SnapServer 4200/4500 Status and Drive Light Behavior The server has two status lights, two network lights, and two lights for each of the four disk drives, as shown in the following illustration: Overland Storage recommends that you become familiar with the operation of these lights.
Page 208 The Meaning of LED Indicators System LED Blinking amber during normal operation Blinking amber and green LAN 1 and LAN 2 LEDs Solid green Disk Drive LEDs Disk drive LEDs on these SnapServers are located at the base of the bezel. The left light indicates drive status.
Page 209 SnapServer 18000 Status and Drive Light Behavior The server has two status lights, two network lights, and two lights for each of the eight disk drives, as shown in the following illustration: Power, System, and LAN LEDs Looking at the server from the front, the lights appear in the following order, from left to right: power LED, system LED, LAN 1 (Ethernet1) LED, and LAN 2 (Ethernet2) LED.
Page 210 The Meaning of LED Indicators LAN 1 and LAN 2 LEDs Solid green Disk Drive LEDs Disk drive LEDs on the SnapServer 18000 are located on the bezel to the right of the LED display. The left light indicates drive status. The right light indicates drive activity.
Page 211 The Meaning of LED Indicators Fan Module LED Indicator Lights The SnapServer has no external LEDs that indicate the status of a fan module. The screen of the Administration Tool indicates when a fan has Monitoring > Status failed. When the cover of the chassis is removed, the Fault LED on the failed module will be lit.
Page 212 The Meaning of LED Indicators Snap Expansion S50 Enclosure, Disk Drive, APC Module, and Controller Behavior This section describes the LED indicators on the Snap Expansion S50 enclosure, disk drives, and APC modules. Enclosure LEDs On the right front of the Snap Expansion S50 (as shown in the following illustration) are four LEDs that indicate the status of the enclosure.
Page 213 These LEDs operate as described in the following table: Condition Solid green Solid amber Solid green Green random flash APC Unit LEDs Each APC unit has two LEDs that indicate status. These LEDs operate as described in the following table: Condition Power Green (solid)
Page 214 The Meaning of LED Indicators Controller LEDs The controller has two LEDs that indicate status. Fault LED (yellow) These LEDs operate as described in the following table: Condition Master Fault On 5-10 seconds only On continuously Snap Disk 10 Disk Drive and Power Supply Module LEDs This section describes the LED indicators on the Snap Disk 10’s disk drives and power module.
Page 215 The LEDs operate as described in the following table: Drive Status Drive Activity Green Amber, flashing Green Not lit Amber Not Lit Not Lit Not Lit Power Module LED The Snap Disk 10 power module has a single LED. The LED operates as described in the following table: Power Light Condition of Disk Drive...
Page 216 The Meaning of LED Indicators Snap Disk 30SA Disk Drive and Power/Fan Module Behavior This section describes the LED indicators on the Snap Disk 30SA disk drives and power /fan modules. Disk Drive LEDs The Snap Disk 30SA has two LEDs at the edge of each disk drive as shown in the following illustration.
Page 217 Power and Fan Module LEDs The Power/Fan module has four LED indicators as shown in the following illustration. To remove the module, squeeze the two latches on the handle together and then withdraw the module by pulling the handle towards you. Fan Fault Power The LEDs operate as described in the following table:...
Page 218 The Meaning of LED Indicators Ops Panel LEDs The SD30SA Ops Panel has six LEDs, which are shown in the following illustration. The LEDs operate as follows: Invalid Address Power On System Fault PSU Fault Hub Mode 2GB Link Speed SnapServer Administrator Guide Normal Status Fault Flashing...
Page 219: System Reset Options
System Reset Options Often the first thing to try in resolving anomalous behavior on a SnapServer is to reset the server to factory defaults. This section provides information about the following ways to reinstall or reset the system defaults. • Maintenance Mode •...
Page 220: Performing System Resets Without Network Access
System Reset Options When the server finishes rebooting, the Login dialog box opens. Enter the default admin password of you to reset the server name, admin password, and IP address. • Reset To Default ACLs For Volume security on selected volumes. Volumes and snaptrees are all set to the Windows/ Mixed security model.
Page 221: Networking Issues
Networking Issues These are some of the networking issues you may encounter when using your SnapServer. The Server Cannot Be Accessed over the Network Inaccessibility may be caused by a number of reasons. To resolve this issue, use one of the following methods: •...
Page 222 Networking Issues The SnapServer Does Not Operate Properly on a Network Running Gigabit- Full-Duplex For Gigabit Ethernet to operate properly, both the switch and the SnapServer’s primary Ethernet port must be set to Auto (autonegotiate). Any other setting will result in unexpected behavior and reduced performance. The Network Does Not Have a DHCP Server and the SnapServer IP Address Is Unknown Install SnapServer Manager from the SnapServer User CD onto a client workstation...
Page 223 Networking Issues port on the SnapServer. To resolve this problem, verify that all settings (if using multiple Ethernet ports) on the switch/hub match the setting on the server. When the server is shipped from the factory, both ports are set to autonegotiate. Therefore, the switch/hub must be set to autonegotiate to initially connect to the server.
Page 224: Miscellaneous Issues
Miscellaneous Issues You Cannot Log in as Root to the SnapServer GuardianOS allows you to log in as root over SMB. If this operation has failed or you have trouble logging in, be sure that you have enabled root login in the page.
Page 225: Other Issues
NetVault client application may not be able to connect to the NetVault for GuardianOS server running on the SnapServer. To resolve this issue, simply disable and then re-enable the NetVault for GuardianOS Server via the screen. BakBone NetVault BakBone NetVault Restore Limitations for UNIX SnapTrees File and directory permissions will be restored when using BakBone NetVault.
Page 226: Phone Home Support
Phone Home Support Problems with Cable Arm on the 18000 with a SCSI Cable Attached The size of the connector on an attached SCSI cable may prevent the 18000 from fully withdrawing into a rack when the cable management arm is attached. To resolve this problem, remove the cable management arm.
Page 227 listed in the Recipient(s) field populates the Admin Email Address field on the Support screen. Complete the following fields as appropriate, then click Text Field Description Subject (Required) Enter a concise description that identifies the issue. Case (Required) Select New Case if you are emailing technical support for the first time.
Page 228 Phone Home Support SnapServer Administrator Guide...
Page 229: Appendix D Guardianos Ports
GuardianOS Ports The following table outlines the ports used in the GuardianOS. Port # Layer GOS Feature TCP & UDP Network > Apple Network > Apple TCP & UDP Network > FTP TCP & UDP Server > SSH TCP & UDP Server > Email Notification TCP &...
Page 230 Port # Layer TCP & UDP Network > NFS TCP & UDP • Networking > NFS TCP & UDP Server > Date/Time > TCP & UDP Network > Windows TCP & UDP Network > Windows TCP & UDP Network > Windows TCP &...
Page 231 Port # Layer GOS Feature TCP & UDP • WebUI • SnapServer Manager • SnapExtension > Snap TCP & UDP Network > Windows Server > Printing TCP & UDP Network > Apple TCP & UDP Server > Printing Network > NFS •...
Page 232 Port # Layer 3205 3260 8001 8002 8003 8005 8008 TCP & UDP Web UI 9049 9050 10000 10001 12000 TCP & UDP Network > Apple 12168 16384 16388 20031 24066 32780 32781 49221 49229 1024 - TCP & UDP • Network > NFS 65535 SnapServer Administrator Guide GOS Feature...
Page 233: Glossary
Term access permissions ACL (Access Control List) Administration Tool ADS (Active Directory Service) AFP (AppleTalk Filing Protocol) agent algorithm AllLocalUsers group AllUsers group array Definition A rule associated with a share, a file, or a directory to regulate which users can have access to the share and in what manner.
Page 234 Term authentication autonegotiation autosensing bonding CA eTrust Antivirus chaining channel CHAP (Challenge Handshake Authentication Protocol) checksum CIFS (Common Internet File System) The default Windows protocol for communication between daemon default gateway degraded DHCP (Dynamic Host Configuration Protocol) SnapServer Administrator Guide Definition The validation of a user’s identity by requiring the user to provide a registered login name and corresponding...
Page 235 Term directory disaster recovery disk DNS server (Domain Name System server) domain domain name Ethernet Ethernet address Ethernet port event Definition A virtual folder used to organize files. Also called a folder. A strategy that allows a company to return to normal activities after a catastrophic interruption.
Page 236 Term failover FTP (File Transfer Protocol) full-duplex gateway GID (group IDs) GuardianOSImage.gsu half-duplex hidden share host name hot spare (local or global) hot swapping HTTP (Hypertext Transfer Protocol) SnapServer Administrator Guide Definition A strategy that enables one Ethernet port to assume the role of another port if the first port fails.
Page 237 Term HTTPS (Hypertext Transfer Protocol Secure) I/O (Input/Output) Inheritance IP (Internet Protocol) address iSCSI (Internet SCSI) Jukebox JVM (Java Virtual Machine) Kerberos LCD (Liquid Crystal Display) Definition The HTTP protocol using a Secure Sockets Layer (SSL). SSL provides data encryption, server authentication, message integrity, and client authentication for any TCP/IP connection.
Page 238 Term LED (Light-Emitting Diode) Linux load balancing local group/local user MAC (Media Access Control) maintenance mode MIB (Management Information Base) mirroring mounted multihomed SnapServer Administrator Guide Definition An electronic device that lights up when electricity is passed through it. A UNIX-like operating system that was designed to provide personal computer users a free or very low-cost operating system comparable to traditional and usually more expensive UNIX systems.
Page 239 Term NAS (Network Attached Storage) NetVault for GuardianOS NFS (Network File System) NIS (Network Information Service) node NVDB (NetVault Database) directory A NetVault for GuardianOS database directory stored on the orphan parity Permissions PoP (Proof of Purchase) Definition Hard disk storage that is set up with its own network address as opposed to being attached to the department computer that is serving applications to a network's workstation users.
Page 240 Term POSIX (Portable Operating System Interface) protocol public access share quota RAID (Redundant Array of Independent Disks) RAID 0 (Striped) RAID 1 (Mirrored) RAID 5 (Striping with Parity) RAID 6 (Striping with Dual Parity) SnapServer Administrator Guide Definition A set of standard operating system interfaces based on the UNIX operating system.
Page 241 Term RAID 10 (Striped Mirroring) recurring snapshot restrict anonymous resynchronization rollback SCSI (Small Computer System Interface) serial number server number share share access SMB (Server Message Block) Definition RAID 10 is two or more RAID 1’s striped together to provide greater redundancy and higher performance than a simple RAID 1.
Page 242 Term Snap EDR SnapServer Manager (SSM) SnapDRImage SnapExtension snapshot snapshot pool snapshot share SnapTree Directory SNMP (Simple Network Management Protocol) SSH (secure shell) SSL (Secure Sockets Layer) SnapServer Administrator Guide Definition A SnapExtension that copies the contents of a share from one SnapServer to another share on one or more SnapServers.
Page 243 Term standalone static IP address striping subnet mask TCP/IP (Transmission Control Protocol/Internet Protocol) trap UI (User Interface) UID (User IDs) unassigned UNC (Universal Naming Convention) UPS (Uninterruptable Power Supply) A device that allows a computer to keep running for a short URL (Uniform Resource Locator) Definition A network bonding mode which treats each port as a...
Page 244 Term Virtual Disk Service (VDS) volume Volume Shadow Copy Service (VSS) Microsoft VSS provides a mechanism for creating consistent Web View Windows domain authentication WINS (Windows Internet Naming Service) workgroup SnapServer Administrator Guide Definition Microsoft VDS is a service that extends existing storage capabilities of Windows Server operating systems.
Page 245: Index
Symbols .os_private 116 Access network access to the server 21 problems with 202 users and groups 43 Windows ACLs 105 Access Denied Message 202 ACLs defined 213 backing up 116 resetting to defaults 201 setting file-level permissions (Windows) Active Directory defined 213 and name resolution servers 30 SnapServer interoperability with 32...
Page 246 CA BrightStor ARCserve, installing agent CA eTrust Antivirus, see Antivirus Cable management arm 207 Chooser, see MacintoshOS Client access, configuring Apple 35 FTP 37 HTTPS/HTTP 38 NFS 34 Cloning a server 122 Command Line Interface 165 Running Scripts 175 Syntax 165 Connecting to SnapServers 14 Converting to 137...
Page 247 GuardianOS and re-enabling antivirus software 124 specifications 2 GuardianOS Ports 209 Hardware Components, purchasing new Hidden Shares 102 Host File Editor 150 Hot spares 52 Hot swapping automatic incorporation 53 disk drives 68 HTTPS/HTTP configuring 38 Initial Setup Wizard 16 IP address setting 25 using SSM to discover 15...
Page 248 Networking problems with access 202 reset to factory defaults 200 NFS access configuring 34 supported clients and protocols 35 to hidden shares 102 NFS exports file 93 Operating system, see GuardianOS Password default for admin account 44 Paths for backing up snapshots 114 for distributing antivirus updates 131 for restoring a "cured"...
Page 249 Server registration via Initial Setup Wizard 17 Setup wizard, see Initial Setup Wizard Shared-hub configurations 27 Shares backing up configuration 116 hidden 102 snapshot shares 102 Single-subnet configuration 27 Snap Disk 10 troubleshooting connectivity 205 SnapCLI 165 Running Scripts 175 Syntax 165 SnapDRImage 116 SnapServer Manager 12...
Page 250 effect of deleting on antivirus software 124 expanding capacity of 57 management tools 59 using quotas to control usage 60 Wake-on-LAN Support 20 Web Server 38 Web View 39 WebRoot 38 SnapServer Administrator Guide Windows 142 connecting from a client 33 file and folder name support 30 guest account access 32 issues with master browser 204...

Adaptec 5325301507 Administrator's Manual

Preface

Chapter 1 Administrative Overview

Chapter 2 Network Access to the Server

Chapter 3 User & Group Management

Chapter 4 Storage Configuration and Expansion

Chapter 5 Iscsi Disks

Chapter 6 Share and File Access

Chapter 7 Snapshots

Chapter 8 Disaster Recovery

Chapter 9 CA Etrust Antivirus Software

Chapter 10 Unicode

Appendix A Backup and Replication Solutions

Appendix B Command Line Interface

Appendix C Troubleshooting Snapservers

Appendix D Guardianos Ports

Glossary

Index

Quick Links

Need help?

Questions and answers

Related Manuals for Adaptec 5325301507

Summary of Contents for Adaptec 5325301507

Table of Contents