sata nas subsystem
SATA NAS SUBSYSTEM
Hardware Installation Reference Guide
Revision 1.2
P/N: PW0020000000292
Copyright
No part of this publication may be reproduced, stored in a retrieval system, or
transmitted in any form or by any means, electronic, mechanical, photocopying,
recording or otherwise, without the prior written consent.
Trademarks
All products and trade names used in this document are trademarks or registered
trademarks of their respective holders.
Changes
The material in this documents is for information only and is subject to change
without notice.
FCC Compliance Statement
This equipment has been tested and found to comply with the limits for a Class
B digital device, pursuant to Part 15 of the FCC rules. These limits are designed to provide reasonable protection against harmful interference in residential installations. This equipment generates, uses, and can radiate radio
frequency energy, and if not installed and used in accordance with the
instructions, may cause harmful interference to radio communications.
However, there is not guarantee that interference will not occur in a particular
installation. If this equipment does cause interference to radio or television
equipment reception, which can be determined by turning the equipment off
and on, the user is encouraged to try to correct the interference by one or
more of the following measures:
1.
2.
3.
4.
Reorient or relocate the receiving antenna
Move the equipment away from the receiver
Plug the equipment into an outlet on a circuit different from that to
which the receiver is powered.
Consult the dealer or an experienced radio/television technician for
help
All external connections should be made using shielded cables.
Table of Contents
Chapter 1
1.1
1.2
1.3
Chapter 2
2.1
2.2
2.3
2.4
2.5
2.6
2.7
Chapter 3
3.1
3.2
3.3
3.4
3.5
3.6
3.7
Introduction
Key Features.............................................................................................................
RAID Concepts..........................................................................................................
Array Definition....................................................................................................
1.3.1 RAID set...................................................................................................
1.3.2 Volume Set...............................................................................................
1.3.3 Easy of Use features...................................................................................
1.3.4 High Availability..........................................................................................
1-2
1-3
1-10
1-10
1-10
1-11
1-13
Installation Overview
Unpacking the subsystem.......................................................................................... 2-1
Identifying parts of the subsystem.............................................................................. 2-3
2.2.1 Front View ................................................................................................. 2-3
2.2.2 Rear view ........................................................................................................ 2-6
Connecting NAS subsystem to Your Network.............................................................. 2-8
Powering-on............................................................................................................. 2-8
Installing Hard Drives................................................................................................. 2-9
Install OS............................................................................................................ 2-11
Array Maintenance............................................................................................... 2-12
RAID Configuring
Configuring through a Terminal..............................................................................
Configuring the Subsystem Using the LCD Panel...................................................
Menu Diagram.....................................................................................................
Web browser-based Remote RAID management via R-Link ethernet.........................
Quick Create.......................................................................................................
Raid Set Functions...............................................................................................
3.6.1 Create Raid Set..........................................................................................
3.6.2 Delete Raid Set............................................................................................
3.6.3 Expand Raid Set...........................................................................................
3.6.4 Activate Incomplete Raid Set.......................................................................
3.6.5 Create Hot Spare........................................................................................
3.6.6 Delete Hot Spare.........................................................................................
3.6.7 Rescue Raid Set..........................................................................................
Volume Set Function..............................................................................................
3.7.1 Create Volume Set......................................................................................
3.7.2 Delete Volume Set......................................................................................
3.7.3 Modify Volume Set........................................................................................
3.7.3.1 Volume Expansion...........................................................................
3.7.4 Volume Set Migration..................................................................................
3.7.5 Check Volume Set........................................................................................
3.7.6 Stop Volume Set Check..............................................................................
3-1
3-9
3-10
3-15
3-17
3-18
3-18
3-19
3-20
3-22
3-24
3-24
3-25
3-26
3-26
3-29
3-30
3-30
3-32
3-33
3-33
3.8
3.9
3.10
3.11
3.12
Physical Drive.........................................................................................................
3.8.1 Create Pass-Through Disk...........................................................................
3.8.2 Modify Pass-Through Disk...........................................................................
3.8.3 Delete Pass-Through Disk............................................................................
3.8.4 Identify Selected Drive.................................................................................
System Configuration...........................................................................................
3.9.1 System Configuration.................................................................................
3.9.2 Ethernet Config.............................................................................................
3.9.3 Alert By Mail Config......................................................................................
3.9.4 SNMP Configuration.....................................................................................
3.9.5 NTP Configuration.......................................................................................
3.9.6 View Events..................................................................................................
3.9.7 Generate Test Events..................................................................................
3.9.8 Clear Events Buffer......................................................................................
3.9.9 Modify Password..........................................................................................
3.9.10 Upgrade Firmware......................................................................................
Information Menu....................................................................................................
3.10.1 RaidSet Hierarchy......................................................................................
3.10.2 System Information....................................................................................
3.10.3 Hardware Monitor.......................................................................................
Creating a new RAID or Reconfiguring an Existing RAID...........................................
Upgrading the Firmware........................................................................................
3-34
3-34
3-35
3-36
3-36
3-37
3-37
3-40
3-41
3-42
3-43
3-44
3-45
3-46
3-46
3-47
3-48
3-48
3-50
3-51
3-52
3-53
Chapter 1
Introduction
Storage networks become more and more complex. If you need to easily expand storage capacity while providing uninterrupted high-performance data access across your LAN. You may want to consider a NAS (Network Attached
Storage) appliance. When budgets are tight and a quick fix is required, a NAS
appliance is a low-cost, efficient solution to dodge that network-to-storage
logjam. That's why more and more users select NAS architecture as their storage networking.
The DN-503A-PDC (SATA NAS subsystem) is a reliable, cost-effective way to
add storage to the network. It comes with 5 drive trays accommodating 3.5"
SATA II drives. The DN-503A-PDC system is managed and configured by Java
browser based software, including pre-configure disk capacity, users setting,
volume management, quick installed on popular network platform, Multi protocol support, etc... Equipped with H/W RAID to offer fault tolerant data
protection. It is a full featured data protection supporting RAID levels 0,1,3,0+1,
5,6 and JBOD.
System reliability is ensured by an environmental monitoring unit, which tracks
the enclosure temperature as well as individual disk temperatures. If any irregularity in these systems occurs, the monitoring unit alerts the administrator.
Introduction
1-1
1.1 Key Features
Desktop SATA NAS Subsystem
Supports up to five (5) 1" hot-swappable SATA II (3Gb/s) hard drives
Supports RAID levels 0, 1, 0+1, 3, 5, 6, and JBOD
Supports hot spare and automatic hot rebuild
LCD panel for IP setting
Allows online capacity expansion within the enclosure
Four Gigabit Ethernet ports
1-2
Introduction
1.2 RAID Concepts
RAID Fundamentals
The basic idea of RAID (Redundant Array of Independent Disks) is to combine
multiple inexpensive disk drives into an array of disk drives to obtain performance,
capacity and reliability that exceeds that of a single large drive. The array of
drives appears to the host computer as a single logical drive.
Five types of array architectures, RAID 1 through RAID 6, were originally defined,
each provides disk fault-tolerance with different compromises in features and
performance. In addition to these five redundant array architectures, it has become
popular to refer to a non-redundant array of disk drives as a RAID 0 array.
Disk Striping
Fundamental to RAID technology is striping. This is a method of combining
multiple drives into one logical storage unit. Striping partitions the storage
space of each drive into stripes, which can be as small as one sector (512
bytes) or as large as several megabytes. These stripes are then interleaved in
a rotating sequence, so that the combined space is composed alternately of
stripes from each drive. The specific type of operating environment determines
whether large or small stripes should be used.
Most operating systems today support concurrent disk I/O operations across
multiple drives. However, in order to maximize throughput for the disk subsystem,
the I/O load must be balanced across all the drives so that each drive can be kept
busy as much as possible. In a multiple drive system without striping, the disk I/O
load is never perfectly balanced. Some drives will contain data files that are
frequently accessed and some drives will rarely be accessed.
Introduction
1-3
By striping the drives in the array with stripes large enough so that each record
falls entirely within one stripe, most records can be evenly distributed across all
drives. This keeps all drives in the array busy during heavy load situations. This
situation allows all drives to work concurrently on different I/O operations, and
thus maximize the number of simultaneous I/O operations that can be performed
by the array.
Definition of RAID Levels
RAID 0 is typically defined as a group of striped disk drives without parity or data
redundancy. RAID 0 arrays can be configured with large stripes for multi-user
environments or small stripes for single-user systems that access long sequential
records. RAID 0 arrays deliver the best data storage efficiency and performance
of any array type. The disadvantage is that if one drive in a RAID 0 array fails, the
entire array fails.
1-4
Introduction
RAID 1, also known as disk mirroring, is simply a pair of disk drives that store
duplicate data but appear to the computer as a single drive. Although striping is
not used within a single mirrored drive pair, multiple RAID 1 arrays can be striped
together to create a single large array consisting of pairs of mirrored drives. All
writes must go to both drives of a mirrored pair so that the information on the
drives is kept identical. However, each individual drive can perform simultaneous,
independent read operations. Mirroring thus doubles the read performance of a
single non-mirrored drive and while the write performance is unchanged. RAID 1
delivers the best performance of any redundant array type. In addition, there is
less performance degradation during drive failure than in RAID 5 arrays.
Introduction
1-5
RAID 3 sector-stripes data across groups of drives, but one drive in the group is
dedicated to storing parity information. RAID 3 relies on the embedded ECC in
each sector for error detection. In the case of drive failure, data recovery is
accomplished by calculating the exclusive OR (XOR) of the information recorded
on the remaining drives. Records typically span all drives, which optimizes the
disk transfer rate. Because each I/O request accesses every drive in the array,
RAID 3 arrays can satisfy only one I/O request at a time. RAID 3 delivers the best
performance for single-user, single-tasking environments with long records.
Synchronized-spindle drives are required for RAID 3 arrays in order to avoid
performance degradation with short records. RAID 5 arrays with small stripes can
yield similar performance to RAID 3 arrays.
Under RAID 5 parity information is distributed across all the drives. Since there
is no dedicated parity drive, all drives contain data and read operations can be
overlapped on every drive in the array. Write operations will typically access one
data drive and one parity drive. However, because different records store their
parity on different drives, write operations can usually be overlapped.
1-6
Introduction
RAID 6 is similar to RAID 5 in that data protection is achieved by writing parity
information to the physical drives in the array. With RAID 6, however, two sets of
parity data are used. These two sets are different, and each set occupies a capacity
equivalent to that of one of the constituent drives. The main advantages of RAID 6
is High data availability – any two drives can fail without loss of critical data.
Introduction
1-7
Dual-level RAID achieves a balance between the increased data availability
inherent in RAID 1 and RAID 5 and the increased read performance inherent in
disk striping (RAID 0). These arrays are sometimes referred to as RAID 0+1 or
RAID 10 and RAID 0+5 or RAID 50.
In summary:
RAID 0 is the fastest and most efficient array type but offers no faulttolerance. RAID 0 requires a minimum of two drives.
RAID 1 is the best choice for performance-critical, fault-tolerant
environments. RAID 1 is the only choice for fault-tolerance if no more than
two drives are used.
RAID 3 can be used to speed up data transfer and provide fault-tolerance
in single-user environments that access long sequential records. However,
RAID 3 does not allow overlapping of multiple I/O operations and requires
synchronized-spindle drives to avoid performance degradation with short
records. RAID 5 with a small stripe size offers similar performance.
RAID 5 combines efficient, fault-tolerant data storage with good performance
characteristics. However, write performance and performance during drive
failure is slower than with RAID 1. Rebuild operations also require more
time than with RAID 1 because parity information is also reconstructed. At
least three drives are required for RAID 5 arrays.
RAID 6 is essentially an extension of RAID level 5 which allows for
additional fault tolerance by using a second independent distributed parity scheme (two-dimensional parity). Data is striped on a block level
across a set of drives, just like in RAID 5, and a second set of parity is
calculated and written across all the drives; RAID 6 provides for an extremely high data fault tolerance and can sustain multiple simultaneous
drive failures. Perfect solution for mission critical applications.
1-8
Introduction
RAID Management
The subsystem can implement several different levels of RAID technology.
RAID levels supported by the subsystem are shown below.
RAID
Level
Description
Min
Drives
0
Block striping is provide, which yields higher performance than with
individual drives. There is no redundancy.
1
1
Drives are paired and mirrored. All data is 100% duplicated on an
equivalent drive. Fully redundant.
2
3
Data is striped across several physical drives. Parity protection is used
for data redundancy.
3
5
Data is striped across several physical drives. Parity protection is used
for data redundancy.
3
6
Data is striped across several physical drives. Parity protection is used
for data redundancy. Requires N+2 drives to implement because of
two-dimensional parity scheme
4
Combination of RAID levels 0 and 1. This level provides striping and
redundancy through mirroring.
4
0+1
Introduction
1-9
1.3 Array Definition
1.3.1 RAID Set
A RAID Set is a group of disks containing one or more volume sets. It is
impossible to have multiple RAID Sets on the same disks.
A Volume Set must be created either on an existing RAID set or on a group of
available individual disks (disks that are not yet a part of an raid set). If there
are pre-existing raid sets with available capacity and enough disks for specified RAID level desired, then the volume set will be created in the existing raid
set of the user’s choice. If physical disks of different capacity are grouped
together in a raid set, then the capacity of the smallest disk will become the
effective capacity of all the disks in the raid set.
1.3.2 Volume Set
A Volume Set is seen by the host system as a single logical device. It is organized in a RAID level with one or more physical disks. RAID level refers to the
level of data performance and protection of a Volume Set. A Volume Set capacity can consume all or a portion of the disk capacity available in a RAID
Set. Multiple Volume Sets can exist on a group of disks in a RAID Set. Additional Volume Sets created in a specified RAID Set will reside on all the physical disks in the RAID Set. Thus each Volume Set on the RAID Set will have its
data spread evenly across all the disks in the RAID Set. Volume Sets of different RAID levels may coexist on the same RAID Set.
In the illustration below, Volume 1 can be assigned a RAID 5 level of operation
while Volume 0 might be assigned a RAID 0+1 level of operation.
1-10
Introduction
1.3.3 Easy of Use features
1.3.3.1 Instant Availability/Background Initialization
RAID 0 and RAID 1 volume set can be used immediately after the creation. But
the RAID 3, 5 and 6 volume sets must be initialized to generate the parity. In
the Normal Initialization, the initialization proceeds as a background task, the
volume set is fully accessible for system reads and writes. The operating system can instantly access to the newly created arrays without requiring a reboot
and waiting the initialization complete. Furthermore, the RAID volume set is
also protected against a single disk failure while initialing. In Fast Initialization,
the initialization proceeds must be completed before the volume set ready for
system accesses.
1.3.3.2 Array Roaming
The RAID subsystem stores configuration information both in NVRAM and on
the disk drives It can protect the configuration settings in the case of a disk
drive or controller failure. Array roaming allows the administrators the ability to
move a completely raid set to another system without losing RAID configuration and data on that raid set. If a server fails to work, the raid set disk drives
can be moved to another server and inserted in any order.
Introduction
1-11
1.3.3.3 Online Capacity Expansion
Online Capacity Expansion makes it possible to add one or more physical
drive to a volume set, while the server is in operation, eliminating the need to
store and restore after reconfiguring the raid set. When disks are added to a
raid set, unused capacity is added to the end of the raid set. Data on the
existing volume sets residing on that raid set is redistributed evenly across all
the disks. A contiguous block of unused capacity is made available on the raid
set. The unused capacity can create additional volume set. The expansion
process is illustrated as following figure.
The RAID subsystem controller redistributes the original volume set over the
original and newly added disks, using the same fault-tolerance configuration.
The unused capacity on the expand raid set can then be used to create an
additional volume sets, with a different fault tolerance setting if user need to
change.
1-12
Introduction
1.3.3.4 Online RAID Level and Stripe Size Migration
User can migrate both the RAID level and stripe size of an existing volume set,
while the server is online and the volume set is in use. Online RAID level/stripe
size migration can prove helpful during performance tuning activities as well as
in the event that additional physical disks are added to the RAID subsystem.
For example, in a system using two drives in RAID level 1, you could add
capacity and retain fault tolerance by adding one drive. With the addition of
third disk, you have the option of adding this disk to your existing RAID logical
drive and migrating from RAID level 1 to 5. The result would be parity fault
tolerance and double the available capacity without taking the system off.
1.3.4 High availability
1.3.4.1 Creating Hot Spares
A hot spare drive is an unused online available drive, which is ready for replacing the failure disk drive. In a RAID level 1, 0+1, 3, 5 or 6 raid set, any
unused online available drive installed but not belonging to a raid set can
define as a hot spare drive. Hot spares permit you to replace failed drives
without powering down the system. When RAID subsystem detects a UDMA
drive failure, the system will automatic and transparent rebuilds using hot
spare drives. The raid set will be reconfigured and rebuilt in the background,
while the RAID subsystem continues to handle system request. During the automatic rebuild process, system activity will continue as normal, however, the
system performance and fault tolerance will be affected.
!
Important:
The hot spare must have at least the same or more capacity as the
drive it replaces.
Introduction
1-13
1.3.4.2 Hot-Swap Disk Drive Support
The RAID subsystem has built the protection circuit to support the replacement
of UDMA hard disk drives without having to shut down or reboot the system.
The removable hard drive tray can deliver “hot swappable,” fault-tolerant RAID
solutions at prices much less than the cost of conventional SCSI hard disk
RAID subsystems. We provide this feature for subsystems to provide the advanced fault tolerant RAID protection and “online” drive replacement.
1.3.4.3 Hot-Swap Disk Rebuild
A Hot-Swap function can be used to rebuild disk drives in arrays with data
redundancy such as RAID level 1, 0+1, 3, 5 and 6. If a hot spare is not
available, the failed disk drive must be replaced with a new disk drive so that
the data on the failed drive can be rebuilt. If a hot spare is available, the
rebuild starts automatically when a drive fails. The RAID subsystem automatically and transparently rebuilds failed drives in the background with user-definable rebuild rates. The RAID subsystem will automatically restart the system
and the rebuild if the system is shut down or powered off abnormally during a
reconstruction procedure condition. When a disk is Hot Swap, although the
system is functionally operational, the system may no longer be fault tolerant.
Fault tolerance will be lost until the removed drive is replaced and the rebuild
operation is completed.
1-14
Introduction
Chapter 2
Installation Overview
Getting started with the NAS subsystem consists of the following steps:
Unpack the storage subsystem.
Identifying Parts of the subsystem.
Connect the NAS subsystem to the network.
Power on the subsystem.
Install Hard Drives.
Install OS.
Array Maintenance.
2.1 Unpacking the Subsystem
Before we continue, you need to unpack the subsystem and verify that the
contents of the shipping carton are all there and in good condition. Before
removing the subsystem from the shipping carton, you should visually inspect
the physical condition of the shipping carton. Exterior damage to the shipping
carton may indicate that the contents of the carton are damaged. If any damage is found, do not remove the components; contact the dealer where you
purchased the subsystem for further instructions.
The package contains the following items:
Installation Overview
2-1
•
•
•
•
•
•
•
DN-503A-PDC NAS subsystem unit
One power cord
Five CAT.5 Ethernet LAN cables
One external serial cable
Installation Reference Guide
Spare screws, etc.
Key set package
If any of these items are missing or damaged, please contact your dealer or
sales representative for assistance.
2-2
Installation Overview
2.2 Identifying Parts of the subsystem
The illustrations below identify the various features of the subsystem. Get yourself familiar with these terms as it will help you when you read further in the
following sections.
2.2.1 Front View
HDD Status LEDs
Power LED
Over Temp LED
Fan fail LED
Lock Indicator
HDD Power LEDs
Power on/off switch
HDD Access LEDs
LCD Display
Slot 3
Slot 2
Slot 4
Slot 1
Slot 5
Installation Overview
2-3
CD/DVD Recorder
(Optional for WSS 2003)
1. HDD status Indicator
Function
Parts
HDD Power LEDs
Green LED indicates power is on and hard drive status is good for
this slot.
HDD Status LEDs
Green LED indicates power is on and hard drive status is good for
this slot. If there is no hard drive, the LED is red.
HDD access LEDs
These LED will blink blue when the hard drive is being accessed.
2. Environment status
Parts
Function
Over temp LED
If temperature irregularity in these systems occurs (HDD slot temperature over 60oC/140oF or under 0oC/32oF), this LED will turn red
and an alarm will sound.
Fan fail LED
When a fan’s rotation speed is lower than 1500rpm, this LED will
turn red and an alarm will sound.
Power LED
Green LED indicates power is on.
2-4
Installation Overview
3. Lock Indicator
Every Drive Tray is lockable and is fitted with a lock indicator to indicate
whether or not the tray is locked into the chassis or not. Each tray is also fitted
with an ergonomic handle for easy tray removal.
Drive Tray is Locked
Drive Tray is Unlocked
4. Front Panel
Power LED
Busy LED
Down button
Exit button
Up button
Parts
Select button
Function
Power LED
Green LED indicates power is on.
Busy LED
Orange blinking LED indicates data is being accessed.
Up and Down
arrow buttons
Use the Up or Down arrow keys to go through the information on
the LCD screen. This is also used to move between each menu
when you configure the subsystem.
Select button
This is used to enter the option you have selected.
Exit button
Press this button to return to the previous menu.
Installation Overview
2-5
2.2.2 Rear View
a. For proNAS
Power Supply
AC power input socket
FAN
Monitor
R-Link
LAN2
LAN0
COM2
COM1
VGA
1394
LAN1
LAN3
Keyboard
2-6
USB 2.0 port
Mouse
Installation Overview
b. For WSS
Power Supply
AC power input socket
FAN
Monitor
R-Link
LAN3
LAN2
COM2
COM1
VGA
1394
LAN1
LAN4
Keyboard
USB 2.0 port
Mouse
1. R-Link Port : Remote Link through RJ-45 ethernet for remote management
The subsystem is equipped with one 10/100 Ethernet RJ45 LAN port. You use
web-based browser to management RAID subsystem through Ethernet for remote configuration and monitoring.
Link LED: Green LED indicates ethernet is linking.
Access LED: The LED will blink orange when the 100Mbps ethernet is being
accessed.
Note:
The R-Link IP address is shown in the LCD display panel. The default R-Link IP
address is 172.16.0.2 subnet mask 255.255.0.0.
Installation Overview
2-7
2.3 Connecting NAS subsystem to Your Network
1.
Before you use the NAS subsystem, please configuring your NAS subsystem at first. (Refer to Chapter 3 for configuring your RAID subsystem)
2.
To connect the NAS unit to the network, insert the cable that came with
the unit into the network connection on the back of NAS unit. Insert the
other end into a Gigabit BASE-T Ethernet connection on your network hub
or switch.
2.4 Powering-on the Subsystem
You should press the System Power Supply Switch. It will turn the NAS subsystem on and the Self-Test will be started automatically.
1.
Plug in the power cord located at the rear of the subsystem.
AC power
input socket
Power Supply
!
Note:
The subsystem is equipped with PFC (power factor correction), Full
Range power suppy. The subsystem will automatically selector
voltage.
2.
You should press the system switch to turn on the power.
3.
The “Power” LED on the front panel will turn green.
2-8
Installation Overview
2.5 Install Hard Drives
This section describes the physical locations of the hard drives supported by
the subsystem and gives instructions on installing a hard drive. The subsystem
supports hot-swapping allowing you to install or replace a hard drive while the
subsystem is running.
1.
Each Drive Tray has a locking mechanism. When the Lock Groove is
vertical, this indicates that the Drive Tray is locked. When the Lock
Groove is horizontal, then the Drive Tray is unlocked. Lock and unlock the
Drive Trays by using a flat-head screw driver.
Drive Tray is Locked
Tray Open Button
Drive Tray is Unlocked
2.
The Lock Grooves are located on a button. Press the button and the Drive
Tray handle will flip open.
3.
Pull the Drive Tray handle outwards to remove the tray from the
enclosure.
Installation Overview
2-9
!
Note:
When removing the Drive Tray Module from the enclosure, handle
with care to prevent dropping the module.
4.
To install the hard drive into the Drive Tray, first insert the hard drive as
show below.
5.
Turn the Drive Tray over. Notice the 4 screws. Tighten these 4 screws to
firmly secure the hard drive to the Drive Tray.
6.
To install the trays, insert the trays into the enclosure and close the Drive
Tray handle. Then lock the Drive Tray using a screw driver.
2-10
Installation Overview
2.6 Install OS
2.6.1
NAS subsystem with ProNAS DOM
1.
ProNAS is DOM (Disk on Module) based NAS operation environment. It
makes NAS subsystem operating with zero OS installation procedure.
2.
To getting start ProNAS configuration after the first time power on, please
reference “ProNAS Configuration Guide”.
2.6.2
NAS subsystem with Microsoft WSS
1.
Configuring the RAID functions in the NAS subsystem.
2.
Connect a keyboard and a VGA monitor to the NAS subsystem.
3.
To ensure proper communications between the NAS subsystem and Web
browser-based RAID management, Please connect the NAS subsystem
Monitor port to COM1 port.
Monitor
COM1
4.
Connect a CD-ROM. (Connect a USB port on the CD-ROM to USB port
of the NAS subsystem. ) Insert WSS CD.
Installation Overview
2-11
2.7 Array Maintenance
The following section describe how to remove and install the parts of your NAS
subsystem.
1.
Remove the screws located at the corners of the rear panel. Place the
screws in a safe place as you will need them later.
2.
Sliding top cover off.
Top cover
3.
Screw
Screw
Screw
Screw
Remove the screws on each side. Place the screws in a safe place as you
will need them later.
Remove Screw
2-12
Installation Overview
4.
Loose the screws and pull the front panel outwards from the enclosure.
5.
Tighten the screws to firmly secure the front panel to the enclosure.
Tighten
6.
Then you can install or replace parts of your NAS subsystem.
7.
Put back front panel. Replace the screws you removed in step 1 & 3.
Installation Overview
2-13
Chapter 3
Configuring
The subsystem has a setup configuration utility built in containing important
information about the configuration as well as settings for various optional
functions in the subsystem. This chapter explains how to use and make
changes to the setup utility.
Configuration Methods
There are three methods of configuring the subsystem. You may configure
through the following methods:
• VT100 terminal connected through the controller’s serial port
• Front panel touch-control keypad
• Web browser-based Remote RAID management via the R-Link ethernet port
!
Important:
The subsystem allows you to access the utility using only one method
at a time. You cannot use both methods at the same time.
3.1 Configuring through a Terminal
Configuring through a terminal will allow you to use the same configuration
options and functions that are available from the LCD panel. To start-up:
1.
Connect a VT100 compatible terminal or a PC operating in an equivalent
terminal emulation mode to the monitor port located at the rear of the
subsystem.
Configuring
3-1
Note:
You may connect a terminal while the subsystem’s power is on.
2.
Power-on the terminal.
3.
Run the VT100 program or an equivalent terminal program.
3-2
Configuring
4.
The default setting of the monitor port is 115200 baud rate, 8 data bit,
non-parity, 1 stop bit and no flow control.
Configuring
3-3
5.
Click
6.
Open the File menu, and then open Properties.
3-4
disconnect button.
Configuring
7.
Open the Settings Tab.
8.
Open the Settings Tab. Function, arrow and ctrl keys act as: Terminal
Keys, Backspace key sends: Crtl+H, Emulation: VT100, Telnet terminal:
VT100, Back scroll buffer lines: 500. Click OK.
Configuring
3-5
9.
Now, the VT100 is ready to use. After you have finished the VT100 Terminal setup, you may press “ X “ key (in your Terminal) to link the RAID
subsystem and Terminal together. Press “X’ key to display the disk array
Monitor Utility screen on your VT100 Terminal.
10. The Main Menu will appear.
Keyboard Function Key Definitions
“ A “ key - to move to the line above
“ Z “ key - to move to the next line
“ Enter “ key - Submit selection function
“ ESC “ key - Return to previous screen
“ L ” key - Line draw
“ X ” key - Redraw
3-6
Configuring
Main Menu
The main menu shows all function that enables the customer to execute actions by clicking on the appropriate link.
Note:
The password option allows user to set or clear the raid subsystem’s
password protection feature. Once the password has been set, the user
can only monitor and configure the raid subsystem by providing the correct password. The password is used to protect the internal RAID subsystem from unauthorized entry. The controller will check the password
only when entering the Main menu from the initial screen. The RAID
subsystem will automatically go back to the initial screen when it does
not receive any command in twenty seconds. The RAID subsystem
password is default setting at 00000000 by the manufacture.
Configuring
3-7
VT100 terminal configuration Utility Main Menu Options
Select an option and the related information or submenu items display beneath
it. The submenus for each item are explained on the section 3.3. The configuration utility main menu options are:
Option
Description
Quick Volume And Raid Set
Setup
Create a RAID configurations which is
consist of the number of physical disk
installed
Raid Set Functions
Create a customized raid set
Volume Set Functions
Create a customized volume set
Physical Drive Functions
View individual disk information
Raid System Functions
Setting the raid system configurations
Ethernet Configuration
Setting the Ethernet configurations
Views System Events
Record all system events in the buffer
Clear Event Buffer
Clear all event buffer information
Hardware Monitor
Show all system environment status
System Information
View the controller information
3-8
Configuring
3.2 Configuring the Subsystem Using the LCD Panel
The LCD Display front panel function keys are the primary user interface for
the Disk Array. Except for the “Firmware update” ,all configuration can be performed through this interface.The LCD provides a system of screens with areas for information, status indication, or menus. The LCD screen displays up
to two lines at a time of menu items or other information. The RAID subsystem
password is default setting at 00000000 by the manufacture.
Function Key Definitions
The four function keys at the top of the front panel perform the following functions :
Down button
Exit button
Up button
Select button
Function
Parts
Up and Down
arrow buttons
Use the Up or Down arrow keys to go through the information on
the LCD screen. This is also used to move between each menu
when you configure the subsystem.
Select button
This is used to enter the option you have selected.
Exit button
Press this button to return to the previous menu.
Configuring
3-9
3.3 Menu Diagram
The following tree diagram is a summary of the various configuration and setting functions that can be accessed through the LCD panel menus or the terminal monitor.
Raid 0
Selected Capacity
Select Stripe Size
4K,8K,16K,32K,64K,128K
Create Vol / Raid Set
Yes, No
Raid 1 or 0+1
Selected Capacity
Select Stripe Size
4K,8K,16K,32K,64K,128K
Create Vol / Raid Set
Yes, No
Initialization Mode
Foreground, No Initialization, No Init
Raid 1 or 0+1 +Spare
Selected Capacity
Select Stripe Size
4K,8K,16K,32K,64K,128K
Create Vol / Raid Set
Yes, No
Initialization Mode
Foreground, No Initialization , No Init
Raid 3
Selected Capacity
Create Vol / Raid Set
Yes, No
Initialization Mode
Quick Volume / Raid Setup
Foreground, Background, No Init
Raid 5
Selected Capacity
Select Stripe Size
4K,8K,16K,32K,64K,128K
Create Vol / Raid Set
Yes, No
Initialization Mode
Foreground, Background, No Init
Raid 3 + Spare
Selected Capacity
Create Vol / Raid Set
Yes, No
Initialization Mode
Foreground, Background, No Init
Raid 5 + Spare
Selected Capacity
Select Stripe Size
4K,8K,16K,32K,64K,128K
Create Vol / Raid Set
Initialization Mode
Yes, No
Foreground, Background, No Init
Raid 6
Selected Capacity
Select Stripe Size
4K,8K,16K,32K,64K,128K
Create Vol / Raid Set
Initialization Mode
Yes, No
Foreground, Background, No Init
Raid 6 + Spare
Selected Capacity
Select Stripe Size
4K,8K,16K,32K,64K,128K
Create Vol / Raid Set
Initialization Mode
3-10
Configuring
Yes, No
Foreground, Background, No Init
Create Raid Set
Select IDE Drives for Raid Set
Create Raid Set
Ch01 ~ Ch05
Yes, No
Edit The Raid Set Name
Delete Raid Set
Select Raid Set To Delete
Delete Raid Set
Yes, No
Are you sure?
Yes, No
Expand Raid Set
Select IDE Drives for Raid Set Expansion
Select Drives IDE Channel
Chxx ~ Ch05
Expand Raid Set
Raid Set Function
Yes, No
Are you sure?
Activate Raid Set
Select Raid Set To Active
Activate Raid Set
Are You Sure?
Create Hot Spare
Select Drives for Hot spare,
Max 3 Hot spare supported
Create Hot Spare
Yes, No
Yes, No
Yes, No
Chxx ~ Ch05
Yes, No
Delete Hot Spare Disk
Select The Hot Spare Device To Be Deleted
Delete Hot Spare
Yes, No
Raid Set Information
Select Raid Set To Display
Configuring
3-11
Create Volume Set
Create Volume From Raid Set
Volume Creation
Volume Name, Raid Level,
Capacity, Stripe Size, IDE Channel,
Drive Select, Cache Mode,
Tag Queuing, IDE Xfer Mode
Create Volume
Yes, No
Initialization Mode
Foreground, Background
Delete Volume Set
Delete Volume From Raid Set
Select Volume To Delete
Delete Volume Set
Are you sure?
Yes, No
Yes, No
Modify Volume Set
Modify Volume From Raid Set
Volume Set Function
Select Volume To Modify
Volume Modification
Modify Volume
Volume Name, Raid Level,
Capacity, Stripe Size,
IDE Channel, Drive Select,
Cache Mode, Tag Queuing,
IDE Xfer Mode
Yes, No
Are you sure?
Check Volume Set
Check Volume From Raid Set
Select Volume To Check
Check The Volume
Stop Volume Check
Stop All Volume Check
Are you sure?
Yes, No
Yes, No
Display Volume Info.
Display Volume Info in Raid
Select Volume To Display
3-12
Configuring
Yes, No
Yes, No
View Drive Information
Select The Drives
Create Pass Through Disk
Select The Drives
IDE Channel, Drive Select,
Cache Mode, Tag Queuing,
IDE Xfer Mode
Modify Pass Through Disk
Physical Drives
Select The Drives
IDE Channel, Drive Select,
Cache Mode, Tag Queuing,
IDE Xfer Mode
Delete Pass Through Disk
Select The Drives
Delete Pass Through
Yes, No
Are you sure?
Yes, No
Identify Selected Drive
Select The Drives
Yes, No
Mute The Alert Beeper
Alert Beeper Setting
Disabled, Enabled
Save The Settings
Yes, No
Change Password
Enter New Password
Re-Enter Password
Save The Password
Yes, No
JBOD / RAID Function
RAID, JBOD
Configured AS JBOD?
Are you sure?
Background Task Priority
Save The Settings
Raid System Function
Yes, No
Yes, No
UltraLow(5%), Low(20%),
Medium(50%),High(80%)
Yes, No
Maximum SATA Mode
SATA150, SATA150+NCQ,
SATA300, SATA300+NCQ
HDD Read Ahead Cache
Enable, Disable Maxtor,
Disable
Stagger Power on
0.4, 0.7, 1.0, 1.5, 2.0, 2.5,
3.0, 3.5, 4.0, 4.5, 5.0, 5.5, 6.0
HDD SMART status polling
Enabled, Disabled
Capacity Truncation
To Multiples of 10G,
To Multiples of 1G,
Disabled
Terminal Port Config
Baud Rate
Stop Bits
1200,2400,4800,9600,
19200,38400,57600,115200
1 bit, 2 bits
Update Firmware
Restart Controller
Are you sure?
Configuring
Yes, No
Yes, No
3-13
DHCP Function
Disabled, Enabled
Local IP Address
Ethernet Configuration
HTTP Port Number: 80
Telnet Port Number: 23
SMTP Port Number: 25
EtherNet Address
View System Events
Show System Events
Yes, No
Clear Event Buffer
Clear Event Buffer
Hardware Monitor
The Hard Monitor Information
System Information
The System Information
Note:
1. This subsystem can support up to 2 logical volumes.
2. The maximum logical volume size is 2 Terabyte.
3-14
Configuring
3.4 Web browser-based Remote RAID management via RLink ethernet port
Configuration of the internal RAID subsystem with remote RAID management is a
web browser-based application, which utilizes the browser installed on your operating system. Web browser-based remote RAID management can be used to manage all the raid function.
To configure internal RAID subsystem on a remote machine, you need to know its
IP Address. Launch your web browser by entering http://[IP Address] in the remote
web browser.
!
Important:
The R-Link IP address is shown in the LCD display panel. The default RLink IP address is 172.16.0.2 subnet mask 255.255.0.0. DHCP function
is "disabled". You can reconfigure the R-Link IP address through the LCD
panel or the terminal "Ethernet Configuration" menu.
Note that you must be logged in as administrator with local admin rights on the
remote machine to remotely configure it. The RAID subsystem controller default
User Name is “admin” and the Password is “00000000”.
Configuring
3-15
Main Menu
The main menu shows all function that enables the customer to execute actions by clicking on the appropriate link.
Individual Category
Description
Quick Function
Create a RAID configuration, which is consist of
the number of physical disk installed; it can
modify the volume set Capacity, Raid Level, and
Stripe Size.
Raid Set Functions
Create a customized raid set.
Volume Set Functions
Create customized volume sets and modify the
existed volume sets parameter.
Physical Drive
Create pass through disks and modify the existed
pass through drives parameter. It also provides
the function to identify the respect disk drive.
System Control
Setting the raid system configurations
Information
View the controller and hardware monitor
information. The Raid Set Hierarchy can also
view through the RaidSet Hierarchy item.
3-16
Configuring
Configuration Procedures
Below are a few practical examples of concrete configuration procedures.
3.5 Quick Create
The number of physical drives in the raid subsystem determines the RAID
levels that can be implemented with the raid set. You can create a raid set
associated with exactly one volume set. The user can change the raid level,
capacity, Volume Initialization Mode and stripe size . A hot spare option is also
created depending upon the existing configuration.
If the Volume set size is over 2TB, an option “Greater Two TB Volume Support” will be automatically provided in the screen as shown in the above
example. There are two options to select: “No” and “Yes”.
Greater Two TB Volume Support:
No: Volume Set capacity is set to maximum 2TB.
Yes: Volume Set capacity can be set over 2TB.
Tick on the Confirm The Operation and click on the Submit button in the
Quick Create screen, the raid set and volume set will start to initialize.
Configuring
3-17
Note:
1. In Quick Create your volume set is automatically configured based on the number of disks in your system. Use the Raid Set Function and Volume Set Function
if you prefer to customize your system.
2. When use Quick Create the Raid set will default mapping to 0&1 cluster. After
the initialization done, please use the volume set function to modify the IDE
Channel to 0.
3.To support Over 2TB Volume Set Capacity, please upgrade the RAID controller firmware to version 1.43 or later version.
3.6 Raid Set Functions
Use the Raid Set Function and Volume Set Function if you prefer to customize
your system. User manual configuration can full control of the raid set setting,
but it will take longer to complete than the Quick Volume/Raid Setup
configuration. Select the Raid Set Function to manually configure the raid set
for the first time or deletes existing raid set and reconfigures the raid set. A
raid set is a group of disks containing one or more volume sets. The maximum
number of RAID Sets that can be created depends on the number of disk
channels in the RAID subsystem. For 5 bay RAID Subsystem, five RAID Sets
can be created.
3.6.1 Create Raid Set
3-18
Configuring
To create a raid set, click on the Create Raid Set link. A “Select The IDE Drive
For RAID Set” screen is displayed showing the IDE drive connected to the
current controller. Click on the selected physical drives with the current raid set.
Enter 1 to 15 alphanumeric characters to define a unique identifier for a raid
set. The default raid set name will always appear as Raid Set. #.
Tick on the Confirm The Operation and click on the Submit button in the
screen, the raid set will start to initialize.
3.6.2 Delete Raid Set
To delete a raid set, click on the Delete Raid Set link. A “Select The RAID SET To
Delete” screen is displayed showing all raid set existing in the current controller.
Click the raid set number you which to delete in the select column to delete screen.
Tick on the Confirm The Operation and click on the Submit button in the
screen to delete it.
Configuring
3-19
3.6.3 Expand Raid Set
Use this option to expand a raid set, when a disk is added to your system.
This function is active when at least one drive is available.
To expand a raid set, click on the Expand Raid Set link. Select the target raid
set, which you want to expand it.
Tick on the available disk and Confirm The Operation, and then click on the
Submit button in the screen to add disks to the raid set.
Note:
1. Once the Expand Raid Set process has started, user cannot
stop it. The process must be completed.
2. If a disk drive fails during raid set expansion and a hot spare is
available, an auto rebuild operation will occur after the raid set expansion completes.
3-20
Configuring
Migrating occurs when a disk is added to a raid set. Migration status is displayed in the raid status area of the Raid Set information when a disk is added
to a raid set. Migrating status is also displayed in the associated volume status
area of the volume set Information when a disk is added to a raid set.
Configuring
3-21
3.6.4 Activate Incomplete Raid Set
When one of the disk drive is removed in power off state, the raid set state will
change to Incomplete State. If user wants to continue to work, when the RAID
subsystem is power on. User can use the Activate Raid Set option to active
the raid set. After user complete the function, the Raid State will change to
Degraded Mode.
To activate the incomplete the raid set, click on the Activate Raid Set link. A “Select
The RAID SET To Activate” screen is displayed showing all raid set existing in the
current controller. Click the raid set number you which to activate in the select
column.
3-22
Configuring
Click on the Submit button in the screen to activate the raid set that has
removed one of disk drive in the power off state. The RAID subsystem will
continue to work in degraded mode.
Configuring
3-23
3.6.5 Create Hot Spare
When you choose the Create Hot Spare option in the Raid Set Function, all
unused physical devices connected to the current controller appear: Select
the target disk by clicking on the appropriate check box. Tick on the Confirm
The Operation, and click on the Submit button in the screen to create the
hot spares.
The create Hot Spare option gives you the ability to define a global hot spare.
3.6.6 Delete Hot Spare
Select the target Hot Spare disk to delete by clicking on the appropriate
check box.
Tick on the Confirm The Operation, and click on the Submit button in the
screen to delete the hot spares.
3-24
Configuring
3.6.7 Rescue Raid Set
If you try to Rescue Missing RAID Set, please contact our engineer for
assistance.
Configuring
3-25
3.7 Volume Set Function
A volume set is seen by the host system as a single logical device. It is organized in a RAID level with one or more physical disks. RAID level refers to the
level of data performance and protection of a volume set. A volume set capacity can consume all or a portion of the disk capacity available in a raid set.
Multiple volume sets can exist on a group of disks in a raid set. Additional
volume sets created in a specified raid set will reside on all the physical disks
in the raid set. Thus each volume set on the raid set will have its data spread
evenly across all the disks in the raid set.
3.7.1 Create Volume Set
The following is the volume set features:
1.Volume sets of different RAID levels may coexist on the same raid set.
2.Up to 2 volume sets in a raid set can be created by the RAID subsystem
controller.
To create volume set from raid set system, move the cursor bar to the main
menu and click on the Create Volume Set link. The Select The Raid Set To
Create On It screen will show all raid set number. Tick on a raid set number
that you want to create and then click on the Submit button.
The new create volume set allows user to select the Volume name, capacity,
RAID level, strip size, Cache mode, tag queuing, IDE Data Xfer Mode and IDE
channel/IDE Drive#.
Note:
To support Over 2TB Volume Set Capacity, please upgrade the RAID controller firmware to version 1.43 or later version.
3-26
Configuring
Volume Name:
The default volume name will always appear as Volume Set. #. You can rename the volume set name providing it does not exceed the 15 characters limit.
Raid Level:
Set the RAID level for the Volume Set. Highlight Raid Level and press Enter.
The available RAID levels for the current Volume Set are displayed. Select a
RAID level and press Enter to confirm.
Capacity:
The maximum volume size is default in the first setting. Enter the appropriate
volume size to fit your application.
If the Volume set size is over 2TB, an option “Greater Two TB Volume Support” will be automatically provided in the screen as shown in the above
example. There are two options to select: “No” and “Yes”.
Greater Two TB Volume Support:
No: Volume Set capacity is set to maximum 2TB.
Yes: Volume Set capacity can be set over 2TB.
Configuring
3-27
Initialization Mode:
Set the Initialization Mode for the Volume Set. Foreground mode is faster
completion and background is instant available.
Strip Size:
This parameter sets the size of the stripe written to each disk in a RAID 0, 1,
0+1, or 5 logical drive. You can set the stripe size to 4 KB, 8 KB, 16 KB, 32
KB, 64 KB, or 128 KB.
A larger stripe size produces better-read performance, especially if your computer does mostly sequential reads. However, if you are sure that your computer does random reads more often, select a small stripe size
Note: RAID level 3 can’t modify strip size.
Cache Mode:
The RAID subsystem supports Write-Through Cache and Write-Back Cache.
Tag Queuing:
The Enabled option is useful for enhancing overall system performance under
multi-tasking operating systems. The Command Tag (Drive Channel) function controls the SCSI command tag queuing support for each drive channel. This function
should normally remain enabled. Disable this function only when using older SCSI
drives that do not support command tag queuing
IDE Xfer Mode
The RAID subsystem supports 150.00 MB/sec as the highest data transfer
rate.
IDE Channel
One IDE channel can be applied to the RAID subsystem. Choose the IDE
Channel.
Drive Select
Each IDE channel can connect 1 device (Master). IDE Drive#0:Master, #1:
Slave, #2-->#15:Reserved
3-28
Configuring
3.7.2 Delete Volume Set
To delete Volume from raid set system function, move the cursor bar to the
main menu and click on the Delete Volume Set link. The Select The Volume Set To Delete screen will show all raid set number. Tick on a raid set
number and the Confirm The Operation and then click on the Submit button to
show all volume set item in the selected raid set. Tick on a volume set number and the Confirm The Operation and then click on the Submit button to
delete the volume set.
Configuring
3-29
3.7.3 Modify Volume Set
To modify a volume set from a raid set:
(1). Click on the Modify Volume Set link.
(2). Tick on the volume set from the list that you wish to modify. Click on the
Submit button.
The following screen appears.
Use this option to modify volume set configuration. To modify volume set attribute
values from raid set system function, move the cursor bar to the volume set attribute menu and click on it. The modify value screen appears. Move the cursor
bar to an attribute item, and then click on the attribute to modify the value. After
you complete the modification, tick on the Confirm The Operation and click on
the Submit button to complete the action. User can modify all values except the
capacity.
3.7.3.1 Volume Expansion
Volume Capacity (Logical Volume Concatenation Plus Re-stripe)
Use this raid set expands to expand a raid set, when a disk is added to your
system. (refer to section 3.6.3)
The expand capacity can use to enlarge the volume set size or create another
volume set. The modify volume set function can support the volume set expansion function. To expand volume set capacity value from raid set system
function, move the cursor bar to the volume set Volume capacity item and
entry the capacity size.
Tick on the Confirm The Operation and click on the Submit button to complete the action. The volume set start to expand.
3-30
Configuring
Configuring
3-31
3.7.4
Volume Set Migration
Migrating occurs when a volume set is migrating from one RAID level to
another, a volume set strip size changes, or when a disk is added to a raid
set. Migration status is displayed in the volume status area of the RaidSet
Hierarchy screen when one RAID level to another, a Volume set strip size
changes or when a disk is added to a raid set.
3-32
Configuring
3.7.5 Check Volume Set
To check a volume set from a raid set:
(1). Click on the Check Volume Set link.
(2). Tick on the volume set from the list that you wish to check. Tick on Confirm The Operation and click on the Submit button.
Use this option to verify the correctness pf the redundant data in a volume set.
For example, in a system with dedicated parity, volume set check means computing the parity of the data disk drives and comparing the results to the contents of the dedicated parity disk drive. The checking percentage can also be
viewed by clicking on RaidSet Hierarchy in the main menu.
3.7.6 Stop VolumeSet Check
Use this option to stop the Check Volume Set function.
Configuring
3-33
3.8 Physical Drive
Choose this option from the Main Menu to select a physical disk and to perform the operations listed below.
3.8.1 Create Pass-Through Disk
To create pass-through disk, move the mouse cursor to the main menu and
click on the Create Pass-Through link. The relative setting function screen
appears.
Disk is no controlled by the internal RAID subsystem firmware and thus cannot
be a part of a volume set. The disk is available to the operating system as an
individual disk. It is typically used on a system where the operating system is
on a disk not controlled by the RAID firmware. User can also select the cache
mode, Tagged Command Queuing, IDE Data Xfer Mode and IDE channel/IDE
Drive# for this volume.
3-34
Configuring
3.8.2 Modify Pass-Through Disk
Use this option to modify the Pass-Through Disk Attribute. User can modify the
cache mode, Tagged Command Queuing, IDE Data Xfer Mode and IDE channel/IDE Drive# on an existed pass through disk.
To modify the pass-through drive attribute from the pass-through drive pool,
move the mouse cursor bar to click on Modify Pass-Through link. The Select
The Pass Through Disk For Modification screen appears tick on the PassThrough Disk from the pass-through drive pool and click on the Submit button
to select drive.
The Enter Pass-Through Disk Attribute screen appears, modify the drive attribute values, as you want.
Configuring
3-35
3.8.3 Delete Pass-Through Disk
To delete pass-through drive from the pass-through drive pool, move the
mouse cursor bar to the main menus and click on Delete Pass Through link.
After you complete the selection, tick on the Confirm The Operation and click
on the Submit button to complete the delete action.
3.8.4 Identify Selected Drive
To prevent removing the wrong drive, the selected disk LED will light for physically locating the selected disk when the Identify Selected Drive is selected.
To identify the selected drive from the drives pool, move the mouse cursor bar to
click on Identify Selected Drive link. The Select The IDE Device For identification screen appears tick on the IDE device from the drives pool and Flash method.
After completing the selection, click on the Submit button to identify selected
drive.
3-36
Configuring
3.9 System Configuration
3.9.1 System Configuration
To set the raid system function, move the cursor bar to the main menu and
click on he Raid System Function link. The Raid System Function menu will
show all items. Select the desired function.
System Beeper Setting:
The Alert Beeper function item is used to Disabled or Enable the RAID subsystem controller alarm tone generator.
RAID Rebuild Priority:
The Raid Rebuild Priority is a relative indication of how much time the controller devotes to a rebuild operation. The RAID subsystem allows user to choose
the rebuild priority (ultraLow, Low, Medium, High) to balance volume set access and rebuild tasks appropriately. For high array performance, specify a
Low value.
Configuring
3-37
Terminal Port Configuration:
Speed setting values are 1200, 2400, 4800, 9600, 19200,38400, 57600, and
115200.
Stop Bits values are 1 bit and 2 bits.
Note: Parity value is fixed at None.
Data Bits value is fixed at 8 bits.
JBOD/RAID Configuration
The RAID subsystem supports JBOD and RAID configuration.
Maximum SATA Mode Supported:
The 5 SATA drive channel can support up to SATA ll, which runs up to 300MB/s.
NCQ is a command protocol in Serial ATA that can only be implemented on native
Serial ATA hard drives. It allows multiple commands to be outstanding within a
drive at the same time. Drives that support NCQ have an internal queue where
outstanding commands can be dynamically rescheduled or re-ordered, along with
the necessary tracking mechanisms for outstanding and completed portions of
the workload. RAID subsystem allows user to choose the SATA Mode: SATA150,
SAT150+NCQ, SAT300, SATA300+NCQ.
HDD Read Ahead Cache:
This option allows the users to disable the cache of the HDDs on the RAID
subsystem. To some HDD models, disabling the cache in the HDD is necessary to prove the RAID subsystem functions correctly.
Stagger Power On Control:
This option allows the power supplier to power up in order each HDD on the
RAID subsystem. In the past, all the HDDs on the RAID subsystem are powered up altogether at the same time. The power transfer time (lag time) from
the last HDD to the next one can be set within the range of 0.4 to 6.0.
HDD SMART Status Polling:
The RAID subsystem can read HDD temperature information through the
SMART function. This option allows the users to enable the repeat to scan the
HDD temperature. This function is default enabled.
3-38
Configuring
Disk Capacity Truncation Mode:
This RAID subsystem use drive truncation so that drives from differing vendors
are more likely to be able to be used as spares for each other. Drive truncation slightly decreases the usable capacity of a drive that is used in redundant
units.
Multiples Of 10G: If you have 120 GB drives from different vendors; chances
are that the capacity varies slightly. For example, one drive might be 123.5
GB, and the other 120 GB. This drive Truncation mode Multiples Of 10G
uses the same capacity for both of these drives so that one could replace the
other.
Multiples Of 1G: If you have 123 GB drives from different vendors; chances
are that the capacity varies slightly. For example, one drive might be 123.5
GB, and the other 123.4 GB. This drive Truncation mode Multiples Of 1G
uses the same capacity for both of these drives so that one could replace the
other.
No Truncation: It does not truncate the capacity.
Configuring
3-39
3.9.2 EtherNet Config
To set the EtherNet function, move the cursor bar to the main menu and click
on he EtherNet Config. The Raid System EtherNet Function menu will show
all items. Select the desired function.
3-40
Configuring
3.9.3 Alert By Mail Config
To set the Event Notification function, move the cursor bar to the main menu and
click on the Alert By Mail Config. The Raid System Event Notification Function
menu will show all items. Select the desired function. When an abnormal condition occurs, an error message will be email to administrator that a problem has
occurred. Events are classified to 4 levels (urgent, serious, warning, message).
Configuring
3-41
3.9.4 SNMP Configuration
The SNMP gives users independence from the proprietary network management
schemes of some manufacturers and SNMP is supported by many WAN and LAN
manufacturers enabling true LAN/ WAN management integration.
To set the SNMP function, move the cursor bar to the main menu and click on
he SNMP Configuration. The Raid System SNMP Function menu will show
all items. Select the desired function.
SNMP Trap Configurations: Type the SNMP Trap IP Address. The Port default is 162.
SNMP System Configuration:
Community: The default is Public.
(1)sysContact.0; (2)sysLocation.0; (3)sysName.0: SNMP parameter (31 bytes
max). If this 3 categories are selected during initial setting then when an error
occurs SNMP will send out a message that includes the 3 categories within
3-42
Configuring
the message. This allows user to easily define which RAID unit is having
problem. Once this setting is done, alert by mail configuration will also work in
the same way.
SNMP Trap Notification Configurations: Select the desired function.
After you complete the addition, tick on the Confirm The Operation and click
on the Submit button to complete the action.
3.9.5 NTP Configuration
NTP stands for Network Time Protocol, and it is an Internet protocol used to
synchronize the clocks of computers to some time reference. NTP is an
Internet standard protocol. You can directly type your NTP Server IP Address
to have the RAID subsystem can work with it.
To set the NTP function, move the cursor bar to the main menu and click on
he NTP Configuration. The Raid System NTP Function menu will show all
items. Select the desired function.
Configuring
3-43
3.9.6 View Events
To view the RAID subsystem controller’s information, move the mouse cursor
to the main menu and click on the System Information link. The Raid Subsystem events Information screen appears.
Choose this option to view the system events information: Time, Device, Event
type, Elapse Time and Errors. The RAID system does not built the real time
clock. The Time information is the relative time from the client machine power
on.
3-44
Configuring
3.9.7 Generate Test Events
If you want to generate test events, move the cursor bar to the main menu and
click on he Generate Test Events. Tick on the Confirm The Operation, and
click on the Submit button in the screen to create the hot spares. Then click
on the View Events/Mute Beeper to view the test event.
Configuring
3-45
3.9.8 Clear Events Buffer
Use this feature to clear the entire events buffer information.
3.9.9 Modify Password
To set or change the RAID subsystem password, move the mouse cursor to Raid
System Function screen, and click on the Change Password link. The Modify
System Password screen appears.
3-46
Configuring
The password option allows user to set or clear the raid subsystem’s password protection feature. Once the password has been set, the user can only
monitor and configure the raid subsystem by providing the correct password.
The password is used to protect the internal RAID subsystem from unauthorized entry. The controller will check the password only when entering the
Main menu from the initial screen. The RAID subsystem will automatically go
back to the initial screen when it does not receive any command in ten
seconds.
To disable the password, press Enter key only in both the Enter New Password
and Re-Enter New Password column. Once the user confirms the operation
and clicks the Submit button. The existing password will be cleared. No password checking will occur when entering the main menu from the starting screen.
3.9.10 Upgrade Firmware
Please reference the section 3.12 for more information.
Configuring
3-47
3.10 Information Menu
3.10.1 RaidSet Hierarchy
Use this feature to view the internal raid subsystem current raid set, current volume set and physical disk configuration.
To view the raid set information, move the mouse cursor to the right column and
click on the Raid Set # link. The Raid Set Information screen appears.
3-48
Configuring
To view the disk information, move the mouse cursor to the right column and click
on the CH # link. The Disk Information screen appears. The SMART Attribute
(Threshold) Is A Normalized Value, The Value Is The Larger The Better. If The
Attribute Value Is Smaller Than The Threshold Value, The Disk Is In Unstable
State.
To view the volume set information, move the mouse cursor to the right column
and click on the Volume Set # link. The Volume Set Information screen appears.
Configuring
3-49
3.10.2 System Information
To view the RAID subsystem controller’s information, move the mouse cursor to
the main menu and click on the System Information link. The Raid Subsystem
Information screen appears.
Use this feature to view the raid subsystem controller’s information. The controller name, firmware version, serial number, main processor, CPU data/Instruction
cache size and system memory size/speed appear in this screen.
3-50
Configuring
3.10.3 Hardware Monitor
To view the RAID subsystem controller’s hardware monitor information, move the
mouse cursor to the main menu and click the Hardware Monitor link. The Hardware Information screen appears.
The Hardware Monitor Information provides the temperature, fan speed (chassis
fan) and voltage of the internal RAID subsystem. All items are also unchangeable.
The warning messages will indicate through the LCD, LED and alarm buzzer.
Item
Warning Condition
Controller Board Temperature
> 60 Celsius
HDD Temperature
> 55 Celsius
Controller Fan Speed
< 1500 RPM
Power Supply +12V
< 10.5V or > 13.5V
Power Supply +5V
< 4.7V or > 5.4V
Power Supply +3.3V
< 3.0V or > 3.6V
DDR Supply Voltage +2.5V
< 2.25V or > 2.75V
CPU Core Voltage +1.3V
< 1.17V or > 1.43V
DDR Termination Power +1.25V
< 1.125V or > 1.375V
Configuring
3-51
3.11 Creating a New RAID or Reconfiguring an Existing
RAID
You can configure raid sets and volume sets using Quick Create or Raid Set
Functions/Volume Set Functions configuration method. Each configuration
method requires a different level of user input. The general flow of operations
for raid set and volume set configuration is:
Step
Action
1
Designate hot spares/pass-through (optional).
2
Choose a configuration method.
3
Create raid set using the available physical drives.
4
Define volume set using the space in the raid set.
5
Initialize the volume set and use volume set in the HOST OS.
3-52
Configuring
3.12 Upgrading the Firmware
Upgrading Flash Firmware Programming Utility
Since the RAID subsystem controller features flash firmware, it is not necessary
to change the hardware flash chip in order to upgrade the RAID firmware. The
user can simply re-program the old firmware through the RS-232 port. New releases of the firmware are available in the form of a DOS file at OEM’s FTP. The
file available at the FTP site is usually a self-extracting file that contains the
following:
XXXXVVV.BIN Firmware Binary (where “XXXX” refers to the model name and
“VVV” refers to the firmware version)
README.TXT It contains the history information of the firmware change. Read
this file first before upgrading the firmware.
These files must be extracted from the compressed file and copied to one directory in drive A or C.
Establishing the Connection for the RS-232
The firmware can be downloaded to the RAID subsystem controller by using an
ANSI/VT-100 compatible terminal emulation program or Remote web browser
management. You must complete the appropriate installation procedure before
proceeding with this firmware upgrade. Whichever terminal emulation program
is used must support the ZMODEM file transfer protocol.
Configuration of the internal RAID subsystem web browser-based remote RAID
management. Web browser-based RAID management can be used to update
the firmware. You must complete the appropriate installation procedure before
proceeding with this firmware upgrade.
Configuring
3-53
Upgrading Firmware Through ANSI/VT-100 Terminal Emulation
Get the new version firmware for your RAID subsystem controller. For Example,
download the bin file from your OEM’s web site onto the c:
1. From the Main Menu, scroll down to “Raid System Function”
2. Choose the “Update Firmware”, The Update The Raid Firmware dialog box
appears.
3. Go to the tool bar and select Transfer. Open Send File.
3-54
Configuring
4. Select “ZMODEM modem” under Protocol. ZMODEM as the file transfer protocol of your terminal emulation software.
5. Click Browse. Look in the location where the Firmware upgrade software is
located. Select the File name:
“6160FIRM.BIN” and click open.
6. Click Send. Send the Firmware Binary to the controller
Configuring
3-55
7. When the Firmware completes downloading, the confirmation screen appears.
Press “Yes” to start program the flash ROM.
8. When the Flash programming starts, a bar indicator will show “ Start Updating
Firmware. Please Wait:”.
3-56
Configuring
9. The Firmware upgrade will take approximately thirty seconds to complete.
10. After the Firmware upgrade is complete, a bar indicator will show “ Firmware
Has Been Updated Successfully”.
NOTE:
The user has to reconfigure all of the settings after the firmware upgrade is complete, because all of the settings will default to the original
default values.
Configuring
3-57
Upgrading Firmware Through Web Browser Management
Get the new version firmware for your RAID subsystem controller.
1. To upgrade the RAID subsystem firmware, move the cursor to “Upgrade Firmware” link. The “Upgrade The Raid System Firmware” screen appears.
2. Click Browse. Look in the location where the Firmware upgrade software is
located. Select the File name:
“XXXXXXXX.BIN” and click open.
3.Click the “Confirm The Operation” and press the “Submit” button.
4. The Web Browser begins to download the firmware binary to the controller
and start to update the flash ROM.
3-58
Configuring
5. After the firmware upgrade is complete, a bar indicator will show “ Firmware
Has Been Updated Successfully”
Configuring
3-59
ProNAS 1.1.x
Configuration Guide
Revision 1.4
P/N: PW0020000000203
ProNAS 1.1.x
Table of Contents
Chapter 1
Introduction.................................................................................................5
1.1
proNAS Key Components ..............................................................................................................................5
1.2
Setting the IP Address and Using the Web Browser..........................................................................6
1.3
The Phases of the Installation Process .....................................................................................................9
Chapter 2
NAS Device Manager ..............................................................................10
2.1
Using NAS Device Manager....................................................................................................................... 10
2.2
Quick Setup....................................................................................................................................................... 12
2.3
Create Raid Set and Volume Set.............................................................................................................. 14
2.4
Delete Raid Set................................................................................................................................................ 19
2.5
Delete Volume Set ......................................................................................................................................... 20
2.6
Check Volume Set .......................................................................................................................................... 21
2.7
Modify Volume Set ........................................................................................................................................ 22
2.8
Expanding Raid Set........................................................................................................................................ 23
Chapter 3
3.1
proNAS Manager......................................................................................25
Volume Manager ............................................................................................................................................ 26
3.1.1
Volume Group Management................................................................................................................ 27
3.1.1.1
Initialize the default Volume Group proNASVG .................................................................... 27
3.1.1.2
Create another Volume Group...................................................................................................... 29
3.1.1.3
Reset and Remove Volume Group .............................................................................................. 33
3.1.2
Logical Volume Configuration ............................................................................................................. 35
3.1.2.1
Create new Logical Volume ........................................................................................................... 35
3.1.2.2
Extending Logical Volume Size..................................................................................................... 37
3.1.3
Volume Snapshot ...................................................................................................................................... 39
3.1.3.1
Create Snapshots Manually............................................................................................................ 40
3.1.3.2
Create Snapshots Based from Schedule................................................................................... 42
3.1.3.3
Delete Snapshots................................................................................................................................ 46
3.1.4
Volume Replication................................................................................................................................... 47
3.1.4.1
Replication Configuration ............................................................................................................... 48
3.1.4.2
Checking the Status of your Replication .................................................................................. 53
3.1.4.3
Extending Logical Volume under Replication......................................................................... 54
3.1.5
3.2
iSCSI............................................................................................................................................................. 55
3.1.5.1
iSCSI Configuration............................................................................................................................ 55
3.1.5.2
Disable iSCSI in Logical Volume................................................................................................... 58
3.1.5.3
Restore iSCSI to Ordinary Logical Volume............................................................................... 59
Network Manager................................................................................................................................................ 61
2
Configuration Guide
ProNAS 1.1.x
3.2.1
Network Setting and Trunking............................................................................................................... 61
3.2.2
Internet Gateway ......................................................................................................................................... 64
3.2.3
SNMP/MRTG.................................................................................................................................................. 65
3.3
Account Manager................................................................................................................................................. 67
3.3.1
3.3.1.1
Windows Authentication ................................................................................................................. 67
3.3.1.2
Sample Steps to Join the NAS to Windows AD Domain: ................................................. 68
3.3.1.3
NIS Authentication............................................................................................................................. 70
3.3.1.4
Sample Steps to Join the NAS to NIS Domain:..................................................................... 70
3.3.2
3.4
External Accounts Integration (Joining Windows or NIS Domain)......................................... 67
Local Account and Group Management ........................................................................................... 71
Share Manager...................................................................................................................................................... 79
3.4.1
Share Management .................................................................................................................................... 80
3.4.1.1
Creating a New Share ...................................................................................................................... 80
3.4.1.2
Applying ACL........................................................................................................................................ 81
3.4.1.3
Modifying a Share.............................................................................................................................. 81
3.4.1.4
Deleting a Share ................................................................................................................................. 82
3.4.2
Properties Setting ....................................................................................................................................... 82
3.4.2.1
3.4.3
Steps to Make a Share Folder a Public Folder Accessible to All Users:...................... 83
Protocol Setting ........................................................................................................................................... 84
3.4.3.1
CIFS........................................................................................................................................................... 84
3.4.3.2
NFS ........................................................................................................................................................... 85
3.4.3.3
AppleTalk................................................................................................................................................ 85
3.4.3.4
Novell ...................................................................................................................................................... 85
3.4.4
Privilege Setting (Permission)................................................................................................................. 87
3.4.4.1
Group....................................................................................................................................................... 87
3.4.4.2
Account................................................................................................................................................... 88
3.4.4.3
IP Address.............................................................................................................................................. 90
3.4.5
Rsync ................................................................................................................................................................ 92
3.4.6
Duplication..................................................................................................................................................... 96
3.4.7
Default Shares............................................................................................................................................... 99
3.5
System Manager.................................................................................................................................................100
3.5.1
Information tab ..........................................................................................................................................100
3.5.2
Upgrade tab ................................................................................................................................................101
3.5.3
Report tab ....................................................................................................................................................102
3.5.4
Time tab ........................................................................................................................................................103
3.5.5
Serial Ports tab...........................................................................................................................................104
3.5.6
Power tab......................................................................................................................................................105
3.5.7
Reboot tab ...................................................................................................................................................106
3.5.8
Service tab ...................................................................................................................................................107
3.5.9
Status tab......................................................................................................................................................110
Configuration Guide
3
ProNAS 1.1.x
3.5.10
3.6
MRTG tab ...................................................................................................................................................111
Backup Manager ...............................................................................................................................................112
3.6.1
proNAS Configuration Backup ............................................................................................................112
3.6.2
Configure Backup Plan............................................................................................................................113
3.6.3
Tape Control ................................................................................................................................................118
3.7
Log Manager........................................................................................................................................................119
3.8
Event Manager ....................................................................................................................................................120
3.8.1
E-mail Setting tab .....................................................................................................................................120
3.8.2
Event Setting tab.......................................................................................................................................121
Chapter 4
File Manager........................................................................................... 122
4.1
Introduction to File Manager ........................................................................................................................122
4.2
Logon to File Manager ....................................................................................................................................123
4.3
Directory and Upload Function....................................................................................................................124
4.4
User Access Right and Group Access Right ...........................................................................................126
4.5
Change Password and Logout......................................................................................................................126
Chapter 5
proBackup............................................................................................... 127
5.1
Introduction to proBackup.............................................................................................................................127
5.2
Administrator Logon.........................................................................................................................................127
5.3
Create Backup Plan ...........................................................................................................................................129
5.4
Restore Backup....................................................................................................................................................135
5.5
Account Detail.....................................................................................................................................................136
Chapter 6
proNAS HA (Optional Function) ........................................................ 137
6.1
Introduction to proNAS HA .....................................................................................................................137
6.2
Getting Started with proNAS HA...........................................................................................................138
6.2.1
Hardware Aspect .......................................................................................................................................139
6.2.2
Procedure for Setting Up proNAS HA..............................................................................................140
6.3
ProNAS HA Properties................................................................................................................................149
6.4
Extending a Logical Volume in HA........................................................................................................150
6.5
Clear All HA Configuration.......................................................................................................................151
6.6
License Registration.....................................................................................................................................153
6.7
Event Log Properties ...................................................................................................................................154
4
Configuration Guide
ProNAS 1.1.x
Chapter 1 Introduction
Proware deliver NAS subsystem together with “proNAS” NAS management solution and
proBackup” client backup solution as well as proNAS HA solution to provide the
enterprises the most flexible, scalable, securable and manageable NAS
environment. Administrator can centralize and easily manage the NAS nodes via
Internet/Intranet and enhance greater data availability via proNAS.
1.1
¾
¾
proNAS Key Components
NAS Device Manager: Provides configuration of physical hard disks with
Hardware RAID Controller.
proNAS Manager: Provides several management tools to ease the NAS
administration job.
‹
‹
Volume Manager: Responsible for volume management. Configuration of
volume groups, logical volumes, volume snapshot and volume replication.
Account Manager: Local and external account configuration. Import large
accounts.
Backup Manager: Supports system configuration backup and setup the backup
plan for data backup.
Share Manager: Share configuration and ACL setting. This also includes
Rsync and Duplication functions.
System Manager: System configuration and firmware upgrade
‹
Network Manager: Configuration of network information and trunking.
‹
Log Manager: Contains NAS system logs.
‹
Event Manager: Configuration of email notification and system actions when
events occur.
‹
‹
‹
¾
¾
¾
File Manager: Provides user logon mode for share owner to perform folder and
file management such as share folder access control.
proNAS HA: (optional). Provides function of High Availability (two-node cluster)
in Active-Standby mode.
proBackup: Provides web-based GUI backup solution for desktop clients.
Each function of these components is described in the following Chapters.
NOTE: If your proNAS model is DN-503AH, DN-503AH-PDC, SN1403AH, SN-1403AH-PDC, SN-2803H, SN-2803H4, SN-2803H-PDC,
SN-2803H-DX, SN-2803H-QX, SN-2123H, SN-2123H-DX, SN2123H-QX, SN-3163H, SN-3163H-DX, or SN-3163H-QX, use the
NAS Device Manager to configure the RAID controller. Refer to
Chapter 2.
Configuration Guide
5
ProNAS 1.1.x
IMPORTANT: If you use the RAID Manager GUI via web browser or
the LCD front panel buttons to create a Raid Set/Volume Set, and
use the Quick Setup function, you need to re-map the host channel
mapping from “0&1” to “0”. Quick Setup in RAID Manager will map
a Volume Set to both Host Channels 0 and 1 (0&1). To re-map the
Volume Set, use “Modify Volume Set” function in RAID Manager.
Mapping Volume Set to Host Channel 0 only can avoid some
problem when Volume Set is used by the NAS system.
1.2
Setting the IP Address and Using the Web Browser
NOTE: Java 2 Runtime Environment (J2RE) 1.4.2 or later must be
installed before using the proNAS management interface. (Free
download from: http://java.sun.com/j2se/index.jsp)
1. To connect to NAS, change the network settings of your computer to be able to
connect to IP address 172.16.0.1 (see table below), or add IP address 172.16.0.5
subnet 255.255.0.0.
Entity
LAN0 (eth0) IP address
Subnet Mask
Hostname
Username
Password
Default Value
172.16.0.1
255.255.0.0
proNAS
admin
proware
proNAS Default Values
2. Open Web browser.
3. Enter the following URL in the address bar: http://172.16.0.1 then press Enter.
4. In the page that opens, click “Admin Login” command button to enter the NAS
administration page.
START button on the first proNAS
6
Configuration Guide
ProNAS 1.1.x
5. Enter Account as “admin” and password as “proware” and click the Logon
command button.
Login Screen
6. The proNAS main screen will be displayed showing proNAS, NAS Device Manager,
and Event Manager.
Configuration Guide
7
ProNAS 1.1.x
NOTE: For security reason, it is necessary to change the default
admin password. To change admin password, click the “Change
Password” button and enter the new password.
8
Configuration Guide
ProNAS 1.1.x
1.3
The Phases of the Installation Process
The installation and configuration of a proNAS system consists of five phases.
Phase 1: Set up the Hardware RAID Controller (NAS Device Manager)
Prior to proNAS system configuration, a basic hardware RAID configuration must
be setup. (Please see Important note below.)
If your proNAS model is DN-503AH, DN-503AH-PDC, SN-1403AH, SN-1403AHPDC, SN-2803H, SN-2803H4, SN-2803H-PDC, SN-2803H-DX, SN-2803H-QX,
SN-2123H, SN-2123H-DX, SN-2123H-QX, SN-3163H, SN-3163H-DX, or SN3163H-QX, please refer to Chapter 2 for the setup procedure.
If your proNAS model is not one of the models listed above, please consult the
RAID controller manual of the proNAS model for configuring the RAID.
Phase 2: Configure proNAS and its components with proNAS Manager. This is
described in details in Chapter 3 proNAS Manager. To configure proNAS, you
need to:
‹ Join a disk (volume created using NAS Device Manager or using RAID
controller configuration utility) to the system default volume group
“proNASVG” using Volume Manager, and create Logical Volumes. This is
described in Chapter 3 Section 3.1.1 to 3.1.2.
‹ Configure the network settings via Network Manager. This is described in
Chapter 3 Section 3.2.1.
‹ Create or import accounts with Account Manager as described in Chapter 3
Section 3.3.
‹ Setup the shares using Share Manager and assign account/group permissions.
This is described in Chapter 3 Section 3.4.
‹ Windows clients can start using the proNAS shares using CIFS protocol.
UNIX/Linux clients need to enable NFS protocol (disabled by default).
Phase 3: (Optional) Perform NAS system maintenance.
‹ Maintain system via System Manager, as described in Chapter 3 Section 3.5
‹ Check system status using Log Manager and Event Manager. This is described
in Chapter 3 Sections 3.7 and 3.8.
‹ Backup system configuration and data using Backup Manager. This is
described in Chapter 3 Section 3.6.
Phase 4: (Optional) Setup proNAS HA for high-availability environment. Please refer
to Chapter 6 for proNAS HA configuration.
Phase 5: (Optional) Users can store and backup data into proNAS system.
‹ Store data into proNAS system using File Manager, as described in Chapter 4.
‹ Backup data into proNAS system using proBackup, as described in Chapter 5.
IMPORTANT: If you use the RAID Manager GUI via web browser or
the LCD front panel buttons to create a Raid Set/Volume Set, and
use the Quick Setup function, you need to re-map the host channel
mapping from “0&1” to “0”. Quick Setup in RAID Manager will map
a Volume Set to both Host Channels 0 and 1 (0&1). To re-map the
Volume Set, use “Modify Volume Set” function in RAID Manager.
Mapping Volume Set to Host Channel 0 only can avoid some
problem when Volume Set is used by the NAS system.
Configuration Guide
9
ProNAS 1.1.x
Chapter 2 NAS Device Manager
NOTE: If the proNAS system model is DN-503AH, DN-503AH-PDC,
SN-1403AH, SN-1403AH-PDC, SN-2803H, SN-2803H4, SN-2803HPDC, SN-2803H-DX, SN-2803H-QX, SN-2123H, SN-2123H-DX, SN2123H-QX, SN-3163H, SN-3163H-DX, or SN-3163H-QX, refer to
this chapter of NAS Device Manager to configure the RAID
controller.
2.1
Using NAS Device Manager
1. Login as “admin” to proNAS administration page. Select NAS Device Manager
in the left tree node.
2. Login NAS Device Manager and enter Account as “admin”. Use default
password “proware”, or use new password if password has been changed. The
“admin” account
has full privilege
and can setup and
modify all
configuration of
Hardware RAID.
3. Click “Mount Subsystem” to
setup RAID Subsystem. The
“Mount Subsystem” window will
appear.
10
Configuration Guide
ProNAS 1.1.x
There are two Connection Types that can be used for mounting the RAID
subsystem.
‹ RS232: RS232 serial cable must be connected from Monitor Port to COM1
port of the NAS system. The setting of Port is “/dev/ttyS0” which is COM1.
The speed of Baud Rate is same as controller’s setting.
‹ R-Link: R-Link port must be connected to network hub or switch via
Ethernet cable. R-Link supports RAID management and configuration
through web-based GUI and allows users to remotely manage their
storage over their network.
4. Type the RAID subsystem name.
NOTE: The RAID subsystem name is used for identifying the
mounted subsystem in the Subsystem Name list.
5. Change the Subsystem Password if RAID subsystem password is different
from default password.
6. Select the Connection Type. If Connection
Type is “RS232”, verify that the Port is set to
“/dev/ttyS0” and Baud Rate is the same as
controller’s setting (usually set to 115200).
If Connection Type is “R-Link”, enter the RLink IP Address in the designated box.
7. Click “OK”.
8. The RAID
subsystem
name will
appear under
the NAS Device
Manager.
Configuration Guide
11
ProNAS 1.1.x
2.2
Quick Setup
The Quick Setup button provides user with a step-by-step process to create a single
Raid Set and single Volume Set needed to setup the proNAS Volume Group.
NOTE: Quick Setup can only be used if there is no existing Raid Set
(no Raid Set has been created yet.)
To use Quick Setup:
1. Select Storage Manager in the left tree node and click “Quick Setup” button.
2. Choose the number of disks to join in the Raid Set. If not all disks are selected to
be included in the Raid Set, the unselected disk(s) will be set as Hot Spare disk(s)
automatically.
12
Configuration Guide
ProNAS 1.1.x
3. Select the RAID Level. You can select and enable “Background Init” option which
will initialize the Raid Set in background mode. In background mode, the Raid Set
and Volume Set will be accessible immediately during initialization. In foreground
mode (when “Background Init” option is unselected), the Raid Set and Volume
Set will be available only after the initialization is completed. Press the OK button
to start the initialization.
4. Double-click Storage Manager then select “Raid Set #00” to view the RAID Set
status.
NOTE: When the Volume Set Status shows “Ready”, the proNAS
should be restarted in order for the NAS system to detect the
Volume Set as New Disk. Select System Manager under proNAS,
then click Reboot tab then click “Reboot Now” button. Re-login to
NAS administration page after reboot.
Configuration Guide
13
ProNAS 1.1.x
2.3
Create Raid Set and Volume Set
An alternate to “Quick Setup” option is to use the “Create RS” function which will allow
user to create customized Raid Set(s). “Create RS” function can also be used to create
another Raid Set when there is already an existing Raid Set and “Quick Setup” function
can no longer be used.
1. Click Storage
Manager to create
new Raid Set.
2. Click “Create RS” button. A new window will be displayed where the Raid Set
name can be entered and Raid Set disk members can be selected. Choose the
disk drives to be included in the Raid Set by checking the option box of the disk
drives. Click “OK” when done.
NOTE: A Raid Set is a group of disk drives where Volume Sets can
be created. The RAID Level can be assigned when Volume Set is
created.
14
Configuration Guide
ProNAS 1.1.x
3. A “+” sign will appear on the left side of Storage Manager. Click on the “+” sign to
see the Raid Set(s) under Storage Manager. Select the Raid Set where Volume
Set will be created then click “Create VS”.
NOTE: The Volume Set will appear to the NAS system as a SCSI
disk device (/dev/sda, for example) which can be joined to
proNAS Volume Group.
4. Change the Volume Set name if needed. Then select the RAID Level.
Configuration Guide
15
ProNAS 1.1.x
5. Set the Capacity if needed. By default, all the Raid
Set raw capacity will be made available to the
Volume Set.
6. Set the Stripe Size if needed. The default value is 64.
7. By default, Max Speed of Volume Set is set to 320
MB/Sec. Max Speed is used to change Volume Set
SCSI Speed to adapt to the speed of SCSI HBA. In
most cases, there is no need to change the Max
Speed setting.
8. Set the SCSI Channel option to “0” for Channel 0, if
16
Configuration Guide
ProNAS 1.1.x
not set as “0”, in order for the NAS system to detect the Volume Set.
9. Set the SCSI ID and SCSI LUN number if needed. By
default, SCSI ID is set to “0” and SCSI LUN is also
“0”.
10. Other options that can be set are: Background Init, Support Over 2TB (Linux),
Write Cache, and Tagged Command Queuing.
NOTE: When Background Init is enabled, the Volume Set will be
instantly available and accessible during initialization. Otherwise,
Foreground Init mode will be used which will allow access to
Volume Set only after initialization has been completed.
Support Over 2TB (Linux) option allows creation of a Volume Set
over 2TB.
11. Click “OK” when done.
12. The Volume Set will start to initialize.
Configuration Guide
17
ProNAS 1.1.x
Volume Set Status will show “Initializing _%” in Foreground Init mode.
Volume Set Status will show “Ready” in Background Init mode while Volume Set
is initializing in the background.
NOTE: When the Volume Set Status shows “Ready”, the proNAS
should be restarted in order for the NAS system to detect the
Volume Set as New Disk. Select System Manager under proNAS,
then click Reboot tab then click “Reboot Now” button. Re-login to
NAS administration page after reboot.
18
Configuration Guide
ProNAS 1.1.x
2.4
Delete Raid Set
The Raid Set can be deleted whenever necessary.
1. Move to Storage Manager and select the Raid Set you would like to delete. The
selected Raid Set will be highlighted.
2. Click the “Delete RS” button. System will display warning message. Click “OK” if
you are sure to delete the Raid Set, otherwise click “Cancel”.
WARNING! If you use “Delete RS”, all the data of the Volume Set(s)
under the Raid Set will also be deleted. Be careful when using this
function.
Configuration Guide
19
ProNAS 1.1.x
2.5
Delete Volume Set
The Volume Set under a Raid Set can be deleted if necessary.
1. Select a Raid Set under Storage Manager then choose the Volume Set you would
like to delete.
2. Click the “Delete VS” button. Select “OK” to proceed, or click “Cancel” to abort.
WARNING! If you delete the Volume Set, all the data under the
Volume Set will be deleted. Be careful when using his function.
20
Configuration Guide
ProNAS 1.1.x
2.6
Check Volume Set
Check Volume Set is used to verify and, if necessary, correct parity information in the
Volume Set. The Volume Set must be in “Ready” Status in order for Check Volume Set
function to work. Use this function only when needed and when there is no I/O to the
NAS system.
1. Select a Raid Set under Storage Manager and choose the Volume Set you would
like to check.
2. Click “Check VS”. The system will begin to check the Volume Set.
NOTE: Check Volume Set process can be aborted manually by
clicking “Stop Check”.
NOTE: Some RAID Levels does not support Check Volume Set
function, such as RAID 0 or RAID 1.
Configuration Guide
21
ProNAS 1.1.x
2.7
Modify Volume Set
Modify Volume Set function is used to change Volume Set attributes. The Volume Set
Status must be “Ready”.
1. Select a Raid Set under Storage Manager and choose the Volume Set you would
like to modify.
2. Click the “Modify VS” button.
3. The Volume Set attributes that can be changed are: Volume Set Name, Volume
Set Max Speed, Volume Set SCSI Host Mapping (SCSI ID and SCSI LUN), Write
Cache, and Tagged Command Queuing.
WARNING! Changing the “SCSI Channel” setting can make the
Volume Set undetectable by the NAS system. In most cases, it is
not necessary to change SCSI Channel setting.
4. Click “OK” to save changes.
22
Configuration Guide
ProNAS 1.1.x
2.8
Expanding Raid Set
Expanding a Raid Set means adding more disk drive members to the Raid Set which
gives additional free raw capacity and allows the creation of more Volume Sets. The
Raid Set to be expanded must be in “Ready” status to be able to be expanded. One or
more “Free” disks must be available. Check the Slot List for the list of “Free” disks. The
capacity size of the disk(s) that will be added to the Raid Set must be equal to or
larger than the smallest disk member of the Raid Set.
1. Select a Raid Set under Storage Manager the click “Expand RS”.
2. Select the disk(s) that will be added to the Raid Set. Click “OK” to begin
expansion.
Configuration Guide
23
ProNAS 1.1.x
3. The Volume Set will be in “Migrating” status during expansion.
4. After migration is completed, the Volume Set Status will change to “Ready”. Verify
that the new hard disk(s) is/are joined to the Raid Set.
5. A new Volume Set can be created under the Raid Set that was expanded. The
new Volume Set can then be joined to the proNAS Volume Group to expand the
Volume Group’s capacity.
24
Configuration Guide
ProNAS 1.1.x
Chapter 3 proNAS Manager
proNAS supports Multi-Node Management. If you have several NAS subsystems
connected to the intranet, you can see all these systems when you login to the proNAS
system. The IP Address section lists the NAS systems connected to the network.
proNAS Multi-Node Technology is based on UDP Multi-Casting technology. The proNAS
managers are listed below.
The proNAS managers are:
1. Volume Manager
2. Network Manager
3. Account Manager
4. Share Manager
5. System Manager
6. Backup Manager
7. Log Manager
8. Event Manager
Configuration Guide
25
ProNAS 1.1.x
3.1
Volume Manager
The Volume Manager is responsible for disk and volume management.
A Volume Group consists of one or more disks that could be individual physical disk(s)
or RAID disk(s), which is/are Volume(s) created using proRAID Manager. The default
proNAS Volume Group (proNASVG) must be created first by joining at least one “New”
or “Non_Initialized” disk to this volume group. The proNASVG holds the NAS system
configuration and the default system Logical Volumes, such as home, public,
proBackup Device, and proBackup Extended Device, as well as user-defined Logical
Volumes. Files and folders reside on these Logical Volumes.
The default proNASVG Volume Group cannot be deleted. When proNASVG is created,
the XFS file system is set in each default Logical Volume. XFS file system is also set in
all user-defined Logical Volumes. XFS is a high performance journaling file system and
provides better recovery time to repair a file system in case of FS damage. The proNAS
Volume Group will dynamically allocate some space from its assigned disks, and
allocation may fail if no more disk space is available. Therefore, make sure to regularly
monitor the available free space of proNAS Volume Group.
The
‹
‹
‹
‹
‹
‹
‹
Volume Manager can perform the following function:
Create a VG (volume group)
Join New Disks
Reset a VG (volume group)
Remove a VG (volume group)
Create Logical Volume
Create Snapshot
Create Replication
26
Configuration Guide
ProNAS 1.1.x
3.1.1 Volume Group Management
Volume Group (VG) is created by joining at least one disk, which can be physical disk
or RAID disk (volume created in RAID controller). Logical Volumes are created under
the Volume Group.
proNASVG is the system default VG. It must be created first in order to use the NAS
system. To create the proNASVG, it is necessary to join at least one “New” or
“Non_Initialized” disk into proNASVG.
Admin can create other VG by joining other new or “Non_Initialized” disk, create or
remove LV in this VG, join any new disk, remove any disk and reset the VG.
NOTE: The default VG proNASVG cannot be deleted or reset.
NOTE: If the Disk List in Volume Manager does not show any RAID
disk (for example: /dev/sda) but a Raid Set or Array and Volume
Set or Volume has already been created, it is necessary to restart
the proNAS system. Go to System Manager, select Reboot tab, and
click Reboot Now button. Then re-login to NAS administration page.
3.1.1.1 Initialize the default Volume Group proNASVG
To initialize the proNASVG, perform the following steps:
1. In the proFamily tree, select Volume Manager. Verify that the Disk List shows at
least one disk and the Status is “Non_Initialized’. Noticed in the Volume Group
List that the proNASVG has no Disk List.
2. Select proNASVG under Volume Manager and click “Join New Disk” button.
Configuration Guide
27
ProNAS 1.1.x
3. Select the Disk(s) that will be joined to proNASVG from the list of Available
Disk(s). The default Unit Size of proNASVG is 512MB. If needed, the Unit Size can
also be changed. Click “OK” when done.
NOTE: Unit Size is the Physical Extent or block size used in the
Volume Group.
4. A confirmation message will appear. Select “Yes” to proceed.
28
Configuration Guide
ProNAS 1.1.x
5. Another confirmation message will appear. Select “”Yes” to proceed.
6. The process of joining disk to the VG will start.
7. When the process of joining disk to VG is
completed, the NAS will reboot to free some
used system memory. A warning message will
be displayed. Click “OK” to close the message.
8. Re-login to proNAS
management GUI.
The Volume
Manager will show
the joined disk as
“IN_USED” and the
Volume List will
show the system
default Logical
Volumes “home”
and “public”.
NOTE: The other system default LVs proBackup Device and
proBackup Extended Device will only be created and become
visible in the Volume List when the proBackup Service is started.
3.1.1.2 Create another Volume Group
To create another VG, verify from Volume Manager Disk List if there is available free or
Configuration Guide
29
ProNAS 1.1.x
“Non_Initialized” disk. If there is none, a new Volume (RAID disk) must be created first
using proRAID Manager. If a new Volume has already been created, the NAS system
must be restarted in order to detect the new RAID disk. To restart the NAS, select
System Manager under proNAS, then click Reboot tab then click “Reboot Now” button.
Re-login to NAS administration page after reboot.
To create another VG, perform the following steps:
1. In Volume Manager, click “Create VG” button.
2. Enter the Volume Group Name. Click “Save” when done.
3. A confirmation message will appear. Select “Yes” to proceed.
30
Configuration Guide
ProNAS 1.1.x
4. Click “Join New Disk” to continue with creating the new Volume Group.
5. Check the disk(s) to be joined to the VG. Click “OK” when done.
6. A confirmation message will appear. Select “Yes” to proceed.
Configuration Guide
31
ProNAS 1.1.x
7. A process window will appear.
8. When the process of joining disk to the new VG is completed, the newly created
VG will be shown.
NOTE: The new VG has no default Logical Volumes. Admin can
create new Logical Volumes.
32
Configuration Guide
ProNAS 1.1.x
3.1.1.3 Reset and Remove Volume Group
If you choose to reset the Volume Group, all the data will be erased. Use the “Reset
Volume Group” function only when necessary, and when the data from the VG have
been backed up or you do not want to keep the data.
1. Select “Reset Volume Group” button.
2. Select “Yes” to confirm.
Configuration Guide
33
ProNAS 1.1.x
3. Click “Remove”.
4. Select “Yes” from the confirmation message.
5. Verify from Volume Group List in Volume Manager that the VG has been removed.
NOTE: The default VG proNASVG cannot be deleted or reset. But
other VGs can be deleted or reset.
34
Configuration Guide
ProNAS 1.1.x
3.1.2 Logical Volume Configuration
3.1.2.1 Create new Logical Volume
To create a new Logical Volume, follow these steps:
1. Double-click on a VG name. Click “Create New Volume” button.
2. The LV Configuration tab will be displayed. Enter the Logical Volume name and
the volume size (in MB). You can also enable the “Send email when not enough
space” option to send an email notification to email recipients specified in Event
Manager if the remaining free volume size is smaller than the size entered in this
option. Click “Save” when done.
Configuration Guide
35
ProNAS 1.1.x
3. Select “Yes” from the confirmation message to create the LV.
4. A process window will be shown.
5. The new Logical Volume will be shown.
36
Configuration Guide
ProNAS 1.1.x
3.1.2.2 Extending Logical Volume Size
When the Logical Volume free space gets smaller and smaller, the Logical Volume size
can be extended to allow more space for storing data. To extend the LV size, follow these
steps:
1. Select the LV that will be extended then click “Extend LV Size” button.
2. Enter in the “Extend size” box the additional size to be used for extension. Verify
from the Free Volume Group Size (MB) the allowable size to be used in extension.
3. The Logical Volume will be extended.
Configuration Guide
37
ProNAS 1.1.x
4. Verify the new LV size.
38
Configuration Guide
ProNAS 1.1.x
3.1.3 Volume Snapshot
Snapshots are point-in-time copies of a logical volume. This allows the system
administrator to create a new block device which presents an exact copy of a logical
volume, frozen at some point in time. As changes are made to the original volume, the
snapshot remains the same and looks exactly like the original at the time the snapshot
was created.
A Snapshot can be created manually or scheduled. Admin need to enable first this
special function.
NOTE: Logical Volume with snapshot cannot be extended nor
replicated (see next section about Volume Replication).
To enable Snapshot function, select Volume Manager then click Options tab. Tick the
“Enable Snapshot function” option.
NOTE: Creating Snapshots while a Logical Volume is under heavy
I/O will slowdown the I/O access or interrupt the I/O process to a
Logical Volume. This means that clients accessing the proNAS
share, in which the Logical Volume is under snapshots, can
experience slow write access.
Configuration Guide
39
ProNAS 1.1.x
3.1.3.1 Create Snapshots Manually
To manually create snapshots:
1. Select the Logical Volume, go to Snapshot tab and click “Create Snapshot”.
2. A confirmation message will appear. Select “Yes”.
3. The Snapshot configuration
window will be displayed. A
system-created Snapshot name
is automatically created. The
default snapshot name can be
renamed if needed. Enter the
new Snapshot Size (in MB) if the
size shown need to be changed.
See details about Snapshot
Options below. Click “Create
Snapshots” to start creating
snapshot.
40
Configuration Guide
ProNAS 1.1.x
Snapshot Options:
‹ Snapshot Name: The default snapshot name is created by appending the date
and time to the volume name. You can modify the snapshot name but the prefix
volume name will still remain.
‹ Size (MB): This indicates the size of the snapshot volume that will be created.
The default is 10% of the size of the logical volume where snapshot is to be taken.
The size of the snapshot volume will be multiple of the PE size.
‹ Origin LV Size: This indicates the size of the Logical Volume where the new
snapshot volume will be created.
‹ Free Volume Group Size (MB): This indicates the amount of free space on the
volume group where the new snapshot volume will be created.
‹ Mount: When checked, the created snapshot volume will be automatically
mounted. When a snapshot volume is mounted, the existing share from the
snapshot volume will be accessible. Note that a snapshot volume is a read-only
volume.
‹ ID: This specifies the shares created under this logical volume.
‹ Snapshot share name: This specifies the name of the snapshot shares. Your
may access these shares by mounting the snapshot volume. The naming format
used is: the last two digit of the year, followed by the month/date, and then
followed by the hour/min/sec. For example: "060123_171516".
4. A process window will be displayed.
5. When snapshot
has been created,
it will be shown in
the Snapshot List
of the Logical
Volume.
Configuration Guide
41
ProNAS 1.1.x
3.1.3.2 Create Snapshots Based from Schedule
To create scheduled snapshots:
1. Select the Logical Volume, go to Snapshot tab and click “Edit”.
2. Edit the following snapshot options listed below then click “Save” when done.
42
Configuration Guide
ProNAS 1.1.x
Snapshot Options:
‹ Snapshot Numbers: Specifies the total number of snapshots that will be created.
‹ Snap Ratio (%): This is the ratio in percentage between the snapshot volume
and the volume of origin. This indicates the ratio of the volume size that will be
set as the size of the snapshot volume. For example, if your logical volume is 1GB
and the Snap Ratio is 10%, the size of the snapshot volume that will be created is
128MB, assuming that your PE size is 128MB and below. The snapshot volume
size will always be a multiple of PE size and the smallest snapshot size is equal to
the PE size.
‹ Overwrite: Selecting this option will automatically delete the oldest snapshot if
the total number of snapshots is already exceeded.
‹ Mount: When checked, it means that the created scheduled snapshot will be
automatically mounted.
‹ Reserved/VG Free Size (MB): The left side indicates the total volume space
that will be used for the creation the snapshots. The right side indicates the free
space of the volume group available for use.
‹ Execute Day: Specifies whether the scheduled task is to run on the selected
day(s).
‹ Execute time:
Once - Specifies the time of the day when the scheduled task will be taken.
Every - Specifies how often the scheduled task is to be repeated. You can
also select the starting time and the ending time.
‹ Snapshot Lists:
Mount - Allows you to mount the snapshot volume. All snapshot volumes will
be mounted read-only. By mounting the snapshot volume, the files under this
snapshot volume will become accessible.
Name - This specifies the name of the snapshot volume. If the snapshots are
created by schedule, proNAS will automatically create the snapshot name. The
format that will be used is: the last two digit of the year, followed by the
month/date, and then followed by the hour/min/sec. For example:
"060123_171516".
Date - This indicates the date and time when the snapshot was created.
Used Size - This indicates the space used by the snapshot data. The right
side is the size of the snapshot volume. If the used space nearly exceeds the
snapshot volume capacity, it will be set as "Invalid" and will be un-mounted
automatically to keep the system consistent.
Configuration Guide
43
ProNAS 1.1.x
3. A confirm message window will be displayed. Select “Yes” to proceed.
4. An “Updating Volume Setting” message will be shown.
5. When the snapshot setting of LV has been set, click “Enable Scheduled” to active
scheduled snapshot.
44
Configuration Guide
ProNAS 1.1.x
6. A clock-like icon will appear on the left side of the LV which means a scheduled
snapshot is active. To disable the schedule, click “Disable Scheduled”.
7. After disabling the schedule, the “Enable Scheduled” button will become available.
Configuration Guide
45
ProNAS 1.1.x
3.1.3.3 Delete Snapshots
1. Select the Logical
Volume where
snapshot will be
deleted, then go to
Snapshot tab. Click
the snapshot that
will be deleted then
click “Delete
Snapshot”.
2. Select “Yes” to delete the snapshot.
3. A process window will be shown.
4. The deleted
snapshot will no
longer exist in the
Snapshot List.
46
Configuration Guide
ProNAS 1.1.x
3.1.4 Volume Replication
Replication function enables proNAS to replicate a logical volume from one NAS server
(source) into another NAS server (destination). Replication involves intelligent copying
and maintaining of exact copy of a volume from a source server to a destination server.
The destination volume is always an exact copy of the source volume. This is done by
mirroring the whole block device via a standard network interface. This solution
creates a real time replication of data. However, it does not create a cluster solution
where you can have a highly available system.
Note: Logical Volume under snapshot cannot be replicated.
To enable Replication, select Volume Manager then click Options tab and tick “Enable
Replication function”.
Note: Make sure the two proNAS servers have different host
names before setting up Replication.
Configuration Guide
47
ProNAS 1.1.x
3.1.4.1 Replication Configuration
To setup Replication between two NAS servers:
1. Admin need to login to the administration page of the two NAS servers.
2. On the primary NAS (source), select the Logical Volume which will be replicated,
then click “Create Replication”.
NOTE: The logical volume to be replicated from source proNAS
must not exist in the destination proNAS. If the destination
proNAS has the same logical volume, replication cannot be setup.
48
Configuration Guide
ProNAS 1.1.x
3. The Create Replication window will be displayed. Set the options below and click
“OK” when done.
Replication Options:
[Remote]
‹ Local - Select the IP address of the local (source) proNAS that will be used for
replication.
‹ Remote - Select or type manually the IP address of remote (destination) proNAS
that will be used for replication.
NOTE: The local and remote IP addresses serve as the channel
between the source and destination NAS servers. This is where the
replication of data takes place. Please be sure to have a good
connection on this medium. As much as possible, set this channel
as a dedicated or a private network. It is recommended to use
different Ethernet port for replication from the Ethernet port used
for data access. It is best to use a crossover network link between
the Ethernet ports involved. Refer to Network Manager Section for
configuring Ethernet port.
‹ Remote VG - Select the VG on remote proNAS where the replicated logical volume
will be created.
Configuration Guide
49
ProNAS 1.1.x
[Setting]
‹
Port to Bind - A TCP port to bind locally and is used to connect to the remote node.
Default is 7788.
NOTE: User cannot use ports that already have been used.
Available ports are from 7788 to 77xx.
‹
Connection Type: proNAS supports two types of data replication protocols:
Sync - Synchronous. The system will acknowledge the transaction as completed
after the data is written to the disk of destination proNAS. It is recommended to
use this mode. In most cases, this connection type preserves transaction
semantics. Write IO is reported as completed if it has reached the remote disk.
Async (for high latency network) - Asynchronous. The system will acknowledge
the transaction as completed after the data is written to buffer. It provides faster
transmission and is suitable for busy network. Write IO is reported as completed
if it has reached the local TCP send buffer.
‹
Max Sync Rate – This sets the limit of the bandwidth that will be used by the
synchronization process. Default is 30MB/sec. Minimum value is 4MB/sec and
maximum value is 680 MB/sec – for high latency network environment (e.g.
bonding on Gigabit Ethernet).
‹
Send buffer size (K) - It is the size of the TCP socket send buffer. You can specify
smaller or larger values. Larger values are appropriate for reasonable write
throughput with asynchronous protocol over high latency networks. Default is 512K
and maximum is 1024K.
‹
Time out (sec) - It is the value to wait for connection timeout if the remote node
is degraded. If the remote node fails to send the response packet within the
specified timeout time, the remote node will be considered dead and the TCP/IP
connection is abandoned. The default is 6 sec. Minimum is 1 sec and maximum is
60 sec.
‹
When Lost Connection: When the replication connection is lost, the replication
program can either go stand-alone or will try to reconnect.
Reconnect: The replication program will attempt to reconnect. (Default)
Stand-alone: The replication program will not attempt to reconnect and will go
on stand-alone state. All IO request are only passed locally and no replication.
NOTE: Before replication will be successfully created, a 4GB logical
volume will be created on each node. This will serve as the
metadata device for the replicated volume. This volume is not
mounted and will not be seen on the proNAS GUI. Please be sure
to have an extra 4GB space on either side of your NAS nodes.
50
Configuration Guide
ProNAS 1.1.x
4. A message box will be displayed.
5. Initialize the Replication by clicking “Initial Replication” button.
NOTE: After creating a replication, a similar logical volume will be
created on the destination server under the specified VG. At this
point, the replication is not yet initialized and no synchronization.
Replication still needs to be initialized. After selecting “Initial
Replication” button, the first node will then connect to the second
node and starts to synchronize. Synchronization typically takes
quite a while especially on larger logical volumes. After initializing,
the source node should be in "Primary" state and the destination
node should be in "Secondary" state. If this is the state, you have
now a working replication. Initializing should be done in the
source volume.
Configuration Guide
51
ProNAS 1.1.x
6. The volume replication setting will be initialized.
7. The volume replication synchronization process will start.
8. After the initial synchronization process is completed, the Status will show
“Primary/Secondary Consistent”.
52
Configuration Guide
ProNAS 1.1.x
3.1.4.2 Checking the Status of your Replication
Primary: The source volume. All the writing and reading are done on the primary
node.
Secondary: The destination volume. The replicated data on the secondary node is
used for backup only and is not accessible. Only the source data is accessible
during replication.
Unknown: The peer node fails to establish connection.
Setting the replicated volume on destination proNAS to be primary
To set the replicated volume to primary, first you need to set both nodes to
secondary. This can be done by setting the primary to be secondary. After both
nodes becomes secondary/secondary, go to the management GUI of the
destination node. Under the replicated logical volume, press the "Set Primary"
button.
WARNING! The replicated volume on the secondary node must not
be mounted. Please do not attempt to mount it manually.
Setting the primary volume to be secondary
To set the primary volume to be secondary, just press the "Set Secondary"
button on the primary node.
Forcing the synchronization
To manually force the synchronization, press the "Force Sync." button. The data
on the primary node will be forcefully synchronized to the secondary node.
Reconnect when the connection of the peer is lost.
To reconnect the replicated volume, press the "Reconnect" button. At some point
if the replication fails to establish connection to the other node, you may try to
set up a connection thru this button. This button will be enabled only if one of the
node losses connection.
Aborting the replication
To abort or drop the replication, press the "Abort Replication" button. To access
the data on the replicated volume after aborting the replication, you may need to
create a share under destination volume whose share name must be equal to the
share name on the source proNAS.
Configuration Guide
53
ProNAS 1.1.x
3.1.4.3 Extending Logical Volume under Replication
NOTE: Extending the size of a Logical Volume under replication is
not allowed. However, there is a work around to extend the LV size.
The following are the steps:
1. Abort the replication by selecting “Abort Replication”.
2. Remove or delete the replicated logical volume on the destination proNAS.
3. Extend the capacity of the source logical volume. Please note that there should
be enough space on the logical volume of the destination proNAS to
accommodate the extended logical volume space.
4. Create a new replication using the extended source logical volume.
54
Configuration Guide
ProNAS 1.1.x
3.1.5
iSCSI
The iSCSI function in proNAS makes a logical volume become an iSCSI target LUN.
Note: You can’t enable iSCSI function in a Logical Volume if
Snapshot or Replication exists.
To enable iSCSI
function, select Volume
Manager then click
Options tab and tick
“Enable iSCSI”.
3.1.5.1 iSCSI Configuration
To configure iSCSI:
1. Select the logical
volume and click
the iSCSI tab.
Configuration Guide
55
ProNAS 1.1.x
2. Click “Edit” and tick
the “Enable iSCSI”
option.
3. Enter the target
name. If you want
to enable CHAP
authentication,
check the “Enable
Auth (CHAP)” option
and enter the
account and
password.
4. Click “Save” when
done.
56
Configuration Guide
ProNAS 1.1.x
5. A message box will be
displayed. Select “Yes”
to continue.
6. A progress box will be displayed.
7. The iSCSI volume
is ready. Note that
there is an “i” icon
on the left of
logical volume
name to denote
that this is an
iSCSI volume.
8. You may now connect to the iSCSI target LUN using iSCSI initiator.
Configuration Guide
57
ProNAS 1.1.x
3.1.5.2 Disable iSCSI in Logical Volume
To disable iSCSI:
1. Select the logical volume and click the iSCSI tab.
2. Click “Edit” and
remove the check
mark in “Enable
iSCSI” option.
Click “Save” when
done.
3. A confirm message box will be
displayed. Select “Yes” to proceed.
4. The iSCSI
function in the
logical volume is
disabled.
58
Configuration Guide
ProNAS 1.1.x
3.1.5.3 Restore iSCSI to Ordinary Logical Volume
The iSCSI volume can be restored back to normal logical volume and remove the iSCSI
function. The existing data in the logical volume will be deleted; so if there are important
data in the logical volume, a backup must be made.
To restore iSCSI to normal volume:
1. Select the logical volume and click the iSCSI tab. Select the “Restore to Volume”
button.
2. When a warning message is displayed, select “Yes” to proceed.
3. When a confirm message is displayed, select “Yes”.
Configuration Guide
59
ProNAS 1.1.x
4. A process window will show that the volume is being restored back to normal
logical volume.
5. The logical volume is restored to normal volume. Note that the “i” icon on the left
of logical volume name has been removed.
60
Configuration Guide
ProNAS 1.1.x
3.2 Network Manager
Using the Network Manager, you can configure the NAS network settings. There are
three tabs in Network Manager: Network, Internet Gateway, and SNMP.
3.2.1 Network Setting and Trunking
There are two sections in the Network tab, the General Setting section and the
Network Adapter section.
The Network tab
Press “Edit” button to configure the Network settings and click “Save” button to update
new settings.
General Setting:
‹
‹
Host Name - The NetBIOS name of proNAS, it should be unique.
Domain/Workgroup - Windows domain name or workgroup. Domain name is
limited only up to 15 characters. For example: MYDOMAIN
‹ DNS Suffix – The DNS suffix appended to server name to complete the server’s
FQDN. This includes the domain name, for example: MYDOMAIN.LOCAL
‹ DNS Server - DNS server is responsible for mapping machine name and IP
Address.
‹ WINS Server - WINS Server is responsible for the setting NetBIOS name
resolution.
Edit DNS Table: If you have not set the DNS, you can use this button to edit DNS in
the DNS table. This is optional.
Edit Lmhost Table: You can use this option to define the resolution of NetBIOS in
the Lmhosts table. This is optional.
Configuration Guide
61
ProNAS 1.1.x
Network Adapter:
The Network Adapter section consists of the Adapter List and the Configuration section.
The Adapter List is the list of available Ethernet ports in the system. The number of
ports might be two or three depending on different models.
Adapter List: Lists the available Ethernet adapters.
Configuration:
‹
Use Dynamic IP Configuration (BOOTP/DHCP) - If checked, this specifies
that this network connection will dynamically obtain an IP address from a
Dynamic Host Configuration Protocol (DHCP) server or from a Bootstrap Protocol
(BOOTP) server.
‹
Enable this adapter on boot – If enabled, this adapter will be active when
proNAS starts up.
‹
Enable default gateway on this adapter - If checked, the default gateway will
be enabled in this adapter. A default gateway is a local IP router that is used to
forward packets to destination beyond the local network. Only one default
gateway can be enabled in a certain time.
‹
Device - Displays the type of Network Interface Card.
‹
IP address – Shows the current IP address. To edit IP address, enter the new IP
address.
‹
Gateway – Shows the current gateway IP address. To edit, type in a new
gateway IP address.
‹
Subnet mask – Shows the current subnet mask setting. To edit, type in the new
subnet mask number.
‹
MTU – The MTU size (Maximum Transmission Unit) in bytes. To modify the MTU
size for this interface, enter the new MTU size.
Network Trunking
proNAS provides the network trunking/bonding function. Ethernet bonding refers to
aggregating multiple Ethernet channels together to form a single channel.
NOTE: It is necessary that the network switch supports the type of
trunking mode that will be used. Otherwise, the network
connections may be unstable.
62
Configuration Guide
ProNAS 1.1.x
To create a trunk adapter:
2. Click on the "Edit" button. Press the “Ctrl” key then at the same time select the
adapters that will be included in the network trunking then click on "Trunk
Adapter" button.
3. A warning message will be displayed. Click “OK” to proceed.
4. Setup the network settings. Select the Team Mode to use. Click “Create” when
done.
Configuration Guide
63
ProNAS 1.1.x
The Team Mode defines the type of operation for the bonded ports.
Team Mode options:
‹
‹
‹
‹
Fault Tolerant (Active_ Backup) - Active_Backup policy: If the active
Ethernet port fails, the standby Ethernet port will become active. This
enhances the availability of access to the NAS.
Load balance and Fault Tolerant (XOR) - XOR policy: Transmit based on
source MAC address XOR with destination MAC address. This selects the same
slave for each destination MAC address. This mode provides load balance and
fault tolerance.
Link Aggregation (802.3ad) - 802.3ad policy: Combines multiple physical
network links into a single logical link for increased performance. Transmits
and receives on all slaves in the active aggregator. Pre-requisite: the network
switch must support IEEE 802.3ad.
Load Balance (ALB) - ALB (Adaptive load balancing) policy: The receive load
balancing is achieved by ARP negotiation and does not require special switch
support.
5. Connect to proNAS using the new IP address used in network trunking.
3.2.2 Internet Gateway
proNAS provides Internet gateway function which enables proNAS to act as an Internet
Gateway, integrating DHCP service, routing and NAT. Using Internet gateway function,
administrators can easily enable and disable the Internet access for network users.
To configure Internet Gateway, press “Edit” button.
64
Configuration Guide
ProNAS 1.1.x
Configuration options:
‹ DHCP's IP range starting from - means the lower bound (starting) range of
private IP addresses for DHCP
‹ DHCP's IP range ending with - means the upper bound (ending) range of
private IP addresses for DHCP
‹ Private Net Adapter - means the port connected to private network. This port
has to be a Static port and could also be a Trunk port.
‹ WAN Adapter: means the port connected to WAN or Internet. This port could be
a Trunk port.
NOTE: When using Internet Gateway function, make sure the
Internet Gateway service is enabled in the Service tab of System
Manager.
3.2.3 SNMP/MRTG
The SNMP/MRTG service can be enabled to monitor proNAS network traffic. Select
Service tab of System Manager then enable SNMP/MRTG service. Click “Start” to
enable the service.
Configuration Guide
65
ProNAS 1.1.x
To view the SNMP/MRTG network traffic information, select the SNMP tab in Network
Manager.
For more information about MRTG service, please visit http://www.mrtg.org.
66
Configuration Guide
ProNAS 1.1.x
3.3 Account Manager
With Account Manager, the administrator can manage and administer local accounts as
well as import external domain accounts. proNAS will utilize external directory services
to do account authentications which currently supports ADS/PDC and NIS.
The
‹
‹
‹
main functions of the Account Manager are:
Authentication
User Account
Group Management
3.3.1 External Accounts Integration (Joining Windows or NIS Domain)
You can utilize external directory services to authenticate accounts. Currently,
PDC/ADS and NIS authentication are supported. You may choose any one of them or
both at the same time depending on your network environment.
3.3.1.1 Windows Authentication
If you would like to integrate proNAS with Windows environment, please select “Edit”
button then check "Enable Domain authentication". Set the necessary Windows options
then click “Save” to update settings.
NOTE: Hostname, Domain name and DNS Suffix need to be set first
in Network Manager.
Configuration Guide
67
ProNAS 1.1.x
Windows options:
‹
Automatic detect Domain IP – This is enabled by default. When enabled,
proNAS will try to automatically detect the domain server’s IP address.
‹
Hostname - Indicates the NetBIOS name of proNAS; must be set in Network
Manager.
‹
Domain/Workgroup - Windows Domain name; must be specified in Network
Manager.
‹
DNS Suffix - The DNS suffix used; must be set in Network Manager.
‹
Domain Server IP - The IP address of the domain server. proNAS will
automatically acquire the domain server's IP address after setting the Domain
name in Network Manager if “Automatic detect Domain IP” option is enabled.
When “Automatic detect Domain IP” option is disabled, you need to manually
enter the domain server’s IP address.
‹
Logon account (Administrator) – the administrator’s logon name in the
Domain Controller
‹
Password - the administrator's password in the Domain Controller.
‹
PDC/ADS Mode – The type of Domain Controller. Choose PDC for Windows NT
Server or ADS for Windows 2000/2003 Server.
‹
Auto Detect Enctypes – This option automatically detects the encryption type
used in Windows authentication. To manually select the encryption type, disable
this option and select the preferred encryption type from the EncType drop-down
list.
‹
Enable NTLMv2 authentication - This parameter determines whether or not
smbclient will attempt to authenticate itself using the NTLMv2 encrypted
password. If enable, proNAS will only sent NTLMv2 and LMv2 responses. NTLMv2
authentication protocol is available only on WindowsNT4 with SP4 and Windows
2000 or later. Default is disabled.
‹
Enable client schannel - This controls whether the client offers or even
demands the use of the netlogon schannel. Default is auto, means it offers the
schannel but does not enforce it.
3.3.1.2 Sample Steps to Join the NAS to Windows AD Domain:
1. Select Network Manager. In Network Manager –> Network tab, click “Edit” to
configure network settings.
2. Change the default proNAS Host Name if there are other proNAS systems in the
network. Enter the Windows Domain name in “Domain/Workgroup”. For example:
MYDOMAIN
68
Configuration Guide
ProNAS 1.1.x
3. Enter the DNS Suffix.
The DNS suffix is the
name appended to
the server name to
complete the server’s
FQDN. This includes
the domain name.
For example:
MYDOMAIN.LOCAL
4. Enter the DNS
Server and WINS
Server (IP address)
as necessary.
5. Click “Save” to
update changes.
6. Select Account Manager. In Account Manager –> Windows Authentication, click
“Edit”.
7. Tick “Enable Domain Authentication” option.
8. If the Domain Server IP is not detected (not shown), you can manually specify
the Domain Server IP by removing the check mark in “Automatic Detect Domain
IP” and entering the Domain Server IP address.
9. Enter the Domain Administrator Account and Password.
NOTE: No need to
include “domainname\” in Domain
Administrator
Account.
10. Select the Domain
Server mode (PDC or
ADS).
11. If needed, change
the encryption type
to the same type
used by your domain
server.
12. Click “Save”. The
NAS will be joined to
Windows Domain in
a while.
13. To verify, select Account under Account Manager; the user accounts should be
shown. You can also verify group accounts in Group List.
Configuration Guide
69
ProNAS 1.1.x
3.3.1.3 NIS Authentication
If you would like to integrate proNAS with UNIX/Linux environment, please select “NIS
Authentication” tab and click “Edit” button then check "Enable NIS authentication". Set
the necessary configuration options then click “Save” to update settings.
Configuration Options:
‹
‹
NIS Domain - Enter the NIS domain name
NIS server - Enter the IP Address of NIS server.
3.3.1.4 Sample Steps to Join the NAS to NIS Domain:
1. Under Account Manager, select NIS Authentication tab. Click Edit.
2. Check the Enable NIS Authentication option. Enter the NIS Domain name (e.g.:
TESTDOM.LOCAL) and NIS Server IP address or FQDN. Click Save when done.
3. Click Account under Account Manager to verify that the NIS Accounts are listed in
the Account List, or select Group to display the NIS Groups in the Group List.
70
Configuration Guide
ProNAS 1.1.x
3.3.2 Local Account and Group Management
Account Management
The Account List in Account Manager includes Local users and External users, ADS/PDC
or NIS.
In Account menu, admin can perform the following functions:
‹
Create a new Local Account
‹
Enable and Disable an Account
‹
Modify and Delete an Account
‹
Mass Import Accounts
‹
Refresh the Account List
Creating a new Local Account
Following are the steps to create a new Local Account:
1. Select Account Manager in the proFamily tree. Choose Account node under the
Account Manager. It will display all accounts under the Account List tab.
Configuration Guide
71
ProNAS 1.1.x
2. Press the "Create" button. System will display "Account List tab". Account List
tab consist of two tabs, "Properties" and "Permission". In the Properties tab, enter
the necessary information.
General:
‹ Login Name - Input the login name, it should be unique in proNAS
‹ Full Name - the complete name of the account
‹ Directory Service - system will display if the directory service is Local or
ADS/PDC,NIS
‹ Create Date - system will display the create date of the account.
‹ UID - In UNIX or Linux, OS will assign a unique user number called UID to access
the system resource. (UID range is 1 to 65535). proNAS may either assign a new
UID automatically starting from 500 or you can manually specify the UID. Domain
accounts will have a UID starting from 10000-30000.
‹ Quota Size (MB) - This specifies the quota (usable space) of a user for its home
folder. The default is 10MB.
‹ Set it to default value for new account – When this option is enabled and the
Quota Size value has been changed from 10MB to another value, the new value
set in Quota Size will become the new default Quota Size when other accounts
are created.
‹ Set Password – Click this button to set the account's password. Passwords have
to be at least 6 characters.
72
Configuration Guide
ProNAS 1.1.x
Status:
‹ Current status: Displays Enable or Disable.
‹ Used Size (MB): Displays the current used size.
Use the following guidelines to ensure that you are using a valid Account
name:
š
š
š
Account names must start with a small alphabet letter.
š
š
Account names cannot contain blank spaces.
š
š
Account names cannot contain the following characters: /\[]";:|<>+=,?*
Account names cannot be longer than 32 characters.
Account names should be unique. No account names must be the same. No
account names must be the same with share names.
Account names cannot begin with a dash (-) and cannot consist of only a single
dash.
Account names cannot be duplicated with the system default accounts, i.e. root,
mail, news, operator, gopher, nobody, ftp, games, rpc, adm, nobody, etc.
3. After completing the settings, press the "Save" button, or you can go to
"Permission" tab to have a look at the permissions of the account then click
“Save” button when done.
Configuration Guide
73
ProNAS 1.1.x
Permission tab
‹
Joined Groups: The account has gained access right because of joining certain
groups.
‹
Individually Authorized Shares: Implies that the account has gained access
rights individually.
‹
Ownership: Implies that the account has gained access right because it is the
owner.
NOTE: Newly created accounts will automatically be a member of
"users" group.
Enabling and Disabling an Account
Account Manager allows the administrator to enable or disable a user account. When
an account is disabled, the account cannot be used to login and access proNAS.
To forbid certain user account in accessing proNAS, highlight the account then press
"Disable" button. The account will be shown with “Status” as Disable. If you would like
to re-enable the user account proNAS, press "Enable" button. Disabling account
"admin" is not allowed as well as all ADS/PDC and NIS accounts.
74
Configuration Guide
ProNAS 1.1.x
Deleting an Account
If you would like to delete a certain account, highlight the account then press "Delete"
button. The user's home directory will be deleted. If the user owns one of the share,
the owner of that share will be set to "admin". Account "admin" is not allowed to be
deleted as well as ADS/PDC and NIS accounts.
Modifying an Account
If you want to modify an account, double-click on the account. You can only
modify the password and permissions. If the account is an external domain account
(created by ADS/PDC or NIS domain server), the account and password can not be
modified in proNAS Account Manager. In such a case, you can only modify the
permissions.
Importing of Accounts
proNAS provides Import Account function for creating large number of accounts
instead of adding an account one by one. Administrator can create multiple user
accounts in a text file with the following format: UID, Logon Account, Logon Password,
Full Name.
Example:
1019, david, proware, David Huang
1020, rocky, proware, Rocky Lee
To import the accounts, click on "Import Accounts" button then select the text file.
NOTE: The information for each account must start on a new line.
If account creation fails for any account, proNAS skips that line (of
account information) and continues with the next line.
Refreshing the Account List
Use the “Refresh” button to automatically synchronize any new accounts created in
ADS/PDC or NIS domain.
Group Management
Using group management, admin can organize access to proNAS shares. For example,
a Sales group can be created for the sales department and this group can be assigned
read-write access to the Sales Report share. All account members of the Sales group
can have access to the Sales Report share.
Configuration Guide
75
ProNAS 1.1.x
Group List tab
The Group List tab shows the Local and External (ADS/PDC or NIS) Groups.
Group management allows the administrator to:
‹
‹
‹
Create or Delete a Local group
Modify a Group
Refresh the Group List
proNAS has two default groups, "users" and "proBackup". Every local user that will be
created will automatically become a member of users group. proBackup group is used
by proNAS for the proBackup service.
Creating a new Local Group
When a Local Group is added, it is created in the local account database of NAS. One
account can become a member of more than one group.
Following are the steps to create a new Local Group:
1. Select Account Manager in the proFamily tree. Choose Group node under the
Account Manager. It will display all groups under the Group List tab. Press the
"Create" button.
76
Configuration Guide
ProNAS 1.1.x
2. Enter the necessary information. Refer to options below.
Create Group Options:
‹ Group Name - Enter the name of new group. It should be unique.
‹ GID - Group ID. proNAS will either automatically assign a GID when you create a
group, or you can manually specify a GID.
‹ Description – Additional information or description about the Group can be
entered here.
Account List – shows the list if accounts that are available and can be joined to the
group
Current Member(s) – shows the list if accounts that are currently member of the
group
Use the following guidelines to ensure that you are using a valid Group name:
‹
‹
‹
‹
Group names cannot be longer than 16 characters.
Group names should be unique. No group names must be the same.
Group names cannot contain blank spaces.
Group names cannot begin with a dash (-) and cannot consist of only a single
dash.
‹ Group names cannot contain the following characters: /\[]";:|<>+=,?*
‹ Group names cannot be duplicated with the system default groups, i.e. root, mail,
news, operator, gopher, nobody, ftp, games, rpc, adm, nobody, etc.
Configuration Guide
77
ProNAS 1.1.x
3. In the Account List, select the account(s) that will be joined to the group then
click the “>>” button. The accounts will appear in the Current Member(s) list. To
remove an account from the group, select the account in Current Member(s) list
then click “<<” button.
4. Click “Save” button to save settings.
Deleting a Local Group
To delete a group, select the group to be deleted and then click the "Delete" button.
ADS/PDC and NIS groups are not allowed to be deleted. Default group "users" and
"proBackup" cannot also be deleted.
Modifying a Group
To modify a group, double click the group in Group List tab. The "Group List" tab will
be displayed in edit mode. Group name, description, group members are allowed to be
modified however this is only applicable to local groups. ADS/PDC and NIS groups are
not allowed to be modified. Default group "users" and "proBackup" cannot be modified.
ADS/PDC and NIS domain accounts are also not allowed to be joined to any local group
except to "proBackup" group.
Refreshing the Group List
Use the “Refresh” button to automatically synchronize any new groups created in
ADS/PDC or NIS domain.
78
Configuration Guide
ProNAS 1.1.x
3.4 Share Manager
In proNAS Share Manager, you can create and configure a Share, assign a share owner,
assign user permission, and specify file sharing protocol. Under this node you can also
use duplication function and rsync utility. Duplication is a share function in which you
can replicate your share into another share using file level replication. Rsync utility
is used to copy files either to or from a remote host, or locally on the current host.
In the "Share List" tab, you can list the current shares and also display share
information such as share name, quota, used space, logical volume and share owner.
There are 2 Default Share in proNAS: "home" and "public".
Share folder gets created under a logical volume. Make sure that an LV is already
created before creating the share folder or admin can create the share folder and LV
simultaneously, which can be done using the option “Create New Volume” in Properties
tab of Share Manager.
Configuration Guide
79
ProNAS 1.1.x
3.4.1 Share Management
3.4.1.1 Creating a New Share
To create a new share folder:
1. Select Share Manager then press "Add New Share" button.
2. Configure all necessary share options in Properties, Protocol, and Privilege tabs.
3. Click “Save” button to save share settings.
NOTE: After creating the share and setting the Properties, Protocol
and Privilege tabs, you can go back to these tabs and modify the
various options. To edit, click the share name in Share Manager
and click “Edit” button.
80
Configuration Guide
ProNAS 1.1.x
3.4.1.2 Applying ACL
When applying ACL in a share, all the files and subfolders under this share will inherit
the share's permission. "Apply ACL" will propagate the ACL settings of the share folder
into all of its child directories and files. For example, if user1 has read/write permission
on the sub-folder but read only on the share, after applying ACL, user1 will now have a
read-only permission on the sub-folder.
3.4.1.3 Modifying a Share
After creating the share, you can modify the Properties, Protocol, and Privilege tabs, as
well as setup the Rsync and Duplication functions. Click the “Edit” button to modify the
share.
Configuration Guide
81
ProNAS 1.1.x
3.4.1.4 Deleting a Share
If you delete a share, all the data in the share is deleted. If the data in the share is no
longer needed or a backup of the data has been made, you may delete a share. If
there is no data backup, we recommend you to create a backup first before deleting a
share.
3.4.2 Properties Setting
The Properties tab contains the following settings:
‹
Share Name - Input the share name, it should be unique in proNAS.
Use the following guidelines to ensure that you are using a valid Share name:
‹
‹
‹
‹
82
š
š
Names cannot be longer than 31 characters.
š
š
š
Names cannot contain blank spaces.
Names should be unique. It cannot be a duplicate with other LV names,
shares, and Account names.
Names cannot begin with a dash (-) and cannot consist of only a single dash.
Names cannot contain the following characters: /\[]";:|<>+=,?*
Volume Group (VG) - Choose a volume group from the list. Only Volume groups
that has member disk will be displayed. System will also display the available
space of the volume group.
Create New Volume (LV) -If you check this option, system will create LV as
well as create the new Share. The LV name will be the same as the share name.
Volume - Select a logical volume from the selected volume group.
Quota (MB) - Input the size of the share. This is also the size of the logical
Configuration Guide
ProNAS 1.1.x
‹
‹
‹
‹
volume to be created if you choose to create a volume at the same time.
Owner Account - Specifies the owner of the share.
ACL Support – Specifies if the share will support ACL permission (option is
enabled by default) or support “chmod” permission.
Public (777) - This option allows you to set a share as a public share. When
enabled, any user within the specified private net can connect to this share.
Hide Duplications - This option allows you hide or unhide the "_Duplication"
folder in this share. The default will be hidden.
3.4.2.1 Steps to Make a Share Folder a Public Folder Accessible to All Users:
NOTE: It is not recommended to set a Share as a Public Share
folder. Any local NAS account or Windows/NIS domain account (if
NAS is joined to the domain) can login to the share with
Read/Write privilege.
1. Select Share Manager. Select the share name that will be made accessible to all
users.
2. In the Properties tab, click “Edit”. Select (tick) the “Public (777)” option.
3. Click “Save”.
NOTE: If you need to reassign ACL, disable first (click to unselect)
the “Public (777)” option and enable (check) the “ACL Support”
option.
Configuration Guide
83
ProNAS 1.1.x
3.4.3 Protocol Setting
ProNAS supports the following share protocols: CIFS, NFS, AppleTalk, and Novell,
which can be set in Protocol tab when creating the share or when in edit mode.
3.4.3.1 CIFS
‹ Enable CIFS Sharing - This specifies whether to enable or disable CIFS sharing
‹ Case sensitive - This control whether filenames are case sensitive.
‹ Hide files that begins with dot - This option controls whether files starting with
a dot will appear as hidden files.
‹ MediaHarmony AVID – This option enables media file interoperability for nonlinear editors. It allows multiple editing clients (Avid editors) to interoperate
without conflicts.
‹ MediaHarmony MXF – This option enables media file interoperability for nonlinear editors. It allows on-the-fly unwrapping of MXF-wrapped DV essence so
that a Final Cut Pro client can share the same DV media files as an Avid client.
‹ Maximum Connections - This option limits the number of simultaneous
connections at a certain time. A value of zero means an unlimited number of
connections will be possible in this share.
NOTE: Only one option from “MediaHarmony AVID” and
“MediaHarmony MXF” can be enabled or selected at a time.
NOTE: The default setting of “Maximum Connections” is 10. If
there will be more than 10 client connections via CIFS
simultaneously, change the setting to a higher value. For unlimited
number of simultaneous connections, set it to zero (0).
84
Configuration Guide
ProNAS 1.1.x
3.4.3.2 NFS
‹ Enable NFS file sharing v2/v3 - This specifies whether to enable or disable NFS
version 2 / version 3 file sharing
‹ Enable NFS file sharing v4 - This specifies whether to enable or disable NFS
version 2 / version 3 file sharing
‹ Synchronize write operation – Use this option to enable or disable write caching
‹ Allow root's access – Use this option to allow or disallow access by root super
user account
‹ Insecure - If you choose this option, it means only the port under 1024 can access,
it provides higher security
‹ Subtree check – Use this option to enable or disable subtree checking. A subtree
check happens if a subdirectory of a filesystem is exported, but the whole
filesystem isn't then whenever a NFS request arrives, the server must check not
only that the accessed file is in the appropriate filesystem (which is easy) but also
that it is in the exported tree (which is harder).
3.4.3.3 AppleTalk
Enable AppleTalk File Sharing: This specifies whether to enable or disable AppleTalk
file sharing.
3.4.3.4 Novell
Enable Novell/IPX Sharing: This specifies whether to enable or disable Novell
Netware file sharing.
Configuration Guide
85
ProNAS 1.1.x
Accessing proNAS shares under Linux
For NFS
share:
Usage:
where:
mount -t nfs x.x.x.x:/mnt/proNAS/volume/share /mnt/temp
x.x.x.x = proNAS IP address
/mnt/proNAS/volume/share = the complete path of the NFS share. You
may use the command "showmount -e x.x.x.x" to query the complete
path.
/mnt/temp = local mount point on the client
For CIFS
share:
Usage:
mount -t smbfs //x.x.x.x/share /mnt/temp -o
username=account,password=secret
or
mount.cifs //x.x.x.x/share /mnt/temp -o
username=account,password=secret
or
smbmount //x.x.x.x/share /mnt/temp -o
username=account,password=secret
where:
x.x.x.x = proNAS IP address
share = CIFS share name. You may use the command "smbclient -L
x.x.x.x" to query the CIFS share names.
/mnt/temp = local client mount point.
-o username=account,password=secret = the account name and
password
86
Configuration Guide
ProNAS 1.1.x
3.4.4 Privilege Setting (Permission)
Using Privilege tab, administrator can set the ACL (Access Control List) for share folder
either by Group, Account, and IP Address.
3.4.4.1 Group
You can assign specific group read or read/write permission for certain share folder.
Choose the group and press "ADD" button. The group will displayed in the
permission list, and check "Read" or "Write" or check both and press "Save". If you
would like to remove the group with ACL setting to certain share folder, select the
group name and press "REMOVE" button.
Sample Steps to Assign Group Account Permission to Share:
1. Select Share Manager. Select the share name where account will be given
permission, and click Privilege tab.
2. Click “Edit”. Select Group tab.
3. Select the group account that will be given permission and click “ADD”.
NOTE: When group account name is selected, it will be highlighted. If
you want to select more than one group account at the same time,
press “Shift” key then click the groups you want to add to Permission
list.
4. In the Permission list, modify the permission, either Read-Only (no check mark in
“Write” box) or Read/Write (both “Read” and “Write” boxes have check marks).
Configuration Guide
87
ProNAS 1.1.x
5. Click Save.
3.4.4.2 Account
You can assign specific account user read or read/write permission for certain
share folder. When you set the account with ACL, it may be necessary to remove
the users group from the permission list in order to prevent access of other
members of “users” group to the share. Choose the account and press "ADD"
button, and the account will be displayed in the permission list. Check "Read" or
"Write" or check both and press "SAVE".
NOTE: Newly added users or groups may have no permissions on
the existing files or sub-folders until "Apply ACL" button is
executed.
88
Configuration Guide
ProNAS 1.1.x
Sample Steps to Assign User Account Permission to Share:
1. Select Share Manager. Select the share name where account will be giver
permission, and click Privilege tab.
2. Click “Edit”. Select Account tab.
3. Select the account name that will be given permission and click “ADD”.
NOTE: When account name is selected, it will be highlighted. If you
want to select more than one account at the same time, press “Shift”
key then click the accounts you want to add to Permission list.
4. In the Permission list, modify the permission, either Read-Only (no check mark in
“Write” box) or Read/Write (both “Read” and “Write” boxes have check marks).
5. Click Save.
Configuration Guide
89
ProNAS 1.1.x
3.4.4.3 IP Address
This option allows you to set a certain range of hosts to have an access into share
folder of proNAS. By default, the IP address is set to *.*.*.* which means that
the share folder will accept connections from any host. If set to 192.168.100.*,
this will only allow connections from your private network 192.168.100 and all
other connections will be refused.
NOTE: Not all ACL permission settings may be applicable to all
share protocols. If you set NFS protocol, it can support all ACL
setting mentioned above. If you set CIFS protocol, read only IP
address will not be honored. If you set AppleTalk or Netware
protocol, you can only set ACL permission by account or group.
Sample Steps to Limit Share Connections to Selected IP Range:
1. Select Share Manager. Select the share name where account will be giver
permission, and click Privilege tab.
2. Click “Edit”. Select IP Address tab.
NOTE: BY default, all IP addresses (*.*.*.*) have Read/Write access
to the NAS. If you restrict NAS connections from specific IP range,
only the selected IP range can access the NAS share. Group
Permission or User Account Permission is still needed to be assigned
in order for users to gain access to the share folder.
3. To remove *.*.*.*, select “*.*.*.*” from Permission list and click “REMOVE”.
4. To add an IP range, enter the IP range (e.g.: 192.168.1.*) in the “IP Address”
box, check the “Write” box to assign Read-Write access if necessary, and click
“ADD”.
90
Configuration Guide
ProNAS 1.1.x
5. Click “Save” when done.
Permissions:
This section lists the permissions that you can assign for each user, group, or IP
address. When you create a share, the default owner which is the "admin" will be
granted full control. The same is also true for "users" group and the "*.*.*.*" for IP
address.
Listed below are the share permissions defined in proNAS:
Read only
Read+Write
Allow Deny
Access share, sub-folder
Read
Write
Edit/Modify
Delete
Rename
;
;
Allow Deny
Access share, sub-folder
Read
;
;
;
;
Write
Edit/Modify
Delete
Rename
;
;
;
;
;
;
Setting the amount of quota to a specific user
In the "Quota(MB)" field, you can input the quota of an account which is granted
permission to the share. Press the "Enter" key after you input the amount in Quota(MB)
field. To remove the quota limit, set the Quota(MB) to 0 then press "Enter" key.
Configuration Guide
91
ProNAS 1.1.x
3.4.5 Rsync
Rsync copies files either to or from a remote host, or locally on the current host. It is
also a utility that provides fast incremental file transfer. proNAS Rsync implementation
can be set either in server mode or client mode. Server mode means that proNAS can
accept incoming Rsync connections, where as in client mode, proNAS is the one who
initiates the synchronization. To use as a server mode, you must start the "RSYNC
server” first. Go to System Manager -> Service tab, highlight "RSYNC server” then
click the “Start” button.
Some of the additional features of Rsync are:
‹ Support for copying links, devices, owners, groups, and permissions.
‹ Pipelining of file transfers to minimize latency costs
‹ Support for anonymous or authenticated Rsync daemons
Server Mode:
When proNAS system is in Server Mode, the Rsync clients can connect either within a
local transfer, via a remote shell or via a network socket.
‹ Enable - When checked, proNAS is set as a Rsync server.
‹ Read only - When checked, all files within this share will be read only to any
Rsync client.
‹ Anonymous - When checked, anonymous connections will be accepted.
‹ Maximum Connections - This specifies the maximum number of Rsync client that
can connect to this share at a certain time.
‹ Edit accounts - You may edit and existing account, or add/delete a user. These
accounts are the accounts that need to be supplied by the Rsync clients when
connecting to this server.
92
Configuration Guide
ProNAS 1.1.x
Client Mode:
The proNAS system will initiate the synchronization and contact an Rsync server. There
are two different ways for Rsync to contact a remote system: using SSH as a remoteshell program as the transport or contacting an Rsync daemon directly via TCP.
‹ IP Address - This specifies the IP address of the remote Rsync server.
‹ Remote Path - This specifies the share on the remote Rsync server.
‹ Account - The valid account name that will be required by the Rsync server for
authentication.
‹ Password - The account's password.
‹ Mode - Either to
download files from
the Rsync server or
to upload files into
the Rsync server.
‹ SSH - When
checked, SSH
service will provide
the secure tunnel
between an Rsync
client and an Rsync
server.
‹ Rsync Options These are the lists
of options used
during Rsync file
transfer
Configuration Guide
93
ProNAS 1.1.x
Here is a short summary of the available options. Please refer to the detailed
description below for a complete description. Some options only have a long variant.
-r, --recursive
recurse into directories
-v, --verbose
increase verbosity. This option increases the amount of information
your are given during the transfer
-l, --links
copy symlinks as symlinks
-p, --perms
preserve permissions. This option causes the receiving Rsync to set
the destination permissions to be the same as the source
permissions.
-o, --owner
preserve owner (super-user only). This option causes Rsync to set
the owner of the destination file to be the same as the source file
-g, --group
preserve group. This option causes Rsync to set the group of the
destination file to be the same as the source file.
--ignore-existing
Ignore files that already exist on the receiver. This tells Rsync to skip
updating files that already exist on the destination.
-b, --backup
With this option, preexisting destination files are renamed as each
file is transferred or deleted. You can control where the backup file
goes and what (if any) suffix gets appended using the --backup-dir
and --suffix options
--backup-dir=dir
In combination with the --backup option, this tells Rsync to store all
backups in the specified directory. This is very useful for incremental
backups. You can additionally specify a backup suffix using the -suffix option (otherwise the files backed up in the specified directory
will keep their original filenames).
--suffix=SUFFIX
This option allows you to override the default backup suffix used
with the --backup (-b) option. The default suffix is a ~ if no -backup-dir is specified, otherwise it is an empty string.
-D, --devices
preserve device files
--specials
preserve special files
-t, --times
preserve times
-S, --sparse
handle sparse files efficiently
-z, --compress
Compresses file data during the transfer. This option is useful in slow
links.
-a, --archive
This is equivalent to -rlptgoD. It is a quick way of saying you want
recursion and want to preserve almost everything (with -H being a
notable omission).
-E, --executability
This option causes Rsync to preserve the executability (or nonexecutability) of regular files when --perms is not enabled.
-h, --humanreadable
Output numbers in a human-readable format.
--stats
Give some file-transfer stats.
--delete
Delete files that don't exist on the sender.
--log-fileformat=FORMAT
Output filenames using the specified format.
--log-file=FILE
Output filenames using the specified file.
94
Configuration Guide
ProNAS 1.1.x
--bwlimit=KB/S
Limit I/O bandwidth; KBytes per second.
-n, --dry-run
This tells Rsync to not do any file transfer; instead it will just report
the actions it would have taken.
--timeout=SECS
Sets the maximum I/O timeout in seconds. If no data is transferred
for the specified time then Rsync will exit. The default is 0, which
means no timeout.
There are lot more useful options that are not included in this list. It may vary
depending on your usage, for more information on Rsync, please visit
http://samba.org/rsync/.
After completing the above settings, you can run the Rsync client task immediately by
clicking the "Execute" button.
Rsync Schedule
You can automate the
Rsync client tasks
simply by running it
thru schedule. Please
select which day(s) to
run, the time of the
day or if by interval,
select a time then set
the starting/ending
time and then enable
the schedule by
clicking on the "Enable
Scheduled" button.
Configuration Guide
95
ProNAS 1.1.x
3.4.6 Duplication
Duplication is a file level snapshot utility for making backups of your local filesystem.
Using Duplication, it is possible to take incremental snapshots of your filesystem at
different points in time. Duplication creates the illusion of having a multiple full
backups by using hard links, while only taking up the space of one full backup plus
differences. This saves much more disk space than one might image. The duplication
files will be directed to a share which you can access via share protocols or by telnet
service.
Duplication can be invoked manually or by schedule.
Select the share folder in Share Manager then click “Edit” button.
Creating Duplication by Schedule
To create duplication by schedule, first set the number of total duplication that will be
created, specify which day to be run, set the time task whether by interval or once in a
specific time of day, set the destination path and then click “Save” button. Enable the
schedule by clicking on the "Enable Scheduled" button. To disable the scheduled
duplication, just click on the "Disable Scheduled" button.
96
Configuration Guide
ProNAS 1.1.x
The Duplication tab information is shown below.
Execute Day:
Specifies whether the scheduled task is to run on this day.
Execute Time:
Once - Specifies the time of the day the scheduled task create
the snapshot.
Every - Specifies how often the scheduled task is to be
repeated. You can also select the starting time and the ending
time.
Destination
Path:
This will be the location where your duplication files will be
saved. The default path will be the path of the share itself. You
can change the path to the other shares except home and
public. Duplication will follow the ACL settings of the destination
share. If you set the destination of your home duplication to a
public share then anybody can access that folders, so please be
warned!
Snapshot
Numbers:
Specifies the total number of snapshots that can be created.
The maximum total number of duplication a share can have is
256.
NOTE: The destination space must be larger than the source.
proNAS will check only the destination volume size, not the share
usage. Be sure that the available space on the destination is
reasonably big enough to accommodate any changes in the source.
Home duplication is a special case. If the destination path of the
home folder is set to the home itself, its duplication files will only
be accessible via NFS, Telnet, SSH or FTP service.
Create
Duplication:
This button allows you to create duplication
manually.
Delete All:
This button will remove all the duplication files of
this share on the current destination path.
Enable/Disable
Scheduled:
This button allows you to enable or disable a
scheduled task.
Get List:
This button allows you to get the lists of
duplications on the current destination path.
Configuration Guide
97
ProNAS 1.1.x
Creating Duplication Manually
To create duplication manually, first set the number of total duplication that will be
created, set the destination path and then click the "CreateDuplication" button. The
source share must have at least a single file in order for the duplication to work
properly.
Removing or Clearing All Duplication Files
To delete all the duplication files of this share on the current destination path, press
the "Delete All" button. Duplication files on the previous destination path will not be
removed. Duplication files of other shares on the same destination path will not also be
removed.
Getting the Duplication List
To get the lists of all duplication files of this share on the current destination path,
please press the "Get List" button. The table will then update the lists of duplication
folders. The table includes the date and time it was created and the destination path
where it was saved. Duplication files of this share on the previous destination will no
longer be included in the list. However proNAS will automatically update the duplication
list for you every minute.
How Duplication Works
After you have created Duplication, your destination path will contain a folder
"._Duplication". (It is hidden by default, to unhide it, uncheck the "hide duplication"
option in the Properties tab of the destination folder). Inside the "._Duplication" folder
are the directories that are created for the various intervals that you have defined. It
will look something like in the figure below.
98
Configuration Guide
ProNAS 1.1.x
Inside each of these folders is the full backup of that point in time of the source share.
The format of the duplication folder name will be the share name of the source share
appended by an underscore then the character "Dup" followed by the number of the
interval. "ShareName_Dup.0" will always contain the most recent snapshot and the
duplication with the highest interval number will contain the oldest snapshot. When a
new duplication is run, it will rotate all the duplication directories. The files on oldest
duplication will not be saved and will be replaced with the content of its succeeding
duplication, so please take note of this. The number of duplication will depend on the
number of snapshots that you have defined. You need to increase the total number of
snapshots if you want to save the backups for a longer time. For example, if you set
the snapshot numbers to 60 and you set a schedule to take duplication every day, the
very last backup would be around two months old before it will be discharged if a new
duplication is made.
NOTE: To view the date modified of duplication folders that
corresponds to the date when the duplication was taken, use File
Manager and view in detailed mode.
3.4.7 Default Shares
Basically, there are only two default shares when proNASVG is initially created. If the
proBackup Service is started, two other default shares are created. The default shares
in proNAS are:
‹ home - holds the individual shares of all users. It cannot be deleted.
‹ public - a share intended for all users. Any type of user (including guests or
anonymous) can logon to this share and is given read-write permissions.
‹ proBackupDevice - holds the major backup device for proBackup application. It
becomes visible after proBackup service is enabled.
‹ proBackupExtendedDevice - holds the extended device for other proBackup
servers to utilize. It becomes visible after proBackup service is enabled.
Configuration Guide
99
ProNAS 1.1.x
3.5 System Manager
System Manager is composed of different tabs which is responsible for the
configuration of proNAS system settings and services, such as: Firmware Upgrade,
Account and Share reports, Date and Time Zone, Serial Ports and UPS settings, Reboot
functions, and Services configurations.
3.5.1 Information tab
The Information tab shows the account, storage and system information.
Account Information
‹ Account Numbers - Indicates the total numbers of all local and external
accounts.
‹ Share Numbers - Indicates the total number of all shares.
Storage Information
‹ Disk Numbers (Free/Total) - The number of disks in the subsystem, "Free"
means the disks those are not joined in volume group.
‹ Vol Group Numbers - The total number of volume groups.
‹ Volume Numbers - The total number of logical volumes. Snapshots will also be
counted as volumes.
100
Configuration Guide
ProNAS 1.1.x
System Information
‹
‹
‹
‹
‹
‹
Model - Specifies the proNAS system model name.
Build Version - proNAS current firmware version.
CPU - Specifies the CPU Type and the number of CPUs.
MHz - Specifies the CPU speed.
Memory - Memory size.
NIC – The Ethernet ports. Shows NIC status, MAC address and IP address.
3.5.2 Upgrade tab
The Upgrade tab is used to upgrade the proNAS system firmware version.
‹ Firmware Version - Displays the current firmware version.
‹ Release Date - The Release Date of this version.
‹ Upgrade from the specified URL - You can download the latest version from
URL: ftp://support:xxxxxxxx@upgrade.proware.com.tw/proNAS/
If you would like to see if there is latest version, please press "Check Updates" button.
The system will search if there is any latest firmware to update.
Besides firmware update from web-site, you can also do a firmware update from local
file system, but you need to download first the firmware Patch and save to the local file
system. Press "Browse" button and locate the firmware patch.
Configuration Guide
101
ProNAS 1.1.x
3.5.3 Report tab
proNAS provides report function which enables you to collect the usage information of
all accounts and shares. The output file will be saved in a ".csv" file. Report function
can generate report either by schedule or immediately.
Schedule Report
If you would like to enable schedule report, press the "Edit" button, check "Enable
Schedule Report", check the report option for "Account" or "Share" or both, and set the
Day and Time when to generate the report. The system will generate the report and
save in the path /mnt/proNAS/home/admin (The path can be modified).
If you would like to receive the report by e-mail, please check "Enable Mail Deliver"
and input the information for SMTP server, sender e-mail and receiver e-mail address.
If you prefer to enable email authentication, enter the account and password. You can
also change the default port if needed.
Immediate Report
If you would like to collect the report immediately, press "..." and choose the path for
the output file and press "Generate Now" button.
102
Configuration Guide
ProNAS 1.1.x
3.5.4 Time tab
You can configure the system time, date and time zone in this tab. Click the "Edit"
button and choose the appropriate time zone. After setting the time zone, select "Set
time manually", if not selected, then set the Date and Time. To set the date, press "...",
then the system will display a calendar to choose the date.
If you would like to synchronize time with NTP server, select "Synchronize time to NTP
server". The system will display two NTP servers by default. If you would like to add
NTP server, press ">>", or press "<<" to remove the NTP server". When the settings
are completed, press "Save" button.
Configuration Guide
103
ProNAS 1.1.x
3.5.5 Serial Ports tab
Com1 and Com2 Serial ports can be configured in this tab for specific application. Press
"Edit".
Com1
Supported Applications are: NAS Device Mgr or proNAS HA
NOTE: Some NAS model does not support NAS Device Manager.
You can use Com1 port for proNAS HA (optional) application.
Com2
Supported Applications are: UPS or proNAS HA
If you set Com2 to UPS, you can select between two supported UPS Modes: dumb
mode or smart mode.
If you choose dumb mode, you don't have to configure the detail setting about vendor
and cable. If you choose smart mode, proNAS supports three UPS Vendor: (a) APC,
(b) BeamTech, and (c) HyperPro. Select the UPS vendor then set the UPS Model and
Cable Model. The only Beamtech UPS model supported is SSpro 650. The only
HyperPro UPS model supported is 1410HP. APC has many models supported. APC cable
models are: simple, smart, ether, usb, and snmp
Shut Down delay (Min): the time to shutdown system after power fail
Auto Shutdown UPS (APC only): automatically shutdown system after power fail; APC
UPS only
After completing the settings, press "Save" button.
104
Configuration Guide
ProNAS 1.1.x
3.5.6 Power tab
The Power tab is used to configure schedule system power off and power on. You can
also shutdown the system immediately using “Shutdown Now” button.
Scheduling Power Off
Select the day or days, and set the Hour and Minute when the system will shutdown.
Scheduling Power On
Select the day or days, and set the Hour and Minute when the system will power on.
Configuration Guide
105
ProNAS 1.1.x
3.5.7 Reboot tab
The administrator can reboot proNAS by schedule or immediately.
If you would like to reboot by schedule, press "Edit" button, and check "Enable
schedule reboot". Choose the date and time when to reboot. This function can help to
clean the unnecessary system process or connection periodically.
If you would like to shut down or reboot immediately, press "Shutdown Now" or
"Reboot Now":
If you check there is file error or I/O error from system log, or VG can not mount, or
system shutdown abnormally, it is recommended to use the function “Reboot & File
System Check”.
If you would like to erase existing storage and proNAS configuration and reset to
factory default, you can use the “Erase Storage & Configuration” button.
WARNING! All data and configuration will be deleted if you use this
function. Please make sure you already have a backup of your data
and configuration, or that you do not need the current data and
configuration.
106
Configuration Guide
ProNAS 1.1.x
3.5.8 Service tab
The various proNAS services can be set in this tab.
If you would like to enable service while booting, please check "Enable on Boot" option.
You can also press "Start All Services" button to run all services, or press "Stop All
Services" button to stop all services. If you would like to enable or disable certain
service, please select the service item and press "Start" button or "Stop" button.
proNAS system services are as follows:
Samba services:
Provides CIFS file sharing, MS Windows users need this to
access proNAS.
NFS service:
Provides NFS file sharing, UNIX users need this to access
proNAS.
AppleShare
service:
Provides AppleTalk sharing, Mac OS users need this to access
proNAS.
File Manager
server:
Enables to stop and start the File Manager web page service.
RSYNC server:
Provides Rsync process or system to which the Rsync client
connects.
Novell file server:
Provides Netware file sharing, Novell users need this to
access proNAS.
SSH server:
Provides remote management with more secure level.
Configuration Guide
107
ProNAS 1.1.x
Apache Web
server:
Provides web service, you have to enable this service, port
number default is 80.
Telnet/Ftp service:
Provides users access proNAS with telnet or ftp
Internet Gateway:
Provides Internet access.
UPS monitor:
If you would like to connect UPS, you have to enable this
service.
SNMP/MRTG
service:
Provides SNMP/MRTG service to view system information.
proNAS can send trap messages if:
- A logical volumes becomes almost full (ID 128)
- A snapshot volume becomes almost full (ID 129)
- A replication is disconnected (ID 130)
Veritas Backup
Exec eng:
Provides service for Veritas console to make proNAS a Veritas
Backup media node.
proBackup service:
Provides service for NAS users to backup their files to NAS.
Refer to Chapter 11 for fore information.
proNAS HA service:
Provides NAS HA solution.
proNAS provides "Quick Configuration" for administrator to configure service
parameters. Experienced administrator can also configure the advance settings in
"Detail Configuration".
ProNAS Quick Configuration options are as follows:
Samba Service
‹
Strict allocate setting – This option controls the handling of disk space allocation
in the proNAS server. When strict allocate is set to “no” (default setting) the
server does sparse disk block allocation when a file is extended.
AppleShare Service
‹
Languages – set the language used for Apple Share service
proBackup Service
‹
‹
IP of Rx/Tx backup streams: Enter the proNAS network interface IP address for
proBackup service stream
Port of Rx/Tx backup streams: Enter the Port number for proBackup stream ,
default is 1089.
SSH Service
‹
‹
Allows root login via SSH service
Enable SFTP
Apache Web Service
‹
108
Default port number is 80
Configuration Guide
ProNAS 1.1.x
Telnet/FTP services
‹
‹
Allows root login via FTP
Allows root login via Telnet
Veritas BackupExec eng service
‹
‹
Advertised Host: Name of media node
Workstation password: Administrator password
SNMP/MRTG Service
‹
Trap Receiver IP: Enter the IP address of the SNMP trap receiver.
Configuration Guide
109
ProNAS 1.1.x
3.5.9 Status tab
You can use this tab to view system status, such as various Service Connections, Top,
PS, and Iostat.
By default, a summary of connections and resources used for local and remote
computers is listed. The information includes the PID, User, User full name or comment,
login time, and the IP address of the connected computer. You can click the
“Connections” button to display current connection list.
Click the “Top” button to display system summary information and tasks list.
Click the “PS” button to display information about active processes.
Click the “Iostat” button to display system input/output device loading, specifically
storage and disk device statistics.
110
Configuration Guide
ProNAS 1.1.x
3.5.10 MRTG tab
This tab shows information about MRTG graphs and includes CPU Loading, Memory
Usage, Disk IO, and Network Traffic.
Configuration Guide
111
ProNAS 1.1.x
3.6
Backup Manager
You can backup proNAS data and system configuration via Backup Manager.
In "Backup Manager" tab, you can check the existing backup plans in the "Backup Plan
List" which includes backup plan name, next backup time and if the backup plan
schedule is enabled. If you would like to create new backup plan, please press "Add
Backup Plan" button.
3.6.1 proNAS Configuration Backup
proNAS provides System Configuration Backup which means administrator can backup
system configuration information. Select "NAS Config Backup" tab.
112
Configuration Guide
ProNAS 1.1.x
Press "Backup" button. Choose the path you would like to save the file and enter the
file name. System will backup the configuration information as an .xml file. If you
would like to restore the configuration later, press "Apply" button.
NOTE: Not all proNAS configuration will be included in NAS Config
backup. These includes replication, snapshot, Event Manager
setting and HA configurations.
NOTE: In order to restore a NAS backup configuration, you need to
reset the NAS to factory default settings.
3.6.2 Configure Backup Plan
Backup Plan Setting
In the "Backup Plan Setting" tab, you can create new a backup plan. Enter the "Backup
Plan Name", and then press "..." to choose the backup destination, your destination
could be remote share, tape or local device.
Configuration Guide
113
ProNAS 1.1.x
Use the following guidelines to ensure that you are using a valid backup plan
name:
‹
‹
‹
‹
‹
Names
Names
Names
Names
Names
cannot be longer than 256 characters.
should be unique. It cannot be a duplicate with other Backup plan names.
cannot contain blank spaces.
cannot begin with a dash (-) and cannot consist of only a single dash.
cannot contain the following characters: /\[]";:|<>+=,?*
If you choose remote share, please input the IP address in the "path" field. Choose
Samba or NFS of the protocol and enter account and password.
Example:
For
Samba:
Path =
//192.168.100.164/Share
You cannot use the directory under the share.
Example:
//192.168.100.164/Share/dir1 <==Incorrect
//192.168.100.164/Share <==Correct
If you are not sure of the share name on the
remote machine, you may query it by using the
command "smbclient".
-bash-3.00# smbclient -L 192.168.100.164
Login = account
Account that has full access permission on the
remote share.
For NFS:
Path =
Example:
192.168.100.164:/PathToSh 192.168.100.164:/mnt/proNAS/vol1/share1
areName
If you are not sure of the correct path of the
remote NFS server, you may use the command
"showmount".
-bash-3.00# showmount -e 192.168.100.164
Login
114
Configuration Guide
For NFS, it will assume the root account to be
used. Please verify that root account can
access the remote NFS share.
ProNAS 1.1.x
If Backup Manager fails to mount the remote share, you may need to verify it manually
via console. That is to connect to the remote machine and mount the remote share.
First we need to create a directory as our mount point.
-bash-3.00# mkdir /mnt/temp/
For Samba:
-bash-3.00# mount //ServerIP/ShareName /mnt/temp -o lfs,
username=account,password=password
For NFS:
-bash-3.00# mount ServerIP:/PathToShareName /mnt/temp
If you choose tape, you don't need additional setting.
If you choose local device, the system will display the available disks in the "Free Disk"
field.
If you choose the option "compressed", the data will be compressed to * .gz file.
Press "Save” button complete the setting and go back to "Backup Plan Setting" tab. In
the field of "Description", system will display you backup destination (remote share /
tape / local disk) in Type area.
Please press "Edit Backup Item List" button. System will display the window for you to
choose the backup items ("Volumes" or "Share"). Choose your backup items and press
"Save" button to go back to "Backup Plan Seting" tab. You can check the backup items
in the "Backup Item(s)" list, if you would like to remove some items. Please check in
the "Remove" filed and press "Remove Backup Item(s)".
Schedule Backup tab
After you complete the above setting, you can setup the schedule in the "Schedule
Backup" tab, if the tab, you will see the option of "No Schedule", "Daily", "Weekly",
and "Monthly".
Configuration Guide
115
ProNAS 1.1.x
š
Daily: If you would like to do the backup every day, please check "Daily". Please
press"...", system will display the calendar. You can choose "Start Date" and
"Ending Date" and the "Starting time".
proNAS provides 3 kinds of backup methods:
Incremental: An incremental backup stores all files that have changed
since the last backup. The advantage of an incremental backup is that it
takes the least time to complete. However, during a restore operation,
each incremental backup is processed, which could result in a lengthy
restore job.
Differential: A differential backup contains all files that have changed since
the last FULL backup. The advantage of a differential backup is that it
shortens restore time compared to a full backup or an incremental backup.
However, if you perform the differential backup too many times, the size of
the differential backup might grow to be larger than the baseline full
backup.
Full: Full backup
š
116
Weekly: If you would like to backup weekly, please check this option. Please
press "...", system will displays the calendar. You can choose "Start Date" and
"Ending Date" and the "Starting time".
Configuration Guide
ProNAS 1.1.x
š
Monthly: Full backup is the starting point for all data backup. Choose this option
to do full backup monthly.
Press "Save" after you completed the settings. Go back to "Backup Plan Setting" tab.
You will see the backup plan in the "backup plan list".
If you would like to modify the backup plan, please choose the backup plan in the left
tree-node, and press "Edit". If you would like to backup immediately, please press
"Backup Now"; or press "Enable schedule backup". System will display schedule enable
or disable in "Backup Status" field.
If you would like to restore data from the backup plan, please choose the backup plan
in the left tree-node, and go to "Restore" tab, press "Restore" button.
Configuration Guide
117
ProNAS 1.1.x
3.6.3 Tape Control
The Tape Control tab allows you to control the tape function when attached to the NAS.
Options:
rewind tape to the begin. – This enables the tape to be rewound to the
beginning of the tape.
forward tape to the end of data – This enables the tape to be forwarded to the
end of data.
erase all data in tape – This enables the data on the tape to be erased.
eject tape – This enables the tape to be ejected from tape drive.
Status – This shows some information about current status of tape.
118
Configuration Guide
ProNAS 1.1.x
3.7 Log Manager
The Log Manager enables you to view the important logs generated by proNAS.
The Event List tab of the Log Manager lists the log type, file name, date and size (KB).
To update and view the latest log information, please press "Reload".
‹ KER - This log contains information about the Linux Kernel service. Its path is
/var/log/messages. It can store information of 7 days.
‹ SMB - This log contains information about CIFS and Samba protocol. Its path
is /var/log/samba.log
‹ DSK - This log contains information about the changes to volume. Its path is
/var/log/storage.log. It can store information of 7 days
‹ NBS - This log contains information about NetBios protocol service provided
by Samba.
‹ NWS - This log contains information about Netware protocol. Its path is
/var/log/nws.log
‹ BAK - This log contains the status of Backup Manager.
‹
RSY – This is the log for Rsync service.
‹ VRT - This log contains the status of Veritas.
‹ DUP - This log contains the information of the duplication function.
Save All Logs - Allows you to download the system log files to local folder or
destination.
Configuration Guide
119
ProNAS 1.1.x
3.8 Event Manager
Event manager is a set of management option wherein you can set to receive email
notifications or trigger certain commands when a proNAS, proNAS HA or NAS
Device Manager event occurs.
3.8.1 E-mail Setting tab
Press "Edit" button to edit the following fields:
‹
‹
‹
‹
‹
‹
‹
120
Sender E-mail Address - Enter the sender's e-mail address.
SMTP Server - Enter the IP address of the SMTP server.
Port - Enter the port number. Default is 25.
Accounts - Enter the SMTP server admin account.
Password - Enter the SMTP server admin password.
Press "Add" button to insert the e-mail address recipients. You can have multiple
receivers.
If you would like to delete a receiver, select that receiver and then press "Delete".
Configuration Guide
ProNAS 1.1.x
3.8.2 Event Setting tab
Press "Edit" button and check the box "Enable Event Notification". Choose the following
mail notification. The lists of event options will depend on which service is currently
active. By default, all proNAS event will be displayed. Events for proNAS HA or NAS
Device Manager will be displayed only after you have started or logon into these
services.
The event options are:
Application
Event
Purpose
proNAS
Web service stopped
Notify if Apache web service is
stopped.
proNAS
Over Quota
proNAS
Invalid Snapshot
Notify if a snapshot became
invalid.
proNAS
Replication
Disconnected
Notify if replication was
disconnected.
Notify if a logical volumes
exceeds the given quota (full or
almost full). Please check the
"Send email when not enough
space" for the logical volume.
Please don't forget to press Enter key after you input the script path.
Configuration Guide
121
ProNAS 1.1.x
Chapter 4 File Manager
4.1 Introduction to File Manager
File Manager is a web-base file system for normal account users to do the following
actions:
Read a file: User needs the read permission of the folder and the file itself. The file
may be opened immediately if the browser knows the corresponding applications that
can open it, or the browser will prompt users to save the file in the local computer
instead.
Upload a file: User needs the write permission of the folder and the file itself. A
browser’s upload window will show up and user needs to locate the file from local
computer to be uploaded to the current directory.
Create a folder: User needs the write permission on the directory. A browser’s
“Create New Dir” window will show up and user needs to enter the folder name.
Delete a file: User needs the write permission of the folder and the file itself.
Rename a file: Same as above. User needs to give the new name of a file.
Change Password: If user needs to change password, please select this function.
122
Configuration Guide
ProNAS 1.1.x
Access Right (Change the ACL of a file or sub-folder): User needs to be the
creator or the owner of the share folder. A user is the creator of a file or folder if user
creates it. The owner of a share folder can grant the access permission of a share to
other accounts or access groups. User also can manage the ACL of all the files and
sub-folders under the share.
The function of access right is for share owner to do more detail management for the
users accessing the shares. Share owner can increase or delete the access right of
users or groups in addition to the setting of administrator in proNAS GUI. Furthermore,
share owner can manage the detail access right of the subfolders.
4.2 Logon to File Manager
Enter the username and password to pass authentication.
The first Screen of file Manager will display and help users to understand the possible
options and to perform file management. There are 4 Main Menu in the File Manager
screen: CurrentDir, Upload, Setting, and Logout. There are also short-cut icons below
the main
menu, like
Main, Home,
Reload
Page,
Delete
Current
Folder, and
Create New
Folder.
Configuration Guide
123
ProNAS 1.1.x
4.3 Directory and Upload Function
NOTE: Operations in the main Share folder, such as changing ACL
or deleting the Share itself, is not permitted. This must be done in
the Share Manager on proNAS management GUI.
Current Dir – Shows possible menu options that can be done in the current directory.
‹
Create – Allows user to create a new directory.
‹
Chmod – Allows user to change the file access permission on the current directory.
‹
Rename – Allows user to rename the current directory.
124
Configuration Guide
ProNAS 1.1.x
‹
Delete – Allows a user to delete the current directory.
‹
Permission – Allows user to change the Access Rights of different users on the
current directory.
Upload – An option used to upload a local file into the current directory. Use the
“Browse” button then select the file to upload.
WARNING! The file size to upload should not be greater than 1GB.
Configuration Guide
125
ProNAS 1.1.x
4.4 User Access Right and Group Access Right
A user who is the owner of the share can grant access permissions to other users or
groups listed in the Permission list.
After changing the Access Rights, click the “Submit” button. The ACL will be saved and
updated only in the current directory or sub-folder. To update other directories or subfolders below the current directory, use the “Apply ACL” button. This will propagate the
current ACL to the ACL off all files and sub-folders below. To cancel any changes, click
the “Cancel” button.
4.5 Change Password and Logout
Setting – Allows a user to change his/her password.
NOTE: The password must be at least 6 characters in length.
Logout - Allows a user to logout from the current session of File Manager.
126
Configuration Guide
ProNAS 1.1.x
Chapter 5 proBackup
5.1 Introduction to proBackup
proBackup provides end users a friendly Java GUI that makes versatile backup
functions available to general users. They can easily backup and restore their files to
and from proBackup storage device, and they do not need to install proprietary
software in their machines. It is also simple to setup a proBackup storage for a
company or an organization, even for non-IT-pro person.
5.2 Administrator Logon
The administrator account, admin, can login to proBackup. In proNAS Manager, admin
can also assign other privileged users to become member of the proBackup group.
Only admin and members of the proBackup group can login to proBackup and perform
proBackup functions.
Before admin or proBackup user can login to proBackup Java GUI, the proBackup
service must be started in Service tab of System Manager. In Quick Configuration,
setup the “IP of Rx/Tx
backup streams” to the
proNAS IP address that
will be used as the
channel for proBackup.
The “Port of Rx/Tx
backup streams” is set
to 1089 by default. If
this port is already used,
assign another port.
Configuration Guide
127
ProNAS 1.1.x
After setting the Quick Configuration options, start the proBackup service. When the
proBackup service is in “Running” status, login to proBackup Java GUI can be done.
The default LVs proBackup
Device
and
proBackup
Extended Device will also
be created.
To login to proBackup java
GUI, open web browser
then type the proNAS IP
address.
Click
the
proBackup icon on the
lower right side of the page.
The proBackup page will be
displayed. Click “Start Java
Web”.
Enter the login account and password.
NOTE: All the backups of an account are lost forever if it is deleted.
128
Configuration Guide
ProNAS 1.1.x
Please make sure such action before doing it.
NOTE: It is advised that only the organization’s privileged persons
can assume the role of administrator since it can restore all others’
data, which may contain sensitive information.
The proBackup Java GUI Welcome screen will be displayed. You can view the recent
proBackup operations and existing backup plans in the Welcome screen. To learn about
proBackup release version, click the About tab.
5.3 Create Backup Plan
Configuration Guide
129
ProNAS 1.1.x
To create backup plan, either click the “Create Plan” button in the proBackup main
screen or click the “New” button in Plan Manager.
The General tab of Plan Manager will be displayed. Fill in the required fields. Some
information about Local Host and proBackup Server are also shown.
130
Configuration Guide
ProNAS 1.1.x
The Configuration options:
‹
‹
‹
‹
‹
‹
Plane Name – Enter the backup plan name.
Compressed – If checked, the backup will be in compressed format.
Backup Entry Home Directory – Click the “…” button then select the directory
when data will be backed up.
Backup File/Directory Entries – Click the “…” button. Select the files and/or
directories to be backed up then click “>>” button to add them to the backup list.
Click “OK” to go back to General tab.
Purpose – Enter additional information in this optional field.
Memo – Enter additional information in this optional field.
Configuration Guide
131
ProNAS 1.1.x
After completing the
necessary information,
click “Save” button. The
Backup Plan will be
saved.
Function buttons in the General tab.
‹
‹
‹
‹
‹
Refresh – Refresh the information about the current backup plan.
Enable – Activates the backup plan schedule. When enabled, a “Disable” button
will appear which can be used to deactivate the backup schedule.
Delete – Deletes the current backup plan.
Run – Execute the backup plan immediately.
Edit – Use this to change settings in the backup plan.
To add schedule in the Backup Plan, click the “Edit” button then select Schedule tab.
Configure the Schedule options then click “Save” when done.
132
Configuration Guide
ProNAS 1.1.x
Schedule options:
‹
‹
‹
‹
‹
‹
‹
Start Date – The starting date when the backup will be done. This usually
defaults to the current date. Click the “…” button. A calendar will be displayed. To
change the Start Date, select a new date in the calendar.
Run At – The preferred time to run the backup. To change the Run At time, click
the pull-down arrow then select the preferred time.
Expired Date – The ending date for the backup. To change the Expired Date,
click the “…” button then select in the calendar the preferred last date of backup.
How often to take a backup? (Days/Round) – The number of days that will
pass before a differential backup will be done.
A cycle begins with a full backup and follows rounds of differential
backup – Enter the number of differential backups that will be made before
starting a new full backup.
How many recent cycles of backups are preserved? – Enter a number which
is the total number of backup cycles that will be preserved. A backup cycle starts
with a full backup and ends with the last differential backup before the next full
backup. When the number of cycles in a schedule has been reached and a new
cycle is started, the oldest backup cycle will be automatically removed.
Preview Schedule – Click this button to update the calendar schedule.
¾
¾
Full Backup – archival backup; all files are copied to a backup storage
device
Differential Backup – backup only the data files that have been modified
since the last full backup
Click “Save” to update the schedule settings. Then click “Enable” to activate the
backup schedule.
The History tab shows a
log or list of operations
that have happened in
proBackup such as
backup or restore
operation. To delete an
entry in the history list,
select the item in the list
and click “Delete”.
Configuration Guide
133
ProNAS 1.1.x
To view detailed information about the backup, double-click the item from the History
tab.
“Log details” is used to display detailed information about the execution process.
“Error log” will display errors that happened during the execution process.
“Search” will allow you to search for a string currently displayed in the Message
screen.
“Restore” will allow you to restore a backup.
Another alternative to do backup or restore is to use the Backup Wizard and the
Restore Wizard. Click proBackup in the left tree node. The Welcome screen will be
displayed where the Backup Wizard and Restore Wizard can be used.
134
Configuration Guide
ProNAS 1.1.x
5.4 Restore Backup
To restore a backup, double-click the backup item from the History tab. The Execution
Log Detail window will appear.
Click “Restore”. Then input the destination where the data will be restored. Or click the
“Browse” button then select the destination directory or folder where data will be
restored. Click “Ok” to start the restore process.
Configuration Guide
135
ProNAS 1.1.x
5.5 Account Detail
Under Plan Manager, click the account name to view information about the account.
136
Configuration Guide
ProNAS 1.1.x
Chapter 6 proNAS HA (Optional Function)
6.1
Introduction to proNAS HA
proNAS HA (High Availability) provides solution for business continuity with automatic
failover which ensures that should a critical server become unavailable - due to failure
or maintenance-related downtime — a replica will immediately provide all services in
its place without the need for time-consuming manual procedures.
The core processes of ProNAS HA are implemented as two mutual-guarded fail-safe
proNAS services. They can be manipulated by accessing the Services tab in the
proNAS System Manager node. The dual service architecture of ProNAS HA prevents
ProNAS HA from being the single-point-of-failure of the server cluster.
When a server is down or unavailable, ProNAS HA switches the critical operations of
that server over to the peer server automatically. The switch over procedure can also
be triggered manually to handle scheduled downtime more gracefully and user
transparently. ProNAS HA can be manually instructed to switch over the critical
operations of a server to the peer server. Users can then perform upgrade,
replacement, or maintenance to the hardware and software of that proNAS server. The
critical operations of a server can be configured as auto-switch back. After those
critical operations were taken over by the peer server, ProNAS HA can switch them
back to their original active server when the active server becomes available again.
Auto-switch back ensures that the original load distribution between the two servers
will be resumed immediately when possible.
proNAS HA provides:
¾
Manual or auto-triggered failover to a standby server.
¾
Supports manual or automatic failover back to the original server when ready
¾
Real-time replication minimizes potential data loss
Configuration Guide
137
ProNAS 1.1.x
6.2
Getting Started with proNAS HA
Before Configuring High Availability
Before attempting to configure two proNAS HA as a High Availability pair, check the
following requirements:
1. Each proNAS server box must have a different and unique hostname. (It is highly
recommended to use the same NAS model.)
2. Each proNAS box must have at least two static IP addresses.
3. Must have a reliable heartbeat, private net Ethernet is required, serial RS232 is
optional.
4. proNAS HA services must be started in both proNAS servers.
5. The maximum number of logical volumes that can be created under HA is 32.
6. proNAS HA does not support logical volumes larger than 2TB. Users can create
and extend volumes larger than 2TB but this cannot be used in proNAS HA.
7. Changing hostname and IP addresses when proNAS HA is running is not allowed.
8. Snapshot function is disabled under HA.
9. Be sure there are no scheduled snapshot task enabled either on each proNAS box.
Setting up a private network:
Private net is a communication channel between the two proNAS box through which
they exchange information about their states (heartbeats). proNAS supports two
private network, TCP/IP Socket and RS232 Serial Port.
To setup TCP/IP private net: Connect a dedicated network into Ethernet1 adapter. You
may use a crossover cable. Ethernet0 serves as your public net.
To setup RS232 Serial Port private net: Connect a serial cable to either Com1 or Com2
for both proNAS box then configure it under the "Serial Port" tab on System Manager.
NOTE: It is recommended to use both TCP/IP and RS-232 for your
private net. Private net IP will be used for replication and RS-232
for heartbeat.
NOTE: Some proNAS models have eth0 Fast Ethernet port. In order
to have faster access to your proNAS, use the Gigabit Ethernet port
(eth1, if eth0 is Fast Ethernet) as your public net; that is where the
users access your proNAS. Then use eth2 as your Private Net.
138
Configuration Guide
ProNAS 1.1.x
6.2.1 Hardware Aspect
Active server: proNAS HA server that performs cluster-protected operations.
Backup (Standby) server: proNAS HA server that can takeover the critical operations
of an active server when the active server is down or unavailable.
Private net: Private net is a dedicated channel for servers to exchange their operating
status (i.e., heartbeat message).
Types of Private Net Available:
¾
¾
TCP/IP socket: Ethernet network running TCP/IP protocol. Each server must
install a dedicated IP to attach to the private net.
RS-232 serial port: One free serial port per server. A null modem cable must be
installed to connect the serial ports of the two servers.
Public net: Public net is the paths for networked clients to access cluster- protected
resources.
Network Configuration for High Availability Pair
The following diagram illustrates the network configuration for a High Availability pair:
Multi Port Switch
Public Net
Private Net
Private Net
Public Net
RS232 Serial Ports
Active Server
proNAS HA Resource
Virtual IP
Backup Server
Configuration Guide
139
ProNAS 1.1.x
6.2.2 Procedure for Setting Up proNAS HA
Setting up a server cluster:
Below are the basic steps in setting up a server cluster:
1.
2.
3.
4.
Configure the hostname for both proNAS servers (must be unique).
Configure two static IP addresses for each proNAS server.
Set up private net. At least the private net IP must be configured to start cluster.
Start proNAS HA service for both proNAS servers. You may do this under System
Manager then Services tab, highlight proNAS HA service then click Start. proNAS
HA node will then appear on the left tree after it starts successfully.
5. On the designated Active Server, go to proNAS HA->"General Settings".
6. On the "General Setting" tab, click "Edit" button. Input the Peer Server hostname
then select "Active(local-host) – Standby(peer host) Mode" under the
Cluster mode. Click "Save".
NOTE: The Cluster Mode of Backup Server must be configured as
“Standby(local host) – Active(peer-host) Mode” (see Step 10).
Other configuration options:
Computer Name:
Local Server: The hostname of the Active or Primary server
Peer Server: The hostname of the Backup or Secondary server
140
Configuration Guide
ProNAS 1.1.x
Reference IP:
Enable Reference IP Checking – Select this option to enable reference
IP checking. A Reference IP is an IP address that the proNAS
HA service will check when the heartbeat channel(s)
between the two servers are lost. This IP will be used as a
reference point to device whether the network really has a
problem before doing failover or takeover. HA will ping the
local and virtual IP address of proNAS, and for any reason
that this fails, HA will ping this reference IP as a double
check. If ping still fails, proNAS HA will proceed with failover
or takeover. The IP of a router or any network device which
is always online can be used as a Reference IP.
IP Address – Enter the IP address of the Reference IP to check the
availability of the servers.
Event Log:
Level – Select the type of logging that will be used for proNAS HA service.
Default is Normal which shows operation processes. Other
option is Trace, which shows operation and traceable
processes.
Preserved Days – Select the number of days that the log will be
preserved before deleting.
Operational Preferences:
On Server Shutdown, failover the resource groups automatically –
When enabled, the resource groups will be failed over to the
other server when this server shutdown.
On Server Startup, start the cluster system automatically – When
enabled, the cluster system will be started automatically
when this server starts up.
Configuration Guide
141
ProNAS 1.1.x
7. Back to proNAS
HA node, click
"Get Peer IPs"
button. The IP
addresses of the
peer server will
then be displayed
in the status info
table. Be sure
that it gets the
peer IP addresses!
If it fails, check
again the
hostname that
you supplied in
step 6.
Buttons:
Stop Cluster
Stop Cluster Operation.
Start Cluster
Start Cluster Operation.
Get peer IPs
Get the IP's of the peer server and display it in
the host peer table.
Network Test
Tool for testing network IP address (e.g ping ip)
Volume Status
Shows the current Replication status of logical
volumes.
NOTE: When HA is already configured and Cluster is in operation,
you can see the current replication status of logical volumes by
clicking “Volume Status”.
Volume Status Example 1: All logical
volume Replications are consistent
142
Configuration Guide
ProNAS 1.1.x
Volume Status
Example 2:
Replication of one
logical volume is
initializing.
8. Go to Private Net node and click "Ethernet#1". Set the local and peer IP address,
check "Auto Enable on Starting Cluster" then save. Be sure not to select the
public IP (eth0 IP address) for both proNAS servers.
Private Net: Ethernet
Local/peer
Port Number
Specify an unused TCP port for each server to receive the
heartbeat sent from the peer server. The default value is
5000.
Local/peer IP
Address
Specify the IP Addresses of the network interface cards that
constitutes both ends of the private net. These IP addresses
must be on a separate subnet from the public net.
Heartbeat
Interval
Specify the period of time between two consecutive
heartbeats.
Acceptable
Consecutive
Each server will keep counting and timing the heartbeats
received from the peer server. If the number of times a
Configuration Guide
143
ProNAS 1.1.x
Heartbeat
Loses
server fail to receive the heartbeat in time exceed this
threshold, the peer server will be considered down or
unavailable. The resource group of the peer server will be
taken over.
Auto enable
on starting
cluster
This option is disabled by default. This private net will be
enabled automatically when starting cluster. Add the
checkmark to enable this option.
9. Configure private net "RS232#1", if you setup serial port as an additional private
net.
Private Net: RS232
To use RS232 as a private net, you need to configure Serial ports settings in
proNAS System Manager > Serial Ports tab, select either COM1 or COM2 for
proNAS-HA.
Local Serial Port
Specify an unused serial port for each server to receive
the heartbeat sent from the peer server.
Baud Rate
Specify the Baud Rate of the selected serial ports.
Heartbeat
Interval
Specify the period of time between two consecutive
heartbeats.
Acceptable
Consecutive
Heartbeat Loses
Each server will keep counting and timing the
heartbeats received from the peer server. If the
numbers of times a server fail to receive the heartbeat
in time exceed this threshold, the peer server will be
considered down or unavailable. The resource groups of
the peer server will be taken over.
Auto enable on
starting cluster
This option is disabled by default. This private net will
be enabled automatically on starting cluster. Users can
add the checkmark to enable this option
10. Follow the same steps from step 5 to step 9 to configure your standby Backup
Server except you need to select "Standby(local host) – Active(peer-host)
Mode" as the Cluster Mode.
11. Click "Start Cluster" button.
144
Configuration Guide
ProNAS 1.1.x
12. Wait until the
status of the local
and peer server
are in be standbystandby mode
respectively. The
status of the
private net must
also be "Enabled
and Healthy". If
this is not the
status, check and
repeat previous
steps.
13. Go to "Resource Group Manager" then press "Add Resource Group".
The Resource Group Manager of proNAS HA is used to manage resource
groups. Users need to configure resource groups only on one of the servers,
usually the Active server. proNAS HA will automatically synchronize the status
of resource groups between both servers. Note that users are prohibited to
create or remove resource groups unless proNAS HA are running on both
servers and at least one of the private net is functioning.
Buttons:
Add
Add new resource group member. User can specify the
Resource
name of the resource group. This name must be unique
Group button for the resource groups within the cluster
Switch All
Resource
Groups from
Peer
This is to manually takeover the all resource groups from
the peer server. Users can manually takeover resource
groups from the peer server to perform maintenance or
troubleshooting on the active server. This button will be
displayed only if resource groups are bring in.
Switch All
Resource
Groups to
Peer
This is to manually failover the all resource groups to the
peer server. Users can manually failover resource groups
to the peer server to perform maintenance or
troubleshooting on the active server. This button will be
displayed only if resource groups are bring in.
Configuration Guide
145
ProNAS 1.1.x
14. Input a resource group name. You may check "Auto Switch back" or "Auto Bring
In" then click “Save”.
Resource Group Properties:
Resource Name
A unique name for identifying the resource group
Active Server
The active server of the resource group
Backup Server
The peer server is automatically display
Local Status
The status of the local server
Peer Status
The status of the peer server
Auto-switch
back
An option for enabling the Group to be switched back
from the Backup server to the Target server
automatically when the Target Server is available
again.
Auto Bring In
An option for enabling the resource group to be
brought in automatically when Cluster is started.
Buttons:
Bring in
The selected resource group will be activated and
brought under the protection of proNAS HA. This
button is only visible if there are resource group
added.
Bring out
The selected resource group will be brought out from
the protection of proNAS HA. A resource group can be
brought out of cluster to perform maintenance or
troubleshooting. This button is visible if resource
groups are brought in.
15. Click the resource group name on the left tree node then press "Add Resource".
146
Configuration Guide
ProNAS 1.1.x
16. On the "Basic Settings" tab, input a resource name.
Resource Basic Setting:
Resource Name
A unique name for identifying the resource group.
AC interval
(Availability Check
Interval)
A time interval for proNAS HA to check the
availability of the resource group periodically.
AC Retry
(Availability Check
Retry)
The number of times for proNAS HA to check the
availability of the resource group periodically.
Stop timeout
Specify the period of time for resource startup and
stop. If a server fail to receive the heartbeat in
time exceed this threshold, the peer server will be
considered down or unavailable. The resource
group of the peer server will be taken over.
Skippable if
releasing resource
fail
This option is disabled by default. Basically all of
the resource group of the peer server will be
taken over when the peer server fails. Users can
add the checkmark to enable this option. The
failover will be taken even if resource releases fail.
17. On the "IP Address Resource" tab, select the original IP address (eth0 IP) for both
local and remote proNAS, enter an active IP address, active subnet mask and
then save. Active IP address is the virtual IP address.
IP Resource:
Original IP Address Choose the original IP Address for the local and
peer server.
Active IP Address
Type an IP Address (virtual IP) for client-end
applications to access specific resources on the
NAS Target Server.
Active Subnet Mask The subnet mask used by the Active IP Address.
Configuration Guide
147
ProNAS 1.1.x
18. Click the resource group name on the left tree node then press "Bring In". The
resource name will be brought in.
19. The Cluster Servers will be in Active – Standby mode.
148
Configuration Guide
ProNAS 1.1.x
6.3
ProNAS HA Properties
Status Properties
Users can monitor all the resources from the proNAS HA Status Pad. Users can monitor
the status of the servers, the resource groups and the private net in real-time. The
status after the Cluster Service starts running on both servers.
The status icons in status bar and their respective meaning:
- Active Mode
- Error Mode
- Fail Mode
- Offline Mode
- Standby Mode
- Startup Mode
The private net status:
The colored lines between the servers indicate the status of the private net. Status is
also displayed in the function bar.
‹
Gray line
‹
Red line
‹
Blue line
Only one end of the Private Net is created, the other end is not yet
created.
Both ends of the Private Net are established but either one of the
servers can not receive heartbeat message from the peer server.
Both ends of the Private Net are established and both servers are
exchanging heartbeat messages.
Configuration Guide
149
ProNAS 1.1.x
Indicators:
Users can accurately monitor the status of the system such as the License status,
Private Net, Public Net and the resource takeover/failover. When a condition occurs,
the icon will turn red. You will also see a message appear in the Event Log.
Private Net: This icon will turn red if there's a problem with the connection of
the private net.
Public Net: This icon will turn red if there's a problem with the connection of
the public net.
Failover/Takeover: This icon will turn red during the failover or takeover
scenario.
License: This icon will turn red if proNAS HA is not registered.
Host box: Display the status of Local and Peer Server
Resource Group box: Display the resource group status
Buttons:
Stop Cluster button
Stop Cluster Operation.
Start Cluster button
Start Cluster Operation.
Get peer IPs button
Get the IP's of the peer server and display it in the host
peer table.
Network test button
Tool for testing network IP address (e.g ping ip)
6.4
Extending a Logical Volume in HA
Extending a logical volume while in cluster is basically not allowed same as in
Replication. However, here is the workaround.
1.
2.
3.
4.
5.
6.
7.
150
Stop Cluster
Stop HA service for both proNAS.
Abort the replication of the logical volume that needs to be extended.
Extend the logical volume on the Active server.
Removed the logical volume (the replica) on the Standby server.
Start HA service for both proNAS.
Start cluster.
Configuration Guide
ProNAS 1.1.x
6.5
Clear All HA Configuration
A function button “Clear All HA Configuration” is provided to remove all proNAS HA
configuration. This is located in General Setting tab.
When you clear the HA configuration, you have an option to clear all logical volume
Replication. If you don’t clear the all Replication, only HA configuration will be reset, and
all logical volumes will still have Replication.
After you clear all HA configuration and clear all Replication, you can re-configure
another HA. This is normally used when one of the proNAS servers has failed and you
want to reconfigure HA for another (new) proNAS server using the remaining proNAS
server.
IMPORTANT: Before you clear all HA configuration, make sure the
cluster is stopped (all nodes are “down”).
To remove all existing proNAS HA configuration:
1. Select the proNAS node name, click proNAS HA, and select General Setting. Click
“Clear All HA Configuration”.
Configuration Guide
151
ProNAS 1.1.x
2. A warning message to clear all HA configuration will be displayed. Click “Yes” to
proceed.
3. A warning message to remove all replication in logical volumes will be displayed.
Click “Yes” to remove Replication in all logical volumes, or “No” to just clear HA
but replication of logical volumes still exists.
4. An information message will be displayed. Click “OK” to close the message. You
can verify the proNAS HA Event Log for further information.
Example of Replication
status after selecting
“Yes” to remove all
replication:
152
Configuration Guide
ProNAS 1.1.x
Example of Replication
status after selecting “No”
to retain all replication:
6.6
License Registration
To apply ProNAS HA license codes and register them to ProNAS HA, users must first
get the S/N of the two servers. Forward the S/N to your local ProNAS HA provider.
Then Input the acquired License and click “Register” button. Users can now put ProNAS
HA to work.
Configuration Guide
153
ProNAS 1.1.x
6.7
Event Log Properties
All the messages generated by ProNAS HA will be displayed in the Event Log. The
messages can help users to identify the possible reasons that prevent ProNAS HA from
operating normally.
154
Configuration Guide
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertising