6.1.0.349
I had looked at the log in the Backup folder.
Bingo, from log:
3 times:
[13.02.2024 09:07:18] <34> Info AP] (9f02) output: --asyncNtf:--vdisk_corrupted:\\.\PhysicalDrive0
13.02.2024 09:17:58] <01> Info AP] Waiting for completion. Id: n0x1e75bc1], Time: 00:30:00.0112192
213.02.2024 09:37:11] <32> Info AP] (cc2e) output: --asyncNtf:Pipeline timeout: it seems that pipeline hanged.
a13.02.2024 09:37:11] <17> Info oAP] (1147) output: --asyncNtf:Pipeline timeout: it seems that pipeline hanged.
i13.02.2024 09:37:11] <32> Info ;AP] (9f02) output: --asyncNtf:Pipeline timeout: it seems that pipeline hanged.
p13.02.2024 09:37:18] <32> Info 3AP] (a7f9) output: --asyncNtf:Pipeline timeout: it seems that pipeline hanged.
h13.02.2024 10:37:18] <42> Info AP] (a7f9) output: --asyncNtf:Pipeline timeout: it seems that pipeline hanged.
etc, etc.
n13.02.2024 10:47:58] <01> Info 4AP] Waiting for completion. Id: 0x1e75bc1], Time: 02:00:00.0462863
Wonder why it goes on so long… Still going, over 2 hours on that one bad partition now. It is a restore partition so I will just delete it. Windows always makes a new one. Will wait until I get a good backup.
Thanks. Like I said, wait for the next version and try again.
Lou
Oops, gave myself a pat on the back by mistake.
Thanks all.
Oops, gave myself a pat on the back by mistake.
Thanks all.
If you feel another answer should have been selected, we can have @Madi.Cristil or @safiya reverse it for you @louyo
Just let them know here.
Well, kudos should go to you Chris.Childerhose, you put me onto the right log. Clicked to quick, sorry for the screw up.
Never enough time to it right but always enough time to do it over...
I’ve not seen any posts on here lately about Agent for Windows having a problem backing up a drive; especially not that close to finish. I assume you’re on the latest current version of the Agent? (v6.1)
What version of the Agent are you using for Veeam? Did you check in the log files here to see what might be causing the issue - C:\ProgramData\Veeam\Endpoint?
Details are helpful for these types of issues. Better to also open a support ticket as well.
Glad to hear you were able to solve the issue with the logs.
Well, kudos should go to you Chris.Childerhose, you put me onto the right log. Clicked to quick, sorry for the screw up.
Never enough time to it right but always enough time to do it over...
No worries looks like it got changed.