Trial partitioning requirements, NFM-P components

Trial collocated main server and database partitioning scheme

The following table lists the partitions required for the trial deployment of a collocated main database and main server.

Table 2-8: Trial partitioning scheme, collocated main server and database

Disks required: Physical deployment—two 300 Gbyte (RAID 0) qcow deployment— minimum of 480 Gbytes, plus calculated /opt/nsp/nfmp/nebackup partition size
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 data	6
/var/log/audit	System data	6
/opt/nsp	NSP and NFM-P software, operating data	75
/opt/nsp/nfmp/dbbackup	Database backups	35
/opt/nsp/nfmp/nebackup	NE configuration backups	Network-specific ¹
/opt/nsp/nfmp/db	Database tablespaces	90
/opt/nsp/nfmp/db/archivelog	Database archive logs	35
/opt/nsp/nfmp/server/nms/log	NFM-P server logs	15
/opt/nsp/nfmp/server/xml_output	Output of XML API file export operations	10
/opt/nsp/os	NSP system files	40
/extra	NSP and NFM-P software storage	50

Notes:

Derived using the formula in Sizing the NFM-P NE backup partition

Trial distributed main server partitioning scheme

The following table lists the partitions required for the trial deployment of a main server in a distributed NFM-P system.

Table 2-9: Trial partitioning scheme, main server, distributed system

Disks required: one 300 Gbyte, two 300 Gbyte, or one 600 Gbyte
Partition	Content	Size (Gbytes)
Partition	Content	One 300 Gbyte disk	Two 300 Gbyte or one 600 Gbyte disk
swap	Swap space	16
/	Root	26
/home	User home directories	0.5
/tmp	Temporary files	4
/var	System data	14 ¹	64
/var/log	System logs	6
/var/log/audit	System audit logs	6
/opt/nsp	Main server software, operating data	70
/opt/nsp/nfmp/nebackup	NE configuration backups	Network-specific ²
/opt/nsp/nfmp/server/nms/log	NFM-P server logs	15
/opt/nsp/nfmp/server/xml_output	Output of XML API file export operations	10
/opt/nsp/os	NSP system files	40
/extra	NSP and NFM-P software storage	50

Notes:

Insufficient capacity for application core files
Derived using the formula in Sizing the NFM-P NE backup partition

Trial distributed main database partitioning scheme

The following table lists the partitions required for the trial deployment of a main database in a distributed NFM-P system.

Table 2-10: Trial partitioning scheme, main database, distributed system

Disks required: two 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/nfmp	Main database software	40
/opt/nsp/nfmp/dbbackup	Database backups	40
/opt/nsp/nfmp/db	Database tablespaces	100
/opt/nsp/nfmp/db/archivelog	Database archive logs	40
/opt/nsp/nfmp/db/redolog	Database redo logs	8
/extra	NSP and NFM-P software storage	50

Trial auxiliary server partitioning scheme

The following table lists the partitions required for the trial deployment of an auxiliary server.

Table 2-11: Trial partitioning scheme, auxiliary server

Disks required: one 300 Gbyte, two 300 Gbyte, or one 600 Gbyte		Size (Gbytes)
Partition	Content	One 300 Gbyte disk	Two 300 Gbyte or one 600 Gbyte disk
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	NFM-P server software, operating data	40	90
/opt/nsp/nfmp/auxserver/nms/log	NFM-P server logs	20	30
/opt/nsp/nfmp/auxserver/xml_output	Output of XML API file export operations	20	30
/extra	NSP and NFM-P software storage	50

Trial auxiliary database partitioning scheme

The following table lists the partitions required for the trial 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:
- station 1:
  
  remote_host:station_1_backup_volume_path/opt/nsp/nfmp/auxdb/backup
- station 2:
  
  remote_host:station_2_backup_volume_path/opt/nsp/nfmp/auxdb/backup
- station 3:
  
  remote_host:station_3_backup_volume_path/opt/nsp/nfmp/auxdb/backup
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-12: Trial partitioning scheme, auxiliary database

Disks required: two 300 Gbyte (RAID 0)
Partition	Content	Size (Gbytes)
swap	Swap space	16
/	Root	26
/home	User home directories	0.5
/opt	NFM-P auxiliary database software	49
/tmp	Temporary files	4
/var	System data	64
/var/log	System logs	6
/var/log/audit	System audit logs	6
/opt/nsp/nfmp/auxdb/data	Auxiliary database data	335
/extra	NSP and NFM-P software storage	50
Required additional storage
/opt/nsp/nfmp/auxdb/backup	Auxiliary database backup data	Equal to /opt/nsp/nfmp/auxdb/data

Trial single-user client or client delegate server partitioning scheme

The following table lists the partitions required for the trial deployment of a single-user client or client delegate server on RHEL.

Table 2-13: Trial partitioning scheme, single-user client or client delegate server

Disks required: one 300 Gbyte or larger
Partition	Content	Size (Gbytes)
—	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