Netgear RD5200 (ReadyDATA 5200) – ReadyDATA 5200 System Empty Chassis with 10G (2 port SFP+ card) Guia Do Programa
Manage Shares and LUNs
106
ReadyDATA OS 1.4
to another array. However, iSCSI settings are not moved when you migrate a LUN from one
volume to another volume or when you move the disk or disks on which the volume with the
LUN resides to another array. (For information about how to configure the iSCSI settings, see
volume to another volume or when you move the disk or disks on which the volume with the
LUN resides to another array. (For information about how to configure the iSCSI settings, see
You can specify whether a snapshot is created, and with what frequency it is created.
You can specify the size of a LUN in two ways:
•
Thin. Even though you specify the size of a thin LUN when you create it, storage space is
assigned on demand instead of up front. This method greatly improves the utilization rate
of the LUN because storage space is assigned only as data is written to the LUN.
However, the size of the LUN is reported as the total storage space that you specify when
you create the LUN. As data is written to the LUN, the used storage space is displayed on
the volume icon in purple.
assigned on demand instead of up front. This method greatly improves the utilization rate
of the LUN because storage space is assigned only as data is written to the LUN.
However, the size of the LUN is reported as the total storage space that you specify when
you create the LUN. As data is written to the LUN, the used storage space is displayed on
the volume icon in purple.
A thin LUN lets you over-allocate its size, that is, you can assign a LUN size that is larger
than the size of the volume. You can then expand the volume as needed (if necessary,
adding disks in the process) without expanding the size of the LUN, and therefore without
disconnecting users. Make sure that you watch the volume capacity of the volume on
which the over-allocated LUN resides so that you do not run out of storage space
unexpectedly.
adding disks in the process) without expanding the size of the LUN, and therefore without
disconnecting users. Make sure that you watch the volume capacity of the volume on
which the over-allocated LUN resides so that you do not run out of storage space
unexpectedly.
Note:
NETGEAR recommends that you do not use an over allocated LUN for
storage of critical data. Instead, use a thick LUN.
storage of critical data. Instead, use a thick LUN.
•
Thick. All storage space that you specify when you create a thick LUN is also allocated
up front, and the storage space is reserved on the volume. Snapshots, other LUNs, and
shares on the volume cannot consume storage space that is reserved. The reserved
storage space is displayed on the volume icon in orange. The size of the LUN is reported
as the total storage space that you specify when you create the LUN. You cannot assign
more storage space than the available nonreserved storage space on the volume. As
data is written to the share, the used storage space is displayed on the volume icon in
purple.
up front, and the storage space is reserved on the volume. Snapshots, other LUNs, and
shares on the volume cannot consume storage space that is reserved. The reserved
storage space is displayed on the volume icon in orange. The size of the LUN is reported
as the total storage space that you specify when you create the LUN. You cannot assign
more storage space than the available nonreserved storage space on the volume. As
data is written to the share, the used storage space is displayed on the volume icon in
purple.
The following table explains the default settings of a LUN. You can change these settings
when you create or change the LUN.
when you create or change the LUN.
Table 9. LUN default settings
Item
Default State
Logbias
a
Latency
Compression
Disabled
Dedupe
Disabled
Protection
Continuous
Interval
Daily
Provision
Thick