Go to main content

Oracle® Solaris Cluster Data Replication Guide for ZFS Snapshots

Exit Print View

Updated: October 2018
 
 

Debugging an Oracle Solaris ZFS Snapshot Protection Group

If you encounter problems when creating a protection group and replication component, modifying a replication component, or replicating a protection group with the geopg get command, you can set the SET_DEBUG property of the /opt/ORCLscgrepzfssnap/etc/config file to run trace logs. These logs will display on the terminal.

If you encounter problems with the Oracle Solaris ZFS snapshot agent or the status resources after the replication configuration is setup, then you can enable debugging directly on the resources by setting the Debug_level property of the appropriate resource with the clresource set command. Debug messages will be displayed according to the level value. The ORCL.ZFSSnapRepAgent and ORCL.ZFSSnapRepStatus resource types follow this kind of debugging control.

# clresource set -p Debug_level=N zfssnap-replication-resource

The following values are valid for the Debug_level properties:

0

No debug messages

1

Logs debug messages into syslog about the Begin and End of functions

2

Logs all debug messages to syslog and directs KSH tracing output to console

3

Logs all debug messages to the trace log file

Additionally, each resource of type ORCL.ZFSSnapRepAgent and ORCL.ZFSSnapRepStatus logs important messages into the trace log file and resource log file.

Trace Log File

A trace log file logs all important messages showing a resource's work progress. Such trace messages are logged irrespective of the Debug_level of the resource, thereby ensuring that critical messages about resource's execution are always logged and stored.

A resource of type ORCL.ZFSSnapRepAgent logs messages about replication activities, such as finding common base snapshot, taking snapshots, and sending and receiving snapshot streams. A resource of type ORCL.ZFSSnapRepStatus logs messages about the actions to query and report replication status.

The location of the trace log file on a cluster node is /var/cluster/logs/DS/Resource_Type/message_log.resource_name. For example, the location of the trace log file for the resource rs1 of ORCL.ZFSSnapRepAgent type is /var/cluster/logs/DS/ORCL.ZFSSnapRepAgent/message_log.rs1. The location of the trace log file for the resource rs2 of the ORCL.ZFSSnapRepStatus type is /var/cluster/logs/DS/ORCL.ZFSSnapRepStatus/message_log.rs2.


Note -  The trace log files and resource log files are log-rotated by logadm.

Resource Log File

A resource creates a log file to display the status of any command that is executed by the resource. You can examine the log file to check the errors encountered by a command and the possible cause of failure. The location of the resource log file on a cluster node is /var/cluster/logs/DS/Resource_Type/resource_log.resource_name. You must examine the resource log file for run-time errors, in addition to syslog and console messages. If you require more information, examine the trace log file.

For example, the location of the resource log file for the resource rs1 of the ORCL.ZFSSnapRepAgent type is /var/cluster/logs/DS/ORCL.ZFSSnapRepAgent/resource_log.rs1. The location of the resource log file for the resource rs2 of the ORCL.ZFSSnapRepStatus type is /var/cluster/logs/DS/ORCL.ZFSSnapRepStatus/resource_log.rs2.