Skip to main content

snapmirror restore

Contributors
Suggest changes
PDFs

Restore a Snapshot copy from a source volume to a destination volume

Availability: This command is available to cluster and Vserver administrators at the admin privilege level.

Description

The snapmirror restore command restores the entire contents of a snapshot or one or more files, LUNs or NVMe namespaces of a snapshot from one volume to another volume.

The snapmirror restore command, in context to Application Consistency Groups, restores the entire content of a snapshot from one Application Consistency Group to another Application Consistency Group. Each Application Consistency Group is considered as atomic entity in restore operation

The source of the restore can be a volume or an Application Consistency Group that is:

  • the destination volume or destination Application Consistency Group of a extended data protection (XDP) relationship

  • the destination volume of a data protection (DP) relationship with "Relationship Capability" of "8.2 and above"

  • a data-protection volume or an Application Consistency Group which is not the destination endpoint of any SnapMirror relationship

  • a read-write volume or an Application Consistency Group.

  • an AltaVault endpoint. In this case the destination must be an empty ONTAP volume.

The following cannot be used as either the source or destination volume or destination Application Consistency Group of a restore:

  • a volume or Application Consistency Group that is the source or destination endpoint of a SnapMirror load-sharing relationship.

  • a volume that is the destination endpoint of a SnapMirror relationship with the "Relationship Capability" of "Pre 8.2" .

  • a SolidFire endpoint.

A SnapMirror relationship of type RST is created from the source volume or source Application Consistency Group to the destination volume or destination Application Consistency Group by the snapmirror restore command. This relationship lasts for the duration of the restore operation and is deleted when the command completes successfully.

The following paragraphs describe the behavior when restoring the entire contents of a snapshot to a destination volume or destination Application Consistency Group.

By default the snapmirror restore will copy the latest snapshot from the source volume or source Application Consistency Group to the destination volume or destination Application Consistency Group. A specific snapshot can be selected with the -source-snapshot parameter.

Any quota rules defined for the destination volume are deactivated prior to restoring the entire contents of a snapshot. Run the command volume quota modify-vserver`destination-volume-vserver-volumedestination-volume-name-state`on to reactivate quota rules after the entire contents of the snapshot have been restored.

If the destination Application Consistency Group contains empty data protection volumes, the snapmirror restore command performs a baseline restore.

If the destination volume is an empty data protection volume, the snapmirror restore command performs a baseline restore. For a baseline restore the following steps are performed:

  • Create the RST SnapMirror relationship.

  • The entire contents of the snapshot selected to be restored are copied to the active file system of the destination volume or destination Application Consistency Group.

  • The destination volume or destination Application Consistency Group is made read-write.

  • The RST SnapMirror relationship is deleted.

If the destination volume is a read-write volume, an incremental restore is performed. The incremental restore fails if it cannot find a common snapshot between the source and destination volumes. Restoring a snapshot to an empty read-write volume is not supported. Incremental restore from a non-ONTAP endpoint to a ONTAP volume is not supported.

If the destination Application Consistency Group contains a read-write flex volume, an incremental restore is performed. The incremental restore fails if it cannot find a common snapshot between the source and destination Application Consistency Group. Restoring a snapshot to an empty read-write flex volumes which are the part of Application Consistency Group is not supported.

An incremental restore preserves all snapshots on the destination volume but does not preserve changes to the active file system since the latest snapshot. To preserve changes to the destination volume since the latest snapshot use the volume snapshot create command. Restore is a disruptive operation so client access of the destination volume is not advised for the duration of the operation.

For an incremental restore the following steps are performed:

  • Create the RST SnapMirror relationship.

  • The active file system of the destination volume is reverted to the latest snapshot on the destination volume and the destination volume is made read-only.

  • In context to Application Consistency Group, the active file system of the destination Application Consistency Group is reverted to the latest snapshot on the destination Application Consistency Group and the flex volumes inside destination Application Consistency Group is made read-only.

  • This snapshot is the exported snapshot and it is the view to which clients are redirected when accessing the destination volume or destination Application Consistency Group.

  • The contents of the snapshot selected to be restored are copied to the active file system of the destination volume or destination Application Consistency Group.

  • The destination volume or destination Application Consistency Group is made read-write.

  • The RST SnapMirror relationship is deleted.

