Adaptec 5325301656 Administration Guide - Page 81

Configuring Shares to iSCSI Disks, Mounting an iSCSI Disk Without a Drive Letter

Page 81 highlights

Configuring iSCSI Initiators Configuring Shares to iSCSI Disks When using the Microsoft initiator, shares to iSCSI disks may not automatically reconnect when the Windows system hosting the shares is rebooted. There are two methods to resolve this issue: • Share an iSCSI target that has an assigned drive letter. This method requires changes to the Windows registry and is described in Microsoft Knowledgebase article #870964. • Mount the iSCSI disk to a folder on an existing NTFS volume as described in "Mounting an iSCSI Disk Without a Drive Letter". This method does not require changes to the Windows registry and is described below. Mounting an iSCSI Disk Without a Drive Letter To complete this procedure, you must create and format an iSCSI target on the Snap Server and connect to this iSCSI disk using the Microsoft initiator. You must also have an existing NTFS volume on a local disk within the Windows server, initiating the connection. 1 Right-click My Computer and select Manage. 2 The new formatted volume will appear in the Disk Management window. 3 Right-click the New Volume and select Change Drive Letter and Paths.... 4 Click Remove in the Change Drive Letter and Paths for (New Volume) dialog, and click Yes to confirm drive letter removal. 5 Right-click the New Volume again and select Change Drive Letter and Paths.... 6 Select Add in the Change Drive Letter and Paths for (New Volume) dialog. 7 In the Add Drive Letter or Path dialog, select Mount in the following empty NTFS folder. 8 Create a folder or enter the path to the one that will be shared from the Windows server and select OK. 9 Select OK in the Add Drive Letter or Path dialog. This will return you to the Disk Management window. You will see the icon of a disk in place of the folder icon in the File Management window. 10 Create a share to the iSCSI disk in the standard method, then reboot the Windows machine and verify that the share is persistent. 67

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224

Configuring iSCSI Initiators
67
Configuring Shares to iSCSI Disks
When using the Microsoft initiator, shares to iSCSI disks may not automatically
reconnect when the Windows system hosting the shares is rebooted. There are two
methods to resolve this issue:
Share an iSCSI target that has an assigned drive letter. This method requires
changes to the Windows registry and is described in
Microsoft Knowledgebase
article #870964
.
Mount the iSCSI disk to a folder on an existing NTFS volume as described in
“Mounting an iSCSI Disk Without a Drive Letter”. This method does not require
changes to the Windows registry and is described below.
Mounting an iSCSI Disk Without a Drive Letter
To complete this procedure, you must create and format an iSCSI target on the Snap
Server and connect to this iSCSI disk using the Microsoft initiator. You must also
have an existing NTFS volume on a local disk within the Windows server, initiating
the connection.
1
Right-click My Computer and select
Manage
.
2
The new formatted volume will appear in the Disk Management window.
3
Right-click the
New Volume
and select
Change Drive Letter and Paths...
.
4
Click
Remove
in the Change Drive Letter and Paths for (New Volume) dialog,
and click
Yes
to confirm drive letter removal.
5
Right-click the
New Volume
again and select
Change Drive Letter and Paths...
.
6
Select
Add
in the Change Drive Letter and Paths for (New Volume) dialog.
7
In the Add Drive Letter or Path dialog, select
Mount in the following empty NTFS
folder
.
8
Create a folder or enter the path to the one that will be shared from the Windows
server and select
OK
.
9
Select
OK
in the Add Drive Letter or Path dialog. This will return you to the Disk
Management window.
You will see the icon of a disk in place of the folder icon in the File Management
window.
10
Create a share to the iSCSI disk in the standard method, then reboot the
Windows machine and verify that the share is persistent.