Create a network share for private data storage
Storage zones for ShareFile Data requires a network share for your private data. When multiple storage zones controllers are configured for high availability and load balancing within a zone, all controllers access the same shared location for private data.
Even if you store ShareFile files in a supported third-party storage system, storage zones controller requires a network share for encryption keys, queued files, other temporary items, and a storage cache for file uploads to or downloads from that storage system. For more information about the storage cache, see Customize storage cache operations.
Storage zones controllers access a network share using the IIS Account Pool user. By default, application pools operate under the Network Service user account, which has low-level user rights. Storage zones controller uses the Network Service account by default. You can use a named user account instead of the Network Service account to access the share. However, you should run the IIS application pool and the Citrix ShareFile Services using the Network Service account.
If you want to use a named user account instead of the Network Service account to access the share, create a named user account in Active Directory. We will refer to that named user account as the ShareFile Service account. Note: When you configure storage zones controller, you will specify the Network Share User Name and Network Share Password, which are the credentials for the account you will use to access the share, either the ShareFile Service account or the Network Service account.
To improve security, the admin will need to deny permissions to all other users to the particular folder containing the ShareFile storage repository and only give access to the storage location user that is being configured.
Connect to the server that will host the network share and create a folder for your ShareFile private data.
Right-click the folder and choose Share with specific people….
Add the account you will use to access the share (Network Service account or ShareFile Service account) and change the Permission Level to Read/Write.
Click Share and then click Done.
Right-click the folder and choose Properties.
On the Security tab, verify that the account you will use to access the share (Network Service account or ShareFile Service account) has Full Access permissions.
Increase the number of files per zone
By default, a storage zones controller configured to use a CIFS share stores all zone files in a single folder. As a result, the maximum number of files supported for a zone is limited by the maximum number of files per folder supported by your storage array.
You can configure storage zones controller to divide the persistent storage layout. This increases the maximum number of files per zone for some types of storage arrays from less than a half million to ten million or more. If you need even more capacity, you can change the default.
To enable storage zones controller to store files in multiple folders
Editing the Registry incorrectly can cause serious problems that may require you to reinstall your operating system. Citrix cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk. Be sure to back up the registry before you edit it.
On all storage zones controllers in the zone, update the value of the registry key
HKLM\Software\Wow6432Node\Citrix\storagezone\PathSelection from 0 to 1. If a storage zones controller registry does not include that key after an upgrade, add it.
Restart IIS on the storage zones controllers when you are finished editing the registry.
To increase the maximum number of folders
By default, divided storage layout has 256 top-level folders, each of which contains 256 folders. That configuration is represented in the primary storage zones controller registry key
The first value constrains the number of top-level folders to “16 to the power of 2” or 256. The second value also constrains the number of child folders of the top-level folders to 256.
Using that same formula (16 to the power of N) you can determine the appropriate values for your site. For example, PathSelectionParams=3,4,4,4 constrains the number of top-level folders to 4096 (16 to the power of 3). The second value constrains the child folders of the top-level folders to 65536 (16 to the power of 4). The third value constrains the child folders of the second-level folders to 65536, and so on.
Restart IIS on the primary and secondary storage zones controllers if you are finished editing the registry.
To remove empty folders
When storage zones controller stores files in multiple folders, file deletion can result in empty folders. By default, storage zones controller removes empty folders. The file delete service will delete empty folders, starting at the bottom of the tree and continuing up until it reaches a non-empty folder.
However, some upgrade paths might not update your settings. After an upgrade, verify that the following key appears in
<add key="DeleteEmptyFoldersAfterFileDeletion” value=“1”/>
If you need to add the key, restart the File Delete Service when you are finished.