이 기사가 도움이 되었습니까?
이 기사를 더욱 유용하게 만들 수 있는 방법은 무엇입니까?
Click on the Devices tab to view devices that have been added to Lyve Client.
A disk group is a combination of two or more physical drives that are presented to the operating system as a single device. Drives are combined into different configurations known as ‘RAID levels’. RAID stands for redundant array of independent disks. A RAID level categorizes how data is written to the drives in the array.
The RAID level you choose depends on which storage attributes are most important to you:
Capacity | The total amount of data you can store. |
Performance | The speed at which data is copied. |
Protection | The number of disks that can fail before data is lost. |
Lyve Mobile Array can be configured as RAID 0 or RAID 5. Both RAID levels offer advantages and disadvantages, described below.
In RAID 0, data is split into blocks that get written across all drives in the array. A minimum of two drives is required to create a RAID 0 array.
Data is not duplicated across drives. This results in faster transfers and more storage, since the full capacity of all drives can be used to store unique data.
RAID 0 lacks data protection. If a single drive fails, all data in the array is lost.
In RAID 5, data is also split into blocks that get written across all hard drives in the array. In addition, a redundant parity block is written for each data block. A minimum of three hard drives is required to create a RAID 5 array.
RAID 5’s strong advantage over RAID 0 is data protection. If one physical drive fails, the parity blocks can be used to rebuild the data on a spare drive. You still have access to all your data, even while the data is being rebuilt on the spare drive. For a configuration that does not include a spare drive, be sure to back up your data to another storage device. Contact customer support concerning the failed drive.
RAID 5 offers read performance that can approach RAID 0. However, write performance is slower because the parity data must also be calculated.
Additionally, you still have much of the storage capacity of a RAID 0 array, based on the total available hard drives and storage capacities. The equation for determining the storage is:
(The size of the drive with the smallest capacity in the array) * (Total hard drives minus 1)
Example: An array is assigned five 10TB hard drives for a total of 50TB. The equation is:
10TB * 4 = 40TB
If one drive in the array fails, restoring the data by building a replacement drive may take hours, depending on the array’s capacity. If another drive fails during this time, all data in the array is lost.
Volume Name | Enter a name for the volume. |
Auto format | Automatically format the hard drives when creating a RAID array. Use the dropdown menu to select the format that is best for your operating system: exFAT (macOS and Windows), NTFS (Windows only), HFS+ (macOS only). |
Disk cache | Enabling the cache optimizes performance, however, data is at risk since a power loss or system error clears all cached data. Disabling the cache prevents data loss in the event of power loss or system error but copy performance may be reduced. |
Initialization | Fixes sector errors that can lead to corrupt data. Note that an initialization can run for hours, or days based on the array’s capacity. You can use the device during an initialization, but it will prolong the time to complete it. Performance is degraded during an initialization.. |
Volume Name | Enter a name for the volume. |
Auto format | Automatically format the hard drives when creating a RAID array. Use the dropdown menu to select the format that is best for your operating system: exFAT (macOS and Windows), NTFS (Windows only), HFS+ (macOS only). |
Disk cache | Enabling the cache optimizes performance, however, data is at risk since a power loss or system error clears all cached data. Disabling the cache prevents data loss in the event of power loss or system error but copy performance may be reduced. |
Initialization | Fixes sector errors that can lead to corrupt data. Note that an initialization can run for hours, or days based on the array’s capacity. You can use the device during an initialization, but it will prolong the time to complete it. Performance is degraded during an initialization.. |
Lyve Client can identify a connected Lyve Mobile device for you by having it temporarily flash its LED. This is useful if you have a large bank of connected Lyve Mobile devices and you need to identify a particular device.
You can rename connected Lyve Mobile devices.
To view device details:
You can turn a Lyve Mobile device's LED on or off and view the device's LED color legend. The Legend shows the definition of each LED color to a specific state.
You can add metadata tags to your device.
A crypto-erase securely deletes all data on the Lyve Mobile device while keeping your device settings and password intact.
To securely erase your Lyve device, Lyve Client accesses all data on individual drives. Therefore, the RAID must be recreated after the crypto-erase is complete. Recreating the RAID requires an initialization that can take over 24 hours if the Lyve device is not in use. You can use your Lyve device during the initialization but performance will be degraded until it is complete. Also, using the device during an initialization will increase the time for it to complete. To avoid delays in completing the initialization, make certain that the host computer does not go to sleep until it is complete. If the computer goes to sleep, the initialization will be paused until it wakes up.
You can view Lyve Mobile device disk details, such as the status of each disk, it's capacity, and its RAID array setting. You can also allow disks that are unassigned to an array to act as a spare for any disk group on the device.
To aid in troubleshooting, you can download device log files to your computer.
You can quickly open Disk Management (Windows) or Disk Utility (Mac) to view device volumes.
You can quickly open File Explorer (Windows) or Finder (Mac) to view the content of your volume.
You can view details about your Lyve Mobile device's firmware for use in troubleshooting.