How do I back up the NFM-P log and configuration files?

Process

Perform this procedure to save a copy of the NFM-P installation log and configuration files for later analysis in the event of a failure.

Note: During a system restart, NFM-P log files are backed up to directories that are named using a timestamp. A component that runs for a long time can generate multiple log files. Before you restart an NFM-P component, ensure that there is sufficient disk space to store the backed-up log files.

Steps
 

Copy the following files from the /tmp directory on a RHEL station, or from the installation_directory\client directory on a Windows client station:

  • NFM-P_component_stderr.txt

  • NFM-P_component_stdout.txt.

where component is the NFM-P component type, for example, Main_Server, Main_Database, or Client


Copy the following file from each GUI client station; rename each file to indicate the client station from which it is copied:

  • installation_directory/nms/config/nms-client.xml


Copy the following file from each main database station:

  • /opt/nsp/nfmp/db/install/config/dbconfig.properties


Copy the following files from each main server station.

  • /opt/nsp/nfmp/server/nms/config/nms-server.xml

  • all log files in the /opt/nsp/nfmp/server/nms/log/server directory

  • all log files in the /opt/nsp/nfmp/server/nms/log/jmsserver directory

When an NFM-P log file reaches a predetermined size, the NFM-P closes, compresses, and renames the file by including a sequence number and a timestamp. The following is an example of the filename format:

EmsServer.#.timestamp.log

where

# is a sequence number; the sequence begins at 0

timestamp is the log closure time, in the following format: YYYY-MM-DD_hh-mm-ss


Copy the following file from each auxiliary server station:

  • /opt/nsp/nfmp/auxserver/nms/config/nms-auxserver.xml


Transfer the files to a secure location that is not in the network management domain.

End of steps