Backup Copy Job - Hard Disk 1 - 0.0 KB read at 0KB/s

[Dave-Departed]

Hi All,

Another BCJ query...

I've seen this on a few of my BCJ's so far (seems intermittent, and not always the same BCJ affected), but I've got one running right now, where it has been sat on:

Hard disk 1 (25.0 GB) 0.0 KB read at 0 KB/s

For almost 2 hours.

There are no issues (that I'm aware of) with the regular backup job, it's been running successfully for months and months now, and yesterday, this very same BCJ completed successfully.

Anyone seen this before? Is there a timeout on this particular step, or should I just stop the job?

Thanks

Dave

[veremin]

Hi, Dave, have you had a chance to open a ticket on this issue? According to our QA team, they haven't seen similar issues so far, and it seems that corresponding logs are required for further investigation.

Thanks.

[veremin]

Additionally, after this "suspension" do you see any message regarding synchronizing global cache like "Synchronizing global cache from target" or similar? It might happen that during this period global cache is being synchronized between source and target. As the result, job seems to be doing nothing.

Thanks.

[Dave-Departed]

Hi Vladimir,

I've not opened a ticket yet, because I didn't know if it was just an expected behaviour (or a quick fix, in case someone else had seen it too). I've already got a ticket in progress for other problems with our Backup Copy Jobs, so I will probably just add it to that list hehe!

As for any other messages, no, I don't see anything else. It's still sat on the same thing right now, after 3.5 hours! I've definitely seen the 'synchronizing global cache from target' message before, but not this time. I can see there is WAN activity, but there is nothing in the Throughput window. My question is, why would it need to sync the global cache from target if the job ran successfully for the last 3 days in a row?

Thanks

Dave

[veremin]

Occasionally, cache between source and target needs to be synchronized. There are no issues with that, it's just the way it works.

As to support case, opening a ticket will allow support engineers to confirm whether the suspension is related to cache synching or not.

Thanks.

[RMullis]

Hi Dave-Departed,

I had a similar issue where I had let in sit overnight with no change in job %. I contacted support and they had me disable parallel processing and it worked great. Since R2 I tried again, hoping i would be able to use parallel processing but I saw the same issue so I again I had to disable it.

Rick

[Dave-Departed]

After watching the job(s) in question, I think you're right, Vladimir... There is still network traffic at a high rate between the local and remote VBR servers when the job is sat looking like it's doing nothing. And eventually, the next step kicks in, and the backup completes shortly after!

[Dave-Departed]

Hi Rick,

Cheers for the input, I will try that later tonight and let you know!

[tfloor]

I also see this issue:

screenshot:
http://gyazo.com/f2362d84860ddbf0ab394c6b5e12aba3

Rebooting veeam servers doesn't work.

[tfloor]

I also see this issue:

screenshot:
http://gyazo.com/f2362d84860ddbf0ab394c6b5e12aba3

Rebooting veeam servers doesn't work.

But if you are lucky he is going further after a long time

[Dave-Departed]

Occasionally, cache between source and target needs to be synchronized. There are no issues with that, it's just the way it works.

Vladimir, could this be taking so long because our remote site uses ADSL with 8mbps Down and 500kbps Up speeds? So sending data to remote site is fine, but if anything has to come back the other way (like syncing global cache from target > source), it's gonna be crawling?

Thanks

Dave

[foggy]

I think this could have some impact on the overall performance.

[menthol]

Sorry if this is too old to reply to, but just incase anyone has the same issue, I fixed it by clearing the cache of both WAN Accelerators and then triggering a new sync and it's now reading the disk at 3mb/s.

Thanks

[veremin]

Hi, Brad, thank you for taking time and providing found resolution; much appreciated.