Checking SnapMirror data transfer logs

Why you check data transfer logs  

You can use the options snapmirror.log.enable command to check SnapMirror data transfer logs. You can find out whether transfers are occurring as planned, how long the transfers take, and how well the system setup works. You find this information in the SnapMirror log file.

What checking data transfer history shows you  

The SnapMirror log file shows you

• The start time and the end time of the SnapMirror logging process
• The start time, end time, and size of each transfer
• Any abnormal termination and restart of a transfer
• Other SnapMirror-related activities

What you can do with the information recorded  

You can use the raw information provided to do the following:

• Calculate the average transfer size
• Calculate the average transfer time
• Look at the number of successful transfers and the failure rate
• Tune the schedule
• Create a notifier for aborted transfers
• Monitor performance on a per-volume level
• Be assured that things are working as planned

How to find out whether SnapMirror logging is turned on or off  

SnapMirror logging is turned on by default. However, if you need to find out whether SnapMirror logging is turned on or off, complete the following step.

options snapmirror.log.enable

Example

filerA> options snapmirror.log.enable

snapmirror.log.enable      on 

How to turn SnapMirror logging on  

To turn SnapMirror logging on, complete the following step.

options snapmirror.log.enable on

Where the log files are kept  

SnapMirror keeps the current log on the root volume of the executing filer, as /etc/log/snapmirror.0. A new log file is generated every week as /etc./log/snapmirror.0. Older log files are renamed /etc./log/snapmirror.[1-5] and the oldest log file is deleted. The log files can be read with a text editor.

Format of the log files  

The log file is in the following format:

type timestamp source_filer:source_path dest_filer:dest_path 
event_info 

type can be one of the following: src, dst, log, cmd.

type specifies whether the record is for the source side (src) or destination side (dst) of the transfer. Certain events apply to only one side. The type log indicates a record about the logging system itself, for example, Start_Logging and End_Logging. The type cmd indicates a record of user commands, for example, Release_command and Resync_command.

timestamp is expressed in ctime format, for example:

Fri Jul 27 20:41:09 GMT.

event_info includes the following event names:

Request ( IP address | transfer type )

Start

Restart (@ num KB)

End (num KB done)

Abort (error_msg)

Defer (reason)

Rollback_start

Rollback_end

Rollback_failed

Start_Logging

End_Logging 

Wait_tape

New_tape

Snapmirror_on

Snapmirror_off

Quiesce_start

Quiesce_end

Quiesce_failed

Resume_command

Break_command

Release_command

Abort_command

Resync_command

Migrate_command

The Request event on the source side includes the IP address of the filer that made the transfer request; the Request event on the destination side includes the type of transfer. At the end of each successful transfer, the End event also reports the total size of the transfer in KB. Error messages are included with the Abort and Defer events.

Examples of log files  

The following is an example of a log file from the source side.

log Fri Jul 27 20:00:01 GMT - - Start_Logging 

cmd Fri Jul 27 20:00:20 GMT - - Snapmirror_on 

src Fri Jul 27 20:41:09 GMT filer1:vol1 filer2:vol1 Request (10.56.17.133) 

src Fri Jul 27 20:41:32 GMT filer1:vol1 filer2:vol1 Abort (Destination not allowed) 

src Fri Jul 27 20:45:31 GMT filer1:vol0 filer1:vol1 Request (10.56.17.132) 

src Fri Jul 27 20:45:35 GMT filer1:vol0 filer1:vol1 Start 

src Fri Jul 27 20:51:40 GMT filer1:vol0 filer1:vol1 End (26200 KB) 

src Fri Jul 27 22:41:09 GMT filer1:/vol/vol1/qtA filer2:/vol/vol1/qtB Request 
(10.56.17.133) 

src Fri Jul 27 22:41:12 GMT filer1:/vol/vol1/qtA filer2:/vol/vol1/qtB Start 

src Fri Jul 27 22:41:13 GMT filer1:/vol/vol1/qtA filer2:/vol/vol1/qtB Abort (Non 
unicode directory found in source qtree.) 

src Fri Jul 27 22:45:53 GMT filer1:/vol/vol1/qtb filer2:/vol/vol1/qsmb Request 
(10.56.17.133) 

src Fri Jul 27 22:45:56 GMT filer1:/vol/vol1/qtb filer2:/vol/vol1/qsmb Start 

src Fri Jul 27 22:45:59 GMT filer1:/vol/vol1/qtb filer2:/vol/vol1/qsmb End (3800 KB) 

cmd Fri Jul 27 22:50:29 GMT filer1:/vol/vol1/qtb filer2:/vol/vol1/qsmb Release_command 

The following is an example of a log file from the destination side.

dst Fri Jul 27 22:50:18 GMT filer1:vol0 filer1:vol1 Request (Initialization) 

dst Fri Jul 27 22:50:20 GMT filer1:vol0 filer1:vol1 Abort (Destination is not 
restricted) 

dst Fri Jul 27 22:57:17 GMT filer1:/vol/vol1/qtA filer2:/vol/vol1/qtB Request 
(Initialize) 

dst Fri Jul 27 22:57:24 GMT filer1:/vol/vol1/qtA filer2:/vol/vol1/qtB Start 

dst Fri Jul 27 22:57:36 GMT filer1:/vol/vol1/qtA filer2:/vol/vol1/qtB End (55670 KB) 

dst Fri Jul 27 23:10:03 GMT filer1:/vol/vol1/qtA filer2:/vol/vol1/qtB Request 
(Scheduled) 

dst Fri Jul 27 23:10:07 GMT filer1:/vol/vol1/qtA filer2:/vol/vol1/qtB Start 

dst Fri Jul 27 23:10:18 GMT filer1:/vol/vol1/qtA filer2:/vol/vol1/qtB End (12900 KB) 

cmd Sat Jul 28 00:05:29 GMT - filer2:/vol/vol1/qtB Quiesce_start 

cmd Sat Jul 28 00:05:29 GMT - filer2:/vol/vol1/qtB Quiesce_end 

cmd Sat Jul 28 00:05:40 GMT - filer2:/vol/vol1/qtB Break_command 

cmd Sat Jul 28 00:41:05 GMT filer1:/vol/vol1/qtA filer2:/vol/vol1/qtB Resync_command 

log Sat Jul 28 00:41:10 GMT - - End_Logging 

The following is an example of a log file from a retrieve (from tape) request.

dst Fri Jun 22 03:07:34 GMT milton:rst0l milton:bigtwo Request 
(retrieve) 

dst Fri Jun 22 03:07:34 GMT milton:rst0l milton:bigtwo Start 

dst Fri Jun 22 05:03:45 GMT milton:rst0l milton:bigtwo Wait_tape 

dst Fri Jun 22 15:16:44 GMT milton:rst0l milton:bigtwo New_tape 

dst Fri Jun 22 17:13:24 GMT milton:rst0l milton:bigtwo Wait_tape 

dst Fri Jun 22 17:56:43 GMT milton:rst0l milton:bigtwo New_tape 

dst Fri Jun 22 18:10:37 GMT milton:rst0l milton:bigtwo End 
(98602256 KB)

How to turn off the SnapMirror log  

To turn off the SnapMirror log process, complete the following step.

options snapmirror.log.enable off

Copyright © 1994-2003, Network Appliance, Inc. All rights reserved.
Part No. 210-00325
File: mirror13.htm
Last updated: 01/14/03 18:24:45