To configure a probe-based backup, you must configure the required NetWorker Probe, Group, and Client resources and complete the scheduled backup configuration.
Note
For MySQL probe-based backups, NMDA supports only user-defined probes, not the NMDA probe implemented through the nsrdaprobe program.
Procedure
1. Create a separate NetWorker Probe resource for the nsrdaprobe program and any other script or program that checks for a user-defined condition.
Set the Probe resource attributes as described in the following table.
NOTICE
Create a separate NetWorker Probe resource for each database that the nsrdaprobe program will probe.
Table 14 NetWorker Probe resource attributes Attribute Description
Name Specify a name to identify the Probe resource. Each Probe resource must have a unique name, which does not have to be the same as the probe script or program name.
Probe Command
Specify the name of the probe script or program that checks (“probes”) for the condition that triggers a probe-based backup. Specify nsrdaprobe to use the NMDA probe, or specify the user-created script or program.
Command Options
Required for the nsrdaprobe program only. Specify a comma-separated list of parameters with their settings.
Command Options settings for the nsrdaprobe program on page 106 describes the possible parameter settings.
Parameter Type of client Description
DBA_DISK_BACKUP Oracle Optional. Set to TRUE if both of the following conditions are true on the Oracle client:
l A backup administrator has used the wizard to configure NMDA scheduled backups of Oracle disk backups of the database.
l You want nsrdaprobe to check if any new Oracle disk backups have been created for the database since the last successful probe-based backup.
With DBA_DISK_BACKUP=TRUE, if the probe finds any new Oracle disk backups and no Oracle disk backup is currently running for the database, the probe triggers an NMDA scheduled backup of the new disk backups.
Note
Do not set DBA_DISK_BACKUP in the same Probe resource as LOG_THRESHOLD.
LOG_THRESHOLD DB2, Informix, Oracle
Mandatory unless DBA_DISK_BACKUP=TRUE is set for an Oracle client. Specify the change threshold, which is the minimum number of logs required to trigger a new probe-based backup.
Configuring a probe-based backup 103
Table 14 NetWorker Probe resource attributes (continued) Attribute Description
Note
Do not set LOG_THRESHOLD in the same Probe resource as DBA_DISK_BACKUP.
Lotus Mandatory. Specify the change threshold, which is the minimum size in KB of Lotus Domino transaction logs required to trigger a new probe-based backup.
NOTICE
For Lotus circular and linear transaction logging, the change threshold value must be sufficiently smaller than the value specified by “Maximum log space” in the Domino server “Transactional Logging” configuration. This requirement ensures that a probe-based backup is triggered before the transaction log size exceeds the maximum log space value and causes transaction logs to be overwritten.
Sybase Mandatory. Specify the change threshold, which is the minimum number of Sybase transaction log pages required to trigger a new probe-based backup.
LOTUS_NSF_FILE Lotus Recommended. Specify the full pathname of a Domino database file used for transaction log querying. The specified database file can be any file backed up by the associated scheduled backup.
If you do not set this parameter, the default value used is admin4.nsf in the Lotus data directory (UNIX) or C:\Program Files\IBM\Lotus\Domino\data\admin4.nsf (Windows).
NSR_DEBUG_LEVEL All Optional. Specify the level of debug information generated by the probe and written to the debug log. NSR_DEBUG_LEVEL on page 361 describes debug levels.
NSR_DIAGNOSTIC_
DEST
All Optional. Specify the directory location of the NMDA debug logs, including the debug logs generated by the probe. NSR_DIAGNOSTIC_DEST on page 364 provides details.
Command Options
Parameter Type of client Description NSR_ORACLE_
CONNECT_FILE
Oracle Optional. Set if both of the following conditions are true:
l You have not configured the Client resource with the wizard.
l You have not set up the NWORA resource file with the Oracle home and database connection information.
Specify the pathname of the RMAN connection file, which contains the connection strings required to connect to the Oracle database.
Command Options settings for the nsrdaprobe program on page 106 provides a sample setting of this parameter.
ORACLE_SERVICE Oracle Optional. Set if both of the following conditions are true:
l You have not configured the Client resource with the wizard.
l You have set up the NWORA resource file with the Oracle home and database connection information by using the command nsroraadmin –r add sid=Net_service_name home=Oracle_home connect=connect_filepath.
Configuring the NWORA resource file with the nsroraadmin program on page 332 describes the nsroraadmin command.
Table 14 NetWorker Probe resource attributes (continued) Attribute Description
Specify the Net service name for the Oracle database. The ORACLE_SERVICE setting must be the same as the NSR_ORACLE_SID setting in the NWORA resource file.
Command Options settings for the nsrdaprobe program on page 106 provides a sample setting of this parameter.
At the end of a successful probe-based backup, the nsrdaprobe program stores information about the current transaction log and some other database information in the State attribute of the Probe resource. User-defined probes do not use the State attribute. The State attribute is visible only in diagnostic mode.
2. Configure the NetWorker Group resource for a probe-enabled backup group. Set the probe-specific attributes in the Group resource, as described in the EMC NetWorker Administration Guide (the information about creating and scheduling a probe group).
When you enable probing through the Group resource attributes, each probe runs once when the probe interval is reached, which is the time window defined by the Probe Start Time and Probe End Time attributes. A probe-based backup ignores the group’s Start Time attribute.
Note
If you start a probe-enabled backup group manually, probing occurs immediately (only once, not repeatedly at intervals) and the backup starts only if the probe conditions are met.
3. Configure the scheduled backup with or without the wizard:
l Configuring scheduled backups with the wizard on page 78
l Configuring scheduled backups without the wizard on page 81 In addition, in the Client resource:
l For the Probe attribute, specify the name of the Probe resource from step 1 on page 103.
You can associate a Client resource with only one probe.
Note
The configuration wizard does not display the Probe field. If you configure a Client resource with the wizard, you must then use NMC to edit the Client resource and set the Probe attribute.
l For the Group attribute, specify the probe-enabled group from step 2 on page 105.
Note
A probe-based backup group must include at least one probe-enabled client, which is a Client resource associated with a probe.
Configuring a probe-based backup 105