Issuing an authentication ticket

You need to have the user issue authentication tickets with the commands shown below.

CAUTION:

This command must be run. If the command is not run, it will not be possible to obtain a dump file in the event of a failure during operations after a restore.
Save the created authentication ticket file for backup purposes. Keep the authentication ticket file safe to prevent leakage to a third party.

Issue an authentication ticket.

Run either of the following commands with the expiration time specified. Date and time of ticket issuance + valid period becomes the expiration time.

REST API: POST /v1/objects/tickets

CLI: ticket_create

After running the command, you will receive a response indicating the authentication ticket and expiration time.

If you receive no response after waiting approximately 1 minute, stop the CLI command forcibly with Ctrl+C, and then retry the operation. If the problem persists, contact the Hitachi design team.
Create an authentication ticket file from the issued authentication ticket.

In response to command execution of step 1, the system displays the expiration time and authentication ticket as shown below. Confirm the character string displayed at <authentication-ticket>, and then save the character string in a file.
- Example of output when the REST API is used:
```
{
  "ticket":"<authentication-ticket>",
  "expirationTime": "<expiration-time>"
}
```
- Example of output when the CLI is used (when the format option is omitted):
```
Ticket: <authentication-ticket>
Expiration Time: <expiration-time>
```
Note:
<authentication-ticket> does not include line breaks.
This completes the restore procedure.

Now that system operation is possible, ask the user to write back user data.

When I/O communication is not possible after restore operation, perform allocation of volumes to compute nodes again according to Canceling allocation of volumes to compute nodes (Bare metal) and Allocating volumes to compute nodes (Bare metal) in the VSP One SDS Block and SDS Cloud System Administration. When performing the allocation, rescan the storages on the compute nodes.

Notify the users that operation after restore differs from the operation at the time of backup.
- The following information that existed at the time of backup no longer exists in the post-restore environment because the information is outside the scope of the restore operation.
  - Event log
  - Audit log (Storage cluster only.)
  - Monitoring information
  - Job information
  - Dump log file
- The backed up information does not include information about user data encryption keys. If Data at rest encryption is used at the time of configuration backup, encryption keys are recreated during configuration restore. At this time, the maximum allowable number of encryption keys for the system are created regardless of the number of encryption keys that existed at the time of configuration backup. The created encryption keys may be allocated or deleted later. As a result, after configuration restoration, newly created encryption keys are allocated to the drives to which encryption keys were allocated at the time of configuration backup.
- The write I/O when writing back user data is the first write, and the write performance might be reduced. The performance in the area to which the user data is written back returns to the same level as that before backup.
  
  When data is not written to the whole area of a volume, a write I/O to the area to which data has not yet been written is the first write and the write performance might be reduced.
- For a license with an expiration date, the date is deemed to be a judgment criteria. Therefore, days in which the restore operation is being performed are included in the day count.
When event log KARS13300-W is output in step 13 of Restoring, request users to delete the Universal Replicator pair according to the VSP One SDS Block and SDS Cloud Universal Replicator, and then to recreate a Universal Replicator pair as necessary.