Coffer Disk
The storage system has two kinds of coffer disks: built-in coffer disk and external coffer disk. Coffer disks are used to store three types of data: cache data requiring power failure protection, OceanStor OS system data, and system configuration information and logs.
Built-in Coffer Disk
Each controller houses one or more disks as coffer disks. Table 4-91 describes capacity partitions of the built-in coffer disks.
Built-in Coffer Disk |
2200 V5/2600 V5/5300 V5 |
5500 V5 |
5600 V5 |
5800 V5 |
6800 V5 |
Description |
||||
---|---|---|---|---|---|---|---|---|---|---|
Size |
1 x 64 GB M.2 SATA |
1 x 240 GB M.2 SATA |
2 x 480 GB M.2 SATA |
- |
||||||
Cache dirty data partition |
9.5 GB |
21 GB |
32 GB |
Stores the cache dirty data that has not been written into a disk when the storage system is powered off. |
||||||
OS system partition |
32 GB |
Stores the OceanStor OS system data. |
||||||||
Cluster Configuration Database (CCDB) partition |
3 GB |
6 GB |
Stores the user configuration information (such as remote replication, HyperMetro, and NAS data). |
|||||||
LogZone partition |
2 GB |
4 GB |
Stores system logs and run logs when the storage system is powered off and write through is enabled. |
|||||||
DB partition |
1 GB |
Stores the user configuration information (such as information about the LUN capacity, ID, WWN, Fibre Channel ports, and iSCSI ports). |
External Coffer Disk
The first four disks in the storage system are configured as coffer disks. SAS, NL-SAS, and SSD disks can be used as coffer disks. The type of the four coffer disks must be the same.
Appearance
Figure 4-212, Figure 4-213, and Figure 4-214 show the appearances of coffer disks.
Positions
- If a storage system employs the disk and controller integration architecture, the first four disks in the storage system are configured as coffer disks. Figure 4-215 uses a 2 U controller enclosure with 25 disk slots as an example.
- If a storage system employs the disk and controller separation architecture, the first four disks in the first disk enclosure are planned as coffer disks. Figure 4-216 uses a 2 U disk enclosure with 25 disk slots as an example.
Capacity partitions
- For the disk and controller integration device, the first four disks each spares 6 GB of space to form a RAID 1 group. The rest of the coffer disk space can be used to store service data. Table 4-92 describes capacity partitions of external coffer disks.
Table 4-92 Capacity partitions of external coffer disks
Partition Name
Partition Size
Description
CCDB partition
3 GB
Stores the user configuration information (such as remote replication, HyperMetro, and NAS data). The four coffer disks are mirrors of each other for redundancy.
LogZone partition
2 GB
Stores system logs and run logs when the storage system is powered off and write through is enabled. The four coffer disks are mirrors of each other for redundancy.
DB partition
1 GB
Stores the user configuration information (such as information about the LUN capacity, ID, WWN, Fibre Channel ports, and iSCSI ports). The four coffer disks are mirrors of each other for redundancy.
- For the disk and controller separation device, the first four disks each spares 7 GB of space to form a RAID 1 group. The rest of the coffer disk space can be used to store service data. Table 4-93 describes capacity partitions of external coffer disks.
Table 4-93 Capacity partitions of external coffer disks
Partition Name
Partition Size
Description
CCDB partition
2 GB
Stores the user configuration information (such as remote replication, HyperMetro, and NAS data). The four coffer disks are mirrors of each other for redundancy.
LogZone partition
4 GB
Stores system logs and run logs when the storage system is powered off and write through is enabled. The four coffer disks are mirrors of each other for redundancy.
DB partition
1 GB
Stores the user configuration information (such as information about the LUN capacity, ID, WWN, Fibre Channel ports, and iSCSI ports). The four coffer disks are mirrors of each other for redundancy.