Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

How can I tell if my hard drives have a battery backed write cache (BBWC)?

How can I tell if it is enabled and/or configured correctly?

I don't have physical access to my server. It's a GNU/Linux box.

I can provide supplemental incremental information/details as requested. My frame of reference is that of a DBA -- I have access and privileges, but (usually) only tread where I know am supposed to. :)

share|improve this question

I've never actually seen battery backed write cache in harddisks - only in RAID controllers. How to query the controller is rather specific to your hardware. It will almost certainly require root privileges on the box.

For example, using Dell PERC controllers, and having dell-omsa-repository installed, I can do:

# omreport storage battery
List of Batteries in the System

Controller SAS 6/iR Integrated (Slot Embedded)
No Batteries found

On another server:

# omreport storage battery
List of Batteries in the System

Controller PERC 4e/Di (Slot Embedded)
ID                        : 0
Status                    : Ok
Name                      : Battery 0
State                     : Ready
Recharge Count            : 0
Max Recharge Count        : 1100
Predicted Capacity Status : Not Applicable
Learn State               : Not Applicable
Next Learn Time           : Not Applicable
Maximum Learn Delay       : Not Applicable

I haven't been able to find right now how to ask it what the current write cache setting is, but I think I've seen it in there before. However, if you're not using Dell RAID controllers, you will need different software.

share|improve this answer
They do not exist, BUT - some enterprise storage systems (not sure about HD, definitely SSD) have capacitators to write the internal cache out in case of a power failure. – TomTom Jul 1 '13 at 20:35

This way you can see if the battery backup is speeding up your server, on this server it is working:

root@server:~# omreport storage vdisk
List of Virtual Disks in the System

Controller PERC H700 Adapter (Slot 1)
ID                        : 0
Status                    : Ok
Name                      : VD1
State                     : Ready
Hot Spare Policy violated : Not Assigned
Encrypted                 : Not Applicable
Layout                    : RAID-5
Size                      : 1,862.00 GB (1999307276288 bytes)
Device Name               : /dev/sda
Bus Protocol              : SATA
Media                     : HDD
Read Policy               : Adaptive Read Ahead
Write Policy              : Write Back
Cache Policy              : Not Applicable
Stripe Element Size       : 64 KB
Disk Cache Policy         : Enabled

The important line here is the

Write Policy              : Write Back

Make sure you have a battery before enabling this, using:

root@server:~# omreport storage battery

Then you can enable using:

root@server:~# omconfig storage vdisk controller=0 vdisk=0 action=changepolicy writepolicy=wb
share|improve this answer

It is called KNOWING. A dark secret by experienced system admins. They remember what hardware they order and how they configure it. Very arcane stuff. Part of the dark art of administration and requires you to read the ancient scrolls containing the purchase orders.

In the end, if you are the DBA, ask the people responsible for the system.

  • Discs normally dont have a BBWC. Discs arep owered by the computer. so that would be a redundant power supply witha USV. I know of not a single disc having the availablility top plug in a battery.
  • BBWC are a raid controller feature. Sadly ,there is no common API. Where exactly you see stuff like controlelr configuration etc. depends on the hardware. On modern hardware you may even be protrected WITHOUT battery - Adaptec recently released a controller without battery. It has a condensator keeping thing alive long enough... to write the whoe cache onto basically an on board flash non volatile memory. Same result, no maintenance (batteries needs regular replacement, they wear out within 2-3 years).

Depending - if you are the DBA - on how large the company is you may not have discs, a USV or even a raid controller available at all, but run against a SAN (which has all this in a much larger configuration).

share|improve this answer
"Knowing" is only applicable when you are the one who ordered and configured the system. – Henk May 18 '12 at 8:46
So if you do not keep a copy, the company / owner of the machine THROWS THE INVOICES AWAY? What does the government say to that when he gets a tax audit? No laws in place about proper handling of financial documents? Computers are valuable assets. – TomTom May 18 '12 at 14:42
See other answers for how to determine the answer without the packing slips. – dmourati Jul 1 '13 at 18:55

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.