TerraBlock Users Guide

Transcription

Version 6.5.5 Setup & User Guide
PRODUCTS:
TERRABLOCK 24D/HA
TERRABLOCK 24D
TERRABLOCK 24EX/16/12/8
TERRABLOCK 8D
TERRABLOCK 8XS
TX16 EXPANSION CHASSIS
ACCESSORIES:
QLOGIC SANBOX, ATTO FIBRE CHANNEL SWITCHES
EDGE-CORE, HP ProCurve, NETGEAR ETHERNET SWITCHES
ATTO FIBRE HOST BUS ADAPTERS
SOFTWARE:
FACILIS
FACILIS
FACILIS
FACILIS
SHARED FILE SYSTEM
TERRABLOCK MANAGER
FILE MIGRATION TOOL
PROJECT MANAGER / VIEWER
TO THE EXTENT ALLOWED BY LOCAL LAW, NEITHER FACILIS TECHNOLOGY NOR ITS THIRD
PARTYSUPPLIERS MAKE ANY OTHER WARRANTY OR CONDITION OF ANY KIND, WHETHER EXPRESS OR
IMPLIED, WITH RESPECT TO THE FACILIS TECHNOLOGY PRODUCTS, AND SPECIFICALLY DISCLAIM THE
IMPLIED WARRANTIES OR CONDITIONS OF MERCHANTABILITY, SATISFACTORY QUALITY, AND FITNESS
FOR A PARTICULAR PURPOSE.
Limitations of Liability
To the extent allowed by local law, the remedies provided in this Warranty Statement are the customer's sole and
exclusive remedies.
TO THE EXTENT ALLOWED BY LOCAL LAW, EXCEPT FOR THE OBLIGATIONS SPECIFICALLY SET FORTH IN THIS
WARRANTY STATEMENT, IN NO EVENT SHALL FACILIS TECHNOLOGY OR ITS THIRD PARTY SUPPLIERS BE LIABLE FOR
DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES, WHETHER BASED ON CONTRACT, TORT,
OR ANY OTHER LEGAL THEORY AND WHETHER ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
Local Law
This Warranty Statement gives the customer specific legal rights. The customer may also have other rights that vary from
state to state in the United States, from province to province in Canada, and from country to country elsewhere in the
world.
To the extent that this Warranty Statement is inconsistent with local law, this Warranty Statement shall be deemed
modified to be consistent with such local law. Under such local law, certain disclaimers and limitations of this Warranty
Statement may not apply to the customer. For example, some states in the United States, as well as some governments
outside the United States (including provinces in Canada), may:
Preclude the disclaimers and limitations in this Warranty Statement from limiting the statutory rights of a consumer (e.g.,
the United Kingdom);
Otherwise restrict the ability of a manufacturer to enforce such disclaimers or limitations; or Grant the customer
additional warranty rights, specify the duration of implied warranties which the manufacturer cannot disclaim, or not allow
limitations on the duration of implied warranties.
FOR CONSUMER TRANSACTIONS IN AUSTRALIA AND NEW ZEALAND, THE TERMS IN THIS WARRANTY STATEMENT,
EXCEPT TO THE EXTENT LAWFULLY PERMITTED, DO NOT EXCLUDE, RESTRICT, OR MODIFY, AND ARE IN ADDITION
TO, THE MANDATORY STATUTORY RIGHTS APPLICABLE TO THE SALE OF FACILIS TECHNOLOGY PRODUCTS TO SUCH
CUSTOMERS.
© Facilis Technology Inc. TERRABLOCK Version 6.5.5 Setup & Users Guide, January 2016
2
Contents
Page Number
Using This Guide
Who Should Use This Guide
What This Guide Contains
Symbols and Conventions
Documentation Comments
How to Download this Manual
Overview
7
8
Chapter 1 – Hardware
Server Protection Features
TerraBlock Enclosure Front Panel
10
24D Front Panel LED Indicators
24D Front Panel Buttons
8XS Front Panel Buttons
8XS Front Panel LED Indicators
Enclosure Front Panel Cover
Rear Panel
11
12
Power Supplies
Fans
VGA
Ethernet
Mouse/Keyboard
SAS Controller Slots
Fibre Channel / Ethernet Slots
PSU Alert Mute Button (24D, 24EX)
Chapter 2 – Hardware Installation
Before You Begin
Rack Mounting the 24D/24EX Enclosure
Installing the Drives
Mouse/Keyboard
Monitor
Power Cords
Client Hardware Installation
Cabling the TerraBlock Server
Fibre Channel Cabling
Cabling the Fibre Switch
Ethernet Cabling
Cabling the Ethernet Switch
Turning on the TerraBlock Server
3
14
16
17
18
20
Chapter 3 – Setup and Administration
System Setup
21
Management Tools
Troubleshooting/Service Tools
Tools Volume
TerraBlock Manager
TerraBlock Manager User Mode Menus
Volumes Tab
Volumes Tab – Button Functions
Mount
Un-mount
Update Read-Only
Add Users
Mount Properties
Show & Hide Permissions
Create Volume
Delete Volume
Change Volume
User Access Permissions
Refresh
23
25
26
30
29
31
32
34
38
Users Tab
Users Tab – Button Functions
39
Create User
Delete User
Change Access
Copy User
Add Volumes
Refresh
Volume Access Permissions
40
41
System Tab
TerraBlock Manager on the Server
41
43
Additional Button Functions
Mount and Un-mount by Index
Add Attached Volumes
Synchronize Users
System Tab: Locate
44
45
Admin Settings Tab
LDAP Tab
LDAP Tab – Button Functions
46
48
49
50
Configure LDAP
Refresh
Sync Selected
Sync All
TerraBlock Client Setup
51
Mac and Windows Clients
Linux Clients
4
Ethernet Shared File System Setup
Single Ethernet Connection
Enabling the Ethernet Option on the Server
Enabling the Ethernet Option on the Clients
Teamed Ethernet Connection
Teaming the NIC Connections
10Gbit Ethernet Connection
Creating and Managing Users
Username and Password Feature
Logging in to the TerraBlock System
Changing Passwords
LDAP/Active Directory User Feature
Creating Volumes
Single-user Write Volumes
Multi-user Write Volumes
DynaRAID
Raid Descriptions
Creating Tandem Volumes
Formatting Options
Creating Volumes Larger Than 8TB
Tandem Volumes
59
60
61
62
63
66
68
69
70
71
73
74
75
77
80
81
82
Chapter 4 – Working with the Shared File System
Launching TerraBlock Manager and Creating Volumes
Changing Single-user Write Volumes to Multi-user Write
Mounting Multi-user Write Volumes
Working with Multi-user Write Volumes
83
84
85
Chapter 5 – Volume Permissions and Workflows
User Permissions to Volumes
Volume Workflows – Single-user Write
Volume Workflows – Multi-user Write
87
Chapter 6 – Facilis File Migration Tool
Setup and Usage
89
Chapter 7 – Facilis Project Manager / Viewer
Facilis Project Manager Overview
Facilis Project Manager Usage
Facilis Project Viewer
92
93
95
5
Chapter 8 – Using the CommandApp
Running the CommandApp as an Application
Running the CommandApp from a Command Line
96
98
Appendix A – Additional Setup Tools
Tools Volume Configuration
OSX Icon Installation
Additional Client Software
TerraBlock Manager Keyboard Shortcuts
100
101
102
Appendix B – Manually Formatting Larger than 8TB
Formatting Steps
103
Appendix C – Working with External Tandem Volumes
External Tandem RAID5 using ATTO Power Center
Formatting Multi-server External Tandem Volumes - Mac
Formatting Multi-server External Tandem Volumes – Windows
105
106
106
Appendix D – Server Hardware Specifications
Dimensions and Weight
Environment
Electrical Load
Connectivity
110
6
Using This Guide
Who Should Use This Guide
This guide is intended for any user or administrator of the Facilis TerraBlock
system.
What This Guide Contains
This guide covers the information you will need to:



Install the enclosure and drives
Administer the volumes and configure user access
Understand the workflow of the TerraBlock
Symbols and Conventions

Important Caution or Instruction

Related Information or Tip

Checklist

Description or Definition
Documentation Comments
If you have comments relating to the documentation, please E-mail
[email protected], and specify the page and error or omission in the guide.
How to Download This Manual
We offer a download location on our main web site.
Go to http://facilis.com/support/.
7
Overview
The Facilis TerraBlock Server is a turnkey system that will enable collaboration
between different editorial and/or content creation workstations within the same
facility. The following TerraBlock User Guide explains server and accessory
installation, and contains connectivity and configuration instructions for end users
and installation technicians.
Chapter 1 - Hardware
The TerraBlock protection features and physical attributes of your server are
discussed in this section.
Server Protection Features
The TerraBlock comes standard with 8, 12, 16 or 24 physical hard drives, depending
on your TerraBlock model. Through the TerraBlock software, virtual volumes are
created utilizing all the drives to provide full bandwidth. Any of the hard drives are
hot swappable. Automatic recovery will take place for a replaced failed drive when
DynaRAID protection is enabled. DynaRAID protection allows for one physical hard
drive failure at any given time per TerraBlock chassis. DynaRAID and other software
features will be described later is this guide.
The TerraBlock Server chassis used for the 24D and 24EX models contain
redundant field replaceable power supplies. It is recommended that each power
supply be connected to a separate circuit to maintain proper grounding. The
TerraBlock 8D and 8XS contain a single power supply. An uninterruptable power
supply (UPS) is also highly recommended.
All TerraBlock Servers ship with field replaceable internal fans.

Never leave the TerraBlock cover off for more than 2 minutes as the hard
drives may overheat
8
TerraBlock Enclosure Front Panel
The front panel of the TerraBlock system is used to start up and shut down the unit
and to monitor hard drive activity through LED indicators. The drive carriers are
inserted in the front of the unit during initial installation, or in the event of drive
replacement. Software updates can be loaded via USB drive in the front or rear of
the unit or by downloading from www.facilis.com/media. The 24D and 24EX front
panel is shown below.
LED indicators from left to right:
1. Internal System Disk Activity
 Blinks amber when active, typically only LED 1 is used
2. Ethernet Activity
 Blinks green when active, only LED’s 2 & 3 are used
3. Temperature Indicator
 Green when OK
 Flashing green on error with audible alarm
4. Fan speed Indicator
 Green when OK
 Flashing green on error with audible alarm
5. Power Indicator
 Green when powered on
 Flashing green when a power supply fails with audible alarm
Front panel buttons from left to right
1. Server Reset
 Only use when instructed. Do not use to power cycle the unit
2. Alarm Mute
 Silences the fan and temperature audible alarms
3. Power On/Off
 Use to power on the unit or to initiate Windows shutdown
9
The 8XS unit is shown below
!
Front panel buttons from left to right
1. Power On/Off
 Use to power on the unit or to
initiate Windows shutdown
2. Server Reset
 Only use when instructed
 Do not use to power cycle
the unit
LED indicators from left to right:
1. Power Indicator
 Green when powered on
2. Internal System Disk Activity
 Blinks green on activity
5. Temperature Indicator
 Off when OK
 Flashing amber on error
6. Power Warning
 Off when OK
 Flashing amber on error
The 8D unit is shown below
10
Enclosure Front Panel Cover
The 24D and 24EX TerraBlock enclosures have a front cover that can be kept in place
to prevent access to the physical hard drives. If access to the drives is necessary,
the cover is attached via two thumb screws at the top left and right. The cover is
hinged at the bottom. A lock spring must be disengaged to remove the cover. The
front panel cover must be removed to install or remove the bottom row of drives
when fully populated (24D models). The 8XS model has a lockable hinged cover that
swings to the right or top to bottom if the 8XS is rack mounted.
24D & 24EX
8XS
Front cover thumbscrews
Front cover lock
Front cover hinge
Front cover hinges
8D
Front cover thumbscrews
Front cover hinges
11
Rear Panel
The rear panel (back of the server) is the location for direct connect client
connectivity, switch hardware connectivity, control and monitor ports. Power supply
cabling and cooling fans are also located in this area. The diagram below shows the
24D and 24EX enclosure rear panel (earlier models will differ).
PSU Alert Mute Button
Keyboard & Mouse
USB Ports
Optional ATTO FC or Ethernet
NIC Controllers
Ethernet Ports
Monitor Port
B
L
A
N
K
1
0
G
A
T
T
O
S
A
S
S
A
S
A
T
T
O
S
A
S
SAS disk controllers
with blank bulkhead
AC Power Input
 The 8D and 8XS rear panel is very similar to this diagram when rack
mounted, but a single power supply.

Power Supplies – One power supply in the TerraBlock 24D and 24EX chassis is
replaceable while the unit is running. The unit will run as long as at least 2
power supplies are active. The 8D and 8XS do not have a redundant power
supply, and require a power supply or chassis replacement through your reseller
if failure occurs.

Fans – The high-speed internal fans maintain an ideal operating temperature
within the enclosure. Fan units can be removed while the TerraBlock is running if
a replacement is necessary.

VGA – The VGA port is available for monitoring the server locally; attaching a
monitor (not supplied) to the server is necessary for software installation and
troubleshooting. A standard 15-pin VGA monitor cable is supported.

Ethernet – The Ethernet ports are supplied for network access to the unit,
communication to the optional Fibre Channel switch, and when used in
conjunction with the Facilis Shared File system, access from Ethernet clients to
the TerraBlock virtual volumes. Direct Ethernet connectivity can be configured
using a single Gigabit Ethernet port on the server. A combination of 2 or more
12
Gigabit Ethernet ports (additional Ethernet hardware may be added) can be
(Teamed) for additional bandwidth and performance. See Fibre
Channel/Ethernet Slots below.
 Running windows network software on the TerraBlock for the
purpose of sharing volumes is not supported. Any Ethernet
connectivity must be supplied through the Facilis Shared File System
(SFS).
 Keyboard/Mouse – The keyboard/mouse ports are available for direct control of
the server. Standard PS2 or USB keyboard and mouse are supported but not
included.
 SAS Controller Slots – The SAS controller cards for the server media hard
drives use slot 1, 3 and 4 on the 24D and 24EX and slot 1 on the 8XS (with latest
TerraBlock models). Slots are numbered starting from the right if standing at the
rear of the unit. These slots are unavailable for any other use.
 Fibre Channel/Ethernet Slots – The number and type of Fibre Channel and
Ethernet host bus adapters (HBA’s) may vary depending on your configuration.
There is a maximum of 4 additional HBA’s that can be added. This can be all Fibre
Channel HBA’s (up to 8 direct connect FC ports), all 10Gbit Ethernet (up to 8
direct connect 10Gbit Ethernet ports) or a combination of both. This may also
include 1G Ethernet hardware. Some HBA’s may need to be removed to free a
slot if the server is fully populated.
 PSU Alert Mute Button (24D, 24EX) – The enclosure sounds an alarm beep
whenever it detects a power supply or fan failure. The Mute button stops the
alarm until the next error occurs. Pressing the Mute button only silences the
alarm—it does not correct the condition that caused it.
13
Chapter 2 – Hardware Installation
This chapter describes how to install your TerraBlock shared storage system and
additional hardware peripherals.
Before You Begin
The location of the unit should be cool, clean and vibration-free. Make sure you have
all the components that shipped with the system available at the time of installation.
If you are missing any of the components listed below, do not attempt installation
until contacting Facilis Technology customer service at +1 978-562-7022.
After unpacking the TerraBlock kit, check the contents of the kit against the following
list to be sure you have received all the components. The kit contains:












One TerraBlock Server enclosure or chassis
One or three power cords
USB stick containing the TerraBlock Software and Documentation
8, 12, 16 or 24 numerically labeled SATA drives in carriers (boxed
separately)
One SATA drive labeled “Spare”
A rack-mount kit (optional on 8XS and 8D)
An enclosure front cover or bezel (located on chassis)
QLOGIC 8Gbit or ATTO 16Gbit Fibre Channel switch (optional)
QLOGIC or ATTO switch rack mount kit or rack hardware (optional)
Edge-Core (formerly LG-Ericsson/SMC) 24 or 48 port managed 1Gbit, HP
ProCurve 1Gbit/10Gbit, or NetGear RJ45 10Gbit Ethernet Switch (optional)
ATTO 8Gbit or 16Gbit Fibre Channel client cards (optional)
Myricom or ATTO 10GBit Ethernet client cards (optional)
Rack Mounting the 24D/24EX Enclosure
The base configuration of the TerraBlock system includes rack rails for mounting
the server in a standard 19” rack containing rear rails. If you are installing the
TerraBlock enclosure in a rack (recommended), follow the instructions supplied in
the rail kit to install the rack-mount rails. Be sure that:





The rails attach as far forward on the TerraBlock enclosure as possible.
The rails do not interfere with the power strips, power cords, or other cables
at the rear of the rack.
The rails allow the unit to slide completely into the rack.
Power supply vents and other airflow are not restricted when installing the
unit in a rack.
A reliable grounding path is maintained within the rack system. This unit must
be connected to earthen ground.
 Mounting the TerraBlock enclosure on rack-mount rails is a twoperson job! The enclosure is heavy, and both sides need to be in
alignment to fit properly. The server should be installed or rack
mounted without drives installed. If you try to mount the enclosure
alone, you may damage the server or injure yourself.
14
Installing the Drives
The TerraBlock SATA drives ship boxed separately from the enclosure.
 If the SATA drives have been left at or below 45F (7C) for several hours
(on a delivery truck or loading dock), allow the drives to return to room
temperature before inserting and powering on the unit. Drive failure may
occur if cold drives are powered up before warming.
24D Drive Locations
24EX Drive Locations (8 Drives)
8XS Drive Locations
8D Drive Locations
1. Slide the drive carrier assembly into the appropriate slot until the latch makes
contact with the enclosure.
2. Push the latch toward the enclosure to finish sliding the drive and carrier into the
enclosure. You will hear the latch click when the drive and carrier are seated in
the slot. If you encounter resistance do not force the latch closed.
Remove the drive and check the connector and slot for foreign objects.
3. Repeat steps 1 through 5 for all remaining drives.
 The front bezel of the 24D chassis will need to be removed to insert all
24 drives. Disengage the latch spring on the left side of the cover back to
free the left pin, and move the bezel left. To replace, hold the latch
spring back and line up the two pins and slide into position.
15
Keyboard/Mouse
A keyboard and mouse (not supplied) should be installed prior to powering on the
TerraBlock Server. If possible, use a USB keyboard and mouse, as these will remain
enabled after boot and can also be connected after the server is on. PS2 devices may
require a reboot after they are connected.
1. Locate an available keyboard and mouse.
2. Locate the proper USB or PS2 ports using the symbols on the rear of the unit.
3. Plug the connectors into the proper ports securely.
Monitor
A monitor (not supplied) is required for initial setup and software updates, and is
recommended for daily usage or in the event of troubleshooting. To install a monitor:
1. Locate the VGA port on the rear of the unit. The VGA port is a blue female 15pin DIN connector.
2. Plug the monitor into the VGA port.
3. Supply power to the monitor and turn it on.
Power Cords
Connect the power cords (supplied) into the AC ports on the rear of the enclosure.
Do not start the unit until all power cords are connected.
Client Hardware Installation
Client hardware will depend on your TerraBlock Server configuration. Configurations
may consist of all Fibre Channel, all Ethernet, or a combination of both.
All Fibre Channel based configurations require hardware installation in your Mac,
Windows or Linux client. ATTO Technology is the supported Fibre Channel HBA to be
used with your TerraBlock Server. Please follow the manufacturer’s instructions for
installing hardware in your client workstation (Mac Pro, HP Workstation, etc.). It is
recommended to use the fastest PCIe slot available. ATTO ThunderLink devices are
also supported for Mac specific workstations that do not have an available PCIe slot
and are Thunderbolt capable (MacBook Pro, iMac). After the hardware is installed,
power on the client and install the proper drivers and firmware (see the TerraBlock
Release Notes for supported driver and firmware versions and more in depth ATTO
Fibre Channel HBA configuration).
 The ATTO Configuration Tool must be installed on each client workstation to
verify and adjust the HBA settings.
Ethernet client configurations may or may not require hardware installation. The 1G
Ethernet onboard adapters can be used with any Mac, Windows or Linux client for
connectivity to the TerraBlock Server. 10G Ethernet configuration will require
hardware be installed in your client. Myricom and ATTO 10G HBA’s are supported.
Please follow the manufacturer’s instructions for installing hardware in your client
workstation (Mac Pro, HP Workstation, etc.). It is recommended to use the fastest
PCIe slot available. ATTO ThunderLink devices are also supported for Mac specific
workstations that do not have an available PCIe slot and are Thunderbolt capable
(MacBook Pro, iMac). After the hardware is installed, power on the client and install
the proper drivers and firmware (see the TerraBlock Release Notes for supported
driver and firmware versions).
16
Cabling the TerraBlock Server
The following explains how to cable the TerraBlock system to clients directly or any
switches in your configuration. Keep the location of the edit rooms in mind when
installing the TerraBlock. There is a 380 meter limitation in 4Gbit, 150 meter
limitation in 8Gbit, and a 100 meter limitation in 16Gbit using OM3 50 micron rated
cabling. Ethernet connectivity for CAT 5E, CAT 6 or CAT 7 cabling has a limitation on
length of 100 meters (328ft) in 1Gbit. Ethernet connectivity for 10Gbit optical cabling
has a length limitation of 300 meters (984ft) using OM3 rated cabling. (See
Appendix D or call Facilis customer support for additional information on cabling
options).
Fibre Channel Cabling
Up to 6 users may connect directly to the TerraBlock Server with optical Fibre
Channel. Direct client connections are based on the number of Fibre Channel cards
that are installed in your server.
The TerraBlock may also be connected to a switch via single or multiple 4/8/16Gbit
connections. The client workstations would also connect to the switch. All connectors
are “LC” type, and the supported cable type is duplex (send/receive) multimode
fibre. The LC connector will plug into an SFP module. The SFP is inserted in the
fibre channel card on the server and client. SFP’s are also used in the fibre switch
for connectivity between the server and clients. All SFP’s are removable and
replaceable.
This image represents an 8Gbit dual-channel fibre card.
Only one port is used per-client. If using a switch, a single
or dual connection (shown here) can be run to the switch
for connectivity. Additional free ports on the server may
be used for more direct-connect clients an additional
switch.
If a 4Gbit client or switch is connected, a single LED will be
illuminated; if an 8Gbit client or switch is connected, both
LEDs will be illuminated. At least one LED will be active
when linked.
If the TerraBlock server is attached to a switch through a
single connection, an additional connection to the switch
will provide more balanced performance (recommended).
See Cabling the Fibre Switch in this chapter for more details.
A Fibre Channel cable is comprised of send and receive strands, these must be
mated properly to the send and receive ports on the SFP. If your cable was built as
an LC-to-LC patch cable, the connector should be built to achieve this. If you’re
patching through another cable via a union or patch field, you may have to
determine the send and receive sides. Try each combination of port connection and
connector ends (reversing if necessary) until a link light appears.
 ATTO Fibre Channel host bus adapters contain class 1 laser emitting
