logo

Manual Pages


Table of Contents

NAME

na_snapmirror - Log of SnapMirror Activity

SYNOPSIS

/etc/log/snapmirror

DESCRIPTION

The SnapMirror log file contains a log of SnapMirror activity for this filer. The file lives in /etc/log on the root volume of both the source and destination filers. When the option snapmirror.log.enable is set to on, all the SnapMirror activities will be recorded in this log file. See na_options(1) for details regarding how to enable and disable this option. Every Sunday at 00:00, /etc/log/snapmirror is moved to /etc/log/snapmirror.0, /etc/log/snapmirror.0 is moved to /etc/log/snapmirror.1, and so on. The suffix can go up to 5. This process is called rotation. SnapMirror log entries are saved for a total of six weeks.

Each entry of the /etc/log/snapmirror file is a single line consisting of space-separated fields. All log entries begin with a type field and a timestamp field. The final field may be enclosed by parentheses, in which case it may contain spaces. The timestamp field contains a fixed number of spaces, and as such can be parsed as five space-delimited fields. Which fields appear, and in what order they appear in, is determined by the type field of log entry (which is the first field).

Following is a description of each field.

type Indicate the type of the entry, which also determines the format of the rest of the entry. It can be one of the following values:

log
log facility activity

Format: type timestamp event_info...

sys
system-wide activity

Format: type timestamp event_info...

tgt
snapvault target activity

Format: type timestamp volume target event_info...

src
source activity

Format: type timestamp source destination event_info...

dst
destination activity

Format: type timestamp source destination event_info...

cmd
user command activity

Format: type timestamp source destination event_info...

scn
replication check source activity

Format: type timestamp source destination event_info...

chk
replication check destination activity.

Format: type timestamp source destination event_info...

vol
volume-wide activity

Format: type timestamp volume event_info...

slk
softlock addition-deletion activity

Format: type timestamp softlock event_info...

timestamp
Displayed in ctime() format, e.g. Fri Jul 17 20:41:09 GMT. Indicates the time this event is recorded.

volume Specifies the name of the volume to which this entry applies.

target This is the name and type of the target for this entry. Targets are volume-wide actions, typically snapshot creations. It is displayed as two colonseparated fields, as follows:

target_type:target_name

The target name may be an empty string.

source This is the name of the source filer and the volume name or qtree path to be mirrored. The name is specified as two colon-separated fields, as follows:

host:path

This field may be `-' when not applicable for the event.

destination
This is the name of the destination filer and the volume name or qtree path of the destination. The name is specified as two colon-separated fields, same as in the source field.

This field may be `-' when not applicable for the event.

event_info
This field contains the event which is being logged. Some events may have extra information in parentheses.

Request (IP address | transfer type) A transfer request has been sent (destination) or received (source). On source side, the IP address of the destination filer that made the request is included in parentheses. On destination side, the transfer type is included in the parentheses.

Start The beginning of a transfer.

