Veeam replication job goes to 97% and then doesn't finish

[gthomson@pylusd.org]

Recent install of Veeam Enterprise 6.5, and upgraded to v7.
ESXi 5.0 is the virtualization environment.
Upgrade isn't the problem, same problem on v6.5.
More likely my lack of understanding of Veeam and snapshots that's the problem.

I'm trying to get an MS SQL 2008 server replicated to a remote location.
It has 4 volumes:
80gb - O/S
700gb - .mdf files
100gb - .ldf files
600gb - mostly .bak files

I have a Veeam replication job replicating to what will be a remote setup, but is currently local.

It seems to get through the first three volumes okay.
Last volume, it never finishes - stayed at 97% done for quite a few hours.

I don't see a way to upload photos, and don't know if links will work here, but if it's helpful - here's a link to a graphic:
http://www.gthomson.us/temp/veeam-support1.jpg
If you can see it, what is that graphic telling me?

Greg

[foggy]

Gregory, have you already contacted technical support with that? If yes, what is the support case ID? If no, please do as debug logs investigation is definitely required to understand what's the job is doing at that very moment.

Btw, does the hard disk read count (551.8 GB currently at the screenshot) changes with time after the job reaches that 97% point or the job is completely stuck?

Thanks!

[gthomson@pylusd.org]

I don't have a case id, thought I'd try the forums first since it may just be admin error at this point.
But I'll submit as a new case if that's better.

Re: 551.8gb,
I think I only watched that number intermittantly for maybe 15 minutes, and it was after the job registered at being 97% done, and it stayed the same.

Greg

[foggy]

Let's see what our support can say after reviewing the logs.

[gthomson@pylusd.org]

Problem resolved.
Submitting the case helped me find the logs (although they were in a different location than mentioned in the helper tip when submitting the case.)
But looking at a few of the logs triggered something.
Problem was the remote SAN volume the replication was going to didn't have enough space.
Bumped that up, and job finished okay today.
Based on the graphs showing mentioned earlier, seems like it probably kept re-trying to write in case more space became available.

[veremin]

Thanks, Gregory, for coming back and updating the topic with the found resolution.