Scale up deployments focus on single resource domain in terms of computational power. Scale of the system is achieved by increasing the existing CPU power or adding more memory to a single server. This is the simplest and highest performing type of installation.
Scale up deployments can be converted to Scale Out by adding additional servers to the landscape.
The following volumes and size recommendations are created and mounted before installation:
|
Volume |
Size |
Purpose |
|---|---|---|
|
Installation |
Installation size = Minimum 1 x RAM |
Contains run-time binaries, installation scripts and other support scripts. This also contains the SAP HANA configuration files, trace files and profiles. |
|
Backups |
Backup size = (Size of Data + Size of Redo Log) x retention period |
Regularly scheduled backups are written to this location. |
|
Data |
Data size = 1 x Amount of RAM |
SAP HANA persists a copy of the in-memory data to this location. This is achieved by writing changed data in the form of savepoints. |
|
Redo Log |
For systems <512GB, Redo Log size = 1/2 RAM For systems >512GB Redo Log size = 512GB or larger |
Each transaction performed on the database is recorded to this location in the form of a redo log entry. |
Block based volumes on FlashArray are provided with a capacity limit at creation.
File services based directories must have a Quota Policy applied to restrict capacity use.
Below is an example of a 6 Terabyte capacity limit applied in the graphical user interface to all of the directories for a scale up instance :