If snapmirror restore fails or is aborted, the RST relationship remains. Use the snapmirror show command with the destination volume name or destination Application Consistency Group name to display the reason for the error. An EMS is also generated when a failure occurs. There are two options to recover when restore fails or is aborted:

  • Take corrective action suggested by the EMS and reissue the original command.

  • Use the original command with -clean-up-failure to cancel the request.

When specifying -clean-up-failure to cancel an incremental restore request, the following steps are performed:

  • If the snapshot has not been restored to the destination volume or destination Application Consistency Group, all data copied to the active file system by snapmirror restore to the destination volume or destination Application Consistency Group is reverted.

  • The destination volume or destination Application Consistency Group is made read-write.

  • The RST SnapMirror relationship is deleted.

When specifying -clean-up-failure to cancel a baseline restore request, the following steps are performed:

  • If the snapshot has been restored to the destination volume or destination Application Consistency Group, the volume or Application Consistency Group is made read-write.

  • The RST SnapMirror relationship is deleted.

The following paragraphs describe the behavior and requirements when restoring one or more files, LUNs or NVMe namespaces to the destination volume.

The destination volume must be a read-write volume. Restoring files, LUNs or NVMe namespaces to a data protection volume is not supported. When restoring files, LUNs or NVMe namespaces the source and destination volumes are not required to have a common snapshot. If a common snapshot exists, an incremental restore is performed for those files, LUNs or NVMe namespaces being restored which exist in the common snapshot.

The destination Application Consistency Group must contains a read-write volume. While restoring, source and destination Application Consistency Group are not required to have a common snapshot. If a common snapshot exists, an incremental restore is performed.

The contents of the files, LUNs or NVMe namespaces to which data is being restored on the destination volume are not preserved by this command. To preserve the contents of the destination files, LUNs or NVMe namespaces, create a snapshot on the destination volume prior to running this command. Client I/O is not allowed to a file, LUN or NVMe namespace to which data is being restored on the destination volume.

The -source-snapshot parameter is required when restoring files, LUNs or NVMe namespaces. It identifies the snapshot on the source volume from which the files, LUNs or NVMe namespaces to be restored are copied. If all files, LUNs or NVMe namespaces to be restored do not exist in this snapshot the command fails.

The source path for each file, LUN or NVMe namespace being restored is required. The source path of a file, LUN or NVMe namespace is from the root of the source snapshot of the source volume. The file is restored to the same path on the destination volume unless an optional destination path is specified. The destination path is from the root of the destination volume. If a file, LUN or NVMe namespace to which data is being restored on the destination volume does not exist, the file, LUN or NVMe namespace is created. If any directory in the path of the file, LUN or NVMe namespace being restored does not exist on the destination volume, the command fails. Overwriting the contents of an existing file with the contents of a different file is supported. Similarly, overwriting the contents of an existing LUN or NVMe namespace with the contents of a different LUN or NVMe namespace is supported. However, overwriting a file with the contents of a LUN or NVMe namespace is not supported. Overwriting a LUN with the contents of a file or NVMe namespace is not supported. Overwriting an NVMe namespace with the contents of a file or LUN is not supported. Client I/O is not allowed to all files, LUNs and NVMe namespaces to which data is being restored on the destination volume.

If quota rules have been defined for the destination volume, resource usage is updated during file restore, but limits of quota rules are not enforced. Therefore, resource limits might be exceeded during a file restore.

Multiple concurrent snapmirror restore commands, restoring one or more files, LUNs or NVMe namespaces to the same destination volume, are not supported. The destination volume of a snapmirror restore to which one or more files, LUNs or NVMe namespaces are being restored, can simultaneously be the source volume of a snapmirror update .

For a file, LUN or NVMe namespace restore the following steps are performed:

  • Create the RST SnapMirror relationship.

  • If any file, LUN or NVMe namespace being restored does not exist on the destination volume, create all such files, LUNs or NVMe namespaces.

  • Prevent client I/O to files, LUNs or NVMe namespaces to which data is being restored on the destination volume.

  • Revoke locks and space reservations held by NAS clients for files being restored.

  • Copy the contents of all source files, LUNs or NVMe namespaces to the corresponding file, LUN or NVMe namespace on the destination volume.

  • Allow client I/O to files, LUNs or NVMe namespaces to which data has been restored on the destination volume.

  • Delete the RST SnapMirror relationship.

Note Some file restore operations require a snapshot to be created. This snapshot is temporary, it is deleted before the operation completes.

