microsoft / service-fabric-issues

This repo is for the reporting of issues found with Azure Service Fabric.
168 stars 21 forks source link

Backup fails to restore to remote collection #1558

Closed qmatto closed 4 years ago

qmatto commented 5 years ago

Hi,

I am trying to migrate our on prem workloads to Azure. I have a Reliable Collection backup set in a BlobStorage account, and have deployed the necessary services to Azure.

I am using the following REST command.

{
  "BackupId": "23aa0ace-2cc4-49e2-90bd-08db2df3d39a",
  "BackupStorage":  {
    "StorageKind": "AzureBlobStore",
    "ConnectionString": "DefaultEndpointsProtocol=https;AccountName=",
    "ContainerName": "asf-backup"
  },
  "BackupLocation": "d9ae2849-50c6-4214-8d3f-aff388f560a9\\2019-08-02 06.14.52.zip"
}

The backup ID I have used from the most recent backup of that service - the Cloud service, not the on prem.

The following URL

https:///Partitions/d9ae2849-50c6-4214-8d3f-aff388f560a9/$/Restore?RestoreTimeout=60&api-version=6.4

yields

{"Error":{"Code":"FABRIC_E_RESTORE_SOURCE_TARGET_PARTITION_MISMATCH","Message":"BackupId and Backup Locations are mismatch."}}

Can someone explain the process to restore a reliable collection to a different service location - which backupId should be used?

Cheers

raunakpandya commented 5 years ago

You should pick the backupId and backupLocation from the output of the backup for on prem. Hopefully you were able to resolve that.

qmatto commented 5 years ago

Hi @raunakpandya thanks for your response,

I have changed my method to the following:

This yields the following error:

{"Error":{"Code":"E_UNEXPECTED","Message":"Unable to get backup locations in chain."}}

raunakpandya commented 5 years ago

This means that the service while trying to walk through the backuplocation either couldnt find the same in the container or one or more of its preceding backups in chain. I am assuming you copied the backup ID, backup chain ID and backup location as is from the output of get backups. Is that correct?

masnider commented 4 years ago

Hi there @qmatto hopefully you were able to resolve this? I'm going to close down this issue since we haven't heard back from you. If you still are having issues, please reopen and answer Raunak's questions and hopefully we can sort it out for you.

Thanks -Matt