Skip to main content
SnapCenter 4.9 cmdlets

Mount-SdSnapshot

Contributors
PDFs

Facilitates mounting the list of SMB shares from the specified Snapshot copy as a different set of shares. Facilitates mounting one LUN at a time from the specified Snapshot copy as a different LUN.
Mounting secondary LUN is not supported, Check Example 9

Syntax

Mount-SdSnapshot [-Path]  <Object[]>  [-Snapshot]  <String>  [-StorageSystem]  <String>  [-VolumeName]  <String>  [-PrefixForVolumeClone]  <String>  [-MountPath]  <Object[]>  [-SharedDisk]  <>  [-ClusteredSharedVolume]  <>  [-AutopickMountPoint]  <>  [-ValidateCloneDepth]  <>  [-Session]  <String>  [-Host]  <String>

Detailed Description

Facilitates mounting the list of SMB shares from the specified Snapshot copy as a different set of shares. Facilitates mounting one LUN at a time from the specified Snapshot copy as a different LUN.You can use this cmdlet to perform backup verification. Mount the database and log shares/LUN from the Snapshot copy and perform the verification operations. For SMB shares, the mounted share names are automatically appended with a unique identifier. For a LUN, the cloned volume name is automatically appended with a unique identifier, while the LUN name remains the same.For example:If the original share is \\SQLFileServer\DBShare, the mounted share name is \\SQLFileServer\DBShare-GUID. (\\SQLFileServer\DBShare-73111E50-E7C2-49B7-8A63-7279512CB09B)If the original LUN is PrimarySVM:/vol/SCE_VOL/lun1, the mounted LUN name is PrimarySVM:/vol/SCE_VOLGUID/lun1. (PrimarySVM:/vol/SCE_VOLSiClone2b77c074_1d9b_4929_9fac_d361bf342794/lun1)The ACLs on the mounted share are the same as the original share. To mount the shares or a LUN from a secondary Snapshot copy, you must specify the storage system and volume.Ensure that the aggregate of the volume that is the source of the FlexClone operation is assigned to the virtual storage server aggregates list.For the 'Path' parameter below, if file system path of the LUN is specified, it can be mounted on the same host as the source LUN. If the complete storage path of the LUN is specified, it can be mounted on the same host or on a different host.To mount the LUN on a different host, an igroup and an iSCSI session should to be present for the host that is accessing the SVM, where the source LUN is present.Related cmdlets: Get-SdSnapshot, Remove-SdSnapshot, Rename-SdSnapshot, New-SdSnapshot, Dismount-SdSnapshot

Parameters

Name Description Required? Pipeline Input Default Value

Path

Specifies a comma-separated list of shares you want to mount from the Snapshot copy.Only one LUN can be mounted at a time. For a LUN, this parameter specifies one value which is the file system path of the LUN in the host machine or the complete storage path of the LUN in the SVM.You cannot mix a logical disk or mount point with SMB shares in the same input path.

true

true (ByPropertyName)

Snapshot

Indicates the Snapshot copy that you want to use for mounting the SMB shares/LUN. For SMB shares, you must use a Snapshot copy that is valid for all the shares in your list.

true

true (ByPropertyName)

StorageSystem

Indicates the name of the storage system in which the Snapshot copy you want to mount is located.

false

true (ByPropertyName)

VolumeName

Indicates the name of the storage system volume in which the Snapshot copy you want to mount is located.

false

true (ByPropertyName)

PrefixForVolumeClone

You can use this optional parameter to set a short name for the share on which the Snapshot copy is mounted. For LUNs, use this parameter to prefix the cloned volume name. Use this parameter when you are working on a system with name length restrictions.

false

true (ByPropertyName)

MountPath

Indicates the drive letter or mountpoint that you want to assign to the disk mounted from the Snapshot copy. For a LUN mount operation, this parameter takes only one destination value.

false

true (ByPropertyName)

SharedDisk

false

true (ByPropertyName)

ClusteredSharedVolume

false

true (ByPropertyName)

AutopickMountPoint

Specifies that the mountpoint is assigned automatically.

false

true (ByPropertyName)

ValidateCloneDepth

false

false

Session

false

true (ByPropertyName)

Host

Specifies the name or IP address of the host on which you execute the operation. For SMB shares, the default is your local machine. For a LUN, this parameter must be provided with the hostname.

false

true (ByPropertyName)

Examples

Example 1: Mounting shares from a specified backup

 PS C:\> Mount-SdSnapshot -Path "\\SQLFileserver\DBShare","\\SQLFileserver\LogShare" -snapshot "weekly_backup"

This example syntax mounts your shares from "weekly_backup".

OriginalResource MountedResource
============== ===============
\\SQLFileserver\DBShare \\SQLFileserver\DBShare-A470FF3A-5107-4B6A-B0C1-FB3D8744F14C
\\SQLFileserver\LogShare \\SQLFileserver\DBShare-E6980DF6-3E64-45BD-965A-7F7A9B02156A

Example 2: Mounting shares from piped Snapshot copies that start with "weekly" in the name.

 PS C:\> Get-SdSnapshot \\SQLFileserver\DBShare -Snapshot weekly* | Mount-SdSnapshot  "\\SQLFileserver\dbshare","\\SQLFileserver\logshare"

This example syntax mounts specified shares from Snapshot copies that start with "weekly." The shares you want to mount must be on the same volume.

OriginalResource MountedResource
============== ===============
\\SQLFileserver\DBShare \\SQLFileserver\DBShare-A470FF3A-5107-4B6A-B0C1-FB3D8744F14C
\\SQLFileserver\LogShare \\SQLFileserver \DBShareE6980DF6-3E64-45BD-965A-7F7A9B02156A

