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
Related publications available from Tandberg Data Asia:
Part No. Title
6582B7 Tandberg Viking FS-1600 NAS Hardware User
Manual
6582A7 Tand
Manual
658297 Tand
Manual
berg Viking FS-1500 NAS Hardware User
berg Viking FS-412 NAS Hardware User
This publication may describe designs for which patents are granted or pending.
By publishing this information, Tandberg Data Asia conveys no license
er any patent or any other rights.
und
effort has been made to avoid errors in text and diagrams. However,
Every
Tandberg
pear
It
is the policy of Tandberg Data Asia to improve products as new techniques
and
the
We
Data Asia assumes no responsibility for any errors which may ap-
in this publication.
components become available. Tandberg Data Asia therefore reserves
right to change specifications at any time.
would appreciate any comments on this publication.
__________________________________________________________________________________________________
Table of Contents
Table of Contents i
1. System Overview 1-1
1.1. Product Information 1-1
1.1.1. Product Manageability 1-2
1.2. Redundancy 1-2
1.2.1. Configuring RAID using 4 HDD (1U) 1-3
1.2.2. Configuring RAID using 16 HDD (3U) 1-4
1.2.3. System Volume (SV) 1-5
1.2.4. Data Volume (DV) 1-5
1.4. Deployment 1-5
1.4.1. File Server Consolidation 1-5
1.4.2. Multi-protocol Environments 1-5
1.4.3. Protocol and platform transitions 1-5
1.4.4. Remote office deployment 1-5
1.5. Environment scenarios 1-6
1.5.1. Workgroup 1-6
1.5.2. Domain 1-6
1.6. User Interfaces 1-7
1.6.1 Direct Attached Method 1-7
1.6.2. Using Windows Remote Desktop Console 1-7
2. Setting Up & Administration 2-1
2.1. Using Windows Remote Desktop 2-2
2.1.1. Improper Closure of Remote Desktop 2-2
2.2. Telnet Server 2-2
2.2.1. Enabling Telnet Server 2-3
2.3. Setup Completion 2-3
2.4. Managing System Storage 2-4
2.5. Creating and Managing Users and Groups 2-4
2.2.1. Joining Workgroup & Domain 2-4
2.6. Creating and Managing File Shares 2-4
2.7. Running Microsoft Windows Update 2-4
2.8. Using Ethernet NIC Teaming 2-5
2.9. Installing 3rd Party Software Applications 2-5
3. Storage & File Server Management 3-1
3.1. Storage Management Element 3-1
3.1.1. Physical Storage Element 3-1
3.1.1.1. Disk Array 3-2
3.1.1.2. Fault Tolerance 3-2
3.1.1.3. Online Spares (Hot-Spares) 3-2
3.1.2. Logical Storage Element 3-3
3.1.2.1. Logical Drives (LUNs) 3-3
3.1.2.2. Partitions 3-3
3.1.2.3. Volumes 3-3
3.1.3. File System Element 3-4
3.1.4. File Sharing Element 3-4
3.2. Volume Shadow Copy Service Overview 3-4
3.3. Using Storage Element 3-5
3.4. Network Adapter Teaming 3-5
i
Tandberg Data Table of Content
__________________________________________________________________________________________________
Disk Management 3-5
3.5.
3.6. Guidelines for Managing Disks & Volumes 3-7
3.7. RAID & Volume Management 3-8
3.8. Scheduling Defragmentation 3-10
3.9. Disk Quotas 3-10
3.10. Using Diskpart 3-11
3.10.1. Example of using Diskpart 3-13
3.11. Adding Storage 3-13
3.11.1. Expanding Storage 3-13
3.11.2. Extending Storage using Disk Management 3-14
3.12. File Services Features in Windows Storage Server 2003 R2 3-14
3.12.1. Storage Manager for SANs 3-14
3.12.2. Single Instance Storage 3-15
3.12.3. File Server Resource Manage 3-15
3.12.4. Windows SharePoint Services 3-15
3.12.5. Windows Storage Server Management Console 3-16
4. Volume Shadow Copy Service(VSS) 4-1
4.1. Volume Shadow Copy Service Overview 4-1
4.2. Planning for use of Shadow Copy 4-2
4.2.1. Identifying the Volume 4-2
4.2.2. Allocating Disk Space 4-3
4.2.3. Identifying the Storage Area 4-4
4.2.4. Determining Creation Frequency 4-5
4.2.4. Shadow Copies & Disk Defragmentation 4-5
4.2.5. Mounted Drives 4-6
4.3. Managing Shadow Copies 4-6
4.3.1. Shadow Copy Cache File 4-8
4.4. Enabling and Creating Shadow Copies 4-10
4.5. Viewing List of Shadow Copies 4-11
4.6. Scheduling Shadow Copies 4-11
4.6.1. Setting Shadow Copy Schedule 4-11
4.6.2. Deleting Shadow Copy Schedule 4-12
4.6.3. Viewing Properties of Shadow Copies 4-12
4.6.4. Redirecting Shadow Copies to Alternate Volume 4-13
4.6.4. Disabling Shadow Copies 4-14
4.7. Shadow Copies for Shared Folders 4-15
4.7.1. SMB Access to Shadow Copies 4-15
4.7.2. NFS Access to Shadow Copies 4-17
4.8. Recovery of Files and Folders 4-18
4.8.1. Recovering Deleted Files or Folders 4-18
4.8.2. Recovering Overwritten or Corrupted Files 4-19
4.8.3. Recovering Folders 4-20
4.9. Backup & Shadow Copies 4-21
4.10. Shadow Copy Transport 4-21
5. User & Group Management 5-1
5.1. Overview 5-1
5.2. Domain versus Workgroup Environments 5-1
5.3. User & Group Name Planning 5-2
5.3.1. Managing User Names 5-2
5.3.2. Managing Group Names 5-3
5.4. Workgroup User & Group Management 5-3
6. Folder & Share Management 6-1
ii
Tandberg Data Table of Content
__________________________________________________________________________________________________
Folder Management 6-1
6.1.
6.2. Managing File Level Permissions 6-2
6.3. Share Management 6-9
6.3.1. Share Considerations 6-9
6.3.2. Defining Access Control Lists 6-10
6.3.3. Integrating Local File System Security into Windows Domain
Environments 6-10
6.3.4. Comparing Administrative & Standard Shares 6-11
6.3.5. Planning for Compatibility between File Sharing Protocols 6-11
6.3.5.1. NFS Compatibility Issues 6-11
6.3.6. Managing Shares 6-12
6.3.6.1. Creating a New Share 6-12
6.3.6.2. Stopping a Share 6-13
6.3.6.3. Modifying Share Properties 6-13
6.4. File Server Recourse Manager 6-23
6.4.1. Using the File Server Resource Manager Component 6-23
6.4.2. Opening File Server Resource Manager 6-24
6.4.3. Quota Management 6-25
6.4.4. File Screening Management 6-25
6.4.5. Storage Report Management 6-25
6.4.6. Using Command-Line Tools for File Server Resource Manager 6-26
7. Distributed File System (DFS) 7-1
7.1. Overview 7-1
7.2. DFS Namespaces 7-2
7.3. DFS Replication 7-4
7.3.1. DFS Replication Concept 7-4
7.3.2. DFS Initial Replication 7-5
7.4. DFS Management Snap-in 7-6
7.5. Deploying Namespace (Step-by-Step Guide) 7-8
7.5.1. Create a Namespace 7-8
7.5.2. Add a Namespace Server (Domain) 7-9
7.5.3. Delegate Management Permissions 7-9
7.5.4. Add Folders to Namespace 7-10
7.5.5. Change How Target are Ordered in Referrals 7-13
7.5.6. Rename and Move a Folder 7-14
7.5.7. Replicate a Folder in the Namespace Using DFS Replication 7-15
7.5.8. Create a Diagnostic Report 7-17
7.5.9. Browse the Namespace 7-18
7.5.10. Test Failover 7-19
7.6. Deploying DFS Replication (Step-by-Step Guide) 7-20
7.6.1. Create a Multipurpose Replication Group and Two Replicated
Folders 7-20
7.6.2. Add a New Member to Replication Group 7-23
7.6.3. Share and Publish Replicated Folders in a Namespace 7-25
7.6.4. Create a Replication Group for Collection Purposes 7-26
7.6.5. Create a Diagnostic Report 7-28
8. Microsoft Services for Network File System (MSNFS) 8-1
8.1. MSNFS Features 8-1
8.1.1. UNIX Identity Management 8-2
8.2. Microsoft Services for NFS usage scenarios 8-2
8.3. Microsoft Services for NFS components 8-3
8.4. Microsoft Services for NFS administrative tools 8-3
iii
Tandberg Data Table of Content
__________________________________________________________________________________________________
Microsoft Services for NFS snap-in 8-3
8.4.1.
8.4.2. Microsoft Services for NFS command-line tools 8-4
8.5. Test Scenario 8-5
8.6. Steps for Deploying and Testing Microsoft Services for NFS 8-5
8.6.1. Reviewing system requirements for Microsoft Services for NFS 8-5
8.6.2. Setting up the environment for Microsoft Services for NFS 8-6
8.6.2.1. Deploy computers 8-6
8.6.3. Create test user accounts 8-7
8.6.4. Installing Microsoft Services for NFS 8-7
8.6.5. Configuring NFS authentication 8-8
8.6.6. Configuring User Name Mapping 8-8
8.6.6.1. Specify where UNIX user and group information is stored 8-8
8.6.6.2. Edit the .maphosts file 8-10
8.6.6.3. Create a user map 8-11
8.6.6.4. Create a group map 8-12
8.6.6.5. Restart the User Name Mapping service 8-12
8.6.7. Specifying the User Name Mapping server 8-13
8.6.8. Creating an NFS shared folder 8-13
8.6.9. Specifying default permissions for new files and folders 8-15
8.6.10. Configuring Windows Firewall 8-15
8.6.10.1. Open ports 8-15
8.6.10.2. Add mapsvc.exe to the exception list 8-16
8.6.10.3. Enable file and printer sharing for administration tools 8-17
8.6.11. Testing your deployment 8-17
8.6.11.1. Test 1: On the computer running Client for NFS, map a drive
letter to a UNIX-based NFS shared resource. 8-17
8.6.11.2. Test 2: On the computer running Client for NFS, create a test file
and verify its permissions. 8-18
8.6.11.3. Test 3: On a UNIX client computer, mount the Windows NFS
shared resource. 8-18
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. 8-19
8.7. Using Remote Desktop for MSNFS 8-20
8.7.1. Using Remote Desktop 8-20
9. Using iSCSI Software Target 9-1
9.1. Microsoft iSCSI Software Target 9-1
9.1.1. Virtual Disk Storage 9-1
9.1.2. Snapshots 9-2
9.1.3. Wizards 9-2
9.1.4. Create iSCSI Target Wizard 9-2
9.1.5. Create Virtual Disk Wizard 9-4
9.1.6. Import Virtual Disk Wizard 9-5
9.1.7. Extend Virtual Disk Wizard 9-6
9.1.8. Schedule Snapshot Wizard 9-6
9.2. Hardware Providers 9-7
10. Remote Access Methods & Monitoring 10-1
10.1. Remote Desktop 10-1
10.2. Telnet Server 10-2
iv
__________________________________________________________________________________________________
1. 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.
This chapter provides an overview of these environments and deployments
and includes brief descriptions of the available user interfaces.
Series NAS appliance is the disk-based storage for remote office or small to
medium business class NAS solutions that provide reliable performance,
manageability, and fault tolerance.
The Viking Series NAS appliance provides performance gains over general
purpose servers by integrating optimized hardware components and
specialized operating software. Integrating NAS appliance into the network
improves the performance of existing servers because NAS appliances are
optimized for file serving tasks.
Notes
The Viking Series NAS appliance has been specifically designed to function as a
Network Attached Storage server. Except as specifically authorized by Tandberg
Data, you may not use the server software to support additional applications or
significant functionality other than system utilities or server resource management
or similar software that you may install and use solely for system administration,
system performance enhancement, and/or preventative maintenance of the
appliance.
Your Viking Series NAS appliance comes preinstalled with either the Windows®
Storage Server™ 2003 R2 operating system (32-bit version) or the Microsoft®
Windows® Unified Data Storage Server 2003, Enterprise x64 Edition operating
system.
Microsoft Windows Storage Server 2003 R2 extends the Windows Storage
Server 2003 operating system, providing a more efficient way to manage and
control access to local and remote resources. In addition, Windows Storage
Server 2003 R2 provides a scalable, security-enhanced Web platform for
simplified branch server management, improved identity and access
management, and more efficient
storage management.
The Viking
1-1 Tandberg Viking Series Storage Server Administration Manual
Tandberg Data System Overview
__________________________________________________________________________________________________
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® Windows® Unified Data Storage Server 2003, Enterprise x64 Edition
operating system provides unified storage server management capabilities,
simplified setup and management of storage and shared folders, and support for
Microsoft iSCSI Software Target.
Notes
For more information about Microsoft® Windows® Unified Data Storage Server
2003 operating system, see “Using iSCSI Software Target” on chapter 9.
1.1.1. Product Manageability
The Viking Series NAS appliance ships with the following utilities and
features that ease the administration tasks associated with managing the
system:
• The Recovery Disc (factory image) contains the preconfigured default
settings of either the Windows Storage Server 2003 R2 operating system
or the Microsoft® Windows® Unified Data Storage Server 2003 operating
system. This is a quick and easy way to setup or bring the Viking Series
NAS appliances back to the factory default configuration.
• Using the Windows Remote Desktop client to establish
administrative session with the appliance without physically
connecting to it.
• Ability to connect directly to the NAS appliance’s console.
1.2. Redundancy
The Viking Series NAS appliance is specifically designed to perform file
serving tasks for networks, using industry standard components to ensure
reliability. Other industry standard features, such as redundant array of
independent drives (RAID) and remote manageability, further enhance the
overall dependability of the NAS appliance.
To ensure redundancy and reliability, it is recommended that the hard drives
installed in the Viking Series NAS appliance are configured so that a single
drive failure will not cause data loss or system failure.
Depending on the model of Viking Series NAS used, it is capable of support
from 4 HDD to 16 HDD in a single chassis:
• Viking FS-412 supports up to 4 HDD (1U)
• Viking FS-1600 / FS-1610 supports up to 16 HDD (3U)
1-2 Tandberg Viking Series Storage Server Administration Manual
Tandberg Data System Overview
A
__________________________________________________________________________________________________
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). The two logical volumes (SV and
DV) are then allocated from aggregated capacity of the RAID set with the
desired RAID levels. The System Volume, installed with the host operating
system, is organized as RAID 0+1 and the Data Volume is organized as
RAID 5. This is to allow OS redundancy if more than one HDD fails. Please
see the Viking Series NAS Hardware User Manual for details.
The volume layout for the appliance is illustrated below.
ID5
R
HDD 0 HDD 1 HDD 2 HDD 3
RAID0 RAID0
RAID1
SystemVolume
DataVolume
1-3 Tandberg Viking Series Storage Server Administration Manual
Tandberg Data System Overview
__________________________________________________________________________________________________
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). HDD of differing capacity can
also be grouped into similar RAID sets.
• Assigning unused HDD as hot-spares.
• Multiple RAID level support on Volume sets.
Depending on the number of HDD used and their capacity, the RAID Set
grouping and the RAID level of each Volume Set is easily customizable.
Below is a working example:
Using 16 HDD in which 4 is 750GB and 12 is 1,000GB in capacity. The HDD
can be grouped into their respective RAID Set:
RAID Set#00 is created to house the OS as well as a File-system for
sharing. Volume Set#00 is created with RAID level 0+1 which contains a
usable capacity of 200GB. The remaining RAID Set#00 capacity is sliced
into Volume Set#01 of RAID level 5 that yield a resultant capacity of
1,950GB. Volume Set#00 is the System Volume (SV) and Volume Set#01 is
the Data Volume (DV).
• RAID Set#00 = 4 x 750GB
• Volume Set#00 = 200GB (RAID 0+1) SV
• Volume Set#01 = 1,950GB (RAID 5) DV
RAID Set#01 is created with iSCSI target LUN provisioning in mind. Ten (10)
of the 1,000GB HDD are grouped into RAID Set#01 and Volume Set#00 of
RAID level 6 is created out of it. This yields a usable capacity of 8,000GB
after the RAID 6 overhead.
• RAID Set#01 = 10 x 1000GB
• Volume Set#00 = 8,000GB (RAID 6)
The remaining two (2) of the 1,000GB HDD are set as hot-spares.
• Hot-spare = 2 x 1,000GB
The hot-spare can be assigned to any degraded RAID Set for rebuilding in
event that one (or more) of its member disk have failed.
Notes
While assigning hot-spare to a degraded RAID Set, ensure that the capacity of the
hot-spare must be equal or greater than the lowest capacity of the member disk of
that RAID Set.
1-4 Tandberg Viking Series Storage Server Administration Manual
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. The web-based RAID
manager is only available after OS installation or recovery.
1.2.4. Data Volume (DV)
The remaining hard drives space can be organized as the Data Volume
using RAID 5 or other RAID level definable by user. For a FS-412 NAS
appliance installed with four 250 GB hard drives, the data volume size can
be set to 735 GB using the recommended RAID and Volume settings.
1.4. Deployment
Various deployment scenarios are possible. Typical application of NAS
appliances include:
1.4.1. File Server Consolidation
As businesses continue to expand their information technology (IT)
infrastructures, they must find ways to manage larger environments without
a corresponding increase in IT staff. Consolidating many servers into a
single NAS appliance reduces the number of points of administration and
increases the availability and flexibility of storage space.
1.4.2. Multi-protocol Environments
Some businesses require several types of computing systems to accomplish
various tasks. The multi-protocol support of the NAS appliance allows it to
support many types of client computers concurrently.
1.4.3. Protocol and platform transitions
When a transition between platforms is being planned, the ability of the NAS
appliance to support most file sharing protocols allows companies to
continue to invest in file storage space without concerns about
obsolescence. For example, an administrator planning a future transition
from Windows to Linux can deploy the NAS appliance with confidence that it
can support both CIFS and NFS simultaneously, assuring not only a smooth
transition, but also a firm protection of their investment.
1.4.4. Remote office deployment
Frequently, branch offices and other remote locations lack dedicated IT staff
members. An administrator located in a central location can use the
Microsoft Terminal Services, and other remote administration methods to
configure and administer all aspects of the NAS server.
1-5 Tandberg Viking Series Storage Server Administration Manual
Tandberg Data System Overview
__________________________________________________________________________________________________
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.
Regardless of the deployment, the NAS appliance integrates easily into
multi-protocol environments, supporting a wide variety of clients. The
following protocols are supported:
• Distributed File System (DFS)
• Network File System (NFS)
• Hypertext Transfer Protocol (HTTP)
• File Transfer Protocol (FTP)
• Microsoft Server Message Block (SMB)
1.5.1. Workgroup
In a workgroup environment, users and groups are stored and managed
separately, on each member server of the workgroup. Workgroups are
typical for very small deployments where little or no computing environment
planning is required.
1.5.2. Domain
When operating in a Windows NT or Active Directory domain environment,
the NAS appliance is a member of the domain and the domain controller is
the repository of all account information. Client machines are also members
of the domain and users log on to the domain through their Windows based
client machines. The domain controller also administers user accounts and
appropriate access levels to resources that are a part of the domain.
Additional information about planning for domain environments can be found
at Microsoft web site.
The NAS appliance obtains user account information from the domain
controller when deployed in a domain environment. The NAS server itself
cannot act as a domain controller, backup domain controller, or the root of
an Active Directory tree as these functions are disabled in the operating
system.
1-6 Tandberg Viking Series Storage Server Administration Manual
Tandberg Data System Overview
__________________________________________________________________________________________________
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. Each of these interfaces are illustrated in the following
sections.
1.6.1 Direct Attached Method
The Viking Series NAS appliance can be accessed directly be connecting a
keyboard, mouse, and monitor.
The default user name is “Administrator”. The default password is “1234”.
1.6.2. Using Windows Remote Desktop Console
The NAS appliance desktop console can be accessed remotely using
Windows Remote Desktop. This requires the use of the Windows Remote
Desktop client on the machine it is accessing from.
Remote Desktop provides the ability for you to log onto and remotely
administer your server, giving you a method of managing it from any client.
Installed for remote administration, Remote Desktop allows only two
concurrent sessions. Leaving a session running takes up one license and
can affect other users. If two sessions are running, additional users will be
denied access.
To connect the storage server to a network using the Remote Desktop
method:
• On the PC client, select Start > Run. At Open, type mstsc, then
click OK.
• Type the IP address of the NAS appliance you will be connecting to
in the Computer box and click Connect.
• Use the default user name “Administrator” and default password
“1234” to gain system access.
Notes
When using Remote Desktop to connect to the NAS appliance desktop do not use
the window close feature (X). Click on Start/Log Off Administrator to exit Remote
Desktop. See “Improper Closure of Remote Desktop” in Chapter 2.
1-7 Tandberg Viking Series Storage Server Administration Manual
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. Later, you
can log back on the server, re-enter the session and either resume the task
or check results. This is especially helpful when operating over a remote
connection on a long-distance toll line.
Ending the session is known as logging off. Logging off ends the session
running on the server. Any applications running within the session are
closed, and unsaved changes made to open files will be lost. The next time
you log onto the server, a new session is created.
Remote Desktop requires that all connecting users be authenticated, which
is why users must log on each time they start a session.
1-8 Tandberg Viking Series Storage Server Administration Manual
__________________________________________________________________________________________________
2. 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.
Notes
The NAS appliance desktop can be accessed via a directly connected keyboard,
mouse, and monitor.
Unlike the Windows Storage Server 2003, Windows Storage Server 2003 R2
uses as new Windows Storage Server Management Console that configures
and manages shares, storage, quotas, various file sharing protocol as well
as print service. The Storage Server Management Console can only be
accessed using direct attached method or Windows Remote Desktop.
2-1 Tandberg Viking Series Storage Server Administration Manual
Tandberg Data Setting Up & Administration
__________________________________________________________________________________________________
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:
• Select Start > Run. At Open, type mstsc, then click OK.
• Type the IP address of the NAS appliance you will be connecting to
in the Computer box and click Connect.
• Use the default user name “Administrator” and default password
“1234” to gain system access.
Notes
Two open sessions of Remote Desktop are allowed to operate at the same time.
After completing an application do not use the window close feature (X) to close that
session of Remote Desktop. Click Start then Log Off Administrator to exit Remote
Desktop.
2.1.1. Improper Closure of Remote Desktop
Certain operations can leave the utilities running if the browser is closed
versus exiting from the program via the application menu or logging off the
Remote Desktop session. A maximum of two Remote Desktop sessions may
be used at any given time. Improper exit from a session can result in the
sessions becoming consumed. Sessions and processes can be terminated
using the Terminal Services Manager via Start > Programs >
Administrator Tools.
Note
The Terminal Services Manager must be accessed via the direct attached method.
2.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
storage server, but must be activated before use.
Notes
For security reasons, the Telnet Server is disabled by default. The service needs to
be modified to enable access to the storage server with Telnet.
2-2 Tandberg Viking Series Storage Server Administration Manual
Tandberg Data Setting Up & Administration
__________________________________________________________________________________________________
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:
1. Select Start > Run, and then enter services.msc.
2. Locate and right-click the Telnet service and then select
Properties.
3. Choose one of the following:
o For the Telnet service to start up automatically on every
reboot, in the Startup Type drop-down box, click Automatic,
and then click OK.
o For the Telnet service to be started manually on every
reboot, in the Startup Type drop-down box, click Manual,
and then click OK.
On the storage server, access the command line interface, either by Remote
Desktop or a direct connection, and then enter the following command:
net start tlntsvr
The sessions screen provides the ability to view or terminate active
sessions.
2.3. Setup Completion
After the NAS appliance is physically set up and the basic configuration is
established, additional setup steps must be completed. Depending on the
deployment scenario of the NAS appliance, these steps may vary.
Additional setup steps may include:
• Managing system storage
• Creating and managing users and groups
• Creating and managing file shares
• Running Microsoft Windows Update
• Using Ethernet NIC teaming
• Installing third-party software applications
Each of these setup steps is discussed in the following sections.
2-3 Tandberg Viking Series Storage Server Administration Manual
Tandberg Data Setting Up & Administration
__________________________________________________________________________________________________
2.4. Managing System Storage
The NAS administrator uses Disk Management to manage volumes, and
Shadow Copies to manage snapshots. See the following chapters for more
detailed information on managing system storage:
• Chapter 3 discusses storage and file server management
procedures
• Chapter 4 discusses snapshot (shadow copy) management
procedures
• Chapter 6 discusses folder and share management procedures
2.5. Creating and Managing Users and Groups
User and group information and permissions determine whether a user can
access files. If the NAS appliance is deployed into a workgroup environment,
this user and group information is stored locally on the device. By contrast, if
the NAS device is deployed into a domain environment, user and group
information is stored on the domain usually the Primary Domain Controller.
To enter local user and group information, see Chapter 5.
2.2.1. Joining Workgroup & Domain
These are the two system environments for users and groups. 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 storage server. For information on managing users and groups on a
domain, see the domain documentation available on the Microsoft web site.
2.6. Creating and Managing File Shares
Files shares must be set up, granting and controlling file access to users and
groups. See Chapter 6 for complete information on managing file shares.
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
on the storage server. For recommendations, instructions, and
documentation to help manage the software update, hotfix, and security
patches process on the storage server, see documentation of Microsoft
Software Updates available on Microsoft web site.
2-4 Tandberg Viking Series Storage Server Administration Manual
Tandberg Data Setting Up & Administration
__________________________________________________________________________________________________
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.
2.9. Installing 3rd Party Software Applications
For example, these might include an antivirus or backup application that you
install.
2-5 Tandberg Viking Series Storage Server Administration Manual
Tandberg Data Setting Up & Administration
__________________________________________________________________________________________________
This Page Intentionally Left Blank
2-6 Tandberg Viking Series Storage Server Administration Manual
__________________________________________________________________________________________________
3. 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 Management Element
Storage is divided into four major divisions:
• Physical storage elements
• Logical storage elements
• File system elements
• File sharing elements
Each of these elements is composed of the previous level's elements.
3.1.1. Physical Storage Element
The lowest level of storage management occurs at the physical drive level.
Minimally, choosing the best disk carving strategy includes the following
policies:
• Analyze current corporate and departmental structure.
• Analyze the current file server structure and environment.
• Plan properly to ensure the best configuration and use of storage.
o Determine the desired priority of fault tolerance,
performance, and storage capacity.
o Use the determined priority of system characteristics to
determine the optimal striping policy and RAID level.
• Include the appropriate number of physical drives in the arrays to
create logical storage elements of desired sizes.
3-1 Tandberg Viking Series Storage Server Administration Manual
Tandberg Data Storage & File Server Management
__________________________________________________________________________________________________
3.1.1.1. Disk Array
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.
Notes
Depending on the storage server model, array configuration may not be possible or
necessary.
Because the read/write heads are simultaneously active, the same amount
of data is written to each drive during any given time interval. Each unit of
data is termed a block. The blocks form a set of data stripes over all the hard
drives in an array.
For data in the array to be readable, the data block sequence within each
stripe must be the same. This sequencing process is performed by the array
controller, which sends the data blocks to the drive write heads in the correct
order.
A natural consequence of the striping process is that each hard drive in a
given array contains the same number of data blocks.
Notes
If one hard drive has a larger capacity than other hard drives in the same array, the
extra capacity is wasted because it cannot be used by the array.
3.1.1.2. Fault Tolerance
Drive failure, although rare, is potentially catastrophic. For example, using
simple striping with several HDD, failure of any hard drive leads to failure of
all logical drives in the same array, and hence to data loss.
To protect against data loss from hard drive failure, storage servers should
be configured with fault tolerance.
3.1.1.3. Online Spares (Hot-Spares)
Further protection against data loss can be achieved by assigning an online
spare (or hot-spare) to any configuration except RAID 0. This hard drive
contains no data and is contained within the same storage subsystem as the
other drives in the array. When a hard drive in the array fails, the controller
can then automatically rebuild information that was originally on the failed
drive onto the online spare. This quickly restores the system to full RAID
level fault tolerance protection. However, unless RAID 6 is being used, which
can support two drive failures in an array, in the unlikely event that a third
drive in the array should fail while data is being rewritten to the spare, the
logical drive still fails.
3-2 Tandberg Viking Series Storage Server Administration Manual
Tandberg Data Storage & File Server Management
__________________________________________________________________________________________________
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. Each of these types of disk has special features that
enable different types of management.
3.1.2.1. Logical Drives (LUNs)
While an array is a physical grouping of hard drives, a logical drive consists
of components that translate physical storage elements into file system
elements. It is important to note that a LUN may extend over (span) all
physical drives within a storage controller subsystem, but cannot span
multiple storage controller subsystems.
Through the use of basic disks, primary partitions or extended partitions can
be created. Partitions can only encompass one LUN. Through the use of
dynamic disks, volumes can be created that span multiple LUNs. The
Windows Disk Management utility can be used to convert disks to dynamic
and back to basic, and manage the volumes residing on dynamic disks.
Other options include the ability to delete, extend, mirror, and repair these
elements.
3.1.2.2. Partitions
Partitions exist as either primary partitions or extended partitions and can be
composed of only one basic disk no larger than 2 TB. Basic disks can also
only contain up to four primary partitions, or three primary partitions and one
extended partition. In addition, the partitions on them cannot be extended
beyond the limits of a single LUN. Extended partitions allow the user to
create multiple logical drives. These partitions or logical disks can be
assigned drive letters or be used as mount points on existing disks. If mount
points are used, it should be noted that Services for UNIX (SFU) does not
support mount points at this time. The use of mount points in conjunction
with NFS shares is not supported.
3.1.2.3. Volumes
When planning dynamic disks and volumes, there is a limit to the amount of
growth a single volume can undergo. Volumes are limited in size and can
have no more than 32 separate LUNs, with each LUN not exceeding 2
terabytes (TB), and volumes totaling no more than 64 TB of disk space.
The RAID level of the LUNs included in a volume must be considered. All of
the units that make up a volume should have the same high-availability
characteristics. In other words, the units should all be of the same RAID
level. For example, it would not be a good practice to include both a RAID
0+1 and a RAID 5 array in the same volume set. By keeping all the units the
same, the entire volume retains the same performance and high-availability
characteristics, making managing and maintaining the volume much easier.
If a dynamic disk goes offline, the entire volume dependent on the one or
more dynamic disks is unavailable. There could be a potential for data loss
depending on the nature of the failed LUN.
3-3 Tandberg Viking Series Storage Server Administration Manual
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. Simple
volumes can be mirrored or converted to spanned volumes. Fault-tolerant
disks cannot be extended either. Therefore, selection of the volume type is
important. The same performance characteristics on numbers of reads and
writes apply when using fault-tolerant configurations, as is the case with
controller-based RAID. These volumes can also be assigned drive letters or
be mounted as mount points off existing drive letters.
The administrator should carefully consider how the volumes will be carved
up and what groups or applications will be using them. For example, putting
several storage-intensive applications or groups into the same dynamic disk
set would not be efficient. These applications or groups would be better
served by being divided up into separate dynamic disks, which could then
grow as their space requirements increased, within the allowable growth
limits.
3.1.3. File System Element
File system elements are composed of the folders and subfolders that are
created under each logical storage element (partitions, logical disks, and
volumes). Folders are used to further subdivide the available file system,
providing another level of granularity for management of the information
space. Each of these folders can contain separate permissions and share
names that can be used for network access. Folders can be created for
individual users, groups, projects, and so on.
3.1.4. File Sharing Element
The storage server supports several file sharing protocols, including
Distributed File System (DFS), Network File System (NFS), File Transfer
Protocol (FTP), Hypertext Transfer Protocol (HTTP), and Microsoft Server
Message Block (SMB). On each folder or logical storage element, different
file sharing protocols can be enabled using specific network names for
access across a network to a variety of clients. Permissions can then be
granted to those shares based on users or groups of users in each of the file
sharing protocols.
3.2. Volume Shadow Copy Service Overview
The Volume Shadow Copy Service (VSS) provides an infrastructure for
creating point-in-time snapshots (shadow copies) of volumes. VSS supports
64 shadow copies per volume.
Shadow Copies of Shared Folders resides within this infrastructure, and
helps alleviate data loss by creating shadow copies of files or folders that are
stored on network file shares at pre-determined time intervals. In essence, a
shadow copy is a previous version of the file or folder at a specific point in
time.
By using shadow copies, a storage server can maintain a set of previous
versions of all files on the selected volumes. End users access the file or
folder by using a separate client add-on program, which enables them to
view the file in Windows Explorer.
3-4 Tandberg Viking Series Storage Server Administration Manual
Tandberg Data Storage & File Server Management
__________________________________________________________________________________________________
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.
3.3. Using Storage Element
The last step in creating the element is determining its drive letter or mount
point and formatting the element. Each element created can exist as a drive
letter, assuming one is available and/or as mount points off of an existing
folder or drive letter. Either method is supported. However, mount points
cannot be used for shares that will be shared using Microsoft Services for
Unix. They can be set up with both but the use of the mount point in
conjunction with NFS shares causes instability with the NFS shares.
Formats consist of NTFS, FAT32, and FAT. All three types can be used on
the storage server. However, VSS can only use volumes that are NTFS
formatted. Also, quota management is possible only on NTFS.
3.4. Network Adapter Teaming
Network adapter teaming is software-based technology used to increase a
server's network availability and performance. Teaming enables the logical
grouping of physical adapters in the same server (regardless of whether they
are embedded devices or Peripheral Component Interconnect (PCI)
adapters) into a virtual adapter. This virtual adapter is seen by the network
and server-resident network-aware applications as a single network
connection.
3.5. Disk Management
Disk Management can be accessed after administrator login using Remote
Desktop. Disk Management is accessed by right-clicking on the My
Computer icon on the Desktop and then selects Manage option or using the
Windows Storage Server Management Console.
3-5 Tandberg Viking Series Storage Server Administration Manual
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. Most disk-related
tasks can be preformed in Disk Management without restarting the system or
interrupting users; most configuration changes take effect immediately. A
complete online help facility is provided with the Disk Management Utility for
assistance in using the product
Note
When the Disk Management utility is accessed, the Remote Desktop connection
assumes a dedicated mode and can only be used to manage disks and volumes on
the server. Navigating to another page during an open session closes the session.
Note
It may take a few moments for the Remote Desktop Connection session to log off
when closing Disk Management.
3-6 Tandberg Viking Series Storage Server Administration Manual
Tandberg Data Storage & File Server Management
__________________________________________________________________________________________________
3.6. Guidelines for Managing Disks & Volumes
When managing disks and volumes:
• Read the online Disk Management Help found in the utility.
• Do not alter the Operating System Disk labeled C:. This logical drive
is configured for the storage server operating system and should not
be altered in any manner, unless return to factory image is desired.
• 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.
• Use meaningful volume labels with the intended drive letter
embedded in the volume label, if possible. For example, volume F:
might be named “Disk F:.” Volume labels often serve as the only
means of identification.
• Record all volume labels and drive letters in cases when OS
recovery is necessary.
• When managing basic disks, only the last partition on the disk can
be extended unless the disk is changed to dynamic.
• Basic disks can be converted to dynamic without bringing the
system offline or loss of data, but the volume will be unavailable
during the conversion. However, it cannot be converted back to
basic without deleting all data on the disk.
• Basic disks can contain up to four primary partitions (or three
primary partitions and one extended partition).
• Format drives with a 16 K allocation size for best support of
snapshots, performance, and defragmentation.
• NTFS formatted drives are recommended since they provide the
greatest level of support for snapshots, encryption, and
compression.
• Only basic disks can be formatted as FAT or FAT32.
3-7 Tandberg Viking Series Storage Server Administration Manual
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”. The default password is “0000”.
The web-based RAID manager is use to administer further configurations i.e.
changing the RAID level on the System Volume or the Data Volume, and
monitor controllers as well as the RAID re-building progress.
The default password can be changed using the Modify Password field
located on the left column strip of the web-based RAID manager.
3-8 Tandberg Viking Series Storage Server Administration Manual
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.
Closing the archttppci application during a web session with the array
controller will result in lost of unsaved information.
3-9 Tandberg Viking Series Storage Server Administration Manual
Tandberg Data Storage & File Server Management
__________________________________________________________________________________________________
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. This reduces the likelihood that new files will be
fragmented.
Defragmentation for a volume can be scheduled to occur automatically at
convenient times. Defragmentation can also be done once, or on a recurring
basis.
Notes
Scheduling defragmentation to run no later than a specific time prevents the
defragmentation process from running later than that time. If the defragmentation
process is running when the time is reached, the process is stopped. This setting is
useful to ensure that the defragmentation process ends before the demand for
server access is likely to increase.
If defragmenting volumes on which shadow copies are enabled, use a
cluster (or allocation unit) size of 16 KB or larger during the format.
Otherwise defragmentation registers as a change by the Shadow Copy
process. This increase in the number of changes forces Shadow Copy to
delete snapshots as the limit for the cache file is reached.
Warning
Allocation unit size cannot be altered without reformatting the drive. Data on
a reformatted drive cannot be recovered.
Note
NTFS compression is supported only if the cluster size is 4 KB or smaller.
3.9. Disk Quotas
Disk quotas track and control disk space use in volumes.
Note
To limit the size of a folder or share, see “Directory Quotas” in Chapter 6.
Configure the volumes on the server to perform the following tasks:
• Prevent further disk space use and log an event when a user
exceeds a specified disk space limit.
• Log an event when a user exceeds a specified disk space warning
level.
3-10 Tandberg Viking Series Storage Server Administration Manual
Loading...