Last night we ran out of space on one of our client servers on the D:\ drive which is where the VisualCron software is saved. We were placing files in a queue to keep some import tasks running 24X7. VisualCron crashed and we lost all tasks and jobs on the server. We have a Backup Settings job that runs every day so we didn't lose too much work other than the work we did between backups. However, should this work like that? Very scary; I'd hate to think what we would have done if we didn't have backups. I highly recommend that everyone creates one of those (Backup Settings) as a standard practice and additional ones as well if you need to.

Last night we ran out of space on one of our client servers on the D:\ drive which is where the VisualCron software is saved. We were placing files in a queue to keep some import tasks running 24X7. VisualCron crashed and we lost all tasks and jobs on the server. We have a Backup Settings job that runs every day so we didn't lose too much work other than the work we did between backups. However, should this work like that? Very scary; I'd hate to think what we would have done if we didn't have backups. I highly recommend that everyone creates one of those (Backup Settings) as a standard practice and additional ones as well if you need to.

I agree, this is something that needs to be handled in some way.

---

So the software is working as designed when it does this (runs out of space and erases all the jobs/tasks?

Well, what happens is that saving of Jobs occur when Jobs have been changed or around every minute. It writes the file sequentially to disk. So, what happens is that it may succeed in writing 10kB before an error is thrown that the disk is full. The Jobs are still in memory and VisualCron will try to save again. But if the service is restarted during low diskspace it will try to load the latest file, the corrupt one.

The idea is to change this so that checks this space or allocates before overwriting. Still, it is hard to reproduce the exact same scenario.

---

This information is probably somewhere so I apologize if it is and I haven't found it...What is the minimum amount of space we MUST have to prevent this in the future, any idea?

This information is probably somewhere so I apologize if it is and I haven't found it...What is the minimum amount of space we MUST have to prevent this in the future, any idea?

It depends on size of data. But you should have at least 100MB free.

---