This section will provide you details on how to configure a storage endpoints connection string to utilize the Centera Adapter. Please refer to the StoragePoint Reference Guide for information on managing Storage Endpoints.
On the Application Management page, click Storage and Backup Endpoints.
Click Create New Endpoint or click the name of an existing storage endpoint that you want to edit.
Setting Value/Options | ||
---|---|---|
Name | ||
Type Backup this endpoint will be in the Backup Services dropdown on the profile page. The selection is locked down when saving. See Backup Services Settings in the Reference Guide for more information on how Backup Endpoints are used. | ||
Status Offline (Read Only) A storage endpoint can be configured, but not made available for externalizing content. The BLOBs already on the endpoint are still read only. | ||
| ||
Where examples of the cluster address could be any of the following: Without PEA (Pool Entry Authorization) file ADDRESS=centera.denallix.com
With PEA file See Appendix A for more information. ADDRESS=128.221.200.56?us1_profile1_rwqe.pea Required. | ||
None [DateFormat] example: Retention=08/31/2009;
[Duration][Interval] example: Retention=5D; [Interval] may be days (D), months (M) or years (Y).
| ||
| ||
Yes Externalized content BLOBs are placed in folders. If Folder Content in BLOB Store is Yes then you can select a date/time folder scheme from the dropdown. YYYY/MM/DD/HH/MM is the default. | ||
| ||
Yes Externalized content BLOBs are compressed. | ||
AES (128 bit) 128 bit AES encryption will be applied to externalized BLOBs. AES (256 bit) 256 bit AES encryption will be applied to externalized BLOBs. | ||
| ||
| ||
| ||
|
Click the Show Connection String checkbox to edit the connection string. Otherwise, fill in the connection fields shown for the adapter selected. Notice that the connection string parameters are name/value pairs separated by semi-colons when editing using the Show Connection String option.
|
NOTE: Adapter parameters are not case-sensitive. |
|
NOTE: You should always use a passphrase when generating encryption keys. The passphrase gives you a means of re-creating keys should they become unrecoverable or corrupt. It is very important to remember or record the passphrase outside of StoragePoint. Otherwise, encrypted content could become irretrievable in the event of a database failure. |
If you choose to externalize content you should test the storage profile settings by clicking the Test Storage Settings button. A message under the button will indicate whether or not the test was successful. If the test fails the message will include the error that was the root cause of the failure.
|
NOTE: When testing access to an endpoint from within Central Administration, the Identity of the Application Pool hosting the Central Administration Site is the one that is being used for the test. If there are different Identities used for other Web Applications in the Farm then those identities will also need access but cannot be tested from within Central Admin itself. See BLOB Store Security and StoragePoint Required Privileges in the StoragePoint Reference Guide. |
A client connection to a Centera system typically involves two pieces.
The first is the IP address or host name of the cluster itself.
The second is typically a ".pea" file which contains detailed authentication and rights information.
Here is an example: "192.168.1.10?d:\my_conn.pea"
Clients using the Centera API (this includes the StoragePoint Adapter for Centera) use a .pea file when connecting with Centera.
Each client machine (think "server in the farm") *must* have a copy of the *same* .pea file accessible for use in a consistent location. This file must also be on the machine hosting SharePoint Central Administration.
For example if the pea file used to connect is located at "D:\my_conn.pea" on one Farm machine then it must be similarly located and named on *all* Farm machines.
File system access to the pea file must be granted to the process and service identities of SharePoint. This file will be read when connecting to Centera.
(This requirement is similar to the set of identities that would be configured on a file share in the case of the built-in FileSystem adapter.)
For more information about .pea files, please see your Centera documentation.
© ALL RIGHTS RESERVED. Feedback Términos de uso Privacidad Cookie Preference Center