Adaptec 5325301638 Administration Guide - Page 62

Creating Shares, Guidelines, Maintain at Least One Share at the Root of Each Volume, Hidden Shares - direct cd

Page 62 highlights

Creating Shares Creating Shares Shares are created, viewed, edited, and deleted from the Storage > Shares screen of the Administration Tool. The default share (SHARE1) maps to the root of the volume and grants access to all users and groups over all protocols. As a security measure, disable any protocols not required for your network environment. Guidelines Consider the following guidelines when creating or deleting shares. Maintain at Least One Share at the Root of Each Volume A share to the root of a volume is required for backup purposes. Security for any share at the root of the volume should be given special consideration. Any user or group that has access to the root of a volume will have access to EVERY file and subdirectory on that volume unless there is a specific ACL in place precluding that access. In general, access to a share at the root of a volume should only be granted to a system administrator or backup operator. Hidden Shares A hidden share is hidden from clients connecting from the SMB, HTTP, AFP, and FTP (but not NFS) protocols. For example, assume SHARE1 is set as hidden. Windows users will not see the share when viewing the server through Network Neighborhood, or when performing a net view \\servername on the Snap Server. Tip Windows users who have access rights to a hidden share can still access the share by entering the precise path to the share directly into their file system viewer. For example, Windows users could enter an address of the format \\server_name\hidden_ share_name to access a hidden share. Likewise, FTP clients will still be able to "cd" directly into the folder to which the share points if they know the precise path. This method will not work, however, for Macintosh clients, to whom a hidden share is always inaccessible. Snapshot Shares A snapshot share provides access to all current snapshots of a volume. Just as a share provides access to a portion of a live volume, a snapshot share provides access to the same portion of the file system on any archived snapshots of the volume. You create a snapshot share by selecting the Create Snapshot Share check box in the course of creating or editing a share. 48 Snap Server Administrator Guide

  • 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

Creating Shares
48
Snap Server Administrator Guide
Creating Shares
Shares are created, viewed, edited, and deleted from the
Storage > Shares
screen of
the Administration Tool. The default share (SHARE1) maps to the root of the
volume and grants access to all users and groups over all protocols. As a security
measure, disable any protocols not required for your network environment.
Guidelines
Consider the following guidelines when creating or deleting shares.
Maintain at Least One Share at the Root of Each Volume
A share to the root of a volume is required for backup purposes. Security for any
share at the root of the volume should be given special consideration. Any user or
group that has access to the root of a volume will have access to EVERY file and
subdirectory on that volume unless there is a specific ACL in place precluding that
access. In general, access to a share at the root of a volume should only be granted to
a system administrator or backup operator.
Hidden Shares
A
hidden
share is hidden from clients connecting from the SMB, HTTP, AFP, and
FTP (but not NFS) protocols. For example, assume SHARE1 is set as hidden.
Windows users will not see the share when viewing the server through Network
Neighborhood, or when performing a
net view \\servername
on the Snap Server.
Tip
Windows users who have access rights to a hidden share can still access the
share by entering the precise path to the share directly into their file system viewer.
For example, Windows users could enter an address of the format
\\server_name\hidden_ share_name
to access a hidden share. Likewise, FTP
clients will still be able to “cd” directly into the folder to which the share points if
they know the precise path. This method will not work, however, for Macintosh
clients, to whom a hidden share is always inaccessible.
Snapshot Shares
A
snapshot
share
provides access to all current snapshots of a volume. Just as a share
provides access to a portion of a live volume, a snapshot share provides access to
the same portion of the file system on any archived snapshots of the volume. You
create a snapshot share by selecting the
Create Snapshot Share
check box in the course
of creating or editing a share.