ProNAS Configuration Guide

Revision 1.1

P/N: PW0020000000203

Chapter 1
1.1 1.2 1.3

Introduction of proNAS
proNAS Key Component ...............................................................1-1 Setting IP address through Web Browser .....................................1-2 Installation Phases of the Installation............................................1-4

Chapter 2

NAS Device Manager (SN-3143H, SN-3168H, SN-4120H)

2.1 2.2 2.3 2.4 2.5 2.6 2.7 2.8 2.9 2.10 Starting NAS Device Manager ......................................................2-1 Quick setup ...................................................................................2-2 Create Array and Slice ..................................................................2-4 LUN Mapping ................................................................................2-6 Delete Slice and Array...................................................................2-7 Array Expand.................................................................................2-9 Array Check...................................................................................2-10 Scrub Operation ............................................................................2-10 Disk Clone .....................................................................................2-13 Disk Self Test.................................................................................2-15

Chapter 3

NAS Device Manager (DN-405H, SN-1405H, SN-2805H, SN-2803H, SN-2123H, SN-3163H)

3.1 3.2 3.3 3.4 3.5 3.6 3.7 3.8 Starting NAS Device Manager ......................................................3-1 Quick Setup...................................................................................3-3 Create RAID Set & Volume Set.....................................................3-5 Delete RAID Set ............................................................................3-8 Delete Volume Set.........................................................................3-8 Check Volume Set.........................................................................3-9 Modify Volume Set ........................................................................3-10 Expanding RAID Set .....................................................................3-11

Chapter 4
4.1

proNAS Manager
Volume Manager ...........................................................................4-1 4.1.1 Volume Group Management .............................................4-2 4.1.2 Logic Volume configuration ...............................................4-4 4.1.3 Volume Snapshot ..............................................................4-5 4.1.4 Volume Replication............................................................4-6 Network Manager ..........................................................................4-9 4.2.1 Network Setting and Trunking ...........................................4-9 4.2.2 Internet Gateway ...............................................................4-11 4.2.3 SNMP/MRTG.....................................................................4-12 Account Manager ..........................................................................4-13 4.3.1 External Accounts Integration............................................4-13 4.3.2 Local Account and Group Management ............................4-14 4.3.3 Import Accounts.................................................................4-18 Share Manager..............................................................................4-19 4.4.1 Share Management and Protocol Setting .........................4-19 4.4.2 Privilege (ACL) ..................................................................4-21 4.4.3 Sub-Folder Management...................................................4-22 4.4.4 Default Share.....................................................................4-23 System Manager ...........................................................................4-24 4.5.1 System Information............................................................4-24 4.5.2 Firmware Upgrade.............................................................4-25 4.5.3 Report................................................................................4-25 4.5.4 Time Setting.......................................................................4-26

4.2

4.3

4.4

4.5

4.6 4.7 4.8

4.5.5 Serial Port..........................................................................4-27 4.5.6 Reboot ...............................................................................4-28 4.5.7 Service...............................................................................4-29 4.5.8 Hardware Health................................................................4-31 Backup Manager ...........................................................................4-33 4.6.1 Configure Backup Plan......................................................4-33 4.6.2 proNAS Configuration Backup ..........................................4-37 Log Manager .................................................................................4-38 Event Manager ..............................................................................4-39 4.8.1 E-mail Notification Setting .................................................4-39

Chapter 5
5.1 5.2 5.3 5.4 5.5

File Manager
Introduction of File Manager .........................................................5-1 Logon to File Manager ..................................................................5-2 Directory and Upload Function......................................................5-3 Access Right and Group Access Right .........................................5-4 Change Password and Logout......................................................5-5

Chapter 6
6.1 6.2 6.3 6.4

proBackup
Introduction of proBackup .............................................................6-1 Administrator Logon ......................................................................6-1 6.2.1 Quota Review Management ..............................................6-1 6.2.2 Archive Plan for proBackup System..................................6-5 Backup Files..................................................................................6-7 Restore Files .................................................................................6-11 6.4.1 Restore a backup ..............................................................6-11 6.4.2 Restore some of files in a backup .....................................6-14 6.4.3 Delete backups..................................................................6-16

Chapter 7
7.1 7.2

proNAS HA ( Option Function )

Introduction of proNAS HA............................................................7-1 Getting Started with proNAS HA ...................................................7-1 7.2.1 Hardware Aspect ...............................................................7-1 7.2.2 Procedure to Set up proNAS HA.......................................7-3 7.2.3 Start proNAS HA Service...................................................7-4 proNAS HA Properties (Status and Indicator) ...............................7-5 General Setting .............................................................................7-7 7.4.1 General Setting Properties ................................................7-7 7.4.2 License Registration ..........................................................7-8 Setting up Private Net ...................................................................7-9 7.5.1 Ethernet .............................................................................7-9 7.5.2 RS232................................................................................7-10 Resource Group Manager.............................................................7-11 7.6.1 Add Resource Group Properties .......................................7-11 7.6.2 Resource Group Properties...............................................7-12 7.6.3 Add IP Resource Type Properties .....................................7-13 7.6.4 Resource Type Basic Setting Properties...........................7-13 7.6.5 Configuration for IP Address Resource Group ..................7-14 7.6.6 Resource Group with Group Properties ............................7-15 7.6.7 Bring in Resource Group Properties .................................7-16 7.6.8 Resource Group Manager Properties When Bring in........7-16 Event Log ......................................................................................7-17

7.3 7.4 7.5 7.6

7.7

Appendix A --- Glossary

Chapter 1 Introduction of proNAS

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 Component

NAS Device Manager: Provides configuration of physical hard disks with Hardware RAID Controller. proNAS administration manager: Provides several NAS system manager tool to ease the administration job. Volume Manager: Configuration of volume group and logic volume and supports the function of volume snapshot and replication Account Manager: Local and external account configuration. Large accounts import. Backup Manager: Supports system configuration backup and Setup the backup plan for data backup. Share Manager: Share configuration and ACL setting System Manager: System configuration and firmware upgrade Network Manager: Network information and trunking. Log Manager: System log List. Event Manager: Setup system actions when event occur.

File Manager: User logon mode to perform file management as well as the share folder access control for share owner. proNAS HA: Option function of proNAS. Provide function of High Availability with Active-Standby mode. proBackup: Provides desktop backup solution with web base GUI for users. Each function of these component would be described in the following Chapter.

1-1

1.2

Setting the IP Address using the Web Browser

