vCSA 6.7 – Health Status Storage Alert /storage/archive

This post is applicable to customers using the VMware vCenter Server Appliance (vCSA) 6.7.

Update: This KB indicates VMware Engineering is aware of the issue and has been fixed. The workaround detailed below may not be supported, so implement it at your own risk.


  1. vCenter Server Appliance 6.7 deployed and in use.
  2. Login to vSphere Client: https:// <IP Address or hostname of vCenter Server>
  3. vSphere Client System Configuration reports Node Health is Degraded. Access this page from Administration, Deployment, System Configuration.
  4. Login to vCenter Server Appliance VAMI: https:// <IP Address or hostname of vCenter Server>:5480
  5. vCenter Server Appliance VAMI Health Status reports an Alert for Storage: “File system /storage/archive is low on storage space. Increase the size of the disk /storage/archive.” Access this page from Summary, Health Status.
  6. VMware has not created an updated KB article explaining how to remediate this particular issue.


  1. SSH into the vCSA and login as root and execute the “shell” command to get shell access.
  2. Run the “df -h” command and verify the “/storage/archive” mount is at 90+% of use.
  3. Access the vCenter Server that the vCSA instance is running on and increase Disk 13 of the vCSA VM Hardware by a significant amount.
  4. In the SSH session to the vCSA, run the autogrow script “/usr/lib/applmgmt/support/scripts/”.
  5. Run the “df -h” command and verify the “/storage/archive” mount Use percentage has decreased.
  6. After some time has passed, verify the vSphere Client System Configuration Node Health is “Good”.
  7. Verify the vCenter Server Appliance VAMI Health Status for Storage is “Good”.


In vSphere 6.5, the vCenter Server Appliance has 12 vDisks, in vSphere 6.7, this has increased to 13. The 13th disk is used for the /storage/archive volume.

Published by


Chief Enterprise Architect and Strategist, 4xVCDX#133, NPX#8, DECM-EA.

5 thoughts on “vCSA 6.7 – Health Status Storage Alert /storage/archive”

  1. My vCenter is 6.7 build 11338799. I had to increase disk 4 from 50GB to 90GB. Increasing the size of disk 13 caused /storage/dblog to be increased.

    1. not what it says. ‘the /storage/archive partition can be full by design’. Can does NOT imply should.. I don’t agree that systems ‘automatically’ fix themselves. Too many times I have been victim that services should rotate logs or delete older entries.. not doing it again. Therefore if a volume is FULL it should be increased regardless of what automated batch files *SHOULD* address the issue.

Comments are closed.