The individual Components | The Backup Component |
The shell script saveinfo.sh in the directory $NSR_INST/oracle/bin evaluates the protocol files save*.prot in the subdirectory tablespaces and tells you the status, the start and end of a backup, the type of backup (onlineoffline) and the names and sizes of the backed up tablespaces.
You can call saveinfo.sh at any time, even while there is a backup in progress. It is called automatically when a tablespace backup has been completed and writes its output to the file actual_saves_of_tablespaces. This information is also sent to you by mail.
!saveinfo.sh tool provide you with complete information on the status and success of a backup process.Please note that only the
AMON Recordings
The file /nrs/oracle/${ORACLE_SID}/prot/save_logfiles contains a log of all redolog files backed up by the archiving monitor (see the section “Logging”). The subdi- rectory /nrs/oracle/${ORACLE_SID}/prot/dbg contains debug information, which can be evaluated by Fujitsu Siemens Computers if errors are encountered.
If you want to observe a backup in progress on the screen, you can do so using the command nsrwatch or from the main NetWorker window.
Please note that only the
If you call ora_recut, additional debugging information, which can be evaluated by Fujitsu Siemens Computers specialists if an error occurs, is entered in the directory /nsr/${ORACLE_SID}/tmp/RUT.
!to ensure that all tablespaces occur in at least one backup cycle. If a tablespace does not occur in at least one partial backup interval, it is never saved! Consequently, a configuration tool has been supplied (see the section “Establishing tablespace names”) for supporting this task.
At least one backup process is started for each backup if the attribute Backup Command was set to nsrora_save_cmd for the relevant client in the Clients window. Otherwise, at least two backup processes are started
for each backup - one by NetWorker and one by
System Administrator’s Guide |
