question

MichaelWilcox-2099 avatar image
0 Votes"
MichaelWilcox-2099 asked karishmatiwari-msft edited

Regarding migration to azure-cloud-services-extended-support - How can we 'back out' of a migration ?

Regarding migration from Classic to azure-cloud-services-extended-support
Assuming we use the 'in place migration' see https://docs.microsoft.com/en-us/azure/cloud-services-extended-support/in-place-migration-overview and we need to back out the migration ie revert back to the original classic environment ? Basically, my client wants to do the in place migration, however, if for some reason the applications do not pass a validation test after the migration they want to revert back to the original classic environment.

azure-cloud-services-extended-support
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

MichaelWilcox-2099 avatar image
1 Vote"
MichaelWilcox-2099 answered

As of 05/05/22 there is not 'back out' or revert 'to the original option for the in place migration.
So we assume if we want a back out option we have to use the 'redeploy ' option ?

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

karishmatiwari-msft avatar image
0 Votes"
karishmatiwari-msft answered karishmatiwari-msft edited

@MichaelWilcox-2099
Thanks for sharing the details. This is the lifecycle of the migration process as explained in this document.

199786-image.png


Here are the FAQs that should help answer your questions:

Can I roll back after my migrating resources are committed in Resource Manager?
You can abort your migration as long as the resources are in the prepared state. Rollback is not supported after the resources have been successfully migrated through the commit operation.

Can I roll back my migration if the commit operation fails?
You cannot abort migration if the commit operation fails. All migration operations, including the commit operation, are idempotent. So we recommend that you retry the operation after a short time. If you still face an error, create a support ticket.

In case of in-place migration, the platform deletes the Cloud Services (classic) resources after migration. Reploy option might work better for you as you can deploy a new cloud service directly in Azure Resource Manager and then delete the old cloud service in Azure Service Manager thorough validation. The differences between the two process are documented here.

You may also find these documents helpful:

https://docs.microsoft.com/en-us/azure/virtual-machines/migration-classic-resource-manager-errors
https://docs.microsoft.com/en-us/azure/virtual-machines/migration-classic-resource-manager-faq

Let me know if you have further questions.



image.png (48.9 KiB)
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.