Page 1 ™ Snap Server Administrator Guide GuardianOS v5.0 For GuardianOS-powered Snap Servers and Expansion Arrays...
Page 3 Information in this document is subject to change without notice and does not represent a commitment on the part of Adaptec 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.
Page 4 Restricted Software, or permit others to do so, except as permitted by applicable law, but then only to the extent that Adaptec (and/or its licensors) is not legally entitled to exclude or limit such rights by contract.
Page 5 You agree to ascertain necessary licensing procedures and obtain required licenses before exporting or re-exporting either. You also agree to indemnify Adaptec and assume all financial responsibility for any losses it may suffer if you do not comply with this paragraph.
Page 6 COMPUTER ASSOCIATES INTERNATIONAL, INC. ("CA") END USER LIMITED LICENSE AGREEMENT (THE "AGREEMENT") CAREFULLY READ THE FOLLOWING TERMS AND CONDITIONS REGARDING YOUR USE OF ETRUST ANTIVIRUS, INCLUDING ITS CODE AND DOCUMENTATION (THE "PROGRAM") BEFORE USING THE PROGRAM. CA PROVIDES YOU WITH ONE COPY OF THE PROGRAM AND LICENSES THE PROGRAM TO YOU PURSUANT TO THE TERMS OF THIS AGREEMENT.
Page 7: Table Of Contents
Preface ...xi Chapter 1 Administrative Overview ...1 GuardianOS Specifications ... 2 What’s New in GuardianOS ... 5 Snap Server Manager... 9 Connecting to the Server for the First Time ... 12 Using the Initial Setup Wizard ... 14 Determining Capacity ... 15 Scheduling Data Protection Tasks...
Page 8 DHCP Server ...34 Print Server ...34 Chapter 3 User & Group Management ... 37 Default User and Group Settings ...38 UID and GID Assignments ...38 Local Users and Groups ...39 NIS Domain ...40 Chapter 4 Storage Configuration and Expansion ... 41 Default Storage Configuration ...42 Changing the Default Storage Configuration ...42 RAIDs ...43...
Page 9 Configuring Share Access ... 88 Creating Home Directories ... 90 Windows ACLs ... 90 Security Guides ... 92 Chapter 7 Snapshots ...95 Snapshot Management and Usage ... 96 Estimating Snapshot Pool Requirements ... 97 Adjusting Snapshot Pool Size ... 98 Accessing Snapshots...
Page 10 Chapter 10 Unicode ... 123 What is Unicode? ...123 Converting to Unicode...123 Unicode and Protocol Interaction...125 How Snapshots Interact with Unicode ...127 Backing Up Unicode Servers...127 Unicode and Expansion Arrays...129 Appendix A Backup and Replication Solutions ... 131 Integrated Backup Solutions for the Snap Server...132 Off-the-Shelf Backup Solutions for the Snap Server ...135 Appendix B Command Line Interface...
Page 11: Preface
Audience and Purpose This guide is intended for system and network administrators charged with installing and maintaining Snap Servers 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 Snap Servers.
Page 12: Typographical Conventions
Typographical Conventions Convention Italic Arial Bold Arial Courier Italic Courier Bold Right-Click Snap Server Administrator Guide Usage • Emphasis • The introduction of new terms • File names • Settings you select or enter in the Administration Tool Navigational paths, command buttons, and navigational links.
Page 13: Finding More Information
Finding More Information Product documentation related to GuardianOS Snap Servers and expansion arrays are listed below. The current versions of all these documents are always available from http://www.snapserver.com/support. Source and Location Quick Start Guide Product Packaging and Web Snap Server Administrator Guide User CD and Web Snap Server Online Help Administration Tool...
Page 14 Source and Location StorAssure Documentation Product packaging and User CD Field Service Documentation Service CD and Web Snap Server Administrator Guide Content Provides instructions for installing StorAssure client backup software. The StorAssure CD includes a User Guide. Provides detailed instructions for the replacement of disk drives, adapter cards, power assemblies, slide rails, and other hardware components.
Page 15: Chapter 1 Administrative Overview
Administrative Overview Snap Servers are designed as flexible, low-maintenance network file servers optimized for performance and efficiency. Snap Servers run the GuardianOS, built to maximize file I/O throughput across multinetwork protocols. To this end, all unnecessary system control and processing functions that are associated with a general-purpose server have been removed.
Page 16: Guardianos Specifications
GuardianOS Specifications GuardianOS Specifications These specifications apply to all Snap Servers and expansion arrays running the most recent version of GuardianOS. Feature Network Transport Protocols TCP/IP Network Block Protocols Network File Protocols Network Client Types Server Emulation Snap Server Administrator Guide Specification UDP/IP AppleTalk...
Page 17 Feature Network Security Data Protection System Management Specification CA eTrust Antivirus software Microsoft Active Directory Service (ADS) (member server) Windows NT Domain (member server) UNIX Network Information Service (NIS) File and Folder Access Control List (ACL) Security for Users and Groups Secure Sockets Layer (SSL v2/3) 128-bit Encryption Target Challenge Handshake Authentication Protocol (CHAP) for iSCSI...
Page 18 GuardianOS Specifications Feature RAID Options DHCP Support Snap Server Administrator Guide Specification RAID 0 (drive striping): Large virtual drive with data striped across all drives of the array to provide maximum performance with no loss in usable capacity. Does not provide data protection.
Page 19: 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 v5.0 GuardianOS 5.0 has the following new features and functionality Feature Improved system performance Enhanced Windows security and permissions compatibility Improved User Interface RAID 6 and RAID 10 support NFS v4 support...
Page 20 What’s New in GuardianOS Feature NTP Server Expanded iSCSI capabilities What’s New in GuardianOS v4.4 GuardianOS 4.4 has the following new features and functionality Feature Data Migration utility Command Line Interface Enhanced Disaster Recovery Support for recovering Snap EDR Management Console Enhanced iSCSI support New OS and browser support Support has been added for Windows Vista, Internet USB tape drive support...
Page 21 Feature Automatic Adjustment for U.S. Daylight Saving Time New Time Zones What’s New in GuardianOS v4.3/4.2 GuardianOS 4.3/4.2 contains the following new functionality: Feature Enhanced NFS client support in Unicode mode Upgrade of NetVault Bakbone NetVault Bakbone has been upgraded from v7.1.1 to v7.4 Improved Snap EDR support Improved UPS support Improved Quotas design...
Page 22 What’s New in GuardianOS What’s New in GuardianOS v4.1 GuardianOS v4.1 introduced the following new functionality: Feature (pre-4.1) RAID Sets System Monitoring What’s New in GuardianOS v4.0 Starting with GuardianOS v4.0, Backup Express is no longer supported. Note GuardianOS v4.0 introduced the following notable changes to the web admnistration interface: Feature (pre-4.0) Add-on Features...
Page 23: Snap Server Manager
Feature (pre-4.0) View all disks (formerly from Storage > Devices page) Share Management Snap Server Manager Snap Server 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 Snap Servers on their network.
Page 24: Installing Ssm
Snap Server Manager Installing SSM You can download and install SSM using the Install_SSM.html file found on your Snap Server User CD. SSM can be installed to all client platforms, including Windows, Macintosh OS X, Linux, and UNIX. If you plan to run SSM on a Macintosh client, you must upgrade the client to MacOS 10.2 or higher (required for JRE 1.4.0 or higher support).
Page 25 • Automatic email notification of completed operations — You can configure SSM to send an operations report (CSV format) upon completion of any operation. Licensing Snap Servers for Use with SSM For multiserver administration of GuardianOS Snap Servers, the purchase of a license for every server is required.
Page 26: Ssm Feature Licensing
Connecting to the Server for the First Time SSM Feature Licensing Use the SSM Feature Licensing menu to apply SnapExtension and SSM license keys to one or more servers. There is no limit to the number of licenses that can be entered using this dialogue box.
Page 27 Connect to the server. In a Web browser, enter the following URL: (where nnnnnn is the server number) http://SNAPnnnnnn Press . The Web View screen opens. Enter Log into the Administration Tool. Click the link, and in the login dialog box, enter admin as the user administration name and admin as the password, and then click Complete the Initial Setup Wizard.
Page 28: Using The Initial Setup Wizard
Using the Initial Setup Wizard Using the Initial Setup Wizard The first time you connect to a Snap Server 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 (Ethernet1), and reclaim the snapshot space that is by default allotted on the volume.
Page 29: Determining Capacity
Determining Capacity • The default gateway IP address • The DNS IP address • WINS server(s) IP address(es) Keeping or Reclaiming the Snapshot Space A Snapshot is a point-in-time image of your volume. This image can be used for backup or recovery purposes. See “Snapshots” on page 95 for detailed information. Approximately 20% of the default volume is allocated for snapshot use.
Page 30: Scheduling Data Protection Tasks
Scheduling Data Protection Tasks • 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. This results in a data volume capacity of 576 GB for this Snap Server 520/1 TB.
Page 31: Configuring The Snap Server As A Print Server
“Print Server” on page 34. Configuring an APC-Brand UPS Adaptec recommends that you use a UPS with Snap Servers and expansion arrays to protect your data from unforeseen power outages. Snap Servers are compatible with USB- and network-based, APC-brand uninterruptible power supplies that allow you to take advantage of the automatic shutdown capability.
Page 32 SnapExtensions Feature Snap EDR Management Console and Agent S2Sv2 - Server to Server Synchronization Manager and Node Snap Server Manager iSCSI Snapshots Snap Server Administrator Guide Description Utility included with your Snap Server that transfers, backs up, and restores files between Windows, UNIX, and GuardianOS systems.
Page 33: Chapter 2 Network Access To The Server
Network Access to the Server Snap Servers are preconfigured to use DHCP, autonegotiate network settings, and allow access to the server for Windows (CIFS/SMB), Unix (NFS), Macintosh (AFP), FTP, and HTTP/HTTPS clients. Discussed next are the options for configuring TCP/IP addressing, network bonding, and access protocols.
Page 34: Viewing Current Network Settings
Viewing Current Network Settings Viewing Current Network Settings The Network > Information screen displays the server's current network settings. One column appears for each Ethernet port. Field definitions are given in the following table: Ethernet Interface Information Port Name Enabled TCP/IP Settings Obtained from IP Address...
Page 35: Tcp/Ip Options
DNS Information Domain Name Primary DNS Secondary DNS #1 Secondary DNS #2 TCP/IP Options GuardianOS Snap Servers ship with Dual Gigabit Ethernet (GbE) ports. Exceptions to this are the Snap Server 110 and 210, which ship with a single Note Gigabit Ethernet port.
Page 36 TCP/IP Options Option Setting Failover Switch Trunking Link Aggregation (802.3ad) Enable Checked Ethernet Unchecked Speed/ Auto duplex Fixed Snap Server Administrator Guide Description This mode uses the first Ethernet port as the primary network interface and the second Ethernet port is held in reserve as the backup interface.
Page 37: Configuring Tcp/Ip Settings
Configuring TCP/IP Settings TCP/IP settings are configured on the Administration Tool. This screen defaults to the current settings for the primary Ethernet port (Ethernet1). Issues in TCP/IP Configuration Consider the following guidelines when connecting a Snap Server to the network. Cabling for Single-Subnet, Multihomed, or Network Bonding Configurations All GuardianOS Snap Servers ship with two Ethernet cables for connecting the server to the network.
Page 38 Configuring TCP/IP Settings Connect the Snap Server to the Network via a Switch While it is possible to connect a Snap Server to the network via a hub, this configuration unduly restricts the performance of the server for the following reasons: •...
Page 39: Default Network Protocol Settings
Default Network Protocol Settings Snap Servers are preconfigured to allow multiplatform access in heterogeneous Windows, UNIX/Linux, and Macintosh environments. The following table summarizes the Snap Server’s default network protocol access configuration. Protocol Default Windows (CIFS/ Enabled SMB) UNIX (NFS) Enabled Apple (AFP) Enabled Enabled...
Page 40: Windows Networking Configuration
Windows Networking Configuration Windows Networking Configuration Windows SMB and security settings are configured on the 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 Snap Server available to SMB clients in the workgroup named Workgroup.
Page 41: Support For Windows Network Authentication
still see these shares. To completely hide shares from visibility from any protocols, screen gives you access to a separate and distinct Hidden Security > Shares share option that hides a share from SMB, AFP, HTTP, HTTPS, and FTP clients (However, shares are not hidden from NFS clients, which cannot connect to shares that aren't visible.
Page 42 (not local) user name and password that the Snap Server can use to communicate with the PDC. For ease of administration, Adaptec recommends that you create a unique user account on the domain using the following guidelines: •...
Page 43 Mapping a Drive in Windows In addition to browsing the network to find the Snap Server and access its shares, you can also connect to your Snap Server by mapping a drive to a share on the server. The procedure to map a drive is essentially the same for all versions of Windows, though some of the names change slightly from version to version (e.g., My Computer in NT/2000/XP vs Computer in Vista).
Page 44: Nfs Access
NFS Access To access files on the server, double-click the icon for the share. A Finder window will display the contents of the share, and your Snap Server will now behave like any other disk on your Mac. To disconnect from the Snap Server, drag its icon into the trash. NFS Access NFS access to the server is enabled on the Administration Tool.
Page 45: Apple Networking Configuration
• Sun Solaris 9, 10 • SuSE Pro 9 • SuSE Linux Enterprise Server (SLES) 8.x, 9.x, 10.x To Enable NFS v4 Access to the Server To enable NFS v4, check the Do not uncheck the Note boxes must be checked for NFS v4 access. Apple Networking Configuration Apple File Protocol (AFP) settings are configured on the the Administration Tool.
Page 46 Apple Networking Configuration Term Definitions Volume A volume on a Snap Server is a logical partition of a RAID’s storage space that contains a file system. Right-click This document uses the Windows convention in describing keyboard/mouse access to context-sensitive menus. For example, “To rename a group, right- click a group and then choose Rename.”...
Page 47: Ftp Access
FTP Access FTP settings are configured on the By default, FTP clients can access the server using the anonymous user account, which is mapped to the Snap Server's guest user account and AllUsers group account. You can set share access and file access for anonymous FTP users by modifying permissions for these accounts.
Page 48: Dhcp Server
DHCP Server DHCP Server DHCP server settings are configured on the Administration Tool. To configure the Snap Server 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.
Page 49: Adding The Network Printer To The Client
Adding the Network Printer to the Client The Snap Server supports both Windows SMB and IPP printing protocols. To make printer drivers easily accessible to users, copy them to a share that Note everyone can access on the Snap Server. The Snap Server cannot be configured to automatically provide printer drivers to clients.
Page 50: Monitoring Print Jobs Using The Administration Tool
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 Snap Server 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 Snap Server and sharename is the...
Page 51: Chapter 3 User & Group Management
User & Group Management Authentication validates a user’s identity by requiring the user to provide a registered login name and corresponding password. Snap Servers 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 Snap Server to a traditional Windows NT or Active Directory domain, and Windows clients can then authenticate to the server using their domain credentials.
Page 52: Default User And Group Settings
Default User and Group Settings Default User and Group Settings Snap Server 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 Snap Server using the Administration Tool.
Page 53: 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 Snap Server will discard any that are less than 101 or are in conflict with UIDs already in use by local or Windows domain users and groups.
Page 54: Nis Domain
For guidelines on integrating compatible Snap Server UIDs, see “UID and GID Assignments” on page 38. NIS identifies users by UID, not user name, and although it is possible to have duplicate user names, Adaptec does not support this configuration. Snap Server Administrator Guide Navigation Path Navigate to the Security >...
Page 55: Chapter 4 Storage Configuration And Expansion
Storage Configuration and Expansion Much of the configuration discussion presented here is not applicable to Snap Note Servers with fewer than four (4) drives. For Snap Server 110 and 210, see the User’s Guide for Snap Server 110 and 210 for storage configuration guidelines. Snap Servers with four or more drives are preconfigured as a single RAID 5, and Snap Server 110 and 210 are preconfigured with a single RAID 0.
Page 56: Default Storage Configuration
Default Storage Configuration Default Storage Configuration Snap Servers with four or more drives are preconfigured as a single RAID 5 and Snap Server 110 and 210 are preconfigured as a single RAID 0. Each server’s disk space has a single volume, and a single share pointing to the volume. The share access settings of the default share grant access to all users and groups over all protocols.
Page 57: Raids
for servers with four or more drives. In cases where multiple expansion arrays are attached to the Snap Server, a combination of a RAID 1 and hot spares may be the optimal configuration for the Snap Server. See the online help for more information. RAIDs RAIDs are created, viewed, edited, and deleted from the of the Administration Tool.
Page 58 RAIDs Local and Global Hot Spares A hot spare is a disk drive that can automatically replace a damaged drive in a RAID 1, 5, 6, or 10. Designating a disk drive as a hot spare helps ensure that data is available at all times.
Page 59: Raid Groups
Background Disk Scan The background disk scan checks the integrity of RAID data by continuously scanning the disk drives for errors. Each RAID (except RAID 0) has its own background disk scan that is set to run when the I/O activity falls to a very low disk activity.
Page 60 RAIDs of a single RAID allows administrators to expand a volume without reconfiguring RAIDs and allows users to continue working as usual with no interruption. Grouped RAIDs must be the same type; you can group two RAID 1s or two RAID 5s (e.g., you cannot group a RAID 1 and a RAID 5).
Page 61: Volumes
Two RAIDs at a Time To group more than two RAIDs, create a RAID group with two RAIDs, then group the RAID group with each RAID one at a time. You can view your RAID group status from either the Storage > RAID Sets or Monitor >...
Page 62 Volumes To retain NVDB information, you must back up the NVDB directory (see page 104) before you delete the volume, create your new storage configuration, and then restore the directory. After creating your new storage configuration, you can reinstall the antivirus software by navigating to the the next screen, check the the antivirus software (using default settings) on the volume with the most...
Page 63: Quotas
A volume can be expanded up to 16 TBs, either as a standalone volume or as a volume group. Security Models, SnapTrees, and Volumes Volumes are created with the Windows security model (which can be changed in Securities > SnapTrees root).
Page 64: Default Quota Assignments
Data Migration Default Quota Assignments For users and groups, there are no pre-assigned default quotas on the Snap Server. When quotas are enabled on the Snap Server, you can assign a default quota for all users, or allow all users to have unlimited space on the volume. Unless you assign individual user or group quotas, all users and groups will receive the default quota.
Page 65: Preserving Permissions
• Preserve the original permissions settings If you elect to preserve original permissions settings, be sure to review Note Preserving Permissions. • Verify migrated data If you elect to verify migrated data, all data will be read twice, once for Note migration and once for comparison to the copied data.
Page 66: Expansion Arrays
This section does not apply to the Snap Server 110 or 210. Note To increase the capacity of a Snap Server, Adaptec offers the SANbloc S50 expansion array. Details on installing a SANbloc S50 are provided in the Quick Start Guide that comes packaged with the array.
Page 67 SANbloc S50s can be connected to a Snap Server 520, 550, 650, or 18000. Up to three SANbloc S50s can be connected to a Snap Server 4500. Specific configurations are recommended when SAS and SATA drives are Note combined in the same expansion array. Be sure to review the S50 Quick Start Guide before configuring a mixed-drive array.
Page 68 Expansion Arrays Storage > Disks/Units attached to the head unit. For more information about the Disk/Units screen, please see “Disks and Units” on page 55. The disk drives of an expansion array are completely integrated into the host Snap Server’s logic. The default RAID configurations can be deleted and the internal and external disk drives recombined as necessary.
Page 69: Disks And Units
Disks and Units The Disks/Units screen is a graphic representation of RAID configuration and disk status on your server. The legend explains the meaning of each icon. • Move the mouse over a RAID set name to highlight all disks within the RAID set. •...
Page 70: Hot Swapping Disk Drives
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 Snap Servers, after a fresh drive is inserted into a drive bay, you must use the Administration Tool to add it to a RAID.
Page 71 Configure the new drive as part of the RAID. When you remove a drive from a Snap Server, the affected RAID transitions to degraded mode. It remains in degraded mode until the newly inserted drive is configured as a member of the RAID via the Administration Tool. For details on this procedure, see “Adding Disk Drives to a RAID”...
Page 72 Disks and Units Replacing a Disk Drive on a Snap Server 510, 520, 550, 650, or SANbloc S50 Remove the front bezel by pressing in the latches on each side of the bezel and pulling the bezel away from the chassis. On the closed handle of the failed disk drive, press the button in and to the left to release the latch.
Page 73 Replacing a Disk Drive on the Snap Server 4200, 4500, or Snap Disk 10 When the drive’s power LED is amber and the activity LED is off, the disk drive has failed or is not working correctly. Remove the front bezel. With a hand on each latch, slide both latches on the front bezel toward the center.
Page 74 Disks and Units drive into the empty drive bay, pushing it all the way forward before you close the handle. Close the font panel. Replacing a Disk Drive on an SD30SA If a disk drive fails on a Snap Disk 30SA, the disk drive status light below the Note failed drive turns amber.
Page 75 To insert a new disk drive, release the carrier handle by pressing the latch and insert the carrier all the way into the enclosure. Once the carrier is in the enclosure, close the handle until you hear a click. Using the Torx driver, lock the carrier into place by turning the lock screw clockwise until the red padlock icon is visible.
Page 76 Disks and Units Snap Server Administrator Guide...
Page 77: Chapter 5 Iscsi Disks
iSCSI Disks A license is required to activate iSCSI on some Snap Servers. Note Internet SCSI (iSCSI) is a standard that defines the encapsulation of SCSI packets in Transmission Control Protocol (TCP) and their transmission via IP. On Snap Servers, an iSCSI disk is based on an expandable, RAID-protected volume, but appears to a client machine as a local SCSI drive.
Page 78: Configuring Iscsi Initiators
Snap Server and Adaptec websites. Configuring iSCSI Initiators Adaptec has qualified a number of software initiators, PCI cards, and drivers to interoperate with Snap Servers. See the latest information on supported versions of these software and hardware initiators.
Page 79 Windows system whose registry is being modified. The result of any modifications to the Windows registry can vary, and implied outcomes of any modification suggested by Adaptec are NOT guaranteed, and may not be supported. Adaptec strongly recommends backing up your registry before making any modifications.
Page 80 Configuring iSCSI Initiators box to make this a persistent target, then click system reboots Snap Server target. Use the Disk Administrator to configure all volumes on top of the disks. From the Bound Volumes/Devices tab on the Property dialog box, click to allow the iSCSI service to configure the list of persistent volumes.
Page 81 Configuring Shares to iSCSI Disks When using the Microsoft initiator, shares to iSCSI disks may not automatically reconnect when the Windows system hosting the shares is rebooted. There are two methods to resolve this issue: • Share an iSCSI target that has an assigned drive letter. This method requires changes to the Windows registry and is described in article #870964.
Page 82 Configuring iSCSI Initiators Configuring Dynamic Disks to Persistently Reconnect On pre-Vista operating systems, when iSCSI targets are configured as dynamic disks, the Microsoft iSCSI initiator connecting to the dynamic disk may fail to connect properly during system boot. Using dynamic disks for iSCSI targets on pre- Vista operating systems is not supported by Microsoft.
Page 83 Verify that you have additional space available on the Snap Server to expand an existing volume • Open the browser-based Administration Tool for the Snap Server from a client on the network. • Navigate to Storage > iSCSI • Select the iSCSI disk you intend to expand. If you have not disconnected from the iSCSI disk at the host, you will be Note unable to proceed to the configuration page.
Page 84 Configuring iSCSI Initiators Identify the specific volume you are expanding. Enter: select disk n where n is the disk number that Diskpart indicated from the list command. Enter: select Volume n where n is the volume number that Diskpart indicated from the list command. Enter extend size=n where n is the number of megabytes you want to expand the disk.
Page 85 • The QLogic QLA4010/4050 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. The SANSurfer utility is included with the HBA to initiate, monitor, and change iSCSI targets using its text-based user interface.
Page 86: Iscsi Configuration For Vmware
Configuring iSCSI Initiators iSCSI Configuration for Novell NetWare Consider the following information before implementing iSCSI on NetWare servers: • NetWare 6.5 with SP1 for NetWare is required, and the iSCSI packages must also have been installed using the Custom Install method to utilize the NetWare iSCSI initiator.
Page 87: Iscsi Configuration On The Snap Server
Using the VI Client to Configure iSCSI Services Follow the instructions in the VMware Server Configuration Guide, available at http://www.vmware.com Create the VMKernel on the NIC card used for the iSCSI connection. Configure the Service Console that connects to the VMware host. Add the VMKernel port, enable the iSCSI software initiator, set up target IP addresses, and configure CHAP authentication.
Page 88 iSCSI Configuration on the Snap Server client can maintain the file system embedded on the iSCSI disk in the consistent state that is required for data integrity. • Do Not Use Snapshots on a Volume Containing an iSCSI Disk — Running a snapshot on a volume containing an iSCSI disk will abruptly disconnect any clients attempting to write to the server’s iSCSI disk and the resulting snapshot may contain inconsistent data.
Page 89 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 Snap Server.
Page 90: Creating Iscsi Disks
Creating iSCSI Disks Creating iSCSI Disks Navigate to Storage > iSCSI Be sure to read “iSCSI Configuration on the Snap Server” on page 73 before you begin creating iSCSI Disks. You cannot delete or edit an iSCSI Disk until all clients have been Note disconnected from that disk.
Page 91 Creating iSCSI Disks To Edit an iSCSI Disk Click an iSCSI disk name. You can increase (but not decrease) its size and enable or disable CHAP logon. You cannot edit an iSCSI disk if an initiator is connected. The hostname and Note IQN name of all connected initiators will be displayed.
Page 92 Creating iSCSI Disks Snap Server Administrator Guide...
Page 93: Chapter 6 Share And File Access
Share and File Access Snap Server has implemented features to accommodate the disparate methods used by the SMB and NFS protocols for sharing data. At the share level, administrators can assign read-write or read-only share access to individual Windows (and local) users and groups. Administrators can also edit the NFS exports file to control how shares are exported to NFS client machines.
Page 94: Configuring Share And Folder Security Overview
Configuring Share and Folder Security Overview Configuring Share and Folder Security Overview Snap Servers support file access in Windows, UNIX, and Apple networks, as well as access via FTP and HTTP. Although the GuardianOS runs on an optimized Linux kernel and has many Linux characteristics, the cross-platform features make it very different than a pure Linux distribution.
Page 95: Where To Place Shares
File and Directory Permissions GuardianOS supports two “personalities” of file system security on files and directories: • UNIX: Traditional UNIX permissions (rwx) for owner, group owner, and other. • Windows ACLs: Windows NTFS-style file system permissions. Introduced in GuardianOS 5.0, Windows ACLs fully support the semantics of NTFS ACLs, including configuration, enforcement, and inheritance models (not including the behaviour of some built-in Windows users and groups).
Page 96: Components And Options
Components and Options SnapTrees SnapTrees are directories that can be configured for the Windows/Mixed or UNIX security model. SnapTrees make a specific directory structure follow the rules of the specified security model, which indicates which file permission personality will be present on files by default, and whether that personality can be changed by users when changing permissions.
Page 97 Component Options Shares Shares are created on the Security > Shares screen. When creating a share, you must set the following options: • Name Select a name for the new share. • Volume Select a volume from the drop-down list. •...
Page 98: Snaptrees And Security Models
SnapTrees and Security Models SnapTrees and Security Models Volumes and directories created on the root of a volume are assigned one of two security models: Windows/Mixed or UNIX. The security model determines the rules regarding which security personality will be present on files and directories created by the various protocols and clients, and whether the personality of files and directories can be changed by changing permissions.
Page 99 SnapTree Functionality The following table describes the behavior of SnapTrees and Security Models. Function Description SnapTree Default ownership differs according to the method used to create the Directory SnapTree directory: Ownership • From the client — For UNIX personality directories, the owner and owning group will be according to the logged-in user.
Page 100: Id Mapping
ID Mapping Function Description SnapTree File Security model and permissions differ according to the method used to System create the SnapTree directory: Permissions • From the client: If SMB, permissions will either be according to ACL inheritance (if the parent volume root directory has the Windows security model) or Full Access to the owning user only.
Page 101: Creating Shares
example, if you enter ‘abc’ as your search criterion, all users and groups containing ‘abc’ in the name will be identified. Creating Shares Shares are created, viewed, edited, and deleted from the the Administration Tool. The default share (SHARE1) maps to the root of the volume and grants access to all users and groups over all protocols.
Page 102: Configuring Share Access
Configuring Share Access Security Models, SnapTrees, and Shares In the course of creating a share that points to a volume or to a directory on the root of the volume (aka SnapTree directory), you must assign a security model to the volume or SnapTree directory.
Page 103 Example A: More restrictive file-level access trumps more permissive share-level access. Share Level File Level Full control Read-only to FileA Example B: More restrictive share-level access trumps more permissive file-level access. Share Level File Level Read-only Full control to FileB Read-only access to all directories and files in Setting Share Access Permissions Share permissions for Windows, Apple, FTP, and HTTP users are configured from by selecting a share and clicking...
Page 104: Creating Home Directories
Creating Home Directories Creating Home Directories The Home Directories feature creates a private directory for every local or Windows domain user that accesses the system. When enabling Home Directories (from the Security > Home Directories serve as the home directory root. When a user logs in to the server for the first time after the administrator has enabled Home Directories, a new directory named after the user is automatically created inside the home directory root, and is configured to be accessible only to the specific user and the administrator.
Page 105 Permissions are enforced for the specified users in the same manner for all client protocols, including non-SMB clients that normally have the UNIX security personality. However, if a non-SMB client changes permissions or ownership on a Windows personality file or directory (or deletes and recreates it), the personality will change to UNIX with the UNIX permissions specified by the client.
Page 106: Security Guides
Security Guides To Set File and Directory Permissions and Inheritance (Windows) Using a Windows NT 4.0, 2000, 2003, XP, or Vista client, map a drive to the Snap Server, logging in as a user with change permissions for the target file or directory.
Page 107 Security Guides name of the organizational unit within the Active Directory tree in which the Snap Server will appear. For more information about Windows Active Directory, please see “Support for Windows Network Authentication” on page 27. Share-level Access to an Entire Volume This security guide provides steps for allowing users share-level access to a whole volume on the Snap Server.
Page 108 Security Guides Snap Server Administrator Guide...
Page 109: Chapter 7 Snapshots
Snapshots A snapshot is a consistent, stable, point-in-time image of a volume that can be backed up independent of activity on the live volume. Snapshots can also satisfy short-term backup situations such as recovering a file deleted in error, or even restoring an entire file system, without resorting to tape.
Page 110: Snapshot Management And Usage
Snapshot Management and Usage Snapshot Management and Usage This section describes snapshot components and dependencies. The Snapshot Pool Snapshot data are stored on a RAID in a snapshot pool, or space reserved within the RAID for this purpose. Each RAID on the system contains only one snapshot pool. This pool contains all snapshot data for all volumes on the RAID.
Page 111: Estimating Snapshot Pool Requirements
Snapshots and iSCSI Disks Running a 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 snapshots on a volume containing an iSCSI Disk.
Page 112: Adjusting Snapshot Pool Size
Adjusting Snapshot Pool Size Adjusting Snapshot Pool Size The current size of the snapshot pool for each RAID (or RAID group) can be viewed by navigating to the Storage > Snapshots link in the introductory text. On the screen that opens, you can adjust the pool space up or down as necessary at any time.
Page 113: Coordinating Snapshot And Backup Operations
read-only), a snapshot share inherits access privileges from its associated live- volume share. The same folders appear on the Web View screen when you connect to the Note Snap Server using a Web browser; however, the snapshot share folder does not provide access to the snapshot;...
Page 114 Coordinating Snapshot and Backup Operations native ACLs and quotas. Placing this information in a recovery file allows all backup packages to include this information. If the volume needs to be restored from tape, or the entire system needs to be recreated from scratch on a different server, this information may be required to restore all rights and quota information.
Page 115: Chapter 8 Disaster Recovery
Disaster Recovery Disaster recovery entails creating the files you need to recover a Snap Server’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 Snap Server is cut off due to a hardware or software failure.
Page 116: The Snapdrimage File And The Volume Files
Backing Up Server and Volume Settings The SnapDRImage File and the Volume Files Details on the Snap Server disaster recovery files and the information they contain are as follows: • SnapDRImage — The Snap Server disaster recovery image saves server-specific settings such as network, RAID, volume and share configuration, local user and group lists, and EDR Management Console settings (if applicable).
Page 117: Rejoining The Server To A Windows Domain
• You have devised and implemented a data backup strategy. It is recommended that you make a backup of your system regularly, from the root of the share for each volume, and store it in an off-server location. This ensures that the most current data is backed up and available for use with a disaster recovery.
Page 118: Backing Up The Netvault Database Directory
Backing Up the NetVault Database Directory Backing Up the NetVault Database Directory This section details the use of the NetVault Database plug-in and offers various tips for its use. Backup Recommendations It is important to note that the NetVault Database can be backed up at any time as long as no other NetVault jobs controlled by this server are running.
Page 119: 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 Snap Server. Pre-Restore Requirements Before restoring the database, perform the following steps on the Snap Server acting as the NetVault Server: Completely reinstall and configure the same version of the GuardianOS that the server was running.
Page 120 Recovering the NetVault Database Restore Procedure Access the Restore window from the NetVault GUI by clicking the button in the command toolbar. Double-click the NetVault Server open it. Plug-ins (and APMs) used to conduct successful backups on the selected client will be displayed.
Page 121: Disaster Recovery Procedural Overview
Any third-party license keys you have not purchased through Adaptec will be lost. If you have installed data replication or management utilities such as Snap EDR, you will need to re-install and/or relicense them for use with the new server.
Page 122 Disaster Recovery Procedural Overview Now you can replace your data from tape backup. If the backup doesn’t retain permission and ownership settings, you can restore these by selecting Volume Security Settings If you are restoring from any backup other than NetVault, you will need to Note recover the volume settings.
Page 123: Chapter 9 Ca Etrust Antivirus Software
CA eTrust Antivirus Software The CA eTrust Antivirus software is preinstalled on all GuardianOS Snap Servers. By default, the software is enabled on most Snap Servers, but no scan jobs or signature updates have been scheduled. (The server will, however, check for signature updates whenever the server boots.) These and other antivirus configuration and management tasks are performed using the CA eTrust Antivirus GUI, accessed from the screen of the Administration Tool.
Page 124: Antivirus Dependencies
Antivirus Dependencies Antivirus Dependencies The Snap Server implementation of CA eTrust Antivirus software includes the following features: HTTP Access and Antivirus Configuration To access the CA eTrust Antivirus configuration interface, HTTP must be enabled on the Network > Web Re-enabling the Antivirus Software The antivirus software is enabled by default.
Page 125: Launching The Ca Etrust Antivirus Gui
Launching the CA eTrust Antivirus GUI The CA eTrust Antivirus software is enabled by default. Some situations, such as deleting a volume or performing an upgrade procedure, may require you to re- enable the software. To learn how the antivirus software interacts with other GuardianOS software components, see “Antivirus Dependencies”...
Page 126: The Local Scanner View
The Local Scanner View The Local Scanner View Use the Local Scanner view to scan a Snap Server for infected drives, folders, files, or disks on demand. Component Root Directory Move Folder Scheduled Scan Jobs Snap Server Administrator Guide Description Displays the directory structure of the Snap Server.
Page 127: Scan Job Configuration And Scheduling
Scan Job Configuration and Scheduling You can run scan jobs on demand or you can configure scan jobs to run periodically. This section outlines the process of configuring and running manual and scheduled scans. For detailed descriptions of all scanning options, see the CA eTrust Antivirus online help.
Page 128: Running A Manual Scan Job
Scan Job Configuration and Scheduling Setting the Type of Files to Scan (Selections tab) Use the Selections tab options to choose the types of objects to scan, the types of file extensions to include or exclude from a scan, and the types of compressed files to scan.
Page 129: Signature Updates
Schedule the scan. The Schedule tab allows you to set a start date and a repeat interval for the scan. Select the directories to scan. The Directories tab lists all paths that currently exist on the server. You can remove or add new paths as desired. You can also use the Exclude Directories tab to achieve the same result.
Page 130 Signature Updates Method Description Use UNC to distribute signature updates from one Snap Server to another (or from any arbitrary SMB or Windows server). Note that for UNC to work, you must have the Enable Guest Account option enabled (Network > Windows) on the Snap Server on which the signature updates reside.
Page 131 Updating a Snap Server that does not have Internet Access If you have Snap Servers that do not have Internet access, use the following procedures to download the signature files to a machine with Internet access and then copy them to the Snap Server. When retrieving signature updates, the antivirus software attempts to connect Note to all the sites in the site list in the order they are listed.
Page 132 Signature Updates To Distribute Files via UNC If you have more than one Snap Server with no Internet access, you can perform the previous procedure on just one of them (or any Windows/SMB server), and then configure your other Snap Servers to get the update from that server automatically via UNC.
Page 133: Verifying Download Events
Enter the following information regarding the server on which the update file resides as follows: • In the Host Name field, enter the IP address. • In the User Name and Password fields, enter the admin user name and password. •...
Page 134: Alert Options
Alert Options Alert Options Alert options allow you to tailor the notification information that is provided to the Alert Manager, cut down on message traffic, and minimize the dissemination of notifications that are not critical. To set alert options, select Scanner menu.
Page 135: Log View
Option Restore and Cure Delete Log View The Log View provides easy access to detailed information on scan, distribution, and other events. To access this view select Description This option allows you to restore the selected item back to the original folder it was in, and cure it.
Page 136 Log View Option Local Scanner RealTime Scanner Scheduled Scanner General Events Distribution Events Snap Server Administrator Guide Description Displays summary information about scan jobs that have run. Not Supported. Displays summary information on scheduled scans that have run. Displays the Event log for a given day. Click a date to view all events that occurred that day.
Page 137: Chapter 10 Unicode
Unicode This section details how the GuardianOS Snap Server operates when Unicode is enabled. Topics in Unicode • What is Unicode? • Converting to Unicode • Unicode and Protocol Interaction • How Snapshots Interact with Unicode • Backing Up Unicode Servers •...
Page 138 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 101. Step 3: Convert to Unicode Navigate to Server >...
Page 139: Unicode And Protocol Interaction
Unicode and Protocol Interaction Step 4: Make a new DRImage Once your system has been converted to unicode, make a new DRImage. The procedures are the same as before (see “Disaster Recovery Procedural Overview” on page 107 for more details). Step 5: Back up the system with Unicode enabled backup applications Back up your system with a Unicode compliant backup application.
Page 140 Unicode and Protocol Interaction filename; for example, you might see {!^AB in a file name. MacOSX clients can edit such files, and the names will be retained in their original form when written back to the file system. MacOS 9 and lower are not Unicode-compliant, and use the MacRoman code page to represent extended characters.
Page 141: How Snapshots Interact With Unicode
HTTP HTTP integrates easily with Unicode and the Snap Server. If invalid UTF8 characters are encountered on the file system, the characters will be returned with an escape sequence. Escape sequences begin with {!^. The following two characters are the hexidecimal value of the characters in the file name; for example, you might see {!^AB in a file name.
Page 142 Backing Up Unicode Servers The following table gives an overview of how Unicode interacts with backup applications: Officially Supports Unicode UI Displays Correct Filenames Backups and Restores Unicode data 1.The UI displays garbage but the data is intact. 2.SNAP EDR Guardian to Guardian, both in Unicode mode: OK SNAP EDR Windows, Linux, or Guardian in non-Unicode to Guardian in Unicode mode: files and directories with extended characters are dropped.
Page 143: Unicode And Expansion Arrays
Unicode and Expansion Arrays 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. If you do not have language compliant backup applications, do not back up using UNIX.
Page 144 Unicode and Expansion Arrays Snap Server Administrator Guide...
Page 145: Appendix A Backup And Replication Solutions
Backup and Replication Solutions GuardianOS supports several backup methods, including third-party off-the-shelf backup applications and applications that have been customized and integrated with the GuardianOS on the Snap Server. Enabling Unicode on the server will limit some backup applications’ ability to Note function with the Snap Server.
Page 146: Integrated Backup Solutions For The Snap Server
Integrated Backup Solutions for the Snap Server This appendix provides a brief description of the supported backup solutions and, where applicable, gives instructions on how to install the solutions on the Snap Server. Integrated Backup Solutions for the Snap Server The following backup solutions are preinstalled and/or customized for the Snap Server: BakBone Netvault...
Page 147: Snap Enterprise Data Replicator (Snap Edr)
Click on the BakBone NetVault page. Add Clients Enter the management workstation’s DNS name or IP address. Enter the NetVault client password created during installation for the client. The password field cannot be left blank. Click You can add multiple workstations by completing the fields and repeatedly selecting the button.
Page 148 Integrated Backup Solutions for the Snap Server Once the server is configured, a screen appears with the following options: Option Description Click here to Opens the Management Console where jobs can be scheduled. configure jobs Stop Service Stops all services. Restart Service Restarts all services.
Page 149: Off-The-Shelf Backup Solutions For The Snap Server
• A secure shell (SSH) client — To remotely install any backup solution on the Snap Server, you must have an SSH client installed on a remote workstation. The Adaptec SSH implementation requires SSH v2. If you do not already have an SSH client application installed, you can download one from the Internet.
Page 150: Preinstallation Tasks
Off-the-Shelf Backup Solutions for the Snap Server • Locate the Snap Server backup and restore path — Backup servers often request the path for backup and restore operations on the Snap Server. When you configure a backup server to see the agent or client running on the Snap Server, use the following path: /shares/sharename where sharename is the name of the share to be backed up.
Page 151 Installing the CA BrightStor ARCserve Agent This section explains how to install the CA BrightStor ARCserve Agent versions 11.5 and 12.0. This procedure assumes that you are using the default Snap Server Note configuration; and you have created a directory called agent (to which to copy your agent/client files) on the default share (SHARE1), such that the path to the directory is /shares/SHARE1/agent.
Page 152 Off-the-Shelf Backup Solutions for the Snap Server Determine which volume has the most available space by looking at the column in the volume usage table. cd /hd (lists all volumes) (shows volume usage) df -h Change directory to the volume with the most available space. cd [volumename] where [volumename]...
Page 153 Close the SSH client and return to the Administration Tool, then do the following: To disable SSH on the Snap Server, navigate to the the Enable SSH checkbox, then click To start the newly installed backup agent, navigate to the screen, and click Shutdown/Restart Delete the agent files you copied to the Snap Server because they are no longer...
Page 154: Installing The Symantec Backup Exec Ralus Agent
Off-the-Shelf Backup Solutions for the Snap Server Installing the Symantec Backup Exec RALUS Agent This procedure assumes that you are using the default Snap Server Note configuration; and you have created a directory called agent (to which to copy your agent/client files) on the default share (SHARE1), such that the path to the directory is /shares/SHARE1/agent.
Page 155 In the ralus directory, create 3 directories called VRTS, VRTSralus, and VRTSvxms. cd ralus mkdir VRTS VRTSralus VRTSvxms [to verify that the directories are there] If CA Antivirus has been installed, you will have an /opt directory. If it has not been installed, create an /opt directory: mkdir /opt Create the following symbolic links from the new directories in ralus to the...
Page 156 Off-the-Shelf Backup Solutions for the Snap Server Install the agent: cd /shares/SHARE1/linux ./installralus Follow the installation instructions, accepting the default options. During the installation process, you may see an error message about the Note failure to add root to the beoper group. This error will be resolved in the following step.
Page 157 Installing the Symantec NetBackup v6.5 Client This procedure assumes that you are using the default Snap Server Note configuration; and you have created a directory called agent (to which to copy your agent/client files) on the default share (SHARE1), such that the path to the directory is /shares/SHARE1/agent.
Page 158 Off-the-Shelf Backup Solutions for the Snap Server Create a “symbolic” link to the openv directory in the /usr/ directory: ln -s hd/[volumename]/openv /usr/ where [volumename] is the name of the volume with the most available space. Use the host file editor ( Exec servers to /etc/hosts Backup Exec server.
Page 159 Remove the NetBackup services by deleting the files for in the bpjava-msvc /etc/xinetd.d rm -rf /etc/xinetd.d/bpcd rm -rf /etc/xinetd.d/vnetd rm -rf /etc/xinetd.d/vopied rm -rf /etc/xinetd.d/bpjava-msc Restart the Snap Server services by either rebooting or typing: /etc/rc.d/init.d/xinetd reload Installing the EMC Legato NetWorker Client This procedure assumes that you are using the default Snap Server Note configuration;...
Page 160 Off-the-Shelf Backup Solutions for the Snap Server Select a volume on which to put a directory called networker. If you later delete the volume the networker directory is on, you will need to Note reinstall the agent. cd /hd [lists all the volumes] [shows volume usage] df -h Determine which volume has the most available space by looking at the...
Page 161 copy the backup to the original using the command and then edit the file again. etc/profile To implement the changes, enter the following command: source /etc/profile Install the EMC Legato Networker Client Connect to the Snap Server via SSH, and log in as admin, using your admin user password.
Page 162 Off-the-Shelf Backup Solutions for the Snap Server Delete the client files you copied to the Snap Server because they are no longer needed. To verify the success of the installation, use your backup management software to configure and run a test backup. 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 Snap Server.
Page 163 Connect to the Snap Server via SSH, and log in using the admin user name and password. SSH v2 is required. If you fail to connect to the server, ensure that your SSH Note client is configured to connect via SSH v2. You are placed into the CLI shell.
Page 164 Off-the-Shelf Backup Solutions for the Snap Server Snap Server Administrator Guide...
Page 165: Appendix B Command Line Interface
Command Line Interface GuardianOS includes a command line interface (SnapCLI) accessible through SSH. Using the CLI, users can access information about some of the Snap Server configuration parameters and perform certain configuration and maintenance functions without using the GuardianOS web interface or SSM. Several administrative tasks must still be performed using the Administration Note Tool.
Page 166 SnapCLI Syntax For example, to see a list of available commands once you have logged into SnapCLI, type at the prompt. To see a description of a specific command, type the command name (e.g., date) + help or ?: date help Command Arguments and Options date...
Page 167 Suppose, instead of , you entered the command date available, one with options: Command Arguments and Options set [OPTIONS] - require-webview-auth=(yes|no) - non-secure-http=(yes|no) Thus, the following command string: web set require-webview-auth=yes non-secure-http=no sets HTTP/HTTPs properties on the Snap Server to require clients to authenticate in order to access the server and to disable non-secure HTTP access.
Page 168: Scripts In Snapcli
Following is an example script that can be used to create and remove users, groups, and shares: #!/bin/sh ########################################################## # Copyright 2003-2007 Adaptec, Inc. All rights reserved. # # Permision is granted to use this code provided that it # # retains the above copyright notice. ##########################################################...
Page 169: Create A Share
# if the user does not exist then create it if ! $CLI user get user-name="$1" > /dev/null 2>&1; then echo "Creating user '$1' ..." $CLI user create user-name="$1" password="$2" > /dev/null 2>&1 if [ $? -ne 0 ]; then echo "Creation of user '$1' failed."...
Page 170 Scripts in SnapCLI $CLI share create share-name="$1" share-volume="$2" > /dev/null 2>&1 if [ $? -ne 0 ]; then echo "Creating share '$1' failed." return 1 else echo "Share '$1' already exists." return 0 # usage: 'rmuser <user_name>' rmuser() # if the user exists then delete it if $CLI user get user-name="$1"...
Page 171 Scripts in SnapCLI echo "Share '$1' does not exist." return 0 Create a user, group, and share; then add the user to the group ############## Main ############## # create a user, a group and a share and add the user to the group mkuser "$USER"...
Page 172 Scripts in SnapCLI Snap Server Administrator Guide...
Page 173: Appendix C Troubleshooting Snap Servers
Troubleshooting Snap Servers Basic techniques for identifying and resolving common hardware and networking issues are described here. Topics in Troubleshooting Snap Servers • The Meaning of LED Indicators • System Reset Options • Networking Issues • Miscellaneous Issues • Phone Home Support Additional Resources Resource Description...
Page 174: The Meaning Of Led Indicators
The Meaning of LED Indicators The Meaning of LED Indicators LED indicators provide information on the status of basic connectivity, disk drives, fan modules, and power supply modules. • Snap Server 110/210 Status and Drive Light Behavior • Snap Server 410 Status and Drive Light Behavior •...
Page 175 The LEDs operate as described in the following tables: Power LED Solid green The server is powered on. 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 The server is in Maintenance Mode.
Page 176 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: Adaptec 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.
Page 177 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: Adaptec 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.
Page 178 The Meaning of LED Indicators Disk Drive LEDs are below the status lights, and the indentification (Unit ID) LED is to the right of the LCD display. The LEDs operate as described in the following tables: Power LED Solid green System LED Double-blink green Triple-blink green...
Page 179 Disk Drive LEDs Disk drive LEDs on these Snap Servers are located beneath the status lights on the bezel. For all disk drive LEDs, the left light indicates drive status; the right light indicates drive activity. They operate as follows: Status LED (left) Activity LED (right) Solid green Off (SATA drive)
Page 180 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: Adaptec 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.
Page 181 The LEDs operate as described in the following tables: Power LED Solid green The server is powered on. The server is powered off. System LED Double-blink green The server is booting up. Triple-blink green The server is shutting down. Solid or blinking A problem was detected.
Page 182 The Meaning of LED Indicators Snap Server 18000 Status and Drive Light Behavior The server has two status lights, two network lights, and two lights for each of the eight disk drives, as shown in the following illustration: Power, System, and LAN LEDs Looking at the server from the front, the lights appear in the following order, from left to right: power LED, system LED, LAN 1 (Ethernet1) LED, and LAN 2 (Ethernet2) LED.
Page 183 LAN 1 and LAN 2 LEDs Solid green The server is active and connected to the network. The port is disconnected; or the Ethernet cable is not connected or linked to an active switch. Disk Drive LEDs Disk drive LEDs on the Snap Server 18000 are located on the bezel to the right of the LED display.
Page 184 The Meaning of LED Indicators Power Fault Solid red Fan Module LED Indicator Lights The Snap Server has no external LEDs that indicate the status of a fan module. The screen of the Administration Tool indicates when a fan has Monitoring >...
Page 185 SANbloc S50 Enclosure, Disk Drive, APC Module, and Controller Behavior This section describes the LED indicators on the SANbloc S50 enclosure, disk drives, and APC modules. Enclosure LEDs On the right front of the SANbloc S50 (as shown in the following illustration) are four LEDs that indicate the status of the enclosure.
Page 186 The Meaning of LED Indicators Disk Drive LEDs Each disk drive has three LEDs that indicate the status of the disk drive. These LEDs operate as described in the following table: Condition Solid green Solid amber Solid green Green random flash APC Unit LEDs Each APC unit has two LEDs that indicate status.
Page 187 Condition Yellow (flash) Yellow (solid) When an APC unit fails, the enclosure LED on the front of the unit also indicates the failure. Controller LEDs The controller has two LEDs that indicate status. Fault LED (yellow) FAULT ! SEP MASTER These LEDs operate as described in the following table: Condition Master...
Page 188 The Meaning of LED Indicators Snap Disk 10 Disk Drive and Power Supply Module LEDs This section describes the LED indicators on the Snap Disk 10’s disk drives and power module. Disk Drive LEDs The Snap Disk 10 has two lights below each disk drive. The Power light (left) indicates power.
Page 189 Snap Disk 30SA Disk Drive and Power/Fan Module Behavior This section describes the LED indicators on the Snap Disk 30SA disk drives and power /fan modules. Disk Drive LEDs The Snap Disk 30SA has two LEDs at the edge of each disk drive as shown in the following illustration.
Page 190 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. Fan Fault Power The LEDs operate as described in the following table:...
Page 191 Ops Panel LEDs The SD30SA Ops Panel has six LEDs, which are shown in the following illustration. The LEDs operate asfollows: Normal Status Fault Invalid Address Power On Solid green System Fault Solid amber PSU Fault Solid amber Hub Mode not used 2GB Link Speed not used...
Page 192: System Reset Options
System Reset Options System Reset Options Often the first thing to try in resolving anomalous behavior on a Snap Server is to reset the server to factory defaults. This section provides information about the following ways to reinstall or reset the system defaults. •...
Page 193: Performing System Resets Without Network Access
• Reset System Settings, Network, and Admin Passwords To Factory Defaults Returns the admin and root passwords to the default value, returns TCP/IP and other protocol settings to factory defaults, eliminates all shares to all volumes, and returns settings for server name, date and time, users, groups, quotas, and the activation and configuration of CA eTrust Antivirus to factory default values.
Page 194: Networking Issues
Networking Issues • Resets the Administrator password to the default ( • Resets the web server to allow http Networking Issues These are some of the networking issues you may encounter when using your Snap Server. The Server Cannot Be Accessed over the Network Inaccessibility may be caused by a number of reasons.
Page 195 Networking Issues Snap Server users before authenticating through the Domain. However, the Domain users/groups may be the ones that had been granted access to the shares. Be careful not to add local users or groups that are duplicates of those that are found on the Windows domain controller.
Page 196 Check the firewall configuration to your Linux workstation. Be sure you have not blocked the ability to receive TCP or User Datagram Protocol (UDP) communications. If problems persist, contact Adaptec Technical Support. You Receive an Access Denied Message When Attempting to Mount a Share...
Page 197 Networking Issues is missing a forward slash (/) in the command, which will return an Access Denied message. The correct syntax should be the following: mount 192.168.32.124:/SHARE1 /mnt The share name is case sensitive. Note You Cannot Log in as Root to the Snap Server GuardianOS allows you to log in as root over SMB.
Page 198: Miscellaneous Issues
Miscellaneous Issues Miscellaneous Issues These are some miscellaneous issues you may encounter when using your Snap Server. Back Up Applications You Backed Up Your Snapshot Share and Are Now Attempting to Restore It, and the Operation Fails A snapshot share is read-only. You can restore the data to a read-write accessible share.
Page 199 Power to the Snap Server Is Unexpectedly Cut Off Due to a Power Outage Adaptec recommends that you use an uninterruptible power supply (UPS) with the Snap Server. If you did not have a UPS attached to the server at the time of the...
Page 200: Phone Home Support
Once your Snap Server has been registered, Phone Home Support becomes available for use. Phone Home Support emails system logs and files that contain information useful for troubleshooting purposes to Adaptec technical support. You can use the Monitoring > Support or, in the course of working to resolve an issue, a technical support representative may ask you to fill out and submit this page.
Page 201: Appendix D Guardianos Ports
GuardianOS Ports The following table outlines the ports used in the GuardianOS. Port # Layer GOS Feature TCP & UDP Network > Apple Network > Apple TCP & UDP Network > FTP TCP & UDP Server > SSH TCP & UDP Server > Email Notification TCP &...
Page 202 Port # Layer TCP & UDP • Networking > NFS TCP & UDP Server > Date/Time > TCP & UDP Network > Windows TCP & UDP Network > Windows TCP & UDP Network > Windows TCP & UDP Network > SNMP TCP &...
Page 203 Port # Layer GOS Feature TCP & UDP Network > Windows Server > Printing TCP & UDP Network > Apple Server > Printing Network > NFS Network > NFS Network > NFS Network > NFS Assist Assist 2005 SnapExtensions 2049 TCP &...
Page 204 Port # Layer 9049 9050 9080 9090 9091 9092 9093 9100 9110 9200 9311 10000 10001 12000 TCP & UDP Network > Apple 12168 16384 16388 Snap Server Administrator Guide GOS Feature Name Sysbroker Sysbroker • SnapExtension > S2S S2Sv2 Replication Node •...
Page 205 Port # Layer GOS Feature 20031 SnapExtension > BakBone NetVault 24066 32780 WebUI 32781 WebUI 49221 SnapExtension > SnapEDR Name Comment NetVault Listening Port poolmgr Used by /bin/poolmgr tomcat Random Port tomcat Random Port SnapEDR External Communications Port Appendix D GuardianOS Ports...
Page 206 Snap Server Administrator Guide...
Page 207: Glossary
Term access permissions ACL (Access Control List) Administration Tool ADS (Active Directory Service) AFP (AppleTalk Filing Protocol) agent algorithm AllLocalUsers group AllUsers group array Definition A rule associated with a share, a file, or a directory to regulate which users can have access to the share and in what manner.
Page 208 Term authentication autonegotiation autosensing bonding CA eTrust Antivirus chaining channel CHAP (Challenge Handshake Authentication Protocol) checksum CIFS (Common Internet File System) The default Windows protocol for communication between daemon default gateway degraded DHCP (Dynamic Host Configuration Protocol) Snap Server Administrator Guide Definition The validation of a user’s identity by requiring the user to provide a registered login name and corresponding...
Page 209 Term directory disaster recovery disk DNS server (Domain Name System server) domain domain name Ethernet Ethernet address Ethernet port event Definition A virtual folder used to organize files. Also called a folder. A strategy that allows a company to return to normal activities after a catastrophic interruption.
Page 210 Term failover FTP (File Transfer Protocol) full-duplex gateway GID (group IDs) GuardianOSImage.gsu half-duplex hidden share host name hot spare (local or global) hot swapping HTTP (Hypertext Transfer Protocol) Snap Server Administrator Guide Definition A strategy that enables one Ethernet port to assume the role of another port if the first port fails.
Page 211 Term HTTPS (Hypertext Transfer Protocol Secure) I/O (Input/Output) Inheritance IP (Internet Protocol) address iSCSI (Internet SCSI) Jukebox JVM (Java Virtual Machine) Kerberos LCD (Liquid Crystal Display) Definition The HTTP protocol using a Secure Sockets Layer (SSL). SSL provides data encryption, server authentication, message integrity, and client authentication for any TCP/IP connection.
Page 212 Term LED (Light-Emitting Diode) Linux load balancing local group/local user MAC (Media Access Control) maintenance mode MIB (Management Information Base) mirroring mounted multihomed Snap Server Administrator Guide Definition An electronic device that lights up when electricity is passed through it. A UNIX-like operating system that was designed to provide personal computer users a free or very low-cost operating system comparable to traditional and usually more...
Page 213 Term NAS (Network Attached Storage) NetVault for GuardianOS NFS (Network File System) NIS (Network Information Service) node NVDB (NetVault Database) directory A NetVault for GuardianOS database directory stored on the orphan parity Permissions PoP (Proof of Purchase) Definition Hard disk storage that is set up with its own network address as opposed to being attached to the department computer that is serving applications to a network's workstation users.
Page 214 Term POSIX (Portable Operating System Interface) protocol public access share quota RAID (Redundant Array of Independent Disks) RAID 0 (Striped) RAID 1 (Mirrored) RAID 5 (Striping with Parity) RAID 6 (Striping with Dual Parity) Snap Server Administrator Guide Definition A set of standard operating system interfaces based on the UNIX operating system.
Page 215 Term RAID 10 (Striped Mirroring) recurring snapshot restrict anonymous resynchronization rollback SCSI (Small Computer System Interface) serial number server number share share access SMB (Server Message Block) Definition RAID 10 is two or more RAID 1’s striped together to provide greater redundancy and higher performance than a simple RAID 1.
Page 216 Term Snap EDR Snap Server Manager (SSM) SnapDRImage SnapExtension snapshot snapshot pool snapshot share SnapTree Directory SNMP (Simple Network Management Protocol) SSH (secure shell) SSL (Secure Sockets Layer) Snap Server Administrator Guide Definition A SnapExtension that copies the contents of a share from one Snap server to another share on one or more Snap Servers.
Page 217 Term standalone static IP address striping subnet mask TCP/IP (Transmission Control Protocol/Internet Protocol) trap UI (User Interface) UID (User IDs) unassigned UNC (Universal Naming Convention) UPS (Uninterruptable Power Supply) A device that allows a computer to keep running for a short URL (Uniform Resource Locator) Definition A network bonding mode which treats each port as a...
Page 218 Term volume Web View Windows domain authentication WINS (Windows Internet Naming Service) workgroup Snap Server Administrator Guide Definition A logical partition of a RAID’s storage space that contains a file system. In the default storage configuration of many Snap Servers, eighty percent of the RAID capacity is allocated to the default volume.
Page 219: Index
Symbols .os_private 102 Access network access to the server 19 problems with 180 users and groups 37 Windows ACLs 90 Access Denied Message 180 ACLs defined 193 backing up 102 resetting to defaults 179 setting file-level permissions (Windows) Active Directory defined 193 and name resolution servers 26 Snap Server interoperability with 28...
Page 220 CA eTrust Antivirus, see Antivirus Cable management arm 185 Chooser, see MacintoshOS Client access, configuring Apple 31 FTP 33 HTTPS/HTTP 33 NFS 30 Command Line Interface 151 Running Scripts 154 Syntax 151 Connecting to Snap Servers 12 Converting to 123 Defaults admin password 38 authentication 38...
Page 221 Hidden Shares 87 Host File Editor 136 Hot spares 44 Hot swapping automatic incorporation 44 disk drives 56 HTTPS/HTTP configuring 33 HTTPS incompatibility with MSIE 5.x on Mac 32 Initial Setup Wizard 14 IP address setting 23 using SSM to discover 13 IPP port number 35 iSCSI Disks 63 creating 76...
Page 222 Password default for admin account 38 Paths for backing up snapshots 100 for distributing antivirus updates 117 for restoring a "cured" file 120 to SnapDRImage 102 to volume disaster recovery files 102 Permissions share- and file-level interaction 88 file-level default behavior 91 share-level setting 89 Phone home support 186...
Page 223 Snap Servers backup and restore path 136 connecting to 12 SnapCLI 151 Running Scripts 154 Syntax 151 SnapDRImage 102 Snapshot shares 98 Snapshots autobackup of volume settings 102 coordinating with backup jobs 99 estimating storage requirements for 97 excluding from antivirus scans 113 excluding iSCSI Disks from 74 ways to adjust pool size 98 Snapshots and Unicode 127...
Page 224 Snap Server Administrator Guide...

Adaptec 5325301656 Administrator's Manual

Preface

Chapter 1 Administrative Overview

Chapter 2 Network Access to the Server

Chapter 3 User & Group Management

Chapter 4 Storage Configuration and Expansion

Chapter 5 Iscsi Disks

Chapter 6 Share and File Access

Chapter 7 Snapshots

Chapter 8 Disaster Recovery

Chapter 9 CA Etrust Antivirus Software

Chapter 10 Unicode

Appendix A Backup and Replication Solutions

Appendix B Command Line Interface

Appendix C Troubleshooting Snap Servers

Appendix D Guardianos Ports

Glossary

Index

Quick Links

Need help?

Questions and answers

Related Manuals for Adaptec 5325301656

Summary of Contents for Adaptec 5325301656

Table of Contents