Skip to main content

Backup Replication to Cyber Infrastructure

Thread needs solution
Beginner
Posts: 3
Comments: 7

Hello,

 

Anyone that is doing replication to a Cyber Infrastructure appliance experiencing issues? When I initiate my replication job it sits there for 12 minutes and then it times out with error. The error just indicates that there was a timeout. 

I can see that my Cyber Infrastructure location is attached to the Cyber Protect console but there are no other indications as far as errors. I did try updating Cyber Infrastructure to version 4.70 (234). My Cyber Protect build is: 15.0.27009.

 

I've opened a ticket with support but no answer as of yet.

 

Here is a snippet of the error:

 

esult

{
    "code": "timedout",
    "error": {
        "domain": "task-manager",
        "code": "timedOut",
        "context": {
            "reason": "queue-timeout-expired",
            "span": ""
        },
        "type": "error",
        "startTime": "2021-11-19T17:12:41.434Z",
        "parentActivityId": "1143602156742377472",
        "isRoot": true,
        "cause": "Task timeout expired",
        "effect": "Task timeout expired",
        "index": 0
    }
}
0 Users found this helpful
Beginner
Posts: 3
Comments: 7

After restarting the Storage Node (which is also the machine with the Cyber Protect console), now I get the following error.

 

{
    "$module": "staging_command_vsa64_27009",
    "Time": 1637348015,
    "_src": {
        "code": 7504010,
        "fields": {
            "$module": "staging_command_vsa64_27009"
        },
        "src": {
            "file": "d:\\1759\\enterprise\\dms\\common\\task_execution\\source_processor.cpp",
            "func": "TaskExecution::SourceProcessor::ProcessLocation",
            "line": 75,
            "tag": "0x10851ec94f3c45b"
        },
        "suberror": {
            "code": 7504010,
            "fields": {
                "$module": "staging_command_vsa64_27009"
            },
            "src": {
                "file": "d:\\1759\\enterprise\\dms\\common\\task_execution\\source_processor.cpp",
                "func": "TaskExecution::SourceProcessor::ProcessLocation",
                "line": 76,
                "tag": "0x10851ec94f3c45c"
            },
            "suberror": {},
            "text": "One or more backups have been skipped when processing.",
            "types": {
                "$module": "A"
            }
        },
        "text": "The activity has succeeded with warnings.",
        "types": {
            "$module": "A"
        }
    },
    "cause_str": "One or more backups have been skipped when processing.",
    "effect_str": "The activity has succeeded with warnings."
}
Beginner
Posts: 0
Comments: 1

Yes same here, started a few days ago, no response from Acronis. Some of our backups have hung on replication

Forum Member
Posts: 12
Comments: 33

Good morning,

this could be helpful: Acronis Knowledge Base

 

Erik

Beginner
Posts: 3
Comments: 7

IT Helpdesk wrote:

Yes same here, started a few days ago, no response from Acronis. Some of our backups have hung on replication

Do you recall this started after possibly upgrading your Acronis Cyber Protect version? I had fully working replication before, but my monkey brain decided to upgrade Cyber Protect builds and all of the sudden replication no longer works.

I should have learned my lesson by now, NEVER, NEVER upgrade an Acronis product if it is working. This is the most finicky piece of software I have ever worked with.

Beginner
Posts: 3
Comments: 7

Erik Woltmann wrote:

Good morning,

this could be helpful: Acronis Knowledge Base

 

Erik

Erik,

 

I appreciate your response. I did get this same response from support. Unfortunately this did NOT work.

Forum Member
Posts: 19
Comments: 12

I thought the clients local storage backup to the ACI cloud location was automatic?

What are you all replicating?