Standalone backup agents for Linux, Mac, AIX & Solaris workloads on-premises or in the public cloud
Post Reply
Machariel
Novice
Posts: 6
Liked: never
Joined: Feb 03, 2021 4:17 pm
Full Name: Jared DeWitt
Contact:

Job hung at 50% but Agent Backup shows 98%

Post by Machariel »

Case: #04652448

I'm trying to back up from a Linux agent. The files that are to be backed up are mounted to a SMB share on another Linux box. When I back them up, it seems like it's working fine. I can see all 9TB being backed up.

The job seems stuck now. When I take a look at the job, I can see the Job Progress is 50%, but the agent is showing 98%. This is the only agent assigned to this job, so it's odd that the entire job is stopped at 50%.

The error that I'm receiving is....

There was no finalized server sessions during the last 60 minutes.
[17.02.2021 02:12:09.195] <140625827563264> cli | WARN|Timed out to wait for updates trigger
[17.02.2021 02:12:09.322] <140625810777856> cli | WARN|Mount cleanup thread : cycle timeout

That error just repeats.

Image
PTide
Product Manager
Posts: 6431
Liked: 729 times
Joined: May 19, 2015 1:46 pm
Contact:

Re: Job hung at 50% but Agent Backup shows 98%

Post by PTide »

Hi,

Typically when VAL backs up network shares it does not have any means to figure out how much data has been laready backed up and how much more data is left. Therefore, the progress may hang for a while.

Is SMB share the only object in the backup scope, or there are other disks? If the latter, then how big is the backup set that resides on SMB?

Thanks!
Machariel
Novice
Posts: 6
Liked: never
Joined: Feb 03, 2021 4:17 pm
Full Name: Jared DeWitt
Contact:

Re: Job hung at 50% but Agent Backup shows 98%

Post by Machariel »

Yeah, the SMB share is the only thing being backed up. There should be about 18 TB to back up, so the overall progress seems correct.

I tried building a new job on the client server and having it save directly to another SMB share (so basically just using VAL as a free product), and I'm seeing the same issues. Once the Job progress hits around 9TB and 50%, it hangs up.

Job.log (Last Message was over 3 hours ago)
[19.02.2021 06:45:07.129] <139894718453504> vmb | pex: 10146163980117/10146163980117/0/10146163980117/10148027352496 / 77/57/11/0/57/8
[19.02.2021 06:45:07.130] <139894718453504> vmb | Session progress: 51%; processed: [10146163980117/7130054656] read: [10146163980117], transfer: [10148027352496] speed: 76207314 bottleneck: 77/57/0/57

Agent.Source.log
[19.02.2021 08:44:50.997] <139746584012544> cli | WARN|Timed out to wait for updates trigger
[19.02.2021 08:44:51.097] <139746172966656> cli | WARN|Mount cleanup thread : cycle timeout
[19.02.2021 08:46:09.949] <139746844428032> srv | There was no finalized server sessions during the last 60 minutes.

Agent.Target.log
WARN|MTA invoke thread : timed out for backup events. Wait cycle will be resumed for '336' hours.
[19.02.2021 07:46:09.460] <139663268120320> srv | There was no finalized server sessions during the last 60 minutes.
[19.02.2021 08:46:09.507] <139663268120320> srv | There was no finalized server sessions during the last 60 minutes.
Post Reply

Who is online

Users browsing this forum: No registered users and 6 guests