Dot Hill Systems 200 manual Data Safety

No single-point-of-failure	Supported
Automatic engagement of replacement	Supported
controller
Dynamic cache memory allocation	Supported
	Cache memory is dynamically allocated, not fixed.
Environment management	Supported
	SAF-TE, S.E.S., ISEMS (I2C interface), and onboard controller
	voltage/temp monitor are all supported in both single and
	redundant controller mode. In the event of controller failure,
	services can be taken over by the existing controller.
Cache battery backup	Supported
	Battery backup solutions for cache memory are supported in both
	single controller and redundant modes.
Load sharing	Supported
	Workload can be flexibly divided between different controllers by
	assigning logical configurations of drives (LDs/LVs) to different
	controllers.
User-configurable channel mode	Supported
	Channel modes configurable (SCSI) as HOST or DRIVE in both
	single controller and redundant controller mode.
Redundant controller firmware upgrades	Supported
	Firmware upgrade can be downloaded to the primary controller
	and then be adopted by both controllers, without interrupting host
	I/O.
Redundant controller firmware	Supported
synchronization	In the event of controller failure, a replacement controller running
	a different version of firmware can restore a redundant array with
	a failed controller. Different firmware versions can be auto-
	synchronized later.
Data Safety
Regenerate parity of logical drives	Supported
	Can be performed periodically by the user to ensure that bad
	sectors do not cause data loss in the event of drive failure.
Bad block auto-reassignment	Supported
	Automatic reassignment of bad block
Battery backup for cache memory	Supported
	The battery backup solutions provide long-lasting battery support
	to the cache memory when power failure occurs. The unwritten
	data in the cache memory can be committed to drive media when
	power is restored.
Verification on normal writes	Supported
	Performs read-after-write during normal write processes to ensure
	data is properly written to drives.
Verification on rebuild writes	Supported
	Performs read-after-write during rebuild write to ensure data is
	properly written to drives.
Verification on LD initialization writes	Supported
	Performs read-after-write during logical drive initialization to
	ensure data is properly written to drives.

27