We are having issues with these. Sometimes they work and sometimes they don't. When they fail, we get Task Exception Errors like these:

• Exception in Task: Object reference not set to an instance of an object.
  
• The given key was not present in the dictionary.
  
• Value cannot be null.
  

We actually run two backup jobs - the default one and one that backs up the settings to a network share. The network share job almost never fails, only the local job.

However, in the last 2 days, 2 different machines have gotten "stuck" in the Running status (both jobs, local and network share) and would not stop until I restarted the VisualCron service.

The real problem is when they get stuck, they are using a TON of resources (25% CPU and hammering the disk drives.) One of these occurrences were on a production web server. I'm not sure what to do to troubleshoot the issue.

1. which version are you running?
2. can you confirm that you only get this on local backup?
3. how large is the resulting file`?

We are having issues with these. Sometimes they work and sometimes they don't. When they fail, we get Task Exception Errors like these:

• Exception in Task: Object reference not set to an instance of an object.
  
• The given key was not present in the dictionary.
  
• Value cannot be null.
  

We actually run two backup jobs - the default one and one that backs up the settings to a network share. The network share job almost never fails, only the local job.

However, in the last 2 days, 2 different machines have gotten "stuck" in the Running status (both jobs, local and network share) and would not stop until I restarted the VisualCron service.

The real problem is when they get stuck, they are using a TON of resources (25% CPU and hammering the disk drives.) One of these occurrences were on a production web server. I'm not sure what to do to troubleshoot the issue.

---

1. which version are you running?
2. can you confirm that you only get this on local backup?
3. how large is the resulting file`?

1. 6.2.2
2. I know it's confusing, but it's NOT just the local - the local was the only one generating those errors - the "failure" that occurred the last two days, generated no errors, but did cause performance problems and in this case was the local AND the remote share job once and then last night was just the remote share job.
3. Screenshot attached

Soooo...........any thoughts on this?

FYI, this did not start until about 2-3 months ago.

Even though we have not heard of this issue before we will release a new version with an updated zip component to see if that solves the problem. This will be included in the 7.0.0 beta.

---

ETA?

The beta with that change will probably released within one week. Public version 3 weeks. weeks.

---