Live partitioning requirements, NFM-P components
Description
|
CAUTION Service Disruption |
Each disk partition described in this section must be a mounted partition and not a symbolic link.
The NFM-P does not support the use of symbolic links to represent partitions.
The following disk layouts are for a deployment in a live network environment.
Note: See the NSP Planning Guide and the response to your NFM-P Platform Sizing Request for information about the supported disk types.
Note: For each database partitioning scheme, the Oracle management user home directory specified by the ORACLE_HOME environment variable is /opt/nsp/nfmp/oracle19.
Live collocated main server and database partitioning scheme
The following table lists the partitions required for the live deployment of a collocated main database and main server.
Table 2-20: Live partitioning scheme, collocated main server and database
|
Disks required: |
Size (Gbytes) | ||
|---|---|---|---|
|
Partition |
Content |
Physical |
qcow |
|
swap |
Swap space |
16 | |
|
/ |
Root |
26 | |
|
/home |
User home directories |
0.5 | |
|
/tmp |
Temporary files |
4 | |
|
/var |
System data |
64 | |
|
/var/log |
System data |
6 | |
|
/var/log/audit |
System data |
6 | |
|
/opt/nsp |
NSP and NFM-P software, operating data |
150 |
80 |
|
/opt/nsp/nfmp/db |
Main database software, tablespaces |
300 |
200 |
|
/opt/nsp/nfmp/db/archivelog |
Database archive logs |
120 |
70 |
|
/opt/nsp/nfmp/dbbackup |
Main database backup sets |
120 |
70 |
|
/opt/nsp/nfmp/nebackup |
NE configuration backup files |
Network-specific 1 | |
|
/opt/nsp/nfmp/server/nms/log |
NFM-P server logs |
50 |
35 |
|
/opt/nsp/nfmp/server/xml_output |
Output of XML API file export operations |
20 |
10 |
|
/opt/nsp/os |
NSP system files |
90 | |
|
/extra |
NSP and NFM-P software storage |
50 | |
Notes:
Derived using the formula in Sizing the NFM-P NE backup partition
Live distributed main server partitioning scheme
The following table lists the partitions required for the live deployment of a main server in a distributed NFM-P system.
Table 2-21: Live partitioning scheme, main server, distributed system
|
Disks required: two 300 Gbyte (RAID 0), or four 300 Gbyte (RAID 0) | |||
|---|---|---|---|
|
Partition |
Content |
Size (Gbytes) | |
|
Two 300 Gbyte disks |
Four 300 Gbyte disks | ||
|
swap |
Swap space |
16 | |
|
/ |
Root |
26 | |
|
/home |
User home directories |
0.5 | |
|
/tmp |
Temporary files |
4 | |
|
/var |
System data |
64 | |
|
/var/log |
System logs |
6 | |
|
/var/log/audit |
System audit logs |
6 | |
|
/opt/nsp |
Main server software, operating data |
150 | |
|
/opt/nsp/nfmp/nebackup |
NE configuration backups |
Network-specific 1 | |
|
/opt/nsp/nfmp/server/nms/log |
NFM-P server logs |
50 | |
|
/opt/nsp/nfmp/server/xml_output |
Output of XML API file export operations |
20 | |
|
/opt/nsp/os |
NSP system files |
90 |
140 |
|
/extra |
NSP and NFM-P software storage |
50 | |
Notes:
Derived using the formula in Sizing the NFM-P NE backup partition
Live distributed main database partitioning scheme
The following table lists the partitions required for the live deployment of a main database in a distributed NFM-P system.
Table 2-22: Live partitioning scheme, main database, distributed system
|
Disks required: four 300 Gbyte (RAID 0) or six 300 Gbyte (RAID 0) |
Size (Gbytes) | ||
|---|---|---|---|
|
Partition |
Content |
Four disks |
Six disks |
|
swap |
Swap space |
16 | |
|
/ |
Root |
26 | |
|
/home |
User home directories |
0.5 | |
|
/tmp |
Temporary files |
4 | |
|
/var |
System data |
64 | |
|
/var/log |
System logs |
6 | |
|
/var/log/audit |
System audit logs |
6 | |
|
/opt/nsp/nfmp |
Main database software |
120 | |
|
/opt/nsp/nfmp/dbbackup |
Database backups |
120 |
200 |
|
/opt/nsp/nfmp/db |
Database tablespaces |
360 |
500 |
|
/opt/nsp/nfmp/db/archivelog |
Database archive logs |
120 |
570 |
|
/opt/nsp/nfmp/db/redolog |
Database redo logs |
30 | |
|
/extra |
NSP and NFM-P software storage |
50 | |
Live auxiliary server partitioning scheme
The following table lists the partitions required for the live deployment of an auxiliary server.
Table 2-23: Live partitioning scheme, statistics-collection auxiliary server
|
Disks required: four 300 Gbyte (RAID 0) | ||
|---|---|---|
|
Partition |
Content |
Size (Gbytes) |
|
swap |
Swap space |
16 |
|
/ |
Root |
26 |
|
/home |
User home directories |
0.5 |
|
/tmp |
Temporary files |
4 |
|
/var |
System data |
64 |
|
/var/log |
System logs |
6 |
|
/var/log/audit |
System audit logs |
6 |
|
/opt/nsp |
Auxiliary server software, operating data |
180 |
|
/opt/nsp/nfmp/auxserver/nms/log |
Auxiliary server logs |
50 |
|
/opt/nsp/nfmp/auxserver/xml_output |
Output of XML API file export operations |
150 |
|
/extra |
NSP and NFM-P software storage |
50 |
Live auxiliary database partitioning scheme
The following table lists the partitions required for the live deployment of an auxiliary database.
For a multi-station auxiliary database, or a single-station database that has a high data rate, the /opt/nsp/nfmp/auxdb/backup partition has the following special requirements:
-
It is strongly recommended that the partition is a remote mount point or directly attached storage connected by a minimum 10 Gbyte/s link.
-
Each auxiliary database station requires a separate backup volume that is mounted as /opt/nsp/nfmp/auxdb/backup on the auxiliary database station.
For example, if the specified auxiliary database backup location is /opt/nsp/nfmp/auxdb/backup, the auxiliary database stations require the following mount points: -
The supported file systems for the backup location are ext3, ext4, and NFS.
Note: The /opt/nsp/nfmp/auxdb/backup partition can be a local mount point in a single-station database that has a low to moderate data rate.
Table 2-24: Live partitioning scheme, auxiliary database
|
Disks required: two 300 Gbyte (RAID 1), plus data storage and database backup storage capacity described in table |
Size (Gbytes) | ||
|---|---|---|---|
|
Partition |
Content |
Single-station |
Multi-station |
|
swap |
Swap space |
16 | |
|
/ |
Root |
26 | |
|
/home |
User home directories |
0.5 | |
|
/opt |
NFM-P auxiliary database software |
100 | |
|
/tmp |
Temporary files |
4 | |
|
/var |
System data |
64 | |
|
/var/log |
System logs |
6 | |
|
/var/log/audit |
System audit logs |
6 | |
|
/extra |
NSP and NFM-P software storage |
50 | |
|
Data storage disks required, RAID 1+0: |
Four 1.2-Tbyte |
Twelve 600 Gbyte | |
|
/opt/nsp/nfmp/auxdb/data |
Auxiliary database data |
2200 |
3300 |
|
Database backup storage disks required, RAID 5: |
Four 1.2-Tbyte |
Five 1.2-Tbyte | |
|
/opt/nsp/nfmp/auxdb/backup 1 |
Auxiliary database backup data |
3300 |
4400 |
Notes:
Auxiliary database backups are optional but strongly recommended to protect against complete data loss due to disk failure, data corruption, or upgrade failure. The backups can be stored on a separate volume, as indicated in the table above, or on a remote mount point reachable over a minimum 10 Gbyte/s link. The listed capacity is sufficient for at least one persisted backup.
Live single-user client or client delegate server partitioning scheme
The following table lists the partitions required for the live deployment of a single-user client or client delegate server on RHEL.
Table 2-25: Live partitioning scheme, single-user client or client delegate server
|
Disks required: one 300 Gbyte | ||
|---|---|---|
|
Partition |
Content |
Size (Gbytes) |
|
swap |
Swap space |
16 |
|
/ |
Root, including /usr and /var |
26 |
|
/opt/nsp |
NFM-P client software |
16 |
|
At operator discretion |
Customer data; can be partitioned according to customer requirements |
Remainder |