nnmbackupembdb.ovpl — make a full backup of the NNMi embedded database.
Use the nnmbackupembdb.ovpl script to make a full backup of the NNMi embedded database. The contents
of the backup are uncompressed and stored in a file you specify. This file must be used to restore the NNMi embedded database by using the
nnmrestoreembdb.ovpl script.
If you plan to use the nnmbackupembdb.ovpl script to create a backup
of the NNMi embedded database, then use the nnmrestoreembdb.ovpl script to place embedded database
records on a second NNMi management server, both NNMi management servers must have the same type of operating system and NNMi version and
patch level.
Before running the nnmbackupembdb.ovpl script, make sure you have adequate storage space in the target
directory. Look for the embedded database data storage in the %NNM_DATA%\shared\nnm\databases\Postgres (Windows)
or $NNM_DATA/shared/nnm/databases/Postgres (UNIX) directory. Check the size of this directory to make sure the
target directory has sufficient space to store the backup file. Compress the file after backup if necessary.
The backup file is created in the target directory and contains all data stored in the database at the start of the backup operation. Any statements run in the database while the backup is running are not included in the backup.
You can run this script while NNMi is running; however, you may experience temporary performance degradation. At a minimum,
the nmsdbmgr process must be running for the script to be successful. If you use the
-force option, the script starts the nmsdbmgr process (if it is not
running), and suppresses any interactive messages.
You must be logged in as administrator on Windows systems or root on UNIX systems to run this script.
-noTimeStamp
With this option, the nnmbackupembdb.ovpl script
stores the backup files in a target directory without a timestamp in the name, i.e. just "nnm-bak".
Any previous backup which exists with that same folder/file name will be renamed to have ".previous" suffix.
If there is already a ".previous" backup, it will be deleted.
This option is provided to allow for daily backups, keeping latest two successful backups, and
not keeping every backup that has been performed, over time, to reduce disk usage.
-target <directory>
Directory name in which to store the backup file. (Will be created if it does not exist)
-force
If you provide this option, the script starts the nmsdbmgr process if it is not currently
running.
-?|-h|-help
Display command usage.
You can use this script to run an on-demand backup, or you can include running the script as a task in regularly scheduled backup scripts. Run the script as follows:
# nnmbackupembdb.ovpl -target /backups/nnm
You'll see these messages:
WARNING: Running this command while NNM is running, while allowed, will cause
temporary performance problems. At a minimum, please make sure the
nmsdbmgr process is running (ovstart nmsdbmgr).
Are you sure you want to run a full database backup now? [n] y
Ok, performing full embedded database backup...
NNM embedded database successfully backed up to /backups/nnm/nnm-bak.2009092906.pgd.
#