1. Manuals
  2. Brands
  3. Tandberg Data Manuals
  4. Storage
  5. NAS Hardware Viking FS-1500
  6. Administration manual

Tandberg Data NAS Hardware Viking FS-1500 Administration Manual

Viking series data storage server
Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
TANDBERG
VIKING SERIES
NAS APPLIANCE
Storage Server Administration Manual
TANDBERG DATA ASIA
20 Bendemeer Road, #04-05
Cyberhub, Singapore 339914
Phone + 65 6396 0786
Telefax + 65 6396 0787
© Tandberg Data Asia
Part No.
65 82 X2 - 01
January
2008

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the NAS Hardware Viking FS-1500 and is the answer not in the manual?

Questions and answers

Related Manuals for Tandberg Data NAS Hardware Viking FS-1500

Summary of Contents for Tandberg Data NAS Hardware Viking FS-1500

  • Page 1 VIKING SERIES NAS APPLIANCE Storage Server Administration Manual TANDBERG DATA ASIA 20 Bendemeer Road, #04-05 Cyberhub, Singapore 339914 Phone + 65 6396 0786 Telefax + 65 6396 0787 © Tandberg Data Asia Part No. 65 82 X2 - 01 January 2008...
  • Page 2 Tandberg Data Asia assumes no responsibility for any errors which may ap- pear in this publication. It is the policy of Tandberg Data Asia to improve products as new techniques and components become available. Tandberg Data Asia therefore reserves the right to change specifications at any time.

  • Page 3: Table Of Contents

    Table of Contents Table of Contents System Overview 1.1. Product Information 1.1.1. Product Manageability 1.2. Redundancy 1.2.1. Configuring RAID using 4 HDD (1U) 1.2.2. Configuring RAID using 16 HDD (3U) 1.2.3. System Volume (SV) 1.2.4. Data Volume (DV) 1.4. Deployment 1.4.1.
  • Page 4 __________________________________________________________________________________________________ 3.5. Disk Management 3.6. Guidelines for Managing Disks & Volumes 3.7. RAID & Volume Management 3.8. Scheduling Defragmentation 3.9. Disk Quotas 3.10. Using Diskpart 3.10.1. Example of using Diskpart 3.11. Adding Storage 3.11.1. Expanding Storage 3.11.2. Extending Storage using Disk Management 3.12.
  • Page 5 __________________________________________________________________________________________________ 6.1. Folder Management 6.2. Managing File Level Permissions 6.3. Share Management 6.3.1. Share Considerations 6.3.2. Defining Access Control Lists 6.3.3. Integrating Local File System Security into Windows Domain Environments 6.3.4. Comparing Administrative & Standard Shares 6.3.5. Planning for Compatibility between File Sharing Protocols 6.3.5.1.
  • Page 6 __________________________________________________________________________________________________ 8.4.1. Microsoft Services for NFS snap-in 8.4.2. Microsoft Services for NFS command-line tools 8.5. Test Scenario 8.6. Steps for Deploying and Testing Microsoft Services for NFS 8.6.1. Reviewing system requirements for Microsoft Services for NFS 8.6.2. Setting up the environment for Microsoft Services for NFS 8.6.2.1.

  • Page 7: System Overview

    __________________________________________________________________________________________________ System Overview 1.1. Product Information The Tandberg Viking Series NAS appliance can be used in many types of computing environments, from basic Microsoft Windows workgroups to complicated multi-protocol domains using DFS, NFS, FTP, HTTP, and Microsoft SMB. The corresponding varieties of clients that can be serviced include any Windows, UNIX, Linux, Novell, or Macintosh variant.

  • Page 8: Product Manageability

    __________________________________________________________________________________________________ Notes The Microsoft® Windows® Storage Server 2003 x64 Edition operating system is designed to support 32–bit applications without modification; however, any 32–bit applications that are run on this operating system should be thoroughly tested before releasing the storage server to a production environment. Microsoft®...

  • Page 9: Configuring Raid Using 4 Hdd (1U)

    __________________________________________________________________________________________________ 1.2.1. Configuring RAID using 4 HDD (1U) For the 1U appliance (FS-412) Tandberg Data recommends two logical Volume sets consisting of System Volume (SV) and Data Volume (DV) to be created within the RAID set. The RAID set is first created which comprises of member HDD (number of HDD in a set).

  • Page 10: Configuring Raid Using 16 Hdd (3U)

    __________________________________________________________________________________________________ 1.2.2. Configuring RAID using 16 HDD (3U) The 3U appliance uses (FS-1600 / FS-1610) supports up to a maximum of 16 HDD. This provides greater degree of flexibility in RAID configurations: • Allow HDD to be grouped into multiple RAID sets with respect to their usage role: System Volume, Data Volume(s) or RAW Volumes (for iSCSI target volume provisioning).

  • Page 11: System Volume (Sv)

    Tandberg Data System Overview __________________________________________________________________________________________________ 1.2.3. System Volume (SV) This volume is organized as a RAID 0+1 volume. This volume includes the operating system image. The minimum recommended size for this volume is 10 GB (default). The RAID level can be customized using the RAID controller BIOS or web-based RAID manager.

  • Page 12: Environment Scenarios

    __________________________________________________________________________________________________ 1.5. Environment scenarios The NAS appliance is deployed in one of two security modes: • Workgroup • Domain (Windows NT® Domain or Active Directory Domain) The NAS appliance uses standard Windows user and group administration methods in each of these environments. For procedural instructions on managing users and groups, see Chapter 5 of this Manual.

  • Page 13: User Interfaces

    __________________________________________________________________________________________________ 1.6. User Interfaces There are several user interfaces that administrators can use to access and manage the Viking Series NAS appliance. Two of these interfaces are: • Using direct attached method • Using Windows Remote Desktop Each interface contains the same or similar capabilities, but presents them in a different manner.
  • Page 14 Tandberg Data System Overview __________________________________________________________________________________________________ Remote Desktop provides two options when closing a client: you can either disconnect or log off the system. Disconnecting leaves the session running on the server. You can reconnect to the server and resume the session. If you are performing a task on the server, you can start the task and disconnect from the session.

  • Page 15: Setting Up & Administration

    __________________________________________________________________________________________________ Setting Up & Administration Basic system administration functions are discussed in this chapter. This chapter also continues the process of setting up the system that was started using the Viking Series NAS Hardware User Manual by discussing additional setup procedures and options. Unless otherwise instructed, all procedures are performed using the Windows Remote Desktop Interface.

  • Page 16: Using Windows Remote Desktop

    __________________________________________________________________________________________________ 2.1. Using Windows Remote Desktop Remote Desktop is provided to allow for additional remote system administration and installation of approved third-party applications. Backup software and antivirus programs are examples of approved applications. To open a Remote Desktop session from a connecting machine using Windows XP: •...

  • Page 17: Enabling Telnet Server

    __________________________________________________________________________________________________ 2.2.1. Enabling Telnet Server The Telnet Server service needs to be enabled prior to its access. The service can be enabled by opening the services MMC: Select Start > Run, and then enter services.msc. Locate and right-click the Telnet service and then select Properties.

  • Page 18: Managing System Storage

    UNIX specific information is discussed in the “Microsoft Services for NFS” chapter. 2.7. Running Microsoft Windows Update Tandberg Data highly recommends that you run Microsoft Windows updates to identify, review, and install the latest, applicable, critical security updates storage server.

  • Page 19: Installing 3 Rd Party Software Applications

    __________________________________________________________________________________________________ 2.8. Using Ethernet NIC Teaming All Viking Series NAS appliances are equipped with an Intel or Broadcom NIC Teaming utility. The utility allows administrators to configure and monitor Ethernet network interface controller (NIC) teams in a Windows-based operating system. These teams provide options for increasing fault tolerance and throughput.
  • Page 20 Tandberg Data Setting Up & Administration __________________________________________________________________________________________________ This Page Intentionally Left Blank Tandberg Viking Series Storage Server Administration Manual...

  • Page 21: Storage & File Server Management

    Storage & File Server Management This chapter provides an overview of some of the component that make up the storage structure of the Viking Series NAS appliance. 3.1. Storage is divided into four major divisions: Each of these elements is composed of the previous level's elements. 3.1.1.

  • Page 22: Disk Array

    __________________________________________________________________________________________________ Disk Array 3.1.1.1. With an array controller installed in the system, the capacity of several physical drives can be logically combined into one or more logical units called arrays. When this is done, the read/write heads of all the constituent physical drives are active simultaneously, dramatically reducing the overall time required for data transfer.

  • Page 23: Logical Storage Element

    __________________________________________________________________________________________________ 3.1.2. Logical Storage Element Logical storage elements consist of those components that translate the physical storage elements to file system elements. The storage server uses the Window Disk Management utility to manage the various types of disks presented to the file system. There are two types of LUN presentation: basic disk and dynamic disk.

  • Page 24: File System Element

    Tandberg Data Storage & File Server Management __________________________________________________________________________________________________ Volumes are created out of the dynamic disks, and can be expanded on the fly to extend over multiple dynamic disks if they are spanned volumes. However, after a type of volume is selected, it cannot be altered. For example, a spanning volume cannot be altered to a mirrored volume without deleting and recreating the volume, unless it is a simple volume.

  • Page 25: Using Storage Element

    __________________________________________________________________________________________________ Shadow copies should not replace the current backup, archive, or business recovery system, but they can help to simplify restore procedures. For example, shadow copies cannot protect against data loss due to media failures; however, recovering data from shadow copies can reduce the number of times needed to restore data from tape.
  • Page 26 Tandberg Data Storage & File Server Management __________________________________________________________________________________________________ The Disk Management tool is a system utility for managing hard disks and the volumes, or partitions that they contain. Disk Management is used to initialize disks, create volumes, format volumes with the FAT, FAT32, or NTFS file systems, and create fault-tolerant disk systems.

  • Page 27: Guidelines For Managing Disks & Volumes

    • Tandberg Data does not recommend spanning arrays (volume set) with dynamic volumes. The use of software RAID-based dynamic volumes is not recommended. Use the array controller instead; it is more efficient.

  • Page 28: Raid & Volume Management

    Tandberg Data Storage & File Server Management __________________________________________________________________________________________________ 3.7. RAID & Volume Management The RAID and Volume set can be managed using web-based RAID manager. It can be accessed using the following on your web browser: http://<your NAS machine name or IP Address>:81/ The default user name is “admin”.
  • Page 29 Tandberg Data Storage & File Server Management __________________________________________________________________________________________________ Prior to using the web-based RAID manager, ensure that the web service of RAID manager is started by accessing the Remote Desktop using Start > Programs > Areca Technology Corp > archttppci > archttppci.

  • Page 30: Scheduling Defragmentation

    __________________________________________________________________________________________________ 3.8. Scheduling Defragmentation Defragmentation is the process of analyzing local volumes and consolidating fragmented files and folders so that each occupies a single, contiguous space on the volume. This improves file system performance. Because defragmentation consolidates files and folders, it also consolidates the free space on a volume.

  • Page 31: Using Diskpart

    Tandberg Data Storage & File Server Management __________________________________________________________________________________________________ When enabling disk quotas, it is possible to set both the disk quota limit and the disk quota warning level. The disk quota limit specifies the amount of disk space a user is allowed to use. The warning level specifies the point at which a user is nearing his or her quota limit.
  • Page 32 __________________________________________________________________________________________________ Some of the common Diskpart commands are: • add disk Mirrors the simple volume with focus to the specified disk. • assign Assigns a drive letter or mount point to the volume with focus. • convert basic Converts an empty dynamic disk to a basic disk. •...

  • Page 33: Example Of Using Diskpart

    __________________________________________________________________________________________________ 3.10.1. Example of using Diskpart The following example shows how to configure a volume on the NAS server. In the cmd window, type: c:\>diskpart DISKPART>rescan DISKPART>select disk 1 DISKPART>convert dynamic DISKPART>rem create a simple volume DISKPART>create volume simple size=4000 DISKPART>rem assign drive letter F: to the volume DISKPART>assign letter=F DISKPART>list vol...

  • Page 34: Extending Storage Using Disk Management

    __________________________________________________________________________________________________ 3.11.2. Extending Storage using Disk Management The Disk Management snap-in provides management of hard disks, volumes or partitions. It can be used to extend a dynamic volume only. Notes Disk Management cannot be used to extend basic disk partitions. Guidelines for extending a dynamic volume: •...

  • Page 35: Single Instance Storage

    __________________________________________________________________________________________________ 3.12.2. Single Instance Storage Single Instance Storage (SIS) provides a copy-on-write link between multiple files. Disk space is recovered by reducing the amount of redundant data stored on a server. If a user has two files sharing disk storage by using SIS, and someone modifies one of the files, users of the other files do not see the changes.

  • Page 36: Windows Storage Server Management Console

    __________________________________________________________________________________________________ 3.12.5. Windows Storage Server Management Console The Windows Storage Server Management Console is a user interface in Windows Storage Server 2003 R2 and Windows Unified Data Storage Server 2003 that provides one place to manage files or print serving components.
  • Page 37 Tandberg Data Storage & File Server Management __________________________________________________________________________________________________ 3-17 Tandberg Viking Series Storage Server Administration Manual...
  • Page 38 Tandberg Data Storage & File Server Management __________________________________________________________________________________________________ This Page Intentionally Left Blank 3-18 Tandberg Viking Series Storage Server Administration Manual...

  • Page 39: Volume Shadow Copy Service(Vss)

    Volume Shadow Copy Service(VSS) 4.1. The Volume Shadow Copy Service provides an infrastructure for creating point-in-time snapshots (shadow copies) of volumes. Shadow Copy supports 64 shadow copies per volume under Windows® Storage Server 2003 environment. A shadow copy contains previous versions of the files or folders contained on a volume at a specific point in time.

  • Page 40: Planning For Use Of Shadow Copy

    __________________________________________________________________________________________________ 4.2. Planning for use of Shadow Copy Before Shadow Copy Service is initiated on the NAS appliance and the client interface is made available to end users, consider the followings: • From what volume will shadow copies be taken? •...

  • Page 41: Allocating Disk Space

    Tandberg Data Shadow Copy Service __________________________________________________________________________________________________ 4.2.2. Allocating Disk Space When shadow copies are enabled on a volume, the maximum amount of volume space to be used for the shadow copies can be specified. The default limit is 10 percent of the source volume (the volume being copied).

  • Page 42: Identifying The Storage Area

    __________________________________________________________________________________________________ When using a basic disk as a storage area for shadow copies and converting the disk into a dynamic disk, it is important to take the following precaution to avoid data loss: • If the disk is a non-boot volume and is a different volume from where the original files reside, first dismount and take offline the volume containing the original files before converting the disk containing shadow copies to a dynamic disk.

  • Page 43: Determining Creation Frequency

    Tandberg Data Shadow Copy Service __________________________________________________________________________________________________ 4.2.4. Determining Creation Frequency The more frequently shadow copies are created, the more likely that end users will get the version that they want. However, with a maximum of 64 shadow copies per volume, there is a trade-off between the frequency of making shadow copies and the amount of time that the earlier files will be available.

  • Page 44: Mounted Drives

    Tandberg Data Shadow Copy Service __________________________________________________________________________________________________ 4.2.5. Mounted Drives A mounted drive is a local volume attached to an empty folder (called a mount point) on an NTFS volume. When enabling shadow copies on a volume that contains mounted drives, the mounted drives are not included when shadow copies are taken.
  • Page 45 Tandberg Data Shadow Copy Service __________________________________________________________________________________________________ Tandberg Viking Series Storage Server Administration Manual...

  • Page 46: Shadow Copy Cache File

    Tandberg Data Shadow Copy Service __________________________________________________________________________________________________ 4.3.1. Shadow Copy Cache File The default shadow copy settings allocate 10% of the source volume being copied (with a minimum of 350 MB), and store the shadow copies on the same volume as the original volume. See figure below. The cache file is located in a hidden protected directory entitled “System Volume Information”...
  • Page 47 __________________________________________________________________________________________________ As mentioned previously, the cache file location can be altered to reside on a dedicated volume separate from the volumes containing files shares. See figure below. cache fil e cache fil e The main advantage to storing shadow copies on a separate volume is ease of management and performance.

  • Page 48: Enabling And Creating Shadow Copies

    __________________________________________________________________________________________________ 4.4. Enabling and Creating Shadow Copies Enabling shadow copies on a volume automatically results in several actions: • Creates a shadow copy of the selected volume • Sets the maximum storage space for the shadow copies • Schedules shadow copies to be made at 7 A.M. and 12 noon on weekdays.

  • Page 49: Viewing List Of Shadow Copies

    __________________________________________________________________________________________________ 4.5. Viewing List of Shadow Copies The list of Shadow Copies can be view on a volume using the following method: 1. Right-clicked on the volume or logical drive with shadow copy service enabled and select Properties. 2. Click the Shadow Copies tab. All shadow copies are listed, sorted by the date and time they were created.

  • Page 50: Deleting Shadow Copy Schedule

    __________________________________________________________________________________________________ 7. Use the Advance… controls to specify the recurrence pattern and the starting date and time. The available controls change according to the frequency selected. 8. Click OK. 4.6.2. Deleting Shadow Copy Schedule To delete a shadow copy schedule on a volume: 1.

  • Page 51: Redirecting Shadow Copies To Alternate Volume

    __________________________________________________________________________________________________ Note If shadow copies have already been enabled, the cache file location is grayed out. To change this location after shadow copies have been enabled, all shadow copies must be deleted and cannot be recovered. Remember enabling Shadow Copies creates a Shadow Copy by default.

  • Page 52: Disabling Shadow Copies

    __________________________________________________________________________________________________ 4.6.4. Disabling Shadow Copies When shadow copies are disabled on a volume, all existing shadow copies on the volume are deleted as well as the schedule for making new shadow copies. To disable shadow copies on a volume: 1. Right-clicked on the volume or logical drive with shadow copy service enabled and select Properties.

  • Page 53: Shadow Copies For Shared Folders

    Tandberg Data Shadow Copy Service __________________________________________________________________________________________________ 4.7. Shadow Copies for Shared Folders Shadow Copies are accessed over the network by supported clients and protocols. There are two sets of supported protocols, SMB and NFS. All other protocols are not supported; this would include HTTP, FTP, AppleTalk, and NetWare Shares.
  • Page 54 Tandberg Data Shadow Copy Service __________________________________________________________________________________________________ Users access shadow copies with Windows Explorer by selecting View, Copy, or Restore, from the Previous Versions tab. See figure below. Both individual files and folders may be restored. When users view a network folder hosted on the NAS appliance for which shadow copies are enabled, old versions (prior to the snapshot) of a file or directory are available.

  • Page 55: Nfs Access To Shadow Copies

    Tandberg Data Shadow Copy Service __________________________________________________________________________________________________ 4.7.2. NFS Access to Shadow Copies UNIX users can independently access previous versions of files stored on NFS shares via the NFS client; no additional software is required. Server for NFS exposes each of a share's available shadow copies as a pseudo- subdirectory of the share.

  • Page 56: Recovery Of Files And Folders

    __________________________________________________________________________________________________ 4.8. Recovery of Files and Folders There are three common situations that may require recovery of files or folders: • Accidental file deletion, the most common situation. • Accidental file replacement, which may occur if a user selects Save instead of Save As.

  • Page 57: Recovering Overwritten Or Corrupted Files

    __________________________________________________________________________________________________ 4.8.2. Recovering Overwritten or Corrupted Files Recovering an overwritten or corrupted file is easier than recovering a deleted file because the file itself can be right-clicked instead of the folder. To recover an overwritten or corrupted file use the following procedure: 1.

  • Page 58: Recovering Folders

    __________________________________________________________________________________________________ 4.8.3. Recovering Folders To recover a folder, use the following procedure: 1. Position the cursor so that it is over a blank space in the folder that will be recovered. If the cursor hovers over a file, that file will be selected.

  • Page 59: Backup & Shadow Copies

    __________________________________________________________________________________________________ 4.9. Backup & Shadow Copies As mentioned previously, Shadow Copies are only available on the network via the client application and only at a file or folder level as opposed to the entire volume. Hence the standard backup associated with a volume backup will not work to back up the previous versions of the file system.
  • Page 60 __________________________________________________________________________________________________ The transport process is accomplished through a series of DISKRAID command steps: 1. Create a shadow copy of the source data on the source server (read-only). 2. Mask off (hide) the shadow copy from the source server. 3. Unmask the shadow copy to a target server. 4.

  • Page 61: User & Group Management

    User & Group Management 5.1. There are two system environments for users and groups: workgroup and domain. Because users and groups in a domain environment are managed through standard Windows or Active Directory domain administration methods, this document discusses only local users and groups, which are stored and managed on the NAS appliance.

  • Page 62: User & Group Name Planning

    __________________________________________________________________________________________________ Administering users and groups in a domain environment is similar in a mechanical sense to administering them in a workgroup environment. If using an Active Directory domain controller, the Computer Management tool allows for adding, modifying, and removing users in the same context as in a workgroup environment.

  • Page 63: Managing Group Names

    __________________________________________________________________________________________________ • Last name followed by first initial (doej for Jane Doe) Guidelines must be in place for instances when two users have the same initials or name. For example, a number can be added to the end of the username (jdoe1 and jdoe2).
  • Page 64 Tandberg Data User & Group Management __________________________________________________________________________________________________ This Page Intentionally Left Blank Tandberg Viking Series Storage Server Administration Manual...

  • Page 65: Folder & Share Management

    Folder & Share Management The Tandberg Viking Series NAS appliance supports several file sharing protocols, including DFS, NFS, FTP, HTTP, and Microsoft SMB. This chapter discusses overview information as well as procedural instructions for the setup and management of the file shares for the supported protocols. In addition, discussions on security at the file level and at the share level are included in this chapter.

  • Page 66: Managing File Level Permissions

    __________________________________________________________________________________________________ 6.2. Managing File Level Permissions Security at the file level is managed using Windows Explorer available from the Desktop of the NAS appliance. To access the NAS server Desktop from use either the direct attached method or Windows Remote Desktop. File level security includes settings for permissions, ownership, and auditing for individual files.
  • Page 67 __________________________________________________________________________________________________ 3. Several options are available in the Security tab dialog box: To add users and groups to the permissions list, click Add. Then follow the dialog box instructions. To remove users and groups from the permissions list, highlight the desired user or group and then click Remove. The center section of the Security tab provides a listing of permission levels.
  • Page 68 __________________________________________________________________________________________________ To modify specific permissions assigned to a particular user or group for a selected file or folder in the Advanced screen: 1. Select the desired user or group. 2. Click Edit. 3. Check all the permissions that you want to enable, and clear the permissions that you want to disable.
  • Page 69 __________________________________________________________________________________________________ Replace permission entries on all child objects with entries shown here that apply to child objects. This allows all child folders and files to inherit the current folder permissions by default. 5. Another area of the Advanced Security Settings is the Auditing tab.
  • Page 70 __________________________________________________________________________________________________ 6. Click Add to display the Select User or Group dialog box. Note Click Advanced to search for users or groups. 7. Select the user or group. 8. Click OK. Figure below illustrates the Auditing Entry screen that is displayed.
  • Page 71 __________________________________________________________________________________________________ 9. Select the desired Successful and Failed audits for the user or group as shown in Figure 40. 10. Click OK. Note Auditing must be enabled to configure this information. Use the local Computer Policy Editor to configure the audit policy on the NAS appliance. 11.
  • Page 72 __________________________________________________________________________________________________ 12. The current owner of the file or folder is listed at the top of the screen. To take ownership: a. Select the appropriate user or group from the Change owner to list. b. If it is also necessary to take ownership of subfolders and files, enable the Replace owner on subcontainers and objects box.

  • Page 73: Share Management

    __________________________________________________________________________________________________ 6.3. Share Management There are several ways to set up and manage shares. Methods include using a command line interface, Windows Explorer, or NAS Management Console. As previously mentioned, the file sharing security model of the NAS appliance is based on the NTFS file-level security model. Share security seamlessly integrates with file security.

  • Page 74: Integrating Local File System Security Into Windows Domain Environments

    Tandberg Data Folder & Share Management __________________________________________________________________________________________________ 6.3.2. Defining Access Control Lists The Access Control List (ACL) contains the information that dictates which users and groups have access to a share, as well as the type of access that is permitted. Each share on an NTFS file system has one ACL with multiple associated user permissions.

  • Page 75: Comparing Administrative & Standard Shares

    __________________________________________________________________________________________________ 6.3.4. Comparing Administrative & Standard Shares CIFS supports both administrative Administrative shares are shares with a last character of $. Administrative shares are not included in the list of shares when a client browses for available shares on a CIFS server. Standard shares are shares that do not end in a $ character.

  • Page 76: Managing Shares

    __________________________________________________________________________________________________ 6.3.6. Managing Shares Shares can be managed through the Windows Storage Server Management Console. Tasks include: • Creating a new share • Deleting a share • Modifying share properties • Publish in DFS (See “Publishing a new share in DFS”) Each of these tasks is discussed in this section.

  • Page 77: Stopping A Share

    __________________________________________________________________________________________________ Stopping a Share 6.3.6.2. Caution Before deleting a share, warn all users to exit that share and confirm that no one is using the share. To delete a share: 1. On the Windows Storage Server Management console, right-click on the share that you want to stop sharing.
  • Page 78 __________________________________________________________________________________________________ 2. The name and path of the selected share is displayed. 3. After all share information has been entered, click OK. The setting is updated. 6-14 Tandberg Viking Series Storage Server Administration Manual...
  • Page 79 __________________________________________________________________________________________________ Windows Sharing From the Share Properties menu: 1. Enter a descriptive Comment, and the User limit (optional). See figure below for an example of the screen display. 2. Select Offline settings. 3. Set the permissions. The Share Permissions tab lists the currently approved users for this share.
  • Page 80 __________________________________________________________________________________________________ UNIX Sharing The UNIX (NFS) sharing need to be access using Windows Explorer: 1. Using the Windows Explorer, navigate to the share folder and right- click. Select Properties. Go to the NFS Sharing tab. 2. Select the radio button Share this folder to enable UNIX sharing (NFS).
  • Page 81 __________________________________________________________________________________________________ No access—Use this permission to restrict all access to the share. 5. Select whether or not to allow root access by checking the box. Read-only + Root—Use this permission to restrict write access to the share. Use this permission to assign administrative access to the share.
  • Page 82 __________________________________________________________________________________________________ Web Sharing (HTTP) The HTTP sharing can be enabled using Windows Explorer: 1. Select Using the Windows Explorer, navigate to the share folder and right-click. Select Properties. Go to the Web Sharing tab. 2. Select the radio button Share this folder to enable web sharing (HTTP).
  • Page 83 __________________________________________________________________________________________________ AFP (Appletalk) Sharing AppleTalk shares can be set up only after AppleTalk Protocol and File Services for Macintosh have been installed on the NAS appliance. Note AppleTalk shares should not be created on clustered resources as data loss can occur due to local memory use.
  • Page 84 __________________________________________________________________________________________________ Instaling the File Services for Macintosh To install the AppleTalk Protocol: 1. From the desktop of the NAS server, click Start, navigate to Control Panel > Add or Remove Programs. Click on Add/Remove Windows Components and navigate to the Other Network and File and Print Services, and then click on Details….
  • Page 85 __________________________________________________________________________________________________ Setting AppleTalk Protocol Properties To set up AppleTalk shares: 1. From Windows Storage Server Management console, drop down the Share Folder Management. Select the Shares folder and then right- click. From the pop-up menu, click on New Share. 2. Step through the Share a Folder Wizard to create shares. 3.
  • Page 86 __________________________________________________________________________________________________ To change AppleTalk settings: 1. On the Windows Storage Server Management console, right-click on the AppleTalk share that you want to change settings. Click Properties from the pop-up menu. 2. Enter a user limit. 3. Enter password information. 4. Indicate whether the share has read only permission or read write permission by checking or un-checking the checkbox.

  • Page 87: File Server Recourse Manager

    __________________________________________________________________________________________________ 6.4. File Server Recourse Manager With the increasing demand on storage resources, as organizations rely more heavily on data than ever before, IT administrators face the challenge of overseeing a larger and more complex storage infrastructure, while at the same time, tracking the kind of information available in it.

  • Page 88: Opening File Server Resource Manager

    __________________________________________________________________________________________________ 6.4.2. Opening File Server Resource Manager File Server Resource Manager is a Microsoft Management Console (MMC) snap-in and is located in Administrative Tools on the Start menu. To open File Server Resource Manager: • On the Start menu, click Programs, click Administrative Tools, and then click File Server Resource Manager.

  • Page 89: Quota Management

    __________________________________________________________________________________________________ The following is a list of tasks that you can perform from each respective node in File Server Resource Manager: 6.4.3. Quota Management • Create, manage, and obtain information about quotas, which are used to set a space limit on a volume or folder. By defining notification thresholds, you can send e-mail notifications, log an event, run a command or script, or generate reports when users approach or exceed a quota.

  • Page 90: Using Command-Line Tools For File Server Resource Manager

    __________________________________________________________________________________________________ 6.4.6. Using Command-Line Tools for File Server Resource Manager If you prefer to work from the command line, you can use the following tools: • Dirquota.exe. Use to create and manage quotas and quota templates. • FileScrn.exe. Use to create and manage file screens, file screening exceptions, and file groups.

  • Page 91: Distributed File System (Dfs)

    Distributed File System (DFS) 7.1. One of the goals of information technology (IT) groups in medium and large organizations is to manage file servers and their resources efficiently while keeping them available and secure for users. As organizations expand to include more users and servers—whether they are located in one site or in geographically distributed sites—administrators find it increasingly difficult to keep users connected to the files they need.

  • Page 92: Dfs Namespaces

    Tandberg Data Distributed File System __________________________________________________________________________________________________ As the figure shows, when a user attempts to access a folder in the namespace (1), the client computer contacts a namespace server. The namespace server sends the client computer a referral that contains a list of servers that host the shared folders (called folder targets) associated with the folder.
  • Page 93 __________________________________________________________________________________________________ • Namespace server. A namespace server hosts a namespace. The namespace server can be a member server or a domain controller. • Namespace root. The root is the starting point of the namespace. In the previous figure, the name of the root is Public, and the namespace path is \\Contoso\Public.

  • Page 94: Dfs Replication

    __________________________________________________________________________________________________ 7.3. DFS Replication DFS Replication is the new state-based, multimaster replication engine in Windows Server 2003 R2. Although some DFS Replication concepts and processes are similar to the concepts and processes in File Replication service (FRS), there are several important differences that you should be aware of before you deploy DFS Replication.

  • Page 95: Dfs Initial Replication

    __________________________________________________________________________________________________ 7.3.2. DFS Initial Replication When you first set up replication, you must choose a primary member. Choose the member that has the most up-to-date files that you want replicated to all other members of the replication group, because the primary member's content is considered "authoritative."...

  • Page 96: Dfs Management Snap-In

    __________________________________________________________________________________________________ 7.4. DFS Management Snap-in The DFS Management snap-in is the graphical user interface tool for managing DFS Namespaces and DFS Replication. This snap-in is new and differs from the Distributed File System snap-in in Windows Server 2003. Therefore, before you begin using DFS Namespaces and DFS Replication, you might want to review the components of this snap-in, which are shown in the following figure and described in the sections that follow.
  • Page 97 Tandberg Data Distributed File System __________________________________________________________________________________________________ Notes If you are not familiar with namespace terminology, see the section "DFS Namespaces" earlier section. Replication node The following figure shows the elements under the Replication node in the console tree. As the figure shows, the Replication node contains the replication groups you create as well as any existing replication groups that you add to the console display.

  • Page 98: Deploying Namespace (Step-By-Step Guide)

    __________________________________________________________________________________________________ 7.5. Deploying Namespace (Step-by-Step Guide) The tasks in this section walk you through the process of deploying a namespace that looks similar to the namespace shown in the figure that appears in "DFS Namespaces" earlier in this chapter. 7.5.1. Create a Namespace To create a namespace: 1.

  • Page 99: Add A Namespace Server (Domain)

    __________________________________________________________________________________________________ 7.5.2. Add a Namespace Server (Domain) If you created a domain-based namespace, perform this task to specify an additional server to host the namespace. Doing so increases the availability of the namespace and allows you to place namespace servers in the same sites as users.

  • Page 100: Add Folders To Namespace

    __________________________________________________________________________________________________ Notice that the user or group you added shows "Explicit" in the How Permission Is Granted column. "Explicit" means that you can remove the user or group from the delegation list by right-clicking the user or group, and then clicking Remove. Any users or groups that show "Inherited" have inherited management permissions from Active Directory, and you cannot remove them from the delegation list using the DFS Management snap-in.
  • Page 101 __________________________________________________________________________________________________ Next, you add two folders with targets to the namespace. You create one folder named Tools within the Software folder, and you create another folder named Training Guides directly under the root named Public. To create a folder named Tools in the namespace: 1.
  • Page 102 __________________________________________________________________________________________________ 4. Click New Shared Folder. 5. In the Create Share dialog box, in the Share name box, type Tools, and then enter the local path where you want the shared folder to be created. If the folder does not exist, you are prompted to create it. Click OK to close all dialog boxes.

  • Page 103: Change How Target Are Ordered In Referrals

    __________________________________________________________________________________________________ 7.5.5. Change How Target are Ordered in Referrals In this task, you change settings that optimize how targets are ordered in referrals. If you are not familiar with referrals, a referral is a list of targets that a client computer receives from a domain controller or namespace server when the user accesses a namespace root or folder with targets in the namespace.

  • Page 104: Rename And Move A Folder

    __________________________________________________________________________________________________ 1. Targets in the same site as the client are listed in random order at the top of the referral. 2. Targets outside of the client’s site are listed in order of lowest cost to highest cost. Referrals with the same cost are grouped together and within each group the targets are listed in random order.

  • Page 105: Replicate A Folder In The Namespace Using Dfs Replication

    __________________________________________________________________________________________________ To rename the Training Guides folder: 1. In the console tree of the DFS Management snap-in, right-click the Training Guides folder, and then click Rename Folder. 2. In the Rename Folder dialog box, in New name, type Training Demos. To move the Training Demos folder: •...
  • Page 106 __________________________________________________________________________________________________ To enable DFS Replication on the Tools folder: 1. In the console tree of the DFS Management snap-in, right-click the Tools folder, and then click Replicate Folder. 2. Follow the steps in the Replicate Folder Wizard and supply the information in the following fields: Replication Group and Replicated Folder Name - Accept the defaults.

  • Page 107: Create A Diagnostic Report

    __________________________________________________________________________________________________ From the Replication node, you can manage aspects of DFS Replication, such as the schedule and bandwidth usage, file and subfolder filters, and the topology (a framework of replication paths between members). On the Replicated Folders tab in the details pane, you can also view the namespace path that corresponds to the replicated folder, as shown in the following figure.

  • Page 108: Browse The Namespace

    __________________________________________________________________________________________________ Members to Include - Accept the defaults. Options - Ensure that Yes, count backlogged files in this report is selected, and also click the Count the replicated files and their sizes on each member check box. Review Settings and Create Report - Click Create to create the diagnostic report.

  • Page 109: Test Failover

    __________________________________________________________________________________________________ 2. In Windows Explorer, click the Folders button to display the Public root in the folder tree. 3. In the folder tree, right-click Public, and then click Properties to open the Properties dialog box. 4. On the DFS tab, review the paths listed under Referral list. These are the root targets in the root referral that the client received when it accessed \\server_or_domain\Public.

  • Page 110: Deploying Dfs Replication (Step-By-Step Guide)

    __________________________________________________________________________________________________ 7.6. Deploying DFS Replication (Step-by-Step Guide) The tasks in this section walk you through the process of deploying DFS Replication, adding a member to a replication group, publishing a replicated folder in a namespace, and creating a diagnostic report. 7.6.1.
  • Page 111 __________________________________________________________________________________________________ Next, create a replication group to replicate files between the two servers. To create a replication group and two replicated folders: 1. In the console tree of the DFS Management snap-in, right-click the Replication node, and then click New Replication Group. 2.
  • Page 112 __________________________________________________________________________________________________ After you finish the New Replication Group Wizard, click the new replication group named Data Distribution located under the Replication node in the console tree as shown in the following figure: Notice the four tabs in the details pane: Memberships, Connections, Replicated Folders, and Delegation.

  • Page 113: Add A New Member To Replication Group

    __________________________________________________________________________________________________ 7.6.2. Add a New Member to Replication Group In this task, you add a third server to the Data Distribution replication group and specify where one of the two replicated folders, Antivirus Signatures, will be stored on the new member. You'll use a new feature in DFS Replication to specify that the LOB Data replicated folder is not replicated to the new member.
  • Page 114 __________________________________________________________________________________________________ Confirmation - Click Close to close the wizard. Replication Delay - Click OK to close the dialog box that warns you about the delay in initial replication. After you finish the wizard, click Data Distribution in the console tree, and then review the contents of the Connections tab.

  • Page 115: Share And Publish Replicated Folders In A Namespace

    __________________________________________________________________________________________________ 7.6.3. Share and Publish Replicated Folders in a Namespace When you created replicated folders in the previous tasks, you specified the local path of a folder on each member of the replication group. Unless the local path on each server was previously shared, users cannot access the replicated folders after they are created.

  • Page 116: Create A Replication Group For Collection Purposes

    Tandberg Data Distributed File System __________________________________________________________________________________________________ Next, review the namespace path listed in the Replicated Folders tab, which should look similar to the following figure. You can see that the LOB Data replicated folder is published in a namespace but the Antivirus Signatures replicated folder is not. To access the LOB Data folder in the namespace, in the Run dialog box, type \\server_or_domain\Public\Software\LOB Data.
  • Page 117 __________________________________________________________________________________________________ IMPORTANT When you create a new replication group, replication does not begin immediately. The topology and DFS Replication settings must be replicated to all domain controllers, and each member in the replication group must poll its closest domain controller to obtain these settings. The amount of time this takes depends on Active Directory replication latency and each member's long polling interval (60 minutes).

  • Page 118: Create A Diagnostic Report

    __________________________________________________________________________________________________ Replication Delay - Click OK to close the dialog box that warns you about the delay in initial replication. After you finish the wizard, click the Branch Backups replication group in the console tree and view the Memberships tab in the details pane. Notice that two replicated folders were created, Projects and Proposals, as shown in the following figure: In the previous figure, notice that the path of the Projects and Proposals...
  • Page 119 __________________________________________________________________________________________________ Review the diagnostic report created for the Tools replication group. In particular, take a look at the following sections: • Note the DFS Replication efficiency savings. This savings will change over time as files are added and changed. • Review any errors or warnings, if any, for the members.
  • Page 120 Tandberg Data Distributed File System __________________________________________________________________________________________________ This Page Intentionally Left Blank 7-30 Tandberg Viking Series Storage Server Administration Manual...

  • Page 121: Microsoft Services For Network File System (Msnfs)

    Microsoft Services for Network File System (MSNFS) Microsoft Services for Network File System is a comprehensive software package designed to provide complete UNIX environment integration into a Windows NT, Windows 2000, Windows Storage Server 2003, or Active Directory domain file server. Services for NFS manages tasks on both Windows and UNIX platforms.

  • Page 122: Unix Identity Management

    __________________________________________________________________________________________________ The following features that were previously available in Services for UNIX 3.5 are not included in MSNFS: • Gateway for NFS • Server for PCNFS • All PCNFS components of Client for NFS 8.1.1. UNIX Identity Management Identity Management for UNIX makes it easy to integrate users of Windows operating systems into...

  • Page 123: Microsoft Services For Nfs Components

    __________________________________________________________________________________________________ • Enable UNIX-based client computers to access resources on computers running Windows Server 2003 R2. Your company may have UNIX clients accessing resources, such as files, on UNIX file servers. To take advantage of new features in Windows Server 2003 R2 such as Shadow Copies for Shared Folders, you can move resources from your UNIX servers to computers running Windows Server 2003 R2.

  • Page 124: Microsoft Services For Nfs Command-Line Tools

    __________________________________________________________________________________________________ To open Microsoft Services for Network File System: • Click Start, point to Administrative Tools, and click Microsoft Services for Network File System. Notes To perform this procedure, you must be a member of the Administrators group on the local computer, or you must have been delegated the appropriate authority. If the computer is joined to a domain, members of the Domain Admins group might be able to perform this procedure.

  • Page 125: Test Scenario

    __________________________________________________________________________________________________ • umount. Removes NFS-mounted drives. 8.5. Test Scenario This test scenario requires you to deploy Microsoft Services for NFS in a lab environment to assess how this technology would function if deployed in your production environment. The instructions provided in this document will help you: •...

  • Page 126: Setting Up The Environment For Microsoft Services For Nfs

    __________________________________________________________________________________________________ Notes By default, Server for NFS supports UNIX client computers using NFS version 2 or version 3. You can override this, however, and configure Server for NFS to allow access only to clients running NFS version 2. For instructions, see "Configuring Server for NFS"...

  • Page 127: Create Test User Accounts

    Tandberg Data Microsoft Services for Network File System (MSNFS) __________________________________________________________________________________________________ 8.6.3. Create test user accounts For the purposes of this test, you can create several fictitious users. For each user, you can create one Windows security account and one UNIX security account, giving the two accounts different user names.

  • Page 128: Configuring Nfs Authentication

    __________________________________________________________________________________________________ To install Microsoft Services for NFS: 1. On the computer on which you want to install Microsoft Services for NFS, install Windows Server 2003 R2. 2. In Control Panel, double-click Add or Remove Programs. 3. Click Add/Remove Windows Components, click Other Network File and Print Services, and then click Details.
  • Page 129 __________________________________________________________________________________________________ To specify where UNIX user and group information is stored: 1. On the computer running User Name Mapping, open Microsoft Services for NFS. To open Microsoft Services for NFS, click Start, point to Administrative Tools, and then click Microsoft Services for Network File System.

  • Page 130: Edit The .Maphosts File

    __________________________________________________________________________________________________ Notes To perform this procedure, you must be a member of the Administrators group on the local computer, or you must have been delegated the appropriate authority. 8.6.6.2. Edit the .maphosts file Next, you need to add entries to the .maphosts file, which is installed with User Name Mapping.

  • Page 131: Create A User Map

    __________________________________________________________________________________________________ A .maphosts file with the following contents allows access by all computers except computers named rogue_host and malicious_wks: rogue_host - malicious_wks - In the next example, rogue_host is denied access even though it appears in the list without a minus sign (–) because it follows a minus sign on its own line: R2_host UNIX_host...

  • Page 132: Create A Group Map

    __________________________________________________________________________________________________ Notes To perform this procedure, you must be a member of the Administrators group on the local computer, or you must have been delegated the appropriate authority. Notes You can only map one user name to another user name at a time. If you want to map multiple user names with a single user name, you must repeat steps 6 and 7 in this procedure for each additional user name to map.

  • Page 133: Specifying The User Name Mapping Server

    __________________________________________________________________________________________________ To restart the User Name Mapping service: 1. On the computer running the User Name Mapping service, click Start, point to Administrative Tools, and click Services. 2. In the list, right-click User Name Mapping, click Stop, wait for the service to stop, and then click Start.
  • Page 134 __________________________________________________________________________________________________ To create a shared folder using NFS sharing: 1. On the computer running Server for NFS, create a folder to use as the NFS shared folder. 2. Right-click the folder you created and click NFS Sharing. 3. Select Share this folder. 4.

  • Page 135: Specifying Default Permissions For New Files And Folders

    __________________________________________________________________________________________________ 8.6.9. Specifying default permissions for new files and folders You can specify the default permissions that will be applied to any file or folder created on an NFS shared resource by the computer running Client for NFS. You can assign Read, Write, and Execute permissions to Owner, Group, and Others.

  • Page 136: Add Mapsvc.exe To The Exception List

    __________________________________________________________________________________________________ To open ports in Windows Firewall: 1. On a computer running the User Name Mapping service or Server for NFS, click Start, click Run, type firewall.cpl, and then click 2. Click the Exceptions tab, and then click Add Port. 3.

  • Page 137: Enable File And Printer Sharing For Administration Tools

    __________________________________________________________________________________________________ 5. Click OK two times. 8.6.10.3. Enable file and printer sharing for administration tools On the computer hosting the Microsoft Services for NFS snap-in and Microsoft Services for NFS command-line tools, you must enable file and printer sharing in Windows Firewall. To enable file and printer sharing: 1.

  • Page 138: Test 2: On The Computer Running Client For Nfs, Create A Test File And Verify Its Permissions

    __________________________________________________________________________________________________ 8.6.11.2. Test 2: On the computer running Client for NFS, create a test file and verify its permissions. The test is successful if you can create a new document, and its ownership and permission match the default file permissions that you had specified. To create a test file and verify its permissions: 1.

  • Page 139: Test 4: On A Unix Client, Create A Test File And Verify The File

    __________________________________________________________________________________________________ 8.6.11.4. Test 4: On a UNIX client, create a test file and verify the file permissions match, from both Windows and UNIX. The test is successful if you can create the text file and the file permissions match from both Windows and UNIX To create a test file and verify the file permissions match from both Windows and UNIX: 1.

  • Page 140: Using Remote Desktop For Msnfs

    __________________________________________________________________________________________________ 8.7. Using Remote Desktop for MSNFS Windows Remote Desktop is available for remote administration of Services for UNIX. This service let users connect to machines, log on, and obtain command prompts remotely. See the following Table for a list of commonly used commands.

  • Page 141: Using Iscsi Software Target

    __________________________________________________________________________________________________ Using iSCSI Software Target Some Tandberg Viking Series NAS appliances use the Microsoft® Windows® Unified Data Storage Server 2003 operating system. This operating system provides unified storage server management capabilities, simplified setup and management of storage and shared folders, and support for Microsoft iSCSI Software Target.

  • Page 142: Snapshots

    __________________________________________________________________________________________________ 9.1.2. Snapshots To facilitate backup and recovery operations, you can schedule and create snapshots of iSCSI virtual disks. A snapshot is a point-in-time, read-only copy of an iSCSI virtual disk. Snapshots are typically used as interim copies of data that has been modified since the most recent backup. Snapshots offer the following advantages: •...
  • Page 143 __________________________________________________________________________________________________ 7. To enter additional identifiers, or if you are using an identifier other than an IQN (DNS domain name, IP address, or MAC address): Click Advanced. On the Advanced Identifiers page, click Add. Tandberg Viking Series Storage Server Administration Manual...

  • Page 144: Create Virtual Disk Wizard

    __________________________________________________________________________________________________ Select the identifier type from the Identifier Type list and type the identifier in the Value field. Repeat steps b and c for each identifier you want to add. Click OK. Click OK again to close the Advanced Identifiers page. 8.

  • Page 145: Import Virtual Disk Wizard

    __________________________________________________________________________________________________ 3. Click Next on the Welcome page of the wizard. 4. On the File page, specify the full path to use as the virtual disk and click Next. 5. On the Size page, specify the size to use for the virtual disk and click Next.

  • Page 146: Extend Virtual Disk Wizard

    __________________________________________________________________________________________________ 9.1.7. Extend Virtual Disk Wizard This section describes how to extend a virtual disk using the Extend Virtual Disk Wizard. 1. In the Microsoft iSCSI Software Target MMC snap-in, click the Devices node. 2. On the details view (right pane) of the Devices node, right-click a virtual disk and select Extend Virtual Disk.

  • Page 147: Hardware Providers

    __________________________________________________________________________________________________ 9.2. Hardware Providers To support advanced management of iSCSI virtual disks and snapshots, you can use the following hardware providers, which come preinstalled on the Viking Series NAS applaince: • Microsoft iSCSI Software Target Virtual Disk Service Hardware Provider Microsoft Windows Server 2003 introduced Virtual Disk Service (VDS), a set of application programming interfaces (APIs) that provides a single interface for managing disks.
  • Page 148 Tandberg Data Using iSCSI Software Targets __________________________________________________________________________________________________ This Page Intentionally Left Blank Tandberg Viking Series Storage Server Administration Manual...

  • Page 149: Remote Access Methods & Monitoring

    Remote Access Methods & Monitoring The Tandberg Data Viking Series NAS appliance comes from the factory with full remote manageability. Several methods of remote access are provided. These options let administrators use interfaces with which they are already familiar. 10.1. Remote Desktop The NAS appliance supports Remote Desktop, with a license for two concurrently running open sessions.

  • Page 150: Telnet Server

    __________________________________________________________________________________________________ 10.2. Telnet Server Telnet Server is a utility that lets users connect to machines, log on, and obtain a command prompt remotely. Telnet Server is preinstalled on the NAS server, but must be activated before use. Caution For security reasons, the Telnet Server service must be restarted each time the server is restarted.
  • Page 151 Tandberg Data Remote Access Methods & Monitoring __________________________________________________________________________________________________ This Page Intentionally Left Blank 10-3 Tandberg Viking Series Storage Server Administration Manual...

This manual is also suitable for:

Viking fs-412Viking fs-1600

Table of Contents