Overland®, Overland Storage®, LoaderXpress®, Multi-SitePAC®, NEO SERIES®, PowerLoader®, Protection OS®, REO®, REO SERIES®,
ULTAMUS®, VR2®, WebTLC®, and XchangeNOW® are registered trademarks of Overland Storage, Inc.
ARCvault™, NEO™, Simply Protected™, Simply Protected Storage™, SnapWrite™, and ULTAMUS SERIES™ are trademarks of Overland
Storage, Inc.
All other brand names or trademarks are the property of their respective owners.
The names of companies and individuals used in examples are fictitious and intended to illustrate the use of the software. Any resemblance to
actual companies or individuals, whether past or present, is coincidental.
PROPRIETARY NOTICE
All information contained in or disclosed by this document is considered proprietary by Overland Storage. By accepting this material the recipient
agrees that this material and the information contained therein are held in confidence and in trust and will not be used, reproduced in whole or in
part, nor its contents revealed to others, except to meet the purpose for which it was delivered. It is understood that no right is conveyed to
reproduce or have reproduced any item herein disclosed without express permission from Overland Storage.
Overland Storage provides this manual as is, without warranty of any kind, either expressed or implied, including, but not limited to, the implied
warranties of merchantability and fitness for a particular purpose. Overland Storage may make improvements or changes in the products or
programs described in this manual at any time. These changes will be incorporated in new editions of this publication.
Overland Storage assumes no responsibility for the accuracy, completeness, sufficiency, or usefulness of this manual, nor for any problem that
might arise from the use of the information in this manual.
Copyright (c) 1998,1999,2000. Traakan, Inc., Los Altos, CA. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
1. Redistributions of source code must retain the above copyright notice unmodified, this list of conditions, and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.
THIS SOFTWARE I10400175-101S PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED
WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT,
INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
POSSIBILITY OF SUCH DAMAGE.
GNU GENERAL PUBLIC LICENSE
NOTE! This copyright does *not* cover user programs that use kernel services by normal system calls - this is merely considered normal use of
the kernel, and does *not* fall under the heading of “derived work”.
Also note that the GPL below is copyrighted by the Free Software Foundation, but the instance of code that it refers to (the Linux kernel) is
copyrighted by me and others who actually wrote it.
Also note that the only valid version of the GPL as far as the kernel is concerned is _this_ particular version of the license (i.e., v2, not v2.2 or v3.x
or whatever), unless explicitly otherwise stated.
Linus Torvalds
----------------------------------------
GNU GENERAL PUBLIC LICENSE
Version 2, June 1991
Copyright (C) 1989, 1991 Free Software Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.
Preamble
The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public License is
intended to guarantee your freedom to share and change free software--to make sure the software is free for all its users. This General Public
License applies to most of the Free Software Foundation's software and to any other program whose authors commit to using it. (Some other Free
Software Foundation software is covered by the GNU Library General Public License instead.) You can apply it to your programs, too.
When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the
freedom to distribute copies of free software (and charge for this service if you wish), that you receive source code or can get it if you want it, that
you can change the software or use pieces of it in new free programs; and that you know you can do these things.
To protect your rights, we need to make restrictions that forbid anyone to deny you these rights or to ask you to surrender the rights. These
restrictions translate to certain responsibilities for you if you distribute copies of the software, or if you modify it.
For example, if you distribute copies of such a program, whether gratis or for a fee, you must give the recipients all the rights that you have. You
must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights.
We protect your rights with two steps: (1) copyright the software, and (2) offer you this license which gives you legal permission to copy, distribute
and/or modify the software.
Also, for each author's protection and ours, we want to make certain that everyone understands that there is no warranty for this free software. If
the software is modified by someone else and passed on, we want its recipients to know that what they have is not the original, so that any problems
introduced by others will not reflect on the original authors' reputations.
Finally, any free program is threatened constantly by software patents. We wish to avoid the danger that redistributors of a free program will
individually obtain patent licenses, in effect making the program proprietary. To prevent this, we have made it clear that any patent must be
licensed for everyone's free use or not licensed at all.
The precise terms and conditions for copying, distribution and modification follow.
GNU GENERAL PUBLIC LICENSE
TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
0. This License applies to any program or other work which contains a notice placed by the copyright holder saying it may be distributed under the
terms of this General Public License. The “Program”, below, refers to any such program or work, and a “work based on the Program” means either
the Program or any derivative work under copyright law: that is to say, a work containing the Program or a portion of it, either verbatim or with
modifications and/or translated into another language. (Hereinafter, translation is included without limitation in the term “modification”.) Each
licensee is addressed as “you”.
Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running the
Program is not restricted, and the output from the Program is covered only if its contents constitute a work based on the Progr
having been made by running the Program). Whether that is true depends on what the Program does.
1. You may copy and distribute verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and
appropriately publish on each copy an appropriate copyright notice and disclaimer of warranty; keep intact all the notices that refer to this License
and to the absence of any warranty; and give any other recipients of the Program a copy of this License along with the Program.
You may charge a fee for the physical act of transferring a copy, and you may at your option offer warranty protection in exchange for a fee.
2. You may modify your copy or copies of the Program or any portion of it, thus forming a work based on the Program, and copy and distribute such
modifications or work under the terms of Section 1 above, provided that you also meet all of these conditions:
a) You must cause the modified files to carry prominent notices stating that you changed the files and the date of any change.
b) You must cause any work that you distribute or publish, that in whole or in part contains or is derived from the Program or any part thereof,
to be licensed as a whole at no charge to all third parties under the terms of this License.
c) If the modified program normally reads commands interactively when run, you must cause it, when started running for such interactive use in
the most ordinary way, to print or display an announcement including an appropriate copyright notice and a notice that there is no warranty (or
else, saying that you provide a warranty) and that users may redistribute the program under these conditions, and telling the user how to view a
copy of this License. (Exception: if the Program itself is interactive but does not normally print such an announcement, your work based on the
Program is not required to print an announcement.)
These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from the Program, and can be
reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you
distribute them as separate works. But when you distribute the same sections as part of a whole which is a work based on the Program, the
distribution of the whole must be on the terms of this License, whose permissions for other licensees extend to the entire whole, and thus to each
and every part regardless of who wrote it.
Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely by you; rather, the intent is to exercise the
right to control the distribution of derivative or collective works based on the Program.
In addition, mere aggregation of another work not based on the Program with the Program (or with a work based on the Program) on a volume of
a storage or distribution medium does not bring the other work under the scope of this License.
3. You may copy and distribute the Program (or a work based on it, under Section 2) in object code or executable form under the terms of Sections
1 and 2 above provided that you also do one of the following:
a) Accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2
above on a medium customarily used for software interchange; or,
b) Accompany it with a written offer, valid for at least three years, to give any third party, for a charge no more than your cost of physically
performing source distribution, a complete machine-readable copy of the corresponding source code, to be distributed under the terms of Sections
1 and 2 above on a medium customarily used for software interchange; or,
c) Accompany it with the information you received as to the offer to distribute corresponding source code. (This alternative is allowed only for
noncommercial distribution and only if you received the program in object code or executable form with such an offer, in accord with Subsection b
above.)
The source code for a work means the preferred form of the work for making modifications to it. For an executable work, complete source code
means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and
installation of the executable. However, as a special exception, the source code distributed need not include anything that is normally distributed
(in either source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs,
unless that component itself accompanies the executable.
If distribution of executable or object code is made by offering access to copy from a designated place, then offering equivale
sour ce code from the s ame p la ce co unts as di stri buti on of th e source code, even though third parties are not compelled to copy the source along with
the object code.
4. You may not copy, modify, sublicense, or distribute the Program except as expressly provided under this License. Any attempt otherwise to copy,
modify, sublicense or distribute the Program is void, and will automatically terminate your rights under this License. However, parties who have
received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance.
5. You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute
the Program or its derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by modifying or distributing
the Program (or any work based on the Program), you indicate your acceptance of this License to do so, and all its terms and conditions for copying,
distributing or modifying the Program or works based on it.
6. Each time you redistribute the Program (or any work based on the Program), the recipient automatically receives a license from the original
licensor to copy, distribute or modify the Program subject to these terms and conditions. You may not impose any further restrictions on the
recipients' exercise of the rights granted herein. You are not responsible for enforcing compliance by third parties to this License.
7. If, as a consequence of a court judgment or allegation of patent infringement or for any other reason (not limited to patent issues), conditions
are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from
the conditions of this License. If you cannot distribute so as to satisfy simultaneously your obligations under this License and any other pertinent
obligations, then as a consequence you may not distribute the Program at all. For example, if a patent license would not permit royalty-free
redistribution of the Program by all those who receive copies directly or indirectly through you, then the only way you could satisfy both it and this
License would be to refrain entirely from distribution of the Program.
If any portion of this section is held invalid or unenforceable under any particular circumstance, the balance of the section is intended to apply and
the section as a whole is intended to apply in other circumstances.
It is not the purpose of this section to induce you to infringe any patents or other property right claims or to contest validity of any such claims;
this section has the sole purpose of protecting the integrity of the free software distribution system, which is implemented by public license
practices. Many people have made generous contributions to the wide range of software distributed through that system in reliance on consistent
application of that system; it is up to the author/donor to decide i f he or she is willi ng to d ist ri bute s oft ware t hroug h any o ther system and a licensee
cannot impose that choice.
This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this License.
8. If the distribution and/or use of the Program is restricted in certain countries either by patents or by copyrighted interfaces, the original
copyright holder who places the Program under this License may add an explicit geographical distribution limitation excluding those countries, so
that distribution is permitted only in or among countries not thus excluded. In such case, this License incorporates the limitation as if written in
the body of this License.
9. The Free Software Foundation may publish revised and/or new versions of the General Public License from time to time. Such new versions will
be similar in spirit to the present version, but may differ in detail to address new problems or concerns.
Each version is given a distinguishing version number. If the Program specifies a version number of this License which applies to it and “any later
version”, you have the option of following the terms and conditions either of that version or of any later version published by the Free Software
Foundation. If the Program does not specify a version number of this License, you may choose any version ever published by the Free Software
Foundation.
10. If you wish to incorporate parts of the Program into other free programs whose distribution conditions are different, write to the author to ask
for permission. For software which is copyrighted by the Free Software Foundation, write to the Free Software Foundation; we sometimes make
exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting
the sharing and reuse of software generally.
NO WARRANTY
11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT
PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER
PARTIES PROVIDE THE PROGRAM “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT
NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE
RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU
ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY
OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR
DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR
INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE
OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
END OF TERMS AND CONDITIONS
Copyright (c) 2000. Traakan, Inc., Los Altos, CA. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
1. Redistributions of source code must retain the above copyright notice unmodified, this list of conditions, and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.
THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON
ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Project: NDMJOB
Ident: $Id: $
Description: NDMPv0, represented here, is a fictitious version used to negotiate NDMP protocol version for the remainder of the session. Early,
as a connection is being set up, the version of the protocol is unknown. The first messages exchanged negotiate the protocol version, and such
messages are in the NDMP format. This is different than other protocols, such as ONC RPC which negotiate version by lower layers before the
objective protocol becomes involved. During the negotiation, we deem the connection to be in “v0” mode. This NDMPv0 protocol specification is the
subset of the NDMP protocol(s) required for the negotiation, and necessarily must remain immutable for all time.
Copyright (c) 1997 Network Appliance. All Rights Reserved.
Network Appliance makes no representations concerning either the merchantability of this software or the suitability of this software for any
particular purpose. It is provided “as is” without express or implied warranty of any kind.
These notices must be retained in any copies of any part of this documentation and/or software.
Various copyrights apply to this package, listed in various separate parts below. Please make sure that you read
all the parts. Up until 2001, the project was based at UC Davis, and the first part covers all code written during
this time. From 2001 onwards, the project has been based at SourceForge, and Networks Associates Technology,
Inc. hold the copyright on behalf of the wider Net-SNMP community, covering all derivative work done since then.
An additional copyright section has been added as Part 3 below also under a BSD license for the work contributed
by Cambridge Broadband Ltd. to the project since 2001.
An additional copyright section has been added as Part 4 below also under a BSD license for the work contributed by Sun Microsystems, Inc. to
the project since 2003.
Code has been contributed to this project by many people over the years it has been in development, and a full list of contributors can be found in
the README file under the THANKS section.
---- Part 1: CMU/UCD copyright notice: (BSD like) -----
Copyright 1989, 1991, 1992 by Carnegie Mellon University
Derivative Work - 1996, 1998-2000
Copyright 1996, 1998-2000 The Regents of the University of California. All Rights Reserved
Permission to use, copy, modify and distribute this software and its documentation for any purpose and without fee is hereby granted, provided
that the above copyright notice appears in all copies and that both that copyright notice and this permission notice appear in supporting
documentation, and that the name of CMU and The Regents of the University of California not be used in advertising or publicity pertaining to
distribution of the software without specific written permission.
CMU AND THE REGENTS OF THE UNIVERSITY OF CALIFORNIA DISCLAIM ALL WARRANTIES WITH REGARD TO THIS SOFTWARE,
INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL CMU OR THE REGENTS OF
THE UNIVERSITY OF CALIFORNIA BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
WHATSOEVER RESULTING FROM THE LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE
OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
---- Part 2: Networks Associates Technology, Inc. copyright notice (BSD) -----
Copyright (c) 2001-2003, Networks Associates Technology, Inc. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
* Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
* Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.
* Neither the name of the Networks Associates Technology, Inc. nor the names of its contributors may be used to endorse or promote products
derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED
WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR CONTRIBUTORS BE LIABLE FOR
ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED
TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
POSSIBILITY OF SUCH DAMAGE.
---- Part 3: Cambridge Broadband Ltd. copyright notice (BSD) -----
Portions of this code are copyright (c) 2001-2003, Cambridge Broadband Ltd. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
* Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
* Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.
* The name of Cambridge Broadband Ltd. may not be used to endorse or promote products derived from this software without specific prior written
permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDER ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING,
BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY
WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
---- Part 4: Sun Microsystems, Inc. copyright notice (BSD) -----
This distribution may include materials developed by third parties.
Sun, Sun Microsystems, the Sun logo and Solaris are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other
countries.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
* Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
* Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.
* Neither the name of the Sun Microsystems, Inc. nor the names of its contributors may be used to endorse or promote products derived from this
software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED
WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR CONTRIBUTORS BE LIABLE FOR
ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED
TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
POSSIBILITY OF SUCH DAMAGE.
---- Part 5: Sparta, Inc. copyright notice (BSD) -----
Copyright (c) 2003-2004, Sparta, Inc. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
* Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
* Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.
* Neither the name of Sparta, Inc. nor the names of its contributors ma y b e use d t o end or se or promote products derived from this software without
specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED
WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR CONTRIBUTORS BE LIABLE FOR
ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED
TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
POSSIBILITY OF SUCH DAMAGE.
---- Part 6: Cisco/BUPTNIC copyright notice (BSD) -----
Copyright (c) 2004, Cisco, Inc. and Information Network
Center of Beijing University of Posts and Telecommunications. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
* Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
* Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.
* Neither the name of Cisco, Inc., Beijing University of Posts and Telecommunications, nor the names of their contributors may be used to endorse
or promote products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED
WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR CONTRIBUTORS BE LIABLE FOR
ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED
TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
POSSIBILITY OF SUCH DAMAGE.
Overland Storage, Inc.
4820 Overland Avenue
San Diego, CA 92123
U.S.A.
The Overland Storage REO 9100 Disk-Based Backup-and-Recovery Appliance
serves as a shared network resource by utilizing high-capacity disks; high-speed
Ethernet, Fibre Channel, and Internet SCSI (iSCSI) connectivity; and unique
software intelligence capability from Overland.
The REO 9100 comes with a standard software package called Protection OS™
already installed. Protection
need to configure your REO 9100 to work within your network environment.
This document includes information that helps you set up the REO 9100,
including system requirements, questions that you need to answer before
installing the product, and installation procedures.
Preface
OS software contains all the basic features that you
Product Documentation
REO product documentation and additional literature are available online at:
This user guide exercises several typographical conventions to help explain how to
use the REO 9100.
ConventionDescription & Usage
BoldfaceWords in boldface indicate items to select such as menu items or
command buttons.
Ctrl-Alt-rThis type of format details the keys you press simultaneously. In this
example, hold down the Ctrl and Alt keys and press the r key.
NOTEA Note indicates neutral or positive information that emphasizes or
supplements important points of the main text. A note supplies
information that may apply only in special cases—for example,
memory limitations or details that apply to specific versions of a
program.
IMPORTANTAn Important note is a type of note that provides information
essential to the completion of a task or that can impact the product
and its function.
Flow Indicator (>) Words in bold font with a greater than sign between them indicate the
Safety Notices
General Cautions
CAUTIONA Caution contains information that the user needs to know to avoid
damaging or permanently deleting data or causing physical damage
to the hardware or system.
WARNINGA Warning contains information essential to people’s safety. It
advises users that failure to take or avoid a specific action could
result in physical harm to the user or hardware.
flow of actions to accomplish a task. For example, Setup > Passwords
> User indicates that you should press the Setup button, then the
Passwords button, and finally the User button to accomplish a task.
CAUTION: Before touching any of the appliance components, ground yourself and
take antistatic precautions. Use an antistatic wrist strap and a grounding wire as a
minimum precaution.
CAUTION: Each storage appliance must have a good electrical ground connection
through each power cord, through the building power grid to the point of origin for
the building power source entry.
CAUTION: Circuit Overloading—Consideration should be given to the connection of
the equipment to the supply circuit and the effect that overloading of circuits might
have on overcurrent protection and supply wiring. Appropriate consideration of
equipment nameplate ratings should be used when addressing the concern.
CAUTION: Reliable Grounding – Reliable grounding of rack-mounted equipment
should be maintained. Particular attention should be given to supply connections
other than direct connections to the branch circuit (for example, use of power
strips).
Installation Warnings and Notes
WARNING: To prevent personal injury and equipment damage, have someone
assist you during installation. If necessary, reduce the weight of the storage
appliance by removing the disk drives and PS unit.
WARNING: Mechanical Loading—Prevent instability by installing heavier items into
the bottom of the equipment rack. Mounting of the equipment in a rack should be
such that a hazardous condition is not achieved due to uneven loading to prevent
personal injury.
CAUTION: Ensure that your equipment rack is placed in a dust-free, well ventilated
area close to a UPS. Leave enough room behind the rack for servicing and to allow
for sufficient airflow.
CAUTION: Elevated Operating Ambient Temperature—When installed in a closed or
multi-unit rack assembly, the operating ambient temperature of the rack
environment may be greater than the room ambient. Therefore, consideration
should be given to installing the equipment in an environment compatible with the
manufacturer's maximum recommended ambient (TMRA).
Connecting a UPS ...................................................................................................................................... 2-7
Contents
Chapter 3 - Powering Up the Appliance
Verifying Insertion of Disks .......................................................................................................................... 3-1
Enabling Power ........................................................................................................................................... 3-1
Power Supplies ...................................................................................................................................... 3-2
Shutting Down the Appliance ................................................................................................................... 3-4
Backup Power ............................................................................................................................................. 3-4
UPS Power Monitoring .......................................................................................................................... 3-5
Behavior When Connected to UPS ..................................................................................................... 3-5
Set Up Network Addressing ....................................................................................................................... 4-1
Logging On ............................................................................................................................................ 4-1
Entering Your Network Configuration Settings ...................................................................................4-3
Configuring GbE Data Ports ...................................................................................................................... 4-4
Configuring FC Data Ports ......................................................................................................................... 4-5
Entering the System Information ............................................................................................................... 4-7
Using RAID Setup ....................................................................................................................................... 4-10
RAID Setup with One or More Expansion Units ................................................................................ 4-10
Adding a VTL ............................................................................................................................................... 5-1
Displaying VTL Status ............................................................................................................................. 5-9
Backing Up the Appliance Configuration ............................................................................................. 5-10
Standalone Disk Devices ........................................................................................................................... 6-1
Creating Standalone Disk Devices ..................................................................................................... 6-2
Modifying Standalone Disk Devices ................................................................................................... 6-2
Setting the SCSI Time-Out Value in Windows Environments ............................................................. 6-3
Creating a Multisite Tape Device ..................................................................................................... 6-13
Providing Job Schedule Information ................................................................................................ 6-14
Making a Backup Copy of the Configuration File ................................................................................6-15
Restoring Configuration Settings From Backup File ......................................................................... 6-16
Chapter 7 - Working With the Appliance
Logging On from Any System with Network Access ............................................................................... 7-1
Logging Off the GUI .............................................................................................................................. 7-2
Establishing Communication Between the Systems ............................................................................... 7-2
Connecting the REO Ports ................................................................................................................... 7-2
Looking at How Dynamic Tape Devices Work ........................................................................................ 7-3
Checking Communication with Other Appliances or Systems ............................................................. 7-4
Managing Multi-SitePAC Jobs ............................................................................................................. 7-5
Refreshing the GUI Display ......................................................................................................................... 7-6
Reviewing How the Disk Drives are Numbered ....................................................................................... 7-6
Understanding What the LEDs Represent ................................................................................................ 7-7
Front Panel LEDs .................................................................................................................................... 7-7
Back Panel LEDs .................................................................................................................................... 7-8
Relocating (Moving) an Appliance ......................................................................................................... 7-9
Using Compression ..................................................................................................................................... 9-1
List of Appliance-Specific Alerts ................................................................................................................A-2
List of Generic SNMP Alerts (Traps) ......................................................................................................A-4
Using the Log Files .......................................................................................................................................A-6
Unable to Access the Appliance .............................................................................................................A-7
REO 9100 Does Not Start Correctly ...........................................................................................................A-7
Unable to Log On to the GUI ....................................................................................................................A-8
Internet Explorer Does Not Redirect from IP Address on Windows Server 2003 .............................A-8
GUI Stops Responding or Displays a Refresh Error ...................................................................................A-9
Addressing an Unresponsive GUI ........................................................................................................A-9
Addressing a Refresh Error Message ...................................................................................................A-9
Out of Resources Message When Trying to Create a VTL ...................................................................A-11
Unexpectedly Logged Off .......................................................................................................................A-11
Unable to Connect to the Disks via Windows Explorer ........................................................................A-12
Perpetual Loop of Audible Alerts on the Appliance ............................................................................A-12
Disabling the Audible Alarm on the Appliance ....................................................................................A-13
Recover System Page Appears in the GUI ............................................................................................A-13
Troubleshooting a Disk Drive Problem ....................................................................................................A-15
Rebuilding a RAID 5 Volume (Without Hot Spare) ..........................................................................A-15
Re-creating a Hot Spare (RAID 5 With Hot Spares) .........................................................................A-16
Purchasing a Spare Disk Drive .................................................................................................................A-16
Impact of a Power Outage .....................................................................................................................A-16
Restoring a Configuration ........................................................................................................................A-17
Appendix B - Specifications
Capacities, Requirements and Limits ....................................................................................................... B-1
Industry Canada ................................................................................................................................... B-3
Title Bar .................................................................................................................................................. C-2
Submenu Bar ........................................................................................................................................ C-2
Disk ......................................................................................................................................................... C-7
FC Initiator Access ............................................................................................................................... C-8
FC LUN Map ........................................................................................................................................ C-16
System Tab ................................................................................................................................................ C-22
System Summary ................................................................................................................................ C-22
Disk Management ............................................................................................................................. C-24
Set Time ......................................................................................................................................... C-31
Setting the Time Manually ........................................................................................................... C-32
Setting the Time by NTP Server ................................................................................................... C-32
Disabling NTP Time Synchronization ........................................................................................... C-32
System Diagnostics ............................................................................................................................ C-35
Support Request File .................................................................................................................... C-36
Ping an IP Address ........................................................................................................................ C-36
Test Communication with a Remote (Multi-SitePAC) .............................................................. C-36
Test Bandwidth (Multi-SitePAC) .................................................................................................. C-37
Contact Us .......................................................................................................................................... C-37
About Initiators and Targets ...................................................................................................................... E-1
Setting Up a Multi-SitePAC Application ................................................................................................... F-3
Backing Up the Data and Data Transfer ............................................................................................ F-3
Performing a Restore Operation ......................................................................................................... F-7
Appendix G - Customer Support
Registering Your Product .......................................................................................................................... G-1
Locating Additional Information for Your Product ................................................................................. G-2
Updating the Appliance ........................................................................................................................... G-2
Determining the Version of the Protection OS ................................................................................. G-3
Checking For and Downloading Updates ........................................................................................ G-3
Updating the Appliance ..................................................................................................................... G-4
The Overland REO 9100 Disk-Based Backup and Recovery Appliance with
Protection OS™ embeds data protection intelligence, and delivers a core set of
volume and device virtualization, management, and connectivity features. It
supports both iSCSI and Fibre Channel (FC) connectivity.
The REO 9100 uses a Web-based interface and can be easily configured as a
virtual tape library (VTL) and/or any mix of standalone virtual tape drives,
Dynamic Virtual Tape (DVT) drives, or virtual disks. Using DVT, users can create
virtual tape cartridges that automatically expand or shrink as needed to match
the exact capacity requirements of the backup operation.
The REO 9100 comes in two versions: the basic appliance with optional software
compression (REO 9100) or the always-on hardware compression version (REO
9100c). The REO 9100c comes with special data compression hardware that offers
high performance compression and decompression capabilities for use with any
virtual tape device. It provides 2:1 or better compression without sacrificing
performance.
NOTE: Due to the availability of the superior hardware compression feature, software
compression is not supported on the REO 9100c. Also, hardware compression is
only available for virtual tape drives; it is not an available option for disk targets.
By default, compression is enabled and is available for all virtual tape devices on
the REO 9100c. The REO 9100c also implements in-band host application enable
or disable requests, and monitors the compression status for the virtual tape
devices.
NOTE: Hardware compression settings cannot be changed manually.
Reviewing Pre-Installation Requirements
Before attempting to operate the REO 9100 with your backup servers, verify that
your network meets the minimum requirements specified in the following
sections.
REO 9100/9100c User GuideIntroduction and Requirements
Network
For best results, Overland strongly recommends that you use a dedicated GbE
network to share the storage resources on the REO 9100 among multiple backup
servers.
To ensure optimum performance, always use the appropriate patch cables to
connect the REO 9100 to the backup-server storage network. To select the
appropriate cables, use the following guidelines:
• If you intend to use GbE, you must use Category 5e (or better) cables for
GbE connections. You can use either straight-through or cross-over cables.
• If you intend to connect the REO 9100 to a 100BaseT or faster network, use
Category 5 (or better) shielded cables.
• The maximum length of cable for any Ethernet-based network connection is
328 feet (100 meters).
NOTE: For smaller environments, you can attach the REO 9100 directly to a single
application or backup server by using standard Category 5e cables without the
use of a switch.
Initiators
Browser
Initiators are required to communicate with the REO 9100 targets (devices). Each
backup server that will interface with the REO 9100 must be equipped with a
software- or hardware-based initiator. The REO 9100 supports any computing
platform with an available iSCSI initiator, either in software or using an iSCSI
HBA (it must comply with iSCSI draft 20, version 1.0).
The REO 9100 GUI is a Web-enabled program that requires the use of cookies,
Java applets, and Java scripts. Make sure that the Web browser you use is
configured to allow these items.
The main steps involved in setting up the REO 9100 include:
1. Registering the unit to activate technical support.
2. Preparing by unpacking the appliance and reviewing safety guidelines.
3. Installing the appliance in a rack.
4. Inserting the disk drive carriers into the chassis.
5. Connecting the REO to the management LAN.
Register your REO 9100
Hardware Setup
Before installing your new unit, it is essential that you activate your REO
warranty. Technical and warranty support are not available until this is done:
1. Go to the Overland Technical Support web site at:
http://support.overlandstorage.com/
2. Using the MEMBER LOGIN, log in to the site.
NOTE: If you are not yet a member, click the New member? link and follow the
instructions. It’s free!
Figure 2-1: Login and Sign-up Links
3. From the menu on the left, select My Products > Add or Register a
WARNING: Due to the weight of each rack-mounted unit when it is fully extended,
you should install units in the rack from the bottom up. Extending a unit that has
empty spaces beneath it might cause the rack to tip forward or might result in
personal injury. Overland recommends that at least two people support and slide
the unit in the rack.
Unpacking the REO 9100
Because of its weight when loaded with disk drives, the Overland Storage REO
9100 appliance ships in two boxes.
Box one contains:
• REO chassis
• Power cords
• Rack-mount slide rail kit and hardware
• REO 9100 Documentation CD
• REO 9100 Quick Start Guide
Box two contains:
• 24 disk carriers, some or all with disk drives installed
NOTE: Depending on which version of the product that you purchased, either 12 or
24 of the carriers come with drives installed.
IMPORTANT: Before unpacking the unit, ensure that the area is free from conditions
that cause electrostatic discharge (ESD). Discharge static electricity from your body
by touching a known grounded surface. Also, avoid touching pins, leads, or circuitry.
Preparing the Installation Area
Review the following guidelines before positioning the appliance physically within
your network.
• Make sure there is unrestricted air flow around the unit and through the
vents in the sides and rear of the case.
• Route external cables so that they can be connected easily without blocking
air vents or impeding air flow.
• Protect the appliance from extreme temperature and humidity. Overland
recommends that you install the unit in a clean, air-conditioned
environment where water and moisture cannot enter the case of the
appliance. Keep the air as free from dust as possible.
• Protect the appliance from physical shock and vibration.
• Make sure that the inlet air temperature within the rack remains below the
specified limit of 95°F (35°C).
• Keep the appliance and cabling away from sources of electrical noise since
electromagnetic fields can interfere with the signals on copper cabling and
introduce errors, therefore slowing down the network.
Your REO 9100 appliance comes with a set of slide rails for mounting the chassis
in the 19-inch rack. The REO unit has a 5U form factor. The inner rail segments
are already attached to the chassis.
Installing the Rail Kit
Use these steps to install the rail kit in a square-holed RETMA rack (Figure 2-2):
NOTE: For a threaded-hole rack, omit the washers.
Figure 2-2: Outer Rail & Bracket Assembly and Positioning
1. Identify and mark the screw holes on the front and rear vertical rails of the
2. Using a mechanical lifter or two people, lift the appliance to its install height
and engage the inner slides mounted on the chassis with the middle slides
protruding from the rack.
3. Slide the appliance in until it stops.
4. Simultaneously press both lock buttons on the inner rails and slide the
appliance in until it stops again.
5. Press the same lock buttons again and slide the appliance all the way into
the rack.
6. Slide the appliance in and out several times, ensuring that the inner and
outer slide locks engage and the
chassis does not bind against the slides. If
binding occurs:
a. Remove the appliance.
a. Loosen the screws that secure the slides to the front and the rear rails of
the rack.
b. Readjust the slide positioning as needed and retighten the screws.
c. Reinsert the appliance and verify that it does not bind.
7. Slide the appliance all the way into the rack and secure the appliance
flanges with screws (left and right side) to the rack.
Reinstalling Drive Carrier Assemblies
IMPORTANT: To maintain proper airflow and cooling, a disk drive or a blank drive
carrier must be installed in every slot.
The disk drive assemblies (disks mounted in carriers) are packaged separately,
which allows you to insert them into the array chassis after you have installed the
chassis in the rack. Each disk carrier contains a label that identifies the slot into
which you must insert it.
1 - USB Ports
2 - Data Port 2 (RJ-45)
3 - Data Port 1 (RJ-45)
4 - SCSI Ports 1
5 - SCSI Port 0
6 - FC Port 1
7- FC Port 0
8 - Management Port
9- AC Power Connectors
124
5
678
9
3
IMPORTANT: Do not remove the drives from the drive carriers. The RAID array is
preconfigured so failure to install the disks in the corresponding slots may result in
the need to create a new configuration.
To install disk carriers in chassis
1. Insert the first disk carrier into the appropriate slot in the chassis.
2. With the lever in the open position, push firmly on both sides of the carrier
to ensure that the latch and connector are fully seated.
3. Press the lever in until it clicks into the locked position.
This draws the carrier fully into the slot and seats it properly inside the
chassis.
4. Repeat these steps for each disk carrier.
Attaching Cables
All cabling and power connections are located on the rear panel of your REO
appliance (Figure 2-7). Connections are available for Ethernet, USB, and serial
cabling. All unit cooling exhaust is handled through the rear panel.
Once the unit is secured in the rack and the disk drives installed, you are ready to
attach the cables that connect the REO appliance to your host system and power
source.
1. Plug the network connection into the Ethernet port.
Using a Category 5e (or better) cable, connect Data Port 1 on the appliance
to the management LAN.
2. Connect any other cables to the appropriate plugs as shown (Figure 2-7).
3. Attach the four power cords to the AC Power sockets on the REO back
panel, but do not connect the cords to any AC power sources yet.
Powering up the unit is covered in the next chapter.
Connecting a UPS
IMPORTANT: Overland recommends connecting your REO 9100 to an
Uninterruptible Power Supply (UPS).
NOTE: For more information on using a UPS, refer to “Backup Power” on page 3-4.
1. Make sure the REO 9100 is powered down and unplug the AC cords from the
main AC power source.
2. Connect the USB cable from the UPS to the USB port on the REO 9100 back
panel.
3. Plug the AC power cords from the REO 9100 into the AC sockets on the UPS.
4. Plug the AC power cord from the UPS into a main AC power source.
The main steps involved in enabling power to the REO 9100 include:
1. Making sure that the disks are correctly inserted in the appliance.
2. Connecting the power cords to a power source and enabling power.
3. Shutting down the appliance.
4. Using an Uninterruptible Power Supply (UPS).
Verifying Insertion of Disks
Because your appliance is configured with two RAID 5 with Hot Spare arrays, it is
important that the disks are inserted in the correct slots in the appliance.
all of the same capacity. The drives in one unit can be a different capacity than those in
the other units as long as all the drives in that unit are the same size.
Make sure that the disks are seated correctly to prevent an error state during the
power-on procedure. For more information, see
Assemblies” on page 2-5.
Enabling Power
situation is resolved. Overland recommends that you use separate power mains for the
power sources.
Power problems can be the cause of serious failures and downtime on your
network. Ensure that the power input to your system is clean and free from sags
and surges to avoid unforeseen network outages. Overland strongly recommends
that you install power conditioning and an adequately rated uninterruptible
power supply (UPS), especially in areas prone to blackouts, power dips, and
electrical storms.
IMPORTANT: The REO 9100 head unit must be populated with drives that are all of
the same capacity. Also, expansion units must be fully populated with drives that are
“Reinstalling Drive Carrier
IMPORTANT: All four power cords must be connected. If one of the cords is
disconnected or malfunctioning, the appliance beeps continuously until the
REO 9100/9100c User GuidePowering Up the Appliance
Power Button
To power up the appliance:
1. Plug each of the power cords into a separate AC power source.
IMPORTANT: If power is automatically enabled when you attach the cords to
an AC power source, shut down the appliance before continuing with the
setup process. For details on shutting down an appliance, see “Shutting Down the
Appliance” on page 3-4
2. To power up the REO 9100, press and hold the power button for about 1
second, which starts the power-up sequence.
The power switch is located in the top area of the front panel above the third
column of disks. The power switch is a momentary contact device that needs
to be held to begin the power-up sequence.
Figure 3-2: Power Button Location
After you turn the power on, the REO 9100 performs a power-on self-test
(POST) process. Following successful completion of the POST, which takes
several minutes, you should hear 3 beep tones spaced about 1 second apart.
If you are unable to hear the tones in your physical environment, wait
approximately five minutes before continuing.
IMPORTANT: On startup, the appliance might reach an error state and begin
an endless loop of alerts. The pattern (2 beeps separated by a 1-second
delay) repeats every 4 seconds. If this occurs, turn the appliance off and then
back on. For more information, see “Perpetual Loop of Audible Alerts on the
Appliance” on page A-12
3. After you hear the POST completion beep tones, proceed to the configuration
steps outlined in the next chapter,
“Configuring the REO Software” on
page 4-1.
IMPORTANT: You must leave the appliance ON while completing the
configuration process for your application and backup servers.
REO 9100/9100c User GuidePowering Up the Appliance
Shutting Down the Appliance
IMPORTANT: To ensure preservation of data on the REO 9100, you should not turn
off the appliance using the power button. Always use the Shut Down option located
in the REO 9100 GUI.
NOTE: If you are setting up a new appliance and you did not complete the steps in the
proper order or power was automatically enabled, you might not have access to
the Shut Down option in the REO 9100 GUI.
To shut down the appliance via the GUI:
1. Verify that no backup/restore jobs are running.
2. In the REO 9100 GUI, under System Menu, click Maintenance.
3. On the Maintenancepage, under Shut Down/Restart, click Shut Down.
4. When the confirmation message appears, click OK.
To shut down the appliance without GUI access:
1. Press and release the power button on the front of the appliance quickly
(1 second or less) to initiate a graceful software-system shutdown process.
2. Wait up to 1 minute to see if the appliance responds.
3. If the appliance does not shut down after the first attempt, repeat
Backup Power
In order to protect your data from loss due to sudden power interruption, your
REO 9100 supports the use of an external UPS. The REO 9100 monitors the UPS
via the USB port (reporting the charge level on the System Summary page). When
the REO 9100 senses a low UPS power condition, it initiates a graceful shutdown
that completes before the UPS runs out of battery power.
The LED for power will turn off after the shutdown process is finished.
Steps 1–2 a second time.
CAUTION: Pressing and holding the power button for 4 seconds or more causes an
immediate hardware-shutdown that might result in the loss of data on the
appliance if there are any active read-, write-, or management-operations.
Whenever possible, turn off the appliance using the REO 9100 GUI or the graceful
shutdown method described earlier. If you must use the immediate hardwareshutdown method, make sure that you first stop all host- and management-serverrelated activity.
REO 9100/9100c User GuidePowering Up the Appliance
UPS Power Monitoring
When the REO appliance detects that it is connected to a UPS, it displays the UPS
Information (
• When the REO is receiving power from the main AC source, the indicator
bar is green. A complete green bar and 100% indication mean that the UPS
battery is fully charged.
• When the main AC power is interrupted and the REO is powered by the
UPS, the indicator bar turns red. The red bar and the numeric indication
grow smaller as the UPS battery charge goes down.
Figure 3-3) at the bottom of the System Summary page.
Figure 3-3: System Summary Page UPS Information
• When the primary AC power is restored, the indicator bar turns green. The
green bar and the numeric indication grow toward 100% as the UPS battery
charges itself up.
Behavior When Connected to UPS
A REO 9100 with a UPS works normally as long as the main AC power is supplied.
When the main AC power is interrupted and the REO 9100 detects battery power,
it initiates a graceful shutdown in such a way as to be completed before the battery
power runs out.
Once initiated, the shutdown continues to completion, even if the AC power has
been restored. Upon completion of the shutdown, and when the AC power has been
restored, the REO 9100 does not restart automatically. Use the Power button on
the front panel to restart the REO 9100.
Supported UPS Models
UPS support has been verified with the APC Smart-UPS 2200VA. Other UPS
devices that connect via the same driver can be found at:
The main steps involved in configuring the management environment include:
1. Entering default gateway and Management Port addresses.
2. Entering the Data Port information.
3. Entering Fibre Channel and system information.
4. Configuring logon information.
5. Configuring alerts.
6. Setting the applicable time information.
7. Connecting the appliance to the application and backup servers, SAN for the
backup servers, or FC.
8. Installing software client drivers or storage adapters for iSCSI or FC access
on systems involved in the backup process.
The images shown in the following sections were captured on a Windows system.
The screens might appear slightly different if you are using a UNIX-based system.
Set Up Network Addressing
Before using your REO 9100, you must configure the network communication
addresses. The Management Port connects the REO 9100 to the Management
LAN. A workstation or computer connected to the LAN can then be used to
manage the REO 9100.
IMPORTANT: The Management Port and both Data Ports must be on a separate
subnets.
Logging On
When setting up your REO 9100, you must initially connect to Data Port 1 and
configure the network settings.
1. Directly connect a laptop or other computer to Data Port 1.
2. Configure the NIC in the laptop to be on the 10.0.0.0 network except