The disk space management mechanism in ACS 5.5 manages the system automatically and configures the available file volumes on the file system per file type, such as local store, logs, configuration, cache, and so on. The actual file size limits are calculated at the time of installation, based on the hard coded relative disk quota configuration (percent based), using the disk size as an input. However, ACS database logs have a fixed size. ACS 5.5 gets installed with a variable hard disk size between 60 GB and 750 GB, based on the disk size that was chosen while creating the VMware instance. If you want to change the size of the ACS disk after the installation, complete the following procedure:
- Back up your data.
- Reimage the ACS application or install a fresh application.
- Restore the backed up data.
While restoring the backed up data, a warning message is displayed when the backup size or ACS view database size exceeds the corresponding disk quota. However, the restore operation will not be interrupted. The restore operation fails only when the hard limit of /opt partition size is reached.
In ACS 5.5, the log collector server can be installed on a 60 GB disk space. An ACS view log collector node usually requires more space to maintain a database of logs and reports. Therefore, the recommended disk size for the secondary instance, which acts as a log collector server, is 500 GB.
When you allocate 60 GB for the log collector server, the view database gets only 5.6 GB as total disk space. As a result of this, some of the functionalities may not work properly. The functionalities that may be affected are backup, full backup, incremental backup, logging recovery, purge, database compress operation, and so on.
While creating the VMware instances, ensure that the resources allocated for VMware instances with respect to CPU cores, RAM, and disk, are not more than the actual physical resources of the VMware host server. For example, if the VMware host server has a total of 10 CPU cores, then the sum of the allocated CPU cores for all the VMware instances that are created on that server should not exceed 10.
http://www.cisco.com/c/en/us/td/docs/net_mgmt/cisco_secure_access_control_system/5-5/installation/guide/csacs_book/csacs_vmware.html#87424
