Solved "The machine name is invalid." error during Restore Backup.

Status
Not open for further replies.

problem_solving

Free User
Joined
Feb 22, 2022
Messages
2
Reaction score
0
I am trying to redeploy a backup onto a new AWS instance on the page https://portal.3cx.com/. "Self Host in your Cloud"

Step 1: No issues Do you have a 3CX backup you would like to restore?=yes, Select Backup using 2.21.22, etc.)
Step 2: No issues (Select Hosting=Amazon-AWS, Access Key ID,

Step 3: Possible Issues
Machine name = prepopulates Note: I have check/verified that the AWS instance name matches.
Region = select region that matches AWS Availability Zone
Key pair = prepopulates from AWS
Machine type = select machine type to match AWS instance machine type , in my case t2.micro

Step 4: no issues (License Agreement)
Step 5: Installing, "Your deployment is about to start"
The 3CX response = "The machine name is invalid." (only option is to chose "back" e.g. to step 3)

Notes: I have rebooted the AWS instance and renamed them (using different names and physically changing the 3CX Machine name to match, however I get the same error "The machine name is invalid."

Now just for Giggles I tried the following path:

Step 1: No issues (Do you have a 3CX backup you would like to restore?=no)
Step 2: No issues (Select the Time Zone= UTC-05:00; Select Language=Standard English)
Step 3: No issues (Extension Length)
Step 4: No issues (Select Hosting=Amazon-AWS, Access Key ID, etc.)
Step 5: Possible Issues
Machine name = prepopulates Note: I have check/verified that the AWS instance name matches.
Region = select region that matches AWS Availability Zone
Key pair = prepopulates from AWS
Machine type = select machine type to match AWS instance machine type , in my case t2.micro

Step 6: no issues (License Agreement)
Step 7: Installing, "Your deployment is about to start"
The 3CX response = "The machine name is invalid." (only option is to chose "back" e.g. to step 3)

Hopefully someone has a solution, maybe this will help someone in the future.
 
Resolved. Launched a new instance "debian-10-amd64-20210721"
Then backup was uploaded without error.
 
Provided I understood this correctly, the error you got was is expected.

Deploying via the 3CX Customer deployment wizard will always deploy a new machine, regardless of whether you select to restore a backup or not. If you already had a machine with the same name then the deployment will fail. When you specify the machine name during the deployment wizard, you are not specifying a machine to which the backup will be restored, rather, you are specifying a machine name for the VM about to be created, so, naturally if you already have a VM with that name it will fail as you cannot have 2 VMs with the same name.

In any case, glad to see you managed to get this sorted. Just remember to delete or shutdown the old machine if you have not done so already.

Note: If you want to keep the same name, you'll have to first check if you can rename existing machines via AWS's control panel, and if yes, delete the old machine first so that you can give that same name to the new one. I'd consult AWS's documentation before doing absolutely anything like this though in case this involves other changes or consequences too.
 
Status
Not open for further replies.

Forum statistics

Threads
111,974
Messages
590,081
Members
164,899
Latest member
mazet