SnapDrive for Windows - Drive Letter to LUN Mapping Config File

-

SnapDrive for Windows - Drive Letter to LUN Mapping Config File view 


SnapDrive doesn't maintain a text file or database containing the information you want.  Rather, if connects to the storage one demand and generates this data as needed comparing the current Windows LUN mounts to the current locations of the LUNs on storage.  Given you can move a LUN transparently at current levels of Data OnTap, the disk information needs to be dynamic.
 You can list the current disk mapping and underlying detail easily to a text file using the SnapDrive CLI.
 > sdcli disk list
 for example and you could periodically run that and save it off to a text file for reference.  You may have to preface the command with path information depending on your Windows PATH variable setting:
 > "C:\Program Files\NetApp\SnapDrive\sdcli" disk list
 assuming all default locations.  The SnapDrive command line is highly useful for automating common operations.

PS C:\Program Files\NetApp\SnapDrive> sdcli disk list
UNC Path: None
LUN Path: storage server name.com:/vol/lun path/lun_name
        Storage System:        storage server name.com
        Storage System Path:    storage server name.com:/vol/lun path/lun_name
        Type:                   lun
        Disk serial number:     805cL?GCK9j/
Backed by Snapshot Copy:
        Shared:                 No
        BootOrSystem Disk:      No
        SCSI port:              3
        Bus:                    0
        Target:                 0
        LUN:                    0
        Readonly:               No
        Size:                   14292 MB
        Snapmirror Source:      No
        Snapvault Primary:      No
        Disk Partition Style:   GUID Partition Table (GPT)
        Clone Split Restore status: Normal
        DiskID:                 3
        Volume Name:            \\?\Volume{a32d2ca8-7a06-4011-ae60-cdc23b25a7bc}\
        Mount points:           G:\
        IP Addresses:           10.13.0.2
iSCSI initiator:        iqn.1991-05.com.microsoft:server name.domainname.com

Comments

Post a Comment

Popular posts from this blog

Using Non-Maskable Interrupt (NMI) facilities to troubleshoot unresponsive VMware Virtual Machine.

-
Using Non-Maskable Interrupt (NMI) facilities to troubleshoot unresponsive VMware Virtual Machine. 1, Need to identify the ESXi host name, Where the hung VM running. 2, Login to ESXi server using Putty and run ‘vmdumper –l’ for find world id(wid) of the hung VM 3, Run ‘vmdumper <wid> nmi. 4, After send NMI signal, we can see dump creation in the VM console. 5. Export the System log on particular VM,
Read more

Removing invalid linked clone entries automatically using the ViewDBChk tool

-
Removing invalid linked clone entries automatically using the ViewDBChk tool in VMware Horizon View 5.3 and later versions (2118050) he ViewDbChk tool allows administrators to scan for and fix provisioning errors that can not be addressed using View Administrator C:\Program Files\VMware\VMware View\Server\tools\bin viewdbchk.cmd --scanMachines --desktopName Intertrust_Global_Desktop_x64 --limit 6 --force To run the View DbChk tool: If required, unzip the tool into a new folder. Click  Start  >  Run , type  cmd , and click  OK . The Command Prompt window opens. Navigate to the ViewDbChk tool: For version Horizon View 6.1,  ViewDbChk  is located under:  C:\Program Files\VMware\VMware View\Server\Tools\bin . For Horizon View 5.3 or 6.0, navigate to the folder created during the unzip process in step 1.   Enter  ViewDbChk  with the required flags as listed below into the command prompt to find and clean your database ...
Read more

VMTool update steps on Horizon VDI Parent VM

-
VMTool update steps on Horizon VDI Parent VM The order should be as follows: 1 - Turn on the parent VM  and login 2 - Uninstall VMware Horizon Agent and reboot 3 - Uninstall VMware Tools and reboot 4 - Delete the following registry keys and directories if applicable(dependant on Guest OS), then reboot the VM: HKEY_LOCAL_MACHINE\SOFTWARE\VMware, Inc.\VMware Tools HKEY_LOCAL_MACHINE\SOFTWARE\VMware, Inc.\VMware VDM <C:\Program Files\VMware\VMware View\*.*> <C:\Documents and Settings\All Users\Application Data\VMware\VDM\*.*>  <C:\Program Files\VMware\VMware Tools\*.*>  5  - Install VMware Tools, then reboot 6 - Install VMware Horizon Agent and reboot 7 - Log back in and open CMD and type ipconfig /release, then shutdown the VM 8  - Take a snapshot and recompose the pool =================================================================================== https://kb.vmware.com/s/article/2118048 installation order of End User Co...
Read more