Administrator Guide GuardianOS v6.0 For GuardianOS-powered SnapServers and Expansion Arrays 10400272-001 www.overlandstorage.
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. The software may be used only in accordance with the terms of the license agreement. It is against the law to copy the software on any medium.
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 EMBEDDE
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. 5 Ownership of Restricted Software.
COMPUTER ASSOCIATES INTERNATIONAL, INC. ("CA") ETRUST ANTIVIRUS 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. 1 CA PROVIDES YOU WITH ONE COPY OF THE PROGRAM AND LICENSES THE PROGRAM TO YOU PURSUANT TO THE TERMS OF THIS AGREEMENT. a.
Contents Preface ................................................................................... xiii Chapter 1 Administrative Overview ....................................................................1 GuardianOS Specifications .................................................................... 2 What’s New in GuardianOS .................................................................. 6 SnapServer Manager...........................................................................
Apple Networking Configuration .........................................................34 FTP/FTPS Access..................................................................................36 HTTP/HTTPS Access .............................................................................37 DHCP Server .......................................................................................39 Print Server .........................................................................................
Chapter 6 Share and File Access ........................................................................95 Configuring Share and Folder Security Overview................................... 96 Components and Options..................................................................... 99 SnapTrees and Security Models ...................................................... 100 ID Mapping ...................................................................................... 102 Shares .........................
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 ......................
Appendix C Troubleshooting SnapServers ........................................................181 The Meaning of LED Indicators .......................................................... 182 System Reset Options ........................................................................ 203 Networking Issues ............................................................................ 205 Miscellaneous Issues .......................................................................... 208 Phone Home Support ....
xii SnapServer Administrator Guide
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.
Typographical Conventions Convention Usage Italic • Emphasis • The introduction of new terms • File names • Settings you select or enter in the Administration Tool Arial Bold Navigational paths, command buttons, and navigational links.
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 Content Quick Start Guide Details package contents, identifies server hardware components, and provides complete instructions for installing the server to a rack and connecting the server to the network. Also contains the EULA and warranty.
xvi SnapServer Administrator Guide
Chapter 1 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.
GuardianOS Specifications Snap Unit Description SnapServer EXP E2000 The SnapServer EXP E2000 is a 2U expansion array with 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. Snap Expansion S50 The Snap Expansion S50 is a 2U expansion array with up to up to 12 hot-swappable SAS or SATA disk drives. It can be used to expand the capacity of the SnapServers 520, 550, 620, 650, 4500, and 18000.
GuardianOS Specifications Feature Specification Server Emulation Windows 2000/2003/2008/NT 4 AppleShare 6.
GuardianOS Specifications Feature Specification System Management 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 Email event notification and SNMP trap notification Data migration 4 SnapServer Administrator Guide
GuardianOS Specifications Feature Specification RAID Options 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. Note Available only on systems with two (2) or more drives. RAID 5 (drive striping with parity): For each array, the size of one drive is reserved for parity.
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 New Functionality Support for Multiple Ethernet With the installation of an Ethernet card, the SnapServer Ports NAS N2000 supports up to 6 ethernet ports. Write Cache Option Write cache can now be disabled on a volume, allowing data to be written directly to the disk.
What’s New in GuardianOS Feature New Functionality User Interface Enhancements The User Interface now comes in three color schemes: green slate, azure sea, and golden desert. Windows 2008 Domain Support Windows domains hosted by Windows 2008 servers are now supported. Support for 128-bit SMB Encryption GuardianOS now supports 128-bit encrypted communcation with SMB clients and servers.
What’s New in GuardianOS What’s New in GuardianOS v5.0 GuardianOS 5.0 has the following new features and functionality Feature New Functionality Improved system performance Improved memory management, resulting in reduced swap utilization, which improves overall performance of the operating system. Enhanced Windows security and permissions compatibility File system access control lists (ACL) now follow the Windows NTFS security paradigm for assignment and enforcement of file system permissions.
What’s New in GuardianOS What’s New in GuardianOS v4.4 GuardianOS 4.4 has the following new features and functionality Feature New Functionality Data Migration utility Utility that allows you to migrate data from any server or workstation supporting CIFS or NFS to a SnapServer. Command Line Interface Support for performing certain GuardianOS functions using a command line shell rather than the GUI.
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 New Functionality Enhanced NFS client support Additional NFS client code page option for UTF-8 in in Unicode mode Unicode mode, supporting the default client character set of many Linux/Unix distributions.. Upgrade of NetVault Bakbone NetVault Bakbone has been upgraded from v7.1.1 to v7.4 Improved Snap EDR support Snap EDR is now pre-installed at the factory.
What’s New in GuardianOS What’s New in GuardianOS v4.0 Note Starting with GuardianOS v4.0, Backup Express is no longer supported. GuardianOS v4.0 introduced the following notable changes to the web admnistration interface: Feature (pre-4.0) New (4.0) Functionality Add-on Features Add-on and 3rd-party features are now managed together on the SnapExtensions page, accessible from the home page’s Site Map or by clicking the SnapExtensions icon in the upper right corner of the Administration tool.
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.
SnapServer Manager Launching SnapServer Manager Launch SSM using one of the methods described in the following table: Operating System Procedure Microsoft Windows NT/XP/ 2000/2003/Vista/2008/7 Click Start. Point to Programs (or All Programs)> SnapServer Manager, then select SnapServer Manager. Macintosh v10.2 or higher Open the SnapServer Manager folder and double-click the SnapServer Manager icon. UNIX/Linux For default options: cd to home directory, then run the SnapServer Manager command: .
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. 1 Start SSM and select the GuardianOS servers to be licensed. 2 Navigate to Administration > Feature Licensing. If you have not already obtained your licenses, in the License Required dialog box, select Click here to purchase SnapExtension license keys at www.
Connecting to the Server for the First Time 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. • On the SnapServer 110 or 210, the label is on the underside of the chassis. • To obtain the server number for SnapServer 4200 and 4500, remove the front bezel to read the label. 2 Connect to the server.
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.
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. Approximately 20% of the default volume is allocated for snapshot use.
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. • The four disks when joined in a RAID 5 configuration net 720 GB of capacity for the RAID. • The snapshot space is 20% of the space available on the RAID, reducing the space on the RAID for the data volume by 144 GB.
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. For more information, see “Data Migration” on page 61.
SnapExtensions SnapExtensions SnapExtensions are software applications, agents, and utilities that extend the capabilities of a SnapServer. Some SnapExtensions are fully functional out-of-thebox; 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. To access SnapExtensions, click the SnapExtensions administration web UI.
Chapter 2 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. Network bonding options allow you to configure the SnapServer for load balancing and failover. Network protocols control which network clients can access the server.
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 The name of the ethernet interface (e.g., Ethernet1) Enabled Yes or no TCP/IP Settings Obtained from DHCP or Static IP Address The unique 32-bit value that identifies the server on a network subnet.
TCP/IP Options DNS Information Domain Name The ASCII name that identifies the internet domain for a group of computers within a network. Primary DNS The IP address of the primary Domain Name System server that maintains the list of all host names. Secondary DNS #1 Secondary Domain Name System server #1 Secondary DNS #2 Secondary Domain Name System server #2 TCP/IP Options GuardianOS SnapServers ship with one or more Gigabit Ethernet (GbE) ports.
TCP/IP Options Option Enable Ethernet Setting Description Switch Trunking This mode groups multiple physical Ethernet links to create one logical interface. Provides high fault tolerance and fast performance between switches, routers, and servers. 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.
Configuring TCP/IP Settings Configuring TCP/IP Settings TCP/IP settings are configured on the Network > TCP/IP screen of 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. Status • OK—Port is connected and active.
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.
Configuring TCP/IP Settings 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. • Hubs do not support Gigabit speeds. Attempting to force a Gigabit setting when the SnapServer is cabled to a hub will produce unintended consequences.
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 Comments Windows (CIFS/ SMB) Enabled Allows access to Windows clients via the workgroup Workgroup.
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.
Windows Networking Configuration still see these shares. To completely hide shares from visibility from any protocols, the Security > Shares screen gives you access to a separate and distinct Hidden 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. To hide shares from NFS clients, consider disabling NFS access on hidden shares).
Windows Networking Configuration 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. The SnapServer supports the Microsoft Windows implementation of Kerberos.
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 Network > server_name. • For Microsoft Windows 2003, 2000, Me, or XP clients, navigate to My Network Places > workgroup_name > server_name.
NFS Access 2 Select a share (called a volume on the Mac) to mount on your desktop. a 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 Authenticate to log in as a different user. A network icon should appear on your desktop for the share. b If a user login prompt displays, enter a username and password. Once authenticated, the share selection dialog box will be displayed.
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 Source NFS 2.0, 3.0, 4.0* RFC 1094, RFC 1813, RFC 3530 Mount 1.0, 2.0, 3.0 RFC 1094 Appendix A, RFC 1813, RFC 3530 Lockd 1.0, 4.0 RFC 1094, RFC1813, RFC 3530 * NFS v4 ACLs are not supported.
Apple Networking Configuration 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. Note Unlike standard AppleShare servers, SnapServers allow nested shares (folders within folders).
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 Network > FTP screen of 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.
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 Network > Web screen of the Administration Tool. Additionally, you can require browser-based clients to authenticate to the server.
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.
DHCP Server DHCP Server DHCP server settings are configured on the Network > DHCP screen of 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. You may negatively impact the network if you enable the SnapServer as a DHCP server while another server on the network is performing this function.
Print Server Adding the Network Printer to the Client The SnapServer supports both Windows SMB and IPP printing protocols. Note To make printer drivers easily accessible to users, copy them to a share that everyone can access on the SnapServer. The SnapServer cannot be configured to automatically provide printer drivers to clients. Adding the Network Printer to a Windows Client Windows offers several methods for adding a printer.
Print Server 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 name of the printer. Note 631 is the IPP port number.
Print Server 42 SnapServer Administrator Guide
Chapter 3 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.
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. The default users and groups listed below cannot be modified or deleted.
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. The NIS user ID ‘nobody’ (UID 65534) is reserved.
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.
NIS Domain NIS Domain NIS domains are configured on the Network > NIS screen of the Administration Tool. 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. Changes you make on the NIS server do not immediately appear on the SnapServer; it may take up to 10 minutes for changes to be replicated.
NIS Domain 48 SnapServer Administrator Guide
Chapter 4 Storage Configuration and Expansion Note Much of the configuration discussion presented here is not applicable to 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.
Default Storage Configuration Default Storage Configuration Drives / RAID 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. The data space is preconfigured to allocate 80 percent of the RAID for the file system and the remaining 20 percent for snapshots.
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.
RAIDs drives as a hot spare. The following table summarizes the advantages and disadvantages of each type of RAID.
RAIDs 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: 1 If a local hot spare dedicated to the RAID exists, use the local hot spare.
RAIDs The background disk scan is enabled by default. To disable the background disk scan, go to the Storage > RAID Sets screen and click the RAID Settings button. 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. • The background scan will not run on RAIDs that are degraded, syncing, or rebuilding.
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.
Volumes Volumes Volumes are created, viewed, edited, and deleted from the Storage > Volumes screen 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. Consider the following facts and guidelines when planning your new volume configuration.
Volumes a RAID or the volume. To reconfigure the antivirus software, click Configure eTrust 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 Snap EDR link in the Site Map (under Extras) and click the Start button.
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 Note Not related to write cache on iSCSI disks. For information about configuring write cache on iSCSI disks, see “Write-Cache Options with iSCSI Disks” on page 89. By default, write cache is enabled on all volumes.
Volumes Volume Management Tools The SnapServer offers several tools for monitoring and controlling how storage space on a volume is used. Function Navigation Path Ongoing Maintenance Navigate to the Storage > Volumes screen, from which you can create, view, edit, and delete volumes. Email Notification The server can notify you when a volume is full. This allows you to increase volume size or take other actions to ensure workflows are not disrupted (Server > Email Notification).
Quotas To start the filesystem check, select the level and click Check Filesystem. The progress of the filesystem check will be displayed while it runs. You can view a log of the filesystem check by clicking View Log. Quotas Quotas are configured in the Storage > Quotas screen of the Administration Tool. Assigning quotas ensures that no one user or group consumes a disproportionate amount of volume capacity.
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). To access the Data Migration utility, navigate to Maintenance > Data Migration. If an error is encountered during migration (e.g.
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). • Certain built-in Windows users and groups.
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. Note Local users that have UNIX permissions on the source will not be created 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. Expansion Arrays Note This section only applies to SnapServer models that can attach an expansion array.
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. Up to seven Snap Expansion S50s can be connected to a SnapServer 520, 550, 620, 650, or 18000. Up to three Snap Expansion S50s can be connected to a SnapServer 4500.
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. The Storage > Disks/Units screen displays the head unit and any expansion arrays attached to the head unit. For more information about the Disk/Units screen, please see “Disks and Units” on page 67. The disk drives of an expansion array are completely integrated into the host SnapServer’s logic.
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. SnapServer disk drives contain GuardianOS-specific data that is lacking on expansion array disk drives.
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. • Click a RAID set name to view or edit the RAID set. • Click a disk icon to view disk details. • Click a unit’s LED icon to flash the unit’s LEDs for identification. Note The LEDs will continue to flash for five minutes.
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. How RAIDs React to Disk Drive Additions • RAID 0 (nonredundant) — You cannot add a drive to a RAID 0. To reconfigure a RAID 0, you must delete the RAID and then recreate it.
Disks and Units Unsupported Disk Drive Combinations Do not include disk drives with different rotational speeeds in the same column. Do not include a column of drives with one rotational speed between a column of drives with a different rotational speed. To Add New Disk Drives to Increase Capacity on a SnapServer N2000 or E2000 1 Review the Recommended Disk Drive Configurations and Unsupported Disk Drive Combinations, and determine which drive slots to populate with new 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. This solution assures that client access to file systems is not interrupted.
Disks and Units 3 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. 4 With the drive carrier lever open, slide the new drive into the chassis. 5 Once the drive is pushed all the way into the chassis, close the drive carrier lever and press until it locks into place. 6 Replace the bezel by sliding the pegs on the right side of the bezel into the holes in the chassis.
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. 1 Remove the front bezel by pressing in the latches on each side of the bezel and pulling the bezel away from the chassis. 2 On the closed handle of the failed disk drive, insert your finger into the handle slot and pull out to open the handle. 3 Pull to remove the drive from the chassis. 4 Open the handle of the new drive.
Disks and Units 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. 1 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. 2 On the closed handle of the failed disk drive, press the button in and to the left to release the latch.
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. 1 Remove the front bezel. With a hand on each latch, slide both latches on the front bezel toward the center. While holding the latch in the release position, pull the bezel away from the chassis. 2 On the closed handle of the failed disk drive, press the latch to the right.
Disks and Units 3 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. Latch 4 Close the font panel. Replacing a Disk Drive on an SD30SA When the status LED is green and the fault LED is amber, the drive has failed or is not working properly.
Disks and Units 3 Grasp the handle and remove the failed disk drive by pulling it towards you. 4 To insert a new disk drive, release the carrier handle by pressing the latch and insert the carrier all the way into the enclosure. 5 Once the carrier is in the enclosure, close the handle until you hear a click. 6 Using the Torx driver, lock the carrier into place by turning the lock screw clockwise until the red padlock icon is visible.
Chapter 5 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.
Configuring iSCSI Initiators • The SANSurfer iSCSI HBA CLI Application Users Guide: This document is available for download on the QLogic web site at http://support.qlogic.com/ 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. • The Novell NetWare Administrator’s Guide: This document is available for download on the Novell web site.
Configuring iSCSI Initiators 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: • On pre-Vista operating systems, Microsoft does not support "dynamic" disks for use with the Microsoft iSCSI initiator.
Configuring iSCSI Initiators system reboots box to make this a persistent target, then click OK to log in to the SnapServer target. 3 Use the Disk Administrator to configure all volumes on top of the disks. 4 From the Bound Volumes/Devices tab on the Property dialog box, click Bind All to allow the iSCSI service to configure the list of persistent volumes.
Configuring iSCSI Initiators 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 Microsoft Knowledgebase article #870964.
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 preVista operating systems is not supported by Microsoft. For more information, see the Microsoft iSCSI Software Initiator User’s Guide, available on the Microsoft web site (uguide.doc).
Configuring iSCSI Initiators 4 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. Note If you have not disconnected from the iSCSI disk at the host, you will be unable to proceed to the configuration page.
Configuring iSCSI Initiators 6 Identify the specific volume you are expanding. 7 Enter: select disk n where n is the disk number that Diskpart indicated from the list command. 8 Enter: select Volume n where n is the volume number that Diskpart indicated from the list command. 9 Enter extend size=n where n is the number of megabytes you want to expand the disk.
Configuring iSCSI Initiators 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.
Configuring iSCSI Initiators In System B's /etc/iscsi.conf, enter the following: 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: • NetWare 6.
Configuring iSCSI Initiators 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. Using the VI Client to Configure iSCSI Services Follow the instructions in the VMware Server Configuration Guide, available from http://www.vmware.com to configure your iSCSI service.
iSCSI Configuration on the SnapServer iSCSI Configuration on the SnapServer iSCSI disks are created on the Storage > iSCSI screen of the Administration Tool. Before setting up iSCSI disks on your SnapServer, carefully review the following information.
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. Data corruption becomes possible when multiple initiators write to the same disk in an uncontrolled fashion. Note GuardianOS v5.
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.
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. For example: iqn.1997-10.com.snapserver:snap123456:iscsi0.000 • The format of IQN names for VDS-based iSCSI disks on the SnapServer is: iqn.1997-10.com.
Creating iSCSI Disks To View iSCSI Disk Status Information You can view iSCSI disk status information from the Storage > iSCSI screen. Label Description iSCSI Disk Name The name of each iSCSI disk Volume The volume on which the iSCSI disk was created Status Current condition of the iSCSI disk: • OK — The iSCSI disk is online and accessible. • Not Mounted — The iSCSI disk is offline.
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. Note VSS/VDS operations are supported on iSCSI disks created using GuardianOS v5.2 and later. • The VSS hardware provider provides a mechanism for taking applicationconsistent native snapshots of iSCSI disks without performing full application (or system) shutdown.
Configuring VSS/VDS for iSCSI Disks 94 SnapServer Administrator Guide
Chapter 6 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. The SMB and NFS protocols also part ways in their handling of file-level permissions.
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. Systems running GuardianOS are storage appliances dedicated to file services.
Configuring Share and Folder Security Overview • Disable individual protocol access to certain shares by navigating to Security > Shares > Create Share > Advanced Share Properties and enabling/ disabling specific protocols, or by selecting a share, clicking to expand Advanced Share Properties, and enabling/disabling specific protocols.
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.
Components and Options Components and Options Shares are created and share access is granted using the Administration Tool. Filelevel 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 (SnapTrees) Volumes and directories created in the root of a volume have one of two security models: Windows/Mixed or UNIX.
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. Share NFS Access The Administration Tool provides a window into the exports file for defining how a share is exported to NFS clients.
SnapTrees and Security Models SnapTree Functionality The following table describes the behavior of SnapTrees and Security Models. Function Description SnapTree Directory Ownership Default ownership differs according to the method used to create the SnapTree directory: • From the client — For UNIX personality directories, the owner and owning group will be according to the logged-in user.
ID Mapping Function Description SnapTree File System Permissions Security model and permissions differ according to the method used to create the SnapTree directory: • 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. Permissions for directories created by all other protocols will be set by the client (per the client’s umask).
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 Security > Shares screen of the Administration Tool. The shares table lists all of the shares on the SnapServer, and describes the share properties. Guidelines for creating shares are provided below. Be sure to review them before configuring shares on the SnapServer.
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. Hidden Shares A hidden share is hidden from clients connecting from the SMB, HTTP, AFP, and FTP (but not NFS) protocols. For example, assume SHARE1 is set as hidden.
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.
Creating Home Directories Example B: More restrictive share-level access trumps more permissive file-level access. Share Level File Level Result Read-only Read-only access to all directories and files in SHARE1, including where a less restrictive filelevel permission applies. The user has read-only access to FileB.
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. Users are not limited only to their virtual shares; all other shares on the server continue to be accessible in the usual fashion. • For NFS, the home directory is exported.
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. Note Group membership of NFS clients is established by configuring the local 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. Therefore, ACL permissions applied to groups may not apply as expected to NFS clients.
Security Guides To Set File and Directory Permissions and Inheritance (Windows) 1 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. 2 Do one of the following: • In Windows NT, right-click the file or directory, choose Properties, click the Security button, and then select Permissions.
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” on page 30.
Chapter 7 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.
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. For more information, see “Estimating Snapshot Pool Requirements” on page 113.
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” on page 93.
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 screen and clicking the Snapshot Space button, then clicking the Raid Set. On the screen that opens, you can adjust the size of the pool as necessary.
Coordinating Snapshot and Backup Operations read-only), a snapshot share inherits access privileges from its associated livevolume share. Note The same folders appear on the Web View screen when you connect to the SnapServer using a Web browser; however, the snapshot share folder does not provide access to the snapshot; it will always appear to be empty. You can prevent the snapshot share from displaying on this Web View screen by selecting the Hide Snapshot Share option when creating or editing a share.
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. • Offset the snapshot and backup schedules such that the backup does not occur until you are sure the snapshot has been created.
Chapter 8 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.
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).
Backing Up Server and Volume Settings • 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. Use the following procedure to create and secure the disaster recovery files: 1 Create the disaster recovery files.
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.
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: 1 Completely reinstall and configure the same version of the GuardianOS that the server was running.
Recovering the NetVault Database Restore Procedure 1 Access the Restore window from the NetVault GUI by clicking the Restore button in the command toolbar. 2 Double-click the NetVault Server that the desired backup was performed from to open it. 3 Plug-ins (and APMs) used to conduct successful backups on the selected client will be displayed. Double-click the NVDB Plug-in to open it. 4 All of the backup savesets are created using the NVDB Plug-in display.
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. Overland Storage strongly recommends that you contact a technical service representative before proceeding.
Cloning a Server 5 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 Recover Volume Security Settings on the Maintenance > Disaster Recovery screen. Note If you are restoring from any backup other than NetVault, you will need to recover the volume settings. Cloning a Server The Disaster Recovery process can be used to clone a server in order to apply the same configuration to one or more servers.
Chapter 9 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 SnapExtensions > CA Antivirus screen of the Administration Tool.
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 screen. Re-enabling the Antivirus Software The antivirus software is enabled by default.
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 reenable the software. To learn how the antivirus software interacts with other GuardianOS software components, see “Antivirus Dependencies” on page 126.
Scan Job Configuration and Scheduling Component Description Root Directory Displays the directory structure of the SnapServer. As in Windows Explorer, click folder icons to navigate the structure and display subfolders and files in the right-hand pane. Move Folder May contain infected files. The administrator can instruct the software to automatically move infected files to this directory. For more information, see “Scan Job Configuration and Scheduling” on page 128.
Scan Job Configuration and Scheduling 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. Infected files with the same name are given incremental extensions (e.g., FILE.0.AVB, FILE.1.AVB, and so on).
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. 1 In Local Scanner View, select the folders you want to scan. The left-hand pane displays the directory structure of the SnapServer. A red check mark on a folder or file indicates that it is selected for scanning. (By default, all directories and files are selected for scanning.
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. These updates are cumulative, so they contain everything from all previous file updates, plus the newest information on the latest infections.
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 1 Choose Scanner > Signature Update Options. 2 On the Schedule tab, click Enable Scheduled Download.
Signature Updates 5 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. 6 Click OK. The path appears in the list box. 7 Click Download Now.
Signature Updates 3 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. (On a SnapServer, the update files must reside on the root of the share.) 4 Click OK. The path you entered appears in the Download Sources list box. 5 Click Download Now.
Alert Options Verifying Download Events Use the following procedure to verify download and distribution events. 1 Select View > Log Viewer. 2 In the left-hand pane, select Distribution Events. Distribution events are listed in the upper right-hand pane in chronological order. 3 Select a distribution event. The details of the distribution event display in the lower pane.
The Move Directory The Move Directory You can configure scans to move infected files to the move folder (Scanner > Local Scanner options). To view infected files, click the Move directory on the left-hand pane of the Local Scanner View. To manage a moved file, right-click the file and select from the following options: Option Description Restore This option removes the file from the Move Folder and restores it to its original location with its original name and type.
Log View Log View The Log View provides easy access to detailed information on scan, distribution, and other events. To access this view select Log View from the View menu. Option Description Local Scanner Displays summary information about scan jobs that have run. RealTime Scanner Not Supported. Scheduled Scanner Displays summary information on scheduled scans that have run. General Events Displays the Event log for a given day. Click a date to view all events that occurred that day.
Log View 138 SnapServer Administrator Guide
Chapter 10 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 • Unicode and Expansion Arrays What is Unicode? GuardianOS supports Unicode. Unicode defines a universal means of representing characters in all languages.
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 > Unicode and enable Unicode. Once it has been enabled on your SnapServer you cannot disable Unicode. Be sure your settings and data have been saved to an off-server location before enabling Unicode.
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. Please see the following section “Backing Up Unicode Servers” on page 143 for more information.
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. AFP translates MacRoman into UTF8 when writing to SnapServers. Any extended characters on the file system that cannot be translated to MacRoman will also be returned with an escape sequence.
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. CA Antivirus CA Antivirus is not Unicode-aware.
Backing Up Unicode Servers Snap EDR over Sync only EMC Legato Networker v7.3, 7.4 over SMB only CA ARCServe 11.5, 12.0 over SMB only1 Symantec NetBackup 6.5 Symantec Backup Exec 10.d, 11.d, 12.d over SMB only Bakbone NetVault over client1 The following table gives an overview of how Unicode interacts with backup applications: Officially Supports Unicode no no no no no no UI Displays Correct Filenames no yes no no no no Backups and Restores Unicode data yes yes yes yes yes 1.
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.
Unicode and Expansion Arrays Unicode Converted Head Units When a SnapServer is converted to Unicode, it stays converted to Unicode. If a nonUnicode 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. Caution Converting to Unicode is a one-way operation. There is no undoing the conversion to Unicode if you change your mind.
Appendix A 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. Note Enabling Unicode on the server will limit some backup applications’ ability to function with the SnapServer. Refer to “Unicode” on page 139 for more information. GuardianOS (disk-to-tape backup) Symantec Backup Exec 11.d, 12, 12.5 Symantec NetBackup 6.
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: • Near-line storage — The SnapServer manages backup jobs, locally storing the backup images on disk using virtual tape library technology.
Integrated Backup Solutions for the SnapServer You can add multiple workstations by completing the fields and repeatedly selecting the Add 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.
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: 1 Click the Snap EDR link in the Site Map (under Extras). 2 Select either the Configure as the Management Console or Configure as the Agent button. Note If you are configuring the server as an Agent, you must provide the server name or IP Address of the Management Console.
Off-the-Shelf Backup Solutions for the SnapServer Off-the-Shelf Backup Solutions for the SnapServer Note These backup packages do not support the backup of Windows ACLs or 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.
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.
Off-the-Shelf Backup Solutions for the SnapServer 4 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.
Off-the-Shelf Backup Solutions for the SnapServer 7 To unpack the tar file to get the agent files, type the following command and press Enter: tar -zxvf Linux.tar.Z Note If you later delete the volume this directory is on, you will need to reinstall the agent. 8 Determine which volume has the most available space by looking at the Avail column in the volume usage table. cd /hd ls (lists all volumes) df -h (shows volume usage) 9 Change directory to the volume with the most available space.
Off-the-Shelf Backup Solutions for the SnapServer 6 Close the SSH client and return to the Admnistration Tool. To start the newly installed backup agent, navigate to the Maintenance > Shutdown/Restart screen, and click Restart. 7 Delete the agent files you copied to the SnapServer because they are no longer needed. 8 To verify the success of the installation, use your backup management software to configure and run a test backup.
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 1 Connect to the server over SSH. Note SSH v2 is required. If you fail to connect to the server, ensure that your SSH client is configured to connect via SSH v2. 2 Log in as admin (using the password for the admin account). 3 You are placed into the CLI shell. However, a standard Linux shell must be used to install the agent.
Off-the-Shelf Backup Solutions for the SnapServer 9 If CA Antivirus has been installed, you will have an /opt directory. If it has not been installed, create an /opt directory: mkdir /opt 10 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.
Off-the-Shelf Backup Solutions for the SnapServer cli group member add group-name=beoper user-name=root Note If using a local Snap user account other than root or admin, and if password policies are enabled, configure the user to be exempt from password expiration. See “To Set Password Policy for Local Users” on page 68. 5 Start the Backup Exec RALUS agent by rebooting the SnapServer either through the Admin Tool (Maintenance > Restart), or by typing: /etc/rc.d/init.d/VRTSralus.
Off-the-Shelf Backup Solutions for the SnapServer Installing the Symantec NetBackup v6.5 Client Note This procedure assumes that you are using the default SnapServer 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. To install the Symantec NetBackup v6.5 Client, do the following: Prepare the SnapServer 1 Connect to the server over SSH. Note SSH v2 is required.
Off-the-Shelf Backup Solutions for the SnapServer 8 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. 9 Use the host file editor (Maintenance > Host File Editor screen) to add the NetBackup servers to /etc/hosts on the SnapServer. Verify that you can ping the NetBackup server. Install NetBackup v6.
Off-the-Shelf Backup Solutions for the SnapServer 4 Remove the NetBackup services by deleting the files for bpcd, vnetd, vopied, and bpjava-msvc in the /etc/xinetd.d/ directory. 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 5 Restart the SnapServer services by either rebooting or typing: /etc/rc.d/init.
Off-the-Shelf Backup Solutions for the SnapServer 5 Select a volume on which to put a directory called networker. Note If you later delete the volume the networker directory is on, you will need to reinstall the agent. cd /hd ls [lists all the volumes] df -h [shows volume usage] 6 Determine which volume has the most available space by looking at the Avail column in the volume usage table. Change directory to the volume with the most available space.
Off-the-Shelf Backup Solutions for the SnapServer copy the backup to the original using the command cp /etc/profile.nwbk / etc/profile and then edit the file again. 12 To implement the changes, enter the following command: source /etc/profile Install the EMC Legato Networker Client 1 Connect to the SnapServer via SSH, and log in as admin, using your admin user password. Note SSH v2 is required. If you fail to connect to the server, ensure that your SSH client is configured to connect via SSH v2.
Off-the-Shelf Backup Solutions for the SnapServer 11 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. Add the SnapServer as a Root User For backup operations, NetWorker requires that the SnapServer be configured as a root user.
Off-the-Shelf Backup Solutions for the SnapServer Use either the recover or the retrieve command exactly as described below. For more details on these commands, see the EMC Legato Networker Command Reference. 1 Connect to the SnapServer via SSH, and log in using the admin user name and password. Note SSH v2 is required. If you fail to connect to the server, ensure that your SSH client is configured to connect via SSH v2. 2 You are placed into the CLI shell.
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. Windows clients can make backups of VSS-based snapshots of iSCSI disks using VSS-compatible backup applications. See “Backing up an iSCSI Disk using VSS Snapshots” on page 141 for instructions.
Appendix B 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. Note Some administrative tasks must still be performed using the Administration Tool.
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 Descriptions date timezones - list available time zones get - get server date/time set [OPTIONS} - set server date/time - [day=1-31] - day of month - [month=1-12] - month of year - [year=1900-...
SnapCLI Syntax Suppose, instead of date, you entered the command web.
SnapCLI Commands SnapCLI Commands The following table presents a list of the available SnapCLI commands and a brief description of the function of each.
SnapCLI Commands 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 group members get Get a list of the members of a local group group members list List the members of a local group homedirs ge
SnapCLI Commands 172 Command Description iscsi delete Delete an iscsi disk iscsi get Get iscsi disk properties iscsi set Set iscsi disk properties isns get Get configuration settings for iSNS server isns set Set configuration settings for iSNS server jumboframe get Get jumbo frame settings for all interfaces jumboframe list List jumbo frame settings for all interfaces jumboframe set Set jumbo frame settings for all interfaces name get Get the name of the SnapServer name set Set the na
SnapCLI Commands 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 Create a raid set raid delete Delete a raid set raid get Get raid set properties raid add disk Add a disk to a raid set raid remove disk Remove a disk from a raid set raid repair Repair a degraded raid set rai
SnapCLI Commands Command Description share nfsaccess delete Delete NFS access permission of the host for the specified share shutdown Shutdown the SnapServer slidingwindow get Get sliding window settings for a specific interface slidingwindow set Set sliding window settings for a specific interface slidingwindow list List sliding window settings for all interfaces snapex Perform a control operation on the snap extension snapshot create later Create a new snapshot schedule snapshot get Get
SnapCLI Commands 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 Get TCP/IP parameters tcpip set Set TCP/IP parameters.
SnapCLI Commands Command Description volume get Get a specific volume’s properties volume create Create a new logical volume volume edit Edit an existing logical volume volume delete Delete a logical volume volume fscheck Check or repair filesystem volume fscheck-root Repair root filesystem (requires reboot) volume write-cache Enable or disable write cache on a volume.
Scripts in SnapCLI Scripts in SnapCLI Administrative tasks can be automated with shell scripts that call SnapCLI commands. Running a SnapCLI Script 1 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). Avoid using Windows clients to create or edit scripts. • Place the script in a share that will never be part of a delete 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.
Scripts in SnapCLI Add the user to the group # 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" group-name="$2" > /dev/null 2>&1 if [ $? -ne 0 ]; then echo "Adding user '$1' to group '$2' failed.
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 fi else echo "Group '$1P' does not exist." fi return 0 } # usage: 'rmshare ' rmshare() { Delete the share # if the share exists delete it if $CLI share get share-name="$1" > /dev/null 2>&1; then echo "Deleting share '$1' ..." $CLI share delete share-name="$1" > /dev/null 2>&1 if [ $? -ne 0 ]; then echo "Deletion of share '$1' failed.
Appendix C 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 Knowledge Base Search for solutions to specific issues by clicking the Knowledge Base link on the SnapServer support page: http://www.snapserver.
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.
The Meaning of LED Indicators 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. Off The port is disconnected or the Ethernet cable is not connected or linked to an active switch.
The Meaning of LED Indicators Disk LEDs Top LED Off (SATA drive) Disk drive installed properly but is not active Solid Blue (SAS drive) Blinking Blue Disk drive installed properly and is active Bottom LED Solid Red Disk drive error All Drive LEDs (E2000 only) Blinking simultaneously UID identification from Disks/Units page of Admin Tool. Power Supply Module Indicator Lights The LED on a SnapServer N2000 and E2000 power module is identified in the following illustration.
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.
The Meaning of LED Indicators The LEDs operate as described in the following tables: Power LED Solid green The server is powered on. Off The server is powered off. Status LED Blinking green The server is operating normally. Blinking amber A thermal or other system problem was detected. Blinking amber and green The server is in Maintenance Mode. Network LED Solid green The server is active and connected to the network.
The Meaning of LED Indicators 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. The Disk Drive LEDs run along the bottom of the bezel, two LEDs for each disk drive.
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: Power LED System LED LAN LEDs Disk Drive LEDs Unit ID (UID) LED 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.
The Meaning of LED Indicators The LEDs operate as described in the following tables: Power LED Solid green The server is powered on. Off 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 amber at boot time A problem was detected. The server will not boot. Blinking amber during normal operation A thermal or other system problem was detected.
The Meaning of LED Indicators Status LED (left) Activity LED (right) Solid amber Off Disk drive installed, but not working correctly Off Off No disk drive installed Power Supply Module Indicator Lights The LED on a 500/600 Series power module is identified in the following illustration. Status LED Power Description Solid green The module is operating properly. Blinking green The module has failed or is not connected.
The Meaning of LED Indicators 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: Power LED System LED LAN LEDs Disk Drive LEDs 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.
The Meaning of LED Indicators System LED Blinking amber during normal operation A thermal or other system problem was detected Blinking amber and green The server is in Maintenance Mode. LAN 1 and LAN 2 LEDs Solid green The server is active and connected to the network on the network port. Off The port is disconnected or the Ethernet cable is not connected or linked to an active switch. Disk Drive LEDs Disk drive LEDs on these SnapServers are located at the base of the bezel.
The Meaning of LED Indicators 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 LED System LED LAN LEDs 1 2 3 4 Disk Drive LEDs 5 6 7 8 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.
The Meaning of LED Indicators LAN 1 and LAN 2 LEDs Solid green The server is active and connected to the network. Off The port is disconnected; or the Ethernet cable is not connected or linked to an active switch. 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.
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 Monitoring > Status screen of the Administration Tool indicates when a fan has failed. When the cover of the chassis is removed, the Fault LED on the failed module will be lit. The Fault LED of a SnapServer 18000 fan module is identified in the following illustration. To remove a failed fan module, squeeze its handles together and lift the module out of the unit.
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. 1 2 3 4 These LEDs operate as described in the following table: LED Condition Indication 1 On Enclosure power on.
The Meaning of LED Indicators These LEDs operate as described in the following table: LED Condition Indication 1 N/A Not used. 2 Solid green Drive present and OK. Solid amber Drive failed. Off Drive not present Solid green Drive present and idle. Green random flash I/O activity on disk drive. Off Drive not present. 3 APC Unit LEDs Each APC unit has two LEDs that indicate status.
The Meaning of LED Indicators Controller LEDs The controller has two LEDs that indicate status. Master LED (green) Fault LED (yellow) HOST EXP FAULT ! SEP MASTER These LEDs operate as described in the following table: LED Condition Indication Master On Controller is current Master for enclosure. Fault On 5-10 seconds only Enclosure is powering on.
The Meaning of LED Indicators The LEDs operate as described in the following table: Drive Status Drive Activity Condition of Disk Drive Green Amber, flashing Disk drive installed and being accessed Green Not lit Disk drive installed properly but not being accessed Amber Not Lit Disk drive installed, but not working correctly Not Lit Not Lit No disk drive installed Power Module LED The Snap Disk 10 power module has a single LED.
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.
The Meaning of LED Indicators 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.
The Meaning of LED Indicators Ops Panel LEDs The SD30SA Ops Panel has six LEDs, which are shown in the following illustration.
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.
System Reset Options When the server finishes rebooting, the Login dialog box opens. Enter the default admin password of admin, and click OK. The Initial Setup Wizard runs, allowing you to reset the server name, admin password, and IP address. • Reset To Default ACLs For Volume Resets the file and directory security on selected volumes. Volumes and snaptrees are all set to the Windows/ Mixed security model.
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: • Verify that you have the correct IP address of the server, and try to connect again. • Verify that the LED for the primary Ethernet port is lit. (This light indicates network connectivity.
Networking Issues The SnapServer Does Not Operate Properly on a Network Running GigabitFull-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.
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.
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 Network > Windows page. Also note that the root account password is tied to the admin account password. If you cannot log in as root, change the password for the admin account on the Network > Windows screen. Use the admin password to log in as root.
Miscellaneous 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 SnapExtensions > BakBone NetVault screen. BakBone NetVault Restore Limitations for UNIX SnapTrees File and directory permissions will be restored when using BakBone NetVault.
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.
Phone Home Support listed in the Recipient(s) field populates the Admin Email Address field on the Support screen. Complete the following fields as appropriate, then click OK: 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. Select Existing Case if you have previously contacted technical support concerning the issue.
Phone Home Support 212 SnapServer Administrator Guide
Appendix D GuardianOS Ports The following table outlines the ports used in the GuardianOS.
Port # Layer GOS Feature Name Comment 81 TCP WebUI HTTP Hypertext Transport Protocol 88 TCP & UDP Network > NFS Kerberos Kerberos Security (NFS v4) 111 TCP & UDP • Networking > NFS sunrpc Remote Procedure Call (RPC) Protocol for remote command execution, used by Network Filesystem (NFS) and SnapServer Manager • Assist • SnapServer Manager 214 123 TCP & UDP Server > Date/Time > Advanced ntp Network Time Protocol (NTP) 137 TCP & UDP Network > Windows netbios-ns NETBIOS Name Services
Port # Layer 443 GOS Feature TCP & UDP • WebUI Name Comment https Secure Hypertext Transfer Protocol (HTTP). microsoft-ds Server Message Block (SMB) over TCP/IP • SnapServer Manager • SnapExtension > Snap EDR 445 TCP & UDP Network > Windows 515 TCP 548 TCP & UDP Network > Apple 631 TCP & UDP Server > Printing IPP (Internet Printing Protocol)/CUPS (Common UNIX Printing System) 852 TCP Network > NFS Used by rpc.
216 Port # Layer GOS Feature Name 3205 TCP Network > iSCSI iSNS 3260 TCP Network > iSCSI iSCSI 8001 TCP SnapExtension > SnapEDR SnapEDR External Communications 8002 TCP SnapExtension > SnapEDR SnapEDR External Communications 8003 TCP SnapExtension > SnapEDR SnapEDR External Communications 8005 TCP WebUI tomcat Tomcat Shutdown port 8008 TCP & UDP Web UI http-alt Tomcat - Apache Bridge 9049 TCP Sysbroker Sysbroker Shutdown Port 9050 TCP Sysbroker Sysbroker RPC Port
Glossary Term Definition access permissions 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. ACL (Access Control List) The list that controls access to directories and files. Each ACL includes a set of access control entries, which contain the metadata that the system uses to determine access parameters for specified users and groups.
Term Definition authentication The validation of a user’s identity by requiring the user to provide a registered login name and corresponding password. autonegotiation An Ethernet feature that automatically negotiates the fastest Ethernet speed and duplex setting between a port and a hub or switch. This is the default setting and is recommended. autosensing An Ethernet feature that automatically senses the current Ethernet speed setting.
Term Definition directory A virtual folder used to organize files. Also called a folder. disaster recovery A strategy that allows a company to return to normal activities after a catastrophic interruption. Through failover to a parallel system or by restoration of the failed system, disaster recovery restores the system to its normal operating mode.
Term Definition failover A strategy that enables one Ethernet port to assume the role of another port if the first port fails. If a port fails on a SnapServer, the second port assumes its network identity (if the two Ethernet cards have been configured for failover). When the port comes back online, the original identities are restored. Failover is possible only in a multi-Ethernet configuration.
Term Definition HTTPS (Hypertext Transfer Protocol The HTTP protocol using a Secure Sockets Layer (SSL). Secure) SSL provides data encryption, server authentication, message integrity, and client authentication for any TCP/IP connection. I/O (Input/Output) The operation of transferring data to or from a device, typically through an interface protocol like CIFS, NFS, or HTTP. The SnapServer presents a file system to the user and handles block I/O internally to a RAID array.
Term Definition LED (Light-Emitting Diode) An electronic device that lights up when electricity is passed through it. Linux 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. The GuardianOS is based on the Linux operating system. load balancing A process available only in multi-Ethernet configurations.
Term Definition NAS (Network Attached Storage) 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. By removing storage access and its management from the department server, both application programming and files can be served faster because they are not competing for the same processor resources.
Term Definition POSIX (Portable Operating System Interface) A set of standard operating system interfaces based on the UNIX operating system. The need for standardization arose because enterprises using computers wanted to develop programs that could run on multiple platforms without the need to recode. Pre-GuardianOS 5.0 SnapServers use Extended POSIX ACLs. protocol A standardized set of rules that specifies the format, timing, sequencing, and/or error checking for data transmissions.
Term Definition RAID 10 (Striped Mirroring) RAID 10 is two or more RAID 1’s striped together to provide greater redundancy and higher performance than a simple RAID 1. recurring snapshot A snapshot that runs at an administrator-specified time and interval. restrict anonymous A Windows feature in which anonymous users cannot list domain user names and enumerate share names.
Term Definition Snap EDR A SnapExtension that copies the contents of a share from one SnapServer to another share on one or more SnapServers. Snap EDR is designed to work with SnapServers and other SnapServer Storage Solutions. SnapServer Manager (SSM) A Java-based utility for discovering and monitoring SnapServers.
Term Definition standalone A network bonding mode which treats each port as a separate interface. This configuration should be used only in multihomed environments in which network storage resources must reside on two separate subnets. static IP address An IP address defined by the system administrator rather than by an automated system, such as DHCP. The SnapServer allows administrators to use DHCP-assigned or statically assigned IP addresses.
Term Definition Virtual Disk Service (VDS) Microsoft VDS is a service that extends existing storage capabilities of Windows Server operating systems. volume A logical partition of a RAID’s storage space that contains a file system. In the default storage configuration of many SnapServers, eighty percent of the RAID capacity is allocated to the default volume. Volume Shadow Copy Service (VSS) Microsoft VSS provides a mechanism for creating consistent point-in-time copies of data known as shadow copies.
Index Symbols .
C CA BrightStor ARCserve, installing agent 151 CA eTrust Antivirus, see Antivirus Cable management arm 207 Chooser, see MacintoshOS Client access, configuring Apple 35 Disk drives adding 68 automatic incorporation 53 hot swapping 68 replacing 67 Documents e-mail feedback on xiii related to SnapServers xv FTP 37 HTTPS/HTTP 38 NFS 34 Cloning a server 122 Command Line Interface 165 Running Scripts 175 E Ethernet, see Gigabit Ethernet Expand Volume button 57 Exports file, NFS 93 Syntax 165 Connecting to Sna
GuardianOS and re-enabling antivirus software 124 specifications 2 GuardianOS Ports 209 H Hardware Components, purchasing new 179 L LEDs, understanding 180 Legato NetWorker installing agent 159 special backup and restore operations 162 Load balancing configuring server for 25 restrictions on 24 Hidden Shares 102 Local hot spares 52 Host File Editor 150 Login Hot spares 52 to Admin Tool 15 Hot swapping to antivirus GUI 125 automatic incorporation 53 disk drives 68 HTTPS/HTTP configuring 38 M Maci
Networking Deleting a Printer from the SnapServer 42 problems with access 202 IPP port number 41, 42 reset to factory defaults 200 list of supported printers 40 NFS access configuring 34 Monitoring Print Jobs 42 Pausing the Printer 42 supported clients and protocols 35 to hidden shares 102 NFS exports file 93 Q Quotas O assigning and managing 60 backing up configuration 116 Operating system, see GuardianOS P Password default for admin account 44 Paths RAID types defined 220 choosing 51 creatin
Server registration Standalone 27 via Initial Setup Wizard 17 Setup wizard, see Initial Setup Wizard Shared-hub configurations 27 T Shares TCP/IP backing up configuration 116 configuration guidelines 27 hidden 102 configuring 25 snapshot shares 102 options 23 Single-subnet configuration 27 Snap Disk 10 troubleshooting connectivity 205 SnapCLI 165 Technical Support Telephone Numbers xiii Troubleshooting 179 Typographical Conventions xiv Running Scripts 175 Syntax 165 SnapDRImage 116 SnapServer
effect of deleting on antivirus software 124 expanding capacity of 57 Windows 142 connecting from a client 33 management tools 59 file and folder name support 30 using quotas to control usage 60 guest account access 32 issues with master browser 204 W issues with PDC 203 Wake-on-LAN Support 20 restrict_anonymous 32 Web Server 38 see also Active Directory Web View 39 see also Authentication WebRoot 38 234 SnapServer Administrator Guide name resolution server support 30 Windows Client 142
