Probe-based / Event Based Backup – Oracle

Probe-based backup:
Type of scheduled backup where the NetWorker server initiates the backup only when certain conditions are met, as determined by one or more probes. An alternate term for probe-based backup is event-based backup. The backup of the group is triggered by the successful execution of one or more user-defined client probes (scripts or programs) that are associated with the group. The NetWorker server schedules probe-based backups that are based on user-defined events for clients and NetWorker modules, in addition to time-based events.

To run probe-based backups, perform the following tasks:

1. Create a user-defined client probe.

2. Associate a probe with a Client resource.

3. Create a probe group.

4. Run the probe group the same as you would a save group.

NOTE: Running the savegrp program with the -g attribute bypasses probing when running a probe group backup from the command line.

Creating a client probe:

Users are responsible for creating and supporting user defined probes.

To create a client probe:

1. Type the name, and path of the probe script in the Command: field. The probe resource script must be placed in the same directory as the nsr binaries for each client referencing the probe. For example, /usr/sbin on Solaris and Linux.

Note: The probe script name must begin with save, or nsr.

2. Associate the probe with a Client resource as shown:

Note: The Command Options: field is applies to NetWorker Module probes only.

Probe Group:

Probe-based backup groups specify probe interval, and backup window to schedule the group. Probing occurs continuously throughout the probing window (the hours defined Probe start time, and Probe end time), and only when the Autostart attribute of the save group is enabled. If a save group is started manually, probes run immediately. If autostart is used, then probes only run during the specified probe window.

Clients are associated with probe-based backup groups in the same manner as they are with regular backup groups. However probe-based backup groups must include at least one client which references a probe resource as described in Each client can reference only one probe but, since backup groups can contain many clients, multiple probes can be run with the group.

Instead of a start time, the probe start and end times are used to schedule the group. It is the outcome of the probing which determines if the backup will proceed. Note: Each client in a group can have a probe associated with it, but a probe is not required. However, a probe-based backup group must have at least one probe-enabled client associated with it.

NMDA supports two types of probes, an NMDA probe and user-defined probes:

– An NMDA probe is implemented through the nsrdaprobe program, which determines the amount of logs generated since the previous backup. The probe-based backup runs when that amount is equal to or exceeds the user-configured log threshold.

– A user-defined probe checks if any user-defined condition has been met since the previous backup.

Configuring optional probe-base d backups of DBA disk backups:

You can optionally configure probe-based backups that detect any new Oracle disk backups and trigger the corresponding NetWorker backups by using NMDA. The probe-based backups enable the automatic synchronization of the Oracle disk backup

schedule to the FRA and the NetWorker backup schedule. To configure a probe-based backup, you must complete the required NetWorker Probe, Group, and Client resource configurations.

1. Create a separate NetWorker Probe resource and set the Probe resource attributes as described in the following table.

NOTE: Create a separate NetWorker Probe resource for each database in the backup.

2. Use NMC to 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. Use NMC to edit the NetWorker Client resource:

• Set the Probe attribute to the name of the Probe resource from step 1 . You can associate a Client resource with only one probe.

• Set the Group attribute to the probe-enabled group from step 2 .

Note:A probe-based backup group must include at least one probe-enabled client, which is a Client resource associated with a probe.

NMDA probe:

The NMDA nsrdaprobe program checks for one of the following conditions for the database or application:

◆ For DB2, Informix, or Oracle, the nsrdaprobe program checks for the number of logs generated since the last probe-based backup.

◆ For Lotus, the nsrdaprobe program checks for the size of Domino transaction logs generated since the last backup of the Domino database specified by LOTUS_NSF_FILE in the NetWorker Probe resource.

◆ For Sybase, the nsrdaprobe program checks for the number of transaction log pages generated since the last probe-based backup.

Configuring probe-based backups:

Note:NMDA supports probe-based backups of Oracle disk backups in addition to regular Oracle data. NMDA does not support probe-based backups of MySQL data.Before you configure a probe-based backup, ensure that you have installed the required

NetWorker releases, as described in the EMC NetWorker Module for Databases and Applications Release Notes. An NMDA probe-based backup starts when both of these conditions are true:

◆ (Condition 1) The current time is within a specified window of time (the backup window, as defined by the probe start time and probe end time in the probe-enabled backup group resource).

◆ The backup meets one of the following conditions:

• (Condition 2) A specified amount of time has elapsed since the previous probe-based backup.

• (Condition 3) One or all of the probes associated with the backup are successful, depending on the probe success criteria specified in the backup configuration.You can set the probe success criteria in the NetWorker Group resource to the value Any or All.

Advertisements

About Ahmad Sabry ElGendi

https://www.linkedin.com/pub/ahmad-elgendi/94/223/559
This entry was posted in E20-597. Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s