Note: You must install Java 2 Runtime (J2RE) 1.4.2 or later before you start using the proNAS management console. (Free download from: http://java.sun.com/j2se/index.jsp)

1. To connect to NAS, change the settings of your computer as follows: a. Click Start Programs Accessories Communications Network and

Dial-up Connections. b. In the Network and Dial-up Connections dialog box, double-click on the Local Area Connection icon. c. In the Local Area Connection Status dialog box, click Properties. d. In the Local Area Connection Properties dialog box, double-click on Internet Protocol (TCP/IP). e. In the Internet Protocol (TCP/IP) Properties dialog box, select Use the following IP address. f. Enter the IP address, Subnet mask, and Default gateway. g. To save the settings, click OK.

2. Open the Web browser. 3. Enter the following URL in the address bar: http://172.16.0.1 Then press Enter. Table 1 NAS Default Values Entity LAN IP address Netmask IP address Hostname Username Password Default Value 172.16.0.1 255.255.0.0 proNAS admin proware

4. In the page that opens, click Admin Login command button to enter the NAS administration page.

1-2

Figure 1.1 START button on the first proNAS

Figure 1.2 Login Screen

Enter Account as admin and password as proware and click on Logon command button.

proNAS main screen will get displayed which will have 1. NAS device manager and 2. proNAS.

1-3

1.3

Installation Phases of the Installation: An Overview

The installation and configuration of a ProNAS can be seen to consist of five phases. 1. Phase One: Setting up and Configuring the Hardware RAID Prior to installing the ProNAS you will need a basic hardware setup in place. You can find the supported hardware detailed in the RAID configuration guide. For ProNAS subsystem (model: SN-3143H, SN-3168H, SN-4120H), Please reference chapter 2 to setting up and configuring the Hardware RAID. chapter 3 to setting up and configuring For ProNAS subsystem (model: DN-405H, SN-1405H, SN-2805H, SN-2803H, SN-2123H, SN-3163H), Please reference the Hardware RAID. 2. Phase Two: Configuring ProNAS and its Components with proNAS manager, "proNAS Manager on Chapter 4 describes the procedures for installing proNAS. When you proNAS, you are: Create a VG with "Volume Manager" that described on Chapter (4.1.1) to (4.1.2). Setting up the network environment with "Network Manager" that described on Chapter (4.2.1). Create or import accounts with 'Account Manager" that described on Chapter (4.3) Setting up the Shares used by accounts and protocols, hat is described on Chapter (4.4) User can get start using proNAS subsystem to store data from the Windows or Unix client with NFS or CIFS(Network Neighbor) permission. 3. Phase Three (optional): Maintain and check ProNAS system Maintain system (4.7) and (4.8) Backup system configuration and data by using "Backup Manager" on Chapter (4.6) 4. Phase Four(optional): Setting up proNAS for H.A. (High Availiable) environment Reference Chapter 7 to setting up proNAS HA 5. Phase Five(optional): Users can Store and Backup data into proNAS system Store data into proNAS system by using "File Manager" on Chapter 5 Backup data into proNAS system by using "proBackup" on Chapter 6
1-4

by using "System Manager" on Chapter (4.5)

Check system status by using "Log Manager" and "Event Manager" on Chapter

Chapter 2. NAS Device Manager (SN-3143H, SN-3168H, SN-4120H)

NAS Device Manager provides the function for RAID planning and operation. If your proNAS subsystem model is SN-3143H, SN-3168H and SN-4120H, please refer to the description of this chapter.

2.1

Starting NAS Device Manager

1. Running proNAS and choose NAS Device Manager in the left tree node. 2. Logon NAS Device Manager and enter Account as admin with default password prowareThe administrator account gets full privilege to set up and modify all the configuration of RAIDwe recommend you to change the default password. 3. Mount RAID Subsystem Choose the Subsystem Unit and press Mount Subsystem button

4. System will display the Mount Subsystem window. Please connect Normal Modem Cable to host com1 port and controller Monitor Port then set the Port field to /dev/ttyS0 and Baud Rate to the speed of controller. After the above configuration, press OK button.

2-1

2.2 Quick Setup

1. Choose the left tree node to Storage Manager to Array 1 to create the new Array. Press Edit button.

2. Select Joined Slots field

to select the disk number to create Array.

3. Select RAID Level field to choose the RAID Level

2-2

4. Click Create Slice to create Slice

5. Click Save button, system will auto restartthe Array configuration will be ready after reboot.

2-3

2.3 Create Array and Slice

1. The same steps as section 2.2 , Setps1 ~ 5 2. Double-Click the mouse to Slice 0 capacity and enter the size of capacity, press Enter.

3. Lun Mapping Host 1 & 2 can set up the Slice to be detected from which SCSI Hostthe number is from LUN 0 to 127 , and Disable LUN Mapping

4. If theres space left to create another Slice, please press Create Slice button again.

2-4

5. Detect the Slice capacity former created Available Space - Already Array Used Space, you can get the available spaceand enter to the field of Slice 1and choose the LUN Mappingpress Save button to complete the configuration.

2-5

2.4 LUN Mapping

1. In the Array 1 Information tagpress Edit button to set up/ modify Mapping, then press Save button. LUN

2. To check the setting of LUN Mapping you can choose By Slices or By Hosts

2-6

2.5 Delete Slice and Array

1. In Array 1 Information tag

2. Press Edit buttondouble-click the mouse on the slice you would like to deleted.

3. Press Delete Slice buttonand press Save button to complete the setting. Please be informed that you can only delete the slice from to last one to the first one in backward order. You can not choose the certain slice to delete it nor delete the first one.

2-7

4. Delete ArrayMove to Array List in the Storage Managerdouble click the mouse on the array list which you would like to deleted, press Erase button and system will display the dialog box Are You Sure to Erase Array This will make data lose!!! . If yes, please press OK button and system will delete the Array if no, please press Cancel button. Notice: If you press OK button, all the data of the Array will be deleted and could not be save back. Be careful to do this action.

2-8

2.6 Array Expand

1. Please make sure that there is free disk in the Subsystem Unit Free Disk and Free Disk capacity is larger than or the same as the capacity of the disk. 2. Move to Array List in the Storage Manager. 3. Double click the mouse on the Array name which you would like to expand. 4. Press restart. Expand button, system will display the Expand Array dialog box choose the disk number to expand, press OK button , the controller will

5. System will display the expanding progress in the status field.

2-9

2.7 Array Check

1. Move to Array List in the Storage Manager. Double click the mouse in the Array which you would like to perform the Array Check. 2. Press the Check button system will perform Array Check. 3. If you would like to abort this operation, please press Cancel Check button.

2.8 Scrub Operation

1. Move to Array List in the Storage Manager. Double click the mouse in the Array which you would like to perform Array Scrub. 2. Press scrub button, system will perform Array Scrub. Notice: You can also check with the option Overwrite Parity in Global Setting. 3. If you would like to abort this operation, please press Cancel Scrub button.

2-10

4. Scrubbing Schedule (1) (2) Move to Array List in the Storage Manager. Double click the mouse in the Array which you would like to perform Array Scrub. Press Scrub Schedule button, system will display the window of Scrubbing.

(3)

Check the box Enable Schedule Scrubbing to configure the Schedule.

Scrub

(4)

FrequencyThis Week OnlyOnly perform schedule scrub in this week. Every 1 ~ 52 WeekTo perform schedule scrub on each week of the year (1 ~ 52 ).

2-11

(5)

OnTo perform Schedule Scrub on what day of the week.

(6)

AtTo perform Schedule Scrub at what time of the day.

Please the Save Button to complete the above setting

2-12

2.9 Disk Clone

1. Move to Subsystem Name (1) (2) Prepare free hard drive which capacity is larger than or the same as the source disk. Move to the Slot List tag of the Subsystem Name.

(3) (4)

Press the Clone Disk buttonsystem will display the window of Clone Disk Select Mode Permanent Clone Keep source disk after clone disk Swap after CloneDo not keep source disk after clone disk StopAbort Clone operation Replace Replace source disk

(5)

SourceSelect the slot disk for Clone operation

2-13

TargetSelect Target Disk for Clone operation.

2. Press OK button to complete the above setting to perform Clone operation.

2-14

2.10 Disk Self Test

1. Move to the Slot List tag of the Subsystem Name. 2. Press the Disk Self Test buttonsystem will display the window of Disk Self Test. 3. ModeShort Self TestQuick SMART scan to Disk Extended Self TestFull SMART scan to Disk Stop DSTAbort SMART scan operation

4. SourcePerform SMART scan to certain disk or all disk

5. Press OK button after the above setting to perform Disk Self TestYou can check the system progress in the status field.

2-15

2-16

Chapter 3 NAS Device Manager (DN-405H,SN-1405H,SN-2805H,SN-2803H,SN-2123H,SN-3163H)

If your proNAS subsystem model is DN-405H,SN-1405H,SN-2805H,SN-2803H,SN-2123H and SN-3163H, please refer to the description of this chapter.

3.1 Starting NAS Device Manager

1. Running proNAS and choose NAS Device Manager in the left tree node. 2. Logon NAS Device Manager and enter Account as admin with default password prowareThe administrator account gets full privilege to set up and modify all the configuration of RAID, we recommend you to change the default password. 3. Mount RAID Subsystem Choose the Subsystem Unit and press Mount Subsystem button

4. System will display the Mount Subsystem window. Please connect Normal Modem Cable to host com1 port and controller Monitor Port, then set the Port field to /dev/ttyS0 and Baud Rate to the speed of controller. After the above configuration, press OK button.

3-1

3-2

3.2 Quick Setup

1. Press Storage Manager in the left tree node and press Quick Setup button to create new RAID Set.

2. Choose the number of disk to join in the RAID set . disk automatically.

If you do not select all

the disks to the RAID set, the reminding disks will be set to be the Hot Spare

3. Select the RAID Level, if you would like to initial the setting directly, please check the box of Background Init and press the OK button.

3-3

4. After the above setting, please switch to Raid Set# 00 under the Storage Manager, and you can check the initializing status in the status field.

3-4

3.3 Create RAID Set & Volume Set

1. Move to Storage Manager to create new RAID Set.

2. Press Create RS button and system will display the following windows to Select Raid Set Member Disks. Choose the disk you would like to join to RAID set and press OK button.

3. After complete the configuration of RAID set, you can see + node before Storage Manager, move to Raid Set list to create Volume set.

3-5

4. Press Create VS button and select the RAID level.

5. Select the Stripe Size, the default value is 64

3-6

6. Areca Volume Set SpeedTo adapt the speed of Volume Set to Host.

7. SCSI ChannelVolume Set Mapping to Host Channel.

0&1 For Cluster can

set the Mapping to 2 host channel. After the above setting, press OK Button.

3-7

3.4 Delete RAID Set

1. Move to Storage Manager, and choose the RAID Set you would like to delete, and press Delete RS button. System will display warning message after you press this button. If you press Delete RS, all the data of the volume set under RAID set will be deleted. If you would like delete RAID set, please press OK button or press Cancel button to leave the window.

3.5 Delete Volume Set

Move to RAID Set #xx and choose the Volume Set you would like to delete, and press Delete VS button. will be deleted. If you would like delete volume set, please press OK button or press Cancel button to leave the window. If you press delete Volume Set, all the data under the Volume Set

3-8

3.6 Check Volume Set

Move to RAID Set #xx and choose the volume set you would like to check. If you would like to perform this, the Volume Set Status must be Ready

Press Check VS button and system will begin to check Volume Set

3-9

3.7 Modify Volume Set

1. Move to RAID Set #xx and choose Volume Set you would like to modify. If you would like to perform this function, the Volume Set Status must be Ready.

2. Press Modify VS button, the available modify items are: Volume Set Name Volume Set SpeedVolume Set SCSI Host MappingSCSI ID & LUN MappingWrite CacheTagged Command Queuing

3. Press OK button to complete setting or the Cancel button to leave the window

3-10

3.8 Expanding RAID Set

Move to Storage Manager and choose the RAID Set you would like to Expand. Please be noticed that there has to be Free Disk for this operation, you can check the slot list in the Subsystem name.

1. Press the Expand RS button. Check the free disk to Expand. Press OK button to complete the setting or press Cancel button to leave the window.

3-11

2. After complete the action of Migrating, the status will change to Ready. Move to RAID List and you can see the new disk joined to RAID Set, you can create new volume set under RAID Set #xx .

3-12

Chapter 4 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 developed based on the 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 System Status monitors the health of the NAS subsystem.

4.1

Volume Manager

The Volume Manager is responsible for disk and volume management. You can organize disks into logical volumes. Files and folders can reside on these logical volumes. A volume group consists of one or more disks that could be individual disks or RAID disks created by the RAID Manager. A proNAS volume group cannot be deleted and no disks are assigned in the default configuration. The proNAS volume group holds all default logic volumes such as the home, proBackup device, proBackup Extension device and public .You must add the disks before using the default shares. You can set a file system (XFS) for each proNAS volume group. XFS gives more recovery time to repair a file system in case of damage. The proNAS volume group will dynamically allocate some space from its assigned disks and may fail the allocation if no more disk space is available. Therefore, you must take care that the free space of the proNAS volume group is enough for the extension of home shares. You can create more volume groups to hold project shares. The Volume Manager can perform the following function: Create a VG (volume group) Join disks Reset a VG (volume group) Remove a VG (volume group) Create Volume Create Snapshot Create Replication

4-1

4.1.1

Volume Group Management

Volume Group, (VG) is the logic unit of the composition of logic volume, it can built with one or more than one Disk of Raid Disks created from NAS Device Manager. Each volume group has its own file system; admin can create the logic volume (LV) under the volume group. proNAS VG is the system default VG, it includes the system information and Default LV (Home, Public, proBackup Device, proBackup Extension Device). The first step is that you have to add new disks into proNAS VG and notice that you cannot delete proNAS VG. User can create new Volume on that VG, remove that VG, Join any new disk, Remove any disk and Reset the Volume Group. Create a volume group and Join Disks A. To create a volume group and join disks, perform the following steps: 1. In the proFamily tree, select Volume Manager. When clicked on Volume manager a detailed status of all Volumes gets displayed. Figure 4.1 Volume Manager Screen

2. In the Volume tab click on Create VG command button to create a VG. 3. In the Create New Volume Group dialog box, specify the name of VG select the Unit Size. Click on Save command button.

4-2

Figure 4.2 Create Volume Screen

4. After creation of VG click on Join Disk(s) command button to join disk.

Figure 4.3 Join New Disk Screen

5. All the available disks are listed in the Available Disk(s) list. Select the disks you want to join by checking the check box in the Join column. Remove and Reset volume group If you choose Reset the volume group all the data will be erased, so please make sure that you have already backup the data or you do not want to keep the data. 6. Click OK to close the dialog box.

4-3

4.1.2 Logic Volume configuration To create New Volume double-click on the VG name and click on Create new Volume command button. Specify the parameters, Volume name, and size of Volume. Click on save command button. Figure 4.4 LV Configuration screen

Logical Volume will get created successfully. The user can extend the LV size.

1. To extend the LV size click on Extend LV size. 2. Enter the size, in extend LV screen and click on OK command button.
Figure 4.5 Extend LV Size screen:

4-4

4.1.3

Volume Snapshot

The user can Create Snapshot, Create Replication and Remove the Logical Volume. FEATURES OF SNAPSHOT: 1. Snapshot supports only local destination. 2. Snapshot Logical Volumes is a read only volume. 3. In order to restore data to the original volume, user should copy and paste file from snapshot 4. Volumes to the original volumes. Capacity of snapshot is 10% size of the original volumes. 1. To create a snapshot of the Volume click on Volume name and then click on Create Snapshot command button. Figure 4.6 Create Snapshot screen

2. Specify the Snapshot name and click on Create Snapshot command button. 3. When the snapshot gets created successfully it gets displayed in the display of VG.

4-5

Figure 4.7 Status of Snapshot:

In order to restore data to the original volume, user should copy and paste file from snapshot volumes to the original volumes. The user can remove the created snapshot. To remove the snapshot double-click on Snapshot name and click on remove command button. 4.1.4 Volume Replication

Replication: To enable replication is working, login admin in two proNAS in same windows is required. 1. To create a replication of Logical Volume click on Volume name whose replication is to be taken. Message will get display stating that if there is a Volume with the same name, the data of that Volume will get erased and the data of this Volume will get copied. Click on Yes command button if on remote side there is no Volume with the same name. Figure 4.8 Replication Screen

4-6

2. After click on Yes command button Create replication window will get displayed. Specify the parameters. Figure 4.9 Create replication screen:

There are two tabs in the replication screen: Remote and Setting. Remote: 1. Remote: Select the remote proNAS device here. 2. Remote VG: Specify the VG on which the replication is to be taken. Setting: 1. Status Initialized: Status is the status of replication. Primary status means the source. Primary status is the active node. Secondary status means the destination or passive node. Error status means Replication fail. Unconfigured means not Initialized, Inconsistent means both primary and secondary devices are not synchronized and Consistent means both primary and secondary devices are synchronized. When replication is configured, user needs to press Initialized button. After initialization, it will display SECONDARY. Then press set to Primary button in the primary proNAS to synchronized replication to secondary. 2. Port to Bind: Port is the Internet address and it is to bind locally or to connect on the partner node. Default is 7,758. NOTE: User should change the default port, which is not used by the system. (i.e. 7788 to 77XX) 3. Connection Type: Sync: The system will acknowledge the transaction is completed after the data written to the disk of destination proNAS, we recommend you to use this mode. Here, for most cases, it preserves transaction semantics. Write IO is reported as completed, if we know it has reached both local and remote disk. Async (for high latency networks): The system will acknowledge the transaction is completed after the data written to buffer. It provides faster transmission and is suitable for busy network. Here write IO is reported as completed, if it has reached local disk and local TCP send buffer.

4-7

4. Max Synch Rate (Mb/sec): It is limitation of the bandwidth used by the resynchronization in process. Default is 30Mb/sec, Minimum value is 4Mb/sec and Maximum value is 680 Mb/sec only for high latency network environment (e.g. bonding 8 Gigabit Ethernet). For LOW latency network environment maximum is 50 MB/sec. 5. Send Buffer Size (K): Number of data blocks between two write barriers. Default is 512K and Maximum is 1024K. 6. Time Out (sec): It is the value to wait for connection timeout if this node was degraded. Default 6 sec and Maximum is 9 sec. 7. When Lost connect: Reconnect: When it fails to do replication, the source volume could be read/write by users, after the system succeed to connect again, the destination will compare the difference between sources, and to take replication. (Try to reconnect or recover if connection is lost.) Stand-alone: When it fails to do replication, the source volume will be Stand-alone for users to read/write, but no retry, and no replication. (Do not reconnect or standalone state.) Click on OK command button and the Replication of that Volume will successfully get created on the remote machine. Note: When replication is initialized completely, it will create 4GB volume for meta-date purposes. For Replication 2TB size is the limitation of a single volume.

4-8

4.2

Network Manager

Using the Network Manager, you can configure the NAS network settings. There are two sections in the Network tab, the General Settings section and the Network Adapter section.

4.2.1

Network Setting and Trunking Figure 4.10 The Network tab.

Following are the configurations in the General Settings section: Host Name The Host Name is the NetBIOS name of proNAS. This name should be unique. PDC/ADS Domain This the domain name. DNS Suffix To complete the server full name, you must append the DNS Suffix after the server name. DNS Server The DNS Server is responsible for mapping the machine name and IP address. You can enter a maximum of two fields. After setting the DNS server, it manages the machine name. The host name could be changed by the DNS server while booting up proNAS. WINS Server WINS Server is responsible for setting the NetBIOS name resolution. Edit DNS Table If you have not set the DNS, you can use this button to edit the DNS in the DNS table. This is optional. Edit Lmhost Table You can use this option to define the resolution of NetBIOS in the Lmhost table. This is also optional. 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.

4-9

Following are the steps to create a Trunk Port: 1. To start the process of creating a Trunk port, click Edit. 2. Select an Ethernet port from the Port list. Here the users have to select more than one Ethernet ports then only Trunk Adapter get enabled else the button of Trunk adapter is disabled. The created Trunk gets created on top of those two selected Ethernet ports. 3. Click the Trunk Adapter button. If the user tries to use Trunking or Bonding using BOOTP/DHCP user should follow the steps: A. Create bonding adapters. B. Set to DHCP. C. Click on SAVE command button. D. Configured Aggregation functions provided in your switch device. E. Restart proNAS services in the CLI. 4. In the Create Trunk Adapter dialog box, enter the Device, IP address, Gateway and Subnet Mask. Figure 4.11 The Create Trunk Adapter dialog box.

5. Select the Team Mode. The Team Mode defines the operation of the trunk port. You can select any one of the following team modes: Team modes are 1. Fault Tolernat (Active Backup) 2. Load balance and Fault Tolerant XOR 3. Link aggregation (802.3ad) 4. Load Balance alb Fault Tolerant(Active backup) Only one slave in the bond is active. A different slave becomes active if, and only if, the active slave fails. The bonds MAC address is externally visible on only one port (network adapter) to avoid confusing the switch. This mode provides fault tolerance. If the active NIC is not available, the standby NIC will take over the job so that it enhances the availability of NAS.
4-10

Load Balance and Fault Tolerant - XOR Transmit based on [(source MAC address XORs with destination MAC address) modula slave count]. This selects the same slave for each destination MAC address. This mode provides load balancing and fault tolerance. XOR policy: Transmit based on source MAC address and XOR with destination. MAC address: This selects the same slave for each destination MAC address. This provides load balance and fault tolerance. Link Aggregation (802.3ad) It consists of a team of 2-8 adapters that simultaneously receive and transmit data. Aggregation groups include only members with full duplex communication and with the same speed. This team mode includes fault tolerance and load balancing. It rewires a switch that supports the IEEE 802.3ad Dynamic standard. It supports link aggregation. Transmits and receives on all slaves in the active aggregator. Pre-requisites. The switch must support IEEE 802.3ad Load Balance ALB(Adaptive Load Balancing) Adaptive load balancing includes balance tlb + receive load balancing (rlb) for IPV4 traffic and does not require any special switch support. They receive load balancing is achieved by ARP negotiation and doesnt require special switch support. The bonding driver intercepts the ARP replies sent by the server on their way out and overwrites the src hardware address with the unique hardware address of one of the slaves in the bond such that different clients use different hardware addresses for the server.

6. Enter the VLAN ID. VLANs are based on the addition of a tag to the packet header. The settings on the adapter must match the VLAN settings on the switch. There is a limit of 64 VLANs per server, and the VLAN IDs may be numbered from 1 to 4094. 7. Click Create. In the Configuration section, you need to select Dynamic or Static IP configuration. Then, you must enter the Device, IP address, Gateway, and Subnet Mask. Gateway is a required field. Finally, to save the Network settings, click Save.

4.2.2

Internet Gateway

The Internet Gateway settings allow you to enable and disable access to Internet easily. Using the Internet Gateway settings, you can configure NAS to act as an Internet gateway, which integrates DHCP service, routing, and NAT. For example, in a classroom with several computers, you can disable Internet access in class, so that the students cannot browse Web sites. Using proNAS, you can also assign private IP addresses to each computer within the upper-bound and lower-bound of a subnet. If you want to check whether the Internet service is enable or not, you need to check the Service in System Manager.

4-11

Figure 4.12

The Internet Gateway tab.

You need to enter the following information to configure the Internet Gateway settings: DHCPs IP range starting from The starting IP address of the DHCP range of private IP addresses. DHCPs IP range ending with The ending IP address of the DHCP range of private IP addresses. Private Net Adapter A Private Net Adapter is a port that connects a private network. The port could be a trunked port and the port setting should be static. WAN Adapter A WAN Adapter is a port that connects to a WAN router. It could be a trunked port. SNMP/MRTG

4.2.3

You can enable the SNMP/MRTG service to monitor proNAS network traffic. Figure 4.13 The SNMP tab.

4-12

If you would like to monitor more information such as memory, you should edit the Detail Configuration in SNMP/MRTG service. For more information, please refer to http://www.mrtg.org

4.3

Account Manager

The main functions of the Account Manager are: Authentication User Account Group Management 4.3.1 External Accounts Integration

You can utilize external directory services to authenticate accounts. You do not need to create accounts and access groups again in NAS. Currently, PDC/ADS and NIS are supported. You may choose any one of them or both at the same time. Figure 4.14 The Authentication tab in Account Manager.

In the Windows section of the Authentication tab, you need to enter the following information:
Host Name

Host Name is the NetBIOS name of proNAS.

PDC/ADS Domain

It is the Windows domain name.

DNS Suffix

You must append the DNS Suffix after the server name to complete the name of the server.
Account Synchronization Interval (Min)

This is the time interval for proNAS to refresh any added or deleted accounts. A Disable Account message is displayed if the account is deleted in the Directory Server. However, the data still exists and you can backup this data and delete the account manually.
Logon Account and Password

You need to enter the Administrator logon name and password of the Domain Controller.
PDC/ADS Mode

You can choose either the Native mode or the Mixed mode.

4-13

Note: Native mode is compatible with the Primary Domain Controller (PDC), which is the Windows NT account management service, but it is not compatible with Windows 2000 ADS. If you cannot enable the Mixed mode, change to the Native mode. In the NIS section, you need to enter the following information:
NIS Server

You need to enter the IP address of the NIS Server. The NIS Server is responsible for management of the Unix account and password.
NIS Domain

You need to enter the domain name of NIS. Note: If you logon through Telnet, FTP, or Windows Network Neighbor you must enter the domain name in the following format: Domain name\Account name

4.3.2

Local Account and Group Management

In User Account, proNAS performs the following functions: Create a new account Enable and Disable an account Modify and Delete an Account Create a new account Following are the steps to create a new account: 1. Select Account Manager in the proFamily tree. It will display the content of all accounts under the Accounts List tab. 2. Click the Add New Account button. Figure 4.15 The Properties tab while adding a new account.

4-14

In the General section of the Properties tab, enter the following information: Login Name Account name must start with characters a-z (lower case), 0-9, special character _, -. It should not exceed maximum length of 32 chars. Duplicate username shouldnt get entered. Full Name You need to enter the name of the account. Directory Service The Directory Service specifies whether the account is created locally or by ADS\PDC and NIS. Note: Directory Service field will be updated automatically. Quota Size Each account is assigned its own home directory, which is located in the proNASVG home device. Quota means the usable space in the home device. Create Date Note: Date will get displayed as per the system date. UID In the UNIX or Linux operating systems, when access management is processed, users are allocated a unique number called the UID. NFS uses the UID to decide the access right for each file and directory. Its not necessary to enter UID 3. Click the Change Password button if you want to change the existing password click on Change password to input the password. System will not provide default password. Password length must be more than 6 characters and valid characters to enter password are a-z and 0-9. Illegal characters wont be accepted. If you do not want to change the password, skip to the next step. The Status section displays the Current Status and the Used Size. 4. Click the Permission tab. 5. To edit the information, click the Edit button. Figure 4.16 The Permission tab while adding a new account.

The account can gain the access rights from the following categories: Joined groups Implies that the account has gained access rights because of joining certain groups. Individually Authorized shares Implies that the account has gained access rights individually.
4-15

Ownership Implies that the account has gained access rights because it is the owner.

6. To save the information, click Save. Enable and Disable an account The Account Manager allows you to enable and disable accounts. You can enable or disable only local accounts. If an account is disabled by the administrator, you cannot logon to that account. Modify and Delete an Account If you want to modify or delete an account, double-click on the account. If you delete an account, the data in the home directory is also deleted. You can only modify the password and permissions. If the account is created by the directory server (ADS/PDC or NIS )then the account and password can not be modified. In such a case, you can only modify the permissions.

Group Management
Using group management you can administer the access of project shares. For example, you can create a Sales group for the sales department and you can give this group read-write access to the Sales Report project share. Create New Access Groups In group management, you can add new access groups. These groups are created in the local account database of NAS. One account can be included in more than one access group. Following are the steps to create new access groups: 1. In the proFamily tree, select the Group node under Account Manager. 2. Click the Add New Group button. 3. In the Properties tab, enter the Group Name, GID, and the Description. Figure 4.17 The Properties tab while adding a new group.

4. You can add accounts to the Current Member(s) list by selecting an account in the Account List and clicking the >> button. To remove existing accounts, select the account in the Current Member(s) list and click the << button. 5. To save the information, click Save. The Permission tab only has the individually authorized shares permission.
4-16

Modify or Delete Groups To modify a group, double click on group name for the group information. Note: A group name or member cannot be modified if the groups have been created in the directory server (ADS/PDC or NIS). In such a case, you can only modify the group permission. To delete a group, click the Delete button. Deleting a group will not delete the accounts in the group. Access Groups of proBackup In proNAS, there is a special proBackup group. Members of the proBackup group are allowed to logon to the proBackup service. You cannot delete the proBackup group and you cannot edit the group name. Following are the steps to add members to the proBackup group: 1. Under Account Manager in the proFamily tree, select proBackup under the Group node. 2. In the Properties tab, you can add accounts to the Current Member(s) list by selecting an account in the Account List and clicking the >> button. 3. To save the information, click Save. Access Groups of Users Users are a default group, which includes all local accounts. It is automatically updated when you add or remove local accounts. The Users group is used for access control in shares.

4-17

4.3.3

Import Accounts

Import Accounts (from a file) The Import Accounts function saves a lot of time by enabling you to create a number of accounts and groups at one time instead of creating accounts individually. Following are the steps to Import Accounts: 1. Use a text editor to create the import file format. Figure 4.18 A sample Import file.

In the import file, account information must be in the following format: UID, Logon Account, Logon Password, Full Name 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. Note: The UID field is optional. The UID number must be greater than zero and less than 65535. All the values in a line must be separated by a comma. 2. In the proFamily tree, click Account Manager. 3. Click the Import Accounts button. 4. Select the location where you have stored the import file. 5. Click OK.

4-18

4.4 Share Manager

Share Management is the core function of proNAS. In proNAS, the Share folder of a general file server is called Project share. Creation, modification, or deletion of a share is made very easy by proNAS. For example, if the Sales department wants to have a share folder named Sales, you can create it very easily and quickly using proNAS. You can also grant read-write access rights to the entire sales team. Share folder gets created under logical volume. Make sure that user has already created LV before you create share folder or the user can create the LV and share folder simultaneously. 4.4.1 Share Management and Protocol Setting

Creating a New Share 1. In the proFamily tree, select Share Manager.

2. Click the Add New Share button.

Figure 4.19 The Properties tab while adding a new share.

3. In the Properties tab, enter the following information:

Share Name

You can identify a share using the Share Name. The Share Name should be accessible through the network protocol and should be unique in NAS.
Quota

Quota is the usable space of the share.

Volume Group

The Volume Group specifies the storage devices on which this share resides. A volume group may contain more than one project share. Each Volume Group supports only one file system (For example, XFS).
Owner

This field specifies which account owns the privilege to manage this share. Owners can grant the access permissions of a share to other accounts or access groups. Owners can also manage the ACL of all the files and sub-folders in the share. This enables them to delete all of them if necessary. Note:

a.

If the user wants to create a LV click on Create Volume check box LV will get created successfully before creating share.
4-19

b. c. d.

NFS The NFS protocol supports all the permission settings described above. CIFS The CIFS protocol does not support the IP subnet with read only permission. Apple Talk and Netware The AppleTalk and Netware protocols ignore the IP subnet setting. You can have only one account (Owner) and group.

4. Click the Protocol tab.

Figure 4.20 The Protocol tab while adding a new share.

The different settings in the Protocol tab are as follows: Settings for CIFS Protocol: You can enabled or disable file sharing for CIFS. You can use the Case Sensitive option to make the names of files or subfolders case sensitive. You can use the Synchronize write option to enable or disable the write cache. You can hide files or folders that begin with a dot. You can set the maximum CIFS connections that can access the NAS system simultaneously. Settings for NFS Protocol: You can enabled or disable file sharing for NFS. You can use the Synchronize write option to enable or disable the write cache. You can also allow root access. The Insecure option is only for Macintosh systems. Settings for AppleTalk Protocol: You can enabled or disable file sharing for AppleTalk. Settings for Novell Protocol: You can enabled or disable file sharing for Novell.

5. To save the information, click Save.

Modifying or Deleting a Share You can modify or delete a share in the form view. You can modify the following properties of a share:
4-20

Expand the quota space of the share The maximum of quota space cannot be larger than the space of volume group. You can expand the share space online. Expansion of share space will not interrupt the user access from the File Manager or the network. The owner can modify the permission. You can add or remove the protocol. However, if you remove all the protocols, the users can not access the share from any network.

If you delete a share, all the data in the share is deleted. Therefore, we recommend you to create a backup before deleting a share.

4.4.2

Privilege (ACL) Figure 4.21 Privilege Tab

This field is used to grant read-write permissions of the share to other accounts, access groups, accounts or IP subnets. To grant permissions, select an account, access group, or IP address from the list and click the Add button to move the selected account to the permission list. User should press Enter command button after setting Quota for Users/groups. To deny permissions, select an account, access group, or IP address from the Permissions section and click the Remove button. Note: When new users access is added to a share, admin should disable write access of users group.
Strick ACL

This is an advanced setting of access rights. It is the advance setting for share folder. You can choose to configure with Strict ACL mode. If you check Strict ACL, the permission of the sub-folder cannot be superior to the parent folder. For example, if you set the permission read only in the parent folder, and sub-folder cannot get read/write permission in Strict ACL mode. For more information, see File Manager.

4-21

4.4.3

Sub-Folder Management

In the Sub-folder tab user can add, modify, delete and Refresh sub-folder in the selected share. Add new folder 1. To add a new folder click on share name. Select Add new folder command button. Figure 4.22 Add Folder Screen

2. Enter the folder name. Select the username to assign the permission and click on Ok command button. Sub-folder will get created under that share. Modify folder: 1. The user can modify the name and the permissions of the folder. To modify click on Modify folder command button. 2. Specify the new folder name and click on Ok command button. Delete Folder: 1. To delete a sub-folder click on folder name and select delete folder. 2. Sub-folder will get deleted successfully. Refresh: Refresh command button will scan and detect new sub folders created in File Manager.

4-22

4.4.4

Default Share

The four default shares are: home proBackupDevice proBackupExtendedDevice public You can modify the Quota size for all default shares except the home share. home The home share holds the shares of all individuals. It cannot be modified and deleted. It increases its space automatically. proBackupDevice proBackupDevice holds the major backup device for proBackup application. It is visible after you enable proBackup service. ProBackupExtendedDevice proBackupExtendedDevice holds the extended device for other proBackup servers to utilize. It is visible after you enable proBackup service. public NAS has a built-in project share called public. This share is authorized with read-write permissions to the public access group due to which all logons (including guests or anonymous) can access it.

4-23

4.5 System Manager

System Manager is responsible for the configuration of the system and various services such as, network setting, system service, date and time zone, UPS setting and so on. You can also perform system related issues such as firmware upgrade, shutdown and reboot, and configuration backup or restore. The System Manager includes the following tabs: Information Upgrade Report Time Serial Ports Reboot Service Hardware Health 4.5.1 System Information

It displays the information of Account, Storage and System manager. Figure 4.23 Information screen

In Account information it displays the number of Account and the number of shares. Share manager displays the total numbers of disks (used and free), Volume group numbers and Volume numbers on it. System information displays the information of proNAS i.e. Model no., CPU, MHz, memory, NIC and the Build version. Note: The information in this tab gets updated automatically.

4-24

4.5.2

Firmware Upgrade

The Upgrade tab enables you to upgrade NAS firmware. The Current Version of the firmware and its Release Date is also displayed in the Upgrade tab. Figure 4.24 The Upgrade tab.

proNAS tries to access the default URL ( ftp://support:xxxxxxxx@upgrade.proware.com.tw/proNAS/ ) to download appropriate patches. If you fail to connect to the Web site, please check your network and firewall settings. You can also download patches manually, save it in the local and press Browse to find the patches. Before you begin the upgrade, make sure that all the users are off line. Also, make sure you do not power off during the patching process. You need to click the Upgrade button to start the upgrade process. After patching, NAS reboots automatically. This upgrade can take approximately 15 to 20 minutes depending on the Internet bandwidth. You can click the Check Updates button to check for any new upgrades or patches that might have been released since the time you upgraded last.

4.5.3

Report

In the Report tab, the user can generate reports on daily or weekly basis. 1. To schedule a report enable the Enable schedule report. Schedule the day and time to generate the report. 2. Specify the Destination path where the report should get saved. 3. The user can also mail the report on e-mail id. Click on Enable Mail Deliver option and specify the SMPT server (address of mail server), sender and receiver mail id. Report will be successfully mailed on the selected mail-id. The user can generate immediate reports of Account and shares created. Specify the Account or the share name whose report is to be generated. Click on Generate Now command button. Report will get generated immediately.

4-25

Figure 4.25

Report Tab

4.5.4

Time Setting

In the Time tab, you can configure the Time Zone, Date, and Current Time. You can set the time manually or you can synchronize the time to a NTP server. You can use the Add and Remove buttons to add or remove available NTP servers. Figure 4.26 Time screen

4-26

4.5.5

Serial Port

proNAS enables you to configure two serial ports, com1 and com2. The Serial Ports tab has two sections, Com1(RAIDMgr) and Com2(UPS). The first section is for Prowares RAID Manager configuration and the second for the UPS configuration. User can configure Com1 and Com2 serial ports in this tab, press Edit: and then Com1. Figure 4.27 The Serial Ports tab.

Following are the configurations in the Com1(RAIDMgr) section for the Proware RAID manager: Supported Application: Choose ProRAIDMgr or proNAS HA. Baud (Bits/Sec): If you choose ProRAIDMgr default Baud rate will get displayed according to your model i.e. SN-3143, SN-4120 19200 and SN-1405, SN-2805, DN-405, SN-3168 115200. If you choose proNAS HA, system will display the Baud Rate: 9600, 38400. Data bits: 8. Parity checking: None Stop bit: 1 Flow control: None Following are the configurations in the Com2(UPS) section for the UPS: Supported Application: UPS or proNAS HA. UPS Mode: Choose UPS system mode support as Dumb mode or Smart mode. If you choose Dumb mode, you dont have to configure the detail setting about vendor and cable. UPS Vendor: If you choose Smart mode, proNAS supports two vendors 1. APC 2. Beam Tech. If you choose APC model then choose UPS cable. And if you choose Beam Tech it supports SSPro 650. UPS Model Cable Model Shutdown Delay (Min): Delay is the time for which proNAS uses the UPS after a power failure. After completion of the above settings press Save command button to save the current settings.
4-27

4.5.6

Reboot

The Reboot tab has two sections, By Schedule and Instant. Figure 4.28 The Reboot tab.

In the By Schedule section, you can enable scheduled reboot by selecting Enable schedule reboot. Once you enable the schedule reboot, you can set the Day and Time for the reboot. In the Instant section, you have the following options: Shutdown Now Reboot Now Erase storage & configuration: Clicking on this button will reset all settings to factory default settings. All the data and settings are deleted. You must be careful while using this function. To save the Time configuration, click Save. Reboot and File System Check

4-28

4.5.7

Service

The Service tab enables you to view the status of various services. You can Start or Stop services manually using the Start and Stop buttons. Figure 4.29 The Service tab.

The various services that can be configured are: Samba (CIFS sharing) Provides CIFS file sharing. MS windows users need the service to access proNAS. NFS (NFS sharing) Provides NFS file sharing. UNIX users need the service to access proNAS. AppleShare (AppleTalk sharing) Provides AppleTalk file sharing. Mac OSX 9 users need the service to access proNAS. Novell (Novell sharing) Provides Novell file sharing. Netware users need the service to access proNAS. SSH Server Allows you to use the SSH Server to remotely manage systems and copy data securely. Apache (Web service) Provides Web service and should always be enabled. The Apache setting includes the Port number whose default value is 80. Telnet/Ftp Services Provides Telnet/Ftp service so that account users can use Telnet and Ftp to access proNAS. However, the root account cannot use Telnet/Ftp to logon to proNAS, they must have to use the console. Internet Gateway Provides the service to access the Internet. UPS Monitor To connect to UPS, you must enable this service. SNMP/MRTG service Provides SNMP and MRTG service so that you can check system information. VERITAS BackupExec eng Provides Veritas BackupExec engine service so that the Veritas console can make proNAS the media node for Veritas. proBackup service Provides backup service for all account users. You must enable the service first, if you want to use proBackup.
4-29

After you submit the configuration changes, NAS tries to apply them. You can enable any of the services on boot-up by checking the Enable On Boot check box adjacent to the respective service. You can stop or start all services simultaneously using the Stop All Services or Start All Services buttons. proNAS HA service proNAS 1.1 has new High availability feature with active stand mode. While running 2 proNAS systems, admin can configure these 2 proNAS with HA function. ProNAS HA service will check network and proNAS services while running, and do fail over to stand-by NAS if theres network cable problem or service stopped event happened in Active-NAS.

In the Service tab, there are two types of configurations: Quick Configuration Detailed Configuration Quick Configuration To do a quick configuration, click on the service then only Quick Configuration command button will be enabled. Quick Configuration is convenient setting for administrator. Some services which require a Quick Configuration to be done first are: proBackup Service Figure 4.30 proBackup service Quick Configuration dialog box.

Following is the information you need to enter in the proBackup Service Quick Configuration dialog box: IP of Rx/Tx backup streams The IP address of the adapter used by the proBackup service streams. Port of Rx/Tx backup streams The Port number for the backup streams. The default, which can be modified, is 1089. Languages of proBackup server The language for server side log. Apache Web Service The Apache Web service uses Port number 80 as the default port. This Port number can be modified. Veritas BackupExec eng Service

4-30

Following is the information you need to enter in the Veritas BackupExec eng Service Quick Configuration dialog box: Advertised Host The name of media node known to Veritas Console. Workstation password The administrator password. SNMP/MRTG Service: Before the service starts up, it asks you to regenerate the report during boot-up or to keep the statistics report last time. Detailed Configuration To do a detailed configuration, click the Detailed Configuration button. Once you click the Detailed Configuration button, you can edit the configurations in a simple text editor, similar to the editing in Linux. The detailed configuration is recommended only for experienced users. It is also recommended that you take a backup before the detailed configuration.

4.5.8

Hardware Health

In the Hardware Health tab, you can view images of the front and rear panel of the NAS subsystem. Each component of the hardware is labeled. Figure 4.31 Front view in the Hardware Health tab.

4-31

Figure 4.32

Back view in the Hardware Health tab.

The hardware monitor provides the following information: System temperature Disk temperature Fan speed Voltage Note: Different models will display different information: DN-405P: Display the information of disk temperature and fan speed. SN-1405P: Display the information of system temperature and fan speed. SN-2805P: Display the information of system temperature and fan speed. SN-3143P: Display the information of disk temperature, fan speed and voltage. SN-3168P: Display the information of disk temperature, fan speed and voltage. SN-3163P: None. SN-4120P Display the information of disk temperature, fan speed and voltage.

4-32

4.6

Backup Manager

porNAS provides both data backup and configuration backup in Backup manager. For Data Backup, administrator can create backup plan and decide the backup destination, schedule and backup method. Configuration backup could be saved in xml file and we highly recommend taking configuration backup periodically. 4.6.1 Configure Backup Plan Figure 4.33 The Backup Manager tab.

Following are the steps to backup a share: 1. Click the Backup Manager. 2. Click the Add Backup Plan button. 3. In the backup dialog information enter the Backup plan name. Figure 4.34 The Backup Share dialog box.

4-33

4. Click on Destination Figure 4.35 The Backup Destination dialog box.

5. In the Destination dialog box, you need to enter the following information: Destination You can select Remote Share, Local Disk or Tape Device as the backup destination. If you choose Tape Device, you must make sure the Tape Device is connected to proNAS before you take the backup. If you choose Remote Share, the Protocol, Path, Account, and Password fields are enabled and you have to enter information in these fields. Protocol You can choose Samba or NFS as the protocol. This enables you to backup the share to a Windows file server, NFS file server, or some other proNAS system. Path Path specifies the location of the share from the remote server share. The format of the path depends on the type of protocol you choose. If you choose the Samba protocol, use the following format: //IP address/share folder For example, //192.168.10.190/public or //machine net bios name/ share folder For example, //server1/public If you choose the NFS protocol, use the following format: IP address: exports full path For example, 192.168.10.12:/mnt/proNAS Account and Password You must enter the Logon ID and Password of an account, which has read-write permissions for the share. Compressed Selecting the Compressed option enables GNUZIP compression while creating the backup. Schedule Backup Tab This option allows you to set the day and time when you want to schedule the backup. A. If the user clicks on Daily two tabs will get displayed Schedule Setting and Daily Backup Setting.

4-34

Figure 4.36 Daily schedule Backup

In Schedule Setting the user should enter Starting Date, Ending date and Starting Time of the Backup. In Daily Backup Setting user should select default plan. Default plan such as Incremental, Differential. B. If the user click on Weekly two tabs will get displayed Schedule Setting and Daily Backup Setting. Figure 4.37 Weekly schedule Backup

In Schedule Setting the user should enter Starting Date, Ending date and Starting Time of the Backup. In Daily Backup Setting user should select default plan and Run at i.e. on which day the backup should start. Default plan such as Incremental, Differential. C. If the user clicks on Periodic two tabs will get displayed Schedule Setting and Periodic Backup Setting.

4-35

Figure 4.38 Monthly schedule Backup

In Schedule Setting the user should enter Starting Date, Ending date and Starting Time of the Backup. In Monthly Backup Setting user should select the parameter i.e. full Backup every 2 days. User can select after how many days user wants to take the backup. If the user clicks on No schedule backup wont get scheduled. 6. After entering the information, click the Save button to save the information. 7. When the information gets saved click on Edit Backup item list to add the list of items (folders) whose backup is to be taken. Select the items for Backups and again click on Save command button. User can modify the backup plan by click on Edit command button. In modify user can Enable, Disable and Remove the backup plan. Restore You can select a backup from the backup history and restore the backup to what it was at that time. NAS preserves at the most a hundred backup histories for a share. It can also recycle older ones if necessary. However, NAS does not guarantee the availability of archives before a restoration, since it is possible that the archive resides on a tape, a remote folder, or even an un-pluggable local drive.

4-36

Figure 4.39

Steps for restoring a share.

Following are the steps to restore a share to one of its backups: 1. Click on Restore tab. 2. From the backup history, select the backup to which you want the share to be restored. 3. Click Restore. Figure 4.40 NAS Config backup

4.6.2

proNAS Configuration Backup

The NAS Configuration backup tab has two sections, Backup Configuration and Apply Configuration. Using this tab you can backup and restore the NAS configuration. Following are the configurations in the NAS Configuration Backup section: Memo Select the Destination Path box, browse to a local folder where you want to save the backup. Then, click the Backup button to start the backup. The configuration will be saved in xml format. The Apply Configuration section is used to restore a backup. You must click the Apply button to restore a selected backup.
4-37

4.7

Log Manager

The Log Manager enables you to view the important logs generated by proNAS. The Log List tab of the Log Manager lists the Log Type, File Name, Date, and Size (KB). To view the contents of a log, Click on Reload command button. Figure 4.41 The Log Manager Screen.

The types of logs are: KER This log contains information about the Linux kernel service. Its path is /var/log/messages. It can store information of seven days. SMB This log contains information about the CIFS and Samba protocols. Its path is /var/log/samba.log. NBS This log contains information about the NetBIOS protocol service provided by Samba. ATK This log contains information about the AppleTalk protocol. Its path is /var/log/atalk.log. DSK This log contains information about the changes to volume. Its path is /var/log/storage.log. It can store information of seven days. BAK This log contains information about backup and restore. Its path is /var/log/backup.log. It can store information of seven days. You can click the Reload button to refresh the latest system logs. NWS This log contains information about Netware protocol. Its path is /var/log/nws.log VRT This log contains the status of veritas. BAK This log contains the status of proBackup.

4-38

4.8

Event Manager

You can receive email notices when UPS on battery event occurs or when there is a RAID warning. You must make sure that the SMTP service is enabled. The event tab has two sections, Email Setting and Event Setting.

4.8.1

E-mail Notification Setting Figure 4.42 The E-mail setting tab.

In the email setting section, you need to enter the following information: 1. Sender E-mail address Enter the senders e-mail address 2. SMTP server Enter the IP address of the SMTP server 3. Port Enter the port number 4. Accounts Enter the username 5. Password Enter the password After entering these fields enter the receivers e-mail address and click on Add command button to add the receipts address. You can enter multiple e-mail addresses separated by semi-colons. E-mail setting: Admin user can define what NAS do when event occur. One can send mail to notify users. These email setting define the receiver, all these user will get the warning message from proNAS if theres some event happened.

4-39

Figure 4.43

E-mail setting

4-40

Chapter 5 File Management

5.1 Introduction of 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 know the correspond applications that can open it, or the browser will prompt users to save the file in the local computer instead. Update a file: user needs the write permission of the folder and the file itself. A browsers upload window will show up and user needs to locate the file with the same file name in local computer. Create a file: user needs the write permission of the folder. A browsers upload window will show up and user needs to locate the file in local computer. Delete a file: user needs the write permission of the folder and the file itself. Rename a file: same as above, and user needs to give the new name of a file. Change Password: if user needs to change password, please select the function. 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 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 in 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, 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. The default setting of share members gain the read/write permission to the files in the shares and administrator can manage it in advance. If the share is set Non-Strick mode in proNAS GUI that means users can gain more permission in sub-folder than the parent folder. For example: share owner John create sub-test under the parent folder test, the users has read only permission in the test folder, but they can gain read/write permission in sub-test folder if set by the share owner John. However, this situation is not allowed in the strick mode in proNAS.

5-1

Administrator changes the mode of non-strick or strick in proNAS GUI will not effect the original setting of share owner. For example: in the non-strick mode. share owner John creates sub-test under the parent folder test, originally, user Andy gains read only permission in test folder and read/write permission in sub-test folder. If the administrator change non-strick mode to strick mode in proNAS, the original setting will not be effected that is to say user Andy still get read/write permission in sub-test folder. However, share owner John can not grant read/write permission to other user because the non-strick mode is changed to strick mode. To determin if one user gets read/write permission to a file or subfolder, its not only depending on the ACL setting, but also depending on if he(she) is the creator of the file ( subfolder). For example: user Andy gets read/write permission in sub-test folder and he creates the file mytest.txt under sub-test folder. After that, share owner John changes ACL to Andy of read only permission to sub-test folder, but Andy still gets read/write permission of mytest.txt file because he is the creator. We would like to mention that, the ACL setting only effect the permission of users and groups, but also effect the restriction of different protocol. Please remember that, if you do not choose any one of the protocol ( CIFS, NFS, AppleTalk,Netware), you can not access the File Manager.

5.2 Logon to File Manager:

Enter the username and password to pass authentication.

5-2

The first Screen of file Manager will display and help users to understand their recent activities and perform file management. There are 5 sections in the File Manager screen:

Section 1: displays Home Share and Public Share. Section 2: displays all project shares. Section 3: displays the function list of File Manager. Section 4: sorted by the columns (File name, size, last modified...) Section 5: list the current directory and files.

5.3 Directory and Upload Function

Directory: In the Directory function, you can create a sub-folder in current folder, or rename / delete current folder. Please notice that in the action of create or rename folder, you can execute the permission management conveniently.

5-3

For example, administrator created a project share named class share in proNAS GUI, and set the share owner to be teacher John, and students Andy, Bill, Cindy gained the read/write permission to the class share. One day, teacher John would like to create a sub-folder named project A under the class share, and assigned Andy only to study project A. He may enter to File Manager, choose class share to be current folder and click Directory function, in default, he can see Andy, Bill, Cindy got read/write permission. Later, John created the sub-folder named project A under class share and granted Andy with read only permission and Bill and Cindy with no access permission. Upload: Users with read/write permission to the folder can choose Upload function to upload local files to the folder.

5.4 Access Right and Group Access Right

Access Right Share owner can change the permission in Access Right function by add/remove users to selected list.

5-4

Group-Member-AR Group Member Access Right In the non-strick mode, group member can gain more permission in sub-folder than parent folder. Other case is that share owner can select some members with different permission to the others in the same group. Example: In the non-Strick mode, teacher John created a project share named Essay and assigned the group students ( Andy,Bill,Cindy) with permission read only. Later, share owner John created 3 sub-folders named andy,bill and cindy under the share Essay. After that, John granted Andy to the subfolder andy with permission read/write by using the function Group_Member_AR , other students with permission read only.

5.5 Change Password and Logout

Setting: Users can change password in the Setting function. Logout Users can logout to File Manager in Logout function.

5-5

Chapter 6 proBackup
6.1 Introduction of 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 by proBackup storages, 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.
ProBackup Server
(Backup Plan) User backup his files to proBackup Server according to his Backup plan

(Quota review Plan) Replicate proBackup Server archives to Replication Server to extend proBackup Server capacity virtually

Client A

Client B

Client C

Replication Server

Infrastructure diagram show proBackup storages

6.2 Administrator Logon

Note: 1: All the backups of an account are lost forever if it is deleted. Please make sure such action before do it. 2: It is advised that only the organization privilege persons can assume the role of administrator since it can restore all others data, which may contain sensitive data.

6.2.1

Quota Review Management

The Quota review plan periodically review accounts quota of a quota class and will move out archives if necessary. Accounts disk usages be lower than the quota limitation after then if there are enough disk spaces in applicable replica servers. 1. Click Plan Manager icon in tree view and the plan list show up in the major content window by a table panel as below. Each row briefs the info of a plan. The plan manager node will automatically expand.
6-1

2. Click a row of the list panel or one of plan and the detail of a plan shows up in the

major content window by a tabbed panel.

3. Click General tab and show the basic info of a plan.

6-2

4. Click Schedule tab and show the setting to control periodical execution.

6-3

5. Click Enable to plan Quota review. System will show up the icon that denotes Quota review execution.

6. Click History tab and show the historical activities ever performed on a plan.

6-4

6.2.2

Archive Plan for proBackup System

Archive the proBackup system to other volume for restore if necessary. 1. Logon as admin. (Choose the logon site of server IP) 2. Click Plan Manager icon. Click Archive plan for proBackup system in tree view.

3. In the General panel, click Edit to fill in destination folder. The destination volume could be a tape device, i.e. /dev/tape, or other volumes. To backup to another proBackup server, enter a dual slash and the target proBackup server ip or server name. Notice that this plan will not run while other plans are executing.

4. Click schedule tab and fill desired schedule. 5. Click save button.

6-5

6. To understand all the execution results, users can click History tab and see a list

of them, and double clicking one of them to see the details.

6-6

6.3 Backup Files

To backup files, users have to create backup plans first. 1. Logon. (Choose the logon site of server IP in case of administrator logon. Choose Local for normal users.) 2. Click create plan or New button to open a draft form for the new plan in edit model that could be found in proBackup wizard and plan manager.

A. proBackup Wizard

B. Plan Manager

6-7

B. Plan Manager 3. In the General panel, fill in required fields include plan name, backup entry home directory, and backup files/directories. Optional fields include temporary archive path, purpose, compression, and memo. Click the compression optional to enable GNUZIP compression while creating the backup.

6-8

Choose home directory and backup entries. Note: Users are advised to classify your files or folders first. Good backup plans only backup certain types of files that having something in common. Please avoid backup a whole hard driver or root file systems. 4. Click schedule tab and fill desired schedule. 5. Click save button.

Note: 1: Users need to enable their plans to start up the scheduling, vice versa. However, users always can click RUN button to backup files immediately, as long as plans are not executing. 2: The key concept of plans schedule is the days/per-round between two backups. Lets take seven days for example. In day 1 we have a backup

6-9

by scheduler, and the next backup will be seven days after the last backup; that is, day 8. Once users manually execute a backup in day 5, then the next backup will become day 12. 3: An enabled plan will retry to backup if it cannot perform it due to some reasons. For example, a plan supposes to backup in day 7, but the intranet goes down a whole day. The backup will be performed as long as the intranet returns. However, failed or warned backups belong performed ones. 4: How many recent cycles of backups are perserved? One backup cycle begins with a full backup and follows as many differential backups as specified (Rounds/Per-cycle). proBackup will repeat the backup schedule unless the schedule expires or no more disk space is available. The number of cycles tells proBackup to keep that many cycles of backups at most, so users may manage the space usage of their periodical plans accordingly. For example, if a schedule has four cycles, then the backups of first cycle will be automatically removed after the completion of fifth cycle. 5: Users are free to perform other uses case while backup is running. The progress window will automatically show up again while users browse the plan again. A new activity will be added after backup is completed. 6: In proBackup wizard, users can click backup wizard button and double click a plan to perform desired backups, too. 6. To understand all the execution results, users can click History tab and see a list of them, and double clicking one of them to see the details.

6-10

7. Double click the desired one or right click to choose View and the details of an

activity will show up as below. Use scroll bar to understand the backup status of specific files.

6.4 Restore Files

6.4.1 Restore a backup

To restore files, users have to pick up a backup first. 1. Logon. (Choose the logon site of server IP in case of administrator logon. Choose Local for normal users.) 2. Click a plan in left tree panel, or pick one out of the plan list found in Plan Manager, or pick one out of the plan list found in proBackup wizard.

A. Tree Panel

6-11

B. Plan Manager

C. proBackup Wizard Note: In proBackup wizard, users can click backup wizard button and double click a plan to perform desired backups, too. 3. Click History tab. 4. Double click one out of executing logs.

6-12

5. Click Restore button.

7. Choose a directory to restore.

Note: 1: Users may restore their backups in different machines, since an account can find out all past backups of its won across all machines. 2: Users can restore some of files in a backup

6-13

6.4.2

Restore some of files in a backup

1. Click a row of the list panel or one of plan and the detail of a plan shows up in the major content window by a tabbed panel.
2. Click History tab and show the historical activities ever performed on a plan.

3. Double click the desired one or right click to choose View and the details of an activity will show up as below. Use scroll bar to understand the backup status of specific files. Hold down the control key of keyboard and select those files to be restored in the scrolling view.

6-14

4. Click Restore button.

5. Choose a directory to restore.

6-15

6.4.3

Delete backups

Users may delete a backup or all the backups of a plan. 1. Click a row of the list panel or one of plan and the detail of a plan shows up in the major content window by a tabbed panel. 2. Click History tab and show the historical activities ever performed on a plan.

3. Right click on the one to delete and choose Delete.

Note: A backup is lost forever once it is deleted. All the backups of a plan are lost if a plan is deleted.

6-16

Chapter 7 proNAS HA ( Option Function )

7.1 Introduction of proNAS HA

The core processes of ProNASHA are implemented as two mutual-guarded fail-save proNAS services. They can be manipulated by accessing the Services tab in the proNAS services manager node. The dual service architecture of ProNASHA is to prevent ProNASHA from being the single-point-of-failure of the server cluster. When a server is down or unavailable, ProNASHA 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. ProNASHA 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, ProNASHA 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.

7.2

Getting Started with ProNASHA

Before Configuring High Availability Before attempting to configure two ProNASHA as a High Availability pair, check the following requirements: Two (2) proNAS NAS box model, Two (2) Network Adapters of each proNAS One (1) RS232 Cable for Heartbeat use(optional) Two (2) Static or DHCP IP address (we recommend STATIC scheme) ProNASHA services must be started in both proNAS At least ONE reliable heartbeat, RS232 or Ethernet Each proNAS must have a unique HOSTNAME

7.2.1

Hardware Aspect ProNASHA server that performs cluster-protected operations. ProNASHA server that can takeover the critical operations of an active server when the active server is down or unavailable. Private net is a dedicated channel for servers to exchange their operating status (i.e., heartbeat message).

Active server: Backup server: Private net:

7-1

Types of Private Net Available TCP/IP socket: FDDI or Ethernet network running TCP/IP protocol. Each server must install a dedicated IPs to attach to the private net.

RS-232 serial port: One free serial port per server. A null modem must be installed in one end of the serial cable that connects the two servers. Public net: Public net is the paths for networked clients to access clusterprotected resources. Currently ProNASHA supports only TCP/IP and NETBEUI protocols. Each active server must install a dedicated IPs to attach to the public net. This is the entry point for incoming client requests and outgoing server responses. Each backup server must install a dedicated IPs to attach to the public net. When the active server is down or unavailable, the backup server will takeover and the backup IPs acts as the new entry point for incoming client requests and outgoing server responses.

Active IPs:

Backup IPs:

Network Configuration for High Availability Pair The following diagram illustrates the network configuration for a High Availability pair: CLIENT NODE

Multi Port Switch

Public Net

Private Net

Private Net

Public Net

SN-3143P Active Server

Virtual IP Address xx.xx.xxx.xxx

SN-3143P Backup Server

7-2

7.2.2

Procedures for Setting up a ProNASHA High Availability

A step by step setting up ProNASHA: Step 1: Step 2: Step 3: Step 4: Step 5: Step 6: Step 7: Step 8: Step 9: Configured at least two Ethernet IP address on each proNAS Login Admin on both servers Start ProNASHA services in proNAS Service Manager of both servers On General Setting, Enter the Hostname of the peer server. Set Operation preferences to Active (Local Host) Standby(Peer host) mode On Peer Server General Setting, Enter the Hostname of the peer server. Set Operation preferences to Standby (Local Host) Active(Peer host) mode Press Get peer IPs on each server (local and peer)" Configure at least one private net of each server. Configure Ethernet private net is recommended. The proNAS data replication use the same ip if you configure Ethernet private net.The RS232 private net is backup communication channel when Ethernet private net is failed if you configure Ethernet and RS232 private nets. Start Cluster Wait until all status of both server are in Standby Mode (SB) On Resource Group Manager, Press Add Resource Group Configured the Resource Group member Add Resource type Configured the IP resource type properties Bring In the ProNASHA

Step 10: Step 11: Step 12: Step 13: Step 14: Step 15: Step 16:

If the server cluster follows the complete setting perfectly, you can carry on to the production operation.

7-3

7.2.3

Start proNAS HA Service

Starting the ProNASHA services on the Active or Primary ProNASHA To start configure Active or Primary ProNASHA, Click System Manager on the left side of the proNAS software and click SERVICE tab

You can Start or Stop ProNASHA services manually using the Start and Stop buttons. Note: ProNASHA will override replication if there are an existing. Staring the ProNASHA services on the Backup or Secondary ProNASHA To start configure Backup or Secondary ProNASHA, Click System Manager on the left side of the proNAS software and click SERVICE tab

You can Start or Stop ProNASHA services manually using the Start and Stop buttons. Note: ProNASHA will override replication if there are an existing.

7-4

7.3

ProNASHA Properties

Status Properties

Users can monitor all the resource from the ProNASHA 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

Active Mode Standby Mode Error Mode

Startup Mode Fail Mode Offline Mode

7-5

The private net status The colored lines between the servers indicate the status of the private net. Also status are display 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.

Indicators Users can accurately monitors the status of the system such as the License status, Private Net, Public Net and resource takeover/failover. When a condition occurs, the icon will turn red. You will also see a message appear in the Event Log.

When the private net does not create properly, this gui will turn red and display information. When the public net does not connect properly, this node will turn red and display information When the resource group failover or takeover, this node will turn red and display information When the ProNASHA is not register, this node will turn red.

Stop Cluster: Start Cluster: Get peer IPs: Network test: Host:

Stop Cluster Operation. Start Cluster Operation. Get the IPs of peer server and display all IPs of peer server in the message pad. Tool for testing network IP address Display the status of Local and Peer Server

Resource Group: Display the resource group status

7-6

7.4
7.4.1

General Setting
General Setting Properties

If both primary and secondary ProNASHA node already show up in the left side of proNAS software. Its time to configure the HIGH Availability feature of proNAS.

Click on the ProNASHA node, and then choose General setting Option under General Setting Computer Name Box Local Server: The hostname of the Active or Primary server Peer Server: The hostname of the Backup or Secondary server Reference IP Box: Identify an IP Address to check the availability of the servers. This IP address must be on a separate subnet from the public net. Event Log box Level: Normal: Display operation process Trace: Display operation and traceable process Reserved Days: Numbers of day to clear or delete existing log Operation Preferences: An option for user operation preferences.

7-7

7.4.2

License Registration

To apply ProNASHA license codes and register them to ProNASHA users must first get the S/N of the two servers. Forward the S/N to your local ProNASHA provider. Then Input the acquired License and click Register button. Users can now put ProNASHA to work.

7-8

7.5 Setting up Private Net

Private net is a dedicated channel for servers to exchange their operating status (i.e., heartbeat message). Click the Private Net Node of ProNASHA. Two types of communication channels are available for creating private net or heartbeat: TCP/IP Socket and RS232 Serial Port. At least one private net must be functioning before users can proceed to configure resource groups. One or more private net must be configured to prevent single point of failure.

7.5.1

Ethernet

Ethernet Private Net Properties

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.

7-9

Local / peer IP Address: Specify the IP Addresses of the network interface cards that constitute 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 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 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 on starting cluster. Users can add the checkmark to enable this option.

7.5.2

RS232

RS232 Private Net Properties To start RS232 as a private net, users need to configure SERIALS ports settings in proNAS Service Manager SERIAL ports TAB, select either COM 1 or COM2 for ProNASHA.

Local Serial Port: Specify an unused serial port for each server to receive the heartbeat sends 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

7-10

7.6 Resource Group Manager

Click the Resource Group Manager Node of ProNASHA. To manage resource groups, users need only apply the following procedures on one of the servers. ProNASHA will automatically synchronize the status of resource groups between both servers. Note that users are prohibited to create or remove resource groups unless ProNASHA are running on both servers and at least one of the private net is functioning. 7.6.1 Add resource group Properties

Add Resource Group: Add new resource group member. User can specify the name of the resource group. This name can be your choice but must be unique for the resource groups within the cluster

Resource Name: A unique name for identifying the resource group Active Server: The active server of the resource group

7-11

Backup Server: The peer server is automatically display 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 bring in automatically when Cluster starting Save: Save the resource group configuration. Cancel: Cancel the resource group configurations

7.6.2

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. Auto-switch back: An option for enabling the resource 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 bring in automatically when Cluster starting Add Resource: Select the type of resource group to be use Remove: Remove and delete this group member Edit: Edit the configuration

7-12

7.6.3

Add IP resource type Properties

7.6.4

Resource Type Basic Setting Properties

Resource Name: A unique name for identifying the resource group. AC interval (Availability Check Interval): A time interval for ProNASHA to check theavailability of the resource group periodically. AC Retry (Availability Check Retry): The number of times for ProNASHA availability of the resource group periodically. to check the

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.

7-13

7.6.5

Configuration for IP Address Resource Groups

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 Target Server. Active Subnet Mask: The subnet mask used by the Active IP Address.

7-14

7.6.6

Resource Group with group properties

Resource Name: A unique name for identifying the resource group. Active Server: The active (primary) server of the resource group Backup Server: The peer (secondary) 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 resource group to be switched back from the backup server to the primary server automatically when the primary server is available again Auto Bring In: An option for enabling the resource group to be bring in automatically when cluster starting Add Resource: Select the type of resource to be use Edit: Edit the configuration Bring in: The selected resource group will be activated and brought under the protection of ProNASHA.

7-15

7.6.7

Bring In Resource Group Properties

Bring out: The selected resource group will be terminated and brought out from the protection of ProNASHA. A resource group can be brought out of cluster to perform maintenance or troubleshooting. Note that a resource group is no longer guarded by ProNASHA after being brought out of cluster. Bring out a resource group currently accessed by client-end applications can cause data loss or corruption. Make sure a resource group is free before bringing it out. 7.6.8 Resource Group Manager Properties when Bring In

Add Resource Group: Add new resource group member Switch All Resources Group 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

7-16

7.7

Event Log Properties

All the messages generated by ProNASHA will be displayed in the Event Log. The messages can help users to identify the possible reasons that prevent ProNASHA from operating normally.

7-17

Appendix A

Glossary

A
ACL Access Control List (ACL) filters network traffic by controlling whether routed packets are forwarded or blocked at the router's interfaces. Router examines each packet to determine whether to forward or drop the packet, based on the criteria specified within the access lists. Access list criteria could be the source address of the traffic, the destination address of the traffic, the upper-layer protocol, or other information. APC smart APC Smart-UPS protects data by supplying reliable, network-grade power in either traditional Tower or Rack-optimized form factors for space constrained business critical applications. Rack Mount versions are the choice for rack optimized servers, server appliances, blade servers, other blade devices and rack-mounted network switches and hubs. AppleTalk Protocol The AppleTalk protocol allows multiple users to share resources, such as files and printers. The devices that supply these resources are called servers, while the devices that make use of these resources (such as a user's Macintosh computer) are referred to as clients.

C
CIFS Common Internet File System (CIFS) defines a standard remote file system access protocol for use over the Internet, enabling groups of users to work together and share documents across the Internet or within corporate intranets. CIFS is an open, cross-platform technology based on the native file-sharing protocols built into Microsoft Windows and other popular operating systems, and supported on dozens of other platforms.

D
DHCP Dynamic Host Configuration Protocol (DHCP) is a set of rules for dynamically allocating IP addresses and configuration options to workstations on a network. DNS Domain Name System (DNS) is the name resolution protocol for TCP/IP networks, such as the Internet. A DNS server hosts the information that enables client computers to resolve memorable, alphanumeric DNS names to the IP addresses that computers use to communicate with each other. Dynamic IP Dynamic IP is a term used to describe how IP address is dynamically assigned to computers as and when needed. Unlike Static IP addresses, the IP address is temporary.

E
EXT3 EXT3 is a journaling file system. It is compatible to the EXT2 file systems. You can switch back and forth between EXT2 and EXT3 on a partition without any problem.

F
Fail-free online firmware upgrade (The definition of the topic is yet not available) FTP File Transfer Protocol (FTP) is a way of transferring files over the Internet from one computer to another.

G
Gateway A computer system for exchanging information across incompatible networks by translating between two dissimilar protocols. May also describe any mechanism that gives access to another, such as an ISP, which acts as a gateway to the Internet. GNUZIP GNUZIP is a compression utility designed to be a replacement for compress. Its main advantages over compress are much better compression and freedom from patented algorithms. GUI GUI is the Graphical User Interface to a computer, and its elements include windows, icons, buttons, cursors, and scroll bars.

I
IP address Every computer connected to the Internet is assigned a unique number known as an Internet Protocol (IP) address. Since these numbers are usually assigned in country-based blocks, an IP address can often be used to identify the country from which a computer is connecting to the Internet.

L
Lmhost table The HOSTS or LMHOST file that contains lists of known IP addresses mapped to host names or NetBIOS computers names.

N
NAT Network Address Translation (NAT) is a program or piece of hardware that converts the IP address from a private address to a public address in real time. This allows multiple users to share a single public IP address. It also prevents access to these users from the outside without special configurations. NetBIOS NetBEUI is a raw NetBIOS frame protocol implementation that allows NetBIOS data grams to be sent out over the 'wire' embedded within LLC frames. NetBEUI is not required when using NetBIOS over TCP/IP protocols and it is preferable NOT to install NetBEUI if it can be avoided. NFS Network File System (NFS) is a type of distributed file system that allows NFS servers to give NFS clients access to their local file system using TCP/IP. Sun Microsystems originally created the NFS standard.

NIS Network Information Service (NIS) is a service that provides information that has to be known throughout the network, to all machines on the network. Novell Protocol The Novell NetWare protocol provides comprehensive support for every major desktop operating system, including DOS, Windows, Macintosh, OS/2, and UNIX. In addition, Novell provides extensive support for local area networks and asynchronous wide area communications. NTP server settings The Network Time Protocol (NTP) is designed to synchronize the clocks of computers over a network. NTP is used to synchronize the time of a computer client or server to another server or reference time source, such as a radio, satellite receiver, or modem.

P
Port number Port number is a number identifying a certain Internet application. For example, the default port number for the WWW service is 80. proNASVG home device Proware Network Attached Storage (proNAS) subsystems offer a reliable, cost effective way to add storage to the network. It is cross platform supports, (Windows, NT, Linux, Unix, MAC) for multi-users to share storage devices through Intranet and/or Internet.

R
RAID Redundant Array of Independent (or Inexpensive) Disks (RAID) is a category of disk drives that employ two or more drives in combination for fault tolerance and performance. RAID disk drives are used frequently on servers but aren't generally necessary for personal computers. Routing Routing is the act of moving information across an inter-network from a source to a destination. Along the way, at least one intermediate node typically is encountered.

S
Samba Samba is a suite of Unix applications that uses the Server Message Block (SMB) protocol. Many operating systems, including Windows and OS/2, use SMB to perform client-server networking. SNMP/MRTG Service Simple Network Management Protocol (SNMP) provides performance information and allows you to manage network servers, routers, hubs, and switches remotely. Multi Router Traffic Grapher (MRTG) is a freeware tool that supports the collection and display (in HTML pages) of SNMP statistics, thereby enabling you to monitor usage patterns over daily, weekly, monthly, and yearly periods.

Subnet Mask A local bit mask (set of flags) that specifies which bits of the IP address specify a particular IP network or a host within a sub network. An IP address of 128.66.12.1 with a subnet mask of 255.255.255.0 specifies host 1 on subnet 128.66.12.0. The subnet mask determines the maximum number of hosts on a sub network. Support trunking /load balance/fail over (The definition of the topic is yet not available)

T
Tape Device Tape devices allow large companies as well as end users to backup large amounts of data. Tape drives are capable of backing up a couple hundred megabytes to several gigabytes of information without having to spend large sums of money on disks. Telnet Telnet is a protocol for remote computing on the Internet. It allows a computer to act as a remote terminal on another machine, anywhere on the Internet.

U
UDP User Datagram Protocol (UDP) is a transport layer protocol in the TCP/IP protocol suite used in the Internet. UDP is used at the two ends of a data transfer. It does not establish a connection or provide reliable data transfer like TCP. UPS Uninterruptible Power Supply (UPS) is a device connected between a computer (or other electronic equipment) and a power source (usually an outlet). The UPS ensures that electrical flow to the computer is not interrupted because of a blackout and, in most cases, protects the computer against potentially damaging events, such as power surges and brownouts.

V
Veritas BackupExec Agent (The definition of the topic is yet not available) VLAN Virtual Local Area Network (LAN) is a network of computers that behave as if they are connected to the same wire even though they may actually be physically located on different segments of a LAN. Volume Groups A Volume Group (VG) is made up of a number of Physical Extents which may have come from multiple Physical Volumes or hard drives.

W
WINS Server A Windows Internet Name Service (WINS) server allows mapping NetBIOS names to IP addresses or centrally managing the name-to-address database.

X
XFS XFS is the next generation local file system for Silicon Graphics (SGI) workstations

and servers. It is a general purpose Unix file system that runs on workstations with 16 megabytes of memory and a single disk drive and also on large SMP network servers with gigabytes of memory and terabytes of disk capacity.