Chat now with support
Chat with Support

NetVault Plug-in for SAP on Oracle 11.4.5 - User Guide

Parameter table

The following table describes options that you can use with an SAP Backint parameter file. These options are used with the “-p” argument in the command syntax, and can be used in either of the following ways:

With the “-p <par_file> command, where <par_file> represents the applicable parameter filename: In this case, you can use a parameter file other than the default.
With the “-p” command alone, without naming a parameter file: In this case, the default parameter file specified in the Configure dialog box is used.

The following table lists the available options, valid entries, and default values used.

IMPORTANT: The equal sign (=) is the only valid separator that you can use with values in a parameter file, for example, “-p client = Client1.” This requirement applies to both the manual entry of the “-p” command from a terminal session and in an existing parameter file; that is, one called out by using the “-p <parameter filename> command or the one established as the default in the Configure dialog box.

Advanced options set

<Advanced options set name>

n/a

auto label media

true | false

TRUE

backup by volume

true | false

TRUE

backup directories

true | false

FALSE

backup job count

<Sort count>

1

Backup Life

<# days|weeks|years>

 

Backup target set

<nameOfBackupTargetSet>

n/a

client

<NetVaultBackupClientName>

n/a

device

<deviceName> [,<device name>[,…]]

<local machine>

dont reuse media

true | false

FALSE

Duplicate

true | false

FALSE

Duplicate schedule set

<setNameOfScheduleSetToBeUsed>

Immediate

Duplicate target set

<setNameOfTargetSetToBeUsed>

Any Device

file online mass open

true | false

FALSE

first on media

true | false

FALSE

Group label

<nameOfTapeGroup>

n/a

max restore jobs

<subjobCount>

1

MID

<tapeLabel>

n/a

Migrate

true | false

FALSE

Migration Life

<# days|weeks|years>

n/a

minimum space on media

<space in MB>

n/a

Network compression

true | false

FALSE

Post script

<nameOfScriptFile>

n/a

Post script args

<userArgumentsForPostscript>

n/a

Pre script

<nameOfScriptFile>

n/a

Pre script args

<userArgumentsForPrescript>

n/a

recurse directories

true | false

FALSE

Restore backup

true | false

FALSE

Restore overwrite

true | false

FALSE

Restore timestamps

true | false

TRUE

reuse media

never | any | by_group

Never

Target client

<nameOfTargetNetVaultBackupClient>

<Local Client>

title

<job title>

Command Line

verify

true | false

FALSE

Note the following information regarding use of parameters:

You only have to enter the “-p” argument once in the command syntax. You can then follow it with as many of the commands listed in the previous table as applicable.
You can issue a Backint command that includes the “-p <parameter filename> argument. In this case, the specified parameter file and its default values are used instead of the file specified in the Configure dialog box.

Input variables

The Input variable used along with the Backint command, that is, whether in a file specified by the “-i <in_file>” option, or using standard input, depends the applicable function, that is, backup, restore, or inquire and is described in the following table:

backup

Full path names of files to back up. One file per line.

inquire

<SSID> [<file>]

<SSID> is either the saveset ID that contains the file, or “#NULL” if all savesets are to be searched.

<file> is the full path name of the file to list. If omitted, the complete contents of the specified saveset are output.

restore

<SSID> <file> [<relocate>]

<SSID> is the saveset ID that contains the file to restore. This was output by Backint at the time the backup was made. You can also determine it by using the “inquire” function, or by using the saveset table on the Create Restore Job page to list the Backint backups. If <SSID> is #NULL, the most recent <file> from the latest saveset is restored.

<file> is the full path name of the file to restored

<relocate> If present, the name of the directory to write the file to. This variable can be used if the original location is no longer available or active.

Output variables

The Output variable is entered along with the Backint command, that is, specified by the “-o <out_file> option or to standard output if not supplied, depends the applicable function, that is, backup, restore, or inquire, and is described in the following table:

backup

<result> <SSID> <filename>

There is one line of the preceding format for each file specified in the input list.

<result> is “#SAVED” if the file was successfully written to the backup, or “#ERROR” if the file could not be written. You can use the View Logs page to determine the reason for the failure.
<SSID> is the saveset ID that the file was written to. If the result was <ERROR>, none is given.
<filename> is the filename, as specified in the input list.

restore

<result> <SSID> <filename>

There is one line of the preceding format for each file specified in the input list.

<result> is “#RESTORED” if the file was successfully restored, or “#ERROR” if the file could not be restored. You can use the View Logs page to determine the reason for the failure.
<SSID> is the saveset ID that the file was written to. If the result was <ERROR>, none is given.
<filename> is the filename, as specified in the input list.

inquire

<result> <SSID> <filename>

There is at least one line of the preceding format for each line of the input list.

<result> is “#BACKUP” for each file on backup matching the requested criteria, or “#NOTFOUND” if no matches were found.
<SSID> is the saveset ID that the file was written to. If the result was <ERROR>, none is given.
<filename>> is the filename, as specified in the input list.

Troubleshooting

This topic describes some common errors and their solutions. If an error occurs that is not described in this table, obtain the SAP Backint error number from the NetVault Backup Logs, and then see the relevant SAP documentation for the resolution.

NetVault Backup 10.x service (netvault-pgsql) does not start on Windows.

Check the Windows Event Viewer for the following message: PDT FATAL: lock file “postmaster.pid” already exists.

NetVault Backup 10.x uses a PostgreSQL database. If the PostgreSQL database does not start, NetVault Backup cannot start. To correct this issue, delete the “postmaster.pid” file from the location referenced in the log and restart the NetVault Backup Server. For more information, see https://support.quest.com/netvault-backup/kb/122475.

These messages indicate that the selected data was backed up, but the job’s index information was not properly added by NetVault Backup to its database. Without this index information, the data cannot be properly restored.

Method 1:

In the Navigation pane, click Explore Storage, select the target media, and click Scan. NetVault Backup stores index information for backup jobs in two locations: in the NetVault Database and on the media targeted by the backup. Performing this scan adds the index information to the NetVault Database. To verify that the information was added, open the saveset table on the Create Restore Job page and locate the specific job. If you can browse it and set up a restore job, the scan process has corrected the problem.

Method 2:

If the previous method failed, run the backup job again.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating