ADMINISTERING
Complete the steps in this procedure to enable DAOS tier 2 storage on a Domino server when your storage service is IBM Cloud Object Store.
Procedure
1. Complete the following steps to enable DAOS tier 2 storage in the Domino directory Server document:
c. In the DAOS Tier 2 field, selectEnable.
d. In the S3 Credential Name field, select the credential name from the Domino credential store to use to connect to the storage service specifed in Step 5 of the procedure Configuring a credential store for DAOS tier 2 storageBefore you enable DAOS tier 2 storage, configure a Domino credential store to store the credentials that are used for connections to the storage service.. For example, dominocos.
e. In the S3 Bucket field, enter the name of the bucket created in Step 2 of the procedure Configuring a credential store for DAOS tier 2 storageBefore you enable DAOS tier 2 storage, configure a Domino credential store to store the credentials that are used for connections to the storage service..
f. In the S3 Endpoint field, enter the endpoint to use to connect to the object storage service. For example:s3.us-south.cloud-object-storage.appdomain.cloud
g. In the S3 Region field, provide the region associated with the S3 Endpoint, for example:us-south
h. In the Push object to store if not accessed forfield, enter the number of days an attachment is not accessed for it to be put in tier 2 storage. Default is 180 days.
i. In the Push objects only between field, specify the range of time to push attachments to tier 2 storage. Default is between 2:00 AM and 5: AM.
j. Optional: In the Index T2 attachments field, selectEnable to rebuild full-text indexes for attachments stored in tier 2 when the indexer runs. By default, this option is disabled.
The server tests the DAOS tier 2 configuration. If the test is successful, the following output is shown at the server console:
AWS:AWSSelfTest: Success. AWS connection for DAOS is up and running.
If the test is not successful, the console shows an AWS:ProcessErrorerror. For example, if the bucket name is incorrect, the following error is shown:
AWS:ProcessError: 131 Exception NoSuchBucket: The specified bucket does not exist