Error: the Submission Did Not Complete Successfully. Please Try Again.
Updated 26/08/2017: [Please notation that if you currently delete the Management Azure Backup Server from Azure Portal, all the Cloud Recovery Points will be deleted in Azure.]
Introduction
Microsoft Azure Fill-in Server (MABS) inherits the same functionality of System Center Data Protection Manager (SCDPM) for workloads backup, so if you are familiar with SCDPM, MABS looks very similar. However, MABS does not provide protection on tapes nor can integrate with whatsoever Organisation Center component, so if you need Organisation Middle integration then you need the total SCDPM license for that. Besides that, MABS comes without a Organisation Center license, and is gratuitous to download. Did I say free? Yes, it's Gratis!
For more data about MABS, delight check the following article.
The result
I take an exiting Azure Backup Server deployed in my environment and registered with Azure Recovery Services Vault.
I have some VMs protected on-premises and to Azure as well. I created a new Recovery Services Vault and decided to move to the new Vault. The reason behind this is, the old Recovery Services Vault was created with Geo-Redundant Storage (GRS) which toll 4.8 Cent / 1GB / Month. The new Recovery Services Vault is configured with Local-Redundant Storage (LRS) which cost 2.four Cent / 1GB / Month, then half the price!
Equally a side note, in one case you lot create the Recovery Services Vault and configure the Storage (GRS or LRS), you cannot change the storage configuration. This is a one time operation.
When I tried to register Azure Backup Server with Azure, I received the following error:
The activation did not complete successfully. And if y'all click on More Information link, you will be redirected to a non relevant link: Organization Heart vNext Information Protection Manager fault codes.
Next, I tried to uninstall the Microsoft Azure Recovery Services Agent and then I re-installed the amanuensis again.
In one case you install the Recovery Services Agent, you will be directed to register this server with Azure Backup vault.
When I tried to register Azure Backup Server with Azure again, I received a similar error to the previous one just with additional details:
The activation did not complete successfully. The current operation failed due to an internal service error "Authorization Failed". Delight retry the performance after some fourth dimension. If the issue persists, please contact Microsoft support.
The error description is not articulate and the More Information link is the same.
At present y'all tin web search this one and find very little information or people having issues with normal Azure Fill-in functions like Azure Fill-in installation fails, or Azure Backups operations fail with error message "Unable to communicate to authentication service", or you should uninstall everything and reinstall everything once more. etc. This doesn't sound skilful, does information technology? Actually is not helpful.
Finding the cause
What was causing this result?
And then when I look at the Azure Portal under Recovery Services Vault | <Vault Name> | MANAGE | Backup Infrastructure | Direction SERVERS | Fill-in Direction Servers
Aye I know information technology'south a long path :) I found the AZURE BACKUP AGENT VERSION ii.0.9081.0
Then the server is registered with the new Vault merely information technology's not showing on-premises.
If nosotros look at the Microsoft Azure Backup Server console under Direction | Online – we tin come across that this server is not registered with Azure Backup. Click Annals to brainstorm the registration process.
However, the Azure fill-in agent version on-bounds ii.0.9082.0 does not match the agent version reported to Azure ii.0.9081.0
BINGO! That was the 1 and merely common gene
Fixing the event
The fastest way to solve this issue was to delete the server from Azure Portal.
Once the server is deleted from Azure (Deleting the server is a one fourth dimension operation and cannot be undone), you can register the server over again and the operation will be succeeded.
Root cause?
Microsoft has updated the Azure Backup agent for Microsoft Azure Recovery Services Agent: August 2017.
As stated in the Known issues section of the article. When you try to register a server that is running this update of the MARS Agent to a Recovery Services Vault on which it was previously registered, the MARS Agent does not get registered, and you receive the post-obit fault message:
The current operation failed due to an internal service error "Authorization Failed". Please retry the operation after some time.
The commodity state to successfully annals a server to the desired Recovery Services Vault, follow these steps:
- Open up the Azure portal by using the following URL, and then log on as usual.
- Open the Recovery Services Vault to which you intend to register the server, and then download the vault credential file.
- Register the server by using the downloaded vault credential file.
In my example, I tried the steps mentioned in a higher place, however, without success. When deleting the server from the Azure portal and so register it again it works!
Promise this helps someone out in that location!
Cheers,
-Ch@rbel-
Source: https://charbelnemnom.com/azure-backup-server-registration-failed-to-microsoft-azure-recovery-services-vault-azure-azurebackup-mabs/
0 Response to "Error: the Submission Did Not Complete Successfully. Please Try Again."
Post a Comment