StoragePoint 6.4 - Azure Adapter Guide

Name

Enter the unique name of the Storage or Backup Endpoint.

Type

Primary – this endpoint will be available for externalization when creating storage profiles.

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

Online – Storage Endpoint should be available to associate to a Storage Profile and accept BLOBs. (default)

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.

Select the adapter for the endpoint that is being created.

(yes/no) – Determines whether or not the adapter negotiates an SSL connection for all data (and metadata) transfers. Default = No.

This is the name you gave your application in the Azure web UI.

This is the top level container name in which the profile blobs are stored in Azure. It must be lower case and may NOT include the underscore character. This container will be created by the adapter automatically. You may create a different name for each profile.

This is the Primary or Secondary storage key of your storage application in the Azure Web UI

None – no retries.

N,{max} – where {max} is the number of times you want it to retry the operation. N,2 is the default value if this parameter is not supplied.

ExponentialN,{max} – the same as N,{max} except the delays between retries will become exponentially larger.

(Yes/No)  If UseSSL is Yes, the StrictSSL flag controls whether or not the use of "self-issued" or otherwise suspicious certificates on the Azure system will be tolerated. Note that the default certificate out of the box with Azure is self-issued and will not work unless this flag is set to No (default).

The amount of seconds to wait for operations to complete before forcing a timeout. Default = 300.

If the endpoint is on a WORM (Write Once, Read Many) device, Unused BLOB Cleanup will ignore this endpoint.

No – Externalized content BLOBs are not placed in folders (default).

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.

The Test Storage Settings button can be used at this point, or after completing the endpoint configuration, to verify that the endpoint is accessible. For some adapters, testing the connection will create the container if it doesn't already exist.

No – Externalized content BLOBs are not compressed (default).

Yes – Externalized content BLOBs are compressed.

None – Encryption will not be applied to externalized BLOBs (default).

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.

Enter a passphrase to use when generating the encryption key. Using a passphrase will help you re-create the encryption key if necessary. You can generate a random key by leaving the box blank and clicking the Generate Key button. The encryption key passphrase will be hidden.

A warning email can be sent if it encounters errors.

An online storage endpoint can be automatically taken offline if it encounters errors. If a storage endpoint is taken offline automatically, BLOBs that were intended to be written to that endpoint will go to the content database.

Default email addresses for system error and offline notification can be entered. Check the box to include the list of Default Notification Contacts specified on the General Settings page.

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.

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.