Listing SnapMirror Snapshot copies

About SnapMirror listing

You can use the Data ONTAP snap list command to list all Snapshot copies, including the SnapMirror-specific Snapshot copies, that are stored on your storage system.

To list all the Snapshot copies on your system, complete the following step.

Step	Action
1	In the console of either your source or destination system, enter the following command: snap list vol_name Result A listing of all Snapshot copies stored on your system appears. SnapMirror Snapshot copies are distinguished from system Snapshot copies by a more elaborate naming convention and the label "snapmirror" in parentheses.

Step

Action

In the console of either your source or destination system, enter the following command:

snap list vol_name

Result

A listing of all Snapshot copies stored on your system appears. SnapMirror Snapshot copies are distinguished from system Snapshot copies by a more elaborate naming convention and the label "snapmirror" in parentheses.

Naming conventions for Snapshot copies used by SnapMirror

When you run the snap list command, SnapMirror Snapshot copies are distinguished from the regular system Snapshot copies by their naming conventions.

For volume replication, SnapMirror creates a Snapshot copy of the whole source volume that is copied to the destination volume. For qtree replication, SnapMirror creates Snapshot copies of one or more source qtrees on the source volume that are copied to a qtree on the destination volume.

A SnapMirror volume Snapshot copy name is in the following format:

dest_system(sysid)_name.number

dest_system is the host name of the destination system.

sysid is the destination system ID number.

name is the name of the destination volume.

number is the number of successful transfers for the Snapshot copy, starting at 1. Data ONTAP increments this number for each transfer.

A SnapMirror qtree Snapshot copy name is in the following format:

dest_system(sysid)_name-src|dst.number

dest_system is the host name of the destination system.

sysid is the destination system ID number.

name is the name of the destination volume or qtree path.

src|dst is the source or destination name.

number is an arbitrary start point number for the Snapshot copy. Data ONTAP increments this number for each transfer.

In the output of the snap list command, SnapMirror Snapshot copies are followed by the SnapMirror name in parentheses.

Volume example

systemA(0016791363)_vol0.9 (snapmirror)

Qtree example

systemA(0016789302)_vol1_qtree3-dst.15 (snapmirror)

Caution
Do not delete manually created Snapshot copies marked "snapmirror" in the output of the snap list command.

Using snap list to show SnapMirror updates on the destination volume

The following example describes SnapMirror Snapshot copies that are created on a source volume and copied to a destination volume. In this example, data is copied from vol1 of systemA (the source) to vol2 of systemB (the destination).

To create a baseline version of a destination volume, systemA creates a Snapshot copy named systemB(0016782130)_vol2.1 on systemA. All Snapshot copies in vol1 of systemA, including systemB(0016782130)_vol2.1, are transferred to vol2 of systemB. When replicating a qtree, SnapMirror transfers only the qtree's data in the Snapshot copy for the qtree.

If the administrator were to run the snap list command on the destination systemB after the systemB(0016782130)_vol2.1 Snapshot copy was transferred from systemA to systemB, a listing similar to the following example would be generated:

systemB> snap list vol2

working.....

%/used    %/total  date          name

-------- --------  ------------  --------

0% ( 0%) 0% ( 0%)  Nov 17 10:50  systemB(0016782130)_vol2.1 
(snapmirror)

1% ( 0%) 0% ( 0%)  Nov 17 10:00  hourly.0

1% ( 0%) 0% ( 0%)  Nov 17 00:00  nightly.0

1% ( 0%) 0% ( 0%)  Nov 15 16:00  hourly.1

1% ( 0%) 1% ( 0%)  Nov 15 15:00  hourly.2

2% ( 0%) 1% ( 0%)  Nov 15 14:00  hourly.3

2% ( 0%) 1% ( 0%)  Nov 15 13:00  hourly.4

2% ( 0%) 1% ( 0%)  Nov 15 12:00  hourly.5

When it is time to update the destination, another Snapshot copy is created on systemA.

The snap list command on systemA would generate the following display after the systemB(0016782130)_vol2.2 Snapshot copy was created on systemA:

systemA> snap list vol1

working....

%/used   %/total     date          name

-------- ----------  ------------  --------

0% ( 0%) 0% ( 0%)    Nov 17 10:52  systemB(0016782130)_vol2.2 
(snapmirror)

0% ( 0%) 0% ( 0%)    Nov 17 10:51  systemB(0016782130)_vol2.1 
(snapmirror)

1% ( 0%) 0% ( 0%)    Nov 17 10:00  hourly.0

1% ( 0%) 0% ( 0%)    Nov 17 00:00  nightly.0

1% ( 0%) 0% ( 0%)    Nov 15 16:00  hourly.1

1% ( 0%) 1% ( 0%)    Nov 15 15:00  hourly.2

After the systemB(0016782130)_vol2.2 Snapshot copy is transferred from systemA to systemB, both Snapshot copies exist on systemB. On systemA, however, systemB(0016782130)_vol2.1 is no longer needed and is deleted; only systemB(0016782130)_vol2.2 is retained to be used for the next transfer.

You can see a list of each SnapMirror Snapshot copy on the server, and the qtrees it contains, and the client sources of those qtrees and their timestamps by using the snap list -q command.

You can use the snap list -o command to display the names, timestamps, and sources (if they are copies) of the qtrees in a specified volume or at a path name.