User Manual
Table Of Contents
- Revision History
- Chapter One Hardware Installation and Initial Configuration
- Chapter Two VAST2 Software Configuration and Management
- Log in
- Introducing VAST2
- Charged Add-on Features
- Installation Option - OpenVPN
- Chapter 2-1 Basics: Control and Elements
- Hot Keys
- View Cell Elements
- VAST Server and Client Components
- Minimum System Requirements
- Chapter 2-2 Starting Up
- 2-2-1. Selecting Devices
- 2-2-2. Recording Options
- 2-2-3. Storage
- 2-2-4. Starting Up - Main Page
- 2-2-5. Saving a View
- 2-2-6. Add More Live Views
- 2-2-7. Save Your Preferences
- 2-2-8. Customizable Layout
- 2-2-9. Dashboard
- 2-2-10. E-Map
- Placing DI/DO Devices
- Configuring Google Map and GPS
- 2-2-11. Event Search
- 2-2-12. PTZ Control
- 2-2-13. Playback
- 2-2-14. Alarm
- 2-2-15. Search Panel
- 2-2-16. Smart search
- 2-2-17. Tour
- 2-2-18. Thumbnail search
- Chapter 3 Applications:
- 3-1. I/O DI/DO Devices: IO Box and Related Configuration
- Configuring I/O Box DI/DO as a Trigger or Action in Alarm
- 3-2. Configuring Redundant Servers - Failover
- Failover Configuration Process
- 3-3. VCA (Video Content Analysis)
- 3-4. VAST Software License
- Updating Licenses for VAST on Virtual Machines
- Reminders for VAST Software License
- Chapter 4 Settings:
- 4-1. Settings > System > Preferences
- 4-2. Settings > Device > Cameras
- 4-3. Logical Folders
- 4-4. Settings > Recording > Recording Options
- 4-5. Settings > Recording > Backup
- Storage
- 4-6. Settings > Device > Sites
- 4-7. Settings > Device > POS
- 4-8. Settings > Device > Local DB
- 4-9. Settings > System > SMTP
- 4-10. Settings > IO Box and Related Configuration
- 4-11. Settings > User Management
- Add a New User Account - Windows AD Account
- Appendix A: VAST Service Control Tool
- Appendix B: Matrix
- Appendix C: Joystick Support
- Appendix D: Upload Device Pack
- Appendix E Database Merge Function
VIVOTEK - A Leading Provider of Multimedia Communication Solutions
User's Manual - 51
RAID 1 Drive Groups
In RAID 1 drive groups, the RAID controller duplicates all data from one drive to a second drive
in the drive group. A RAID 1 drive group supports an even number of drives from 2 through 32
in a single span. The RAID1 drive group provides complete data redundancy, but at the cost
of doubling the required data storage capacity. The following table provides an overview of a
RAID1 drive group. The following gure provides a graphic example of a RAID1 drive group.
Uses Use RAID 1 drive groups for small databases or any other environment that requires fault
tolerance but small capacity.
Strong points Provides complete data redundancy.A RAID 1 drive group is ideal for any application that
requires fault tolerance and minimal capacity.
Weak points Requires twice as many drives.
Performance is impaired during drive rebuilds.
Drives 2 through 32 (must be an even number of drives)
Segment 1
RAID 1
Segment 1
Duplicate
Segment 5 Segment 5
Duplicate
...
Segment 2 Segment 2
Duplicate
Segment 6 Segment 6
Duplicate
...
Segment 3
Segment 3
Duplicate
Segment 7 Segment 7
Duplicate
...
Segment 4 Segment 4
Duplicate
Segment 8 Segment 8
Duplicate
...
RAID 1 RAID 1 RAID 1
RAID 5 Drive Groups
A RAID 5 drive group includes disk striping at the block level and parity. Parity is the data’s
property of being odd or even, and parity checking is used to detect errors in the data. In RAID5
drive groups, the parity information is written to all drives. A RAID5 drive group is best suited for
networks that perform a lot of small input/output (I/O) transactions simultaneously.The following
table provides an overview of a RAID5 drive group. The following gure provides a graphic
example of a RAID5 drive group.
Uses Provides high data throughput, especially for large les.
Use RAID 5 drive groups for transaction processing applications because each drive can
read and write independently.
If a drive fails, the RAID controller uses the parity drive to re-create all missing
information.Use also for online customer service that requires fault tolerance.Use for any
application that has high read request rates but random write request rates.
Strong points Provides data redundancy, high read rates, and good performance in most environments.
Provides redundancy with lowest loss of capacity.
Weak points Not well suited to tasks requiring lots of small writes or small block write operations.
Suers more impact if no cache is used.
Drive performance is reduced if a drive is being rebuilt.
Environments with few processes do not perform as well because the RAID drive group
overhead is not oset by the performance gains in handling simultaneous processes.
Drives 3 through 32










