Hello, Thanks, I have a backup copy job from 12/27/2023 and I cannot stop it.
The ‘Stop Session`menu option is disabled.
The job details shows the job that stuck at 13%
The job details also show that the job completed.
Not sure what is going on, Please advise
Page 1 / 1
It looks like the dashboard/working area is latent. The actuall job is stopped. Close the Console then re-open to see if it updates.
Please ignore, I deleted this post.
What type of job is that running? Is it a VM backup, agent, etc.? In the second screenshot that is on top of the console showing the job if you click at the bottom on the left side to highlight the Server - the right should change to show you if it is working on anything. But from what I can see and like Shane said the job is done.
What version of Veeam also are you running? That is helpful.
Sorry, I am a bit vision limited and at first, did not see this teeny image.
But from what I can see and like Shane said the job is done.
Sorry, The image is not clear It started on 12/27/2023, is stuck at “13% completed” and there is no “End Time”
What version of Veeam also are you running? 12.0.0.1420 P20230718
I guess the only other option would be to try rebooting the VBR server to see if that clears up the stuck state. You could also try upgrading to 12.1 as they have done lots of work around console refresh.
Yeah..can either try a server reboot, or close the Console, go into Services, and do a restart of the Veeam Backup Service. It takes several minutes to stop then start, so be patient.
I noticed the issue a week ago, but was not able to deal with it then.
For some reason, the issue went away and I am not sure why.
Thanks,
Glad to hear; btw...this happens in my Console sometimes. Though, not for that long. But sometimes refresh of items in the Console can be latent. One (minor) ‘gripe’ I have about the Console.
Version 12.1 works well with console refresh.
Console refresh has been a problem for yrs….just sayin’. If 12.1 is better, I’ll be looking fwd to it when I upgrade
I did windows update, then 12.1 update and now that issue has gone away
Once again, Thanks to all!
I did windows update, then 12.1 update and now that issue has gone away
Once again, Thanks to all!
Glad to hear the issue is resolved.
So now that I have upgraded to 12.1, from the console, i get getting this error, anybody else getting this? i did search the R&D forum but did not find anything
the token supplied to the function is invalid
So now that I have upgraded to 12.1, from the console, i get getting this error, anybody else getting this? i did search the R&D forum but did not find anything
the token supplied to the function is invalid
Never seen that before. May need to open a support case to get help with that if the logs don't give you any details - C:\ProgramData\Veeam\Backup
now, i get the following error.
in am my time using veeam, not really got an serious error. and i am trying to understand what it means, is that backup chain corrupted? any way to recover that?
so, after that, each incremental failed, so i forced an active full and that was successful.
any ideas?
Error: A data integrity checksum error occurred. Data in the file stream is corrupt. Asynchronous request operation has failed. requestsize = 278528] offset = 1609728] Failed to open storage for read access. Storage: ABP_EN10_F2024-01-09T183334.vbk]. Failed to restore file from local backup. VFS link: summary.xml]. Target file: MemFs://frontend::CDataTransferCommandSet::RestoreText_{34288fa2-1919-4b8b-93cd-627adbe16253}]. CHMOD mask: 378]. Agent failed to process method {DataTransfer.RestoreText}
There is something corrupted in the previous chain. That is why the active full worked.
In the end, It was an issue with a hard drive in the storage pool. I replaced the hard drive and all is good.
thanks,
In the end, It was an issue with a hard drive in the storage pool. I replaced the hard drive and all is good.