HP StoreOnce D2D4324 HP StoreOnce VSA user guide (TC458-96002, July 2013) - Page 37

Creating a CIFS share, A note about permissions

Page 37 highlights

3. You will be advised that if you update the Share settings, any backup or restore jobs in progress for it will fail. Click Yes (or No). When the changes are applied they will take effect immediately. If the NAS server (service) needs to restart, there will be a warning provided to the user, which they can accept to allow all shares to temporarily go offline. Note that you cannot change the share name once it has been created. If a share is converted from Read/Write to Read Only, any open items will be force closed which may result in inconsistencies if they are being written to by a backup application. The user will be warned that this could occur before the change is made. Deleting share details Users with an Admin login may delete a share. Select the share in the list and click Delete. Creating a CIFS share A note about permissions Each share also has a Permissions tab. The options available on this tab depend upon the type of Authentication that you selected when you configured the CIFS Server. • If No Authentication was selected, the Permissions tab is disabled. • If User Authentication was selected, there will be a list of users and you may set the access permissions for that share for each user in the list to Access or No Access. See Configuring user authentication (page 34) for a worked example. • If AD Authentication was selected, share permissions are managed from the AD Domain. See Configuring CIFS Server with AD and CIFS Share with AD domain users (page 39) for a worked example. Shares (NAS) 37

  • 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

3.
You will be advised that if you update the Share settings, any backup or restore jobs in progress
for it will fail. Click
Yes
(or
No
).
When the changes are applied they will take effect immediately. If the NAS server (service)
needs to restart, there will be a warning provided to the user, which they can accept to allow
all shares to temporarily go offline. Note that you cannot change the share name once it has
been created.
If a share is converted from Read/Write to Read Only, any open items will be force closed
which may result in inconsistencies if they are being written to by a backup application. The
user will be warned that this could occur before the change is made.
Deleting share details
Users with an Admin login may delete a share.
Select the share in the list and click
Delete
.
Creating a CIFS share
A note about permissions
Each share also has a
Permissions
tab. The options available on this tab depend upon the type of
Authentication
that you selected when you configured the CIFS Server.
If
No Authentication
was selected, the
Permissions
tab is disabled.
If
User Authentication
was selected, there will be a list of users and you may set the access
permissions for that share for each user in the list to
Access
or
No Access
. See Configuring
user authentication (page 34) for a worked example.
If
AD Authentication
was selected, share permissions are managed from the AD Domain. See
Configuring CIFS Server with AD and CIFS Share with AD domain users (page 39) for a
worked example.
Shares (NAS)
37