Start (Snapshots to check=#num, level={data|checksum}, {check|fix}, {quick|full} mode)
The beginning of a replication check or fix session. The session options are included in the parentheses. All options appear on the destination side log but only the "snapshots to check" option appears in source side log.

Restart (@ num KB)
The beginning of a restarted transfer.

End (num KB done)
The completion of a transfer. The total size of the transfer in KB is included in the parentheses.

End (src_only=num_1, dst_only=num_2, mismatch=num_3) The completion of a replication check or fix session. The summary of the session is included in the parentheses. The summary is present only on the destination side logs. Source side logs will not contain any summary information.

Abort (error msg)
A transfer is aborted. The error message is included in the parentheses.

Defer (reason)
Indicates a transfer is deferred because of a resource limitation. The reason for the deferment is included in the parentheses.

Wait_tape
A SnapMirror tape operation is waiting for next tape.

New_tape
A SnapMirror tape operation continued the operation with the new tape.

Sync_start
The start of synchronous mirroring mode for the SnapMirror relationship specified by this log entry.

Sync_end (reason)
The end of synchronous mirroring mode for the SnapMirror relationship specified by this log entry. The reason for dropping out of synchronous mode is included in the parentheses.

Quiesce_start
The beginning of quiesce process.

Quiesce_end
The completion of quiesce process.

Quiesce_failed (reason)
The failure of quiesce process. The reason for failure is included in the parentheses.

Rollback_start
The beginning of a rollback process for a qtree SnapMirror or SnapVault.

Rollback_end
The completion of a rollback process for a qtree SnapMirror or SnapVault.

Rollback_failed (reason)
The failure of a rollback process for a qtree SnapMirror or SnapVault. The reason for failure is included in the parentheses.

Coalesce_start (snapshot)
The beginning of a coalesce process for a SnapVault qtree. The base snapshot for the coalesce operation is included in the parentheses.

Coalesce_end
The completion of a coalesce process for a SnapVault qtree.

Coalesce_failed (reason)
The failure of a coalesce process for a SnapVault qtree. The reason for failure is included in the parentheses.

Target_start
The beginning of a SnapVault target.

Target_end
The completion of a SnapVault target.

Target_failed (reason)
The failure of a SnapVault target. The reason for failure is included in the parentheses.

Start_logging
SnapMirror log was enabled.

End_logging
SnapMirror log was disabled.

SnapMirror_on (cause)
SnapMirror was enabled on this host. The operation or process that caused SnapMirror to become enabled is specified in the parentheses.

SnapMirror_off (cause)
SnapMirror was disabled on this host. The operation or process that caused SnapMirror to become disabled is specified in the parentheses.

SnapVault_on (cause)
SnapVault was enabled on this host. The operation or process that caused SnapVault to become enabled is specified in the parentheses.

SnapVault_off (cause)
SnapVault was disabled on this host. The operation or process that caused SnapVault to become disabled is specified in the parentheses.

Resume_command
User issued snapmirror resume command.

Break_command
User issued snapmirror break command.

Release_command
User issued snapmirror release command.

Abort_command

Abort_command (type)
User issued snapmirror abort command. The type will only be present if the abort was issued with additional options which changed the type of the abort.

Resync_command (common snapshot)
User issued snapmirror resync command. The common snapshot for the resync operation is included in the parentheses.

Restore_resync_command (common snapshot) User issued snapvault restore -r command. The common snapshot for the resync operation is included in the parentheses.

Migrate_command
User issued snapmirror migrate command.

Request_check (snapshot_name)
A request for single snapshot during replication check session. This is source side log entry. Each snapshot being checked in a replication check session will have its entry. Name of snapshot is included in the parentheses.

Checking_snapshot source snapshot_name (timestamp, cpcount=num_2, snapid=id) to dest_snapshot_name (timestamp, cpcount=count, snapid=id) The beginning of a single snapshot comparison during replication check. It is logged on both source and destination.

Abort_check
replication check session for SnapMirror or SnapVault aborted. Reason of abort is included in the parentheses.

Abort_check_command
User issued replication check abort command. Corresponding log file entry appears with cmd type.

Data_differ ({block blk_num in file_path | VBN vbn})
Replication check found a data block mismatch. Either the block number and the inode path or Volume Block Number (VBN) is included in the parentheses.

Unique_in_src (entry_type for entry_path) Replication check found an entry only present in the source. The entry type and entry path are included in the parentheses.

Unique_in_dst (entry_type for entry_path) Replication check found an entry only present in the destination. The entry type and entry path are included in the parentheses.

Size_differ (path)
Replication check found a file size mismatch in specified inode. The inode path is included in the parentheses.

Type_differ (path)
Replication check found a inode type mismatch. The inode path is included in the parentheses.

UID_differ (path)
Replication check found a user ID mismatch for specified inode. The inode path is included in the parentheses.

GID_differ (path)
Replication check found a group ID mismatch for specified inode. The inode path is included in the parentheses.

Perm_differ (path)
Replication check found a permission or dosbit mismatch for specified inode. The inode path is included in the parentheses.

Atime_differ (path)
Replication check found a mismatch in the last access time for specified inode. The inode path is included in the parentheses.

Mtime_differ (path)
Replication check found a mismatch in the last modification time for specified inode. The inode path is included in the parentheses.

Ctime_differ (path)
Replication check found a mismatch in the last size/status change time for specified inode. The inode path is included in the parentheses.

Crtime_differ (path)
Replication check found a mismatch in the creation time for specified inode. The inode path is included in the parentheses.

Rdev_differ (path)
Replication check found a device number mismatch for specified inode. The inode path is included in the parentheses.

DOSbits_differ (path)
Replication check found a DOS bits mismatch for specified inode. The inode path is included in the parentheses.

ACL_differ (path)
Replication check found an NT or NFS V4 ACL mismatch for specified inode. The inode path is included in the parentheses.

Hardlink_differ (path)
Replication check found a hardlink for specified inode, but the inode on destination doesn't match between the links. The inode path is included in the parentheses.

Qtree_oplock_differ (path)
Replication check found oplock setting mismatch for a qtree. The qtree path is included in the parentheses.

Qtree_security_differ (path)
Replication check found security setting mismatch for a qtree. The qtree path is included in the parentheses.

Hole_uses_disk_space (path)
Replication check found unnecessary disk usage for specified inode, this however is not a mismatch. The inode path is included in the parentheses.

Convert_command
User issued snapmirror convert command.

Older_snapshot
Updating from a snapshot which is older than the current base snapshot.

Snapshot_delete (snapshot name)
A snapshot is deleted from this volume. The snapshot name is included in the parentheses.

Snapshot_replace (snapshot name)
A SnapVault snapshot has been replaced after a SIS operation with a newer snapshot of the same name. The snapshot name is included in the parentheses.

FILER_REBOOTED
The filer is rebooted.

WORM_LOG_FAIL (reason)
Write to WORM log file failed. The reason for failure is included in the parentheses.

WORM_LOG_FAILURE_RECOVER_START
The beginning of the recovery of the failed WORM log entries.

WORM_LOG_FAILURE_RECOVER_END
The end of the recovery of the failed WORM log entries.

Softlock_add (operation)
A softlock is added. The operation that added the softlock is included in the parentheses.

Softlock_add_pending (operation)
A softlock is added as a pending softlock. The operation that added the softlock is included in the parentheses.

Softlock_delete (operation)
A softlock is deleted. The operation that deleted the softlock is included in the parentheses.

Softlock_delete_pending (operation) A pending softlock is deleted. The operation that deleted it is included in the parentheses.

Softlock_mark_pending (operation)
A softlock is marked as pending. The operation that marked it is included in the parentheses.

EXAMPLES

A typical entry in /etc/log/snapmirror looks like:
  dst Fri Jul 17 22:50:18 GMT filer1:srcvol filer2:dstvol Request (Update)

The above example shows an update request recorded by the destination side for a SnapMirror relationship from filer:srcvol to filer2:dstvol that happened at the recorded time.

A typical Replication check session in /etc/log/snapmirror on destination looks like:

  chk Wed Jan 19 01:07:39 GMT woolf:/vol/vol1 milton:/vol/vol1 Request (check)
  chk Wed Jan 19 01:07:39 GMT woolf:/vol/vol1 milton:/vol/vol1 Start (Snapshots to check = 2, level= data, check, full)
  chk Wed Jan 19 01:07:39 GMT woolf:/vol/vol1 milton:/vol/vol1 Checking_snapshot milton(0033587346)_vol1.5 (Jan 18...
  chk Wed Jan 19 01:07:48 GMT woolf:/vol/vol1 milton:/vol/vol1 Checking_snapshot nightly.0 (Jan 18 00:00, cpcount =...
  chk Wed Jan 19 01:07:57 GMT woolf:/vol/vol1 milton:/vol/vol1 End (src_only = 0, dst_only = 0, mismatch = 0)

A typical Replication check session in /etc/log/snapmirror on source looks like:

  scn Wed Jan 19 00:58:27 GMT woolf:/vol/vol1 milton:/vol/vol1 Request (172.29.19.15)
  scn Wed Jan 19 00:58:27 GMT woolf:/vol/vol1 milton:/vol/vol1 Start (Snapshots to check = 2)
  scn Wed Jan 19 00:58:27 GMT woolf:/vol/vol1 milton:/vol/vol1 Request_check (milton(0033587346)_vol1.5)
  scn Wed Jan 19 00:58:27 GMT woolf:/vol/vol1 milton:/vol/vol1 Checking_snapshot milton(0033587346)_vol1.5 (Jan 18...
  scn Wed Jan 19 00:58:36 GMT woolf:/vol/vol1 milton:/vol/vol1 Request_check (nightly.0)
  scn Wed Jan 19 00:58:36 GMT woolf:/vol/vol1 milton:/vol/vol1 Checking_snapshot nightly.1 (Jan 18 00:00, cpcount =...
  scn Wed Jan 19 00:58:45 GMT woolf:/vol/vol1 milton:/vol/vol1 End

A typical softlock logging in /etc/log/snapmirror looks like:

  slk Wed May 10 03:06:15 GMT  state.softlock.vol1.0000011e.054.filer1:vol3 Softlock_add (Transfer)
  slk Wed May 10 03:06:15 GMT  state.softlock.vol1.0000011b.054.filer1:vol3 Softlock_delete (Transfer)
  slk Wed May 10 03:06:15 GMT  state.softlock.vol1.0000011b.054.filer1:vol3 Softlock_delete (Revert)
  slk Wed May 10 03:06:15 GMT  state.softlock.vol1.0000011b.054.filer1:vol3 Softlock_delete (Release)
  slk Wed May 10 03:06:15 GMT  state.softlock.vol1.0000011b.054.filer1:vol3 Softlock_delete (Clean_softlocks)
  slk Wed May 10 03:06:15 GMT  state.softlock.vol1.0000011b.054.filer1:vol3 Softlock_add (RSM_forward)
  slk Wed May 10 03:06:15 GMT  state.softlock.vol1.0000011b.054.filer1:vol3 Softlock_delete (RSM_forward)
  slk Wed May 10 03:06:15 GMT  state.softlock.vol1.0000011b.054.filer1:vol3 Softlock_delete (Snapmirror_destinations)
  slk Wed May 10 03:06:15 GMT  state.softlock.vol1.0000011b.054.filer1:vol3 Softlock_delete_pending (Transfer)
  slk Wed May 10 03:06:15 GMT  state.softlock.vol1.0000011b.054.filer1:vol3 Softlock_add_pending (Transfer)
  slk Wed May 10 03:06:15 GMT  state.softlock.vol1.0000011b.054.filer1:vol3 Softlock_mark_pending (Transfer)

FILES

/etc/log/snapmirror
SnapMirror log file for current week.

/etc/log/snapmirror.[0-5]
SnapMirror log files for previous weeks.

SEE ALSO

na_options(1), na_snapmirror(1) na_snapvault(1)


Table of Contents