devices. Keep the transmit port covered whenever a cable is not
connected. It is good practice to keep open ports covered. Avoid
staring into open ports or aperture
17
Cabling the Fibre Switch
Several QLOGIC switches are supported ranging from 8-16 port 4Gbit models to 820 port 8Gbit models. ATTO 16Gbit switch models are also supported. The diagram
below shows a standard single-server, dual-zone (0-7; 8-15) configuration, with two
channels from the server fibre channel card connecting to the first (0) and last (15)
switch ports. The clients should be balanced across the remainder of the ports. The
lights above the switch ports show activity and link, regardless of the connection
speed (4Gbit or 8Gbit).
Activity
Link
Server Ch.1
Server Ch.2
Single Server with dual connection (switch must be zoned)
In a multi-server workgroup, there will be additional ports dedicated to server
connectivity. A configuration sheet that ships with each switch from Facilis
Technology describes the recommended zoning in detail.
Ethernet Cabling
There are two methods of connecting the TerraBlock Server to an Ethernet switch via
1Gbit Ethernet diagrammed below. Alternatively, you can install a 10Gbit Ethernet
card to connect either directly to a client with the model card or to connect to the
Ethernet switch with the 10Gbit uplink option (servers shipped after 8/1/2010).
1Gbit Clients
18
1Gbit Clients
Cabling the Ethernet Switch
There are multiple switch options that are supported for the Facilis Shared File
System (SFS) over Ethernet configurations (Facilis Shared File system is required for
all Ethernet connections). In addition to 1Gbit connectivity, some switch models
support connecting via the 10Gbit uplink option (10Gbit/1Gbit), all 10Gbit Optical,
and all 10Gbit RJ45 (copper).
There are no specific cabling locations for the switch itself. The Facilis Shared File
System cabling will consist of either one or four cables (teaming option) from the
TerraBlock Server to the switch. Cabling may be connected to any port on the
Ethernet switch.
For the 10Gbit option Facilis supports the optical (LC) version of the 10Gbit Ethernet
card as well as a copper (Cat 5E, 6, 7) RJ45 version. Cabling will vary based on
which model TerraBlock Server is used and/or the purchased Shared File System
Ethernet Option. The 10Gbit optical uplink connection in the rear of the switch
requires an SFP+ module. For troubleshooting purposes, cabling should be done in
an organized fashion so cables can be easily identified.
Not shown here: Established link LED’s
When a link has been established with the TerraBlock Server or a client system, an
LED light will illuminate on the switch where the port number is listed. Additional
configuration on the TerraBlock Server and clients will be required (see Ethernet
Shared File System Setup for more information).
19
Turning on the TerraBlock Server
Before turning on the TerraBlock Server, make sure that you have all the drive
carriers installed in the server enclosure per the diagram(s) above. Once all of the
drive carriers are properly installed in the TerraBlock Server enclosure, you can then
turn on the TerraBlock.
The Power button is on the front indicator panel. Press it once. After a delay of 3-4
seconds, the system will power on. The system has been configured from the factory
to login to the operating system automatically with user account “Facilis” and no
password.
 It is the responsibility of the site administrator to maintain any desired
software security options, including passwords, for the TerraBlock Server.
Upon reaching the Windows Explorer (desktop), launch the SMDriveMonitor tool
shortcut (yellow Facilis icon) on the desktop. The text on screen should state that the
Facilis storage service has started, list the version of the service, and display the
date and time.
 If your TerraBlock Server was ordered with 16Gbit Fibre Channel
hardware, a password “facilis” (without quotes) will be set to log into
the operating system.
 REFER TO THE TERRABLOCK RELEASE NOTES FOR CLIENT SOFTWARE
INSTALLATION INSTRUCTIONS.
20
Chapter 3 – Setup and Administration
The TerraBlock system has software management tools pre-installed on the server.
The following covers these tools that are installed prior to shipping.
The most important and most commonly used is the TerraBlock Manager. It allows
for user and volume management. The default user that launches the TerraBlock
Manager on the server will have the ability to add, change and remove volumes;
add, change and remove users and assign permissions to users. A TerraBlock user
given Admin permissions can also perform these functions from any client
workstation. With the TerraBlock Manager you can be quickly off and running with
your Server.
System Setup
After the server is installed and powered on, no additional configuration is required.
The disk set was created prior to shipping and is presented to the TerraBlock
Manager application. You can begin allocating the storage into virtual volumes.
When the TerraBlock is shipped from the factory, there are no volumes and no
users; these will need to be created. Administrator access is given when the
TerraBlock Manager is launched on the TerraBlock Server itself, and volume/user
creation can occur here. Alternately, the first user to launch the TerraBlock Manager
from a client connected to a new TerraBlock Server is given Administrative access,
and all administrative functions can be accessed from that client.
There are several applications that can be launched on the TerraBlock Server itself:
Management:
 Facilis TerraBlock Manager
 SMDriveMonitor
 SMManager
 Web-based Switch Management

Facilis TerraBlock Manager
Looking at the TerraBlock Server’s desktop, you’ll find the main tool for both
client and administrator control of the system. The TerraBlock Manager will
display different information and functionality, depending on the access setting of
the TerraBlock client (Admin or Normal user permission). This is the tool that the
administrator will use to create volumes, users, and assign access and
permissions.


Troubleshooting/Servicing:
 Drive Checker
 Data Verifier
 ATTO Configuration Tool
The Facilis TerraBlock Manager is launched from “Program Files\Facilis
\TerraBlock\Manager\Windows Manager” or the blue desktop shortcut. The
program name is TerraBlockManager.exe.
SMDriveMonitor
This tool is used to monitor the output of the service during operation. The
SMDriveMonitor will display the version, and time/date of the service startup, any
special features licensed on the system, as well as the drives found in the disk
set. The SMDriveMonitor also displays any drive errors and any recovery or
DynaRAID protection activity, including the percentage of recovery while in
progress.

The SMDriveMonitor is launched from “Program Files\Facilis \TerraBlock” or
the yellow desktop shortcut. The program name is SMDriveMonitor.exe
21
 SMManager
The SMManager tool is a command-line interface for the administration and
management of TerraBlock volumes and users. It is suggested that SMManager
only be used at the recommendation of, and with assistance from, Facilis
Technical Support.


The SMManager is launched from “Program Files\Facilis\TerraBlock\Utilities”
or the red desktop shortcut. The name of the program is SMManager.exe
QLOGIC Switch Management
When a Fibre Channel switch is included with a TerraBlock order, managing the
QLOGIC switch may be necessary. This can be performed from the TerraBlock
Server. One of the Server’s Ethernet ports can be configured to connect to the
switch. The QLOGIC switch management software allows the administrator to
zone and monitor the performance of the switch.
Web-based Switch Manager software using a default browser is used to establish
connection to the Switch. The IP address of the Server’s network interface card
(NIC) should be verified and may need to be changed to connect. The NIC of the
server should be set to a subnet matching the Switch (10.0.0.x). The Switch has
a default IP address of 10.0.0.1.
 After connecting using the web based Switch manager, you may need to ‘Add
Fabric’ and type the IP address (default is 10.0.0.1), user name and password
(default is “admin”/”password”).
 Facilis DriveChecker
DriveChecker is a performance diagnostic tool for SATA and SAS based chassis’
to exercise drives in the server. When a certain drive or controller is suspected to
be underperforming, this utility can determine if the drive is in need of
replacement. See “Appendix A: Additional Setup Tools” for more information.

A resulting log file will be generated by DriveChecker in the same directory
where the utility is run. The log file should be sent to [email protected] for
analysis when requested.
 ATTO Configuration Tool
TerraBlock servers configured with Fibre Channel interface cards to connect to
client stations or a Fibre Channel switch will have the ATTO Configuration Tool
pre-installed. ATTO Celerity 42XS, 42ES, 82EN or 162E model cards can be
viewed and configured using this tool. In some legacy configurations, an ATTO
Celerity 22XH may be used. The ATTO Configuration Tool will allow a system
administrator to set the Connection Mode, update firmware, and check ATTO
driver versions. See the Facilis TerraBlock 6.5 Release Notes for more
information. This tool should be installed on all client stations with fibre channel
hardware.
22
 NOTE: Version 3.38 (or higher) of the ATTO Configuration Tool is required in
order to configure an ATTO 8Gbit Fibre Channel interface card. Config Tool
version 4.08 (or higher) is required for 16Gbit cards. Both are provided with
this release.
Tools Volume
The Tools volume allows communication between the TerraBlock Server and the
TerraBlock Manager software on the clients. The Tools volume is a 1GB default Read
Only volume in each TerraBlock system and cannot be removed or deleted. It is
mounted by default on every fibre connected client workstation.
The Tools volume will contain a single file called “Control” as part of the factory preconfiguration. This file must reside on the Tools volume for proper communication
with the server by Mac Fibre Channel clients and all Ethernet clients (Mac, Windows
and Linux).
If there is more than one server being installed into the same facility, there should
be a separately named Tools volume for each server. The name of each Tools
volume must be different, and follow the convention: Tools; Tools1; Tools2; Tools3;
etc. The Tools volume may require renaming for a multiple server environment due
to an incremental storage upgrade or if an additional server is added.

The Site Administrator must configure or verify all Tools volumes
have unique names within the TerraBlock Manager for certain
features to work properly.
 Renaming a Tools volume with all caps (TOOLS) within the TerraBlock
Manager is not supported. Only a numerical value can be added (1-8).
 Mac OS 10.10 or higher requires that the Tools drive be excluded from
Spotlight indexing in order for proper functionality. See Tech note TN049 for more details.
The Tools volume name may be changed within the TerraBlock Manager through the
Change Volume dialog. The Tools volume label in the OS as well as the contents of
the Tools volume and/or its filesystem may be changed by obtaining Write access to
the Tools volume. See Appendix A: Additional Setup Tools for more information.
23
TerraBlock Manager
The TerraBlock Manager is used to create and change volumes and users, assign
volumes to users, mount, un-mount and update volumes. The TerraBlock Manager
can be launched from the blue shortcut icon after the server is powered on. These
examples show the Mac OSX client TerraBlock Manager. The Windows clients or the
Server itself, and Linux versions are identical in look and functionality. Areas of the
TerraBlock Manager can be customized to suit each user.
Mac TerraBlock Manager Volumes Tab– Administration Mode
The columns in the Volumes tab are
selectable/de-selectable by right-mouse
click on the headings bar. Right clicking
will display a list of all columns which
are selected by default. When selecting
a listed column, it will become “unchecked” removing the column from
the Volumes Tab display. For example,
a facility with a single server can deselect the server column as the name
of the server is not needed.
Volume tab column selector
The “Autosize All Columns” feature will adjust the column widths to allow for
the widest line item in the column. Column positions can also be moved further
customizing the Volumes tab. The column position changes are saved on a per client
machine basis, not by individual user.
24
TerraBlock Manager User Mode Menus
Mount Read Only volumes as local drives (Windows) – When selected, Singleuser Write volumes mounted Read Only will appear as local disks rather than
removable disks in Windows Explorer. They may appear writeable to some
applications, even though the volume is locked for write access at the TerraBlock
Server.
This setting should only be used with software applications that will not allow use of
removable volumes. Avid DS is an example of software that requires this setting. All
other Avid products, as well as most other software applications will not require this,
so it is recommended to leave this setting disabled.
Auto update Read Only Volumes (Windows and Mac OSX) – When mounting a
Single-user Write volume as Read Only, updates will not occur to the volume
contents until the ‘Update Read Only’ button is selected in the Manager, or the ‘Auto
update Read Only volumes’ option is selected in the User Mode menu. A dialog box
will appear after selecting this menu option, and a time should be entered for the
update cycle. 30 minutes is the default and recommended interval.
After setting the ‘Auto update Read Only volumes’ option, the TerraBlock Manager
must remain open in the background in order to update volumes at the given
interval. For OSX, this feature supports only HFS+ volumes (Mac OS Extended file
system). For Windows, NTFS volumes are supported.
File System Emulation Mode (Windows and Mac OSX) – When mounting a Multiuser Write volume, this setting changes the appearance of the volume’s filesystem.
Multi-user Write volumes mounted using File System Emulation Mode will appear as
‘avidfs’ in the client OS. If this setting is disabled, the Multi-user Write volume will
appear as ‘factbfs’ in the client OS.

This setting is enabled by default and should be enabled whenever using
Multi-user Write volumes with Avid editorial clients.
Un-mount all volumes on exit (Windows, Mac OSX, Linux) – When this setting is
enabled, all volumes will be un-mounted upon close of the TerraBlock Manager
application. Because of this, it is necessary to have the TerraBlock Manager open in
the background while the workstation requires use of the TerraBlock volumes.
DAW Mode (Mac OSX) – This setting changes the internal appearance of mounted
Single-user Write volumes from Removable to Fixed in the OS. Applications that do
not support removable volumes for media locations will require this setting.
Examples of these applications are Pro Tools and Adobe CS4.
 After changing the setting, volumes must be un-mounted and the client
should be rebooted before re-mounting volumes.
Read Only support for legacy applications (Mac OSX) – This setting changes the
appearance of Single-user Write mounted volumes from hardware-locked to
software-locked Read Only. Software locked Read-only volumes will use the volume
attribute in the “Get Info” window to designate the volumes are Read Only. Some
older applications on OSX will not work with hardware-locked Read Only volumes. It
is recommended that this setting remain off.
25
Export to .csv
Users may export the contents of the TerraBlock Manager’s current window display
to a .csv file by using the ‘Export to .CSV’ command under the File Menu rather than
the User Mode menu. This .csv file can be then imported into any application that
supports comma-separated value files.

If the user wishes to view all the members of a multi-server External
Tandem volume in the .csv document, they must first expand the External
Tandem volume display in the Volumes Tab prior to exporting the .csv file.
To expand the display of an External Tandem Volume, double-click the
External Tandem Volume name. The arrow icon next to the volume name
will turn down and the names of individual tandem pieces that make up the
volume will be displayed (~1, ~2, etc.).
Volumes Tab
The following describes each column listed displayed in the Volumes tab:
Name – The name of the volume as given by the administrator at time of creation.
If AutoFormat is used, the formatted volume label in the client OS will match the
TerraBlock name column.
If AutoFormat is not used when creating volumes, the volume must be formatted
and labeled manually in the client OS. It is highly recommended to use AutoFormat
at all times.
 For proper identification of volumes and the successful mounting and
un-mounting of volumes on client workstations, the formatted disk
label name must exactly match the TerraBlock volume name. Again,
AutoFormat is highly recommended when creating volumes.
Current User (“Editor” above) – This column shows the current mounted state of
a volume for the logged in user.
 W - This indicates the volume in the Name column is mounted on the
local workstation with write access. This row will be highlighted GREEN or
ORANGE depending on whether the volume is mounted Multi-user Write or
Single-user Write.
 R - This indicates the volume in the Name column is mounted on the
local client workstation with Read-Only access. This row will be highlighted
BLUE.
 - (dash) - This indicates the volume in the Name column has not been
mounted by the local workstation. This row will not be highlighted.
Sys (System) – The current mounted state of a volume across the entire network.
 W - This indicates the volume in the Name column is mounted on
another client workstation or the TerraBlock Server with write access.
26
 R - This indicates the volume in the Name column is mounted on
another client workstation with Read-Only access.
 - (dash) - This indicates the volume in the Name column has not been
mounted by any workstation or the TerraBlock Server on the network.
State – The state of a volume is related to the physical drives that comprise the
volume. The possible states are “OK”; “DEGRADED”; “DAMAGED”; “RECOVERING”.
 OK - The physical drives installed in the TerraBlock Server that
comprise the volume are all present and working. This state will exist
under normal operation, or after a drive recovery is complete.
 DEGRADED - A physical drive in the group that comprises the volume
has failed or incurred an error, and data has been written to the volume
since the drive failure occurred. If the volume is protected, the state will
return to ‘OK’ once the volume recovery is complete.
 DAMAGED – Multiple physical drive failures have occurred affecting
individual volumes (this will occur on a volume by volume basis). This
state can also occur if a volume is using the DynaRAID setting
‘Unprotected’ (no raid) and an individual physical drive is replaced. This
condition is very rare, and drives may be re-activated and data salvaged,
only in cases where a drive replacement has not occurred. Contact Facilis
Customer Support if a volume shows ‘Damaged.’
 RECOVERING - A physical drive in the group had failed and was
reactivated or replaced. A protected volume will show ‘Recovering’ while
the recovery process is active and the drive set is being repaired. Use the
SMDriveMonitor application (yellow icon), located on the TerraBlock
Server, for real-time updates on the recovery process.
Size – The size of the volume given at the time of creation by the administrator.
When using Auto-format, the volume size will match the partition size in the client
OS. If formatting volumes manually, the volume must be formatted the same size
set in the TerraBlock Manager, and not partitioned into smaller sections at the client
station. The size of a volume can be increased after creation.
Group – The group column is related to the group of physical drives used to create
the volume on the server. The graphic below lists some common drive group number
examples:
1 (group 1 only)
2 (group 2 only)
1,2 (group 1 and 2 (tandem))
The numbers apply to either each group of 12 drives in a 24D unit (24 drives total),
or one group of 12 drives in a 24EX (12 drives total) or 8 drives on the 8XS (8 drives
total).
27

Facilis TX16 EXPANSION CHASSIS – After connecting and adding a Facilis
TX16 Expansion Chassis to the TerraBlock Server, you will see additional groups
(3, 4, etc), depending on the number of TX16 Expansion Chassis you have
added. Refer to the Facilis TX16 Expansion Chassis Setup Guide for more
information on the Facilis TX16 Expansion Chassis
DynaRAID – The designations of “Mirror”, “RAID5”, “RAID50”, “RAID51”, or “----“
(unprotected) are listed for each volume, according to the state of protection on the
specific volume. This represents the current state of protection selected when first
creating the volume.
Mirrored, RAID5 and unprotected volume protection can be changed at any time
without losing data. RAID50 and RAID51 cannot be changed. In the case of an
individual physical drive failure, RAID5, RAID50, RAID51 and Mirrored
DynaRAID settings will maintain the data integrity of virtual volumes.

Mirror indicates that the data on the volume is being mirrored. Every
file written to a disk drive is written again to another drive and in the
case of an individual physical drive failure the necessary mirror data
takes over. A volume may be mirrored when created, and the
protection removed or changed to RAID5 at any time.

RAID5 indicates that the volume is being protected by RAID5 parity
data. Information about the primary data stored on the virtual volume
is calculated, compressed and saved back onto the physical drive set.
If an individual physical drive failure occurs, the necessary RAID5 data
is decompressed and used in place of the missing primary data. A
volume may be protected with RAID5 when created, and have the
protection removed or changed to Mirrored at any time.

---- indicates that the volume is not protected. A volume may be
unprotected when created utilizing a Single group of drives (Group 1).
RAID5 or Mirror protection can be added at any time. If an individual
physical drive failure occurs, all data on an unprotected virtual volume
will be lost.

RAID50 indicates that the virtual volume spans multiple Facilis
devices and is being protected with RAID50 parity. The data and
DynaRAID RAID5 parity data is striped across multiple Facilis devices.
The Facilis device can be an additional TerraBlock Server or a Facilis
TX16 Expansion Chassis.
If an individual physical drive failure occurs, the necessary RAID5 data
is decompressed and used in place of the missing primary data. If one
of the individual Facilis devices (TerraBlock Server or TX16 Expansion
Chassis) containing the RAID50 data becomes unavailable, the RAID50
volume will also become unavailable for use on all clients.
RAID50 volumes require a Windows 7 TerraBlock Server and must be
created on the TerraBlock Server itself. RAID50 DynaRAID protection
is set at volume creation time and cannot be changed.
28

