Skip to main content
System Manager Classic

Application-specific LUN settings with System Manager - ONTAP 9.7 and earlier

Contributors netapp-mwallis

ONTAP System Manager classic (available in ONTAP 9.7 and earlier) supports Oracle, SQL, and other application types while creating FC SAN optimized LUNs on an AFF cluster. LUN settings such as the LUN size are determined by rules specific to the application type. For SQL and Oracle, LUN settings are automatically created.

If your cluster contains two or more nodes, System Manager uses only the first two nodes selected by the API to create LUNs. Data aggregates are already created in each of the two nodes. The size of each volume created is equal to the available capacity of the aggregate. The volumes are thin-provisioned and space reservation is disabled on the LUNs.

Storage efficiency policy is enabled by default with the schedule set to “daily” and quality of service (QoS) set to “best_effort”. By default, access time (atime) update is enabled on the cluster. However, access time updates are disabled by System Manager while creating volumes and therefore every time a file is read or written, the access time field in the directory is not updated.

Note

Enabling the access time update causes performance degradation to the data-serving capability of the cluster.

LUN settings for SQL

By default, LUNs and volumes are provisioned for a single instance of the SQL server with 2 databases of 1 TB each and 24 physical cores. Space is provisioned for LUNs and volumes according to specific rules for the SQL server. Load balancing is performed for LUNs across the HA pair. You can modify the number of databases. For each database, eight data LUNs and one log LUN is created. One temporary LUN is created for each SQL instance.

The following table provides information about how space is provisioned for the default values of SQL:

Node Aggregate LUN type Volume name LUN name Formula for LUN size LUN size (GB)

node1

node1_aggr1

data

db01_data01

db01_data01

Database size ÷ 8

125

data

db01_data02

db01_data02

Database size ÷ 8

125

data

db01_data03

db01_data03

Database size ÷ 8

125

data

db01_data04

db01_data04

Database size ÷ 8

125

data

db02_data01

db02_data01

Database size ÷ 8

125

data

db02_data02

db02_data02

Database size ÷ 8

125

data

db02_data03

db02_data03

Database size ÷ 8

125

data

db02_data04

db02_data04

Database size ÷ 8

125

log

db01_log

db01_log

Database size ÷ 20

50

temp

sql_temp

sql_temp

Database size ÷ 3

330

node2

node2_aggr1

data

db01_data05

db01_data05

Database size ÷ 8

125

data

db01_data06

db01_data06

Database size ÷ 8

125

data

db01_data07

db01_data07

Database size ÷ 8

125

data

db01_data08

db01_data08

Database size ÷ 8

125

data

db02_data05

db02_data05

Database size ÷ 8

125

data

db02_data06

db02_data06

Database size ÷ 8

125

data

db02_data07

db02_data07

Database size ÷ 8

125

data

db02_data08

db02_data08

Database size ÷ 8

125

log

db02_log

db02_log

Database size ÷ 20

50

LUN settings for Oracle

By default, LUNs and volumes are provisioned for one database of 2 TB. Space is provisioned for LUNs and volumes according to specific rules for Oracle. By default, Oracle Real Application Clusters (RAC) is not selected.

The following table provides information about how space is provisioned for the default values of Oracle:

Node Aggregate LUN type Volume name LUN name Formula for LUN size LUN size (GB)

node1

node1_aggr1

data

ora_vol01

ora_lundata01

Database size ÷ 8

250

data

ora_vol02

ora_lundata02

Database size ÷ 8

250

data

ora_vol03

ora_lundata03

Database size ÷ 8

250

data

ora_vol04

ora_lundata04

Database size ÷ 8

250

log

ora_vol05

ora_lunlog1

Database size ÷ 40

50

binaries

ora_vol06

ora_orabin1

Database size ÷ 40

50

node2

node2_aggr1

data

ora_vol07

ora_lundata05

Database size ÷ 8

250

data

ora_vol08

ora_lundata06

Database size ÷ 8

250

data

ora_vol09

ora_lundata07

Database size ÷ 8

250

data

ora_vol10

ora_lundata08

Database size ÷ 8

250

log

ora_vol11

ora_lunlog2

Database size ÷ 40

50

For Oracle RAC, LUNs are provisioned for grid files. Only two RAC nodes are supported for Oracle RAC.

The following table provides information about how space is provisioned for the default values of Oracle RAC:

Node Aggregate LUN type Volume name LUN name Formula for LUN size LUN size (GB)

node1

node1_aggr1

data

ora_vol01

ora_lundata01

Database size ÷ 8

250

data

ora_vol02

ora_lundata02

Database size ÷ 8

250

data

ora_vol03

ora_lundata03

Database size ÷ 8

250

data

ora_vol04

ora_lundata04

Database size ÷ 8

250

log

ora_vol05

ora_lunlog1

Database size ÷ 40

50

binaries

ora_vol06

ora_orabin1

Database size ÷ 40

50

grid

ora_vol07

ora_lungrid1

10 GB

10

node2

node2_aggr1

data

ora_vol08

ora_lundata05

Database size ÷ 8

250

data

ora_vol09

ora_lundata06

Database size ÷ 8

250

data

ora_vol10

ora_lundata07

Database size ÷ 8

250

data

ora_vol11

ora_lundata08

Database size ÷ 8

250

log

ora_vol12

ora_lunlog2

Database size ÷ 40

50

binaries

ora_vol13

ora_orabin2

Database size ÷ 40

50

LUN settings for other application type

Each LUN is provisioned in a volume. The space is provisioned in the LUNs based on the specified size. Load balancing is performed across the nodes for all the LUNs.