Reverting use of DAOS tier 2 storage

HCL Domino does not currently provide an automated way to move DAOS objects from tier 2 storage to tier 1 storage. The following steps describe how to revert manually.

About this task

The overall steps are as follows. See the detailed steps for more information.

Disable DAOS tier 2.
Verify that there are objects in tier 2.
Copy all tier 2 objects to tier 1 storage.
Verify that DAOS no longer has tier 2 references.

Procedure

Disable DAOS tier 2 storage:
1. On the DAOS tab of the Server document, disable the DAOS Tier 2 field.
2. Restart the Domino server on which you made the change:
```
restart server
```
3. When the server comes back up, enter the following command at the server console:
```
tell daosmgr status
```
  Verify that the output says DAOS Tier2 is Read Only.
  Note: Although tier 2 is disabled, existing objects that are stored there can still be downloaded by Domino, because its object index is still aware that those objects are stored in tier 2. No additional objects will be pushed to tier 2 at this point, though.

Verify that there are DAOS objects in tier 2 by issuing the following command at the server console: .

tell daosmgr objectinfo summary

If the output indicates that there are no tier 2 objects, skip the remaining steps in this procedure. The following example output indicates that there are 32 tier 2 objects:

[1998:0002-082C] DAOS TIERED STORAGE SUMMARY
[1998:0002-082C] TIER 1 STORAGE:
[1998:0002-082C] 	OBJECTS      - 0
[1998:0002-082C] 	MB           - 0 MB
[1998:0002-082C] TIER 2 STORAGE:
[1998:0002-082C] 	OBJECTS      - 32
[1998:0002-082C] 	MB           - 70 MB
[1998:0002-082C] TOTAL STORAGE :
[1998:0002-082C] 	OBJECTS      - 32
[1998:0002-082C] 	MB           - 70 MB
[1998:0002-082C] 	AVERAGE AGE  - 1521 days

Copy all tier 2 objects to tier 1 storage, using one of the following options. You may want to use the second option if you have a large number of tier 2 objects so that you can "lazily" perform the copies, spreading them over separate commands that can be issued at times that are convenient for you.
Note: When objects are pulled from tier 2, if necessary, they are re-encrypted according to the configured DAOS encryption settings, which takes additional time.
Copy all objects with one command
1. Enter the following command at the Domino console:
```
 tell daosmgr objectpull all
```
  When the operation starts, it outputs this message to the console: DAOSMGR: Start OBJECTPULL all
  When the operation ends, it outputs this message to the console: DAOSMGR: End OBJECTPULL all
  There is no output for individual objects that are pulled. If there are no other servers that reference a tier 2 object, it is deleted after it is successfully pulled to tier 1.
  This command can take an extended period of time to execute since there might be a large number of tier 2 objects to be copied over the network. If the server shuts down while the operation is in progress, it aborts and will not be automatically restarted. In this case, you must re-enter the command after system restart.
Copy objects in stages
1. Enter the following command at the Domino console:
```
 tell daosmgr status
```
  In the section of output for DAOS Tier2, note the value listed for DAOS Tier2 days since last access before pushing. Here we will assume the value is 180 days. That means that any objects had to go at least 180 days since last being accessed before they were pushed to tier 2. It follows that the large majority of objects in tier 2 will be at least 180 days "old". Some may be "newer" if they were accessed after being pushed to tier 2, but this is typically rare. Thus you would use the value of 180 as a starting point for your commands below.
2. Enter the following command at the Domino console, using the starting value you identified:
```
tell daosmgr objectpull 180
```
  This causes DAOSmgr to pull any objects that were last accessed in 180 or fewer days to tier 1. This initial command may execute fairly quickly. Look for the message DAOSMGR: End OBJECTPULL 180 in the output, which indicates the command has completed.
3. Then progressively, over time, enter additional commands, gradually increasing the value. Wait for each command to complete before starting the next one. For example:
```
tell daosmgr objectpull 210
tell daosmgr objectpull 240
tell daosmgr objectpull 270
```
  These commands can take an extended period of time to execute since there might be a large number of tier 2 objects to be copied over the network. If the server shuts down while the operation is in progress, it aborts and will not be automatically restarted. In this case, you must re-enter the command after system restart.
  Search the console log for DAOSMGR: End OBJECTPULL to confirm completion before entering the next command. If the server has lots of tier 2 objects, enter the command and check the console log later for completion.

Verify that there are no longer tier 2 objects by issuing the following command at the server console:

tell daosmgr objectinfo summary

The output should indicate 0 tier 2 objects, for example:

[1D1C:0002-6170] DAOS TIERED STORAGE SUMMARY
[1D1C:0002-6170] TIER 1 STORAGE:
[1D1C:0002-6170]        OBJECTS      - 32
[1D1C:0002-6170]        MB           - 70 MB
[1D1C:0002-6170] TIER 2 STORAGE:
[1D1C:0002-6170]        OBJECTS      - 0
[1D1C:0002-6170]        MB           - 0 MB
[1D1C:0002-6170] TOTAL STORAGE :
[1D1C:0002-6170]        OBJECTS      - 32
[1D1C:0002-6170]        MB           - 70 MB
[1D1C:0002-6170]        AVERAGE AGE  - 1521 days