RAID51 indicates that the virtual volume resides on a primary server
and the volume is mirrored to another Facilis device (TerraBlock
Server or TX16 Expansion Chassis). The primary server is the
TerraBlock Server where the RAID51 volume was created, formatted
and is mounted.
For RAID51 volumes, the RAID5 parity data is independent on each on
each Facilis device. Because the RAID5 data is independent on each
Facilis device, an individual physical drive failure on one device will not
affect any additional devices. In other words, you can have an
individual failed drive on server A and it will not affect server B.
If an individual physical drive failure occurs on one of the Facilis
devices, the necessary RAID5 data is decompressed and used in place
of the missing primary data.
If the individual Facilis device (TerraBlock Server or TX16 Expansion
Chassis) containing the RAID51 mirrored data becomes unavailable,
the RAID51 volume will still be accessible by the primary TerraBlock
Server; however, the volume will only be available as Read-only.
RAID51 volumes require a Windows 7 TerraBlock Server and must be
created on the TerraBlock Server itself. RAID51 DynaRAID protection
is set at volume creation time and cannot be changed.
 If working with a RAID51 volume and one of the individual Facilis
devices where the RAID51 volume was created becomes unavailable,
do not attempt to write additional data to the RAID51 volume.
 Any data written to a RAID51 volume while an individual Facilis device
(TerraBlock Server or TX16 Expansion Chassis) is unavailable is
written to disk cache only. Data may appear to write successfully to
the volume, but it is not saved to disk and this data WILL NOT be
accessible when the individual Facilis device becomes available again.
Server – Multiple servers can be employed to increase capacity and bandwidth in a
Facilis network. The names of the servers will be displayed in this column for ease of
volume location. If a volume is spanned across multiple Facilis devices, (RAID50,
RAID51, ATTO Power Center) “Tandem” will be displayed.
Creation Date – This column reports the date and time of volume creation. If
updating from a TerraBlock version prior to version 3.0, the creation date will be the
date of upgrade.
Mount Type – This column displays the volume sharing attribute. Volumes may be
created as either Single-user Write or Multi-user Write.
Note: Multi-user Write volumes require a Shared File System license.
Persistent Mount – This column displays the setting as chosen in the Mount
properties under “Use Persistent Mount”. The choices are ‘R’ and ‘W’. If the column
is empty, the user will be asked to specify how the volume will be mounted at the
time of volume mount. Otherwise it will mount without prompt based on the setting.
29
Mount Point (Windows Only) – This column displays the setting as chosen in the
Mount properties under “Use Drive Letter”. There are three possible displays:
C:/Volumes – If no mount point is chosen, the volume will only appear in a
directory on the C: drive (usually the system drive) called “Volumes”.
<drive letter> - If a specific drive letter (such as H:) is chosen, that drive
letter is displayed. The mounted volume will then have this letter in Windows
Explorer.
Z to A – If “Highest Available Letter” is chosen, the display will show that the
volume will be mounted with a letter starting at Z and descending until an
available letter is found.
Volumes Tab - Button Functions
Mount
When the Mount button is clicked, the TerraBlock Manager will attempt to mount any
volume highlighted according to that volume’s settings in the Mount Properties and
according to the Mount Type; Multi-user or Single-user Write (see Change Volume
for more information on changing Mount Type).
If mounting a Single-user Write volume, TerraBlock Manager will initiate a rescan
cycle that may last for up to 40 seconds. A progress dialog will appear while the
rescan is occurring. Please allow extra time for volumes to appear if performing
multiple operations during the same rescan cycle.
The mount process for Multi-user Write volumes should only take a few seconds.
Mount Dialog
Mac, Windows and Linux clients – After selecting the mount button for a volume with
Write Access permissions, a Mount Dialog box will appear. This will give the user the
option to mount the volume with Write or Read Only Access. Volumes with Read
Only permissions will not present a dialog. Volumes with the Persistent Mount
setting enable also will not present a dialog to the user. The volume will mount
based on the setting previously specified.
Windows clients only – After
selecting the mount button for a
volume with Write Access
permissions, an expanded dialog
may appear. This will appear if “Use
Drive Letter” has been deselected
under “Mount Properties” (for
additional details, see Mount
Properties later is this guide). A
Drive letter can be chosen for a
specific volume at this time.
Un-mount
The Un-mount button will remove the volume selected in the Manager from the
user’s client workstation.
30

Mac OS X: The formatted volume label in the client OS must be
exactly the same as the volume name in TerraBlock Manager.
 Client machines may mount up to 30 volumes per Terrablock server.
Update Read-Only
This button is used to refresh the data or contents for workstations that have a
Single-user Write volume mounted with Read Only Access. This action will refresh
the files and directories on the Read-Only volumes, and present the latest version of
the data.
Mac OS 10.6.8 through 10.10.x: The Update Read Only function will update HFS+
(Mac OS Extended) volumes without ejecting from the Mac desktop. Applications do
not need to be closed to update HFS+ volumes. Other file systems, such as NTFS will
be ejected from the desktop when Update Read-Only is selected.
 The user mode menu item “Auto update Read Only Volumes” is an
automated and timed instance of the Update Read-Only button
function, but only updates HFS+ volumes. NTFS volumes must be
updated manually.
Add Users
This button allows an administrator to add users to a volume. Once a user has been
added to a volume, the user will then be able to mount and work with that volume. Users
are added with Read-Only permissions by default. Write permission can be selected at
the bottom the of the Add Users dialog box. A User’s permission can be changed at
anytime afterwards. Multiple users can be selected and added to a volume at the same
time. This action may take longer to process if adding a high number of users.

When using Single-user Write volumes, multiple users may be given
write permission to a volume, but only one user can mount the
volume with write access at a time.
Mount Properties
This button will allow a user to adjust the mount settings or properties for a specific
volume. The “Persistent Mount” settings will be set within. For Windows clients,
“Use Drive Letter” settings will be set. Double click the volume in the volumes list
will also produce this dialog box.
Show & Hide Permissions
A new feature in version 6.0 is the Show/Hide Permissions button. By default the
User Permissions area on the right is hidden. Selecting the button with expand this
area. The User Permissions area is only viewable by a user with Admin access. User
with Normal access will no longer see this area displayed. See “User Access
Permissions” later is this section for additional information for this area.
31
Create Volume
This button is used to create new virtual
volumes. The creation of new virtual
volumes does not affect volumes or clients
already active on the system. The size of
a volume can range from 1GB to 8TB. It
is not recommended to exceed 8TB for a
single volume. On the TerraBlock 24D
Server (24 drives), the volumes can be
created on either of the 2 drive groups
(the emptiest is chosen by default), or
both groups if choosing ‘Tandem’. The
‘Tandem’ setting is recommended for the
best possible performance. See “Group”
above in TerraBlock Manager Columns
– Volume Tab.
Create Volume Window
Volume Name – Any name can be given
when creating the volume, up to 16
characters. Some characters cannot be
used when naming, the user will be
notified if the character is illegal.
Size (GB) – The size of the volume. Auto
Formatted volume sizes can range from
1GB to 8TB. A default size of 2 TB is set
for new volumes, this can be changed to the
desired size.
Create Volume Dialog
 Volumes over 8TB in size are supported but not recommended. If
volumes will be designated as Multi-user Write on a 64bit Windows 7
TerraBlock, there is no hard limitation on volume size, however Facilis
recommends against creating extremely large volumes as it may impact
the volume recovery time.
 Multi-User Write Volumes over 8TB should be performance tested on the
server before use. This can be done using AJA system test or Atto Disk
Benchmark.
 MUW Volumes that are created over 8TB in size must be created from the
server.
See page 81 – Creating Volumes: Creating Volumes larger than 8TB.
 If working with 32Bit Windows clients, in order to maintain compatibility
with 32Bit Windows, only create volumes up to 8TB (8000GB) in size.
 Volumes over 2TB (2000GB) in size
 HFS+ volumes up to 8TB (8000GB) in size are compatible with
Windows 7 based TerraBlock servers or clients with MediaFour
MacDrive 8 (or higher) installed.
32

NTFS volumes up to 8TB in size are compatible with Windows 32 bit
and 64 bit platforms.

HFS+ volumes over 2TB in size and created on a Mac OSX client are
NOT compatible with Windows 32 bit (XP) platforms.
 Any volume over 2TB in size created using Mac OSX TerraBlock Manager
and formatted as HFS+ will not be compatible with Windows 32bit
operating systems. For full compatibility when working with HFS+
volumes and Windows 32bit operating systems, create an unformatted
volume over 2TB (up to 8TB) on a Windows 32bit workstation (or
server) and then format the volume using a Mac OSX client.

Remember when specifying a size for a DynaRAID protected volume
on a TerraBlock 24D Server, Mirroring requires 100% of the primary
space be available on the alternate group, while RAID5 requires 9% be
available on the group where the volume is being created.
Tandem – This selection allows the administrator to specify multiple drive groups
during the creation of a volume to work together. The resulting volume may require
additional software to be used when creating ATTO Power Center External Tandem
volumes in a multi-server workgroup. This will apply with a fully populated 24D or an
attached TX16 expansion chassis. For additional information on the Tandem feature
see Appendix B: Working with External Tandem Volumes.
 Facilis recommends creating Tandem volumes for TerraBlock 24D
systems. This will ensure the server operates with optimal
performance. Tandem is optional for multi-server configurations.
DynaRAID – This section allows the administrator to choose a protection level for
the virtual volume: Mirror, RAID5, RAID50, RAID51 or Unprotected.
When selecting a Single drive group or utilizing the Tandem feature, different raid
options are available.

The Mirror option is for use creating Single group volumes with single
server configurations or for multi-server External Tandem volumes that
will be formatted using ATTO Power Center.

The RAID5 option is for use with single server configurations or for multiserver External Tandem volumes that will be formatted using ATTO Power
Center.

The Unprotected option is intended for use on a single server creating
single group volumes, or for multi-server External Tandem volumes that
will be formatted using ATTO Power Center.

The RAID50 and RAID51 options are intended for use with External
Tandem volumes in a multi-server environment or with Facilis TX16
Expansion Chassis. See TerraBlock Manager Columns – DynaRAID for
more information.
33
Add All Users with write access - This option automatically adds all known users
to the volume with write permissions.
Mount Type - This option allows the user to create either a Single-user or Multi-user
Write Volume. When selecting Single-user Write on Windows and Macintosh clients,
the Auto Format option is available (see Auto Format Volume, below).

Auto Format for Single-user Write volumes is not available on Linux
clients.
When selecting Multi-user Write, the Auto Format option is not available. Multi-user
Write volumes are created and automatically formatted as NTFS on the TerraBlock
Server. They are then automatically set to Multi-user volumes after the server
format is complete.
 Multi-user Write volumes are formatted as NTFS when created. If
these volumes are switched to Single-user write, they will be
mountable only as Read-only volumes on Mac clients. If your
workflow requires mounting Single-user Writable volumes on a Mac
client, create the volume as Single-user Write and choose Auto
Format from a Mac client in order to create the drives with HFS+
formatting.
 In order to mount Multi-user Write volumes that are formatted as
HFS+, additional 3rd party software, MacDrive 8 (or higher), must be
installed on the TerraBlock Server (see Change Volume, below).
Auto Format Volume NTFS (Windows) or HFS+ (Mac OSX) – When creating
Single-user Write volumes on Mac or Windows, the client requires a fibre channel
connection. When ‘Auto Format’ is chosen, the volume will be created and mounted
with Single-user Write access. After a drive rescan the TerraBlock Manager will
initiate formatting the volume as NTFS or HFS+ using the same name given in the
TerraBlock Manager ‘Create Volume’ dialog. See “Create Volume” (above) for more
information.

Note: When creating Single-user Write volumes on Linux clients,
Auto Format is not an available option in the TerraBlock Manager
‘Create Volume’ dialog. Single-user Write volumes created on Linux
clients must be manually partitioned and formatted using Linux disk
management tools.
Add Cascade Volume. . .
This button allows you to expand the selected volume by appending another
volume. The original volume can be single group or internal Tandem, and the
cascade volume can be added on the same group(s), separate group(s) or separate
server.
 In order to cascade across two or more servers, the servers must be
linked through fibre channel via switch zoning or direct connection
(direct connection recommended).
 A volume must be formatted NTFS in order to cascade.
34
Delete Volumes
This button will delete a selected volume(s). The contents or data is permanently
deleted as well. The size of the volume is then reallocated to the server and
available for use to create new volumes immediately. Only Administrative users can
delete volumes and the user will be issued a warning before the delete is executed.
Change Volume
After the virtual volume is created, protected and formatted, there is the option to
change the Name, Size (GB), DynaRAID (non-Tandem), and Mount Type of the
volume. Selecting this button will give the user access to make changes.
Change Volume Window
Volume Name – An existing volume
name can be highlighted and changed in
the same fashion as when it was
created. After changing the name of a
Single-user Write (SUW) volume, the
TerraBlock Manager name will no longer
match the formatted volume label or
name in the OS. Because of this, it is
necessary to change the volume
label or name at the OS level to
match the name given in TerraBlock
Manager “Volume name”. The
volume must be mounted with Write
Access in order to change it. The
TerraBlock volume name and OS label
must be exactly the same in order to
prevent issues with mounting and unmounting the volume.
Multi-user Write (MUW) volumes will
reflect the change after un-mounting
and remounting the volume on the
clients. The OS label change will
need to be done on the TerraBlock
server.
Change Size (SUW) – When changing the size of a volume, the volume must be
mounted with Write Access on the client where the change is applied. After changing
the volume size in the TerraBlock Manager ‘Change Volume’ window select the OK
button to submit changes. Depending on the OS, different rules will be applicable.
See below for specific resize behavior on each operating system.

Windows Change Volume Size – Single-user Write volumes on Windows
(Windows 7 64bit) can be increased or decreased (size reduction of volumes
is supported in version 6.0 and above). The resizing of a volume will be
completed automatically. It is not necessary to un-mount the volume, it
should remain mounted. After the changes have been submitted, check “My
Computer” to see the new volume size. This action may take up to one
minute. The resize option is only available with NTFS formatted volumes.
35

Note: When you increase the size of an NTFS volume it can take up to 1
minute after you have changed the capacity to appear in My Computer. If
you have waited more than that amount of time and the size still has not
increased, un-mount and re-mount the volume. If the un-mount/remount
process does not result in the size increasing see Tech Note TN-032
 Decreasing the size of a NTFS volume may take a long period of time
if contents or data must me moved and reallocated on the virtual
volume. Facilis recommends performing this action when the server
is not under heavy use, possibly end of day. The progress can be
monitored via Windows Disk Defragmenter.
 Mac OSX Change Volume Size – Single-user Write volumes can only be
