You can simplify the creation of the configuration file for NetWorker if you use the following example and adjust it to suit your needs. If you do not want to set a certain parameter by using the parameter file, you have to invalidate or delete the relevant keyword.
NSR_HOST
p47579
NSR_HOME
"C:\Program Files\nsr\bin"
NSR_POOL
SAPDBPOOL
NSR_EXPIRE
year
NSR_NOTVERBOSE
RECOVER
NSR_EBIDTYPE NSAVETIME
NSR_USEOUTPUT
SAVE
NSR_IGNOREERROR
"unknown error 109 (0x6d)"
NSR_IGNOREERROR
"using unlocked access"
NSR_IGNOREERROR "The
pipe has been ended.”
NSR_SAVEINTERVAL 60
NSR_BACKUPNAME
SAPDB:<database_name>_on_<node>
NSR_AVOIDPSSIDBUG YES
NSR_SAVETIMEFORMAT "yyyy/mm/dd HH:MM:SS AM"
Keyword |
Value |
Explanation |
NSR_HOST |
p47579 |
The NetWorker server is running on server p47579. |
NSR_HOME |
"C:\Program Files\nsr\bin" |
The NetWorker
client is installed on the database server in the directory |
NSR_POOL |
SAPDBPOOL |
Backups are stored in the NetWorker pool SAPDBPOOL. |
NSR_EXPIRE |
year |
The backups have an expiration time of one year. |
NSR_NOTVERBOSE |
RECOVERY |
The NetWorker RECOVER program is run without the -v option. |
NSR_EDITTYPE |
NSAVETIME |
The backup time is used to identify backups. |
NSR_USEOUTPUT |
SAVE |
The output of the NetWorker SAVE program is searched for errors during every backup. |
NSR_IGNOREERROR |
" unknown error 109 (0x6d)" |
The messages |
NSR_SAVEINTERVAL |
60 |
The system waits 60 seconds between two SAVE calls during parallel backups. |
NSR_BACKUPNAME |
SAPDB:<database_name>_on_<node> |
If the name of the database instance is DB72, the backups are created with the name SAPDB:DB72_on_p47579 in NetWorker. |
NSR_AVOIDPSSIDBUG |
YES |
The PSSID bug of the NetWorker MMINFO program is avoided (only for NetWorker as of Version 6.0). |
NSR_SAVETIMEFORMAT |
"yyyy/mm/dd HH:MM:SS AM" |
The NetWorker
MMINFO program delivers date specifications in the specified
format. |