Is a BBU necessary when you have A+B power?
Would the data on the RAID Card Cache and Drive Cache be lost when a kernel panic happens and you are forced to do a cold reset?
Is a BBU necessary when you have A+B power?
Would the data on the RAID Card Cache and Drive Cache be lost when a kernel panic happens and you are forced to do a cold reset?
Some of this has been covered here before... and here, too. I can't think of any situation where you wouldn't want a battery-backed or flash-backed cache unit on your hardware RAID controller. It's what makes write caching possible.
See: BBWC: in theory a good idea but has one ever saved your data?
If your system panics suddenly, the question as to what happens to in-flight disk transitions depends a bit on the nature of the crash, when it happens, the filesystem in use and your storage subsystem. I've had data corruption in some cases and I've also had the RAID controller cache save the day.
Cache Status Details: The current array controller had valid data stored in its battery/capacitor backed write cache the last time it was reset or was powered up. This indicates that the system may not have been shut down gracefully. The array controller has automatically written, or has attempted to write, this data to the drives. This message will continue to be displayed until the next reset or power-cycle of the array controller.
With regard to A/B power feeds, it's nice that your datacenter or facility provide it, but it should have no bearing on your RAID controller caching decision.
A "real" hardware RAID controller (not a "fake" RAID that relies on the host CPU) is a freestanding computer separate from the host computer in which it's installed. A hardware RAID controller will handle reading/writing from the disks as the operating system makes requests, but it does not specifically rely on anything running inside the host computer operating system to function. The controller's operating system will continue running (and flushing cache, etc) even if the host computer's operating system crashes.
Edit:
I didn't mention the battery backed cache at all. I'm so used to RAID controllers like Dell's PERC series that disable write-back caching when there's no battery that I just consider a battery backup to be an integral part of any serious RAID controller.
re: the kernel panic scenario - It's worth noting that your RAID controller isn't going to save you at all if your operating system or applications aren't leaving the filesystem or their data files in a consistent state at the end of each write. If you're using a journaling filesystem or database applications that are ACID-compliant then your odds of losing data are a lot lower than if you're using filesystems or applications that are capable of leaving their on-disk data structures in an inconsistent state.
Yes, redundant power, while reducing the need for a BBU, does not eliminate that need.
Consider the case where you wire up A/B power incorrectly, for example.
The additional cost for a BBU is usually worth it where your data matters e.g. storage node, DB, etc.