increased on Mac OSX. In order to increase the volume size on a Mac, a 3rd
party utility from Coriolis Systems Inc. called iPartition is required
(http://www.coriolis-systems.com). Prior to making the change to the SUW
volume, the volume must be un-mounted. After the change is applied,
remount the volume in order for the Mac OS and iPartition to acknowledge
the additional space. The resize option is only available with Mac OS
Extended (HFS+) volumes. See the TerraBlock Manager Release Notes for the
latest supported iPartition version.
To complete the volume resize, do the following:
1.
2.
3.
4.
5.
6.
7.
Mount a SUW volume with write access
Enter iPartition and select the volume on the left hand side list of drives.
Enter the “Partitions” tab bellow.
Select the volume, right click on it and select the “Expand Partition Map”
Select “Show Pending Operations” from the “View” menu
Click on the current partition size to enable the resize handle
Move the resize handle to adjust the Volume into the new additional
space. Notice there may be some space left over, this is normal.
8. Check the “Show Pending Operations” box to be sure “Move” is not an
operation that needs to be performed. If Move is listed, reduce the resize
handle slightly until Move is not listed.
9. Select the “Commit” (or “Go”) button at the top of the window, then OK.

Linux Change Volume Size – Consult the documentation for your specific
Linux Distribution.
Change Size (MUW) – To change the size of a Multi-user Write volume, open the
TerraBlock Manager on a client system or the TerraBlock Server itself. From the
Change Volume window enter a new size for the Multi-user Write volume and click
OK. The size change can be increased or decreased (size reduction of volumes is
supported in version 6.x and above). The MUW volume size will change without unmounting at the server or clients. It is not necessary to assign a drive letter to the
MUW volume to resize.
 When resizing a Multi-user Write volume, the volume must be
formatted NTFS. HFS+ formatted volumes must be resized on a Mac
client with iPartion while mounted Single-user Write. Decreasing the
size of Mac HFS+ volumes is not supported.
36
 Decreasing the size of a Multi-user Write Volume must be performed
at the TerraBlock server.
 There are limitations increasing the size of NTFS volumes.
o A volume created 8000GB or less can only be expanded up to
8000GB.
o A volume created 16000GB or less can only be expanded up to
16000GB.
o These limitations can be bypassed by using Cascade Volume.
 Decreasing the size of a Multi-user Write volume may take a long
period of time if contents or data must me moved and reallocated on
the virtual volume. Facilis recommends performing this action when
the server is not under heavy use, possibly end of day. Progress can
be monitored via Windows Disk Defragmenter.
 An NTFS volume may not be decreased below half of the original
volume size. This is because of the location of the volumes bitmap.
Change DynaRAID - When changing DynaRAID protection level, the volume must
be un-mounted from all client workstations. Depending on the type of change, the
volume may only be available for Read-Only use for the duration of the action. The
DynaRAID protection process could take several hours for very large volumes.
 Internal Tandem volumes (utilizing groups 1&2 on the same 24D
server) must remain RAID5 protected.
Change Mount Type – This selection determines whether a volume will be
designated as a Single-user Write (exclusive write access) or Multi-user Write (full
read/write access by all users). In order to use the Multi-user Write feature for a
volume, the following must be configured properly:
1. The server must be licensed for Facilis Shared File System (SFS). To
determine if your system is licensed for Shared FS, look at the
SMDriveMonitor output (see System Setup – SMDriveMonitor). If the
SMDriveMonitor displays “Shared File System support enabled”, you have
the proper license for Shared FS.
2. A volume must be formatted using either NTFS or HFS+ in order to be
used as a Multi-user Write volume. NTFS is supported natively on the
TerraBlock Shared File System (SFS) without any additional software
required. For HFS+ Multi-user Write support, MacDrive 8 (or higher) must
be installed on the TerraBlock Server. While HFS+ is supported for
Multi-user Write volumes, it is preferred to have Multi-User Write
volumes formatted as NTFS in all environments, Mac, Linux or
Windows, for optimal performance.
3. Changing an NTFS or HFS+ formatted Single-User Write volume to a
Multi-user Write volume is supported on Windows, Mac or Linux Fibre
Channel and Ethernet clients.
 Volumes formatted as XFS, UFS, Fat32, etc. are not supported for
use as Multi-user Write Volumes. TerraBlock Volumes must be
formatted as either NTFS or HFS+ for use as Multi-user Write
Volumes.
37
 To change an HFS+ volume to Multi-user Write, it is required to have
MacDrive 8 or higher from MediaFour (third party utility, purchased
separately) installed on the TerraBlock Server. Installation of this
software is not required on TerraBlock clients.
When changing a volume from Single-user Write to Multi-user Write, the volume is
mounted on the TerraBlock Server itself. The TerraBlock Server then becomes the
“Single-user Write” owner of the volume. Every volume designated as Multi-user
Write will have a “W” in the TerraBlock Manager Sys (System) column, and “Multiuser Write” in the Mount Type column.

When working with Multi-user Write volumes, the recommended
volume creation method is to create the volume as a Multi-user
Write volume from fibre or Ethernet clients. Volumes created as
Multi-User Write are automatically formatted as NTFS on the
TerraBlock Server and automatically set as Multi-User Write.

In an all Ethernet environment, volumes can be only created as
Multi-user Write.
 Mount Type can only be changed after the volume is un-mounted
from all client workstations; the volume may remain mounted on the
server prior to changing.
User Access Permissions
Within the Volumes Tab, the User Access
Permissions pane is hidden by default for
Administrative Users. Selecting “Show Permissions”
will expand the display. TerraBlock Users with
Normal access will not see this area displayed. This
lists users and their permissions. It allows an
Admin to change user access permissions for the
selected volume(s).
Change Permission – This feature allows an
Administrator to change a selected volume’s
read/write permissions for one or multiple users.
Remove From Volume – User permissions can be
removed from a Volume. Once permissions have
been removed, the user(s) will no longer have the
ability to mount the selected volume. A user that
has Normal access with no longer see this volume
displayed in the Volumes Tab when logged in.
If a volume is mounted with write access in the Sys
(System) column of the Volumes Tab, there should be a corresponding entry of a
user displaying write access in the User Access Permissions pane (see example user
‘Editor’ in the image above). If The Sys displays a selected volume mounted read or
write but the is no user displayed in User Access Permissions as having this volume
mounted, the user may have been removed from the volume while that user had the
volume mounted (with read or write access).
38
Refresh
The Refresh button is used to manually update the display of the TerraBlock
Manager. If the user interface (UI) does not update automatically the information
displayed in the TerraBlock Manager may become outdated. Use the Refresh button
to force a TerraBlock Manager UI update. Using the Refresh button at regular
intervals will ensure that accurate data is displayed. If for some reason, the
information displayed in the TerraBlock Manager is inaccurate after manually
refreshing the UI, close and re-launch the TerraBlock Manager.
Users Tab
On TerraBlock client systems, the ‘Users’ tab on the TerraBlock Manager will only be
visible if the TerraBlock User has “Admin” access.
These are the columns in the TerraBlock Manager Users Tab:
Name – This is the name of the user as given by the administrator at the time of
creation. The name here matches the exact user name as reported by the operating
system on the client station.
Hostname – The name given to the computer on which the user is logged in.
Hostnames must be unique to avoid incorrect information being viewed on the
TerraBlock Manager Volume tab.
WWN – The World-Wide-Name is one of the ways Facilis protects the users from
mounting the same volumes with Write access in several places. Every Fibre Channel
card has a unique WWN. The WWN Index is also used to mount volumes remotely
from the TerraBlock Server version of TerraBlock Manager.
Port – The Port designation specifies the location of the system on the rear of the
TerraBlock Server. If using a switch, several users may share the same port.
Access – User access is determined by the administrator, and will have 2 states:

Admin – A user may be granted Administrator access to create and remove
volumes, and create and remove users. Only an Admin will see the User tab
in the TerraBlock Manager. An admin will see all volumes, but will not
automatically have permissions to mount all volumes.

Normal – A new user is defaulted to Normal. A Normal user will see only the
volumes to which they were given read or write permissions, and will have
the option to mount, un-mount, or Update Read-Only.
User Tab - Button Functions
Create User - This function is used to create a user
account for a TerraBlock client. The window appears
as seen here:
User Name – The OS login name of the TerraBlock
client. This must be exactly the same as the user
“long” name. This only applies if the User and
Password feature is disabled on the TerraBlock
Server. See “User and Password” feature later in this
guide.
39
Admin – The Administrator check box allows any user to be given the right to see a
display of every volume, create and remove volumes and users as well as add and
remove permissions to those volumes. It is not recommended that large numbers of
users have Administrator access level.

To quickly add the correct user name of a client system without
using the “Create User” button and dialog, simply launch the
TerraBlock Manager on the client. If communication is successful,
the user will be automatically created based on the name of the OS
local user account. See “User and Password” feature later in this
guide for additional user login information.
Delete Users – Users can be removed from the system by highlighting the user
and selecting the Delete Users button. All volumes should be un-mounted from all
workstations under that user account prior to deleting.
 It is not necessary to delete users to gain permissions to a
volume, change access of a volume, or delete a volume.
Change Access
Users can be assigned Admin or Normal access after being created. It is
recommended to have as few Admin accounts as possible to avoid unauthorized
volume creation, change and deletion.

After a user is created, an Administrator can change the access level
of that user at any time.
Copy User
Copy User will duplicate the volumes and permissions of the user highlighted in the
User pane, and will prompt for a new user name. If the name given already exists,
the existing user account will be appended with the new permissions. Regardless of
the original user’s privileges (Admin or Normal), copied users are given “Normal”
access.
Add Volumes
Volumes can be added to users, just as users can be added to volumes in the
Volumes Tab. The window appears as seen here:
When a volume is added, the selected user
will have either Read-Only (Default) or Write
permissions to the volume (if the Write
Permission box is checked). Several volumes
can be added simultaneously, but they will
all be given the same permissions.
Volume Access permissions can be changed
after volumes are added by using the
“Change Permission…” button under the
Volume Access Permissions pane in the User
tab.
40
Refresh
The Refresh button is used to update the display of the TerraBlock Manager. Upon
completing a task in the User Tab, if the display does not refresh automatically, click the
Refresh button. If the TerraBlock Manager display still had not updated, quit and re-launch
the TerraBlock Manager.
Volume Access Permissions
The Volume Access Permissions
pane in the Users Tab allows an
Administrator to remove volumes
from users and change users’
permissions to volumes. When a
user is selected, the following
information appears:
Name – Volumes with permissions
for the selected user.
Status – The current volume mount
status for the selected user.
Permission – Write ‘W’ or Read
Only ‘R’ permissions for the selected
volume.
Change Permission – Change a
user’s read/write permissions for
the selected volume(s).
Remove from User – After
removal, the selected user will no
longer have the ability to mount the
selected volume(s). If the user is
set to “Normal”, the volume will not
be displayed in the Volumes Tab.
System Tab
These are the columns displayed in the System tab:
Unit# – This lists the drive label number given when the TerraBlock drive set was
created. The number should correspond to the position of the physical drive in the
server if the physical drives were installed correctly. The drive Unit number will
increment after a drive replacement has completed (replaced drive will list as 25).
Status – The Status column will list the current state of the physical drives. The
status will list as GOOD under normal operation. Status will changed to FAILED if a
physical drive has failed, RECOVERING if a failed drive has been replace and
recovery is in progress, and REPLACED once the recovery has completed.
41
Model – This lists the model of the physical drives in the TerraBlock Server.
Serial# – This lists the serial number of the physical drives in the TerraBlock Server.
This can be useful to verify the correct drive is being replaced during a drive
replacement.
Size – This lists the size of the physical drives in the TerraBlock Server.
Errors – In the case where a drive encounters and error, it will change in this
column.
SATA# – This column corresponds to the internal SAS or SATA cards within the
TerraBlock server. There are three cards; each controlling eight drives in a
TerraBlock 24D chassis.
Port – This lists the connection of the physical drive to the SAS or SATA card (the
numbers in this column may not list in order i.e. 1,2,3).
Server – This column will list the name of the TerraBlock server. Normally the
server name is the model, but this can be changed if desired. Select Properties in
My Computer and changing the Computer Name.
42
TerraBlock Manager on the Server
Additional Function Buttons
When launching the TerraBlock Manager on the TerraBlock Server itself, there are
several additional features that the Server administrator may use. These additional
features are available only when running TerraBlock Manager from the Server and
will not appear on a TerraBlock client, regardless of the user’s permissions.
Volumes Tab
Mount and Un-mount by Index
In the example above, the Volumes tab shows the features of Mount and Un-mount
by Index. Select a volume to enable these buttons.
The Server
Administrator has the
ability to remove
Volumes from client
workstations (indexes)
that may be currently
shut down, or have
been removed from the
TerraBlock workgroup
43
without un-mounting their volumes.
The Server Administrator may also mount Single-user Write volumes to client
workstations that are inactive or active, to be mounted after a startup or reboot,
respectively. In this way, the administrator may remove all management duties from
a particular user, and only remotely mount (SUW only) or un-mount Volumes when
needed.
If a user has never launched the TerraBlock Manager on the local workstation, the
username will show up as “Unknown (xx)”, with no hostname. When remotely
mounting or un-mounting for this user, the Administrator must know the WWN
number of the Fibre Channel card. This can be found in the ATTO Configuration Tool,
by highlighting the channel and viewing “Node Name”. See the TerraBlock Release
Notes for more information and installation of the ATTO Config Tool.

When mounting a volume remotely while the client is active, the
volume will not appear immediately on the client workstation. The
user must reboot if using a Mac, or rescan in Windows Disk
Management for Windows clients.
Upon selection of Un-mount by Index, the following confirmation will appear:
Only continue if it has been confirmed that the workstation is shut down or
disconnected from the TerraBlock Server.
 Never un-mount a volume from an active workstation using
Unmount by Index. Even if that volume is not currently in use,
the unsafe removal will cause damage to the TerraBlock virtual
volume and potentially lead to data loss.
Add Attached Volumes
This feature is used when attaching an external Facilis T8 or TX16 to the
TerraBlock Server. If a T8 or TX16 Storage Array is not attached, this button
will have no functionality, but still appear.
Refer to the documentation provided with the Facilis T8 or TX16 Storage
Array for detailed instructions on attaching these devices to the TerraBlock
Server and working with the attached storage volumes.
44
Add Cascade Volume. . .
This button allows you to expand the selected volume by cascading it to another
Terrablock storage location. This feature allows you to cascade across drive groups
for single group volumes, as well as across servers and expansion chassis.
 In order to cascade across two or more server the servers must see
each other over fibre channel via switch zoning or direct connection.
 A volume must be formatted NTFS in order to cascade.
Users Tab
Synchronize Users
In a multi-server configuration, the Synchronize User button will appear when
selecting the Users Tab. The Administrator may synchronize users to make other
servers aware of changes to user accounts (permissions, etc.). Any new servers
added to the current TerraBlock network will have no knowledge of current
TerraBlock users until Synchronize Users is used.
System Tab
Locate
When running the TerraBlock Manager on the TerraBlock Server itself, the Locate
feature is available on the ‘System’ tab.
45
The Locate feature allows the Server Administrator to locate an individual physical
drive installed in the TerraBlock Server that the TerraBlock Manager is currently
running on. Pressing the Locate button causes the selected physical drive’s disk
activity light to blink, making it easier to locate the physical drive in the TerraBlock
Server Enclosure.
 Under the ‘System’ tab, select a drive from the list and press the
‘Locate’ button, which is displayed in the lower right corner of the
System tab window.
Pressing ‘Locate’ will cause the selected physical drive’s disk activity
light to flash for 15 seconds, allowing the user to easily locate the
physical drive within the TerraBlock Server Enclosure. It is
recommended to stop all client activity on the TerraBlock server.
 The Locate function only locates drives on the specific
server that the TerraBlock Manager is currently running on.
In a multi-server TerraBlock workgroup, the ‘Locate’ button
will remain grayed out and unavailable if drives from a
different server are selected. In order to easily identify the
drive you are attempting to locate, use the Locate feature
while the TerraBlock Server is idle.
Admin Settings Tab
Launching the TerraBlock Manager on the TerraBlock Server itself will display an
additional ‘Admin Settings’ tab containing a group enhanced features.
The Admin Settings tab will not appear on client workstations, regardless of the user
permissions.
46
Enable E-mail Notification of TerraBlock errors
The server is able to report any Disk error, SMDrive (TerraBlock Server’s service) or
MVSATA/SAS to an e-mail address specified in the Admin Settings tab of the
TerraBlock Manager. Enter the e-mail information and select ‘Test E-mail’ to verify
your e-mail information is valid.
Remember mounted volumes after a server reboot
This option in the Admin tab will store the mounted volume list for each client and
restore each mount after the server is rebooted.
Enable username and password login
This option enables the username and password functionality for all TerraBlock
Users. When enabled, TerraBlock users will be prompted to enter their TerraBlock
username and password when launching the TerraBlock Manager on a TerraBlock
Client.
In a multi-server environment, users will be prompted for their username and
password once the setting has been enabled on any one of the TerraBlock servers.
Disable automatic user creation
This option is used in conjunction with the ‘Enable username and password login’
feature. When enabled, this option prevents the automatic creation of TerraBlock
Users from a client workstation. The user must be an existing TerraBlock user to
login and launch the TerraBlock Manager from a client workstation.
When this option is enabled, new TerraBlock Users must be manually created by a
TerraBlock User with ‘Admin’ access or by using the TerraBlock Manager on the
server. As the user logs in at the client workstation for the first time, the user will be
prompted to create a password.
Refer to page 39 “TerraBlock Manager – User Tab” section, for more information
on TerraBlock User creation.
Reset disk error count
This feature allows the Administrator to reset active disk error reports. This will
cause the error column in the system tab to return to zero, and the warning message
on launch of the TerraBlock Manager to cease.
Number of TerraBlock Servers
This feature takes the number
entered and checks for a
matching number of servers each
time the Manager is launched on
the TerraBlock Server itself. If all
of the servers are not seen, a
rescan of disk management will
occur, and all servers should then
be available after re-launch.
If you see this message, the server count may be incorrect, or a server is
missing. To initiate a rescan, select 'Yes'. To continue on without rescanning,
select 'No' (selecting ‘No” will allow the TerraBlock Manager to launch on the
server if all servers are still not present).
47
Rebuild Priority
In the event of a physical drive failure and replacement, the Rebuild Priority feature
allows users to control the priority of the volume recovery (rebuild) process.

Normal: This is the default setting for volume recovery. The recovery
process will automatically reduce the speed of the process in order to
accommodate client bandwidth needs.


High: This setting causes the recovery process to maintain high priority
regardless of client bandwidth needs.

 Note: This setting can cause dropped frames during playback and other


bandwidth related issues for clients. Do not enable the ‘High’ setting
during periods of high client usage.
Paused: This setting stops the recovery process for 2 hours. Recovery
can be manually resumed by selecting ‘Normal’ or ‘High’. After the 2
hour pause, recovery will begin under the default ‘Normal’ mode.
Enable LDAP administration
This feature enables the TerraBlock Server to connect with an LDAP or Active
Directory server. Once this option is enabled, an additional tab will be displayed in
the TerraBlock Manager on the server itself, as well as any client with Admin
privileges. Users from the LDAP or Active Directory server can then be synced or
pulled to the TerraBlock server to become a TerraBlock user.
LDAP Tab
The LDAP tab will only be displayed once the feature is enabled from the Admin
Settings tab. Launching the TerraBlock Manager on the TerraBlock Server itself or
from a client that has logged in with a user with Admin privileges, will now display
this additional tab.
48
The LDAP tab is separated into three areas, Groups, Users and Settings. Each
column and function of each is as follows:
Show
Connection to specific groups that exist on the LDAP or Active Directory (AD) server
can be configured. Once a connection with an LDAP/AD server has been established,
these groups will be displayed under Groups. If multiple groups are listed from the
LDAP/AD server, selecting the box under the Show column will only display that
group of users to the right under the Users area.
Group
The Group column displays the existing group name that located on the LDAP/AD
server.
Permission
This column lists the permissions of an existing TerraBlock user to be applied to an
LDAP/AD user when “Sync” is performed.
Name
This lists the display name of the user provided by the LDAP/AD server. This most
commonly will match the Common Name.
Login Name
The lists the LDAP/AD Users login for the domain provided by the LDAP/AD server.
The Login Name is what is used to create the TerraBlock user when Sync is
performed. If the User Login Name contains spaces, an “_” will be added
automatically when Synced and will be displayed for the new TerraBlock User.re
Status
This will list the current status of users displayed. If the user exists on the LDAP/AD
server but not the TerraBlock, it will show as ‘Missing in TerraBlock’, visa versa with
show ‘Missing in LDAP’. If the user exists in both areas but volume permissions have
been changed, ‘Changes: +0 -1’ will be displayed. Synchronized displays after
successful sync between servers. Please see ‘Creating and Managing Users’ later in
this guide.
LDAP Tab - Button Functions
Show users in TerraBlock Server
Selecting this in the Settings area will display existing TerraBlock users in the Users
area.
Show users in LDAP
Selecting this in the Settings area will display existing LDAP users in the Users area.
Only show unsynced users
Users that have not been synced between the TerraBlock and LDAP servers will be
the only users display when this is selected.
Name
This lists the display name of the user provided by the LDAP/AD server. This most
commonly will match the Common Name.
49
Configure LDAP
To connect to an LDAP/AD server, configurations settings must first be defined.
Click the ‘Configure LDAP’ button to open the Setup LDAP Connection window. A
system Administrator must provide the parameters for the LDAP server.
LDAP URL: String
specifying the location of
an LDAP resource. An LDAP
URL consists of server host
and port, search scope,
base DN, filter, attributes
and extensions.
Base User DN: Base distinguished name. A search operation is performed on the
base DN, the DN of the entry and all entries below it in the directory tree.
DomainComponent (DC), organizationalUnitName (OU), etc. are defined here.
Base Group DN: Group distinguished name. A search operation is performed on the
Group DN, the DN of the entry and all entries below it in the directory tree.
DomainComponent (DC), organizationalUnitName (OU), etc. are defined here.
User DN: User distinguished name. This is required for the directory connections
setup. This is the account that is used to log on to your Active Directory
environment.
Password: This is the password for the user specified in User DN.
 Use the ‘Test Connection’ button to test the connection to the LDAP server.
If
a valid connection is established, a ‘Connected Successfully’ dialog will be
displayed.
Refresh
The Refresh button is used to manually update the display of the TerraBlock
Manager. If the user interface (UI) does not update automatically the information
displayed in the TerraBlock Manager may become outdated. Use the Refresh button
to force a TerraBlock Manager UI update. Using the Refresh button at regular
intervals will ensure that accurate data is displayed. If for some reason, the
information displayed in the TerraBlock Manager is inaccurate after manually
refreshing the UI, close and re-launch the TerraBlock Manager.
Sync selected
This will synchronize only the selected user from the LDAP/AD server to the
TerraBlock.
50
Sync all
This will synchronize all users from the LDAP/AD server to the TerraBlock.
 If Sync all is selected while both TerraBlock and LDAP users are
shown, existing TerraBlock users that do not exist on the LDAP server
will be deleted. TerraBlock users will then match only what the LDAP
server has provided. It is recommend to user this at initial setup
when there are no existing TerraBlock users.
TerraBlock Client Setup
Mac and Windows Clients
Once the necessary hardware and drivers are installed for connectivity to the
TerraBlock Server, the TerraBlock Manager will need to be installed. The TerraBlock
Manager can be found on the supplied USB key or downloaded at www.facilis.com.
When installing on the Mac, the Manager should be unzipped at each client
workstation. For Windows workstations, copy the Manger folder to a desired
location.
 All client installations require the Mac or Windows local user account to have
Administrative access.
 Please see the TerraBlock release notes for more in depth installation
instructions.
 Note: All client workstation hostnames should be set to unique
names. Client workstation hostnames should not contain any spaces
or special characters.
Windows workstation hostnames can be determined by typing the
‘hostname’ command in a Windows command window. Mac and Linux
workstation hostnames can be determined by typing the ‘hostname’
command in a Terminal shell. Consult your workstation’s operating
system documentation for instructions on permanently changing the
hostname.
Linux Clients
Linux clients consist of a more in depth installation process. In addition to existing
Single-user Write functionality, the TerraBlock 5.5 Release and greater, adds support
for Multi-user Write volumes over both Fibre Channel and Ethernet for Linux Clients.

Linux clients require the use of shell commands in the Linux terminal. Basic
familiarity with the Linux terminal and shell commands is recommended.
Fibre / Ethernet card installation
Refer to your fibre or Ethernet card manufacturer’s instructions for proper installation
of the fibre / Ethernet card hardware and its accompanying software drivers in your
Linux client.
51
Hardware installation notes

Installation of software drivers requires root access.

Installation of software drivers may require a permissions change to the
software driver package in order to run the installer application or access
installation files. After extracting the installation files, use the command
‘chmod –R 777 <installer folder>’ to set the permissions of the driver
installation folders and files.

Installation of the ATTO Configuration Tool requires the Sun/Oracle version of
JAVA. The Sun/Oracle version of JAVA is not installed on all Linux
distributions.
ATTO provides instructions for configuring the proper version of JAVA in order
to install the ATTO Configuration Tool here:
http://www.attotech.com/support/trouble/linux.html#configtool

After the Fibre Channel card has been installed and configured properly,
attach the fibre cable to the ATTO fibre card.

In a single TerraBlock Server environment, there must be only one fibre cable
connected to the Linux Client.

Once the Linux client’s Fibre Channel connection is active, the TerraBlock
Server’s TOOLS volume will appear as a device on the Linux client.

The TOOLS volume can be viewed using Logical Volume Management
(LVM) or Disk Utility (depending on your distribution) or by using the
shell command: fdisk –l. This command will list the volumes that are
available on the Linux client.
 If running as a normal Linux user, the fdisk command requires
root access.
 Depending on your path setting the fdisk command may require
an absolute path in order to run. Fdisk is usually located in the
/sbin/ directory.

The TOOLS volume will appear as 1.03GB device under /dev/.

The TOOLS volume will have a single partition formatted as FAT32.

The TOOLS volume will not have a mount point.
Launching the Linux TerraBlock Manager
Fibre Attached
 In order to function properly, the Facilis TerraBlock Manager on fibre
attached machines requires that the software be launched by the
ROOT user. Contact your site administrator to obtain the ROOT user
password for your Linux client.

In a shell window, navigate to the ‘Linux TerraBlock Manager’ directory
52

Switch to the ROOT user using the ‘su’ command and supply the ROOT user
password when prompted.

As the ROOT user, run the following command: “./TerraBlock\ Manager”.

Once the TerraBlock Manager has started, the user ‘root’ will be created as a
Facilis user. At this point the user ‘root’ may be granted access to Facilis
volumes from a TerraBlock admin user. See “TerraBlock Manager
Functions: Adding Users” for more information.
Ethernet Attached
Simply navigate to the Linux Terrablock Manager directory and double click
the TerraBlock Manager application.
Working with Facilis Volumes
Multi-User Write Volumes
As of the TerraBlock 5.5 release, Linux clients may now access Multi-user Write
volumes via fibre or Ethernet connections. Multi-user Write volumes may be created
from a Linux client and mounted with read or write permissions. See “Chapter 5:
Getting Started with Shared File System” for more information.
Single-User Write Volumes
In order to use Single-user Write (SUW) Volumes with Linux clients, the volumes
must be created from the TerraBlock Manager as raw, unformatted volumes, then
manually partitioned and formatted using Linux disk management tools. Once the
SUW volume has been formatted it can then be mounted to a mount-point in the
Linux filesystem.
Different utilities are available for partitioning and formatting volumes on various
distributions of Linux. We will cover only the shell operations that are common to
most distributions. If GUI is preferred, please consult the documentation for your
specific distribution.
To create a Single-user Write volume for use with Linux Clients, in the TerraBlock
Manager ‘Volumes’ tab, select the ‘Create Volume’ button. In the ‘Create Volume’
dialog, enter the desired volume name, size, drive group, DynaRAID and user
permissions options. Select the Single-user Write option and press the ‘Ok’ button.

When creating Single-user Write volumes from Linux clients, the Auto
Format function is not available.

The XFS file system supports a maximum of 12 characters for volume
labels. If creating a Single-user Write volume that will be formatted using
XFS, do not create a volume with a name containing more than 12
characters.

When creating Multi-user Write volumes, the volumes are created and
formatted as NTFS on the TerraBlock Server. The volumes are then
automatically set to Multi-user Write.
53
Once the Single-user Write volume has successfully been created and is listed in the
TerraBlock Manager ‘Volumes’ tab, select the volume in TerraBlock Manager and
mount with write access.
After the Single-user Write volume has been mounted by the TerraBlock Manager,
the volume is now available to the Linux client as an un-partitioned and unformatted
device. In order to work with the volume, it must be partitioned and formatted. Next,
a mount-point in the filesystem must be created and finally, the volume must be
mounted to the mount-point.
The remainder of the Single-user Write volume creation and mounting process can
be done using either the GUI method or the UNIX Shell method described below:
1. Redhat GUI Method:
Enter System Settings - Logical Volume Management (or Disk Utility
depending on your distribution) and look for an unallocated volume of the
proper size and filesystem (no filesystem). In the sample picture below, the
unformatted volume is /dev/sdh. It is 50GB in size and has no filesystem.
You will use the device label (example: /dev/sdh) to create a partition on the
volume. Note the device label of the volume, enter a shell window and go to
step 3.
2. Shell Method 1:
Open terminal shell and type /sbin/fdisk –l
This will list the mounted disk devices.
Look for an un-partitioned disk of the expected size.
Example:
Disk /dev/sdd: 4294.9 GB, 4294967296000 bytes
255 heads, 63 sectors/track, 522166 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
54
Disk /dev/sdd doesn't contain a valid partition table
In the example above the disk is /dev/sdd and it is 4294.9 GB (4TB).
Shell Method 2:
Open terminal shell and type “dmesg”. This command will print the recent
device activity, including the discovery of new devices. Look for the volume
name that was mounted with TerraBlock Manager. It should look something
like this:
Vendor: Facilis
Model: (volume name)
Rev: 1.0
Type: Direct-Access
Ansi SCSI revision: 05
SCSI Device sd~: (block count)
SCSI Device sd~: drive cache: write through SCSI Device sdc: (block count) SCSI Device
sd~: drive cache: write through
sd~: sd~1
Note: ~ denotes the letter, b through z (a is the system drive), in the order the devices were
recognized by the Linux OS
Record the label of the device you mounted with the TerraBlock Manager (example:
sdh) and go to step 3.
3. Once you have determined the device label of the Volume, it can then be
partitioned. To create a partition on the volume follow the steps below:
Note: the volume must be mounted writable.
PARTED Method (recommended):
Note: This is the required method when creating Single-user Write
volumes greater than 2TB in size.
a. As ROOT, run the following command: /sbin/parted /dev/sd~
(Replace the ‘~’ with the device label you obtained in the
previous steps).
b. In PARTED enter the following commands (parted) unit TB – set
the unit value to terabytes.
c. (parted) mklabel gpt – applies a GUID partition label
d. (parted) mkpart primary 0 -0 – create a primary partition using
all available space.
e. (parted) print – Prints the partition information. Verify the
partition information is as expected for the disk device.
f. (parted) q – quit parted
FDISK Method:
Note: This method works with volumes 2TB or less in size. For
volumes greater than 2TB, use the PARTED method.
a. As ROOT, run fdisk /dev/sd~. Replace the ‘~’ with the device label you
obtained in the previous steps.
55
 Note: depending on your path setting you might need to use an
absolute path to run fdisk. The fdisk utility is generally located
in /sbin/.
b. Enter: “n” for new <enter> - This creates a new partition on the disk.
c. Enter: “p” for primary partition <enter> - This sets the new partition
as the primary partition.
d. Enter: “1” for partition 1 <enter> - This sets the partition number to
partition 1.
e. When asked which cylinders to use, take the default selections.
f. Enter: “w” <enter> to save your changes.
g. You may be prompted that a reboot is necessary. If so, reboot the
Linux Client.
4. To apply an XFS filesystem, as ROOT, run the command mkfs.xfs –L <volume
name> /dev/sd~1.
a. Replace the ‘~’ with the device label you obtained earlier. If the
system had been rebooted, re-verify the device label is correct.
 Note: depending on your path setting you might need to use and
absolute path to run mkfs.xfs. The mkfs.xfs command is generally
located in /sbin/.
 The –L switch in the mkfs.xfs command sets the volume label in the
Linux OS. Be sure the volume name inserted into the xfs formatting
command is EXACTLY the same as the name listed in TerraBlock
Manager. Be aware that volume names are case sensitive.
5. Once the volume has been formatted, it can then be mounted in the Linux
filesystem. To mount the volume to a mount point, first create a mount point
directory, then mount the formatted device:
a. mkdir /media/<volume name>
 Volume mount points are generally located in the ‘media’
directory or the ‘mnt’ directory. Consult your Linux distribution
documentation for the proper mount point directory.
b. Once the mount point has been created, mount the volume with the
following command: mount /dev/sd~1 /media/<volume name>
i. Replace the ‘~’ with the device label you obtained earlier
6. Type either of the following commands to verify the volume is mounted
properly:
a. ‘mount’ – lists mounted volumes
b. ‘df -h’ – lists mounted volumes and will show available space.
Maintaining Single-user Write Mount Points
On Linux clients, Single-user Write volume mount points are not maintained after a
client reboot. In order to maintain your volume mount points after a client reboot, an
entry for the volume must be made in the /etc/fstab file.
56
Entries can be made in the /etc/fstab for mounting volumes automatically at startup.
The easiest way to do this is through the volume label. If you formatted the volume
using mkfs.xfs –L, the volume label should be the name of the TerraBlock volume.
In order to view the fstab file use the following command: cat /etc/fstab. The fstab
file can also be viewed using a graphical text tool, such as Gedit.
The fstab file will look something like this:
# This file is edited by fstab-sync - see 'man fstab-sync' for details
/dev/sda1
LABEL=Video
LABEL=Graphics
/dev/hdc
/dev/fd0
/dev/hdd
/
/mnt/Video
/mnt/Graphics
/media/cdrecorder1
/media/floppy
/media/cdrecorder
ext3
auto
auto
auto
auto
auto
defaults
11
defaults
00
defaults
00
pamconsole,exec,noauto,managed
00
00
00
The above example shows two volumes mounted by label – “Video” and “Graphics”.
Be aware that there are two tab stops between the label description and the mount
point, and also between the mount point and the File System (‘auto’ in the example
above). The remainder of the file is single tabs.
As ROOT, using a text editor such as VI (shell) or Gedit (graphical UI), add an entry
in the /etc/fstab file for the volume you wish to automatically mount at start up. Use
the above Video and Graphics entries as an example.
Configuring Autodesk Stone & Wire for Standard FS
Once the volume has a mount point, a Specific directory will be created on the
volume (Managed Media Cache Directory) and that directory will be declared to the
Stone&Wire software as a Standard FS Partition in the stone+wire.cfg file.
It is recommended that the root level not be used as the designated standard FS
target, rather a descriptive hierarchy, such as /mnt/Video1/Smoke/p7. The “p7”
directory may designate the volume as [Partition7] in the stone+wire.cfg file.
Multiple standard FS volumes may be added to the stone+wire.cfg file by duplicating
the configuration listing (from [Partition7] on) and appending to the bottom of the
file with proper changes.
For more information, see the Autodesk Stone and Wire 2008 - Filesystem and
Networking Guide, page 47 “Setting up a Standard Filesystem”.
A sample of a stone+wire.cfg file is shown below with paths as described above.
#
# S+W configuration file
#
# Each S+W partition can be independently configured.
#
[Partition7]
# Name of the partition.
#
# Default: Name=stonefs#
#
Name=Video
57
# If specified, the path denotes that media should be stored in the file path
# specified, as opposed to the Stone. Typical standard fs path will be
# /mnt/<device>/fs<id>/part<id>/ where <device> is the device name, fs<id> is
# the framestore identifier and part<id> is the partition identifier.
#
# Default: Path=
#
Path=/mnt/Video/Smoke/p7
BREAK – KEEP ALL DEFAULTS FROM THIS POINT UNTIL THE END OF THE FILE
FOR ADDITIONAL PARTITIONS COPY ALL TEXT AND ADD BELOW FINAL LINE, THEN MODIFY VALUES
[Partition6]
# Name of the partition.
#
# Default: Name=stonefs#
#
Name=Video2
# If specified, the path denotes that media should be stored in the file path
# specified, as opposed to the Stone. Typical standard fs path will be
# /mnt/<device>/fs<id>/part<id>/ where <device> is the device name, fs<id> is
# the framestore identifier and part<id> is the partition identifier.
#
# Default: Path=
#
Path=/mnt/Video2/Smoke/p6
BREAK – KEEP ALL DEFAULTS FROM THIS POINT UNTIL THE END OF THE FILE
Un-mounting Single-user Write Volumes
Un-mounting a Single-user Write volume is a two step process.
1. In the TerraBlock Manager, select the Single-user Write volume and press the
‘Unmount’ button. This will remove the device from the Linux client.
2. In the Terminal, as ROOT, un-mount the volume from the Linux filesystem by
running the ‘umount’ command.
Example: umount /mountpoint/volume-name
3. Verify the volume has been unmounted from the mount point by opening the
mount point directory or by using the ‘ls’ shell command to list the contents
of the mount point directory. The directory should be empty.
You can also verify the volume is no longer mounted by running the ‘mount’
command, which will list the currently mounted devices.
 If you intend to re-mount the Single-user Write volume at a later
date, the mount point can remain in the filesystem. It will reside as
an empty directory.
 Unlike Multi-user Write volume mount points, Single-user Write
volume mount points are not automatically removed when the Singleuser Write volume is un-mounted. The SUW volume mount point will
remain in the file system. If desired, the SUW mount point directory
can be deleted once the SUW volume has been un-mounted. However,
if you intend to re-mount the Single-user Write volume at a later
58
date, it is suggested the mount point be left in the file system,
otherwise it will need to be re-created.
59
Ethernet Shared File System Setup
Your TerraBlock Server may have initially shipped standard with Fibre Channel only
connectivity. Ethernet connectivity can be enabled at any time provided the server
has a Shared File System (SFS) license. New TerraBlock Servers have the Ethernet
option enabled by default.
This is achieved with either a single Ethernet connection from the TerraBlock NIC
card to an Ethernet switch, four teamed Ethernet links from the TerraBlock to an
Ethernet switch, or, with servers shipped after 8/1/2010, a 10Gbit uplink to a 10Gbit
enabled switch.
The following section describes how to install and configure a single and four way
teamed Ethernet configuration. Since the Shared File System (SFS) is a pre-requisite
to using the Ethernet option it is assumed in this section that all requirements for
Shared File System have been met.
Single Ethernet Connection
A lower bandwidth configuration can be achieved by utilizing the onboard Ethernet
adapter of any model TerraBlock Server.
The server Ethernet port should be cabled to the switch (switch models may vary).
The Ethernet port from the server will then have to be configured. It can be
configured with a static IP address or set to DHCP if your network supports this
function.
Keep in mind, for best performance an isolated network is optimal. It is also
recommended that you disable the Windows Firewall Service for best performance.
 The Windows Firewall Service can be disabled via the
Computer Management console under Services and
Applications > Services.
To configure the TerraBlock Server’s Ethernet port, right-click on ‘My Network Places’
and choose: ‘Properties’. Right-click the active network interface card (NIC) that has
been cabled to the Ethernet switch and choose ‘Properties’. Select ‘Internet Protocol’
in the list and then press the ‘Properties’ button. Here an IP address can be specified
or DHCP can be selected if your network supports this functionality.
Once the Ethernet configuration is complete, the IP address can be confirmed by
going to the Start Menu and
choosing ‘Run’. In the ‘Run’
window, type “cmd” and hit
enter. At the cursor prompt
(>) in the command prompt
window, type “ipconfig” or
type “ipconfig /all”, for
extended information. Your
server’s IP address will be
listed along with additional
information about your
network configuration such
as Subnet Mask and Default
60
Gateway. The TerraBlock Server’s hostname can be found by typing the command
‘hostname’ in the command window, or by right clicking ‘My Computer’ and choosing
‘Properties’.
 Either the TerraBlock Server’s IP address or hostname (Example:
TerraBlock24D) will be needed to complete the network setup from
the client stations that will be connecting to the TerraBlock Server via
Ethernet.
 Make note of both the TerraBlock Server’s IP address and the
TerraBlock Server’s hostname.
Enabling the Ethernet Option on the Server
Once the TerraBlock Server is cabled to the Ethernet switch and the IP address is
set, the Ethernet option can be enabled (the Ethernet option should be enable for all
new TerraBlock servers). To do this, open the TerraBlock Manager on the TerraBlock
Server. At the top of the TerraBlock Manager select the “File” menu and choose
“Network Configuration”.
The Ethernet option should be enable for all new
TerraBlock servers.
Select the “Enable Network Configuration” check box within the Configure TerraBlock
Network dialog box. This will enable the Ethernet option on the TerraBlock Server.
A reboot is required after this feature is enabled. After reboot the SMDriveMonitor
will verify that the service is listening on port 859.
The default network port
number is (859). If a
different port number for
your network is desired,
make this change prior to
rebooting.
 Warning: In the TerraBlock Manager running on the TerraBlock
Server, leave all IP address fields blank in the Network
Configuration setting. Entering an IP address in these fields
when running the TerraBlock Manager on the Server itself will
cause incorrect behaviors when mounting volumes and result
in an extended delay when launching the TerraBlock Manager.
 For optimal performance the Windows Firewall Service should
be disabled in Computer Management
61
Enabling the Ethernet Option on the Clients
Any Windows, Mac or Linux Client system that will be connecting to the Ethernet
enabled TerraBlock Server should be cabled to an open port of the switch. This will
provide optimal performance. The client(s) must be on the same network or subnet
as the TerraBlock Server. The client(s) can be configured with either DHCP or a static
IP address. When using static IP addresses, if the Server IP address has been set up
to be 192.168.1.128 for example, the client will need an IP address of 192.168.1.x
(x being any available number on the subnet).
To verify the client(s) can communicate with the TerraBlock Server over the network,
Ping the TerraBlock Server by IP address and/or Host Name.
To Ping the TerraBlock Server from a Windows client system go to the Start Menu of
the client and choose Run. Type “cmd” and hit enter. At the > prompt type “ping
<server IP address>”. From a Mac client, go to Applications/Utilities/Terminal. At
the $ prompt type “ping <server IP address>”. From a Linux client open a terminal
window. At the $ prompt type “ping <server IP address>”.
If your network is configured properly, you should receive a response from the
server (Hit ‘control-c’ to stop pinging from a Mac or Linux Client). You can also ping
by the server’s Host Name (example: TerraBlock24D). If the name can be resolved
over your network, you should receive a response.
After network communication with the server has been confirmed, the Network
Configuration feature can be enabled on the client(s).
 If you ping the TerraBlock Server and do not receive a
response using the ping command, confirm the server’s
Firewall is disabled and try again.
 If the server’s Firewall is disabled and you do not receive a
response using the ping command, verify your client IP
address is using the same network as your server. To
determine your client’s IP address: on Windows, open a
command prompt and type the command ‘ipconfig’. For Mac
and Linux clients, open a terminal window and type the
command ‘ifconfig’.
Launch the TerraBlock Manager from the client system. Select the “File” menu and
choose “Network Configuration”.
Select the “Enable Network Configuration” within the Configure TerraBlock Network
dialog box. This will enable the Ethernet option on the client system.
In the Port Number field, enter the same Port Number that is configured on the
TerraBlock Server’s Network Configuration setting. The Port Number has to match
that of the TerraBlock Server. The default port number is (859). If the port number
on the server has been changed, set the port number on the client to match the
same port number that was set on the TerraBlock Server.
62
In the Server Name or IP Address field, enter the
server IP address or hostname that was
previously obtained when configuring the server’s
network configuration.
Click OK to exit the Configure TerraBlock Network
window. Quit and re-launch the TerraBlock
Manager.
You should now be connected to the TerraBlock
Server. If a Tools Volume is listed but no other
volumes are displayed in the TerraBlock Manager
Volumes Tab, it may be necessary to change User
Access for the volumes. This can be done from
the TerraBlock Manager running on TerraBlock
Server or any client with Admin access.
Teamed Ethernet Connection
Included in the Ethernet Connectivity Kit is a dual channel Ethernet Network
Interface Card (NIC). You must install the Ethernet NIC into an available slot in the
TerraBlock Server. The driver for that card is also included with the kit on a USB
thumb drive. At this time Facilis only supports the use of X7 (or newer) based
TerraBlock 24EX and 24D units for the 4X teamed Ethernet option.
 Under certain rare circumstances the process of creating a NIC team
for the Ethernet based Shared File System may prevent the
TerraBlock Server software (smdrive.exe) from starting successfully.
Contact Facilis Support if this should occur.
Configuring the TerraBlock Server for 4 x 1 Gbit Ethernet option
Installing the add-in Ethernet card
1. Shutdown and UNPLUG the TerraBlock Server. The server MUST BE
UNPLUGGED in order to prevent potential damage to the server
motherboard.
2. Remove the top cover to gain access to the PCI slots.
3. Install the Ethernet card into PCIe slot number four. Slot four is the first
PCIe slot if you are facing the back of the unit and looking from right to
left. It is also the slot closest to the last SATA controller.
4. Close the TerraBlock Server and power it on.
Installing the add-in Ethernet driver
1. Once the system has booted you may receive the New Hardware
Installation Wizard for each new NIC port found. Please hit “Cancel” to
the Wizard if presented. New TerraBlock Servers have the Ethernet
drivers pre-installed so the New Hardware Wizard may not appear. If
63
presented with the new hardware dialog, proceed with the following steps
after hitting Cancel.
2. The Intel driver package should be found in the following path on the
TerraBlock Server:
C:\Program Files\Facilis\TerraBlock\Drivers\Windows\Intel
(Drivers can also be found on the provided USB key or downloaded at
www.facilis.com).
3. Double click the PROWinx64.exe. Click Next when presented with the
Intel Welcome screen:
4. Click the “I accept the terms of the license agreement” radio button then
click Next to proceed:
5. Click Install when presented with the “Ready to Install the Program
screen:
6.
Click Finish when presented with the Intel Wizard Completed screen.
Teaming the NIC Connections
1. Right click on My Computer and choose Manage.
2. In the Computer Management window click on Device Manager.
3. Click the “+” symbol next to the Network Adapter category.
64
4. Double click on the first Network Adapter listed (see above). You will be
presented with the Network Connection Properties Window. Click on the
Teaming tab in that window.
5. In the Teaming tab select the “Team this adapter with other adapters”
option and click the New Team button (see above). The New Team
Wizard will appear. Give the team a name and click the Next button.
6. In the next New Team Wizard window select all four Network adapters in
the list then click 'Next'.
65
7. In the next New Team Wizard window select Adaptive Load Balancing and
click 'Next'. If you are using a switch other than that supplied by Facilis
and it supports the IEEE 802.3ad Dynamic Link Aggregation option you
may want to consider using that option. However, you will have to
configure your switch appropriately for this option.
8. At the last New Team Wizard window click Finish. This may take a few
minutes.
9. Once the team is created it will default to using DHCP. If you are not
using DHCP you will have to assign a static IP address to the Team
adapter. You can access the Team adapter by right clicking My Network
Places on the Desktop. The team adapter is usually the highest number
adapter and will have the name Team: <the team name you gave in step
5> in the Device name column. You should see something like the
following:
66
10. Right click that adapter to change your TCP/IP settings as you would in a
single connection configuration (see pg. 59 “Single Ethernet Connection”).
10 GB Ethernet Connection
The 10Gbit option requires a TerraBlock Server that is running the Windows 7 x64
operating system. The card installation requires an available PCIe slot in the
TerraBlock Server. If all the PCIe slots are occupied with Fibre Channel cards you
will have to remove one card and consider adding a Fibre Channel switch to
accommodate those clients connected to the card(s) you remove.
Installing the add-in 10Gbit Ethernet Card Driver
1. Once the card is installed and the system is rebooted you must install the
driver. The driver is provided with the 6.5 release.
2. Double click the Myricom driver installer (myrige-1.1.10_64) and choose
“Run”.
3. Click “Next” at the Myricom introduction splash screen.
4. At the “Welcome to the Myri-10GE_x64 Setup Wizard”, click “Next”.
5. At the “Allow TCP Adjustments” screen, select “Please keep Default
(Windows 2008 and later). Click “Next”.
6. At the “Network Values” screen, leave all values at default. Click “Next”.
67
7. At the “Select Installation Folder” screen, leave the default directory and
click “Next”.
8. Click “Finish” at the next screen to complete the driver installation.
9. Once the 10Gbit adapter driver is installed the new NIC will default to
using DHCP. If you are not using DHCP you will have to assign a static IP
address to the Team adapter. You can access the adapter by right clicking
My Network Places on the Desktop.
10. Right click that adapter to change your TCP/IP settings as you would in a
single connection configuration (see pg. 59 “Single Ethernet Connection”).

When installing a dual channel Myricom 10GBit Ethernet card
in the TerraBlock server it is recommended to have an
independent subnet or network for each channel. For
example, when configuring an IP address, channel 1 can be
set to 10.0.0.1 and channel 2 to 20.0.0.1. This will create two
separate networks to avoid any conflicts with the Windows
operating system.
68
Creating and Managing Users
From the Users tab, TerraBlock Administrators can create users, manage the users’
access to volumes and determine which users can be given access to administrative
functions. The administrator may also determine which volumes a user currently has
mounted, and with what type of access, read or write.
TerraBlock Manager Users Tab– Server Administration Mode
In the example above, you see user Name (Editor); user’s computer Hostname
(FacilisMacBook); World-Wide Name of the fibre card in the host; Port designation on
the TerraBlock Server, and user Access privilege.
 In the Users Tab, users may show up with the name “Unknown
(xx)” - you may disregard these users.
The most efficient method of creating users on the TerraBlock manager if not
using User and Password Authentication is to allow client stations to send
their user information to the server. Login with the local user account (Mac or
Window OS user) and launch the TerraBlock Manger.
When the connection is successful, the local user account name will be sent to
the server automatically. The User tab will reflect the new Facilis User
account, and a TerraBlock Administrator may assign volumes and access level
to that user.
With User and Password Authentication enabled the TerraBlock user can be
created from a client system or from the TerraBlock server.
69
Mac User Login
The TerraBlock Manager must first be installed while logged in with a local
Mac Admin user. The Admin user should install the TerraBlock Manager in the
Mac Applications folder. After installation (see release notes for installation
instructions) a Standard Mac user account can be used. Run the TerraBlock
Manger from the Applications folder.
Windows User Login
The TerraBlock Manager must first be installed while logged in with a local
Windows Administrator user. After installation (see release note for
installation instructions) a Windows Normal user account can be used.
TerraBlock Username and Password Feature
The TerraBlock Username and Password feature allows TerraBlock users to login to
any TerraBlock Server from a client workstation as any specific TerraBlock User. The
user is independent, rather than utilizing the existing local machine’s user account.
The specific user’s access level (admin, normal), volume access list and volume
mount permissions (read, write) will follow the user on the client machine where the
user is logging in.
The Username and Password feature is enabled on the TerraBlock server. The setting
is located under the ‘Admin Settings’ tab of the TerraBlock Manager.
Refer to the “TerraBlock Manager on the Server” section, for more information
on the ‘Enable username and password login’ setting.
Logging in to the TerraBlock System
Once the Username and Password
feature has been enabled, all TerraBlock
users will be prompted for their
TerraBlock username and password
when launching the TerraBlock Manager
from any client workstation.
New User Login
If the user does not currently exist on the TerraBlock server, the user logging in will
be asked to create a new user.
Selecting “Yes” will allow the
server to automatically create
the new user. Importing users is
not supported, so allowing the
server to automatically create
users is helpful in environments
with a high number of TerraBlock
users.
Once the new TerraBlock user has been created on the server, a password must be
70
created. The user logging in will be asked to create and verify their password.
Existing User Login
If a user is logging in for the first time using an existing TerraBlock user (a user that
existed prior to version 5.6) the user will be asked to create and verify their
password.
Once a TerraBlock user has
successfully logged in to the
TerraBlock system, the user’s
name will be displayed in the
Username column of the
TerraBlock Manager’s ‘Volume’
tab.
Disable Automatic User Creation
Automatic user creation is the default setting on the TerraBlock server when the
username and password login feature is enabled. This feature can be disabled from
the ‘Admin Settings’ tab in the TerraBlock Manager at the server. After all users
have been created, this can be selected to prevent additional users from being
created in the event of misspelling, etc.
New TerraBlock users must then be
created from a client with Admin
access or from the TerraBlock server.
Changing User Passwords
TerraBlock Users may change their passwords using
the ‘Change Password’ option via the ‘File Menu’ in the
client TerraBlock Manager.

Note: in a multi-server environment, users will
be prompted for username and password once the setting has been enabled
on any one of the TerraBlock servers.
 Volumes that are left mounted when logging out of the local machine
will be accessible to other local machine users after logging in to the
local machine. In order to prevent other local users from accessing
volumes, always un-mount all volumes prior to switching TerraBlock
users or logging out of your local machine.
71
LDAP/Active Directory User Feature
Once connection to an LDAP or Active Directory (AD) server has been established,
the User Groups will be listed in the TerraBlock Manager. A specific user or multiple
users can then be selected and synced or pulled from the LDAP/AD server and will
become a new TerraBlock user. It is recommended to disable the TerraBlock
User/Password feature if logging into clients using an LDAP/AD user.
Groups
Once a connection has successfully been established to the domain component or
organizational unit groups of the Active Directory (AD) server, the user groups will
be displayed. There can be multiple user groups listed depending on how the AD
server is configured.
 Please consult your Systems (IT) Administrator for LDAP/AD setup and
groups.
In the case where multiple groups are displayed, you can show specific groups,
filtering out all others, by selecting the box to the left of the group. Multiple groups
can be displayed as well, simply check which groups to display. Groups displayed
can or may be within multiple nested Organizational Units.
Right clicking directly to the right of the displayed group under the Permission
column will produce an interactive list box. This lists all of the TerraBlock users
currently active on the TerraBlock server. The user selected from this list will then
be displayed under the Permission column. The volumes and permissions for the
TerraBlock user (“Editor” in the example above) will be applied to any LDAP/AD user
that is synced. This applies to any LDAP/AD user in the selected group (all users in
the Class105 group in the example above).
72
Users
The list of Users corresponds to the LDAP/AD Group that is selected as well as what
filter settings are set in the Settings area (Show TerraBlock or LDAP users).
After a group(s) has been selected, a Users list will populate (the only list of LDAP
users is group Class105 in the example above). The user’s status may be reviewed.
Any new LDAP/AD user will be missing from the TerraBlock. The same User(s) may
be located on both servers. Changes may have to be applied to the TerraBlock user
if volumes and or permissions have changed for the user (see above). A single click
of the user in the User list will generate a “pop up” dialog box that will list the
changes to be applied.
Sync Selected
A User can be selected in the User list and depending on the status the action
performed will differ upon selecting the ‘Sync Selected’ button. Sync is intended to
match the TerraBlock and LDAP/AD users exactly. Existing TerraBlock users may
be deleted. Expected action:
1. Missing in TerraBlock Status – The highlighted user(s) will be created on the
TerraBlock server, pulling from the LDAP/AD server. Sync Selected will
perform this action only for the highlighted user(s).
2. Missing in LDAP Status – The highlighted user(s) will be deleted from the
TerraBlock server when using Sync Selected.
3. Changes: +1 -3 Status – This indicates the user(s) exists on both the
TerraBlock and LDAP server, but the volume assignment or permissions have
changed. Single click the user to obtain Change action.
 Only users displayed in the User list will be synchronized.
TerraBlock and
LDAP users can be filtered under Settings.
 User passwords for the LDAP/AD user that has been synchronized are
not applied to the newly created TerraBlock user. The user will be
prompted to set a password when logging in with the TerraBlock
Manager for the first time if using the TerraBlock User/Password
feature.
Sync All
Selecting the ‘Sync all’ button will synchronize all users between the TerraBlock and
LDAP/AD servers at one time. This option is recommended during initial setup of the
TerraBlock to move or pull current LDAP/AD users to the TerraBlock server. User
passwords will need to be created when logging in to the TerraBlock Manager for the
first time if using the TerraBlock User/Password feature. Volumes and permission
can be added or changed afterwards.
 Choose to display only LDAP Users under Settings and selecting ‘Sync all’ will
add all LDAP/AD users to the TerraBlock leaving any existing TerraBlock user
untouched. If a TerraBlock user is displayed and ‘Missing in LDAP’, that user
will be deleted with ‘Sync all’.
73
Creating Volumes
Volumes must be formatted prior to use by client workstations. If the volume will be
used with the Facilis Shared File System (Multi-user Write), it is recommended that
all volumes be formatted as NTFS.
 While HFS+ is supported for use with the Facilis Shared File System, it is
strongly recommended that Multi-user Write volumes are formatted with an
NTFS filesystem.
When creating Single-user Write volumes from a fibre channel connected client
workstation, the Auto Format feature within the ‘Create Volume’ window should be
used. This will ensure that Windows and Mac client workstations have properly
formatted volumes. For Linux clients, Single-user Write volumes must be manually
formatted.
 The client workstation must be Fibre Channel attached in order to format
Single-user volumes.
Multi-user Write volumes can be created from any client workstation or the
TerraBlock server itself. Selecting Multi-user Write as the volume type within the
‘Create Volume’ window will automatically create, format, and set the volume to
Multi-user Write. When completed, the volume will be NTFS formatted. Once this
process is completed by the server, the volume will is ready to mount on any client
workstation.
 Please allow up to one minute or more for the server to create Multi-user
write volumes.
 If the TerraBlock Server has not completed creating a Multi-user
Write volume or the automatic format has failed for some reason,
users will be presented with the following when mounting: (Contact
Facilis Support if this message proceeds after several minutes).
Any virtual volume formatted NTFS and set to Multi-user Write can now be mounted
74
with write access by Mac OS 10.6.8 or higher, Windows XP 32bit and Windows 7
64bit and Linux kernel 2.6.18 or higher. While you can change SUW HFS+ (MAC OS
EXTENDED) formatted volumes as Multi-user Write, NTFS is recommended. Setting
an HFS+ (MAC OS EXTENDED) volume to Multi-user Write requires that you install
the latest version of the MediaFour MacDrive software on the TerraBlock Server.
Logical Volumes
When creating a volume the Terrablock server creates the volume in logical pieces.
A logical volume may be no more than 1000GB. Thus larger volumes are
constructed with more logical pieces. Each logical volume has a second RAID or
Mirror piece unless the volume is unprotected. Expanding a volume creates new
logical volumes.
 The logical volume limit on a server is 475 per drive group. The
logical volume count can be seen by launching SMDriveMonitor or
Dataverifier. Exceeding the logical volume limit may prevent you from
creating new volumes.
DynaRAID
The DynaRAID option within the ‘Create Volume’ window allows the system
Administrator to determine which protection scheme will be used on a per virtual
volume basis.
DynaRAID: Single TerraBlock Server

In a mirrored volume, data on one drive is protected by another drive or set
of drives. If an individual physical drive fails, there is a backup copy of the
information contained on the mirrored volume which is read from the
remaining drives. Mirrored volumes require available storage space that is
equal to the size of the volume. Mirrored data is self-contained on a single
TerraBlock Server.

In a RAID5 Parity volume, data is compressed and saved as parity
information. The RAID5 compression algorithm reduces the space required for
protection of data to about 9% of the total volume size. In the event of an
individual physical drive failure, the data is read in real-time from the parity
information contained on the remaining drives. RAID5 data is self-contained
on a single TerraBlock Server.

In an unprotected volume, there is no RAID5 or mirroring protection to back
up the data contained on the volume. Unprotected volumes are not
recoverable in the case of an individual physical drive failure. If an individual
physical drive failure occurs, all data residing on unprotected volumes will be
lost. This data will need to be re-ingested. Because unprotected volumes
contain no DynaRAID protection, no additional storage space is required.
DynaRAID: Multiple TerraBlock Servers or Facilis TX16 Expansion Chassis
DynaRAID volume protection scheme also allows RAID5 Parity data to be striped or
mirrored across multiple TerraBlock Servers or Facilis TX16 Expansion Chassis’.
75

A RAID50 volume is a single volume which is striped across multiple
TerraBlock Servers or TX16 Expansion Chassis’. This multi-device striping
provides increased performance when accessing the RAID50 volume. RAID50
volumes are also referred to as ‘external tandem’ volumes due to their being
striped across multiple physical Facilis devices.
RAID50 uses the same storage-saving compression algorithm as RAID5 and
like RAID5, in the event of an individual physical drive failure, the RAID50
parity data is read in real-time from the parity information contained on the
remaining drives.
If a volume is created with RAID50 protection and one of the individual Facilis
devices becomes unavailable, the RAID50 volume will be unavailable to users
until the individual Facilis device (TerraBlock Server or TX16 Expansion
Chassis) is restored to operation.

A RAID51 volume is a single volume which is then mirrored across multiple
TerraBlock Servers or Facilis TX16 Expansion Chassis’. RAID51 volumes have
additional protection on top of the existing RAID5 Parity protection. If the
physical device (TerraBlock Server or TX16 Expansion Chassis) containing the
mirrored data becomes unavailable, the RAID51 volume will still be
mountable as ‘Read-only’ on the primary TerraBlock Server and the data
contained on the RAID51 volume will still be accessible.
RAID51 volumes are also referred to as ‘external tandem’ volumes, due to
their being mirrored across multiple Facilis devices.
RAID51 uses the same storage-saving compression algorithm as RAID5 and
like RAID5, in the event of an individual physical drive failure, the RAID51
parity data is read in real-time from the parity information contained on the
remaining drives.
RAID Descriptions
Mirrored Volumes:
In a 24D (24 drive) unit, a mirrored volume uses 2 groups even when a single group
is selected during creation.
A Mirrored volume created on group 1 will use group 2 for its mirror; a Mirrored
volume created on group 2 will use group 1 for its mirror. To create a Mirrored
volume on a given group, the alternate group must have enough free space available
as well. On the 24EX (12 drive) and 8D / 8XS (8 drive) units, the mirror occurs
within the same 8 or 12 drive group, so remaining space must be 2 x the intended
capacity of the volume.
RAID5 Volumes:
A RAID5 volume may be created on a single group, with parity (RAID5) data written
on the same group the volume is created on. To create a RAID5 volume on a singlegroup system (8D, 8XS, 24EX), that group must have enough remaining space for
the capacity of the volume, plus 9% of the capacity of the volume for parity
information. On a 24D, 9% of the volume capacity must be available on the group
where the volume is being created.
76
Tandem Volumes:
In Tandem mode, both drive groups in a 24D are used for primary data, as well as
parity (RAID5) data. Only RAID5 DynaRAID protection is available when creating a
volume in Tandem mode between two groups on the same server. Tandem volumes
created on a single server are also referred to as ‘Internal Tandem’ volumes as they
are self contained on a single server. Facilis recommends creating all volumes
Tandem for optimal performance.
RAID50 / RAID51
RAID50 and RAID51 volumes are created across multiple Facilis devices (TerraBlock
Servers or TX16 Expansion Chassis’) and are referred to as Multi-Server or ‘External
Tandem’ volumes. In a RAID50 external tandem volume, the RAID5 data is spread
across multiple Facilis devices. In a RAID51 external tandem volume, the RAID5 data
is mirrored across multiple Facilis devices.
External Tandem Volumes:
External Tandem (RAID50, RAID51,) volumes appear under a single heading in the
TerraBlock Manager ‘Volumes’ Tab for mount, un-mount and administration
purposes. External Tandem volumes are displayed with an arrow icon next to the
Volume Name in order to indicate that the volume is an External Tandem.

The individual server pieces that are used to comprise the combined
External Tandem volume may be viewed by double-clicking on the volume
name. Individual server pieces will appear with a ‘~’ symbol next to the
volume name with a number indicating the number of the individual piece
(~1, ~2, etc).
RAID50: RAID50 volumes are created on the TerraBlock Server and are intended for
use as Multi-user Write volumes. If the RAID50 volume has not yet been set to Multiuser Write, this can be done using the ‘Change Volume’ feature in the TerraBlock
Manager. Changing RAID50 volumes to Multi-user Write can only be done from the
TerraBlock Manager running on the TerraBlock Server.
Changing a volume from Single-user to Multi-user Write does not require the volume
to be un-mounted on the TerraBlock Server.
When working with RAID50 volumes, verify they are set to Multi-user Write prior to
mounting on a client workstation.
RAID51: RAID51 volumes are created on the TerraBlock Server and are intended for
use as Multi-user Write volumes. If the RAID51 volume has not yet been set to Multiuser Write, this can be done using the ‘Change Volume’ feature in the TerraBlock
Manager. Changing RAID51 volumes to Multi-user Write can only be done from the
TerraBlock Manager running on the TerraBlock Server.
Changing a volume from Single-user to Multi-user Write does not require the volume
to be un-mounted on the TerraBlock Server.
When working with RAID51 volumes, verify they are set to Multi-user Write prior to
mounting on a client workstation.
77

In order to mount a RAID50 or RAID51 volume as Single-user Write on a
TerraBlock client workstation, there are specific conditions that must be met:

The client must be a Windows 7 64 bit system.

The client must have specific Facilis drivers installed in order to
properly mount the RAID50 or RAID51 volume as Single-user Write.
Contact Facilis Customer Support to obtain the required drivers
and additional details for mounting RAID50 or RAID51 volumes
as Single-user Write on TerraBlock clients.
ATTO Power Center (Windows / Macintosh):
Unlike RAID50 or RAID51 volumes, ATTO Power Center External Tandem volumes
are intended for use as Single-user Write only. When mounting an ATTO Power
Center External Tandem volume for the first time, all Tandem members will appear
as raw devices until the ATTO Power Center software is launched and the Tandem
span is created. ATTO Power Center External Tandem volumes are not crossplatform when mounted as Single-user Write. See pg. 102 Appendix B – Working
with External Tandem Volumes for more information.
Creating Tandem Volumes
In the ‘Create Volume’ dialog, the Tandem button allows selection of multiple drive
groups. Drive groups may be on the same TerraBlock Server, (if working with a
TerraBlock 24D (24 drives)), different servers (in a multi-server workgroup) or TX16
Expansion Chassis’. The resulting volume or set of volumes will depend on how many
groups were selected when creating of the volume.
Internal Tandem
Internal Tandem volumes use both groups
from the same server (24 drives). Here,
groups 1 and 2 from the “TERRABLOCK24D”
server are automatically selected when
choosing the ‘Tandem’ option. The
TerraBlock Manager will create a single
volume spanning the two drive groups
selected, and give the resulting volume a
designation of “1,2” in the ‘Group’ column of
the Volumes Tab. Volumes are managed the
same way, whether they are a single group
or Tandem volume.
There is no external software necessary to
use Internal Tandem volumes, and this is the
highest-performance volume that can be
created on a 24D server. RAID5 is the only
option when creating an Internal Tandem
volume.
78
 Facilis recommends creating all volumes Tandem when applicable for optimal
performance.
External Tandem
When creating External Tandem Volumes, there are four options available: RAID50,
RAID51, and, when using ATTO Power Center, RAID5 or Unprotected.
External Tandems can be created across multiple TerraBlock Servers or individual
TerraBlock servers with an attached TX16 Expansion Chassis.
RAID50
RAID50 is supported on Windows 7 TerraBlock Servers only. When creating a
RAID50 volume, the volume must be created on the Windows 7 TerraBlock Server or
a Windows 7 client.
Creating the RAID50 Volume:
On the TerraBlock Server or Windows
client, open the TerraBlock Manager
and select the ‘Create Volume’ button.
After entering the Volume Name and
Size, select the ‘Tandem’ check box.
Select the desired drive groups from
your TerraBlock Servers or TX16
Expansion Chassis. In this example,
four drive groups are selected,
consisting of the multiple servers,
“TERRABLOCK24D” and
“TERRABLOCK24D2” in the server
column.
Select the ‘RAID50’ DynaRAID button.
Multi-user Write can also be selected.
With Multi-user Write chosen, after the
‘Ok’ button is selected a message will
appear allowing the Administrator to
choose which will be the primary
server to present the Multi-user Write
volume. The TerraBlock Server will
then create, format and mount the
RAID50 volume. The volume will be
mounted on the TerraBlock Server as
a Single-user Write volume, but set to
79
Multi-user.

The RAID50 volume creation and formatting process could take several
minutes, depending on the size of the volume. Do not interrupt the RAID50
volume creation process by performing other actions on the server during
this process.
Once the RAID50 volume has been created and formatted, it will appear in the
TerraBlock Manager ‘Volumes’ tab and will have the designation of ‘Tandem’ in the
‘Server’ column. The ‘DynaRAID’ column will display the volume as ‘RAID50’. The
RAID50 volume will have an arrow icon (Mac) or “+” icon (Windows) next to the
volume name. Double-clicking on the Volume name will cause the icon to turn down
and the individual pieces that comprise the External Tandem volume will be
revealed. The individual pieces will be displayed as <volume name>~1, ~2, ~3 etc.

When working with External Tandem Volumes, is not necessary to select the
individual External Tandem pieces (~1, ~2, etc). Any action performed on
the External Tandem Volume, such as switching to Multi-user Write, should
be performed on the ‘combined’ volume (arrow up, no ~ pieces displayed).
RAID50 volumes are intended for use as Multi-user Write volumes. Choosing Multiuser Write when creating the volume is recommended. The RAID50 Volume will be
set to Multi-user Write after the create volume process is complete, and is now
available to be mounted on any fibre or Ethernet TerraBlock client.
RAID51
RAID51 is supported on Windows 7 TerraBlock Servers only. When creating a
RAID51 volume, the volume must be created on the Windows 7 TerraBlock Server
itself.
Creating the RAID51 Volume:
On the TerraBlock Server or Windows client, open the TerraBlock Manager and select
the ‘Create Volume’ button. After entering the Volume Name and Size, select the
‘Tandem’ check box. Select the desired drive groups from your TerraBlock Servers or
TX16 Expansion Chassis. In this example, four drive groups are selected, consisting
of the multiple servers, “TERRABLOCK24D” and “TERRABLOCK24D2” in the server
column. Select the ‘RAID51’ button.
Multi-user Write can also be selected. With Multi-user Write chosen, after the ‘Ok’
button is selected a message will appear allowing the Administrator to choose which
will be the primary server to present the Multi-user Write volume. The TerraBlock
Server will then create, format and mount the RAID50 volume. The volume will be
mounted on the TerraBlock Server as a Single-user Write volume, but set to Multiuser.

The RAID51 volume creation and formatting process could take several
minutes, depending on the size of the volume. Do not interrupt the RAID51
80
volume creation process by performing other actions on the server during
this process.
Once the RAID51 volume has been created and formatted, it will appear in the
TerraBlock Manager ‘Volumes’ tab and will have the designation of ‘Tandem’ in the
‘Server’ column. The ‘DynaRAID’ column will display the volume as ‘RAID51’. The
RAID51 volume will have an arrow icon (Mac) or “+” icon (Windows) next to the
volume name. Double-clicking on the Volume name will cause the icon to turn down
and the individual server pieces that comprise the External Tandem volume will be
revealed. The individual pieces will be displayed as <volume name>~1, ~2, ~3, etc.

When working with External Tandem Volumes, is not necessary to select the
individual External Tandem pieces (~1, ~2, etc). Any action performed on
the External Tandem Volume, such as switching to Multi-user Write, should
be performed on the ‘combined’ volume (arrow up, no ~ pieces displayed).
RAID51 volumes are intended for use as Multi-user Write volumes. Choosing Multiuser Write when creating the volume is recommended. The RAID50 Volume will be
set to Multi-user Write after the create volume process is complete, and is now
available to be mounted on any fibre or Ethernet TerraBlock client.
Formatting Options
When formatting volumes directly on a Windows 7 64bit, or Windows XP 32bit,
TerraBlock Server, volumes may be created up to 8 terabytes (8000 GB) in size.
Any HFS+ (MAC OS EXTENDED) volume larger than 2 TB created and formatted on a
Mac OSX client is not supported with Windows 32 bit operating systems (TerraBlock
Server or client).
Any HFS+ (MAC OS EXTENDED) volume created as a raw volume using the
TerraBlock Server or Windows client and then formatted as HFS+ using a Mac OSX
client is supported up to 8 TB.
When formatting volumes with a filesystem other than NTFS (Windows), or HFS+
(Apple), formatting of the volume must be done manually. In order to format a
volume on a client station, the user account must be given Write permission to the
volume and the volume must be mounted in Single-user Write mode. The Virtual
Volume can be formatted using the following applications:
Windows
Macintosh OS X
Linux
Disk Management
Disk Utility
Logical Volume Management (LVM)/Shell*
Parted
* See Linux Setup

To prevent issues un-mounting volumes on Mac OSX clients,
when naming the volume on the client system when manually
formatting, you must use a volume label or name that
EXACTLY matches the TerraBlock volume name.
 Never upgrade a volume to a “Dynamic disk” on Windows.
TerraBlock does not support Dynamic disks on any system.
81

Creating volumes greater than 2TB in size on Windows XP x64
or Windows Server 2003 x64 is not supported. Create and
format volumes over 2TB in size on the TerraBlock Server or a
fibre attached Windows XP (32bit) or Windows 7 client.
 Never format a TerraBlock volume on a Mac as “Mac OS
Extended Journaled”. Journaled volumes are not supported.
When manually formatting a volume with Mac OS 10.7.2 or
greater (Lion), journaling should be disabled after the volume
format is complete. Journaling can be disabled using the Mac
OS ‘Disk Utility’ application.
 Never format a TerraBlock volume on a Mac using “GUID”
partition table. Be sure the volume is formatted using “Apple
Partition Map” as the partition scheme.
Creating Volumes larger than 8TB
With TerraBlock version 6.0 and greater, Auto Format is now supported for creating
volumes over 8TB in size. This applies to Single-user and Multi-user Write volumes.
 Volumes greater than 8TB in size are only supported using a
Windows 7 64bit based TerraBlock Server.
 Windows XP servers do not support volumes greater than 8TB
in size.
Single-user Write Volumes (SUW) are supported but have limited use. When
creating a SUW volume on a Windows 7 64bit or Mac OSX fibre channel connected
client, Auto Format should be used. The volume will be formatted using GUID
partition table which will prevent additional users from mounting the volume with
Read Only access on other client workstations.
Single-user Write volumes larger than 8TB (8000) that have been created on a
Windows 7 64bit client can be changed through the ‘Change Volume’ window to a
Multi-user Write Volume (MUW). It is best if the volume is intended to be MUW, to
create the volume at the TerraBlock Server.
 Single-user Write mounted volumes that are larger than 8TB
are only supported for single client workstations. Volumes will
not mount Read Only on other client workstations.
Single-user Write volume larger than 8TB created on a Mac OSX workstation may
also be changed to Multi-user Write. This requires Media Four’s MacDrive be
installed on the Windows 7 based TerraBlock Server.
 HFS+ Multi-user Write volumes require the installation of MediaFour
MacDrive version 8 or higher on the TerraBlock Server.
82
Multi-user Write Volumes (MUW) larger than 8TB (8000) must be created from the
TerraBlock Server itself. Creating a volume larger than 8TB from client workstation
and selecting Multi-user Write as the volume type will display the following warning:
The volume will automatically
create, format, and be set to
Multi-user Write when
created from the TerraBlock
Server itself. Choose Multiuser Write as the volume
type from the ‘Create
Volume’ window and allow
the server up to two minutes
or more to complete the process. Once the process is complete, the volume will be
mountable from all client workstations (Mac, Windows and Linux).
 Volumes larger than 8TB in size require a TerraBlock Server running
Windows 7.
 Multi-User Write Volumes over 8TB should be performance tested on the
server before use. This can be done using AJA system test or Atto Disk
Benchmark.
Tandem Volumes
If working with External Tandem volumes, please read Appendix B: Working with
External Tandem Volumes.
83
Chapter 4 – Working with Shared File System
To use the Shared File System, there first must be a properly formatted volume on
the TerraBlock Server. All the following steps are described in Chapter 4 – Setup
and Administration.

The following steps assume version 5.5 has been installed properly
and all prerequisites for hardware have been met. See the
“TerraBlock 5.5 Release Notes: Hardware and Software
Requirements” for more information.
Launching the TerraBlock Manager and Creating Volumes
The easiest way to create volumes for use with the Facilis Shared File System (SFS)
is by launching the TerraBlock Manager on a Fibre Channel or Ethernet attached
workstation, opening the ‘Create Volume…’ dialog and selecting Mount Type: ‘Multiuser Write’ in the ‘Create Volume’ dialog.
After the appropriate volume name, size, and drive group have been selected, Multiuser Write volumes will then be created, formatted using NTFS and set to Multi-user
Write automatically on the TerraBlock Server.
Single-user Write volumes can be switched to Multi-user Write after they have been
created and formatted. Single-user Write volumes created using the Auto Format
feature will be formatted automatically on Windows (NTFS) and Macintosh (HFS+)
clients. Single-user Write volumes can only be created on a fibre attached client.
While it is possible to use an HFS+ formatted volume as Multi-user Write by
installing MediaFour MacDrive software (purchased separately) on the TerraBlock
Server, NTFS format is recommended.
 Note: Single-user Write volumes created on Linux clients must be
manually formatted with a file system (i.e. XFS) using Logical Volume
Management (LVM) and/or shell commands. Single-user Write
volumes formatted with XFS are not supported for use as Multi-user
Write volumes.
 Note: When installing the Mac OSX or Linux TerraBlock Manager on a
fibre client, to ensure the Multi-user Write driver is properly installed,
mount a Multi-user Write volume and then reboot the client. This
reboot procedure only needs to occur once, after the first initial
mount of a Multi-user Write Volume. Subsequent reboots when
mounting Multi-user Write volumes are not necessary.

When creating and formatting a volume, be sure to choose a large enough
size to accommodate the project. If necessary, volume expansion is
supported. Refer to the section Change Volume: Change Size.
 Whenever possible, the TerraBlock Server drive rescan process
should be avoided during heavy client workstation use.
84
Changing a Single-user volume to Multi-user
After the format of a Single-user volume completes, the Single-user volume will be
accessible to the local client system. The TerraBlock Manager will show the volume
mounted for Single-user Write. On Windows clients, verify the volume appears on
the client with the drive letter specified, (or in C:\volumes, if specified) in the
TerraBlock Manager’s ‘Mount Point’ column. On Mac OSX clients, the volume should
appear on the Mac Desktop.
In order to change the attribute of the volume from Single-user to Multi-user, the
volume must be un-mounted from all client workstations. When the volume is clear
of all client mounts, highlight the volume in the TerraBlock Manager Volume tab and
select ‘Change Volume’. In the Change Volume dialog, move the selected Mount
Type from Single-user Write to Multi-user Write. Click OK to leave the dialog.
.

If the volume has been created as Single-user Write using ‘Auto
Format’ on the TerraBlock Server itself, the change to Multi-user
Write can be performed after format has completed. The volume
does not need to be un-mounted from the TerraBlock Server.

At this point the server will attempt to start the Shared File System
software. If an error occurs, record the error message and reference
the TerraBlock 5.5 Release Notes ‘known issues’ section.

Only NTFS and HFS+ formatted volumes may be set to Multi-user
Write
Once the volume has successfully switched from Single-user to Multi-user Write, the
volume will display in the TerraBlock Manager with a ‘W’ in the Sys column, and
‘Facilis’ will appear in the Volume Access Permissions pane as Mounted Writable in
orange (Single-user Write). Switching a Single-user Write volume to Multi-user Write
will initiate a Rescan Disks operation on the TerraBlock Server.
 TerraBlock Server disk rescan operations should be avoided
during heavy client use if possible.
 Verify the TerraBlock Manager application is not running on the
TerraBlock Server when using a client workstation to change
volume mount type.
85
Mounting Multi-user Write volumes
Once the volume has been automatically created or changed to Multi-user Write, and
displays a ‘W’ in the Sys column, the user is free to mount the volume with Write or
Read-Only access. If desired, on Windows clients prior to mounting the volume, use
the volume ‘Mount Properties’ setting in TerraBlock Manager to set up a mount
location (drive letter or C:\Volumes). For Windows, Mac and Linux clients, Persistent
Mount, a mount attribute that will persist (Read/Write), can also be set.


On Windows and Mac clients, the TerraBlock Manager “File System
Emulation” setting is set to “ON” by default. “File System
Emulation” is required whenever an Avid application is accessing a
Multi-user Write volume.
Once the Mount Properties are set, select the volume from the list and then
press the ‘Mount’ button. The volume should turn bold green and display a
‘W’ in the local user column. In Windows Explorer, Mac OS Finder and Linux
Filesystem, the volume will appear as a network drive. Verify that the
contents of the volume are consistent with the previous known contents.
Working with Multi-user Write volumes
Windows
After a Multi-user Write volume has been mounted on a Fibre Channel or Ethernet
client, a Facilis Technology blue icon will appear in the Windows system tray.
Holding the mouse over the Facilis icon will display the number of mounted files.
Mounted files is the number of volumes that are mounted.
Depending on its Mount Properties, after the mount completes, the volume will be
seen in Windows Explorer as a Network Drive if
it is mapped to a drive letter. Mapped in
C:\Volumes, the volume will be seen as a
subdirectory.
The proceeding network information after the volume name will not be visible in
applications using the volume. The network information cannot be removed.
Macintosh
After a Multi-write volume is mounted on a client and the Finder
Preferences are set to view Connected Servers, the volume will
mount on the Desktop as a Network Drive.

To set the Mac OS Finder display preferences, select
Preferences from the Finder menu or click on the Mac OS
Finder icon in the Doc and press the ‘Command + ,’ keys on the keyboard.
To choose this Multi-user Write Drive
as a usable drive in an application,
select the Computer Name to list
connected drives.
86
In this example, ‘Render’ is the
Facilis Multi-user Write (Shared File
System) volume to be chosen for
use in the Apple Final Cut Pro
application.
Linux
When a Multi-user Write volume is mounted on a Linux client, the volume will
automatically mount to a mount-point in the Linux Filesystem. When working with
Multi-user Write volumes, no additional manual steps are needed to mount volumes.
To un-mount Multi-user Write volumes, use the Unmount button in the TerraBlock
Manager ‘Volumes’ tab. Unlike Single-user Write volumes, Multi-user Write volumes
do not require you to manually un-mount them from the filesystem prior to unmounting them with the TerraBlock Manager.

Because the TerraBlock Manager runs under the ROOT user, the Multi-user
Write volume mount-points may need to have their permissions set in order
for users and applications to access them.
To set the permissions of the Multi-user Write drive mount-point, open a
Terminal and as ROOT use the ‘chmod’ command in the Linux shell.
Example: chmod –R 777 /<mount-point>/<volume name>
87
Chapter 5 –Volume Permissions and Workflows
Users Permissions to Volumes
Up to 200 users may be given permissions to over 250 volumes per server. User
permissions are based on the OS login user that was created or the user created
after the User and Password feature has been enabled. If multiple users require
different permissions, but use the same workstation, the User and Password feature
is recommended. Enabling the “Unmount Volumes on Exit” feature from the User
Mode menu should be used for this type of workflow. Multiple user accounts can be
created on the local machine, or users may login to the local machine through Active
Directory. If logging in with Active Directory, the LDAP user feature can be used to
sync and create new TerraBlock users.
The login name sent to the TerraBlock server after login at a client workstation will
be the basis for permissions when displaying and mounting new volumes. If the
Administrator wishes the permissions to remain the same on a per client basis, the
same user should be used when logging in with the TerraBlock Manager.
Permissions to volumes can be granted to allow Write, Read Only or no access.
Multiple users may have write permissions to a single volume. Keep in mind, while in
Single-user Write mode, only the first user to mount the volume with write access
will have the ability to write to the volume. All others must mount with Read Only
access. Multi-user Write gives all users the ability to mount the same volume with
write access.
Volume Workflows for Single User Write
Virtual volumes benefit from the ability to be managed on a per-project basis. The
media management that project-based workflow allows will simplify the clean-up,
consolidation, archive and eventual deletion of project data.
A volume created for a particular project can be resized as the project grows. After
the project is completed or archived, the volume can be deleted to make room for
additional projects entering the facility. This flexibility offers the administrator the
opportunity to be very particular about the location of media and create unique
permissions to small writable volumes, or use the high-capacity volume option to
create very few multi-terabyte volumes and simplify the user workflow with an open
access approach.
There is never a need to partition all the space immediately. The administrator may
choose to create volumes only as needed for a particular week or month. Even if
some static space is needed for users that create content for all projects, or require
dedicated capacity for media ingest or archive operations, some of the TerraBlock
storage can always be left unallocated for future needs.
Volume Workflows for Multi-user Write
The Facilis Shared File System (SFS) allows users to create volumes that are larger
and have Multi-user Write access for multiple clients to write data. However, the
media management of very large volumes can become cumbersome unless an asset
management system is put in place for search ability.
When moving from a Single-user Write access model to Multi-user Write, the security
88
in effect through volume-level locking will no longer apply. When using Single-user
volumes, even if multiple users had write permissions, only one user could add or
delete data at a time. If a volume was consistently used for write on a single
workstation, all other workstations were blocked from affecting that data.
In Multi-user Write, this changes so that all users have the ability to change data on
any volume to which they are given write permissions. Keep this in mind when
moving volumes to Multi-user write, so that writable data is not exposed to the
wrong users.
89
Chapter 6 – Facilis File Migration Tool
The Facilis File Migration Tool enables the user to quickly copy data between local
storage or network storage and TerraBlock volumes.
Facilis File Migration Tool
The Facilis File Migration Tool is a cross-platform Mac and Windows copy file utility.
The tool is designed to reduce the bandwidth load on the Terrablock Server. The
standard drag and drop file copy in Mac OS X and Windows will copy files as fast as
possible. This is often not desirable since it impacts the performance of the
Terrablock Server, potentially resulting in performance issues for other clients. The
Facilis File Migration Tool governs the copy speed and prevents valuable bandwidth
from being used when copying and archiving. In addition, the tool copies files to
TerraBlock volumes in sequential order. This ensures optimal performance for file
based workflows.
 The File Migration Tool should always be used when copying files for file
based workflows (DPX, RED, ARRI, etc.).
Setup and Usage
Using the Facilis File Migration Tool
On the left pane of the Facilis File Migration Tool, you can select directories and files
to be copied. In the right pane, choose the destination volume or directory.
Facilis File Migration Tool UI
90
Click the “Add” button to add/create a ‘Job’ to be run. The job will be added to the
lower pane. Files and/or directories can be selected from multiple volumes and
added as separate jobs to be run at once. A job added will display a “Pending”
status. Once the jobs have completed, the status will change to “Done”. A job can
be removed by highlighting it in the lower pain and clicking the ‘Remove Job’ button.
 Multiple jobs can be added and all will be run after selecting the ‘Start Copy’
button.
Set the copy speed by entering the desired number of mega-bytes per second
(MB/s). Setting the MB/s is useful if you want to keep the traffic and/or load on the
TerraBlock server low.
Compare File Dates Checkbox
This checkbox is deselected by default. In the default case, files are copied only if
they do not exist in the destination. If a file has the same name and size, it will not
be copied. Selecting “Compare File Dates” instructs the tool to inspect modification
times of files, so if a file exists in the destination, it will be copied if it is newer. If the
checkbox is off, file modification times are ignored. The checkbox is useful in cases
where a file has the same name and size in the destination, but you want to copy if it
is newer.
 Be sure the destination volume has enough space for the data being
copied.
After the jobs have completed, the Log tab can be selected above the lower pane to
view the status of each job that has been done. If any errors are generated during
the copy, check the Log for more details.
91
Chapter 7 – Facilis Project Manager / Viewer
Facilis Project Manager Overview
The Facilis Project Manager application allows Administrators to manage Final Cut Pro
and Adobe Premiere Pro project ownership. Once a user has taken ownership of a
project, that user alone will have write access to the project. All other users will have
read-only access to the project.
 Because Facilis Project Manager can be used to manipulate Final Cut
Pro and Adobe Premiere Pro Project ownership, it is recommended
that the Facilis Project Manager application be used by site
Administrators only.
Upon launching the Facilis Project Manager, the user will be presented with the
Facilis Project Manager Window.
The Facilis Project Manager window is split into two panes, the Volume Name Pane
and the Project List Pane.
The Volume Name Pane will list any volumes that were mounted at the time the
application was launched. If a volume is mounted after the Facilis Project Manager
has been opened, quit and re-launch the Facilis Project Manager to see the recently
mounted volume in the list.
The Project List Pane will list any shared Final Cut Pro or Adobe Premiere Pro projects
located on the volume selected in the Volume Name Pane.
The Project List Pane contains three columns: ‘Shared Project Name’, ‘User Name’
and ‘Host Name’.
 The Shared Project Name column lists any shared Final Cut Pro or Adobe
Premiere Pro projects that reside on the selected volume.

The User Name column lists Facilis users that currently have ownership of
92
Final Cut Pro or Adobe Premiere Pro projects.

The Host Name column lists the client machine that currently has ownership
of Final Cut Pro or Adobe Premiere Pro projects.
Facilis Project Manager Usage:
Enabling Sharing
In order to share a Final Cut Pro and Adobe Premiere Pro project on a Facilis volume,
the volume must first have sharing enabled.
1. Select the Facilis Volume you wish to use for Final Cut Pro or Adobe
Premiere Pro project sharing in the Volume Name Pane
2. Press the ‘Enable Sharing’ button.
3. The Volume will become highlighted in green in the Volume Name Pane
to indicate that Facilis project sharing has been enabled on the volume.
4. A new folder called “_Facilis Project Share” will be created on the selected
volume.
 Volumes are required to be mounted in C:\Volumes for the Windows
Project Manager to function properly. The Windows Project Manager
is for use with Windows Adobe Premiere only.
In order for the Facilis Project Manager to manage project ownership, the
Final Cut Pro or Adobe Premiere Pro project (.FCP file or .PRPROJ file) must
reside within the “_Facilis Project Share” folder located on the Facilis
volume.
Once a volume has had Facilis project sharing enabled, copy any Final Cut Pro or
Adobe Premiere Pro projects you wish to share into the “_Facilis Project Share” on
the TerraBlock volume. Alternatively, Final Cut Pro and Adobe Premiere Pro projects
can be saved directly into the “_Facilis Project Share” folder directly from the Final
Cut Pro and Adobe Premiere Pro Application using “Save” or “Save As”.

For organizational purposes, users can create sub-directories within the
“_Facilis Project Share” directory. The Facilis Project Manager will see any
Final Cut Pro project file (.FCP) or Adobe Premiere Pro Project File (.PRPROJ)
located in sub-directories within the “_Facilis Project Share” directory.
Taking or Removing Ownership
 It is recommended that only site administrators access Facilis Project
Manager to manage project ownership.
To take ownership of a Final Cut Pro or Adobe Premiere Pro project:
1. Open the Facilis Project Manager.
2. Select the volume in the Volume Name Pane where your shared project resides.
Your shared project will be listed in the Project List Pane.
3. If the project does not have an owner listed in the User Name / Host Name
columns, then the project is ‘unlocked’ and any user can take ownership by
simply opening the project from within the “_Facilis Project Share” and saving the
project.
93

Users can also take ownership by selecting the ‘Take Ownership’ button in the
Facilis Project Manager.
 Users cannot take ownership of a project if they have received an
“Access Denied” error when trying to save the project. The user must
choose “Save Project As” to ensure the original project owner’s
changes are not overwritten.
 When receiving the access denied message, attempting to save a
project, a tmp.xxxxx file is produced in the projects directory. It is
safe to delete these files.
4. If the project has an owner listed in the User Name / Host Name columns, then
the project is currently ‘locked’ for write access by the user listed in the User /
Host name columns.
 TAKING OWNERSHIP AWAY FROM THE CURRENT PROJECT OWNER
WHILE THE PROJECT IS OPEN BY OTHER USER(S) WILL RESULT IN
DATA LOSS! THE PROJECT MUST BE CLOSED FROM ALL
WORKSTATIONS BEFORE TAKING OWNERSHIP. SAVE “PROJECT AS”
IF NECESSARY.
5. Select the ‘Take Ownership’ button to take ownership of the project.
6. The owner that was listed as the project owner will now have read-only access to
the Project. That user will no longer be able to save any changes to the project.
 If changes to the project had been made but had not yet been
saved prior to taking ownership, in order to retain the changes,
do a “Save As” from within Final Cut Pro or Adobe Premier and
save as a new project.
7. The current user will now have sole write-access to the project. All other users
will have read-only access to the project.
To remove ownership of a project:
1. Open the Facilis Project Manager.
2. Select the volume in the Volume Name Pane where your shared project
resides. Your shared project will be listed in the Project List Pane.
3. If the project does not have an owner listed in the User Name / Host
Name columns, then the project is ‘unlocked’ and any user can take
ownership by simply opening the project from within the “_Facilis
PROJECT Share” and saving the project.
4. If the project has an owner listed in the User Name / Host Name
columns, then the project is currently ‘locked’ for write access by the
user listed in the User / Host name columns.
 REMOVING OWNERSHIP FROM THE CURRENT PROJECT OWNER
WHILE THE PROJECT IS OPEN BY OTHER USER(S) WILL RESULT IN
DATA LOSS! THE PROJECT MUST BE CLOSED FROM ALL
WORKSTATIONS BEFORE REMOVING OWNERSHIP. SAVE “PROJECT
AS” IF NECESSARY.
5. Select the ‘Remove Ownership’ button to remove ownership of the
94
Project.
6. The project will now be ‘unlocked’ and available for any user to take
ownership of the project.
 It is recommended that site administrators install the Facilis Project
Manager on a single Final Cut Pro or Adobe Premiere Pro client designated
for Admin purposes and use the ‘remove ownership’ feature where
possible to manage project ownership.
Once work is complete on a project segment, administrators can then
remove project ownership to make it available for different users to then
take ownership and continue working on the project.
Facilis Project Viewer
The Facilis Project Viewer is intended for use by non-admin users on Final Cut Pro or
Adobe Premiere Pro client machines. Its sole purpose is to allow non-admin users to
see which Final Cut Pro or Adobe Premiere Pro projects are currently being shared
and the current ownership status of the projects.
Facilis Project Viewer is a viewer application only and has no administrative
capabilities. The Enable Sharing, Take Ownership and Remove Ownership buttons
are grayed out and non-functional.
 The Project Viewer and Project Manager should not be run from the
same location. For example, if the two applications are both located
on the Mac desktop, the Manager will run as the Viewer application.
95
Chapter 8 – Using the CommandApp
The Facilis CommandApp provides access to functionality of the Terrablock Manager
through a Command Line Interface (CLI). The CommandApp can be launched as an
application or through a CLI on Mac, Windows, and Linux.
Running the CommandApp as an application
The CommandApp can be found in the Manager folder within the CommandApp
folder on windows or at the root of the Manager folder on both Mac and Linux OS’s.
It must remain there in order to run. On windows, the application should be renamed
to TerraBlockManager if you want to preserve mount points set in the
TerraBlockManager.
To Launch
1. Double Click CommandApp or TerraBlockManager within the CommandApp
folder.
2. The Application will ask if you want to enter an address for a TB server.
a. If you are connecting via fibre enter “n”
b. If you are connecting via Ethernet enter the IP address of the
Terrablock server
3. If you have the username and password feature enabled on the server it will
then prompt for the username.
a. Enter the username and hit enter
b. Then enter the password and hit enter (Enter ~ for no password).
4. The CommandApp will then display the list of available commands
Available Commands
l – List volumes: Lists the TerraBlock Manager volumes tab.
Example output:
s – List System: Lists the Terrablock Manager system tab.
96
Example output:
r – Remount MultiWrite volumes: Remounts Multi User Write volumes after a system
reboot. The volumes will mount and return to the command prompt.
m – Mount volume: Begins the mount volume dialogue.
1. Enter the volume name to mount then hit enter.
2. The application will then ask if to Mount read-only
a. Enter Y (uppercase Y) for yes – mount read-only
b. Enter n for no – mount writable
u – Unmount volume: Begins the unmount volume dialogue.
1. Enter the volume name to unmount then hit enter.
c – Create volume: Begins the create volume dialogue.
1. Enter the volume name to create then hit enter.
2. Enter volumes size in GB then hit enter.
3. Enter group number then hit enter.
a. The dialogue will display the groups with and the available
space.
4. Create as multi user write?
a. Enter Y (uppercase Y) to create as multi user write.
b. Enter n to create as Single user write.
q – Quit: Quits the application.
97
Running the CommandApp from a Command Line
The Facilis CommandApp can be run from the CLI on Windows, Mac, and Linux. This
gives users the ability to script and automate TerraBlock Manager commands. The
CommandApp must remain in the manager folder in order to run.
The application allows for certain variables to be set when running.
CommandApp.exe -i ipaddr -u username -p password -command
-i – Specify the IP address of the TerraBlock server if connecting via Ethernet.
-u – Specify the username you wish to log into the Terrablock server with.
-p – Specify the password if username and password login is enabled on the
Terrablock server. Enter “” for no password.
-h – Displays the CommandApp help menu.
- command – where command is one of the following:
-l
-f
-s
-r
-m
-mr
-e
-
list volumes
list users
list system
remount multiwrite volumes
mount volume
mount read only
unmount volume
Windows
On windows you will use the command prompt to run the CommandApp. You can
launch the Command Prompt by going to the Start Menu and choosing ‘Run’. In the
‘Run’ window, type “cmd” and hit enter.
In the command prompt “cd” to the directory containing the CommandApp. This
should be the Windows Manager/CommandApp directory. From here you can launch
the CommandApp with any of the variables above.
The example below would cd to the Windows Manger directory in Program Files then
remounts Multi User Write volumes via Ethernet from the server at IP address
192.168.1.1. The CommandApp connects to the server using user
CommandAppUser with no password.
cd \Program Files\Windows Manager\CommandApp
TerraBlockManager.exe -i 192.168.1.1 -u CommandAppUser -p "" –r
 Windows 8 will require you set the application to run as an
administrator in the application properties.
98
Mac/Linux
On Mac and Linux you can use Terminal to run the CommandApp. After launching
the Terminal you will need to first “cd” to the Mac Manager or Linux_Manager
directory. Then from the prompt type ./CommanApp and the appropriate variables
to launch the application.
The example below would cd to the Mac Manger directory in Applications on the Mac
then remounts Multi User Write volumes via Ethernet from the server at IP address
192.168.1.1. The CommandApp connects to the server using user
CommandAppUser with no password.
cd /Applications/Mac\ Manager
./CommandApp.exe -i 192.168.1.1 -u CommandAppUser -p "" –r
 For help creating automated scripts with the CommandApp contact
Facilis support.
99
Appendix A – Additional Setup Tools
Tools Volume Configuration
The Tools volume (named “Tools” by default in the system software), is the first 1GB
volume on the first group of drives in the TerraBlock system. Tools (or Tools1,
Tools2, etc.) is presented as a Read-Only volume to every client that connects over
Fibre Channel. Because the Tools volume is Read-Only, it cannot be formatted or
changed. In order to change or reformat the Tools volume, access can be reassigned on the fly through the TerraBlock Manager or mounted remotely using the
‘Mount by Index’ feature on the TerraBlock Server.
Windows:
1. Launch the TerraBlock Manager Application.
2. In the ‘Volumes’ tab, select the Tools volume.
3. Add User – select your local user with Write Permissions (you must be an
Admin user to do this).
4. Select the Tools volume again, choose “Mount” with Write Access.
5. Make your changes to the Tools volume (rename, reformat, etc).

Note: When reformatting, the Tools volume should be formatted using
FAT32 only.
6. Reboot the client to change the Tools volume back to Read-Only.
Mac OSX
1. Close any applications including TerraBlock Manager, and do not launch
TerraBlock Manager on the Mac client at all during this process until
instructed to do so.
2. Eject the Tools volume (apple-E) and verify it returns to the desktop.
3. Move to the TerraBlock Server, launch the TerraBlock Manager on the
TerraBlock Server and in the ‘Volumes’ tab, highlight the Tools volume.
4. Select “Mount By Index” and choose the ATTO WWN index of the client
workstation you’re using to change the Tools volume (see Chapter 4 –
Setup and Administration, Server TerraBlock Manager).
5. Mount with ‘write’ access. In the TerraBlock Manager, ‘Volumes’ tab, verify
the Tools volume now has a “W” in the ‘sys’ column.
6. Move to the Mac workstation and change or format the Tools volume.

Note: When reformatting, the Tools volume should be formatted using
FAT32 only.
7. If renaming the Tools Drive, after renaming the Tools Drive on the Macintosh
100
Client using the Mac OS Finder, open the TerraBlock Manager, select the Tools
Drive and press the ‘Change Volume’ button. Update the Tools Drive name to
exactly match the name you set when using the Mac OS Finder.

Note: After renaming the Tools Drive, verify that the Tools Drive name has
also been updated on the TerraBlock Server using the Disk Management
utility.
8. If formatting the Tools volume, once the format process is complete,
immediately launch the TerraBlock Manager on the Mac workstation. This will
create the Control file (the Control file should be 3.8MB in size after creation).
The Control file allows the Mac clients to communicate with the TerraBlock
Server.
9. Verify that the Control file has been created and is the correct size (3.8MB).
10. Reboot the Mac client when finished renaming or reformatting in order to
change the Tools volume back to ‘Read-only’.

For more information on Tools drive formatting, see Tech Note 035 – Snow
Leopard Tools Reformat.
Mac OSX Icon Installation
 The Facilis TerraBlock Icon Installer is intended for use on Macintosh
clients using the ATTO Fibre Channel cards only. The Facilis
TerraBlock Icon Installer does not install custom icons for Multi-user
write volumes.
The TerraBlock System comes with custom volume icons to distinguish Facilis
TerraBlock Single-user and Multi-user write volumes from others on the Mac
desktop. The Facilis TerraBlock Icon Installer can be used for Fibre Channel
connected Mac clients using the ATTO 4G, 8G, 16G and ATTO ThunderLink Fibre
Channel devices.

The TerraBlock Icon Installer is optional software and is not required
for TerraBlock Server / Client functionality.
To install the TerraBlock Volume OSX Icons, launch the Facilis TerraBlock Icon
Installer package on the Mac client, and follow installer application instructions. The
Icon Installer can be found in the Utilities folder on the TerraBlock Server or the
Facilis Download Center.
 The Multi-user Write (MUW) Mac icon installer will change all
connected server icons to the Facilis icon. The MUW Mac icon
uninstaller will revert this back to defaults.
101
Additional Client Software
TerraBlock clients can benefit from additional software to aid in the setup of Windows
clients. This software is available from the Downloads area of the Facilis web site.
Scrubber
In Windows XP, the mounting and un-mounting of numerous volumes, especially
Multi-server External Tandem volumes, can cause the Windows registry to become
too large. Error messages may occur referencing the size of the registry, or the lack
of resources to complete an operation. When this happens, volumes may appear
mounted, but fail to be visible in My Computer or Disk Management.
Scrubber is a Microsoft application that was designed to eliminate all entries for
devices that are unused and taking up memory. Please contact Facilis support for
more information on this utility.
TerraBlock Manager Keyboard Shortcuts
Command + ‘Letter’ for Mac OSX
Alt + ‘Letter’ for Windows
Volumes Tab
User Tab
A
Add User
Add Volume
C
Create Volume
Create User
D
Delete Volume
Delete User
E
Show Permissions Pane
No Function
F
Refresh Volume list
Opens File Menu
G
Change Permission (Within User Access
pane)
Change Permission (Within Volume
Access pane)
H
Hide Application (Mac only)
Change User Access (User highlighted)
M
Mount
No Function
N
Change Volume for selected volume
No Function
O
Update Read Only
Copy User
P
Mount Properties selected volume
R
Remove User (Within User Access pane)
No Function
Remove Volume (Within Volume Access
pane)
U
Unmount
No Function
102
Appendix B – Manually Formatting Volumes
Larger than 8TB
When creating a volume larger that 8TB, the volume can be manually formatted if
Multi-user Write is not selected when creating.
From the Create Volume window, after hitting the ‘OK’ button, use the following
procedure to complete the creation of a volume that is larger than 8TB.
Steps:
1. Wait for the volume creation to complete. The TerraBlock Manager should
display the volume with the correct size when finished.
2. Select the volume you just created and select ‘Change Volume’.
3. Change the volume Mount Type to ‘Multi-user Write’ and press OK.
4. Right-click on ‘My Computer’ and select “Manage”.
5. Select Disk Management.
6. In the lower portion of the middle pane, locate the drive you just created.
7. Right-click on the disk name (Disk number) and select properties.
8. Check the volume name and verify you are working with the correct volume.
Once you have verified you are working with the correct volume, cancel out of
the properties dialog.
9. Right-click on the disk name and select ‘Convert to GPT Disk’
 Single-user Write NTFS volumes that have been converted to
GPT will not be mountable for Read Only access on additional
clients.
10. Select the unformatted space and right-click.
11. Select ‘Create New Simple Volume’
12. Follow the prompts and select the defaults until you reach the ‘Format
Partition’ window.
13. In the ‘Format Partition’ window, select the ‘Volume Label’ text entry field and
enter the volume name exactly as it was created in the TerraBlock Manager.
103
 The Volume Label must exactly match the Volume Name in the
TerraBlock Manager in order for the TerraBlock Manager to
properly mount and un-mount the volume.
14. Select ‘Perform a quick format’ and complete the drive formatting procedure.
15. Once the drive has been successfully formatted, the volume is ready for use
104
Appendix C – Working with External Tandem
Volumes
External Tandem RAID5 using ATTO Power Center
ATTO Power Center External Tandem Volumes require the use of 3rd party software:
ATTO Power Center. When creating an ATTO Power Center External Tandem Volume,
the individual tandem pieces are created on the Facilis device (TerraBlock Servers or
TX16 Expansion Chassis). The ATTO Power Center software is then used to complete
the volume creation process.
ATTO Power Center External Tandem Volumes are supported for use as Single-user
Write ONLY and are platform specific, depending on the platform they are created
on, Mac or Windows.
Creating the External Tandem RAID5 ATTO Power Center Volume
Here, the volume “HDSpan” is given a size of 500GB. Four groups are selected,
consisting of the multiple servers, “TERRABLOCK24D” and “TERRABLOCK24D_2” in
the server column. The TerraBlock Manager will create four volumes, one on each
group selected. The resulting volume will have the designation of “Tandem” in the
Group column.
Third party software is required to use RAID5 External Tandem volumes. ATTO Power
Center is required for Windows or Macintosh, respectively.
 RAID5 External Tandem volumes are not Cross Platform between Mac
and Windows. Do not attempt to mount a RAID5 External Tandem
volume on a platform that is different from the platform used to
create the volume.
If a user needs to access data on a RAID5 External Tandem volume
from a platform that is different from the platform that the volume
was created with, use a network re-share of the RAID5 External
Tandem volume to access the volume.
 NTFS based RAID5 External Tandem volumes that are greater than
2TB must be created from a Windows 7 or XP 32 bit fibre connected
client that has ATTO Power Center installed. 64 bit based Windows
OS will force GUID Partition Table which does not support read-only
functionality.
 When a RAID5 External Tandem volume is created and both groups
from a particular TerraBlock Server or TX16 Expansion Chassis are
used, those two groups will appear as one piece when viewing the
individual tandem pieces in TerraBlock Manager. You will be able to
see that groups 1 and 2 will be listed under the Groups column next
to that individual piece.
105
Formatting the External Tandem RAID5 ATTO Power Center Volume
After creation, RAID5 External Tandem volumes will exist on a single
line of the TerraBlock Manager ‘Volumes’ tab. An arrow to the left of
the volume name designates it as an External Tandem.
When the volume name is double-clicked, the members of the
RAID5 External Tandem volume are exposed. The entire volume
set is mounted and un-mounted by selecting the single line-item.
Before formatting, the RAID5 External Tandem volume will be
seen as many separate volumes to the client station.
Formatting RAID5 External Tandem Volumes – Mac
The ATTO Power Center version 4.3.0 or later must be used to format RAID5
External Tandem volumes. The volumes will first appear normally as un-initialized
raw devices. Do not use the OSX disk utility with these volumes, and select “Ignore”
if prompted to initialize the volumes after mounting on the Mac client.
 Quit all applications at this time, including TerraBlock Manager. The
final format step will fail if any volumes are being accessed during the
process.
ATTO Power Center is a licensed utility.
Contact Facilis Technology to purchase a
license for Power Center in order to use
the RAID5 External Tandem Feature.
The ATTO Power Center utility will open with
the option to Create, Delete or open Utilities.
Select Create.
This will be followed by an option to create a
Standard or RAID0 Volume. Select RAID 0.
Once in the Create RAID 0 dialog, select the
volumes mounted as part of the Tandem set.
The names given to the volumes in
TerraBlock Manager will be displayed under
the Model column.
Select 'Next' and proceed through the next
window as well with no changes.
On the third window you’re asked to provide
a Name, and an Interleave. Name the volume
exactly the same as the name you first gave
the volume in TerraBlock Manager.
106
The Interleave should always be set to
1MB.
Performance problems will occur if any other
setting is used. Finish on this step and
information will be given to verify before the
spanned volume is created.
When the rescan of the mounted volumes is
complete, a successful completion dialog will
appear. At this point you may choose
Continue to format additional RAID5 External
Tandem volumes, or quit and start using your
RAID5 External Tandem volume.
Formatting RAID5 External Tandem Volumes – Windows
ATTO Power Center version 1.33 and later must be used to format RAID5 External
Tandem volumes. The volumes will first appear normally as un-initialized raw
devices. Do not use the Disk Manager with these volumes until the span is created.


ATTO Express Power Center is a licensed utility, contact Facilis
Technology to purchase a license for ATTO Express Power Center in
order to use the RAID5 External Tandem Feature.
When the Express Power Center first
opens, it has no Stripe Groups or
Members.
Choose the “Add” button at the top
of the window to show a location to
enter the name of the Stripe Group.
The name of the Stripe Group should
be the same as the name given the
RAID5 External Tandem Volume.
107
Select the Members portion of the
window and click the “Add” button
again.
The “Add Drives” Selection
window appears. Select the
volumes one at a time to add into
the Tandem Span. The Product ID
is the name of the volume from
TerraBlock Manager
Click the
“Add” button
once for every
Tandem
volume to be
added to the
span.
Once all volumes have been
added to the Members area, the Interleave should be set. The Interleave should
always be set to 1024KB. Performance problems will occur if any other setting is
used.
Set the Interleave and Save the
configuration.
108
In Disk Management, initialize and create
partition on the new unallocated space.
 NTFS based RAID5 External Tandem volumes that are greater than 2 TB
must be created from a XP 32 bit fibre connected client that has Atto Power
Center installed. 64 bit based Windows OS will force GUID Partition Table
which does not support read-only functionality.
See TerraBlock Manager Function: Volume Tab - Mount for more information on
mounting External Tandem volumes as Multi-user Write for use with Facilis Shared File
System.
109
Appendix D – Server Hardware Specifications
 Warning: Be sure to remove all power before servicing the unit. See label
affixed on the TerraBlock unit for power ratings.
Power Supplies
Power supplies are hot-swappable while the server is in operation. Please read the following
procedure for swapping a power supply unit.
1.
2.
3.
4.
5.
Locate the failed power supply by the flashing amber light on the unit.
Remove the AC power cord from that power supply unit.
Press the green tab to the right to free the power supply from the chassis.
Pull on the handle to remove the power supply.
Slide the new power supply into the slot, and lock into place.
6. Attach AC power cord to the replacement power supply in the chassis.
Dimensions and Weight
Product
TerraBlock
24D/24EX
Weight with Drives
150/120Lbs
63.5/54.4 Kg
Depth
28in
71.1cm
Width
19 in
48.26cm
Height
8 ¾ (5u)
22.2cm
TerraBlock
8D
38lbs
17.23Kg
22 in
55.88 cm
19 in
48.26 cm
3.5 in (2u)
8.89 cm
TerraBlock
8XS
95lbs
43Kg
25.5 in
64.77 cm
7 in
17.78 cm
18 in
46.02
TX-16
63 Lbs
28.6 Kg
25.6 in
65 cm
19 in
48.26 cm
5.2 in (3u)
13.2 cm
T8
33 Lbs
14.97 Kg
11 1/8 in
28.25 cm
6 5/8 in
16.83 cm
12 in
30.48 cm
Environment
Max Ambient Temp: 30C / 86F
Min Ambient Temp: 5C / 41F
Non-Condensing
Electrical Input
100-240 Vac, 3-1.5 A per power cord
50-60Hz
Auto switching
Multiple power sources. Disconnect all three power cords before servicing. See user guide for
additional Warnings.
24D/24EX
Startup: ~600W
Idle: ~290W
Active: ~415W
8XS / 8D (single PSU)
Startup: ~250W
Idle: ~120W
Active: ~160W
110
Connectivity
Fibre Channel Cable Fibre Channel Terminations Fibre Channel Tolerance Ethernet Cable Ethernet Connector -
Multimode 50 or 62.5/125 Full Duplex
LC (square small form factor)
.5 DB/jump, Max 6DB/run P2P
Cat5e rated for Gbit
Multimode 50/125
RJ45 for Gbit
LC for 10 Gb
Fibre Channel Cable Specifications and Length
Micron
9 µm (OS1) Single mode
50 µm (OM4) Multi mode 4700 MHz
62.5 µm (OM1) Multi mode 200 MHz
Max Distance by optical cable 4Gbit/8Gbit/16Gbit
10km/10km/NA
400m/190m/125m
380m/150m/100m
150m/50m/35m
70m/21m/15m
Ethernet Cable Specifications and Length
UTP
CAT 5E, CAT 6 or CAT 7
Length Max 1Gbit
100m
UTP
CAT 6 or CAT 7
Length Max 10Gbit
100m
Optical Fiber
50 µm (OM3)
Length Max 10Gbit
300m
111

TerraBlock Users Guide

Transcription

Similar documents

AccessHR Harvard July 2010 v2

Program Manager`s Report

Akira Page 5 Astro Boy Page 6 Azumanga Daioh Page 7 Bakuman

DermaTOP-HE

Hilary Boulding, Principal of the Royal Welsh College of Music

Using a bookrest with original archive volumes

Announcing

Highlights - Colliers International

TermiCom SE-15

artbook - Elcograf