Since client I/O is not allowed to files, LUNs or NVMe namespaces being restored, client I/O to files, LUNs or NVMe namespaces being restored should be quiesced. Mapped LUNs or NVMe namespaces remain mapped throughout the operation. SAN clients do not need to rediscover a mapped LUN that has been restored. Restoring an NVMe namespace on top of another NVMe namespace with a different attribute relevant to NVMe protocol accessibility (like size) is not supported.

If snapmirror restore fails or is aborted, the RST relationship remains. Use the snapmirror show command with the destination volume or destination Application Consistency Group to display the reason for the error. An EMS is also generated when a failure occurs. There are two options to recover when restore fails or is aborted:

  • Take corrective action suggested by the EMS and reissue the original command.

  • Use snapmirror restore`-clean-up-failure` along with specifying the destination volume or destination Application Consistency Group to cancel the request.

When specifying -clean-up-failure to cancel a file restore request, the following steps are performed:

  • Any files to which client I/O is not allowed are removed.

  • Any snapshot created for use during a file restore operation is deleted.

  • The RST SnapMirror relationship is deleted.

Note LUNs to which client I/O is not allowed remain. For LUNs to which client I/O is not allowed, do one of the following:

  • Use the snapmirror restore command to restore data to the LUN. Once the command completes successfully, client I/O to the LUN is allowed.

  • Delete the LUN using the lun delete command with the -force-fenced parameter.

Note Similarly, NVMe namespaces to which client I/O is not allowed remain. For NVMe namespaces to which client I/O is not allowed, do one of the following:

  • Use the snapmirror restore command to restore data to the NVMe namespace. Once the command completes successfully, client I/O to the NVMe namespace is allowed.

  • Delete the NVMe namespace using the vserver nvme namespace delete command with the -skip-mapped-check parameter.

The snapmirror restore command must be used from the destination Vserver or cluster.

With -lun-list , subset of LUNs can be restored to the Destination Consistency Group endpoint.

Parameters

