Tandberg Data NAS Hardware Viking FS-1500 Instruction Manual

TANDBERG
VIKING SERIES
NAS APPLIANCE
Storage Server Administration Manual
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
TANDBERG DATA ASIA

Related publications available from Tandberg Data Asia:
Part No. Title
6582B7 Tandberg Viking FS-1600 NAS Hardware User
Manual
6582A7 Tandberg Viking FS-1500 NAS Hardware User
Manual
658297 Tandberg Viking FS-412 NAS Hardware User
Manual
This publication may describe designs for which patents are granted or pen-
ding. By publishing this information, Tandberg Data Asia conveys no license
under any patent or any other rights.
Every effort has been made to avoid errors in text and diagrams. However,
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.
We would appreciate any comments on this publication.

__________________________________________________________________________________________________
i
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

Tandberg Data Table of Content
__________________________________________________________________________________________________
ii
3.5. Disk Management 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

Tandberg Data Table of Content
__________________________________________________________________________________________________
iii
6.1. Folder Management 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

Tandberg Data Table of Content
__________________________________________________________________________________________________
iv
8.4.1. Microsoft Services for NFS snap-in 8-3
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

__________________________________________________________________________________________________
1-1 Tandberg Viking Series Storage Server Administration Manual
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. The Viking
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.

Tandberg Data System Overview
__________________________________________________________________________________________________
1-2 Tandberg Viking Series Storage Server Administration Manual
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)

Tandberg Data System Overview
__________________________________________________________________________________________________
1-3 Tandberg Viking Series Storage Server Administration Manual
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.
RAID1
RAID0 RAID0
R
A
ID5
HDD 0 HDD 1 HDD 2 HDD 3
SystemVolume
DataVolume

Tandberg Data System Overview
__________________________________________________________________________________________________
1-4 Tandberg Viking Series Storage Server Administration Manual
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.

Tandberg Data System Overview
__________________________________________________________________________________________________
1-5 Tandberg Viking Series Storage Server Administration Manual
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.

Tandberg Data System Overview
__________________________________________________________________________________________________
1-6 Tandberg Viking Series Storage Server Administration Manual
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.

Tandberg Data System Overview
__________________________________________________________________________________________________
1-7 Tandberg Viking Series Storage Server Administration Manual
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.

Tandberg Data System Overview
__________________________________________________________________________________________________
1-8 Tandberg Viking Series Storage Server Administration Manual
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.

__________________________________________________________________________________________________
2-1 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.

Tandberg Data Setting Up & Administration
__________________________________________________________________________________________________
2-2 Tandberg Viking Series Storage Server Administration Manual
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.

Tandberg Data Setting Up & Administration
__________________________________________________________________________________________________
2-3 Tandberg Viking Series Storage Server Administration Manual
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:
oFor the Telnet service to start up automatically on every
reboot, in the Startup Type drop-down box, click Automatic,
and then click OK.
oFor 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.

Tandberg Data Setting Up & Administration
__________________________________________________________________________________________________
2-4 Tandberg Viking Series Storage Server Administration Manual
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.

Tandberg Data Setting Up & Administration
__________________________________________________________________________________________________
2-5 Tandberg Viking Series Storage Server Administration Manual
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.

Tandberg Data Setting Up & Administration
__________________________________________________________________________________________________
2-6 Tandberg Viking Series Storage Server Administration Manual
This Page Intentionally Left Blank