1. Manuals
  2. Brands
  3. Adaptec Manuals
  4. Network Storage Server
  5. 5325301638 - Snap Server 4500 NAS
  6. Administrator's manual

Adaptec 5325301638 Administrator's Manual

Snap server 4500 nas
Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
Snap Server
®
Administrator Guide
GuardianOS v3.2
For GuardianOS-powered Snap Servers and
Snap Disk Expansion Arrays

Advertisement

Table of Contents
loading

Related Manuals for Adaptec 5325301638

Summary of Contents for Adaptec 5325301638

  • Page 1 Snap Server ® Administrator Guide GuardianOS v3.2 For GuardianOS-powered Snap Servers and Snap Disk Expansion Arrays...
  • Page 3 COPYRIGHT Copyright © 2004, Snap Appliance, Inc. All rights reserved worldwide. Information in this document is subject to change without notice and does not represent a commitment on the part of Snap Appliance or any of its subsidiaries. The software described in this document is furnished under a license agreement.
  • Page 4 FOR USE OF SNAP APPLIANCE STORAGE SOLUTIONS SNAP IP, ASSIST, AND SNAP SERVER MANAGER (“INSTALLATION UTILITIES”); THE SYSTEM SOFTWARE EMBEDDED IN THE SNAP SERVER STORAGE SOLUTION (“EMBEDDED SOFTWARE”); SOFTWARE MARKETED BY SNAP APPLIANCE OR THAT IS EMBEDDED IN OR OTHERWISE CONSTITUTES A PART OF SNAP APPLIANCE COMPUTER HARDWARE PRODUCT(S) (SOMETIMES REFERRED TO COLLECTIVELY HEREIN, TOGETHER WITH THE INSTALLATION UTILITIES AND THE EMBEDDED SOFTWARE, AS THE “LICENSED SOFTWARE”), EXCEPT WHERE EXPRESSLY PROVIDED OTHERWISE, ARE PROPRIETARY COMPUTER SOFTWARE BELONGING TO SNAP APPLIANCE, INC.
  • Page 5 purposes, you may not copy any documentation pertaining to the Licensed Software. You agree that your use and possession of the Licensed Software is permitted only in accordance with the terms and conditions of this Agreement. Ownership of Restricted Software. You agree and acknowledge that, (i) Snap Appliance transfers no ownership interest in the Restricted Software, in the intellectual property in any Restricted Software or in any Restricted Software copy, to you under this Agreement or otherwise, (ii) Snap Appliance and its licensors reserve all rights not expressly granted to you hereunder, and (iii) the Restricted Software is protected by United States Copyright Law and international treaties relating to protection...
  • 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 New Features in this Release ... 5 Snap Server Manager... 5 Connecting to the Server for the First Time ... 7 Using the Initial Setup Wizard ... 8 Configuring an APC-Brand UPS ... 9 SnapExtensions ...
  • Page 8 Local Users and Groups ...24 Windows Workgroup or Domain ...25 NIS Domain ...27 Chapter 4 Storage Configuration & Expansion... 29 Default Storage Configuration ...29 RAIDs ...30 Volumes ...33 Quotas...34 Expansion Arrays ...35 Status Devices...38 Chapter 5 iSCSI Disks ... 41 iSCSI Disk Management and Usage ...41 Chapter 6 Share and File Access ...
  • Page 9 Backing Up the NetVault for GuardianOS NVDB Directory ... 63 Recovering the NetVault Database ... 64 Disaster Recovery Procedural Overview... 66 Chapter 9 CA eTrust Antivirus Software ...69 Antivirus Dependencies... 70 Launching the CA eTrust Antivirus GUI ... 71 The Local Scanner View ... 72 Scan Job Configuration and Scheduling ...
  • Page 10 Snap Server Administrator Guide...

  • 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 Tips and Cautions Conventions used to call out useful or important information are described next: A tip presents time-saving shortcuts related to the main topic. A caution alerts you to potential hardware or software issues or hazards in Caution the configuration or operation of Snap Servers. Consider cautions carefully before proceeding with any operation.
  • Page 13 Finding More Information Product documentation related toGuardianOS Snap Servers and Snap Disk expansion arrays are listed below. The current versions of all these documents are always available from the Snap Appliance documentation center at www.snapappliance.com/support Source and Location Quick Start Guide Product Packaging and Web Snap Server Administrator Guide User CD and Web...
  • Page 14 Snap Server Administrator Guide...

  • 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.This guide applies to the following Snap Servers and expansion arrays: Snap Unit...

  • Page 16: Guardianos Specifications

    GuardianOS Specifications GuardianOS Specifications These specifications apply to all Snap Servers and expansion arrays running the most recent version of the GuardianOS. Feature Network Transport Protocols Network Block Protocols Network File Protocols Network Client Types File Server Emulation Network Security Snap Server Administrator Guide Specification TCP/IP...
  • Page 17 Feature System Management RAID Options Specification Browser-based Administration Tool for remote system administration Snap Server Manager utility (platform independent) SNMP (MIB II and Host Resource MIB) User disk quotas for Windows, UNIX/Linux, Mac, FTP Group disk quotas for UNIX/Linux Environmental monitoring E-mail notification RAID 5 (drive striping with parity): For each array, the size of one drive is reserved for parity.
  • Page 18 GuardianOS Specifications Feature Data Protection DHCP Support Snap Server Administrator Guide Specification Snapshots for immediate or scheduled point-in-time images of the file system. Local Backup with BakBone Netvault Workgroup Edition. Network Backup with VERITAS NetBackup/Backup Exec, CA BrightStor ARCserve/Enterprise, Legato NetWorker, BakBone Netvault, Microsoft Backup Software for Windows 95/98/NT/2000/Me/XP, or Dantz Retrospect (Macintosh).

  • Page 19: New Features In This Release

    New Features in this Release The major enhancements listed in the following table have been included in the latest release. Feature iSCSI Multi-initiator Support BakBone NetVault 7.1.1 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 20 Snap Server Manager • Java Requirements — JRE 1.4.0 or higher must be installed. • MacOS requirements — If you plan to run Snap Server Manager on a Macintosh client, you must upgrade the client to MacOS 10.2 or higher. (Required for JRE 1.4.0 or higher support.) Launching Snap Server Manager Launch Snap Server Manager using one of the methods described in the following table:...

  • Page 21: Connecting To The Server For The First Time

    Connecting to the Server for the First Time Snap Servers are preset to acquire an IP address from a DHCP server. If no DHCP server is found on the network, the Snap Server defaults to an IP address of 10.10.10.10, and you may not be able to see the server on your network. You can discover a Snap Server using either the default server name or the Snap Server Manager (SSM) utility.

  • Page 22: 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 register the server.

  • Page 23: Configuring An Apc-Brand Ups

    Configuring an APC-Brand UPS Server Registration You must register your server to activate your warranty, to receive Snap Care service and support, to create and track service requests, to download software updates, and to receive exclusive promotional offers. You can register multiple Snap Servers in one operation using Snap Server Manager.

  • Page 24: Snapextensions

    SnapExtensions SnapExtensions A SnapExtension is a Java application that extends a Snap Server's functionality. The SnapExtension start screen shows the current state of the components of a SnapExtension. Currently, Server to Server Synchronization is the only SnapExtension on offer. Server to Server Synchronization (S2S) Server-to-Server Synchronization is a SnapExtension that moves, copies, or replicates the contents of a share from one Snap Server to another share on one or more different Snap Servers.

  • Page 25: Add-On Features

    Add-On Features Add-on features are software applications, agents, and utilities that extend the capabilities of a Snap Server. Some add-on features are fully functional out-of-the- box; others may require a download and/or the purchase of a license for full operation. For up-to-date information on feature availability, contact Snap Appliance.

  • Page 26: Finding More Information

    Finding More Information Finding More Information Product documentation related toGuardianOS Snap Servers and Snap Disk expansion arrays are listed below. The current versions of all these documents are always available from the Snap Appliance documentation center at www.snapappliance.com/support Source and Location Quick Start Guide Product Packaging and Web Snap Server Administrator Guide...

  • Page 27: 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, NFS, Macintosh, FTP, 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 Snap Server for load balancing and failover.

  • Page 28: Tcp/Ip Options

    TCP/IP Options TCP/IP Options GuardianOS Snap Servers ship with Dual Gigabit Ethernet ports. The following table describes TCP/IP options; default settings appear in boldface. Default TCP/IP Settings and Options Option Setting TCP/IP DHCP Addressing Static Network Standalone The default Standalone setting treats each port as a separate bonding Load Balancing...

  • Page 29: 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 30 Configuring TCP/IP Settings Make Sure the Switch is Set to Autonegotiate Speed/Duplex Settings When the server is shipped from the factory, both ports are set to autonegotiate. This setting allows the Snap Server to base speed and duplex settings on the physical port connection to a switch.

  • Page 31: Default Protocol Access Settings

    Default Protocol Access 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 Windows (CIFS/SMB) Apple (AFP) HTTP/HTTPS (Internet/Intranet) DHCP Server As a security measure, disable any network protocols not required in your network environment.
  • Page 32 Windows SMB Access Support for Windows (SMB) Consider the following information when configuring access for your Windows clients. Windows File and Folder Name Support In Windows, most file and directory names are transmitted as a 2-byte (16 bit) UCS- 2 character set. However, this is not true in every case. Some are still sent via a single byte character set.

  • Page 33: Nfs Access

    NFS Access NFS access to the server is enabled on the Administration Tool. By default, NFS access is enabled and any NFS client can access the Snap Server through the guest account. NFS client access to shares can be specified by navigating to the and then clicking the Support for NFS Consider the following technical information when configuring access for your NFS...

  • Page 34: Apple File Protocol Access

    Apple File Protocol Access Apple File Protocol Access Apple (AFP) settings are configured on the Administration Tool. The default settings provide access to AFP clients over an AppleTalk or TCP/IP network. Macintosh clients can access the server using the local guest user account. For more granular control over Macintosh client access, create local user accounts for Macintosh users.

  • Page 35: Ftp Access

    FTP Access Macintosh Access via a Browser When Only HTTPS Is Enabled If HTTP access is disabled, the Snap Server cannot be accessed using Internet Explorer 5.x for Macintosh. To resolve this issue, either use an alternate browser, or re-enable HTTP access on the screen.

  • Page 36: Http/Https Access

    HTTP/HTTPS Access HTTP/HTTPS Access Web View is the screen that opens when users access a Snap Server using their Web browsers. This screen displays a list of all shares to which the user has access. Users can navigate the share structure to locate and view or download files, but they cannot modify or upload files.

  • Page 37: 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 Windows NT, Windows 2000, or Active Directory domain, and Windows clients can then authenticate to the server using their domain credentials.

  • Page 38: Local Users And Groups

    Local Users and Groups guidelines: (1) the Snap Server does not recognize users or groups whose identification numbers are less than 100 or greater than 17999; and (2) each UID or GID must be unique. Local Users and Groups Local users or groups are created using the screens in the Administration Tool.

  • Page 39: Windows Workgroup Or Domain

    Local Account Management Tools The Snap Server offers several tools for creating, modifying, and editing local user and group accounts. Function Local User Management Local Group Management Windows Workgroup or Domain Windows workgroup or domain authentication is configured on the screen of the Administration Tool.
  • Page 40 Windows Workgroup or Domain Windows Networking Options Windows networks use a domain controller to store user credentials. The domain controller can validate all authentication requests on behalf of other systems in the domain. Option Workgroup Domain (NT or ADS) Kerberos Authentication Kerberos is a secure method for authenticating a request for a service in a network.

  • Page 41: Nis Domain

    NIS Domain Directory domains as member servers. References to the Snap Server's shares can be added to organizational units (OU) as shared folder objects. Guest Account Access to the Snap Server screen contains an option that allows unknown users to Security >...
  • Page 42 NIS Domain Snap Server Administrator Guide...

  • Page 43: Chapter 4 Storage Configuration & Expansion

    Storage Configuration & Expansion Snap Servers are preconfigured as a single RAID 5, with a single volume encompassing 80 percent of RAID capacity, and a single share pointing to the volume. The default storage configuration reserves 20 percent of the data space for snapshots.

  • Page 44: Raids

    RAIDs space is preconfigured to allocate eighty percent of the RAID for the file system and the remaining twenty percent for snapshots. Snap Server 18000 Snap Server 15000 Snap Server 4500 Snap Server 4200 Snap Server 14000 Snap Disk 10 Snap Disk 30/32SA Volume Snapshot Pool...
  • Page 45 would configure one of the drives as a hot spare. The following table summarizes the advantages and disadvantages of each type of RAID: Comparative Advantages of RAID Types Features Data Loss Risk Write Access Speeds Usable Capacity Disks Required Supports Hot Spares RAID Groups Two RAIDs can be grouped together to neatly resolve a number of capacity issues.
  • Page 46 RAIDs automatically uses the hot spare to rebuild itself without administrator intervention. Snap Servers offer two kinds of hot spares: local and global. Item Description Definitions Local hot spare — A local (or dedicated) hot spare is associated with and is available only to a single RAID. Administrators typically create a local hot spare for RAIDs containing mission-critical data that must always be available.

  • Page 47: Volumes

    Volumes Volumes are created, viewed, edited, and deleted from the screen of the Administration Tool. The default volume organizes the Snap Server’s storage capacity into a single volume with a single file system. If you need separate file systems on the same server, you can delete the default volume and create two or more smaller volumes in its place.

  • Page 48: Quotas

    Quotas • Adding Unallocated Capacity — If there is unallocated capacity remaining on the RAID, you can add this capacity to the volume simply by editing the size field and clicking Save • Creating a New RAID — If all capacity on the RAID is allocated, and either: (1) a sufficient number of drives to create a new RAID exists, or (2) a RAID of the same type with excess capacity exists, the button to create an additional RAID and automatically add its entire capacity to...

  • Page 49: Expansion Arrays

    how much space each user or group is currently consuming on the volume, allowing for precise tracking of usage patterns. You can set individual quotas for any local, Windows domain, or NIS user known to the Snap Server. Group quotas are available only for NIS groups.
  • Page 50 Expansion Arrays The Snap Disk 10 The Snap Disk 10 expansion array allows you to expand the capacity of a Snap Server 4500 (only) without increasing administrative tasks. You can attach up to two Snap Disk 10s via a Serial ATA cable to a Snap Server 4500. Each expansion array holds four disk drives.
  • Page 51 Expansion Arrays further preparation (other than preparing rack space) is necessary; the Snap Disk 30SA comes with the necessary cables. Otherwise, you will need to purchase and install the Snap Appliance fibre channel card, available from an authorized Snap Appliance reseller. The Snap Disk 32SA The Snap Disk 32SA expansion array works with a Snap Server 15000 or 18000.

  • Page 52: Status Devices

    Status Devices On the Storage > Devices from those of the host server by the label EXTN. The following graphic shows the Devices screen of a host Snap Server 4500. The disk drives of the expansion array connected to Port 1 of the host server’s Serial ATA card display with the label EXTN1;...
  • Page 53 Deleteing Unassigned Global Hot Spares Label Description Location The bay in which the drive is seated Model Device specifications Size Actual available capacity Status Current condition of the device: • Member Of — The RAID to which the drive is assigned. •...
  • Page 54 Status Devices Understanding the Disk Drive Detail table This screen displays summary information on each enclosure in the system as follows: Label Snap Unit Model Server Number Drives Status To view detailed disk drive information Do one of the following: •...

  • Page 55: Chapter 5 Iscsi Disks

    iSCSI Disks Internet SCSI (iSCSI) is a standard that defines the encapsulation of SCSI packets in 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 56 iSCSI Disk Management and Usage Isolate iSCSI Disks from Other Resources for Backup Purposes It is important to isolate iSCSI Disks from other resources on the Snap Server for two reasons: (1) the file system of an iSCSI Disk differs fundamentally from the Snap Server’s native file system;...
  • Page 57 iSCSI Disk Management and Usage without some risk. If the Snap Server were to suddenly lose power, for example, data still in cache would be lost. This risk can be minimized by following industry-standard security precautions such as keeping servers in a secured location and connecting power supplies to the mains using a network-based UPS.
  • Page 58 iSCSI Disk Management and Usage To Configure iSNS Label iSCSI Disk Name Volume Device Authentication Size Status Click the Configure iSCSI screen, from which you can configure iSNS. > iSCSI To Edit an iSCSI Disk Click an iSCSI Disk name. You can increase (but not decrease) its size. To Delete an iSCSI Disk The system will not allow the deletion of an iSCSI Disk when clients are connected.

  • Page 59: Chapter 6 Share And File Access

    Share and File Access Snap Appliance 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 60: Components And Options

    Components and Options Components and Options Shares are created and share access is granted using the Administration Tool. File- level permissions are configured from a Windows or UNIX/Linux workstation. The following table summarizes the components, options, and tools available for setting up share and file security on Snap Servers.

  • Page 61: Snaptrees & Security Models

    SnapTrees & Security Models Directories created at the root of a Snap Server volume are assigned one of two security models: Windows or UNIX. The security model determines the file-level security scheme that will apply to files, folders, and subdirectories within the top- level directory.

  • Page 62: Creating Shares

    Creating Shares 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. As a security measure, disable any protocols not required for your network environment.

  • Page 63: Share-Level Access Permissions

    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. Thereafter, security models for these entities are managed on the Security >...

  • Page 64: Setting File And Folder Permissions (Windows)

    Setting File and Folder Permissions (Windows) • Interaction between share-level and file-level access permissions — When both share-level and file-level permissions apply to a user action, the more restrictive of the two applies. Consider the following examples: Example A: More restrictive file-level access trumps more permissive share-level access.
  • Page 65 the parent directory. The example displayed in the graphic shows the default settings for a file created by the local user admin. File/Directory-Level Access Permissions User owner Initially, the user who created the file or directory Group owner The primary group of the user who created the file or directory Everyone Includes users to whom no other permission applies •...
  • Page 66 Setting File and Folder Permissions (Windows) in Windows security are available on the Snap Server. The GuardianOS supports the following file and directory permissions. File- and Directory-Level Access Permissions Read Grants complete read access. It is a combination of List Folder/ Read Data, Read Attributes, Read Extended Attributes, Read Permissions.
  • Page 67 To Set File and Directory Permissions and Inheritance (Windows) Using a Windows NT 4.0, 2000, or XP client, map a drive to the Snap Server, logging in as a user with change permissions for the target file or directory. Do one of the following: •...
  • Page 68 Setting File and Folder Permissions (Windows) Snap Server Administrator Guide...

  • Page 69: Chapter 7 Snapshots

    Snapshots A snapshot is a consistent, stable, point-in-time image of a volume used for backup purposes. Snapshots can satisfy short-term backup situations such as recovering a file deleted in error, or even restoring an entire file system, without resorting to tape. Perhaps more importantly, snapshots can be incorporated as a central component of your backup strategy to ensure that all data in every backup operation is internally consistent and that no data is overlooked or skipped.
  • Page 70 Snapshot Management and Usage snapshot and clicking the the volume will be inaccessible to clients. (1) Rolling back a volume cannot be undone and should only be used as a last Cautions resort after attempts to restore selected directories or files have failed; (2) Performing a rollback on a volume may invalidate the NetVault for GuardianOS nvdb directory for the volume, and may also disable the antivirus software.

  • Page 71: Estimating Snapshot Pool Requirements

    Estimating Snapshot Pool Requirements Snapshot data grows dynamically for as long as a snapshot is active and as long as there is enough space available in the snapshot pool to store them. When the snapshot pool approaches its capacity (at about 95 percent), the Snap Server deletes the oldest snapshot’s data to create space for more recent snapshot data.

  • Page 72: Accessing Snapshots

    Accessing Snapshots • Creating a RAID Group — When two RAIDS are grouped, their snapshot pools are added together. For example, if RAID A with a snapshot pool of 50 MB is grouped with RAID B with a snapshot pool of 25 MB, the resulting RAID Group will have a snapshot pool or 75 MB.

  • Page 73: Coordinating Snapshot And Backup Operations

    Accessing Snapshots Within the Snapshot Share A snapshot share contains a series of directories. Each directory inside the snapshot share represents a different snapshot. The directory names reflect the date and time the snapshot was created. For example, assume the snapshot share named Sales_SNAP contains the following four directories: latest 2003-12-25.120000...
  • Page 74 Coordinating Snapshot and Backup Operations depending on the number of files in the volume.) For example, assuming you schedule nightly backups for a heavily used volume at 3:00 a.m., you might schedule the snapshot of the volume to run every day at 2:30 a.m., allowing half an hour for the snapshot to run to completion.

  • Page 75: Chapter 8 Disaster Recovery

    Disaster Recovery This chapter explains how to create 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 discusses what to do if all access to the data on a Snap Server is cut off due to a hardware or software failure.
  • Page 76 Backing Up Server and Volume Settings • SnapDRImage — The Snap Server disaster recovery image saves server-specific settings such as server name, network, RAID, volume and share configuration, local user and group lists, and snapshot schedules. There is one SnapDRImage file per server, residing on the root directory of the first volume at the following path: \\server_name\volume_name.

  • Page 77: Backing Up The Netvault For Guardianos Nvdb Directory

    Take no action regarding the volume-specific files. These files will be copied to tape as part of your regular volume backup procedures. Backing Up the NetVault for GuardianOS NVDB Directory This section details the use of the NetVault Database plug-in and offers various tips for its use.

  • Page 78: Recovering The Netvault Database

    Recovering the NetVault Database Enter a suitable name for the job in the Job Title box and start the backup job by clicking the Submit button on the command toolbar. Only clients successfully added via the NetVault Client Management window will display. Recovering the NetVault Database This section summarizes the procedure necessary for recovering the NetVault Database from tape.
  • Page 79 • Do Not Monitor Job Progress During a Recovery — It is strongly recommended that all NetVault windows be closed, and the NetVault GUI be closed during the recovery of the NetVault Database, as this may interfere with the process. Restore Procedure Access the Restore window from the NetVault GUI by clicking the button in the command toolbar.

  • Page 80: Disaster Recovery Procedural Overview

    Disaster Recovery Procedural Overview Disaster Recovery Procedural Overview The procedures described in this section for responding to a catastrophic event are general in nature and may result in the loss of data. Should such an event actually occur, the exact procedure to follow will vary according to environmental conditions.
  • Page 81 Select the Fresh Install option, and click This operation may take a few minutes. As the operation progresses, the screen reports the progress of the operation. When the operation is finished, scroll to the bottom of the screen, and click screen opens.
  • Page 82 Disaster Recovery Procedural Overview Restore data using a fully qualified path to a share. When entering the path to the restore directory, use the following format: /share_name/path_to_directory /Finance/Sales If you install to an invalid share or path the software will restore to the Caution root file system.

  • Page 83: 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, but no scan jobs or signature updates have been scheduled. (The server will, however, check for signature updates whenever the server is powered on). These and other antivirus configuration and management tasks are performed using the CA eTrust Antivirus GUI, accessed from the the Administration Tool.

  • Page 84: 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 85: 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 86: 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. Local Scanner View of the CA eTrust Antivirus GUI Left-pane Components of the Local Scanner View Component Root Directory Move Folder...

  • Page 87: 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 88 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 89: 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 90 Signature Updates Methods of Downloading and Distributing 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 set to on the Snap Server on which the signature updates reside.
  • Page 91 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 to all the sites in the site list in the order they are listed.
  • Page 92 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 93: Alert Options

    Click . The path you entered appears in Download Sources list box. Click Download Now Verifying Download Events Use the following procedure to verify download and distribution events. Select View > Log Viewer In the left-hand pane, select the upper right-hand pane in chronological order. Select a distribution event.

  • Page 94: The Move Directory

    The Move Directory The Move Directory You can configure scans to move infected files to the move folder ( Options). To view infected files, click the Scanner pane of the Local Scanner View. To manage a moved file, right-click the file and select from the following options: The Right-Click Menu Options for Infected Files Option...

  • Page 95: 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 with Local Scanner selected Option Local Scanner RealTime Scanner Scheduled Scanner General Events Distribution Events from the View menu. Log View Description Displays summary information about scan jobs that have run...
  • Page 96 Log View Snap Server Administrator Guide...

  • Page 97: Chapter 10 Troubleshooting Snap Servers

    Troubleshooting Snap Servers This chapter describes basic techniques for identifying and resolving common hardware and networking issues. 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 98: 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 4200/4500/15000 Status & 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: Snap Appliance recommends that you become familiar with the operation of these lights.
  • Page 99 System LED Solid amber The server has encountered a system error. Blinking green then The server has booted to maintenance mode. For more amber information, see “Using Maintenance Modes to Perform System Resets” on page 93. LAN 1 and LAN 2 LEDs Solid green The server is active and connected to the network on the network port.
  • Page 100 The Meaning of LED Indicators Power Supply Module Indicator LEDs If a power supply fails on a Snap Server 14000, a failure message appears on the front LCD display. On the back of the server, there is a status light on each of the power modules, and below the power supply enclosure two activity lights.
  • Page 101 Snap Server18000 Status & 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 102 The Meaning of LED Indicators Disk Drive LEDs Disk drive LEDs on the Snap Server 18000 are located on the bezel to the right of the LED display. The left light indicates drive health. The right light indicates drive activity. They operate as follows: Health LED (left) Solid green Solid amber...
  • Page 103 The Meaning of LED Indicators 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 > Status failed. When the cover of the chassis is removed, the Fault LED on the failed module will be lit.
  • Page 104 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 Status light (left) indicates power.
  • Page 105 Snap Disk 30SA and Snap Disk 32SA Disk Drive & Power/Fan Module Behavior This section describes the LED indicators on the Snap Disk 30SA and Snap Disk 32SA’s disk drives and power /fan modules. Snap Disk 30SA and Snap Disk 32SA Disk Drive LEDs The Snap Disk 30SA and Snap Disk 32SA have two LEDs at the edge of each disk drive as shown in the following illustration.

  • Page 106: System Reset Options

    System Reset Options Snap Disk 30SA and Snap Disk 32SA Power/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 107 Resetting the Snap Server to Factory Defaults The GuardianOS allows you to reset different components of the system. Default settings can be found in the default configuration sections of Chapters 2, 3, and 4 of the Administrator Guide. Each reset option requires a reboot of the server. To prevent possible data Caution corruption or loss, make sure all users are disconnected from the Snap Server before proceeding.
  • Page 108 System Reset Options Mode Description As in mode 1, clears the IP address stored on the network, resets the server to use DHCP, and resets speed/duplex settings to autonegotiate. Mode 3 additionally, resets network bonding to standalone and resets all network protocols to factory defaults.

  • Page 109: Networking Issues

    Networking Issues 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. •...
  • Page 110 Networking Issues The Snap Server Does Not Operate Properly on a Network Running Gigabit- Full-Duplex For Gigabit Ethernet to operate properly, both the switch and the Snap Server’s primary Ethernet port (Ethernet1) must be set to Auto (autonegotiate). Any other setting will result in unexpected behavior and reduced performance.
  • Page 111 Networking Issues mismatch between the switch/hub and the Ethernet port on the Snap Server. To resolve this problem, verify that both settings (if using both of the server's 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.
  • Page 112 Networking Issues You Cannot Log in as root to the Snap Server The root account password is tied to the admin accout password. If you cannot log in as root, change the password for the admin account on the System > General Settings screen.

  • Page 113: Miscellaneous Issues

    You Are Unable to See Your Domain Users When Trying to Set Up Windows Security Permissions on File Folders The Snap Server (GuardianOS) has joined the Active Directory domain properly, and you can see the domain users when you set Share permissions from the browser-based Administration Tool.

  • Page 114: Phone Home Support

    Phone Home Support The Server Is Not Responding to File Requests or Configuration Commands Call your Snap Appliance technical support representative. 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.
  • Page 115 Complete the following fields as appropriate and click Text Field Description Subject: (Required) Enter a concise description that identifies the issue. Case: (Required) Select New Case if you are e-mailing technical support for the first time. Select Existing Case if you have previously contacted technical support concerning the issue.
  • Page 116 Phone Home Support Snap Server Administrator Guide...

  • Page 117: Appendix 11Third-Party Backup Applications

    Third-Party Backup Applications This appendix describes how to install the following backup agents on the Snap Server from a Linux or a Windows backup host system: • CA BrightStor ARCServe 2000 v7.0 • CA BrightStor ARCServe Backup v9.0 • CA BrightStor Enterprise Backup v10.0 •...

  • Page 118: Preparing To Install A Third-Party Backup Agent

    Preparing to Install a Third-Party Backup Agent Preparing to Install a Third-Party Backup Agent Before performing one of the backup agent installation procedures described in this appendix, make sure you have the following information and tools: • Backup and media server IP addresses — Most backup agents need to know the IP addresses of the backup and media servers you plan to use with the Snap Server.

  • Page 119: Pre-Installation Tasks

    Pre-installation Tasks Perform the following tasks prior to installing any agents. Identify backup and media servers to the Snap Server. In the Administration Tool, navigate to the and click . In the screen that opens, do the following: (a) enter the IP address of the backup or media server;...

  • Page 120: Installing Third-Party Agent Software

    Installing Third-Party Agent Software Installing Third-Party Agent Software For purposes of illustration, the procedures in this section assume that (1) you are using the default Snap Server configuration; and (2) 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 121 To change to the agent directory, enter one of the following commands and press Enter cd /opt/uagent (for ARCserve 2000 v7 only) cd /opt/CA/uagent (for ARCserve v9 and Enterprise v10) To start the agent, enter the following command and press ./uagentsetup The BrightStorARCserve agent is now installed.
  • Page 122 Installing Third-Party Agent Software To run the Backup Exec agent installation, type the following command: ./INSTALL Then press and follow the prompts, using the default install locations and Enter default options. You must respond to “yes” or “no” prompts in lowercase ( Caution uppercase will cause an error and abort the procedure.
  • Page 123 Installing a VERITAS NetBackup 3.4.1 Client This section describes how to install the UNIX/Linux agent from VERITAS NetBackup. Copy the NetBackup NBClients directory and the Linux directory from the root of the NetBackup CD to the agent directory on the Snap Server. Connect to the Snap Server via SSH, and login as admin using your admin user password.
  • Page 124 Installing Third-Party Agent Software Installing the VERITAS NetBackup 4.5 FP6 Client This section describes how to install the Veritas NetBackup 4.5 FP agent on a Snap Server to enable interoperability with NetBackup 4.5 Feature Pack 6 for Windows. Procedures for installing from the following media are given: •...
  • Page 125 You will be prompted for the NetBackup server name and for the NetBackup client name. • Specify the hostname of the already existing NetBackup Server on your network for the NetBackup server. • Specify the name of the Snap Server to which you are installing as the NetBackup client.
  • Page 126 Installing Third-Party Agent Software Installing from a CD Copy the NetBackup NBClients directory and the Linux directory from the root of the NetBackup CD to the agent directory on the Snap Server. Connect to the Snap Server via SSH, and login as admin using your admin user password.
  • Page 127 You will be prompted for the NetBackup server name and for the NetBackup client name. • Specify the hostname of the already existing NetBackup Server on your network for the NetBackup server. • Specify the name of the Snap Server to which you are installing as the NetBackup client.
  • Page 128 Installing Third-Party Agent Software Installing a Legato NetWorker Client This section describes how to install the Legato NetWorker UNIX/Linux client as well as special procedures Legato NetWorker users must use in order to perform backup and restore operations on the Snap Server. To Install the Legato Networker Client Connect to the Snap Server via SSH, and login as admin using your admin user password.
  • Page 129 Backup and Restore Operations with a Legato NetWorker Client This section describes special procedures Legato NetWorker users must use in order to perform backup and restore operations on the Snap Server. To Add the Snap Server as a Root User For backup operations, NetWorker requires that the Snap Server be configured as a root user.
  • Page 130 Installing Third-Party Agent Software Enter one of the following commands, and press • To recover data to its original location: recover -s backupservername -c snapservername -f -i “/shares/ SHARE1/data/” -a where /shares/SHARE1/data • To recover data to a different location recover -s backupservername -c snapservername -f -i -a R -d “/shares/SHARE1/relocated_data/”...

  • Page 131: 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 132 Term authentication autonegotiation autosensing bonding CA eTrust Antivirus chaining channel CHAP Authentication checksum CIFS (Common Internet File System) A specification for an Internet file access protocol that daemon default gateway degraded DHCP (Dynamic Host Configuration Protocol) directory 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 133 Term disaster recovery disk DNS server (Domain Name System server) domain domain name Ethernet Ethernet address Ethernet port event failover Definition 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.
  • Page 134 Term 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) HTTPS (Hypertext Transfer Protocol Secure) Snap Server Administrator Guide Definition A standard Internet protocol that provides a way to exchange files between computers on the Internet.
  • Page 135 Term I/O (input/output) Inheritance iSCSI IP (Internet Protocol) address Jukebox JVM (Java Virtual Machine) Kerberos LCD (liquid crystal display) LED (light-emitting diode) Definition The operation of transferring data to or from a device, typically through an interface protocol like CIFS, NFS, or HTTP.
  • Page 136 Term 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 A UNIX-like OS that was designed to provide personal computer users a free or very low-cost operating system comparable to traditional and usually more expensive UNIX systems.
  • Page 137 Term NAS (network attached storage) NetVault for GuardianOS NFS (Network File System) NIS (Network Information Service) node nvdb directory 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 138 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) recurring snapshot Snap Server Administrator Guide Definition A set of standard operating system interfaces based on the UNIX operating system.
  • Page 139 Term restrict anonymous resynchronization rollback S2S (Server-to-Server Synchronization) SCSI (Small Computer System Interface) serial number server number share share access SMB (Server Message Block) Snap Server Manager Definition A Windows feature in which anonymous users cannot list domain user names and enumerate share names. Microsoft has provided a mechanism in the Registry called restrict anonymous for administrators to restrict the ability for anonymous logon users (also known as NULL session...
  • Page 140 Term SnapDRImage SnapExtension snapshot snapshot pool snapshot share SnapTree Directory SNMP (Simple Network Management Protocol) SSH (secure shell) SSL (Secure Sockets Layer) standalone Snap Server Administrator Guide Definition The Snap Server disaster recovery image that saves server- specific settings such as server name, network, RAID, volume and share configuration, local user and group lists, and snapshot schedules.
  • Page 141 Term static IP address striping subnet mask TCP/IP (Transmission Control Protocol/Internet Protocol) trap 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) volume Web View Definition...
  • Page 142 Term Windows domain authentication WINS (Windows Internet Naming Service) workgroup Snap Server Administrator Guide Definition Windows-based networks use a domain controller to store user credentials. The domain controller can validate all authentication requests on behalf of other systems in the domain.

  • Page 143: Index

    Chapter 12Symbols Symbols .os_private 62 Access file and folder permissions 50 network access to the server 13 problems with 95 users and groups 23 See also Share access Access Denied Message 95 ACLs defined 117 backing up 62 resetting to defaults 93 setting file-level permissions (Windows) Active Directory defined 117...
  • Page 144 CA BrightStor ARCserve, installing agent CA eTrust Antivirus, see Antivirus Cable management arm 100 Chooser, see MacintoshOS Client access, configuring Apple (AFP) 20 FTP 21 HTTPS/HTTP 22 NFS 19 Windows (SMB) 17 Code page support 18 Connecting to Snap Servers 7 Defaults admin password 23 file-level access permissions 51...
  • Page 145 Hardware Components, purchasing new Hidden Shares 48 Host File Editor 105 Hot spares 31 HTTPS/HTTP configuring 22 HTTPS incompatibility with MSIE 5.x on Mac 21 Initial Setup Wizard 8 IP address setting 15 using SSM to discover 7 iSCSI Disks 41 management and usage 41 JRE, see Java Kerberos 26...
  • Page 146 Operating system, see GuardianOS Paths for backing up snapshots 60 for distributing antivirus updates 77 for restoring a "cured" file 80 to SnapDRImage 62 to volume disaster recovery files 62 Permissions share- and file-level interaction 50 file-level default behavior 50 GuardianOS processing of 53 setting folder inheritance 52 share-level...
  • Page 147 SnapDRImage 62 Snapshot shares 58 Snapshots autobackup of volume settings 62 coordinating with backup jobs 59 estimating storage requirements for 57 excluding from antivirus scans 73 excluding iSCSI Disks from 42 ways to adjust pool size 57 SnapTree 47 Specifications, GuardianOS 2 Speed/duplex options 14 SSH 105 Standalone 15...
  • Page 148 Snap Server Administrator Guide...

Table of Contents