Table of ContentsView in Frames

Performing tape seeding using SMTape

Using SMTape, cluster administrators can perform tape seeding to initialize a destination FlexVol volume in a data protection mirror relationship. The time taken to initialize this destination volume over a low bandwidth connection using SMTape is faster when compared to using the snapmirror initialize command.

Before you begin

About this task

If you back up 32-bit volumes, then you can restore these volumes only in the Data ONTAP 8.2 release family.

Steps

  1. Determine which Snapshot copy you want to use for tape seeding by using the volume snapshot show command.
    Example
    The following example lists the Snapshot copies:
    clus1::> vol snapshot show -vserver vs1 -volume vol1
     (volume snapshot show)
                                                                      
    Vserver  Volume  Snapshot               State       Size   Total% Used%
    -------- ------ ---------- -------------------------------- ----  ------  
    vs1	    vol1     hourly.2013-01-25_0005   valid     224KB     0%    0%
                    	daily.2013-01-25_0010    valid     92KB      0%    0%
                    	hourly.2013-01-25_0105   valid     228KB     0%    0%
                    	hourly.2013-01-25_0205   valid     236KB     0%    0%
                    	hourly.2013-01-25_0305   valid     244KB     0%    0%
                    	hourly.2013-01-25_0405   valid     244KB     0%    0%
                    	hourly.2013-01-25_0505   valid     244KB     0%    0%
    
    7 entries were displayed.
  2. If you do not have an existing Snapshot copy, manually create a Snapshot copy of the source volume by using the volume snapshot create command.
    You must specify Storage Virtual Machine (SVM, formerly known as Vserver) name, source volume name, and Snapshot copy name.
    Attention: You must not delete this Snapshot copy until tape seeding is over.
    Example
    The following example shows how to create a Snapshot copy mysnap of the source volume src1 on the SVM vs1. You can view the details of the Snapshot copy mysnap by using the volume snapshot show command:
    clus1::> volume snapshot create -vserver vs1 -volume src1 -snapshot mysnap
    
    clus1::> volume snapshot show -vserver vs1 -volume src1 -snapshot mysnap
    
                                  Vserver: vs1
                                   Volume: src1
                                 Snapshot: mysnap
                            Creation Time: Thu Aug 09 12:03:46 2012
                            Snapshot Busy: false
                           List of Owners: -
                            Snapshot Size: 52KB
               Percentage of Total Blocks: 0%
                Percentage of Used Blocks: 1%
                                  Comment: 
                          7-Mode Snapshot: false
          Label for SnapMirror Operations: -
                           Snapshot State: valid 
                     Constituent Snapshot: false
  3. Move and position the tape correctly by using the storage tape position command.
    Example
    The following example moves and positions the no-rewind tape device, st01, and shows the status of the rewind operation:
    clus1::> storage tape position -node clus1-01 -name nrst01 -operation rewind
    
    Note: Rewind operation in progress. Use the "storage tape show -status" command to view the status of the operation.
    
    clus1::> storage tape show -status -device-name-nr nrst01 -node clus1-01
    
    Device ID: fc215-21:5.126L1
    Description: IBM LTO 4 ULTRIUM
    Device Type: tape drive
           WWNN: 5:00a:098200:01dc69
           WWPN: 5:10a:098200:01dc69
    Serial Number: bdf31432387ba0980a026c
    
           Errors: -
    
    Node      Alias   Device Status       FileNo   BlockNo   Resid
    --------  ------  ------------------  -------  --------  ------
    clus-01   st01     read-write-enabled   0       0         0
    
  4. Use the smtape backup command to copy all the volume Snapshot copies, including the base Snapshot copy, to tape.
    Example
    The following example backs up the Snapshot copy mysnap to the tape device st0l:
    clus1::> system smtape backup -vserver vs1 -volume src1 -backup-snapshot mysnap -tape /clus1-01/nrst0l
    
    Session 35 created successfully
    
  5. Use the smtape status show command to view the progress of the baseline transfer.
    Example
    The following example shows the progress and status of the SMTape backup operation triggered in the previous step:
    clus1::> system smtape status show -session 35 -instance
    
    Session Identifier: 35
             Node Name: clus1-01
        Operation Type: backup
        Session Status: ACTIVE
             Path Name: /vs1/src1
           Device Name: /clus1-01/nrst0l
     Bytes Transferred: 0B
            Start Time: 8/9/2012 12:03:55
              End Time: -
         Snapshot Name: mysnap
       Tape Block Size: 240
     Error Description: None
    
    clus1::> smtape status show
      (system smtape status show)
    
    Session Type    Status    Progress  Path         Device             Node
    ------- ------- --------- --------  ------------ ------------------ ----------
         35 backup  COMPLETED   6.01MB  /vs1/src1    /clus1-01/nrst0l     clus1-01
  6. Depending on the status of the SMTape backup operation, perform one of the following actions:
    If the Status shows... Then...
    COMPLETED Go to step 7.

    The baseline transfer is complete.

    WAITING
    1. Load and position the new tape by using the storage tape position command.
    2. Continue the SMTape backup operation by using the smtape continue command.
    FAILED

    The SMTape backup operation may fail due to a number of reasons; such as loss of network connectivity, failure to access the named snapshot, unable to find the snapshot and so on. You must resolve the failure and restart the operation.

    ACTIVE

    The system displays the following message if the SMTape backup is in active state:

    The SMTape backup is in progress.

  7. Physically transport the tapes to the destination node.
  8. Optional: View the data backed up on a tape by using the smtape showheader command.
  9. Create a destination volume of type DP and appropriate size (same or larger than the source volume size) on the destination cluster that will become the data protection mirror by using the volume create command and restrict the volume.
    Example
    The following example creates the data protection mirror volume dst1 on the Storage Virtual Machine (SVM, formerly known as Vserver) vs1. The destination volume is located on the aggregate aggr5 and the destination volume dst1 is in the restricted state:
    clus1::> volume create  -vserver vs1 -volume dst1 -aggregate aggr5 -size 400m -type DP -state  restricted                                                     
    [Job 83] Job succeeded: Successful
  10. Move and position the tape correctly by using the storage tape position command.
    Example
    The following example moves and positions the no-rewind tape device, st01, at the destination volume and shows the status of the rewind operation:
    clus1::> storage tape position -node clus1-01 -name nrst01 -operation rewind
    
    Note: Rewind operation in progress. Use the "storage tape show -status" command to view the status of the operation.
    
    clus1::> storage tape show -status -device-name-nr nrst01 -node clus1-01
    
    Device ID: fc215-21:5.126L1
    Description: IBM LTO 4 ULTRIUM
    Device Type: tape drive
           WWNN: 5:00a:098200:01dc69
           WWPN: 5:10a:098200:01dc69
    Serial Number: bdf31432387ba0980a026c
    
           Errors: -
    
    Node      Alias   Device Status       FileNo   BlockNo   Resid
    --------  ------  ------------------  -------  --------  ------
    clus-01   st01     read-write-enabled   0       0         0
    
  11. Use the smtape restore command to restore all the volume Snapshot copies, including the base Snapshot copy, from tape to the destination volume.
    Example
    The following example restores all the data from tape to the destination volume dst1 on the Storage Virtual Machine (SVM, formerly known as Vserver) vs1:
    clus1::> system smtape restore -vserver vs1 -volume dst1 -tape /clus1-01/nrst0l
    Session 36 created successfully
    
  12. Use the smtape status show command to view the progress of the baseline transfer.
    Example
    The following example shows the progress and status of the SMTape restore operation triggered in the previous step:
    clus1::> system smtape status show -session 36 -instance
    	
    Session Identifier: 36
             Node Name: clus1-01
        Operation Type: restore
        Session Status: ACTIVE
             Path Name: /vs1/dst1
           Device Name: /clus1-01/nrst0l
     Bytes Transferred: 0B
            Start Time: 8/9/2012 12:04:15
              End Time: -
         Snapshot Name: None
       Tape Block Size: 240
     Error Description: None
    
    clus1::> system smtape status show
    	
    Session Type    Status    Progress  Path         Device             Node
    ------- ------- --------- --------  ------------ ------------------ ----------
         36 restore COMPLETED   6.01MB  /vs1/dst1    /clus1-01/nrst0l     clus1-01
         35 backup  COMPLETED   6.01MB  /vs1/src1    /clus1-01/nrst0l     clus1-01
    2 entries were displayed.
    
  13. Depending on the status of the SMTape restore operation, perform one of the following actions:
    If the Status shows... Then...
    COMPLETED Go to step 14.

    The baseline transfer is complete.

    WAITING
    1. Load and position the new tape by using the storage tape position command.
    2. Continue the SMTape restore operation by using the smtape continue command.
  14. Use the smtape break command to break the volume and tape relationship.
    Note: This command is also available for SVM administrators.
    Example
    The following example breaks the SMTape relationship between the tape and the volume dst1:
    clus1::> system smtape break -vserver vs1 -volume dst1
    
    Operation succeeded: snapmirror break for destination vs1:dst1             
    
    The destination volume is now writeable and a mirror relationship can be reestablished.
  15. Establish the SnapMirror or SnapVault relationship by using the snapmirror resync command.
    A SnapMirror relationship creates a data protection copy of the source volume; a SnapVault relationship creates a backup copy. The -type parameter determines the type of relationship established. The value of the -type parameter for a SnapMirror relationship is DP and the value for a SnapVault relationship is XDP.
    Example
    The following example reestablishes a SnapMirror relationship between the destination volume dst1 and the source volume src1:
    clus1::> snapmirror resync -destination-path vs1:dst1  -source-path vs1:src1 -type  DP 
    
    [Job 85] Job is queued: initiate snapmirror resync to destination "vs1:dst1".  
    [Job 85]                                                                       
    [Job 85] Job succeeded: SnapMirror Resync Transfer Queued                      
    
  16. Use the snapmirror show command to view the progress of the data protection mirror relationship reestablished between the destination volume and source volume in the previous step.
    Example
    The following example shows the data protection mirror relationship established between the source volume vs1 and destination volume dst1. The data protection mirror relationship type established is DP:
    clus1::> snapmirror show -destination-path vs1:dst1
    	
    	                Source Path: vs1:src1
    	           Destination Path: vs1:dst1
    	          Relationship Type: DP
    	        SnapMirror Schedule: -
    	                Tries Limit: -
    	          Throttle (KB/sec): unlimited
    	               Mirror State: -
    	        Relationship Status: Transferring
    	          Transfer Snapshot: snapmirror.58621f01-e214-11e1-833d-123478563412_2147484708.2012-08-09_120444
    	          Snapshot Progress: 0B
    	             Total Progress: 0B
    	        Snapshot Checkpoint: -
    	            Newest Snapshot: -
    	  Newest Snapshot Timestamp: -
    	          Exported Snapshot: -
    	Exported Snapshot Timestamp: -
    	                    Healthy: true
    	   Constituent Relationship: false
    	            Relationship ID: 6485d262-e21a-11e1-833d-123478563412
    	              Transfer Type: resync
    	             Transfer Error: -
    	           Current Throttle: 103079214
    	  Current Transfer Priority: normal
    	         Last Transfer Type: -
    	        Last Transfer Error: -
    	         Last Transfer Size: -
    	     Last Transfer Duration: -
    	         Last Transfer From: -
    	      Progress Last Updated: 08/09 12:04:45
    	    Relationship Capability: 8.2 and above
    	                   Lag Time: -
    	                     Policy: DPDefault
    
    When the relationship status shows idle, the data protection mirror relationship is established and tape seeding is complete.
    Example
    clus1::> snapmirror show -destination-path vs1:dst1
    	
    	                Source Path: vs1:src1
    	           Destination Path: vs1:dst1
    	          Relationship Type: DP
    	        SnapMirror Schedule: -
    	                Tries Limit: -
    	          Throttle (KB/sec): unlimited
    	               Mirror State: Snapmirrored
    	        Relationship Status: Idle
    	          Transfer Snapshot: -
    	          Snapshot Progress: -
    	             Total Progress: -
    	        Snapshot Checkpoint: -
    	            Newest Snapshot: snapmirror.58621f01-e214-11e1-833d-123478563412_2147484708.2012-08-09_120444
    	  Newest Snapshot Timestamp: 08/09 12:04:44
    	          Exported Snapshot: snapmirror.58621f01-e214-11e1-833d-123478563412_2147484708.2012-08-09_120444
    	Exported Snapshot Timestamp: 08/09 12:04:44
    	                    Healthy: true
    	   Constituent Relationship: false
    	            Relationship ID: 6485d262-e21a-11e1-833d-123478563412
    	              Transfer Type: resync
    	             Transfer Error: -
    	           Current Throttle: 103079214
    	  Current Transfer Priority: normal
    	         Last Transfer Type: resync
    	        Last Transfer Error: -
    	         Last Transfer Size: 72KB
    	     Last Transfer Duration: 0:0:7
    	         Last Transfer From: vs1:src1
    	      Progress Last Updated: -
    	    Relationship Capability: 8.2 and above
    	                   Lag Time: 0:0:7
    	                     Policy: DPDefault