{ [-S, -source-path {<[vserver:][volume]>|<[[cluster:]//vserver/]volume>|<hostip:/lun/name>|<hostip:/share/share-name>|<[vserver:]/cg/[app-cgname]>}] - Source Path

Specifies the source endpoint in one of four formats. The basic format includes the names of the Vserver (vserver) and volume (volume). A format which also includes the name of the cluster (cluster) is supported for consistency with other snapmirror commands. The form of the pathname which includes the cluster name is not valid when operating in a Vserver context. Source endpoint having Application Consistency Group includes vserver name followed by cg and Application Consistency Group name. A non-ONTAP source endpoint (for example, AltaVault) can be specified in the form hostip:/share/share-name .

| [-source-cluster <Cluster name>] - Source Cluster

Specifies the cluster in which the source volume resides. This parameter is not needed; it is provided for consistency with other snapmirror commands. If this parameter is specified, the -source-vserver and -source-volume parameters must also be specified. This parameter is not valid when operating in a Vserver context. This parameter is not supported if the source is a non-ONTAP endpoint.

[-source-vserver <vserver name>] - Source Vserver

Specifies the source Vserver of the SnapMirror relationship. If this parameter is specified, the -source-volume parameter must also be specified. This parameter is not supported if the source is a non-ONTAP endpoint.

[-source-volume <volume name>] - Source Volume }

Specifies the source volume of the SnapMirror relationship. If this parameter is specified, the -source-vserver parameter must also be specified. This parameter is not supported if the source is a non-ONTAP endpoint.

{ -destination-path {<[vserver:][volume]>|<[[cluster:]//vserver/]volume>|<hostip:/lun/name>|<hostip:/share/share-name>|<[vserver:]/cg/[app-cgname]>} - Destination Path

Specifies the destination endpoint in one of three formats. The basic format includes the names of the Vserver (vserver) and volume (volume). A format that also includes the name of the cluster (cluster) is supported for consistency with other snapmirror commands. The form of the pathname which includes the cluster name is not valid when operating in a Vserver context. Destination endpoint having Application Consistency Group includes vserver name followed by cg and Application Consistency Group name.

| [-destination-cluster <Cluster name>] - Destination Cluster

Specifies the cluster in which the destination volume resides. This parameter is not needed; it is provided for consistency with other snapmirror commands. If this parameter is specified, the -destination-vserver and -destination-volume parameters must also be specified. This parameter is not valid when operating in a Vserver context. This parameter is only applicable for relationships with "Relationship Capability" of "Pre 8.2" .

-destination-vserver <vserver name> - Destination Vserver

Specifies the destination Vserver. If this parameter is specified, the -destination-volume parameter must also be specified.

-destination-volume <volume name> - Destination Volume }

Specifies the destination volume. If this parameter is specified, the -destination-vserver parameter must also be specified.

[-s, -source-snapshot <text>] - Source Snapshot

When restoring the entire contents of a snapshot, this optional parameter identifies the snapshot to be restored from the source volume to the destination volume. The default value is the latest snapshot on the source volume. When restoring one or more files, LUNs or NVMe namespaces from a snapshot, this parameter is required.

[-k, -throttle <throttleType>] - Throttle (KB/sec)

This optional parameter limits the network bandwidth used for the restore transfer when the source and destination volumes belong to different clusters. It sets the maximum rate (in Kbytes/sec) at which data can be transferred between the clusters during the operation. To fully use the network bandwidth available between the clusters, set the throttle value to unlimited or 0 . The minimum throttle value is four Kbytes/sec, so if you specify a throttle value between 1 and 4 , it will be treated as if you specified 4 .

[-transfer-priority {low|normal}] - Transfer Priority

This optional parameter specifies the priority at which the transfer runs. The default value for this parameter is normal .

[-cg-item-mappings {<source volume>:@<destination volume>|<source item path>:@<destination item path>}] - Consistency Group Item Mappings

This optional parameter specifies a list of the consistency group (CG) item mappings. It is considered only if the supplied source and destination path values denote valid CG paths. For CG level relationships, this parameter must be specified. The value for this parameter must contain mappings of one or more pairs of constituent source and destination volumes of the form srcvol1:@dstvol1,…​ .

[-disable-storage-efficiency <true>] - Disable Storage Efficient Transfer

The default behavior of restore is to preserve storage efficiency when possible. Use this optional parameter to turn off storage efficiency for data transferred over the wire and written to the destination volume.

[-clean-up-failure <true>] - Clean up after Failure

Use this optional parameter to recover from an aborted or failed restore operation. Any temporary RST relationship is removed from the destination Vserver. An attempt is made to remove any temporary RST relationship from the source Vserver. If cleaning up an incomplete restore of the entire contents of a snapshot and the destination volume was read-write prior to the failed or aborted restore operation, it is converted back to read-write if necessary, while removing all data transferred or copied during the restore operation. If cleaning up an incomplete restore of one or more files, LUNs or NVMe namespaces of a snapshot, any file to which client I/O is not allowed is deleted.

[-tries <integer_or_unlimited>] - Tries Limit

Specifies the total number of attempts to transfer data in cases where a transfer is interrupted by an error that SnapMirror can recover from. The value of this parameter must be a positive integer or unlimited .

[-f, -force <true>] - Force

If this parameter is specified, the command proceeds without prompting for confirmation.

{ [-file-list <<source path>[,@<destination path>]>,…​] - File List

Specifies the files, LUNs or NVMe namespaces to be restored. The list can contain specifications for up to 8 files, LUNs or NVMe namespaces. Specification for each file, LUN or NVMe namespace consists of a source_path and an optional destination_path , and is of the form 'source_path[,@destination_path ]'. source_path is required and is the path of the file from the source snapshot, e.g. /dira/file1 or /lun1. The source path does not include the snapshot name nor the source volume name. The path to each file to be restored in the active file system of the destination volume is the same as the path specified by source_path , unless an optional destination_path is specified. destination_path begins with the @ symbol followed by the path of the file from the root of the active file system of the destination volume, e.g. @/file1 or @/dira/lun1. File restore is not supported if the source_path or destination_path contains commas in its directory or file name. Each source_path and destination_path is a separate entity in the list of paths. A destination_path is associated with the source_path that immediately precedes it. If this parameter is specified, -source-snapshot must also be specified. Examples:

/dira/file1
/dira/file1,@/dirb/file2
/dira/file1,@/dirb/file2,/dirc/file3
| [-lun-list [source lun>:@<destination lun],…​] - Lun List }

Specifies the source and destination LUN pairs to be restored. Specification for each LUN list consists of a source_lun and destination_lun , and is of the form 'source_lun:@destination_lun '. source_lun is required and is the name of the LUN from the source snapshot. A source LUN name is considered as destination LUN if destination LUNs are not provided. Examples:

source_lun1

:@

destination_lun1

,or

source_lun1

,

source_lun2

``[-use-network-compression <true>]`` - Use Network Compression::
Use this optional parameter to use network compression for data transfer over the wire. This parameter is not supported for relationships with non-ONTAP endpoints.

``[-backoff-level {high|medium|none}]`` - SM Backoff Level due to Client Ops::
This optional parameter specifies the SnapMirror backoff level due to client ops. This parameter is supported only for FlexVol SnapMirror relationships. The default value is `high` .

== Examples

The following example does an incremental restore between the restore source volume ``_vs2.example.com:dept_eng_dp_mirror2_`` and the restore destination volume ``_vs1.example.com:dept_eng_`` :

vs1.example.com::> snapmirror restore
-destination-path vs1.example.com:dept_eng
-source-path vs2.example.com:dept_eng_dp_mirror2
-source-snapshot snap3
Warning: All data newer than snapshot snap6 on volume
vs1.example.com:dept_eng will be deleted.
Do you want to continue? {y|n}: y
[Job 34] Job is queued: snapmirror restore from source
vs2.example.com:dept_eng_dp_mirror2 for the snapshot snap3.
vs1.example.com::>

The following example does a restore between the source Application Consistency Group ``_vs2.example.com:/cg/src_cg_`` and destination Application Consistency Group ``_vs1.example.com:/cg/dst_cg_`` :

vs1.example.com::> snapmirror restore
-destination-path vs1.example.com:/cg/dst_cg
-source-path vs2.example.com:/cg/src_cg
-source-snapshot snap3
[Job 34] Job is queued: snapmirror restore from source
vs2.example.com:/cg/src_cg for the snapshot snap3.
vs1.example.com::>

The following example restores /file3 from the source snapshot ``_snap3_`` on the source volume ``_vs2.example.com:dept_eng_dp_mirror2_`` to the active file system of the restore destination volume ``_vs1.example.com:dept_eng_`` :

vs1.example.com::> snapmirror restore
-destination-path vs1.example.com:dept_eng
-source-path vs2.example.com:dept_eng_dp_mirror2
-source-snapshot snap3
-file-list /file3
Warning: This command will overwrite any file on destination
"vs1.example.com:dept_eng" that has the same path as any of
the files to be restored.
Do you want to continue? {y|n}: y
[Job 35] Job is queued: snapmirror restore from source
"vs2.example.com:dept_eng_dp_mirror2" for the snapshot snap3.
vs1.example.com::>

The following example restores /file3 from the source snapshot ``_snap3_`` on the source volume ``_vs2.example.com:dept_eng_dp_mirror2_`` to /file3.new in the active file system of the restore destination volume ``_vs1.example.com:dept_eng_`` :

vs1.example.com::> snapmirror restore
-destination-path vs1.example.com:dept_eng
-source-path vs2.example.com:dept_eng_dp_mirror2
-source-snapshot snap3
-file-list /file3,@/file3.new
Warning: This command will overwrite any file on destination
"vs1.example.com:dept_eng" that has the same path as any of
the files to be restored.
Do you want to continue? {y|n}: y
[Job 36] Job is queued: snapmirror restore from source
"vs2.example.com:dept_eng_dp_mirror2" for the snapshot snap3.
vs1.example.com::>

The following example restores /file1, /file2, and /file3 from the source snapshot ``_snap3_`` on the source volume ``_vs2.example.com:dept_eng_dp_mirror2_`` respectively to /file1.new, /file2, and /file3.new in the active file system of the restore destination volume ``_vs1.example.com:dept_eng_`` :

vs1.example.com::> snapmirror restore
-destination-path vs1.example.com:dept_eng
-source-path vs2.example.com:dept_eng_dp_mirror2
-source-snapshot snap3
-file-list /file1,@/file1.new,/file2,/file3,@/file3.new
Warning: This command will overwrite any file on destination
"vs1.example.com:dept_eng" that has the same path as any of
the files to be restored.
Do you want to continue? {y|n}: y
[Job 36] Job is queued: snapmirror restore from source
"vs2.example.com:dept_eng_dp_mirror2" for the snapshot snap3.
vs1.example.com::>

== Related Links

* link:volume-quota-modify.html[volume quota modify]
* link:volume-snapshot-create.html[volume snapshot create]
* link:snapmirror-show.html[snapmirror show]
* link:snapmirror-update.html[snapmirror update]
* link:lun-delete.html[lun delete]
* link:vserver-nvme-namespace-delete.html[vserver nvme namespace delete]