Skip to main content

Validation Bug v15

Thread needs solution

If you validate multiple Backups in one Plan the validation will most likely fail with a timeout. Do it insted one by one.
It seems that it tries to start them all at once, but then only one is processed and the others timout after 10+ min. It only works if you have small Backup chains which can be quickly validated.

This worked in v12.5 

 

0 Users found this helpful

I get daily 2-5 validation error mails with possible data corruption alert. If i create a validation plan and just include the one that was stated in the error mail it validates without a problem (validate all backups not just last one).

Just tried it with 12.5 and instead of starting all at once it indeed did it one by one even if you throw many backups in one validation plan.

So basically the validation is useless at the moment for me. I get corruption messages which are then validated without a problem.

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 0
Comments: 2016

Hello somebody,

thank you for posting on Acronis forums!

If you validate multiple Backups in one Plan the validation will most likely fail with a timeout. Do it insted one by one.

The validation works as in Acronis Cyber Backup 12.5: it validates backups sequentially.

The validation can fail with a timeout error if a backup location of any single backup gets inaccessible at the moment of validation.

I get daily 2-5 validation error mails with possible data corruption alert. If i create a validation plan and just include the one that was stated in the error mail it validates without a problem (validate all backups not just last one).

I recommend that you open a case with Acronis Support Team for investigating the archive corruption issue.

 

 

It's not as in 12.5. Steps to reproduce:

  1. Create validaton plan
    1. put 3 or more backups in it (big ones preferred)
    2. choose "All backups" (important, only "last backup" works!)
    3. run
  2. The first one will be successful, all other start circling and will fail
{
    "code": "timedout",
    "error": {
        "domain": "task-manager",
        "code": "timedOut",
        "context": {
            "reason": "queue-timeout-expired",
            "span": ""
        }
    }
}

 

Attachment Size
559970-207251.png 22.3 KB
559970-207254.png 39.51 KB

The validation works as in Acronis Cyber Backup 12.5: it validates backups sequentially.

- Then it's no wonder it doesn't work anymore, because the scheduler seems to start all at once. When I create the validation plan with 2 or more backups and the option "All backups", they start circling and one ends sucessful all other fail. Tried it with format 12 local storage and format 11 dedup storage. I could even reproduce the issue on a fresh install!

It's only sucessful if i use "last backup" instead of "All backups" option, because it doesn't reach the "queue-timeout".

{
    "code": "timedout",
    "error": {
        "domain": "task-manager",
        "code": "timedOut",
        "context": {
            "reason": "queue-timeout-expired",
            "span": ""
        }
    }
}

 

Step 1: Create a validation plan

Step 2: Select 2 or more Backups (this doesn't occur if you just use a small backup archiv) not the complete location

Step 3: Select "All backups" option

Step 4: Run

 

Attachment Size
560044-207299.png 22.3 KB
560044-207302.png 39.51 KB
frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 250
Comments: 7092

Hello tim tim,

our QA team wasn't able to reproduce the issue. Could you please clarify the size of archive being validated? 

I also have the same issue.  I'm backing up to 4 disk Raid 0 eSata device.  Selecting more than one backup set to Archive will generate the error below.  If I setup Backup Replication to only use one source at a time it works without timing out.  I do see in Activities for the job that both sources are trying to backup at the simultaneously. 

image 291

image 292

image 293

 

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 0
Comments: 2016

Hello Lou Kalis,

thank you for posting in this forum thread!

Please consult this KB article and follow instructions provided there: https://kb.acronis.com/content/63997

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 0
Comments: 2016

Hello all!

There is a new KB article published for issues with off-host data processing plans that fail with timeout error if several backups/locations are selected “Task timeout expired”:

https://kb.acronis.com/node/68166