Example 3: Mounting shares from the specified secondary Snapshot copy

 PS C:\> Mount-SdSnapshot -Path "\\SQLFileserver\DBShare","\\SQLFileserver\LogShare" -snapshot "weekly_snap" -storagesystem mirror_vserver -volume dbmirrorvolume

This example mounts the specified shares from the specified secondary Snapshot copy.

OriginalResource MountedResource
================ ===============
\\SQLFileserver\DBShare \\DRSQLFileServer\DBShare-A470FF3A-5107-4B6A-B0C1-FB3D8744F14C
\\SQLFileserver\LogShare \\DRSQLFileServer\DBShare-E6980DF6-3E64-45BD-965A-7F7A9B02156A

Example 4: Mounting shares using a prefix

 PS C:\> Mount-SdSnapshot -Path \\172.17.165.40\capital_vol_share -Snapshot Newtest -PrefixForVolumeClone capitalShare

This example syntax creates a short name for the share on which you mount the Snapshot copy.

Resource ConnectedResource
-------- -----------------
\\172.17.165.40\capital_vol_share \\JENKINS-CIFS\capitalShare030713155542929

Example 5: Mounting a LUN from a specified Snapshot with file system path.

 PS C:\> Mount-SdSnapshot -Path L:  -Snapshot Host1_DMN_COM_SLDB3_Host1_06-10-2020_02.51.43.9645 -MountPath I: -Host Host1.DMN.COM

This example syntax mounts the Snapshot copy specified for the LUN in L: onto I: on the host Host1.DMN.COM.

Resource ConnectedResource
-------- -----------------
L:\ I:\

Example 6: Mounting a LUN from a specified Snapshot with AutoMount option

 PS C:\> Mount-SdSnapshot -Path L:  -Snapshot Host1_DMN_COM_SLDB3_Host1_06-10-2020_02.51.43.9645 -AutopickMountPoint -Host Host1.DMN.COM

This example syntax mounts the Snapshot copy specified for the LUN in L: onto the automount location "C:\scmnpt\mpdisk0002\" on the host Host1.DMN.COM.

Resource ConnectedResource
-------- -----------------
L:\ C:\scmnpt\mpdisk0002\

Example 7: Mounting a LUN to a different host with LUN storage path

 PS C:\> Mount-SdSnapshot -Path PrimarySVM:/vol/SCE_VOL/lun1  -Snapshot Host1_DMN_COM_SLDB3_Host1_06-10-2020_02.51.43.9645 -MountPath I: -Host Host2.DMN.COM

This example syntax specifies the storage path of the LUN mounted on Host1 and mounts the Snapshot copy onto I: on the host Host2.DMN.COM. The cmdlet is executed on Host2.DMN.COM.

Resource ConnectedResource
-------- -----------------
L:\ I:\

Example 8: Mounting a LUN with LUN storage path using Primary SVM

 PS C:\>  Mount-SdSnapshot -Path Primary_SVM:/vol/Volume_Vault/Volume_Vault_Lun1 -Snapshot R70105EC0A5V1_SQL2019_SQL_DB1_R70105EC0A5V1_03-15-2021_22.37.23.2993_1 -PrefixForVolumeClone Clone_01292021_2330 –AutopickMountPoint -Verbose

This example syntax specifies the storage path of the Primary LUN mounted and mounts the Snapshot copy onto random drive letter on the same host using Primary Storage . The cmdlet is executed on Host1.

VERBOSE: Validating input paths.
VERBOSE: LUN: Primary_SVM:/vol/Volume_Vault/Volume_Vault_Lun1
VERBOSE: The Snapshot 'R70105EC0A5V1_SQL2019_SQL_DB1_R70105EC0A5V1_03-15-2021_22.37.23.2993_1' of Primary_SVM:/vol/Volume_Vault/Volume_Vault_Lun1 will be mounted.
VERBOSE: Drive letter if available or a mount point will be auto-picked
VERBOSE: Mounting the specified resources from the Snapshot copy.
VERBOSE: Operation successful.
Resource   ConnectedResource
--------   -----------------
Primary_SVM:/vol/Volume_Vault/Volume_Vault_Lun1   C:\scmnpt\mpdisk0006\

Example 9: Mounting a LUN with LUN storage path using Secondary Storage fails

 PS C:\>  Mount-SdSnapshot -Path Secondary_SVM:/vol/Volume_Secondary_Vault/Volume_Secondary_Vault_Lun1 -Snapshot BCHExchDAG2016_Backup_kdcbchexch1_01-29-2021_23.30.20.2845 -PrefixForVolumeClone Clone_01292021_2330 –AutopickMountPoint

This example syntax specifies the storage path of the LUN mounted and trying to mount the Snapshot copy with random drive letter on the any host using Secondary Storage . The cmdlet is executed on Host1.

Mount-SdSnapshot : Failed to mount the Snapshot copy.Failed to mount the resource: Secondary_SVM:/vol/Volume_Secondary_Vault/Volume_Secondary_Vault_Lun1 from snapshot: BCHExchDAG2016_Backup_kdcbchexch1_01-29-2021_23.30.20.2845.
The source LUN's iGroup does not exist.
Possible Resolution: Make sure that Host to storage connectivity is available.
At line:1 char:1
+ Mount-SdSnapshot -Path Secondary_SVM:/vol/Volume_Secondary_Vault/Volume_Secondary_Vault_Lun1 ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo  : InvalidResult: (SnapDrive.Clien...MountSdSnapshot:MountSdSnapshot) [Mount-SdSnapshot], Exception
+ FullyQualifiedErrorId : 102,SnapDrive.Client.PSModule.MountSdSnapshot