Collecting information required for restore

This section describes how to collect the following information required for restore.

clusterId of the storage cluster to be restored
Username for ticket authentication
sha256 hash of the password for ticket authentication
SSH public key

CAUTION:

Collect the information required for restore, and then have customer support issue two Rescue tickets for the storage cluster to be restored.

Note:

If you are requested to collect the information by customer support after you asked customer support to issue the tickets, perform the following procedure in parallel with the subsequent procedure of Reinstalling the storage cluster.

[On the controller node] Obtain the clusterId of the storage cluster to be restored. Unzip and extract a configuration backup file. You can obtain the clusterId by referring to clusterID stored in the configuration backup file.

If the controller node OS is Linux:

$ tar xvfO \
hsds_config_backup_<internalID>_<VERSION>_<YYYYMMDD>_<hhmmss>.tar \
--wildcards */data.tar | tar xvO --wildcards */clusterID

If the controller node OS is Windows:

> tar xvf ` 
hsds_config_backup_<internalID>_<VERSION>_<YYYYMMDD>_<hhmmss>.tar
> tar xvf `
hsds_config_backup_<internalID>_<VERSION>_<YYYYMMDD>_<hhmmss>/data.tar
> cat data/clusterID

[On the controller node] Specify a username and password for ticket authentication.

The username and password for ticket authentication that you specified here will be used as options for the quiescent point setting command that is described later in the restore procedure.
Note:
Characters that can be used for a username and password for ticket authentication are as follows:
- Username:
  - Number of characters: 6 to 255
  - Usable character types: Numbers (0 to 9), upper-case alphabet (A to Z), lower-case alphabet (a to z), symbols (! # $ & % ' - . @ ^ _ ` { } ~)
- Password:
  - Number of characters: 8 to 256
  - Usable character types: Numbers (0 to 9), upper-case alphabet (A to Z), lower-case alphabet (a to z), symbols (! " # $ % & ' ( ) * + , - . / : ; < = > ? @ [ \ ] ^ _ ` { | } ~)
[On the controller node] Obtain the sha256 hash of the password for ticket authentication.

CAUTION:

When you obtain the hash value, verify that it does not include line breaks.

The following example shows how to obtain the sha256 hash of the password when the OS is Linux and you specify "password" as a password.
```
$ echo -n password | sha256sum | cut -d ' ' -f 1
5e884898da28047151d0e56f8dc6292773603d0d6aabbdd62a11ef721d1542d8
```
The following example shows how to obtain the sha256 hash of the password when the OS is Windows and you specify "password" as a password.
```
[string]::concat(([security.cryptography.SHA256]::create().computehash([text.encoding]::ascii.getbytes("password"))|%{$_.tostring("x2")}))
5e884898da28047151d0e56f8dc6292773603d0d6aabbdd62a11ef721d1542d8
```

[On the controller node] Obtain a public key and private key for SSH.

CAUTION:

Use the ssh-keygen command.
Use ED25519 of key length 256 as an encryption method.
Do not use a passphrase.
Comments are optional. If necessary, use the -C option to specify a comment.

The following is an example of key generation.

$ ssh-keygen -t ed25519
Generating public/private ed25519 key pair.
Enter file in which to save the key (/home/user/.ssh/id_ed25519):sample_ed25519 ¹
Enter passphrase (empty for no passphrase): ²
Enter same passphrase again: ²
$ ls sample_ed25519* ¹
sample_ed25519 sample_ed25519.pub

1. You can specify any name. The name in the example is sample_ed25519. 
2. Do not enter a passphrase.

Collect and send required information to customer support, and then have customer support issue two Rescue tickets.
Store the issued ticket files in the directory where restore commands are run on the controller node.

Ticket names are as follows:
- ticket_for_initialization: Ticket to be used for storage system initialization
- ticket_for_restore: Ticket to be used for storage cluster restore after storage system initialization