Resolution:

No, you have to use same members name while running recovery. You can not use different names. If you change the name, AS will not able to find the SN files and it will create new SN files as-agent name (member names).

=======================================================

as-admin help will provide a list of recovery commands. A detailed description of the as-admin command "recover metaspace" follows.

 recover space <string>
     [recovery_policy <string>]
     [quorum <integer>] [keep_files <boolean>]
     [(with|without) data]

recover metaspace
         [recovery_policy <string>]
         [quorum <integer>] [keep_files <boolean>]
         [thread_count <integer>]
         [(with|without) data]


[recovery_policy <string>]
New parameter to define the policy to use during recovery. There are several recovery policies as part of recovery options available when shared-nothing persistence is implemented and recovery is issued and the policy determines when and how recovery can be made. The policy value can be:

no_data:  
Recover the space without any data. This is the same as "recover space without data" in previous releases.

data_loss:  
Recover the space with available data from each seeder. If recovery is done with missing seeders, there is a potential for data loss, because not all members are started to ensure that all data is recovered. This policy ensures best effort recovery with available data.

no_data_loss:  
Recover the space only if there are enough members to be able to recover the data before shutdown. If there are not enough seeders to recover the previous state of the cluster, recovery throws an exception. This is the same as "recover space with data" in previous releases.

exact_cluster:  
Recover the space only if all of the members that were active before the shutdown are available in the cluster. This policy enables fast recovery. If there are more or less cluster members than before the shutdown, recovery throws an exception.

robust_load_only:
available since AS2.1.4HF3 (AS-3651)
You can now enter the recover space command with a recovery policy of "robust_load_only."

For example, enter:

recover space "persisted_space" recovery_policy "robust_load_only"

Note: The previous form of the command-recover space with data is still supported, but will be deprecated.

[quorum <integer>]
Defines the number of Seeders must be available before start recovering.

Note: Starting with release 2.1.4, the quorum attribute for recover space with data, which specifies the number of seeders required before ActiveSpaces initiates loading of the space when a recovery is done, is no longer required. However, you can still pass the quorum value with recover command or in the recovery options in the API. ActiveSpaces stores the seeder information in the shared-nothing persistence file and uses the information at startup/restart to perform recovery (recover still needs to be issued manually using the API or as-admin).

[keep_files <boolean>]
Default behavior is "false" meaning old persistence files will be deleted after recovery (unless there is a failure during recovery). If keep_files is set to "true", old files will not be deleted after recovery (successful or not).


[thread_count <integer>]
Specify thread count to parallelize the recovery. The default is 1 which means each space is recovered one after the other. Thread count 5 means five spaces will recover in parallel before we move to the next 5 or remaining if less than 5.

recover metaspace quorum 1 thread_count 16 recovery_policy  no_data_loss

[(with|without) data]
Recovery method to load data from persistence file or not (see note to recovery_policy)

Note: A detailed description of all parameters can be printed with the as-admin command "help -long <command>"

Example: as-admin> help -long recover metaspace

=====================================================

Can the SEEDER name (member name) be changed while space is reconfigured for Shared_Nothing?