Skip to main content

The archive could not determine the backup path.

Thread solved

Hello.
This is my client's Acronis 11.7 error.

They backed up the AMS server.
And they selected D drive of AMS backup from the recovery screen.
And the recovery target is a new virtual machine.

And when the recovery button was clicked, "Failed to check the backup path in -path-archive." Error message appears. (Reference: Image01)

However, the D drive is displayed normally in the recovery list or path. (Reference: Image02 ~ 03)

They want to recover the D drive.

What is the problem and what is the solution?

Attachment Size
image01.png 19.07 KB
image02.png 31.62 KB
image03.png 66.87 KB
0 Users found this helpful
frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 0
Comments: 2016

Hello Lemoning!

Please advise your client to refresh the vault where the backup is stored: it looks like a problem with metadata of that vault.

Please share the results on whether it solves the issue.

Hello Maria.

They tried it. But it still has problems.
One singularity is,
If they do the same at the initial backup location, the recovery will proceed normally.
However, if they move the backup file to the D drive of AMS and try the operation, the problem occurs.

They basically take backups on other equipment,
When they do recovery work, they want to work on D drive of AMS.

Is there a good way for you?

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 0
Comments: 2016

Hello Lemoning.

However, if they move the backup file to the D drive of AMS and try the operation, the problem occurs.

Unfortunately, I do not see the exact error message in the original activity log.

There could be two possible reasons:

1) The backup is moved to the D drive without its metadata XML file (i.e. only tib file is moved).

2) This D drive is not accessible from the Agent which initiates the recovery (this Agent simply connects to its own D drive). Please organize this new backup location as a network shared folder so the Agent accesses it by IP.