Comprehensive data protection for all workloads
Post Reply
Frosty
Expert
Posts: 182
Liked: 40 times
Joined: Dec 22, 2009 9:00 pm
Full Name: Stephen Frost
Contact:

Scheduled backup hung at "Starting" status

Post by Frosty » Mar 22, 2010 9:27 pm

I have four (4) backup jobs scheduled to run each night. Last night one of them (the 2nd in the sequence of 4 jobs) seemed to 'freeze' and when I came in this morning its status showed "Starting" and it had been that way all night. I was able to force the job to stop. It warned me that this would leave the backup files in an uncertain state. I then re-ran the job manually and it worked just fine.

I'm running v4.1.1 and am wondering if anyone else has noticed this kind of issue? Its not happened to me before, although I have only been running backup jobs for a few weeks so far (I used VM Copy jobs before that).

Gostev
SVP, Product Management
Posts: 25145
Liked: 3698 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland
Contact:

Re: Scheduled backup hung at "Starting" status

Post by Gostev » Mar 22, 2010 9:56 pm

Hello Stephen, we would need to see full log files to tell you what exactly the job was doing (or waiting for) while hanging in the "Starting" status. Please contact our support and provide all logs from Help | Support information for investigation.

Frosty
Expert
Posts: 182
Liked: 40 times
Joined: Dec 22, 2009 9:00 pm
Full Name: Stephen Frost
Contact:

Re: Scheduled backup hung at "Starting" status

Post by Frosty » Mar 23, 2010 12:24 am

Thanks Gostev.

I had a look through the logs. Found that it was caused by SQL connection timeouts, causing the Veeam Backup Manager (process?) to fail. I will keep an eye on it and if it happens again I will log a call.

Cheers,

Steve.

Gostev
SVP, Product Management
Posts: 25145
Liked: 3698 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland
Contact:

Re: Scheduled backup hung at "Starting" status

Post by Gostev » Mar 23, 2010 12:29 am

Steve, just wanted to note that Veeam Backup Manager is UI process, so it does not participate in job management. You need to be looking at the corresponding job's log instead. But in any case, potential SQL issues may of course affect the jobs as well.

Post Reply

Who is online

Users browsing this forum: Bing [Bot], Google [Bot] and 18 guests