HP StoreOnce 4430 HP StoreOnce Backup System Concepts and Configuration Guidel - Page 72

Maximum number of users per CIFS share, CIFS share authentication, Backup application configuration

Get HP StoreOnce 4430 PDF manuals and user guides View all HP StoreOnce 4430 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 72 highlights

There are also limits on the number of open files greater than the deduplication threshold that are allowed per share and per appliance. These are the files that hold the backed-up data. Backup applications generally create a small number of additional files during a backup job in order to store configuration details and catalog entries. Some of these small files will generally be updated throughout the backup process and, in most instances, these files will be below the deduplication threshold. So, there is also a maximum number of open files that are the same size or smaller than the deduplication threshold that are allowed per appliance. See Key parameters (page 115). Maximum number of users per CIFS share The maximum number of users that may be configured when using "user" or AD authentication for access to a CIFS share is 50. This maximum is the total number of users per CIFS server and also the maximum that can be allocated access to any single CIFS share Different users may access single NAS shares simultaneously, however, a file within a share may only be opened by one user at a time. Maximum number of hosts per NFS share The maximum number of host systems that may be configured to access an NFS share is 50. This maximum is the total number of hosts per NFS server and also the maximum that can be allocated access to any single NAS share. A file within a share may only be opened by one user at a time. CIFS share authentication The StoreOnce device provides three possible authentication options for the CIFS server: • None - All shares created are accessible to any user from any client (least secure). • User - Local (StoreOnce) User account authentication. • AD - Active Directory User account authentication. None - This authentication mode requires no username or password authentication and is the simplest configuration. Backup applications will always be able to use shares configured in this mode with no changes to either server or backup application configuration. However this mode provides no data security as anyone can access the shares and add or delete data. User - In this mode it is possible to create "local StoreOnce users" from the StoreOnce management interface. This mode requires the configuration of a respective local user on the backup application media server as well as configuration changes to the backup application services. Individual users can then be assigned access to individual shares on the StoreOnce appliance. This authentication mode is ONLY recommended when the backup application media server is not a member of an AD Domain. AD - In this mode the StoreOnce CIFS server becomes a member of an Active Directory Domain. In order to join an AD domain the user needs to provide credentials of a user who has permission to add computers and users to the AD domain. After joining an AD Domain access to each share is controlled by Domain Management tools and domain users or groups can be given access to individual shares on the StoreOnce appliance. This is the recommended authentication mode if the backup application media server is a member of an AD domain. It is the preferred option. Refer to the "HP StoreOnce Backup system user guide" for more information about configuring authentication. Backup application configuration The HP StoreOnce Backup system NAS functionality is designed to be used with backup applications that create large "backup files" containing all of the server backup data rather than applications that simply copy the file system contents to a share. 72 NAS shares

  • 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
There are also limits on the number of open files greater than the deduplication threshold that are
allowed per share and per appliance. These are the files that hold the backed-up data.
Backup applications generally create a small number of additional files during a backup job in
order to store configuration details and catalog entries. Some of these small files will generally be
updated throughout the backup process and, in most instances, these files will be below the
deduplication threshold. So, there is also a maximum number of open files that are the same size
or smaller than the deduplication threshold that are allowed per appliance. See
Key
parameters (page 115)
.
Maximum number of users per CIFS share
The maximum number of users that may be configured when using “user” or AD authentication for
access to a CIFS share is 50. This maximum is the total number of users per CIFS server and also
the maximum that can be allocated access to any single CIFS share
Different users may access single NAS shares simultaneously, however, a file within a share may
only be opened by one user at a time.
Maximum number of hosts per NFS share
The maximum number of host systems that may be configured to access an NFS share is 50.
This maximum is the total number of hosts per NFS server and also the maximum that can be
allocated access to any single NAS share. A file within a share may only be opened by one user
at a time.
CIFS share authentication
The StoreOnce device provides three possible authentication options for the CIFS server:
•
None – All shares created are accessible to any user from any client (least secure).
•
User – Local (StoreOnce) User account authentication.
•
AD – Active Directory User account authentication.
None
– This authentication mode requires no username or password authentication and is the
simplest configuration. Backup applications will always be able to use shares configured in this
mode with no changes to either server or backup application configuration. However this mode
provides no data security as anyone can access the shares and add or delete data.
User
– In this mode it is possible to create “local StoreOnce users” from the StoreOnce management
interface. This mode requires the configuration of a respective local user on the backup application
media server as well as configuration changes to the backup application services. Individual users
can then be assigned access to individual shares on the StoreOnce appliance. This authentication
mode is ONLY recommended when the backup application media server is not a member of an
AD Domain.
AD
– In this mode the StoreOnce CIFS server becomes a member of an Active Directory Domain.
In order to join an AD domain the user needs to provide credentials of a user who has permission
to add computers and users to the AD domain. After joining an AD Domain access to each share
is controlled by Domain Management tools and domain users or groups can be given access to
individual shares on the StoreOnce appliance. This is the recommended authentication mode if
the backup application media server is a member of an AD domain. It is the preferred option.
Refer to the “HP StoreOnce Backup system user guide” for more information about configuring
authentication.
Backup application configuration
The HP StoreOnce Backup system NAS functionality is designed to be used with backup applications
that create large “backup files” containing all of the server backup data rather than applications
that simply copy the file system contents to a share.
72
NAS shares